Skip to content
linux-nerds.org

linux-nerds.org
  1. Übersicht
  2. Pine64
  3. ROCKPro64
  4. ROCKPro64 - USB3 Probleme

ROCKPro64 - USB3 Probleme

ROCKPro64
  • FrankMF

    Nehmen wir einen uralten USB2-Stick, Größe 8GB und flashen Kamil's letztes Image drauf. Ab in den USB3-Port und starten.

    USB2-Stick am USB3-Port

    System

    rock64@rockpro64:~$ uname -a
Linux rockpro64 4.4.132-1075-rockchip-ayufan-ga83beded8524 #1 SMP Thu Jul 26 08:22:22 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux

    lsusb

    rock64@rockpro64:~$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

    fdisk

     Disk /dev/sda: 7.5 GiB, 8022654976 bytes, 15669248 sectors
 Units: sectors of 1 * 512 = 512 bytes
 Sector size (logical/physical): 512 bytes / 512 bytes
 I/O size (minimum/optimal): 512 bytes / 512 bytes
 Disklabel type: gpt
 Disk identifier: 2C9A4A22-7AA8-4A1B-815E-0C3E2E7065E6
 
 Device      Start      End  Sectors  Size Type
 /dev/sda1      64     8063     8000  3.9M Linux filesystem
 /dev/sda2    8064     8191      128   64K Linux filesystem
 /dev/sda3    8192    16383     8192    4M Linux filesystem
 /dev/sda4   16384    24575     8192    4M Linux filesystem
 /dev/sda5   24576    32767     8192    4M Linux filesystem
 /dev/sda6   32768   262143   229376  112M Microsoft basic data
 /dev/sda7  262144 15669214 15407071  7.4G Linux filesystem

    dmesg

    rock64@rockpro64:~$ sudo dmesg | grep -i usb
