How would I go back to Chromium as the default browser?? Something like
xdg-settings set default-web-browser chromium.desktop

This should work:
xdg-settings set default-web-browser chromium-browser.desktop

dtoverlay=vc4-kms-v3d
in the config.txt file.This is the composite video overlay

Thanks for the info Jay. I just played with the file until I found the right combination. I didn't take the time to look up what vc4-kms-v3d was used for. I also wasn't sure if commenting it out would create issues for users that connected a monitor to their Pi part time.

I have to say that I don’t think Bullseye is ready for prime time. I don’t have the wherewithal to hop on the 64-bit BaP beta testing right now, but I’m finding other problems with Bullseye in general that make me want to stay on the rock-solid Buster on my production Pis

I am still running Buster on my main Pi but Bullseye has gotten better.? I am slowly moving every system to Bullseye. My main Pi will be the last to get the upgrade as this is where I write the vast majority of my code. As much as I hate to admit, Bullseye reminds me of past Microsoft blunders (Windows ME).

also worked for me, I removed the HDMI emulator and have appropriate Conky positioning and NO Chromium lag.

There's almost always multiple ways to accomplish a task with Linux :-)

--

David -- good morning.

Raspberry Pi WiFi is not very good!
I too have suffered hours of frustration trying to get it to work after it appears -- usually after a reboot -- to stop working!

VERY frustrating.

The 'WPA Supplicant' is a small text file that essentially tells your WiFi hardware what to do.
If this becomes corrupt -- or doesn't exist, then you will have no WiFi.

I'm not in my shack at present -- but later this evening I will be and I'll try and help you sort out your issues.
Don't despair, this is a VERY common issue.

If there are others on the forum who are close to their Pi's maybe they can jump in and help :-)

73
Bruce G4ABX

Jason,
Those settings that you used:

also worked for me, I removed the HDMI emulator and have appropriate Conky positioning and NO Chromium lag.

Thanks for the update!
73 WH6A

? Hello and thank you all...? Well I struggled last nite after a fresh install of build a pi on a pi4b 8 g in ar gon case.
I have conky running to check the ip info.. have wire but no wireless.. I checked the wifi settings and each time I check it it has gone back to interface after closing...? ?after setting it to ssid and choosing network.? I have tried raspi config and it tells me? "Could not communicate with wpa_supplicant? ?"? ? I saw someting in the posts but i did not quite catch what to do with the information there, but seems there is some missing code..??? ?
Any help will be greatly appreciated.....? ?For futre notice I plane to run headless to a samsung tab a with vnc already installed,, which I struggled with last nite not realising I had no wifi.. hence no vnc connection.
?Be warned I am not fimiliar with linux... so plz have patience with a guy trying to learn...lol

Thanks to all for this huge project!!? Oh i installed the build a pi with all features...?
73?

On Sat, Mar 5, 2022 at 07:32 AM, km4ack wrote:

In Pat Menu, click on "quick stats" and post a screenshot please.
--

73, de KM4ACK

|

|

?

?

开云体育

I'm running Bullseye 11.2???? 32 bit on a Pi 3B+
I installed WSJT-X prior to installing latest PAT.? Running the full FLDIGI suite with PAT, ARDOP, etc.? Jason found some problems with my PAT config and helped me to clear that up.? Have run with an ICOM 705 and an FT-817 .. Signalink for audio on the 817 and generic USB to serial for CAT.
73, K2KGJ

Jay:

I've forked my systems, roughly 2/3rd will be staying on Buster 32 due to RPiFoundation's dropping support for projects that have been supported from the beginning, namely PiCam (CSI Cameras, motionEye/motionEyeOS, etc.).
I agree with your assessment as to puppy dogs. I am trying to move forward into Bullseye 32, but am finding more and more projects are dumping 32 bit, also (FlatPak, AppImage, etc.)
Unfortunately, at least in the SBC arena, there isn't the 'nice' conversion processes available. I really feel sorry for the other SBCs, though, that don't have the community that RPi does. I love Jason's community, here and on Github, trying to help him move forward (and sideways <grin>)...

Kevin -- KD9EFV

New discovery this morning.? If I have my radio and power supply off when I boot my RPI, then turn on the power supply.... it all works.? If the power supply alone is on when the RPI boots, no sound.? Again, only since the last Bullseye updates, so I'm not sure what's causing this.? Glad to at least be on FT8 this morning, but don't like the new conditions.? Let me know if you guys think of something.

-73

Jason & gang,
I know I mentioned on Patreon that I’ve been resisting Bullseye, mainly because I couldn’t get headless screen resolution resolved. I’ve corrected that problem and it also is related to?
dtoverlay=vc4-kms-v3d
in the config.txt file.
This is the composite video overlay and seems to cause more problems than it’s worth. In fact, I’m wondering why the folks developing the OS even have it enabled by default (or have it at all — who uses composite?).?

I have to say that I don’t think Bullseye is ready for prime time. I don’t have the wherewithal to hop on the 64-bit BaP beta testing right now, but I’m finding other problems with Bullseye in general that make me want to stay on the rock-solid Buster on my production Pis

Sorry Raspberry Pi OS developers, you screwed the pooch with Bullseye.
Jay
73 de N0SR

Clean install of RaspberryPiOS Bullseye on Pi4-8GB
Add wpa_supplicant.conf to /boot
boot
latest updates
run command
ip a
see wifi is present as wlan0
add
dtoverlay=disable-wifi
to /boot/config.txt
reboot
run command
ip a
wifi is now gone
insert USB WiFi dongle
confirm it is recognized with command
lsusb
run command
ip a
USB Wifi should show as wlan0

--

Just curious, have you successfully ran build-a-pi 100% over VNC?

Glad you got it figured out. I always setup, build, and run my Pi's headless with the exception of one particular machine. This is using the Pi's built in VNC server.

--

In Pat Menu, click on "quick stats" and post a screenshot please.
--

On Fri, Mar 4, 2022 at 10:11 AM, N5VMO Pat wrote:

Think I remember you saying it was in C++ language? .... Jason ???

BAP scrirpt(s) are written in bash.
?
--

Hi Kevin

I tried both variants, you mentioned.?

1 copying?dtoverlay=disable-wifi to config.txt -> no change internal wlan still is running
2 blacklist.conf -> internal wlan seems to be disabled, hotspot is running, no possibility to configure the external wlan adapter to connect to home network with hotspot tool or raspberry pi configuration

klaus

dc2jr

Any other suggestions are greatly appreciated?

I tried the change to make Firefox the default browser but I forgot to backup my image before I did it.

How would I go back to Chromium as the default browser?? Something like
xdg-settings set default-web-browser chromium.desktop
--
--Bill AA6BD

I have no sound coming into WSJT-X after updating to latest version of Bullseye.? Upon closer look, Pulse Audio does not show my sound card and I can not select the burr brown codecs in WSJT-X any longer.? Only since updating Bullseye.? Worked fine on Buster, and on initial install with Bullseye.? RPI still sees sound card, running "arecord -l", and FLRIG sets up and connects as before.? Hardware is an FT-991a using it's built in sound card on RPI4 w/4GB ram.? Thanks for your help!

Thanks Kevin, that seems to have done the trick! Man that seems like it was so much more difficult than it had to be. I guess I should just use the built-in VNC server.

Unless your tigervnc is enabling port 5900, yes, it is.
RealVNC is already installed by default and enabled in sudo raspi-config, Interface Options.

Kevin -- KD9EFV