Jump to content
  • 0

Helios64 - Armbian 23.08 Bookworm issues

ebin-dev

Asked by ebin-dev,

 Share

Question

ebin-dev

ebin-dev

Posted
Posted (edited)

Recently a new Armbian 23.08.1 Bookworm image with linux-6.1.50 was made available for Helios64 on its download page (see here) - which is as such great 😀.

 

Everything  starts up nicely, but unlike the previous Bookworm 23.05 image, the current one has an issue with accessing USB devices. In the boot process the following error occurs: 

  

# cat /var/log/syslog | grep error
2023-09-07T12:31:05.671598+02:00 helios64 kernel: [    2.537009] dwc3 fe900000.usb: error -ETIMEDOUT: failed to initialize core
2023-09-07T12:31:05.671602+02:00 helios64 kernel: [    2.537107] dwc3: probe of fe900000.usb failed with error -110

 

No USB device could be accessed.

 

As this seems to be related to the realtek driver r8152, I compiled and installed the current version of that driver (see below) and after that the USB devices were accessible.

  

# compile and install the current realtek driver
git clone https://github.com/wget/realtek-r8152-linux.git
cd realtek-r8152-linux...
make 
sudo make install
Edited by ebin-dev
0
Link to comment
Share on other sites

10 answers to this question

Recommended Posts

  • 0
ebin-dev

ebin-dev

Posted
  • Author
Posted (edited)

For linux versions higher than 5.12, the Armbian build system does not replace the realtek driver r8152 but it uses an aged realtek driver from the linux source tree.

So if someone intends to build from sources at home, the realtek r8152 driver in the linux source tree must be replaced by a newer version, otherwise USB devices will not be accessible to helios64.

 

It follows that all fully automated builds with the current Armbian build system building linux kernel versions higher than 5.12 will not support USB devices on helios64 anymore (until that is fixed).

 

The good news is that there is an image available for download were the USB issue was fixed: Armbian_23.5.4_Helios64_bookworm_current_6.1.36.img (here)

Edited by ebin-dev
0
Link to comment
Share on other sites

Donate your old hardware to community. Start a giveaway Raffle!

  • 0
mrjpaxton

mrjpaxton

Posted
Posted (edited)

I don't know if 23.8 is the same as 23.08. This is where the numbering gets confusing, and I don't know why they did that...

 

If you mean "Colobus" which was released on Sep 1st, I'm not entirely on that version right now. I didn't "dist-upgrade" the rest of the 23.08 packages. I sort of am, but here's what I mean.

 

I have these packages held back: 

armbian-bsp-cli-helios64-current
armbian-config
armbian-firmware
armbian-plymouth-theme
linux-dtb-current-rockchip64
linux-image-current-rockchip64
linux-u-boot-helios64-current

 

My version of these is apparently at "23.08.0-trunk". I can verify that my system is still working with USB and everything. Sorry to hear you're having this problem, but thanks for telling us, because I was also getting concerned if I should upgrade them or not, but I think I will hold off for a bit. The newest one available is actually 23.8.1. Have you tried that specific one, yet?

Edited by mrjpaxton
0
Link to comment
Share on other sites
  • 0
ebin-dev

ebin-dev

Posted
  • Author
Posted (edited)

It does not matter if you refer to the current Armbian version as 23.8 as indicated on the helios64 download page or to 23.08 as indicated on the welcome screen. And it does not matter if it is 23.8.1.

 

The important bit is that any current linux kernel or image (fully automatically) built by the Armbian build system does not provide any USB support for your Helios64 for linux kernel versions higher than 5.12. You could verify that yourself by upgrading your backup sd to the current kernel versions.

 

Unless you have access to the original linux kernel debs you would have to reinstall your system entirely from scratch.

 

You should therefore not upgrade your system to any current linux kernel produced by the Armbian build system until the linux rtl8152 driver is replaced for kernel versions higher than 5.12 (in this code). For the time being you could disable Armbian updates entirely (and still receive debian updates):

  

cat /etc/apt/sources.list.d/armbian.list 

# deb http://apt.armbian.com bookworm main bookworm-utils bookworm-desktop
Edited by ebin-dev
0
Link to comment
Share on other sites
  • 0
alchemist

alchemist

Posted
Posted (edited)

Hi, I also have dwc3 usb issues since kernel 6.4.12 (mainstream vanilla).

It seems there is a regression. a patch is recently in discussion: https://lore.kernel.org/lkml/ba6285cb-f9ff-8047-ad53-1f4534517b66@synopsys.com/T/
Kernel 6.5 doesnt boot, I will check if I enabled the PCI SATA bridge

 

