(old)Puppy Linux Discussion Forum

@tempestuos, do you know if the eeepc pets enable the 4 silver hotkeys of the 901 and 1000 models? just wondering if there's a way to map those keys.
also to other 901/1000 owners, appreciate if you share your methods if you've managed to get those 4 silver hotkeys working.

ta,

venger wrote:@tempestuos, do you know if the eeepc pets enable the 4 silver hotkeys of the 901 and 1000 models? just wondering if there's a way to map those keys.
also to other 901/1000 owners, appreciate if you share your methods if you've managed to get those 4 silver hotkeys working.

ta,

I think this patchset might be for those, in case tempestuous wants to try and patch the sources he's using...

venger wrote:@tempestuos, do you know if the eeepc pets enable the 4 silver hotkeys of the 901 and 1000 models? just wondering if there's a way to map those keys.

It's quite easy to map those keys (or any keys). Go here -
http://robertek.brevnov.net/files/linux ... pi-eee901/
and look at eee-handler.sh. This is the Arch Linux equivalent of /etc/acpi/hotkey.sh which is provided in my dotpets.
You can paste parts of the ArchLinux file into mine, and set it up any way you like.
The four silver keys are defined as:
0000001a)
0000001b)
0000001c)
0000001d)

ArchLinux uses the first silver key to toggle the LCD screen off/on, and the second silver key to toggle the resolution of the LCD screen and external VGA port.

From the ArchLinux files you would need to copy over -
buttonblank.sh (and make executable)
buttonres.sh (and make executable)
eee.conf
user

into /etc/acpi

Wireless modems (GPRS/EDGE and UMTS/HSDPA) - USB
Early USB HSDPA modems are supported by the standard "usbserial" module in Puppy. General information here -
http://www.pharscape.org/usbserial.html
There's a good connection HOWTO by forum member wescht here -
http://www.murga-linux.com/puppy/viewtopic.php?t=12603

The next generation USB devices are supported by the "option" module.
UPDATE April 1 2009
"option" module patched with device ID's from those defined in kernel 2.6.29. Broad support includes models by Huawei, Novatel, Amoi, Anydata, Bandrich, BenQ, Dell, Kyocera, Maxon, Onda, Qualcomm, Telit, ZTE.

More recent USB wireless modems often require the "hso" module, now attached.
Information here -
http://www.pharscape.org/hso.html
This is a somewhat complex module, which requires a special utility called "ozerocdoff" to enumerate the modem, and this process is triggered by a udev event.
All of the necessary components are contained in the dotpet package; module, utlitity, and udev rule.
Hopefully this will work in Puppy 4.1.x

Connection is a little complex. The "Internet by wireless GPRS modem ..." option in the Connection wizard might work, but if not, there is a sample connection script at /usr/local/bin/hso_connect.sh
There is also a comprehensive README at /root/my-applications/hso-README.txt

UPDATE: Several USB wireless modems (such as the Globetrotter GT Max) have their MS Windows drivers onboard; when plugged in for the first time they act like a flash storage and start installing the driver from there. After that (and on every consecutive plugging) this driver switches the mode internally, the storage device vanishes (in most cases), and a new device (USB modem) shows up.
In Linux the solution is to use the "usb_modeswitch" utility to switch the device to its wireless modem mode, then the "option" module can be loaded. The whole process is automated by the configuration file; /etc/usb_modeswitch.conf
Open this file in Geany, and remove the ";" characters from the configuration values for your particular model of Globetrotter device.

UPDATE April 8 2009:
"usb-storage" driver patched so that the ZTE/Onda modem devices will be automatically detected, and when used in combination with the updated "option" driver and also rerwin's "3G_pupdial-wireless" dotpet -
http://www.murga-linux.com/puppy/viewtopic.php?t=37828
the modeswitching should happen automatically, and all drivers should load automatically.

Wireless modems - PCMCIA/Cardbus
The very first Cardbus devices such as the original Globetrotter appear as a serial interface, and are supported by the standard "serial_cs" module in Puppy.

The next generation Cardbus devices such as the Vodafone 3G appear as a USB interface, and are supported by the "usbserial" module, but will work better with the more modern "option" module.
http://www.pharscape.org/datacards-option.ko.html

The next generation of Cardbus devices requires the "nozomi" module, which is a standard kernel module but it was not enabled in Puppy's kernel configuration. So it's now available as a separate dotpet, attached.
Supported devices are listed here
http://www.pharscape.org/nozomi-datacards.html

And the latest Cardbus devices are supported by the "hso" module, dotpet available in the previous post.

Hi,
I have a problem with the microphone in EeePc 900 running Puppy 4.1.1 or Ripple.
If I use Skype and try to send a test call, I hear the automatic voice, but my own message they send back to me, I can't hear.
Microphone is on and loud, I can hear it if I blow to it or scratch.
What I don't have is mic boost in alsa mixer. So I tried to install eee-snd-hda-intel-patched-k2.6.25.16.pet from tempestuous but it fails: I can choose to install or abort, then comes the message 'packet manager processing... please wait' . A few seconds later this message disappears and that was all. I downloaded this pet two times and tried it several times so I don't think I made a mistake..

I have no more idea what's wrong or even where i should search for a solution.

Has anybody a idea, solution or at least a hint?
Thanks
Rolf

rhadon wrote:... but it fails: I can choose to install or abort, then comes the message 'packet manager processing... please wait' . A few seconds later this message disappears and that was all.

