Re: [opensuse] KNETWORK MANAGER PROBLEM PLS HELP

newer
Re: [opensuse] Possible bug in...

older
[opensuse] xfs_check64?

Helmut Schaa

2 Jul 2008 2 Jul '08

15:12

Am Mittwoch, 2. Juli 2008 16:51:29 schrieb Jide Ogunmekan:

...

Pls find my iwlist scan

Thanks.

...

Encryption key:off

So, the AP uses no encryption. Does the wireless connection succeed if you use the commandline method (see [1] for an explanation)? Helmut [1] http://en.opensuse.org/Tracking_down_wireless_problems -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Show replies by date

Jide Ogunmekan

2 Jul 2 Jul

16:50

New subject: [opensuse] KNETWORK MANAGER PROBLEM PLS HELP

Helmut Schaa wrote:

...

Am Mittwoch, 2. Juli 2008 16:51:29 schrieb Jide Ogunmekan:

...
Pls find my iwlist scan

Thanks.

...
Encryption key:off

So, the AP uses no encryption. Does the wireless connection succeed if you use the commandline method (see [1] for an explanation)?

Helmut

[1] http://en.opensuse.org/Tracking_down_wireless_problems

I used the commandline method which works ok. Jide -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Helmut Schaa

3 Jul 3 Jul

05:12

New subject: [opensuse] KNETWORK MANAGER PROBLEM PLS HELP

Am Mi 02 Jul 2008 18:50:15 CEST schrieb Jide Ogunmekan :

...

...
...
Encryption key:off

So, the AP uses no encryption. Does the wireless connection succeed if you use the commandline method (see [1] for an explanation)?

I used the commandline method which works ok.

Hmm, could you please try to create a new connection in KNetworkManager, start a connection attempt and if it fails attach /var/log/NetworkManager? Helmut -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Jide Ogunmekan

12:26

New subject: [opensuse] KNETWORK MANAGER PROBLEM PLS HELP

Helmut Schaa wrote:

...

Am Mi 02 Jul 2008 18:50:15 CEST schrieb Jide Ogunmekan :

...
...
...
Encryption key:off

So, the AP uses no encryption. Does the wireless connection succeed if you use the commandline method (see [1] for an explanation)?

I used the commandline method which works ok.

Hmm, could you please try to create a new connection in KNetworkManager, start a connection attempt and if it fails attach /var/log/NetworkManager?

Helmut

