LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices



Reply
 
Search this Thread
Old 02-05-2004, 12:06 AM   #1
renegade69
LQ Newbie
 
Registered: Aug 2003
Distribution: red hat 9.0
Posts: 26

Rep: Reputation: 15
Question EtherExpress100 driver conflict on toshiba 1800


Hello everyone,
I have had a new problem arise with my linux box. I am currently running red hat 9.0 on a toshiba satellite 1800. Until today I have not had a problem for about 5 months. Everything was working perfectly(almost!), when today my Intel Ether Express 100 nic card felt like dieing on me. It was very peculiar because I did nothing to provoke this. It is almost as someone came into my system and messed with it. I have written my own iptables but I have yet to try tripwire for security.
The problem is somewhere with my drivers/modules for my nic card. I have tried over and over again to recompile my kernel but I cannot seem to work out this bug.
The main error message I am receiving is:

"redhat-config-network:

eth0 has an alias to module e100 in modules.conf,
instead of currently loaded module eepro100!"

this shouldn't be. I have used eepro100 for the past 5 months without any problems.

I can remove this error if I switch the driver to e100. Either of these drivers should work perfectly for my card. One is a Becker driver, the other is a Intel driver.
But this does not solve the problem. I still get an error when I specify the driver for my ethernet card in redhat-config-network.
"command failed: sbin/modprobe e100"

this comes up when either module is selected in xconfig. It seems that even If I load eepro100 it still tries to use e100. But either way e100 does not work. BUT did work before! BOTH DID!

I am at my wits end. Any help on this would be greatly appreciated.

If you are a newbie with a toshiba 1800 and red hat 9.0, you can go ahead and post questions in this thread. I will be checking this multiple times a day. There were alot of problems after installation but they are all easily worked out If you know what to do! Red Hat works perfectly on a toshiba 1800. I am bit of a newbie myself, but Ive gained enough experience with this OS in the past 8 months to battle (almost!) any problem!

Renegade
 
Old 02-05-2004, 03:08 AM   #2
adz
Senior Member
 
Registered: Jun 2003
Location: Sydney
Distribution: Debian, FreeBSD
Posts: 1,713

Rep: Reputation: 53
So are you saying that neither module will load now?
 
Old 02-05-2004, 11:34 AM   #3
renegade69
LQ Newbie
 
Registered: Aug 2003
Distribution: red hat 9.0
Posts: 26

Original Poster
Rep: Reputation: 15
NO... eepro100 is loaded... but it refuses to use this module for some reason... which is the one I have used for the past 5 months...

e100 will not load... but it is the module that it will try to load for my nic card...
 
Old 02-05-2004, 06:53 PM   #4
adz
Senior Member
 
Registered: Jun 2003
Location: Sydney
Distribution: Debian, FreeBSD
Posts: 1,713

Rep: Reputation: 53
There will be a line in your modules.conf (or conf.modules) that says "alias eth0 e100". If you changed that to say "alias eth0 eepro100" then you should be OK.
 
Old 02-05-2004, 09:20 PM   #5
renegade69
LQ Newbie
 
Registered: Aug 2003
Distribution: red hat 9.0
Posts: 26

Original Poster
Rep: Reputation: 15
Hey adm,
I cannot find modules.conf! *That was my problem from the beggining! I should have stated that in my first post!
 
Old 02-05-2004, 10:03 PM   #6
adz
Senior Member
 
Registered: Jun 2003
Location: Sydney
Distribution: Debian, FreeBSD
Posts: 1,713

Rep: Reputation: 53
It should be in /etc. It can also be called "conf.modules" in some distros. If you don't have it, then that's highly unusual unless you're running a 2.6 series kernel. If you're a 2.6er then the file will be called "modprobe.conf". It you ever need to find a file again just type find <path> -iname <search pattern>. A man find will tell you more.
 
Old 02-06-2004, 03:46 PM   #7
renegade69
LQ Newbie
 
Registered: Aug 2003
Distribution: red hat 9.0
Posts: 26

Original Poster
Rep: Reputation: 15
ok, so I have found modules.conf... changed it to either drive whichever I have installed at the time... I have tried both many times... but neither will work...

I couldnt remember the parameter -iname for the find command... haha... thanks...

now I have even recompiled the kernel from untouched source code... meaning I tar -xf the source code, taking away the problem that my files on my comp have been altered...

but I am still receiving this retarded error. This is with module e100 loaded:


"redhat-config-network:

The Ethernet card could not be initialized. Please verify your settings and try again.

