As UEFI was discussed during the beta period, I looked at it a bit and I have a question. If my machine only boots from "clean" "read only" ISO images, does UEFI have any benefit for that environment?

UEFI is a replacement firmware for BIOS that's found on newer computers. You ether have it or you don't, though some UEFI implementations do have a legacy (BIOS) mode. Fatdog64-620 will boot on BIOS computers or UEFI computers.

Thanks for the response, Kirk.
I should have given more information. I do have a machine that will boot either way and I have it set to accept either. Without any change in settings, FD610 and 620 each boot no problem. My question came from my recollection of the reading I did during the early beta time and my recollection of the purpose of UEFI as I understood it.

As I recall UEFI boots only with signed code and is intended to prevent maliciously corrupted access to the machine. Yes? Is there more that relates to FatDog64 that perhaps I did not understand? Further, since I boot only from a "clean" "read only" ISO and do not use a "savefile" does UEFI benefit my environment?
Thanks again!

Is there more that relates to FatDog64 that perhaps I did not understand?

Fatdog64 can boot on SecureBoot environment but it doesn't bring any supposed "benefits" of SecureBoot (whatever the "benefits" are).

Quote:

Further, since I boot only from a "clean" "read only" ISO and do not use a "savefile" does UEFI benefit my environment?

In this *very particular scenario*, no, there is no benefit choosing to boot Fatdog with UEFI over booting Fatdog with BIOS mode.

Gnuxo wrote:

Edit: Ok nevermind. Russian is included in the keyboard layouts but whenever I try to change it, I'm unable to type at all. It's not detected.
Something is wrong with the russian language in Fatdog64

As far as locales are concerned, I'm sorry to say that Fatdog64 is English only.
Additional locales are available from the package manager and also on the devx - load the devx, set the appropriate locales and then you can unload devx, of you wish, but there is no localisation/internationalisation in Fatdog64.
Keyboard layouts are supposed to work, but both myself and kirk only understand one layout so we rely on people like you to confirm whether it work (or not) and hopefully over a fix if not.

EDIT: seems that you need to enable an UTF-8 locale before you can use the Russian keyboard layout. I tested using en_AU.UTF-8 locale, restart X as suggested, and after that I changed the keyboard layout to Standard Russia. Opening terminal, I can then type some characters.

liboicl wrote:

First of all, as of 6.0.0, I believe, the initrd has contained the base and mosule sfs files. This makes the initrd file huge. I have a 10MB boot partition and I have to edit the initrd, move the files, and modify the init script with every release. This is very tedious. I preferred the previous releases with the files already separate.

You don't have to edit the initrd manually. There is a CLI tool called "fatdog-split-initrd.sh" to do that for you. Okay, I concede we'll probably need a FAQ entry on this

Quote:

Secondly, I upgraded from 6.0.1 to this one and it takes about 40 seconds after boot for my mouse and keyboard to start working. On 6.0.1 they both worked instantaneously. They are both USB devices.

? Can you elaborate?

Gobbi wrote:

I unchecked 'Sofware mixing (shared access)' from the second window after I chose the sound card from
Control Panel/Sound/Fatdog64 Set Default Sound Card and the annoying nasty noise from my HDMI output doesn't bother me anymore . Now my Sapphire HD 7870 XT works great in Fatdog64 620 .

Thank you. I am under the impression that everybody knows that when using HDMI, the software mixing should be turned off ...

JustGreg wrote:

USB 2.0 Device Booting

Thank you for the testing the USB booting in USB boot. This is very useful information, we should get this information documented in a more permanent place, let me think ...

spandey wrote:

You are right, the routing table is not correct.

I need to look at pppoe stuff, but I won't have the time for that now
Can you try this: type "route add default gw x.x.x.x" where x.x.x.x is the the second IP address on ppp0 interface (the one you get from ifconfig ppp0), and see if you can ping 8.8.8.8 after this?

gcmartin wrote:

Server Manager (SAMBA, et.al)
Further review of the Server manager shows that the server I "disabled" remained disabled while the servers I enable and started did not show enabled/restarted after save-session during reboot. Specifically crond, ntp, samba.

I've just tested on a fresh ISO, booted up with "multisession" option, enable all the 3 services (crond, ntp, samba), reboot (and saving the session), and everything came back running after that

Very slow to detect drives, just slow to operate, normal to sign off.
Got 1Gb, but it isn't doing much (subjectively). This is still a compact distro with .iso of 224Mb. Can run live CDs three times that size at normal speed. This is the first time on any machine, any distro, any mem complement that I've seen this super-slow behaviour.

Server Manager (SAMBA, et.al)
Further review of the Server manager shows that the server I "disabled" remained disabled while the servers I enable and started did not show enabled/restarted after save-session during reboot. Specifically crond, ntp, samba.

I've just tested on a fresh ISO, booted up with "multisession" option, enable all the 3 services (crond, ntp, samba), reboot (and saving the session), and everything came back running after that

Thanks JamesBond.

Maybe you and I have somehow used different boot options or save-session path back to Live media. I have this problem on 2 completely different PCs with identical results. That is, the subsystems are not restarting; and they are shown so in the tool provided in the Control panel. The PCs are non-UEHI PCs with old BIOSs.

Has anyone else seen a similar issue with Live media boot and save sessions where these or other servers that are enabled and started via the control panel are not enabled and/or started upon reboot?

I will revisit my "boot-run-reboot" path again and report back, here, in this post soon. I will document the steps in such a way as it will lead to discovery of where this may be breaking down.

Edit: If there are any system files which anyone feels would also help shed light on the issue, please advise and I will provide.

Here to help_________________Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Enginesor use DogPile

Using Live Media to boot FATDOG620. This time an installation departure was taken. I DID NOT INSTALL ALL PETs as had been done on prior FATDOG620 Live Media setup. I ONLY installed the 2 requirements I felt necessary: see below:

Created a fresh FATDOG620 multi-session base DVD on an RW

Booted FATDOG with parms

... withlvm withmdadm nouveau.noaccel=1 savefile=no

At desktop

turn on swap to use the swap partition

install Kirk's "eject" PET

setup SAMBA configuration for LAN sharing

Use Control Panel for following

Localization

timezone

hostname

set wallpaper

System

Fatdog PPM

install required SAMBA Extensions

Fatdog Server Management

Enable and Start all necessary servers

exited the desktop

set system password

set SAMBA password

Enter the desktop

Reboot

designate the savefile drive (sr0)

system rebooted with parms

... withlvm withmdadm nouveau.noaccel=1 savefile=direct:multi

Opened desktop to find the Server subsystems are started. (This is the expected behavior that I had NOT gotten before.)

Thanks James for testing.
Again, the primary change, this time, was to NOT install all of the PETs required for this version to replace my older FATDOG520_________________Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Enginesor use DogPile

The nvidia-310.44-3.8.7 driver was already installed on here. I uninstalled it, rebooted, then installed the Nvidia-313.30-FD620-K3.7.8.pet. Rebooted, and it could not detect the correct resolution of my monitor, which is 1900x1080. Here is xerrs log;

After many tries I had no success with ati_13.4 pet on my computer . Tomorrow I shall install the pet on a different AMD hardware . The 13.3b3 pet gave me much hope because it works .
With 13.4 it happens exactly as with 13.1 that is X does not start . After loading the kernel a message tells that the file /var/log/Xorg.0.log is missing .Neither xorgwizardxwin or xorgwizard-old solves anything .
Using 13.3b3 I found that file , so posting it maybe helps ...

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum