Did a full install on a SATA internal hard drive and my Logitech Trackman Wheel is not recognized. .... My 'puter has a generic PS/2 mouse in the mouse port and also a Logictech Track Ball. I redid the Wary installation and watched more closely. 1) Boot with fresh Wary CD - both mice work 2) Full i...

Did a full install on a SATA internal hard drive and my Logitech Trackman Wheel is not recognized. .... [/code] My 'puter has a generic PS/2 mouse in the mouse port and also a Logictech Track Ball. I redid the Wary installation and watched more closely. 1) Boot with fresh Wary CD - both mice work 2...

The busybox version of "findfs" has been broken in both Quirky and Wary: # /sbin/findfs LABEL=boot tune2fs 1.41.9 (22-Aug-2009) Usage: /sbin/findfs [-c max_mounts_count] [-e errors_behavior] [-g group] [-i interval[d|m|w]] [-j] [-J journal_options] [-l] [-m reserved_blocks_percent] [-o [^]...

Did a full install on a SATA internal hard drive and my Logitech Trackman Wheel is not recognized. I keep a generic USB PS/2 mouse plugged in for events like this. Other USB devices are a UPS and a flash stick. I don't see any glaring errors in here: # dmesg | grep -i usb usbcore: registered new int...

I have used the "findfs" utility for several years in various backup scripts that I run from Puppy. /sbin/findfs is actually a symbolic link to "/sbin/tune2fs" which still works in Quirky but not in LuPu 5.0.0 nor 5.0.1. If I copy the "tune2fs" from Quirky into LuPu, th...

For several generations of Puppies I have used the "findfs" utility in backup scripts. Here is an example issued from a command line: # findfs LABEL=gentoo /dev/sda5 # This works in Quirky and Puppies before 5.0.0. However, in Puppy 5.0.0, you get a "tune2fs" usage message like t...

I use the findfs utility in several backup scripts. Here is what I have observed so far: # findfs LABEL=gentoo tune2fs 1.41.11 (14-Mar-2010) Usage: findfs [-c max_mounts_count] [-e errors_behavior] [-g group] [-i interval[d|m|w]] [-j] [-J journal_options] [-l] [-m reserved_blocks_percent] [-o [^]mou...

My Dell laptop needs a "real" i810 xorg driver to display its native 1024x768 like was in Puppy 3.1. lrwxrwxrwx 1 root root 12 2008-07-17 15:46 i810_drv.so -> intel_drv.so -rwxr-xr-x 1 root root 307156 2007-11-28 20:42 intel_drv.so The current i810_drv.so is a symlink to the intel driver w...

As I posted in the Alpha 1 forum, my Dell laptop with its Intel video chip needs the "i810" driver for xorg to work and display 1024x768. In Puppy 4+, this driver is "unreal" because it is just a symbolic link to the "intel" driver. On a hunch, I made my laptop work pro...

I assumed that the greatly reduced number of Xorg drivers and the single symlink for i810 was something you had done to reduce the size of Puppy 4. Wrong assumption?

My Dell laptop with an Intel 82845 video chip has worked fine with recent Puppy versions using the i810 driver selected by the wizard. The only video that works on this machine with Puppy 4.0 is xvesa and then only at 640x480x16 which is basically unusable. The Xorg video wizard selects the intel dr...

My Dell laptop with an Intel 82845 video chip has worked fine with recent Puppy versions using the i810 driver selected by the wizard. The only video that works on this machine with Puppy 4.0 is xvesa and then only at 640x480x16 which is horrible. The Xorg video wizard selects the intel driver which...

I just got Puppy 2.11 to boot from my SATA HD with this one-line addition to /etc/rc.d/rc.sysinit: #v2.11 redirect all output to a log file... mount -o remount / #16Oct2006pop-pop exec 1>/tmp/bootsysinit.log 2>&1 Barry, looks like this code to make the drives rw needs to be executed a little ear...

Can you also look in /tmp/bootsysinit.log and /initrd/tmp/bootinit.log.

Looking at my 2.11 HD partition using Puppy 2.10, /tmp is completely empty. The permissions are OK (same as 2.10):

ditto symptom on my desktop with SATA drive from my scribbly notes: touch: cannot touch "/tmp/bootcnt.txt": Read-only file system -sh /tmpbootkernel.log: Read-only file system This script will run X windows for you... /usr/X11R7/bin/xwin: line 61 /tmp/videomode: Read-only file system /usr/...

After a few tries, I finally got Puppy 2.10 to boot from USB flash.

Last try used fdisk, mkdosfs (no volume label), and the new initrd.gz.

This no-name flash stick was a replacement for one that failed and this is my first time using it.

Hmmm.. My post started this thread and other users seem to be able to boot from USB with the fixed initrd.gz file. My Dell laptop still won't boot from a USB flash stick. With the new initrd, here are the last several console lines: USB Mass Storage support registered 1 2 3 4 Vendor: USB2.0 Model: F...

On my Dell laptop (Inspiron 1100) previous Puppy versions have booted fine from a USB flash memory stick. Both beta and final Puppy 2.10 start the kernel fine, print a couple of pages of messages, but stall at the final message below and here a few of the messages: ERROR, cannot find Puppy on usbfla...

I was going to test booting from an SATA hard drive with Jesse's "init" but I need some help. I have a spare empty SATA HD that will be a RAID drive one of these days and I was going to use that for boot testing. My plan was to first get the "init" working with my Puppy 2.02 inst...

What did you pack the init.gz file with?

Oops! brainphart on my part

It was packed with gzip.