search

hypriot / Pirate-ShieldTV

Hacking the Nvidia ShieldTV to use Ubuntu Linux for ARM64/AARCH64
https://blog.hypriot.com
MIT License
19 stars 0 forks source link

No network device when booting a TWRP recovery image #1

Open DieterReuter opened 8 years ago

DieterReuter commented 8 years ago

When I'm booting the latest TWRP recovery image twrp-multirom-20151112-UNOFFICIAL-foster.img I don't get any network device, so eth0 isn't working at all.

Flashing was done with

fastboot flash recovery twrp-multirom-20151112-UNOFFICIAL-foster.img

The dmesg output was gathered with:

adb shell
dmesg > /tmp/dmesg.txt
adb pull /tmp/dmesg.txt .

Here is my dmesg output right after booting: dmesg-003.txt

DieterReuter commented 8 years ago

Boot infos from @ericvh: shield-boot.txt This may only be partially useful to you since i boot my own kernel (the config is in my github). [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.10.61-g621d7f5-dirty (erivan01@vTrogdor) (gcc version 4.9.2 (Ubuntu/Linaro 4.9.2-10ubuntu13) ) #5 SMP PREEMPT Fri Jun 19 11:37:49 CDT 2015 ... 7.784264] usb 3-3: new SuperSpeed USB device number 2 using tegra-xhci [ 7.805948] usb 3-3: New USB device found, idVendor=0bda, idProduct=8153 [ 7.812782] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [ 7.820037] usb 3-3: Product: USB 10/100/1000 LAN [ 7.824843] usb 3-3: Manufacturer: Realtek [ 7.828948] usb 3-3: SerialNumber: 000001000000 [ 8.293788] tegra-xhci tegra-xhci: xHCI xhci_drop_endpoint called with disabled ep ffffffc0a7f64740 [ 8.302961] tegra-xhci tegra-xhci: xHCI xhci_drop_endpoint called with disabled ep ffffffc0a7f64780 [ 8.312072] tegra-xhci tegra-xhci: xHCI xhci_drop_endpoint called with disabled ep ffffffc0a7f647c0 [ 8.357291] r8152 3-3:1.0 eth0: v2.03.3 (2015/01/29) [ 8.362399] r8152 3-3:1.0 eth0: This product is covered by one or more of the following patents: [ 8.362399] US6,570,884, US6,115,776, and US6,327,625. So, looks like same as you. You may need to have a cable actively plugged in for it to turn on the USB (just a guess really, but I seem to remember something stupid like this)..

Confirmed that its not a module thing (at least my kernel doesnt have any modules loaded, but I may have built everything in). I'm wondering if SElinux or something else is tripping you up.