(old)Puppy Linux Discussion Forum

Sorry, I didn't realize there were two different lists.

It was the WPA list. The wizard said the module only supported WEP.
I dug around and found out that could be due thttp://www.murga-linux.com/puppy/viewtopic.php ... 37#284437o an out-of-date /etc/networkmodules.
I tried to add an entry manually, but it stilll didn't work.

I got the wireless up by copying /etc/network-wizard from another puppy PC, which bypasses the wizard altogether. The wizard let me load and run the copied config, which may or may not be a good thing.

Where's the WPA whitelist? I can check the date/md5sum.

Since 4.2 is due out any day, I can wait.

sue wrote:Where's the WPA whitelist? I can check the date/md5sum.

It's in the wizard itself, in /usr/sbin/wag-profiles.sh, pretty close to the top, you have a case structure with a bunch of modules listed (you can just search for the other iwl modules).

Another update:
- add iwl5100 and iwlagn to WPA whitelist
- in the "no wpa" dialog, add option for user to add module to whitelist.
- when running a wireless scan, run two scans, redirecting output to files, then use the bigger file... sometimes not all networks appear in a scan.
- clean up a bit and remove some unnecessary "sleep 1" instances.

Note to translators: some messages have been changed and a few added after them. See the head of the .mo file.

Thanks!

Hi,

I've installed Puppy 4.2 onto a 2GB SD card to try on my eeepc 701 4G

I'm very impressed with how well everything works, but am having problems with the wifi.

Had to install madwifi-hal-0.10.5.6-r3861-k2.6.25.16.pet to get it to see my wifi. Tried to configure, but Puppy will not accept my 63 digit WPA-PSK, cutting it down to 30 digits when 'save' is clicked. I get the impression that I could connect without issue to an unencrypted or weakly encrypted network, even if not to my own. (I don't consider weakening my network encryption to be an acceptable compromise to get Puppy connected.)

Is there a way to work around this problem?
Any thoughts would be appreciated.

Grenville Grimace wrote:Tried to configure, but Puppy will not accept my 63 digit WPA-PSK, cutting it down to 30 digits when 'save' is clicked.

By "WPA-PSK" you mean the (8-64 char) passphrase, not the (64 char) hex key, right?
Does it have any "special" characters ('"$` etc.) in it?
When you say it gets cut down, do you mean what it shows in the dialog?
Try looking in /etc/network-wizard/wireless/, both in the "profiles" and "wpa_profiles" directories, you should find configuration files named after your AP MAC address.
The one in "profiles" should contain the KEY variable -- see if it's truncated.
The one in "wpa_profiles" should contain a "#psk=" line which would include your key (between quotes) -- see if this one's ok, too.

Hi Dougal,
thanks for your wonderful network wizard.

Valpy: thanks for your suggestions: http://www.murga-linux.com/puppy/viewtopic.php?t=35586

I am using the latest puppy 4.2, and I thought Dougal had the following already fixed, but apparently not:

in /usr/sbin/wag_profile.sh should be This effectively solves the RTL8187 not connecting if WAP is used as an encryption method.


As a side note, another suggestion from Valpy has been confirmed on my setup: indeed gives a more reliable connection. I can go up to 48M following the same idea and still get a reliable connection.

Hope this helps.

gulk wrote:

Code: Select all

...
 r8180|r8187rtl8180|rtl8187|) CARD_WPA_DRV="ipw" ;;
...
rt61pci|rt73usb|rt2400pci|rt2500*|rt28[67]0*) CARD_WPA_DRV="wext" ;;

Hmm. Which version of the wizard are you using? I just checked and the rtl modules are under wext (I think we fixed this quite a while ago).

As a side note, another suggestion from Valpy has been confirmed on my setup:

Code: Select all

iwconfig wlan0 rate 5.5M

indeed gives a more reliable connection. I can go up to 48M following the same idea and still get a reliable connection.

Yeah. The problem is which value to use... you are limiting the rate, after all...
With ath5k, I have a special line to set it to 10M, since it defaults to 1M (it was suggested on the linux-wireless website), but we have no idea what every driver supports... and don't want to needlessly limit the user.
I might add something to give the user an option to select a rate ti use, but that would require changing the gui etc...

Another update:
- with pcmcia devices, add sleeping for 5 seconds before running wireless scan
- try to fix WEP, by explicitly turning on encryption (iwconfig key on) before setting key.

I made a little update to the locale file, so translations need to be updated (just one extra message).

I'm including here a .pet, in case people are having problems handling a .tar.gz -- use at your own risk.

Dougal wrote:

Grenville Grimace wrote:Tried to configure, but Puppy will not accept my 63 digit WPA-PSK, cutting it down to 30 digits when 'save' is clicked.

By "WPA-PSK" you mean the (8-64 char) passphrase, not the (64 char) hex key, right?
Does it have any "special" characters ('"$` etc.) in it?
When you say it gets cut down, do you mean what it shows in the dialog?
Try looking in /etc/network-wizard/wireless/, both in the "profiles" and "wpa_profiles" directories, you should find configuration files named after your AP MAC address.
The one in "profiles" should contain the KEY variable -- see if it's truncated.
The one in "wpa_profiles" should contain a "#psk=" line which would include your key (between quotes) -- see if this one's ok, too.

My 63 digit passphrase is: fyQ~xG\a@9zvoO7a[.]lY,f%0w_`0vj3kX<@~zTYnvNBbbEpob(0s:,/>-4`4=}
After entering into dialogue box and pressing 'save' it becomes: fyQ~xG\a@9zvoO7a[.]lY,f%0w_4=}


/etc/network-wizard/wireless/profiles:

TITLE="MyWiFi"
WPA_DRV="wext"
WPA_TYPE=""
WPA_AP_SCAN="1"
ESSID="MyWiFi"
NWID=""
KEY="fyQ~xG\a@9zvoO7a[.]lY,f%0w_4=}"
MODE="managed"
SECURE="open"
FREQ="2.462G"
CHANNEL="11"
AP_MAC="00:18:4D:FA:7E:4E"


/etc/network-wizard/wireless/wpa_profiles:

ctrl_interface=/var/run/wpa_supplicant
ap_scan=1
update_config=1

network={
ssid="MyWiFi"
scan_ssid=1
#psk="fyQ~xG@9zvoO7a[.]lY,f%0w_4=}"
psk=3599b4b55979bf79390a0102ac0404218dce503c13379bfc88163d598401518f
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
}

[Dougal]: Hmm. Which version of the wizard are you using? I just checked and the rtl modules are under wext (I think we fixed this quite a while ago).

I am using whatever version is in the official 4.2 final. Maybe I should let WhoDo know about that. I am not too sure about the procedure here.

Dougal,

Pet worked great. I can now connect in the 2 series wonderfully. The only issue now is it's not saving any of the info to:

/etc/network-wizard/wireless/profiles/00:1F:33:27:10:AO.Open.conf

/etc/network-wizard/wireless/profiles/00:1F:33:C2:62:AA.WEP.conf

*I have two routers. Now that I have WEP working I can close the other one.

In the 2 series I had to add the following to rc.local get my PCMCIA card to turn on

modprobe i82365
cardmgr

In the 3 series I had this (again in rc.local) to get everything working and connected on boot up:

modprobe i82365
cardmgr
/etc/rc.d/rc.network

In the 4 series I had to add this (rc.local again)

modprobe i82365
/etc/network-wizard/wireless/profiles/00:1F:33:27:10:AO.Open.conf

Both 3 & 4 both load the card, driver, and connect. They also save the profile info and login to the routers fine.

In series 2 the profiles files are both blank. Nothing saved in them.

Any ideas?

I suppose I could code manually from the info in ifconfig? But I'd like to get this rock solid for my Puppy-Libretto
Pupplet .

Thank you for your time.

Grenville Grimace wrote:My 63 digit passphrase is: fyQ~xG\a@9zvoO7a[.]lY,f%0w_`0vj3kX<@~zTYnvNBbbEpob(0s:,/>-4`4=}
After entering into dialogue box and pressing 'save' it becomes: fyQ~xG\a@9zvoO7a[.]lY,f%0w_4=}

