USB not working under arm64 on Pi4 with 4G ram

[Dave Jones]

Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10 armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the keyboard on either. Booting the arm64 image on a Raspberry Pi 3, the keyboard worked successfully.

Output of lsusb under arm64 on a Pi 3:

ubuntu@ubuntu:~$ lsusb
Bus 001 Device 007: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Output of lsusb under armhf on a Pi 4 (same keyboard attached):

ubuntu@ubuntu:~$ lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Output of lsusb under arm64 on the same Pi 4 (same keyboard attached):

ubuntu@ubuntu:~$ lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

The fact even the VIA Labs hub doesn't show up (which is built in) suggests the kernel is (for some reason) unable to enumerate anything against the USB hubs.

== Temporary Workaround ==

As noted by various people below, the following line can be added to the "usercfg.txt" file on the boot partition:

total_mem=3072

This will limit the available RAM to 3Gb, but otherwise things should operate normally. Note that this bug does not affect Pi 4Bs with less than 4Gb of RAM.

[Dave Jones (waveform)]

Additional detail from dmesg:

...

[ 1.390148] usbcore: registered new interface driver lan78xx
[ 1.391889] usbcore: registered new interface driver smsc95xx
[ 1.393568] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.395273] ehci-pci: EHCI PCI platform driver
[ 1.396956] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 1.398622] ohci-pci: OHCI PCI platform driver
[ 1.400281] uhci_hcd: USB Universal Host Controller Interface driver
[ 1.402251] xhci_hcd 0000:01:00.0: xHCI Host Controller
[ 1.403963] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 1
[ 1.406172] xhci_hcd 0000:01:00.0: hcc params 0x002841eb hci version 0x100 quirks 0x0000001000000890
[ 1.408067] genirq: irq_chip Brcm_MSI did not update eff. affinity mask of irq 43
[ 1.410313] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.03
[ 1.412064] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.413755] usb usb1: Product: xHCI Host Controller
[ 1.415461] usb usb1: Manufacturer: Linux 5.3.0-1007-raspi2 xhci-hcd
[ 1.417152] usb usb1: SerialNumber: 0000:01:00.0
[ 1.419377] hub 1-0:1.0: USB hub found
[ 1.421083] hub 1-0:1.0: 1 port detected
[ 1.423195] xhci_hcd 0000:01:00.0: xHCI Host Controller
[ 1.424869] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2
[ 1.426579] xhci_hcd 0000:01:00.0: Host supports USB 3.0 SuperSpeed
[ 1.428528] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.03
[ 1.430209] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.431906] usb usb2: Product: xHCI Host Controller
[ 1.433577] usb usb2: Manufacturer: Linux 5.3.0-1007-raspi2 xhci-hcd
[ 1.435268] usb usb2: SerialNumber: 0000:01:00.0
[ 1.437425] hub 2-0:1.0: USB hub found
[ 1.439157] hub 2-0:1.0: 4 ports detected
[ 1.441611] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[ 1.443556] dwc_otg fe980000.usb: base=(____ptrval____)
[ 1.647527] Core Release: 2.80a
[ 1.649145] Setting default values for core params
[ 1.650809] Finished setting default values for core params
[ 1.758372] usb 1-1: new high-speed USB device number 2 using xhci_hcd
[ 1.854949] Using Buffer DMA mode
[ 1.856573] Periodic Transfer Interrupt Enhancement - disabled
[ 1.858211] Multiprocessor Interrupt Enhancement - disabled
[ 1.859865] OTG VER PARAM: 0, OTG VER FLAG: 0
[ 1.861530] Dedicated Tx FIFOs mode
[ 1.864183] WARN::dwc_otg_hcd_init:1043: FIQ DMA bounce buffers: virt = ffff0000105d1000 dma = 0x00000000eb500000 len=9024
[ 1.865894] FIQ FSM acceleration enabled for :
               Non-periodic Split Transactions
               Periodic Split Transactions
               High-Speed Isochronous Endpoints
               Interrupt/Control Split Transaction hack enabled
