slaxer_pup "cooking version" released 5-19-2010
cooking version not working right on IBM thinkpad 600x
Hi Joe, long story short, I wanted to watch a dvd video on my laptop and neither gxine or vlc worked on Fedora 11 lxde spin, nor on the new lupo (puppy v501) so I tried your original slaxer pup and it worked!
So I visted these forums and saw you had this cooking version which I downloaded and that works too as far as playing a video -- (and my broadcom 4318 wireless too!) but I did a frugal install to it's own (puppy412) folder and it didn't save any of my settings and I noticed the HDD light stayed on, even when the HDD wasn't being accessed. So there's something not 'quite right' about the newest version on my laptop. Here are some specs:
IBM Thinkpad 600x with 256mb ram Pentium PIII at 500mhz
Audio adapter is a Cirrus Logic Sound Fusion CS46xx (I ran hardinfo)
IDE disks
IC25N010ATCS04-0 (that must be the hard drive)
MATSHITADVD-ROM SR-8171 (Obviously the dvd drive)
Thankfully I wrote the iso for the 'cooking' slaxer on an RW cd. If you need anything else, let me know.
So I visted these forums and saw you had this cooking version which I downloaded and that works too as far as playing a video -- (and my broadcom 4318 wireless too!) but I did a frugal install to it's own (puppy412) folder and it didn't save any of my settings and I noticed the HDD light stayed on, even when the HDD wasn't being accessed. So there's something not 'quite right' about the newest version on my laptop. Here are some specs:
IBM Thinkpad 600x with 256mb ram Pentium PIII at 500mhz
Audio adapter is a Cirrus Logic Sound Fusion CS46xx (I ran hardinfo)
IDE disks
IC25N010ATCS04-0 (that must be the hard drive)
MATSHITADVD-ROM SR-8171 (Obviously the dvd drive)
Thankfully I wrote the iso for the 'cooking' slaxer on an RW cd. If you need anything else, let me know.
Hey CiaW
A great report
if you want a very nice media player select mplayer from the first page of this thread
that plays many formats
*about the hard drive light nothing I changed could have effected that
make sure you dont have any older pupsaves or 412 sfs getting loaded
maybe it is using swap ?
thanks for posting if you need anything else let me know
Joe
A great report
if you want a very nice media player select mplayer from the first page of this thread
that plays many formats
*about the hard drive light nothing I changed could have effected that
make sure you dont have any older pupsaves or 412 sfs getting loaded
maybe it is using swap ?
thanks for posting if you need anything else let me know
Joe
lilo boot puppy
this is for anyone who boots from lilo instead of grub
and installs slaxer_pup
easy to modify for your different drives
since I have slackware 12.2 installed it uses lilo
to boot the system
if you want to install puppy on the same hardrive as your other lilo bootloader 2 distro in my case slackware was installed first
1.)install puppy using the installer the official way
frugal dont install grub
2.)edit /etc/lilo.conf {this gets added to lilo.conf its not complete}
then save it
boot into your lilo based distro
then in a console
now reboot and you have options to boot slaxer
slaxer which is frugal and uses your saved file
Ram-Slaxer like when you boot the first time from the live cd
fsck Slaxer does the file system check then boots your system with the saved file
P.S I saw that pizzasgood did this along time ago
but you dont need to move any files into the boot folder this way
and I wanted it pre setup for slaxer_pup for the slackware users
that join in to help
Joe
and installs slaxer_pup
easy to modify for your different drives
since I have slackware 12.2 installed it uses lilo
to boot the system
if you want to install puppy on the same hardrive as your other lilo bootloader 2 distro in my case slackware was installed first
1.)install puppy using the installer the official way
frugal dont install grub
2.)edit /etc/lilo.conf {this gets added to lilo.conf its not complete}
Code: Select all
other = /dev/hda1
label = Windows
table = /dev/hda
# Windows bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda2
label = Linux
read-only
###################################
# lilo boot for slaxer_pup
# frugal with save file
image =/puppy412/vmlinuz
root = /dev/hda2
initrd =/puppy412/initrd.gz
label = Slaxer
read-only
###################################
# Ram-Slaxer
image = /puppy412/vmlinuz
root = /dev/ram0
label = Ram-Slaxer
append = "pfix=ram"
initrd = /puppy412/initrd.gz
read-only
##################################
# fsck Slaxer
image = /puppy412/vmlinuz
root = /dev/ram0
label = fsck-Slaxer
append = "pfix=fsck"
initrd = /puppy412/initrd.gz
read-only
# Linux bootable partition config ends
boot into your lilo based distro
then in a console
Code: Select all
lilo
slaxer which is frugal and uses your saved file
Ram-Slaxer like when you boot the first time from the live cd
fsck Slaxer does the file system check then boots your system with the saved file
P.S I saw that pizzasgood did this along time ago
but you dont need to move any files into the boot folder this way
and I wanted it pre setup for slaxer_pup for the slackware users
that join in to help
Joe
=========================================
upgrade browser firefox 3.64
firefox-3.6.4-i486-3_SLXR
---> download_now
dbus-glib *needed for firefox
dbus-glib-0.80-i486-4_SLXR
---> download_now
June 27 2010 flashplayer
flashplayer-10-06272010-i486-3_SLXR.txz
flashplayer-10-06272010-i486-3_SLXR
---> download_now
========================================
tony
maybe the package nvidia 96.43.07 has to be re compiled
because HID is compiled in the kernel not a "module"
so thats a false error message
#
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
#
thers a copy of the kernel config here
/proc/config.gz
maybe the package nvidia 96.43.07 has to be re compiled
because HID is compiled in the kernel not a "module"
so thats a false error message
#
Code: Select all
cat /tmp/bootkernel.log | grep hid
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
#
thers a copy of the kernel config here
/proc/config.gz
keyboard trouble
I installed this in a Thinkpad 600 with 420mb ram and 300mhz cpu.
It is wonderful but the keys are typing as though numlock is on ie J=1 K=2 L=3 etc. and I can't turn it off. Any ideas?
I only have a shallow understanding of Linux, OK up to a point, then clueless.
It is wonderful but the keys are typing as though numlock is on ie J=1 K=2 L=3 etc. and I can't turn it off. Any ideas?
I only have a shallow understanding of Linux, OK up to a point, then clueless.
Re: keyboard trouble
very easy wayduckrow wrote:I installed this in a Thinkpad 600 with 420mb ram and 300mhz cpu.
It is wonderful but the keys are typing as though numlock is on ie J=1 K=2 L=3 etc. and I can't turn it off. Any ideas?
I only have a shallow understanding of Linux, OK up to a point, then clueless.
delete this file if you dont know anything about linux
/root/Startup/numberlock_on
another way if you know a bit how to edit files
if you know a little bit about linux you could comment out these lines
Code: Select all
#!/bin/sh
#add to /root/Startup for slaxer_pup big_bass
# Turn NumLock on (using numlockx)
#if [ -x /usr/bin/numlockx ]; then
#/usr/bin/numlockx
#fi
thanks for trying and posting
Joe
Hey Tony
lets do it the manual hard way first
/usr/bin/Xdialog
linux-gate.so.1 => (0xffffe000)
libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0xb7bcb000)
libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0xb7b49000)
libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0xb7b32000)
libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0xb7b1b000)
libpangocairo-1.0.so.0 => /usr/lib/libpangocairo-1.0.so.0 (0xb7b13000)
libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0xb7ae3000)
libcairo.so.2 => /usr/lib/libcairo.so.2 (0xb7a86000)
libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0xb7a66000)
libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0xb7a63000)
libdl.so.2 => /lib/libdl.so.2 (0xb7a5f000)
libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0xb79d2000)
libc.so.6 => /lib/libc.so.6 (0xb78d6000)
libX11.so.6 => /usr/X11R7/lib/libX11.so.6 (0xb7805000)
libXfixes.so.3 => /usr/X11R7/lib/libXfixes.so.3 (0xb7801000)
libm.so.6 => /lib/libm.so.6 (0xb77df000)
libXi.so.6 => /usr/X11R7/lib/libXi.so.6 (0xb77d7000)
libfontconfig.so.1 => /usr/X11R7/lib/libfontconfig.so.1 (0xb77b0000)
libXext.so.6 => /usr/X11R7/lib/libXext.so.6 (0xb77a4000)
libXrender.so.1 => /usr/X11R7/lib/libXrender.so.1 (0xb779d000)
libXinerama.so.1 => /usr/X11R7/lib/libXinerama.so.1 (0xb779a000)
libXrandr.so.2 => /usr/X11R7/lib/libXrandr.so.2 (0xb7794000)
libXcursor.so.1 => /usr/X11R7/lib/libXcursor.so.1 (0xb778c000)
libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0xb7766000)
libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0xb7708000)
libz.so.1 => /lib/libz.so.1 (0xb76f9000)
libpng12.so.0 => /usr/lib/libpng12.so.0 (0xb76dc000)
libpixman-1.so.0 => /usr/lib/libpixman-1.so.0 (0xb76ab000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb75df000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0xb75d5000)
/lib/ld-linux.so.2 (0xb7f32000)
libXau.so.6 => /usr/X11R7/lib/libXau.so.6 (0xb75d2000)
libXdmcp.so.6 => /usr/X11R7/lib/libXdmcp.so.6 (0xb75cd000)
libexpat.so.1 => /usr/lib/libexpat.so.1 (0xb75b1000)
#
now lets do it the easy way
click on this
*I wrote a complete GUI package management system
from scratch its called slaxer_pkgtools2.2
select dependency
select Xdialog as an example only
enjoy the easy way
*only works for packages installed as slackware type packages
thanks for reporting back and glad you tried again with
the new package
I hope this little how to helps clear up the dependency questions
Joe
lets do it the manual hard way first
Code: Select all
which Xdialog
/usr/bin/Xdialog
Code: Select all
ldd /usr/bin/Xdialog
libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0xb7bcb000)
libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0xb7b49000)
libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0xb7b32000)
libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0xb7b1b000)
libpangocairo-1.0.so.0 => /usr/lib/libpangocairo-1.0.so.0 (0xb7b13000)
libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0xb7ae3000)
libcairo.so.2 => /usr/lib/libcairo.so.2 (0xb7a86000)
libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0xb7a66000)
libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0xb7a63000)
libdl.so.2 => /lib/libdl.so.2 (0xb7a5f000)
libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0xb79d2000)
libc.so.6 => /lib/libc.so.6 (0xb78d6000)
libX11.so.6 => /usr/X11R7/lib/libX11.so.6 (0xb7805000)
libXfixes.so.3 => /usr/X11R7/lib/libXfixes.so.3 (0xb7801000)
libm.so.6 => /lib/libm.so.6 (0xb77df000)
libXi.so.6 => /usr/X11R7/lib/libXi.so.6 (0xb77d7000)
libfontconfig.so.1 => /usr/X11R7/lib/libfontconfig.so.1 (0xb77b0000)
libXext.so.6 => /usr/X11R7/lib/libXext.so.6 (0xb77a4000)
libXrender.so.1 => /usr/X11R7/lib/libXrender.so.1 (0xb779d000)
libXinerama.so.1 => /usr/X11R7/lib/libXinerama.so.1 (0xb779a000)
libXrandr.so.2 => /usr/X11R7/lib/libXrandr.so.2 (0xb7794000)
libXcursor.so.1 => /usr/X11R7/lib/libXcursor.so.1 (0xb778c000)
libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0xb7766000)
libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0xb7708000)
libz.so.1 => /lib/libz.so.1 (0xb76f9000)
libpng12.so.0 => /usr/lib/libpng12.so.0 (0xb76dc000)
libpixman-1.so.0 => /usr/lib/libpixman-1.so.0 (0xb76ab000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb75df000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0xb75d5000)
/lib/ld-linux.so.2 (0xb7f32000)
libXau.so.6 => /usr/X11R7/lib/libXau.so.6 (0xb75d2000)
libXdmcp.so.6 => /usr/X11R7/lib/libXdmcp.so.6 (0xb75cd000)
libexpat.so.1 => /usr/lib/libexpat.so.1 (0xb75b1000)
#
now lets do it the easy way
click on this
Code: Select all
/root/slaxer_pkg_tools2.2
from scratch its called slaxer_pkgtools2.2
select dependency
select Xdialog as an example only
enjoy the easy way
*only works for packages installed as slackware type packages
thanks for reporting back and glad you tried again with
the new package
I hope this little how to helps clear up the dependency questions
Joe
- Attachments
-
- menu-packagetools .png
- (25.7 KiB) Downloaded 1538 times
-
- dependency-viewer.png
- (43.13 KiB) Downloaded 1548 times
-
- Xdialog-depends.png
- (30.54 KiB) Downloaded 1547 times
hey big_bass
Nice job on slaxer pup! I gave it a spin on my eeepc 900 and was very impressed. There are a few slight problems though.
When I shut down, I never get a chance to make a pupsave. I just get the message "session not saved" and it shuts off. I checked and it is running in pupmode 5, so maybe there is an issue in the shutdown script.
About every 5 to 6 seconds the mouse cursor freezes for a split second. Also noticed the same thing when scrolling a document or entering text. Not sure if there is some kind of background process causing the problem or a driver issue.
Other than that good deal!
Nice job on slaxer pup! I gave it a spin on my eeepc 900 and was very impressed. There are a few slight problems though.
When I shut down, I never get a chance to make a pupsave. I just get the message "session not saved" and it shuts off. I checked and it is running in pupmode 5, so maybe there is an issue in the shutdown script.
About every 5 to 6 seconds the mouse cursor freezes for a split second. Also noticed the same thing when scrolling a document or entering text. Not sure if there is some kind of background process causing the problem or a driver issue.
Other than that good deal!
Hej Joe,
Nice update you got here on your solid and dependable Slaxer_Pup-4.12
Good idea putting a date on the versions. Makes it easier to keep track of them.
I've put away my ARM-based hardware for a while to concentrate on a couple of surplus HP t5525 Thin Clients I picked up. These have VIA Eden 800 MHz CPUs, 128 MB RAM and 256 MB Flash memory, perfect for running SlaxerPup in other words
What I have in mind is to make a special *server* version of SlaxerPup to run on hardware like this. I was inspired by bchafy's Xin server puplet (http://www.murga-linux.com/puppy/viewtopic.php?t=55154) which I have been running on the HP t5525.
What I have decided so far is to have the 'SlxrPupServer' puplet work as a printer server and a simple NAS (Network-Attached Storage: the HP t5525 has 4 USB 2.0 ports) for storing and sharing files on a USB HD or Flash drive. I may also try to add some streaming server app and a torrent client (need to figure out how first )
I've already got the printer server part working. I downloaded the p910nd printer daemon source, installed amigo's src2pkg and it compiled easily. Works great with my *2* USB printers, an Epson inkjet and a Brother laser, attached at the same time. Just need to configure CUPS for each printer (using the JetDirect/socket raw printing protocol) on the client PCs and you're ready to print through the HP server
Thanks for sticking with SlaxerPup
Paul
PS Almost forgot to thank you for compiling the audio and wifi drivers for the eBox-2300. I'll test them soon and report back.
Nice update you got here on your solid and dependable Slaxer_Pup-4.12
Good idea putting a date on the versions. Makes it easier to keep track of them.
I've put away my ARM-based hardware for a while to concentrate on a couple of surplus HP t5525 Thin Clients I picked up. These have VIA Eden 800 MHz CPUs, 128 MB RAM and 256 MB Flash memory, perfect for running SlaxerPup in other words
What I have in mind is to make a special *server* version of SlaxerPup to run on hardware like this. I was inspired by bchafy's Xin server puplet (http://www.murga-linux.com/puppy/viewtopic.php?t=55154) which I have been running on the HP t5525.
What I have decided so far is to have the 'SlxrPupServer' puplet work as a printer server and a simple NAS (Network-Attached Storage: the HP t5525 has 4 USB 2.0 ports) for storing and sharing files on a USB HD or Flash drive. I may also try to add some streaming server app and a torrent client (need to figure out how first )
I've already got the printer server part working. I downloaded the p910nd printer daemon source, installed amigo's src2pkg and it compiled easily. Works great with my *2* USB printers, an Epson inkjet and a Brother laser, attached at the same time. Just need to configure CUPS for each printer (using the JetDirect/socket raw printing protocol) on the client PCs and you're ready to print through the HP server
Thanks for sticking with SlaxerPup
Paul
PS Almost forgot to thank you for compiling the audio and wifi drivers for the eBox-2300. I'll test them soon and report back.
Methinks Raspberry Pi were ideal for runnin' Puppy Linux
BTW, here are a couple of apps I compiled using src2pkg to add to your collection.
Note that the forum doesn't allow the .tgz suffix - just remove the .ace ending after downloading.
Afterwards, just click on the file to install in SlaxerPup-cooking
Note that the forum doesn't allow the .tgz suffix - just remove the .ace ending after downloading.
Afterwards, just click on the file to install in SlaxerPup-cooking
- Attachments
-
- p910nd-0.93-i486-1.tgz.ace
- p910nd: a small daemon that can turn an old PC into a printer server
- (18.28 KiB) Downloaded 498 times
Methinks Raspberry Pi were ideal for runnin' Puppy Linux
A brief howto for the p910nd printer server daemon
Short description from the p910nd man page
p910nd is a small printer daemon intended for diskless workstations that does not spool to disk but passes the job directly to the printer. Normally a lpr daemon on a spooling host connects to it with a TCP connection on port 910n (where n=0, 1, or 2 for lp0, 1 and 2 respectively). p910nd is particularly useful for diskless Linux workstations such as those set up with LTSP and embedded devices that have a printer hanging off them. Common Unix Printing System (CUPS) supports this protocol, it's called the AppSocket protocol and has the scheme socket://. LPRng also supports this protocol and the syntax is lp=remotehost%9100 in /etc/printcap.
Installing the daemon
Download p910nd-0.93-i486-1.tgz and install in SlaxerPup by clicking on the file name.
You can test it by simply executing p910nd in a terminal
# p910nd &
If you want the daemon to start at every bootup, just include the above line (without the #) in /etc/rc.d/rc.local.
Using the daemon
On your client PC, configure the printer in CUPS. When CUPS asks which URI to use, choose 'socket://' and add the IP address of the 'server', i.e. the PC running the printer daemon (choosing a static IP address for the printer server makes things easier ) followed by a colon and the port number).
Example URI: socket://192.168.0.15:9100
That's it!
Advanced - using two printers on the same server
Two printers on the same server is a little more complicated, but I did get it to work. Here's where the 'lsusb' utility came in handy. Two instances of the daemon need to run and the server must somehow determine which daemon controls which physical USB port.
Here's how I did it
1. Connect both printers to USB ports on the server.
2. Start up two printer daemons (in a terminal or in rc.local). The daemons will change name to reflect which port they use.
# p910nd -f /dev/usb/lp0 0 &
# p910nd -f /dev/usb/lp1 1 &
3. Run lsusb in a terminal and check the output. For example:
# lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 04f9:0027 Brother Industries, Ltd HL-2030 Laser Printer
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 04b8:0005 Seiko Epson Corp. Stylus D88+
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
#
Note that here the Epson printer is on Bus 001 and the Brother printer on Bus 002.
4. On your client PC, add the two printers in CUPS. For example if the printer server has the IP address 192.168.0.15:
Epson printer - Device URI: socket://192.168.0.15:9100
Brother printer - Device URI: socket://192.168.0.15:9101
Here's how the choice was made: The Epson printer has the lower bus number, so give it the first port number (9100). The Brother printer then gets the next higher port number (9101).
I found out the above by experimentation. There is probably a better way to determine which logical port (9100/9101) connects to which physical USB port. Perhaps someone can enlighten me
BTW, this printer daemon will also work with parallel port printers, but I haven't tested that.
Short description from the p910nd man page
p910nd is a small printer daemon intended for diskless workstations that does not spool to disk but passes the job directly to the printer. Normally a lpr daemon on a spooling host connects to it with a TCP connection on port 910n (where n=0, 1, or 2 for lp0, 1 and 2 respectively). p910nd is particularly useful for diskless Linux workstations such as those set up with LTSP and embedded devices that have a printer hanging off them. Common Unix Printing System (CUPS) supports this protocol, it's called the AppSocket protocol and has the scheme socket://. LPRng also supports this protocol and the syntax is lp=remotehost%9100 in /etc/printcap.
Installing the daemon
Download p910nd-0.93-i486-1.tgz and install in SlaxerPup by clicking on the file name.
You can test it by simply executing p910nd in a terminal
# p910nd &
If you want the daemon to start at every bootup, just include the above line (without the #) in /etc/rc.d/rc.local.
Using the daemon
On your client PC, configure the printer in CUPS. When CUPS asks which URI to use, choose 'socket://' and add the IP address of the 'server', i.e. the PC running the printer daemon (choosing a static IP address for the printer server makes things easier ) followed by a colon and the port number).
Example URI: socket://192.168.0.15:9100
That's it!
Advanced - using two printers on the same server
Two printers on the same server is a little more complicated, but I did get it to work. Here's where the 'lsusb' utility came in handy. Two instances of the daemon need to run and the server must somehow determine which daemon controls which physical USB port.
Here's how I did it
1. Connect both printers to USB ports on the server.
2. Start up two printer daemons (in a terminal or in rc.local). The daemons will change name to reflect which port they use.
# p910nd -f /dev/usb/lp0 0 &
# p910nd -f /dev/usb/lp1 1 &
3. Run lsusb in a terminal and check the output. For example:
# lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 04f9:0027 Brother Industries, Ltd HL-2030 Laser Printer
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 04b8:0005 Seiko Epson Corp. Stylus D88+
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
#
Note that here the Epson printer is on Bus 001 and the Brother printer on Bus 002.
4. On your client PC, add the two printers in CUPS. For example if the printer server has the IP address 192.168.0.15:
Epson printer - Device URI: socket://192.168.0.15:9100
Brother printer - Device URI: socket://192.168.0.15:9101
Here's how the choice was made: The Epson printer has the lower bus number, so give it the first port number (9100). The Brother printer then gets the next higher port number (9101).
I found out the above by experimentation. There is probably a better way to determine which logical port (9100/9101) connects to which physical USB port. Perhaps someone can enlighten me
BTW, this printer daemon will also work with parallel port printers, but I haven't tested that.
Methinks Raspberry Pi were ideal for runnin' Puppy Linux
Hej Joe,
I finally got around to fixing the 'FATAL: Module usbhid not found.' message that occurs during booting.
This happens because a script tries to modprobe the usbhid module but SlaxerPup's kernel already has the usbhid module compiled in it.
'modprobe usbhid' actually occurs in two scripts:
/etc/rc.d/functions4puppy4
/usr/X11R7/bin/xwin
I've modified these scripts and have attached them in a tarball.
Paul
I finally got around to fixing the 'FATAL: Module usbhid not found.' message that occurs during booting.
This happens because a script tries to modprobe the usbhid module but SlaxerPup's kernel already has the usbhid module compiled in it.
'modprobe usbhid' actually occurs in two scripts:
/etc/rc.d/functions4puppy4
/usr/X11R7/bin/xwin
I've modified these scripts and have attached them in a tarball.
Paul
- Attachments
-
- usbhid-fix.tar.gz
- just unpack and copy the files over the originals
- (40 KiB) Downloaded 555 times
Methinks Raspberry Pi were ideal for runnin' Puppy Linux
Hey Paul (pakt)
wonderful stuff all about the server set up I will write you a PM too later with more details ( I have an all package build which is easier to modify for this type of use )
could you re upload the usbhid-fix.tar.gz it was empty
I did fix the other location that message pops up in the initrd.gz
but missed the other two you fixed thanks
I will add them in thanks
Joe
wonderful stuff all about the server set up I will write you a PM too later with more details ( I have an all package build which is easier to modify for this type of use )
could you re upload the usbhid-fix.tar.gz it was empty
I did fix the other location that message pops up in the initrd.gz
but missed the other two you fixed thanks
I will add them in thanks
Joe
While I'm at it, here's a modified initrd.gz for SlaxerPup-cooking
bchafy has done some wonderful stuff with his Xin puplet
(http://www.murga-linux.com/puppy/viewtopic.php?t=55154)
One of the innovations in Xin is a new kind of re-mastering - a simple and fast way that doesn't require a pupsave file or burning a CD.
It works like this: During bootup, if a folder named 'precfg' is found in the top directory of the boot CD/USB/HD or frugal install, the contents are overlayed the file system.
For example, if folder precfg contains the file /etc/rc.d/rc.local, it replaces the original in the file system. Great for simple mods and troubleshooting
In bchafy's own words: "A precfg area for faster re-mastering, no need to regenerate a .SFS every time you want to change the core, and no need for a hard drive to store customizations"
I have added a slightly modified version of bchafy's code in SlaxerPup's initrd.gz. It works as I have described above.
Enjoy
bchafy has done some wonderful stuff with his Xin puplet
(http://www.murga-linux.com/puppy/viewtopic.php?t=55154)
One of the innovations in Xin is a new kind of re-mastering - a simple and fast way that doesn't require a pupsave file or burning a CD.
It works like this: During bootup, if a folder named 'precfg' is found in the top directory of the boot CD/USB/HD or frugal install, the contents are overlayed the file system.
For example, if folder precfg contains the file /etc/rc.d/rc.local, it replaces the original in the file system. Great for simple mods and troubleshooting
In bchafy's own words: "A precfg area for faster re-mastering, no need to regenerate a .SFS every time you want to change the core, and no need for a hard drive to store customizations"
I have added a slightly modified version of bchafy's code in SlaxerPup's initrd.gz. It works as I have described above.
Enjoy
Methinks Raspberry Pi were ideal for runnin' Puppy Linux
Hey Paul
don't know why it wouldnt open only in a new version of xarchiver
thanks I packaged it up
http://www.puppy2.org/slaxer/usbhidfix- ... 3_SLXR.txz
I added this to the slack-desc
I'll test the initrd looks very interesting
this has a lot of ideas running in my head now
of what could be done
a big thanks
Joe
don't know why it wouldnt open only in a new version of xarchiver
thanks I packaged it up
http://www.puppy2.org/slaxer/usbhidfix- ... 3_SLXR.txz
I added this to the slack-desc
Code: Select all
usbhidfix: usbhidfix (suppress usbhid error message)
usbhidfix:
usbhidfix: thanks to pakt
I'll test the initrd looks very interesting
this has a lot of ideas running in my head now
of what could be done
a big thanks
Joe