wifi ko after reboot .

[fabrice_035]

hi,

Strange, after reboot my computer, wifi bug and cant connect, can you help me ?

log:

Code: Select all

Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory



Thanks for help 

[ardvark]

Hi...

What is the chipset precisely?

Code: Select all

lspci -nnk

Did you make any changes to the system (hardware of software) to the system just prior to the reboot you mentioned? How long has your wifi ran successfully before this happened and can this be duplicated by running Puppy live (I'm going to take a guess that you're running Puppy from your hard drive,) another version of Puppy or another distribution?

Thanks!

[fabrice_035]

Hardware is same, change nothing, just power off and restart after some time and now wifi is broke. Puppy work several months ago.
Just install 2 little software: copy fast 2.2 and Extract pet 1.7

Code: Select all

With Puppy Network Wizard:
supplicant - wpa_ctrl_open: No such file or directory

?

[fabrice_035]

after try update and file check (puppy pfix), problem same.

Wifi work when AP is open ( no security ) Problem with WPA.

Any idea ?

[rcrsn51]

Abandon Simple Network Setup and try a different connection manager.

[technosaurus]

Abandon Simple Network Setup and try a different connection manager.

I just open a terminal and use:
iwconfig wlan0 essid "myessid" enc "mysecret"
then
udhcpc -i wlan0

[fabrice_035]

Abandon Simple Network Setup ? Problem same with other tool.
And working if puppy run totaly in ram (no saved session)

[ardvark]

Hi...

Just my thought but I think it's quite unusual for Puppy to lose that kind of information or have it suddenly become corrupted by itself without help from the user (even unknowingly) or the hardware, such as a hard drive or memory modules, has failed or is failing. You might want to test your hard drive and memory just as a precaution, just in case you've never done so.

I don't know if swapping a savefile would work here but if not, you might need to back up what you have and reinstall Puppy from scratch. That's the only thing I know to do at this point. Perhaps someone here who knows a lot more than I do can guide you to a solution without doing any of that.

Regards...

[rcrsn51]

Go into the folder /var and delete any files that might belong to wpa_supplicant. Look in /var/run, /var/lock, etc.

Reboot.

[fabrice_035]

@rcrsn51, remove any wpa_supplicant, reboot, but problem is same

Code: Select all

STEP4: iwconfig wlan0 essid "Space"
STEP5a: ifconfig wlan0 up
STEP5b: wpa_supplicant -B -Dwext -iwlan0 -c"/etc/simple_network_setup/wpa_supplicant.conf-Space-18:3D:A2:3B:7E:44"
daemon: No such device
Running: wpa_cli -i wlan0 status
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory

Not a hardware problem because work fine with no saved session, it's just my personal file who is broken.

I can restart from zero but i hope find solution before.

Thx.

[fabrice_035]

I have found a solution, not perfect but work, i'm use this cmd :

Code: Select all

wpa_passphrase AccesPointName MYPASSWORDWIFI > config_file
wpa_supplicant -iwlan0 -c config_file -Dwext

and in over terminal

Code: Select all

dhcpcd -f /etc/frisbee/dhcpcd.conf 

work.

[rcrsn51]

All you have done is build a new valid wpa_supplicant.conf file. The old one must have been corrupted by SNS. Did you ever look inside it?

[fabrice_035]

The difference is

ctrl_interface=/var/run/wpa_supplicant
ap_scan=0

but wpa_supplicant.conf file who is broken in the puppy 2fs is same from puppy 2fs that works.

Just found strange behavior, after create /var/run/wpa_supplicant folder (doesnt exist) , it's always deleted when simple Network Setup or Frisbee try to connect.

may be problem come "ctrl_interface=/var/run/wpa_supplicant"

[fabrice_035]

start sns from terminal:

Code: Select all

# sns

(process:2191): Gtk-WARNING **: Locale not supported by C library.
	Using the fallback 'C' locale.
EXIT="Interface_wlan0"
xwininfo: can not set locale properly

(process:2623): Gtk-WARNING **: Locale not supported by C library.
	Using the fallback 'C' locale.
/usr/sbin/sns: line 547:  2623 Terminated              yaf-splash -placement center -bg orange -text "$(gettext 'Please wait, scanning for wireless networks...')"

(process:2855): Gtk-WARNING **: Locale not supported by C library.
	Using the fallback 'C' locale.
xwininfo: can not set locale properly

(process:4022): Gtk-WARNING **: Locale not supported by C library.
	Using the fallback 'C' locale.
EXIT="Exit on mouse-over"
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
...
killall: wpa_supplicant: no process killed

?

[greengeek]

Abandon Simple Network Setup and try a different connection manager.

I just open a terminal and use:
iwconfig wlan0 essid "myessid" enc "mysecret"
then
udhcpc -i wlan0

What does the format of the encoded "mysecret" portion have to be? I tried this by just typing in my passkey which is something like TTYUKJJUOPIKK (that is how I would type it into sns or PWF) but it was obviously not the correct format. Do I need to encode it into ascii or something?

EDIT - this is the message:

Code: Select all

# iwconfig eth1 essid "vodafoneE40C" enc "TTYUKJJUOPIKK"
Error for wireless request "Set Encode" (8B2A) :
    invalid argument "TTYUKJJUOPIKK".
# 

[technosaurus]

What does the format of the encoded "mysecret" portion have to be? I tried this by just typing in my passkey which is something like TTYUKJJUOPIKK (that is how I would type it into sns or PWF) but it was obviously not the correct format. Do I need to encode it into ascii or something?

EDIT - this is the message:

Code: Select all

# iwconfig eth1 essid "vodafoneE40C" enc "TTYUKJJUOPIKK"
Error for wireless request "Set Encode" (8B2A) :
    invalid argument "TTYUKJJUOPIKK".
# 

iwconfig from the old wireless tools (and the newer "iw") only does wep encryption (hex digits), but it also does't require a running daemon process. For stronger WPA encryption, you need wpa_supplicant, which has horrible command line tools (there is no way to do anything without a config file) I know this is a horrible reason to use a less secure method but also some of my kids' devices only work on open/wep. I would use an open network if it weren't for "unlimited" != 'unlimited' and being on the hook for crimes a guest committed.

I may start a discussion on toybox's mail list about writing a sane WPA wireless tool with proper unix operation. You shouldn't need to write a config file to get a simple command line program to run.

[jamesbond]

... wpa_supplicant, which has horrible command line tools (there is no way to do anything without a config file)

You don't need a config file. Fatdog's initrd starts (static) wpa_supplicant without any config file, and join networks by issuing commands using wpa_cli. But you can't help needing a daemon, though.

[linus.cl]

That is very easy:

Code: Select all

rfkill unblock all