Pixmaps, floppy icon fixed, keyboard trouble

Zigbert reported that the FPM and Gwhere pixmaps are not 16x16 in the menu. Fixed.

Linuxcbon reported that some icons are missing from the 'Chat' and 'Edit' menus in Ayttm. Fixed.

Flapdoodle reported that the desktop floppy icon changed to a hd icon. Fixed.

Keyboard trouble
smokey01 has reported that the ps/2 keyboard does not work on his PC. The kernel has the ps/2 driver builtin and it should work. Your HardInfo reports this:
Class 0600	1106:3205

Class 0604 1106:b198
Class 0280 104c:9066
Class 0c03 1106:3038
Class 0c03 1106:3038
Class 0c03 1106:3038
Class 0c03 1106:3104
Class 0601 1106:3177
Class 0101 1106:0571
Class 0401 1106:3059
Class 0200 1106:3065
Class 0300 1106:7205


When you boot from live-CD, does the keyboard work at the boot prompt? That is controlled by Syslinux, not Puppy. If not, you are in trouble. If yes, try "puppy loglevel=7" and watch for any error messages.

Another thing to try: Run PupScan, find out what one of the vendor:chip IDs is mostly likely concerned with the keyboard (or just run 'scanpci' in a terminal), then google to try and find out if there are any known issues with this glue-chip and recent Linux kernels.

Posted on 20 Aug 2008, 10:14


Comments:

Posted on 21 Aug 2008, 16:45 by wombat01
Keyboard trouble
Keyboard does not work from the begining of the bootup via CD.

The first time one needs to use the keyboars is to select the keybourd layout and it does not work.

# scanpci

pci bus 0x0000 cardnum 0x00 function 0x00: vendor 0x1106 device 0x3205
VIA Technologies, Inc. VT8378 [KM400/A] Chipset Host Bridge

pci bus 0x0000 cardnum 0x01 function 0x00: vendor 0x1106 device 0xb198
VIA Technologies, Inc. VT8237 PCI Bridge

pci bus 0x0000 cardnum 0x09 function 0x00: vendor 0x104c device 0x9066
Texas Instruments ACX 111 54Mbps Wireless Interface

pci bus 0x0000 cardnum 0x10 function 0x00: vendor 0x1106 device 0x3038
VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller

pci bus 0x0000 cardnum 0x10 function 0x01: vendor 0x1106 device 0x3038
VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller

pci bus 0x0000 cardnum 0x10 function 0x02: vendor 0x1106 device 0x3038
VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller

pci bus 0x0000 cardnum 0x10 function 0x03: vendor 0x1106 device 0x3104
VIA Technologies, Inc. USB 2.0

pci bus 0x0000 cardnum 0x11 function 0x00: vendor 0x1106 device 0x3177
VIA Technologies, Inc. VT8235 ISA Bridge

pci bus 0x0000 cardnum 0x11 function 0x01: vendor 0x1106 device 0x0571
VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE

pci bus 0x0000 cardnum 0x11 function 0x05: vendor 0x1106 device 0x3059
VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller

pci bus 0x0000 cardnum 0x12 function 0x00: vendor 0x1106 device 0x3065
VIA Technologies, Inc. VT6102 [Rhine-II]

pci bus 0x0001 cardnum 0x00 function 0x00: vendor 0x1106 device 0x7205
VIA Technologies, Inc. VT8378 [S3 UniChrome] Integrated Video
#



Posted on 21 Aug 2008, 17:13 by BarryK
Keyboard
"Keyboard does not work from the begining of the bootup via CD."

Do you mean it does not work right from the boot prompt? I mean that 5 second interval when you can type in kernel boot parameters.


Posted on 22 Aug 2008, 6:22 by wombat01
puppy
Sorry for the confusion.

Initially it does allow you to type puppy pfix=ram.

The next time typing is required is at the selection of the keyboard. All I need to do is press enter as the US keyboard is what I need to select. At this point no key strokes can be entered. Actually that is not entirely true, CTL ALT & DEL works. The computer starts to shut down but then you can't select to save the pup_save file or not.

Quite unusual as every other version has worked without any keyboard problems. I am using 4.00 now and it's fine. 4.1Alpha5 works too.

Regards

smokey01 (aka wombat01)


Posted on 5 Aug 2009, 24:27 by Admiraln
Puppy 4.2.1 install keyboard prolem
Puppy 4.2.1 (and 4.1) has the exact same problem with a compaq evo with a 2002 dated compaq bios.
Windows Xp is installed and the key board
works but is infected with the deleted wuspdater.exe problem which is why I am trying to boot with puppy.