Fatdog64-630rc1 (16 Oct 2013) [CLOSED]

A home for all kinds of Puppy related projects
Message
Author
Scotchialoo
Posts: 50
Joined: Fri 25 Oct 2013, 14:58
Location: Poland
Contact:

#121 Post by Scotchialoo »

kirk wrote:
Also, If I don't respond to a post it usually means I have nothing of value to add, at least at the moment. So please don't take offense. Thanks to everyone for testing. The next RC will be in a couple weeks. In retrospect we probably should have called this release a beta because we've now decided to change quite a few things. The next release will have a 3.12.x kernel with squashfs parallel decompression patches and user namespaces enabled. Mesa-10 and new video drivers and some other things still in the works.
Oh yea... Thanks,I will be wait with a Next Release,but T2 is not updated...

http://svn.exactcode.de/ChangeLog-t2 [in 2013-06-18: glibc 2.13 -> glibc 2.17]

Because I want Switch to Chromium Waterfall instead of Stable Google chrome (29)... and Chromium Waterfall depend glibc 2.15 and In my Libraries is will be errors with glibc 2.18 -> http://www.murga-linux.com/puppy/viewtopic.php?t=90112 [even in glibc 2.16 with link description...]

laurentius77
Posts: 82
Joined: Wed 30 Mar 2011, 07:02

(solved) UEFI limitation

#122 Post by laurentius77 »

kirk wrote:
I get the error "not enough memory to load specified image".
Haven't had that. It's probably a kernel/boot loader/BIOS/UEFI limitation.
is there a way to create a barebone fd64?
Only by manually removing things and then recreating the sfs.

I have FD630 from aarnet.edu.au and I have Avidemux and default screen dpi is still at 78.
You have an old save file being used. Remove old save file or boot with savefile=none.


Also, If I don't respond to a post it usually means I have nothing of value to add, at least at the moment. So please don't take offense. Thanks to everyone for testing. The next RC will be in a couple weeks. In retrospect we probably should have called this release a beta because we've now decided to change quite a few things. The next release will have a 3.12.x kernel with squashfs parallel decompression patches and user namespaces enabled. A new panel, Mesa-10 and new video drivers and some other things still in the works.

1.(solved) UEFI limitation
Thank you for helping me there is a UEFI limitation in loading the huge initrd. I solved the problem by installing a distro with small initrd option enabled. Then I merged base.sfs with devx.sfs, enabled base2ram=yes in bootloader and now everything is perfect, I have the best environment to compile my own applications.

2.removing default applications
For removing apps a simple method is to install it using pet package manager and removing it and rebuild the distro. But this working only for those pets that are in pet repository.
Having a possibility to create a barebone distro would be welcomed any time. A barebone distro can be later customized by desire for different kind of applications like running servers on it. A barebone distro which includes just must have things would be more secure when running a server application.

3.WPA2+CCMP not working on Atheros AR5BMD222
Another small problem for me is that my wireless card Atheros AR5BMD222 cannot connect to routers if I use WPA2+CCMP. Instead if I use WPA+TKIP it connects but this is a lot less secure.

Thank you again for your great work. I will continue to test and use this great distro.

joe0855
Posts: 60
Joined: Tue 05 Oct 2010, 09:09
Location: Raleigh, North Carolina, U.S.A.

Installing Fatdog64-630 with YUMI (Multiboot USB Creator)

#123 Post by joe0855 »

Hello Gents,

When I install Fatdog64 using YUMI, I no longer see the syslinux.cfg file where I add the 'append' path to my savefile. The result is a 'groundhog-day-like" boot-up, where I'm prompted to create a new savefile.

Has anyone tried multi-booting Fatdog64 with YUMI or some other multi-boot utility for USB flash drives?

Kirk/Jamesbond - You did it again! Kudos on such a kick-butt distro (630)!

Thanks,
Joe

Aung
Posts: 144
Joined: Sat 20 Jan 2007, 03:30
Location: Hervey Bay

#124 Post by Aung »

You have an old save file being used. Remove old save file or boot with savefile=none.

Solved and sorted, I was booting from a SD card in an onboard slot on a laptop with the 'boot' folder on the SD card. I was getting the correct savefile but the initrd from the hard drive was being picked up. On this laptop the SD card has to be called root (0.0) not (1.0) When booting from a SD card the card is seen as the first drive, took some experimenting to find it. Aung

jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

#125 Post by jamesbond »

L18L, I'm looking at your updated scripts and comments.
I've built the latest internationalised version of dialogs - no problem.
What's the problem with Xdialog? I can display utf8 strings - it seems to work ok?

Joe - what's the bootloader used by YUMI? If it's GRUB then you'll have to look at either menu.lst or grub.cfg

laurentius77 -
2) The current build process makes it impossible to do so. You can try slackbone64 if you want it now. This is on todo list for Fatdog64 700.
3) I think kirk found out the issue was about internal encryption of these atheros cards. What's the driver being used? It may be possible to turn hardware encryption off and use software's one from wpa_supplicant.
You also asked) "Maybe someone have a woof-ce for this distro, I'm also interested in this". Not woof, but Fatdog's own build system. Here: http://www.ibiblio.org/fatdogscm/cgi-bi ... .cgi/index

Scotchialoo - we're not going to update glibc at this stage. Yes it is old, but so is the the other libs. We update what we can without affecting others too much --- glibc is used by *all* apps so it's definitely a no-no.

gcmartin - if I recall correctly, the latest pburn requires the latest gtkdialog too ...
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]

joe0855
Posts: 60
Joined: Tue 05 Oct 2010, 09:09
Location: Raleigh, North Carolina, U.S.A.

#126 Post by joe0855 »

jamesbond wrote:Joe - what's the bootloader used by YUMI? If it's GRUB then you'll have to look at either menu.lst or grub.cfg
Thanks Jamesbond. So since my post, I played around with it some more. YUMI uses syslinux.cfg (which is found in the 'Multiboot' folder created by YUMI). But I needed drill down further into the Fatdog64 directory, where a file called 'isolinux.cfg' was found. This is where I needed to add my 'append' statement which points to the savefile.

Works like a champ. Thanks again for the quick response.

User avatar
L18L
Posts: 3479
Joined: Sat 19 Jun 2010, 18:56
Location: www.eussenheim.de/

Fatdog64-630rc1 (16 Oct 2013)

#127 Post by L18L »

jamesbond wrote:What's the problem with Xdialog? I can display utf8 strings - it seems to work ok?
The buttons should be translated but they are english only in fatdog.
Attachments
Xdialog_OK.png
Xdialog in precise puppy 5.7.1
(107.84 KiB) Downloaded 700 times

Scotchialoo
Posts: 50
Joined: Fri 25 Oct 2013, 14:58
Location: Poland
Contact:

Glibc source

#128 Post by Scotchialoo »

jamesbond wrote:Scotchialoo - we're not going to update glibc at this stage. Yes it is old, but so is the the other libs. We update what we can without affecting others too much --- glibc is used by *all* apps so it's definitely a no-no.
In any apps with a <glibc-2.13,instead of >=glibc-2.13?

Maybe I would be find a Compile problem... Begin to binutils.,and Going to "curl" [Doesn't helps to build glibc-2.17,even in glibc-2.16: Links doesn't works... and crashes at any Startups... - "fatdog savefile=none" is would be helps for a clear Scripts and a still "glibc 2.13"...] and That's be reason for glibc depends? -> http://svn.exactcode.de/t2/trunk/packag ... libc.cache

When I want compile with a My Favorite Browser [Chromium]
http://www.murga-linux.com/puppy/viewtopic.php?t=90112 - Problem detects...

When If glibc is going depend to Newest GCC (4.7.3 instead 4.6.2)
Command for glibc compile is [When I doesn't find a Correct build]: ~/glibc[-2.18,Created empty folder]/glibc[-2.18,Downloaded]/configure --prefix=/usr --libdir=/usr/lib64 --build=x86_64-t2-linux-gnu --disable-profile --enable-kernel=2.6.32 --with-headers=/usr/include libc_cv_forced_unwind=yes libc_cv_cleanup=yes libc_cv_ctors_header=yes
And Command for GCC Compile is (incorrect too...) : ./configure --prefix=/usr --libdir=/usr/lib64 --build=x86_64-t2-linux-gnu --enable-shared --enable-threads=posix --enable-__cxa_atexit --disable-multilib --disable-bootstrap --disable-install-libiberty --with-system-zlib --enable-clocale=gnu --enable-lto --enable-languages=c,c++,objc --disable-libstdcxx-pch --with-newlib --without-headers --disable-decimal-float --disable-threads --disable-libatomic --disable-libgomp --disable-libitm --disable-libmudflap --disable-libquadmath --disable-libsanitizer --disable-libssp --disable-libstdc++-v3 [Without Java,Eclipse]

jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

Re: Fatdog64-630rc1 (16 Oct 2013)

#129 Post by jamesbond »

L18L wrote:
jamesbond wrote:What's the problem with Xdialog? I can display utf8 strings - it seems to work ok?
The buttons should be translated but they are english only in fatdog.
Ah, ok. I thought it is only because of missing locales, but that's not it. I'm going to rebuild Xdialog and hopefully this time it works. I tried amigo patches for Xdialog but not all of them works, so I need to see which one does.

EDIT:

Scotchialoo, sorry I don't understand what you're saying. I do understand your wish for compiling Chromium. But if Chromium needs newer glibc that what is in Fatdog, then it is not going to be easy. You don't need new gcc, only new binutils (and that only because the old binutils that comes with Fatdog has bugs affecting newer glibc). To give out a picture of the enormous task you're about to do:
1. First build new binutils (explained by Sunny here: http://murga-linux.com/puppy/viewtopic. ... 273#733273)
2. Then build the new glibc, installing to different path (*not* to /usr/lib64)
3. Make sure you install the correct "userspace kernel headers" to the new glibc location.
4. Then modify your compiler to make sure that it uses the new glibc (modify the compiler's specs file, or use the trick outlined here: http://stackoverflow.com/questions/8471 ... ingle-host).
5. Then build chromium ... if chromium only depends on glibc. Most likely it's not, so you will need to ...
6. Re-build *all the other libs needed by chromium* (even if they already exist in Fatdog). You may be able to avoid this step, but do so at your own peril. We are talking about Qt libs, X libs, openssl, media codec libs, and all other libs. Build and put them in the new glibc location.
7. Then and only then you can build chromium.

As you can see, the effort would probably be similar to building entirely new distribution altogether. An oh, don't try to replace the existing glibc - you must install the new glibc elsewhere (e.g. /opt/glibc-2.18 or something). Replacing/upgrading glibc is another subject altogether - which I already said I will not touch (there are many other threads on this forum which discuss the wisdom (or lack thereof) of upgrading glibc).
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]

Scotchialoo
Posts: 50
Joined: Fri 25 Oct 2013, 14:58
Location: Poland
Contact:

Re: Fatdog64-630rc1 (16 Oct 2013)

#130 Post by Scotchialoo »

jamesbond wrote: 2. Then build the new glibc, installing to different path (*not* to /usr/lib64)
4. Then modify your compiler to make sure that it uses the new glibc (modify the compiler's specs file, or use the trick outlined here: http://stackoverflow.com/questions/8471 ... ingle-host).

A a bash type before a Compile,alright?:
"> example"

I tried to semi-automatic (without "4." post before you editing...) with /opt/glibc-2.18 and Chromium still doesn't works... :/

But I can be sure too that's Old GCC would be accept without problem...
When I can't be belive about a Portability "Chromium" [Auto instead of G++ Comand.]

jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

Re: Fatdog64-630rc1 (16 Oct 2013)

#131 Post by jamesbond »

Scotchialoo wrote:A a bash type before a Compile,alright?:
"> example"

I tried to semi-automatic (without "4." post before you editing...) with /opt/glibc-2.18 and Chromium still doesn't works... :/
I have no idea what you mean by "semi-automatic". I just want to say that glibc is unlike any other libraries out there that you can simply put to /opt/xxx and hope it will work by adding -I/opt/xxx/include and -L/opt/xxx/lib.
But I can be sure too that's Old GCC would be accept without problem...
The existing gcc can be made to work as I said above (step 4), I have done and tested it myself. But this is not the "proper" way. The proper way is to make a new toolchain that will use the new glibc exclusively.
When I can't be belive about a Portability "Chromium" [Auto instead of G++ Comand.]
Again, I don't think I understand what you are trying to say; but I myself have never built chromium from source, so I can't comment further on difficulting of building chromium. That being said, there are two chromium-derived SFS in the repo: one is from SR Iron, another one is google-chrome itself. Both works well with the current glibc, so I suppose there should not be a need to use newer glibc to build chromium in the first place ...
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]

Scotchialoo
Posts: 50
Joined: Fri 25 Oct 2013, 14:58
Location: Poland
Contact:

Re: Fatdog64-630rc1 (16 Oct 2013)

#132 Post by Scotchialoo »

jamesbond wrote:
Scotchialoo wrote:A a bash type before a Compile,alright?:
"> example"

I tried to semi-automatic (without "4." post before you editing...) with /opt/glibc-2.18 and Chromium still doesn't works... :/
I have no idea what you mean by "semi-automatic". I just want to say that glibc is unlike any other libraries out there that you can simply put to /opt/xxx and hope it will work by adding -I/opt/xxx/include and -L/opt/xxx/lib.
But I can be sure too that's Old GCC would be accept without problem...
The existing gcc can be made to work as I said above (step 4), I have done and tested it myself. But this is not the "proper" way. The proper way is to make a new toolchain that will use the new glibc exclusively.
When I can't be belive about a Portability "Chromium" [Auto instead of G++ Comand.]
Again, I don't think I understand what you are trying to say; but I myself have never built chromium from source, so I can't comment further on difficulting of building chromium. That being said, there are two chromium-derived SFS in the repo: one is from SR Iron, another one is google-chrome itself. Both works well with the current glibc, so I suppose there should not be a need to use newer glibc to build chromium in the first place ...
When... I must be editing from a "Four Step" before a "make",right? [instead of ./configure etc. - of auto]

When I trying to locale with a glibc-2.18 (or in a simple: /opt/chromium) and doesn't help... (even with a editing: ld.so.conf in /opt/etc and /opt/nsswitch.conf doesn't be run to a Chromium waterfall [Binary - not a source from a ~2gb])
Attachments
DoesntWorks-Auto.jpg
/opt/glibc-2.18 and /opt/chromium: Doesn't works.
(149.77 KiB) Downloaded 364 times

jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

Re: Fatdog64-630rc1 (16 Oct 2013)

#133 Post by jamesbond »

Scotchialoo wrote:When... I must be editing from a "Four Step" before a "make",right? [instead of ./configure etc. - of auto]

When I trying to locale with a glibc-2.18 (or in a simple: /opt/chromium) and doesn't help... (even with a editing: ld.so.conf in /opt/etc and /opt/nsswitch.conf doesn't be run to a Chromium waterfall [Binary - not a source from a ~2gb])
No, all this while I thought you were trying to *build chromium from source*. The -L and -I are flags you pass to gcc to build chromium, not to run it.

In this case, all you need to do is do step 1 and 2, and then run chromium like this:

Code: Select all

LD_LIBRARY_PATH=/opt/glibc-2.18/lib:$LD_LIBRARY_PATH /opt/chromium/lib64/chromium/chromium
(assuming your glibc-2.18 is in /opt/glibc-2.18 ). If you get lucky, this may work. If not, well ... let's try google-chrome sfs instead, that is already proven to work :) Where do you get this binary chromium anyway?
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]

User avatar
L18L
Posts: 3479
Joined: Sat 19 Jun 2010, 18:56
Location: www.eussenheim.de/

Fatdog64-630rc1

#134 Post by L18L »

internationalisation of control panel continues

Some utilities internationalized

One problem with pschedule:

Code: Select all

        <col id="0" translatable="yes">Sunday</col>
and others have not been translatable by me :?



edit
Thanks for downloading (3 times) fd_control-panel-utilities.tar.gz
deleted now because everything for control panel is
in http://www.murga-linux.com/puppy/viewto ... &start=164 now
Attachments
pschedule.png
(11.5 KiB) Downloaded 407 times
Last edited by L18L on Thu 05 Dec 2013, 16:27, edited 1 time in total.

Scotchialoo
Posts: 50
Joined: Fri 25 Oct 2013, 14:58
Location: Poland
Contact:

Re: Fatdog64-630rc1 (16 Oct 2013)

#135 Post by Scotchialoo »

jamesbond wrote: No, all this while I thought you were trying to *build chromium from source*. The -L and -I are flags you pass to gcc to build chromium, not to run it
To build chromium from Source? Eh... That's will be big cost... (After compiling glibc instead of runtime.)
In this case, all you need to do is do step 1 and 2, and then run chromium like this:

Code: Select all

LD_LIBRARY_PATH=/opt/glibc-2.18/lib:$LD_LIBRARY_PATH /opt/chromium/lib64/chromium/chromium
(assuming your glibc-2.18 is in /opt/glibc-2.18 ).
If you get lucky, this may work. If not, well ... let's try google-chrome sfs instead, that is already proven to work :) Where do you get this binary chromium anyway?
That's metod are will be works (and that's most important: is Portability. Thanks. But I will be find about a GCC Depend... Maybe That's important about a GCC...? I doesn't know... With a GCC 4.6.2 build works around but... maybe that's Newest is depend -> http://sourceware.org/glibc/wiki/Release/2.18 - But in any event I think that's solve a partial problem but that's not end...) but That's: "Segmentation fault" (that's same as a glibc build to /usr/lib64 - When maybe that's is library reason...) - from Arch Linux:
I downloaded binary chromium waterfall from:
http://build.chromium.org/p/chromium/waterfall [Linux x64]
Attachments
MethodWorks.png
in Arch Linux rep: Works.
in FatDog64: Segmentation fault.
(137.66 KiB) Downloaded 340 times

laurentius77
Posts: 82
Joined: Wed 30 Mar 2011, 07:02

#136 Post by laurentius77 »

jamesbond wrote:L18L, I'm looking at your updated scripts and comments.
I've built the latest internationalised version of dialogs - no problem.
What's the problem with Xdialog? I can display utf8 strings - it seems to work ok?

Joe - what's the bootloader used by YUMI? If it's GRUB then you'll have to look at either menu.lst or grub.cfg

laurentius77 -
2) The current build process makes it impossible to do so. You can try slackbone64 if you want it now. This is on todo list for Fatdog64 700.
3) I think kirk found out the issue was about internal encryption of these atheros cards. What's the driver being used? It may be possible to turn hardware encryption off and use software's one from wpa_supplicant.
You also asked) "Maybe someone have a woof-ce for this distro, I'm also interested in this". Not woof, but Fatdog's own build system. Here: http://www.ibiblio.org/fatdogscm/cgi-bi ... .cgi/index

Scotchialoo - we're not going to update glibc at this stage. Yes it is old, but so is the the other libs. We update what we can without affecting others too much --- glibc is used by *all* apps so it's definitely a no-no.

gcmartin - if I recall correctly, the latest pburn requires the latest gtkdialog too ...
Thank you jamesbond.
I use ath9k wireless driver. I noticed disconnection problems even for wpa+tkip, when I got an error in logs like "radio carrier lost" from the wifi card. I searched the internet and I found that enabling "nolink" option in dhcpd.conf may help in solve the problem. I put "nolink" option in dhcpd.conf and I can connect now using wpa2+ccmp, I will monitor it from now in order to see if there will be disconnections from now on.

User avatar
L18L
Posts: 3479
Joined: Sat 19 Jun 2010, 18:56
Location: www.eussenheim.de/

Fatdog64-630rc1

#137 Post by L18L »

Buttons in zarfy need flexible width, see screenshot.
Attachments
zarfy.png
(27.11 KiB) Downloaded 701 times

jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

#138 Post by jamesbond »

L18L, attached is internationalised version of Xdialog. I will move the Xdialog binary to the main repo, but I will leave out the locale (and the docs) (otherwise it is unfair - all other apps have their locales excluded too :p). Its locale can be merged and bundled with the langpacks. What do you think?

laurentius77 - thanks for the tip.
Attachments
Xdialog-2.3.1-amigo.pet
(31.82 KiB) Downloaded 321 times
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]

nooby
Posts: 10369
Joined: Sun 29 Jun 2008, 19:05
Location: SwedenEurope

#139 Post by nooby »

How far has Fatdog 64 come with the more difficult UEFI
laptops that people have contacted you two about.

Or you have had the chance to borrow or install on
to see what works and what not.

I have now postponed to the far future any buy
due to this dreaded computer lock in they try to force us to.

Sure I can do that another year or two :)
Because most likely those I have will work
for two years more but are getting old now.
I use Google Search on Puppy Forum
not an ideal solution though

User avatar
don570
Posts: 5528
Joined: Wed 10 Mar 2010, 19:58
Location: Ontario

#140 Post by don570 »

I downloaded Fatdog630 from
http://ftp.nluug.nl/os/Linux/distr/fatdog/iso/

It took about half an hour.
________________________________

Post Reply