 |
Puppy Linux Discussion Forum Puppy HOME page : puppylinux.com "THE" alternative forum : puppylinux.info
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in|
The time now is Tue 25 Jul 2017, 20:57 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
|
 
|
View previous topic :: View next topic |
| Page 3 of 8 [108 Posts] | Goto page: Previous 1, 2, 3, 4, 5, 6, 7, 8 Next |
| Author | Message | |||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Whitesnow
 Joined: 20 Nov 2007 Posts: 118 Location: Italy |
I didn't know. Thank you, I'll try. 
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. 
Formally, I know you right.
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 *.* 
My repo: http://qualapinna.dyndns.org/repo My blog: http://qualapinna.dyndns.org |
|||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||
 |
||||||||||||||||||||||||||||||||||||||||||
|
tempestuous
Joined: 10 Jun 2005 Posts: 5468 Location: Australia |
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 |
|||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||
jemimah
 Joined: 26 Aug 2009 Posts: 4309 Location: Tampa, FL |
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
Last edited by jemimah on Tue 29 Dec 2009, 11:41; edited 3 times in total |
|||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||
|
tempestuous
Joined: 10 Jun 2005 Posts: 5468 Location: Australia |
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) Last edited by tempestuous on Tue 16 Nov 2010, 20:58; edited 2 times in total |
|||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||
|
jemimah
Joined: 26 Aug 2009 Posts: 4309 Location: Tampa, FL |
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. |
|||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||
|
tempestuous
Joined: 10 Jun 2005 Posts: 5468 Location: Australia |
When configured properly, the PREFLIST (which is referenced by Puppy's version of udev) sets the preference/priority of one module over another. |
|||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||
|
jemimah
Joined: 26 Aug 2009 Posts: 4309 Location: Tampa, FL |
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. |
|||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||
|
tempestuous
Joined: 10 Jun 2005 Posts: 5468 Location: Australia |
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. |
|||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||
|
jemimah
Joined: 26 Aug 2009 Posts: 4309 Location: Tampa, FL |
Interestingly, it works fine in Puppeee 4.31 (the only relevant difference being the lightweight kernel build) . |
|||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||
rerwin
 Joined: 24 Aug 2005 Posts: 1800 Location: Maine, USA |
tempestuous, jemimah,
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 |
|||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||
|
jemimah
Joined: 26 Aug 2009 Posts: 4309 Location: Tampa, FL |
I retested with the same result. Rebooted twice. Still atl1c loads. I think the blacklist entry is not being added to modprobe.conf.
|
|||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||
|
rerwin
Joined: 24 Aug 2005 Posts: 1800 Location: Maine, USA |
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:
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 |
|||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||
|
tempestuous
Joined: 10 Jun 2005 Posts: 5468 Location: Australia |
To start with, there are some problems with jemimah's atl1e-1.0.0.11-test.pet: The post-install script contains this -
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 -
this command is unrecognised ... so the new module fails to be registered. Once I run the correct command -
my updated modules.alias file then contains this -
As you can see, there's a direct overlap for devices 1969:1062 and 1969:1063. |
|||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||
|
davesurrey
Joined: 05 Aug 2008 Posts: 1201 Location: UK |
@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 |
|||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||
|
jemimah
Joined: 26 Aug 2009 Posts: 4309 Location: Tampa, FL |
I've fixed the typo tempestuous found and uploaded new versions. Sorry about that! |
|||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||
| Page 3 of 8 [108 Posts] | Goto page: Previous 1, 2, 3, 4, 5, 6, 7, 8 Next |
|
|
View previous topic :: View next topic |
|
Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Drivers |
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