Those are supposed to produce either keyboard or acpi events. If neither happens, I have no idea how to fix it. I tried to capture the acpi events in the terminal again, saw nothing, but went to the log file, and here is what I found: Sep 26 16:17:23 (none) daemon.notice acpid: exiting Sep 26 16:17 ...

Got this from Hardinfo: Device Info: Name Sleep Button Type Keyboard Bus 0x19 Vendor 0 Product 0x3 Version 0x0 Connected to PNP0C0E/button/input0 Name Lid Switch Type Unknown Bus 0x19 Vendor 0 Product 0x5 Version 0x0 Connected to PNP0C0D/button/input0 Does that help any for those two items. Jon Hmm ...

Ok, did that. Got nothing from any of the keys in the terminal window, including the ones that work. I do know in Windows, Averatec has a driver for something special, but they don't say what it is for. I think you figured out what! I doubt it would help you much, but I can get you a copy if you'd ...

Jonlowe, open up Xbindkeys (on the Desktop menu), and try to capture the keycodes for the keys that don't work. Then send them to me and I'll fix it in the next version. Ok, Xbindkeys got Volume up and down to work. I didn't know that app was there, thanks! However, hitting the Sleep key (Fn+F1 ...

That worked. The following function keys work ok both in puppeee and fluppy: Brightness Wireless on and off Following don't work in either: Sleep Volume up and down Mute Closing the lid also doesn't put it to sleep. Hardinfo sees them, but they don't do anything. Have I missed something in setup ...

I recently installed puppeee 1.0 on my Averatec N1231, which works amazingly well, although certain function keys don't work. I'm running off a USB stick. I didn't realize at the time that Fluppy existed. I've installed some other apps and librarys from .debs, that I don't really want to go thru the ...

This is on an HP Omnibook 600ct with a SCSI CD drive attached to a docking station. It can boot only from a floppy or the HD. No USB ports, and I can't add them since no one ever made a 16bit PCMCIA card with USB ports! Anyway, with wakepup2, it loads aspi2dos.sys ok, finds the CD and loads vmlinuz ...

My Vaio PCG-R505 can do the first part of the boot process from the firewire CD in the docking station, but initrd does not load the firewire drivers so it will continue the boot with the pup_410.sfs files from the cd. Right now, I initiate the boot with the CD, then have the rest of Puppy on a USB ...

Hmmm, I'm at 80mb! I will try your suggestion. Thanks.

Jon

I guess I wasn't too clear. Puppy 4.1 retro frugal works fine on my Omnibook, it's just slow. I wanted to go to a full install. I find it interesting that it apparently sees the CD drive, but doesn't never boots from it. The drive, etc work fine under frugal,again, just very slow.

Thanks.
Jon

Tried Wakepup2 again. Got a lot further. By loading the Panasonic drivers, it loads the USB2 PCMCIA card, and sees my CD drive. It also finds the Puppy files, and asks me how I want to boot. No matter what option I choose, it gives me the "Kernel command line:" parameters for that particular option ...

I've got a special case here. Omnibook 800CT with cardbus slots and a USB_2 PCMCIA card. This card works well on this computer with a frugal Puppy install (4.1 retro) on the harddrive. However, I want to be able to use my USB CD drive (which also works with Puppy) to do a full install to this ...

Default font in Puppy is too large for 800x600 monitors. Certain pages won't display fully. Good example is Pupscan. Without reducing the global font size to 72 dpi, the Pupscan page won't fully show on the screen, leaving off the bottom part, and there is no way to resize the screen so it will ...

Asus WL_100G PCMCIA wireless card. This card works GREAT with an old HP Omnibook 800ct, with a fast Pentium 166 MMX processor and 80mb of ram! I'm using it now. Does WAP, WEP, etc. Puppy 4.1 regular and retro picked it up in the wizard instantly. Uses the "b43" driver. A lot of other cards put too ...

Based on information I've found on this site and elsewhere, I'm trying to optimize my hard disk access speed. By playing with hdparm in the console, I've found parameters that speed up access. However, I can't find anything on current flavors of Puppy on how to make them permanent so that Puppy ...

Another note; 4.1 standard will NOT work on my Omnibook. 4.1 Retro works fine. Standard hangs at the loading kernel modules screen.

On to wireless cards...

Jon

I also found another way to install puppy without using a grub file. In the universal installer, choose USB harddrive. Follow the default choices for installation. At the MBR screen, I chose the mbr.bin option. Not sure it is necessary, but it worked. When it is done, and while the drive is still ...

OK, solved that problem. I redid the harddrive AGAIN, but this time took the default option of how the do the puppy save file, instead of the option to use the whole partition. That worked. Not sure why, but it did. now I can reboot and things proceed normally. Still using retro. Will try 4.1 ...

I am doing virtually the same thing on my Omnibook 600ct and was getting identical results and error messages. YOur thread looks like you were copying my screens today! You can see my thread at www.murga-linux.com/puppy/viewtopic.php?t=34526 As you can see from my thread, I made a lot of progress ...

OK, here is what I tried today. I made another partition on my main computer, and did a clean frugal install of 4.1 retro to that partition; did not boot from it. Copied that over to my harddrive for my Omnibook, which had a clean partition for Linux plus a separate Linux swap file partition. Did an ...