Buster bug report thread

[Durarara]

Two things ..

When I enable Serial console, at 115200 (default) ...
... I get boot log messages at 57600 but login prompt at 115200 baud.
I have to set putty both ways to see one or the other correctly.

When I have dual monitors ... most boots halt at HDMI 0 black screen (but good HDMI signal) ...
... and HDMI1 with no HDMI signal.

With only one monitor plugged into HDMI0 ... every boot is ok.

[ OK ] Started Show Plymouth Boot Screen.
[ OK ] Started Forward Password Requests to Plymouth Directory Watch.
[ OK ] Reached target Local Encrypted Volumes.
[ OK ] Reached target Paths.
[ OK ] Found device /dev/ttyS0.
[ OK ] Found device /dev/serial1.
[ OK ] Found device /dev/disk/by-partuuid/16985271-01.
----------------------------------- with both plugged in stops here (below message never logs)
[ OK ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Starting File System Check on /dev/disk/by-partuuid/16985271-01...
Starting Load/Save RF Kill Switch Status...

[jonmacd]

WPA2 Enterprise Issues:

I have a Pi Zero W and a Pi3. I've connected both Pis (and plenty of other pis) successfully to the same WPA2-Enterprise network in the past using this tutorial:
https://www.raspberrypi.org/forums/view ... p?t=111100

I recently flashed a fresh copy of Buster to an SD card. Using the above wpa_supplicant tutorial I can no longer connect to the same enterprise network on both my Pi3 and Pi Zero W. Reflashing Stretch, and using the same wpa_supplicant.conf I was trying to use in Buster, both my Pi3 and Pi Zero W connect to the network no problem.

The very strange part is that if I plug in a USB WiFi adapter, the Pis (running Buster) which previously would not connect, are able to connect to the network just fine via the USB WiFi stick. This seems to rule out my original thought that the wpa_supplicant.conf structure has possibly changed for Buster. Again, the same wpa_supplicant.conf works fine in buster but ONLY with a USB WiFi stick. On board WiFi will not connect to WPA2-Enterprise networks.

I checked and the Pis running Buster will connect to standard (non enterprise) WPA2 networks using the on board WiFi. However I need to use them on a WPA2-Enterprise network.

This is after booting Buster on a pi using a known working wpa_supplicant.conf file:

Code: Select all

pi@raspberrypi:~$ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

pi@raspberrypi:~$ ifconfig wlan0
wlan0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet6 fe80::91bd:8bd6:abf7:bd83  prefixlen 64  scopeid 0x20<link>
        ether b8:27:eb:d2:b9:29  txqueuelen 1000  (Ethernet)
        RX packets 1856  bytes 414959 (405.2 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1865  bytes 254256 (248.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

pi@raspberrypi:~$ sudo wpa_supplicant -B -i interface -c /etc/wpa_supplicant/wpa_supplicant.conf
Successfully initialized wpa_supplicant
Could not read interface interface flags: No such device
nl80211: Driver does not support authentication/association or connect commands
nl80211: deinit ifname=interface disabled_11b_rates=0
Could not read interface interface flags: No such device
interface: Failed to initialize driver interface
pi@raspberrypi:~$ 

This is pretty much the extent of my troubleshooting abilities. Any tips on anything else to try would be appreciated.

[bls]

Not a big deal, but on my freshly-installed Buster Pi which is only wifi-connected, I'm seeing errors like the following:

Code: Select all

Jul 03 06:49:19 rpi31 systemd[1]: Starting Daily apt upgrade and clean activities...
Jul 03 06:49:50 rpi31 systemd-networkd-wait-online[972]: Event loop failed: Connection timed out
Jul 03 06:49:50 rpi31 apt-helper[969]: E: Sub-process /lib/systemd/systemd-networkd-wait-online returned an error code (1)
Jul 03 06:49:54 rpi31 systemd[1]: apt-daily-upgrade.service: Succeeded.
Jul 03 06:49:54 rpi31 systemd[1]: Started Daily apt upgrade and clean activities.
...
Jul 03 08:14:19 rpi31 systemd[1]: Starting Daily apt download activities...
Jul 03 08:14:50 rpi31 systemd-networkd-wait-online[1098]: Event loop failed: Connection timed out
Jul 03 08:14:50 rpi31 apt-helper[1096]: E: Sub-process /lib/systemd/systemd-networkd-wait-online returned an error code (1)
Jul 03 08:14:52 rpi31 systemd[1]: apt-daily.service: Succeeded.
Jul 03 08:14:52 rpi31 systemd[1]: Started Daily apt download activities.

It would appear that systemd-networkd-wait-online waits for eth0 to come online. I know that I can modify /lib/systemd/systemd/systemd/neworkd-wait-online.service to have it ignore eth0, but shouldn't this be parameterized via something in /etc/default?

[startrek.steve]

Ok got my shiny (Hot) Raspberry Pi 4 yesterday,. installed Buster, did all the updates, added a bottom panel to the desktop, rebooted and the top panel has vanished along with all menus! If I delete config with sudo rm -r ~/.config/lxpanel and reboot, the top panel comes back ok, but as soon as I add a bottom panel, the top one vanishes after a reboot. Is therfe a fix for this bug?

Steve

[paiku]

Currently unable to minimize, maximize, close, move, resize or change focus with windows in LXDE via the titlebar. I can use the right-click menu to click on lxpanel's Window List, then it brings up the text versions of close, raise, restore, maximize and iconify, but I haven't found any workarounds for resizing or moving the windows.

It was like this on Stretch as well before I flashed the microSD with Buster. IIRC, these problems may have started happening after I changed my Widget theme in lxappearance to arc-theme.

Overall, it appears to be a problem with the mouse not getting proper focus on the titlebar somehow. Even if I change the Widget theme to Adwaita, the problems persist.

[PeterO]

xcompmgr seems to be contributing to poor openGL and openGLES performance. See this thread.
https://www.raspberrypi.org/forums/view ... 2#p1491828

Since it's raison d'être is "It enables basic eye-candy effects." can it be disabled by default please ?

PeterO

[paiku]

xcompmgr seems to be contributing to poor openGL and openGLES performance. See this thread.
https://www.raspberrypi.org/forums/view ... 2#p1491828

[...] can it be disabled by default please ?

If that is so, it may depend on use case. I prefer less screen tearing and frame loss. Running only one or two programs in X without pretty animations or transparencies is fine by me.

I'll disable it and see if it fixes the problem, thanks for the idea.

[Ernst]

Splash screen time very short and no messages shown with Pi 4B

On a Pi 4B the splash screen is erased almost immediately and it is impossible to read anything on it.
There are no further messages shown on the bottom of the screen.
It looks as if the complete screen is blacked out until the desktop is loaded.

On a Pi 3B the splash screen does not get erased and messages are shown on the bottom of the screen.

After removing the following lines from config.txt the splash screen is shown as expected:

Code: Select all

dtoverlay=vc4-fkms-v3d
max_framebuffers=2

[jeancc]

Hi everybody!

Has anybody notice that eth0 , a lot of times cannot get IP from the DHCP server? A couple of times it can, but the major the assigned IP is 169.254.118.199

I've tried set down / up the interface, call dhclient -4 ... nothing works.

Rebooting the system a couple of times and sometimes eth0 is properly setted with an IP of my network range. Service dhcpcd is enabled, I've no changed nothing of the default configuration files.


EDIT: I can get IP address executing mii-tool to restart eth0 intreface, but I don't understand why eth0 can not obtain IP address on system startup.

[hippy]

Has anybody notice that eth0 , a lot of times cannot get IP from the DHCP server?

I can't say I have noticed that. Every re-boot I have done with Buster has always got a DHCP assigned 192.168.0.x address.

And I have done a lot of re-booting lately though admittedly mostly the same Pi.

[davidrnewman]

I downloaded the Rasbian Buster image for a Pi 4, installed it to a card and successfully booted the Pi 4 inside a pi-top laptop. The touchpad and keyboard worked fine.

When I updated and upgraded the Raspbian software, on reboot, the touchpad no longer works. It can move left or right but not up or down. It is stuck on the panel.

Which particular update is breaking the touchpad integration in the desktop?

[nachoparker]

`php-smbclient` pulls in PHP7.2 dependencies, even though Buster defaults to PHP7.3. Or regular Debian, `php-smbclient` does not pull in PHP7.2, but depends on PHP7.3.

Code: Select all

root@raspberrypi:/# apt-get install php-smbclient
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following additional packages will be installed:
  libavahi-client3 libcups2 libjansson4 libldb1 libpython2.7 libsmbclient libsodium23 libtdb1 libtevent0 php-common php7.2-cli php7.2-common php7.2-json
  php7.2-opcache php7.2-phpdbg php7.2-readline python-talloc samba-libs
Suggested packages:
  cups-common php-pear
The following NEW packages will be installed:
  libavahi-client3 libcups2 libjansson4 libldb1 libpython2.7 libsmbclient libsodium23 libtdb1 libtevent0 php-common php-smbclient php7.2-cli php7.2-common
  php7.2-json php7.2-opcache php7.2-phpdbg php7.2-readline python-talloc samba-libs
0 upgraded, 19 newly installed, 0 to remove and 0 not upgraded.
Need to get 9461 kB of archives.
After this operation, 39.8 MB of additional disk space will be used.
Do you want to continue? [Y/n]

[plugwash]

`php-smbclient` pulls in PHP7.2 dependencies, even though Buster defaults to PHP7.3. Or regular Debian, `php-smbclient` does not pull in PHP7.2, but depends on PHP7.3.

Looking at this.

[Shadi1989]

I am trying to get this Aeotec Z-Stick Gen5, Z-Wave Plus USB to work on Buster:

https://www.amazon.co.uk/Aeotec-Z-Stick ... th=1&psc=1

I don't see this device appear when i connect it:

/dev/ttyACM0

It talks to the device via a serial connection and i then use it via Home Assistant. Has something changed for USB drivers?

I'm going to cross post this over on the HA forum for awareness.
https://community.home-assistant.io/t/t ... rk.carline

I opened this guthub bug report:
https://github.com/raspberrypi/linux/issues/3027

Thanks!

Having exactly the same issue.
Aeonlabs Gen5 Z-wave usb stick works at Pi 2 and P3. Does not with Rasbian Buster on Pi 4 4GB.

[lramalho]

Thanks for all your efforts for the new hardware and OS - greatly appreciated!

I just flashed Buster Lite on a fresh SD card and put it into my Pi Zero W. It does boot fine, reports to resize the Boot Partition and boots again. The boot process is also working the second time, but it’s the automatically started update process that’s worrying me a bit: it has been running for multiple hours now, with no more information than something along the lines of “Checking and downloading updates” (seems I can issue commands while the setup is still running, and I made the mistake of running dmesg, so I no longer see the original message). It never reported to have completed. This is the second run of going through the setup process, I rebooted the first one impatiently, and the result was a system with garbled keyboard layout names, so I reflashed.

Is the setup process of a fresh install supposed to take that long? Does it report when it’s finished? Is there any way to see what exactly it’s doing behind the scenes (and get a more fine grained progress report)?

I eventually rebooted after some 4 hours, and the result is again that keyboard layout selection is completely garbled (some layout names are displayed in French, some in Dutch, some as black squares, really strange):





Here are the steps that allow me to reproduce the issue:

1) Download the Buster Lite Image from the official website (The checksum does match for my download)
2) Use Etcher on macOS to flash the image (I let Etcher extract the zip for me)
3) Remove and reinsert the card in the MacBook SD slot to mount the boot partition in macOS
4) Duplicate the LICENSE.broadcom file, then rename the duplicate to “ssh” and delete its contents
5) Eject the card and insert into the Pi Zero W (Pi has Internet connection via USB hub + Ethernet dongle)
6) Power up the Pi
7) The Pi will get stuck at “[OK] Started Daily apt upgrade and clean activities.”
At this point, it is possible to use a USB keyboard (attached to aforementioned hub) to log in and issue commands. This allowed me to verify that the Pi has Internet Access (Ping Google.com) and (after having waited for ~4 hours), to reboot via sudo reboot
8) Steps Continue below screenshot


