Puppy Linux Discussion Forum

[techtype]

[MU]

I read at bottom here about problems caused by a network card driver:
Link

[techtype]

-Loaded Modules-

sky2 : Marvell Yukon 2 Gigabit Ethernet driver

/lib/modules/2.6.28.5/kernel/drivers/net/sky2.ko

Aragon mentions in his thread that he just renamed his firmware folder.

[aragon]

[MU]

Thanks Aragon, very important hint!

Techtype, sky2.ko itself seems to use no firmware.
Maybe one of the other modules needs firmware.
You could try to run without savefile.
Then click on the old ultrapup 1.0 pup_411.sfs to mount it.
Then copy the old /lib/firmware from the mounted sfs to the "real" /lib/firmware.
Then run the network wizard to set up the network card.

Mark

[techtype]

[playdayz]

I have grabbed both of the 2.6.29 kernels to play with. As we go forward here is one or two thoughts. I hasn't hurt me at all that NYP has a different kernel than Puppy4. I do like to have an updated kernel more often than the kernel for Puppy 4 was updated (never); that is not a criticism--puppy4 worked well for me, but I do like more frequent updates--not constantly necessarily, but well tested and reliable updates. I also prefer to have the latest versions of software; again, not a criticism of puppy4 which worked wonderfully for me and I do understand choosing a stable older version over a buggy new version, but what I really prefer is a stable new version . thanks.

[MU]

playdayz,

yes, but you always must compare advantages/disadvantages.

Kernel 2.6.15.16 meanwihle has a lot of additional modules, so more older hardware might be supported better.
And it supports closed source drivers, that were dropped in newer kernels.
So it is very important, to have a Puppy, that still uses it.

Concerning 2.6.29.1, I see mainly disadvantages.
- no squashfs lzma compression (acceptable)
- incompatible to older squashfs (acceptable)
- Ati drivers require ugly patches, reports in other forums say, those drivers now work less reliable (showstopper)
- no support for the reliable "aufs" unionfs driver (showstopper)

As this thread did not solve yet any of the open bugs for NYP with kernel 2.6.28.5, I think, I will stay with that 2.6.28.5 for now. It has more advantages for our system based on a layered filesystem.

Once lzma and aufs work, I will test again to switch to a newer one.
Reports speculate, that 2.6.30 might have inbuilt lzma support.

Mark

[aragon]

playdayz,

to give you also a little answer on my point of view:

1. All things MU wrote about the disadvantages of 2.6.29.1 are correct in my eyes, especially when it comes to a point of an 'official' release or at least a non experimental release.

2. For my release i could say, that it's a testbed / an experiment. It has a more 'fixed' state. I just picked up 2.6.29.1, as Barry did this actually for woof. i wanted to collect experience about kernel-configuration / optimisation. This may / may not help to build a modern / optimised kernel (maybe with 2.6.28.5) for a future official or non-official release.

3. Yes, a stable actual version is the goal. And a little less conservative kernel-config (my opinion).

aragon

[tlchost]

[techtype]

[playdayz]

@ MU, Aragon

Thanks for the theory guys. I was not agitating for 2.6.29, only saying that it was not necessary imo to have the same kernel as Puppy main official release. 2.6.28.5 is working splendidly for me right now in NYPrc10. Am I right that it wouldn't matter if they were the same number, because they would be configured differently and so modules would not be interchangeable anyway??? If things would be interchangeable would that be a reason to use the same kernel version?

[playdayz]

@ MU, Aragon

Thanks for the theory guys. I was not agitating for 2.6.29, only saying that it was not necessary imo to have the same kernel as Puppy main official release. 2.6.28.5 is working splendidly for me right now in NYPrc10.

[Béèm]

Having seen the 2.6.29.1 kernel announcement, I had good hopes, but apparently wow based distro's are incompatible with my Medion MD8818 PC. No joy thus.

I booted with loglevel=7 and I am again stuck at the same point as other wow distro's.

[aragon]