Puppy Linux Discussion Forum

[AlexS]

So I tried the pet you prepared, but after rebooting I could not even see the wlan0 interface.

My system uses the default b43 you get from puppy lucid 5.1

When I try to load the b43 module, I get the following message:

[tempestuous]

[AlexS]

Sorry for the wait, I got side tracked.

I created a fresh pup save file, in which the only thing I did was to install firefox.

I tried to load that pet, but in this case the pet instalation completely failed.

I'm wondering if the file is corrupted?

Here is the MD5 as given by GtkHash:
7fb089ee9bd647f706c76349a015fef1

[tempestuous]

Yes, that md5sum is wrong for rfkill-upgrade-k2.6.33.2.pet. It should be 9abeee2d109808002d7877758dc8a759
I will have access to Dell Mini this coming week end, and I will try the wifi switch myself.

[tempestuous]

The Linux drivers for Intel gigabit LAN adaptors; e1000/e1000e/igb, seem to require constant updating to keep up with the latest Intel ethernet devices.
Here are the latest versions of the Intel gigabit LAN Linux drivers, released by Intel in August/September 2010.

- For Intel 8254x PCI and PCI-X devices the compatible driver is e1000
- For Intel 82563/6/7, 82571/2/3/4/7/8, and 82583 PCI-E devices the compatible driver is e1000e
- For Intel 82575/6 and 82580 PCI-E devices the compatible driver is igb

These drivers will overwrite the older versions already contained in Puppy 5.1.
After installing any of these dotpets, reboot.

[tempestuous]

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.

[mories]

Please, tempestuous, can you explain the steps to compile a kernel module.
I compiled external modules (like the ATI Catalyst), but now I have problems with internal kernel modules.
I have installed the packages (sfs) devx and kernel_src, and I want to recompile the i915 module.
The steps that follow are:

make modules_prepare
make drivers/gpu/drm/i915/i915.ko

The module compile correctly, but at load (modprobe) I get the error
"no symbol version for module_layout"

Even without changing anything in the original configuration of the kernel, I get the same error.
I've tried both lupu as quirky, with its corresponding devx.
What am I doing wrong?

The reason for wanting to recompile the i915 is that the module and kernel 2.6.33.2 including quirky and lupu not loaded (and therefore not Xorg works) for the graphics controller integrated into the Intel Core i5, but with the module and kernel 2.6.32.24 included in Puppy Squeeze 009 it load properly.
So there must be some difference in the compilation of these kernel and modules.
Thanks in advance

[tempestuous]

[mories]

Thank you tempestuous, for your attention.

But this
make menuconfig
make bzImage
make modules
make modules_install
change and recompile the kernel and all modules.

I want to rebuild and change only the i915 module. Is it possible to do that?.
For example, as the driver xhci in your previous post.

Greetings.

[tempestuous]

Realtek N-mode wifi devices

Realtek has an extensive range of N-mode wifi chipsets, for miniPCI and USB devices.
Puppy 5.1.x already contains 3 "official" drivers for these devices:
r8192_pci
r8192u_usb
r8192s_usb

But there are quite a lot of other Realtek-based wifi devices not supported by these drivers.
So here are the proprietary Realtek wifi drivers for all other unsupported Realtek N-mode wifi devices (at October 2010):
PCI
r8192se_pci is for RTL8191SE-VA2/8192SE chips * see note below
r8192ce_pci is for RTL8188CE/8192CE-VA4 chips
USB
8712u is for RTL8188SU/8191SU/8192SU/8712SU chips
8192cu is for RTL8188CUS/8188CE-VAU/8192CU chips

UPDATE June 2014 - regarding these TP-Link USB dongles:
TL-WN723N v1 is supported by 8712u
TL-WN723N v2 is supported by 8192cu
TL-WN725N v1 is supported by 8192cu
But two new dongles have appeared:
TL-WN723N v3
TL-WN725N v2
Both of these adaptors require the new 8188eu driver, which I have just compiled and uploaded here -
www.smokey01.com/tempestuous/8188eu-rev382-k2.6.33.2.pet
I obtained the source code from
https://github.com/lwfinger/rtl8188eu/

* Regarding the r8192se_pci driver: this will conflict with the standard r8192_pci driver for one (and only one) device ID:
10EC:8192