That’s as far as it boots up. No input was entered to this point.


8) Reboot
9) Log in using default credentials (via the Pi itself, ssh is not actually used)
10) Start raspi-config
11) Choose Localisation Options > Change Keyboard Layout
12) Layout names are partly in French, partly in Spanish (or is it Italian?), partly black squares; It’s impossible to find the correct configuration without proper labels. See image above.

Just to let you know that I'm actually happy to find this post since I was looking for a place to post about this very same issues I had while installing Buster, and with screen pictures of my own.

The problem extends to raspi-config as well. I was about to ask what kind of eyeglasses should I bought that allows me to translate such nonsense. I wonder if there was someone with, at least with minimum care to inspect for visual problems in buster install and configuration apps. Clearly no one has cared about this..

Anyway, I'm here to confirm this problem.

[DougieLawson]

There's a bug in piclone. It fails to mount the target ext4 partition.

Raspberry Pi1 is booted from a SDCard with the rootfs on that same 8GB sdcard. Target is another 8GB SDCard in a USB reader.

dmesg

Code: Select all

[68948.088433]  sda:
[68951.087475]  sda:
[68953.103311]  sda: sda1
[68956.435010]  sda: sda1
[68962.641073]  sda: sda1
[68975.681865]  sda: sda1
[68975.879601]  sda: sda1
[68975.967227]  sda: sda1
[68984.159740]  sda: sda1 sda2
[68986.721122]  sda: sda1 sda2
[68994.875205]  sda: sda1 sda2
[69083.854402]  sda:
[69088.170271]  sda:
[69090.950554]  sda: sda1
[69093.942812]  sda: sda1
[69099.416598]  sda: sda1
[69112.339203]  sda: sda1
[69112.418902]  sda: sda1
[69112.529015]  sda: sda1
[69120.954523]  sda: sda1 sda2
[69124.335282]  sda: sda1 sda2
[69133.827331]  sda: sda1 sda2
[69142.017127]  sda: sda1 sda2
[69142.219821]  sda: sda1 sda2
[69142.293088]  sda: sda1 sda2
[69144.542514]  sda: sda1 sda2
[69159.685263]  sda: sda1 sda2
[69205.802032]  sda: sda1 sda2
[69215.460343]  sda: sda1 sda2
[69223.711878] F2FS-fs (sda2): Magic Mismatch, valid(0xf2f52010) - read(0x66695a54)
[69223.711904] F2FS-fs (sda2): Can't find valid F2FS filesystem in 1th superblock
[69223.722518] F2FS-fs (sda2): Magic Mismatch, valid(0xf2f52010) - read(0x0)
[69223.722548] F2FS-fs (sda2): Can't find valid F2FS filesystem in 2th superblock
[69223.723767] F2FS-fs (sda2): Magic Mismatch, valid(0xf2f52010) - read(0x66695a54)
[69223.723793] F2FS-fs (sda2): Can't find valid F2FS filesystem in 1th superblock
[69223.723813] F2FS-fs (sda2): Magic Mismatch, valid(0xf2f52010) - read(0x0)
[69223.723823] F2FS-fs (sda2): Can't find valid F2FS filesystem in 2th superblock
[69262.905311]  sda: sda1 sda2
[69282.682374]  sda:
[69282.797421]  sda:
[69288.429939]  sda:
[69306.522341]  sda: sda1
[69404.236448]  sda:
[69407.695480]  sda:
[69409.945398]  sda: sda1
[69411.161657]  sda: sda1
[69413.170043]  sda: sda1
[69417.282511]  sda: sda1
[69426.996638]  sda: sda1
[69427.116032]  sda: sda1
[69427.200099]  sda: sda1
[69435.388106]  sda: sda1 sda2
[69440.996482]  sda: sda1 sda2
[69447.244114]  sda: sda1 sda2
[69455.383439]  sda: sda1 sda2
[69455.506322]  sda: sda1 sda2
[69455.601124]  sda: sda1 sda2
[69457.688921]  sda: sda1 sda2
[69472.078228]  sda: sda1 sda2
[69514.874671]  sda: sda1 sda2
[69523.651822]  sda: sda1 sda2
[69531.287051] F2FS-fs (sda2): Magic Mismatch, valid(0xf2f52010) - read(0x66695a54)
[69531.287079] F2FS-fs (sda2): Can't find valid F2FS filesystem in 1th superblock
[69531.288650] F2FS-fs (sda2): Magic Mismatch, valid(0xf2f52010) - read(0x0)
[69531.288673] F2FS-fs (sda2): Can't find valid F2FS filesystem in 2th superblock
[69531.288798] F2FS-fs (sda2): Magic Mismatch, valid(0xf2f52010) - read(0x66695a54)
[69531.288812] F2FS-fs (sda2): Can't find valid F2FS filesystem in 1th superblock
[69531.288828] F2FS-fs (sda2): Magic Mismatch, valid(0xf2f52010) - read(0x0)
[69531.288837] F2FS-fs (sda2): Can't find valid F2FS filesystem in 2th superblock
[69944.170014] usb 1-1.3: USB disconnect, device number 4
[69948.569858] usb 1-1.2: new high-speed USB device number 5 using dwc_otg
[69948.705574] usb 1-1.2: New USB device found, idVendor=05e3, idProduct=0727, bcdDevice= 2.50
[69948.705603] usb 1-1.2: New USB device strings: Mfr=3, Product=4, SerialNumber=2
[69948.705616] usb 1-1.2: Product: USB Storage
[69948.705630] usb 1-1.2: Manufacturer: Generic
[69948.705641] usb 1-1.2: SerialNumber: 000000000250
[69948.713811] usb-storage 1-1.2:1.0: USB Mass Storage device detected
[69948.735137] scsi host0: usb-storage 1-1.2:1.0
[69949.781954] scsi 0:0:0:0: Direct-Access     Generic  STORAGE DEVICE   0250 PQ: 0 ANSI: 0
[69949.787410] sd 0:0:0:0: Attached scsi generic sg0 type 0
[69949.900935] sd 0:0:0:0: [sda] 15353856 512-byte logical blocks: (7.86 GB/7.32 GiB)
[69949.902805] sd 0:0:0:0: [sda] Write Protect is off
[69949.902832] sd 0:0:0:0: [sda] Mode Sense: 0b 00 00 08
[69949.904286] sd 0:0:0:0: [sda] No Caching mode page found
[69949.904312] sd 0:0:0:0: [sda] Assuming drive cache: write through
[69949.919117]  sda: sda1 sda2
[69949.934597] sd 0:0:0:0: [sda] Attached SCSI removable disk
[70074.647683]  sda:
[70077.994533]  sda:
[70080.240750]  sda: sda1
[70083.908219]  sda: sda1
[70091.655685]  sda: sda1
[70104.422587]  sda: sda1
[70104.579763]  sda: sda1
[70104.664981]  sda: sda1
[70114.381594]  sda: sda1 sda2
[70125.544325]  sda: sda1 sda2
[70135.102848]  sda: sda1 sda2
[70135.174030]  sda: sda1 sda2
[70135.234646]  sda: sda1 sda2
[70150.523458]  sda: sda1 sda2
[70199.843670]  sda: sda1 sda2
[70209.969310]  sda: sda1 sda2
[70219.728868] F2FS-fs (sda2): Magic Mismatch, valid(0xf2f52010) - read(0x66695a54)
[70219.728895] F2FS-fs (sda2): Can't find valid F2FS filesystem in 1th superblock
[70219.754083] F2FS-fs (sda2): Magic Mismatch, valid(0xf2f52010) - read(0x0)
[70219.754111] F2FS-fs (sda2): Can't find valid F2FS filesystem in 2th superblock
[70219.754242] F2FS-fs (sda2): Magic Mismatch, valid(0xf2f52010) - read(0x66695a54)
[70219.754256] F2FS-fs (sda2): Can't find valid F2FS filesystem in 1th superblock
[70219.754271] F2FS-fs (sda2): Magic Mismatch, valid(0xf2f52010) - read(0x0)
[70219.754281] F2FS-fs (sda2): Can't find valid F2FS filesystem in 2th superblock

