Slaxer_Pup 4.12 solid and stable non woof build

[pakt]

anything else for those mini systems let me know
love to see Slaxer_Pup on those

[Getting on soapbox]
Just like Barry loves software that is lean and fast, I love hardware that is small and efficient. Apart from not working as a heating element and also contributing to a lower electricity bill , all electronics last longer when running at a lower temperature. The life span of an electronics component shortens exponentially with increasing temperature, something I learned early on as an electronics professional. I'm retired now due to poor health but I still love working with these gadgets.

The SiS Vortex86 SoC (System on Chip) in the eBox-2300 almost makes up a complete 200MHz, i586-compatible PC, only memory needs to be added, in this case 128MB. Measuring with a simple power meter, the eBox-2300 (including the AC adapter, the inserted CF card (with SlaxerPup) and the wireless module) draws only 11W (max).

This pocket-sized unit was never designed to run as a complete PC but only as a thin client. That's why it's so enjoyable to be able to run Puppy Linux on it albeit rather slowly mainly due to the X-Window GUI. Quitting X and just running a CLI makes this box run acceptably fast. And with SlaxerPup running in RAM, there is still more then 50MB RAM free.

Looking at the future, ARM-based devices promise to be more power efficient than ones based on x86. If windows XP had run on the ARM architecture, I believe we would already have had ARM-based netbooks for sale on the market and not just prototypes displayed at conventions. The demand for netbooks with Linux is simply too low. Who knows, perhaps ARM-based netbooks will appear soon in stores, but running Linux-based Google Chrome OS instead
[Getting off soapbox]

Paul

[mikeb]

Neat stuff...x86 was always the most inefficient architecture yet became the most common...like vhs was the worst format for video tape...I guess it's where big business controls technology these illogical happenings occur
...falls off soapbox
mike

[big_bass]

Gilbert (amigo)

Thanks for posting how to reduce the kernel down to a much smaller size

and the optional overmounting way (I can think of a few other good things to do with that ) thanks

I will be pretty busy until at least January 7th when my kids go back to school from vacation. They start vacation today

so I hope people only down load the sources if they really need them
and I´ll repackage it up later to the smaller size [cleaned up] I´ll take a look at the overmounting of the sources also
that looks like good option

Gilbert is


@Paul (pakt)
I am very thankful that you took the time to go through the initrd and
add the delay fix so that the using the USB install option the USB save file is now detected
since I use USB most of the time I really needed that working
I kind of cut it short in the above post because I was in a hurry


I also love the electronics side of things (an electronics tech )
at 11W of power a solar powered Slaxer
would open many possibilities

so I would take any of your good suggestions
and include it in Slaxer

many times if someone doesnt have the hardware to test on
they just forget about trying to build for it because it makes it much more difficult to test and there is usually alot of trial and error until it finally works but if I know that someone really wants something to work I´ll do my best to help out

thanks for testing and if you had to add a special script or something
to make the wifi work correctly it would help the next guy getting his box running also

ahh about slackware now that you have that also installed it will help to test build anything first using src2pkg in its native home slackware



Joe

[amigo]

src2pkg is now getting up to en even higher level of functionality in KISS-Linux along with the new pkgtools . I've rolled in some ideas from slitaz, but without some of the problems of their packaging system. Getting fairly close to having enough kiss packages to release a version for developing on, Joe. Also, a new release of src2pkg shuld be out this weekend -just in time to help Santa with some of his packaing needs LOL.

[pakt]

Ok, I've got the kernel source tgz down to 122MB

I trimmed off all branches from /arch except x86, the /Documentaion branch and all object (.o) files.

I also made a 99MB sfs file from the trimmed source but discovered I forgot to add the links in doinst.sh. I think I can add the links manually ... hmm, probably need to use chroot...

Anyway, I'll report back once I've tested the sfs.

EDIT: Seems I need to leave branch i386 on /arch so I've put it back.

Didn't need chroot to make links, just made relative links with rox.

[pakt]

The 99MB kernel-source sfs works with my frugal install . Now to try it out.

The sis7019 module might be a good choice. I think I saw somewhere how to compile a single kernel module but googling didn't help.

Well, seem to have made an object file:

Code: Select all

# make sound/pci/sis7019.ko
  CHK     include/linux/version.h
  CHK     include/linux/utsrelease.h
  GEN     include/linux/bounds.h
  CC      arch/x86/kernel/asm-offsets.s
  GEN     include/asm/asm-offsets.h
  CALL    scripts/checksyscalls.sh
  CC      scripts/mod/empty.o
  MKELF   scripts/mod/elfconfig.h
  HOSTCC  scripts/mod/file2alias.o
  HOSTCC  scripts/mod/modpost.o
  HOSTCC  scripts/mod/sumversion.o
  HOSTLD  scripts/mod/modpost
  CC      sound/pci/sis7019.o
include/asm/io_32.h: In function 'memcpy_fromio':
include/asm/io_32.h:151: warning: passing argument 2 of '__memcpy' discards qualifiers from pointer target type
include/asm/io_32.h: In function 'memcpy_toio':
include/asm/io_32.h:157: warning: passing argument 1 of '__memcpy' discards qualifiers from pointer target type
  MODPOST 0 modules
#

Not quite a module though. Do I know what I'm doing? Uh, no

[amigo]

You need to be using clusty.com instead of google.com -search 'compile single kernel module' --first hit:
http://www.debian-administration.org/ar ... nel_module

# compile
make -M=Path/To/Module
# test
insmod Path/To/Module/Module.ko

[pakt]

Thanks amigo, but that doesn't seem to work:

# make -M=sound/pci/sis7019.ko
make: invalid option -- M
make: invalid option -- =
Usage: make [options] [target] ...
<snip>

I decided to start fresh and generally follow Barry's instructions http://puppylinux.com/development/compilekernel.htm and just compile all the modules.

Unfortunately, I couldn't find a .config file in /usr/src/linux-2.6.27.7/ so I don't think I can compile either the kernel or drivers.

Maybe Joe has the .config file for SlaxerPup?

Paul

[big_bass]

Hey Paul
I been busy setting up a USB FLASH for compiling with kernel sources

the config is here

Code: Select all

geany /usr/src/linux-2.6.27.7/.config

or if you don't have the kernel sources installed you can check here too

Code: Select all

rox -s /proc/config.gz 

*I'll keep at it but this week I have less free time
but now you have the tools to compile and others so
more help on the way

manual ebox
http://www.compactpc.com.tw/files/eBOX_ ... 20v0r0.pdf

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


*I verified it with amigos post below it is activated


Joe

[amigo]

zcat /proc/config.gz > .config
Then: 'make silentoldconfig'
Then: 'make menuconfig' and drill down to where the options for that module are to be sure it is turned on and set any available options. Save configuration when exiting menuconfig and you should be set.

[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