Drivers for Puppy 5.1-5.2.8 with 2.6.33.2 kernel

For drivers and kernel modules.
Post Reply
Message
Author
night_mare007
Posts: 30
Joined: Sun 07 Aug 2011, 17:13

#101 Post by night_mare007 »

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.
I took your idea, and compiled the XHCI on a Macpup 5.2.8 ( it's based on puppy 5.2.8 without the 001 update ) with kernel 2.6.33.2 as this post relates.
Then I packed ONLY the XHCI.KO driver file and added to the install script the following command that you've missed: "modeprobe xhci" in order to enable immidiatly the driver after it is installed.

I have USB 3.0 PCI-Express card (54mm), and this driver woke it up alive !
( apparently Puppy has "PCI-E host card module" driver already installed, which also needed to run this type of card )

P.S - As tempestuous wrote, just to be sure, after the installation process - REBOOT !
Attachments
USB3_XHCI_Driver_Support.pet
(21 KiB) Downloaded 638 times
Last edited by night_mare007 on Thu 22 Sep 2011, 19:03, edited 1 time in total.

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

#102 Post by tempestuous »

night_mare007 wrote:... and added to the install script the following command that you've missed: "modeprobe xhci" in order to enable immidiatly the driver after it is installed.
When posting additional drivers in this thread, I consider it a practice fraught with risk to manually load the new driver as part of the installation process. Instead, I usually advise users to reboot, since this takes Puppy through the full auto-detection process, and they can then know for sure whether the new driver will auto-load.
In that regard, and for good reason, I didn't "miss" a manual load command as part of the installer package.

In the earlier post in question, I wrote this:
tempestuous wrote:After installing this dotpet, reboot, and the xhci driver should automatically load for any compatible interface detected at boot up.
I know this to be true, in theory, because when I query the driver, it returns this:

Code: Select all

alias: pci:v*d*sv*sd*bc0Csc03i30*
So are you saying that the xhci driver is not automatically loaded at boot up?
That's a far more serious (and relevant) issue, and if true, affected users should have reported this.

night_mare007
Posts: 30
Joined: Sun 07 Aug 2011, 17:13

#103 Post by night_mare007 »

tempestuous wrote:So are you saying that the xhci driver is not automatically loaded at boot up?
You got me me wrong...
Just to be sure I made a restart and just after the puppy completely logged in I plugged in a usb-flash-card, and after 3-4 sec the flashcard started to blink as it should.
Then I opened Pmount - and the device was recognized correctly, as well as mounting and ROXing R/W commands.
So IT DOES AUTO LOAD and work as expected. :P

P.S
Pardon me if what I wrote sound a bit like I criticize your work...
it was not my intentions. :oops:
You gave me the final solution and extractions about how to install the .KO driver. - so THANKS ! :wink:

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

#104 Post by tempestuous »

Patched cx24123 DVB driver for the TechniSat SkyStar S2 PCI TV tuner card
not successful.
Now removed.

dragonneus
Posts: 2
Joined: Fri 16 Mar 2007, 20:23

Puppy 5.2.8 2.6.33.2 RT5370 woes

#105 Post by dragonneus »

Loaded pet for the RT5370 on my puppy distro 5.2.8 kernel 2.6.33.2. Tried WPA and WPA2 encryption. Driver loads fine, sees device as RA0 as it should. Sees my ssid and connects, receives the proper dhcp supplied IP address (also tried static) . Testing by pinging website.com and it will resolve to the proper IP address. When I try to open any browser it does not go to any web page. The device itself is fine as ive used it on an ubuntu 11.04 laptop. Ive tried to statically assign dns servers and that doesnt seem to make a difference. Ping times although work sometimes have erratic ping responses IE 200ms,150ms,1900ms,2500ms 50ms and so on.

Please throw this puppy a knowledge bone?

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

#106 Post by tempestuous »

The cdc-acm driver in Puppy 5.1.x recognises 43 different Nokia phone device ID's.
Using the 2.6.39 kernel source as a reference, I have just patched this driver to recognise an additional 14 Nokia telephone models. This updated driver should now be suitable for the two specific requests on the forum to date:
Nokia N8 - forum member Dave_G
Nokia C5 - forum member rameshiyer

Plug in your phone after you have installed this dotpet, and the new cdc-acm driver should load automatically.

EDIT:
Your phone must be set to the correct mode. A forum user with recent model Nokia C5 reported that the mode-options in the phone's menu are:
1. PC Suite
2. Mass Storage
3. Image Transfer
4. Media Transfer
5. PC to Web
The PC to Web setting failed, but the PC Suite setting was successful.
Attachments
cdc-acm-update-k2.6.33.2.pet
for Puppy 5.1 - 5.2.8
(10.62 KiB) Downloaded 1214 times
Last edited by tempestuous on Thu 03 Nov 2011, 11:10, edited 1 time in total.

rameshiyer

Nokia Connection

#107 Post by rameshiyer »

Dear Sir

Thank you very much. I will try with your pet and let you know the status. Anyway thank you very much for extending your knowledge with me.

Hammerknight
Posts: 5
Joined: Wed 02 Nov 2011, 15:56

#108 Post by Hammerknight »

Drivers for ATI RADEON 9200 pro

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

#109 Post by tempestuous »

Hammerknight wrote:Drivers for ATI RADEON 9200 pro
Well I just compiled the AMD/ATI Catalyst 11.10 graphics driver ... but I see it's not necessary -
playdayz already provided version 10.10 here -
http://www.murga-linux.com/puppy/viewto ... 993#467993
I'm talking about Puppy Lucid 5.1 - 5.2.8, of course.

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

#110 Post by playdayz »

I just compiled the AMD/ATI Catalyst 11.10 graphics driver but I see it's not necessary -
playdayz already provided version 10.10 here -
http://www.murga-linux.com/puppy/viewto ... 993#467993
I'm talking about Puppy Lucid 5.1 - 5.2.8, of course.
I'm glad you did. I have been meaning to do it myself. It is not necessary for the 9200 but it should cover any brand new ATI cards. Could you provide a link and I will post it. Thanks.

In Lucid, users can also get the ati and nvidia proprietary drivers as well as the open source glx driver (Xorg_High) in Quickpet -> Drivers.

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

WLAN not detected in ASUS Zenbook

#111 Post by csshin »

I run Puppy 5.2.8, both standard edition and also those with newer kernels (up to 3.1.0) found on this forum, all cannot detect the wireless interface in an ASUS Zenbook UX31E. I tried icepuppy, three-headed dogs and snow puppy but still no luck.

The wireless chipset used is Atheros AR9485. I tried the new ath9k drivers and firmware pet in this thread but still the interface is not detected.

I tried to use ndiswrapper on the WIN7 driver that comes with the machine but the response is something like: it is not a correct file.

The same is true for the USB wired net interface with chipset AXI...(sorry I forgot the exact name).

Are these chipsets too new to be supported yet?

I attempted to download the up to date compat wireless package hoping to compile a new driver. But it responds that the kernel has something not set so that it cannot get through and just leave the original drivers intact.

I am desperate with this new machine because there is no network interface and problem with wakeup from suspend (that will be a new thread) .

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#112 Post by rcrsn51 »

@csshin:While you are waiting for tempestuous, you should determine the vendor/product ID codes for this device. Type

Code: Select all

lspci -nn
The codes are in square brackets, like [168c:002e].

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

WLAN not detected in ASUS Zenbook

#113 Post by csshin »

rcrsn51 wrote:While you are waiting for tempestuous, you should determine the vendor/product ID codes for this device. Type

Code: Select all

lspci -nn
The codes are in square brackets, like [168c:002e].
I try to type the result here:

00:00.0 Host bridge [0600]: Intel Corporation Device [8086:0104] (rev 09)
00:02.0 VGA compatible controller [0030]: Intel Corporation Device [8086:0116] (rev 09)
00:16.0 Communication controller [0780]: Intel Corporation Cougar Point HECI Controller #1 [8086:1c3a] (rev 04)
00:1b.0 Audio device [0403]: Intel Corporation Cougar Point High Definition Audio Controller [8086:1c20] (rev 05)
00:1c.0 PCI bridge [0604]: Intel Corporation Cougar Point PCI Express Root Port 1 [8086:1c10] (rev b5)
00:1c.1 PCI bridge [0604]: Intel Corporation Cougar Point PCI Express Root Port 2 [8086:1c12] (rev b5)
00:1c.3 PCI bridge [0604]: Intel Corporation Cougar Point PCI Express Root Port 4 [8086:1c16] (rev b5)
00:1d.0 USB Controller [0c03]: Intel Corporation Cougar Point USB Enhanced Host Controller #1 [8086:1c26] (rev 05)
00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:1c4d] (rev 05)
00:1f.2 SATA controller [0106]: Intel Corporation Cougar Point SATA AHCI Controller [8086:1c03] (rev 05)
00:1f.3 SMBus [0c05]: Intel Corporation Cougar Point SMBus Controller [8086:1c22] (rev 05)
02:00.0 Network controller [0280]: Atheros Communication Inc. Device [168c:0032] (rev ff)
03:00.0 USB controller [0c03]: Device [1b73:1009] (rev 02)

