Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Tue 25 Feb 2020, 22:49
All times are UTC - 4
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Unsorted
Extras for Puppy 4.1 alpha5
Moderators: deshlab, Flash, GuestToo, Ian, JohnMurga, Lobster
Post new topic   Reply to topic View previous topic :: View next topic
Page 2 of 3 [41 Posts]   Goto page: Previous 1, 2, 3 Next
Author Message
Nevermore

Joined: 26 Nov 2005
Posts: 365
Location: Italy

PostPosted: Mon 04 Aug 2008, 07:17    Post subject:  

hello
seems is not necessary to load the led-class..after charging the battery i didn't experience anymore quirky behaviours

_________________
--
/sbin/Nevermore
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5472
Location: Australia

PostPosted: Mon 04 Aug 2008, 13:43    Post subject:  

Forum member frankc reports that the new rt2500pci wifi module does not work with WPA encryption. So until this driver matures the only way to get RT2500 WPA support with the 2.6.25.11 kernel is to revert to the older "enhanced legacy" rt2500 driver, now attached.
After installing this package, reboot. This dotpet package contains a suitably modified /etc/rc.d/MODULESCONFIG file so that the new (well, "old") rt2500 module will be used in preference to the rt2500pci module.
Now to configure your wifi connection with WPA encryption you must use iwpriv commands, as explained here:
"PART 3: WPA encryption with Ralink devices"
http://www.murga-linux.com/puppy/viewtopic.php?p=159339#159339
The interface created by this driver will be "ra0".
You cannot use wpa_supplicant with this driver, it's completely incompatible.

Last edited by tempestuous on Mon 04 Aug 2008, 14:08; edited 1 time in total
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5472
Location: Australia

PostPosted: Mon 04 Aug 2008, 14:07    Post subject:  

The enhanced legacy rt2570 USB wifi driver will probably be necessary for WPA support, too. The driver it replaces is rt2500usb.
Similar instructions as for the rt2500. The interface created by this driver will be "rausb0"
Back to top
View user's profile Send private message 
jakfish

Joined: 18 Jul 2008
Posts: 766

PostPosted: Sat 16 Aug 2008, 12:00    Post subject:  

Tempestuous,

Running the 4.1 in an ASUS EEE 900, I can report the following:

1) sound works at last, after running its wizard (earjack as well)

2) successfully loading your asus_acpi pet and then running modprobe asus_acpi gives this:

"FATAL: Error inserting asus_acpi (/lib/modules/2.6.25.15/kernel/drivers/acpi/asus_acpi.ko): no such device"

The asus_acpi.ko is in that directory

3) wifi doesn't come up as a choice in the Network Setup. After installing your madwifi pet, in etc/rc.d/MODULESCONFIG, I see this PREFLIST= 'rt2500usb:irt73usb ath5k:ath-pci'

So it looks as if the substitution is happening.

Don't know if this helps,
Jake
Back to top
View user's profile Send private message 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 9236
Location: Perth, Western Australia

PostPosted: Sat 16 Aug 2008, 19:09    Post subject:  

Just a little clarification to everybody -- all drivers posted above are for Puppy 4.1alpha5only. 4.1alpha6 (and the final) uses the 2.6.25.15 kernel so the above drivers will not work.

However, most of the above (but not all) have been included in alpha6.

You can easily find out for yourself. When you run alpha6, open a terminal and type:

# modinfo r8101

...for example, to see if the r8101.ko driver is present.

_________________
https://bkhome.org/news/
Back to top
View user's profile Send private message Visit poster's website 
Béèm


Joined: 21 Nov 2006
Posts: 11775
Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win

PostPosted: Sat 16 Aug 2008, 19:17    Post subject:  

Where are drivers now?
I don't see a zdrv_xxx.sfs anymore since the last 2-3 releases of Dingo.
I have been away for >8 weeks, maybe I have missed something.

_________________
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
Consult Wikka
Use peppyy's puppysearch
Back to top
View user's profile Send private message 
jakfish

Joined: 18 Jul 2008
Posts: 766

PostPosted: Sat 16 Aug 2008, 22:02    Post subject:  

Thank you, Barry, for the clarification. For testing purposes, I booted fresh in 4.1 Alpha 6 (with a fresh puppy_save and only Alpha 6-installed drivers) and tried to use the ath_pci driver for ASUS eee 900 wifi.

That was a no-go, even when I reversed the order (ath5k:ath_pci) in "Give preference to one module over another"

Jake
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5472
Location: Australia

PostPosted: Sat 16 Aug 2008, 22:22    Post subject:  

I have just updated the title of this thread to include "alpha5".
Once 4.1 reaches final release I will remove these drivers, and make a new post with ONLY the drivers not included in Puppy 4.1. And since Barry has now incorporated most of these drivers, I need only post the Eee-compatible ath_pci and asus_acpi.

jakfish, the ath_pci module in 4.1alpha6 is the conventional version. But the Eee requires a special variant of this module, which cannot be added to the standard Puppy release because it will break compatibility with most other Atheros wifi devices.
Back to top
View user's profile Send private message 
jakfish

Joined: 18 Jul 2008
Posts: 766

PostPosted: Sat 16 Aug 2008, 22:37    Post subject:  

Thanks, tempestuous. I don't know if you saw an earlier post of mine, but the 4.1 Alpha6 does give sound to the ASUS eee 900. So it's all very promising.