[    0.506700] usbcore: registered new interface driver usbfs
[    0.506756] usbcore: registered new interface driver hub
[    0.506852] usbcore: registered new device driver usb
[    0.909861] phy phy-ff770000.syscon:usb2-phy@e460.0: Looking up phy-supply from device tree
[    0.909874] phy phy-ff770000.syscon:usb2-phy@e460.0: Looking up phy-supply property in node /syscon@ff770000/usb2-phy@e460/otg-port failed
[    0.910150] phy phy-ff770000.syscon:usb2-phy@e460.0: Looking up vbus-supply from device tree
[    0.910161] phy phy-ff770000.syscon:usb2-phy@e460.0: Looking up vbus-supply property in node /syscon@ff770000/usb2-phy@e460/otg-port failed
[    0.910174] phy phy-ff770000.syscon:usb2-phy@e460.0: Failed to get VBUS supply regulator
[    0.910358] phy phy-ff770000.syscon:usb2-phy@e460.1: Looking up phy-supply from device tree
[    0.910440] vcc5v0_host: could not add device link phy-ff770000.syscon:usb2-phy@e460.1 err -2
[    0.912857] phy phy-ff800000.phy.4: Looking up phy-supply property in node /phy@ff800000/usb3-port failed
[    1.044647] usbcore: registered new interface driver udl
[    1.151977] usbcore: registered new interface driver cdc_ether
[    1.152585] usbcore: registered new interface driver rndis_host
[    1.155022] rockchip-dwc3 usb@fe800000: failed to get drvdata dwc3
[    1.161158] rockchip-dwc3 usb@fe900000: fail to get drvdata hcd
[    1.163433] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.169174] ehci-platform fe3c0000.usb: EHCI Host Controller
[    1.169931] ehci-platform fe3c0000.usb: new USB bus registered, assigned bus number 1
[    1.170823] ehci-platform fe3c0000.usb: irq 29, io mem 0xfe3c0000
[    1.177217] ehci-platform fe3c0000.usb: USB 2.0 started, EHCI 1.00
[    1.178021] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    1.178666] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.179363] usb usb1: Product: EHCI Host Controller
[    1.179823] usb usb1: Manufacturer: Linux 4.4.132-1075-rockchip-ayufan-ga83beded8524 ehci_hcd
[    1.180631] usb usb1: SerialNumber: fe3c0000.usb
[    1.181678] hub 1-0:1.0: USB hub found
[    1.183295] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    1.185080] ohci-platform fe3e0000.usb: Generic Platform OHCI controller
[    1.185923] ohci-platform fe3e0000.usb: new USB bus registered, assigned bus number 2
[    1.186791] ohci-platform fe3e0000.usb: irq 30, io mem 0xfe3e0000
[    1.242415] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
[    1.243045] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.243742] usb usb2: Product: Generic Platform OHCI controller
[    1.244307] usb usb2: Manufacturer: Linux 4.4.132-1075-rockchip-ayufan-ga83beded8524 ohci_hcd
[    1.245104] usb usb2: SerialNumber: fe3e0000.usb
[    1.246158] hub 2-0:1.0: USB hub found
[    1.249659] usbcore: registered new interface driver iforce
[    1.250247] usbcore: registered new interface driver xpad
[    1.251035] usbcore: registered new interface driver usbtouchscreen
[    1.294313] fusb302 4-0022: GPIO lookup for consumer int-n
[    1.294325] fusb302 4-0022: using device tree for GPIO lookup
[    1.294366] of_get_named_gpiod_flags: parsed 'int-n-gpios' property of node '/i2c@ff3d0000/fusb30x@22[0]' - status (0)
[    1.294400] fusb302 4-0022: GPIO lookup for consumer vbus-5v
[    1.294410] fusb302 4-0022: using device tree for GPIO lookup
[    1.294442] of_get_named_gpiod_flags: parsed 'vbus-5v-gpios' property of node '/i2c@ff3d0000/fusb30x@22[0]' - status (0)
[    1.294473] fusb302 4-0022: GPIO lookup for consumer vbus-other
[    1.294482] fusb302 4-0022: using device tree for GPIO lookup
[    1.294494] of_get_named_gpiod_flags: can't parse 'vbus-other-gpios' property of node '/i2c@ff3d0000/fusb30x@22[0]'
[    1.294505] of_get_named_gpiod_flags: can't parse 'vbus-other-gpio' property of node '/i2c@ff3d0000/fusb30x@22[0]'
[    1.294515] fusb302 4-0022: using lookup tables for GPIO lookup
[    1.294525] fusb302 4-0022: lookup for GPIO vbus-other failed
[    1.294536] fusb302 4-0022: GPIO lookup for consumer discharge
[    1.294546] fusb302 4-0022: using device tree for GPIO lookup
[    1.294556] of_get_named_gpiod_flags: can't parse 'discharge-gpios' property of node '/i2c@ff3d0000/fusb30x@22[0]'
[    1.294567] of_get_named_gpiod_flags: can't parse 'discharge-gpio' property of node '/i2c@ff3d0000/fusb30x@22[0]'
[    1.294576] fusb302 4-0022: using lookup tables for GPIO lookup
[    1.294586] fusb302 4-0022: lookup for GPIO discharge failed
[    1.294794] fusb302 4-0022: Can't get property of role, set role to default DRP
[    1.304027] fusb302 4-0022: port 0 probe success with role ROLE_MODE_DRP, try_role ROLE_MODE_NONE
[    1.311598] usbcore: registered new interface driver uvcvideo
[    1.312130] USB Video Class driver (1.1.1)
[    1.323011] usbcore: registered new interface driver bfusb
[    1.323622] usbcore: registered new interface driver btusb
[    1.402019] usbcore: registered new interface driver usbhid
[    1.402547] usbhid: USB HID core driver
[    1.406726] usbcore: registered new interface driver snd-usb-audio
[    1.635272] phy phy-ff770000.syscon:usb2-phy@e450.5: Looking up phy-supply from device tree
[    1.635280] phy phy-ff770000.syscon:usb2-phy@e450.5: Looking up phy-supply property in node /syscon@ff770000/usb2-phy@e450/otg-port failed
[    1.635486] phy phy-ff770000.syscon:usb2-phy@e450.5: Looking up vbus-supply from device tree
[    1.635492] phy phy-ff770000.syscon:usb2-phy@e450.5: Looking up vbus-supply property in node /syscon@ff770000/usb2-phy@e450/otg-port failed
[    1.635501] phy phy-ff770000.syscon:usb2-phy@e450.5: Failed to get VBUS supply regulator
[    1.636465] phy phy-ff770000.syscon:usb2-phy@e450.6: Looking up phy-supply from device tree
[    1.636532] vcc5v0_host: could not add device link phy-ff770000.syscon:usb2-phy@e450.6 err -2
[    1.637072] phy phy-ff7c0000.phy.8: Looking up phy-supply property in node /phy@ff7c0000/usb3-port failed
[    2.002312] xhci-hcd xhci-hcd.5.auto: new USB bus registered, assigned bus number 3
[    2.005009] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[    2.005732] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.006494] usb usb3: Product: xHCI Host Controller
[    2.007009] usb usb3: Manufacturer: Linux 4.4.132-1075-rockchip-ayufan-ga83beded8524 xhci-hcd
[    2.007904] usb usb3: SerialNumber: xhci-hcd.5.auto
[    2.008827] hub 3-0:1.0: USB hub found
[    2.010665] xhci-hcd xhci-hcd.5.auto: new USB bus registered, assigned bus number 4
[    2.011522] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[    2.012453] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
[    2.013164] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.013932] usb usb4: Product: xHCI Host Controller
[    2.014454] usb usb4: Manufacturer: Linux 4.4.132-1075-rockchip-ayufan-ga83beded8524 xhci-hcd
[    2.015351] usb usb4: SerialNumber: xhci-hcd.5.auto
[    2.016257] hub 4-0:1.0: USB hub found
[    2.018942] usb usb4: USB disconnect, device number 1
[    2.044906] xhci-hcd xhci-hcd.5.auto: USB bus 4 deregistered
[    2.046163] usb usb3: USB disconnect, device number 1
[    2.047960] xhci-hcd xhci-hcd.5.auto: USB bus 3 deregistered
[    2.056668] xhci-hcd xhci-hcd.6.auto: new USB bus registered, assigned bus number 3
[    2.059352] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[    2.060063] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.060827] usb usb3: Product: xHCI Host Controller
[    2.061348] usb usb3: Manufacturer: Linux 4.4.132-1075-rockchip-ayufan-ga83beded8524 xhci-hcd
[    2.062244] usb usb3: SerialNumber: xhci-hcd.6.auto
[    2.063232] hub 3-0:1.0: USB hub found
[    2.076328] xhci-hcd xhci-hcd.6.auto: new USB bus registered, assigned bus number 4
[    2.086994] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[    2.097798] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
[    2.108306] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.114105] usb usb4: Product: xHCI Host Controller
[    2.119391] usb usb4: Manufacturer: Linux 4.4.132-1075-rockchip-ayufan-ga83beded8524 xhci-hcd
[    2.125089] usb usb4: SerialNumber: xhci-hcd.6.auto
[    2.131514] hub 4-0:1.0: USB hub found
[    2.144513] ehci-platform fe380000.usb: EHCI Host Controller
[    2.149510] ehci-platform fe380000.usb: new USB bus registered, assigned bus number 5
[    2.154292] ehci-platform fe380000.usb: irq 27, io mem 0xfe380000
[    2.164358] ehci-platform fe380000.usb: USB 2.0 started, EHCI 1.00
[    2.168907] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002
[    2.173322] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.177741] usb usb5: Product: EHCI Host Controller
[    2.181911] usb usb5: Manufacturer: Linux 4.4.132-1075-rockchip-ayufan-ga83beded8524 ehci_hcd
[    2.186427] usb usb5: SerialNumber: fe380000.usb
[    2.191426] hub 5-0:1.0: USB hub found
[    2.199780] ohci-platform fe3a0000.usb: Generic Platform OHCI controller
[    2.204285] ohci-platform fe3a0000.usb: new USB bus registered, assigned bus number 6
[    2.208254] ohci-platform fe3a0000.usb: irq 28, io mem 0xfe3a0000
[    2.266912] usb usb6: New USB device found, idVendor=1d6b, idProduct=0001
[    2.285507] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.303922] usb usb6: Product: Generic Platform OHCI controller
[    2.322261] usb usb6: Manufacturer: Linux 4.4.132-1075-rockchip-ayufan-ga83beded8524 ohci_hcd
[    2.341046] usb usb6: SerialNumber: fe3a0000.usb
[    2.361476] hub 6-0:1.0: USB hub found
[    2.461390] usb 3-1: new high-speed USB device number 2 using xhci-hcd
[    2.667220] usb 3-1: New USB device found, idVendor=090c, idProduct=1000
[    2.667226] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    2.667230] usb 3-1: Product: USB Flash Disk
[    2.667234] usb 3-1: Manufacturer: General
[    2.667238] usb 3-1: SerialNumber: 042NR6E8C5MLE2GT
[    2.712883] usb 3-1: ep 0x81 - rounding interval to 128 microframes, ep desc says 255 microframes
[    2.719848] usb 3-1: ep 0x2 - rounding interval to 128 microframes, ep desc says 255 microframes
[    3.080440] usb-storage 3-1:1.0: USB Mass Storage device detected
[    3.081243] scsi host0: usb-storage 3-1:1.0
[    3.081460] usbcore: registered new interface driver usb-storage
[    3.082140] usbcore: registered new interface driver uas
[    4.215095] scsi 0:0:0:0: Direct-Access     General  USB Flash Disk   1100 PQ: 0 ANSI: 4

    Das System läuft. Das Logfile -> https://pastebin.com/FimTdZc3

    Nun wollen wir mal schauen, was der andere Stick so auswirft. Den Corsair Voyager GTX eingesteckt und Los!

    USB3-Stick am USB3-Port

    Log

     =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2018.09.20 09:12:03 =~=~=~=~=~=~=~=~=~=~=~=
 DDR Version 1.13 20180801
 In
 Channel 0: LPDDR4,50MHz
 CS = 0
 MR0=0x98
 MR4=0x3
 MR5=0xFF
 MR8=0x8
 MR12=0x4D
 MR14=0x4D
 MR18=0x0
 MR19=0x0
 MR24=0x8
 MR25=0x0
 CS = 1
 MR0=0x18
 MR4=0x3
 MR5=0xFF
 MR8=0x8
 MR12=0x4D
 MR14=0x4D
 MR18=0x0
 MR19=0x0
 MR24=0x8
 MR25=0x0
 Bus Width=32 Col=10 Bank=8 Row=15/15 CS=2 Die Bus-Width=16 Size=2048MB
 Channel 1: LPDDR4,50MHz
 CS = 0
 MR0=0x98
 MR4=0x3
 MR5=0xFF
 MR8=0x8
 MR12=0x4D
 MR14=0x4D
 MR18=0x0
 MR19=0x0
 MR24=0x8
 MR25=0x0
 CS = 1
 MR0=0x18
 MR4=0x1
 MR5=0xFF
 MR8=0x8
 MR12=0x4D
 MR14=0x4D
 MR18=0x0
 MR19=0x0
 MR24=0x8
 MR25=0x0
 Bus Width=32 Col=10 Bank=8 Row=15/15 CS=2 Die Bus-Width=16 Size=2048MB
 256B stride
 channel 0
 CS = 0
 MR0=0x98
 MR4=0x81
 MR5=0xFF
 MR8=0x8
 MR12=0x72
 MR14=0x72
 MR18=0x0
 MR19=0x0
 MR24=0x8
 MR25=0x0
 CS = 1
 MR0=0x18
 MR4=0x81
 MR5=0xFF
 MR8=0x8
 MR12=0x72
 MR14=0x72
 MR18=0x0
 MR19=0x0
 MR24=0x8
 MR25=0x0
 channel 1
 CS = 0
 MR0=0x98
 MR4=0x3
 MR5=0xFF
 MR8=0x8
 MR12=0x72
 MR14=0x72
 MR18=0x0
 MR19=0x0
 MR24=0x8
 MR25=0x0
 CS = 1
 MR0=0x18
 MR4=0x1
 MR5=0xFF
 MR8=0x8
 MR12=0x72
 MR14=0x72
 MR18=0x0
 MR19=0x0
 MR24=0x8
 MR25=0x0
 channel 0 training pass!
 channel 1 training pass!
 change freq to 400MHz 0,1
 channel 0
 CS = 0
 MR0=0x98
 MR4=0x1
 MR5=0xFF
 MR8=0x8
 MR12=0x72
 MR14=0x72
 MR18=0x0
 MR19=0x0
 MR24=0x8
 MR25=0x0
 CS = 1
 MR0=0x18
 MR4=0x1
 MR5=0xFF
 MR8=0x8
 MR12=0x72
 MR14=0x72
 MR18=0x0
 MR19=0x0
 MR24=0x8
 MR25=0x0
 channel 1
 CS = 0
 MR0=0x98
 MR4=0x81
 MR5=0xFF
 MR8=0x8
 MR12=0x72
 MR14=0x72
 MR18=0x0
 MR19=0x0
 MR24=0x8
 MR25=0x0
 CS = 1
 MR0=0x18
 MR4=0x1
 MR5=0xFF
 MR8=0x8
 MR12=0x72
 MR14=0x72
 MR18=0x0
 MR19=0x0
 MR24=0x8
 MR25=0x0
 channel 0 training pass!
 channel 1 training pass!
 change freq to 800MHz 1,0
 ch 0 ddrconfig = 0x101, ddrsize = 0x2020
 ch 1 ddrconfig = 0x101, ddrsize = 0x2020
 pmugrf_os_reg[2] = 0x3AA1FAA1, stride = 0xD
 OUT
 U-Boot SPL board init
 
 U-Boot SPL 2017.09-rockchip-ayufan-1033-gdf02018479 (Aug 06 2018 - 22:29:15)
 booted from SPI flash
 Trying to boot from SPI
 NOTICE:  BL31: v1.3(debug):65aa5ce
 NOTICE:  BL31: Built : 10:47:37, Jun 19 2018
 NOTICE:  BL31: Rockchip release version: v1.1
 INFO:    GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3
 INFO:    Using opteed sec cpu_context!
 INFO:    boot cpu mask: 0
 INFO:    plat_rockchip_pmu_init(1151): pd status 3e
 INFO:    BL31: Initializing runtime services
 WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK
 ERROR:   Error initializing runtime service opteed_fast
 INFO:    BL31: Preparing for EL3 exit to normal world
 INFO:    Entry point address = 0x200000
 INFO:    SPSR = 0x3c9
 
 
 U-Boot 2017.09-rockchip-ayufan-1033-gdf02018479 (Aug 06 2018 - 22:29:23 +0000)
 
 Model: Pine64 RockPro64
 DRAM:  3.9 GiB
 DCDC_REG1@vdd_center: ; enabling
 DCDC_REG2@vdd_cpu_l: ; enabling
 DCDC_REG3@vcc_ddr: ; enabling (ret: -38)
 DCDC_REG4@vcc_1v8: set 1800000 uV; enabling
 LDO_REG1@vcc1v8_dvp: set 1800000 uV; enabling
 LDO_REG2@vcc3v0_touch: set 3000000 uV; enabling
 LDO_REG3@vcc1v8_pmu: set 1800000 uV; enabling
 LDO_REG4@vcc_sd: set 3300000 uV; enabling
 LDO_REG5@vcca3v0_codec: set 3000000 uV; enabling
 LDO_REG6@vcc_1v5: set 1500000 uV; enabling
 LDO_REG7@vcca1v8_codec: set 1800000 uV; enabling
 LDO_REG8@vcc_3v0: set 3000000 uV; enabling
 SWITCH_REG1@vcc3v3_s3: ; enabling (ret: -38)
 SWITCH_REG2@vcc3v3_s0: ; enabling (ret: -38)
 vcc1v8-s0@vcc1v8_s0: set 1800000 uV; enabling (ret: -38)
 dc-12v@dc_12v: set 12000000 uV; enabling (ret: -38)
 vcc-sys@vcc_sys: set 5000000 uV; enabling (ret: -38)
 vcc3v3-sys@vcc3v3_sys: set 3300000 uV; enabling (ret: -38)
 vcc-phy-regulator@vcc_phy: ; enabling (ret: -38)
 vdd-log@vdd_log: ; enabling (ret: -38)
 MMC:   sdhci@fe330000: 0, dwmmc@fe320000: 1
 SF: Detected gd25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
 *** Warning - bad CRC, using default environment
 
 In:    serial@ff1a0000
 Out:   serial@ff1a0000
 Err:   serial@ff1a0000
 Model: Pine64 RockPro64
 Net:   eth0: ethernet@fe300000
 Hit any key to stop autoboot:  0 
 Card did not respond to voltage select!
 mmc_init: -95, time 20
 Card did not respond to voltage select!
 mmc_init: -95, time 9
 starting USB...
 USB0:   USB EHCI 1.00
 USB1:   USB EHCI 1.00
 USB2:   Register 2000140 NbrPorts 2
 Starting the controller
 USB XHCI 1.10
 USB3:   Register 2000140 NbrPorts 2
 Starting the controller
 USB XHCI 1.10
 scanning bus 0 for devices... 1 USB Device(s) found
 scanning bus 1 for devices... 1 USB Device(s) found
 scanning bus 2 for devices... 1 USB Device(s) found
 scanning bus 3 for devices... 1 USB Device(s) found
        scanning usb for storage devices... 0 Storage Device(s) found
 
 Device 0: unknown device
 Speed: 1000, full duplex
 BOOTP broadcast 1
 BOOTP broadcast 2
 BOOTP broadcast 3
 DHCP client bound to address 192.168.3.15 (1007 ms)
 *** Warning: no boot file name; using 'C0A8030F.img'
 Using ethernet@fe300000 device
 TFTP from server 0.0.0.0; our IP address is 192.168.3.15; sending through gateway 192.168.3.1
 Filename 'C0A8030F.img'.
 Load address: 0x800800
 Loading: *T T

    Es ist alles gleich zum anderen Log. Aber beim Scannen vom USB3-Bus wird der Stick nicht erkannt. Hmm???

    Der selbe Stick am USB2-Port.

    USB3-Stick am USB2-Port

    Logfile

    Link Preview Image
    usb3_stick_usb2_port_ok - Pastebin.com

    Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

    favicon

    Pastebin (pastebin.com)

    dmesg

    rock64@rockpro64v_2_1:~$ sudo dmesg | grep -i usb 
