Fatdog64-720 and 721 Final [11 Jan 2018]

[Max Headroom]

Thanx again Jake29, Opera does start now, But Only from urxvt Terminal run-as-spot opera as instructed, But w/ Errors as seen in the attached ScreenShot & there isn't an Opera eNtry in the internet Menu ( Also How Do I Change the Default Browser 2 Opera? ), Also when I Close urxvt Terminal Opera Closes!? Otherwise We're making progress....

Ps Sorry I'm having Problems attaching the ScreenShot

Access to the file was denied

The file at http://murga-linux.com/puppy/posting.php is not readable.

It may have been removed, moved, or file permissions may be preventing access.

K

[jake29]

@Max Headroom - Ignore any errors when running Opera for now. Unless there is something obviously wrong when using Opera - those errors are most likely inconsequential.

Fatdog64 FAQ: http://distro.ibiblio.org/fatdog/web/faqs/faq.html
Default apps - http://distro.ibiblio.org/fatdog/web/faqs/defaults.html

The menu entry file should be located here: /usr/share/applications/opera.desktop
If it's not appearing in the menu, that can only be because this file is missing.

However you may want to edit this file, changing:

Code: Select all

Exec=opera

to

Code: Select all

Exec=run-as-spot opera

Starting Opera that way obviously means you no longer need to use Terminal. An alternative option is to start Opera at FatDog's startup by adding the following file (extract file first) to /root/startup/. Right-click, permissions - yes - to make it executable.

[jake29]

*double-post*

[Max Headroom]

Thanx Again Jake29, Editing the Default Browser Did the Trick, Strangely Opera has Appeared in the internet Menu, But doesn't work? But I'm Not worried since the TaskBaa Default Browser icon Works & is More Convenient anyway!

[kirk]

This means it would require the closed driver [2].

Sounds like it. I haven't used the the proprietary driver for quite a while. AMD was pretty slow at supporting newer kernels and newer Xorg servers. If you want to try it, check their release notes to see if it supports Linux-4.14 and Xorg-server-1.19.5. If it does and you want to install it, you'll need the fd64-devx_721.sfs and the kernel-source-4.14.12.sfs installed before you run AMD's installer. Might want to try this in a temporary savefile/folder in case things go south.

[john009]

Using fatdog as my primary os for the last two months ,pretty zippy to use .
l'm facing one problem though -I'm not able to connect my bluetooth keyboard 'logitech k380'.I noticed that the bluez app hasnt been updated since 2015 ,my device is from 2016.

My version is fatdog 721 updated from 720.
Can you guys help me??

[stemsee]

Fatdog64-721 kernel seems to have a configuration failing. Having manually installed to mmcblk0p1 on a cherry trail tablet it has no way to find the savefile, or even the basefs unless in initrd. Probably the driver is not builtin for accessing MTD device.

Just a heads up!

[csshin]

My Asus Zenbook UX31E comes with an SD card reader. lsusb show that it is Realtek RTS 5139. Fatdog fails to show any drive when an SD card is plugged in.

I Googled and some reported the same problem in Ubuntu and Fedora, and they solve it by installing a kmod-staging package, as mentioned in:

https://bugzilla.redhat.com/show_bug.cgi?id=748159

Could you please advise me on how can I make the SD card recognized in Fatdog 720. Thank you.

[jake29]

VLC v3.0.0 has been released: http://download.videolan.org/vlc/3.0.0/

I've tried to compile this myself, but making a proper pkgbuild is beyond me. The currently included version (v2.2.6) will occasionally hog high CPU usage, even when it's not playing anything - requiring it to be killed to resolve.

[step]

My Asus Zenbook UX31E comes with an SD card reader. lsusb show that it is Realtek RTS 5139.
https://bugzilla.redhat.com/show_bug.cgi?id=748159
...how can I make the SD card recognized in Fatdog 720. Thank you.

Is the kernel module for your card reader loaded? This could be another case of missing firmware, but I'm not sure. You could try to load the additional firmware SFS for your kernel from Control Panel > System > SFS Manager. Then you'll probably need to modprobe the correct driver name. The link you posted shows a name starting from comment #37. After confirming with lsusb that the correct module is loaded, the SD card reader should work. The link mentions card recognition problems for fat32 and other filesystems, but the link is old, so those issues are probably fixed upstream by now.
For more information on adding modules to Fatdog-720 please read the first two posts in this thread.

[smokey01]

Is anyone else having problems with the VLC plugin in Seamonkey Mail? When I double click on an attached video file it does not play. It only shows the VLC icon in the browser. This seems to be a problem with 710 720 and 721.

I normally just change the helper application to use the defaultmediaplayer but that should not be necessary.

Is there a fix?

Thanks

[chiron²]

Since Libreoffice is hardcoded into fatdog:

https://github.com/jollheef/libreoffice ... e3e4e49d6c

[jamesbond]

@Smokey01 - never tried that myself, although I use SM as email. Will try that and get back to you. Perhaps just a missing association.

@chiron: That's B.A.D We'll see what we can do about it.

EDIT: The libreoffice in the ibiblio's repository has been rebuilt using patches from upstream to fix it. The updated libreoffice will only allow http/https to work with WEBSERVICE, as noted here: https://www.libreoffice.org/about-us/se ... 2018-1055/.

