tahrpup 6.0.5 CE

[pemasu]

http://www.murga-linux.com/puppy/viewto ... 022#610022

http://208.109.22.214/puppy/viewtopic.p ... 9cd#615063

gyro is onto something with this built-in versus module saga...

[rcrsn51]

Never having compiled a kernel, I am curious about how this works. Do Puppy builders use a standard DOTconfig out of Woof? Or do they pick-and-choose their own configuration? How did Slacko come to have hid-logitech-dj built-in but Tahr does not?

[gyro]

Never having compiled a kernel, I am curious about how this works. Do Puppy builders use a standard DOTconfig out of Woof? Or do they pick-and-choose their own configuration? How did Slacko come to have hid-logitech-dj built-in but Tahr does not?

The short answer is they can pick-and-choose.
Every person who compiles a kernel is given ample opportunity to modify the DOTconfig file to suit their own purposes. Although there are a number of predefined examples in woof that can be used as a starting point, or an existing DOTconfig file can be used as a starting point.
So, I copied "/etc/modules/DOTconfig-3.14.20-091014" from my running tahrpup and then changed just the single line.

gyro

[666philb]

i basically took the DOTconfig from the example 'HUGE' kernel that 01micko uploaded to ibiblio. missing config lines were added as they were found in tahrpups development phase and are on going. (using the kernel kit in woof.C.E)

chromebook touchpads are now working i believe with the 3.17.7 kernel

i'll test gyros & mavrothals fixes when i get back to my desktop.

next thing to try and fix is via chipset graphic drivers..... any ideas pemasu

[gyro]

When I use the kernel-kit from woof-ce to compile a new tahrpup kernel, my vmlinuz seems ok, but my zdrv is significantly larger than the one in the iso.
On comparing the contents of the 2 zdrv's, my "modules" directory looks ok, but the "firmware" directory is rather different. Mine's got more, but it's also missing some.
How can I end up with a zdrv that contains the same firmware collection as the one in the iso?
Can I just ignore the "firmware" directory produced by "build.sh" and replace it with the "firmware" directory from the iso zdrv?

gyro

[666philb]

with the kernel kit ... once the kernel is compiled it asks you whether you want the 'big' or 'cut' firmware package , then grabs it from here http://ftp.nluug.nl/ibiblio/distributio ... /firmware/ (i think you can miss that if you have accidentally pressed an extra 'enter' earlier)

