Drivers for Puppy 5.1-5.2.8 with 2.6.33.2 kernel

For drivers and kernel modules.
Post Reply
Message
Author
tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#121 Post by tempestuous »

csshin wrote:By the way do I need to install the ath9k firmware pet besides rcrsn51's compat wireless pet to test?
No. The firmware you're probably referring to is for the ath9k_htc driver.
This is a different driver for USB variants of the Atheros chipset. It's unrelated to PCI/Cardbus devices with the Atheros chipset.

csshin
Posts: 45
Joined: Sun 14 Oct 2007, 14:36

WLAN not detected in ASUS Zenbook (Solved)

#122 Post by csshin »

Dpup Exprimo 5.X.9 and Guy Dog 5.0.1 successfully recognized the Atheros AR9485 chip in the WLAN of ASUS Zenbook out of the box.

rcrsn51's compat wireless pets for kernel 2.6.33.x worked for lupu 528. That for kernel 2.6.37.x worked for Three-headed dog.

Thank you all for your help.

I still have the problem of getting the Sentelic touchpad (can move and tap to click but not configurable for other touchpad functions like the synaptic pad) and suspend (cannot enable the keyboard or any USB device as wakeup tool so cannot recover from suspend) to work.
Do you have any direction to point me to?

User avatar
playdayz
Posts: 3799
Joined: Fri 25 Apr 2008, 18:57

#123 Post by playdayz »

tempestuous, I have received a request for usb3 in 5.2.8. I do not even know if this is a simple kernel mode driver, or what is involved. Do you have any recommendations?

I have also been informed that usb3 works in Slacko 5.3 but not in Three-Headed Dog which uses the same kernel. Does that mean there is something else involved other than a kernel driver?

Thanks for any help.

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#124 Post by tempestuous »

Yes, USB3.0 is a standard kernel module. In the kernel configuration it's found at -
Device Drivers > USB support > xHCI HCD (USB 3.0) support

playdayz wrote:I have also been informed that usb3 works in Slacko 5.3 but not in Three-Headed Dog which uses the same kernel. Does that mean there is something else involved other than a kernel driver?
Not to my knowledge. In the case of the failing Three-Headed Dog installation, first check that the module is actually included -

Code: Select all

modinfo xhci
and also check "dmesg" for clues.

Lumsdoni
Posts: 5
Joined: Tue 15 Nov 2011, 13:16

Request

#125 Post by Lumsdoni »

tempestuous wrote:I have just added the Ralink rt5390sta wifi driver to the earlier post in this thead -
http://www.murga-linux.com/puppy/viewto ... 618#494618

I still have one additional Ralink wifi driver to add; rt3090sta
but no one has asked for it yet.
I would very much like this please, if you still have it.

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#126 Post by tempestuous »

First please confirm that the driver is actually compatible:
i) tell us the brand/model of your wifi device.
ii) give us your device ID's, by running this command -

Code: Select all

lspci -n

Lumsdoni
Posts: 5
Joined: Tue 15 Nov 2011, 13:16

#127 Post by Lumsdoni »

tempestuous wrote:First please confirm that the driver is actually compatible:
i) tell us the brand/model of your wifi device.
ii) give us your device ID's, by running this command -

Code: Select all

lspci -n
i) 02:00.0 Network controller: Ralink corp. RT3090 Wireless 802.11n 1T/1R PCIe

ii)
00:00.0 0600: 1022:9600
00:01.0 0604: 1022:9602
00:04.0 0604: 1022:9604
00:05.0 0604: 1022:9605
00:06.0 0604: 1022:9606
00:11.0 0106: 1002:4390
00:12.0 0c03: 1002:4397
00:12.1 0c03: 1002:4398
00:12.2 0c03: 1002:4396
00:13.0 0c03: 1002:4397
00:13.1 0c03: 1002:4398
00:13.2 0c03: 1002:4396
00:14.0 0c05: 1002:4385 (rev 3c)
00:14.1 0101: 1002:439c
00:14.2 0403: 1002:4383
00:14.3 0601: 1002:439d
00:14.4 0604: 1002:4384
00:18.0 0600: 1022:1100
00:18.1 0600: 1022:1101
00:18.2 0600: 1022:1102
00:18.3 0600: 1022:1103
01:05.0 0300: 1002:9612
01:05.1 0403: 1002:960f
02:00.0 0280: 1814:3090
03:00.0 0200: 10ec:8168 (rev 03)

