View previous topic :: View next topic |
Author |
Message |
waxed n00b
Joined: 14 Dec 2003 Posts: 22
|
Posted: Wed Dec 17, 2003 1:12 am Post subject: Failed to bring up eth0 and eth1 |
|
|
After my first fresh install my nic wont come up.
eth0 is the build on board crappy nic that i dont use.
eth1 is a standard 3com that i used the whole install so i know it works.
I tried to /etc/init.d/net/eth1 start but it still tells me that it fails to start.
Also when the system is booting up it says:
modprobe cant locate module /dev/rtc
modprobe cant locate module /dev/misc/rtc
modprobe cant locate module /dev/rtc
modprobe cant locate module /dev/misc/rtc
would that have anything to do with it?
I did a ifconfig and nothing shows up but the local loopback.
|
|
Back to top |
|
|
dice Guru
Joined: 21 Apr 2002 Posts: 577
|
Posted: Wed Dec 17, 2003 1:15 am Post subject: |
|
|
Do you see it if you do an ifconfig -a ? If not, you probably need to load the kernel module. If you do see it, you probably need to edit your /etc/conf.d/net (the comments are self-explanitory). |
|
Back to top |
|
|
m0pr0be Guru
Joined: 29 Aug 2002 Posts: 308
|
Posted: Wed Dec 17, 2003 1:18 am Post subject: |
|
|
tells you if your nic is working. it list all network interfaces.
if its not there, then it is a kernel/module problem |
|
Back to top |
|
|
waxed n00b
Joined: 14 Dec 2003 Posts: 22
|
Posted: Wed Dec 17, 2003 1:35 am Post subject: |
|
|
Ok i ran the ifconfig -a and it was not in there.. Do in need to go back through chroot like im doing the install to configure the kernel? |
|
Back to top |
|
|
dice Guru
Joined: 21 Apr 2002 Posts: 577
|
Posted: Wed Dec 17, 2003 1:44 am Post subject: |
|
|
No, you should just be able to modprobe the module directly. This will be whatever module you loaded up when you booted the livecd, probably 3c59x or something. Once you've done that and verified that it works you can add the module to /etc/modules.autoload and it'll be loaded automagically when you boot the system. |
|
Back to top |
|
|
waxed n00b
Joined: 14 Dec 2003 Posts: 22
|
Posted: Wed Dec 17, 2003 2:06 am Post subject: |
|
|
dice wrote: | No, you should just be able to modprobe the module directly. This will be whatever module you loaded up when you booted the livecd, probably 3c59x or something. Once you've done that and verified that it works you can add the module to /etc/modules.autoload and it'll be loaded automagically when you boot the system. |
My nic is a 3c905b tx
Here is what i typed..
tux root #modprobe 3c95x
modprobe: Can't locate module 3c59x
tux root #
do i need to type something else?
<=== is still a newbie |
|
Back to top |
|
|
waxed n00b
Joined: 14 Dec 2003 Posts: 22
|
Posted: Wed Dec 17, 2003 2:43 am Post subject: |
|
|
Also when i do lsmod the only thing that comes up is
module size used by not tainted
|
|
Back to top |
|
|
dice Guru
Joined: 21 Apr 2002 Posts: 577
|
Posted: Wed Dec 17, 2003 3:00 am Post subject: |
|
|
Sounds like you don't have the proper kernel modules installed. You'll need to configure and compile your kernel as documented in the install guide. |
|
Back to top |
|
|
waxed n00b
Joined: 14 Dec 2003 Posts: 22
|
Posted: Wed Dec 17, 2003 3:15 am Post subject: |
|
|
dice wrote: | Sounds like you don't have the proper kernel modules installed. You'll need to configure and compile your kernel as documented in the install guide. |
could all of this be caused if i had the wrong kernel name in my grub.conf file?
in my grub.conf file i have
kernel (hd0,0)/kernel-2.4.22 root=/dev/hda3
I did a uname -r and it said 2.4.23 since i have the wrong number in there would it cause all this trouble?
EDIT: never mind... i changed it to 23 and now it wont boot.. sigh |
|
Back to top |
|
|
|