There's also a GUI window that says

Code: Select all

terminate_dialog (_("Could not mount partition."));

[Sidebuster]

Fresh install with any version of Raspian buster release with a pi2.

On first boot and from then on, dhcpcd fails. When I try to manually launch it with dhcpcd, it says there was a buffer overflow issue and quits out. This seems to happen right after (or as) it gets to trying to get an address for ip6.

To work around this, I manually entered an ip with:

Code: Select all

ip address add 192.168.x.x/24 dev eth0 && dhcpcd -4 

and it worked. But upon reboot, it'd be back to not working. For some reason just running dhcpcd -4 wouldn't get it working, I had to manually add the address first.

[travellingkiwi]

fatrace

Doesn't appear to work. Installing and attempting to use via

Code: Select all

fatrace -f W

to trace file writes, just results in

Code: Select all

root@piman-401:/home/hamish# fatrace -f W
Cannot initialize fanotify: Invalid argument
root@piman-401:/home/hamish#

[thatchunkylad198966]

First post on this thread..

Not sure if this is a bug (?) or not.

Say I disable swap or install something, anything; like say "gimp" for an example.
I type in my terminal "sudo reboot" and I think it reboots, my keyboard lights up and mouse (after the sudo reboot) I don't get nothing from SSH and my router doesn't give my Pi 4 an IP address. I can hear my USB3 HDD spin up, though.

So confusing.

[linux_author]

alas, while gqrx and Buster readily supports the RTL-SDR on my RPi3Bs (works great!), it looks like SDR radio is a no-go on my RPi4 2GB...

the device is readily recognized:

Code: Select all

[  194.847842] dvbdev: DVB: registering new adapter (Realtek RTL2832U reference design)
[  194.870344] i2c i2c-3: Added multiplexed i2c bus 4
[  194.870360] rtl2832 3-0010: Realtek RTL2832 successfully attached
[  194.870460] usb 1-1.3: DVB: registering adapter 0 frontend 0 (Realtek RTL2832 (DVB-T))...
[  194.895629] r820t 4-001a: creating new instance
[  194.902491] r820t 4-001a: Rafael Micro r820t successfully identified
[  194.925045] Registered IR keymap rc-empty
[  194.925167] rc rc0: Realtek RTL2832U reference design as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/rc/rc0
[  194.925382] input: Realtek RTL2832U reference design as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/rc/rc0/input1
[  194.925745] rc rc0: lirc_dev: driver dvb_usb_rtl28xxu registered at minor = 0, raw IR receiver, no transmitter
[  194.925890] usb 1-1.3: dvb_usb_v2: schedule remote query interval to 200 msecs
[  194.939633] usb 1-1.3: dvb_usb_v2: 'Realtek RTL2832U reference design' successfully initialized and connected
[  194.939878] usbcore: registered new interface driver dvb_usb_rtl28xxu