I managed to get it working using the driver posted on Puppy 4.3, but obviously would prefer to use the latest version of Puppy.

Thank you for your time.

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#128 Post by tempestuous »

Lumsdoni wrote:02:00.0 0280: 1814:3090
PCI device ID 1814:3090 is definitely compatible with the rt3090sta driver.
Driver now posted in the earlier thread -
http://www.murga-linux.com/puppy/viewto ... 618#494618

Lumsdoni
Posts: 5
Joined: Tue 15 Nov 2011, 13:16

#129 Post by Lumsdoni »

Thanks, will install Puppy 5.3 and try it, if not 5.2 and report back.

Lumsdoni
Posts: 5
Joined: Tue 15 Nov 2011, 13:16

#130 Post by Lumsdoni »

Clean install of 5.3.

using the preloaded rt2800pci module I got no wlan0, so unloaded it.
Installed your 3090 module, when loaded it detected new interface wlan0.

Ran Internet Wizard, clicked SCAN, and keep getting error

FAILED to raise interface wlan0
Failed command was ifconfig wlan0 up
Error returned was: ifconfig SIOCSIFFLAGS: Operation not permitted.

This is what i got before. Wireless is definitely working on Ubuntu, Puppy 4.3 and Win7. Any ideas?

EDIT.

Tried on Puppy 4.2.8

Tried to load 3090sta through Wizard and got a device or kernel is busy error.

I then ran modprobe -r rt2860sta
then modprobe rt3090sta

Now when I try to setup Wireless it stops at te "Test wlan0" stage on the WIzard with the error.

FAILED to raise interface wlan0
Failed command was ifconfig wlan0 up
Error returned was: ifconfig SIOCSIFFLAGS: Operation not permitted.

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#131 Post by tempestuous »

Lumsdoni wrote:Clean install of 5.3.
The drivers in this thread are compatible only with Puppy Lucid 5.1 - 5.2.8.

For Puppy 5.3, you will need to talk to the Slacko developers.

Lumsdoni
Posts: 5
Joined: Tue 15 Nov 2011, 13:16

#132 Post by Lumsdoni »

tempestuous wrote:
Lumsdoni wrote:Clean install of 5.3.
The drivers in this thread are compatible only with Puppy Lucid 5.1 - 5.2.8.

For Puppy 5.3, you will need to talk to the Slacko developers.
Apologies, please see edit above re-clean install of 5.2.8

Strangely, I unloaded the 3090 module and reloaded it, and the interface changed from wlan0 to ra0.

And bingo, up and running.

Thank you so, so much for your patience, time and help.

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#133 Post by tempestuous »

Here is the dvb-usb-af903x DVB driver,
for TV tuner USB devices based on the Afatech AF9035 chipset.

I have patched the driver to support the Asus U3100 Mini Plus tuner dongle,
as per instructions here -
http://linuxtv.org/wiki/index.php/Asus_ ... plus_DVB-T

Apparently the ASUS U3100mini dongle is incorrectly recognised in Linux by the usbhid driver as an input device.
So this package includes a configuration file which will stop the usbhid driver from claiming the tuner, and allow the new driver to load properly. If anyone is interested, the configuration file is /etc/modprobe.d/dvb-usb-af903x.conf

Thus, it's essential that you reboot after installing this dotpet.

This package includes a firmware file; dvb-usb-af9035-01.fw
but this only affects the InfraRed remote-control function of the device. And it might be necessary to install additional Linux utilities to get InfraRed working, so you would need to experiment here.

UPDATE: I have also attached the w_scan utility.

User avatar
Subito Piano
Posts: 731
Joined: Mon 28 May 2007, 03:12
Location: UPSTATE New York
Contact:

