Search results

:D Nothing left to paint. Realtek used it's master brush and filled the canvas years ago.

@OP - Are you using a driver that you converted/loaded using ndisgen and then kldload-ed by any chance? Till date 'ifconfig destroy' hangs FreeBSD for lots of broadcom and some other wifi cards.

Thank you for the response. I am now using this - did a bit of hardening. X-Powered by header is gone but will need to test the webpages again - incase it broke something inadvertently [PHP] register_globals = off engine = On short_open_tag = Off precision = 14 output_buffering = 4096...

I know the php method but FreeBSD runs php without a php.ini file, so I was wondering. Setting up a php.ini file means all other parameters within the file too would need to be checked, rather than letting the current default ones being as it is.

From the response header how do I get rid of X-Powered-By: PHP/x.x.x header? I am using lighttpd. I have enabled mod_expire but I think this has something to do with php.ini but there is no file called "php.ini" rather .production .development file instead? Let me know if I can disable...

Realtek ALC strikes again. At this point we don't even need to ask, its's always the latest Realtek chip and drivers - either microphone doesn't work or works as if it is suffering from a new strain of SARS (insert year).

Reflects well in TUI file-managers as well but only using Putty (need to save for every session) but it's fine. Thank you.

Umm.. dmesg.. from Ubuntu compat? RPC calls over HTTP were expected. Tried other ports, same issue. Tested both these software on windows, same command-line, worked fine.

Simple question. Has anyone faced issues opening up and listening onto ports via Linux compat (Ubuntu)? More info: https://forums.freebsd.org/threads/consensus-clients-for-ethereum.92681/post-647713

I was trying to run lighthouse - a rust-based ethereum consensus client which needs to listen onto some ports and it cannot open up ports to listen: CRIT Unable to listen on libp2p address listen_multiaddr: /ip4/0.0.0.0/udp/9001/quic-v1, error: Other(Custom { kind: Other, error...

I realized that the message about unavailability of a consensus client is a warning, not an error. It is not essential if one just wants to test if a sync can be performed. I don't need to stake or validate anything. Although that does not solve the above issue, it is not a problem for me...

Had tried prysm it earlier. Tried again. go build -o=../beacon-chain ./cmd/beacon-chain go: downloading github.com/mmcloughlin/addchain v0.4.0 # github.com/prysmaticlabs/prysm/v5/crypto/bls crypto/bls/bls.go:19:14: undefined: blst.SecretKeyFromBytes crypto/bls/bls.go:24:14: undefined...

Prysm is a consensus client. Sadly broken as of now.

I asked an LLM to list some more. Will try these now: Trinity - developed by the Ethereum Foundation (https://github.com/ethereum/trinity) Artemis - developed by PegaSys (https://artemis.pegasys.tech/ Eth2-cl-box - developed by the Ethereum Foundation...

:( what can we do? There is literally not a single working eth consensus client for FreeBSD :(

git clone https://github.com/sigp/lighthouse.git cd lighthouse If you do not like git, you may directly download the zip : https://github.com/sigp/siren/archive/refs/heads/stable.zip unzip it and then pleae try from inide that directory: cargo build --release I am getting compiling errors...

Hello does anyone know if there are any consensus clients for Ethereum available a pkg? I tried the following: Lighthouse, although in rust, is uncompilable due to lack of support for FreeBSD OS - hardcoded limitations and checks. prysm just goes dumb and says nothing when I try the beacon...

astyle I am not angry and it is you who is not paying attention to understand what I did exactly and why in my previous reply. I doubt if you even read my entire response.

elgrande No, you are wrong, lying and are (even if you didn't mention it) "mindlessly watching YT videos" and not following manuals as per the truer and holier than thou responder above your post. Go and read the manual. Just because every other pkg works after 'pkg install' does not mean...

astyle You think people haven't tried that (following the manual) already?