Puppia (Mageia) Puppy working on laptop

Running now on my laptop. I reported recently a dead keyboard/mouse on my laptop:
http://bkhome.org/blog/?viewDetailed=02328

And earlier reported Puppia working on a desktop PC:
http://bkhome.org/blog/?viewDetailed=02325

I am still in a situation where I have other activities and can only put in a couple of hours on Puppy development per day, that situation will continue a few more days. Anyway, there is progress. A little bit more testing and Puppia/Pupdrake should be ready for first release.

I have disabled hotplug support in X.org, using the older 'kbd' and 'mouse' drivers and hard-coded in xorg.conf. I have got auto-startup of X working nicely. Both auto-startup and the Xorg Wizard no longer have the entries for Synaptics (and similar) touchpads, as it breaks xorg.conf. Flsynclient should be able to work, as 01micko has reported, after being upgraded.

Later I will see if hotplugging can be turned on, and there are udev rules that are supposed to handle touchpads.

Note, 'devx' works fine.


Posted on 1 Jul 2011, 21:24


Comments:

Posted on 2 Jul 2011, 2:34 by Iguleder
Small suggestion
Barry, can you add a DISTRO_ARCH field in DISTRO_SPECS and change all the hardcoded "i386" (Debian, Ubuntu, etc') to $DISTRO_ARCH?

I built an x86_64 flavor of linux_kernel-2.6.32-42-lts (with BFS, my Puppy logo patch and everything) with IA32 emulation, using a Debian testing chroot environment with GCC 4.6.x, on a Fedora 13 x86_64 machine I have lying around. It worked great.

Now I'm running Lupu 5.2.5 with this kernel and it works flawlessly. It's simply amazing how good it is - about the same RAM usage but it feels snappier here and there ... or maybe it's just me.

Now I'm taking this to the next level - I'm trying to rebuild 5.2.5 for amd64 instead of i386. The first step is rebuilding it with that hardcoded "i386" replaced with "amd64" and adding a 32-bit glibc for compatibility. Things like gtkdialog won't work, so I think I'll recompile only the crucial stuff for 64-bit.

That DISTRO_ARCH field could ease the transition to 64-bit in future versions, that's what I'm trying to say. It won't do wonders, but it's a good start.


Posted on 2 Jul 2011, 7:02 by 01micko
great!
Ok, the xorg developments sound great. The only problem I see is that all the latest distros are moving to newer xorg versions and it kind of makes xorg wizard incompatible if events are disabled in your xorg complile. Is there any work around that you can think of for others without recompiling Xorg? I am aware you don't have heaps of time to spend on this, however some pets/packages/diff of the new Xorgwizard will be handy for me at least as I want to ship a new spup alpha this weekend if possible, and I have struggled a bit with Xorg. TIA.

In other developments, to save you a bit of forum scouring, gtkdialog is moving ahead in leaps and bounds. Dougal has started a development thread:
http://www.murga-linux.com/puppy/viewtopic.php?t=69188
There you will find a direct link to the new google code development page started by forum member thunor. There are a multitude of improvements including new widgets and many bugfixes all well documented. It's fun!
Cheers


Posted on 2 Jul 2011, 7:08 by BarryK
Re Xorg compile
01micko,
I only recompiled Xorg to experiment, I have now gone back to using the official Mageia xorg-server package.

Hotplugging is disabled by a line in xorg.conf. So can easily be turned back on.

I did have to recompile 'iptables' though. I don't know why the official iptables pkg reported missing shared libs -- that aren't even available in any package, which is weird.



Posted on 2 Jul 2011, 7:12 by BarryK
Re 64bit
Iguleder,
I'll consider that soon.

Check out kirk's Fatdog64, he compiled many common packages for 64-bit, you will find the PET's in his ibiblio repo:
http://distro.ibiblio.org/fatdog/pets/500/



Posted on 2 Jul 2011, 8:12 by BarryK
Puppia or Pupdrake
I narrowed it down to one of these. I also kind of like "pupeia" except for the pronunciation problem, although we could state the correct pronunciation, as pup-eia.

A quick vote guys, Puppia or Pupdrake?



Posted on 2 Jul 2011, 8:58 by 01micko
drake
that's my vote :)


Posted on 2 Jul 2011, 8:47 by SouthPaws1
Name
Might not someone refer to it (short hand) as P-pup if it were named Puppia or Pupdrake.

I still recommend M-Pup; Mandrake and Mageia can both be implied.


Posted on 2 Jul 2011, 12:16 by bigpup
Name
The standard for names lately seems to be what it was derived from first then Puppy.
Example:
Lucid Puppy
Spup
Macpup
Upup
Dpup

So, what about:
Magpup
Magdrake Puppy


Posted on 2 Jul 2011, 12:47 by adi
vote
magic-puppy


Posted on 2 Jul 2011, 17:09 by dawg
More P's? :)
Puppeia?
Wouldn't it seem like a logical derivation?

MaPuppia/Mapuppia? maybe not...too close to "Mac".

Wait, Madoggia! :D yeah, not "puppy" enough.

Popeyea! :) jk
Then again...



Posted on 2 Jul 2011, 18:04 by xman
μαγεία
Mageia (μαγεία) is something like 'magic' in english. So, why not, Magicpup.


Posted on 2 Jul 2011, 18:04 by xman
μαγεία
Mageia (μαγεία) is something like 'magic' in english. So, why not, Magicpup.


Posted on 3 Jul 2011, 8:12 by FeodorF
Re:Mageia
Mfork Puppy


Posted on 3 Jul 2011, 19:13 by Amélie
'pawpaw' than 'woofwoof'
I'd prefer the handy 'Puppia'. It combines Puppy, Mageia and on the whole the mental association to 'Papaya' (Carica papaya) in one word.


Posted on 3 Jul 2011, 24:06 by f00-
shortname
Drake is unambiguous. Plus it lends itself to a four-letter + version# identifier - it seems mnemonic-related single letter +version# is just stepping on each others toes at this point in growth. Good for all that the kernel id is major now as well. Yah, 2.6.34 drak 0.1 will do until she litters :)