Fatdog64-800RC [13 Feb 2019] [CLOSED]

A home for all kinds of Puppy related projects
Message
Author
jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

#31 Post by jamesbond »

1. standard initrd (aka huge initrd aka humongous initrd)
- fd64.sfs inside
- kernel-modules.sfs inside
- size ~400MB
- easy to replace kernel (just replace kernel-modules.sfs and vmlinuz)

2. small initrd
- fd64.sfs outside, merged with kernel-modules.sfs
- no independent kernel-modules.sfs inside or outside
- minimum number of kernel modules (individual modules) inside
- size less than 10MB
- not easy to replace kernel as kernel-modules.sfs is split into two:
=> large part is merged with fd64.sfs
=> a few small ones are merged inside initrd.

3. medium initrd
- fd64.sfs outside
- kernel-modules.sfs inside
- size ~70MB
- easy to replace kernel (just replace kernel-modules.sfs and vmlinuz)
- if you frugal install on hdd/usb you can do this manually yourself, just unpack initrd, take fd64.sfs out; and re-pack initrd.

4. nano initrd
- fd64.sfs outside
- kernel-modules.sfs outside
- size ~4MB
- no kernel-dependent stuff inside initrd
- may not boot properly if hardware requires kernel modules (e.g can't select from multiple savefiles/savedirs if keyboard requires kernel module loaded)
- if you frugal install on hdd/usb you can do this manually yourself, just unpack initrd, take fd64.sfs & kernel-modules.sfs out; and re-pack initrd.

Additional notes:
- The ISO contains both huge initrd and nano initrd. Remaster support 1/2/3 not but 4.
- even though fd64.sfs and kernel-modules.sfs are outside they can be loaded into RAM too if you wish.
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]

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

#32 Post by jamesbond »

mavrothal wrote:Trying RC on mbp works almost perfect :)
Thanks to your feedback :)
A small typo on mbp-kb-backlight.sh blocks it from working (#!/bin[dot]dash).
Also the volume control keys are not working and need some xmodmap(ing) to do the job.

Code: Select all

keycode 113 = XF86AudioMute NoSymbol XF86AudioMute
keycode 114 = XF86AudioLowerVolume NoSymbol XF86AudioLowerVolume
keycode 115 = XF86AudioRaiseVolume NoSymbol XF86AudioRaiseVolume
You may want to add in in rc.platform.
All done.
Other than that nothing major besides the remaining spot/Downloads on fat/vfat media that is still useless and makes running the browser as spot annoying at least.
I thought we've fixed this. Let me check again.
Also, is a kernel change still in the cards?
Yes
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]

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

Re: WiFi not working

#33 Post by jamesbond »

jajk wrote:Managed to get Fatdog installed and booting off hard drive on Acer ES 15 Laptop despite the (intentionally) buggy UEFI implementation designed to keep Win 10 as the only option.
Love the new O.S apart from not being able to connect to a wifi accesspoint.
The wifi applet can see my accesspoint but something is not working when I try to enter the password and connect......no connection is established.
Any clues as to why I cant' connect? Is there some information I can provide to make it clearer what is going on?
Please launch Control Panel, choose the Utilities tab, scroll down to the bottom, and run "Bug Report Info Collector".
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]

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

#34 Post by jamesbond »

rufwoof wrote:How to you drop capabilities in Fatdog?

EDIT: Sorted. I've added new lines into this otherwise it just widens out the forum (posting) width too much)
Good to know. So what went wrong before?
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]

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

Re: create nvidia driver

#35 Post by jamesbond »

don570 wrote:I suggest that Create Nvidia Driver SFS page be re-written
http://www.lightofdawn.org/wiki/wiki.cg ... aDriverSFS

since there is no patch for current nvidia download. This simplifies the instructions.
Thanks. I think the general statement is still true in the sense that newer kernels usually do need patches. The article pointed out at the time of writing 4.14 was the bleeding edge, so it needed patches. By now of course it isn't true anymore, but I also said that "older kernels don't need it".
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]

dancytron
Posts: 1519
Joined: Wed 18 Jul 2012, 19:20

#36 Post by dancytron »

dancytron wrote:I installed it and removed Seamonkey and flash. Then I installed gtk3 and tested the portable Firefox (Fred's version) that I normally use in Debian Dog (and occasionally in various Puppies).

These are the menu.1st entries I am using.
title Fatdog800 fastboot
rootnoverify (hd0,1)
kernel /Fatdog800/vmlinuz rootfstype=ramfs savefile=ram:local:/Fatdog800/fd64save mergeinitrd1=local:/Fatdog800/initrd waitdev=3
initrd /Fatdog800/initrd-nano

title Fatdog800 fastboot No save file
rootnoverify (hd0,1)
kernel /Fatdog800/vmlinuz rootfstype=ramfs savefile=none mergeinitrd1=local:/Fatdog800/initrd waitdev=3
initrd /Fatdog800/initrd-nano
All works well so far.

Looks like a great job.
Continuing. . .

Removed libreoffice and dictionary, gimp pidgin avidemux transmission-qt5 and compton. Installed lxterminal. Changed defaults to portable firefox and lxterminal as applicable.

Added my /ect/asound.conf from Debian Dog ( See second example - https://alien.slackbook.org/blog/adding ... nd-levels/ ) which worked just fine.

Remastered with small initrd. ISO file was 316 meg.

Everything works great. It is at least as fast as Debian Dog Stretch, maybe even faster.

This is the menu.1st entry.
title Fatdog800 remaster
rootnoverify (hd0,1)
kernel /Fatdog800/vmlinuz rootfstype=ramfs savefile=ram:local:/Fatdog800/fd64save basesfs=ram:local:/Fatdog800/fd64.sfs waitdev=3
initrd /Fatdog800/initrd

jake29
Posts: 253
Joined: Fri 24 Jul 2015, 17:47

#37 Post by jake29 »

I'm now using Fatdog64 regularly on a laptop, and on a few recent occasions did not pay close attention to battery-level - the result was a sudden system power-off.

Is there any utility within Fatdog64 currently that could force standby mode at low battery-level (i.e 5%)? Something like this would be a little more user-friendly to laptop users.

Apologies for making a feature request at RC stage, but this experience has been quite jarring.

EDIT: If a desktop notification warning is supposed to occur at 15%, I have not observed this.

User avatar
rufwoof
Posts: 3690
Joined: Mon 24 Feb 2014, 17:47

#38 Post by rufwoof »

jamesbond wrote:
rufwoof wrote:How to you drop capabilities in Fatdog?
EDIT: Sorted. I've added new lines into this otherwise it just widens out the forum (posting) width too much)
Good to know. So what went wrong before?
When I was just 'trying it' from the command line, I forgot the -- at the end (otherwise just returns).

For example as root run capsh --print and you'll see all the capabilities that are permitted and one will be cap_chown, Then run

Code: Select all

# capsh --drop=cap_chown --
# touch tst
# ls -l tst
-rw-r--r-- 1 root root 0 Feb 17 19:32 tst
# chown spot:spot tst
chown: tst: Operation not permitted
After the first line above you're back at the shell prompt, but if you omitted the -- at the end then you're not in a child process, but back at the parent level, that still has chown capabilities.

The -- signifies what to execute after the capabilities have been adjusted i.e. more usually in code you put a script path/name after the --
Last edited by rufwoof on Sun 17 Feb 2019, 19:42, edited 2 times in total.

User avatar
SFR
Posts: 1800
Joined: Wed 26 Oct 2011, 21:52

#39 Post by SFR »

jake29 wrote:I'm now using Fatdog64 regularly on a laptop, and on a few recent occasions did not pay close attention to battery-level - the result was a sudden system power-off.

Is there any utility within Fatdog64 currently that could force standby mode at low battery-level (i.e 5%)? Something like this would be a little more user-friendly to laptop users.

Apologies for making a feature request at RC stage, but this experience has been quite jarring.

EDIT: If a desktop notification warning is supposed to occur at 15%, I have not observed this.
Ok, what happens when you launch this in terminal, when AC is disconnected:

Code: Select all

batt-low.sh low
You should get a yaf-splash with a warning message.
If not, what's the output of:

Code: Select all

cat /proc/acpi/ac_adapter/*/state /sys/class/power_supply/*/online
Greetings!
[color=red][size=75][O]bdurate [R]ules [D]estroy [E]nthusiastic [R]ebels => [C]reative [H]umans [A]lways [O]pen [S]ource[/size][/color]
[b][color=green]Omnia mea mecum porto.[/color][/b]

jake29
Posts: 253
Joined: Fri 24 Jul 2015, 17:47

#40 Post by jake29 »

SFR wrote: Ok, what happens when you launch this in terminal, when AC is disconnected:

Code: Select all

batt-low.sh low
You should get a yaf-splash with a warning message.
I just now tested and the 15% warning did appear without my intervention. This is the first time I have seen the message, perhaps previously I had clicked it away without noticing.

User avatar
mavrothal
Posts: 3096
Joined: Mon 24 Aug 2009, 18:23

#41 Post by mavrothal »

jamesbond wrote:
Other than that nothing major besides the remaining spot/Downloads on fat/vfat media that is still useless and makes running the browser as spot annoying at least.
I thought we've fixed this. Let me check again.
No, you are right. I had updated the beta savefile :oops: . Is ok on a new one.
Though now spot has access in the entire device not just the Downloads folder. I guess is a trade off.

A bit latter: It would appear that the keyboard issues are not mac-specific. In an oldish i5 samsung (NP350) the Fn modifier is recognized only for F1, 6, 7 and 8 but not F2, 3, 4, 5, 11 and 12. In this cage neither showkey (-s) nor hexdump -C nor xev return any code as if they are dead. For reference "big" distributions have no issue with either mbp nor samsung function keys and modifiers.
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==

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

#42 Post by jamesbond »

mavrothal wrote:No, you are right. I had updated the beta savefile :oops: . Is ok on a new one.
Though now spot has access in the entire device not just the Downloads folder. I guess is a trade off.
It is indeed a trade-off. It's the only way to do it if you're using FAT. Using any other filesystem (including ntfs), spot will not have access to the partition.

If you don't move the Downloads folder, the easiest way to lock down spot when you have savefile in FAT is to pass the boot param SAVEDEVICE_MODE_STRICT=yes. (Don't use this if you move the Downloads folder otherwise spot can't access it).
A bit latter: It would appear that the keyboard issues are not mac-specific. In an oldish i5 samsung (NP350) the Fn modifier is recognized only for F1, 6, 7 and 8 but not F2, 3, 4, 5, 11 and 12. In this cage neither showkey (-s) nor hexdump -C nor xev return any code as if they are dead. For reference "big" distributions have no issue with either mbp nor samsung function keys and modifiers.
Yeah, this is quite confusing. udev changed the way the handle keyboard; but that was a couple years ago (many of the points remain valid however). That being said, we have the full eudev in FD; with complete rules and hwdb for keyboards, so it should work. Except that it doesn't. I installed 800alpha on samsung laptop (not accessible to me at the moment) and I still had to use the compatibility "udev-keymap" to program the special keys. Perhaps those big distros have something else going that I'm not aware off. I'd look at that but it probably won't get resolved in Final. Nevertheless, I have added the mbp special xmodmap codes; so at least we're covered for the mbp case :D
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
mavrothal
Posts: 3096
Joined: Mon 24 Aug 2009, 18:23

#43 Post by mavrothal »

jamesbond wrote: Perhaps those big distros have something else going that I'm not aware off.
As far as I can see now keymaps are kernel modules, kernel kbd and X xkb are unified, and systemd (:shock: ...) takes care of the rest.
I do not know if building the kernel with the keymaps modules in will make scancodes recognizable or not but might worth trying.
In the mean time I went around the lame-way, got scancodes from kernel errors and made the relevant setkeycode entries in rc.local (no messing with udev rules)
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==

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

#44 Post by jamesbond »


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
mavrothal
Posts: 3096
Joined: Mon 24 Aug 2009, 18:23

#45 Post by mavrothal »

jamesbond wrote:I've just rebuild eudev
Is this in the repo (to test)?
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==

stemsee

#46 Post by stemsee »

bluez package no longer has bt-audio, it seems.

I have not examined the difference between this package and the one in fatdog-721, but maybe audio connection is now through 'bluealsa', but my bluetooth app you referenced in the first post does not connect audio service in 800RC.

Also using 'prt sc' to capture areas of the screen places the image in /root. So that when trying to upload to forum using seamonkey, images are not accessible by spot ... they then need to be copied into spot /root directory.

EDIT: bluetoothctl is installed: it wasnt in 721. This maybe useful.
https://stackoverflow.com/questions/218 ... t-commands
Attachments
xscreenshot-20190220T111836.png
(16.66 KiB) Downloaded 728 times
xscreenshot-20190220T111858.png
(9.4 KiB) Downloaded 724 times

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

#47 Post by jamesbond »

bluez package no longer has bt-audio, it seems.
This was provided by bluez-tools package in 721. In 800, bluez-tools no longer provides this as the same functionality can now be done using bt-connect.
I have not examined the difference between this package and the one in fatdog-721, but maybe audio connection is now through 'bluealsa', but my bluetooth app you referenced in the first post does not connect audio service in 800RC.
Oops. I was under the impression you did this for the 800 series and therefore has taken into account the changes in 800.

The change is basically because we use bluez-5.x. Bluez-5 is a major change, they drop a lot of the tools and change the way things work behind the scenes. Bluez-tools also removed a lot of their tools because bluez-5 no longer provides the API to work with it.
Also using 'prt sc' to capture areas of the screen places the image in /root. So that when trying to upload to forum using seamonkey, images are not accessible by spot ... they then need to be copied into spot /root directory.
Yes. This is by design. This is to prevent you accidentally take an embarassing screenshot which is accidentally shared with the rest of the world ....

But if you really want screenshots to be saved to /home/spot automatically, just edit /etc/xdg/Startup/xscreenshot and add the parameter "-p /home/spot/xscreenshot" to the "exec" line you see there. Then logout and login again.
EDIT: bluetoothctl is installed: it wasnt in 721. This maybe useful.
https://stackoverflow.com/questions/218 ... t-commands
bluetoothctl is the "new" CLI tool from bluez.
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]

stemsee

#48 Post by stemsee »

Excellent stuff. I will rewrite the script to take advantage of the bluetoothctl and anything else I can find. But I already connected a speaker using bluetoothctl interactive mode. Yes, it is much easier and more reliable. I also found how to pipe to bluetoothctl so both options will be available if useful.

I will also simply link to fd bluetooth tether in the command section. If the mac address can be piped to the script.

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

#49 Post by don570 »

Suggestion...

When 'Reboot' is selected from menu there is a warning message...
however it should remind user to save open documents.
_________________________________________________

stemsee

#50 Post by stemsee »

jamesbond wrote:This was provided by bluez-tools package in 721. In 800, bluez-tools no longer provides this as the same functionality can now be done using bt-connect.
err bt-connect is not in bluez5 but bluetoothctl connect.

Actually to connect a bluetooth audio device is like this

Code: Select all

bluetoothctl
bluetoothctl#scan on
bluetoothctl#devices
bluetoothctl#pair $mac
bluetoothctl#trust $mac
bluetoothctl#connect $mac
or non interactively

Code: Select all

echo -e "scan on" | bluetoothctl
echo -e "devices" | bluetoothctl
echo -e "pair $mac" | bluetoothctl
echo -e "trust $mac" | bluetoothctl
echo -e "connect $mac" | bluetoothctl
or

Code: Select all

bluetoothctl scan on
bluetoothctl scan off
bluetoothctl devices
bluetoothctl pair $mac
bluetoothctl trust $mac
bluetoothctl connect $mac
Audio Services available seem to be auto-found.
Last edited by stemsee on Tue 26 Feb 2019, 12:07, edited 2 times in total.

Post Reply