Fatdogarm for Raspberry pi3 - headless

Message

woodenshoe-wi · #21 Post by **woodenshoe-wi** » Wed 18 Apr 2018, 15:28

Glad to help.

I knew it should work because I had tested this version myself, just had to figure out what went wrong.

RetroTechGuy · #22 Post by **RetroTechGuy** » Wed 18 Apr 2018, 16:12

Thanks Don. The Pi3 is currently on my radar -- been wondering what versions of Puppy to play with.

don570 · #23 Post by **don570** » Thu 19 Apr 2018, 15:37

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.

__________________________________________________

woodenshoe-wi · #24 Post by **woodenshoe-wi** » Thu 19 Apr 2018, 17:47

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/viewto ... 299#988299
you should be able to boot this on your Pi2.

veronicathecow · #25 Post by **veronicathecow** » Thu 19 Apr 2018, 20:21

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.

veronicathecow · #26 Post by **veronicathecow** » Thu 19 Apr 2018, 20:27

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

veronicathecow · #27 Post by **veronicathecow** » Thu 19 Apr 2018, 22:03

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.

woodenshoe-wi · #28 Post by **woodenshoe-wi** » Thu 19 Apr 2018, 22:10

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?

veronicathecow · #29 Post by **veronicathecow** » Thu 19 Apr 2018, 22:23

Just a typo.

veronicathecow · #30 Post by **veronicathecow** » Thu 19 Apr 2018, 22:25

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.

woodenshoe-wi · #31 Post by **woodenshoe-wi** » Thu 19 Apr 2018, 23:24

29gb and 10gb save file

If that's not a typo I think you need to know that fat filesystems have a 4gb file size limit...

If you need more space you could try repartitioning the SD card and adding an ext4 partition but the first partition needs to remain fat for the bootloader to work.

I am not an expert on how Fatdog works, I just was helping to test because I have a Pi3.

veronicathecow · #32 Post by **veronicathecow** » Fri 20 Apr 2018, 08:10

Hi, yes it was just a typo which I then went back and corrected on my post.

FAT32, of course, blooming fat32, I'm so used to running EXT4 I forgot about those limits, that would explain it even though I was creating a ext4 I am assuming it is within a fat32 4gb limit file container.
Your help has been very much appreciated.

don570 · #33 Post by **don570** » Sat 21 Apr 2018, 18:38

woodenshoe-wi is giving good advice.

fat32 is limited - no links and a few characters can't be used in file names (such as : ).
Of course, the data inside the savefile isn't limited by this, which is neat feature.

You can format SD card with both fat32 and linux EXT4 format if you wish.

You may have to change cmdline.txt file ---> not sure if this will work to find a stored savefile on second partition.

Code: Select all

savefile=direct:local

Maybe it does . I'm not sure??

You can always use

Code: Select all

savefile=ask

That always works.

_______________________________________________

spotted · #34 Post by **spotted** » Sat 28 Apr 2018, 07:58

I thought Pi3's were 64 bit, JB's work around for ARM Pi and Odroid is 32 bit. Is anyone going online and having trouble with Seamonkey 2.33 with security and permissions.

woodenshoe-wi · #35 Post by **woodenshoe-wi** » Sat 28 Apr 2018, 13:22

The CPU on the Pi3 is 64bit capable, but will also run the 32bit code for the Pi2 and Pi Zero.

I was able to fix the SSL errors in Seamonkey by setting the clock to more accurate time.

don570 · #36 Post by **don570** » Sat 28 Apr 2018, 18:53

spotted wrote:I cannot go online with Seamonkey 2.33., wont load webpage, error message says something like the time is in the future (This is after I set date in control panel)

woodenshoe wrote:I was able to fix the SSL errors in Seamonkey by setting the clock to more accurate time.

Is a restart of X needed??

There is a file in /etc that JamesB put in called 'last boot' or something similar.

This contains the time of last boot. It is used by system during booting up to set the time.
_________________________________________________

woodenshoe-wi · #37 Post by **woodenshoe-wi** » Sat 28 Apr 2018, 20:02

Is a restart of X needed??

Not for me, but make sure you have the day, month and year set correctly.

From my tests of the seamonkey-project.org website I could only get away with the clock set five days in the past.

Just setting the time to the last boot will gradually or rapidly lose time, if you want to use SSL websites I think automatically setting the time from a time server is necessary.

spotted · #38 Post by **spotted** » Sun 06 May 2018, 07:50

This is on a Odroid xu4. Pi2 sfs with odroid kernel works.
I have found last boot and changed the date but cant change the time.
2018-05-04 20:16:56
I set the date to yesterday and now Seamonkey works. I think I an going have to pull out the battery until real time matches the time above then put the battery back in.
I have a 'adjtime' file but its all double dutch to me.

-85329.263389 1525439816 0.000000
1525439816
LOCAL

This is what 'set system time ' looks like in control panel.

woodenshoe-wi · #39 Post by **woodenshoe-wi** » Sun 06 May 2018, 14:28

'set system time' looked the same on my Pi3, the trick I used was to assume that the dialogue was already set to the old time and click on the up or down arrows the number of times needed to get the correct time.

After a few repetitions I got it to the correct time.

don570 · #40 Post by **don570** » Sun 06 May 2018, 18:49

A year ago I wrote an app to set the time and date using the 'date' command.
https://www.geeksforgeeks.org/date-comm ... -examples/

You can try it. You'll have to convert it to a fatdog arm package I assume.

____________________________________________________

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Fatdogarm for Raspberry pi3 - headless