Page 8 of 13
Posted: Wed 01 Apr 2009, 12:38
by bigbeck
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.
Posted: Wed 01 Apr 2009, 23:03
by bigbeck
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
Posted: Thu 02 Apr 2009, 09:48
by Dougal
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).
Posted: Thu 02 Apr 2009, 14:48
by bigbeck
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
Posted: Sun 05 Apr 2009, 16:20
by gabe
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!
Posted: Sun 05 Apr 2009, 18:00
by caka
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.
Posted: Sun 05 Apr 2009, 22:06
by Dougal
I compiled iw a while ago, here it is along with libnl (which it depends on).
Posted: Tue 07 Apr 2009, 06:53
by caka
Dougal thanks a lot
It works perfectly.
I don't know why i can't compile iw in my system?
Posted: Tue 07 Apr 2009, 09:41
by tempestuous
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.
Posted: Tue 07 Apr 2009, 18:40
by Dougal
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...
Posted: Tue 07 Apr 2009, 18:46
by Dougal
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...
Posted: Wed 08 Apr 2009, 19:37
by caka
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.
Posted: Mon 13 Apr 2009, 06:12
by tempestuous
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
Posted: Mon 13 Apr 2009, 20:05
by bondo08
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.
Posted: Mon 13 Apr 2009, 20:05
by bondo08
Forgot the attachment...
Posted: Mon 13 Apr 2009, 23:15
by tempestuous
bondo08 wrote:I'm using Puppy 4.0
Puppy 4.0 has an older kernel, and does not contain the "r6040" ethernet driver.
bondo08 wrote:but I think this is also an issue with newer versions as well.
Well, no. Puppy 4.1/4.2 includes the r6040 driver.
I suggest you use Puppy 4.1.2.
Posted: Mon 13 Apr 2009, 23:35
by bondo08
tempestuous wrote:Puppy 4.0 has an older kernel, and does not contain the "r6040" ethernet driver.
I attached the source code for the drivers in my previous message and was hoping someone might be able to compile them for me.
tempestuous wrote:I suggest you use Puppy 4.1.2.
I would upgrade but that isn't an option right now. I've customized 4.0 quite a lot and am unable to upgrade to the newer version for a while.
I'm really hoping there is a way to get it working in Puppy 4.0. Thx.
Posted: Tue 14 Apr 2009, 03:13
by tempestuous
bondo08 wrote:I'm really hoping there is a way to get it working in Puppy 4.0.
Then your request should go in the forum thread which deals with that earlier kernel;
"Extras for Puppy 3.x and 4.0"
http://www.murga-linux.com/puppy/viewto ... 970#294970
r6040 driver now attached there.
Posted: Wed 15 Apr 2009, 02:24
by tempestuous
Here is the "w35und" driver for the Winbond W89C35D wifi device, which is apparently found in certain Koshinja laptops.
The source code is from
http://code.google.com/p/winbondport/
After installing this dotpet, reboot.
Puppy should automatically load the w35und driver, but if not, you can load it from the Network Wizard.
Posted: Thu 16 Apr 2009, 02:22
by egosumpaul
Thank you so much Tempestuous, module loaded, seems to be working, but I cannot connect to internet via wireless. LAN ethernet works fine, as usual... what should I do to make it work? I'm so excited since I've been trying ti load the module since 6 months ago!
I will appreciate any suggestion.
Best.