Fatdog64-700/701 [April 22 2015] [CLOSED]

[gcmartin]

I assume you have added a Bluetooth adapter on the PC. A USB wireless adapter is cheaper than most blues.

In any event, if I understand you correctly, you have smartPhone from some Telco that has disabled your ability to use your Wifi and your Bluetooth to your satisfaction.

Maybe time to consider rooting so that you have some additional local controls that have been turned off, but there. What version of Android/OS in on that device?

[venkat2015]

I assume you have added a Bluetooth adapter on the PC. A USB wireless adapter is cheaper than most blues.

In any event, if I understand you correctly, you have smartPhone from some Telco that has disabled your ability to use your Wifi and your Bluetooth to your satisfaction.

Maybe time to consider rooting so that you have some additional local controls that have been turned off, but there. What version of Android/OS in on that device?

Yes I am using a usb bluetooth dongle. The Android version is 4.4.2. I do not think it is the telco because if I remove the sim from the android phone and put it in a samsung java phone I am able to do a bluetooth DUN. In fact that is how I am posting this msg. Wired tethering also works with the java phone. Getting a usb wifi dongle is no big deal. But where ever I read they say hotspot takes more battery power and also the unit gets very hot whereas bluetooth consumes less power. The phone battery charge might last a bit longer I guess. I am taking this as a challenge to see whether I can get this fixed with puppy community’s help otherwise I have to live with the hazel of taking the sim out and putting in the java phone.

[WillM]

Fatdog64 wallpaper;
https://drive.google.com/file/d/0B4wlew ... sp=sharing

[step]

fglrx module replaced, still with issues. Someone can explain this?

I'm using ATI driver 340.76 for an Nvidia Quadro FX 580 on Fatdog 701 and it works for me. I *think* that I'm using the driver from Fatdog's repo download link but I can't be sure, because I didn't install it with gslapt but I simply unpacked and copied the files in their right places. Still I'm pretty sure I use the official driver. ( I had compiled an earlier driver version on Fatdog 700 when the official package wasn't available from the repo. )
The only customization I did was in the way the driver is loaded:
this is /etc/modprobe.d/nvidia-installer-disable-nouveau.conf in my FD

Code: Select all

# generated by nvidia-installer
blacklist nouveau
options nouveau modeset=0
# 20150402 step: now noveau is blacklisted in the bootloader entry
# by adding blacklist=nouveau to the kernel line

The last comment is mine. So I appended blacklist=nouveau to the bootloader kernel line.
Eveything I tried works here. Admittedly, I'm not a GPU expert or a gamer, so my use isn't stressing the driver or the GPU. I did get CUDA working, but some of the typical CUDA test tools failed - I don't recall the details - though the real programs where I needed CUDA did work. I'm not using CUDA these days, though.

[Atle]

Struggling to remaster the Fatdog+ Scribus 1.5 spinnoff...

I read in this thread somewhere that its important to save the files to a Ext4 partition, but apart from that, is there any other things concerning remastering that one should know?

My remaster iso ended at somewhat 550mb and when i try to boot it, it says i do not have sufficient with RAM. I choose the "humongous" intrd option.

I shall retry and retry, but if there is anyone out there that have succeeded in remastering and then "discovered" some tricks, please share them:-)


Atle

[rufwoof]

Confused!!!

My old 64bit PC died a while back and I'm using a even older 32 bit in the interim. I grub4dos boot and accidentally today booted FatDog by selecting the wrong grub4dos menu item - a remnant from my 64 bit machine.... and it all started up fine!

At least I thought that old box is 32 bit ???

I'm using a 42" TV VGA for display and setting screen resolution to 1920x1080 and most things are fine. However if I maximise browser (or a window) it seems to be limited to a certain size. Reducing the window size and dragging to expand (bottom right corner) and I can expand to full screen. MT screen capture also seems to capture the full screen OK

[quirkian2new]

@Atle, your remaster iso ended at somewhat 550mb and fails to boot. I also had similar experience, and i feel that a huge initrd usually fails to boot if size is over 450mb. So when it is expected to be 450mb or more, i will remaster with small initrd. You can use boot option base2ram=yes with small initrd.

