Interesting.... This is a prebuilt machine, MD8800 from Medion, the motherboard has never been in other machines. I don't suppose you tried 2.4 kernels on it? Mine works fine with 2.4 kernels, but that is not exactly modern anymore. It is of course possible that Medion (or whomever assembles their machines) could have had a problem of the type you mention, especially if Windows doesn't care... But in that case, if everything is fine in Windows, couldn't Linux be told not to care as well? When I used the usbhub patch, the load settled and the machine seemed fine, but I lost my wireless adapter which apparently is on the affected hub. There is also a card-reader in this machine that has never worked in Linux, not with 2.4 either, yet the inf file in windows says it is a USB device. Sounds like a very weirdly implemented one... Incidentally I managed a quick test of 2.5.37 before I left for my parents'. Apparently is doesn't like having usbdevfs enabled, so I'll try again with that disabled when I get the chance... I have basically make the simplest kernel I could think of: All standard values, except: * No loadable module support * Ext3 support compiled in * USB UHCI and EHCI controllers compiled in * usbdevfs selected (apparently not a good idea) * Drivers for most USB types compiled in (audio, serial, storage, HID, etc...) - although not scanners and digitizers I got an oops with this kernel that seemed to imply that usbdevfs couldn't create the nodes it wanted. I have no initrd assigned. I started it from grub with 'kernel /boot/linux-2.5.37 root=/dev/sdb3 vga=normal single init=/bin/sh' /Martin. ----- "Thomas Meindl" <twm.mst@gmail.com> wrote:
Martin Møller schrieb:
Just to mention it, I had something similar half a year ago. I had built an old MSI motherboard (nForce2 based) into a new tower case and got exactly the same messages about the bad USB cable. I investigated and found out, that pin 10 of the USB2 motherboard connector (called 'USBOC' by MSI, called 'NC' on modern boards) caused the problem, because in the old case there was nothing connected to pin 10, in the new one it was - as far as I remember - connected to GND. I isolated the single pin by pulling out the connector on the cable's connector (by lifting the very tiny plastic clasp that holds back the single pin connector and carefully (!!! ) pulling it out) and all went smooth in Linux again. So it was a hardware problem to me and not the kernels fault, kind regards, Tom
-- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org