Slaxer_Pup 4.12 solid and stable non woof build

[big_bass]

found the problem
edit # CONFIG_SND_SIS7019 is not set
to read

CONFIG_SND_SIS7019=m

I did it with geany but you could do it the official way
Joe

I had to build just the sound modules I hope this works

had to modify the makefile
if it works I'll document how


LD [M] sound/pci/snd-rme32.ko
CC sound/pci/snd-rme96.mod.o
LD [M] sound/pci/snd-rme96.ko
CC sound/pci/snd-sis7019.mod.o

LD [M] sound/pci/snd-sis7019.ko
CC sound/pci/snd-sonicvibes.mod.o
LD [M] sound/pci/snd-sonicvibes.ko
CC sound/pci/snd-via82xx-modem.mod.o
LD [M] sound/pci/snd-via82xx-modem.ko
CC sound/pci/snd-via82xx.mod.o
LD [M] sound/pci/snd-via82xx.ko


a long day hope it works
Updated 12/22/2009 to install in the correct place since it was tested to work

Joe

[pakt]

Thanks guys, got SlaxerPup audio working on the eBox-2300

Playing internet radio on it at the moment using wget like this (using the CLI):

Code: Select all

# wget -q -O - http://broadcast.infomaniak.net:80/jazzradio-high.mp3 | madplay -

Both Joe's and the snd-sis7019 driver module I compiled work, but the drivers are not identical: they are exactly the same size but their md5sums are not the same. Could it be because I used devx_412.sfs and Joe used 412-devx-i486-2.tgz? Different compiler options?

I used a frugal install and a large-ish kernel-source sfs I made from Joe's file - this one had only the object files removed for safety's sake. I'll experiment with cutting down the kernel source some more.

Btw, interesting that the .config file is hidden in /proc/config.gz. Good to know

Paul

[amigo]

"interesting that the .config file is hidden in /proc/config.gz" -that's a configurable option to the kernel -which can be built as a module or built-in. It should always be thr first thing you trun on -and not as a module. That way you'll never have doubt about what the kernel is capable of -or lose a working configuration file .-)

[big_bass]

Paul *pakt

Great news!

how to for the compile
not needed if you just want to use the driver just install the above driver

but if you wanted to know what was needed to compile it read on
*********************************************************

I updated the sis driver post since you tested the driver to be working

I used this guide http://www.faqs.org/docs/Linux-HOWTO/Kernel-HOWTO.htmlwhich was modified from a how to compile one module its old but worked
mind you I didnt have that line of code #SUBDIRS with a comment so I added it where I thought it should be
and I compiled in the folder I didnt move the object

cp Makefile Makefile.my
then I cleaned the objects in the sound folder
cd /usr/src/linux-2.6.27.7/sound/pci then rm *.o
SUBDIRS =sound/pci/ #add line number 69 in the Makefile.my for slxr
# Save the file Makefile.my


make -f Makefile.my modules

------------------------------------

snip from makefile.my


# Use make M=dir to specify directory of external module to build
# Old syntax make ... SUBDIRS=$PWD is still supported
# Setting the environment variable KBUILD_EXTMOD take precedence
SUBDIRS =sound/pci/ #add line number 69 in the Makefile.my for slxr
ifdef SUBDIRS
KBUILD_EXTMOD ?= $(SUBDIRS)
endif
ifdef M
ifeq ("$(origin M)", "command line")
KBUILD_EXTMOD := $(M)
endif
endif
--------------------------------------


to clean up the sources you could do it one at a time folder for folder or use this code

Code: Select all

find /usr/src/linux-2.6.27.7 -name '*.o' -exec echo rm {} \; >/tmp/big_clean2

that way its safe nothing gets deleted you can check what your going to delete if you run the text output as a script later
and edit out anything you need to keep


I had to do it one at a time because I compiled the modules at an internet cafe
Joe

[pakt]

Thanks for the guide Joe

I compiled the modules at an internet cafe