So, try to keep kernel <= 6.4.11

Edited by alchemist
0
Link to comment
Share on other sites
  • 0
ebin-dev

ebin-dev

Posted
  • Author
Posted (edited)

@alchemist Thank you for the hint !

 

The dwc3 usb issue remains even if I compile a more recent realtek-r8152-linux driver into kernel 6.1.52. So the realtek driver does not seem to be the (only) reason for the issue.

 

While compiling the kernel I was informed by the build system that 74 patches need to be rebased and that the rk3399-enable-dwc3-xhci-usb-trb-quirk.patch could not be applied - something has changed. 

 

This is how a system looks like that was not maintained for years ...

 

P.S.: I will therefore currently not upgrade Helios64 (hosting all my data) to Armbian bookworm 23.05.4-6.1.36. It uses the linux-tree rtl8152 driver and needs proper testing first, in particular network performance (1Gbit/s and 2.5Gbit/s interfaces), reliability of accessing emmc and stability.

Edited by ebin-dev
0
Link to comment
Share on other sites
  • 0
alchemist

alchemist

Posted
Posted (edited)

Hi!,

 

I tried kernel 6.5.2 vanilla

make oldconfig, + enable JMicron PATA driver

 

USB is working but I don't know if dwc3 is by chance reset or due to the fix...

EDIT: dwc3 reset still doesn't work, waiting for the fix

 

So yes, please freeze your kernels

Edited by alchemist
0
Link to comment
Share on other sites
  • 0
mrjpaxton

mrjpaxton

Posted
Posted (edited)

Ahh, okay. So it only has to do with the kernel and what version it is. Got it.

 

Well, I have an eMMC install, so I back up root FS and `/boot` on an SD card every month, or when making changes, since putting the backups on the NAS itself... won't work out very well unless it's also on the entire NAS backup disk I have, too.

 

But anyway, my kernel is "6.1.36-rockchip64", and just this week in early September I was able to do a full backup of my NAS array with Rsync on a USB 3 attached HDD just fine with zero problems on that kernel (I'm using the back USB ports, but that probably won't matter). Have you all also tested on both SD card and eMMC installs?

 

So wait, I'm guessing this "dwc3" driver thing has to do with some other problem besides specifically USB storage devices. Maybe there are some devices it will work with, and others that it wont?

Edited by mrjpaxton
0
Link to comment
Share on other sites
  • 0
ebin-dev

ebin-dev

Posted
  • Author
Posted (edited)

Linux 6.1.36 is not affected by the dwc3 usb issue. The braking changes made it into the kernel after that.

 

Thank you for confirming that you had no issues accessing emmc with that kernel - your system is even running from there.

 

Your linux kernel uses the linux-tree version of the realtek driver r8152. It is based on an old version of the manufacturer and we have to test if it is reliable when used to drive the 2.5G interface.

 

Once the dwc3 usb issue is resolved (upstream), I intend to build several versions of the linux kernel with different rtl8152 drivers so that performance and reliability can be compared.

Edited by ebin-dev
0
Link to comment
Share on other sites
  • 0
amurchick

amurchick

Posted
Posted
Цитата 
# cat /var/log/syslog | grep error 2023-09-07T12:31:05.671598+02:00 
[ 2.537009] dwc3 fe900000.usb: error -ETIMEDOUT: failed to initialize core
[ 2.537107] dwc3: probe of fe900000.usb failed with error -110

 

No USB device could be accessed.

@ebin-dev @alchemist
Current Armbian Build repo build images with kernel 6.5.4.
And kernel still have this issue ( 

[  +0.000000] Linux version 6.5.3-edge-rockchip64 (armbian@next) (aarch64-linux-gnu-gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #2 SMP PREEMPT Wed Sep 13 14:53:58 +07 2023
[  +0.013683] phy phy-ff800000.phy.8: phy poweron failed --> -110
[  +0.000616] dwc3 fe900000.usb: error -ETIMEDOUT: failed to initialize core
[  +0.000708] dwc3: probe of fe900000.usb failed with error -110

 

0
Link to comment
Share on other sites
  • 0
ebin-dev

ebin-dev

Posted
  • Author
Posted (edited)
On 9/7/2023 at 1:16 PM, ebin-dev said: 
# compile and install the current realtek driver
git clone https://github.com/wget/realtek-r8152-linux.git
cd realtek-r8152-linux...
make 
sudo make install

 

You could try the above and let us know if it solves the issue (should work for linux up to 6.4.10+).

Edited by ebin-dev
0
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
 Share
Go to question listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept