I have no encryption, and also system gone mad and i even cant connect to the net, i'm writing this mail on windows, hoping someone would help.Mywireless card is Linksys WMP54G.Hardware is present but it's not connecting.I can't configure dhcpd via Yast because it says there's a problem with config file. On 10/30/05, 'o-Dzin Tridral wrote:

On 30/10/05, Ilker wrote:

...

Hi all, I just installed OpenSUSE 10.0 on my desktop PC.I almost solved

...

and it installed my printer and scanner (wow, it made it automatically).I also managed to show my Linksys WMP54G wireless lan card.The operating system sees the card but everytime i boot into system, i have to type "dhcpcd -G http://192.168.1.1 wlan0" as root.On my last distro, i just changed the permissions as 755 and put a "script" includes that command into init.d and worked fine, but on SUSE i couldn't get it working.I even

everything tried

...

it with a suid bit but no luck.Is there any way to get it connected automatically at boot ? I don't want to use NetGO.

Dear Ilker,

In case it is of use to you, I've had this problem (or one that sounds similar). The workaround that works for me has been to disable WEP and then the wireless network comes up on boot. I'd like to go back to using WEP at some point but it's ok for now.

I hope this is helpful!

'ö-Dzin

-- 'ö-Dzin Tridral Caerdydd, Cymru www.spacious-passion.org http://www.spacious-passion.org < http://www.spacious-passion.org>

I use ndiswrapper, and it works great.The problem is although i can see my network with iwlist, i cannot cannect to it.That's the problem.I wish it has a solution... I'm going to reinstall my Suse 10.0 after combining 5cds into a dvd, i wish it'll be better. On 10/30/05, Reinhard Gimbel wrote:

Hi !

