Wary 0.7 mix-n-match uploaded

This release of Wary is very interesting. You build your own Puppy with the kernel you want. Announcement page:

http://distro.ibiblio.org/pub/linux/distributions/quirky/wary-070-mix-n-match/mix-n-match-readme.htm

Download:

http://distro.ibiblio.org/pub/linux/distributions/quirky/wary-070-mix-n-match/

Note that the latest Woof (to be uploaded today) is required to be able to build a Puppy that allows mix-n-match.


Posted on 20 Sep 2010, 16:57


Comments:

Posted on 3 Sep 2010, 21:42 by BarryK
Wary 0.7 feedback
I have started a forum thread for feedback:

http://murga-linux.com/puppy/viewtopic.php?t=59514



Posted on 3 Sep 2010, 23:11 by Raffy
Next level
Kernel choice for users - this would allow problem-solving with a kernel change. Surely, this is the next-level Puppy.

Other than "reading the manual", is there a way to give a clue to a newbie about the better kernel for his hardware? (Stupid question:) Can some sort of kernel choice be implemented at first boot? OK, if not during the first boot, then in the second. :)



Posted on 4 Sep 2010, 4:23 by Steven P
ohci_hcd ssb issue
Hey Barry, I was wondering if you could start compiling your kernels with 'CONFIG_USB_OHCI_HCD_SSB=n'

This option is only needed to support a USB controller found in some embedded devices, but causes problems on certain laptops.

For example, my brother's laptop needs both the ohci_hcd and broadcom wl drivers, and setting 'CONFIG_USB_OHCI_HCD_SSB=y' causes the ohci_hcd driver to depend on ssb. The Broadcom driver doesn't seem to work if the ssb module is loaded, so on his laptop it is either no wireless or no usb. I can't get them both working at the same time.


Posted on 4 Sep 2010, 7:20 by jemimah
zdrv
I do something similar with mix and match kernels in Puppeee.

Zdrv works fine except for two things. During an upgrade, the main SFS gets copied down to disk, but not the zdrv. I patched the init script to fix that.

Also the zdrv is not found in Pupmode 6/7 without the aufs patch that would allow that to work.

You might want to put Technosaurus' Zdrv cutter into this new Wary.






Posted on 4 Sep 2010, 8:10 by BarryK
Re zdrv
I think that it must be already fixed in Woof, that is, zdrv copied into ram, as when I tested with a live-CD, after bootup it was not mounted.

Yes, I made the note in the readme file that the 2.6.30.5 kernel needs the latest aufs. And of course the patch.

Hmmm, I think that I will do that today. I will recompile the 2.6.30.5 kernel but leave all config options as-is, as there are many 3rd-party modules that I don't want to break. I just want to update aufs.

The 2.6.27.47 and 2.6.34.1 kernels do have the patched aufs, can't remember about the 2.6.33-git7 kernel -- just checked, no it doesn't.



Posted on 4 Sep 2010, 19:56 by ttuuxxx
Wary and Surfboard
Hi Barry I purchased a Surfboard http://www.murga-linux.com/puppy/viewtopic.php?t=59466 from http://www.xcore86.com/site/node/11I think its the same motherboard as the edubook which you did a version a couple of months back, The pc cpu is Xcore86 1Ghz, and has 512MB of memory, Wary should fly on it, But when its booted and your using Wary 0.6, its running veryyyyy slow. It takes about 1 minute for seamonkey to start and mplayer just crashes. Is there some extra driver I'm missing? I really would like to have Wary running very smooth on this nice looking pc. The info on the spec's the website gives is very minimal.
Thanks for your time
ttuuxxx


Posted on 4 Sep 2010, 20:09 by BarryK
Kernel 2.6.30.5 updated
I have updated the files with a recompiled 2.6.30.5 kernel:

http://distro.ibiblio.org/pub/linux/distributions/quirky/wary-070-mix-n-match/kernel-2.6.30.5-UPDATED_20100904/

I have also improved the README page:

http://distro.ibiblio.org/pub/linux/distributions/quirky/wary-070-mix-n-match/mix-n-match-readme.htm



Posted on 4 Sep 2010, 20:15 by BarryK
Re surfboard
The 2.6.33-git7 kernel works particularly nicely with the vortex86mx chip, see Wary 0.7 mix-n-match.

Even though the chip is rated at 1GHz, it is a very very slow CPU. You should get much better than 1 minute for SM to start though. Mplayer might be using a CPU instruction that is not in the vortex86mx chip. It might have to be especially compiled.