(old)Puppy Linux Discussion Forum

Yes it is intel video.
I believe the network card is Atheros AR9565
It uses ath9k in slacko 5.7.0 but ath9k doesn't do any thing for it in lxpup14

peebee wrote:

Mark_C wrote:I wanted to use lxpup14 but its kernel is to old to work for my network card.
So I used unicornpup which does work with my network card and followed the directions in the first post.
Everything was looking good on boot until it tried to start x which it couldn't do, I ran xorgwizard and it finds the right resolution but x still doesn't start.

Now both lxpup 14 and unicornpup boot no problem and x starts without a problem in their original form.
I even tried deleting etc/x11 and replacing it with the one from unicorn but still x doesn't start.
Hoping someone has an idea what the problem could be.


Mark

Maybe try LxPupUnicorn15.02:
http://lx-pup.weebly.com/upup-unicorn.html

Does that version use the gslapt package manager?

I just started reading this thread, and am very surprized this is not a sticky. Considering the current 2015 state of all things Puppy, I'll ask for this thrread to be made sticky.

TIA

Mark_C wrote: Maybe try LxPupUnicorn15.02:
http://lx-pup.weebly.com/upup-unicorn.html

Does that version use the gslapt package manager?

Sorry - no.

peebee wrote:

Mark_C wrote: Maybe try LxPupUnicorn15.02:
http://lx-pup.weebly.com/upup-unicorn.html

Does that version use the gslapt package manager?

Sorry - no.

I decided to try again using slacko 5.7.0 pae and it worked this time, posting from it now.
I have been curious about this version he made it seems pretty innovative.
Thank you for your replies.

Hi,

subject: switch kernels to Puppies with separate zdrv_xxx.sfs

Just to know if someone has succedeed in trying to perform jrb's method, detailed in page one this thread, and applying it to later puppies isos coming with separate zdrv_xxx.sfs files, and to puppies having only one main sfs file.

I'm here trying-struggling to switch kernels between puppy_wheezy_3.5.2.11-SCSI.iso which comes with one main sfs file, and, e.g. Pupjibaro_wheezy_JWM_1.0.6_22032015.iso; and getting no-success message like "...kernel panic..." and so on...

For sure i'm cutting and trying from reading postsrelevant to this matter; and am still ignorant about how to built a working puppy; so am i asking for help.

Thanks for any answer
Charlie

Perhaps its the naming of the zdrv that needs looking at.

I just booted the retro tahr kernel on lucid ok... used the new kernel and named the zdrv to match and placed it next to the main sfs.

There is usually some naming convention needed to match the initrds wants....

Of course this all may fail if the kernel you want does not have the initrd drivers built in since it will be unable to load anything....that requires the matching initrd as well.

mike

charlie6 wrote:Hi,

subject: switch kernels to Puppies with separate zdrv_xxx.sfs

Just to know if someone has succedeed in trying to perform jrb's method, detailed in page one this thread, and applying it to later puppies isos coming with separate zdrv_xxx.sfs files, and to puppies having only one main sfs file.

I'm here trying-struggling to switch kernels between puppy_wheezy_3.5.2.11-SCSI.iso which comes with one main sfs file, and, e.g. Pupjibaro_wheezy_JWM_1.0.6_22032015.iso; and getting no-success message like "...kernel panic..." and so on...

For sure i'm cutting and trying from reading postsrelevant to this matter; and am still ignorant about how to built a working puppy; so am i asking for help.

Thanks for any answer
Charlie