Sheesh. No wonder it had problems... It appears like everything between the backticks (``) disappeared, which probably means it was interpreted as a subshell (it tried running what's inside as a shell command). I actually added escaping of such chars to the wizard, so they won't get interpreted...
Anyway, I think I found where the problems was and may have fixed it (I need to test my change to see it actually works -- no time at the moment). Will post another update after I deal with the other problems we're having.
(if you want to try it out, you can open /usr/sbin/wag-profiles.sh and in line 1083 just add quotes to the $PROFILE_KEY inside the subshell, so that 'echo $PROFILE_KEY' is changed to 'echo "$PROFILE_KEY"')

gulk wrote:I am using whatever version is in the official 4.2 final. Maybe I should let WhoDo know about that. I am not too sure about the procedure here.

Probably report it in the 4.2 bugs thread...

Libretto100ct wrote:In the 4 series I had to add this (rc.local again)

modprobe i82365

Wow, someone that actually has one of them i82365 card controllers... (most pcmcia cards use yenta_socket)
First, you should figure out why that module isn't loaded!
If you run "elspci -l" in terminal, is there a line where the second field is "060700"? (is it a pci card at all? or ISA-PNP?)
(you could also try something like "cat /sys/module/i82365/drivers/*/*/uevent" and see what you get...)

Anyway, it seems rather strange that the configuration doesn't get saved and I can't really think what is different between Puppy2 and Puppy4 that would cause anything like it.
You should try running the wizard from a terminal in debug mode (net-setup.sh -d) and see what kind of messages it gives... maybe they'll give us a clue.

This is from the 2 series:

elspci -l
or
elspci --list

doesnt pull anything up.

cat /sys/module/i82365/drivers/*/*/uevent

No such file or directory. I looked it up manually and it gets as far as sys/module/i82365/drivers/ , then some sub files.

I'm pretty sure it's not a pci card as I have to set it to 16 bit in BIOS to even get the module to work with Linux. The 2 options in BIOS are 16bit or PCI .

I will look up the specs though to be sure.

Running the net-setup.sh -d turned off my card every time. I'll save a log and post it later. It worked great yeasterday even after I rebooted several times. Each time I went through the motions to scan, enter WEP, and good to go. But it wouldn't save anything anywhere.

Today it shuts down the card. Maybe a fluke. I'll run it from the GUI and see if there is a difference. As I said, worked fine yesterday.

I struggled getting it working. It's an on again , off again proposition.

I logged everything I could think of here:

Not working:

iwconfig
lo no wireless extensions.

eth0 IEEE 802.11-DS ESSID:"" Nickname:"Prism I"
Mode:Managed Bit Rate:11 Mb/s
RTS thr:off
Encryption key:off
Link Quality:0 Signal level:188 Noise level:134
Rx invalid nwid:0 invalid crypt:0 invalid misc:0

ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)


Working:

iwconfig
lo no wireless extensions.

eth0 IEEE 802.11b ESSID:"zerosandones2" Nickname:"Prism I"
Mode:Managed Frequency:2.452 GHz Access Point: 00:1F:33:27:10:A0
Bit Rate:11 Mb/s Sensitivity:1/3
Retry min limit:8 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=92/92 Signal level=5/153 Noise level=110/153
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

ifconfig
eth0 Link encap:Ethernet HWaddr 00:30:AB:0F:4E:0C
inet addr:10.0.0.5 Bcast:10.0.0.255 Mask:255.255.255.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3 errors:0 dropped:0 overruns:0 frame:0
TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1222 (1.1 KiB) TX bytes:1402 (1.3 KiB)
Interrupt:9 Base address:0x100

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

Working:

net-setup.sh -d
cat: /sys/class/net/eth0/device/device: No such file or directory
cat: /sys/class/net/eth0/device/vendor: No such file or directory
grep: /etc/network-wizard/wpa_modules: No such file or directory
/usr/sbin/wag-profiles.sh: line 1285: kill: (3790) - No such process
Error for wireless request "Set Frequency" (8B04) :
SET failed on device eth0 ; Device or resource busy.
eth0 Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

Error for wireless request "Set Frequency" (8B04) :
SET failed on device eth0 ; Device or resource busy.
Configuring interface eth0 to network zerosandones2 with iwconfig...
Error for wireless request "Set Frequency" (8B04) :
SET failed on device eth0 ; Device or resource busy.
Error for wireless request "Set Frequency" (8B04) :
SET failed on device eth0 ; Device or resource busy.
Error for wireless request "Set Frequency" (8B04) :
SET failed on device eth0 ; Device or resource busy.
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
/usr/sbin/net-setup.sh: line 990: 2208 Terminated gtkdialog3 --pro gram NETWIZ_Connecting_DIALOG
/usr/sbin/wag-profiles.sh: line 231: 2257 Terminated gtkdialog3 -- program=Dhcpcd_Progress_Dialog <$PROGRESS_OUTPUT >/dev/null


Not working (endless loop of turning off the card and/or ifconfig eth0 up failures)