Thank you, thank you...

#134 Post by Subito Piano »

Tempestuous -- THANK YOU!!! Friends had an Acer with the Atheros wi-fi -- 500MB RAM with Vista on it?!?!?!? This saved an otherwise nice little computer. Puppy worked great but the wireless card was giving me fits! Works perfectly now. :-)

User avatar
otropogo
Posts: 764
Joined: Sat 24 Oct 2009, 15:17
Location: Montreal
Contact:

could you update this driver please?

#135 Post by otropogo »

tempestuous wrote:Here is the USB 3.0 Linux driver, which was not enabled in the standard Puppy 5.1.x kernel.
The driver is called xhci
I have also included the upgraded isp1760 USB driver, which is apparently USB 3.0 compatible, though very few Puppy users will ever use this driver because the relevant interface is found on embedded devices.
After installing this dotpet, reboot, and the xhci driver should automatically load for any compatible interface detected at boot up.
Have been using this driver for some months now, and it is no longer working at all. As I reported initially, at first its only problem was with lack of hot-plug capability. But now it consistently mounts my ntfs USB3 drive as read only. And strangely, this condition then persists when the drive is moved to the USB2 port.

No such situation arises in lupu 5.2.8 on my desktop machine which has no USB3 port, and therefore no USB3 driver installed. Nor have I encountered this problem with Slacko 5.29.6 unpetted. It detects the same USB3 drive on the USB3 port consistently without reporting any filesystem errors (lupu 5.3 can't detect anything at all on my expresscard USB3 ports).

Very frustrating. In order to back up files on my USB3 enabled laptop, I have to either reboot with Slacko 5.2.9 (which is seriously crippled in other ways) or with Windows.

Since I can't find any drivers for USB3 in the repositories, I assume they are compiled into the Linux Kernel, and were somehow corrupted or removed when Slacko 5.3 was compiled.
otropogo@gmail.com facebook.com/otropogo

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#136 Post by tempestuous »

The xhci driver is a standard kernel module - the only way to update it is to move up to a more recent kernel version (such as Slacko) ...
... but it sounds to me that the xhci driver is not at fault. The driver should have no impact on the read/write status of the drive - I suspect it's more a case of how the NTFS-3G filesystem driver detects the condition of the NTFS filesystem on your drive. In other words, the NTFS-3G driver is possibly "unhappy" about the condition of the filesystem, so mounts it as read-only.

I'm not an expert in this area, so you should consider making a separate post on this subject ...
but a quick thing to try is to connect the drive to a Windows XP computer, then defragment the drive by going to
Start > Programs > Accessories > System Tools > Disk Degfragmenter

Once defragmented, reconnect the drive to Puppy and see if you get a better result.

User avatar
otropogo
Posts: 764
Joined: Sat 24 Oct 2009, 15:17
Location: Montreal
Contact:

#137 Post by otropogo »

tempestuous wrote:The xhci driver is a standard kernel module - the only way to update it is to move up to a more recent kernel version (such as Slacko) ...
I wonder then why Slacko 5.3 is unable to detect anything on the USB3 ports?
... but it sounds to me that the xhci driver is not at fault. The driver should have no impact on the read/write status of the drive - I suspect it's more a case of how the NTFS-3G filesystem driver detects the condition of the NTFS filesystem on your drive. In other words, the NTFS-3G driver is possibly "unhappy" about the condition of the filesystem, so mounts it as read-only.
Then how to explain the fact that Puppy 5.2.8 has no problem with the drive on the desktop that doesn't have the USB3 driver installed, only on the one that does? Or the fact that Slacko 5.29.6, Windows 7, and Win2K report no problems with the drive? All of these mount the drive as writable every time. OTOH, the system that reports the ntfs-3g problem is inconsistent, and sometimes changes its mind and finds the partition acceptable. Since I boot from CD every time, I conclude the difference stems from the lupusave 2fs file on the USB3 PC.

I'm not an expert in this area, so you should consider making a separate post on this subject ...
but a quick thing to try is to connect the drive to a Windows XP computer, then defragment the drive by going to
Start > Programs > Accessories > System Tools > Disk Degfragmenter

Once defragmented, reconnect the drive to Puppy and see if you get a better result.
OK. Any suggestion as to where I should post it and with what subject heading? Most of my past posts on hardware issues have failed to evoke any response from the technical gurus.

As it happens, I don't have a system with XP installed at the moment. But more importantly, I don't want to "swallow a spider to catch the fly..." unless the indications are very persuasive that this is the only solution.

Update: my mistake, the ntfs-3g error DOES occur on the system without the USB3 driver. It's intermittent, and I'd forgotten that. So intermittent that two ntfs drives can be mounted on the same port, and one is mounted normally, the other read only. And the problem can even be resolved sometimes by simply moving the drive from one port to another or even, more rarely, by unmounting, unplugging, and replugging, remounting it in the same place. Most frequently, though, these tricks result in the drive disappearing and failing to reappear without a reboot...

NB: I have discovered since my original post that the problem doesn't occur with Racy 5.2.2.

Unfortunately, I haven't been able to figure out how to install ufraw, rawstudio, or a working copy of xfprot in Racy...
otropogo@gmail.com facebook.com/otropogo

csshin
Posts: 45
Joined: Sun 14 Oct 2007, 14:36

Re: Sound card not detected in ASUS Zenbook (solved)

#138 Post by csshin »

Sound is OK in Exprimo 5.X.10.2. But there is no speaker icon on the taskbar nor any sound output in Lupu 5.2.8. I would like to run Lupu 5.2.8 as it seems to give a better battery life than Exprimo 5.X.10.2.


Edit Dec.22,2011
This has now been solved by installing alsa_driver-1.0.24.pet.

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#139 Post by tempestuous »

Here is the meye webcam driver for the Sony Motion Eye device found in certain Sony VAIO PCG-C1* laptops.
This driver depends on the sony-laptop driver, which in turn depends on the rfkill driver, which was not enabled in the standard 5.1.x-5.2.x Puppy releases. This driver dotpet package provides these additional drivers.
Be aware that the addition of the rfkill driver might break Puppy's existing wifi drivers. If your find that your wifi driver stops working after installing this package, you will need to install my updated rfkill-compatible wifi drivers from earlier in this thread -
http://www.murga-linux.com/puppy/viewto ... 093#452093

Also be aware there are several generations of Motion Eye cameras. The only one supported by this driver is device ID 136B:FF01
If in doubt, run this command to check which camera device ID you have -

Code: Select all

lspci -n
INSTRUCTIONS:
After installing this dotpet, reboot. Run the "lsmod" command to check that the meye driver and sony-laptop driver have both automatically loaded. If not, you need to configure Puppy to do so. Go to
Menu > System > BootManager configure bootup > Click here to add a new module:
Add the "meye" module to the right-hand pane, then click "OK".
Now reboot again. Your new driver should be loaded and ready to use. As always, a suitable application such as mplayer must then be used to display the webcam image.
Attachments
meye-k2.6.33.2.pet
for Puppy 5.1 - 5.2.8
(37.92 KiB) Downloaded 1157 times

IanJ
Posts: 3
Joined: Sun 25 Dec 2011, 00:26

#140 Post by IanJ »

Thanks very much for compiling these modules and making a dotpet.

I've installed the dotpet to my vaio c1xd and rebooted but lsmod doesn't show the modules loaded. I then tried to modprobe them in order to load them.

modprobe rfkill (loads ok)
modprobe sony_laptop ('FATAL: Error inserting sony_laptop (/lib/modules/2.6.33.2/kernel/drivers/platform/x86/sony-laptop.ko): No such device')

There are some notes in the module .txt asking people to test this module as it is the replacement for the older sonypi module; sonypi works for me and enables the jogdial but I get the above error when loading sony_laptop. I made sure sonypi wasn't loaded before trying to load sony_laptop.

Is there anything further I can do to debug this or should I contact the person maintaining the sony_laptop kernel module?

Thanks for your efforts.

Ian

Post Reply