Puppy Linux Discussion Forum

jemimah · Posted: Tue 03 Nov 2009, 16:09 Post subject:

When wpa_gui tells you it connected, it means it brought up your ethernet card. There's a drop down box called Adaptor, that lets you pick wlan0 or eth0. If you pick wlan0, what does it say under status? SCANNING probably. Then press the scan button to see your networks. It will let you press the scan button if eth0 is selected, but nothing will ever show up in there. I configured wpa_gui to automatically try to connect to open networks, but if you've got WEP or WPA you have to go in there and set it up.

jemimah · Posted: Tue 03 Nov 2009, 16:26 Post subject:

Prehistoric, I've been looking at your dmesg output some more.

Did you see this line?

mawebb88 · Joined: 13 Jul 2008 Posts: 202 Location: France nr Lyon

Hi jemimah

Just tried puppeee431beta1_4 on my EeePC901 (2xSSD).

Booted okay but then I got some message saying (from memory) that no wifi module was in the bios and to edit something then run something in /etc/.... Sorry the message did not persist so have not captured it. Anyway I went on to run the Network wizard and got connected okay on WPA. But then the wpa_gui system tray icon just kept alternating pop-up balloons saying it was disconnected then connected, cycling every few seconds. So I've quit for the moment to ask whats going on?

Rgds Mike

mawebb88 · Joined: 13 Jul 2008 Posts: 202 Location: France nr Lyon

Deleted, Duplicate (server problem)

jemimah · Posted: Tue 03 Nov 2009, 17:38 Post subject:

If your wifi is disabled when you boot the first time, the auto detection will fail. I've tried to fix this, but haven't solved it yet. The easiest thing to do, is to just restart, don't save, go into the bios, turn everything on, then boot again.

If you're going to use Network Wizard, you need to prevent wpa_gui from starting by removing the "0networking" script from /root/startup and then reboot. I recommend learning to use wpa_gui though. It's really a lot less of a headache once you figure it out. I admit that whoever designed wpa_gui's interface needs to go to remedial design school. A lot of the functions are not obvious.

There's a bit of a tutorial here if it helps anybody. Ignore the parts about the config files and such.

http://manual.sidux.com/en/internet-connecting-wpagui-en.htm

Remember to switch the adapter drop-down from eth0 to wlan0 when you are trying to setup wireless.

jemimah · Posted: Tue 03 Nov 2009, 17:46 Post subject:

I've tested the new version of alsa and I can say for sure it rearranges the mixers. It fixed my missing "headphone" interface, although adjusting "headphone" still does nothing. There's no longer a switch for the external mic, so that's a bit strange. I'm not sure if this will be an improvement for everybody, but we'll give it a try and you guys can tell me if it helps. I'll post beta 1.5 later tonight.

prehistoric · Joined: 23 Oct 2007 Posts: 709

jemimah · Posted: Tue 03 Nov 2009, 19:27 Post subject:

Yeah I'm not thinking of adding any sleeping to the init script, since I just went to all the bother of removing as much of it as possible. I'm assuming your floppy disk icon does work, right?

Regarding wpa_gui not popping up. When you boot the first time, you get a message that says "click here for information about how to use puppy" or something like that. If you don't click on it, and then close the browser window it opens, it holds up the startup scripts from running for 55 seconds. I should probably fix this.

If you start wpa_supplicant from network wizard, it's definitely going to confuse wpa_gui as they run different versions of wpa_supplicant.

Wpa supplicant is not responsible for DHCP. When it says "connnected to network" that is the point where dhcpcd is supposed to take over. You can see how I set this up by looking at the networking script in /root/startup.

I am pretty sure 'front', 'master', 'pcm', 'speaker', etc all pretty much do the same thing. They are just there to be confusing.

jemimah · Posted: Tue 03 Nov 2009, 19:34 Post subject:

Beta 1.5 is up. Url updated in first post.

The only addition to this version is the new alsa modules to try to fix the sound for people who have a missing master volume. If you downloaded beta 1.4 already, the only file you need to update is zp431305.sfs.

prehistoric · Joined: 23 Oct 2007 Posts: 709

The good news is that I can adjust the master volume with beta 5. The bad news is that the range is less than full. I would estimate that I'm never getting much beyond half the volume I can get under Xandros. Audio is still a work in progress. I think the microphone works, but can't really tell until I can hear the output better.

The mystery of apparently redundant sliders still bothers me. I'm going to try some experiments to figure out what adjustments are taking place when I move the minimixer controls under Xandros.

I got a little farther with the WPA-GUI. With your information, I got the popup without running the network wizard at all. Selecting wlan0 and scanning got me closer to working, but not there. I put in the network SSID and password, and the status went as far as "Completed". I believe this is the point where it expects dhcpd to take over, but still no usable connection.

When I check with Pwireless, I find it using a screwy IP number like 196.254.10.116. (The router assigns IP addresses like 192.168.1.101) This happened earlier when we had a particular bug in the network wizard. That also failed at the point where dhcpd was supposed to take over.

More in the morning. Most of my evening went into solving unrelated problems.

(Beware of generic "security programs" for Windoze systems which do not display copyright, URL, etc. Some will clobber real security programs and prevent you from restoring to a point prior to infection. Look for a program in the prefetch cache with only digits in the name. Naturally, this program claims to be part of the operating system.)

magerlab · Joined: 08 Jul 2007 Posts: 594

is there only a madwifi module to test with beta 1 or 4 ?
i have sound working OK and just want to try how wifi will work with mad wifi

jemimah · Posted: Wed 04 Nov 2009, 12:01 Post subject:

I think Beta 1.3 was the first one to include madwifi.

To use madwifi:
1. First create a save file and reboot.
2. Then go to System->Bootmanager and add ath5k to the "blacklist."
3. Then go to System->Bootmanager and add ath_pci to the startup list.
4. Reboot
5. Click on the script /etc/acpid.install to re-detect your network interfaces. It should tell you it found ath-pci and ath0.
6. Download and uncompress the attached upgraded version of wpa_supplicant and copy it to /usr/local/sbin. (This will be included in the next update)
7. Edit the script /root/Startup/0networking. You should see a line about halfway through that looks like

jemimah · Posted: Wed 04 Nov 2009, 12:07 Post subject:

Prehistoric, sometimes dhcpcd refuses to realize there's a new connection (though generally in that case you don't get any IP address at all). You can restart dhcpcd with

jtouso · Joined: 29 May 2008 Posts: 62 Location: Barcelona, España

Hi,
congratulations! The silver keys are working and the volume up/down using fn+f7, f8 and f9 shows the correct little blue window with the % volume up or down.
The left silver key enable/disable bluetooh, the second one touchpad on/off, the third one close the screen (black screen) and turns "normal" again. The fourth and last silver key...nothing
The fn+keys works ok but the fn+f2 (to turn on/off wireless, works correct turning on/off the wireless conection but the mesage in the little window says other thing about bluetooh and not about wireless. Mistake.
Congratulations again for your work with the scripts in my Asus eeepc 901.
One more question: how can I install these scripts functions (all the silver and fn+ combination keys) with other puppy versions?
Regards
jtouso

jemimah · Posted: Wed 04 Nov 2009, 20:08 Post subject:

I have fn-f2 set to toggle both bluetooth and wireless since most EEEs have no button for bluetooth.

The fourth key is set to launch eee-control but that utility is not installed by default to prevent people damaging their CPUs by accident and since overclocking doesn't work on all EEEs. I will probably write my own eee-control at some point, but it's not there yet.

I will release an acpi pet for all puppy versions once I feel it's totally debugged and working for everybody.