• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Can Suse break my Network port??

L

Lord Banshee

Golden Member
I install Suse this morning and i had a nvidia driver problem (the screen would artifact when X loaded). So i booted back into windows and now it seems my network can not grab a connection it would connect/disconnect over and over again..

So i booted in safe mode reload windows ethernet drivers.... same problem.

Removed Suse, install ubuntu and now ubuntu says i have issues with my DHCP or my network device isn't working right..

What the crap did Suse do 🙁
 
I hate nForce networking.. its likely a software issue caused by a poorly written driver, either NVidia's or the reverse engineered one, not sure which one Suse uses... try reseting your bios and/or reflashing it. Not much else you can do I think... my onboard on this DVD266u-RN is flaky in windows, so I have to pray that the planets align during bootup or I have to do a very long process lol, luckily I use my wireless or a pci card most days.
 
I guess it's possible if the NIC would accept instructions that could cause it harm or something, but that's extremely unlikely.
 
I don't know. My Marvell Ethernet controller has been dead in Windows and sporadic in Linux for some time now.
 
one of the first things i did when i upgraded to an nforce 4 motherboard was buy a nic. the onboard was sporadic when i was lucky. haven't had a problem since.
 
Well i reset bios no luck.. Turned on my Marvell to use it (so i can have internet) and works fine... GRRR!!! Suse is on my bad side for life.

BTW i never had any problems with my Nvidia Ethernet till now...
 
if an OS can break your H/W, then your H/W has major issues....

I dont' think this was the fault of Suse, I think it was a coincidence.
 
I know mine is a hardware/software issue(Been there every revision since board was a prototype) 🙂, not sure about nForce but it seems to have the same problems I do with mine...
 
I've had nic cards that would get wonky through hardware bugs. Sometimes different operating systems initialize stuff or do things slightly different..

It's VERY common for manufacturers to ship broken hardware and use driver work arounds to fix it. It's a lot easier to modify software then it is harware. It's very possible that Suse does something different enough to trigger a bug in the hardware that Windows doesn't do.

What you need to do is shut the computer off completely. Unplug it and then try to turn it back on. The goal here is is to completely deplete the capacitors of all electricity. Even when the system is shut off you have a power going through the motherboard. It's part of the ATX spec, I beleive. So you can do things like 'wake on lan' and allow the motherboard to switch on and off the power supply.

The fans should kick in a bit until all the charge is gone from the motherboard and powersupply. Let it sit like that for up to 30 seconds. This should get the hardare transistors and such to fully reset.

Then after that hopefully your ethernet port should work.

Blame it on a wonky motherboard. This has happenned to me before.
 
if an OS can break your H/W, then your H/W has major issues....
Click to expand...

Yes, but there is a lot of crap hardware out there today. For instance, if I soft reboot my home machine my IDE drive will give CRC errors but if I power it completely down it'll read just fine on the next bootup. I don't know if it does the same thing in Windows though since I don't have Windows on that machine.
 
Originally posted by: xtknight
I don't know. My Marvell Ethernet controller has been dead in Windows and sporadic in Linux for some time now.
Click to expand...

What driver? I know that the Marvell controller in my machine is PCI-e and thus run by the sky2 driver, which is in 2.6.16 but has serious interrupt problems possibly related to MSI (even though I still tried 2.6.16 with MSI not compiled in, but it still had the same problem). I'm running .17-rc1on the machine, and it's actually rather stable.

Never mind; wrong kernel. [changes menu.lst]
 
Originally posted by: drag
What you need to do is shut the computer off completely. Unplug it and then try to turn it back on. The goal here is is to completely deplete the capacitors of all electricity. Even when the system is shut off you have a power going through the motherboard. It's part of the ATX spec, I beleive. So you can do things like 'wake on lan' and allow the motherboard to switch on and off the power supply.

The fans should kick in a bit until all the charge is gone from the motherboard and powersupply. Let it sit like that for up to 30 seconds. This should get the hardare transistors and such to fully reset.
Click to expand...

