Fatdog64-720 and 721 Final [11 Jan 2018]

[Billtoo]

@Billtoo, thanks for the report. Was wifi working OOTB for the "slow bios" option, or did you need to add a driver?
On a side note, I like that you add local weather conditions to your reports!

@step

I wanted to make sure that wireless was supported OOTB when using the
"slow bios" option so I booted the DVD using the option and setup wireless in the
control panel then rebooted after installing Firefox Quantum 58.0.1
creating the savefile on the hard drive.
After rebooting to the desktop I needed to configure wireless once
again in the control panel.
I don't have any sfs files loaded yet so wireless is supported OOTB,
don't have to wait for anything to load from a flash drive either so
this is working better that my first attempt.

System: Host: fatdog64-e81 Kernel: 4.14.12 x86_64 bits: 64 Desktop: Openbox 3.5.2 Distro: Fatdog64 Linux 721
Machine: Device: desktop System: ACER product: Aspire M5620 v: R01-A4 serial: PTS860X0348050CF642700
Mobo: ACER model: G33T-AM v: 1.0 serial: 00000000 BIOS: American Megatrends v: R01-A4 date: 12/19/2007
Battery hidpp__0: charge: N/A condition: NA/NA Wh
hidpp__1: charge: N/A condition: NA/NA Wh
CPU: Quad core Intel Core2 Quad Q6600 (-MCP-) speed/max: 1603/2403 MHz
Graphics: Card: NVIDIA GF108 [GeForce GT 430]
Display Server: X.Org 1.19.5 drivers: nouveau (unloaded: modesetting,fbdev,nv,vesa)
Resolution: 1920x1080@60.00hz, 1920x1080@60.00hz
OpenGL: renderer: NVC1 version: 4.3 Mesa 17.2.8
Network: Card-1: Intel 82566DC-2 Gigabit Network Connection driver: e1000e
Card-2: D-Link System AirPlus G DWL-G122 Wireless Adapter(rev.C1) [Ralink RT2571W] driver: rt73usb
Drives: HDD Total Size: 500.1GB (2.2% used)
Weather: Conditions: 25 F (-4 C) - Overcast Time: January 31, 4:40 PM EST
Info: Processes: 161 Uptime: 13 min Memory: 606.4/7981.0MB Client: Shell (sh) inxi: 2.3.56

I will continue to setup this install now.

Thanks

EDIT: I finished the setup, Ubuntu is on the hard drive and it didn't interfere with that (still boots) and Windows is long gone.
It's working well,

[Gordie]

