X and Fluxbox :: Nforce2 wierdness

Okay, I have noticed something strange.

Since the 0.8.x tree started (continues to current), on every Nforce2 mobo I have had my hands on has had this problem.

If you have a cable plugged into the integrated NIC (forcedeth module) on the mobo, neither Xvesa nor XFree86's vesa module will work, but if you unplug the cable from the NIC, or use another NIC, Xvesa/vesa works normally.

It did NOT do this in pre-0.8.x DSL.

I have no idea why this happens, but it happens on every nforce mobo I've used, no matter the video card being used. ATI, nvidia, or whatever.

The boards I've had this problem on are...

MSI K7N2-Delta-L
ASUS A7N8X-E
ECS NF2400-U
Shuttle SN41G

-J.P.

Hmm, maybe that explains why I can only get FB and nvidia-accelerated Xfree to work on my machine since about v0.8? Used to run vesa fine...

If I get around to it, I'll try experimenting today.
(nvidia albatron fx5200 on an nforce2 albatron mobo - always assumed it was a video card thing...)

Yep, just tested it, Albatron KX18D ProII, runs vesa when the network cable's unplugged, doesn't when it's plugged in.
Interesting. Before 0.8 there was no inbuilt support for nforce2 nic's, now there's support, but the xserver gets screwed up. Oh well, at least now we have networks, and can get X with FB. I usually swap to XFree86 on my machine, anyway. Just a curiosity...

so, do we know if there are any upcoming fixes for this problem. There must be enough of us (people with nforce boards) to make it worth while right?

original here.