Guess you got your 'Compiler USB stick' working, eh? Nice one


A couple of items I've been meaning to post:

1) We talked about modifying 'init' earlier in the thread to make SlaxerPup boot faster by, e.g., adding a 'pfix=usb' option to minimize the search for Puppy files.

Well, while looking through 'init' the other day I found a reference to a boot option that I wasn't aware of that speeds up booting considerably if you have several partitions (like I have).

The option is 'pdev1=<partition-with-puppy-files>'. (That's a 'one' at the end of 'pdev')

As an example, here is the faster GRUB line I now use:
/Slaxer_Pup/vmlinuz pmedia=atahd pdev1=sda7 psubdir=Slaxer_Pup pfix=fsck

2) The new vt6655 wireless module works very well. But when shutting down, SlaxerPup will stop with some kind of code dump with that module loaded. I've modified rc.shutdown so it will look for and unload the module. That fixes the problem.

3) Booting always shows an "Error loading usbhid module" error. This module is in the kernel so I've fixed xwin not to show the error message.

4) I've included rc.sysinit with both the usb booting delay and the 'count-to-ten' delay removed (can't recall if the rc.sysinit I uploaded earlier had both mods).

Paul

[big_bass]

UPDATED 12-29-2009 lite version
src-kernel-slxr-2.6.27.7 Now 71MB 250 MB installed make sure you have the space first though

http://puppy2.org/slaxer/src-kernel-slx ... 2-slxr.tgz

you could add more but the idea was this to clean up the source
to get it down smaller I used this

Code: Select all

find /usr/src/linux-2.6.27.7 -name '*.o' -exec echo rm {} \; >/tmp/big_clean2

find /usr/src/linux-2.6.27.7 -name '*.ko' -exec echo rm {} \; >/tmp/big_clean3

find /usr/src/linux-2.6.27.7 -name '.*.cmd' -exec echo rm {} \; >/tmp/big_clean4

find /usr/src/linux-2.6.27.7 -name '*.mod.o' -exec echo rm {} \; >/tmp/big_clean5

find /usr/src/linux-2.6.27.7 -name '.*.ko.cmd' -exec echo rm {} \; >/tmp/big_clean6

then look them over first and make them executable



@Hey Paul (pakt)

thanks for the three scripts you posted above
the shutdown script I will include with the the sis module package
so there will be a clean shutdown

As an example, here is the faster GRUB line I now use:
/Slaxer_Pup/vmlinuz pmedia=atahd pdev1=sda7 psubdir=Slaxer_Pup pfix=fsck

fsck checking is always good idea but slows down the boot up specially
on large files if you suffered a power out before saving

so you could do that like slackware every 40 boot ups as a default or so
maybe 20 if you like to be more secure

thanks again for the scripts I looked them over and I will include them all

Joe

[gronos04]

Hi BB thanks for the kernel sources.
Was able to get VirtualBox up and running without any problems.
I hope to replace my Centos 4.6 running Parallels system, which I use to run a Windows based access control system, with Slaxer_Pup running VirtualBox.
Have been using Slaxer_Pup on my 'Panasonic CF-18 toughbook' since you released it and I am very happy with it.
I may even try to get the touchscreen up and running one day.
Your hard work is much appreciated.

[Aitch]

gronos04

touchscreen - this may help

http://www.hentges.net/misc/howtos/Pana ... reen.shtml

Happy New Year, Joe

Aitch

[big_bass]

@gronos04 thanks for the report

@Aitch thanks for helping with the touch screen link



---------------------------------------------------------------------
SlaxerPup_updater version 1-7-2010 now with a GUI


to keep slaxer pup updated
in a logical organized way for
experts and new users


automatic updates!
auto downloaded
auto installed too!

now is that easy

Joe

[ttuuxxx]

@gronos04 thanks for the report


automatic updates!
auto downloaded
auto installed too!

now is that easy

Joe

