Author |
Message |
veronicathecow

Joined: 21 Oct 2006 Posts: 560
|
Posted: Tue 17 Apr 2018, 15:42 Post subject:
|
|
Hi thanks I have found it on the memory card (using my main PC
The contents of the file are
pkeys=en waitdev=3 savefile=direct:local basesfs=device:mmcblk0p1:/fatdogarm/fd-arm.sfs
|
Back to top
|
|
 |
woodenshoe-wi
Joined: 28 Jul 2017 Posts: 104 Location: Wisconsin
|
Posted: Tue 17 Apr 2018, 16:26 Post subject:
|
|
Is the fd-arm.sfs file in the fatdogarm directory on the SD card?
Are you still getting the "Cannot load basesfs" error when booting?
|
Back to top
|
|
 |
veronicathecow

Joined: 21 Oct 2006 Posts: 560
|
Posted: Tue 17 Apr 2018, 17:19 Post subject:
|
|
Yes still same error.
Files in root(as are all the files) not in a folder
|
Back to top
|
|
 |
woodenshoe-wi
Joined: 28 Jul 2017 Posts: 104 Location: Wisconsin
|
Posted: Tue 17 Apr 2018, 18:02 Post subject:
|
|
The only file that belongs in the fatdogarm directory is fd-arm.sfs
But you can probably edit the cmdline.txt file to remove the fatdogarm directory from the basesfs path if you don't want to put it in a directory.
Code: |
pkeys=en waitdev=3 savefile=direct:local basesfs=device:mmcblk0p1:/fd-arm.sfs
|
You could even try renaming or deleting cmdline.txt, I was able to reproduce the boot errors you described by renaming cmdline.txt but the fd-arm.sfs file on my SD card is in the fatdogarm directory. Without the cmdline.txt file telling init to look in the fatdogarm directory for fd-arm.sfs the init script will probably look for it in the root of the SD card.
|
Back to top
|
|
 |
veronicathecow

Joined: 21 Oct 2006 Posts: 560
|
Posted: Wed 18 Apr 2018, 02:34 Post subject:
|
|
Woof Woof, up and running!
I just created the folder and moved the file across and it has booted up to desktop.
Many thanks for your help woodenshoe-wi
|
Back to top
|
|
 |
woodenshoe-wi
Joined: 28 Jul 2017 Posts: 104 Location: Wisconsin
|
Posted: Wed 18 Apr 2018, 11:28 Post subject:
|
|
Glad to help.
I knew it should work because I had tested this version myself, just had to figure out what went wrong.
|
Back to top
|
|
 |
RetroTechGuy

Joined: 15 Dec 2009 Posts: 2912 Location: USA
|
Posted: Wed 18 Apr 2018, 12:12 Post subject:
|
|
Thanks Don. The Pi3 is currently on my radar -- been wondering what versions of Puppy to play with.
_________________ Add swapfile
WellMinded Search
|
Back to top
|
|
 |
don570

Joined: 10 Mar 2010 Posts: 5261 Location: Ontario
|
Posted: Thu 19 Apr 2018, 11:37 Post subject:
|
|
Quote: | I just created the folder and moved the file across and it has booted up to desktop. |
Did I do something wrong??
Which fdarm.sfs is successful , mine or James Bond??
If it's mine then you should boot to a giant clock.
What do you guys recommend for a cmdline.txt file??
I have only a raspberry pi2.
__________________________________________________
Description |
screenshot of desktop |
Filesize |
15.17 KB |
Viewed |
189 Time(s) |

|
|
Back to top
|
|
 |
woodenshoe-wi
Joined: 28 Jul 2017 Posts: 104 Location: Wisconsin
|
Posted: Thu 19 Apr 2018, 13:47 Post subject:
|
|
The fault could be with the program veronicathecow used to un-compress the zip file. Everything worked fine for me without any changes.
If you make the changes to config.txt that I wrote about in http://www.murga-linux.com/puppy/viewtopic.php?p=988299#988299
you should be able to boot this on your Pi2.
|
Back to top
|
|
 |
veronicathecow

Joined: 21 Oct 2006 Posts: 560
|
Posted: Thu 19 Apr 2018, 16:21 Post subject:
|
|
Hi don570, Pi is booting to big white and black analouge clock.
Cant seen to save the session though
When I try to close down I follow all the instructions i get the following error
Problem: fdsave.ext.4 on /dev/mmbclkop1 already exists. Please choose a different name.
With a different name it does save, but then on reboot it does not load this save file with a different name.
|
Back to top
|
|
 |
veronicathecow

Joined: 21 Oct 2006 Posts: 560
|
Posted: Thu 19 Apr 2018, 16:27 Post subject:
|
|
Thanks woodenshoe-wi that's a good thought I will check.
"The fault could be with the program veronicathecow used to un-compress the zip file. Everything worked fine for me without any changes. "
|
Back to top
|
|
 |
veronicathecow

Joined: 21 Oct 2006 Posts: 560
|
Posted: Thu 19 Apr 2018, 18:03 Post subject:
|
|
Hi woodenshoe-wi, yes you were right I hadn't chosen the correct options to expand the directories so I have re-installed that correctly now, thank you.
I am still getting similar problems though
Problem: fdsave.ext4 on /dev/mmbclkop1 already exists. Please choose a different name.
With a different name it now does not save but says
Problem: Unable to create tmsave.ext4 on /dev/mmcblk01p. Please chose another device/partition.
Last edited by veronicathecow on Thu 19 Apr 2018, 18:23; edited 1 time in total
|
Back to top
|
|
 |
woodenshoe-wi
Joined: 28 Jul 2017 Posts: 104 Location: Wisconsin
|
Posted: Thu 19 Apr 2018, 18:10 Post subject:
|
|
I didn't have any problem creating a save file, but mine is named fdsave.ext4
I don't know if fdsave.ext.4 with the extra "." in between "ext" and "4" is a typo or part of the problem. If there is nothing important in it maybe you could try deleting it from the SD card with the computer and trying again?
If you are getting errors is there enough free space on the SD card?
|
Back to top
|
|
 |
veronicathecow

Joined: 21 Oct 2006 Posts: 560
|
Posted: Thu 19 Apr 2018, 18:23 Post subject:
|
|
Just a typo.
|
Back to top
|
|
 |
veronicathecow

Joined: 21 Oct 2006 Posts: 560
|
Posted: Thu 19 Apr 2018, 18:25 Post subject:
|
|
I did a complete re-install with the corrected file structure and the results posted were from that. It's a 32gb card and I have tried a 29gb and 10gb save file, both same problem. However a 512 and a 1024 file size work.
Will try other sizes tomorrow.
|
Back to top
|
|
 |
|