however, when attempting to use the dongle:

Code: Select all

[  194.925167] rc rc0: Realtek RTL2832U reference design as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/rc/rc0
[  194.925382] input: Realtek RTL2832U reference design as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/rc/rc0/input1
[  194.925745] rc rc0: lirc_dev: driver dvb_usb_rtl28xxu registered at minor = 0, raw IR receiver, no transmitter
[  194.925890] usb 1-1.3: dvb_usb_v2: schedule remote query interval to 200 msecs
[  194.939633] usb 1-1.3: dvb_usb_v2: 'Realtek RTL2832U reference design' successfully initialized and connected
[  194.939878] usbcore: registered new interface driver dvb_usb_rtl28xxu
[  295.679295] r820t 4-001a: destroying instance
[  295.679705] dvb_usb_v2: 'Realtek RTL2832U reference design:1-1.3' successfully deinitialized and disconnected
[  307.758828] dvb_usb_rtl28xxu 1-1.3:1.0: chip type detection failed -110
[  307.758865] dvb_usb_rtl28xxu: probe of 1-1.3:1.0 failed with error -110
[  313.939080] usb 1-1.3: reset high-speed USB device number 3 using xhci_hcd
[  319.069235] usb 1-1.3: device descriptor read/64, error -110

this does not happen on the RPi3B...