now that is cool
Could be great for bug fixes.
The only 2 options that I can see it missing .s a remove and reset button.
say if you don't want to install all those particular updates ever, the list could get very long.
so if you had a remove button, you tick the ones you want removed from the list and click ok then you get a shorter list, but if you accidentally ticked the wrong one and its gone, it would be a matter of ticking the reset and it would reset the whole list.
well just an idea, Great job Joe
ttuuxxx

[big_bass]

@gronos04 thanks for the report


automatic updates!
auto downloaded
auto installed too!

now is that easy

Joe

now that is cool
Could be great for bug fixes.
The only 2 options that I can see it missing .s a remove and reset button.
say if you don't want to install all those particular updates ever, the list could get very long.
so if you had a remove button, you tick the ones you want removed from the list and click ok then you get a shorter list, but if you accidentally ticked the wrong one and its gone, it would be a matter of ticking the reset and it would reset the whole list.
well just an idea, Great job Joe
ttuuxxx

Hey Jeff

Thanks for the feedback

The only 2 options that I can see it missing .s a remove and reset button.

the same script when run again auto resets all the values to the default what should be installed (at least what I tested to be working correctly ) and is the bare minimum list

the majority should install all the preselected values

[ only install what you want selected *I consider that the expert option*]
but you can do that also the script allows for it already


*I will have a package manager to offer the bigger selection of "optional packages" which will allow uninstalling also

the main idea here was for the new user or the experienced user to just have some easy way to to get updated / bug fix /edit and add config files too

without going through a heap of threads wondering if you got it all or not


thanks, and since this is the same problem for everyone trying to keep things updated using what ever version of puppy/derivative/other OS

peace brothers

Joe

[Cur Dog]

Big_Bass I would like to give you a big thumbs up for slaxer_pup.
It has been very stable and very fast. I am having a problem with the usb icon loading on top of hda3 icon when I plug in a usb stick. I am not sure if this is the result of something that I done myself because I looked through the thread and did not see problem mentioned before. I have attached screen shot.....any suggestions?

[big_bass]

Hey Cur Dog

I dont know the size of your screen but the idea is the same
and I couldnt read the small print of the usb value

you need to get the usb in the fourth icon location of the screen
lets say your usb is sda1 for an example

the y= is up and down on the far left of the screen
you dont need to edit that

the x= is the right to left position on the screen
thats what has to change

-------------------------------------------------------------------
so to fix it manually open the file

Code: Select all

geany /root/Choices/ROX-Filer/PuppyPin

note: if your y value is different dont change it this is only an example
it has to be manually entered in the PuppyPin

Code: Select all

  <icon x="224" y="704" label="sda1" 

this is the only thing you will edit x="224"

tip this depends on your screen size so to get the value of the fourth location you could also use the same x value as your install icon

save the file

Code: Select all

fixmenus

then restart x



the most import thing is you know what to edit

Joe

[potchan]

Hi Team, and a happy new year started with the awesome updater.

Last days I got enlightenment while started the Potchan build all over again with Slaxer-pup as onGround platform. It's much better than the latest version of Puppy because BK seems to cut some edges especially where I need it most: capability to boot any limpware on Earth smooooothly. Slaxer-pup is more reliable basis to my cloud project (enriched with extra technician's tools and emulators).

Few questions:

1. Should I drop /root/slaxer_updater folder after pet-install without any fear from a damage ? the folder is a bit heavy (8818K). Do all tar.gz'es left inside folder installed already or need further actions ?

2. How I can be directed for adding ext4 support ? I need the closest link in this forum (or elsewhere) and I go on by myself.

3. I have radeonmodule compiled for 2.26.25.16. Do you know of a proper adjustment for slaxer kernel ? I found out since Muppy it helps to sharp display on PCs with old radeon cards when VertRefresh set to 70 (1024x768x24).

4. 11g LevelOne wireless USB modem ? I'm unlucky finding a proper solution to this for my ancient DELL inspiron 2600 test-wreck 1MHz 122M RAM no USB BIOS support (functions as project bottom raf).

