Will Dyson wrote:
Neo is just something MSI has been using for a while to make their product names "interesting" and "futuristic" and <add market babble here>.
In any case, I'll be testing 2.6.10 and I'll see what happens. It's very
likely I just have a faulty mb as well.
Do you always get that "Kernel BUG at r8169.c:713" and similar stack
trace? I'd be surprised if a faulty component resulted in a
reproducable error.
In fact not. This is the latest, now with 2.6.10 kernel running: http://vekotin.org/shared/yue_panic2.jpg
I'm getting the distinct feeling that the mobo is just broken. Let's just hope they'll offer a change to Abit...
/v\
