Wireless connection in 7.0

Post your comments, questions, bug reports or suggest new features for alphaOS
Marv
Proficient
Posts: 81
Joined: 16 May 2013, 16:42

Wireless connection in 7.0

Postby Marv » 22 May 2013, 23:25

In 7.0, not in 6.0 or earlier, on a reboot, in order to reconnect or when first connecting with Pwireless2, I need to restart the wpa_supplicant, either using the button in the debug tab of Pwireless2 or directly executing /usr/local/Pwireless2/reset-wpa &. If I put that line in /root/.start, It comes up flawlessly every time. Pwireless2 in /etc/init.d and in the daemons line of rc.conf in /etc. exactly as in the 7.0 iso. Seems position independent in the daemons line. I've only run 7.0 on the 1.6G Pentium M laptop so it could be a timing issue but on that machine anyway it is totally consistant. Anyone else see this? Clue is not seeing any networks in Pwireless2 GUI until you go to the debug tab, restart wpa supplicant and refresh. Then connection is normal.

john3voltas
Expert
Posts: 266
Joined: 19 May 2013, 21:53

Re: Wireless connection in 7.0

Postby john3voltas » 23 May 2013, 11:40

Unfortunately in my case it still does not work.
I am running the 22/05 build of 7.0 and even if I restart wpa_supplicant and hit the refresh button I still don't see any wireless networks.
Big bummer :(

Here's Pwireless2 log after having reset wpa_supplicant:

Code: Select all

wpa_supplicant v2.0
Successfully initialized wpa_supplicant
Initializing interface 'wlan0' conf '/usr/local/Pwireless2/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/usr/local/Pwireless2/wpa_supplicant.conf' -> '/usr/local/Pwireless2/wpa_supplicant.conf'
Reading configuration file '/usr/local/Pwireless2/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
update_config=1
WEXT: cfg80211-based driver detected
wext: interface wlan0 phy: phy0
rfkill: initial event: idx=0 type=1 op=0 soft=1 hard=0
rfkill: WLAN soft blocked
rfkill: initial event: idx=1 type=2 op=0 soft=1 hard=0
rfkill: initial event: idx=2 type=1 op=0 soft=0 hard=1
rfkill: WLAN hard blocked
rfkill: initial event: idx=4 type=6 op=0 soft=1 hard=1
Could not set interface wlan0 flags (UP): Operation not possible due to RF-kill
WEXT: Could not yet enable interface 'wlan0' due to rfkill
SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf
  capabilities: key_mgmt 0xf enc 0x1f flags 0x0
netlink: Operstate: linkmode=1, operstate=5
wlan0: Own MAC address: 00:18:de:b8:5a:2b
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wlan0: RSN: flushing PMKID list in the driver
wlan0: State: DISCONNECTED -> INACTIVE
WPS: Set UUID for interface wlan0
WPS: UUID based on MAC address - hexdump(len=16): df 97 1e 24 e9 e2 56 1b b6 95 6e 65 71 b5 be 63
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: Supplicant port status: Unauthorized
EAPOL: Supplicant port status: Unauthorized
wlan0: Added interface wlan0
wlan0: State: INACTIVE -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
wlan0: Event INTERFACE_DISABLED (30) received
wlan0: Interface was disabled
wlan0: State: DISCONNECTED -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portValid=0
EAPOL: Supplicant port status: Unauthorized
wlan0: State: DISCONNECTED -> INTERFACE_DISABLED
RTM_NEWLINK: operstate=0 ifi_flags=0x1002 ()
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
WEXT: if_removed already cleared - ignore event
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1002 ()
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
WEXT: if_removed already cleared - ignore event
Wireless event: cmd=0x8b1a len=8
l2_packet_receive - recvfrom: Network is down
EAPOL: disable timer tick
EAPOL: Supplicant port status: Unauthorized
RX ctrl_iface - hexdump_ascii(len=4):
     53 43 41 4e                                       SCAN           
wlan0: Control interface command 'SCAN'
RX ctrl_iface - hexdump_ascii(len=4):
     53 43 41 4e                                       SCAN           
wlan0: Control interface command 'SCAN'
RX ctrl_iface - hexdump_ascii(len=12):
     53 43 41 4e 5f 52 45 53 55 4c 54 53               SCAN_RESULTS   
wlan0: Control interface command 'SCAN_RESULTS'
RX ctrl_iface - hexdump_ascii(len=6):
     53 54 41 54 55 53                                 STATUS         
wlan0: Control interface command 'STATUS'
RX ctrl_iface - hexdump_ascii(len=6):
     53 54 41 54 55 53                                 STATUS         
wlan0: Control interface command 'STATUS'
CTRL_IFACE monitor attached - hexdump(len=21): 2f 74 6d 70 2f 77 70 61 5f 63 74 72 6c 5f 31 38 30 31 2d 31 00
RX ctrl_iface - hexdump_ascii(len=4):
     53 43 41 4e                                       SCAN           
wlan0: Control interface command 'SCAN'
RX ctrl_iface - hexdump_ascii(len=4):
     53 43 41 4e                                       SCAN           
wlan0: Control interface command 'SCAN'
RX ctrl_iface - hexdump_ascii(len=12):
     53 43 41 4e 5f 52 45 53 55 4c 54 53               SCAN_RESULTS   
wlan0: Control interface command 'SCAN_RESULTS'
RX ctrl_iface - hexdump_ascii(len=6):
     53 54 41 54 55 53                                 STATUS         
wlan0: Control interface command 'STATUS'
RX ctrl_iface - hexdump_ascii(len=6):
     53 54 41 54 55 53                                 STATUS         
wlan0: Control interface command 'STATUS'


And this is what shows when I push the wireless/bluetooth button on my laptop (which is lit off):

Code: Select all

rfkill: event: idx=0 type=1 op=2 soft=1 hard=1
rfkill: WLAN hard blocked
rfkill: event: idx=1 type=2 op=2 soft=1 hard=1

Notice the soft=1 and hard=1? Does this mean that it is now hard locked?

Now this is when I push the same button again (still does not lit up)

Code: Select all

rfkill: event: idx=0 type=1 op=2 soft=1 hard=0
rfkill: WLAN soft blocked
rfkill: event: idx=1 type=2 op=2 soft=1 hard=0

Now soft=1 and hard=0. Does that mean that hardlock is cleared and that it should be able to find wireless networks?
What exactly is a soft block and how to remove it?
TIA
Cheers

john3voltas
Expert
Posts: 266
Joined: 19 May 2013, 21:53

Re: Wireless connection in 7.0

Postby john3voltas » 24 May 2013, 21:56

Anyone's got any hint why my wireless won't work as per my above post?
Cheers

john3voltas
Expert
Posts: 266
Joined: 19 May 2013, 21:53

Re: Wireless connection in 7.0

Postby john3voltas » 26 May 2013, 12:02

Come on guys, I really need a hand here.
Restarting wpa_supplicant doesn't do the trick for me :(
Cheers

Marv
Proficient
Posts: 81
Joined: 16 May 2013, 16:42

Re: Wireless connection in 7.0

Postby Marv » 26 May 2013, 15:45

Sorry John, I've rolled back to my patched 6.0 version for now. I got printing and wireless working in 7.0 but neither was anywhere as reliable or polished as that in the last ver of 6.0 and I had no problems coming up with all the packages I use daily. Kernel is still pretty much up to date as are packages. lina/Carolina is still my main working system with alphaOS 6.0 a close second. In both cases stability and reliability seems to trump bleeding edge.

Ya, forgot to mention the numlock. I've gotten pretty facile editing that line in .start. ;)

Jim

john3voltas
Expert
Posts: 266
Joined: 19 May 2013, 21:53

Re: Wireless connection in 7.0

Postby john3voltas » 26 May 2013, 17:33

Hi Marv.
Thanks for the reply.
Numlock I never thought it would be a .start line just needing me to edit it.
7.0 doesn't seem to be quite as stable as earlier releases, huh?
Hmmm, I wouldn't mind using the older 5/6 LFS approach releases. I was even getting pretty well used to spkg.
Heck, I wouldn't even mind to run old ArchPup just to test some features like wifi and stuff like that.
I just don't know where to get any of these older releases... :?
There is no arguing that alphaOS is going to be my OS of choice. It just isn't right now already because of some wifi issues and cpu temperature issues.
I'm not missing anything else other than that.

john3voltas
Expert
Posts: 266
Joined: 19 May 2013, 21:53

Re: Wireless connection in 7.0

Postby john3voltas » 27 May 2013, 18:09

Still trying to fight this.
Just tried alphaOS 4, 5, 6 and even archpup 13.2 and none of them had this issue.
simargl: help! :D
Cheers

simargl
Site Admin
Posts: 466
Joined: 16 May 2013, 10:54
Contact:

Re: Wireless connection in 7.0

Postby simargl » 27 May 2013, 19:53

I'm just guessing, but let's say two things might be problem: first wpa_supplicant was upgraded to version 2.0 in Arch repository and in latest alphaos (version 1.0 was used in ArchPup and all earlier alphaOS versions), 2nd maybe this kernel is too new for some wireless firmware files.

john3voltas
Expert
Posts: 266
Joined: 19 May 2013, 21:53

Re: Wireless connection in 7.0

Postby john3voltas » 27 May 2013, 20:35

Aha! Now I'm starting to get it.
This makes me ask for the impossible (that I already asked in the announcements thread): would you teach me/us build alphaOS from scratch as if you were explaining it to a 6yo child :mrgreen: ?
That way I would try to compile a 3.4 kernel and see if that cures my cpu temp+fan speed and also my wifi issues.
I'm just dreaming here with a nice guide in the wiki ;)
Cheers

lvds
Apprentice
Posts: 6
Joined: 22 May 2013, 08:44

Re: Wireless connection in 7.0

Postby lvds » 30 May 2013, 08:15

john3voltas wrote:Aha! Now I'm starting to get it.
This makes me ask for the impossible (that I already asked in the announcements thread): would you teach me/us build alphaOS from scratch as if you were explaining it to a 6yo child :mrgreen: ?


Yes, please :oops: in a dedicated thread, because we may have some questions ;)

john3voltas wrote:That way I would try to compile a 3.4 kernel and see if that cures my cpu temp+fan speed and also my wifi issues.I'm just dreaming here with a nice guide in the wiki ;)
Cheers


There is nothing like compile your own kernel 8-)


Return to “General Discussion”

Who is online

Users browsing this forum: No registered users and 14 guests

cron