I've built a zdrv with just the kernel and firmware from puppy_wheezy_3.5.2.11.sfs and along with its initrd.gz and vmlinuz have managed to boot Pupjibaro_wheezy_JWM_1.0.6_22032015. I didn't check it too thoroughly but it appears to be working OK. The problem comes when I create a savefile and reboot, X won't start. I don't really have the time to dig deep into this but here's what I did:
1. get the initrd.gz from puppy_wheezy and open it up for editing (click on it). Replace /etc/DISTRO_SPECS with the one from Pupjibaro.
2. place the modified initrd.gz and the vmlinuz from puppy_wheezy in your directory. along with pupjibaro_wheezy_1.0.6.sfs.
3, mount zdrv_wheezy_1.0.6.sfs from Pupjibaro and use it as your guide. Open puppy_wheezy_3.5.2.11.sfs for editing and delete out everything that isn't in zdrv_wheezy_1.0.6.sfs. I also copied in the /boot folder from zdrv_wheezy_1.0.6.sfs, who knows? Now save as zdrv_wheezy_1.0.6.sfs and try rebooting.
Did that make sense? Anyway Good Luck! Hope it works for you.

Cheers, J

PS - If you want I can upload the initrd.gz and zdrv files for you, but like I say, It doesn't want to run from a savefile.

Hi jrb,
many thanks for your answer,

Sorry if I might have been unclear:
My purpose is to use a latest kernel (e.g. 3.17.7 from Pupjibaro, or gfrom Tahr-6.0.2) in puppy_wheezy_3.5.2.11.

I could get a booting wheezy_3.5.2.11 after copying /lib/modules, /lib/firmware, /etc/modules /etc/DISTROSPECS from Pupjibaros main.sfs and zdrv_1.0.6.sfs; along with using Pupjibaros vmlinuz and initrd.gz; BUT with the mouse cursor and keyboard not functionnal nor even recognizes...

I haven't edited initrd.gz (don't know if necessary)

Cheers, Charlie

I haven't edited initrd.gz (don't know if necessary)

those kernels you mention appear to have initrd drivers built in.

Again with the save could be a naming convention.... I assume save files are not using any weird tagging system.

Cannot think of another reason off hand ... only things i find are driver related eg matching alsa and nfs ..scripts are scripts.

Again probably of no connection but recent 3 kernels will not find the puppy files on a P3 machine EVEN THOUGH from the initrd I can mount drives and see them with ls from the initrd console. Cannot fathom that one either.

Kernel devs do move things around in /proc, /sys and /dev ..if any script or binary is relying on that then it will be affected (explains the alsa and NFS ...expected behaviour)

mike

charlie6 wrote:Hi jrb,

Sorry if I might have been unclear:
My purpose is to use a latest kernel (e.g. 3.17.7 from Pupjibaro, or gfrom Tahr-6.0.2) in puppy_wheezy_3.5.2.11.

Cheers, Charlie

I'm glad that's what you want. Turns out it's really easy.
1. Place initrd.gz, vmlinuz and zdrv_wheezy_1.0.6.sfs from Pupjibaro in your folder. Rename "zdrv_wheezy_1.0.6.sfs" to "adrv_wheezy_1.0.6.sfs".
2. Place "puppy_wheezy_3.5.2.11.sfs" in the folder and rename it to "pupjibaro_wheezy_1.0.6.sfs".

Reboot and its a done deal. Works with savefile and gives me my favorite resolution which puppy_wheezy never did. Posting from it right now.

Cheers, J

The above technique worked so well and was so easy, I just tried it on Racy-5.5. Posting from it now.

@J and @mike,
Hi ,

@J,
wow ! that so easy ! thanks a lot for that tip !

Success here on applying what you described in yout post !

Having had some reading in BK's literature about PuppyLinux, would the adrv_xxx.sfs have precedence on zdrv_xxx.sfs, and therefore the drivers in the main.sfs are ignored during the bootup, wouldn't it?

@mike,
good to know a bit more about recent kernels

Again many thanks for your time !
Bets regards,
Charlie

charlie6 wrote:Having had some reading in BK's literature about PuppyLinux, would the adrv_xxx.sfs have precedence on zdrv_xxx.sfs, and therefore the drivers in the main.sfs are ignored during the bootup, wouldn't it?