i probably used the 'cut' package (can't remember) for the 3.14.20 kernels

[yerc1]

chromebook touchpads are now working i believe with the 3.17.7 kernel

hey 666philb,

Thanks for tahr 6 and congratulations for it getting a 10/10 score in Linux Format review!

I confirm that toshiba chromebook cb30 touchpad now works with the 3.17.7 kernel. But as I posted (7 or so posts before), there seems to be no touchpad right-click option and later I found touchpad scrolling seems missing too.

The synclient gives the message "synaptics driver not loaded" or something like that, hence I have not found a way to configure the touchpad.

Is there anything I can try to enable right-click and scrolling for the touchpad?

[gyro]

i probably used the 'cut' package (can't remember) for the 3.14.20 kernels

That makes sense, I just downloaded the the 'cut' version and it's contents match the 'firmware' in the iso zdrv.
I chose 'big'. I'll do it again a chose 'cut' this time.

Thanks.

gyro

[mavrothal]

Never having compiled a kernel, I am curious about how this works. Do Puppy builders use a standard DOTconfig out of Woof?

Kernel building is fairly simple (!) because everything is menu driven, with a very good inline help/explanation and error checking.
Configuring your kernel though takes a lot of reading and trial and error to know what to include and what to omit. If properly done, for a specific hardware can be ~80% smaller than a "standard" kernel, which tries to cover all/most hardware combinations (to give you a sense in the XO kernels - the first thing I build even before I could understand bash well - vmlinuz and modules, is 3.5 MB).

However, none of these can solve the OOB problems that a puppy user with some specific hardware, can have.
I would think that the simplest "solution" with the current "huge"-kernel implementation, is to keep building in modules as problems arise/reported.
Hopefully will not grow too much (though there are are ~50 HID modules...).

[gyro]

i probably used the 'cut' package (can't remember) for the 3.14.20 kernels

Yes, when I recompiled k.3.14.20 and chose 'cut', I ended up with a zdrv that looks a lot more like the zdrv in the iso.
It's actually a little smaller since I added "-b 512K" to the mksquashfs command.

gyro

[gyro]

I would think that the simplest "solution" with the current "huge"-kernel implementation, is to keep building in modules as problems arise/reported.

Kind of poetic justice, making use of the thing that caused the problem, to fix the problem.

gyro

[futwerk]

new backgrounds.

[Pelo]

I appreciate a lot polarpup QT (remasterized kernel 3.0.25 for wireless connection with my laptop)
Tahrpup seems to have everything needed for use of QT Apps.
tested OK
association suscribers for my soccer players in FC Nord 17 team
Lyx advanced text maker for scientist puppy . As i am not concerned, i was just to test. It's ok in first steps.Scientists would go further.
Chocolate if for spanish restaurants as spanish spoken. Latin language is easy for french speaking people. Not sure britannic citizen could read the menu of this restaurant. Chocolate won't help you for cooking, but for billing
Gramps not yet tested. Gramps is to register people died (but you can register alive people too) and their relationship (official or not).
Tahrpup bugs are listed in the forum. No need to list them in french one, i was idiot doing that. They are few.
pAVrecord runs well (don't forget activate retrovol for capture and micro).

[mavrothal]

I would think that the simplest "solution" with the current "huge"-kernel implementation, is to keep building in modules as problems arise/reported.

Kind of poetic justice, making use of the thing that caused the problem, to fix the problem.

OK then,... here is a script for the less seasoned user that will automate the initrd modification using this init script, so it will load the zdrv, insert any needed modules before savefile/folder selection and unload everything before switching root.
Just download the attached script expand it, make it executable (if not) and run it from terminal (or just click on it but you'll not be able to see any errors, if there).

The original initrd.gz will be renamed to "initrd.gz.orig" so you can always delete the new one and reinstate the old one to its original glory.
A frugal install on an ext2-4 or vfat filesystem and an active internet connection is required for the script to work but not much more than that.

Make sure that you run this script from within the puppy you want to modify as it is designed to modify the initrd.gz of the currently running puppy.

[gyro]

I would think that the simplest "solution" with the current "huge"-kernel implementation, is to keep building in modules as problems arise/reported.

Kind of poetic justice, making use of the thing that caused the problem, to fix the problem.

OK then,... here is a script for the less seasoned user that will automate the initrd modification using this init script, so it will load the zdrv, insert any needed modules before savefile/folder selection and unload everything before switching root.

Sorry, I did not read this clearly.
What I am suggesting is that we don't patch the 'init' script, but rather recompile the kernel to change any missing module to be built-in to the kernel, every time someone reports a missing module. Since it is so easy to modify puppy to use a new kernel now.

gyro

[mavrothal]

Sorry, I did not read this clearly.
What I am suggesting is that we don't patch the 'init' script, but rather recompile the kernel to change any missing module to be built-in to the kernel, every time someone reports a missing module. Since it is so easy to modify puppy to use a new kernel now.

Oh well, is done now.
See it as an added test to verify that some missing module is the problem.
Besides, replacing/rebuilding the kernel might not be everyone's cup of tee.

[caiosama]

Hi!

Im using Puppy since 2013, with the Pupijbaro remaster in an old Dell (live usb), and Precise 5.7.1 (full) in an old (but like new) Asus EEEpc 701, (1GB RAM) it works beautiful.

Suddenly, Frisbee was broken , and i cannot longer anymore connect to my wifi. I decide to give a chance to the new Tharpup 6.0 Non PAE, full instalation too, and it works beautiful. I have installed Conky, Tint2, Libreoffice and some of my favorite pets without troubles, but i have two questions:

- The video driver im using now is the modesetting. The Precise (non Retro) recognize my old Intel GMA. Can i install the correct drivers in this Tharpup?

- I suggest to add to the Quickpet, the GTK Youtube Viewer, great app.

Cheers from Chile to all the Puppy Team, you rock!

[gyro]

Besides, replacing/rebuilding the kernel might not be everyone's cup of tee.

I thought that the whole point of the new kernel method was to make it very easy to install a different kernel.
And the maintainer should be able to easily provide a new kernel for download by those who have the problem. Just change an 'm' to a 'y' in the DOTconfig file.
(Oh, an then have a cup of tea, while the kernel is compiled.)

gyro

[smokey01]

I've been using tahrpup-6.0 for a couple of weeks now and I must say I'm quite impressed with it's responsiveness and choice of apps. For the few that I like that are not included or are not in the PPM I have put them on my site here.
Well done team.

[bigpup]

Hi!
The video driver im using now is the modesetting. The Precise (non Retro) recognize my old Intel GMA. Can i install the correct drivers in this Tharpup?

You probably are using the correct Intel driver.
The modesetting is something required with the newer Linux kernels.

To see what driver is being used.
Go to menu->System->Pup-Sysinfo->Devices->Display->Summary