I've had problems with a dual boot setup where my nic would work in Linux but if I rebooted into windows it would not connect. A bios update seemed to fix that.

but powering down like described, usually got it working again
also if you have a router you might want to have a look at you routing tables I had problem with those sometimes dual booting.
 
I had the same problem on my DFI Ultra-D board as well. The problem ended up being the Windows drivers for the Marvell LAN (as weird as it sounds). If you installed the drivers of the of the DFI CD, go to the DFI website and get the latest drivers for the Marvell NIC. I know this sounds incredibly weird (SUSE messing up Windows networking because of a bad driver), but that is apparently what happens, and the newer driver luckly fixes that.
 
Linux fried my 3Com 3CR-990TX-97 during setup, trying to cram a 3C905C-TXM driver down its throat for some reason. Afterwards, it didn't work, regardless of OS. So it's empirically proven to be possible 😀
 
Linux fried my 3Com 3CR-990TX-97 during setup, trying to cram a 3C905C-TXM driver down its throat for some reason. Afterwards, it didn't work, regardless of OS. So it's empirically proven to be possible
Click to expand...

I really doubt the hardware was physically fried, most likely the card's firmware just got really confused by the wrong driver and couldn't recover.
 
Originally posted by: bersl2
Originally posted by: xtknight
I don't know. My Marvell Ethernet controller has been dead in Windows and sporadic in Linux for some time now.
Click to expand...

What driver? I know that the Marvell controller in my machine is PCI-e and thus run by the sky2 driver, which is in 2.6.16 but has serious interrupt problems possibly related to MSI (even though I still tried 2.6.16 with MSI not compiled in, but it still had the same problem). I'm running .17-rc1on the machine, and it's actually rather stable.

Never mind; wrong kernel. [changes menu.lst]
Click to expand...

It's an integrated Marvell Yukon Ethernet controller on my A8N-SLI Deluxe motherboard. I'm really not sure if Linux had anything to do with its death but I've disabled it in the BIOS for now and I'm just using the CK804 (nForce 4) controller. Not sure what driver the Yukon used. The BIOS has those things for checking CAT5 cable reliability and whatever, well for the Yukon those tests just completely fail so I know something's wrong with it.
 
Originally posted by: nweaver
if an OS can break your H/W, then your H/W has major issues....

I dont' think this was the fault of Suse, I think it was a coincidence.
Click to expand...

From the OpenBSD emu man page

CAVEATS
ATTENTION!

The hardware interface of this card contains registers not used for nor-
mal operation, but potentially dangerous and not possible to disable.
Potential damage ranges from frying the card to frying motherboard or ex-
ternal equipment connected to its outputs.
Click to expand...
 
I've had a dual nic nForce4 board with SuSe i think 9.3 installed, and the nVidia nic suddenly stopped working altogether. But the other nic still worked (I think it was a Broadcom). Probably more coincidence than anything else.
 
Originally posted by: cubby1223
I've had a dual nic nForce4 board with SuSe i think 9.3 installed, and the nVidia nic suddenly stopped working altogether. But the other nic still worked (I think it was a Broadcom). Probably more coincidence than anything else.
Click to expand...

My Nforce and Nforce2 NICs survived several years of Linux, but my Nforce3 Gbit NIC died after ~4months. Maybe there is something wonky here...
 
I have a DFI lanparty UT ultra-D and my onboard marvell has been dead ever since I can remember in both windows and linux. My other nvidia nic only seems to die when I dual boot with linux (killing in both linux and windows) and the only way to get it working is to nuke it all and reformat.
 
Originally posted by: xtknight
bersl2: My Yukon was using the sk98lin driver, I'm pretty sure.
Click to expand...

My onboard Marvell Yukon lan does the same thing to me when dual boot. I fixed it by using downloading the updated driver from marvell's site (also in windows update) and installing it in windows. You will need another connection if using windows, or just download it in linux to an accessible drive.

Only problem is, that we probably have 2 different cards. Mine is onboard my Asus P4P800-E Deluxe.

I use the skge driver in Linux.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top