(old)Puppy Linux Discussion Forum

I'm running G_Pup on a new Presario laptop. The Nvidia ethernet driver loads fine. For wireless I have a AR5700 802.11b/g WiFi controller ver.7.6.0.209. When I load the ath5k ,which appears to be the correct one,the computer locks up. I've tried many other drivers and still no wireless. The Wizard will not recognize the AR5700. Any suggestions?

I've also had wireless trouble on my eee 900pc, but the MadWiFi pet took care of that

Thanks,

Don

(Note that I accidentally posted in this thread's parent forum as well. Sorry for the double posting).

Hello everyone. This is my first post, so let me begin by thanking all of the Puppy developers, and especially tempestuous for making all the pets available in this forum. I bought an eeePC 900A as a dedicated skype device for my mom. After loading the pets in this forum I've got almost all the hardware working. The internal microphone, however, does not work. If I plug an external mic into the side it works fine. ALSA has a setting for input source of Mic or Front Mic, but changing this has no effect. I already tried the tempestuous patch to snd-hda-intel in eee-snd-hda-intel-patched-k2.6.25.16.pet, and I added "options snd-hda-intel model=auto" to modprobe.conf.

I believe the problem is that the 900A uses the realtek ALC269, which I don't think is supported in the 1.0.16 version of ALSA. This is the same chip used in the 901, and I found a patch to the 1.0.16 version of ALSA which is supposed to fix the microphone issue on the 901. [https://bugs.launchpad.net/ubuntu/+sour ... bug/259878] With only a few changes I think this could support the 900A as well. Unfortunately, I'm a Puppy newbie, and after looking at some of the unleashed documentation I think trying to compile this is way beyond my level. If anyone could help me with this me and my mom would really appreciate it. I suppose she could live with using an external mic, but knowing her it would get lost behind the couch and I'd be stuck trying to explain how to reattach it without being able to hear her!

Thanks again!!!!

For wireless I have a AR5700 802.11b/g WiFi controller ver.7.6.0.209. When I load the ath5k ,which appears to be the correct one,the computer locks up.

5700?? As far as I can tell, ath5k supports AR52xx and some 53xx and 54xx.
I think the ath9k module might support 5700, but it's only in newer kernels (so you might want to search the forum for "ultrapup", which has a newer kernel.

Sorry, I meant AR5007, not AR5700

The driver in Win XP is athw.sys - if that helps.

bigbeck wrote:Sorry, I meant AR5007, not AR5700

Well, the module doesn't seem to specify 5007, but the pci.ids file does mention

the names AR5007* are for AR2425 designs

which ath5k does support.
When you say the computer locks up, do you mean completely, where you have to force a reboot? I'm thinking it might be worth loading it from a terminal, to see if it gives any error messages... so maybe if you can run "modprobe -v ath5k" it will give us a hint.

By "lock up", I have to kill power to the laptop. Ctrl-alt-del won't cut it. I tried modprobe -v ath5k and it locked up again. It just displayed the command I typed with No error messages.

I got wireless working. I booted up unnamed pup 1.1 and it recognized the wireless and loaded the ath5k driver. That's a pup!

So far, I tried 23 different pups and only 2 would boot up on the new presario laptop - all the pups booted up on my other 2 desktops and eee pc,so the burns were good.

One of the things that G_Pup and unnamed pup 1.1 have in common is they both have smp- whatever that is What's going on here?

Don

bigbeck wrote: One of the things that G_Pup and unnamed pup 1.1 have in common is they both have smp- whatever that is What's going on here?

I don't think the support for SMP per se is what makes the difference -- it's the fact that they use a different (most likely newer) kernel than the one in Puppy (and most derivatives).

Dougal wrote: I don't think the support for SMP per se is what makes the difference --

Yes, I booted without SMP support and it worked fine. So it has to be the newer kernel.

Thanks for your help

Don

For the ASUS Eee 900A / 901 / 1000 / 1000H / 1000XPH / 1002HA:
Wifi is supported out-of-the-box by the new Ralink rt2860sta module.

Maybe I'm misunderstanding something, or something has changed with 4.2, but when I booted 4.2 on my 1002HA, there was certainly no wifi "out-of-the-box." Instead, I get "wireless interface not found" when I use the autoconnect to wireless network feature in the network menu. Will one of these patches fix it?

Also, what about the multi-touch touchpad on the 1002HA? I want to turn off 'tap-to-click' as discussed here: http://reality.sgiweb.org/davea/eeepc.html

Thanks for the hard work, and I hope these issues can be addressed!

tempestuous wrote:I managed to patch the following wifi drivers in Puppy 4.1.x's 2.6.25.16 kernel.
- prism2_usb
- hostap (Prism2/2.5/3 PCI & Cardbus)
- iwl3945 & iwl4965 (Intel)
- zd1211rw (Zydas)

After installing any of these wifi drivers, reboot.
The setup of these drivers for use with aircrack-ng is explained at the link provided above.

Hi tempestuous and thanks a lot for your job.

I installed the pet package for iwl4965, but when i try mode monitor i can't:

# airmon-ng start wlan0

Interface Chipset Driver

wlan0 Intel 4965AGN iwl4965 - [phy0]

ERROR: Neither the sysfs interface links nor the iw command is available.
Please download and install iw from
http://wireless.kernel.org/download/iw/iw-0.9.7.tar.bz2

wlan1 Ralink 2573 USB rt73usb - [phy1]

I tried to install that packet iw-0.9.7 but i don't know how to do it and this is the error:

# make
GEN version.h
CC iw.o
CC info.o
CC phy.o
CC interface.o
CC station.o
CC util.o
CC mpath.o
CC reg.o
CC mesh.o
CC genl.o
genl.c: In function 'family_handler':
genl.c:43: error: 'CTRL_ATTR_MCAST_GROUPS' undeclared (first use in this function)
genl.c:43: error: (Each undeclared identifier is reported only once
genl.c:43: error: for each function it appears in.)
genl.c:47: error: 'CTRL_ATTR_MCAST_GRP_MAX' undeclared (first use in this function)
genl.c:52: error: 'CTRL_ATTR_MCAST_GRP_NAME' undeclared (first use in this function)
genl.c:53: error: 'CTRL_ATTR_MCAST_GRP_ID' undeclared (first use in this function)
genl.c:47: warning: unused variable 'tb_mcgrp'
make: *** [genl.o] Error 1

Could you make a pet package or modify the iwl4965 pet package to works correctly.

Thanks a lot and sorry for my poor english.

I compiled iw a while ago, here it is along with libnl (which it depends on).

Dougal thanks a lot It works perfectly.

I don't know why i can't compile iw in my system?

Well done guys.
But does that mean that the other 35 people who downloaded iwl3945-iwl4965-aircrack-k2.6.25.16 dotpet would have failed to launch the aircrack utilities, too?
If so, I'm stunned that people would download a driver for such a specific purpose, then not bother to report something as obvious as a missing wifi utility such as this! We get some strange behaviour on this forum.

caka wrote:I don't know why i can't compile iw in my system?

The errors you got were from undeclared functions, which most likely meant you were missing the header files for libnl (they include a list of functions contained in the library, so the application knows what's there to use).
This was probably the result of not having libnl...

tempestuous wrote:But does that mean that the other 35 people who downloaded iwl3945-iwl4965-aircrack-k2.6.25.16 dotpet would have failed to launch the aircrack utilities, too?

Yeah... whenever you fix something, all these people start popping up saying "we've also had that problem for ages", but they never bothered reporting/investigating it...

tempestuous wrote:Well done guys.
But does that mean that the other 35 people who downloaded iwl3945-iwl4965-aircrack-k2.6.25.16 dotpet would have failed to launch the aircrack utilities, too?
If so, I'm stunned that people would download a driver for such a specific purpose, then not bother to report something as obvious as a missing wifi utility such as this! We get some strange behaviour on this forum.

I only want to say THANKS to tempestuous for the job with the wireless drivers. Yo have compiled a lot of them and i couldn't make that job because i have a low knowledge in linux.

Dougal wrote:

caka wrote:I don't know why i can't compile iw in my system?

The errors you got were from undeclared functions, which most likely meant you were missing the header files for libnl (they include a list of functions contained in the library, so the application knows what's there to use).
This was probably the result of not having libnl...

A lot of thanks for your explanation. I like to learn to compile programs and to know why there is an error.

Here is an updated version of the snd-hda-intel ALSA audio driver.
I specifically patched it to support the ALC663 variant of Intel HDA-based audio devices, using a patch from here
http://marc.info/?l=linux-kernel&m=121602662531525&w=2
but as you can see from that link, many more updates are included.
Also, I added this latest patch on top of earlier patches for the ALC269 device in recent ASUS Eee models, so this audio driver is now relatively up to date, albeit heavily patched.

If you have an HDA-based audio device which still does not work with this driver, I suggest that you should use a Puppy derivative with newer kernel and newer ALSA audio drivers, such as wow's "Unnamed pupplet (puppy411 kernel-2.6.27.5 Xorg-7.4 LXDE)"
http://www.murga-linux.com/puppy/viewtopic.php?t=36592

or kirk's "Fatdog 112"
http://www.murga-linux.com/puppy/viewtopic.php?t=41102

I'm not sure this is the proper place to post this but I was redirected here from another post so here goes...

I have an eBox 3300 but the NIC isn't being detected. I've downloaded the driver from the manufacturer's site but am not sure how to compile it. I'm using Puppy 4.0 but I think this is also an issue with newer versions as well.

Would anyone be able to help me out?

I've attached the source for the r6040 ethernet drivers.

Kind regards.

Forgot the attachment...