Thanks I started a new connection in KnetworkManger and it failed. Here is my log for the session: Jul 3 13:19:53 jide NetworkManager: <info> starting... Jul 3 13:19:53 jide NetworkManager: <info> Found radio killswitch /org/freedesktop/Hal/devices/dell_wlan_switch Jul 3 13:19:53 jide NetworkManager: <info> eth0: Device is fully-supported using driver 'b44'. Jul 3 13:19:53 jide NetworkManager: <info> Found new Ethernet device 'eth0'. Jul 3 13:19:53 jide NetworkManager: <info> (eth0): exported as /org/freedesktop/Hal/devices/net_00_1c_23_8b_32_b7 Jul 3 13:19:53 jide NetworkManager: <info> wlan0: Device is fully-supported using driver 'b43-pci-bridge'. Jul 3 13:19:53 jide NetworkManager: <info> wlan0: driver supports SSID scans (scan_capa 0x01). Jul 3 13:19:53 jide NetworkManager: <info> Found new wireless (802.11) device 'wlan0'. Jul 3 13:19:53 jide NetworkManager: <info> (wlan0): exported as /org/freedesktop/Hal/devices/net_00_1c_26_2c_8f_3c Jul 3 13:19:53 jide NetworkManager: <info> Trying to start the supplicant... Jul 3 13:19:53 jide NetworkManager: <info> Trying to start the system settings daemon... Jul 3 13:19:54 jide NetworkManager: <WARN> nm_signal_handler(): Caught signal 15, shutting down normally. Jul 3 13:19:54 jide NetworkManager: <info> (eth0): now unmanaged Jul 3 13:19:54 jide NetworkManager: <info> (wlan0): now unmanaged Jul 3 13:19:55 jide NetworkManager: <info> starting... Jul 3 13:19:55 jide NetworkManager: <info> Found radio killswitch /org/freedesktop/Hal/devices/dell_wlan_switch Jul 3 13:19:55 jide NetworkManager: <info> eth0: Device is fully-supported using driver 'b44'. Jul 3 13:19:55 jide NetworkManager: <info> Found new Ethernet device 'eth0'. Jul 3 13:19:55 jide NetworkManager: <info> (eth0): exported as /org/freedesktop/Hal/devices/net_00_1c_23_8b_32_b7 Jul 3 13:19:55 jide NetworkManager: <info> wlan0: Device is fully-supported using driver 'b43-pci-bridge'. Jul 3 13:19:55 jide NetworkManager: <info> wlan0: driver supports SSID scans (scan_capa 0x01). Jul 3 13:19:55 jide NetworkManager: <info> Found new wireless (802.11) device 'wlan0'. Jul 3 13:19:55 jide NetworkManager: <info> (wlan0): exported as /org/freedesktop/Hal/devices/net_00_1c_26_2c_8f_3c Jul 3 13:19:59 jide NetworkManager: <info> (eth0): device state change: 1 -> 2 Jul 3 13:19:59 jide NetworkManager: <info> (eth0): bringing up device. Jul 3 13:19:59 jide NetworkManager: <info> (eth0): preparing device. Jul 3 13:19:59 jide NetworkManager: <info> (eth0): deactivating device. Jul 3 13:19:59 jide NetworkManager: <info> (wlan0): device state change: 1 -> 2 Jul 3 13:19:59 jide NetworkManager: <info> (wlan0): bringing up device. Jul 3 13:20:01 jide NetworkManager: <info> (wlan0): preparing device. Jul 3 13:20:01 jide NetworkManager: <info> (wlan0): deactivating device. Jul 3 13:20:01 jide NetworkManager: <info> (wlan0): device state change: 2 -> 3 Jul 3 13:20:01 jide NetworkManager: <info> (wlan0): supplicant interface state change: 1 -> 2. Jul 3 13:20:01 jide NetworkManager: <WARN> killswitch_getpower_reply(): Error getting killswitch power: dellWirelessCtl (/usr/bin/dellWirelessCtl) not available or executable. Jul 3 13:20:33 jide NetworkManager: <info> Activation (wlan0) starting connection 'officeap' Jul 3 13:20:33 jide NetworkManager: <info> (wlan0): device state change: 3 -> 4 Jul 3 13:20:33 jide NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Jul 3 13:20:33 jide NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Jul 3 13:20:33 jide NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Jul 3 13:20:33 jide NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Jul 3 13:20:33 jide NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Jul 3 13:20:33 jide NetworkManager: <info> (wlan0): device state change: 4 -> 5 Jul 3 13:20:33 jide NetworkManager: <info> Activation (wlan0/wireless): connection 'officeap' requires no security. No secrets needed. Jul 3 13:20:33 jide NetworkManager: <info> Config: added 'ssid' value 'officeap' Jul 3 13:20:33 jide NetworkManager: <info> Config: added 'scan_ssid' value '1' Jul 3 13:20:33 jide NetworkManager: <info> Config: added 'key_mgmt' value 'NONE' Jul 3 13:20:33 jide NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Jul 3 13:20:33 jide NetworkManager: <info> Config: set interface ap_scan to 1 Jul 3 13:20:33 jide NetworkManager: <info> (wlan0): supplicant connection state change: 1 -> 2 Jul 3 13:20:33 jide NetworkManager: <info> (wlan0): supplicant connection state change: 2 -> 3 Jul 3 13:20:33 jide NetworkManager: <info> (wlan0): supplicant connection state change: 3 -> 4 Jul 3 13:20:33 jide NetworkManager: <info> (wlan0): supplicant connection state change: 4 -> 7 Jul 3 13:20:33 jide NetworkManager: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'officeap'. Jul 3 13:20:33 jide NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled. Jul 3 13:20:33 jide NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started... Jul 3 13:20:33 jide NetworkManager: <info> (wlan0): device state change: 5 -> 7 Jul 3 13:20:33 jide NetworkManager: <info> Activation (wlan0) Beginning DHCP transaction. Jul 3 13:20:33 jide NetworkManager: <info> dhclient started with pid 9407 Jul 3 13:20:33 jide NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete. Jul 3 13:20:34 jide NetworkManager: <info> DHCP: device wlan0 state changed (null) -> preinit Jul 3 13:21:18 jide NetworkManager: <info> Device 'wlan0' DHCP transaction took too long (>45s), stopping it. Jul 3 13:21:18 jide NetworkManager: <info> wlan0: canceled DHCP transaction, dhclient pid 9407 Jul 3 13:21:18 jide NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) scheduled... Jul 3 13:21:18 jide NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) started... Jul 3 13:21:18 jide NetworkManager: <info> (wlan0): device state change: 7 -> 9 Jul 3 13:21:18 jide NetworkManager: <info> Activation (wlan0) failed for access point (officeap) Jul 3 13:21:18 jide NetworkManager: <info> Marking connection 'officeap' invalid. Jul 3 13:21:18 jide NetworkManager: <info> Activation (wlan0) failed. Jul 3 13:21:18 jide NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) complete. Jul 3 13:21:18 jide NetworkManager: <info> (wlan0): device state change: 9 -> 3 Jul 3 13:21:18 jide NetworkManager: <info> (wlan0): deactivating device. Jul 3 13:21:18 jide NetworkManager: <info> Activation (wlan0) starting connection 'officeap' Jul 3 13:21:18 jide NetworkManager: <info> (wlan0): device state change: 3 -> 4 Jul 3 13:21:18 jide NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Jul 3 13:21:18 jide NetworkManager: <info> (wlan0): supplicant connection state change: 7 -> 0 Jul 3 13:21:18 jide NetworkManager: <info> (wlan0): supplicant connection state change: 0 -> 4 Jul 3 13:21:18 jide NetworkManager: <info> (wlan0): supplicant connection state change: 4 -> 0 Jul 3 13:21:18 jide NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Jul 3 13:21:18 jide NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Jul 3 13:21:18 jide NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Jul 3 13:21:18 jide NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Jul 3 13:21:18 jide NetworkManager: <info> (wlan0): device state change: 4 -> 5 Jul 3 13:21:18 jide NetworkManager: <info> Activation (wlan0/wireless): connection 'officeap' requires no security. No secrets needed. Jul 3 13:21:18 jide NetworkManager: <info> Config: added 'ssid' value 'officeap' Jul 3 13:21:18 jide NetworkManager: <info> Config: added 'scan_ssid' value '1' Jul 3 13:21:18 jide NetworkManager: <info> Config: added 'key_mgmt' value 'NONE' Jul 3 13:21:18 jide NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Jul 3 13:21:18 jide NetworkManager: <info> Config: set interface ap_scan to 1 Jul 3 13:21:18 jide NetworkManager: <info> (wlan0): supplicant connection state change: 0 -> 2 Jul 3 13:21:19 jide NetworkManager: <info> (wlan0): supplicant connection state change: 2 -> 3 Jul 3 13:21:19 jide NetworkManager: <info> (wlan0): supplicant connection state change: 3 -> 4 Jul 3 13:21:19 jide NetworkManager: <info> (wlan0): supplicant connection state change: 4 -> 7 Jul 3 13:21:19 jide NetworkManager: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'officeap'. Jul 3 13:21:19 jide NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled. Jul 3 13:21:19 jide NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started... Jul 3 13:21:19 jide NetworkManager: <info> (wlan0): device state change: 5 -> 7 Jul 3 13:21:19 jide NetworkManager: <info> Activation (wlan0) Beginning DHCP transaction. Jul 3 13:21:19 jide NetworkManager: <info> dhclient started with pid 9450 Jul 3 13:21:19 jide NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete. Jul 3 13:21:19 jide NetworkManager: <info> DHCP: device wlan0 state changed normal exit -> preinit Jul 3 13:22:04 jide NetworkManager: <info> Device 'wlan0' DHCP transaction took too long (>45s), stopping it. Jul 3 13:22:04 jide NetworkManager: <info> wlan0: canceled DHCP transaction, dhclient pid 9450 Jul 3 13:22:04 jide NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) scheduled... Jul 3 13:22:04 jide NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) started... Jul 3 13:22:04 jide NetworkManager: <info> (wlan0): device state change: 7 -> 9 Jul 3 13:22:04 jide NetworkManager: <info> Activation (wlan0) failed for access point (officeap) Jul 3 13:22:04 jide NetworkManager: <info> Marking connection 'officeap' invalid. Jul 3 13:22:04 jide NetworkManager: <info> Activation (wlan0) failed. Jul 3 13:22:04 jide NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) complete. Jul 3 13:22:04 jide NetworkManager: <info> (wlan0): device state change: 9 -> 3 Jul 3 13:22:04 jide NetworkManager: <info> (wlan0): deactivating device. Jide -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Helmut Schaa

4 Jul 4 Jul

11:45

New subject: [opensuse] KNETWORK MANAGER PROBLEM PLS HELP

Am Donnerstag, 3. Juli 2008 14:26:24 schrieb Jide Ogunmekan:

...

Helmut Schaa wrote:

...
Am Mi 02 Jul 2008 18:50:15 CEST schrieb Jide Ogunmekan :

...
...
...
Encryption key:off

So, the AP uses no encryption. Does the wireless connection succeed if you use the commandline method (see [1] for an explanation)?

I used the commandline method which works ok.

Hmm, could you please try to create a new connection in KNetworkManager, start a connection attempt and if it fails attach /var/log/NetworkManager?

I started a new connection in KnetworkManger and it failed. Here is my log for the session: Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'officeap'.

The wireless connection is set up correctly here.

...

Jul 3 13:21:18 jide NetworkManager: <info> Device 'wlan0' DHCP transaction took too long (>45s), stopping it.

DHCP failed. Does DHCP works fine from the commandline? Maybe you ran into bug #402575 (see [1]). Helmut [1] https://bugzilla.novell.com/show_bug.cgi?id=402575 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Jide Ogunmekan

8 Jul 8 Jul

10:02

New subject: [opensuse] KNETWORK MANAGER PROBLEM PLS HELP