Jake
Back to top
View user's profile Send private message 
jakfish

Joined: 18 Jul 2008
Posts: 766

PostPosted: Sun 17 Aug 2008, 13:26    Post subject:  

Hi, tempestuous,

I installed 4.1 Alpha 5, and installed your wifi and acpi eee pets.

For the testing purposes on the ASUS eee 900:

1) the wifi driver works with Alpha 5 and the 900

2) the acpi will allow successful toggling off the 900's wifi. It will also toggle on the blue led, but Alpha 5 doesn't recognize the wifi's reactivation. In Network Wizard, it stops listing wireless as a network option. The only way to bring back wireless is a computer reboot.

Also, the sound/mute buttons do not yet work in the 900.

I'd be happy to do further testing.

Jake
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5472
Location: Australia

PostPosted: Sun 17 Aug 2008, 22:31    Post subject:  

jakfish wrote:
Alpha 5 doesn't recognize the wifi's reactivation

OK, this can probably be fixed by tweaking the relevant acpi configuration file: /etc/acpi/eeepc-wireless-toggle.sh
I have just modified this file to add "ifconfig ath0 up" to the "on" function.
If it still doesn't work, we will probably need to add commands to renew DHCP.

jakfish wrote:
Also, the sound/mute buttons do not yet work in the 900.

Again, this will be an acpi configuration issue. I have just modified /etc/acpi/eeepc-hotkeys.sh to use the "amixer" ALSA utility to handle audio mute (Fn+F7), decrease volume (Fn+FCool, and increase volume (Fn+F9).

EDIT: asus_acpi-hotkeys-test01.pet attachment removed.

Last edited by tempestuous on Mon 18 Aug 2008, 04:59; edited 1 time in total
Back to top
View user's profile Send private message 
jakfish

Joined: 18 Jul 2008
Posts: 766

PostPosted: Sun 17 Aug 2008, 22:42    Post subject:  

Okay, I'll try this out. Should I uninstall the previous pet? Try a fresh puppy_save?

Jake
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5472
Location: Australia

PostPosted: Sun 17 Aug 2008, 23:07    Post subject:  

Don't uninstall anything. Just go ahead and install this dotpet, which will overwrite 3 acpi configuation files. Since the existing configuration files are not working, there's no harm even if these new versions don't work.
Back to top
View user's profile Send private message 
jakfish

Joined: 18 Jul 2008
Posts: 766

PostPosted: Sun 17 Aug 2008, 23:11    Post subject:  

Getting there. With this test pet installed on top of previous two pet downloaded from this thread:

1) Volume Up and Volume Down now work

2) no Mute yet

3) Problem remains with wifi: toggles OFF the wifi succesfully. Toggles ON the blue led successfully. But no wifi shows in Network Wizard. It acts as if the driver needs loading, but ath_pci always shows itself in lsmod, and Network Wizard says ath_pci is already loaded.

Jake
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5472
Location: Australia

PostPosted: Mon 18 Aug 2008, 04:55    Post subject:  

It's strange that the mute function doesn't work, because it uses a similar command to the volume up/down functions. This is the mute/unmute command -
Code:
amixer set Master toggle

It would be worth trying this command from the command prompt.

Regarding wifi re-enable; I did some reading on the web and I see there are quite a number of variations of the acpi scripts with the Eee, depending on what Linux distribution is being used.
In the most complex scenario (with Ubuntu) an extra kernel module is required: "pciehp". This module deals with hotplugging of devices on the PCI-express bus. This module is currently disabled in Puppy's kernel configuration, but I could re-anable and compile it ... but let's try some easier options first. I'm also concerned about how the pciehp module might interact with Barry's uevent mechanism, which was designed to replace hotplugging modules.

So we are at the stage of trial and error. I suggest this testing regime:
First make sure that the asus_acpi module is loaded, and the acpid daemon is running.

TEST 1. Install test02 dotpet.
This is just a slightly refined eeepc-wireless-toggle.sh script (based on examples on the web) which unloads ALL wifi-related modules (not just ath_pci) when toggled "off".
And when toggled "on" the ath_pci module is loaded only AFTER the hardware is re-enabled via acpi.

TEST 1a. Still working with test02 dotpet.
Disable the wifi device in bios. Yes, it sounds crazy, but I read on the web that the wifi hotkey might only re-enable when wifi is disabled in bios.

TEST 2. Install test03, and reboot.
This is a really stripped-down version of the eeepc-wireless-toggle.sh script which NEVER unloads or re-loads the wifi modules. It only turns the device off/on via acpi.
Again, it may be worth testing with wifi both enabled and disabled in bios.

TEST 3 ... on hold until TEST 1 & 2 completed.
This is the most comprehensive solution where I would add the "pciehp" module, and add commands to the "on" script to reinitialise PCI-E hotplugging when toggled "on".
asus_acpi-hotkeys-test02.pet
Description 
pet

 Download 
Filename  asus_acpi-hotkeys-test02.pet 
Filesize  859 Bytes 
Downloaded  344 Time(s) 
asus_acpi-hotkeys-test03.pet
Description 
pet

 Download 
Filename  asus_acpi-hotkeys-test03.pet 
Filesize  777 Bytes 
Downloaded  342 Time(s) 
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 2 of 3 [41 Posts]   Goto page: Previous 1, 2, 3 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Unsorted
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0845s ][ Queries: 13 (0.0366s) ][ GZIP on ]