The other thing the problem devices have in common is that their "LAN LED" flickers at 1 - 2 times a second - the working device may "occasionally" turn off and back on briefly.ġ) Has anyone else come across this or a similar problem?Ģ) I think there are other devices that use a different chipset/driver - any suggestions?ģ) Has anyone purchased a recent version of the Pluscom U1EC device and found it to work?Ĥ) Given that the Pi gets "locked" by the bug are there any logs or similar I could check on w/o triggering the bug? (ie. Since the "Oops" locks up the Pi (model A or B2) I can only attach low-res "physical" screenshots, but I hope there's some useful info. Problem devices - variants of JP108 : 030818 (all physically different in board layout & some chips), lsusb reports ID 0fe6:9700 Kontron (Industrial Computer Source / ICS Advent) DM9601 Fast Ethernet Adapter in all but one case where its ID 0fe6:8101. Working device - Pluscom U1EC, lsusb reports ID 0a46:9000 Davicom Semiconductor, Inc.
I've now tried six devices in total and only one of them (the oldest) does not generate/trigger the Kernel BUG. Didn't get around to trying them with a "B2 512Mb" Pi but next tried with a Model A - this is when the issues first "came to light" and were noted in this thread. Fast-forward to last autumn when I acquired my first Pi (B1 256Mb) - tried them out briefly - seemed to be working - could ping or login via ssh etc. Background: Some years ago I acquired a couple of USB LAN dongles to give my netbook an additional ethernet port to enable direct connection to a NSLU2 box onto which I was about to install Debian (Lenny IIRC) - during its "redboot" sequence it operated on a different sub-net to that of the household.
0 kommentar(er)
