Puppy Linux Discussion Forum

James C · Joined: 26 Mar 2009 Posts: 4768 Location: Kentucky

Manual frugal install of 002 on the main Linux box (Athlon XP).No problems....everything looking good. Smile

jim3630 · Joined: 13 Feb 2011 Posts: 792 Location: Northern Nevada

pemasu · Joined: 08 Jul 2009 Posts: 5174 Location: Finland

Jim3630. Yup, I tested that Universal Installer detects my partitions and that step was fine. I havent tried usb installing yet. But the detection was fine.

pemasu · Joined: 08 Jul 2009 Posts: 5174 Location: Finland

Thunor has investigated the Partview quit button problem and found the reason. It was glade bug and has been fixed. I wait for the next release of the code.

I will include it to the next Midnight Sun Pup, which will be 2.6.38.4 kernel with intel atom optimization with highmem+pae and has of course automatic process scheduler enabled.

pemasu · Joined: 08 Jul 2009 Posts: 5174 Location: Finland

Sfsget has been fixed in new woof. Great. Now I just have to start using that woof and make all the needed modifications. Or just grab the changed scripts to the previous woof, since downloading all the stuff is not reliable right now. Lets see.

Iguleder · Posted: Fri 01 Jul 2011, 05:38 Post_subject:

Hey pemasu, I'm doing a nice experiment you might be interested in.

At the moment I'm building a cross toolchain (i686 to x86_64) so I can build a x86_64 flavor of the awesome linux_kernel-2.6.32-42-lts.

I want to build a 32-bit Puppy with a 64-bit kernel, that's what the Tiny Core guys do and it works well for them - you get 64-bit math, 64-bit drivers, support for more than 4 GB of memory, and all this goodness without sacrificing compatibility.

Another interesting thing about this trick is the ability to run 64-bit stuff. Just think of it - you build a Debian chroot environment with debootstrap, which contains Debian's 64-bit GCC, then build all Puppy's 32-bit only packages for 64 and gain the ability to build an entirely 64-bit Puppy Very Happy

smokey01 · Joined: 30 Dec 2006 Posts: 1642 Location: South Australia

smokey01 · Joined: 30 Dec 2006 Posts: 1642 Location: South Australia

Ray MK · Joined: 05 Feb 2008 Posts: 681 Location: UK

More than interesting - can't wait.

Iguleder · Posted: Fri 01 Jul 2011, 12:38 Post_subject:

Wow, it worked out of the box! Built my famous 2.6.32-lts on a Debian testing chroot environment with GCC 4.6.x and it worked flawlessly!

About the same RAM usage, 4GB+ support, the ability to run 64-bit stuff and I think it also boots a 'lil bit faster Cool

EDIT: I took EZ-Woof, I'm trying to build an exact replica of 5.2.5, but for x86_64 (with a 32-bit glibc just for some traditional Puppy packages) and this wonderful kernel Smile

pemasu · Joined: 08 Jul 2009 Posts: 5174 Location: Finland

Iguleder. It sounds really great what you experimenting now. If I understood right, you have 64 bit kernel which 32 bit and 64 bit apps can utilize. I have to digest little longer before I truly understand what you have done.
2.6.32 kernel is unfortunately too old for my hw and newer comps and their devices also suffer that old kernel.
2.6.38 kernel would be nice. It has natively support for newer hw and also compiling missing stuff is quite easy.
With 2.6.32 there just isnt support for newer drivers anymore.
It sounds like I am making wishlist already, lol.
I volunteer to test your stuff, as always.

Lobster has hard time to keep up with your productivity to puppy linux community and change his sigu accordingly.

Cheers. Keep us informed in the future also....

Iguleder · Posted: Fri 01 Jul 2011, 15:10 Post_subject:

Let me explain this trick, so it becomes clearer: if you use a 64-bit kernel, you can use both 32-bit and 64-bit packages, as long as you have the required dependencies and zero conflicts between them.

If you want to use this for Midnight Sun, just take any 64-bit live distro, install GCC, Make and Perl. Then compile a kernel in the traditional Puppy way (except two changes - the .config and the bzImage path). I just took my configuration file and changed from x86 and i486 to x86_64 and generic optimizations, plus the IA32 emulation, which is needed for 32-bit compatibility. Then I ran my build script ... and that's it Very Happy

I think its better than a 32-bit, PAE-enabled kernel, since this is the real thing. Machines with 512MB - 1 GB of RAM can be 32-bit only, but those that have at least 1 GB should be 64-bit capable. You don't get the traditional PAE instability issues - only the good stuff 64-bit offers Smile

smokey01 · Joined: 30 Dec 2006 Posts: 1642 Location: South Australia

Iguleder · Posted: Sat 02 Jul 2011, 01:28 Post_subject:

Any kernel.

Very Happy

EDIT: btw, I noticed one problem, only one! When you attempt to compile stuff, uname reports you're running x86_64 while all userland is x86, so i686-something-linux-gnu is not seen as the compiler to use. To solve these problems: I moved /bin/uname to /bin/uname-orig and used this as /bin/uname:

pemasu · Joined: 08 Jul 2009 Posts: 5174 Location: Finland

Posting now from Midnight Sun Pup 003. I decided to download whole ubuntu packages during the night and I made inspection through libs. I shaved 3 Mb from the iso from not needed stuff I found. Remnants of my testing which I had left to the woof. Kernel is now 2.6.38-4 intel atom optimization with highmem+pae.
Gnome-mplayer and gecko-mediaplayer now version 1.04. Yad updated.
I will check the gtkdialog latest code if it works now with partview quit button. I suppose the fix is now in the repo now.
I will make the real uploadable version soon.
This uses the latest woof, so it will have Barrys latest woof scripts.