lost eth0 when MEPIS was apt-get updated/upgraded

[keywi]

Help, I am trying MEPIS and installed it to the hard drive.
Apt-get updated/upgraded
Rebooted, that is when i lost eth0.
Also, I couldn't get the sound to work.

William

Oh yea, lspci shows the bcm5702x ethernet card.
I don't know what module to insert also.

[mrBen]

Have you tried bringing eth0 up? ifup eth0

[keywi]

ifup eth0 : No such device.
all i want to do is get my eth0 going to then try to work on my sound. I am curious to what happened. Maybe like in Slackware when you swaret --upgrade. it will knock out the sound.
Is this the same incident?

Thx,

William

[XiaoKJ]

it should not be the case.

give us the output of ifconfig -a

and can you please give more info? can you tell us, at least, the card you have?

also, the output of uname -a

These will give us more infomation

[mrBen]

There are drivers on the broadcom site at http://www.broadcom.com/drivers/downloaddrivers.php for your device, although you could also try the tg3 drivers, which appear frequently against this device in google, although with mixed reports.

You can add devices to /etc/modules for the modules to be loaded at boottime.

What type of soundcard is it?

[keywi]

ifconfig -a just gives "lo" and "sito", which i don't know what that is, anyway, the nic was working before i updated/upgraded.
uname -a just gives "Linux william_mepis 2.6.7 #1 [date] i686 GNU/Linux".
The sound is onboard MSI CM8738.

I might just consider going back to slackware. :D

I will give it a few more weeks.

Thx,

William

[mrBen]

Did you try loading the modules listed above?

[thedreampolice]

Have you tried re-running the MEPIS network config tools?

[keywi]

I tried MEPIS net tools. but it will not let me start or stop the device.

[DarkDexter]

I'm getting a similar error. My solution is to change the static IP and it will go on, but next time i boot it does it again with the new ip too. Everytime i boot and want to connect to the network i have to open up the OS control center in mepis and change the IP (only the last digits 192.168.0.103 -> 192.168.104 or whatever). The point is the eth0 never loads on boot. This happens on all my computers so it isnt hardware, i think it is a bug in Mepis. Anyways, thats all i know how to get it running, but that is far from a permant fix.

[timothykaine]

Something that was just added to the Debian unstable repository is screwing it up. It did it to me too this week on MEPIS, Knoppix, AND Kanotix.

I just installed a fresh copy of Kanotix and havent run a full upgrade yet, so Im going to do it piece by piece and see what triggers it, then I can compare the difference and see if I can fix it.

[infiniphunk]

I had a similar thing happen with apt-get dist-upgrade, at some point it was setting up the new packages and for some reason it set my sound driver to OSS and told me there was an issue with the sound card. I simply reset xmms to use ALSA and it was fixed. Can it be that the update also affected eth0 for you also? I'd double check in OSCENTER and see what it says in there. sito?

[timothykaine]

Running alsaconf as root took care of the sound issue. It still happens in apt upgrades when using unstable repositories.

The repositories seem to have been updated to fix the lost eth0 problem, as upgrading doesnt cause this anymore.

[keywi]

when i run alsamixer

"function snd_ctl_open failed for defaults: No such device"

I ran the alsaconf and it found the sound card but I still don't have sound since I update/upgraded.

William