Fatdog64-810 Final [17 Jan 2020]

A home for all kinds of Puppy related projects
Post Reply
Message
Author
fatdog
Posts: 104
Joined: Wed 17 Apr 2013, 03:12

Fatdog64-810 Final [17 Jan 2020]

#1 Post by fatdog »

PS: This thread was previously used to discuss 810 Beta. Discussion for 810 Final Release starts on page Page 9 of this thread.

The Fatdog team is pleased to release Fatdog 810 Final.

This is a maintenance release. All Fatdog 800/801/802 users are recommended to upgrade to this release where possible as it contains important fixes.

If you still run earlier Fatdog series (700 or 600), we also recommend upgrading to this version where possible. In this case, you may want to read the notes/warnings noted in Fatdog64 802/801/800 thread.

As usual Fatdog64 does not upgrade from any older version. Using a new savefile/savedir is recommended.

=====

Changes from 802:

Updates:
- linux-4.19.92
- yad_gtk2-0.42.0_9 - fixed various crashes
- grub4dos-0.4.6a.2020.01 - fix initrd too large
- printing - defaults to pdftoraster avoiding ghostscript where possible.
- cups-filters - updated to 1.26.1
- gtk2-2.24.32 - include latest upstream patches
- rox-filer-jun7 - update to latest.
- bacon-3.9.3
- fatsort-1.6.2.605 (support sorting exFat)
- mp-5.36 (with Qt GUI now, instead of gtk2)
- xlockmore-5.61
- gparted 0.33.0 with upstream patches (includes "gpart" for gparted)
- parted 3.3
- gtksu-2020.01
- doxygen-1.18.17 (devx only)
- UExtract to 3.41
- vim/gvim: update to 8.2.0069
- fltk-1.3.5
- libgnutls/libp11kit/libnettle version updates
- updated CA certs from 2019.12
- gtk-theme-switch: cli gtk2 theme switcher
- update-firefox: now launches firefox using apulse, make sound work again

- Microcode update 2019-11-15
- New shim - better-looking UI
- Dunst - better looking notification
- Xorg server 1.20.6
- openssl 1.1.0l
- Bluez 5.52, bluez-alsa 2.0.0
- mtpaint 3.49.19
- Fatdog Wireless Antenna 1.3.1
- Misc fixes to SMB browser
- mm_view 20191029
- PackIt 1.20
- musl 1.1.24 (in devx)
- xf86-video-amdgpu 19.1.0
- llvm-6.0.1
- libva-2.5.0
- libva-intel-driver-2.3.0
- mesa-8.3.6
- deb2txz: now will convert post-install/rm scripts too (good for printer drivers)
- libnss and libnspr now in base (not in devx): required for google-chrome
- tar 1.32
- libinput-1.14.1
- squashfs-tools 4.4
- Libreoffice 6.2.8.1
- seamonkey 2.49.5
- Avidemux to 2.7.3

New Features:
- fatdog-brightness.sh now automatically stored
- rc.platform support for mbp mid 2012 and ACER AO722
- screencast.sh: can convert to GIF directly
- samba's testparm now included in base
- ssvnc fixes, now supporting on-the-fly scaling
- bsdriver: x11vnc continue to run until server is stopped
- x11vnc: built with -noxdamage by default
- include a sudo emulation (note: requires password)
- ISO now contains VERSION file information.
- support launching AppImage from Rox

- Supports ISO file booting from SuperGrubdisk2
- zstd and lz4 support
- "autoswap" boot parameter - search and use existing swap partitions on boot
- fatdog-samba-manager.sh: Share/unshare any folder using Samba using Rox right click
- fatdog-convert-root.sh, convert spot-only applications to run as "root".
- Add "wait" to net= boot parameter. New bbshell and bbhook boot parameter.

and numerous bug fixes and fine tunings.

Get it from here: ibiblio.org, or from aarnet, uoc.gr, or nluug.nl.

The ISO builder is available in ibiblio.org or one of the mirrors above, get the builder dated 2020.01 and 810-pkglist.tar.xz.

=====

