[CLOSED] Fatdog64-720 Beta [1 Dec 2017]

Message

chironÂ² · #41 Post by **chironÂ²** » Sun 03 Dec 2017, 11:16

@chiron:
Quote:
"Any chance for a newer GLIBC (like 2.22) in final?"

Unlikely. New glibc requires new tooling and generally speaking requires all packages to be rebuild. I do have glibc 2.26 package but I haven't tested whether it can work as an update for the current glibc in 720.

Quote:
"The later claws-mail builds from Debian repos complain and want GLIBC >=2.22"

We would have built this ourselves but claws-mail has ton of dependency. claws-mail seems to be a fork of sylpheed, is there anything in claws-mail that sylpheed doesn't do?

No problem. Just wanted to test the latest 3.15 claws mail. Will stick with the 3.9 then. I know it's a fork of Sylpheed, but 'Look and Feel' are different, and I'm just used to claws.

chironÂ² · #42 Post by **chironÂ²** » Sun 03 Dec 2017, 11:22

NFS utils. I don't know, where I got it from, it should be around the forum, the first I got was a *.pet, now converted it to txz. i attached the pet, *.txz not allowed.

anikin · #43 Post by **anikin** » Sun 03 Dec 2017, 11:51

jamesbond wrote:... Machines I've previously booted Fatdog on (using USB flash drive)
(I no longer have access to some of them):
- Acer eMachines Netbook (2010): Atom N270 (single-core, 1.6GHz), 1GB - BIOS
- HP desktop (2012): Core i5 (dual-core 3.4 GHz), 8GB - UEFI
- Samsung laptop (2012): AMD A6 (quad-core, 1.6GHz), 8GB - BIOS
- Sony Vaio (2014): Core i5 (dual-core, 2.0Ghz), 16GB - UEFI
- MacMini (2017): Core i5 (dual-core, 2.6GHz), 8GB - UEFI
- Self-assembled desktop (2007): Athlon X2 (dual-core, can't remember GHz, definitely faster than the Atom Netbook), Gigabyte motherboard, 4GB - BIOS ...

Hi jamesbond,

Please, clarify this for me as I'm confused. Atom n270 is a pure 32-bit CPU, not capable of 64-bit. How did you manage to get FD, a 64-bit OS run on it?

Sage · #44 Post by **Sage** » Sun 03 Dec 2017, 11:53

...anything in claws-mail that sylpheed doesn't do?

Plenty, has tons of add-ins, hence the ton of deps! It's the knees of the bees. But Sylpheed will do fine for FD, I use Claws all the time in one of my 'major' installations.

jamesbond · #45 Post by **jamesbond** » Sun 03 Dec 2017, 12:00

anikin wrote:Please, clarify this for me as I'm confused. Atom n270 is a pure 32-bit CPU, not capable of 64-bit. How did you manage to get FD, a 64-bit OS run on it?

Ooops!

I made a mistake. It should be Intel Atom N450, 2nd generation Atom which does support 64-bit. I'm going to fix my original post.

LateAdopter · #46 Post by **LateAdopter** » Sun 03 Dec 2017, 13:49

jamesbond wrote:As an aside, we did have a discussion about small vs huge initrd a couple of months back (pros/cons/trade-off/etc) and decided that for the time being, the huge initrd is still the best.

As an academic question!... Is it possible to make a small initrd that can load the fd64.sfs and the kernel-modules.sfs directly from the CPIO homogeneous initrd file?

bigpup · #47 Post by **bigpup** » Sun 03 Dec 2017, 15:37

don570 wrote:to bigpup....

I noticed something strange.
Your device is ---> device:sdc5

Whereas the system is looking for (hd0,4) which is the 5th partition on sda
Could that be causing the delay in booting???

____________________________________________

In my situation I have saved to a folder (fd64save-folder) rather than a save file ---> I believe that is an option when you first make a savefile??
and I am using the hard drive that the kernel recognizes --> sda
Code: Select all
title fatdog 710 (sda1/fd64save-folder)
  find --set-root --ignore-floppies --ignore-cd /fatdog710/initrd
  kernel /fatdog710/vmlinuz   psubdir=fatdog710 pmedia=atahd pfix=fsck savefile=direct:device:sda1:/fd64save-folder 
  initrd /fatdog710/initrd
  
________

It boots quickly. If it isn't booting quickly then it is having recognition problems.

My device names are correct.
The bootloader is on a USB hard drive. It is seen by my system as sdc.
I am booting from it.
The bootloader is only looking at it for stuff.
So to the bootloader it is (hd0,0)
Fatdog is on the 5th partition so it is (hd0,4) or sdc5.

THANKS for the example you use!!!

I played around with the menu entries.

I had a problem with the USB drive not being searched for the save folder I made.
Fatdog booting too fast to let the drive load, so it was not a device that was seen to search.

I used the option

Code: Select all

waitdev=5

and that fixed the search problem.

I found that a very simple boot menu entry worked about as good as any.

Grub4dos bootloader

Code: Select all

title Fatdog64 (sdc5/Fatdog64720b)
  uuid 19b0847a-549d-49c9-8c98-25af56f1d0ee
  kernel /Fatdog64720b/vmlinuz waitdev=5
  initrd /Fatdog64720b/initrd

A savefile= option really did not change the boot time.
Maybe 2 or 3 seconds faster.

The search for the save, on all devices, normally takes 2 to 3 seconds.
That is 2 hard drives and a USB hard drive.

NOTE:
If you really are going to need to do modifications to a boot loader menu.
Especially by a new to Linux normal person.
However, they are going to have problems understanding.

It is very good that the Fatdog help, actually provides some useful help.

Thank you very much for providing that!!

LateAdopter · #48 Post by **LateAdopter** » Sun 03 Dec 2017, 15:54

In the past I used FD6xx with the bootloader on the USB SDcard. The drive numbering swapped around during the boot process, and FD mounted the wrong partition looking for the savefile that was specified as a boot parameter. The fix was to use LABEL rather than the device.

jamesbond · #49 Post by **jamesbond** » Mon 04 Dec 2017, 07:11

Steps to create your own nvidia sfs: http://lightofdawn.org/wiki/wiki.cgi/Cr ... aDriverSFS

@LateAdopter: device discovery is done by kernel and not under our control. In Fatdog 6xx, there was a "bug" in the kernel that caused USB disks to be recognised earlier than built-in disks. It has since rectified but there is no guarantee that it would not happen again (in fact, the kernel team said as much). LABEL or UUID is indeed the solution for this. As an side, for network devices you can rename them ("wlan0" can be renamed to "mywifi"). You can't do the same for disks, however. Once a disk is "sda1", it is always "sda1".

artsown · #50 Post by **artsown** » Mon 04 Dec 2017, 12:00

Notes on boot times and save folder location specification. Computer is
the good 'ol Dell Inspiron 530 desktop having core duo and 4g Ram.
Boot loader is grldr.

Using large initrd, here is my menu.lst item:

title fatdog 720
rootnoverify (hd0,3)
kernel /fd720/vmlinuz savefile=direct:device:sda4:/fd720/fd64save
initrd /fd720/initrd
boot

Boot time is 25 sec. If save folder is on /sda4 instead of in the fd720
folder (and search is required), boot time is 30 sec. Slacko64 boots in
25 sec and xenial64 7.5 boots in 30 sec. I measure from the time the
menu item is selected until my wireless is connected.

sda4 uses ext3 as Kirk suggested. If ext4 is used, fatdog boot time is
85 sec,

Art

proebler · #51 Post by **proebler** » Mon 04 Dec 2017, 12:05

My experience of running FD64-720 Beta on the Acer C720 [Chromebook with JohnLewis BIOS].

I use Kirk's c720_700-04515-x86_64-1.txz [or c720_700-022215-x86_64-1.txz] package again to get the keyboard special keys working to control brightness and sound levels.
The new touch pad utility of the Fatdog64 Control Panel does not allow to set the the touch pad properties on the Acer C720.
Fortunately, the package manager offers
xf86-input-synaptics-chromebook-1.7.6-x86_64-1.txz
xf86-input-synaptics-1.9.0-x86_64-1.txz
flSynclient-0.7p2-x86_64-1.txz
with these installed, the touch pad can be set as as in FD64-710 and earlier.

With frugal install on the HD [SSD], using a 200MB savefile the boot time is approx. 13 sec.
With frugal install on USB, using the same 200MB savefile, the boot time - including waitdev=5 - is approx. 38 sec.
Legacy Grub is used in both cases.

Thanks to the developers for the new version of FatDog64.
It is excellent for use on the Acer C720.
I look forward to the final release and to then use FD-Builder to make a customized ISO.

proebler

kirk · #52 Post by **kirk** » Mon 04 Dec 2017, 14:25

Thanks proebler, I'll update that c720 package for Fatdog64-720 when I get some time. That package includes a touchpad driver which will have problems with the new xorg-server. The package would probably be ok if you deleted the touch pad stuff.

proebler · #53 Post by **proebler** » Mon 04 Dec 2017, 21:05

@ kirk
what are the problems that could be expected to show?
I have not noted anything so far.

don570 · #54 Post by **don570** » Mon 04 Dec 2017, 21:32

I tested new mtpaint 3.49.13 and new gimp 2.8.22
and they work well.

________________________________________

don570 · #55 Post by **don570** » Mon 04 Dec 2017, 22:45

Fast download site..

https://ftp.nluug.nl/ibiblio/distributi ... 4-720b.iso
____________________________________

foxpup · #56 Post by **foxpup** » Mon 04 Dec 2017, 23:33

I did a quick frugal install on a i5 laptop of the new Fatdog64.
It seems to me quicker then the previous 710. Nice experience. I have no problems so far.

I booted it with refind and with grub2. The difference is amazing: refind waits a long time before it starts booting Fatdog, maybe a minute. Grub goes fast, it starts booting almost immediately. It is the first time I see such a difference.

jake29 · #57 Post by **jake29** » Tue 05 Dec 2017, 00:58

Could REISUB be enabled by default? It's a feature I really appreciate. Thanks.

# zgrep -i 'sysrq' /proc/config.gz
CONFIG_MAGIC_SYSRQ=y
CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE=0

proebler · #58 Post by **proebler** » Tue 05 Dec 2017, 01:38

proebler wrote:@ kirk
what are the problems that could be expected to show?
I have not noted anything so far.

You are correct, there is strange behavior when using the touch pad!
For example:
Controlling multiple open windows does not work, they cannot be closed by tapping the close icon in the window bar. The desktop will not clear.
When multiple tabs are open in Seamonkey, tapping a non-active tab will, instead of switching [to that tab], lead to a Page Load Error > "The connection was refused when attempting to contact 0.0.0.0."

This behavior does not happen when using a mouse.

kirk · #59 Post by **kirk** » Tue 05 Dec 2017, 01:54

@ kirk
what are the problems that could be expected to show?
I have not noted anything so far.

I wouldn't think any of those touchpad drivers would work with the new xorg-server without recompiling them.
Libinput that's included with 720 seems to support the c720's clickpad very well. I've uploaded a new c720 package to the repo (c720_720-120417-x86_64-1.txz). You might want to give that one a go with a clean savefolder. I've also updated the touchpad app in the control panel to work with the c720, that will be in final. The current one in 720beta will work too, but you have to restart X.

Could REISUB be enabled by default? It's a feature I really appreciate. Thanks.

To enable it all you have to do is echo 1 >/proc/sys/kernel/sysrq
You could also put it in /etc/rc.d/rc.local. Hopefully that's not something you have to use much. I'm a little leery about having it enabled by default.

jake29 · #60 Post by **jake29** » Tue 05 Dec 2017, 03:00

@Kirk - Okay, no problem. Thanks for the reply.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

[CLOSED] Fatdog64-720 Beta [1 Dec 2017]

grub much faster then refind