Helmut Schaa wrote:

...

Am Donnerstag, 3. Juli 2008 14:26:24 schrieb Jide Ogunmekan:

...
Helmut Schaa wrote:

...
Am Mi 02 Jul 2008 18:50:15 CEST schrieb Jide Ogunmekan :

...
...
...
Encryption key:off So, the AP uses no encryption. Does the wireless connection succeed if you use the commandline method (see [1] for an explanation)? I used the commandline method which works ok. Hmm, could you please try to create a new connection in KNetworkManager, start a connection attempt and if it fails attach /var/log/NetworkManager? I started a new connection in KnetworkManger and it failed. Here is my log for the session: Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'officeap'.

The wireless connection is set up correctly here.

...
Jul 3 13:21:18 jide NetworkManager: <info> Device 'wlan0' DHCP transaction took too long (>45s), stopping it.

DHCP failed. Does DHCP works fine from the commandline? Maybe you ran into bug #402575 (see [1]).

Helmut

[1] https://bugzilla.novell.com/show_bug.cgi?id=402575

It is possible this bug might be responsible. Could you pls advise how to work around this. Thanks Jide -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Jide Ogunmekan

9 Jul 9 Jul

11:30

New subject: [opensuse] KNETWORK MANAGER PROBLEM PLS HELP