net-setup.sh -d
cat: /sys/class/net/eth0/device/device: No such file or directory
cat: /sys/class/net/eth0/device/vendor: No such file or directory
grep: /etc/network-wizard/wpa_modules: No such file or directory
Error for wireless request "Set Encode" (8B2A) :
SET failed on device eth0 ; Device or resource busy.
Error for wireless request "Set Frequency" (8B04) :
SET failed on device eth0 ; Device or resource busy.
SIOCSIFFLAGS: Connection timed out
Error!
Failed to raise interface eth0.
Failed command was: ifconfig eth0 up
Error returned was:
SIOCSIFFLAGS: Connection timed out

eth0 Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

Error for wireless request "Set Frequency" (8B04) :
SET failed on device eth0 ; Device or resource busy.
eth0 Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

Error for wireless request "Set Frequency" (8B04) :
SET failed on device eth0 ; Device or resource busy.
SIOCSIFFLAGS: Connection timed out
Error!

-------------------------------------------

Lastly when it scans I can use WEP jus fine, but again it's not saving anything. Most of the related files are blank. In fact I just verified it's rewriting blanks files as I hand scripted a wireless file. I went through the GUI, and clicked the save function for reboot. It replaced my file with a blank.

I'm getting it able to get a good scan once out of maybe 5 tries.

I'm going to use the card in other laptops and make sure there is not a physical problem with A) the card or B) the laptop. Sometimes solder can lift on old hot hardware around Mem, HDD, and Wireless ports.

I was thinking that my /var/log/messages was more telling as to what is going on?


