2.01 Wifi, GRUB scripts don't work in 2.13

[smog]

Tempestuous,

It's me again. You got my wireless working on 2.01 but the script doesn't seem to work on 2.13. Any thoughts on what needs to change? Also my Grub menu.lst entry doesn't work either. Both scripts are copied below:

## load the driver
modprobe ipw3945
sleep 4
/sbin/ipw3945d
sleep 2
## if no error messages, this should create a network interface, eth0
ifconfig eth1 up #(sometimes necessary)
## it should now be possible to use WAG (Wireless Access Gadget) to connect to a wireless network
## or continue to set up the wireless network manually -
iwconfig eth1 essid Z2iLd43jq93 key restricted 6Da84c3B0C25e6bDc1a4D7B2fA mode managed
## for automatic IP
rm /etc/dhcpc/*.pid
dhcpcd -t 30 -h puppypc -d eth1

This successfully sets the essid but it doesn't seem able to set the wep key and says the operation is not supported.




Menu.lst:
title Puppy2
rootnoverify (hd0,4)
kernel /boot/vmlinuz root=/dev/ram0 acpi=off PMEDIA=idehd
initrd /boot/initrd.gz

title Puppy2 DVD
rootnoverify (hd0,4)
kernel /vmlinuz root=/dev/ram0 acpi=off
initrd /initrd.gz

Thanks for any help you can provide.

smog

[sml]

Grub menu.lst problems ....

For each of your 4 critical puppy files please provide the following:
- name of file (eg vmlinuz or initrd.gz)
- partition (eg hda2 or sda1)
- directory (eg / or /boot

[tempestuous]

smog,
I presume you ran those commands one at a time just for testing, and the error message was reported after the "iwconfig" command.

It could be a simple case of eth1 not being the correct interface ... which would depend on what order Puppy detects your wifi device and LAN device. Remember that Puppy now contains the ipw3945 driver as standard, unlike before.

Maybe eth0 is the correct interface? Try it.

[John Doe]

This successfully sets the essid but it doesn't seem able to set the wep key and says the operation is not supported.

I noticed this also.Set the wep key on a different line like this (this seems to fix that problem, not sure why):

#!/bin/sh
echo "Configuring wireless card"
modprobe ipw2100
echo "Configuring wireless network"
iwconfig eth1 essid yourESSIDName mode Managed channel 48
iwconfig eth1 key asdf (<- hex key here)
ifconfig eth1 up
iwconfig
echo "Trying rm line..."
rm /etc/dhcpc/dhcpcd-eth1.*
echo "DHCP in"
dhcpcd -t 10 -h puppypc -d eth1 (btw, dhcpcd is totaly f'ed for me on all machines I've tried it with Puppy 2.13., You may have to use the wizard and manual enter a network at this point)

[smog]

eth1 is the wireless interface.

I can set the essid but using iwconfig eth1 key restricted ### command just produces "Operation not supported"

I am sure this happened for a while with 2.01 but eventually worked, is there another way of issuing the command?

I tried putting the essid and key commands on different lines but this made no difference.

Funny thing is, when I first played about with these commands when I was away from home (therefore away from a wireless connection) I am sure it did put the wireless on eth0 and I could enter a WEP key then. Could this be have happened or am I just nuts?



Re the boot issue, I have put all the files in /boot on /hda5, is that wrong.


Cheers

Smog

[smog]

I've just discovered something that amazed me and might help others.

If I press ENTER on boot up to avoid waiting 5 seconds at the point when you can enter boot options my Samsung Q35 laptop won't boot, it fails half way through.

If I type "puppy acpi=off" at this point, it does boot but obviously acpi is off.

BUT........ if I don't press anything and wait for the 5 seconds to elapse, it boots in with acpi working!!!!!!!!

Hope this works for others.

[tempestuous]

I just remembered that there is an important extra wifi module needed for WEP: ieee80211_crypt_wep
Load it before running any other setup commands -

modprobe ieee80211_crypt_wep

Actually "modprobe -vn" would probably suffice, this just "fetches" the module without loading it.
I think this will fix your problem.

Similarly, WPA encryption requires some extra modules:
ieee80211_crypt_tkip
ieee80211_crypt_ccmp
michael_mic

[smog]

modprobe ieee80211_crypt_wep

returns:

module not found

do I need to download it, if so where do I put it?

thanks

[tempestuous]

The ieee80211_crypt_wep module is definitely contained in the zdrv file. It sounds like you are having the same problem as many others on the forum: unable to access the zdrv file.
In your case, this might be related to your boot configuration? In a frugal install, I think it should be in /mnt/home. Check that the zdrv file exists in the same location as your pupsave file on the hard drive.

[smog]

I am working off the live cd at the moment because I can't get the Grub boot to work.

Where is the zdrv file on the cd?

Cheers

smog

[sml]

eth1 is the wireless interface.
Re the boot issue, I have put all the files in /boot on /hda5, is that wrong.

Yes it is wrong I think. The vmlinuz and initrd.gz can be anywhere, but the other two files have to be in the / directory (and not in /root).

Also are you sure you need the PMEDIA=idehd? If so why?

[smog]

I know these aren't bugs but since I have your attention!

1. Any more ideas about why ieee80211_crypt_wep doesn't work off the Live CD?

2. Can I use puppy acpi=off code when booting off a USB stick, I don't seem to get the boot options page?

Thanks

smog

[laptopnewbee]

unless i miss my guess, you are booting from an install on that usb stick, and things like that should be found by puppy in the configuration files during the boot process. in other words you should not need to enter them by hand at boot anymore.