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 23 Oct 2014, 10:48
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 4 of 8 [108 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6, 7, 8 Next
Author Message
rerwin


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

PostPosted: Sat 05 Dec 2009, 22:00    Post subject:  

jemimah, davesurrey, tempestuous,
So far, I have not made any fix for the preference issue. But if the problem is still present now that the corrections have been made, please insert three debug lines into /sbin/pup_event_backend_modprobe after line 144 (which begins with "xMODULE=":
Code:
 echo "MODULE: $MODULE  PREFHIT: $PREFHIT  PREFMOD: $PREFMOD  xMODULE: $xMODULE" >> /tmp/rerwin-pref.log #rerwin
 echo "MODULES: $MODULES" >> /tmp/rerwin-pref.log #rerwin
 echo "Blacklist: `cat /tmp/pup_event_prefhit_blacklist`" >> /tmp/rerwin-pref.log #rerwin
I tested them using a ltmodem driver dotpet, which detected my Agere modem. I set a preference for martian_dev, and it all seemed to work. The debug data in /tmp/rerwin-pref.log is:
Quote:
MODULE: ltmodem PREFHIT: ltmodem:martian_dev PREFMOD: martian_dev xMODULE: martian_dev
MODULES: martian_dev
ungrab_serial
v8250
ltmodem
Blacklist: blacklist ltmodem

Dave, the same version of the modprobe script is used in both kernel-versions of 4.3.1. However, the kernel support of the modprobe command might differ between kernels. Once we understand the problem in both kernels of 4.3.1 and fix it, I can probably retrofit the fix into 412 & 421.

Interestingly, I actually mistyped the preferred module name and it did not impact the result! Looking at the "MODULES" values, since ltmodem is blacklisted, puppy finds whatever is left, excluding the ltmodem dependencies (ungrab... & v8...). Puppy normally chooses the last name in the MODULES list. Part of my fix to that script will be to verify it finds the desired module, in case there are more than one alternative.
Richard
Back to top
View user's profile Send private message 
davesurrey

Joined: 05 Aug 2008
Posts: 1201
Location: UK

PostPosted: Sun 06 Dec 2009, 16:29    Post subject:  

rerwin,

I added your 3 lines of code to /sbin/pup_event_backend_modprobe after the xModule section (prior to fi) in my 431 install and /tmp/rerwin-pref.log gave me an output very similar to yours except it blacklisted rtl8187 in favour of r8187.
But of course everything is working well in 413.

Then I looked at 412 and found that the file /sbin/pup_event_backend_modprobe is different to that in 431. But I added your 3 lines into the section xModules. But after a reboot there wasn't any /tmp/rerwin-pref.log to be seen.

I did get an output very different to rerwin's log if I put the 3 lines of code afer "fi" .

rerwin I appreciate that you want to fix 431 first but may I also ask that you look to 420/412 as I am sure I am not alone in feeling some frustration that I can't sometimes use these distros due to non working wifi or other drivers which may well be due to this bug.

Many thanks
Dave
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5271
Location: Australia

PostPosted: Mon 07 Dec 2009, 01:15    Post subject:  

rerwin,
Even though jemimah has corrected the post-install script for atl1e-1.0.0.11-test.pet
the failure of PREFLIST settings has been reported in several other instances.
So where does that leave us? When I provide an updated kernel module which competes with a standard module, should I

i) create a PREFLIST entry ...
plus a BLACKLIST (SKIPLIST) entry
plus a WHITELIST (ADDLIST) entry?

ii) delete or remove the competing standard module?
Back to top
View user's profile Send private message 
rerwin


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

PostPosted: Mon 07 Dec 2009, 11:22    Post subject:  

tempestuous,
Can you wait a bit? I am working on a comprehensive fix to try, that may correct some of the preflist problems, if not all. But I am waiting for feedback from jemimah or anyone else seeing a problem in 4.3.1. Please insert the debug lines I posted above, so I can see what the situation is with the atl1c/e modules. I can guess all I want about how to improve this, but I need some diagnostic evidence to be sure I am fixing the right problem.

My fixes so far include looking for the specific substitute module no matter how many possibilities there are. Currently, only the "next in line" module is chosen, no matter what is specified as the preference. In addition, I am adding some special HSF/ALSA modem-conflict resolution.

My concern is that my fixes may not address the atl1c/e issue. Once I see the information I need to understand that situation, I plan to post here a corrected backend_modprobe that should work in 431. 412 & 421, kernels 2.6.30.5 & 2.6.25.16. I don't know yet whether it would also apply to 2.6.21, but won't wait to find out.

