FossaDog (Ubuntu 20.04 'Focal Fossa' LTS) 64-bit (updated 2020-11-15)

[fredx181]

Thanks for positive reply, @puddlemoon .

I have no idea why backlight is almost off for you, strange, with so many drivers and kernel modules installed.

somehow my .asoundrc was .asoundrc.bak so i had no sound in FF until i found that.

That probably happened after using "pequalizer" (it creates ~/.asoundrc when running it, and ~/.asoundrc.bak when closing it)

Fred

[fredx181]

Updated FossaDog, FossaDog-2020-09-19_64-bit-UEFI.iso

Kernel upgrade, some small bugfixes and more, see also at Changes and Fixes
This will probably be the last update for some time, unless there are major bugs found.

Download: https://github.com/DebianDog/FossaDog/b ... e-bugfixes

Added to Dog Linux website now: FossaDog

Fred

[fredx181]

Updated packages:

- quick-remaster, version 1.2.4
Change is that there is choice now to merge extra loaded .squashfs modules into the remaster or not.
(previous version in fact only offered to rename extra loaded .squashfs to .bak, if chosen not to rename, it still merged into 01-filesystem.squashfs)
Also added to Stretchdog, Bionicdog, Busterdog repositories.

- straw-viewer (gtk-youtube-viewer alternative), version 0.0.9

Fred

[puddlemoon]

thanks @fredx181
forgot to confirm before that yes, manual install to UEFI USB works as expected. once i exit out of refind, grub.config arrives. i also used from there the copy2ram line, all good.

as a long time puppy/debian user i am still trying to understand where exactly i am in the middle here with dog linux... so far a little lost at times, but very impressed.

I am also teaching myself linux audio, so i am wanting to incorporate jack and rt audio in a remaster and i'd like to know which kernels in this forum can be used? with a script? (or swapped manually)? e.g. the ones from busterdog or perhaps from @rockedge ?
or is that all over complicated and i just should use what is in the repos?

[fredx181]

I am also teaching myself linux audio, so i am wanting to incorporate jack and rt audio in a remaster and i'd like to know which kernels in this forum can be used? with a script? (or swapped manually)? e.g. the ones from busterdog or perhaps from @rockedge ?
or is that all over complicated and i just should use what is in the repos?

Not sure if the lowlatency kernel from Ubuntu will do? (there's no rt kernel available anymore, I believe lowlatency replaces it) Anyway here's a "package":
https://github.com/DebianDog/FossaDog/r ... ncy.tar.gz
For a frugal install: Extract in the "casper" folder (but better first rename initrd1.xz and vmlinuz to .bak, otherwise will be overwritten, also rename k-5.4.0-47-generic.squashfs e.g. to .bak) and reboot.
I tested and boots OK, but cannot really test audio.
Also attached "upgrade-kernel-lowlat" script, can be used to build or upgrade the lowlatency kernel "package" yourself.
Remove fake .gz and make executable.
It will install the lowlatency kernel in "chroot" so does not alter the filesystem.
You need a Linux formatted partition for that (ext2/3/4)

Fred

[puddlemoon]

this is great!
low latency is more than adequate in most cases. i will build an rt at some point, not second nature, but i have done before...
i didn't notice anything ubuntu specific in the script, will the same or similar work with sid?


thanks again

[fredx181]

i didn't notice anything ubuntu specific in the script, will the same or similar work with sid?

The kernel is from the Ubuntu repos (linux-image*).
No rt kernel is in the Sid repo.

Using a rt kernel from Puppy, Fatdog or whatever should be possible, but probably needs some modifications to work with Fossadog.

Fred

[puddlemoon]

Gotcha.
I had assumed that there was a similar low latency in he sid repo.

Well with just some preliminary testing, the kernel you linked is working great! latency is as expected or better (again minimal testing thus far).
Apulse is bridging to jack with no extra fuss.

I will use the script to update from here. Thanks again! this is really the "both worlds" I have been imagining.

[fredx181]

I had assumed that there was a similar low latency in he sid repo.

Buster does have a rt kernel in repo, running from Busterdog "upgrade-kernel" and choose it from list of available kernels will make a kernel 4.19 rt "package".

Fred

[puddlemoon]

Super!
I will juggle some dogs and see what works well. thanks so much for your quick help!

[helloworld]

thanks it works good,but it can not run a app installed by snap ,i can install a app through snap,but the app always fails to run,i mean all snap apps.you can test it to prove my words,So does it with bionicdog.Could you solve this problem to make the fossa/bionic/ or any ubuntu dog more perfect,if you are awailable.

[helloworld]

thanks it works good,but it can not run a app installed by snap ,i can install a app through snap,but the app always fails to run,i mean all snap apps.you can test it to prove my words,So does it with bionicdog.Could you solve this problem to make the fossa/bionic/ or any ubuntu dog more perfect,if you are awailable.

[fredx181]

thanks it works good,but it can not run a app installed by snap ,i can install a app through snap,but the app always fails to run,i mean all snap apps.you can test it to prove my words,So does it with bionicdog.Could you solve this problem to make the fossa/bionic/ or any ubuntu dog more perfect,if you are awailable.

It seems that snap doesn't work in a live system, not that I understand all details, but from a websearch I found that it's problematic, specially in combination with "aufs'" (which is in use with Fossadog), so I'm afraid it cannot be fixed.
Tested just now on a Fossadog full install, and snap works fine.

Fred

[The Flying Cat]

PPA adding command defaults to bionic. Can just add 'focal' at the end like

Code: Select all

 add-apt-repository ppa:graphics-drivers/ppa focal 

or change 'bionic' to 'focal' via synaptic.

[fredx181]

Thanks. Yes, forgot to change in the add-apt-repository script to focal.
Btw, if you use it frequently, it might be better to install software-properties-common, it contains the "real" add-apt-repository (the script fails sometimes).
Then you need to rename the script /usr/local/bin/add-apt-repository because /usr/local/bin is earlier in PATH

Fred

[The Flying Cat]

Seems like Quick Remaster (1.2.4) removes something important. At least after copying from backup '/lib/modules/*kernel-number*-generic' additional sensors, virtual cd drive and nvidia proprietary driver works again. Maybe it is worth to include additional option to keep changes in the kernel folder for cases when kernel dependent software is used. Granted you need to reinstall all this software (and kernel headers) every time you change kernel

And Quick Remaster stalls when there is already existing 'remaster' directory

Code: Select all

mkdir: cannot create directory ‘remaster’: File exists

from previous cancelled remaster.

[fredx181]

Seems like Quick Remaster (1.2.4) removes something important. At least after copying from backup '/lib/modules/*kernel-number*-generic' additional sensors, virtual cd drive and nvidia proprietary driver works again. Maybe it is worth to include additional option to keep changes in the kernel folder for cases when kernel dependent software is used. Granted you need to reinstall all this software (and kernel headers) every time you change kernel

Good point, thanks, yes, quick-remaster excludes the whole /lib/modules directory, fixed in v1.2.5, change:
instead excluding whole /lib/modules directory, exclude files only that exist in the extra loaded kernel module (in '/lib/modules/*kernel-number*-generic/kernel/*'), so any new added files, symlinks and/or folders in '/lib/modules/*kernel-number*-generic' will be included.

And Quick Remaster stalls when there is already existing 'remaster' directory
Code: Select all
mkdir: cannot create directory ‘remaster’: File exists

The warning from mkdir cannot be the reason that it stalls (the script should continue after such warning), no idea why what's the reason then, I will investigate later.

Fred

[trister]

Hello,
I see that FossaDog has newer Kernel version than BusterDog. I tried it and almost all my squashfs work (since many of them are from ubuntu repos).

Is there a Build system/script like BusterDog?

Thanks again for your amazing job

[fredx181]

Hello,
I see that FossaDog has newer Kernel version than BusterDog. I tried it and almost all my squashfs work (since many of them are from ubuntu repos).

Is there a Build system/script like BusterDog?

Thanks again for your amazing job

Hi trister, no build script, sorry.
Btw, there are other newer kernel "packages" (5.6 and higher) that should work on Busterdog here:
https://github.com/DebianDog/BusterDog/ ... s/tag/v0.2

Fred

[fredx181]

*** ISO updated: FossaDog-2020-11-15_64-bit-UEFI.iso ***

Changes and fixes (at bottom of post, for FossaDog-2020-11-15_64-bit-UEFI.iso):
viewtopic.php?p=2476#p2476

Download: https://github.com/DebianDog/FossaDog#d ... e-bugfixes
EDIT: Re-uploaded with small fix, latest version now 2020-11-15 instead of 2020-11-14

Fred

[The Flying Cat]

Seems like quick-remaster 1.2.6 and 1.2.5 doesn't merge loaded squashfs modules. Merging is working in 1.2.4 version.

And 1.2.6/1.2.5 versions show "1.2.4" in it's window name.

[fredx181]

Seems like quick-remaster 1.2.6 and 1.2.5 doesn't merge loaded squashfs modules. Merging is working in 1.2.4 version.

And 1.2.6/1.2.5 versions show "1.2.4" in it's window name.

Thanks, I'm working on other things now, but will look at it sooner or later.

Fred

[fredx181]

Seems like quick-remaster 1.2.6 and 1.2.5 doesn't merge loaded squashfs modules. Merging is working in 1.2.4 version.

And 1.2.6/1.2.5 versions show "1.2.4" in it's window name.

Thanks, I'm working on other things now, but will look at it sooner or later.

Fred

Finally... I tested 1.2.6 now, but could not reproduce, for me extra loaded squashfs modules are merged in the remaster (except for the kernel .squashfs, which is not merged on purpose)
Anything special about your setup ? (so I could try to reproduce perhaps doing similar).

Fred

[The Flying Cat]

It is working! 1.2.6 and 1.2.4! Identically! The only thing is that only 01-filesystem.squashfs getting renamed with ".bak". Other modules persists so you need to remove/rename them manually. Maybe they was renamed in the old versions and I just interpreted it wrongly (or I'm just having some minor one-time-only bug again)

[mcgiwer]

Does it planed to create and become published the documentation for the Focal Fossa?

The main reason of this question is that I'm (and probably many other as well) are unsure, with kernel parameters would be accepted in the boot process" Puppy's , Debian/Ubuntu ones or mixed.

[fredx181]

@mcgiwer
From first post of this thread (if your looking for boot codes specially for FossaDog):

Boot Method: porteus-boot , see examples; https://github.com/DebianDog/FossaDog/r ... -codes.txt

For the rest all general kernel parameters can be used, AFAIK.

Not much documentation for now TBH, only at first post, and at https://debiandog.github.io/doglinux/zz04fossadog.html and above Examples-boot-codes.txt.
(not sure if more will be written in the future)

Fred

[mcgiwer]

Question: Does anyone know who are the developers of FossaDog and how can they be contacted? There is no info about them neither on the website, nor on GitHub

I ask because I haven't seen any activity on neither of any from mentioned above since several months

[rockedge]

I just heard from fredx181, Have you tried to send a PM or email to him via this forum?

[wiak]

Question: Does anyone know who are the developers of FossaDog and how can they be contacted? There is no info about them neither on the website, nor on GitHub

Yes, as rockedge alludes, it is fredx181, who was one of the original developers of the DebianDogs, and now maintains all of them including FossaDog; he texted you on this forum thread as lately ago as 10 April above. Forum member 'saintless', Toni, who started the DebianDogs, left the forum a long time ago.

https://debiandog.github.io/doglinux/zz07about.html

[helloworld]