....and do insmod 3c5x9
Good grief! I did this and it showed the correct info. Strange, I thought, and proceeded to bring up the interface. This also suddenly is working. (hmmmmm) And eth0 is also showing in ifconfig. All I can think is that when i ran modconf I did two things - deleted the dummy0 module and tried installing the 3c509, the latter which just brought up errors yesterday. Perhaps restarting the computer and having no dummy0 in place caused the eth0 mod to do whatever it needed to do properly? Still not pinging anything on the network though. Pinging my own IP shows it is using loopback, and tcpdump then shows for trying to reach anything else on the network: 13:40:32.704186 eth0 > arp who-has jenny?TCL tell TRX850/TCL (0:a0:24:2:cf:26) 13:40:35.694822 lo > TRX850/TCL > TRX850/TCL: icmp: host jenny/TCL unreachable [tos 0xc0] Does this mean anything to anyone? Heff! Heff! A hoffable herralump! Thanks, Jenny. PS. Next time I splash out on the netgear.
--- Jenny_Hopkins@toby-churchill.com wrote:
....and do insmod 3c5x9
Good grief! I did this and it showed the correct info. Strange, I thought, and proceeded to bring up the interface. This also suddenly is working. (hmmmmm) And eth0 is also showing in ifconfig.
In that case don't touch anything else. leave it and work out how todo a auto insmod on boot, a cludge but it'll work, that is all i have for my FA311.
With the 3c509 which I have all I did was putting it in and modprobe 3c509 and it went from there, I didn't touch the settings on the board and from the sound of things you wont need to.
All I can think is that when i ran modconf I did two things - deleted the dummy0 module and tried installing the 3c509, the latter which just brought up errors yesterday. Perhaps restarting the computer and having no dummy0 in place caused the eth0 mod to do whatever it needed to do properly?
I have found it good to stear clear of programs which are supposed to help make these things easier, as they invariably never do. All my hardware was done by learning what i had and doing a simple modprobe for each thing, when that worked I set it all in a script - rc.modules - which does it all for me.
Still not pinging anything on the network though. Pinging my own IP shows it is using loopback, and tcpdump then shows for trying to reach anything else on the network: 13:40:32.704186 eth0 > arp who-has jenny?TCL tell TRX850/TCL (0:a0:24:2:cf:26) 13:40:35.694822 lo > TRX850/TCL > TRX850/TCL: icmp: host jenny/TCL unreachable [tos 0xc0]
what does route -n give? it could be that you have the wrong routing configured and need the default route to be set to something else.
Does this mean anything to anyone? Heff! Heff! A hoffable herralump! Thanks, Jenny. PS. Next time I splash out on the netgear.
Very good idea. Very easy to configure. If you are willing to stretch to it get a 3com card, a PCI 3com card is the dogs danglies.
Thanks
D
PS call me if you need a hand.
__________________________________________________ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
In general, your primary net card should be compiled in and not a module. You can get away with it if you add to your conf.modules (or modules.conf) a line like alias eth0 3c509 (or whatever the module is called) The alternative is to ensure that an explciit modprobe is done for the card before you try to configure the network. Dig around in /etc/rc* to find out where to put it.
I get twitchy on this point because all my machines have two ethernet cards and I have to be very sure which comes up as eth0 and which as eth1.
On 18-May-01 David Freeman wrote:
--- Jenny_Hopkins@toby-churchill.com wrote:
....and do insmod 3c5x9
Good grief! I did this and it showed the correct info. Strange, I thought, and proceeded to bring up the interface. This also suddenly is working. (hmmmmm) And eth0 is also showing in ifconfig.
In that case don't touch anything else. leave it and work out how todo a auto insmod on boot, a cludge but it'll work, that is all i have for my FA311.
With the 3c509 which I have all I did was putting it in and modprobe 3c509 and it went from there, I didn't touch the settings on the board and from the sound of things you wont need to.
All I can think is that when i ran modconf I did two things - deleted the dummy0 module and tried installing the 3c509, the latter which just brought up errors yesterday. Perhaps restarting the computer and having no dummy0 in place caused the eth0 mod to do whatever it needed to do properly?
I have found it good to stear clear of programs which are supposed to help make these things easier, as they invariably never do. All my hardware was done by learning what i had and doing a simple modprobe for each thing, when that worked I set it all in a script - rc.modules
- which does it all for me.
Still not pinging anything on the network though. Pinging my own IP shows it is using loopback, and tcpdump then shows for trying to reach anything else on the network: 13:40:32.704186 eth0 > arp who-has jenny?TCL tell TRX850/TCL (0:a0:24:2:cf:26) 13:40:35.694822 lo > TRX850/TCL > TRX850/TCL: icmp: host jenny/TCL unreachable [tos 0xc0]
what does route -n give? it could be that you have the wrong routing configured and need the default route to be set to something else.
Does this mean anything to anyone? Heff! Heff! A hoffable herralump! Thanks, Jenny. PS. Next time I splash out on the netgear.
Very good idea. Very easy to configure. If you are willing to stretch to it get a 3com card, a PCI 3com card is the dogs danglies.
Thanks
D
PS call me if you need a hand.
Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
alug, the Anglian Linux User Group list Send list replies to alug@stu.uea.ac.uk http://www.anglian.lug.org.uk/ http://rabbit.stu.uea.ac.uk/cgi-bin/listinfo/alug See the website for instructions on digest or unsub!
---------------------------------- ... all the fallacious exactitude that characterises a statistical table. - Eric Partridge E-Mail: Raphael Mankin raph@panache.demon.co.uk Date: 20-May-01 Time: 13:38:25 ----------------------------------
--- Raphael Mankin raph@panache.demon.co.uk wrote:
In general, your primary net card should be compiled in and not a module. You can get away with it if you add to your conf.modules (or modules.conf) a line like alias eth0 3c509 (or whatever the module is called) The alternative is to ensure that an explciit modprobe is done for the card before you try to configure the network. Dig around in /etc/rc* to find out where to put it.
Why should it be compiled in? surely this is a bad idea as every time you change card you need to recompile the whole kernel. On Peanut linux I have a file called rc.modules which is run by init at boot time and sets up each of the devices (network, sound etc...) This seams to work very well, not sure if its optomised for speed, but for someone like me whoes on my 5 network card in 5 months, and who had run out of PCI slots, I find this works well. I still don't understand why we don't just have the core functioanlity and enough to boot the machine compiled in and everything else put in as a module, this way it makes things very configurable, and you don't need to compile the kernel as often as you would other wise. Can anyone tell me why we wouldn't do this?
I get twitchy on this point because all my machines have two ethernet cards and I have to be very sure which comes up as eth0 and which as eth1.
With my box they come up in the order they are entered in the rc.modules file.
Thanks
D
PS I am currently reading writing Linux Device Drivers, which is very good and I would recommend it to anyone who wants to understand whats going on under the hood, even if you don't intend on ever writing some ode.
On 18-May-01 David Freeman wrote:
--- Jenny_Hopkins@toby-churchill.com wrote:
....and do insmod 3c5x9
Good grief! I did this and it showed the correct info. Strange,
I
thought, and proceeded to bring up the interface. This also
suddenly
is working. (hmmmmm) And eth0 is also showing in ifconfig.
In that case don't touch anything else. leave it and work out how
todo
a auto insmod on boot, a cludge but it'll work, that is all i have
for
my FA311.
With the 3c509 which I have all I did was putting it in and
modprobe
3c509 and it went from there, I didn't touch the settings on the
board
and from the sound of things you wont need to.
All I can think is that when i ran modconf I did two things - deleted the dummy0
module
and tried installing the 3c509, the latter which just brought up
errors
yesterday. Perhaps restarting the computer and having no dummy0
in
place caused the eth0 mod to do whatever it needed to do properly?
I have found it good to stear clear of programs which are supposed
to
help make these things easier, as they invariably never do. All my hardware was done by learning what i had and doing a simple
modprobe
for each thing, when that worked I set it all in a script -
rc.modules
- which does it all for me.
Still not pinging anything on the network though. Pinging my own
IP
shows it is using loopback, and tcpdump then shows for trying to reach anything else on the network: 13:40:32.704186 eth0 > arp who-has jenny?TCL tell TRX850/TCL (0:a0:24:2:cf:26) 13:40:35.694822 lo > TRX850/TCL > TRX850/TCL: icmp: host jenny/TCL unreachable [tos 0xc0]
what does route -n give? it could be that you have the wrong
routing
configured and need the default route to be set to something else.
Does this mean anything to anyone? Heff! Heff! A hoffable herralump! Thanks, Jenny. PS. Next time I splash out on the netgear.
Very good idea. Very easy to configure. If you are willing to
stretch
to it get a 3com card, a PCI 3com card is the dogs danglies.
Thanks
D
PS call me if you need a hand.
Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
alug, the Anglian Linux User Group list Send list replies to alug@stu.uea.ac.uk http://www.anglian.lug.org.uk/ http://rabbit.stu.uea.ac.uk/cgi-bin/listinfo/alug See the website for instructions on digest or unsub!
... all the fallacious exactitudethat characterises a statistical table. - Eric Partridge E-Mail: Raphael Mankin raph@panache.demon.co.uk Date: 20-May-01 Time: 13:38:25
__________________________________________________ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
David Freeman wrote:
--- Raphael Mankin raph@panache.demon.co.uk wrote:
In general, your primary net card should be compiled in and not a module. You can get away with it if you add to your conf.modules (or modules.conf) a line like alias eth0 3c509 (or whatever the module is called) The alternative is to ensure that an explciit modprobe is done for the card before you try to configure the network. Dig around in /etc/rc* to find out where to put it.
Why should it be compiled in? surely this is a bad idea as every time you change card you need to recompile the whole kernel.
that depends on your viewpoint... I have a machine that hasn't changed it's HW spec in 5 years... some people say that having modules lowers the memory footprint on startup, this may be true but these days with modern hardware I don't see startup memory footprint being a big issue... if you are constantly messing around with the hardware then, yes, having modules is good, but it dosen't mean that having modules compiled into the kernel is bad ;)..
On Peanut linux I have a file called rc.modules which is run by init at boot time and sets up each of the devices (network, sound etc...) This seams to work very well, not sure if its optomised for speed, but for someone like me whoes on my 5 network card in 5 months, and who had run out of PCI slots, I find this works well. I still don't understand why we don't just have the core functioanlity and enough to boot the machine compiled in and everything else put in as a module, this way it makes things very configurable, and you don't need to compile the kernel as often as you would other wise. Can anyone tell me why we wouldn't do this?
There are some modules which (for reasons unknown to me) can't be loaded as modules wether this is a kernel limitation, or lazy programming (!) I don't know.
There are some kenel's which do what you are saying (mach springs to mind), but I don't know enough about them to speak on the subject ;)...
Sz
On 20-May-01 David Freeman wrote:
--- Raphael Mankin raph@panache.demon.co.uk wrote:
In general, your primary net card should be compiled in and not a module. You can get away with it if you add to your conf.modules (or modules.conf) a line like alias eth0 3c509 (or whatever the module is called) The alternative is to ensure that an explciit modprobe is done for the card before you try to configure the network. Dig around in /etc/rc* to find out where to put it.
Why should it be compiled in? surely this is a bad idea as every time you change card you need to recompile the whole kernel.
[snip]
In general, I agree with you, and that is fine for those who are hapy with doing all the tinkering that is necessary in places like modules.conf. Howver, newbies are likely to be bitten by this, and in the particular case of network cards, which need to have their modules loaded quite early in the startup sequence, it is easier to have them compiled in.
I do exactly the same as you do in my Slackware system, and for the same reasons: I am forever swapping network cards around. However for simple usage stick to simple configurations; you are less likely to be bitten by something unexpected. ---------------------------------- ... all the fallacious exactitude that characterises a statistical table. - Eric Partridge E-Mail: Raphael Mankin raph@panache.demon.co.uk Date: 20-May-01 Time: 22:12:13 ----------------------------------
--- Raphael Mankin raph@panache.demon.co.uk wrote:
On 20-May-01 David Freeman wrote:
--- Raphael Mankin raph@panache.demon.co.uk wrote:
In general, your primary net card should be compiled in and not a module. You can get away with it if you add to your conf.modules (or modules.conf) a line like alias eth0 3c509 (or whatever the module is called) The alternative is to ensure that an explciit modprobe is done for the card before you try to configure the network. Dig around in /etc/rc* to find out where to put it.
Why should it be compiled in? surely this is a bad idea as every
time
you change card you need to recompile the whole kernel.
[snip]
In general, I agree with you, and that is fine for those who are hapy with doing all the tinkering that is necessary in places like modules.conf. Howver, newbies are likely to be bitten by this, and in the particular case of network cards, which need to have their modules loaded quite early in the startup sequence, it is easier to have them compiled in.
Why? it means that it isn't as versitile and that you can only support a small number of cards compiled in. Its better to have one of the init scripts go and load the required modules, its not even difficult to write tool which will aid choosing the correct modules. That way you can just distribute modules as extras etc... To me it just makes sense.
I do exactly the same as you do in my Slackware system, and for the same reasons: I am forever swapping network cards around. However for simple usage stick to simple configurations; you are less likely to be bitten by something unexpected.
Which requires a complex kernel recompile when you want to upgrade from 10Mbps to 100Mbps?
Thanks
D
__________________________________________________ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
On 20-May-01 David Freeman wrote:
--- Raphael Mankin raph@panache.demon.co.uk wrote:
[snip]
Which requires a complex kernel recompile when you want to upgrade from 10Mbps to 100Mbps?
To re-iterate, I *agree* with you. I *do* use modules.
However, for a *novice* it is easier to compile the driver into the kernel. There is less chance of treading on one's own toes.
-
David Freeman -
Jenny_Hopkins＠toby-churchill.com -
Neill Newman -
Raphael Mankin