Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game. |
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.
|
 |
09-12-2005, 08:11 AM
|
#1
|
Member
Registered: Apr 2005
Location: São Paulo - Brazil
Distribution: Mageia Linux 1
Posts: 353
Rep:
|
Internet (eth0 interface) does not auto-start
Hello,
I am running Mandriva 2005 LE and my network does not auto-start with the computer.
I have tryed hundreds of times to check and uncheck "start network on boot" on Mandrake Control Center. I also have already reconfigured my internet duzens of times to no vail. I also googled without sucess.
Now the wierd thing: On boot time I can see the message: "bringing up eth0 interface ..... [OK]"
So I imagine, eth0 should be up, right?
Here is my ifconfig after boot:
Code:
[root@Lapa felipe]# ifconfig
lo Encapsulamento do Link: Loopback Local
inet end.: 127.0.0.1 Masc:255.0.0.0
endereço inet6: ::1/128 Escopo:Máquina
UP LOOPBACKRUNNING MTU:16436 Métrica:1
RX packets:23 errors:0 dropped:0 overruns:0 frame:0
TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
colisões:0 txqueuelen:0
RX bytes:1562 (1.5 Kb) TX bytes:1562 (1.5 Kb)
sit0 Encapsulamento do Link: IPv6 sobre IPv4
endereço inet6: ::127.0.0.1/96 Escopo:Desconhecido
UP RUNNING NOARP MTU:1480 Métrica:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
colisões:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
As you can see eth0 is not functioning after boot. Going to mandrake control center and reconfigure my internet will bring eth0 up, but just until reboot.
So, what command should I use on the command line to get eth0 up?
Is there a proper init file to put it?
Any other suggestions?
My internet is Cable with non-real fixed IP. The configuration is right cos it works once Mandrake Control Center brings eth0 up.
my eth0 after my internet is working:
Code:
eth0 Encapsulamento do Link: Ethernet Endereço de HW 00:08:54:22:B9:1B
inet end.: 172.26.0.21 Bcast:172.26.0.255 Masc:255.255.255.0
endereço inet6: fe80::208:54ff:fe22:b91b/64 Escopo:Link
UP BROADCASTRUNNING MULTICAST MTU:1500 Métrica:1
RX packets:919 errors:0 dropped:0 overruns:0 frame:0
TX packets:528 errors:0 dropped:0 overruns:0 carrier:0
colisões:0 txqueuelen:1000
RX bytes:378589 (369.7 Kb) TX bytes:88943 (86.8 Kb)
IRQ:21 Endereço de E/S:0xc000
thanks a lot,
|
|
|
09-13-2005, 05:01 AM
|
#2
|
Member
Registered: Mar 2005
Location: Finland
Distribution: FreeBSD 9.0
Posts: 59
Rep:
|
What does
ifconfig eth0 up
say?
|
|
|
09-13-2005, 07:41 AM
|
#3
|
Member
Registered: Apr 2005
Location: São Paulo - Brazil
Distribution: Mageia Linux 1
Posts: 353
Original Poster
Rep:
|
Quote:
Originally posted by Fin7PL
What does
ifconfig eth0 up say?
|
eth0: Unknown interface: No such Device
If I go to Mandrake Control Center and go up to half the internet assistent I get eth0 up.
|
|
|
09-13-2005, 08:45 AM
|
#4
|
Member
Registered: Mar 2005
Location: Finland
Distribution: FreeBSD 9.0
Posts: 59
Rep:
|
What about command
lsmod
output?
Before and after the eth0 comes up
|
|
|
09-13-2005, 09:19 AM
|
#5
|
Member
Registered: Apr 2005
Location: São Paulo - Brazil
Distribution: Mageia Linux 1
Posts: 353
Original Poster
Rep:
|
The difference between before eth0 is up and after is:
8139too 22624 0
ummm ... maybe I should bring this module up on one of the init.rd scripts?
Here is before eth0:
Code:
[root@Lapa felipe]# lsmod
Module Size Used by
i915 17600 1
drm 59796 2 i915
raw 7008 4
md5 3872 1
ipv6 243392 14
rfcomm 34936 0
l2cap 22784 5 rfcomm
bluetooth 43620 4 rfcomm,l2cap
snd-seq-dummy 2820 0
snd-seq-oss 32704 0
snd-seq-midi-event 6656 1 snd-seq-oss
snd-seq 50992 5 snd-seq-dummy,snd-seq-oss,snd-seq-midi-event
snd-seq-device 7052 3 snd-seq-dummy,snd-seq-oss,snd-seq
snd-pcm-oss 49760 0
snd-mixer-oss 17536 1 snd-pcm-oss
snd-hda-intel 12832 3
snd-hda-codec 50752 1 snd-hda-intel
snd-pcm 84100 4 snd-pcm-oss,snd-hda-intel,snd-hda-codec
snd-timer 21540 3 snd-seq,snd-pcm
snd-page-alloc 7812 2 snd-hda-intel,snd-pcm
snd 48900 13 snd-seq-oss,snd-seq,snd-seq-device,snd-pcm-oss,
snd-mixer-oss,snd-hda-intel,snd-hda-codec,snd-pcm,snd-timer
soundcore 7584 1 snd
parport_pc 32324 1
lp 10152 0
parport 32680 2 parport_pc,lp
af_packet 17256 0
floppy 55664 0
video 14148 0
thermal 10856 0
tc1100-wmi 5412 0
processor 14524 1 thermal
fan 3332 0
container 3264 0
button 5104 0
battery 7684 0
ac 3524 0
ide-cd 37156 0
loop 14344 0
nls_iso8859-1 3968 1
ntfs 207448 1
supermount 33360 1
intel-agp 20284 1
agpgart 28716 3 drm,intel-agp
usblp 11136 0
ehci-hcd 29544 0
uhci-hcd 29776 0
usbcore 108440 4 usblp,ehci-hcd,uhci-hcd
ext3 125480 2
jbd 52984 1 ext3
sd_mod 16032 5
ata_piix 7332 4
libata 41828 1 ata_piix
scsi_mod 116808 2 sd_mod,libata
and now after:
Code:
[root@Lapa felipe]# lsmod
Module Size Used by
8139too 22624 0
mii 4448 1 8139too
i915 17600 1
drm 59796 2 i915
raw 7008 4
md5 3872 1
ipv6 243392 14
rfcomm 34936 0
l2cap 22784 5 rfcomm
bluetooth 43620 4 rfcomm,l2cap
snd-seq-dummy 2820 0
snd-seq-oss 32704 0
snd-seq-midi-event 6656 1 snd-seq-oss
snd-seq 50992 5 snd-seq-dummy,snd-seq-oss,snd-seq-midi-event
snd-seq-device 7052 3 snd-seq-dummy,snd-seq-oss,snd-seq
snd-pcm-oss 49760 0
snd-mixer-oss 17536 1 snd-pcm-oss
snd-hda-intel 12832 3
snd-hda-codec 50752 1 snd-hda-intel
snd-pcm 84100 4 snd-pcm-oss,snd-hda-intel,snd-hda-codec
snd-timer 21540 3 snd-seq,snd-pcm
snd-page-alloc 7812 2 snd-hda-intel,snd-pcm
snd 48900 13 snd-seq-oss,snd-seq,snd-seq-device,snd-pcm-oss,
snd-mixer-oss,snd-hda-intel,snd-hda-codec,snd-pcm,snd-timer
soundcore 7584 1 snd
parport_pc 32324 1
lp 10152 0
parport 32680 2 parport_pc,lp
af_packet 17256 0
floppy 55664 0
video 14148 0
thermal 10856 0
tc1100-wmi 5412 0
processor 14524 1 thermal
fan 3332 0
container 3264 0
button 5104 0
battery 7684 0
ac 3524 0
ide-cd 37156 0
loop 14344 0
nls_iso8859-1 3968 1
ntfs 207448 1
supermount 33360 1
intel-agp 20284 1
agpgart 28716 3 drm,intel-agp
usblp 11136 0
ehci-hcd 29544 0
uhci-hcd 29776 0
usbcore 108440 4 usblp,ehci-hcd,uhci-hcd
ext3 125480 2
jbd 52984 1 ext3
sd_mod 16032 5
ata_piix 7332 4
libata 41828 1 ata_piix
scsi_mod 116808 2 sd_mod,libata
|
|
|
09-13-2005, 09:29 AM
|
#6
|
Member
Registered: Mar 2005
Location: Finland
Distribution: FreeBSD 9.0
Posts: 59
Rep:
|
Yes..
Try
insmod 8139too
and then
ifconfig eth0 up
I don´t know where to add the insmod 8139too in your distrib?
maybe someone other knows but that should work.
|
|
|
09-13-2005, 09:59 AM
|
#7
|
Member
Registered: Jul 2005
Distribution: Mint 14 64bit
Posts: 71
Rep:
|
Quote:
Yes..
Try
insmod 8139too
and then
ifconfig eth0 up
I don´t know where to add the insmod 8139too in your distrib?
maybe someone other knows but that should work.
|
If it works you could create a bash script like
Code:
#!/bin/bash
insmod 8239too
ifconfig eth0 up
make it executable and add it to the init.local in the init dir
I solved my problem with the wifi in this way.
|
|
|
09-13-2005, 10:10 AM
|
#8
|
Member
Registered: Apr 2005
Location: São Paulo - Brazil
Distribution: Mageia Linux 1
Posts: 353
Original Poster
Rep:
|
Actually it didn't work that easy. To start with insmod could not find 8139too, so I located it by hand, copied 8139too.ko.gz to the root documents folders, gunziped the file and tryed to load it.
[root@Lapa ~]# insmod 8139too.ko
insmod: error inserting '8139too.ko': -1 Unknown symbol in module
ummm ... perhaps I could look into Mandrake configuration scripts and see what it is doing to get the module up.
Here is the result of insmod before I copied the module file and gunziped it:
Code:
[root@Lapa dev]# insmod 8139too
insmod: can't read '8139too': No such file or directory
[root@Lapa ~]# ifconfig eth0 up
eth0: interface desconhecida: No such device
[root@Lapa dev]# locate 8139too
/sys/module/8139too
/sys/module/8139too/sections
/sys/module/8139too/sections/.strtab
/sys/module/8139too/sections/.symtab
/sys/module/8139too/sections/.bss
/sys/module/8139too/sections/.gnu.linkonce.this_module
/sys/module/8139too/sections/.data
/sys/module/8139too/sections/.altinstructions
/sys/module/8139too/sections/.rodata.str1.4
/sys/module/8139too/sections/__param
/sys/module/8139too/sections/.rodata.str1.1
/sys/module/8139too/sections/.rodata
/sys/module/8139too/sections/.exit.text
/sys/module/8139too/sections/.init.text
/sys/module/8139too/sections/.altinstr_replacement
/sys/module/8139too/sections/.text
/sys/module/8139too/refcnt
/sys/bus/pci/drivers/8139too
/sys/bus/pci/drivers/8139too/new_id
/sys/bus/pci/drivers/8139too/0000:06:00.0
/usr/src/linux-2.6.10-3.mm.24mdk/drivers/net/8139too.c
/usr/src/linux-2.6.11-6mdk/drivers/net/8139too.c
/lib/modules/2.6.11-6mdksmp/kernel/drivers/net/8139too.ko.gz
[root@Lapa dev]# uname -r
2.6.11-6mdksmp
|
|
|
All times are GMT -5. The time now is 06:44 PM.
|
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
|
|