Hello, I have a PCMCIA Wireless Card that works just fine under SuSE 7.2 and runs on my home wireless hub. However, the problem comes in that there are two network devices in my laptop. A built in eth0 intel card, and the PCMCIA wavelan compatible (PrismII) card. I have tried to get SuSE to automatically configure the PCMCIA card on boot but it doesn't work. Right now what I do is after I log in, I 'su' to and type dhcpcd eth1. This is getting old really fast. I didn't have this problem with Mandrake 8.0 (but I had a host of other problems so that isn't an option). When I try to configure the card through the SuSE tools, the card keeps losing its information. It seems the tools have an issue with PCMCIA network cards. Anyone have any ideas before I start manually tearing apart script to shoehorn this puppy into a working state? Thanks, Anthony.
Hi, I think the problem is that dhclient (dhcpcd) is started after pcmcia. If you go into the runlevel directory for the runlevel you use, for instance /etc/rc.d/rc5.d for graphical system with network and do rm S02dhclient ln -s ../dhclient S07dhclient Since pcmcia is S06 this will (hopefully) restore sanity to your system :) regards Anders On Monday 27 August 2001 21.25, Anthony Moulen wrote:
On Monday 27 August 2001 21.52, Anders Johansson wrote:
Hi,
I think the problem is that dhclient (dhcpcd) is started after pcmcia. If
Should have read 'started before', of course.
Actually, now that I look at the other links, it's probably better to move pcmcia up instead. It looks like there are other services being started in S07 that needs network, so perhaps moving pcmcia to S01 instead?! Anders
Thanks, I will give this a try. I don't think this is the problem though as trying to start the network through the SuSE tools while the system is already in run level 5 doesn't work. For some reason the tools do not detect this device and automatically kill that entry in the configuration. In other words, it would be one thing if the configuration was there and simply needed to be started, but the problem is that the configuration isn't even there. But maybe I missed something. I will move around the configuration files and see what happens. This was the problem on RedHat way back when, and something I totally forgot to consider. Anthony On Mon, 27 Aug 2001, Anders Johansson wrote:
Just a note: the rcnetwork script won't have any effect on devices that uses dhcp. That could be the reason 'starting the network' doesn't do anything. rcdhclient start, however, should work, provided the pcmcia handler is started. If not, check /etc/rc.config and make sure that IFCONFIG_1 is set to "dhcpclient" Anders On Monday 27 August 2001 22.19, Anthony Moulen wrote:
Okay, Just for anyone reading the Archives, I had to actually manually change /etc/pcmcia/network and I think /etc/pcmcia/network.opts to properly show that the card should use DHCP. I had to leave the boot order (or else everything broke) the way it was originally. After that /etc/pcmcia/network start 1, will now bring up my PCMCIA card. This is automatically called from the startup script so I don't need to do any manual tweaking. I am not sure what I would do with a Static IP but then I don't have to worry now do I? ;-). Thanks for all the help, it lead me in the right directions (made me actually read the two scripts that were involved). On Mon, 27 Aug 2001, Anders Johansson wrote:
i have run into this before. it happens because the network services are started before the pcmcia services are started. just go into /etc/init.d/rc#.d and change the order of your network and pcmcia scripts by renumbering them (change S05network to something like S75network) of course if you are running services like apache or named or something that might cause a problem. or you could just do echo "dhcpcd eth1" /etc/init.d/pcmcia-start chmod 755 /etc/init.d/pcmcia-start ln -s /etc/init.d/pcmcia-start /etc/init.d/rc3.d/S90pcmcia-start On Mon, 27 Aug 2001, Anthony Moulen wrote:
Chad Whitten Network/Systems Administrator Nexband Communications chadwick@nexband.com
Hi, I think the problem is that dhclient (dhcpcd) is started after pcmcia. If you go into the runlevel directory for the runlevel you use, for instance /etc/rc.d/rc5.d for graphical system with network and do rm S02dhclient ln -s ../dhclient S07dhclient Since pcmcia is S06 this will (hopefully) restore sanity to your system :) regards Anders On Monday 27 August 2001 21.25, Anthony Moulen wrote:
On Monday 27 August 2001 21.52, Anders Johansson wrote:
Hi,
I think the problem is that dhclient (dhcpcd) is started after pcmcia. If
Should have read 'started before', of course.
Actually, now that I look at the other links, it's probably better to move pcmcia up instead. It looks like there are other services being started in S07 that needs network, so perhaps moving pcmcia to S01 instead?! Anders
Thanks, I will give this a try. I don't think this is the problem though as trying to start the network through the SuSE tools while the system is already in run level 5 doesn't work. For some reason the tools do not detect this device and automatically kill that entry in the configuration. In other words, it would be one thing if the configuration was there and simply needed to be started, but the problem is that the configuration isn't even there. But maybe I missed something. I will move around the configuration files and see what happens. This was the problem on RedHat way back when, and something I totally forgot to consider. Anthony On Mon, 27 Aug 2001, Anders Johansson wrote:
Just a note: the rcnetwork script won't have any effect on devices that uses dhcp. That could be the reason 'starting the network' doesn't do anything. rcdhclient start, however, should work, provided the pcmcia handler is started. If not, check /etc/rc.config and make sure that IFCONFIG_1 is set to "dhcpclient" Anders On Monday 27 August 2001 22.19, Anthony Moulen wrote:
Okay, Just for anyone reading the Archives, I had to actually manually change /etc/pcmcia/network and I think /etc/pcmcia/network.opts to properly show that the card should use DHCP. I had to leave the boot order (or else everything broke) the way it was originally. After that /etc/pcmcia/network start 1, will now bring up my PCMCIA card. This is automatically called from the startup script so I don't need to do any manual tweaking. I am not sure what I would do with a Static IP but then I don't have to worry now do I? ;-). Thanks for all the help, it lead me in the right directions (made me actually read the two scripts that were involved). On Mon, 27 Aug 2001, Anders Johansson wrote:
i have run into this before. it happens because the network services are started before the pcmcia services are started. just go into /etc/init.d/rc#.d and change the order of your network and pcmcia scripts by renumbering them (change S05network to something like S75network) of course if you are running services like apache or named or something that might cause a problem. or you could just do echo "dhcpcd eth1" /etc/init.d/pcmcia-start chmod 755 /etc/init.d/pcmcia-start ln -s /etc/init.d/pcmcia-start /etc/init.d/rc3.d/S90pcmcia-start On Mon, 27 Aug 2001, Anthony Moulen wrote:
Chad Whitten Network/Systems Administrator Nexband Communications chadwick@nexband.com
participants (3)
-
Anders Johansson
-
Anthony Moulen
-
dog@intop.net