Command failed: /sbin/modprobe e100

Output:
modprobe: Can't locate module e100"


So I know where this module is... its in /lib/modules/build/linux2.4.22/drivers/net/e100/

if I try and modprobe in this directory it still says "can't locate module e100"

If I try and insmod I get an error saying:
"e100.o: couldn't find the kernel version the module was complied for"
but 2.4.22 is my working kernel...

I was also wonderring where the script is for my network adapter... which specifies the diver and directory of the driver for my ethernet card when it tries to initialize...

Thanks for your help adz it is much appreciated!!!!!!!!!!!!!!!!!!!!!!

Renegade
 
Old 02-06-2004, 08:37 PM   #8
adz
Senior Member
 
Registered: Jun 2003
Location: Sydney
Distribution: Debian, FreeBSD
Posts: 1,713

Rep: Reputation: 53
It sounds like you didn't do a make modules_install at the end of your kernel compilation. You've mentioned that it didn't work regardless of which module you used. You didn't actually say what you wrote into modules.conf nor did you provide me with an error message. I can't do a lot with "it didn't work". Also, you didn't actually say what you did after editting said file. Did you do an ifconfig? A dhclient? All you say is the network-config thing. I can't see how that will help you. My impression was that it tries to load a module for you which is what you're trying to do already.

When you try to load the module use modprobe and invoke it thus:modprobe eth0. If you've aliased the module correctly then that will load your driver. If modprobe exits without error then do an ifconfig eth0 up. See if you get an error and if not see if the "eth0" interface came up with ifconfig.
 
Old 02-07-2004, 12:06 AM   #9
renegade69
LQ Newbie
 
Registered: Aug 2003
Distribution: red hat 9.0
Posts: 26

Original Poster
Rep: Reputation: 15
Yes... I did do a make modules_install...

The reason I am not overly clear on everything is because I do not understand this ridiculous error...

When I said I am using e100... that means I wrote e100 in for the alias... if I say I am using eepro100 that means I have eepro100 written in modules.conf as the alias...

One thing I was not clear about, is that that my eth0 is up... it receives packets and trasmits(very few) packets...

but If I try to ping... lets say the router... it says "operation not allowed" on every attempt to transmit...

if I go into ethereal... it seems to receive packets from the computer that which I am on right now... a windows machine on our network... now this is a very percular... there is also an outside ip address coming into my computer and then seems to connect to this computer via my own... could this possibly be a cracker in my system?

I have the previous error every time I try to reinstall the driver with "neat"...

dhclient spits out alot of information... I can not understand it completly... if you need to know something from the output just ask..

Im sorry I am not very clear on everything... I am very stressed right now... I had an assigment due today which I will have to submit late because of this problem... If you need any more information just ask...
 
Old 02-07-2004, 02:29 AM   #10
adz
Senior Member
 
Registered: Jun 2003
Location: Sydney
Distribution: Debian, FreeBSD
Posts: 1,713

Rep: Reputation: 53
OK, sounds like a routing problem. Since the eth0 interface is up I'll assume you have a working module loaded. Just double check which one is loaded with lsmod and make sure it corresponds to the entry in modules.conf. Once you've done that, bring the eth0 interface down and then up again (ifconfig eth0 down and ifconfig eth0 up). If you get errors, don't bother going any further and report the errors here. If no errors then your hardware/driver setup is 100% OK and no more needs to be done with that.

Next comes routing. Does your router also act as a DHCP server? If so, you should just be able to do a dhclient eth0. The output of which should look similar to this:

Quote:
hades:/# dhclient eth0
Internet Software Consortium DHCP Client V3.0.1rc11
Copyright 1995-2002 Internet Software Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

sit0: unknown hardware address type 776
sit0: unknown hardware address type 776
Listening on LPF/eth0/00:00:e2:73:95:a9
Sending on LPF/eth0/00:00:e2:73:95:a9
Sending on Socket/fallback
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 192.168.1.1
bound to 192.168.1.10 -- renewal in 126290 seconds.
The money line is "bound to 192.168.1.10 -- renewal in 126290 seconds" and the address there is your assigned IP address. If you do not have a DHCP server then you'll have to pick an IP address. One you've done that, bring the eth0 interface down. Then bring it up with ifconfig eth0 up <IP address>. Then add a default route with route add default gw <your gateway's IP address>, Your gateway is probably your router. Now try to ping yourself. Then your gateway. Then another computer on your network. Then a site in the open internet (assuming that network is connected). Report any errors verbatim (ie copy and paste, if possible).
 
