Debian This forum is for the discussion of Debian Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
04-29-2004, 06:55 PM
|
#1
|
LQ Newbie
Registered: Dec 2003
Location: Portugal
Posts: 22
Rep:
|
After installing Sarge it lost the eth0
Hi,
I just install sarge from CD installer & ftp, every think was fine,
I install samba and SWAT, etc. but after a reboot
the system lost the nic (eth0) saying:
Code:
eth0: ERROR while getting interface flags: No such device
eth0: ERROR while getting interface flags: No such device
what is the problem?
I can't add the nic by hand (alias eth0=tulip;modprobe tulip, etc.)
Thank you.
spiri
|
|
|
04-29-2004, 06:56 PM
|
#2
|
Member
Registered: Sep 2003
Location: Suwon, Korea
Distribution: Slackware 14
Posts: 288
Rep:
|
have you tried
ifconfig eth0 up
|
|
|
04-29-2004, 10:19 PM
|
#3
|
Member
Registered: Nov 2003
Location: Ohio
Distribution: Debian Unstable
Posts: 460
Rep:
|
i think doing a debian upgrade will overwrite your /etc/modules file. this is where your network card driver is specified. you need to find out the name of the driver and add it to that file. do a search on google for "<card name> linux driver". once you find the driver name, add that as a line in /etc/modules
edit: you can type 'lspci' to list the hardware connected to the pci bus to get the name of your network card, but that won't tell you the driver name. you'll still need to search google for that.
once you find the driver name, you can type 'modprobe <driver name>' to load the driver module into the kernel without needing to restart the system. putting the driver name into the modules file just lets the kernel know that you want to load that particular driver every time the system boots.
Last edited by zero79; 04-29-2004 at 11:02 PM.
|
|
|
04-30-2004, 04:05 AM
|
#4
|
LQ Newbie
Registered: Dec 2003
Location: Portugal
Posts: 22
Original Poster
Rep:
|
Quote:
Originally posted by czarherr
have you tried
ifconfig eth0 up
|
It only gives the looback interface.
|
|
|
04-30-2004, 04:08 AM
|
#5
|
LQ Newbie
Registered: Dec 2003
Location: Portugal
Posts: 22
Original Poster
Rep:
|
Quote:
Originally posted by zero79
i think doing a debian upgrade will overwrite your /etc/modules file. this is where your network card driver is specified. you need to find out the name of the driver and add it to that file. do a search on google for "<card name> linux driver". once you find the driver name, add that as a line in /etc/modules
edit: you can type 'lspci' to list the hardware connected to the pci bus to get the name of your network card, but that won't tell you the driver name. you'll still need to search google for that.
once you find the driver name, you can type 'modprobe <driver name>' to load the driver module into the kernel without needing to restart the system. putting the driver name into the modules file just lets the kernel know that you want to load that particular driver every time the system boots.
|
Hi,
I didn't made an upgrade, It was a fresh install.
lspci says that is a en-1216 (driver tulip), but it is a USR7900 (driver tulip),
I load the driver (modprobe) but the sistem says that the device is not there.
|
|
|
04-30-2004, 05:14 AM
|
#6
|
Senior Member
Registered: Jan 2003
Location: Devon, UK
Distribution: Debian Etc/kernel 2.6.18-4K7
Posts: 2,380
Rep:
|
The Debian way is to use modconf (i.e. as root do modconf). If not installed apt-get install modconf. modconf will produce a text menu, go down to net cards and install the relevant driver and then do /etc/init.d/networking restart. Then do ifconfig and check whether the interface is up.
|
|
|
04-30-2004, 01:23 PM
|
#7
|
Senior Member
Registered: Mar 2004
Location: far enough
Distribution: OS X 10.6.7
Posts: 1,690
Rep:
|
just compile the kernel with proper support
|
|
|
05-01-2004, 06:03 AM
|
#8
|
LQ Newbie
Registered: Dec 2003
Location: Portugal
Posts: 22
Original Poster
Rep:
|
Quote:
Originally posted by mrcheeks
just compile the kernel with proper support
|
I install debian again in another machine. It worked fine... until I reboot.
The problem is the same eth0:no such device.
I did the same instalation as in my other machine that is working fine.
Try to set up the network by hand but it doesn't accept the module : no such device!
Do you think that this should happen?
Regards.
|
|
|
05-01-2004, 09:45 AM
|
#9
|
Member
Registered: Nov 2003
Location: Ohio
Distribution: Debian Unstable
Posts: 460
Rep:
|
perhaps tulip is the wrong driver module. have you done a google search for your card to make sure?
i guess you could do a fresh install, type "lsmod" to see which driver is running to give you network support before rebooting, then add that to "/etc/modules"
Last edited by zero79; 05-01-2004 at 09:46 AM.
|
|
|
All times are GMT -5. The time now is 12:35 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|