Dotpets will fail to install if they are located in a directory (or directory path) which contains a space in its name.
There is a fix discussed here -
http://www.murga-linux.com/puppy/viewto ... 919#256919

But a quick fix is obviously to locate the dotpet in a suitably named directory, or even the root path of a drive.

Hi tempestuous,
thank you for trying to help.

There was no space in the pathnames. I used /mnt/home/Downloads/.
To be shure, I copied the pet to root but the same problem.
So I opened a terminal and tried to start it there. First I got the message 'permission denied. I changed permissions and now I get the message 'cannot execute binary file'.

Rolf

Edit: I know that your Dotpets work fine. I use the madwifi.pet from you and it works very fine. I also installed a lot of other pets without any problem. So I'm perplex now and have no idea.

I just booted to the Puppy 4.1 CD, downloaded eee-snd-hda-intel-patched-k2.6.25.16.pet, and the installation worked fine.

@ tempestuous
OK, your pet works fine with Puppy 4.1.1. also on my Eee. The last attempts I did only with Ripple, a derivative of 4.1.1. With original Puppy it works fine and with mic boost the microphone is more sensitiv.
Therefore I'm really sorry for wasting your time in this part.

I still have the actually problem , no matter the pet is installed or not ( for now I use only Puppy):

If I use Skype and try to send a test call, I hear the automatic voice, but my own message they send back to me, I can't hear. Only the automatic voice like "...if you hear this voice, Skype is configured well, if you don't hear your own message, please check your settings for the microphone."

For 'sound in' I have 3 choices:
1. Default device (default)
2. HDA Intel (hw: Intel,0)
3. HDA Intel (plughw: Intel,0)

With #1 and #2 I have the problem above, with #3 I get only the message 'problem with audio capture' and no call.

In Alsa mixer every control is to max without mute.

Do you have any idea what is wrong or what I can check more?

Rolf

Edit: I just tried the same with a headset: if everything is on max it works basically. In the moment I speak, I hear my voice clear and very loud but the voice I get back is low and close.

Hi,
it works .

After installing acpid-Eee-7x-900.pet and eee-asus_acpi-pciehp-k2.6.25.16.pet also the internal microphone works with Skype.
So thank you again tempestuous and have a nice xmas time.
Rolf

Venger, I have not played with... defaulting to lower CPU speed after a given time (the latter sounds especially intriguing)

I have this in my /etc/rc.local which accomplishes what you want: I use Puppy 4.1.2.

Hello,

Just a comment to tempestuous about the logitech quickcam module.

Trying to get my quickcam working in Puppy 2.6.25.16.

Downloaded and ran that .pet file but when i type "modprobe quickcam" i get this error:

# modprobe quickcam
FATAL: Error inserting quickcam (/lib/modules/2.6.25.16/misc/quickcam.ko): Invalid module format

Any clue on that?

Thanks for help,

Best regards,
Johan

Well the quickcam module loads successfully for forum member kuapao.
Maybe your webcam device is not compatible? Please plug in your webcam and run this command - and report the "Vendor" and "ProdID" values for your webcam.

divisionmd wrote:# modprobe quickcam
FATAL: Error inserting quickcam (/lib/modules/2.6.25.16/misc/quickcam.ko): Invalid module format

That looks to me like you're trying to load a module that doesn't match the kernel you're using.

Help!

I have been searching the forums for days trying to find a solution to my problem which is:

WLAN card not detected on a Eee pc 701SD.

I have tried both, Puppy 4.1.2 Normal and Retro.

I have tried both MADwifi modified drivers

I have tried module preference loading in boot manager.

Nothing seems to work.

I have another Eee pc which is the 4G model and the madwifi patch works fine in Puppy 4.1.2 Retro.

On the 701SD there seems to be quite a few different components. The processor and SSD are both different and obviously the wlan card too. BTW how do you find out the type of LAN card installed.

I am tempted to try Pupeee or Eeetiger but they are based on Puppy 3.01 and I didn't really want to return to the past. I really like Dingo.

Thanks

Smokey

Well a quick Google search reveals that the 701SD has a Realtek RTL8187SE wifi chipset (same as the MSI Wind).
So the "rtl8187se-coffelius0.4-k2.6.25.16.pet" I provided earlier in this thread should do the job -
http://www.murga-linux.com/puppy/viewto ... 747#237747

If not, please run this command and report the output.

tempestuous,

Thanks for the quick reply but unfortunately no luck. I had actually tried this driver previously but forgot to mention it. I tried it again just to be sure.

Attached is the output from the lspci -n command.

Thanks

Grant

EDIT:
smokey's wifi vendor/device 10ec:8199 is definitely compatible with the r8180 driver in the rtl8187se-coffelius dotpet.

There is a bug in 4.12 (in fact all "dingo" based puppies I believe) for intel graphics chipsets 8xx and 9xx. It is caused by a missing video driver, i810_drv.so which is missing from the /usr/X11R7/lib/xorg/modules/drivers folder. It manifests by not displaying puppy in the correct screen resolution as specified by the user. This could be a problem as many laptops (and desktops) use onboard intel graphics and the screen resolution needs to be set correctly for LCD screens.

Instructions for how to fix the problem are here

http://www.murga-linux.com/puppy/viewtopic.php?t=37393

It consists of copying the i810_drv.so file from puppy 3 series to the correct location, and restarting the xorgserver. Thanks to ICPUG for finding the fix.

It would be great if someone with more skill than I would make a .pet to fix the problem, and post it here.