TXZ_pup 4.5

[01micko]

mavrothal... possibly because TXZ is using squash3.. just a stab in the dark

________________________________________________________________

Joe

I'm attempting to stay in the loop so to speak, and when I can offer you something that may be an improvement..(or not!) I will.

Barry has a new network tray applet, simply named 'network_tray'. It works very well on TXZ (It is one of the few in my menu.lst ) The applet is a very capable replacement for Blinky and then some. I have hacked the source and packaged but I will also upload the source so , if you wish, you can compile for TXZ. The beauty is that the icon is themable, useless eycandy maybe, but cheap . It has more features, but you may have to investigate those yourself, if interested.

See attached.

Cheers, Mick

[big_bass]

As the tile says, I'm trying to unsquash the TXZ_Pup up_450.sfs on my Mac and I get "Can't find a SQUASHFS superblock on pup_450.sfs"
Any other pupplet I tried unsquashed fine so far.
I did download a couple of times just in case, and the md5 was fine both times.
Any insight?

Hey mavrothal
squashfs is a sensitive thing

so I packaged you up the correct squashfs for TXZ pup which is 3.4
(I am the only one using that here in the forum)

*and I added squash 4 that will uncompress the latest lzm format as a bonus

if you got this error
Can't find a SQUASHFS superblock on /root/pup_450.sfs
#

install the package then (I did a simple tar.gz so you could use it on your Mac)

Code: Select all

unsquashfs3.4 /mnt/hdc/pup_450.sfs

here are two examples this is for TXZ

Code: Select all

unsquashfs3.4 /root/pup_450.sfs

a bonus !
this is for the latest files that are squashed 4 with lzm if you work with any live cd slackware based

Code: Select all

unsquashfs4+ /root/etc.lzm

I used the 4+ so that if you have a puppy 4 you wont confuse them
Joe

[big_bass]

Hey Mick

thanks for helping

I will check it out!



I have been working on something really cool and things are moving a thousand
miles an hour in the direction I want it to go

and that is to have a live cd independent build system that can be built
without any dependencies to any puppy scripts or apps or root skeleton /sfs files
this way everything is easily repeatable when a new version comes out
since its based on an already working system

100% distro/binary compatible with debian or arch or ,slackware
and keeping up to date with the major players

and not losing the speed or small size (or my sanity )

Joe

[gerry]

erm..... will it still be Puppy? Sounds like JOS, Joe's Operating System.

gerry

[Mobeus]

..without any dependencies to any puppy scripts or apps or root skeleton /sfs files

100% distro/binary compatible with debian or arch or ,slackware
and keeping up to date with the major players

OK, now you REALLY have my interest! Will the builds be capable of a frugal install, or will it be ..? Will it….

Ah so many questions, but I will try to be patient and wait for your announcement. This sounds great!

Regards,
Mobeus

[Aitch]

Thanks for the reply, Joe

I'm following your progress with interest

Aitch

[mavrothal]

so I packaged you up the correct squashfs for TXZ pup which is 3.4

Joe

thanks Joe.

However, I find neither geode nor openchrome video drivers in TXZ...

[dinosoep]

wifi doesn't work on my lattitude E5500
I think it has an intel 5100 wireless card(if that makes sense XD)
I don't think the driver isn't listed and as I am a linux starter, could you please explain how to get it working?
it doesnt detect my wlan0 and with eth0 it gives 'unknown interface' or something like that

[big_bass]

erm..... will it still be Puppy? Sounds like JOS, Joe's Operating System.

I am working on using updated linux live scripts they are used to make live cd's
no it wont be "puppy" this works for all major distros


it will be all that I wanted to do for puppy but couldnt as is

it allows total flexibility thats how most of the live cd's are made on distrowatch
then modified for the special flavor

some of the things I have done on the puppy forum
fat free pup ( a light stripped down puppy base )
slaxer pup ( taking puppy 4.12 to a new frontier with a slackware kernel) and keeping it up to date

and TXZ pup (building the whole thing with its own packages and package management and first to have removable core apps )

TXZ pup will gain many good things because of the things I will learn from building
even another way


**if you want to see my progress I´ll post stuff here so I dont mix the work Im doing there with TXZ pup (building stuff takes time and testing too ) but you can get a better idea
scan down to post 164 can you see the difference how the feedback is
with some one using slackware ,debian and arch

http://www.linuxquestions.org/questions ... age11.html

http://www.linuxquestions.org/questions ... age12.html



Joe

[gcmartin]

LiveCD/LiveDVD. Sound like something I'm interested in. An OS independent of the data drive. I will stay tune to this.

Does your work address any of this LiveDVD./LiveCD processing at boot time....or does your work involve processing after desktop presentation on-screen?

Does anyone know

• if the "proper" place for Puppy to find the SFSs at boot time is suppose to be in a /mnt/home folder on the LiveCD or
• in a /mnt/home folder within the main PUP-nnn.sfs on the LiveCD?

This clarification may be all that is needed for the boot operation to be successful with the functionality that Mariner provides.

Just trying to place Mariner's SFSs in the proper place for Puppy boot. I'm sure I am missing something, though.

Dropping the add-ons into /mnt/home in the ISO won't do the trick. To my knowledge, Puppy is not designed for extra SFS files at first boot. Exactly why I'm not sure. I do know the layers are set up at boot time, well before X and GUI dialogs like BootManager become available. Barry K, Pizzasgood or MU would have a more complete picture as they have been more involved with Puppy's design--and much longer than I. Technically, in Puppy and Lighthouse, /mnt/home is a symlink to /initrd/mnt/dev_save, and /mnt/home is not present at first boot. (The extra file system layers, one for each extra SFS also do not yet exist.) ... Hope that helps,
TazOC

Thanks in advance.

[maxpro4u]

I am having a problem with the sound. I just hear static. On puppy 4+5 I needed to add this to rc.local to make the sound work
rmmod snd-es18xx
sleep 1
modprobe snd-es18xx isapnp=0 irq=5 dma1=1
sleep 1
modprobe snd-es18xx isapnp=0 irq=5 dma1=1 dma2=5
modprobe evdev

and set the boot to pnpbios=off, but it did not work for txz. What do I need to do? It is an onboard sound on the laptop in my sig.

[big_bass]

the driver is there in the kernel it is just a matter of getting it loaded correctly

/lib/modules/2.6.27.7/kernel/sound/isa/snd-es18xx.ko:
/lib/modules/2.6.27.7/kernel/sound/core/snd-pcm.ko
/lib/modules/2.6.27.7/kernel/sound/core/snd-page-alloc.ko
/lib/modules/2.6.27.7/kernel/sound/drivers/opl3/snd-opl3-lib.ko
/lib/modules/2.6.27.7/kernel/sound/core/snd-timer.ko
/lib/modules/2.6.27.7/kernel/sound/core/snd-hwdep.ko
/lib/modules/2.6.27.7/kernel/sound/drivers/mpu401/snd-mpu401-uart.ko
/lib/modules/2.6.27.7/kernel/sound/core/snd-rawmidi.ko
/lib/modules/2.6.27.7/kernel/sound/core/seq/snd-seq-device.ko
/lib/modules/2.6.27.7/kernel/sound/core/snd.ko
/lib/modules/2.6.27.7/kernel/sound/soundcore.ko

have to find you a fix confirmed to work

could you run this code and paste the output I want to see what is being used

Code: Select all

cat /proc/asound/cards

yourś should look "something like" this on a working system

cat /proc/asound/cards
0 [ES1869 ]: ES1869 - ESS AudioDrive ES1869
ESS AudioDrive ES1869 at 0x220, irq 5, dma1 1, dma2 5




mine is using this as an example

# cat /proc/asound/cards
0 [V8235 ]: VIA8233 - VIA 8235
VIA 8235 with ALC101 at 0xdc00, irq 5
1 [modem ]: VIA82XX-MODEM - VIA 82XX modem
VIA 82XX modem at 0xe000, irq 5
#



Joe

[maxpro4u]

yourś should look "something like" this on a working system

cat /proc/asound/cards
0 [ES1869 ]: ES1869 - ESS AudioDrive ES1869
ESS AudioDrive ES1869 at 0x220, irq 5, dma1 1, dma2 5

That is exactly what it said

0 [ES1869 ]: ES1869 - ESS AudioDrive ES1869
ESS AudioDrive ES1869 at 0x220, irq 5, dma1 1, dma2 5

[Newcrest]

I just had a play with this. The kernel seems quite good, it is the first and only Puppy related offering that seems to handle the fan and everything else properly on my laptop.

However,
1. The pfix=noram switch is broken in the init script. (I presume because it came from 4.2.1 where it is also broken).

2. Why the old version of pprocess rather than the newer one with easier killing of processes? What's more, why pprocess and no Htop when Htop is so much easier to read and more informative?

3. I can't find the xv driver for mplayer. X11 does not allow brightness/contrast adjustment. The other two drivers are unstable.