If you have any questions please check this pages first: http://distro.ibiblio.org/fatdog/web/faqs/faq.html. This page is also available offline, and you can view it by clicking this link [url]file:///usr/share/doc/faqs/faq.html[/url]. Or you can click the blue (?) icon on the desktop.

Thank you for all the contributors who supported us behind the scene with their feedback, bug reports, ideas, and fixes.


---------------------------------------------------------------------

For 810 beta users:

Changes:
- linux-4.19.92
- yad_gtk2-0.42.0_9 - fixed various crashes
- grub4dos-0.4.6a.2020.01 - fix initrd too large
- printing - defaults to pdftoraster avoiding ghostscript where possible.
- cups-filters - updated to 1.26.1
- gtk2-2.24.32 - include latest upstream patches
- rox-filer-jun7 - update to latest.
- bacon-3.9.3
- fatsort-1.6.2.605 (support sorting exFat)
- mp-5.36 (with Qt GUI now, instead of gtk2)
- xlockmore-5.61
- gparted 0.33.0 with upstream patches (includes "gpart" for gparted)
- parted 3.3
- gtksu-2020.01
- doxygen-1.18.17 (devx only)
- UExtract to 3.41
- vim/gvim: update to 8.2.0069
- fltk-1.3.5
- libgnutls/libp11kit/libnettle version updates
- updated CA certs from 2019.12
- gtk-theme-switch: cli gtk2 theme switcher
- update-firefox: now launches firefox using apulse, make sound work again

Updates:
- fatdog-brightness.sh now automatically stored
- rc.platform support for mbp mid 2012 and ACER AO722
- screencast.sh: can convert to GIF directly
- samba's testparm now included in base
- ssvnc fixes, now supporting on-the-fly scaling
- bsdriver: x11vnc continue to run until server is stopped
- x11vnc: built with -noxdamage by default
- include a sudo emulation (note: requires password)
- ISO now contains VERSION file information.
- support launching AppImage from Rox
Last edited by fatdog on Mon 27 Jan 2020, 18:09, edited 8 times in total.
-= The Fatdog Team (kirk, jamesbond, SFR and step) =-
[url=http://murga-linux.com/puppy/viewtopic.php?p=794748#794748]Contributed Fatdog64 packages thread[/url]
This account is used for announcements only. Send PM directly to members' handle.

fatdog
Posts: 104
Joined: Wed 17 Apr 2013, 03:12

#2 Post by fatdog »

810 Final notes and known problems:
=======
1. Fatdog 810 is re-issued on 21 Jan 2020. This is only one fixes included over the previous issue: bsdriver has been update to 3.20 and now it offers options to be used with Remote Desktop option (this is x11vnc server); it is specifically meant to address some performance issues because now x11vnc is compiled with NOXDAMAGE as default.

If you don't have any issues with bsdriver (or don't use it) then there is no need to re-download.

2. Grub4dos users: 810 comes with grub4dos 0.4.6a by default. This is the actively maintained grub4dos; it has bug fixes and support for things such as 64-bit ext4 support etc. However it is well known that this version doesn't support older computers.

If you need to use grub4dos and the included grub4dos support doesn't work for you, grub4dos 0.4.5c is also available in /usr/share/grub4dos-0.4.5c; you need however to use it manually.

3. Firefox users: 810 comes with a different configuration for libapulse. Existing firefox users will lose sound: to be able to hear sound, run firefox prefixed with "apulse" (e.g. "apulse firefox") like everyone else is doing (including Puppy).

Newly installed firefox using update-firefox.sh will automatically run apulse-prefixed firefox.

4. If you like to use 5.4.7 kernel (or any other kernel), there are guides here: http://distro.ibiblio.org/fatdog/web/faqs/kernel.html and here: http://distro.ibiblio.org/fatdog/web/fa ... ernel.html.

5. The default kernel in 810 beta is still the same as 802 - that is, 4.19.x series; and it still has the same issue with certain Ryzen-based systems: Certain AMD Ryzen-based platforms come with broken BIOS with missing ACPI tables. There are multiple solutions for this, but the easiest one to get your system to boot, is to add "noapic" to the kernel command line (but it will disable certain feature). Alternatively, the better fix is to use "ivrs_ioapic" kernel command line but you must know the proper value for your system. There isn't any generic value for that.

6. We noticed that some fullscreen SDL programs will have blinking mouse cursors. This seems to be a new glitch that didn't exist before, and it seems to be corrected by exporting SDL_VIDEO_X11_DGAMOUSE=0. This has been done on the re-issued 810 release, but if you are on the original release, you need to do this yourself.

7. The nvidia driver SFS has been updated to support kernel 4.19.92 in the 810 release.

8. The soundcard selector does not work for anything other than English language, as reported here. Fix: please install the hotfixes.

9. The language selector "loses" language until the next reboot. Fix: please install the hotfixes.

========

How to install the hotfixes:
1. Download the package. Choose to "save" it, do not attempt to "install" from the browser.
2. Open rox folder that contains the downloaded package. Then right-click on the package, and choose "Install Package."
3. Note: hotfixes cannot be uninstalled because they alter system files. Uninstalling them means you delete some system files and Fatdog may not work correctly after that (until you start a new savefile).
Last edited by fatdog on Mon 27 Jan 2020, 15:34, edited 6 times in total.
-= The Fatdog Team (kirk, jamesbond, SFR and step) =-
[url=http://murga-linux.com/puppy/viewtopic.php?p=794748#794748]Contributed Fatdog64 packages thread[/url]
This account is used for announcements only. Send PM directly to members' handle.

fatdog
Posts: 104
Joined: Wed 17 Apr 2013, 03:12

#3 Post by fatdog »

...reserved...
-= The Fatdog Team (kirk, jamesbond, SFR and step) =-
[url=http://murga-linux.com/puppy/viewtopic.php?p=794748#794748]Contributed Fatdog64 packages thread[/url]
This account is used for announcements only. Send PM directly to members' handle.

fatdog
Posts: 104
Joined: Wed 17 Apr 2013, 03:12

#4 Post by fatdog »

The Fatdog team is pleased to release Fatdog 810 beta on 9 December 2019.

This is a maintenance release. As usual Fatdog64 does not upgrade from any older version. Previous version: Fatdog64 802/801/800. If you are new to Fatdog, or if you are updating from 700/710 series, it is worth to read the notes listed there too.

=====

Changes from 802:

Updates:
- Linux kernel 4.19.86 (5.3.15 is available in the repo)
- Microcode update 2019-11-15
- New shim - better-looking UI
- Dunst - better looking notification
- Xorg server 1.20.6
- openssl 1.1.0l
- Bluez 5.52, bluez-alsa 2.0.0
- mtpaint 3.49.19
- Fatdog Wireless Antenna 1.3.1
- Misc fixes to SMB browser
- mm_view 20191029
- PackIt 1.20
- UExtract 3.40
- musl 1.1.24 (in devx)
- xf86-video-amdgpu 19.1.0
- llvm-6.0.1
- libva-2.5.0
- libva-intel-driver-2.3.0
- mesa-8.3.6
- deb2txz: now will convert post-install/rm scripts too (good for printer drivers)
- libnss and libnspr now in base (not in devx): required for google-chrome
- tar 1.32
- libinput-1.14.1
- squashfs-tools 4.4
- Libreoffice 6.2.8.1
- seamonkey 2.49.5
- Avidemux to 2.7.3

New Features:

- Supports ISO file booting from SuperGrubdisk2
- zstd and lz4 support
- "autoswap" boot parameter - search and use existing swap partitions on boot
- fatdog-samba-manager.sh: Share/unshare any folder using Samba using Rox right click
- fatdog-convert-root.sh, convert spot-only applications to run as "root".
- Add "wait" to net= boot parameter. New bbshell and bbhook boot parameter.

and numerous bug fixes and fine tunings.

Get it from here: ibiblio.org, or from aarnet, uoc.gr, or nluug.nl.

The ISO builder files will be released at a later date (on release of 810 Final).

=====

If you have any questions please check this pages first: http://distro.ibiblio.org/fatdog/web/faqs/faq.html. This page is also available offline, and you can view it by clicking this link [url]file:///usr/share/doc/faqs/faq.html[/url]. Or you can click the blue (?) icon on the desktop.

Thank you for all the contributors who supported us behind the scene with their feedback, bug reports, ideas, and fixes.


---------------------------------------------------------------------


Beta notes
=======
1. Grub4dos users: 810 comes with grub4dos 0.4.6a by default. This is the actively maintained grub4dos; it has bug fixes and support for things such as 64-bit ext4 support etc. However it is well known that this version doesn't support older computers.

If you need to use grub4dos and the included grub4dos support doesn't work for you, go and install grub4dos 0.4.5c from the repo. Or download from here and use the files individual: http://distro.ibiblio.org/fatdog/packag ... i686-1.txz

In the next release, Fatdog will include both grub4dos 0.4.6a (as default) and grub4dos-0.4.5c to ensure maximum compatibility for older computers.

2. Firefox users: 810 comes with a different configuration for libapulse. Existing firefox users will lose sound; and those who uses update-firefox.sh will still lose sound as well. To be able to hear sound, run firefox prefixed with "apulse" (e.g. "apulse firefox") like everyone else is doing (including Puppy).

This issue has been addressed and fixed for the final release: newly installed firefox using update-firefox.sh will automatically run apulse-prefixed firefox.

3. If you like to use 5.3.15 kernel (or any other kernel), there are guides here: http://distro.ibiblio.org/fatdog/web/faqs/kernel.html and here: http://distro.ibiblio.org/fatdog/web/fa ... ernel.html.

4. The default kernel in 810 beta is still the same as 802 - that is, 4.19.x series; and it still has the same issue with certain Ryzen-based systems: Certain AMD Ryzen-based platforms come with broken BIOS with missing ACPI tables. There are multiple solutions for this, but the easiest one to get your system to boot, is to add "noapic" to the kernel command line (but it will disable certain feature). Alternatively, the better fix is to use "ivrs_ioapic" kernel command line but you must know the proper value for your system. There isn't any generic value for that.
Last edited by fatdog on Fri 17 Jan 2020, 15:08, edited 2 times in total.
-= The Fatdog Team (kirk, jamesbond, SFR and step) =-
[url=http://murga-linux.com/puppy/viewtopic.php?p=794748#794748]Contributed Fatdog64 packages thread[/url]
This account is used for announcements only. Send PM directly to members' handle.

User avatar
ally
Posts: 1957
Joined: Sat 19 May 2012, 19:29
Location: lincoln, uk
Contact:

#5 Post by ally »


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

#6 Post by jamesbond »

Thanks ally :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]

LateAdopter
Posts: 361
Joined: Fri 27 May 2011, 17:21
Location: Reading UK

#7 Post by LateAdopter »

Hello jamesbond, kirk et al

Thanks for this.
I have been trying to get it to work properly on my new AM4 motherboard with the Athlon 3000G processor.
I don't want to clutter this thread with debugging that, but if you already know the answer, please tell me...

1) If I boot with the large initrd, grub4dos says Error 28: Selected item cannot fit into memory. It will boot Fatdog with the nano-initrd.
On my old AM3 motherboard grub4dos could boot Fatdog either way with 2GB of RAM and my AM4 has 8GB

2) Fatdog will boot to the desktop with your 5.3.15 kernel using VBE when there is no Raven2 firmware. The only unrelated problem was that the ethernet doesn't connect, but see below.