[snayak]

Dear step,

I'm not too familiar with this piece of Fatdog64, but you could try another chvt. There's /usr/bin/chvt, and /bin/chvt (the busybox applet). Most likely rc.shutdown picks /usr/bin/chvt. So try if replacing "chvt" with /bin/chvt helps.

I did as suggested.
Same problem exist with /bin/chvt also.

Any other guesses?

Sincerely,
Srinivas Nayak

[jamesbond]

snayak, try this:

Add "video=SVIDEO-1:d" on boot parameter, in your bootloader config file.

This is just random shooting in the dark, let me know if it helps.

cheers!

[Atle]

Just a few minutes ago, my FatDog721 "just decided" to downgrade my Firefox from 59 til 38.5 with out my intervention. This tells me I got to stop trusting random dudes" on the internet and go for more bigger organisations like Arch or others as this scared my forever ever away from Puppyland.

I have Gslapt open and was simply watching a video at youtube, when Firefox went dead and I was able to connect using Chrome but not Firefox.

I kill firefox and restart it and BOOM I was somewhat using a browser i do not like or want the Nighly build.

I do not care about the explaination or HOW this could happen.

I just want to say that there is no way I did anything to want this or to "clikc my way to this" it just happen.

I did a "update" in Gslapt earlier today, but made sure there was no firefox updates involved, There was GTk2 and some stuff. But no Mozilla, Firefox and this is WHY i checked the files to be downloaded.

Sorry to say.

Its been ten years and FatDog as the main OS since it came, but todays experience set an end to this.

ATle

[belham2]

I do not care about the explaination or HOW this could happen.

I just want to say that there is no way I did anything to want this or to "clikc my way to this" it just happen.

I did a "update" in Gslapt earlier today, but made sure there was no firefox updates involved, There was GTk2 and some stuff. But no Mozilla, Firefox and this is WHY i checked the files to be downloaded.

Sorry to say.

Its been ten years and FatDog as the main OS since it came, but todays experience set an end to this.

ATle

ATle,

I don't even know where to begin with what you wrote. I am trying to decide if you are just an angry person, or you are a certified crazy-lunatic poster, or possibly both?

First off, you just happen to be watching a Youtube video AND you have Gslapt open? That right there tells me you are off your rocker.

Second, Fatdog did no such thing in just "randomly" downgrading your Firefox. You did that. No one else. You!! If you understood how to use Gslapt, and also what you did in originally installing your Firefox----which I bet when you personally installed your Firefox, you put it in /opt, and then stupidly thought everything was fine & ok. Well, wrong! What did you think was going to happen when you did a Gslapt update today?? You think you actually "unchecked" something? I've got news for you---you DID NOT uncheck anything.

Dam#$, before you come on here blaming people (the Fatdog Team), people who actually take time out of their personal lives to construct, maintain and put out a great little distro that Fatdog is---a distro that has been, and still is, rock-solid for years now---do us all a favor & take a deep breath & stop yourself. If you can't, do us a bigger favor and NEVER post here again.

On murga-linux, there is no place for such attitude and behavior you display. 10 years a user? What an ungrateful person you are. You should be ashamed of yourself.

In all the years (going on 9 now) I have been here, it never ceases to amaze me how people blame others for their own lack of understanding and/or stupidity (or both).

[SFR]

I see, when I shutdown Fatdog 720, sometimes it immediately shows me "Fatdog is shutting down...", but many times it shows me this message after a long time. Till then, screen is black/blank and a single cursor on left top.

Something like this happened to me, but no more than 4-5 times, ever.
IIRC the "fix" was to switch to vt1 manually (Ctrl+Alt+F1) - the shutdown process should continue after that.

Greetings!

[TyroBGinner]

Pardon my ignorance, but I am too lazy to research this in detail.

I need to disable the uas driver in fatdog or activate the disable uas quirk in the usb-storage driver. I looked inside the massive initrd file and saw that there is a blacklist file that already specifies uas. The file is /etc/modprobe.d/initrd.conf, I think...or it is something like that. The .conf file contains only ub and uas. In the loaded fatdog OS, the blackilist file appears in the same place in the filesystem.

I also put in a blacklist_uas.conf file that contains the "options usb-storage xxxx:xxxx:u" line to activate the 'u' quirk. This method works in ubuntu. Of course, I used the rebuild initrd script to repackage the modified initrd and replace the original initrd.

The problem is that the uas driver still loads in response to my device. The kernel messages confirm this and make no mention of uas being blacklisted and usb-storage being used in its place. What is wrong? Does the blacklist file refer only to the booting process and there is needed a separate file for the loaded OS?

[snayak]

@ SFR:

IIRC the "fix" was to switch to vt1 manually (Ctrl+Alt+F1) - the shutdown process should continue after that.

Thanks for reporting the observation. Do you mean, first we have to manually go to vt1 and then using CLI we have to shutdown?

@ jamesbond:

I have added "video=SVIDEO-1:d" on boot parameter, in my bootloader config file. In last three shutdowns I haven't seen delay. Will reconfirm after some more observation. By the way what does this parameter say to kernel? Did some reading around it, but didn't get exact info on this.