Hi, > It's hard to tell without data. It could be any of the usual suspects > or a genuine bug.
Yeah, I realise that. I've tried booting windows which behaves exactly the same, with the latest realtek driver. I've sent back the machine today because I need to have this box up fairly soon. Sorry :/ > Can you send the complete dmesg from boot + lspci -vvx + /proc/interrupts > of the computer ? I don't have a dmesg any more, lspci is at http://johannes.sipsolutions.net/files/lspci-minipc, /proc/interrupts looked normal as far as I can remember. dmesg didn't say much about r8169, and other than that I didn't see any problems. I tried booting with pci=routeirq and some options but none of that helped, and interrupts were definitely counted in all cases. > What does ethtool report if you do not force it to 10Mbps with the media=1 > option and what hardware is it connected to ? Any URL for the motherboard ? Here's the weirdest thing: If I connected it to 100mbit/full duplex hardware, it worked only if I forced it to 10mbit (half or full), otherwise the tx/rx led would blink frantically and the card didn't receive any packets (sending was fine). If I connected it to gbit hardware it worked in gibt mode, but only got transfer speeds of about 10mb/sec. Same behaviour with windows. johannes
signature.asc
Description: This is a digitally signed message part
