View previous topic :: View next topic |
Author |
Message |
Base n00b
Joined: 22 Apr 2005 Posts: 17
|
Posted: Sat Apr 23, 2005 2:10 pm Post subject: Network driver problems |
|
|
Got networking problems with my builtin network card on a compaq p4 2.8 motherboard.
Networking actually works great from the livecd. But after install it wont work.
Installed dhcpcd, but just gets error about netmount couldnt start at boot.
Changed to static ip information and i could ping locahost + my own ip. But no other computer on the local network.
Checked lsmod and found out that on the livecd it seems like the netmodule ohci1394 is used.
But when booting fron hd it uses eth1394 instead.
Thought that this could perhaps be the problem, but then my question is, how can i steer the system over to
the other module? I use gentoo-kernel and this seems to be done automatically.
Loading it in module.autoload wont do anything since its just continues using eth1394 for eth0 it seems.
/Base |
|
Back to top |
|
|
Momo_CCCP Tux's lil' helper
Joined: 26 Oct 2004 Posts: 141
|
Posted: Sat Apr 23, 2005 2:16 pm Post subject: Re: Network driver problems |
|
|
ohci1394 is a Firewire driver, I doubt it is related to your network (unless you use ethernet over firewire, which would be uncommon to say the least). I suggest you issue the lspci command and look for your network adapter and then load the appropriate module. If you have a realtek of some sort this will likely be :
for an SiS chip :
etc...
If you don't manage to solve the problem by yourself, please post the output of lspci here and I'll help you. _________________ Momo_CCCP |
|
Back to top |
|
|
Base n00b
Joined: 22 Apr 2005 Posts: 17
|
Posted: Sat Apr 23, 2005 2:30 pm Post subject: |
|
|
Ah ok, then i got it backwards
i do have the 8139too mod loaded both in livecd and in the installed linux.
Though in the installed version i have eth1394 aswell wich to me sounded kinda like a network module.
Anyway 8139too is always present but when booting from hd it strangely enough wont work.
Obviously its not a problem with cables/switch since livecd works great.
But when trying to bring eth0 up via dhcp i just get !!. And when setting static ip wont help either..hmm strange.. |
|
Back to top |
|
|
Base n00b
Joined: 22 Apr 2005 Posts: 17
|
Posted: Sat Apr 23, 2005 2:42 pm Post subject: |
|
|
I saw no that at boot, eth1394 is assigned to eth0, wich should not be right? 8139too should imo be the module used for the networking. How can i steer this around? |
|
Back to top |
|
|
Momo_CCCP Tux's lil' helper
Joined: 26 Oct 2004 Posts: 141
|
Posted: Sat Apr 23, 2005 2:51 pm Post subject: |
|
|
if you are really sure eth1394 is used for networking just unload it :
rmmod eth1394
after that : modprobe 8139too _________________ Momo_CCCP |
|
Back to top |
|
|
Base n00b
Joined: 22 Apr 2005 Posts: 17
|
Posted: Sat Apr 23, 2005 2:55 pm Post subject: |
|
|
Hmm i saw clearly in the boot thet eth1394 was referred to eth0
I disabled 1394 in the bios then my non functioning networking stopped loading at all at boot time.
No failed dhcp etc.
It doesnt seem to want to have anything to do with my builtin network card.
I put in a realtek pci card(need to get some things done) end that worked directly. Didnt disable LAN but when i disabled 1394 it seemed like the realtek card took over as eth0 as far as i can tell.
Will keep laborating with this, during the evening i think, see if i can get it to work..hmm |
|
Back to top |
|
|
|