4. The fonts are small, fuzzy and hard to read.

Otherwise it seems quite promising.

[big_bass]

Hey Newcrest

I just had a play with this. The kernel seems quite good, it is the first and only Puppy related offering that seems to handle the fan and everything else properly on my laptop.

However,
1. The pfix=noram switch is broken in the init script. (I presume because it came from 4.2.1 where it is also broken).

it came from 4.12 but modified for the new kernel I didnt edit the noram option
so I'll have to check whats wrong there

2. Why the old version of pprocess rather than the newer one with easier killing of processes? What's more, why pprocess and no Htop when Htop is so much easier to read and more informative? the new version of pprocess didnt work so I went back to the older version I couldnt be bothered to hack at it but I did use ziberts other new programs where I could

3. I can't find the xv driver for mplayer. X11 does not allow brightness/contrast adjustment. The other two drivers are unstable.I dont remember compiling the xv driver in on that . mplayer is one of those programs that can take a long time to compile and set up everything to work perfectly I did however add in some nice skins and all was compiled from source on puppy

4. The fonts are small, fuzzy and hard to read.
yeah its all default I dislike playing with the browser settings because
when you get it you get the official version un modified more for the people
that dont like people messing with the original configurations (security )
you can customize it to your preference

Otherwise it seems quite promising.

thanks for the feedback I am working on updating the kernel and programs
and trying some other approaches to the live cd building

I like the way I built with TXZ packages and package tools and a different package management
all that work is re usable in linux (an investment in time )
I just need the live cd part to follow current distros
*without all the spaghetti and cheese something easy to modify the code

effortless change is when you change but its easy and better
since change is happening all the time around us
I dont need a ROM embedded operating system

Joe

[Cur Dog]

big_bass,

I borrowed the control panel from gposil's Dpup and packaged it up for TXZ-Pup.
This is the first package that I have done so I am not sure that it is all correct.
I know that you are a busy man but if you take a look and see something that i didn't
do correct please let me know. I hope that it doesn't offend you that I done this because I am
just trying to get a basic understanding of a TXZ package.

One thing I couldn't figure out was how to place an icon to start the control panel on the desktop. I have a menu entry under system.

Cur Dog

hmmm......I didn't realize that the.txz would not attach. What to do, What to do????

[big_bass]

Hey Cur Dog

there's no way anyone could follow all the work done here in the forum
so if you got a package to work from dpup or another version

thats good news the idea behind linux is to make standardized code and packages so work could be shared

I would be happy to check out and test the package

I usually upload small stuff to the forum with as tar.gz

you can do some ugly cheat by renaming the .txz to
any one of these ace, bz2, gtar, gz, pet, pup, rar, tar, zip

I would rename .txz to .bz2 and just make a note to rename the file back to .txz after its down loaded

there is a size limit so if its big you could email it to me
big.bass.slaxer@gmail.com


some where in this thread I posted two scripts to make TXZ package building much easier one creates the slack-desc and the other makes the txz package
officially if you make a folder with a package name-version number first before you drag N drop

some people may think I am a bit of a rebel that just use puppy pet format
by using a TXZ package but think about this slackware set up the standard
simple package long before puppy came to be
so by sticking with an established format ( not my own )
packages are more "linux friendly"


Joe

[Cur Dog]

Ok big_bass here we go....
I looked back through the thread and found the tools that you shared and used them to create the package. That is some pretty nifty work you done there. Thanks again for all of your hard work.

Just change .bz2 to .txz

[big_bass]

Hey Cur Dog

I like it
I found the latest sources and compiled it
added a bunch of icons and re branded it for use with TXZ_pup



* dpup control panel is an app called tabble
that was modified for dpup the dpup control panel didnt have sources so
it was hard coded in "C" with dpup stuff as a bin I had to get the tabble sources to make it special for TXZ_pup


@gposil hasnt been around for a while but thanks if you do read this

special note : this was also tested on my slackware 13.1 box and the GUI works fine
the links just need to be made to the apps from the GUI hover over the selected item you want to edit
by holding down both the left and right mouse buttons at the same time to allow you to get a secret edit the menu


tabble_TXZ_pup
http://www.puppy2.org/slaxer/tabble_TXZ ... 3_SLXR.txz

[Cur Dog]

Thanks big_bass,

I removed my package and installed this one. Works great here.
I noticed that there were some holes between some of the icons so I cleaned that up in the .tabble file in the root folder. Just download and change the file name to .tabble and place in the root folder.

Thanks again,

Cur Dog