By the way, a question not concerned with the WLAN driver but may concern with the above hardware: the laptop cannot wake up from suspend (acpitool -s). I check the wake up device and found all except a SLPB were disabled. I can enable all the PCI related device and a EHC1, but all the others, including USB1 through USB7, refuse to be enabled. So still cannot wakeup.


[Edited] to add one more PCI bridge and a network controller, I forgot to switch the camera, bluetooth and wireless back on in the Bios during the first attemp.
Last edited by csshin on Tue 08 Nov 2011, 00:42, edited 1 time in total.

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#114 Post by rcrsn51 »

Was there no listing for either an Ethernet or WLAN controller?

[Edit] Apparently, these things don't have an Ethernet port.

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

WLAN not detected in ASUS Zenbook

#115 Post by csshin »

That is all output I get. Perhaps it reflects the fact that the network interfaces were not recognized at all.

From the WIN7 that bundles with the laptop, I was able to determine the wireless lan is an Atheros AR9485WB-EG Wireless Network adapter. The USB dongle for wired lan is ASIX AX88772B USB2.0 to Fast Ethernet Adapter.

[added] Sorry I switched the bluetooth and wireless off in the BIOS after all attempts to detect them failed, in order to lengthen the battery range. I have added the new entries in the original post.
Last edited by csshin on Tue 08 Nov 2011, 00:46, edited 1 time in total.

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#116 Post by rcrsn51 »

