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.
|
 |
12-22-2003, 12:00 PM
|
#1
|
Member
Registered: Nov 2003
Location: Slough, UK
Distribution: Debian
Posts: 146
Rep:
|
No eth ????
I have just installed Debian. Never before used it. Only to find that there is no network device files. i.e eth0.
Do ethernet devices go by another name in Debian or is something wrong?
|
|
|
12-22-2003, 12:34 PM
|
#2
|
Member
Registered: Nov 2003
Distribution: Debian & Ubuntu
Posts: 402
Rep:
|
They go by the ethX naming. Did you configure the network during install, or install straight from cd? If the latter, edit the file /etc/network/interfaces then bring the device up with ifup (or dhclient). Is the card detected by lspci -v?
|
|
|
12-22-2003, 06:00 PM
|
#3
|
Member
Registered: Nov 2003
Location: Slough, UK
Distribution: Debian
Posts: 146
Original Poster
Rep:
|
I have done the following: - Run lspci -v: It said the following.
Code:
00:13.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 10/100 Ethernet (rev 02)
Subsytem: Silicon Integrated Systems [SiS] SiS900 10/100 Ethernet Adapter
Flags: bus master, medium devsel, latency 64, IRQ 12
I/O ports at e400 [size=256]
Memory ay e8000000 (32 bit, non-prefetchable) [size=4k]
Expansion ROM at e7000000 [disabled] [size=128k]
Capabilities: [40] Power MAnagement version 2
I'll assume that means that it can see it.
- I checked the /dev/ directory. It contains no ethXX device files.
- I edited the interfaces file to the following:
Code:
auto lo, eth0
iface lo inet loopback
iface eth0 inet dhcp
For obvious resons it did not work, as there is no device file called eth0.
I did install straight from the CD. I do not understand why installing the server distro of debian, network support isn't included by default.
|
|
|
12-23-2003, 01:27 AM
|
#4
|
Senior Member
Registered: Mar 2003
Location: Nova Scotia, Canada
Distribution: Debian AMD64
Posts: 4,170
|
Quote:
Originally posted by codedv
I have done the following:- Run lspci -v: It said the following.
Code:
00:13.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 10/100 Ethernet (rev 02)
Subsytem: Silicon Integrated Systems [SiS] SiS900 10/100 Ethernet Adapter
Flags: bus master, medium devsel, latency 64, IRQ 12
I/O ports at e400 [size=256]
Memory ay e8000000 (32 bit, non-prefetchable) [size=4k]
Expansion ROM at e7000000 [disabled] [size=128k]
Capabilities: [40] Power MAnagement version 2
I'll assume that means that it can see it.
- I checked the /dev/ directory. It contains no ethXX device files.
- I edited the interfaces file to the following:
Code:
auto lo, eth0
iface lo inet loopback
iface eth0 inet dhcp
For obvious resons it did not work, as there is no device file called eth0.
I did install straight from the CD. I do not understand why installing the server distro of debian, network support isn't included by default.
|
Networking support is included by default you are however expected to configure the system to load the proper modules if it is not already built into the kernel. Try this as root in a console or console window modprobe sis900 if the module loads correctly then /etc/init.d/networking restart this will restart the networking and now that the module was loaded it should be able to get the DHCP lease from whatever server you have that gives you your IP. You may want to check in your /etc/resolv.conf and make sure that you have at least one nameserver in there or you will not be able to resolve internet addresses. To make the change permanent edit the file /etc/modules as root and put the sis900 module name on a line by itself and it will be loaded at boot. BTW what does uname -a say you are running for a kernel if this does not work.
|
|
|
12-23-2003, 08:18 AM
|
#5
|
Member
Registered: Nov 2003
Location: Slough, UK
Distribution: Debian
Posts: 146
Original Poster
Rep:
|
On using modprobe it said it was unable to locate the module. I'm assuming this means I need to obtain the source for the Sis900 driver and compile it into the kernel?
|
|
|
12-23-2003, 02:15 PM
|
#6
|
Senior Member
Registered: Mar 2003
Location: Nova Scotia, Canada
Distribution: Debian AMD64
Posts: 4,170
|
Quote:
Originally posted by codedv
On using modprobe it said it was unable to locate the module. I'm assuming this means I need to obtain the source for the Sis900 driver and compile it into the kernel?
|
Yes if it is available for the 2.2 kernel that you must be running in my firewall's old kernel config which was using the 2.4.18-bf2.4 kernel which would have been installed if you used that option the module is compiled into the kernel so you should be able to use your network card if you are running that kernel so what does uname -a in a console window tell you?
Code:
stephen@SleepyTux:~$ grep SIS /boot/config-2.4.18-bf2.4
CONFIG_BLK_DEV_SIS5513=y
CONFIG_SIS900=y
CONFIG_TMSISA=m
CONFIG_AGP_SIS=y
You should be able to install a 2.4.18 kernel from the CD(s) that you have and get the required support for the card.
|
|
|
12-24-2003, 04:59 AM
|
#7
|
Member
Registered: Nov 2003
Location: Slough, UK
Distribution: Debian
Posts: 146
Original Poster
Rep:
|
Thanks for the all the help. I have compiled the latest kernel 2.4.23 and made sure I included the SiS900 support. After a bit of tweaking I have got it working - for the moment though I have had to set the interfaces file up as follows:
Code:
auto lo eth0 eth0:1
iface lo inet loopback
iface eth0 inet static
netmask 255.255.255.0
address 192.168.0.2
iface eth0:1 inet static
netmask 255.255.255.0
address 192.168.0.20
Unfortunatly using the dhcp option causes them not to work - the dhcp server does not give them ip addresses.
Again, thanks for all the help. Debian is very different from RedHat :s so I might need some more guidance.
|
|
|
All times are GMT -5. The time now is 09:51 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
|
|