3)DELETED
Bionicpup64 works properly with AMDGPU using stemsee's 5.3.11 kernel with the Raven2 firmware.
I have tested Fatdog using that 5.3.11 kernel and the only noticeable difference from your 5.3.15 was that the ethernet does connect.
I can't see any difference in the messages or Xorg0.log between Fatdog and Bionicpup64 up to the modeset.

DELETED
Last edited by LateAdopter on Tue 17 Dec 2019, 11:43, edited 1 time in total.

step
Posts: 1349
Joined: Fri 04 May 2012, 11:20

#8 Post by step »

@LateAdopter, are you using grub4dos 0.4.6a or 0.4.5c? See post #2. If 0.4.6a try replacing grldr with the one from 0.4.5c.
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]

LateAdopter
Posts: 361
Joined: Fri 27 May 2011, 17:21
Location: Reading UK

#9 Post by LateAdopter »

Hello step

Actually it is 4.4 that was installed by Precise Puppy because, at the time, the grub4dos installer in Fatdog would not install to a PBS.

While setting up this box I have accidentally booted Fatdog 800 that worked on the AM3 board with that grub4dos and it gets the same error, so it is motherboard related not installation.

My Fatdog and Bionicpup installs are done manually.

On the subject of grub4dos 0.4.6a my interpretation of what yaya has said is that it does not support 64bit ext4 but does recognise it as an unsupported format, but I may be wrong about that. She also said that it does work with a GPT partitioned disk and installs above 32k or to the PBS (whatever that is called with GPT)