Otherwise, Realtek have done a good job of providing these drivers only for devices not already supported by the standard kernel drivers.
There are no other overlapping ID's or conflicts.

USB users:
There's a chance the 2 USB drivers here may fail to work properly. If so, please run the "dmesg" command and report any error messages relating to the Realtek driver, and especially anything relating to missing firmware.

After installing any of these drivers, reboot. Run the Network Wizard to check if your device is now recognised.

[tempestuous]

Here is an updated version of the Atheros/Attansic atl1e ethernet driver,
to add support for some additional AR8132/AR8152 chipsets.
Device ID's now supported by the driver:

1969:1026
1969:1062
1969:1063
1969:1066
1969:1067
1969:1073
1969:1083
1969:2060
1969:2062

This driver will overwrite the original atl1e driver in Puppy 5.1.x
After installing this dotpet, reboot.
The new driver should automatically load for compatible ethernet devices detected at boot up.
Just configure your ethernet connection in the Network Wizard.

This is vendor-supplied source code.
Kernels from 2.6.36 onwards should have the opensource driver updated to support these ID's.

Update: this driver is needed with
- Acer Aspire One D250 netbook (recent models)
- ASUS P5KPL-CM motherboard

[tempestuous]

Driver support for webcams based on the SONiX SN9C chip (often branded "Microdia") is somewhat strange in the 2.6.33 kernel.
This range of devices is supported by two different drivers: sn9c102 and gspca_sn9c20x. And unfortunately if both drivers are enabled during kernel configuration then 13 USB device ID's are automatically disabled in the sn9c102 driver. I suspect this may be due to the developers of each driver not communicating with each other!

So I have recompiled the sn9c102 driver, with the gspca driver disabled, resulting in an updated sn9c102 driver with those 13 USB device ID's now enabled. These are the additional USB ID's -

0471:0327
0471:0328
0C45:6001
0C45:6005
0C45:6007
0C45:602C
0C45:608F
0C45:60B0
0C45:00F5
0C45:00F7
0C45:613A
0C45:613C
0C45:613E

After installing this dotpet, reboot.
Then plug in your webcam device. Puppy should automatically load the sn9c102 driver.
Now you can try a webcam viewer application such as Luvcview ... but the colours may look strange. That's because this driver has historically needed the libv4l library to work properly. If so, see the next post.

[tempestuous]

Some webcam drivers generate their video image in a pixelformat video/webcam applications cannot handle, so the libv4l library is required.
Once you have installed the libv4l dotpet from this post, it needs to be enabled, by running this command -

[tempestuous]

I just updated the WPA-configuration hotfix in the earlier post, so that WPA encryption will work with the hostap family of wifi drivers -
http://www.murga-linux.com/puppy/viewtopic.php?p=448997#448997

[tempestuous]

Ralink USB wifi devices

rt5370sta for the latest RT5370 devices, added Sep 24 2011

rt3572sta for RT2870/RT35xx
Older RT2870 wifi devices will be supported either by the rt2800usb or rt2870sta opensource drivers already contained in Puppy.
The Tenda W541U V2.0, for example, is now supported by Puppy's rt2800usb driver.
But very recent RT2870 wifi devices will only be supported by the proprietary rt3572sta driver, now attached. This driver now supports the latest RT35xx wifi chips as well.
I have further modified this driver to support these additional wifi devices:
- Buffalo WLI-UC-GN (older version) USB ID 0411:014f
- Linksys AE1000, USB ID 13b1:002f

rt3370sta for RT3070/RT3370
RT3070 wifi devices are supported, confusingly, also by the rt2870sta opensource driver already in Puppy. But there are quite a number of more recent RT3070 devices which are only supported by the latest proprietary rt3370sta driver, now attached. This driver now supports the latest RT3370 wifi chips as well.
I have further modified this driver to support these additional wifi devices:
- Belkin F6D4050 v2000, USB ID 050d:935b
- Buffalo WLI-UC-GN (newer version) USB ID 0411:015d
- Keebox W150NU, USB ID 14b2:3c2c

EDIT, April 15 2011: some of these older RT3070 devices just mentioned, as well as the Linksys WUSB100 v2 may be better supported by an older version of the rt3070sta driver, available later in this thread -
http://www.murga-linux.com/puppy/viewtopic.php?p=513360#513360

After installing either of these dotpets, reboot.