Loading module for network card - 3c509
Hello All - am I not right in thinking that if I am trying to load the module for the network card that the 9.1 install failed to set up (yes, same problem as before), the syntax would be # modprobe 3c509 ? I had fondly imagined this to be the case, but the command appears to have been seen as an instruction to 'lock the machine solid and refuse to allow any keyboard or mouse input'. Why don't I ssh in? Well you see the network card isn't recognised ... Bleh ... Thanks Fergus -- Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB Tel: +44 161 834 7961 Fax: +44 161 839 5797 http://www.chethams.org.uk
Hello All - am I not right in thinking that if I am trying to load the module for the network card that the 9.1 install failed to set up (yes, same problem as before), the syntax would be
# modprobe 3c509
?
That is the way that I do it and it seems to work.
I had fondly imagined this to be the case, but the command appears to have been seen as an instruction to 'lock the machine solid and refuse to allow any keyboard or mouse input'.
Sounds like a driver conflict.
Why don't I ssh in? Well you see the network card isn't recognised ... Bleh ...
Ouch! That sucks! I can relate. On my issue with Gnome, it freezes so bad that I have to do a hard reboot! Before you issue that command, list the modules already installed and see if a module is installed already. If so, remove it and try the modprobe command again. Marshall
On Friday 14 May 2004 11:28, Marshall Heartley wrote:
Hello All - am I not right in thinking that if I am trying to load the module for the network card that the 9.1 install failed to set up (yes, same problem as before), the syntax would be
# modprobe 3c509
?
That is the way that I do it and it seems to work.
I had fondly imagined this to be the case, but the command appears to have been seen as an instruction to 'lock the machine solid and refuse to allow any keyboard or mouse input'.
Sounds like a driver conflict.
Why don't I ssh in? Well you see the network card isn't recognised ... Bleh ...
Ouch! That sucks! I can relate. On my issue with Gnome, it freezes so bad that I have to do a hard reboot!
Before you issue that command, list the modules already installed and see if a module is installed already. If so, remove it and try the modprobe command again.
Thanks Marshall. I did check to see if the module was loaded first, in fact - it wasn't. The problem is undoubtedly a module - loading one. I'm sure I will get it sorted out - however I'm equally sure a Linux neophyte would have scant chance, and it does seem a particular shame that the installer has blown this when so many versions of SuSE handled it without problems. I'm now at the stage where I could do with instruction rather than tips: what line(s) do I have to enter in /etc/modprobe.conf, and/or what other action do I need to take in order for the module 3c509 to load at boot without building into the initrd? Does anyone know of a source of information that explains how to do this in language the crowd can understand? Man modprobe.conf describes the file as being 'simple', but we must have different understandings of the meaning of this word. Thanks for any help Best Fergus
Marshall
-- Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB Tel: +44 161 834 7961 Fax: +44 161 839 5797 http://www.chethams.org.uk
On Friday 14 May 2004 08:43 am, Fergus Wilde wrote:
I did check to see if the module was loaded first, in fact - it wasn't. The problem is undoubtedly a module - loading one. I'm sure I will get it sorted out - however I'm equally sure a Linux neophyte would have scant chance, and it does seem a particular shame that the installer has blown this when so many versions of SuSE handled it without problems.
Not 'the' module. I think he was referring to looking for a module that might have been loaded for eth0 (but the wrong module) You'd have to get rid of that module before loading the correct one. -- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 05/14/04 09:00 + +----------------------------------------------------------------------------+ "99 percent of lawyers give the rest a bad name."
On Friday 14 May 2004 14:01, Bruce Marshall wrote:
On Friday 14 May 2004 08:43 am, Fergus Wilde wrote:
I did check to see if the module was loaded first, in fact - it wasn't. The problem is undoubtedly a module - loading one. I'm sure I will get it sorted out - however I'm equally sure a Linux neophyte would have scant chance, and it does seem a particular shame that the installer has blown this when so many versions of SuSE handled it without problems.
Not 'the' module. I think he was referring to looking for a module that might have been loaded for eth0 (but the wrong module) You'd have to get rid of that module before loading the correct one.
Thanks Bruce, I should have said 'I did check to see if any eth0 module was loaded first' - no, there isn't.
-- +-------------------------------------------------------------------------- --+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 05/14/04 09:00 + +-------------------------------------------------------------------------- --+ "99 percent of lawyers give the rest a bad name."
-- Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB Tel: +44 161 834 7961 Fax: +44 161 839 5797 http://www.chethams.org.uk
On Friday 14 May 2004 09:09 am, Fergus Wilde wrote:
On Friday 14 May 2004 14:01, Bruce Marshall wrote:
On Friday 14 May 2004 08:43 am, Fergus Wilde wrote:
I did check to see if the module was loaded first, in fact - it wasn't. The problem is undoubtedly a module - loading one. I'm sure I will get it sorted out - however I'm equally sure a Linux neophyte would have scant chance, and it does seem a particular shame that the installer has blown this when so many versions of SuSE handled it without problems.
Not 'the' module. I think he was referring to looking for a module that might have been loaded for eth0 (but the wrong module) You'd have to get rid of that module before loading the correct one.
Thanks Bruce, I should have said 'I did check to see if any eth0 module was loaded first' - no, there isn't.
I wonder if it is an IRQ problem. I notice in my /etc/modprobe.conf that for the 3c509 it calls for irq=10. Wonder if you could add that when doing the modprobe.
-- +------------------------------------------------------------------------ -- --+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 05/14/04 09:00 + +------------------------------------------------------------------------ -- --+ "99 percent of lawyers give the rest a bad name."
-- Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB
Tel: +44 161 834 7961 Fax: +44 161 839 5797
-- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 05/14/04 09:21 + +----------------------------------------------------------------------------+ "QUICK!!! Act as if nothing's happened!"
On Friday 14 May 2004 14:21, Bruce Marshall wrote:
On Friday 14 May 2004 09:09 am, Fergus Wilde wrote:
On Friday 14 May 2004 14:01, Bruce Marshall wrote:
On Friday 14 May 2004 08:43 am, Fergus Wilde wrote:
I did check to see if the module was loaded first, in fact - it wasn't. The problem is undoubtedly a module - loading one. I'm sure I will get it sorted out - however I'm equally sure a Linux neophyte would have scant chance, and it does seem a particular shame that the installer has blown this when so many versions of SuSE handled it without problems.
Not 'the' module. I think he was referring to looking for a module that might have been loaded for eth0 (but the wrong module) You'd have to get rid of that module before loading the correct one.
Thanks Bruce, I should have said 'I did check to see if any eth0 module was loaded first' - no, there isn't.
I wonder if it is an IRQ problem. I notice in my /etc/modprobe.conf that for the 3c509 it calls for irq=10. Wonder if you could add that when doing the modprobe.
Could be - though there have been no changes in the hardware since SuSE 6.2, and from there to 9.0 it installed OK, so it's hard to see why an irq issue would arise now ... the module loads, interestingly, if you start yast and then click on 'network devices' ... Thanks for the thought.
-- +---------------------------------------------------------------------- -- -- --+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 05/14/04 09:00 + +---------------------------------------------------------------------- -- -- --+ "99 percent of lawyers give the rest a bad name."
-- Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB
Tel: +44 161 834 7961 Fax: +44 161 839 5797
-- +-------------------------------------------------------------------------- --+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 05/14/04 09:21 + +-------------------------------------------------------------------------- --+ "QUICK!!! Act as if nothing's happened!"
-- Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB Tel: +44 161 834 7961 Fax: +44 161 839 5797 http://www.chethams.org.uk
On Friday 14 May 2004 10:00 am, Fergus Wilde wrote:
On Friday 14 May 2004 14:21, Bruce Marshall wrote:
On Friday 14 May 2004 09:09 am, Fergus Wilde wrote:
On Friday 14 May 2004 14:01, Bruce Marshall wrote:
On Friday 14 May 2004 08:43 am, Fergus Wilde wrote:
I did check to see if the module was loaded first, in fact - it wasn't. The problem is undoubtedly a module - loading one. I'm sure I will get it sorted out - however I'm equally sure a Linux neophyte would have scant chance, and it does seem a particular shame that the installer has blown this when so many versions of SuSE handled it without problems.
Not 'the' module. I think he was referring to looking for a module that might have been loaded for eth0 (but the wrong module) You'd have to get rid of that module before loading the correct one.
Thanks Bruce, I should have said 'I did check to see if any eth0 module was loaded first' - no, there isn't.
I wonder if it is an IRQ problem. I notice in my /etc/modprobe.conf that for the 3c509 it calls for irq=10. Wonder if you could add that when doing the modprobe.
Could be - though there have been no changes in the hardware since SuSE 6.2, and from there to 9.0 it installed OK, so it's hard to see why an irq issue would arise now ... the module loads, interestingly, if you start yast and then click on 'network devices' ...
What I was (trying to) say was that since you are loading it manually, you may not be providing the same information or options as the system would had it picked up the device at install. Hard to say why it didn't on the install; that's a pretty common nic.
Thanks for the thought.
-- +-------------------------------------------------------------------- -- -- -- --+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 05/14/04 09:00 + +-------------------------------------------------------------------- -- -- -- --+ "99 percent of lawyers give the rest a bad name."
-- Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB
Tel: +44 161 834 7961 Fax: +44 161 839 5797
-- +------------------------------------------------------------------------ -- --+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 05/14/04 09:21 + +------------------------------------------------------------------------ -- --+ "QUICK!!! Act as if nothing's happened!"
-- Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB
Tel: +44 161 834 7961 Fax: +44 161 839 5797
-- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 05/14/04 10:15 + +----------------------------------------------------------------------------+ "We are born naked, wet, and hungry. Then things get worse."
On Friday 14 May 2004 15:16, Bruce Marshall wrote:
On Friday 14 May 2004 10:00 am, Fergus Wilde wrote:
On Friday 14 May 2004 14:21, Bruce Marshall wrote:
On Friday 14 May 2004 09:09 am, Fergus Wilde wrote:
On Friday 14 May 2004 14:01, Bruce Marshall wrote:
On Friday 14 May 2004 08:43 am, Fergus Wilde wrote:
I did check to see if the module was loaded first, in fact - it wasn't. The problem is undoubtedly a module - loading one. I'm sure I will get it sorted out - however I'm equally sure a Linux neophyte would have scant chance, and it does seem a particular shame that the installer has blown this when so many versions of SuSE handled it without problems.
Not 'the' module. I think he was referring to looking for a module that might have been loaded for eth0 (but the wrong module) You'd have to get rid of that module before loading the correct one.
Thanks Bruce, I should have said 'I did check to see if any eth0 module was loaded first' - no, there isn't.
I wonder if it is an IRQ problem. I notice in my /etc/modprobe.conf that for the 3c509 it calls for irq=10. Wonder if you could add that when doing the modprobe.
Could be - though there have been no changes in the hardware since SuSE 6.2, and from there to 9.0 it installed OK, so it's hard to see why an irq issue would arise now ... the module loads, interestingly, if you start yast and then click on 'network devices' ...
What I was (trying to) say was that since you are loading it manually, you may not be providing the same information or options as the system would had it picked up the device at install. Hard to say why it didn't on the install; that's a pretty common nic.
I'm with you, Bruce, and thanks - I'm not coming over clearly, I fear, I mean it loads alright when you open the section in Yast, without passing any additional info to the module. I don't know whether locking the machine by doing modprobe 3c509 was a one-off or not ... experiment would appear unwise, in that I don't fancy locking it up again. You don't happen to know the line I need to put in /etc/modprobe.conf, I suppose? Cheers, thanks for taking so much trouble, Fergus
Thanks for the thought.
-- +------------------------------------------------------------------ -- -- -- -- --+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 05/14/04 09:00 + +------------------------------------------------------------------ -- -- -- -- --+ "99 percent of lawyers give the rest a bad name."
-- Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB
Tel: +44 161 834 7961 Fax: +44 161 839 5797
-- +---------------------------------------------------------------------- -- -- --+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 05/14/04 09:21 + +---------------------------------------------------------------------- -- -- --+ "QUICK!!! Act as if nothing's happened!"
-- Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB
Tel: +44 161 834 7961 Fax: +44 161 839 5797
-- +-------------------------------------------------------------------------- --+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 05/14/04 10:15 + +-------------------------------------------------------------------------- --+ "We are born naked, wet, and hungry. Then things get worse."
-- Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB Tel: +44 161 834 7961 Fax: +44 161 839 5797 http://www.chethams.org.uk
On Friday 14 May 2004 10:59 am, Fergus Wilde wrote:
I'm with you, Bruce, and thanks - I'm not coming over clearly, I fear, I mean it loads alright when you open the section in Yast, without passing any additional info to the module. I don't know whether locking the machine by doing modprobe 3c509 was a one-off or not ... experiment would appear unwise, in that I don't fancy locking it up again. You don't happen to know the line I need to put in /etc/modprobe.conf, I suppose? Cheers, thanks for taking so much trouble, Fergus
It should already be there..... but probably commented out. In my modprobe.conf (9.0 running 2.6.6) # options 3c509 irq=10 -- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 05/14/04 12:48 + +----------------------------------------------------------------------------+ "Where there's a will, there's an inheritance tax."
On Friday 14 May 2004 14.43, Fergus Wilde wrote:
information that explains how to do this in language the crowd can understand?
I already told you. Your problem here isn't due to bad syntax. The 'alias' syntax of modprobe.conf is very simple, but if you have colliding modules that needs to be sorted first
On Friday 14 May 2004 15:58, Anders Johansson wrote:
On Friday 14 May 2004 14.43, Fergus Wilde wrote:
information that explains how to do this in language the crowd can understand?
I already told you.
Hi Anders, Sorry, I don't seem to have had that one ... maybe it's delayed somewhere.
Your problem here isn't due to bad syntax. The 'alias' syntax of modprobe.conf is very simple, but if you have colliding modules that needs to be sorted first
What modules do you think might be colliding? When it boots, there are no ethernet modules loaded. -- Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB Tel: +44 161 834 7961 Fax: +44 161 839 5797 http://www.chethams.org.uk
On Friday 14 May 2004 17.14, Fergus Wilde wrote:
What modules do you think might be colliding? When it boots, there are no ethernet modules loaded.
Well, no, now that I read the rest of the thread I see that it loads when you do it from yast. perhaps it's a bad irq that some others have suggested. The syntax is very simple alias eth0 3c509 as I told you yesterday off-list. If it requires any special parameters, you can add them with options 3c509 irq=10 for example. When yast loads the module, it may be possible to see in the log files /var/log/messages or /var/log/YaST2/* what it uses as parameters. I'm disinclined to believe that this is the whole story though, since it loaded fine without parameters when you did it through the initrd. I suspect some other module that loads steals the IRQ (or some other resource). If you can find out which, then it would be possible to force the module load order
participants (4)
-
Anders Johansson -
Bruce Marshall -
Fergus Wilde -
Marshall Heartley