Fatdog64-720 and 721 Final [11 Jan 2018]

[jamesbond]

It works fine. But you know the mac users ... should be done automatically!

Lol

I was actually wondering where should I put in FD a call to grep kernel messages for PowerBookPro and change the permissions of 99-disable-spurious-gpe. /sbin/init or is too early?

The correct place would in in /etc/rc.d/rc.platform (this is where we put that set-hidpi-font-size too --- it's the same place where I put your font-size-change script for OLPC in FatdogArm). But how early does the kernel spits out that message? Or is there any other way to get that info? (Using dmidecode, perhaps?) We don't want rc.platform goes into a loop waiting for that message.

Maybe is a malformed package of mine but this one although has an entry in /var/log/packages does not show up nor I can remove it with slapt-get. The new one I made for 4.14.6 (just change module and up'ed version to 2) also does not show.

Ok, I will check. Did you use "makepkg" to build it?

[mavrothal]

The correct place would in in /etc/rc.d/rc.platform

I tried to put in

Code: Select all

[ "$(dmesg | grep -i macbookpro)" != "" ] && chmod 755 /etc/init.d/99-disable-spurious-gpe

(or grep directly /var/log/messages) but it would appear that is too early.

<Edit>: Hm... I guess rc.platform does not run in every boot. (Is it only in the first one?)
Putting the code just after the rc.platform call in rc.sysinit works fine.</Edit>

Did you use "makepkg" to build it?

Yes

[jamesbond]

<Edit>: Hm... I guess rc.platform does not run in every boot. (Is it only in the first one?)

Yes, indeed. rc.platform is supposed to perform "adjustments" for different platforms, which would be made permanent after you have a savefile/savedir; thus it only run once.

Putting the code just after the rc.platform call in rc.sysinit works fine.</Edit>

If it works there, it would work in rc.platform too. I'll have it included in rc.platform.

Did you use "makepkg" to build it?

Yes

In short - the package naming convention is incorrect, see: http://distro.ibiblio.org/fatdog/web/fa ... ckage.html (I just realised there is one mistake in that document - while Slackware packages don't support uninstall script, Fatdog packages do support uninstall script.

[step]

@mavrothal
fyi, quick package test commands after installpkg:
slapt-get --filelist PkgName
slapt-get --search PkgName (it's grepped, actually)
slapt-get --installed | grep ...

[mavrothal]

the package naming convention is incorrect, see: http://distro.ibiblio.org/fatdog/web/fa ... ckage.html

Indeed.
The new one works fine installing and uninstalling.

[don570]

Btw, check out mhWaveEdit, the labels should work now.

Great! I downloaded the package
http://distro.ibiblio.org/fatdog/packag ... 6_64-1.txz
and installed in fatdog710 and it worked in that version of fatdog as well.
_____________________________________________________

[dr. Dan]

Update:
I found this post in the Contributed Packages thread:
* http://www.murga-linux.com/puppy/viewto ... 830#835830 An alternative menu system for Fatdog64-700 Control Panel

My bad. I installed that package without realizing it.

This is ideal but difficult to do in reality. If we could, we would have already implemented this as an automated "upgrade" process (like Puppy does) for old savefile. I remember having a discussion internally within the team about this, and the conclusion at that time was: it's too much error prone to be useful. Things may change, but for now, that's what it is.

Why is this difficult? Because it depends on various factors beyond our control: what you install (which may be a package from the repo, a package from contrib repo, your own "./configure && make && make install", also depends on what sort of data you keep, how you keep it ... and it also depends on things that we do control but difficult (or very tedious) to keep track - library versions, updated configuration files, updated scripts.

I appreciate the work, and the thought, of all of the above. I was thinking about personal, non-system data. I can generally figure things out, but if I don't have to reinvent the wheel, I am happy to copy someone else's wheel. FWIW, I guess that most users, new or otherwise, will not see this forum, or will only see it after a significant time using Fatdog64, and trying to accomplish whatever they want. Adding to the help files from the large store of knowledge contained here will help those new users, growing the user base, and perhaps leading to more pressure from more users like me who want so much, because Fatdog64 already does so much.
Happy Christmas all!

[step]

@drDan
Thank you, happy holidays to you too.
If you're interested in a menu-based control panel for 71x and 720 you could try https://github.com/step-/scripts-to-go/ ... menu2-fdcp.
Click [Raw]; right-click and save page as /usr/bin/gmenu2-fdcp; set file gmenu2-fdcp executable; click icon to run. You may want to set a hotkey for it with sven.

[Flash]

I downloaded the iso, burned it to a DVD and tried to boot it. It got to where I suppose the desktop should have shown up, but instead, it booted all over again. I guess it would have kept it up indefinitely.

[kirk]

I downloaded the iso, burned it to a DVD and tried to boot it. It got to where I suppose the desktop should have shown up, but instead, it booted all over again. I guess it would have kept it up indefinitely.

I hadn't tried a DVD for a while, so burned one. It works on my laptop. That said, check the md5sum and verify the burn. With a new kernel they fix things and break others, so kernel would be another guess. Other than that, That's all I can think of, I'll let the other guys chime in if they can think of anything else.


BUG ALERT: The Samba sever shares the Downloads folder read-only. This is due to spot not being a valid Samba user. See the third post of this thread for the solution,

[kirk]

Flash,
If your md5sum checks out and the burn is verified, I've uploaded an ISO with kernel 4.12.13. It's here if you want to give it a go.

[jamesbond]

@Flash - alternatively please boot with "pfix=xorgwizard". See if you can get as far to see the xorgwizard without getting the boot-loop. If you manage this far, choose the correct video driver for your system and see if you can get to desktop.

[don570]

I noticed something odd with fatdog 720, that I haven't seen before when using commands.

When using the 'ps' command or 'top' command to make a list of running
processes

Code: Select all

root         1  2.6  0.7  51396  7644 ?        Ss   02:02   0:03 /usr/lib/systemd/systemd --switched-root --system --deserialize 23
root      1249  2.6  3.0 355800 30896 tty1     Rsl+ 02:02   0:02 /usr/bin/X -background none :0 vt01 -nolisten tcp
root       508  2.4  1.6 248488 16776 ?        Ss   02:02   0:03 /usr/bin/python /usr/sbin/firewalld --nofork

but with fatdog 720 just the name of the app running is given -- not the options or the file that is loaded.

I need this info!!

For instance when pmusic is launched,
it also launches ffmpeg -i /path/to/file

and this is normally shown in ps output.

___________________________________________

[Gordie]

I dd'd the iso to a usb flash stick. It booted perfectly BUT, like all the rest of the updates since the 710 release there is no detecting my wifi card on my Lenovo W510 laptop so this release is of no use to me

[jamesbond]

@don570:

Code: Select all

ps -ef w

Should do the trick.

@Gordie: Please launch Control Panel -> Utilities -> (then scroll down) -> Bug Report Info Collector. Then pass the report to us.

EDIT: Gordie - the problem is probably missing firmware. Will post a package that contains some firmware for you to test.

EDIT2: I have uploaded an SFS that contains all the known firmware, as of today, here: http://distro.ibiblio.org/fatdog/sfs/72 ... 017.12.sfs. You can get this from the SFS Manager too. You can use this with any kernel (Fatdog or Puppy) - provided that this is loaded at boot time.

Alternatively, you can download and click this SFS to view its contents and copy only the firmware that you need. Your wifi I think needs these: iwlwifi-9000-pu-a0-jf-b0-34.ucode, iwlwifi-9000-pu-b0-jf-b0-34.ucode, and iwlwifi-9000-pu-a0-jf-a0-34.ucode. Copy these 3 files from the SFS above and put them under /lib/firmware. Then re-boot. See if you can see your wifi.

If that still doesn't work, please send me the output of Bug Report Info Collector.

[stemsee]

So trying to boot frugal from various filesystems results in this error as vmlinuz tries to load initrd

Code: Select all

 error:couldn't find suitable memory target

My hardware is a lenovo flex15 pro i7 laptop. 1TB HDD, 16GB ram

[jamesbond]

So trying to boot frugal from various filesystems results in this error as vmlinuz tries to load initrd

Code: Select all

 error:couldn't find suitable memory target

That's a grub2 error code. How did you install grub2? Or perhaps, what version of grub2 did you install it?
I suspect it has something to do with this: http://www.murga-linux.com/puppy/viewtopic.php?t=109891

My hardware is a lenovo flex15 pro i7 laptop. 1TB HDD, 16GB ram

That should be more than enough to run Fatdog.

[fatdog]

Updated information about firmware in the second post: http://murga-linux.com/puppy/viewtopic. ... 929#977929. Especially, we have uploaded an SFS that contains all the firmware known to the mainline Linux kernel.

[ljward]

Hey guys, thanks for the new release! I just wanted to suggest adding the loading of the virtio kernel modules inside the init script. I got FatDog720 running on FreeBSD inside a Bhyve virtual machine booting with UEFI using the VirtioIO drivers for networking and storage. Initially I was able to save the save file/folder to a virtual disk such as /dev/vda2, but when I reboot it does not detect the virtual disk because the init script inside the initrd does not load the virtio kernel modules so it failed to find my savefile. I added loading the virtio modules to the init script and rebuilt the initrd and now everything works fine and I am able to use my save file/folder stored on a virtual disk.

[Sage]

uploaded an SFS that contains all the firmware known to the mainline Linux kernel

SiS900 NIC? No panic, it's gonna take me a century or two to fathom a FULL installation which is central to my continuing use of FD64. Doubting I have the skills however, despite masses of advice from jb...