LateAdopter
Posts: 361
Joined: Fri 27 May 2011, 17:21
Location: Reading UK

#10 Post by LateAdopter »

DELETED
I guess that Fatdog's pawprint in RAM must be much bigger than Bionicpup64
Last edited by LateAdopter on Tue 17 Dec 2019, 11:45, edited 1 time in total.

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

#11 Post by mavrothal »

Tried it on my mbp and went without a hitch :D
It is only missing the webcam module but I guess I'll wait for the final before I compile it.
I also used sound recording through the builtin microphone and was borderline. Not sure if is missing something or ALSA is not playing well with it. I'll look a bit further if I get any time.
Overall very mac-friendly 8)

You may want to do something about updates though.
If it is to be used on a regular basis, should be upgradable.
I guess one issue with the updates is to make sure that no files in the savefile will cover the new SFS system files but is should not be very difficult. Files on extra-sfs though could be more tricky.
BTW I booted the CD into a VM that had FD801 installed and it found and used the savefile without any issues. The savefile was pretty empty in this machine but still updated fine.
== [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] ==

kirk
Posts: 1553
Joined: Fri 11 Nov 2005, 19:04
Location: florida

#12 Post by kirk »

The solution to getting Fatdog to boot with AMDGPU was to boot without the firmware, create a 1GB swapfile, then boot with the firmware.
Glad you got it to work. You could also try splitting the initrd into a smaller initrd and a fd64.sfs http://distro.ibiblio.org/fatdog/web/fa ... nitrd.html and then with the basesfs= parameter don't choose to load it into RAM. That would save about 340MB of RAM.
Or you can extract the fd64.sfs from the initrd and then use one of the vmlinuz-initrd kernels. The vmlinuz-initrd kernels have an initrd, kernel modules, and firmware compiled into the kernel. I do that with my Acer c720 which has 2GB of RAM, but I'm pretty sure I can boot that one ether way.

Also, what is the name of your AMDGPU firmware? And did you get your Ethernet to work? That could be missing firmware as well. You can type dmesg in a terminal and look for messages about missing firmware. Actually, the easiest thing to do is:

Code: Select all

dmesg | grep firmware 
dmesg | grep Firmware 
The 5.3.15 has a different set of firmware than 4.19.x. That's required because different kernels require different versions of firmware. Unfortunately, there's no really good way to determine exactly what firmware you need for a particular set of kernel modules. Well, other reading a lot of source code.
It is only missing the webcam module but I guess I'll wait for the final before I compile it.
If that's a module that's included in the kernel let me know and I'll add it to our kernel config for next time.

LateAdopter
Posts: 361
Joined: Fri 27 May 2011, 17:21
Location: Reading UK

#13 Post by LateAdopter »

Hello kirk

The ethernet is the well known r8169. In the changelog for kernel 5.4.2 there was a fix for a regression in r8169 to do with the jumbo packet. Maybe your kernel has the regression too. This is from the messages with kernel 5.3.11.

Code: Select all

Dec  9 18:29:27 fatdog64-e75 user.info kernel: [  T405] libphy: r8169: probed
Dec  9 18:29:27 fatdog64-e75 user.info kernel: [  T405] r8169 0000:25:00.0 eth0: RTL8168h/8111h, 00:d8:61:c8:cd:b1, XID 541, IRQ 52
Dec  9 18:29:27 fatdog64-e75 user.info kernel: [  T405] r8169 0000:25:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
The AMD family 18 GPUs in this year's APUs are Raven2 and Picasso. This is the list of firmware. I extracted them from the Debian Buster firmware-amd-graphics package.

Code: Select all

raven2_asd.bin       raven2_me.bin    raven2_pfp.bin    raven2_sdma.bin
raven2_ce.bin        raven2_mec2.bin  raven2_rlc.bin    raven2_vcn.bin
raven2_gpu_info.bin  raven2_mec.bin   raven2_sdma1.bin

picasso_asd.bin       picasso_me.bin    picasso_pfp.bin      picasso_sdma.bin
picasso_ce.bin        picasso_mec2.bin  picasso_rlc_am4.bin  picasso_vcn.bin
picasso_gpu_info.bin  picasso_mec.bin   picasso_rlc.bin
You might need to warn people that the AMDGPU driver takes a lot of RAM and they may need to boot with nomodeset first and create a swapfile.

AMD systems have native HDMI2 capability and can do 4k RGB 444 at 60Hz. They can decode 4k HevcMain10 and that is bound to take at least four times the RAM that 1920x1080 needs.

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

#14 Post by rufwoof »

You might need to warn people that the AMDGPU driver takes a lot of RAM and they may need to boot with nomodeset first and create a swapfile.
I believe that explains why my 4GB AMD Radeon R2 laptop sees around 512MB of that lost to the onboard Radeon GPU
# free -m
total used free shared buff/cache available
Mem: 3406 370 1890 896 1144 1802
Swap: 26623 0 26623
# grep MemTotal /proc/meminfo
MemTotal: 3488488 kB
# glxinfo | egrep -i 'device|memory'
Device: AMD MULLINS (DRM 2.50.0, 4.19.44, LLVM 5.0.2) (0x9853)
Video memory: 512MB
That's with the current 802 Fatdog.
[size=75]( ͡° ͜ʖ ͡°) :wq[/size]
[url=http://murga-linux.com/puppy/viewtopic.php?p=1028256#1028256][size=75]Fatdog multi-session usb[/url][/size]
[size=75][url=https://hashbang.sh]echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh[/url][/size]

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

#15 Post by jake29 »

Thanks for this new build, jamesbond, kirk, step and others.

A few issues so far. The first is likely unrelated to this build.

(1) LICK installation. I decided to give this a try and it does work, provided I manually trigger boot menu and choose LICK. If I simply allow the laptop to boot into LICK, input devices do not function, keyboard and mouse are unresponsive.

(2) Intel AX200 WiFi / Bluetooth card support. Running Kernel 5.3.15 and adding iwlwifi-cc-a0-46.ucode (download) to /lib/firmware - is enough to get WiFi working. However Bluetooth is non-functional, see attached image.

EDIT: A newer version of the firmware (iwlwifi-cc-a0-48.ucode) is available here and fixes the Bluetooth issue.
Attachments
terminal.png
(147.28 KiB) Downloaded 295 times
Last edited by jake29 on Tue 10 Dec 2019, 22:31, edited 2 times in total.

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

#16 Post by don570 »

fatdog64 810 report..

1) when first launch --> SFS loader app has /mnt/home at top of window
however this folder doesn't exist at first launch.
SFS loader does work OK

2) I suggest that there should be link in /root back to /usr/doc/
called 'Help'

3) I couldn't get nvidia-418.43-k4.19.24_32_44.sfs to work on my nvidia 1030 card

__________________________________________

LateAdopter
Posts: 361
Joined: Fri 27 May 2011, 17:21
Location: Reading UK

#17 Post by LateAdopter »

kirk wrote:
The solution to getting Fatdog to boot with AMDGPU was to boot without the firmware, create a 1GB swapfile, then boot with the firmware.
Glad you got it to work.
DELETED
I notice that xserver 19.6 is in the Fatdog 810 repo. Is it practical for me to roll back to that, to test the theory?
Last edited by LateAdopter on Tue 17 Dec 2019, 11:40, edited 1 time in total.

kirk
Posts: 1553
Joined: Fri 11 Nov 2005, 19:04
Location: florida

#18 Post by kirk »

EDIT: A newer version of the firmware (iwlwifi-cc-a0-48.ucode) is available here and fixes the Bluetooth issue.
If we rebuild the kernel before final I'll add that.

3) I couldn't get nvidia-418.43-k4.19.24_32_44.sfs to work on my nvidia 1030 card
Those packages are kernel specific, so none will work with the current kernel. It looks like that one is for the 4.19.24 kernel.
I notice that xserver 19.6 is in the Fatdog 810 repo. Is it practical for me to roll back to that, to test the theory?
Probably, but besides xorg-server, you'll want to install all of the xf86-input-xxxx and xf86-video-xxx packages before you try restarting the x server. You might also have to rollback the libinput package.

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#19 Post by BarryK »

kirk wrote:Unfortunately, there's no really good way to determine exactly what firmware you need for a particular set of kernel modules. Well, other reading a lot of source code.
In EasyOS I run this script:

Code: Select all

#!/bin/sh

KERVER="$(uname -r)"
rm -rf fnd-firmware 2> /dev/null
rm -f missing-firmware 2> /dev/null

ALLMODULES="$(find /lib/modules/${KERVER}/kernel -type f -name '*.ko' | tr '\n' ' ')"

for AMODULE in $ALLMODULES
do
 BASENAME="$(basename $AMODULE .ko)" #ex: radeon
 FIRMWARE="$(modinfo ${BASENAME} | grep '^firmware: ' | tr -s ' ' | cut -f 2- -d ' ' | tr '\n' ' ')"
 for AFIRMWARE in $FIRMWARE
 do
  if [ -f /lib/firmware/$AFIRMWARE ];then
   FIRMDIR="$(dirname /lib/firmware/$AFIRMWARE)"
   mkdir -p fnd-firmware${FIRMDIR}
   cp -a -f /lib/firmware/$AFIRMWARE fnd-firmware${FIRMDIR}/
   if [ -h /lib/firmware/$AFIRMWARE ];then
    REALFILE="$(readlink /lib/firmware/$AFIRMWARE)"
    cp -a -f ${FIRMDIR}/${REALFILE} fnd-firmware${FIRMDIR}/
   fi
   sync
  else
   echo "${BASENAME}: ${AFIRMWARE}" >> missing-firmware
  fi
 done

done
What you do is find all firmware, everything that you can find, and put it into /lib/firmware, then run that script. You need to be running with the particular kernel that you want to find the firmware for.

I also have scripts that will just find network or display related firmware, if you are interested.

Well, the script reads from /lib/firmware, but it can be any folder in which you accumulate all firmware that you can find, let's call it "firmwareEVERYTHING".

If you find some more firmware to add to firmwareEVERYTHING, I recommend copy it in like this:

Code: Select all

# cp -a -u --remove-destination more-fw/* firmwareEVERYTHING/
the --remove-destination will prevent cp from following symlinks and overwriting target of a symlink.

The script will even log what firmware is still missing.
[url]https://bkhome.org/news/[/url]

kirk
Posts: 1553
Joined: Fri 11 Nov 2005, 19:04
Location: florida

#20 Post by kirk »

Thanks Barry. I have a similar script that uses modinfo and outputs the missing firmware, pretty similar really. It also takes in two text files called firmware-delete and firmware-keep. Those files list firmware we don't want (too big, too old, etc) and firmware we want to include. The problem we ran into is that modinfo doesn't always show the firmware that's needed, which is why we have the firmware-keep file. Our process for creating a new firmware collection is:

1)Download git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

2)Copy the old firmware into the downloaded linux-firmware. This is in case we manually added some firmware in the past. Always true.

3)Edit/run create-firmware-collection.sh. Which I described above.

I'm sure you know this, but for the benefit of others, we have to update the firmware collection anytime there is a kernel change. Usually just for major changes, not bug fix revisions. So if we go from 4.19.87 to 4.19.88 no firmware change, but from 4.19.87 to 5.3.15 then we have to update the firmware. This is because newer versions of the same kernel module will sometimes require newer firmware. Of course we could just include everything from linux-firmware.git, but that's 753MB, and that still doesn't contain all the firmware we want. For the 4,19.86 kernel we include 85MB of firmware, and for 5.3.15 it's 90MB. And believe it or not we do try and keep the dog from gaining too much weight :)

Anyway, that's problem we have.

Post Reply