Helmut Schaa wrote:

...

Am Donnerstag, 3. Juli 2008 14:26:24 schrieb Jide Ogunmekan:

...
Helmut Schaa wrote:

...
Am Mi 02 Jul 2008 18:50:15 CEST schrieb Jide Ogunmekan :

...
...
...
Encryption key:off So, the AP uses no encryption. Does the wireless connection succeed if you use the commandline method (see [1] for an explanation)? I used the commandline method which works ok. Hmm, could you please try to create a new connection in KNetworkManager, start a connection attempt and if it fails attach /var/log/NetworkManager? I started a new connection in KnetworkManger and it failed. Here is my log for the session: Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'officeap'.

The wireless connection is set up correctly here.

...
Jul 3 13:21:18 jide NetworkManager: <info> Device 'wlan0' DHCP transaction took too long (>45s), stopping it.

DHCP failed. Does DHCP works fine from the commandline? Maybe you ran into bug #402575 (see [1]).

Helmut

[1] https://bugzilla.novell.com/show_bug.cgi?id=402575

Helmut Schaa

12:03

New subject: [opensuse] KNETWORK MANAGER PROBLEM PLS HELP

Am Mi 09 Jul 2008 13:30:31 CEST schrieb Jide Ogunmekan :

...

Helmut Schaa wrote:

...
Am Donnerstag, 3. Juli 2008 14:26:24 schrieb Jide Ogunmekan:

...
Helmut Schaa wrote:

...
Am Mi 02 Jul 2008 18:50:15 CEST schrieb Jide Ogunmekan :

...
...
> Encryption key:off So, the AP uses no encryption. Does the wireless connection succeed if you use the commandline method (see [1] for an explanation)? I used the commandline method which works ok. Hmm, could you please try to create a new connection in KNetworkManager, start a connection attempt and if it fails attach /var/log/NetworkManager? I started a new connection in KnetworkManger and it failed. Here is my log for the session: Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'officeap'.

The wireless connection is set up correctly here.

...
Jul 3 13:21:18 jide NetworkManager: <info> Device 'wlan0' DHCP transaction took too long (>45s), stopping it.

DHCP failed. Does DHCP works fine from the commandline? Maybe you ran into bug #402575 (see [1]).

Helmut

[1] https://bugzilla.novell.com/show_bug.cgi?id=402575

It is possible this bug might be responsible. Could you pls advise how to work around this.

DHCP from the commandline worked fine? I'm not yet aware of a possible workaround for this issue. Helmut -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

medwinz

12:49

New subject: [opensuse] KNETWORK MANAGER PROBLEM PLS HELP

On Wed, Jul 9, 2008 at 7:03 PM, Helmut Schaa wrote:

...

...
...
[1] https://bugzilla.novell.com/show_bug.cgi?id=402575

It is possible this bug might be responsible. Could you pls advise how to work around this.

DHCP from the commandline worked fine? I'm not yet aware of a possible workaround for this issue.

Helmut --

Jide, I know that "something happened" on wifi connection on 11, it is not reliable as 10.3 did. It happens also here with my intel iwl3945. In my case the dirty workaround is i restarted the iwl3945 # modprobe -r iwl3945 # modprobe iwl3945 In my case, kismet also don't want to capture the traffic until i use the compat-wireless driver from http://linuxwireless.org/en/users/Download. I don't know why, but for the time being seem to me that the address is broken. medwinz -- EB White - "Be obscure clearly." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Joe Morris

13:10

New subject: [opensuse] KNETWORK MANAGER PROBLEM PLS HELP

On 07/09/2008 08:49 PM, medwinz wrote:

...

In my case, kismet also don't want to capture the traffic until i use the compat-wireless driver from http://linuxwireless.org/en/users/Download. I don't know why, but for the time being seem to me that the address is broken.

Have you tried the rpm packages from the BS in http://download.opensuse.org/repositories/home:/schmolle1980/openSUSE_11.0_U... I just thought they might be better to use as they are specifically for opensuse. -- Joe Morris Registered Linux user 231871 running openSUSE 10.3 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

medwinz

15:58

New subject: [opensuse] KNETWORK MANAGER PROBLEM PLS HELP

On Wed, Jul 9, 2008 at 8:10 PM, Joe Morris wrote:

...

On 07/09/2008 08:49 PM, medwinz wrote:

...
In my case, kismet also don't want to capture the traffic until i use the compat-wireless driver from http://linuxwireless.org/en/users/Download. I don't know why, but for the time being seem to me that the address is broken.

Have you tried the rpm packages from the BS in http://download.opensuse.org/repositories/home:/schmolle1980/openSUSE_11.0_U... I just thought they might be better to use as they are specifically for opensuse.

--

Never tried the BS version. I think your point is make sense. Problem is kernel version. I check it and the compat-wireless driver is for kernel 2.6.25.5-1.1, mine is 2.6.25.9-0.2. Anyway I think it is worth for Jide to try it. I read on the README that broadcom also supported by this driver. So Jide please go to webpin ( http://packages.opensuse-community.org/index.jsp?searchTerm=compat-wireless&distro=openSUSE_110 ) and do one click install. See what will happen. Worth to try :) medwinz -- George Burns - "Don't stay in bed, unless you can make money in bed." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Jide Ogunmekan

15 Jul 15 Jul

14:25

New subject: [opensuse] KNETWORK MANAGER PROBLEM PLS HELP

medwinz wrote:

...

On Wed, Jul 9, 2008 at 8:10 PM, Joe Morris wrote:

...
On 07/09/2008 08:49 PM, medwinz wrote:

...
In my case, kismet also don't want to capture the traffic until i use the compat-wireless driver from http://linuxwireless.org/en/users/Download. I don't know why, but for the time being seem to me that the address is broken.

Have you tried the rpm packages from the BS in http://download.opensuse.org/repositories/home:/schmolle1980/openSUSE_11.0_U... I just thought they might be better to use as they are specifically for opensuse.

--

Never tried the BS version. I think your point is make sense. Problem is kernel version. I check it and the compat-wireless driver is for kernel 2.6.25.5-1.1, mine is 2.6.25.9-0.2. Anyway I think it is worth for Jide to try it. I read on the README that broadcom also supported by this driver. So Jide please go to webpin ( http://packages.opensuse-community.org/index.jsp?searchTerm=compat-wireless&distro=openSUSE_110 ) and do one click install. See what will happen.

Worth to try :)

medwinz

Hi I downloaded the packages and installed them, but still have the same situation. I have resigned myself to using the command line which works well. At home is not a problem, knetworkmanager works well with my wireless router, but in my office i simply run /etc/init.d/network restart and I am running smoothly. Thanks everyone for your help, I do hope a fix will happen soon for knetworkmanager, wish i could write it myself too! :D Jide -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Mike McMullin

3 Jul 3 Jul

06:15

New subject: [opensuse] KNETWORK MANAGER PROBLEM PLS HELP

On Wed, 2008-07-02 at 17:12 +0200, Helmut Schaa wrote:

...

Am Mittwoch, 2. Juli 2008 16:51:29 schrieb Jide Ogunmekan:

...
Pls find my iwlist scan

Thanks.

...
Encryption key:off

So, the AP uses no encryption. Does the wireless connection succeed if you use the commandline method (see [1] for an explanation)?

Helmut

[1] http://en.opensuse.org/Tracking_down_wireless_problems

Thank You, I have now solved my wonky Wireless Problems under 11.0 with an atheros card. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

5774

Age (days ago)

5787

Last active (days ago)

List overview

Download

12 comments

5 participants

participants (5)

Helmut Schaa
Jide Ogunmekan
Joe Morris
medwinz
Mike McMullin