The time now is Thu 19 Apr 2018, 18:00
All times are UTC - 4 |
Page 6 of 17 [255 Posts] |
Goto page: Previous 1, 2, 3, 4, 5, 6, 7, 8, ..., 15, 16, 17 Next |
Author |
Message |
venger
Joined: 17 Sep 2008 Posts: 13
|
Posted: Sun 30 Nov 2008, 19:28 Post subject:
|
|
@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,
|
Back to top
|
|
 |
Dougal

Joined: 19 Oct 2005 Posts: 2504 Location: Hell more grotesque than any medieval woodcut
|
Posted: Mon 01 Dec 2008, 06:12 Post subject:
|
|
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...
_________________ What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind
|
Back to top
|
|
 |
tempestuous
Joined: 10 Jun 2005 Posts: 5468 Location: Australia
|
Posted: Mon 01 Dec 2008, 07:01 Post subject:
|
|
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/arch/acpi-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
|
Back to top
|
|
 |
tempestuous
Joined: 10 Jun 2005 Posts: 5468 Location: Australia
|
Posted: Wed 03 Dec 2008, 07:08 Post subject:
|
|
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.
 |
Description |
for Puppy 4.1.x
|

Download |
Filename |
usb-storage-ZTE-patch-k2.6.25.16.pet |
Filesize |
43.08 KB |
Downloaded |
1890 Time(s) |
Description |
for Puppy 4.1.x
|

Download |
Filename |
option-patched-01April09-k2.6.25.16.pet |
Filesize |
7.21 KB |
Downloaded |
1730 Time(s) |
Description |
|

Download |
Filename |
usb_modeswitch-0.9.5.pet |
Filesize |
10.83 KB |
Downloaded |
1786 Time(s) |
Description |
for Puppy 4.1.x
|

Download |
Filename |
hso-1.6-k2.6.25.16.pet |
Filesize |
31.81 KB |
Downloaded |
1561 Time(s) |
Last edited by tempestuous on Wed 08 Apr 2009, 01:45; edited 4 times in total
|
Back to top
|
|
 |
tempestuous
Joined: 10 Jun 2005 Posts: 5468 Location: Australia
|
Posted: Wed 03 Dec 2008, 07:11 Post subject:
|
|
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.
Description |
for Puppy 4.1.x
|

Download |
Filename |
nozomi-k2.6.25.16.pet |
Filesize |
12.49 KB |
Downloaded |
1090 Time(s) |
|
Back to top
|
|
 |
rhadon

Joined: 27 Mar 2008 Posts: 1293 Location: Germany
|
Posted: Sat 13 Dec 2008, 04:58 Post subject:
|
|
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
_________________ Ich verwende "frugal", und das ist gut so.
Raspberry Pi without Puppy? No, thanks.
|
Back to top
|
|
 |
tempestuous
Joined: 10 Jun 2005 Posts: 5468 Location: Australia
|
Posted: Sat 13 Dec 2008, 06:13 Post subject:
|
|
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/viewtopic.php?p=256919#256919
But a quick fix is obviously to locate the dotpet in a suitably named directory, or even the root path of a drive.
|
Back to top
|
|
 |
rhadon

Joined: 27 Mar 2008 Posts: 1293 Location: Germany
|
Posted: Sat 13 Dec 2008, 08:11 Post subject:
|
|
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.
|
Back to top
|
|
 |
tempestuous
Joined: 10 Jun 2005 Posts: 5468 Location: Australia
|
Posted: Sat 13 Dec 2008, 10:36 Post subject:
|
|
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.
Description |
|
Filesize |
22.07 KB |
Viewed |
10039 Time(s) |

|
|
Back to top
|
|
 |
rhadon

Joined: 27 Mar 2008 Posts: 1293 Location: Germany
|
Posted: Sat 13 Dec 2008, 14:59 Post subject:
|
|
@ 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.
_________________ Ich verwende "frugal", und das ist gut so.
Raspberry Pi without Puppy? No, thanks.
|
Back to top
|
|
 |
rhadon

Joined: 27 Mar 2008 Posts: 1293 Location: Germany
|
Posted: Thu 18 Dec 2008, 14:26 Post subject:
|
|
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
_________________ Ich verwende "frugal", und das ist gut so.
Raspberry Pi without Puppy? No, thanks.
|
Back to top
|
|
 |
PaulBx1
Joined: 16 Jun 2006 Posts: 2307 Location: Wyoming, USA
|
Posted: Tue 23 Dec 2008, 21:50 Post subject:
|
|
Quote: | 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:
Code: | # Use "ondemand" cpu frequency scaling to reduce power consumption as described in:
# http://www.murga-linux.com/puppy/viewtopic.php?t=28443
modprobe acpi-cpufreq
echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor |
I use Puppy 4.1.2.
|
Back to top
|
|
 |
divisionmd

Joined: 14 Jul 2007 Posts: 608
|
Posted: Tue 06 Jan 2009, 05:40 Post subject:
|
|
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
|
Back to top
|
|
 |
tempestuous
Joined: 10 Jun 2005 Posts: 5468 Location: Australia
|
Posted: Tue 06 Jan 2009, 07:16 Post subject:
|
|
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 -
Code: | cat /proc/bus/usb/devices |
and report the "Vendor" and "ProdID" values for your webcam.
|
Back to top
|
|
 |
Dougal

Joined: 19 Oct 2005 Posts: 2504 Location: Hell more grotesque than any medieval woodcut
|
Posted: Tue 06 Jan 2009, 07:31 Post subject:
|
|
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.
_________________ What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind
|
Back to top
|
|
 |
|
Page 6 of 17 [255 Posts] |
Goto page: Previous 1, 2, 3, 4, 5, 6, 7, 8, ..., 15, 16, 17 Next |
|
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
|