Thanks in advance

[Cur Dog]

Thanks Big_Bass, worked like a charm.
I still have a lot to learn when it comes to things like this in puppy.
Sorry if I scaled the screenshot to small, but I didn't want to leave it at 1024x768. I will do better next time....Thanks for your time and again, thanks for Slaxer_Pup.

[big_bass]

SlaxerPup_Uninstaller version 1-7-2010 with a GUI

this is the complement to the installer
the uninstaller

the default is remove nothing so it is safe to
click on it

works for the pets and tgz

how I will do this is by date and code number
so it will be easy to keep track of


for some reason you wanted to uninstall
any of the packages the auto installer installed
(there is no need to do so but you could )

you now have a GUI to do it also

note: removing required packages will break things
but since this is linux you have the right to add
or remove what you want when you want

use with care for advanced users


as you will discover everything gets registered
with pet get and pkgtools

without the new package management

keeping things simple


Joe

[Aitch]

Nice, Joe

btw, have you noticed Slack official [up to 13.0] is now ported [12.2] to the ARM architecture

http://www.slackware.com/

& Slackintosh 12.1 is catching up to Official....

http://workaround.ch/

So, my question is, are you going to attempt adding either ARM or PPC ports/support [or both ] to your wonderful creation?

It would be a first for any Puppy if you did!

Anyhow, keep on trucking, Joe,

Oo! nearly forgot, I had a box the other day, which wouldn't run slaxer_pup xorg...
I think it was i810 chipset, but I was at a friend's and in a hurry, so used 214R instead, which ran ok, - when I go back there I'll get more details
Also, I miss Bubbles & Gemgame..... .....not a problem, until I tried to install....they wouldn't run?? .....any suggestions?

thanks

Aitch

[big_bass]

Hey Aitch


In time other builds will be possible
there are a a few steps that need to be achieved first
and I am on that road

(I left but havent arrived )

anything that doesnt fit well with the true linux way to share and build
keeping things transparent as possible
will be removed or replaced with standard practices

I know this is a process but the end result is
people will have more freedom
and free time


because following standard practices
allows you to honor the past work of so many talented people
who built so many great programs and wrote documentation




Joe

[amigo]

Joe and Aitch, I am up to around 500 packages now with kiss -all of X and the development stuff, plus all the rellay basic packages needed for booting. The scripts I am using are usable on x86, x86_64, ppc, arm -whatever...
I gather that Joe is taking care to collect sources and script the builds for puppy-specific programs -at least I hope so.

kiss is using glibc-2.11.1, gcc-4.4.2, gtk-2.19.1, xorg-7.5-ish, so I am staring from a very up-to-date base. I have written a tool which uses the abundant info from src2pkg dependency files(generated with each package build) to create a build-order for the whole distro or parts of it. I'm using a package format like slackware, but highly modified databse through the addition of extra files which make it possible to track dependencies both ways, md5sums of all files installed and other kewlness. The last couple of days I've been hacking on 'spkg' which is a clone of the slackware pkgtools, but written in C. It runs *much* faster (up to 30 times faster at removing packages). I'm getting close to staring work on the installer, so an installer CD can be created -that'll give you guys something to work with while I go on and start creating the ppc version.

BTW, the slackware arm port has been around for several years -but it only recently got adopted as an official port. Unfoirtunately, it uses its' own build system. Most of AlienBobs SlackBuilds for the 64-bit version have been rolled into the 32-bit tree so that at least those two trees are using a common set of scripts. But any ports to other arches implies re-working all the scripts again to make them work on another arch. This is what my src2pkg scripts are supposed to avoid. Adding another arch just means adding a few lines to src2pkg itself and not to each of hundreds of scripts.

[Aitch]

.....because following standard practices
allows you to honor the past work of so many talented people
who built so many great programs and wrote documentation

Joe, totally agree

however.....

Great stuff, amigo - Your methods, knowledge, and ability continue to astound me

& here I sit with baited breath, [it says here ]

Aitch