[eowens2]

I have installed Thunderbird 31.5.0-spot-x86_64 from the Gslapt Package Manager on my Fatdog64 701, and the package works perfectly well doing everything I expect Thunderbird to do except for one thing.

It will not connect to the Thunderbird update server. It keeps trying and trying, but the connection inever occurs.

Anyone know how to make it connect?

[step]

1. Does Fatdog6 provide a key combo to switch the current xwin session to the side and start a new system console login process?

I'd like to ask question #1 because this happened to me today, but I don't know how I got there! It's quite a mistery to me.

2. When you log in the new console process, is there a way to "merge it" with the xwin session that is still running on the side? Essentially, I'm asking if there's a way to get back the xwin desktop without resorting to killing it and all its sub-processes.

[drunkjedi]

Hi step,
I am quite new to Linux, so I might not have understood what you asked.
But, in fatdog, I got to other console (I believe it's called tty or something) by pressing ctrl+alt+Fn. ( where n = 1, 2, 3, ... 7 is the limit I think).

Then in that command session , login and start xwin.
Pressing appropriate Fn button with ctrl+alt, will take me back to previous graphical desktop, or other consoles.

Hope you are asking this.

[gcmartin]

Number of years back, @JamesBond/@Kirk, cant remember which, provided me with a simple manner to start a separate X desktop such that I had 2 X desktops running, each with all it glory, independent of each other. This was NOT a virtual depiction, it was a 2nd 'real' Xdesktop with WM and all the same desktop expectation one gets from a single, normal desktop.

The NAS which contains it is offline, but as soon as I can find it, I will post it.

[step]

Number of years back, @JamesBond/@Kirk, cant remember which, provided me with a simple manner to start a separate X desktop such that I had 2 X desktops running, each with all it glory, independent of each other. This was NOT a virtual depiction, it was a 2nd 'real' Xdesktop with WM and all the same desktop expectation one gets from a single, normal desktop.

The NAS which contains it is offline, but as soon as I can find it, I will post it.

@drunkjedi, thanks. You fully aswered my question #1. Q #2 remains unanswered, though I suspect that the answer is "it can't be done.".

@gcmartin, I think drunkjedi's Ctrl+Alt+Fn solution is enough to start different, normal desktops in parallel. Of course, a single monitor can only display one of those desktops at the time.

[jamesbond]

@step - for your second question: use "reptyr" or "conspy".

@gcmartin - that feature is still available today, just launch User Manager (from Control Panel), highlight a user, and click "Launch a new desktop for user". If you don't have a user yet then create a new one.

@willm - thanks, I will add it to the wallpaper-collection.sfs

@all - I'll get back to your questions and comments later.

[Gobbi]

Right click on a drive icon --> App dir 'drive' --> Set Icon... and I can change the icon of a specific drive (partition). But it is not persistent , the first time I restart X the icon fall back to the system one.
I tried to add a condition to /usr/sbin/fatdog-drive-icon-refresh-icon.sh :

mountpoint=$(get_mount_point $1)
get_icon_dir ${1##*/}
if [$(get_icon_dir ${1##*/}) == /tmp/fatdog-drive-icons.root/md0]; then
iconfile=/usr/share/pixmaps/revodrive/.Diricon
else
iconfile=$icondir/.DirIcon
[ ! -e $iconfile ] && exit

It didn't work .
Is there a way to achieve this
Any help would be appreciated .

[step]

@step - for your second question: use "reptyr" or "conspy".

Thanks jamesbond, conspy is closer to what I had in mind. I built a package of version 1.13 (find it with gslapt).

[jamesbond]

@step - no worries. Fatdog comes with rudimentary busybox version of conspy - the full-sized one you compiled must have more features, thanks for sharing.
@Gobbi - look at function create_rox_icon_file() in /usr/sbin/fatdog-drive-icon-roxlib.sh; that's the one you want to modify.
@eowens: the Thunderbird package is a contributed package I think, and is re-packaged from official binary, so in theory update should work. It probably doesn't work because it is running as spot and the package is installed as root - but that's just my guess for now.

[step]

mountpoint=$(get_mount_point $1)
get_icon_dir ${1##*/}
if [$(get_icon_dir ${1##*/}) == /tmp/fatdog-drive-icons.root/md0]; then
iconfile=/usr/share/pixmaps/revodrive/.Diricon
else
iconfile=$icondir/.DirIcon
[ ! -e $iconfile ] && exit

Interesting, on my system drive icons are located in /tmp/fatdog-drive-icons.root.373e3db/. Perhaps the test fails because the path doesn't exist. The test syntax looks a bit strange, too. Try something like (UNTESTED):

Code: Select all

mountpoint=$(get_mount_point $1)
get_icon_dir ${1##*/}
case $icondir in
  /tmp/fatdog-drive-icons*/md0)
    iconfile=/usr/share/pixmaps/revodrive/.Diricon ;;
  *)
    iconfile=$icondir/.DirIcon ;;
esac
[ ! -e $iconfile ] && exit

Sorry I don't have time to test the above code, I hope it can still help you.

[Gobbi]

Thank you @step for trying to help . It didn't work though ... My syntax is odd indeed , because I'm more familiar with C language than bash .
Thank you @jamesbond for pointing to the right direction . Drive icons are created in /usr/sbin/fatdog-drive-icon-roxlib.sh . I added :
md*) DRIVE_TYPE=md ;;
to the line 45 in /usr/sbin/fatdog-drive-icon-udev-handler.sh - creating a new DRIVE_TYPE . I also added :
md*) DRVICON=md48.png ;;
to the line 93 in /usr/sbin/fatdog-drive-icon-roxlib.sh - assigning a chosen icon to the new created DRIVE_TYPE .
Now the drive icons are persistent over restart X .

----------
EDIT : I also tried sdc1 instead of md* and md with a different icon from /usr/share/pixmaps/themes/puppy48/ and it works too .
It does not make permanent the ROX-Filer right click option , it only works at boot time with that icon acting like a system icon . But , IT WORKS .

EDIT 2 : The 2 RAID0 members of md0 are shown as sdc1 and sdb1 on my desktop . I don't want to see them there . For not seeing a drive on the desktop (sdc1 for example) I added :
rm -f /tmp/udev-fatdog-drive-icon/devices/sdc1 to the line 25 in /usr/sbin/fatdog-drive-icon-frontend.sh . Using Pmount , the drive can still be mounted and searched .

[Atle]

still struggling with remastering the "Scribus Fatdog... Its a 530 mb remaster and i have tried small and big init. same boot problem. I use the same usb that i reformat for the purpose when booting.

I use the same source ISO. And it works fine before i remaster...

i use ext4 file system

first i struggle with vesamenu.c32

the remaster would not boot. that was when i worked from a savefile...

then i try to remaster in ram only boot from the original 701. Gaining experience from several attempts, i now feel ok with failures.

But after trying the entire process in ram only with no save file, i get beyond the versamenu challenge and drops closer to target, now back to the ram problem.

having 6 gb of ram and a intel 5 processor i do not feel that the hardware is the problem, as the iso is "just" 690mb. why its growing like this is a mystery as i use the same source files. I am from a nation that does moonlandings on earth, so that might explain it.

So my question comes down to this:

Is it better to remaster with a savefile, a save to directory or in pure ram?



Best

Atle

[jamesbond]

@Atle - I still remember I need to do the scribus with the file associations and desktop file; L18L give one example but really that should come from me (inside the package). I however need you to tell me the list of files to be associated with scribus (their file extensions).

As for the remaster, let me get to you and do a few tests myself. You seem to be doing everything all right; and in general with a huge initrd an ISO size can grow to up to 25% of total RAM before you start to hit problems. With small initrd there is no limit. Your machine spec also sounds fine to me. Only one thing - if you do a remaster and specify a location other than /tmp, please make sure that your target is also a Linux filesystem. It can't be FAT or NTFS.

@eowens2: I installed thunderbird-3.1.5 spot and when I launched "Help - About" I can see that it offers me a new download. I can't get the auto-update feature to run, perhaps Mozilla kill the update server already?