Ilker wrote a top-post :-( :

...

I have no encryption, and also system gone mad and i even cant connect to the net, i'm writing this mail on windows, hoping someone would help.Mywireless card is Linksys WMP54G.Hardware is present but it's not connecting.I can't configure dhcpd via Yast because it says there's a problem with config file.

...

On 30/10/05, Ilker wrote:

...

Hi all, I just installed OpenSUSE 10.0 on my desktop PC.I almost solved everything and it installed my printer and scanner (wow, it made it automatically).I also managed to show my Linksys WMP54G wireless lan card.The operating system sees the card but everytime i boot into system, i have to type "dhcpcd -G http://192.168.1.1 wlan0" as root.On my last distro, i just changed the permissions as 755 and put a "script" includes that command into init.d and worked fine, but on SUSE i couldn't get it working.I even

On 10/30/05, 'o-Dzin Tridral wrote: tried

...

...

it with a suid bit but no luck.Is there any way to get it connected automatically at boot ? I don't want to use NetGO.

Dear Ilker,

In case it is of use to you, I've had this problem (or one that sounds similar). The workaround that works for me has been to disable WEP and then the wireless network comes up on boot. I'd like to go back to using WEP at some point but it's ok for now.

I hope this is helpful!

'ö-Dzin

I can use the Intel PRO/wireless 2200BG which is installed in my notebook without any problem with WPA-PSK even after booting.

Are you using ndiswrapper to drive your WLAN ports ? I don't if this is related to your problems, but you should consider this in your analysis. -- Never give up !

Best regards, Reinhard.

--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org

Hi, Finally i got my connection by following this page: http://ndiswrapper.sourceforge.net/mediawiki/index.php/Installation. Let's turn back to the real problem. After every boot, i have to type "dhcpcd wlan0" as root.I just hate to do that every boot.Is there any solution ? When i write a script includes dhcpcd wlan0 and put it into directory "/etc/init.d", it doesn't work.Ithink this is because of the rights.(I also tried the absolute path, /sbin/dhcpcd wlan0) route -n: Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 http://192.168.1.0 0.0.0.0 http://0.0.0.0 255.255.255.0http://255.255.255.0U 0 0 0 wlan0 127.0.0.0 http://127.0.0.0 0.0.0.0 http://0.0.0.0 255.0.0.0http://255.0.0.0U 0 0 0 lo 0.0.0.0 http://0.0.0.0 192.168.1.1 http://192.168.1.1 0.0.0.0http://0.0.0.0UG 0 0 0 wlan0 Also, i saw "you have to write the ndiswrapper module into /etc/modprobe.conf to get it loaded ever boot."But my system seems like loading it at every boot.Is there a problem with it ?? On 10/31/05, Reinhard Gimbel wrote:

Hi !

Ilker wrote:

...

I use ndiswrapper, and it works great.The problem is although i can see my network with iwlist, i cannot cannect to it.That's the problem.I wish it has a solution... I'm going to reinstall my Suse 10.0 after combining 5cds into a dvd, i wish it'll be better.

I don't think that creating a DVD out of the 5 CD images will help to solve your problem ...

What exactly is your problem ? Can't you "see" the outside world i.e. "ping www.google.com http://www.google.com" ? Can't you "see" other devices connected to your private network ?

How about your routes ? What the command "route -n" is responding ? Is there a line starting with "0.0.0.0 http://0.0.0.0" (i.e. a default route) ? If not that might be the problem. -- Never give up !

Best regards, Reinhard.

--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org

Hi, Thanks but i just want my connection started every boot time.The command is this: dhpcpd wlan0 Where to put it ? Also, if i try to configure my card with Yast, system screws up and never connect ot the net again, thanks again to Cisco systems. On 11/1/05, Guðlaugur Jóhannesson wrote:

Ilker wrote:

...

After every boot, i have to type "dhcpcd wlan0" as root.I just hate to do that every boot.Is there any solution ?

I do not know if what I am proposing will help that situation, I will only explain what I did on my laptop to get a wlan card with ndiswrapper working.

The first thing to do is go to YaST and network devices and select network cards. There you select yout network card from the list (or create a new one if it is not detected) and click on edit. In the advanced button you can select hardware details. There you should change the module to ndiswrapper. Also in the advanced button is detailed settings where you should select start at boot time. Once that is finished you push next and you should see some selection where you can edit the ESSID and encryption key. If that is not the case, you have to remove the configuration for the device and start again from fresh. At the first page in the configuration you can select the type. Change it to wireless and follow the above steps.

-- Guðlaugur Jóhannesson http://www.hi.is/~gudlaugu Phone: +354 849 8405

--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org

On Tuesday 01 November 2005 15:43, Ilker wrote:

Hi, Thanks but i just want my connection started every boot time.The command is this:

dhpcpd wlan0

Where to put it ? Also, if i try to configure my card with Yast, system screws up and never connect ot the net again, thanks again to Cisco systems.

Hello, Here is what I did: - Create a new file /etc/init.d/dhcp with the following content #! /bin/sh # Copyright (c) # # Author: Norbert Mueller # # ### BEGIN INIT INFO # Description: My attempt on starting dhcpcd, needed because initialization # of wlan at startup did not work for me ### END INIT INFO dhcpcd_BIN=/sbin/dhcpcd dhcpcd_PARAMS="-H eth1" test -x $dhcpcd_BIN || exit 5 . /etc/rc.status rc_reset case "$1" in start) echo -n "Starting dhcpcd" $dhcpcd_BIN $dhcpcd_PARAMS rc_status -v ;; stop) echo -n "Shutting down dhcpcd " killproc -TERM $dhcpcd_BIN rc_status -v ;; *) echo "Usage: $0 {start|stop}" exit 1 ;; esac rc_exit #--------------end----------------- - Make symbolic link cd /etc/init.d/rc2.d ln -s ../dhcp S12dhcp cd /etc/init.d/rc3.d ln -s ../dhcp S12dhcp cd /etc/init.d/rc5.d ln -s ../dhcp S12dhcp HTH Norbert

On Tuesday 01 November 2005 19:14, Philipp Thomas wrote:

Norbert Müller [Tue, 1 Nov 2005 16:01:49 +0100]:

...

- Create a new file /etc/init.d/dhcp with the following content #! /bin/sh # Copyright (c) # # Author: Norbert Mueller # # ### BEGIN INIT INFO # Description: My attempt on starting dhcpcd, needed because initialization # of wlan at startup did not work for me ### END INIT INFO

- Make symbolic link cd /etc/init.d/rc2.d ln -s ../dhcp S12dhcp cd /etc/init.d/rc3.d ln -s ../dhcp S12dhcp cd /etc/init.d/rc5.d ln -s ../dhcp S12dhcp

WRONG! The next time insserv is run these links will be reset.

This is what the 'BEGIN INIT INFO' section is for. From the info given there, insserv will determine the right order to start and stop services and will set the symlinks accordingly.

See /etc/init.d/skeleton and 'man insserv' for further help how to do it correctly.

Philipp

Been there! Done that! Still working! In fact insserv renames the links from S12dhcp to S13dhcp and inserts some links with name K09dhcp. So I guess I was lucky :-) Norbert