Extra drivers for Puppy 4.1 with 2.6.25.16 kernel
Atheros AR242 ? wifi works
I download the madwifi-hal-r3942-aircrack-k2.6.25.16.pet and on the reboot I had wi-fi connection labeled ath0. All these years of watching Puppy and I'm finally free of Windoze, though it is still a good game system. I have had a copy of Puppy since the release of the 2.15 CE release. The first release that gave me a wi-fi connect was WOW's pupplet. I then acquired Exton LXDE which also gave me a connection. Now I have Flexxpup 1.5.5 (stripped XFCE) and I'm happy.
P.S. I would love to help with puppy. I'm currently working on my Associate in Computer Applied Science, with 5 classes left. I'm unemployed and a single parent and would love to give some time.
P.S. my daughter loves Edupup, she's a puppy fan too, and she is six.
P.S. I would love to help with puppy. I'm currently working on my Associate in Computer Applied Science, with 5 classes left. I'm unemployed and a single parent and would love to give some time.
P.S. my daughter loves Edupup, she's a puppy fan too, and she is six.
Hi,
First post and surprise surprise I'm stuck! I am pretty familiar with Ubuntu but thought I would try Puppy.
I downloaded v4.1.2 from the website and put it on a CD, using a TX1138EA (TX1100 series) HP tablet PC with a Broadcom 4321 wifi adapter. For the life of me I cant make it detect it.
The wired works AOK but it doesn't see the wireless using any of the Broadcom drivers on the network wizard load module section. I tried installing the dotpet on page 5 by tempestuous that doesn't help and it doesn't work if I load the wl module either - so now I am at a loss.
Thanks in advance for any help!!
J.
First post and surprise surprise I'm stuck! I am pretty familiar with Ubuntu but thought I would try Puppy.
I downloaded v4.1.2 from the website and put it on a CD, using a TX1138EA (TX1100 series) HP tablet PC with a Broadcom 4321 wifi adapter. For the life of me I cant make it detect it.
The wired works AOK but it doesn't see the wireless using any of the Broadcom drivers on the network wizard load module section. I tried installing the dotpet on page 5 by tempestuous that doesn't help and it doesn't work if I load the wl module either - so now I am at a loss.
Code: Select all
# lsmod
Module Size Used by
ndiswrapper 183444 0
wl 1071364 0
ieee80211_crypt 5632 1 wl
parport_pc 32068 0
lp 12580 0
parport 35656 2 parport_pc,lp
snd_pcm_oss 40992 0
snd_seq_dummy 3844 0
snd_seq_oss 31360 0
snd_seq_midi_event 7168 1 snd_seq_oss
snd_seq 47952 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 8204 3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_mixer_oss 16640 1 snd_pcm_oss
usbtouchscreen 10756 0
uvcvideo 57608 0
compat_ioctl32 1408 1 uvcvideo
videodev 33664 1 uvcvideo
v4l1_compat 14340 2 uvcvideo,videodev
evdev 11776 1
hci_usb 14492 0
bluetooth 56324 1 hci_usb
serio_raw 6788 0
J.
WiFi setup
I never got 4.1.2 (or predecessors) to set up my EeePC901 WiFi via the wizard so had to resort to manually editing some files (got both WEP anf WPA working in the end). But suggest you give Puppy 4.2RC2 (I have not tried RC3 yet so might be ok as well) as with 4.2 the Network Wizards worked fine for me. Keep with it Puppy is great!
Rgds Mike
Rgds Mike
JW1978 wrote:Hi,
First post and surprise surprise I'm stuck! I am pretty familiar with Ubuntu but thought I would try Puppy.
I downloaded v4.1.2 from the website and put it on a CD, using a TX1138EA (TX1100 series) HP tablet PC with a Broadcom 4321 wifi adapter. For the life of me I cant make it detect it.
The wired works AOK but it doesn't see the wireless using any of the Broadcom drivers on the network wizard load module section. I tried installing the dotpet on page 5 by tempestuous that doesn't help and it doesn't work if I load the wl module either - so now I am at a loss.
Thanks in advance for any help!!Code: Select all
# lsmod Module Size Used by ndiswrapper 183444 0 wl 1071364 0 ieee80211_crypt 5632 1 wl parport_pc 32068 0 lp 12580 0 parport 35656 2 parport_pc,lp snd_pcm_oss 40992 0 snd_seq_dummy 3844 0 snd_seq_oss 31360 0 snd_seq_midi_event 7168 1 snd_seq_oss snd_seq 47952 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event snd_seq_device 8204 3 snd_seq_dummy,snd_seq_oss,snd_seq snd_mixer_oss 16640 1 snd_pcm_oss usbtouchscreen 10756 0 uvcvideo 57608 0 compat_ioctl32 1408 1 uvcvideo videodev 33664 1 uvcvideo v4l1_compat 14340 2 uvcvideo,videodev evdev 11776 1 hci_usb 14492 0 bluetooth 56324 1 hci_usb serio_raw 6788 0
J.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
JW1978, we need to identify your wifi device. Please run this command
and post your results.
Code: Select all
lspci -n
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Here is the latest "sierra" driver for Sierra wireless modems.
Puppy already contains an earlier version of this driver, but the new one extends support to these models:
Aircards:
AirCard 580
AirCard 595
AirCard 597E
AirCard 875
AirCard 88X
AirCard 88XE
USB dongles:
AirCard 595U
Compass 597
USB 598
AirCard 875U
AirCard 88XU
Compass 885/888
USBconnect 881
Mercury
Mini Cards:
MC5720
MC5725
MC5727
MC8755
MC8765
MC8775
MC878X
MC879x
Other:
PC5220
EM5625
To configure and connect with these devices, go to the "Connecting using PPPD" section here
http://sierrawireless.custhelp.com/app/ ... JKTWh0ag==
I have already included the Sierra chatscripts in the dotpet package, so just follow the instructions from step 3.
Forum member mill0001 asked to be able to launch the connection script from a desktop icon, so I created pppd-call-cdma.pet
now attached.
After installing this dotpet, use ROX to browse to /usr/local/bin and find pppd-call-cdma.sh.
Right-click its icon, select "Set Icon..." which will open a "Set icon" window.
Now use another ROX window to browse to /usr/local/lib/X11/pixmaps
and drag an icon of your choice into the "Set icon" window.
Now drag the pppd-call-cdma.sh icon onto the desktop.
Each time you want to connect, just click this icon. You will see the connect script run in an rxvt window, then at completion, exit after a 2 second delay.
Of course, it would be better to incorporate these configuration steps into rerwin's "3G_pupdial-wireless" dotpet -
http://www.murga-linux.com/puppy/viewtopic.php?t=37828
Maybe rerwin can work it out?
Puppy already contains an earlier version of this driver, but the new one extends support to these models:
Aircards:
AirCard 580
AirCard 595
AirCard 597E
AirCard 875
AirCard 88X
AirCard 88XE
USB dongles:
AirCard 595U
Compass 597
USB 598
AirCard 875U
AirCard 88XU
Compass 885/888
USBconnect 881
Mercury
Mini Cards:
MC5720
MC5725
MC5727
MC8755
MC8765
MC8775
MC878X
MC879x
Other:
PC5220
EM5625
To configure and connect with these devices, go to the "Connecting using PPPD" section here
http://sierrawireless.custhelp.com/app/ ... JKTWh0ag==
I have already included the Sierra chatscripts in the dotpet package, so just follow the instructions from step 3.
Forum member mill0001 asked to be able to launch the connection script from a desktop icon, so I created pppd-call-cdma.pet
now attached.
After installing this dotpet, use ROX to browse to /usr/local/bin and find pppd-call-cdma.sh.
Right-click its icon, select "Set Icon..." which will open a "Set icon" window.
Now use another ROX window to browse to /usr/local/lib/X11/pixmaps
and drag an icon of your choice into the "Set icon" window.
Now drag the pppd-call-cdma.sh icon onto the desktop.
Each time you want to connect, just click this icon. You will see the connect script run in an rxvt window, then at completion, exit after a 2 second delay.
Of course, it would be better to incorporate these configuration steps into rerwin's "3G_pupdial-wireless" dotpet -
http://www.murga-linux.com/puppy/viewtopic.php?t=37828
Maybe rerwin can work it out?
- Attachments
-
- pppd-call-cdma.pet
- (469 Bytes) Downloaded 923 times
-
- sierra-v1.3.1b-k2.6.25.16.pet
- for Puppy 4.1.x
- (7.24 KiB) Downloaded 928 times
Last edited by tempestuous on Sun 29 Mar 2009, 00:08, edited 1 time in total.
Apologies for the delay, been away for a few days....tempestuous wrote:JW1978, we need to identify your wifi device. Please run this commandand post your results.Code: Select all
lspci -n
Code: Select all
# lspci -n
00:00.0 Class 0500: 10de:02f0 (rev a2)
00:00.1 Class 0500: 10de:02fa (rev a2)
00:00.2 Class 0500: 10de:02fe (rev a2)
00:00.3 Class 0500: 10de:02f8 (rev a2)
00:00.4 Class 0500: 10de:02f9 (rev a2)
00:00.5 Class 0500: 10de:02ff (rev a2)
00:00.6 Class 0500: 10de:027f (rev a2)
00:00.7 Class 0500: 10de:027e (rev a2)
00:02.0 Class 0604: 10de:02fc (rev a1)
00:03.0 Class 0604: 10de:02fd (rev a1)
00:05.0 Class 0300: 10de:0244 (rev a2)
00:09.0 Class 0500: 10de:0270 (rev a2)
00:0a.0 Class 0601: 10de:0260 (rev a3)
00:0a.1 Class 0c05: 10de:0264 (rev a3)
00:0a.3 Class 0b40: 10de:0271 (rev a3)
00:0b.0 Class 0c03: 10de:026d (rev a3)
00:0b.1 Class 0c03: 10de:026e (rev a3)
00:0d.0 Class 0101: 10de:0265 (rev f1)
00:0e.0 Class 0101: 10de:0266 (rev f1)
00:10.0 Class 0604: 10de:026f (rev a2)
00:10.1 Class 0403: 10de:026c (rev a2)
00:14.0 Class 0680: 10de:0269 (rev a3)
00:18.0 Class 0600: 1022:1100
00:18.1 Class 0600: 1022:1101
00:18.2 Class 0600: 1022:1102
00:18.3 Class 0600: 1022:1103
03:00.0 Class 0280: 14e4:4328 (rev 03)
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Well that Broadcom device is definitely compatible with both the opensource "b43" driver and the proprietary "wl" driver.JW1978 wrote:14e4:4328 (rev 03)
I suggest you do some serious diagnosis. At bootup your system should automatically load the wl driver. Check with lsmod.
Now run this command to check if a wifi interface has been created -
Code: Select all
ifconfig -a
If not, unload the wl driver, and load the b43 driver instead -
Code: Select all
rmmod wl
modprobe b43
Hi Tempestuous,
still no joy I think
still no joy I think
Code: Select all
# lsmod
Module Size Used by
parport_pc 32068 0
lp 12580 0
parport 35656 2 parport_pc,lp
snd_pcm_oss 40992 0
snd_seq_dummy 3844 0
snd_seq_oss 31360 0
snd_seq_midi_event 7168 1 snd_seq_oss
snd_seq 47952 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 8204 3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_mixer_oss 16640 1 snd_pcm_oss
usbtouchscreen 10756 0
evdev 11776 1
uvcvideo 57608 0
compat_ioctl32 1408 1 uvcvideo
videodev 33664 1 uvcvideo
v4l1_compat 14340 2 uvcvideo,videodev
hci_usb 14492 0
bluetooth 56324 1 hci_usb
serio_raw 6788 0
wl 1071364 0
ieee80211_crypt 5632 1 wl
k8temp 5504 0
snd_hda_intel 333204 3
snd_pcm 73736 4 snd_pcm_oss,snd_hda_intel
hwmon 3092 1 k8temp
snd_timer 22276 2 snd_seq,snd_pcm
snd 52772 12 snd_pcm_oss,snd_seq_oss,snd_seq,snd_seq_device, snd_mixer_oss,snd_hda_intel,snd_pcm,snd_timer
pcspkr 2944 0
soundcore 7520 1 snd
snd_page_alloc 10376 2 snd_hda_intel,snd_pcm
forcedeth 48268 0
i2c_nforce2 7168 0
i2c_core 24592 1 i2c_nforce2
fuse 48284 2
aufs 150040 1
nls_iso8859_1 4096 0
nls_cp437 5760 0
usbhid 29696 0
usb_storage 85952 0
ehci_hcd 33932 0
ohci_hcd 25860 0
ssb 34436 1 ohci_hcd
usbcore 136560 8 usbtouchscreen,uvcvideo,hci_usb,usbhid,usb_stora ge,ehci_hcd,ohci_hcd
squashfs 46856 1
# ipconfig -a
bash: ipconfig: command not found
# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:1B:24:44:85:50
inet addr:192.168.0.6 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:651 errors:0 dropped:0 overruns:0 frame:0
TX packets:631 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:557598 (544.5 KiB) TX bytes:106606 (104.1 KiB)
Interrupt:11
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)
# rmmod wl
# modprobe b43
# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:1B:24:44:85:50
inet addr:192.168.0.6 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:651 errors:0 dropped:0 overruns:0 frame:0
TX packets:633 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:557598 (544.5 KiB) TX bytes:106848 (104.3 KiB)
Interrupt:11
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)
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
At "Helpful Hints for a tx1000 (tx1120)"
http://ubuntuforums.org/archive/index.p ... 3-p-4.html
they say that the wifi switch needs to be turned off and back on.
http://ubuntuforums.org/archive/index.p ... 3-p-4.html
they say that the wifi switch needs to be turned off and back on.
-
- Posts: 8
- Joined: Fri 27 Mar 2009, 14:28
Hi,
I've installed Puppy 4.1.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.
I've installed madwifi-hal-0.10.5.6-r3861-k2.6.25.16.pet , which has allowed the 4G to be able to see my wifi, but the setup wizard won't let me enter the full 63 digit WPA-PSK it needs. Just a portion is retained.
Is there a way to work around this problem?
(Edit) I've upgraded to Puppy 4.2 and it looks great on the eeepc.
Same problem remains though.
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.)
Any thoughts would be appreciated.
I've installed Puppy 4.1.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.
I've installed madwifi-hal-0.10.5.6-r3861-k2.6.25.16.pet , which has allowed the 4G to be able to see my wifi, but the setup wizard won't let me enter the full 63 digit WPA-PSK it needs. Just a portion is retained.
Is there a way to work around this problem?
(Edit) I've upgraded to Puppy 4.2 and it looks great on the eeepc.
Same problem remains though.
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.)
Any thoughts would be appreciated.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
That's a Network Wizard issue, not driver issue.Grenville Grimace wrote:the setup wizard won't let me enter the full 63 digit WPA-PSK it needs. Just a portion is retained.
I suggest you post your query in the "Improved Network Wizard" thread -
http://www.murga-linux.com/puppy/viewtopic.php?t=31522
or maybe just install the latest version of the Network Wizard.
-
- Posts: 8
- Joined: Fri 27 Mar 2009, 14:28
Thanks, reposted as you suggest.tempestuous wrote:That's a Network Wizard issue, not driver issue.Grenville Grimace wrote:the setup wizard won't let me enter the full 63 digit WPA-PSK it needs. Just a portion is retained.
I suggest you post your query in the "Improved Network Wizard" thread -
http://www.murga-linux.com/puppy/viewtopic.php?t=31522
or maybe just install the latest version of the Network Wizard.
-
- Posts: 8
- Joined: Fri 27 Mar 2009, 14:28
I'm not certain that I understand.Zyxmon wrote:Generate key using wpa_passphrase and enter the hex key in the wizard.Grenville Grimace wrote: Any thoughts would be appreciated.
I already have a 63 digit WPA Pre Shared Key for my wifi.
The problem is that the setup wizard will only accept 30 digits of it.
Run in the terminalGrenville Grimace wrote: I'm not certain that I understand.
Code: Select all
wpa_passphrase [ ssid ] [ passphrase ] > w.txt
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
I've also had wireless trouble on my eee 900pc, but the MadWiFi pet took care of that
Thanks,
Don
Microphone on eeePC 900A
(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!!!!
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!!!!
- Dougal
- Posts: 2502
- Joined: Wed 19 Oct 2005, 13:06
- Location: Hell more grotesque than any medieval woodcut
5700?? As far as I can tell, ath5k supports AR52xx and some 53xx and 54xx.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 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.
What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind
Some say your nose
Some say your toes
But I think it's your mind
- Dougal
- Posts: 2502
- Joined: Wed 19 Oct 2005, 13:06
- Location: Hell more grotesque than any medieval woodcut
Well, the module doesn't seem to specify 5007, but the pci.ids file does mentionbigbeck wrote:Sorry, I meant AR5007, not AR5700
which ath5k does support.the names AR5007* are for AR2425 designs
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.
What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind
Some say your nose
Some say your toes
But I think it's your mind