so, kernel problem? hardware problem? i wonder why everything works fine on the RPi3B but not the RPi4? same distro, same software on both???

any tips appreciated...

here's my write up on using my RPi3B+LCD+RTL-SDR for a panadapter displaying output from the 1st IF out of a Xiegu X5105, along with using gqrx for radio listening:

https://kg4zqz.blogspot.com/2019/07/ras ... r-for.html

it would be great to use the new RPi4 too

tia,

willie
on the Gulf of Mexico

[drmullins]

New installation of buster on RPi 4 B 4GB
After issuing :
sudo gparted /dev/sda
with intention of reformatting a partition of /dev/sda,
the following is displayed in terminal window :
Unit tmp.mount does not exist, proceeding anyway
followed by standard libparted : 3.2 message

Next I unmount /dev/sda1 successfully using gparted GUI

However then trying to format /dev/sda1 as ext4 via gparted GUI fails with attached error message :

Help !

All this works fine in stretch and jessie


<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML 1.0 Transitional//EN' 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd'>
<html xmlns='http://www.w3.org/1999/xhtml' xml:lang='en-GB' lang='en-GB'>
<head>
<meta http-equiv='Content-Type' content='text/html;charset=utf-8' />
<title>GParted Details</title>
</head>
<body>
<p>GParted 0.32.0 --enable-libparted-dmraid --enable-online-resize</p>
<p>Libparted 3.2</p>
<table border='0'>
<tr>
<td colspan='2'>
<b>Format /dev/sda1 as ext4</b>&nbsp;&nbsp;00:00:11&nbsp;&nbsp;&nbsp;&nbsp;( ERROR )
</td>
</tr>
<tr>
<td>&nbsp;&nbsp;&nbsp;&nbsp;</td>
<td>
<table border='0'>
<tr>
<td colspan='2'>
calibrate /dev/sda1&nbsp;&nbsp;00:00:01&nbsp;&nbsp;&nbsp;&nbsp;( SUCCESS )
</td>
</tr>
<tr>
<td>&nbsp;&nbsp;&nbsp;&nbsp;</td>
<td>
<table border='0'>
<tr>
<td colspan='2'>
<i>path: /dev/sda1 (partition)<br />start: 2048<br />end: 1953522863<br />size: 1953520816 (931.51 GiB)</i>
</td>
</tr>
</table>
</td>
</tr>
</table>
<table border='0'>
<tr>
<td colspan='2'>
clear old file system signatures in /dev/sda1&nbsp;&nbsp;00:00:00&nbsp;&nbsp;&nbsp;&nbsp;( SUCCESS )
</td>
</tr>
<tr>
<td>&nbsp;&nbsp;&nbsp;&nbsp;</td>
<td>
<table border='0'>
<tr>
<td colspan='2'>
write 512.00 KiB of zeros at byte offset 0&nbsp;&nbsp;00:00:00&nbsp;&nbsp;&nbsp;&nbsp;( SUCCESS )
</td>
</tr>
</table>
<table border='0'>
<tr>
<td colspan='2'>
write 4.00 KiB of zeros at byte offset 67108864&nbsp;&nbsp;00:00:00&nbsp;&nbsp;&nbsp;&nbsp;( SUCCESS )
</td>
</tr>
</table>
<table border='0'>
<tr>
<td colspan='2'>
write 4.00 KiB of zeros at byte offset 274877906944&nbsp;&nbsp;00:00:00&nbsp;&nbsp;&nbsp;&nbsp;( SUCCESS )
</td>
</tr>
</table>
<table border='0'>
<tr>
<td colspan='2'>
write 512.00 KiB of zeros at byte offset 1000202043392&nbsp;&nbsp;00:00:00&nbsp;&nbsp;&nbsp;&nbsp;( SUCCESS )
</td>
</tr>
</table>
<table border='0'>
<tr>
<td colspan='2'>
write 4.00 KiB of zeros at byte offset 1000202567680&nbsp;&nbsp;00:00:00&nbsp;&nbsp;&nbsp;&nbsp;( SUCCESS )
</td>
</tr>
</table>
<table border='0'>
<tr>
<td colspan='2'>
write 8.00 KiB of zeros at byte offset 1000202649600&nbsp;&nbsp;00:00:00&nbsp;&nbsp;&nbsp;&nbsp;( SUCCESS )
</td>
</tr>
</table>
<table border='0'>
<tr>
<td colspan='2'>
flush operating system cache of /dev/sda&nbsp;&nbsp;00:00:00&nbsp;&nbsp;&nbsp;&nbsp;( SUCCESS )
</td>
</tr>
</table>
</td>
</tr>
</table>
<table border='0'>
<tr>
<td colspan='2'>
set partition type on /dev/sda1&nbsp;&nbsp;00:00:10&nbsp;&nbsp;&nbsp;&nbsp;( SUCCESS )
</td>
</tr>
<tr>
<td>&nbsp;&nbsp;&nbsp;&nbsp;</td>
<td>
<table border='0'>
<tr>
<td colspan='2'>
<i>new partition type: ext4</i>
</td>
</tr>
</table>
</td>
</tr>
</table>
<table border='0'>
<tr>
<td colspan='2'>
create new ext4 file system&nbsp;&nbsp;00:00:00&nbsp;&nbsp;&nbsp;&nbsp;( ERROR )
</td>
</tr>
<tr>
<td>&nbsp;&nbsp;&nbsp;&nbsp;</td>
<td>
<table border='0'>
<tr>
<td colspan='2'>
<b><i>mkfs.ext4 -F -O ^64bit -L &apos;&apos; &apos;/dev/sda1&apos;</i></b>&nbsp;&nbsp;00:00:00&nbsp;&nbsp;&nbsp;&nbsp;( ERROR )
</td>
</tr>
<tr>
<td>&nbsp;&nbsp;&nbsp;&nbsp;</td>
<td>
<table border='0'>
<tr>
<td colspan='2'>
<i></i>
</td>
</tr>
</table>
<table border='0'>
<tr>
<td colspan='2'>
<i>mke2fs 1.44.5 (15-Dec-2018)<br />The file /dev/sda1 does not exist and no size was specified.<br /></i>
</td>
</tr>
</table>
</td>
</tr>
</table>
</td>
</tr>
</table>
</td>
</tr>
</table>
<p>========================================</p>
</body>
</html>