Mar 31 05:30:33 (none) daemon.info init: ^MThe system is going down NOW !!
Mar 31 05:30:33 (none) daemon.info init: ^MSending SIGTERM to all processes.
Mar 31 05:30:33 (none) syslog.info System log daemon exiting.
Mar 31 13:31:45 (none) syslog.info syslogd started: BusyBox v1.01 (2006.08.20-09:28+0000)
Mar 31 13:31:45 (none) user.debug kernel: Probing IDE interface ide1...
Mar 31 13:31:45 (none) user.debug kernel: Probing IDE interface ide2...
Mar 31 13:31:45 (none) user.debug kernel: Probing IDE interface ide3...
Mar 31 13:31:45 (none) user.debug kernel: Probing IDE interface ide4...
Mar 31 13:31:45 (none) user.debug kernel: Probing IDE interface ide5...
Mar 31 13:31:45 (none) user.warn kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Mar 31 13:31:45 (none) user.info kernel: hda: max request size: 128KiB
Mar 31 13:31:45 (none) user.info kernel: hda: 19640880 sectors (10056 MB) w/512KiB Cache, CHS=19485/16/63
Mar 31 13:31:45 (none) user.info kernel: hda: cache flushes not supported
Mar 31 13:31:45 (none) user.info kernel: hda: hda1 hda2 hda3 hda4
Mar 31 13:31:45 (none) user.debug kernel: libata version 2.00 loaded.
Mar 31 13:31:45 (none) user.info kernel: PNP: PS/2 Controller [PNP0303,PNP0f13] at 0x60,0x64 irq 1,12
Mar 31 13:31:45 (none) user.info kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Mar 31 13:31:45 (none) user.info kernel: o: i8042 KBD port at 0x60,0x64 irq 1
Mar 31 13:31:45 (none) user.info kernel: mice: PS/2 mouse device common for all mice
Mar 31 13:31:45 (none) user.info kernel: md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
Mar 31 13:31:45 (none) user.info kernel: md: bitmap version 4.39
Mar 31 13:31:45 (none) user.info kernel: TCP bic registered
Mar 31 13:31:45 (none) user.info kernel: NET: Registered protocol family 1
Mar 31 13:31:45 (none) user.info kernel: NET: Registered protocol family 17
Mar 31 13:31:45 (none) user.warn kernel: Using IPI Shortcut mode
Mar 31 13:31:45 (none) user.info kernel: Time: tsc clocksource has been installed.
Mar 31 13:31:45 (none) user.info kernel: md: Autodetecting RAID arrays.
Mar 31 13:31:45 (none) user.info kernel: md: autorun ...
Mar 31 13:31:45 (none) user.info kernel: md: ... autorun DONE.
Mar 31 13:31:45 (none) user.info kernel: input: AT Translated Set 2 keyboard as /class/input/input0
Mar 31 13:31:45 (none) user.warn kernel: VFS: Mounted root (ext2 filesystem) readonly.
Mar 31 13:31:45 (none) user.info kernel: Freeing unused kernel memory: 176k freed
Mar 31 13:31:45 (none) user.info kernel: input: PS/2 Generic Mouse as /class/input/input1
Mar 31 13:31:45 (none) user.warn kernel: EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
Mar 31 13:31:45 (none) user.info kernel: apm: BIOS version 1.2 Flags 0x02 (Driver version 1.16ac)
Mar 31 13:31:46 (none) user.info kernel: Adding 152608k swap on /dev/hda3. Priority:-1 extents:1 across:152608k
Mar 31 05:31:48 (none) user.info kernel: parport: PnPBIOS parport detected.
Mar 31 05:31:48 (none) user.info kernel: parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE]
Mar 31 05:31:49 (none) user.info kernel: lp0: using parport0 (interrupt-driven).
Mar 31 05:31:49 (none) user.info kernel: lp0: console ready
Mar 31 05:31:51 (none) user.debug kernel: orinoco 0.15 (David Gibson <hermes@gibson.dropbear.id.au>, Pavel Roskin <proski@gnu.org>, et al)
Mar 31 05:31:51 (none) user.debug kernel: orinoco_cs 0.15 (David Gibson <hermes@gibson.dropbear.id.au>, Pavel Roskin <proski@gnu.org>, et al)
Mar 31 05:32:09 (none) user.info kernel:
Mar 31 05:32:09 (none) user.info kernel: Intel i82365sl B step ISA-to-PCMCIA at port 0x3e0 ofs 0x00, 2 sockets
Mar 31 05:32:09 (none) user.info kernel: host opts [0]: none
Mar 31 05:32:09 (none) user.info kernel: host opts [1]: none
Mar 31 05:32:09 (none) user.info kernel: status change on irq 15
Mar 31 05:32:10 (none) user.info kernel: pcmcia: Detected deprecated PCMCIA ioctl usage from process: cardmgr.
Mar 31 05:32:10 (none) user.info kernel: pcmcia: This interface will soon be removed from the kernel; please expect breakage unless you upgrade to new tools.
Mar 31 05:32:10 (none) user.info kernel: pcmcia: see http://www.kernel.org/pub/linux/utils/k ... cmcia.html for details.
Mar 31 05:32:10 (none) daemon.info cardmgr[1425]: watching 2 sockets
Mar 31 05:32:10 (none) user.info kernel: clean.
Mar 31 05:32:10 (none) user.info kernel: clean.
Mar 31 05:32:10 (none) user.info kernel: clean.
Mar 31 05:32:10 (none) user.info kernel: clean.
Mar 31 05:32:10 (none) user.info kernel:
Mar 31 05:32:10 (none) user.info kernel:
Mar 31 05:32:10 (none) user.info kernel: clean.
Mar 31 05:32:10 (none) user.info kernel: clean.
Mar 31 05:32:11 (none) daemon.info init: ^MStarting pid 1432, console /dev/tty2: '/sbin/getty'
Mar 31 05:32:11 (none) daemon.info init: ^MStarting pid 1431, console /dev/tty1: '/sbin/getty'
Mar 31 05:32:11 (none) user.notice kernel: pccard: PCMCIA card inserted into slot 0
Mar 31 05:32:11 (none) user.info kernel: cs: memory probe 0x0d0000-0x0dffff: clean.
Mar 31 05:32:11 (none) user.notice kernel: pcmcia: registering new device pcmcia0.0
Mar 31 05:32:11 (none) user.debug kernel: eth0: Hardware identity 8008:00000000
Mar 31 05:32:11 (none) user.debug kernel: eth0: Station identity 001f0001:0003
Mar 31 05:32:11 (none) user.debug kernel: eth0: Firmware determined as Intersil 1.3.4
Mar 31 05:32:11 (none) user.debug kernel: eth0: Ad-hoc demo mode supported
Mar 31 05:32:11 (none) user.debug kernel: eth0: IEEE standard IBSS ad-hoc mode supported
Mar 31 05:32:11 (none) user.debug kernel: eth0: WEP supported, 104-bit key
Mar 31 05:32:11 (none) user.debug kernel: eth0: MAC address 00:30:AB:0F:4E:0C
Mar 31 05:32:11 (none) user.debug kernel: eth0: Station name "Prism I"
Mar 31 05:32:11 (none) user.debug kernel: eth0: ready
Mar 31 05:32:11 (none) user.debug kernel: eth0: orinoco_cs at 0.0, irq 9, io 0x0100-0x013f
Mar 31 05:32:11 (none) daemon.info cardmgr[1426]: socket 0: Intersil PRISM2 11 Mbps Wireless Adapter
Mar 31 05:32:12 (none) auth.info login[1431]: root login on `tty1'
Mar 31 05:32:38 (none) user.info kernel: usbcore: registered new driver usbfs
Mar 31 05:32:39 (none) user.info kernel: usbcore: registered new driver hub
Mar 31 05:32:40 (none) user.info kernel: Initializing USB Mass Storage driver...
Mar 31 05:32:40 (none) user.info kernel: usbcore: registered new driver usb-storage
Mar 31 05:32:40 (none) user.info kernel: USB Mass Storage support registered.
Mar 31 05:33:41 (none) user.err kernel: hermes @ 00010100: BAP0 offset timeout: reg=0x8000 id=0xfc80 offset=0x0
Mar 31 05:33:41 (none) user.err kernel: eth0: Error -110 setting multicast list.
Mar 31 05:33:42 (none) user.err kernel: hermes @ 00010100: Timeout waiting for command 0x0021 completion.
Mar 31 05:33:43 (none) user.err kernel: hermes @ 00010100: Error -16 issuing command 0x0021.
Mar 31 05:33:59 (none) user.notice kernel: pccard: card ejected from slot 0
Mar 31 05:33:59 (none) user.err kernel: hermes @ 00010100: Error -16 issuing command 0x0002.
Mar 31 05:33:59 (none) user.warn kernel: eth0: Error -16 disabling MAC port
Mar 31 05:34:00 (none) user.notice kernel: pccard: PCMCIA card inserted into slot 0
Mar 31 05:34:00 (none) user.notice kernel: pcmcia: registering new device pcmcia0.0
Mar 31 05:34:00 (none) user.debug kernel: eth0: Hardware identity 8008:00000000
Mar 31 05:34:00 (none) user.debug kernel: eth0: Station identity 001f0001:0003
Mar 31 05:34:00 (none) user.debug kernel: eth0: Firmware determined as Intersil 1.3.4
Mar 31 05:34:00 (none) user.debug kernel: eth0: Ad-hoc demo mode supported
Mar 31 05:34:00 (none) user.debug kernel: eth0: IEEE standard IBSS ad-hoc mode supported
Mar 31 05:34:00 (none) user.debug kernel: eth0: WEP supported, 104-bit key
Mar 31 05:34:00 (none) user.debug kernel: eth0: MAC address 00:30:AB:0F:4E:0C
Mar 31 05:34:00 (none) user.debug kernel: eth0: Station name "Prism I"
Mar 31 05:34:00 (none) user.debug kernel: eth0: ready
Mar 31 05:34:01 (none) user.debug kernel: eth0: orinoco_cs at 0.0, irq 9, io 0x0100-0x013f
Mar 31 05:34:01 (none) daemon.info cardmgr[1426]: socket 0: Intersil PRISM2 11 Mbps Wireless Adapter
Mar 31 05:34:07 (none) user.err kernel: hermes @ 00010100: BAP0 offset timeout: reg=0x8000 id=0xfc80 offset=0x0
Mar 31 05:34:07 (none) user.err kernel: eth0: Error -110 setting multicast list.
Mar 31 05:34:07 (none) user.err kernel: eth0: Error -110 setting multicast list.
Mar 31 05:34:08 (none) user.err kernel: eth0: Error -110 setting multicast list.
Mar 31 05:34:08 (none) user.err kernel: hermes @ 00010100: Timeout waiting for command 0x0021 completion.
Mar 31 05:34:09 (none) user.err kernel: hermes @ 00010100: Error -16 issuing command 0x0021.
Mar 31 05:34:31 (none) user.err kernel: hermes @ 00010100: Error -16 issuing command 0x0011.
Mar 31 05:34:31 (none) user.err kernel: hermes @ 00010100: Error -16 issuing command 0x0021.
Mar 31 05:34:31 (none) user.err kernel: hermes @ 00010100: Error -16 issuing command 0x0002.
Mar 31 05:34:31 (none) user.warn kernel: eth0: Unable to disable port while reconfiguring card
Mar 31 05:34:31 (none) user.warn kernel: eth0: Resetting instead...
Mar 31 05:34:32 (none) user.err kernel: hermes @ 00010100: BAP0 offset timeout: reg=0x8000 id=0xfc80 offset=0x0
Mar 31 05:34:32 (none) user.err kernel: eth0: Error -110 setting multicast list.
Mar 31 05:34:32 (none) user.err kernel: eth0: Error -110 setting MAC address
Mar 31 05:34:32 (none) user.err kernel: eth0: Error -110 configuring card
Mar 31 05:34:32 (none) user.err kernel: eth0: Error -110 setting MAC address
Mar 31 05:34:32 (none) user.err kernel: eth0: Error -110 configuring card
Mar 31 05:34:43 (none) user.err kernel: hermes @ 00010100: Timeout waiting for command 0x0021 completion.
Mar 31 05:34:44 (none) user.err kernel: hermes @ 00010100: Error -16 issuing command 0x0021.
Mar 31 05:35:51 (none) user.err kernel: eth0: Error -110 setting MAC address
Mar 31 05:35:51 (none) user.err kernel: eth0: Error -110 configuring card
Mar 31 05:36:18 (none) user.err kernel: eth0: Error -110 setting MAC address
Mar 31 05:36:18 (none) user.err kernel: eth0: Error -110 configuring card
Mar 31 05:36:35 (none) user.err kernel: hermes @ 00010100: Error -16 issuing command 0x0021.
Mar 31 05:36:35 (none) user.err kernel: hermes @ 00010100: Error -16 issuing command 0x0021.
Mar 31 05:36:35 (none) user.err kernel: hermes @ 00010100: Error -16 issuing command 0x0021.
Mar 31 05:36:35 (none) user.err kernel: hermes @ 00010100: Error -16 issuing command 0x0021.
Mar 31 05:36:35 (none) user.err kernel: hermes @ 00010100: Error -16 issuing command 0x0021.
Mar 31 05:36:35 (none) user.err kernel: hermes @ 00010100: Error -16 issuing command 0x0011.
Mar 31 05:36:35 (none) user.err kernel: hermes @ 00010100: Error -16 issuing command 0x0021.
Mar 31 05:36:35 (none) user.err kernel: hermes @ 00010100: Error -16 issuing command 0x0021.
Mar 31 05:36:35 (none) user.err kernel: hermes @ 00010100: Error -16 issuing command 0x0021.
Mar 31 05:39:28 (none) user.err kernel: hermes @ 00010100: Error -16 issuing command 0x0011.
Mar 31 05:39:28 (none) user.err kernel: hermes @ 00010100: Error -16 issuing command 0x0021.
Mar 31 05:39:29 (none) user.err kernel: eth0: Error -110 setting MAC address
Mar 31 05:39:29 (none) user.err kernel: eth0: Error -110 configuring card
Mar 31 05:39:29 (none) user.err kernel: eth0: Error -110 setting MAC address
Mar 31 05:39:29 (none) user.err kernel: eth0: Error -110 configuring card
Mar 31 05:39:36 (none) user.err kernel: hermes @ 00010100: Error -16 issuing command 0x0021.
Mar 31 05:39:37 (none) user.err kernel: hermes @ 00010100: Error -16 issuing command 0x0021.
Mar 31 05:39:43 (none) user.notice kernel: pccard: card ejected from slot 0
Mar 31 05:39:44 (none) daemon.info cardmgr[1426]: executing: './network stop eth0 2>&1'
Mar 31 05:39:44 (none) daemon.info cardmgr[1426]: + ifconfig: eth0: error fetching interface information: Device not found
Mar 31 05:39:44 (none) daemon.info cardmgr[1426]: +
Mar 31 05:39:44 (none) user.notice kernel: pccard: PCMCIA card inserted into slot 0
Mar 31 05:39:44 (none) user.notice kernel: pcmcia: registering new device pcmcia0.0
Mar 31 05:39:44 (none) user.debug kernel: eth0: Hardware identity 8008:00000000
Mar 31 05:39:44 (none) user.debug kernel: eth0: Station identity 001f0001:0003
Mar 31 05:39:44 (none) user.debug kernel: eth0: Firmware determined as Intersil 1.3.4
Mar 31 05:39:44 (none) user.debug kernel: eth0: Ad-hoc demo mode supported
Mar 31 05:39:44 (none) user.debug kernel: eth0: IEEE standard IBSS ad-hoc mode supported
Mar 31 05:39:44 (none) user.debug kernel: eth0: WEP supported, 104-bit key
Mar 31 05:39:44 (none) user.debug kernel: eth0: MAC address 00:30:AB:0F:4E:0C
Mar 31 05:39:44 (none) user.debug kernel: eth0: Station name "Prism I"
Mar 31 05:39:44 (none) user.debug kernel: eth0: ready
Mar 31 05:39:44 (none) user.debug kernel: eth0: orinoco_cs at 0.0, irq 9, io 0x0100-0x013f
Mar 31 05:39:45 (none) daemon.info cardmgr[1426]: socket 0: Intersil PRISM2 11 Mbps Wireless Adapter
Mar 31 05:39:55 (none) user.info kernel: eth0: New link status: Connected (0001)
Mar 31 05:40:29 (none) user.info kernel: eth0: New link status: Disconnected (0002)
Mar 31 05:40:30 (none) user.info kernel: eth0: New link status: Disconnected (0002)
Mar 31 05:40:31 (none) user.info kernel: eth0: New link status: Connected (0001)
Mar 31 05:40:47 (none) local0.debug dhcpcd[2787]: broadcasting DHCP_DISCOVER
Mar 31 05:40:47 (none) local0.debug dhcpcd[2787]: broadcastAddr option is missing in DHCP server response. Assuming 10.0.0.255
Mar 31 05:40:47 (none) local0.debug dhcpcd[2787]: dhcpIPaddrLeaseTime=86400 in DHCP server response.
Mar 31 05:40:47 (none) local0.debug dhcpcd[2787]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec
Mar 31 05:40:47 (none) local0.debug dhcpcd[2787]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec
Mar 31 05:40:47 (none) local0.debug dhcpcd[2787]: DHCP_OFFER received from (10.0.0.1)
Mar 31 05:40:47 (none) local0.debug dhcpcd[2787]: broadcasting DHCP_REQUEST for 10.0.0.5
Mar 31 05:40:47 (none) local0.debug dhcpcd[2787]: dhcpIPaddrLeaseTime=86400 in DHCP server response.
Mar 31 05:40:47 (none) local0.debug dhcpcd[2787]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec
Mar 31 05:40:47 (none) local0.debug dhcpcd[2787]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec
Mar 31 05:40:47 (none) local0.debug dhcpcd[2787]: DHCP_ACK received from (10.0.0.1)

Dougal wrote:

Grenville Grimace wrote:My 63 digit passphrase is: fyQ~xG\a@9zvoO7a[.]lY,f%0w_`0vj3kX<@~zTYnvNBbbEpob(0s:,/>-4`4=}
After entering into dialogue box and pressing 'save' it becomes: fyQ~xG\a@9zvoO7a[.]lY,f%0w_4=}

Sheesh. No wonder it had problems... It appears like everything between the backticks (``) disappeared, which probably means it was interpreted as a subshell (it tried running what's inside as a shell command). I actually added escaping of such chars to the wizard, so they won't get interpreted...
Anyway, I think I found where the problems was and may have fixed it (I need to test my change to see it actually works -- no time at the moment). Will post another update after I deal with the other problems we're having.
(if you want to try it out, you can open /usr/sbin/wag-profiles.sh and in line 1083 just add quotes to the $PROFILE_KEY inside the subshell, so that 'echo $PROFILE_KEY' is changed to 'echo "$PROFILE_KEY"')

Tested, but sorry to report that it doesn't fix the issue.

Libretto100ct wrote:cat /sys/module/i82365/drivers/*/*/uevent

No such file or directory. I looked it up manually and it gets as far as sys/module/i82365/drivers/ , then some sub files.

I'm pretty sure it's not a pci card as I have to set it to 16 bit in BIOS to even get the module to work with Linux. The 2 options in BIOS are 16bit or PCI .

So the device probably appears in /sys/devices/pnp0 or /sys/bus/pnp or something...

Note that instead of putting the modprobe in rc.local, you can probably use the boot-manager to specify as an extra module to load (it does give that option, doesn't it?).

Not working:

ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

You mean ifconfig doesn't show eth0 at all? If that is the case, it seems like a bigger problem than the wizard. Maybe flaky HW? You should try just loading the module and then running dmesg and see exactly which messages are generated just from that -- from the log you posted it's not obvious when the different errors appear (as a result of what).


Also note that in the "working" output you posted there are messages like I think these might be caused when the wizard tries to scan before the interface is "settled", which might be the cause for the one-in-five success rate (there's another thread where I'm working on this with the user "mbe", in relation to ath_pci).
Please try the new version and see if it helps... (I still need to find a better way to detect if it's a pcmcia card)