[ 1.874175] dwc_otg: Microframe scheduler enabled
[ 1.874206] WARN::hcd_init_fiq:496: MPHI regs_base at ffff0000102c5200
[ 1.875964] dwc_otg fe980000.usb: DWC OTG Controller
[ 1.877651] dwc_otg fe980000.usb: new USB bus registered, assigned bus number 3
[ 1.879366] dwc_otg fe980000.usb: irq 2...

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Hui Wang (hui.wang)]

I reproduced this bug on my rpi4 board.

[Alexander Agnarson (alexander-agnarson)]

Reported and discussed here too: https://bugs.launchpad.net/ubuntu/+bug/1848703

[Ken Howe (leggazoid)]

User on lingon on raspberry pi forum posted the following:

The USB-problem concerning the Raspberry Pi 4GB RAM model might be due to the issue seen earlier that using more RAM than 3072 MB breaks the USB:
https://www.raspberrypi.org/forums/view ... 6&start=25

The issue was solved by a kernel patch:
https://www.raspberrypi.org/forums/view ... 0#p1517839

and the kernel patch was this one:
https://github.com/raspberrypi/linux/is ... -520269280

[Ken Howe (leggazoid)]

fixed links

User on lingon on raspberry pi forum posted the following:

The USB-problem concerning the Raspberry Pi 4GB RAM model might be due to the issue seen earlier that using more RAM than 3072 MB breaks the USB:
https://www.raspberrypi.org/forums/v...46766&start=25

The issue was solved by a kernel patch:
https://www.raspberrypi.org/forums/v...rt=50#p1517839

and the kernel patch was this one:
https://github.com/raspberrypi/linux...ment-520269280

[Ken Howe (leggazoid)]

fixed links

User on lingon on raspberry pi forum posted the following:

The USB-problem concerning the Raspberry Pi 4GB RAM model might be due to the issue seen earlier that using more RAM than 3072 MB breaks the USB:
[url]https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=246766&start=25[/url]

The issue was solved by a kernel patch:
[url]https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=246766&start=50#p1517839[/url]

and the kernel patch was this one:
[url]https://github.com/raspberrypi/linux/issues/3093#issuecomment-520269280[/url]

[Ken Howe (leggazoid)]

Fixed links

User on lingon on raspberry pi forum posted the following:

The USB-problem concerning the Raspberry Pi 4GB RAM model might be due to the issue seen earlier that using more RAM than 3072 MB breaks the USB:
[url]https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=246766&start=25[/url]

The issue was solved by a kernel patch:
[url]https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=246766&start=50#p1517839[/url]

and the kernel patch was this one:
[url]https://github.com/raspberrypi/linux/issues/3093#issuecomment-520269280[/url]

[Adam T (tiermann)]

Setting total_mem=2048 in /boot/firmware/usercfg.txt allowed me to boot Pi4 4GB with 19.10 64bit with working USB. Of course I have less RAM now, but working USB.

Likely the above patch will fix it.

[Hui Wang (hui.wang)]

Thanks everyone.

I didn't notice this problem just because I set total_mem=1024/2048/3072 before, this is problem was not exposed because the full 4G ram was not enabled.

And I will test the patches of #8 and SRU them if they works well.

thx.

[Hui Wang (hui.wang)]

I built a testing kernel, not only includes the fix for USB host, but also includes all new patches from https://github.com/raspberrypi/linux.git rpi-5.3.y branch (about 107 patches).

I tested both arm64 and armhf kernels on Pi4 without HDMI monitor, everything works well.

Could anybody help test these two kernels on Pi4 with HDMI monitor, Pi3 and Pi2 if you have any of them?

After verifying the kernel will not introduce regression on Pi4/3/2, I will submit the patches to UBUNTU kernel.

The new kernel could be downloaded: https://people.canonical.com/~hwang4/rpiv2/

To install and test the kernel:
copy arm64 or armhf folders to rootfs of Pi, sudo dpkg -i linux-modules-xxxx.deb; sudo dpkg -i linux-image-xxx.deb;sudo reboot

thx

[Garyschulte (garyschulte)]

Also can confirm that the arm64 image works on raspberry pi 4/4gb, 1080p HDMI. Still no sound device for bcm2835, but USB is happy, I am happy. Thanks for the quick turnaround

[Garyschulte (garyschulte)]

Same sdhc with arm64 image and modules work for raspberry pi 3b+/1gb, 1080p HDMI also.

[Hui Wang (hui.wang)]

Thanks for your testing.

And I remember we need to enable some configs to make the audio work. If you have time, please have a try with below:

Adding these configs to config.txt

# Enable audio (loads snd_bcm2835)
dtparam=audio=on
disable_audio_dither=on

[Rohit Yadav (rohityadav)]

@hui.wang - thanks, seems to work but /dev/kvm is missing. Can you advise why the kernels are not built by default with KVM/VIRTUALIZATION enabled in the kernel config? If this going to change in future.

[Hui Wang (hui.wang)]

@Rohit,

I will take a look at the issue of kvm, and do you know if the 18.04 support kvm on rpi3/2?

[Rohit Yadav (rohityadav)]

@hui.wang - I'm not sure on RPi3, but Ubuntu 18.04+KVM certainly works on RPi4. See someone already blogged about this here: https://jamesachambers.com/raspberry-pi-4-ubuntu-server-desktop-18-04-3-image-unofficial, I tried their image but it had issues due to older libvirt/qemu versions on 18.04.

[Hui Wang (hui.wang)]

@Rohit,

Got it, thx, and please refer to https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1849369/comments/1

[Rohit Yadav (rohityadav)]

@hui.wang - I tested the compiled kernel on my RaspberryPi4 (4GB RAM model). Both KVM and external SSD/USB (in my case Samsung T5, 500GB external SSD) on the USB 3.0 port are working fine:

root@cloudstack-mgmt:~# ls /dev/kvm
/dev/kvm
root@cloudstack-mgmt:~# kvm-ok
INFO: /dev/kvm exists
KVM acceleration can be used

root@cloudstack-mgmt:~# lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 04e8:61f5 Samsung Electronics Co., Ltd Portable SSD T5
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

# fdisk -l
[.. snipped ..]
Disk /dev/sda: 465.78 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Portable SSD T5
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 33553920 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device Boot Start End Sectors Size Id Type
/dev/sda1 2048 976773134 976771087 465.8G c W95 FAT32 (LBA)

root@cloudstack-mgmt:~# blkid -o list
device fs_type label mount point UUID
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------
/dev/mmcblk0p1 vfat system-boot /boot/firmware 79A2-EC62
/dev/mmcblk0p2 ext4 writable / 2fae1f20-4a20-4c77-a39b-fb6480f64a0b
/dev/loop0 squashfs /snap/lxd/12210
/dev/loop1 squashfs /snap/core/7920
/dev/sda1 ext4 (not mounted) 91175b3a-ee2c-47a7-a1e5-f4528e127523

This confirms that the patch and kernel-image build by @hui.wang fixes the external USB storage issue with the 4GB RPi4 model. Thanks @hui.wang.

[wanthalf (wanthalf)]

I also had to add the new revision "Raspberry Pi 4 Model B Rev 1.2" to /usr/share/flash-kernel/db/all.db in order to make flash-kernel work, but that is probably a different "bug".

[Hui Wang (hui.wang)]

And also Pi 3 Model A Plus is not in the all.db.

[Dave Jones (waveform)]

I've now tested the armhf and arm64 variants of Hui's test kernel from comment #11 on the Pi 2, 3, and 4 (several memory variants) and all seems good so far. Still need to finish testing on the compute modules, though.

As regards flash-kernel, the relevant tickets for the missing entries are LP: #1847587 for the 4B, and LP: #1841955 for the 3A+.