BTW: Where should I put all the fixes I am producing, as additions for 4.4 as well as for retrofitting to 4.3.1 by the users?
Richard
Back to top
View user's profile Send private message 
rerwin


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

PostPosted: Mon 07 Dec 2009, 20:07    Post subject: Debug versions of module-preferences fix  

Everyone with issues about the option to specify module preference when multiple drivers are available for a device:

Here are the debug versions of my preference function fix based on what I know at this point. There are two versions: one for 4.3.1 and the other for both 4.1.2 and 4.2.1. Please install the appropriate version, reboot, and PM the content of:
/tmp/rerwin-prefs.log

Also verify that /tmp/rerwin-error.log is blank/empty.

Eagerly awaiting some results. You can send the info by PM to me, to minimize further hijacking of this thread.

UPDATE: I have added my candidate for release to tempestuous, but with debug additions. I will remove them when I submit it to tempestuous for general use. I found the probable cause of the "atl1c/e" problem, which is due to multiple instances of the modprober running concurrently but using the same temporary blacklist file, so sometimes the old module was not being blacklisted correctly.

Now, I need someone with a wireless modem to try this out, because it re-implements a fix to ensure the correct module gets loaded. Please send me the contents of the /tmp/rerwin-pref.log file. TIA.
Richard

UPDATE 12/13/09: I have posted links to my completed fix packages for pup_event_backend_modprobe, in my second-next posting below. http://www.murga-linux.com/puppy/viewtopic.php?p=371669#371669
The debug versions are no longer relevant, so I have removed them. Please use the new version and report any problems to me by PM, since it would be off-topic for this driver thread.
Richard

Last edited by rerwin on Sun 13 Dec 2009, 23:27; edited 3 times in total
Back to top
View user's profile Send private message 
davesurrey

Joined: 05 Aug 2008
Posts: 1201
Location: UK

PostPosted: Tue 08 Dec 2009, 00:22    Post subject:  

@rerwin.
You have PM.
Dave
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5271
Location: Australia

PostPosted: Tue 08 Dec 2009, 02:45    Post subject:  

Sure, I'm happy to wait for a proper fix.

rerwin wrote:
Where should I put all the fixes I am producing, as additions for 4.4 as well as for retrofitting to 4.3.1 by the users?

Well this thread is good for 4.3. I started this thread as a point of contact for system-related enhancements, not just drivers.
Once you have finalised a hotfix, if you like, I can attach it to one of my posts on page 1, given its importance.
Back to top
View user's profile Send private message 
rerwin


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

PostPosted: Wed 09 Dec 2009, 21:41    Post subject: module preference function fixed!  

Tempestuous, et al,
I think I solved the preference problems and have posted an updated debug version above: http://www.murga-linux.com/puppy/viewtopic.php?p=369837#369837
See the UPDATE for details. Please, someone with a wireless modem, try this out and send me the debug info. Thanks.

UPDATE 12/13/09: Please use the completed fix from the links in my next posting, below.
Richard

Last edited by rerwin on Sun 13 Dec 2009, 23:30; edited 1 time in total
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5271
Location: Australia

PostPosted: Thu 10 Dec 2009, 03:30    Post subject:  

VIA VT6655 PCI and VT6656 USB wifi devices.

Here are the very latest proprietary vendor drivers for these wifi devices.
For the VIA VT6655 PCI device, the driver is called viawget
For the VIA VT6656 USB device, the driver is called vntwusb

The source code is from
http://www.viaarena.com/Drivers.aspx
After installing either of these dotpets, reboot.
Puppy should automatically load the correct driver, but if not, you can load them from the Network Wizard.
Both drivers create an interface called eth#. Usually your LAN device takes eth0, so the wifi interface will probably become eth1.

For WPA-encrypted connections, both packages include a modified version of wpa_supplicant compatible with the new driver.
I have included the necessary configuration file (/usr/sbin/wag-profiles.sh) so that Puppy's Network Wizard should be able to configure the connection.
But if you want to configure a WPA connection via the commandline, be aware that the wpa_supplicant "-D" parameter for each of the new drivers is the same name as the driver itself (which is quite unconventional).
So, example 1; for the viawget driver and a WPA (not WPA2) connection, the command would be -
Code:
wpa_supplicant -i eth1 -D viawget -c /etc/network-wizard/wireless/wpa_profiles/wpa_supplicant.conf -dd

example 2; for the vntwusb driver and a WPA2 connection, the command would be -
Code:
wpa_supplicant -i eth1 -D vntwusb -c /etc/network-wizard/wireless/wpa_profiles/wpa_supplicant2.conf -dd