Old 02-07-2004, 04:51 AM   #11
renegade69
LQ Newbie
 
Registered: Aug 2003
Distribution: red hat 9.0
Posts: 26

Original Poster
Rep: Reputation: 15
ok... this is weird...

when I do lsmod there are only 4 outputs and neither is e100 or eepro100... does lsmod require any parameters?

4 outputs:
ipt_REJECT
ipt_STATE
mousedev
keybdev


I can ifconfig eth0 down and ifconfig eth0 up without any errors...

when I do an ifconfig... it shows everything to be up and running... packets tramited(very few) and received...

when I do dhclient eth0 I get the money line except its in 32734 seconds... with no errors...

I can ifconfig eth0 down and ifconfig eth0 up 192.168.1.x without any errors...

I can add the default gateway(my router) without any errors... there are two lines in my routing table... what should the fist one be? the second is my gateway...

When I try to ping my own ip addres it spits out an error on every attempt...

PING 192.168.1.x (192.168.1.x) ...
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted

ctrl-c

The same for my gateway and any other computers on my network...

Im sorry I couldn't copy and paste my output for dhclient... I will be able to tommorrow... my disk drive is gone to the garbage... so I need to use my flash drive... which I have yet to use on linux... Im still trying to figure out how to create the mount point... I think I am just putting the wrong parameters in /etc/fstab... I know I have the right drive... its on sda but the filesystem and other parameters I have not figured out...

Thanks again adz!!!!!!! I love the help!!!

Renegade
 
Old 02-07-2004, 08:11 AM   #12
adz
Senior Member
 
Registered: Jun 2003
Location: Sydney
Distribution: Debian, FreeBSD
Posts: 1,713

Rep: Reputation: 53
You said you recompiled your kernel several times. You didn't by any chance compile the ethernet driver straight into the kernel did you? I mean NOT as a module but into the kernel proper. Longshot but I had to ask.

OK just to make sure you know, you're not meant to do the dhclient eth0 thing AND the ifconfig eth0 up 192.168.1.x thing. You do one or the other. Sorry if I wasn't clear on that. Since you got a response with the dhclient command then DIRECTLY AFTER THAT do a ping: yourself, your gateway, and some site. I think that should make it work. What dhclient (DHCP client) does is sends out a broadcast on an interface (in this case eth0) and waits for a reply from a DHCP server. They chat for a while and the server assigns the client an IP address and routing instructions. Therefore, specifying the IP address in the ifconfig command and then doing the route command are superfluous (and in fact completely counter-productive as they mess up your already defined settings).
 
Old 02-07-2004, 12:04 PM   #13
renegade69
LQ Newbie
 
Registered: Aug 2003
Distribution: red hat 9.0
Posts: 26

Original Poster
Rep: Reputation: 15
I have tried installing the ethernet driver as a module and directly into the kernel. Which should it be?

After doing a dhclient eth0, it stilll gives me that error when I try and ping anything. "Operation not allowed"

Do you know the parameters needed for a flash drive in the file /etc/fstab...?

Last edited by renegade69; 02-07-2004 at 12:14 PM.
 
Old 02-07-2004, 09:32 PM   #14
adz
Senior Member
 
Registered: Jun 2003
Location: Sydney
Distribution: Debian, FreeBSD
Posts: 1,713

Rep: Reputation: 53
It's preferable that you make it as a module. On a notebook it's not as important since it's pretty hard to change ethernet devices. But sometimes you don't use it a therefore there's no need for it to be loaded and taking up memory. So what is the case in the above example? Is it a module or not? If it is then you 'll need to try and load it.

Could you post the output of route before and after the dhclient eth0?

No, I know nothing about usb hard drives. I did notice that you didn't have the right modules loaded unless you compiled them straight into the kernel. Like "usbcore" for example. But, you're better off starting a new thread for that.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Success: Suse 9.3 Toshiba 1800-S207 al_erola Linux - Laptop and Netbook 3 03-10-2007 07:45 AM
Conflict between network driver and PCMCIA driver dhave Slackware 2 10-06-2004 06:30 AM
sound driver conflict scarabs Linux - Newbie 11 03-29-2004 04:50 PM
linux for Toshiba 1800-204 geru59 Linux - Laptop and Netbook 1 01-05-2004 08:14 PM
Toshiba 1800-4k1 modem problem! X_Ray_Cat Linux - Laptop and Netbook 1 09-05-2003 12:21 AM


All times are GMT -5. The time now is 02:33 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration