Had networking, then USB ports stopped working

2 posts / 0 new
Last post
Had networking, then USB ports stopped working

I purchased and installed a new DVRupgrade hard drive with networking at the end of December.  I had full network access working.  I made a BIG mistake in not learning to backup my system while it was working well and stable.

I ran the rbautch Enhancements script and now my USB ports are totally inactive.  When I boot, the power and link LEDs on my USB to Ethernet adapter blink once a few seconds after the Powering up screen changes to the DVR Upgrade screen.

I've searched the forums for two weeks, but nothing I've found to date has helped.  I know enough to use a serial cable and Hyperterm to capture the boot and kernel logs.  I've examined them both and found few differences.  However, one difference seems to be related to my problem.  I've extracted those areas and pasted them below.  These are from the same bootup.  I removed the timestamps in the kernel log to make it easier to read.

Boot Log

Found hpk front panel model 1
PCI: 00:0d.2 PCI cache line size set incorrectly (0 bytes) by BIOS/FW, correcting to 32
PokeFirewallPort: Poking hole through firewall at port 2190, protocol udp
PokeFirewallPort: Poking hole through firewall at port 2190, protocol tcp

 

Kernel Log

Found hpk front panel model 1
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb.c: starting integrated EHCI driver
ehci_hcd 00:0d.2: PCI device 1033:00e0
ehci_hcd 00:0d.2: irq 6, pci mem b4002000
usb.c: new USB bus registered, assigned bus number 1
PCI: 00:0d.2 PCI cache line size set incorrectly (0 bytes) by BIOS/FW, correcting to 32
ehci_hcd 00:0d.2: USB 2.0 enabled, EHCI 0.95, driver 2003-Dec-29/2.4
hub.c: USB hub found
hub.c: 5 ports detected
usb.c: EHCI initialization succeeded
hub.c: new USB device 00:0d.2-1, assigned address 2
usb.c: USB device 2 (vend/prod 0xb95/0x7720) is not claimed by any active driver.
PokeFirewallPort: Poking hole through firewall at port 2190, protocol udp
PokeFirewallPort: Poking hole through firewall at port 2190, protocol tcp

Thank you for any hints or pointers that anyone can provide. 

I have a similar problem. I

I have a similar problem. I bought in January the 500GB drive upgrade kit from DVRupgrade with the Trendnet TU2-ET100 network dongle, with PTVnet pre-loaded. It worked fine initially, but then I goofed on a patch upgrade.

 I loaded the bufferpatchv4.1 with changes to support my 6.3b version of code on Dtivo HR10-250. Unfortunately, I was running out of space on my partition, and the script renamed my valid tivoapp and failed to replace with the new patched version. Didn't notice until the reboot was already committed!

The system couldn't get past "Almost There" screen. I managed to fix this by removing drive and working on it with mfstools off an old PC. I simply renamed the tivoapp files back and reinstalled.

 Yet, once re-installed, the eth0 device while looking okay, doesn't work. Network is considered down by Tivo.

 This USED to work fine prior to my goof. I don't see why what I did broke this. I would love to get this fixed. The whole premise for my upgrade was more based on having the networking capabilities rather than the additional drive space. So right now I'm bumming!

Disappointed to see no-one has replied usefully to this thread, hopefully this new comment may spark some interest.

 Some output from the console during reboot:

usb.c: USB device 2 (vend/prod 0xb95/0x7720) is not claimed by any active driver.
ehci-dummy: dummy EHCI module loaded
ApgLogFrequency( 0 sec )
unlinking :87162da0
packet write: Network is down

... 

"Call in" status updated.
rc.sysinit is complete
...

 connect failed, reason = Network is unreachable
Internal error #R