@Gordie, perhaps you need to add a kernel module specific to your adapter. In brief, connect to the Internet somehow, start SFS Manager from Control Panel > System, download and load the "additional firmware SFS", depmod the kernel module of your interest (this might be a bit difficult if are inexperienced with depmod), test wifi by clicking "Restart Connection" from the right click menu of the wpa_gui icon in the tray (read Fatdog's Networking help topic for more info). If wifi works then you can make the changes permanent by extracting from the SFS the module files of your interest and adding them to the file system.
Please report the make and model of your wireless adapter so we can add it to the ISO. To keep Fatdog slim the ISO doesn't include all possible firmware but just a selection of mainstream hardware. Occasionally we need to tune the selection. This is better explained in the second post in this thread.
Other people before you have had this problem, so you can search this thread for more tips and additional instructions.

Network controller [0280]: Intel Corporation Centrino Ultimate-N 6300 [8086:4238] (rev 35)
• Kernel Driver: iwlwifi
• Description: Intel(R) Wireless WiFi driver for Linux

[Wognath]

vivaldi-stable 1.14.1077.41 fails to run (opens a gray window with the V logo only) in Fatdog 721 with the message

Code: Select all

# run-as-spot /opt/vivaldi/vivaldi-bin
[10797:10849:0201/082534.460020:ERROR:bus.cc(394)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[10797:10797:0201/082534.734602:ERROR:gpu_process_transport_factory.cc(1009)] Lost UI shared context.

I see no mention of this in Vivaldi forum, so I guess it's a peculiarity of FD. Thanks in advance for any suggestions.

sfs from the deb. gtk3 package from the repo installed.

EDIT: I had said that Vivaldi-stable_1.13.1008.44 runs with just 4 libs from gtk3 pkg, and Opera_50.0.2762.67 runs with those plus libnotify.so.4. However, some fairly common actions cause them to crash. They appear to be ok with the full gtk3 package.

[LateAdopter]

Hello Wognath

I ran vivaldi-stable 1.14.1077.41 on Xenialpup64 for a couple of minutes before I switched back to 1.11. It seems to be far from finished.
It wouldn't display history and it ignored some settings that were present in the settings menu.

I guess there must have been some last minute changes in Chromium that Vivaldi haven't accommodated yet.

I won't try it on FD64 until it's working on Xenialpup64

[snayak]

Thanks step for your guide.

I did a debug of rc.shutdown file.

Coded like this...

Code: Select all

echo $(date +%F.%T) >> /aufs/devsave/shutdown.log
chvt 1
echo $(date +%F.%T) >> /aufs/devsave/shutdown.log

Found that chvt is taking a long time... not always, but sometime. So chvt is the culprit for slow shutdown.

Tried several chvt on my terminal. It killed my puppy.

Any way out?

Sincerely,
Srinivas Nayak

[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.

[FanDog]

hello, hoping this is the place to ask:

how hard would it be to get openCL up and running on FatDog64?

I once done it on gentoo, same machine, so it can be done. However I think we here use the open source driver, which I thought already had openCL working but, according to [1], is still WIP for my card (R9 270).

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

I also read this[3], but doesn't say much, basically just installing the driver should be enough.

I tried "pip install pyopencl", but after going quite far into the installation, complained about not finding the headers for CL/cl.h (which I suppose would also be solved by the right drivers?)


Thanks.

Refs:

[1] S.Islands, on the table here: https://wiki.freedesktop.org/xorg/Radeo ... /#index1h2

[2] " Thus, the closed-source driver is mostly useful to users who want to [...], or want to run anything that uses Vulkan with advanced shaders, or want to fully exploit OpenCL. " @ https://wiki.gentoo.org/wiki/AMDGPU-PRO

[3] https://wiki.tiker.net/OpenCLHowTo

[Wognath]

LateAdopter, thanks for the information. The gray screen issue has now been reported by several people in the Vivaldi blog. One moderator says it's a bug in Chromium 64. I can wait while they fix it since 1.13 works well.

[Max Headroom]

Please Howto install Opera Browser, that's Not in the Package Manager, So when I Downloaded it from opera.com, I got a .deb file that doesn't play well w/ Fatdog64, then I noticed that I could Converter it 2 a Gslapt Happy Format, But that didn't work either, Then I Noticed that I could Convert that 2 a SFS Package,... But Alas that didn't work Either!

How Hard could it be?

:)K

[jake29]

Max Headroom - libnotify 0.7.7 is required and available via Gslapt.

[Max Headroom]

Thanx Jake29, 4 your Reply, I've installed the libnotify 0.7.7 as instructed, But Alas still No joy... Wot am I Missing Please?

K

[jake29]

Thanx Jake29, 4 your Reply, I've installed the libnotify 0.7.7 as instructed, But Alas still No joy... Wot am I Missing Please?

K

In Terminal:

Code: Select all

 run-as-spot opera

If unsuccessful, go to actual folder (see above) and run the command there.

And as last resort, in Terminal:

Code: Select all

 opera --no-sandbox

Note: You also need to install (for video playback) ffmpeg-codecs available here: https://repo.herecura.eu/herecura/x86_64/
Extract libffmpeg.so to usr/lib/x86_64-linux-gnu/opera/lib_extra/

[step]

@Max Headroom, in addition to what jake29 already well said, this is the list of packages that I installed in order to get Opera working
at-spi2-atk-2.18.1-x86_64-1
at-spi2-core-2.18.3-x86_64-1
gtk3-3.18.7-x86_64-1
libnspr-4.17-x86_64-1
libnss-3.33-x86_64-1
libnotify-0.7.7-x86_64-1
You can install them from Fatdog64 Control Panel > System >Gslapt Package Manager.

After the installation open a terminal window and run the following commands

chown root.root /usr/lib/x86_64-linux-gnu/opera/opera_sandbox
chmod 4755 /usr/lib/x86_64-linux-gnu/opera/opera_sandbox

Note: commands adapted from my notes for opera-developer. I didn't actually test them for opera, but they should be the same.

[Max Headroom]

Thanx Step 4 your Help

I think I've installed all the Packages as instructed ( I only say I think because of How Weird / Unfamiliar Gslapt Behaves Compared 2 Puppy Package Manager or Synaptic )

So Assuming the Packages aRe installed by Gslapt

When I Typed chown root.root /usr/lib/x86_64-linux-gnu/opera/opera_sandbox
chown: cannot access '/usr/lib/x86_64-linux-gnu/opera/opera_sandbox': No such file or directory

or without the Space after root

chown root.root/usr/lib/x86_64-linux-gnu/opera/opera_sandbox
chown: missing operand after 'root.root/usr/lib/x86_64-linux-gnu/opera/opera_sandbox'
Try 'chown --help' for more infomation.

I don't understand what operand is, so I di an iNet Search & Red a Wiki about it, But it still doesn't Compute ie. Makes No sCents!

I've Red the chown --help & I'm still Confused...

I'm Sorry if I'm a Pain!

K

[jake29]

@Max Headroom - If /usr/lib/x86_64-linux-gnu/opera/ does not exist, then Opera has not been installed. Maybe you should start again with the .deb. Right-click on the .deb - Convert to Fatdog Package Format and install that new file.

[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.