> It is preferable to just include the whole dmesg directly in the mail > Better still, when it's a "sometimes works" problem, include a "diff -u" > between the two (the context to show where the lines are added/removed).
I have pasted a "diff -u" on https://paste.debian.net/1047098/ > Very unlikely to be a problem with the NIC driver. From what I've > seen (and having seen other examples of the quality of Jetway's BIOSes) > my money would be on a BIOS bug. I originally suspected it to be a BIOS bug (and please excuse me if I make a wrong assumption here), but I have run a ton of tests booting the same hardware up on Arch Linux, but I haven't seen the problem once. I don't know if could still be a BIOS bug, but I would suspect that if it where that I would see similar problems with the card not showing up. > Can you identify any particular situations where it works or fails? For > example "works after a cold boot but not warm" or something? I have been looking for patterns in the different tests I have run, but haven't found anything. Sometimes it works during a cold boot, other times it doesn't, and the same goes for warm boots. I have also tried disabling and enabling the onboard NIC to see if it might affect the problem, but it doesn't. Just for information, I have another identical box (same motherboard), but with a 4-port Intel NIC (same cheap card-thing from China, but with Intel) that runs flawless, but not only that, it performs super well even with several NIC ports going full speed. It has been running for a couple of years as a firewall/gateway, managing multiple networks (each separated by the 4-port NIC). I have made these as cheap alternatives to the very expensive Soekris. By mistake I got two of the 4-port Realtek cards, but since I got them, I wanted to see if they could run as well. Kindest regards. PS.: Sorry for the crappy Yandex mail client problem.