[sudo] password for rock64: 
[    1.796818] usbcore: registered new interface driver usbfs
[    1.797086] usbcore: registered new interface driver hub
[    1.797427] usbcore: registered new device driver usb
[    4.830911] pegasus: v0.9.3 (2013/04/25), Pegasus/Pegasus II USB Ethernet driver
[    4.831796] usbcore: registered new interface driver pegasus
[    4.832477] usbcore: registered new interface driver rtl8150
[    4.833082] usbcore: registered new interface driver r8152
[    4.833652] usbcore: registered new interface driver asix
[    4.834204] usbcore: registered new interface driver ax88179_178a
[    4.834898] usbcore: registered new interface driver cdc_ether
[    4.835490] usbcore: registered new interface driver dm9601
[    4.836060] usbcore: registered new interface driver CoreChips
[    4.836666] usbcore: registered new interface driver smsc75xx
[    4.837264] usbcore: registered new interface driver smsc95xx
[    4.837838] usbcore: registered new interface driver net1080
[    4.838495] usbcore: registered new interface driver plusb
[    4.839063] usbcore: registered new interface driver cdc_subset
[    4.839665] usbcore: registered new interface driver MOSCHIP usb-ethernet driver
[    4.840440] usbcore: registered new interface driver cdc_ncm
[    4.862016] OF: graph: no port node found in /syscon@ff770000/usb2-phy@e450/otg-port
[    4.878662] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    4.882898] ehci-platform fe380000.usb: EHCI Host Controller
[    4.883450] ehci-platform fe380000.usb: new USB bus registered, assigned bus number 1
[    4.886020] ehci-platform fe380000.usb: irq 30, io mem 0xfe380000
[    4.902423] ehci-platform fe380000.usb: USB 2.0 started, EHCI 1.00
[    4.904589] hub 1-0:1.0: USB hub found
[    4.909185] ehci-platform fe3c0000.usb: EHCI Host Controller
[    4.909739] ehci-platform fe3c0000.usb: new USB bus registered, assigned bus number 2
[    4.912468] ehci-platform fe3c0000.usb: irq 32, io mem 0xfe3c0000
[    4.926391] ehci-platform fe3c0000.usb: USB 2.0 started, EHCI 1.00
[    4.928201] hub 2-0:1.0: USB hub found
[    4.931723] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    4.933894] ohci-platform fe3a0000.usb: Generic Platform OHCI controller
[    4.934653] ohci-platform fe3a0000.usb: new USB bus registered, assigned bus number 3
[    4.937294] ohci-platform fe3a0000.usb: irq 31, io mem 0xfe3a0000
[    4.999723] hub 3-0:1.0: USB hub found
[    5.001606] ohci-platform fe3e0000.usb: Generic Platform OHCI controller
[    5.002237] ohci-platform fe3e0000.usb: new USB bus registered, assigned bus number 4
[    5.003822] ohci-platform fe3e0000.usb: irq 33, io mem 0xfe3e0000
[    5.067579] hub 4-0:1.0: USB hub found
[    5.072347] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 5
[    5.079373] hub 5-0:1.0: USB hub found
[    5.081263] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 6
[    5.081968] xhci-hcd xhci-hcd.0.auto: Host supports USB 3.0  SuperSpeed
[    5.082776] usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
[    5.084532] hub 6-0:1.0: USB hub found
[    5.086777] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 7
[    5.164548] hub 7-0:1.0: USB hub found
[    5.188617] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 8
[    5.191985] xhci-hcd xhci-hcd.1.auto: Host supports USB 3.0  SuperSpeed
[    5.197829] usb usb8: We don't know the algorithms for LPM for this host, disabling LPM.
[    5.227852] hub 8-0:1.0: USB hub found
[    5.271464] usbcore: registered new interface driver usb-storage
[    5.572499] usbcore: registered new interface driver usbhid
[    5.573102] usbhid: USB HID core driver
[    6.610333] usb 1-1: new high-speed USB device number 2 using ehci-platform
[    6.786867] usbcore: registered new interface driver uas

    lsusb

    rock64@rockpro64v_2_1:~$ lsusb
   Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 002: ID 1b1c:1a0e Corsair 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

    Ich kann hier leider gar nichts erkennen, wo man auf das Problem schließen kann. Aber evt. hat Kamil ja eine Erklärung dafür. 😞

    Im Fediverse -> @FrankM@nrw.social

    1. NanoPi R5S
    2. Quartz64 Model B, 4GB RAM
    3. Quartz64 Model A, 4GB RAM
    4. RockPro64 v2.1
    0

  • FrankMF

    RockPro64 - Mainline Kernel 6.8.0-rc3

    ROCKPro64
    1
    0 Stimmen
    1 Beiträge
    229 Aufrufe
    Niemand hat geantwortet
  • FrankMF

    ROCKPro64 - Debian Bullseye Teil 1

    ROCKPro64
    17
    0 Stimmen
    17 Beiträge
    2k Aufrufe
    FrankMF

    Durch diesen Beitrag ist mir mal wieder eingefallen, das wir das erneut testen könnten 😉

    Also die aktuellen Daten von Debian gezogen. Das Image gebaut, könnt ihr alles hier im ersten Beitrag nachlesen. Da die eingebaute Netzwerkschnittstelle nicht erkannt wurde, habe ich mal wieder den USB-to-LAN Adapter eingesetzt.

    Bus 005 Device 002: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet

    Die Installation wollte ich auf einem NVMe Riegel installieren.

    Die Debian Installation durchgezogen und nach erfolgreicher Installation neugestartet. Und siehe da, ohne das man alles möglich ändern musste, bootete die NVMe SSD 🤓

    Eingesetzter uboot -> 2020.01-ayufan-2013......

    Die nicht erkannte LAN-Schnittstelle müsste an nicht freien Treibern liegen, hatte ich da irgendwo kurz gelesen. Beim Schreiben dieses Satzes kam die Nacht und ich konnte noch mal drüber schlafen. Heute Morgen, beim ersten Kaffee, dann noch mal logischer an die Sache ran gegangen.

    Wir schauen uns mal die wichtigsten Dinge an.

    root@debian:~# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 62:03:b0:d6:dc:b3 brd ff:ff:ff:ff:ff:ff 3: enx000acd26e2c8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 00:0a:cd:26:e2:c8 brd ff:ff:ff:ff:ff:ff inet 192.168.3.208/24 brd 192.168.3.255 scope global dynamic enx000acd26e2c8 valid_lft 42567sec preferred_lft 42567sec inet6 fd8a:6ff:2880:0:20a:cdff:fe26:e2c8/64 scope global dynamic mngtmpaddr valid_lft forever preferred_lft forever inet6 2a02:908:1260:13bc:20a:xxxx:xxxx:xxxx/64 scope global dynamic mngtmpaddr valid_lft 5426sec preferred_lft 1826sec inet6 fe80::20a:cdff:fe26:e2c8/64 scope link valid_lft forever preferred_lft forever

    Ok, er zeigt mir die Schnittstelle eth0 ja an, dann kann es an fehlenden Treibern ja nicht liegen. Lässt dann auf eine fehlerhafte Konfiguration schließen. Nächster Halt wäre dann /etc/network/interfaces

    Das trägt Debian ein

    # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface allow-hotplug enx000acd26e2c8 iface enx000acd26e2c8 inet dhcp # This is an autoconfigured IPv6 interface iface enx000acd26e2c8 inet6 auto

    Gut, bei der Installation hat Debian ja nur die zusätzliche Netzwerkschnittstelle erkannt, folgerichtig ist die auch als primäre Schnittstelle eingetragen. Dann ändern wir das mal...

    # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface #allow-hotplug enx000acd26e2c8 allow-hotplug eth0 #iface enx000acd26e2c8 inet dhcp iface eth0 inet dhcp # This is an autoconfigured IPv6 interface #iface enx000acd26e2c8 inet6 auto iface eth0 inet6 auto

    Danach einmal alles neu starten bitte 😉

    systemctl status networking

    Da fehlte mir aber jetzt die IPv4 Adresse, so das ich einmal komplett neugestartet habe. Der Ordnung halber, so hätte man die IPv4 Adresse bekommen.

    dhclient eth0

    Nachdem Neustart kam dann das

    root@debian:/etc/network# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 62:03:b0:d6:dc:b3 brd ff:ff:ff:ff:ff:ff inet 192.168.3.172/24 brd 192.168.3.255 scope global dynamic eth0 valid_lft 42452sec preferred_lft 42452sec inet6 fd8a:6ff:2880:0:6003:b0ff:fed6:dcb3/64 scope global dynamic mngtmpaddr valid_lft forever preferred_lft forever inet6 2a02:908:1260:13bc:6003:xxxx:xxxx:xxxx/64 scope global dynamic mngtmpaddr valid_lft 5667sec preferred_lft 2067sec inet6 fe80::6003:b0ff:fed6:dcb3/64 scope link valid_lft forever preferred_lft forever 3: enx000acd26e2c8: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:0a:cd:26:e2:c8 brd ff:ff:ff:ff:ff:ff

    Fertig, eth0 läuft. Nun kann man den zusätzlichen Adapter entfernen oder halt konfigurieren, wenn man ihn braucht.

    Warum der Debian Installer die eth0 nicht erkennt verstehe ich nicht, aber vielleicht wird das irgendwann auch noch gefixt. Jetzt habe ich erst mal einen Workaround um eine Installation auf den ROCKPro64 zu bekommen.

  • FrankMF

    ROCKPro64 - Kernel 5.6 und Wireguard 1.0

    ROCKPro64
    1
    0 Stimmen
    1 Beiträge
    305 Aufrufe
    Niemand hat geantwortet
  • FrankMF

    ROCKPro64 - Armbian - NAS umgezogen

    Armbian
    2
    0 Stimmen
    2 Beiträge
    593 Aufrufe
    FrankMF

    Das NAS mit den drei 2,5 Zoll HDD Platten läuft an einem 3A Netzteil - ohne Probleme. Hat heute Nacht die Jobs einwandfrei erledigt 😉

    Link Preview Image PINE64 Community

    PINE64 is a large, vibrant and diverse community and creates software, documentation and projects.

    favicon

    (www.pine64.org)

  • FrankMF

    Armbian für den ROCKPro64

    Angeheftet Armbian
    1
    0 Stimmen
    1 Beiträge
    529 Aufrufe
    Niemand hat geantwortet
  • FrankMF

    Benchmark

    ROCKPro64
    1
    0 Stimmen
    1 Beiträge
    446 Aufrufe
    Niemand hat geantwortet
  • FrankMF

    zram - Was das??

    ROCKPro64
    3
    0 Stimmen
    3 Beiträge
    923 Aufrufe
    FrankMF

    @tkaiser ; Ich hab dich vermisst 😂

    Danke für die Info, ich bin vor dem ROCKPro64 da noch nie so richtig drüber gestolpert. Aber wenn ich dann was finde, schau auch immer wofür es denn bitte ist.

    Danke für Deine Hinweise.

  • FrankMF

    Interessante Links

    ROCKPro64
    1
    0 Stimmen
    1 Beiträge
    638 Aufrufe
    Niemand hat geantwortet