[DougieLawson]

dpkg-reconfigure keyboard-layout is a little bit broken.
1. It's speaking French (all those years of watching Le Tour de France are useful)
2. It's got lots of unprintable characters in the list of keyboard locations (not good)
3. It's got lots of unprintable characters in the list of keyboard types (too risky - I don't want to get Dvorak by accident)

I was trying to set a PC 105 with Windows keyboard with an American layout (for my trusty wireless keyboard/mouse).

Even tried running it with LOCALE=en_GB.UTF-8 dpkg-reconfigure keyboard-layout but nothing changed.

[DougieLawson]

New installation of buster on RPi 4 B 4GB
After issuing :
sudo gparted /dev/sda
with intention of reformatting a partition of /dev/sda,
the following is displayed in terminal window :
Unit tmp.mount does not exist, proceeding anyway
followed by standard libparted : 3.2 message

Next I unmount /dev/sda1 successfully using gparted GUI

However then trying to format /dev/sda1 as ext4 via gparted GUI fails with attached error message :

Help !

All this works fine in stretch and jessie

Code: Select all

GParted 0.32.0 --enable-libparted-dmraid --enable-online-resize

Libparted 3.2

Format /dev/sda1 as ext4  00:00:11    ( ERROR )
    	
calibrate /dev/sda1  00:00:01    ( SUCCESS )
    	
path: /dev/sda1 (partition)
start: 2048
end: 1953522863
size: 1953520816 (931.51 GiB)
clear old file system signatures in /dev/sda1  00:00:00    ( SUCCESS )
    	
write 512.00 KiB of zeros at byte offset 0  00:00:00    ( SUCCESS )
write 4.00 KiB of zeros at byte offset 67108864  00:00:00    ( SUCCESS )
write 4.00 KiB of zeros at byte offset 274877906944  00:00:00    ( SUCCESS )
write 512.00 KiB of zeros at byte offset 1000202043392  00:00:00    ( SUCCESS )
write 4.00 KiB of zeros at byte offset 1000202567680  00:00:00    ( SUCCESS )
write 8.00 KiB of zeros at byte offset 1000202649600  00:00:00    ( SUCCESS )
flush operating system cache of /dev/sda  00:00:00    ( SUCCESS )
set partition type on /dev/sda1  00:00:10    ( SUCCESS )
    	
new partition type: ext4
create new ext4 file system  00:00:00    ( ERROR )
    	
mkfs.ext4 -F -O ^64bit -L '' '/dev/sda1'  00:00:00    ( ERROR )
    	
mke2fs 1.44.5 (15-Dec-2018)
The file /dev/sda1 does not exist and no size was specified.
========================================

FTFY, you're welcome

[JohnSoCalUSA]

Pi 3B+, Raspbian Buster Full 2019-06-20

Network config fails because dhcpcd crashes due to an IPv6 buffer overflow
The top panel applet for the network settings shows XX and indicates lost connection to dhcpcd
My fix was to open a terminal and type 'sudo dhcpcd -4' to configure IPv4 only
I was then able to access network settings from the panel applet and choose "Disable IPv6" for all interfaces

[PeterO]

I just plugged in one of the old "official pi logo" usb hubs. It has it's own power connected, and the tool bar disappeared because /dev/sda (where the root file system resides) disappeared ! /dev/sda is a segate HDD plubbed directly into one of the PI's USB3 ports.

PeterO