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
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.
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.
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?
Did it say 'Downloading...'?smokey01 wrote: It appears the Nvidia package in your script is pointing to the wrong location. The modem appears to be downloading but after 10 minutes I killed the script.
It did say Downloading but when I examined your script it look like the wrong location, or a different location to where I normally download the source.shinobar wrote:Did it say 'Downloading...'?smokey01 wrote: It appears the Nvidia package in your script is pointing to the wrong location. The modem appears to be downloading but after 10 minutes I killed the script.
Before the 'Download' message, it performs ldconfig.
I realized the 'ldconfig' sometime hungs up, or takes too long time.
To see what URL the script will download from, type (if you have getnvidia):smokey01 wrote:It did say Downloading but when I examined your script it look like the wrong location, or a different location to where I normally download the source.
Code: Select all
ndivia-installer -l
65 seconds when booting from CD would be in the range of normal.Looked again at Fatdog bootup.
1. Loading initrd takes 65 seconds to load.
2. The sda5/Fatdog/sd64save.ext3 file isn't found, therefore not used. Sad
Not good!
So you would want to use:Some examples:
savefile=direct:device:sda1 --- use savefile named fd64save.ext4 located in root directory of /dev/sda1, save directly to it
savefile=ram:device:sda2:/fd600/fd64save.3fs --- use savefile named fd64save.3fs located in /fd600 directory of /dev/sda2, use RAM layer
savefile=ram:usb --- use savefile named fd64save.ext4 located in root directory of the first found usb device, use RAM layer
savefile=direct:multi --- use multisession on device /dev/sr0
(a) I don't think any other Puppy I've EVER run has taken this long to load...kirk wrote:65 seconds when booting from CD would be in the range of normal.
This did the trick.kirk wrote:Fatdog64-600 will only automatically load a save file named fd64save from the root of a partition.
Kirk explained how to do that above.Sylvander wrote:Would be nice if I could put it inside its own folder just like the other Puppies.
Shotwell is available in the precise repos in precise puppy beta 2, I just took a quick look at it (I had to start it with gexec with the runs in terminal box checked) but it seems to work okay, slideshow works at least.smokey01 wrote: Shotwell looks interesting, lots of dependencies though.
If I understood correctly...rcrsn51 wrote:Kirk explained how to do that above.
Thanks Billtoo, I will have a look.Billtoo wrote:Shotwell is available in the precise repos in precise puppy beta 2, I just took a quick look at it (I had to start it with gexec with the runs in terminal box checked) but it seems to work okay, slideshow works at least.smokey01 wrote: Shotwell looks interesting, lots of dependencies though.
If you have room for a puppy precise install on one of your pcs.
Bob, iron doesn't currently run as spot. Not if you do it through the usual "su spot" stuff. You need to be logged in properly as "spot" (or any other user) - the easiest way to do it is by using the user manager.BHINTZ wrote:I have loaded Iron.sfs and get a warning that I am running as root and I have been warned, but the browser does activate. I tried running in terminal as root and get some message about C. I tried as spot and get a message about libORBit.....
Can someone give a clue how to use this browser?
Much appreciated,
bob
If that is too long, just type "search=2" instead. This will look for savefiles in stored at 2 levels deep. It will find savefile in /fd600/fd64save*. If you need deeper level, type "search=3", this will find /mysavefile/fd600/fd64save*. Remember as you go deeper, the more scanning the system has to do *for every drives*; it will slow down the boot process a lot. Best is still to do what kirk recommends - specify the exact location of the savefile. If you find that typing is too long, create a remaster and type that inside syslinux.cfg when asked to - it will become your default settings.Sylvander wrote:If I understood correctly...rcrsn51 wrote:Kirk explained how to do that above.
He explained how TYPE a rather complicated command at the command prompt, at the 5-sec pause, during startup.
Too much of a hassle for my liking.