Jump to content

gnubie

Members
  • Posts

    2
  • Joined

  • Last visited

  1. /sys/class/leds is not populated when running jammy with kernel 5.16.11
  2. First up, I did have a good dig around but couldn't find anything discussing my problem but if there is a thread already existing please just link to it, no need to get huffy. I have a problem with armbian on NanoPi NEO where USB devices are not properly detected at start up (warm or cold start). Armbian version details: BOARD=nanopineo BOARD_NAME="NanoPi Neo" BOARDFAMILY=sun8i VERSION=5.67.181115 LINUXFAMILY=sunxi BRANCH=next ARCH=arm IMAGE_TYPE=nightly BOARD_TYPE=conf INITRD_ARCH=arm KERNEL_IMAGE_TYPE=zImage I have also tried nightly build Armbian_5.65_Nanopineo_Debian_stretch_next_4.14.78.img. The problem as seen from syslog: Nov 26 08:29:20 localhost kernel: [ 3.093697] usb 6-1: new full-speed USB device number 2 using ohci-platform Nov 26 08:29:20 localhost kernel: [ 3.285722] usb 6-1: device descriptor read/64, error -62 Nov 26 08:29:20 localhost kernel: [ 3.585689] usb 6-1: device descriptor read/64, error -62 Nov 26 08:29:20 localhost kernel: [ 3.881816] usb 6-1: new full-speed USB device number 3 using ohci-platform Nov 26 08:29:20 localhost kernel: [ 4.073774] usb 6-1: device descriptor read/64, error -62 Nov 26 08:29:20 localhost kernel: [ 4.373768] usb 6-1: device descriptor read/64, error -62 Nov 26 08:29:20 localhost kernel: [ 4.481838] usb usb6-port1: attempt power cycle Nov 26 08:29:20 localhost kernel: [ 4.985772] usb 6-1: new full-speed USB device number 4 using ohci-platform Nov 26 08:29:20 localhost kernel: [ 5.401757] usb 6-1: device not accepting address 4, error -62 Nov 26 08:29:20 localhost kernel: [ 5.589770] usb 6-1: new full-speed USB device number 5 using ohci-platform Nov 26 08:29:20 localhost kernel: [ 6.005759] usb 6-1: device not accepting address 5, error -62 Nov 26 08:29:20 localhost kernel: [ 6.005887] usb usb6-port1: unable to enumerate USB device I am attempting to connect a USB hard disk to the NanoPi NEO and have it mounted via fstab at boot. The problem occurs with either a bus powered USB hard disk (Toshiba brand) but also using a separately powered USB SATA bridge. Once armbian has completed boot and I can logon, plugging in the USB disk drives shows them correctly detected and they can be manually mounted. The problem does not occur when using nanopi-neo-core_sd_friendlycore-xenial_4.14_armhf_20181011.img from friendlyarm download site. Any suggestions as to how to fix this? Please do not say "it's your power supply". Power supply is not the problem.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines