Re: MA111 problem at boot on Fedora FC3

Karl,

Before adding the patch, the errors I got seemed to be very repeatable. I 
tried putting in a sleep of 5 and 10 seconds in place of the "disable" 
command but that did not work on my system.

I do have hald running, and during the last couple of weeks I have not 
experienced any network lockup.

I notice that the haldaemon is S98 and is the last but one service to start. 
By that time the green led light showing a connection with the AP (ME102) 
has been on for 40 seconds or more, although the linkstatus=CONNECTED 
message does not appear until just 7 seconds before the haldaemon starts.

I have two MA111s (not MA111V2) and the results do not seem to differ 
between the two cards.

Here is the sequence of events on a successful boot:

Jun  7 11:50:35 myntech network: Bringing up loopback interface:  succeeded
Jun  7 11:50:35 myntech ifup: Error for wireless request "Set Mode" (8B06) :
Jun  7 11:50:35 myntech ifup:     SET failed on device wlan0 ; Operation not 
supported.
Jun  7 11:50:35 myntech ifup: Error for wireless request "Set Frequency" 
(8B04) :
Jun  7 11:50:35 myntech ifup:     SET failed on device wlan0 ; Operation not 
supported.
Jun  7 11:50:35 myntech ifup: Error for wireless request "Set Bit Rate" 
(8B20) :
Jun  7 11:50:35 myntech ifup:     SET failed on device wlan0 ; Function not 
implemented.
Jun  7 11:50:35 myntech ifup: Error for wireless request "Set Encode" (8B2A) 
:
Jun  7 11:50:35 myntech ifup:     SET failed on device wlan0 ; Operation not 
supported.
Jun  7 11:50:35 myntech ifup: Error for wireless request "Set ESSID" (8B1A) 
:
Jun  7 11:50:35 myntech ifup:     SET failed on device wlan0 ; Operation not 
supported.
Jun  7 11:50:37 myntech network: Bringing up interface wlan0:  succeeded
..........
Jun  7 11:50:37 myntech syslog: syslogd startup succeeded
......
Jun  7 11:50:38 myntech kernel: klogd 1.4.1, log source = /proc/kmsg 
started.
Jun  7 11:50:38 myntech kernel: Linux version 2.6.11-1.14_FC3 
([email protected]) (gcc version 3.4.3 20050227 (Red Hat 
3.4.3-22)) #1 Thu Apr 7 19:23:49 EDT 2005
....
Jun  7 11:50:38 myntech syslog: klogd startup succeeded
....
Jun  7 11:51:10 myntech kernel: prism2usb_init: prism2_usb.o: 0.2.1-pre26 
Loaded

Jun  7 11:51:10 myntech kernel: prism2usb_init: dev_info is: prism2_usb
Jun  7 11:51:10 myntech kernel: usbcore: registered new driver prism2_usb
......
Jun  7 11:51:21 myntech kernel: ident: nic h/w: id=0x8026 1.0.0
Jun  7 11:51:21 myntech kernel: ident: pri f/w: id=0x15 1.1.3
Jun  7 11:51:21 myntech kernel: ident: sta f/w: id=0x1f 1.8.3
Jun  7 11:51:22 myntech kernel: MFI:SUP:role=0x00:id=0x01:var=0x01:b/t=1/1
Jun  7 11:51:22 myntech kernel: CFI:SUP:role=0x00:id=0x02:var=0x02:b/t=1/1
Jun  7 11:51:22 myntech kernel: PRI:SUP:role=0x00:id=0x03:var=0x01:b/t=1/4
Jun  7 11:51:22 myntech kernel: STA:SUP:role=0x00:id=0x04:var=0x01:b/t=1/15
Jun  7 11:51:22 myntech kernel: 
PRI-CFI:ACT:role=0x01:id=0x02:var=0x02:b/t=1/1
Jun  7 11:51:23 myntech kernel: 
STA-CFI:ACT:role=0x01:id=0x02:var=0x02:b/t=1/1
Jun  7 11:51:23 myntech kernel: 
STA-MFI:ACT:role=0x01:id=0x01:var=0x01:b/t=1/1
Jun  7 11:51:23 myntech kernel: Prism2 card SN: 
\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00
Jun  7 11:51:23 myntech kernel: linkstatus=DISCONNECTED (unhandled)
.......
Jun  7 11:51:30 myntech kernel: linkstatus=CONNECTED
.......
Jun  7 11:51:40 myntech cups-config-daemon: cups-config-daemon startup 
succeeded

