Fatdog64-720 and 721 Final [11 Jan 2018]

[chiron²]

I added Kodi 17.6 from the SFS Manager, pristine FD721 frugal install. Wouldn't start from the menu. When I started Kodi in Terminal I got missing libraries liblibsamba.something. I installed samba4 (full) in GSlapt, and Kodi started normally.

That DVD-issue is as follows: I start DVD playback, everything OK, it shows the company's logo then the usual messages (copying is a crime, age suitability etc.) then the music starts (background sound from the menu), but the last of the messages remains on the screen. If I then click randomly on the screen and hit a menu entry, the corresponding submenu shows up, and from there I can go back to the main menu and everything is as expected. This is in Kodi 17.3 in FD710 and FD720 and Kodi 17.6 in FD721.

[jake29]

@chiron² - Unsure if it will make any difference, but I install 'mesa-vdpau' from gslapt. In the past Kodi would present some freezing issues if it was not installed.

[step]

I added Kodi 17.6 from the SFS Manager, pristine FD721 frugal install. Wouldn't start from the menu. When I started Kodi in Terminal I got missing libraries liblibsamba.something. I installed samba4 (full) in GSlapt, and Kodi started normally.

Can't reproduce here. This is what I did.

Boot Fatdog64-721 ISO without a savefile. Manually load the Kodi sfs (previously downloded and saved - and I also tested Kodi sfs downloaded from ibiblio by sfsmanager).

Code: Select all

# load_sfs.sh --load /path/to/kodi_17_6-2017.12.20-720.sfs
0001-yajl-2.1.0-x86_64-1.txz
0002-tinyxml-2.6.2-x86_64-1.txz
0003-lockdev-1.0.3-x86_64-1.txz
0004-libssh-0.7.5-x86_64-1.txz
0005-libp8_platform-2.1.0.1-x86_64-1.txz
0006-libnfs-2.0.0-x86_64-1.txz
0007-libmysqlclient_mariadb_kodi-10.1.10-x86_64-1.txz
0008-libmicrohttpd-0.9.58-x86_64-1.txz
0009-libcec-4.0.2-x86_64-1.txz
0010-libcdio-0.94-x86_64-1.txz
0011-libass-0.14.0-x86_64-1.txz
0012-crossguid-2016.09.07-x86_64-1.txz
0013-kodi-17.6-x86_64-2.txz
autorun-after.sh

A dialog message tells me that I need to load/install python2 or the devx sfs before Kodi can run. I load the devx sfs.

Then:
- right-click the desktop for a menu and Kodi is found in category "Multimedia".
- click the Menu icon in the application bar; Kodi NOT found in Multimedia or any category.

So, right-click the desktop... to start Kodi. It starts fine here.
Open a terminal window and start Kodi from the shell:

Code: Select all

# kodi &

Again, it starts fine here. No messages about missing libraries. I can browse the local samba shares as I described previously.

Ideas:
1. Is there an existing ~/.kodi folder in your system?
2. Corrupt SFS?

Code: Select all

# md5sum /path/to/kodi_17_6-2017.12.20-720.sfs
cfeff47eb406ba86b0a54d4aad66cace  /path/to/kodi_17_6-2017.12.20-720.sfs

That DVD-issue is as follows: I start DVD playback, everything OK, it shows the company's logo then the usual messages (copying is a crime, age suitability etc.) then the music starts (background sound from the menu), but the last of the messages remains on the screen. If I then click randomly on the screen and hit a menu entry, the corresponding submenu shows up, and from there I can go back to the main menu and everything is as expected. This is in Kodi 17.3 in FD710 and FD720 and Kodi 17.6 in FD721.

Let's restrict testing to Kodi 17.6 in FD721.
Have you tried a different DVD?
Are you loading any other SFS? Check with load_sfs.sh --loaded.
Did you install video drivers? I have an nvidia display card driven by nouveau.

[Billtoo]

I have Kodi 17.6 sfs installed on my 7.21 Fatdog install, no Samba, I
did install the latest proprietary nvidia driver.
Kodi plays the DVD in screenshot2 fine, but it won't play another DVD
(Mad Max Fury Road), this one has 3 or 4 previews of upcoming movies on
it, VLC seems to automatically skip the previews and plays the movie
fine but Kodi won't play it at all.

[dr. Dan]