Note: I also compiled the VIA wifi drivers from the "staging" section of the official kernel source.
But WPA support for these drivers is uncertain, which I learned by contacting the the maintainers of these drivers. The maintainers would be interested to learn if WPA encryption works successfully with the drivers from this post.
Please report your success or failure with WPA connections.
VT6655-1.20.02-k2.6.30.5.pet
Description  for Puppy 4.3.x VIA wifi PCI
pet

 Download 
Filename  VT6655-1.20.02-k2.6.30.5.pet 
Filesize  258.11 KB 
Downloaded  738 Time(s) 
VT6656-1.20.03-k2.6.30.5.pet
Description  for Puppy 4.3.x VIA wifi USB
pet

 Download 
Filename  VT6656-1.20.03-k2.6.30.5.pet 
Filesize  251.35 KB 
Downloaded  742 Time(s) 
Back to top
View user's profile Send private message 
rerwin


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

PostPosted: Sun 13 Dec 2009, 22:49    Post subject: Fix for erratic module-loading preference function
Subject description: Preferred module alternative was sometimes not loaded as specified in BootManager
 

tempestuous, et al,
I have completed my repairs and augmentation of the module loading script pup_event_backend_modprobe, to fix all known problems with the functioning of the Preference capability of the Boot Manager. I have uploaded two versions: the main one for all Puppy 4.3.x installations and a bugfix-only version for 4.1.x and 4.2.x systems. They are in the 4.3.1 bugfix thread and the 4.2.1 fix thread.

4.3.x and details: http://www.murga-linux.com/puppy/viewtopic.php?p=371659#371659

4.1.x & 4.2.x: http://www.murga-linux.com/puppy/viewtopic.php?p=371664#371664

The 4.3.x dotpet should also be integrated into 4.4CE. I plan to upload my modem fix pack to the 4.3.1 bugfix thread in a few days, and will add a link to it in this posting.
Richard
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5271
Location: Australia

PostPosted: Tue 15 Dec 2009, 08:21    Post subject:  

Well done rerwin.
I have updated the first post in this thread to stress the importance of installing your modules-preference fix when conflicting modules are involved.

Last edited by tempestuous on Sun 20 Dec 2009, 07:02; edited 1 time in total
Back to top
View user's profile Send private message 
grash

Joined: 19 Dec 2009
Posts: 2

PostPosted: Sat 19 Dec 2009, 03:16    Post subject: Atmel AT76C505A
Subject description: Can't get this driver working...
 

Hi all. I have an old OQO v01 that has the Atmel AT76C505A chipset and I can't seem to get it going with Puppy 4.3.1. Puppy doesn't detect it on boot and manually installing the module (at76c50x-usb) doesn't work either. Anyone with any ideas on how to troubleshoot this further? Thanks in advance for any help.
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5271
Location: Australia

PostPosted: Sat 19 Dec 2009, 05:00    Post subject:  

December 19 2009
I just updated the Ralink wifi drivers in the third post -
http://www.murga-linux.com/puppy/viewtopic.php?p=346450#346450
There are now four additional drivers to support wifi devices not already supported in Puppy 4.3, and all new drivers are fully compatible with the Network Wizard, including WPA configuration.
Back to top
View user's profile Send private message 
zigbert


Joined: 29 Mar 2006
Posts: 5753
Location: Valåmoen, Norway

PostPosted: Wed 30 Dec 2009, 08:00    Post subject:  

tempestuous
I need some advice.
I have earlier included your updated ati driver in Puppy Stardust. It works great. Now trio has requested yours and jrls broadcom wireless fix. I thought; maybe I should include more of your great stuff. Could you recommend those drivers which are stable enough for a stable Puppy release?


Thanks a lot
Sigmund

_________________
Stardust resources
Back to top
View user's profile Send private message Visit poster's website 
tempestuous

Joined: 10 Jun 2005
Posts: 5271
Location: Australia

PostPosted: Wed 30 Dec 2009, 08:54    Post subject:  

Hi Sigmund.
The modified ssb module is specifically to enable the simultaneous use of the proprietary Broadcom wl module, to support recent Broadcom wifi devices.
Generally I advise against modifications which suit only a limited range of hardware, especially if such modifications disadvantage other users ... but in this case I think it's OK. The question is then whether the b43/b43legacy modules (which are needed for older Broadcom devices) can also co-exist with the wl module without problems. Give me a day or two and I will give you an accurate answer.

zigbert wrote:
I have earlier included your updated ati driver in Puppy Stardust.

Mmm. I have compiled so many specialised drivers over the past 5 years I can't remember which ATI driver you're referring to!
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 4 of 8 [108 Posts]   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:  

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.0963s ][ Queries: 13 (0.0053s) ][ GZIP on ]