I wonder what would happen if you booted with Three-headed Dog and ran "lspci -nn" again. Maybe the newer kernel would reveal more devices.

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

WLAN not detected in ASUS Zenbook

#117 Post by csshin »

Sorry I have forgotten that after a few days' testing with the varies distros but still cannot get the WLAN detected, I switched the bluetooth and wireless off in the BIOS last night in order to lengthen the battery range.

I have switched all device on in the Bios and have the LAN USB dongle plugged before booting and did a [lspci -nn] again. I have added the new entries in the original post.

By the way I am running icepuppy014, which I think has a slightly more recent kernel than the three-headed dog. I will test out the lspci command with other distros and report back if there is anything different.

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#118 Post by rcrsn51 »

So as not to hijack tempestuous' thread, I am sending you a PM.

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

#119 Post by tempestuous »

csshin wrote:I forgot to switch the camera, bluetooth and wireless back on in the Bios during the first attemp.
Yep, I guessed you had your wifi disabled in bios.

csshin wrote:02:00.0 Network controller [0280]: Atheros Communication Inc. Device [168c:0032]
There's your wifi device, and it's quite new. This device ID is not recognised by the ath9k driver in Lucid 5.1-5.2.8.
I just tried to patch recognition of this ID into the driver, but unfortunately several other source files need to be updated as well - it's complicated, and the patched driver might still fail.

So you definitely need to move up to a more recent kernel version, with newer ath9k driver.
I just checked the 2.6.37 kernel ... and the ath9k driver still doesn't recognise your device there, either.
So Slacko 5.3 and Three-Headed Dog won't work.

But it appears that your wifi device is recognised from the 2.6.39 kernel onwards, so you could use -

Dpup Exprimo 5.X.9
http://www.murga-linux.com/puppy/viewtopic.php?t=70399

Polarpup-005
http://www.murga-linux.com/puppy/viewtopic.php?t=68796

Guy Dog 5.0.1
http://www.murga-linux.com/puppy/viewtopic.php?t=72576

and maybe also one of the experimental releases with 3.x kernel ??

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

WLAN not detected in ASUS Zenbook

#120 Post by csshin »

tempestuous wrote:
So you definitely need to move up to a more recent kernel version, with newer ath9k driver.
.
.
.
and maybe also one of the experimental releases with 3.x kernel ??
Thank you very much rcrsn51 and tempestuous for your prompt responses.

I have tested rcrsn51's compat wireless pet (from PM) without success on icepuppy014 (kernel 2.6.38.x?) and also on wuxiandianzi 's lupu 5.28 kernel 3.1.0. For the latter, it refused to save a personal storage file and so I cannot test again after installation and reboot.

I will try to download the other pups and test it out again. That will take some time as I have a slow internet connection.

By the way do I need to install the ath9k firmware pet besides rcrsn51's compat wireless pet to test?

Post Reply