Yes, in Puppy the adrv.sfs loads first, then the puppy.sfs and then the zdrv.sfs. The first loaded takes precedence over the later ones and so on. By loading the kernel first it covered over any conflicts in the puppy.sfs. I was surprised that it named the savefile properly but /etc/DISTROSPECS seems to have been carried over from the initrd.gz and specified the correct name.

I'm very glad you posted this topic , it wouldn't have occurred to me otherwise.

The drivers in the main would be ignored as they are in a different folder under the version number.

firmware and other stuff like module configs and bootmanagers on the other hand may be affected by the upsidown layering of standard puppies... adrv was added to do at least one layer properly i believe

distrospecs copied from initrd does ring a bell.

mike

Hi mike,

mikeb wrote:...
firmware and other stuff like module configs and bootmanagers on the other hand may be affected by the upsidown layering of standard puppies... adrv was added to do at least one layer properly i believe

mikeb wrote:...
distrospecs copied from initrd does ring a bell.

Then, are there some mysfunctioning to be awaited
Cheers,
Charlie

Then, are there some mysfunctioning to be awaited

in your case sounds like its fine... just mentioned the reasons why this may not work out and ways to fix really for others....

sorry to confuse

mike

Hi

Reading through this thread i see no mention regarding compiling in these new frankenpup's, which leaves me asking a few questions.

Those questions are:
Does one need to make any changes to the devx, and if so, then what would those changes be

Also, am i correct in assuming that one would have to use the kernel sources from the donor Puppy

Maybe i'm not thinking this through properly, but i just had to ask.

CatDude
.

translated french traduction française tarhpup procedure

Hi All,

Picking up on CatDude's above inquiry, I would think that the Pup version which provided the vmlinuz & zdrv is the one whose devx would be used in compiling. I've refrained from referring to it as "donor". I have a problem conceptualizing which of the two Pups should bear that name. Both are donating something.

As I see it, the END-PUP, in Charlie6's situation, is pretty much Pupjibaro_wheezy_1.0.6 wearing puppy_wheezy_3.5.2.11's clothing.

Maybe referring to them as "the base pup" --in the above case Pupjibaro-- and the outfitter --wheezy-- would be easier to remember.

I suspect that the employment of a more modular design in Puppy builds since this tread first started is the reason jrb's last technique became possible.

The following seem to be logical conclusions. Just some thoughts. The "real world" isn't always logical. Please feel free to "flesh-out" or correct any:

(a) The zdrv_xxx.sfs from Wheezy_3.5.2.11 serves no useful purpose: firmware is being provided by Pupjibaro's zdrv. If so, Wheezy's firmware/zdrv.sfs can be discarded.

(b) If the ISO's of either or both Pups being used to build an END-PUP lacks a zdrv, simply remaster to create it/them before combining the desired parts. I've used the term "simply" because in this instance all that would be required is to boot a Pup to which no changes were made, and accept all defaults except to select having a zdrv.

(c) A remaster of the END-PUP, should be able to "convert" its current "adrv" into the remastered Pup's zdrv if the unused zdrv was discarded.

More Important than my ramblings above:

Employing the terminology I used above, I just "outfitted" azami's Vividpup 4.0.1 PAE, http://murga-linux.com/puppy/viewtopic. ... 738#847738 with tahrpup 6.0.2's applications. Working my way thru the menu to see what works, and for any problems, everything I tried seemed to work, although there were occasional references to tahrpup, such as to a tahrpup SaveFile when, in fact, it had correctly created a vivid_SaveFile.
A significant problem, however, is that although this is essentially a vividpup, ppm points to tahrpup's repo, and ubuntu's trusty tahr repos rather than VividVervet and VividPup's repos. What's a simple way to correct this?

Perhaps better --as many apps created for TrustyTahr/Tahrpup may function in Vivid Vervet/VividPup, and vice-versa-- didn't RSH/LazyPuppy create an app making it easy to add repositories?

mikesLr