Unfortunately it turns out there's a rather more serious issue with flash-kernel, especially in relation to this bug: it only copies the dtb for the Pi it's being run on to the boot partition. As long as you never switch the SD card between models of Pi that's okay, but to give an example I ran across when testing the fixed kernel here: I upgraded the kernel on a Pi3, tested it, switched the card to a Pi4 and it failed to boot because the Pi4's dtb on the boot partition hadn't been updated (and the fixed kernel has a subtly different dtb). The bug tracking this is #1850678; I've got a fix in the works but it needs a bit of refinement first.

[Brad Figg (brad-figg)]

@all

There is a new kernel in -proposed that should fix these USB issues as well as the KVM support. There is still a known issue with audio as is explained in comment #14 above. Please test the -proposed kernel and let us know of any issues that you find.

[Hadrien Mary (hadim)]

Does someone know when the fix will be ported to the Ubuntu arm64 image?

[Hui Wang (hui.wang)]

Maybe after the proposed kernel is verified

To test -proposed kernel, with the old arm64 image:

edit /etc/apt/sources.list
and add below to that file:
deb http://ports.ubuntu.com/ubuntu-ports eoan-proposed main restricted
deb http://ports.ubuntu.com/ubuntu-ports eoan-proposed universe
deb http://ports.ubuntu.com/ubuntu-ports eoan-proposed multiverse

sudo apt-get update

sudo apt install linux-image-5.3.0-1011-raspi2
sudo reboot

Then the image will run the proposed kernel, and users could check it by 'uname -a', it will show 5.3.0-1011

[Paulo Matos (pmatos)]

To test this, is there an sd card image of ubuntu for pi4 I can flash?

[Hui Wang (hui.wang)]

@Paulo,

Please download (Raspberry Pi 3 (64-bit ARM) preinstalled server image) from http://cdimage.ubuntu.com/releases/eoan/release/

And please note if you use 4G version Pi4 board, the usb keyboard doesn't work with the default kernel in the image, to use the usb keyboard, please add total_mem=3072 in the config.txt, then install the proposed kernel, after that you could remove the total_mem=3072 from the config.txt.

thx.

[Tim Crisall (tcrisall)]

Not to clutter up this bug - but some quick feedback:

 - originally installed with mem_total as proposed earlier
 - updated to your first patched kernel as mentioned earlier and removed mem_total
 - updated a day ago to the -proposed version of the kernel

can confirm:

pi4 4G RAM, booting from SD Card, mounting root from USB attached drive, just successfully installed centos8 using KVM...

Thanks!

[Adam Mierzwiak (adamvm)]

Confirm that solution from #25 works and total_mem=3072 can be removed from config.

[Paulo Matos (pmatos)]

Same as https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/comments/28 https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/comments/29
It's working. Thanks.

[Ian Steiger (isteiger)]

updated my install, removed config.txt entry, available on stable

[Hui Wang (hui.wang)]

We are going to release a new kernel soon, right now it is in the proposed channel, Welcome to test with the new kernel:

edit the $rpi_rootfs/etc/apt/sources.list and add:
deb http://ports.ubuntu.com/ubuntu-ports eoan-proposed main restricted
deb http://ports.ubuntu.com/ubuntu-ports eoan-proposed universe
deb http://ports.ubuntu.com/ubuntu-ports eoan-proposed multiverse

boot the rpi board, then run:
sudo apt-get update
sudo apt install linux-image-5.3.0-1013-raspi2
sudo reboot

Then you could do the test with the proposed kernel.

At least the 1013 kernel fixed these bugs compared with 1012 kernel:
https://bugs.launchpad.net/bugs/1850876
https://bugs.launchpad.net/bugs/1852510

[Removed by request (removed7543109)]

Hello, using apt update && apt upgrade the USB already starts working. I see that the last released image for Raspberry Pi 3/4 was on the 12th of November. When can we see a new image released with the fix?

[Removed by request (removed7543109)]

(P.S.: I was looking at the images at http://cdimage.ubuntu.com/ubuntu-server/eoan/daily-preinstalled/ )

[Akshay (akshaynakra)]

Hui Wang - I tried your proposed solution. Post rebooting the system freezes at login after I type in my password.

[Hui Wang (hui.wang)]

@Unleavened,

This is the image with the new kernel. http://cdimage.ubuntu.com/ubuntu-server/eoan/daily-preinstalled/20191122/

[Hui Wang (hui.wang)]

@Akshay,

Does it 100% happen? Did you login through keyboard/ssh connection/usb-serial console? Last could you please try the Image of #36.

thx.

[Hui Wang (hui.wang)]

Please ignore the #36, the boot.scr in the http://cdimage.ubuntu.com/ubuntu-server/eoan/daily-preinstalled/20191122/ has some problem.

[Jussi Saarinen (jms)]

I tried kernel linux-image-5.3.0-1013-raspi2 on Pi4. I'm running mate-desktop-environment using autologin and with this kernel X-server started but only showing black screen with mouse cursor, I could log in with ssh. I rolled back to linux-image-5.3.0-1012-raspi2 for now.

[Hui Wang (hui.wang)]

@Jussi,

I found that issue too. the driver v3d.ko crashed. In the 1013, we enabled v3d.ko, while before the 1013, the v3d.ko is disabled.

You could change dtoverlay=vc4-fkms-v3d to #dtoverlay=vc4-fkms-v3d in the config.txt, then boot with 1013 kernel, system will use fbdev as before.

[Jussi Saarinen (jms)]

That line was already commented out (#dtoverlay=vc4-fkms-v3d) in config.txt
so I blacklisted module v3d, works now better with 1013 kernel. Thanks.

On Sat, Nov 23, 2019 at 2:05 PM Hui Wang <email address hidden> wrote:

> @Jussi,
>
> I found that issue too. the driver v3d.ko crashed. In the 1013, we
> enabled v3d.ko, while before the 1013, the v3d.ko is disabled.
>
> You could change dtoverlay=vc4-fkms-v3d to #dtoverlay=vc4-fkms-v3d in
> the config.txt, then boot with 1013 kernel, system will use fbdev as
> before.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1848790
>
> Title:
> USB not working under arm64 on Pi4 with 4G ram
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+subscriptions
>

--
-jussi

[Akshay (akshaynakra)]

Hui Wang -
Does it 100% happen? --> I'm not sure what you meant by this, it happened on repeated attempts, till the point I just formatted my SD card.

Did you login through keyboard/ssh connection/usb-serial console? --> I logged in using a keyboard.

Last could you please try the Image of #36. --> Your next comments asks us not to try this, so is there a fresh install I can try that fixes this ?

[Hui Wang (hui.wang)]

@Askshay,

This is the new image you could have a try with. http://cdimage.ubuntu.com/ubuntu-server/eoan/daily-preinstalled/20191126.2/

And "100% happen" means it will freeze every time you reboot and input the password to login.

Thanks.

[Erik Castricum (cas-2)]

@hui.wang, see #20
I had to set this again this morning on updating.
Is this known? If not set I get this upon flash-kernel:

erikcas@thuis:~$ sudo flash-kernel
/usr/share/flash-kernel/functions: line 160: warning: command substitution: ignored null byte in input
Unsupported platform.

I set this (manually) some days ago on flashing 1013 kernel. It seems not to be persistent.

If not known, is a seperate bug to be filed?

[Hui Wang (hui.wang)]

@Erik,

Dave Jones is working on the flash-kernel, and I remember there is already a bug to track this issue. Let Dave answer your question.

[Dave Jones (waveform)]

@Erik I don't think we've got a bug filed for that yet - I'll rectify that now as rev 1.2 of the Pi 4 will need to be added ... LP: #1854487. I'll try and get that patched and released reasonably quickly.

[Erik Castricum (cas-2)]

@Hui @Dave, thanks for quick response ;)

[Dave Jones (waveform)]

@Erik @wanthalf any chance the people with Pi 4 rev 1.2s can have a look at verifying LP: #1854487 ? Unfortunately I don't have a rev 1.2 (yet) and don't have a (reliable) means of obtaining one (yet). Should be reasonably trivial to verify; thanks for any assistance!

[Erik Castricum (cas-2)]

@Dave, after a dist-uograde rev 1.2 is present:

but:
ls -la /usr/share/flash-kernel/db/all.db

-rw-r--r-- 1 root root 56803 Nov 29 17:33 /usr/share/flash-kernel/db/all.db

so probably is the manually edited one. Maybe NOOB question: How do I trigger a regenaration of the file?

[Brian Murray (brian-murray)]

@Erik - Why do you want to regenerate the file? Mine has a similar time stamp but includes the 1.2 e.g.

ubuntu@ubuntu:~$ grep "Pi 4" /usr/share/flash-kernel/db/all.db
Machine: Raspberry Pi 4 Model B
Machine: Raspberry Pi 4 Model B Rev 1.1
Machine: Raspberry Pi 4 Model B Rev 1.2

[Erik Castricum (cas-2)]

@Brian,

output is same here. Issue is:

Last time I updated from 1013 to 1014 (if I remember well) the content was reset to its previous state, see my comment #44. The line "Machine: Raspberry Pi 4 Model B Rev 1.2" was dissapeared.

So in order to confirm Daves question, I need to be sure the "Machine: Raspberry Pi 4 Model B Rev 1.2" line is peristent between updates now. I cannot be shure if it has the timestamp from my manual entry.

[Erik Castricum (cas-2)]

@Brian, @Dave, to be sure this is the timeline on my machine:

running 1012, updating to 1013: "Unsupported Platform"
manually edit all.db. Added "Machine: Raspberry Pi 4 Model B Rev 1.2"
Then it updated to 1013 w/o issues.

running 1013, updating to 1014: "Unsupported Platform"
*again* have to manually edit all.db. Added "Machine: Raspberry Pi 4 Model B Rev 1.2"
Then it updated to 1014 w/o issues.

[Brian Murray (brian-murray)]

@Erik - Where is the 1012, 1013, 1014 number coming from?

[Brian Murray (brian-murray)]

Oh, that's the kernel version. The version that is important is that of flash-kernel. If you install version 3.98ubuntu5.3 of flash-kernel and then update the kernel you should not see "Unsupported Platform".

[Erik Castricum (cas-2)]

erikcas@thuis:~$ sudo apt install --reinstall flash-kernel
Reading package lists... Done
....
...

Setting up flash-kernel (3.98ubuntu5.3) ...
Processing triggers for man-db (2.8.7-3) ...

so that is oke

and flash-kernel succeeds w/o issues

[Stephan van Ingen (stephanvaningen)]

I find in the main download pages (http://cdimage.ubuntu.com/releases/19.10/release) "ubuntu-19.10.1-preinstalled-server-arm64+raspi3.img.xz" of date Dec3 (16:50) - does that build include this bug-correction?

[Brian Murray (brian-murray)]

On Thu, Dec 05, 2019 at 10:20:31PM -0000, Stephan van Ingen wrote:
> I find in the main download pages
> (http://cdimage.ubuntu.com/releases/19.10/release) "ubuntu-19.10.1
> -preinstalled-server-arm64+raspi3.img.xz" of date Dec3 (16:50) - does
> that build include this bug-correction?

Yes it does.

--
Brian Murray

[Stephan van Ingen (stephanvaningen)]

Super!
Thanks for your effort Hui, Brian, and anybody else who worked on this.

[Stephan van Ingen (stephanvaningen)]

(Does a dist-upgrade go from 19.10 to 19.10.1 or do I need to do a reinstall?)

[Brian Murray (brian-murray)]

Upgrading packages on the system via apt will put you in a situation where you have an install equivalent to 19.10.1.