Arjen Runsink wrote:
ds wrote:
BI installed SuSE 6.2 on my Compaq Armada 7800 Laptop also. I am having BIG problems going from my Ethernet network at work to my Ethernet network here at home. Everytime it starts up, there is no networking and as of this morning, my Eth0 interface is gone. Yast says it is still there, but ifconfig says it doesn't exist.
1. What is CardCtl? Where do you get it? Is it a package that is with the distribution? 2. When I change networks, you can use Yast to make network changes, but it doesn't re-start the network with the new changes. What do I execute to get SuSE to except my changes?
I too have an ARMADA 7800 and am running SuSE 62 without a problem.
First do not configure the network via Yast and remove all ethernet devices from it. You should in install the PCMCIA package and edit the network config in /etc/pcmcia/network.opts
If you use DHCP make sure you have IPADDR="" or else it interferes. I have DHCP in the office and at home. I can just take out the PCMCIA, hibernate and then put it back in at home and continue. No swea at all.
BTW to have PCMCIA services working better compile APM in the kernel and download and compile latest PCMCIA package. for some reason APM support is not compiled with the SuSE package ??? At least with 6.2 it isn't.
BB, Arjen
Hello Everybody, reading this thread, I started to think how to boot up different Hardware or Network configs, particulary with labtops and wether there is something like that in linux. I am either reinventing the wheel or more likely inventing a way to rape the system IV boot concept and of course SuSE's boot concept ;-). Basicly, there are two runlevels "unused" by SuSE: 4 and 5. These could be used for different HW configs (or Network "work", network "home") 1) booting: on bootup type "linux 4" to boot into your "home" config. I guess, this parameter can be passed on by lilo, so requiring an extra entry in lilo.conf 2) change inittab this requires uncommenting one line for init 4 or init 5. The parameter for the runlevel is given on to /sbin/init.d/rc as $1, it should be saved for further use in the init scripts. 3) prepare your runlevel copy all links from your "normal" runlevel (/sbin/init.d/rcX.d) to your new runlevel. Booting now woldn't do any change. But if you... 4) tailor the "different" scripts OK, lets speak of a different network, OK? You'd need to change the .../rc4.d/S05network that aktually points to /sbin/init.d/network. To be able to master two choices: create a /etc/rc.config.d/my.rc.config and cut and paste the nessesarry vars from rc.config to there and edit them to your needs 4) Modifiing the system IV scripts (/sbin/init.d/*) All scripts start like . /etc/rc.config This means, all vars from rc.config get set. if you place a . /etc/rc.config.d/my.rc.config *afterwards* your vars win. ;-) This points to solution 4a) copy network to mynetwork, add the above line and let the link from your newly created runlevel point there. There is a elite solution 4b ;-)) if it's possible (OK all stuff is called from the rc script and a simple DES_LEVEL=$1;export DES_LEVEL could do it) to access the desired level you could: . /etc/rc.config ... if test "$DES_LEVEL" = "4"; then . /etc/rc.config.d/my.rc.config fi With that, you'd change the original bootscript file according to your needs. Other scripts that might be affected as well could be handled accordingly. Btw. there are runlevels 7,8,9 as well (in theory, but noone bothered yet) Suggestions? (flames to /dev/null please) Juergen -- =========================================== __ _ Juergen Braukmann juergen.braukmann@gmx.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | /\\ /__/ / _ \/ // /\ \/ / ===========================================_\_v __/_/_//_/\_,_/ /_/\_\ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/