Fatdog64-600b1
Random Wallpaper Changer
Random Wallpaper Changer version 1.3 works fine in Fatdog64-600.
Re: loading sfs permanently
Yeah, I hadn't ticked the box to make it persistent. In other puppies it automatically became persistent if loaded on the fly.shinobar wrote:Maybe we need to load the sfs from the control panel and make a check on the 'permanent'.smokey01 wrote:I have also noticed loading the fd64-devx_600.sfs is not persistent.
So many little, but subtle changes in Fatdog.
Re: getnvidia-0.2-64
Actually, does not workshinobar wrote:getnvidia-0.2-64.pet, NVIDIA driver installer/PET/SFS builder.
It purges the nvouveau driver by listing it up on the blaklist, /etc/modprobe.d/blacklist,conf:
Code: Select all
blacklist nouveau
EDIT: the /etc/modprobe.d/blacklist,conf is cleared after boot. Who and when?
Last edited by shinobar on Sun 24 Jun 2012, 09:51, edited 1 time in total.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
Re: getnvidia-0.2-64
You did better than me, I couldn't even get graphics to work after I tried. Had to delete the savefile and start again.shinobar wrote:Actually, does not workshinobar wrote:getnvidia-0.2-64.pet, NVIDIA driver installer/PET/SFS builder.
It purges the nvouveau driver by listing it up on the blaklist, /etc/modprobe.d/blacklist,conf:It seems success for the first time, but the next boot, the nouveau revives. Why?Code: Select all
blacklist nouveau
Did you get Recorder to work in FatDog?
Treating PET
yes, woks, I had no idea to double-click for checking the mark.jamesbond wrote:1. Choose the package you want to uninstall (double-click or press Enter)
2. Click uninstall
OK, I know SFS incompatibility with the kernel, but this is the first time to see incompatible PET.jamesbond wrote:600 uses xz compression for the pet.
BTW, how to make pet on Fatdog64? The dir2pet does not work because of the bug in the petspec.
/usr/bin/petspec at line 169 wrote: <default>${DEF_compiledrelease}</default><variable>DB_compiledrelease</variable> </entry>
Fix wrote: <default>"${DEF_compiledrelease}"</default><variable>DB_compiledrelease</variable> </entry>
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
Re: getnvidia-0.2-64
Right.smokey01 wrote:I couldn't even get graphics to work after I tried. Had to delete the savefile and start again.
If i cannot get the desktop at boot, i type next 2 commands on console:
Code: Select all
# rm /etc/X11/xorg.conf
# xwin
The Keyboard localization on the control panel only effective with X.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
Sylvander, as I get it they set it up that way.Sylvander wrote:Umm, how's that?jamesbond wrote:Well, you are already running as root,
I'm not aware that I changed to running as root.
How did I do it do you think?
Seamonkey and many other applications run under user Spot.
But the x or GUI desktop is root? As you know I am a true noob I only guess.
One get automatically logged in as root for X?
For to not be root you most likely need to create a user using root
and then log into that user after boot? Am I right?
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
Re: getnvidia-0.2-64
Yes.smokey01 wrote:Did you get Recorder to work in FatDog?
But i think these recorders need more function, at least to specify the saving folder because the /usr/local/recorder folder is on the aufs and easily filled up under frugal installations.
Another impression, the icon on the buttons are better to be the same of the gtk stock icons, gtk-media-record, gtk-media stop, and etc. That is, red circle for record and white box for stop.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
Re: getnvidia-0.2-64
I thought of saving the file to /mnt/home but that's not foolproof either. It only ever makes one file. Each time you create a new recording it overwrites the old one. It took a little while to work out how to do that. Files need to be moved after each recording that's why I made the window pop up to make it easy to find.shinobar wrote:Yes.smokey01 wrote:Did you get Recorder to work in FatDog?
But i think these recorders need more function, at least to specify the saving folder because the /usr/local/recorder folder is on the aufs and easily filled up under frugal installations.
Another impression, the icon on the buttons are better to be the same of the gtk stock icons, gtk-media-record, gtk-media stop, and etc. That is, red circle for record and white box for stop.
I guess icons are a personal choice. They are easy to change. I like to keep things really simple but functional.
Feel free to make any changes you want.
Pretty hard to get simpler than this, Start and Stop, job done.
Cheers
Re: Treating PET
I just used dir2pet and it worked. Maybe it was fixed in B1.shinobar wrote:yes, woks, I had no idea to double-click for checking the mark.jamesbond wrote:1. Choose the package you want to uninstall (double-click or press Enter)
2. Click uninstall
OK, I know SFS incompatibility with the kernel, but this is the first time to see incompatible PET.jamesbond wrote:600 uses xz compression for the pet.
BTW, how to make pet on Fatdog64? The dir2pet does not work because of the bug in the petspec./usr/bin/petspec at line 169 wrote: <default>${DEF_compiledrelease}</default><variable>DB_compiledrelease</variable> </entry>Fix wrote: <default>"${DEF_compiledrelease}"</default><variable>DB_compiledrelease</variable> </entry>
On Lupu 528 I use the Bacon Recorder. Easy to use.
Would that one be easy to make a FatDog64-bit compatible version of?
"at least to specify the saving folder because the /usr/local/recorder folder
is on the aufs and easily filled up under frugal installations. "
That is what Bacon Recorder have taken care of allowing that one place the
saved file on /home or /root or what to name it. Directly on the HardDisk
Would that one be easy to make a FatDog64-bit compatible version of?
"at least to specify the saving folder because the /usr/local/recorder folder
is on the aufs and easily filled up under frugal installations. "
That is what Bacon Recorder have taken care of allowing that one place the
saved file on /home or /root or what to name it. Directly on the HardDisk
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
Mick informed me this is not yet multiuser compatible, so I will hold it off uploading it to the pet repo. But it does work as long as you only use root.Jim1911 wrote:GUI to download LibreOffice version 0.17 is out and works fine with Fatdog64-600
Nooby is right. By default when you boot in Fatdog you auto-login and run as root, just like in any puppies.nooby wrote:Sylvander, as I get it they set it up that way.Sylvander wrote:Umm, how's that?jamesbond wrote:Well, you are already running as root,
I'm not aware that I changed to running as root.
How did I do it do you think?
Seamonkey and many other applications run under user Spot.
But the x or GUI desktop is root? As you know I am a true noob I only guess.
One get automatically logged in as root for X?
For to not be root you most likely need to create a user using root
and then log into that user after boot? Am I right?
If you want to run as non-root you need to specifically create a user and specify that you want to login as that user.
Perhaps the text is not obvious. I have changed "load permanently" to "load at every boot".smokey01 wrote:Yeah, I hadn't ticked the box to make it persistent. In other puppies it automatically became persistent if loaded on the fly.shinobar wrote:Maybe we need to load the sfs from the control panel and make a check on the 'permanent'.smokey01 wrote:I have also noticed loading the fd64-devx_600.sfs is not persistent.
So many little, but subtle changes in Fatdog.
Right on target, Grant ! The drive icons will only kick-in 3 seconds after the desktop is loaded, to ensure that X desktop is running and ready.smokey01 wrote:Sylvander my FD64-600b1 boots from grub to desktop in 10 seconds. It takes about 3 more sec to show the 10 drive icons.
I need to test this, it shouldn't be the case. blacklist.conf should not be cleared at next boot.shinobar wrote:Actually, does not workshinobar wrote:getnvidia-0.2-64.pet, NVIDIA driver installer/PET/SFS builder.
It purges the nvouveau driver by listing it up on the blaklist, /etc/modprobe.d/blacklist,conf:It seems success for the first time, but the next boot, the nouveau revives. Why?Code: Select all
blacklist nouveau
EDIT: the /etc/modprobe.d/blacklist,conf is cleared after boot. Who and when?
EDIT: I just tested, it is not cleared. I did "echo blacklist pcspkr >> /etc/modprobe.d/blacklist.conf" and reboot - after reboot I did "lsmod" and pcspkr was no longer loaded, as expected.
If you hover the mouse cursor over the listview titles, you will get a tooltip saying soshinobar wrote:yes, woks, I had no idea to double-click for checking the mark.jamesbond wrote:1. Choose the package you want to uninstall (double-click or press Enter)
2. Click uninstall
600 supports both gzip compressed pets and xz compressed pets; but only creates xz compressed pets. If you want to create gzip-compressed pets you need to run dir2pet from other puppies; or otherwise you have to go through convoluted process of: dir2pet, followed by pet2txz; followed by tar -xJvf; followed by tar -czvf; follewed by tgz2pet.OK, I know SFS incompatibility with the kernel, but this is the first time to see incompatible PET.jamesbond wrote:600 uses xz compression for the pet.
Thank you shinobar, fix applied.BTW, how to make pet on Fatdog64? The dir2pet does not work because of the bug in the petspec./usr/bin/petspec at line 169 wrote: <default>${DEF_compiledrelease}</default><variable>DB_compiledrelease</variable> </entry>Fix wrote: <default>"${DEF_compiledrelease}"</default><variable>DB_compiledrelease</variable> </entry>
Use the pkeys= boot parameter. You can specify anything which exist in /lib/keymapsshinobar wrote:BTW, How to change the keyboard map on console?
The Keyboard localization on the control panel only effective with X.
Last edited by jamesbond on Sun 24 Jun 2012, 11:25, edited 1 time in total.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
Re: getnvidia-0.2-64
I tried that and it didn't help.shinobar wrote:Right.smokey01 wrote:I couldn't even get graphics to work after I tried. Had to delete the savefile and start again.
If i cannot get the desktop at boot, i type next 2 commands on console:Code: Select all
# rm /etc/X11/xorg.conf # xwin
Small problem but annoying.
Note the drive sequence on the attached.
Note the drive sequence on the attached.
- Attachments
-
- drives.jpg
- Out of sequence
- (12.24 KiB) Downloaded 839 times
Thanks, fixed for next release. If you want to fix it now, edit /usr/sbin/fatdog-drive-icon-start.sh, line 13, change:smokey01 wrote:Small problem but annoying.
Note the drive sequence on the attached.
for p in $(ls /sys/class/block | grep -vE '^loop|^ram|^nbd'); do
to
for p in $(ls /sys/class/block | grep -vE '^loop|^ram|^nbd' | sort -V); do
cheers.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
Will look again at Fatdog as it boots, and see what it's doing NOW.smokey01 wrote:Sylvander my FD64-600b1 boots from grub to desktop in 10 seconds. It takes about 3 more sec to show the 10 drive icons.
Still getting to grips with this new PC.
So much to do.
Information overload on this thread alone.
Nooby's point is taken/understood.
Got to get Psip working.
Got it set up in Slacko, but no-one logged in at 12-noon Sun 24th June?
Apparently my sound isn't working. Cannot hear anything.
64-bit version available for Fatdog?
How should I rerun the sound setup in Psip when I missed my 1st chance?
getnvidia-0.3-64
There is a time race between the load_sfs.sh and the rc.nvidia(.copy).shinobar wrote: the /etc/modprobe.d/blacklist,conf is cleared after boot. Who and when?
OK, fixed for now: was not persistent the nvidia graphics.
getnvidia-0.3-64.pet, NVIDIA driver installer/PET/SFS builder.
http://shino.pos.to/party/bridge.cgi?puppy/opt/fatdog/
You need fd64-devx_600.sfs . Required internet connection.
Recommended to build with new pupsave, 512MB or larger. I am not quite sure but If your RAM is less than 640MB, needs 500MB swap.
- Install the getnvidia.
- Run the getnvidia from the main menu > Setup.
- Reboot PC. You need to save the session if you have not yet.
- Install the devx package
- Exit X, go down to the console.
- Type 'getnvidia'.
But one problem when you use the sfs built on other PC:
DO NOT right click or choose from the offered when the first time after making save file.
Launch the sfs loader from the control panel and tick on the permanent load when you load the SFS.
I am not used to the FD64, so hope someone find more simple way for the persistent sfs load.
Last edited by shinobar on Sun 24 Jun 2012, 15:02, edited 2 times in total.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]