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 Thu 02 Oct 2014, 00:35
All times are UTC - 4
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Drivers
Extras for Puppy 4.3 with 2.6.30.5 kernel
Post_new_topic   Reply_to_topic View_previous_topic :: View_next_topic
Page 3 of 8 Posts_count   Goto page: Previous 1, 2, 3, 4, 5, 6, 7, 8 Next
Author Message
Whitesnow


Joined: 20 Nov 2007
Posts: 103
Location: Italy

PostPosted: Wed 28 Oct 2009, 17:45    Post_subject:    

tempestuous wrote:
you could install the MADWiFi (ath_pci) driver from earlier in this thread. The ath_pci driver supports AP mode, regardless of kernel version.


I didn't know. Thank you, I'll try. Smile

tempestuous wrote:
Be aware that ad-hoc mode is completely different to AP mode. I will post an ad-hoc HOWTO soon.


For ad-hoc net I mean two PC linked by wifi without a DHCP server. IPs set manually. If I don't set one of these computers as AP, I can't link. Question
Formally, I know you right. Smile

OT: I have download 4.3.1, but I have seen that bootmanager, like 4.3.0., can still boot not more than 6 sfs and cannot find kernel src mirrored (virtualbox refuses to run without).
Someone can indicate me where I can find information about these topics?

_________________
*.* Snow *.* Wink
My repo: http://qualapinna.dyndns.org/repo
My blog: http://qualapinna.dyndns.org
Back to top
View user's profile Send_private_message Visit_website 
tempestuous

Joined: 10 Jun 2005
Posts: 5263
Location: Australia

PostPosted: Thu 29 Oct 2009, 06:06    Post_subject:  

Whitesnow wrote:
For ad-hoc net I mean two PC linked by wifi without a DHCP server. IPs set manually. If I don't set one of these computers as AP, I can't link.

That's not ad-hoc. It's a situation where one of your computers is an access point (wifi master mode) and the other computer is a conventional client (wifi station mode).

In ad-hoc mode, both computers are equal peers. I just posted an ad-hoc HOWTO here -
http://www.murga-linux.com/puppy/viewtopic.php?p=159929#159929
Back to top
View user's profile Send_private_message 
jemimah


Joined: 26 Aug 2009
Posts: 4309
Location: Tampa, FL

PostPosted: Sun 01 Nov 2009, 22:32    Post_subject:  

The 2.6.30.5 kernel has Atheros drivers atl1c and atl1e, but some atheros cards will not work with the default driver, notably the EEE 1005HA, and possibly others. I've attached a pet file of the manufacturer's driver, downloaded from the Atheros site. http://partner.atheros.com/Drivers.aspx

Edit: I've uploaded a new version of 1.0.0.10 and added 1.0.0.11-test. It's been mentioned to me that the test version is required for some newer cards; it seems more stable on my machine as well.

Edit: updated both pets for bug tempestuous found
Edit: 12/29/09 updated both pets to include preflist hotfix
atl1e-1.0.0.11-test.pet
Description 
pet

 Download 
Filename  atl1e-1.0.0.11-test.pet 
Filesize  34.81 KB 
Downloaded  936 Time(s) 
atl1e-1.0.0.10.pet
Description 
pet

 Download 
Filename  atl1e-1.0.0.10.pet 
Filesize  34.63 KB 
Downloaded  943 Time(s) 

Edited_times_total
Back to top
View user's profile Send_private_message Visit_website 
tempestuous

Joined: 10 Jun 2005
Posts: 5263
Location: Australia

PostPosted: Sun 29 Nov 2009, 22:13    Post_subject:  

EDIT November 17 2010
Latest Atheros/Attansic atl1e ethernet driver now available later in this thread -
http://www.murga-linux.com/puppy/viewtopic.php?p=467846#467846

EDIT Dec 30 2009
jemimah's atl1e dotpets in the previous post compete with the standard atl1c driver in Puppy 4.3.x
so you must also install the modules-preference fix from here -
http://www.murga-linux.com/puppy/viewtopic.php?p=371659#371659
(as mentioned in the first post in this thread)

Edited_times_total
Back to top
View user's profile Send_private_message 
jemimah


Joined: 26 Aug 2009
Posts: 4309
Location: Tampa, FL

PostPosted: Mon 30 Nov 2009, 00:09    Post_subject:  

Thanks, I had been meaning to update that pet as some people had troubles with it. There's also a newer 1.0.0.11-test version should probably be packaged. I'll post a new pet when I get a chance.

Although, the atl1c driver will try to load on my ethernet card, so adding it to the preflist will probably prevent the correct atl1e driver from loading.
Back to top
View user's profile Send_private_message Visit_website 
tempestuous

Joined: 10 Jun 2005
Posts: 5263
Location: Australia

PostPosted: Mon 30 Nov 2009, 00:39    Post_subject:  

jemimah wrote:
the atl1c driver will try to load on my ethernet card, so adding it to the preflist will probably prevent the correct atl1e driver from loading.

When configured properly, the PREFLIST (which is referenced by Puppy's version of udev) sets the preference/priority of one module over another.
Back to top
View user's profile Send_private_message 
jemimah


Joined: 26 Aug 2009
Posts: 4309
Location: Tampa, FL

PostPosted: Mon 30 Nov 2009, 01:22    Post_subject:  

Ok, I just did a test with the standard kernel. On my hardware, the old atl1c driver loads, but it's the wrong driver and will not work; dhcp fails to obtain an IP. When I install the new atl1e driver pet, the old atl1c driver continues to load. If I add atl1c:atl1e to the preflist, atl1c still loads. If I blacklist atl1c, then neither driver loads. So the only way it works is if if I add atl1e to the whitelist and add atl1c to the blacklist. Hope that clarifies things. YMMV on different hardware.
Back to top
View user's profile Send_private_message Visit_website 
tempestuous

Joined: 10 Jun 2005
Posts: 5263
Location: Australia

PostPosted: Mon 30 Nov 2009, 02:09    Post_subject:  

jemimah wrote:
If I add atl1c:atl1e to the preflist, atl1c still loads.

Then PREFLIST (or udev/pup_event) is not working as designed. This, then, is a bug and should probably be reported to Barry.

This situation might explain a few other problems reported on the forum involving conflicting modules.

EDIT:
I just reported this in the "Puppy 4.3.1 -- bug reports and suggestions" thread.
Back to top
View user's profile Send_private_message 
jemimah


Joined: 26 Aug 2009
Posts: 4309
Location: Tampa, FL

PostPosted: Mon 30 Nov 2009, 10:38    Post_subject:  

Interestingly, it works fine in Puppeee 4.31 (the only relevant difference being the lightweight kernel build) .
Back to top
View user's profile Send_private_message Visit_website 
rerwin


Joined: 24 Aug 2005
Posts: 1519
Location: Maine, USA

PostPosted: Thu 03 Dec 2009, 12:16    Post_subject:  

tempestuous, jemimah,
Quote:
Then PREFLIST (or udev/pup_event) is not working as designed. This, then, is a bug and should probably be reported to Barry.
Since I am already modifying pup_event_backend_modprobe, I would like to include a fix for this problem in my updated version.

Could you re-run your original attempt to set the preference (with no atl1? added or blacklist entries)? But please do not edit any files for this -- use the BootManager to set the preference and be sure the two names are separated only by a colon and no spaces. Once rebooted, please tell me which atl1? lsmod shows as loaded, what the /etc/rc.d/MODULESCONFIG file has for the PREFLIST= data, and whether the /etc/modprobe.conf file contains an entry: "blacklist atl1c" near the end. Also, please save and then attach file /tmp/udevtrace.log to your posting. Then reboot again to see if the preference is fulfilled. (The idea is that maybe the blacklist entry is only added on the first reboot, so is not effective the first time; when present, there might be different behavior.) The udevtrace file might be interesting at that point, too.

To address your concern that by setting the preference you would be unable to use another NIC that takes the old atl!c module, there is a way to specify the preference for only certain hardware IDs. That fix would be to edit-add two items to the "PCI_OVERRIDES=" variable in /etc/rc.d/MODULESCONFIG, as:
atl1e 0x00001969 0x00001062
atl1e 0x00001969 0x00001063

This assumes that the NIC is not USB and that the override will always be valid for those NICs -- at least until the drivers change further.

But I am really concerned about the appearance that the preference listing in not effective. If the information I requested above is indeed present/correct, I will need to provide a "wired" version of the pup_event script to see where things go wrong. But first we need to verify that the preference was entered correctly when it failed.
Richard
Back to top
View user's profile Send_private_message 
jemimah


Joined: 26 Aug 2009
Posts: 4309
Location: Tampa, FL

PostPosted: Thu 03 Dec 2009, 15:47    Post_subject:  

I retested with the same result. Rebooted twice. Still atl1c loads. I think the blacklist entry is not being added to modprobe.conf.
MODULESCONFIG.gz
Description 
gz

 Download 
Filename  MODULESCONFIG.gz 
Filesize  1.39 KB 
Downloaded  823 Time(s) 
modprobe.conf.gz
Description 
gz

 Download 
Filename  modprobe.conf.gz 
Filesize  1.34 KB 
Downloaded  836 Time(s) 
udevtrace.log.gz
Description 
gz

 Download 
Filename  udevtrace.log.gz 
Filesize  2.21 KB 
Downloaded  792 Time(s) 
Back to top
View user's profile Send_private_message Visit_website 
rerwin


Joined: 24 Aug 2005
Posts: 1519
Location: Maine, USA

PostPosted: Fri 04 Dec 2009, 23:22    Post_subject:  

jemimah,
Thanks for the files. I have a confession to make: I jumped to the wrong conclusion about where the "blacklist atl1c" goes. It goes to /tmp/pup_event_prefhit_blacklist and is used immediately in attempting to load the alternative module. Now I have looked deeper into how the preference function works.

The main requirement for a preference to "take" is that multiple modules must claim to support the same device. You can't just tell puppy to use just any module. The /lib/modules/2.6.30.5/modules.alias file contains that information. The released 4.3.1 file contains this:
Code:
alias pci:v00001969d00001048sv*sd*bc*sc*i* atl1
alias pci:v00001969d00001026sv*sd*bc*sc*i* atl1e
alias pci:v00001969d00001066sv*sd*bc*sc*i* atl1e
alias pci:v00001969d00001063sv*sd*bc*sc*i* atl1c
alias pci:v00001969d00001062sv*sd*bc*sc*i* atl1c
There is no duplication of coverage between -c and -e. Since you are using your own version of atl1e, after you install it -- it should overwrite puppy's (or also delete puppy's) -- you must then enter the command:
depmod
to update that file. If you see similar entries for both modules, the preference setting should be effective; if no duplicates for your modem, the preference won't work.

Please try the "depmod" and then check the modules.alias file, by entering the command:
grep ' atl1' /lib/modules/2.6.30.5/modules.alias

If you find you have the duplication of coverage and the preference still doesn't work, I will need you to try a "wired" modprober, to see what is happening internally. If there is no duplicate, you will need to use your workaround or edit the MODULESCONFIG file PCI_OVERRIDES variable.
Richard
Back to top
View user's profile Send_private_message 
tempestuous

Joined: 10 Jun 2005
Posts: 5263
Location: Australia

PostPosted: Sat 05 Dec 2009, 01:20    Post_subject:  

To start with, there are some problems with jemimah's atl1e-1.0.0.11-test.pet:
The post-install script contains this -
Code:
mv /lib/modules/2.6.30.5/kernel/drivers/net/atl1e/atl1e.ko /lib/modules/save

which will actually rename the old module as "save". I suspect the intention was to keep its original name, but relocate it to /lib/modules/save

Also there's a significant typo -
Code:
depmod-Full -a

this command is unrecognised ... so the new module fails to be registered.

Once I run the correct command -
Code:
depmod-FULL -a

my updated modules.alias file then contains this -
Code:
alias pci:v00001969d00002060sv*sd*bc*sc*i* atl1e
alias pci:v00001969d00001062sv*sd*bc*sc*i* atl1e
alias pci:v00001969d00001063sv*sd*bc*sc*i* atl1e
alias pci:v00001969d00001066sv*sd*bc*sc*i* atl1e
alias pci:v00001969d00001067sv*sd*bc*sc*i* atl1e
alias pci:v00001969d00001026sv*sd*bc*sc*i* atl1e
alias pci:v00001969d00001062sv*sd*bc*sc*i* atl1c
alias pci:v00001969d00001063sv*sd*bc*sc*i* atl1c

As you can see, there's a direct overlap for devices 1969:1062 and 1969:1063.
Back to top
View user's profile Send_private_message 
davesurrey

Joined: 05 Aug 2008
Posts: 1201
Location: UK

PostPosted: Sat 05 Dec 2009, 07:11    Post_subject:  

@rerwin,

Richard, sorry for butting into a puppy 431 thread but tempestuous has kindly pointed me here as I have wifi problems in both puppy 412 and 421 which he believes are due to faulty PREFLIST mechanism in these distros. Similar to what is happening here.
see http://www.murga-linux.com/puppy/viewtopic.php?p=368542#368542

My question, will your modifications to pup_event_backend_modprobe be applicable to kernel 2.6.25.16 also ?

Thanks for all your efforts.

Dave
Back to top
View user's profile Send_private_message 
jemimah


Joined: 26 Aug 2009
Posts: 4309
Location: Tampa, FL

PostPosted: Sat 05 Dec 2009, 13:19    Post_subject:  

I've fixed the typo tempestuous found and uploaded new versions. Sorry about that!
Back to top
View user's profile Send_private_message Visit_website 
Display_posts:   Sort by:   
Page 3 of 8 Posts_count   Goto page: Previous 1, 2, 3, 4, 5, 6, 7, 8 Next
Post_new_topic   Reply_to_topic View_previous_topic :: View_next_topic
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Drivers
Jump to:  

Rules_post_cannot
Rules_reply_cannot
Rules_edit_cannot
Rules_delete_cannot
Rules_vote_cannot
You cannot attach files in this forum
You can download files in this forum


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