Jun  7 11:51:40 myntech haldaemon: haldaemon startup succeeded



Peter

----- Original Message ----- 
From: <[email protected]>
To: "Peter Ison" <[email protected]>; 
<[email protected]>
Sent: Tuesday, June 07, 2005 9:25 AM
Subject: Re: [lwlan-user] MA111 problem at boot on Fedora FC3


> Peter
>
> In my experience, this most likely works because on
> some systems the command messages between the prism2_usb
> driver and the actual card can fail (for no very good
> reason), but often issuing a second command then succeeds.
>
> There have been many people who find that issuing
> a command like 'ifstate=enable' twice is enough to
> do the trick, because often if the first one fails,
> the second attempt does get through. Sometimes people
> have found that simply inserting a sleep of 1 second,
> e.g. after firmware upload, is enough to improve reliability
> of the card initialising - but its seems somewhat random
> and system dependant unfortunately.
>
> Now you are on FC3, and have the card coming up okay, we
> will all be interested to see if you have the network lockups some minutes 
> later that other people have had. Do you have the HAL deamon (hald) 
> running on your system?
>
> Karl
>
>>
>> From: "Peter Ison" <[email protected]>
>> Date: 2005/06/06 Mon PM 09:18:41 BST
>> To: <[email protected]>
>> Subject: [lwlan-user] MA111 problem at boot on Fedora FC3
>>
>> I am using Fedora Core 3 (kernel 2.6.11) with the wlan pre26 driver on an 
>> AMD 1200 MHz processor desktop PC, and have been having boot problems 
>> with the MA111 since the 2.6.9 kernel (and the pre 23 driver). I use WEP 
>> shared key security, and a static IP address. I leave the MA111 connected 
>> all the time.
>>
>> Previously I posted a method which entailed a loop in rc.local, removing 
>> module prism2_usb and restarting wlan repeatedly until a connection was 
>> achieved. This was slow and services which required access to LAN or 
>> internet could not connect during boot because the wlan0 interface was 
>> not yet available.
>>
>> I have found a better way, which is to patch the script /etc/wlan/shared 
>> by adding one line as follows:
>>
>> In /etc/wlan/shared
>>         wlan_enable()
>>         .......
>>         nsdname=`wlan_nsdname $1`
>>         if ! ${nsdname}_fwload $1 ; then
>>                 ${ECHO} "Firmware failed to load for device $1"
>>                 return 1
>>         fi
>>         # Enable the interface
>>         # ADD THE FOLLOWING LINE
>>         $WLANCTL $1 lnxreq_ifstate ifstate=disable
>>         result=`$WLANCTL $1 lnxreq_ifstate ifstate=enable`
>>
>> The patched file /etc/wlan/shared is called by /etc/hotplug/wlan.agent 
>> and also by /etc/init.d/wlan.
>>
>> I am not sure why this works, except that before the patch the result of 
>> the "wlanctl-ng  wlan0 lnxreq_ifstate ifstate=enable" in the above script 
>> was "implementation failure" as shown below:
>> Jun  6 21:04:09 myntech kernel: hfa384x_docmd: ctlx failure=REQ_FAILED
>> Jun  6 21:04:09 myntech wlan.agent[19532]: Failed to enable the device, 
>> resultcode= implementation_failure .
>> Jun  6 21:04:09 myntech wlan.agent[19532]: WLAN Could not bring up wlan0
>> Jun  6 21:04:09 myntech kernel: hfa384x_drvr_start: cmd_initialize() 
>> failed, result=-5
>> Jun  6 21:04:09 myntech kernel: prism2sta_ifstate: hfa384x_drvr_start() 
>> failed,result=-5
>>
>>
>> After the patch the wlan0 interface is now stable, and trouble-free.
>>
>> I notice that after un-plugging and re-plugging, sometimes the network 
>> routing table entries get lost. To get going again I must do the 
>> following:
>>
>> service wlan restart
>> service network restart
>>
>> and the link and network are restored.
>>
>> Peter Ison
>>
>>
>
> -----------------------------------------
> Email provided by http://www.ntlhome.com/
>