In the Fatdog64 installer's Boot loader section the 'Additional boot parameters' is available even if 'Do not install boot loader' is selected.

https://imgur.com/a/c7p1Q

From /faqs/boot-options.html:
"These parameters must be passed on to Fatdog64 before the system boots up, during boot-loading stage. Boot loaders can be configured to pause and ask for parameters during boot up (like the one in Fatdog64 Live CD/DVD), or you can put it in the configuration file."

This all suggests that there is a file I can edit to add boot parameters - can someone tell me it's location?

Thanks.

What boot loader are you using?

Dan

[chiron²]

OK. The samba-issue vanished. I obviously had a ~/.kodi directory before loading the 17.6 sfs. From accidentally manually loading and unloading of the 17.3 sfs, then rebooting. After starting fresh (savefolder renamed), kodi 17.6 just runs after loading the sfs (and the devx, of course).

Regarding the DVDs. Of course I tried multiple discs in that machine. Previews are fine, but as soon as the menu comes up, trouble. So, I tested the whole thing in an old T61 Thinkpad, same Fatdog, same kodi, same DVD. Worked. Other DVDs did have the same issue in the T61. So the problem is neither with FD, nor with Kodi, it's probably somehow hardware related and random. Both machines tested are core2duo and have intel graphics.

[jake29]

What boot loader are you using?

Dan

Windows was installed on the drive. Then I installed Fatdog64 to a ext3 partition without boot loader. I now load Fatdog64 via CD - with savefile on hdd.

[step]

jake29, if you installed Fatdog64 to a Windows drive without adding a boot loader then the existing boot loader is the Windows one, which varies depending on the Windows version (XP vs. Win7+). I don't know if the Windows boot loader can start a Linux distro. Usually we do it the other way around, with grub or grub4dos installed to the MBR of the hard drive and two boot entries, one for Linux and one for Windows. Do you care for booting Windows from that hdd at all?

[dr. Dan]

Windows was installed on the drive. Then I installed Fatdog64 to a ext3 partition without boot loader. I now load Fatdog64 via CD - with savefile on hdd.

Is that your preferred method? My primary computer loads fatdog64 with the Windows boot loader, modified according to MS documentation, easily done. Once it is booting, it ought to be possible to add additional parameters. I haven't had to re-boot in a long time, and I don't know when I am likely to again, but I think I remember it getting handed off to syslinux, with its boot options.
Alternately, you could make a remastered disc with custom options at boot. isolinux.cfg is the file. The primary options are listed in the help files.
Does that help?

[snayak]

Dear All,

I see avahi daemon running on my fatdog 720.
This is something new to me. What does it do?
How to stop it so that it wont run on next boot?

Sincerely,
Srinivas Nayak

[Keef]

snayak

Open the FatDog control panel, then Manage Servers and Services. You can disable it there.
It is something to do with networking, but not essential.
https://www.avahi.org/

What is Avahi?

Avahi is a system which facilitates service discovery on a local network via the mDNS/DNS-SD protocol suite. This enables you to plug your laptop or computer into a network and instantly be able to view other people who you can chat with, find printers to print to or find files being shared. Compatible technology is found in Apple MacOS X (branded "Bonjour" and sometimes "Zeroconf").

If I remember correctly when I first ran FatDog 710, it was high on CPU use, and I disabled it without problem. I'm now on 721 and it is running with little overhead, so have left it alone.

[jake29]

step / dr. Dan - Thanks for the replies. That answered my question. I think it's time I set up a proper Boot loader.

[step]

Avahi daemon in 720 has replaced mdns daemon in 710. As others already wrote, CUPS can use avahi to discover printers in a LAN. I can add that the Kodi sfs uses it too. You can disable avahi auto-start in Control-panel > System > Services if you don't need it.

[dr. Dan]

step / dr. Dan - Thanks for the replies. That answered my question. I think it's time I set up a proper Boot loader.

Just FYI, recently I needed to lend my (just purchased) laptop to someone who had to have that other OS in order to use Photoshop and Lightroom. Somewhere I read that W7 (probably others as well) won't perform updates properly when booted from a different boot loader, but I was able to perform them without issue. Not that I would recommend their new "updates".

[snayak]

Thanks for helping me on Avahi.

[step]

step / dr. Dan - Thanks for the replies. That answered my question. I think it's time I set up a proper Boot loader.

Just FYI, recently I needed to lend my (just purchased) laptop to someone who had to have that other OS in order to use Photoshop and Lightroom. Somewhere I read that W7 (probably others as well) won't perform updates properly when booted from a different boot loader, but I was able to perform them without issue. Not that I would recommend their new "updates".

I have seen some corner-case, multi-partition boot loader setups where W7 wasn't marked genuine anymore, therefore Windows Update failed.

[jake29]

step / dr. Dan - Thanks for the replies. That answered my question. I think it's time I set up a proper Boot loader.

Just FYI, recently I needed to lend my (just purchased) laptop to someone who had to have that other OS in order to use Photoshop and Lightroom. Somewhere I read that W7 (probably others as well) won't perform updates properly when booted from a different boot loader, but I was able to perform them without issue. Not that I would recommend their new "updates".

I have seen some corner-case, multi-partition boot loader setups where W7 wasn't marked genuine anymore, therefore Windows Update failed.

I will report back how I get on. The only reason I have the Windows partition is for games. And I certainly can't afford to take the performance hit of the Intel Meltdown patch on my current CPU. So dr. Dan, you don't need to talk to me about avoiding updates

I hope in the near future to upgrade to an i5 based system (I only realised recently how cheap an Ivy Bridge refurb sells for) - and then play Windows games via VGA PCI Passthrough using Looking Glass.

[Billtoo]

I moved the usb-3.0 SSD install from my Lenovo desktop to my HP desktop and
it has a new savefile:

System: Host: fatdog64-ccf Kernel: 4.14.12 x86_64 bits: 64 Desktop: Openbox 3.5.2
Distro: Fatdog64 Linux 721
Machine: Device: desktop System: Hewlett-Packard product: HPE-410f serial: MXX0370KF3
Mobo: FOXCONN model: 2AB1 v: 1.00 serial: N/A
BIOS: American Megatrends v: 6.02 date: 07/21/2010
CPU: 6 core AMD Phenom II X6 1045T (-MCP-) speed/max: 800/2700 MHz
Graphics: Card: Advanced Micro Devices [AMD/ATI] Redwood PRO [Radeon HD 5550/5570/5630/6510/6610/770]
Display Server: X.Org 1.19.5 drivers: ati,radeon (unloaded: modesetting,fbdev,vesa)
Resolution: 1920x1080@60.00hz
OpenGL: renderer: AMD REDWOOD (DRM 2.50.0 / 4.14.12, LLVM 4.0.1)
version: 3.3 Mesa 17.2.8
Network: Card-1: Ralink RT3090 Wireless 802.11n 1T/1R PCIe driver: rt2800pci
Card-2: Realtek RTL8101/2/6E PCIE Fast/Gigabit Ethernet controller driver: r8169
Drives: HDD Total Size: 1127.5GB (0.4% used)
Weather: Conditions: 41 F (5 C) - Scattered Clouds Time: January 28, 12:33 AM EST
Info: Processes: 180 Uptime: 1:29 Memory: 787.5/7981.2MB Client: Shell (sh) inxi: 2.3.53

It's now using Firefox Quantum 58.0 + added dosbox with package
manager + Gkrellm from source code.

The radeon graphics driver is working pretty well.

Thanks.

[amn87]

I was previously using Slacko 6.3.2 but because of screen tearing I decided to test Fatdog64 but to my disappointment the same issue persisted. Not just in video playback, but just moving any window real fast or scrolling in browser etc. I also experimented with Compiz-reloaded but the recommended settings did nothing to fix this issue. I tried switching to the nv drivers but x server will always fail to initialise. In Slacko I was successful in installing the proprietary Nvidia drivers but to no avail.
System specs : Intel Core 2 Duo @2GHz, Nvidia 9600M GT and 3GB RAM
Running Fatdog64 721.
Doesn't anybody else face this issue?
Edit: With Kodi screen tearing is almost eliminated.

[amn87]

In SFS Manager I get the error "Failed to download" and in ibiblio website 404 error. Please reupload if possible. With Kodi finally I have screen tearing free playback. But for some reason with the inbuilt Nouveau drivers the GPU always seems to run at its highest voltage (resulting in high temps) whereas with the proprietary Nv drivers in Slacko it was not the case.
Edit: The link to the guide to compiling SFS for Nvidia drivers is also not working. http://lightofdawn.org/wiki/wiki.cgi/Cr ... aDriverSFS