slaxer_pup "cooking version" released 5-19-2010
slaxer_pup "cooking version" released 5-19-2010
Slackware is the oldest surviving linux distro
uses the 2.6.27.7 kernel patched with lzm support not using the puppy
kernel config file which makes this unique
*the 2.6.27.7 kernel is what slackware 12.2 uses as the default kernel
cooking 5-19-2010 101 MB
http://www.puppy2.org/slaxer/Slaxer_Pup ... 9-2010.iso
5a89adf12cf9b11e4997419ec03b761d Slaxer_Pup-4.12-cooking-5-19-2010.iso
after downloading a package you just click on it to install it
no command line code needed
live cd ? no problem packages will install also
=========================================
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
========================================
upgrade pwireless
pwireless-0.8.4-i486-3_SLXR.txz
---> download_now
wifi ebox 2300
VT6655-driver-v1.20.02-i486-3_SLXR.txz
---> download_now
sound driver ebox 2300
module-snd-sis7019-2.6.27.7-i486-3_SLXR.txz
---> download_now
wifi driver ath5k
madwifi-r3878-20081204_2.6.27.7-i486-3_SLXR.txz
---> download_now
wifi driver martian
martian-full-20080625-i486-3_SLXR.txz
---> download_now
wifi driver broadcom-hybrid
broadcom-hybrid-5.10.91.93-k2.6.27.7-i486-3_SLXR.txz
---> download_now
video drivers
updated to include nvidia drivers
Version: 180.
Legacy GPU version (71.86.xx series):
Legacy GPU version (96.43.xx series):
Legacy GPU version (173.14.xx series):
nvidia -180.29 series for the 2.6.27.7 kernel
nvidia-driver-180.29-i486-3_SLXR.txz
---> download_now
nvidia-kernel-180.29_2.6.27.7-i486-3_SLXR.txz
---> download_now
nvidia-legacy71 series for the 2.6.27.7 kernel
nvidia-legacy71-driver-71.86.09-i486-3_SLXR.txz
---> download_now
nvidia-legacy71-kernel-71.86.09_2.6.27.7-i486-3_SLXR.txz
---> download_now
nvidia-legacy96 series for the the 2.6.27.7 kernel
nvidia-legacy96-driver-96.43.11-i486-3_SLXR.txz
---> download_now
nvidia-legacy96-kernel-96.43.11_2.6.27.7-i486-3_SLXR.txz
---> download_now
nvidia-legacy173 series for the the 2.6.27.7 kernel
nvidia-legacy173-driver-173.14.18-i486-3_SLXR.txz
---> download_now
nvidia-legacy173-kernel-173.14.18_2.6.27.7-i486-3_SLXR.txz
---> download_now
multi media players
mplayer
luxury powerful media plays everything *plays real player
3 skins so you can select the look you want
*if a file doesnt play you could dragN drop it in the viewer
MPlayer-1.0rc2-i486-3_SLXR.txz
---> download_now
extra plug ins for mozilla
mplayerplugin-3.5.0-i486-3_SLXR.txz
---> download_now
real player
if you just need to use real player video and audio this what you need
REALPLAYER-11-i486-3_SLXR.txz
---> download_now
xmms
super light media player still a classic
xmms-1.2.11-i486-3_SLXR.txz
---> download_now
=================special =================
devx compiler lite 40MB
for compiling most packages
*removed qt,python was xz compressed for a smaller package
412-devx-i486-3_SLXR.txz
---> download_now
kernel sources lite 40MB
extra support for compiling special packages and drivers
kernel-slxr-2.6.27.7-i486-3_SLXR.txz
---> download_now
=====================================
src2pkg build packages from source code for the best compatibility
special thanks to Gilbert Ashley forum member amigo
updated 5-22-2010
http://distro.ibiblio.org/pub/linux/dis ... arch-3.tgz
************************************************************
Now all the fixes and new support in a live cd !
Wow ! finally
there's no looking back
************************************************************
*note all packages for cooking will be in *.txz format
with a "-3_SLXR.txz" suffix will upload soon
* you can slaxer pup to repair and install packages on the official slackware 13 using the built in package tools a great rescue repair disk
Slackfind
a slackware package finding tool
http://slackfind.net
Joe
Last edited by big_bass on Tue 29 Jun 2010, 17:17, edited 38 times in total.
features
Hey, this is good!
Hope you can list the features of this puppy.
Is it XO-1-ready (having kernel 2.6.27.7)?
Will be great to have its core ready for net-booting and then load one's choice applications via NFS or Samba shares. (No other puppy does it, not even Quirky.)
Also, I was looking for a way to access Slackware packages through Slaxer. How is this done? (Yes, dumb question. )
Hope you can list the features of this puppy.
Is it XO-1-ready (having kernel 2.6.27.7)?
Will be great to have its core ready for net-booting and then load one's choice applications via NFS or Samba shares. (No other puppy does it, not even Quirky.)
Also, I was looking for a way to access Slackware packages through Slaxer. How is this done? (Yes, dumb question. )
Puppy user since Oct 2004. Want FreeOffice? [url=http://puppylinux.info/topic/freeoffice-2012-sfs]Get the sfs (English only)[/url].
Hey raffy
I am uploading some txz packages so you can try out the package management
if you know the package is good you can just click on the package and it will install
it first asks a yes or no with the package name
updated the server with more packages
all the nvidia drivers and more
the cooking packages are txz
***************txz cooking***********
another feature I built in was package 2 folder
if you right click on the package you get an option to decompress and make a folder using unzipper_dragndrop5 in the ROX right click box
thats for seeing whats inside a package before installing it
a safety step or you can edit it and rebuild it
if you wanted to install official packages you have to be more careful here
because of dependencies
thats why I added in a dependency checker
but an example would be
http://slackware.cs.utah.edu/pub/slackware/
then you could select 12.2
or 13
http://repository.slacky.eu/slackware-13.0
*if "I can" add in any support you need I will
Joe
I am uploading some txz packages so you can try out the package management
if you know the package is good you can just click on the package and it will install
it first asks a yes or no with the package name
updated the server with more packages
all the nvidia drivers and more
the cooking packages are txz
***************txz cooking***********
another feature I built in was package 2 folder
if you right click on the package you get an option to decompress and make a folder using unzipper_dragndrop5 in the ROX right click box
thats for seeing whats inside a package before installing it
a safety step or you can edit it and rebuild it
if you wanted to install official packages you have to be more careful here
because of dependencies
thats why I added in a dependency checker
but an example would be
http://slackware.cs.utah.edu/pub/slackware/
then you could select 12.2
or 13
http://repository.slacky.eu/slackware-13.0
*if "I can" add in any support you need I will
Joe
Last edited by big_bass on Sun 23 May 2010, 00:08, edited 6 times in total.
big_bass,
Thank you for the update on Slaxer_Pup! Unfortunately, this is a mute Pup on my Dell Inspiron 910 netbook, even after adding "options snd-hda-intel index=0 model=dell" at the end of your /etc/modprobe.conf file. (This worked on your previous Slaxer_Pup version.)
I am wondering if the missing "Speaker" volume setting in Alsaconfig is the culprit, but have no way to verify my suspicions.
Regardless, please consider me a fan!
-Roy
Thank you for the update on Slaxer_Pup! Unfortunately, this is a mute Pup on my Dell Inspiron 910 netbook, even after adding "options snd-hda-intel index=0 model=dell" at the end of your /etc/modprobe.conf file. (This worked on your previous Slaxer_Pup version.)
I am wondering if the missing "Speaker" volume setting in Alsaconfig is the culprit, but have no way to verify my suspicions.
Regardless, please consider me a fan!
-Roy
Hey Roy
thanks for posting
I didn't change anything that would effect the sound
so please try again with the
and confirm if you still have sound and the speaker slider in jwm up
because after running alsaconf the slider for the speaker volume gets reset to zero slide it up
*the initrd is the same also
thanks
since I updated the sfs the new sfs has to be used the names are the same the sizes are different
Joe
thanks for posting
I didn't change anything that would effect the sound
so please try again with the
Code: Select all
puppy pfix=ram
because after running alsaconf the slider for the speaker volume gets reset to zero slide it up
*the initrd is the same also
thanks
since I updated the sfs the new sfs has to be used the names are the same the sizes are different
click on the top of the first bar then use the up and down arrows to change the volume
I am wondering if the missing "Speaker" volume setting in Alsaconfig is the culprit, but have no way to verify my suspicions.
Joe
- Attachments
-
- alsa.png
- (10.25 KiB) Downloaded 3853 times
Thanks, Joe.
Silly me, my problem was that I was using the 'puppy pfix=ram' boot parameter! I had forgotten that the "options snd-hda-intel model=dell" addition at the end of /etc/modprobe.conf file would not take just by re-starting X; one has to create a save-file and reboot without pfix=ram for the change to be recognised.
This statement is valid for all Linux distro's I know of which are using versions of Alsa prior to v1.0.20. Sound works with Slaxer_Pup's earlier version of Alsa after modifying modprobe.conf and rebooting with a save-file.
Again, my apologies for not remembering the necessary steps with Alsa v1.0.16!
-Roy
Silly me, my problem was that I was using the 'puppy pfix=ram' boot parameter! I had forgotten that the "options snd-hda-intel model=dell" addition at the end of /etc/modprobe.conf file would not take just by re-starting X; one has to create a save-file and reboot without pfix=ram for the change to be recognised.
This statement is valid for all Linux distro's I know of which are using versions of Alsa prior to v1.0.20. Sound works with Slaxer_Pup's earlier version of Alsa after modifying modprobe.conf and rebooting with a save-file.
Again, my apologies for not remembering the necessary steps with Alsa v1.0.16!
-Roy
.
Roy
Hey Roy
that will be a big help to anyone that has a special fix for sound
on Alsa v1.0.16
there is a good reason I didnt update alsa on the first cooking
because from here on .... everthing will be updated and I had to establish a reference point with all the built in package management support making it slackware 13 package compatible
remember all this work is pre woof I added in and coded the Xdialog
package management from scratch since there is no how to for that
with all that new power at hand its just a small step away from
a major packages update
*thanks for posting the sound fix for your box Roy !
updated the server with more packages
all the nvidia drivers and more
the cooking packages are txz
Joe
Roy
Sound works with Slaxer_Pup's earlier version of Alsa after modifying modprobe.conf and rebooting with a save-file.
I had forgotten that the "options snd-hda-intel model=dell" addition at the end of /etc/modprobe.conf file would not take just by re-starting X; one has to create a save-file and reboot without pfix=ram for the change to be recognised.
Hey Roy
that will be a big help to anyone that has a special fix for sound
on Alsa v1.0.16
there is a good reason I didnt update alsa on the first cooking
because from here on .... everthing will be updated and I had to establish a reference point with all the built in package management support making it slackware 13 package compatible
remember all this work is pre woof I added in and coded the Xdialog
package management from scratch since there is no how to for that
with all that new power at hand its just a small step away from
a major packages update
*thanks for posting the sound fix for your box Roy !
updated the server with more packages
all the nvidia drivers and more
the cooking packages are txz
Joe
Thanks for being so understanding / forgiving, Joe. I still fell like a bit of a heel.....
Can you explain a bit about how your package management system works? After getting sound to work, I downloaded your Broadcom wireless driver to a thumb drive from another computer, transferred it over to the Dell, and installed it by right clicking on it (same method as any other .pet). That put my Dell netbook on line.
But, even with an active internet connection, clicking on ~/slaxer_pkg_tools2.2 doesn't seem to accomplish anything. It does bring up the Xdialog box of options, and clicking on xinstaller shows any .txz package I have previously (manually) downloaded and placed in the ~ directory, but then returns to the main Xdialog screen. Nothing gets installed, nothing shows up in Puppy Package Manager (Menu > Setup > Puppy package manager). Even the Broadcom driver package -- although clearly installed and functioning -- doesn't show up as "installed".
I am certain that this is simply an education issue and am not doing something quite right on my end.
Oh, by the way, booting from a CD with a save file on a thumb drive is giving me an initial desktop which is strictly black -- no icons, no background,... restarting the X-server (ctrl-alt-backspace) from there fixes it -- so I might have other problems on my end.
-Roy
Can you explain a bit about how your package management system works? After getting sound to work, I downloaded your Broadcom wireless driver to a thumb drive from another computer, transferred it over to the Dell, and installed it by right clicking on it (same method as any other .pet). That put my Dell netbook on line.
But, even with an active internet connection, clicking on ~/slaxer_pkg_tools2.2 doesn't seem to accomplish anything. It does bring up the Xdialog box of options, and clicking on xinstaller shows any .txz package I have previously (manually) downloaded and placed in the ~ directory, but then returns to the main Xdialog screen. Nothing gets installed, nothing shows up in Puppy Package Manager (Menu > Setup > Puppy package manager). Even the Broadcom driver package -- although clearly installed and functioning -- doesn't show up as "installed".
I am certain that this is simply an education issue and am not doing something quite right on my end.
Oh, by the way, booting from a CD with a save file on a thumb drive is giving me an initial desktop which is strictly black -- no icons, no background,... restarting the X-server (ctrl-alt-backspace) from there fixes it -- so I might have other problems on my end.
-Roy
Roy
Yes! you have discovered that you can install packages
without petget
you just installed the packages and updated the Broadcom wireless driver using the Xdialog slaxer installer which officially registers the package without petget in the middle to handle things
if you play a bit with the installed package you could check dependencies
you could see every file that was installed
you could search for packages
you could uninstall it too
and you dont have to be a slaxerware user
because its set up to be easy
this means that you can install /uninstall and register
packages using my built in support with the Xdialog slaxer management
which also means many more things
you now have a distro that can handle
tgz, (sackaware's) old standard
txz (slackware's new standard )
tbz and tlz (slackware spin offs distros use )
*lzm from slax can be converted first then repackaged
lzm support is built in too
so I dont convert slackware packages to work with puppy's petget
I use slackware packages that work with slackware's package tools as the backend
which makes you linux compatible with the rest of the word
nobody else is doing anything like that on "puppy"
man there are so many things more to say about that
but it will unfold layer by layer
*since slackware uses kde alot I custom build the packages for slaxer_pup keeping it light
Joe
It does bring up the Xdialog box of options, and clicking on xinstaller shows any .txz package I have previously (manually) downloaded and placed in the ~ directory, but then returns to the main Xdialog screen. Nothing gets installed, nothing shows up in Puppy Package Manager (Menu > Setup > Puppy package manager). Even the Broadcom driver package -- although clearly installed and functioning -- doesn't show up as "installed".
Yes! you have discovered that you can install packages
without petget
you just installed the packages and updated the Broadcom wireless driver using the Xdialog slaxer installer which officially registers the package without petget in the middle to handle things
if you play a bit with the installed package you could check dependencies
you could see every file that was installed
you could search for packages
you could uninstall it too
and you dont have to be a slaxerware user
because its set up to be easy
this means that you can install /uninstall and register
packages using my built in support with the Xdialog slaxer management
which also means many more things
you now have a distro that can handle
tgz, (sackaware's) old standard
txz (slackware's new standard )
tbz and tlz (slackware spin offs distros use )
*lzm from slax can be converted first then repackaged
lzm support is built in too
so I dont convert slackware packages to work with puppy's petget
I use slackware packages that work with slackware's package tools as the backend
which makes you linux compatible with the rest of the word
nobody else is doing anything like that on "puppy"
man there are so many things more to say about that
but it will unfold layer by layer
*since slackware uses kde alot I custom build the packages for slaxer_pup keeping it light
Joe
pwireless-0.8.3 does not automatically create a profile when asked to. Upgrading to pwireless-0.8.4 from the thread http://www.murga-linux.com/puppy/viewto ... 1&start=45 solves this problem.
No need to uninstall anything to my knowledge. Just download pwireless-0.8.4.pet and install it over version 0.8.3.
-Roy
BTW, it looks like some of the issues I had earlier were caused by a problem with my save file... I am learning to dislike the thumbdrives with the unmarked little read/write switch on the side of them!
No need to uninstall anything to my knowledge. Just download pwireless-0.8.4.pet and install it over version 0.8.3.
-Roy
BTW, it looks like some of the issues I had earlier were caused by a problem with my save file... I am learning to dislike the thumbdrives with the unmarked little read/write switch on the side of them!
DVB-T
Hi Joe
Installed the updated files and set this machine up from scratch with DEVX and kernal sources. All is working well got VBox up and running easliy
I got a bit carried away thought about installing some TV recording scripts and VLC.
I have TV set up on the same machine using a vanilla puppy 4.3 so ran dmesg and surprisingly there was no DVB-T device.
This is from lupu-500 but missing on slaxer_pup on the same machine
I have a 20,000 record + access control system running on xp in vbox in slaxer_pup at an organisation that I do voluntary work for. Running perfectly, up time now 6 weeks since I shifted it over from 'parallels' and centos 4.6.
Cheers
Warren
This machine-
AMD Phenom(tm) II X2 545 Processor : 3013.30MHz
Gigabyte ma785g-ud3h mobo
Installed the updated files and set this machine up from scratch with DEVX and kernal sources. All is working well got VBox up and running easliy
I got a bit carried away thought about installing some TV recording scripts and VLC.
I have TV set up on the same machine using a vanilla puppy 4.3 so ran dmesg and surprisingly there was no DVB-T device.
This is from lupu-500 but missing on slaxer_pup on the same machine
Great to see your long term commitment to this normalizing derivative.
dvb-usb: found a 'KWorld USB DVB-T TV Stick II (VS-DVB-T 395U)' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (KWorld USB DVB-T TV Stick II (VS-DVB-T 395U))
Adding 514072k swap on /dev/sda2. Priority:-1 extents:1 across:514072k
af9013: firmware version:4.95.0
DVB: registering adapter 0 frontend 0 (Afatech AF9013 DVB-T)...
Quantek QT1010 successfully identified.
input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:12.2/usb1/1-2/input/input5
dvb-usb: schedule remote query interval to 150 msecs.
dvb-usb: KWorld USB DVB-T TV Stick II (VS-DVB-T 395U) successfully initialized and connected.
usbcore: registered new interface driver dvb_usb_af9015
I have a 20,000 record + access control system running on xp in vbox in slaxer_pup at an organisation that I do voluntary work for. Running perfectly, up time now 6 weeks since I shifted it over from 'parallels' and centos 4.6.
Cheers
Warren
This machine-
AMD Phenom(tm) II X2 545 Processor : 3013.30MHz
Gigabyte ma785g-ud3h mobo
Tried to install skype-2.0.0.72-i486-1jsc.txz from http://slackware.schoepfer.info/13.0/slackware/misc/ Slackware 13.0 directory by using slaxer_pkg_tools2.2, but something went wrong.
First attempt didn't seem to install, but my bottom right tray Freememoryapplet ended up in the upper left-hand corner of my screen in a Gtk-dialog (?) box.
A second attempt to install Skype from the download found Skype under Network in the main menu chain. Never could restore the Free Memory applet, so just performed a hard shutdown via the power button and started over.
Ended up installing skype-2.0.0.72.pet which I had downloaded from the forum ages ago.
Should I be using Slackware 12 stuff for now instead of Slackware 13.0 stuff?
-Roy
ADDED as an afterthought: Maybe it would be a good idea for me to read the earlier Slaxer_Pup threads to get a better handle on the additional software issue....!
First attempt didn't seem to install, but my bottom right tray Freememoryapplet ended up in the upper left-hand corner of my screen in a Gtk-dialog (?) box.
A second attempt to install Skype from the download found Skype under Network in the main menu chain. Never could restore the Free Memory applet, so just performed a hard shutdown via the power button and started over.
Ended up installing skype-2.0.0.72.pet which I had downloaded from the forum ages ago.
Should I be using Slackware 12 stuff for now instead of Slackware 13.0 stuff?
-Roy
ADDED as an afterthought: Maybe it would be a good idea for me to read the earlier Slaxer_Pup threads to get a better handle on the additional software issue....!
you said that you installed a pet from the forum for skypeEnded up installing skype-2.0.0.72.pet which I had downloaded from the forum ages ago.
and that version was compiled "static"
if it works for you use it
but what is not known to the end user that way is what is required to
fill the correct dependencies "its all rolled in one package" but its not [one] package
so you could be mislead into thinking if I just download a skype package it should work
without any other dependent packages (it keeps the user in the dark to have any chance to use a full blown linux system )
skype which requires at least as add on dependencies
--> dbus-glib-0.80
--> glib2-2.18.4
-->qt-r1008952 a special qt
there is also a dependency check in the package tools
slaxer_pkg_tools2.2
if you run the dependency check on that program
a list is saved in
/var/lib/pkgtool/dependencies/
that if all the dependencies were met you wouldn't have this line
-----------------------------------------------
has these missing library files:
libQtDBus.so.4 libQtGui.so.4 libQtNetwork.so.4 libQtCore.so.4
many complex packages that require various other packages
to be complete it is important to know what is needed first
I will be building more packages as I go
thanks for the wireless fix I uploaded the fix as a txz package
pwireless-0.8.4-i486-3_SLXR.txz
Joe
Last edited by big_bass on Mon 24 May 2010, 19:09, edited 1 time in total.
Hey Roy
I did get skype to load using slackware 13 packages
its much bigger than the static version because qt is much larger
on slackware 13
so it can be done
UPDATED to show the packages used
note qt is 40MB compressed
skype-2.0.0.72
--> dbus-glib-0.80
--> glib2-2.18.4
--> qt-r1008952
http://www.puppy2.org/slaxer/dbus-glib- ... 3_SLXR.txz
http://www.puppy2.org/slaxer/glib2-2.18 ... 3_SLXR.txz
http://www.puppy2.org/slaxer/qt-r100895 ... 3_SLXR.txz
http://www.puppy2.org/slaxer/skype-2.0. ... 3_SLXR.txz
Joe
I did get skype to load using slackware 13 packages
its much bigger than the static version because qt is much larger
on slackware 13
so it can be done
UPDATED to show the packages used
note qt is 40MB compressed
skype-2.0.0.72
--> dbus-glib-0.80
--> glib2-2.18.4
--> qt-r1008952
http://www.puppy2.org/slaxer/dbus-glib- ... 3_SLXR.txz
http://www.puppy2.org/slaxer/glib2-2.18 ... 3_SLXR.txz
http://www.puppy2.org/slaxer/qt-r100895 ... 3_SLXR.txz
http://www.puppy2.org/slaxer/skype-2.0. ... 3_SLXR.txz
Joe
- Attachments
-
- skype.png
- (25.98 KiB) Downloaded 1553 times
Last edited by big_bass on Wed 26 May 2010, 13:42, edited 2 times in total.
big_bass I tested the iso but failed to get out on the internet because I don't know what driver to load.
I have no need to know that when I use the Simple Network S. in Quirky.
It just works.
Can I borrow that SNS in some way so I can test your distro? or how do I find out what LAN I have?
I have no need to know that when I use the Simple Network S. in Quirky.
It just works.
Can I borrow that SNS in some way so I can test your distro? or how do I find out what LAN I have?
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
to see what you have for network
you could
and post the result at least I could see what you are using
Joe
you could
Code: Select all
grep "eth0:" /tmp/bootkernel.log
Joe
Seems me have nVidia MCP61 ethernet.
I log out and reboot and test if that one us included among the options.
Did you answer why you don't provide a sns among the network.
Or if I can easily import sns from an existing version or as a Pet?
could not find any kind of nvidia unless the list use a name for it me not recognize.
the more did not help either. It loaded the first always and did not test next and next.
Why not use sns instead for this cumbersome failure? Are you sure sns is not available for your distro.
I log out and reboot and test if that one us included among the options.
Did you answer why you don't provide a sns among the network.
Or if I can easily import sns from an existing version or as a Pet?
could not find any kind of nvidia unless the list use a name for it me not recognize.
the more did not help either. It loaded the first always and did not test next and next.
Why not use sns instead for this cumbersome failure? Are you sure sns is not available for your distro.
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though