FatdogArm Beta1/2/3/4- 16 April 2016

[mories]

@mories

SW in Fatdog' initrd
============
- Inclusion, in savefile (directory /data/Fatdog of Berryboot), of SW that is only in the Fatdog's initrd, eg: iwconfig, ntfs-3g, dropbear ... and that it is necessary for the full operation of Fatdog
- On this point I think it would be more clear and clean if basesfs of Fatdog would include all SW necessary and could function autonomously, without requiring the level pup_init including Fatdog's initrd SW.

Yes, it should. I didn't include some of the stuff because I don't think they are necessary for normal operations - e.g. "ntfs-3g" is usually not needed unless you really plan to plug an external device with NTFS in it. But some - like dropbear, iwconfig, dosfsck, etc should be included in the basesfs. I just got a bit lazy at that time and thought since it was already in initrd, I didn't have to duplicate the effort. On the upstream variant (Fatdog64) all these tools are duplicated in basesfs.

I'll find the time to update these into the basesfs.

What about this aspect of basesfs?

[Ted Dog]

Stuck at rsync-img save to multisession on a f2fs on boot flashdrive. Lots of playing around moving omxplayer stuff. Can we move the fatdogarm sfs to a usb harddrive like we did with MeLe1000? Or copy to RAM?

Edit finally finished and shutdown took nearly 10mins. Any hope of getting a fatBerryBoot idea. I unpacked his initrd and the method is simple, Otherwise since its almost the same as your sandbox for fatdog64 . Layered sfs and launch switchroot ( or change root in this case ) would love to run fatdog-arm in parallel to say kodi.


EDIT failure to save back on F2FS also reported before Wed Jun 17, 2015 11:00 pm top of page 14 this two year old thread.

[don570]

I wrote a tutorial on how to install Samba on a Raspberry pi2
running Fatdog Arm.
http://www.murga-linux.com/puppy/viewtopic.php?t=106343
__________________________________________

Which version of berryboot do you guys recommend??
________________________________________________

[don570]

I think I know the cause of my problem with sound.

I believe I used old 2014 version
http://ftp.nluug.nl/ibiblio/distributio ... fd-arm.sfs

I should have used beta4 version --> april 2016

http://ftp.cc.uoc.gr/mirrors/linux/fatd ... fd-arm.sfs

______________

[Ted Dog]

I move BerryBoot out of the way ( to subfolder ) and used kernel package provided by JB instead. Simple as unpacked files copied onto a fat formatted microSD or miniSD whatever that easy to disappear tiny thing is called. For testing and feedback always best to go with whatever is given.

Second try to save multisession on usb harddrive worked ok. It was NTFS formatted. Also missing kpartx in this build. Minor but very useful to open and look into image files that some Raspberry distro are released in.
Source for omxplayer on OPENMX website. On phone tether internet so can do to much here. Speeds not bad. Can we teather to raspberrypi2b for internet?

EDIT also asked for kpartx a year ago Sun Apr 05, 2015 3:37 pm lol checking back on earlier Mele Posts for tricks I forgot. around page 6 of this thread.

[jamesbond]

@mories - I forgot. I'll do that and re-upload, will post a notice here when done.

@Ted Dog - never tested, but it should work.

[Ted Dog]

Deltas please! Burned thro 1/4th of data plan playing and testing yesterday. Triggered some speed slowdown as a result guess they do not like users to pull 3Gbytes in less than a day.
Will be in town today so will have full free to me internet, have to get the Star Wars movie ( never got around to seeing it in theaters ) I pre ordered.

Is there a built system available like you gave me a link for FD64 for this ARM version. Most interested in adding BerryBoot like setup to initrd.

[jamesbond]

@Ted Dog
Don't download those beta4 sfs-es if you don't have data quota. I'm going to modify them anyway soon.
As for build system: http://distro.ibiblio.org/fatdog/arm/re ... ta.tar.bz2. A bit old but it should still work, I suppose. If not I'm sure you can tweak it

[Ted Dog]

Code: Select all

# ./build-sfs.sh
Missing components.
# ./build-sfs.sh download
Missing components.

nope too old or missing something. In Town downloading packages.

[mories]

At boot, sometimes (not always) I am having problems with wlan0.
In these cases appears in /var/log/messages the following information:

Code: Select all

Jan  1 01:00:22 fatdog-arm kern.info kernel: [   22.956310] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Jan  1 01:00:23 fatdog-arm daemon.info dhcpcd[1019]: version 6.0.5 starting
Jan  1 01:00:23 fatdog-arm daemon.info dhcpcd[1019]: wlan0: waiting for carrier
Jan  1 01:00:24 fatdog-arm daemon.info dhcpcd[1019]: wlan0: carrier acquired
Jan  1 01:00:24 fatdog-arm daemon.info dhcpcd[1019]: wlan0: soliciting an IPv6 router
Jan  1 01:00:24 fatdog-arm daemon.info dhcpcd[1019]: wlan0: soliciting a DHCP lease
Jan  1 01:00:29 fatdog-arm daemon.info dhcpcd[1019]: wlan0: offered 192.168.1.35 from 192.168.1.1
Jan  1 01:00:34 fatdog-arm daemon.info dhcpcd[1019]: wlan0: leased 192.168.1.35 for 43200 seconds
Jan  1 01:00:34 fatdog-arm daemon.info dhcpcd[1019]: wlan0: adding host route to 192.168.1.35 via 127.0.0.1
Jan  1 01:00:34 fatdog-arm daemon.info dhcpcd[1019]: wlan0: adding route to 192.168.1.0/24
Jan  1 01:00:34 fatdog-arm daemon.info dhcpcd[1019]: wlan0: adding default route via 192.168.1.1
Jan  1 01:00:34 fatdog-arm daemon.info dhcpcd[1019]: forked to background, child pid 1119
Jan  1 01:00:34 fatdog-arm daemon.info dhcpcd[1119]: received SIGTERM from PID 1120, stopping
Jan  1 01:00:34 fatdog-arm daemon.info dhcpcd[1119]: wlan0: removing interface
Jan  1 01:00:34 fatdog-arm daemon.info dhcpcd[1119]: wlan0: deleting host route to 192.168.1.35 via 127.0.0.1
Jan  1 01:00:34 fatdog-arm daemon.info dhcpcd[1119]: wlan0: deleting route to 192.168.1.0/24
Jan  1 01:00:34 fatdog-arm daemon.info dhcpcd[1119]: wlan0: deleting default route via 192.168.1.1
Jan  1 01:00:34 fatdog-arm daemon.err dhcpcd[1140]: dhcpcd already running on pid 1119 (/var/run/dhcpcd-wlan0.pid)
Jan  1 01:00:35 fatdog-arm daemon.info dhcpcd[1119]: exited

And "wpa_cli status" provides the following information:

Code: Select all

root:~# wpa_cli status
Selected interface 'wlan0'
bssid=00:11:22:33:44:55
ssid=XXXXX
id=0
mode=station
pairwise_cipher=CCMP
group_cipher=TKIP
key_mgmt=WPA2-PSK
wpa_state=COMPLETED
address=11:22:33:44:55:66
uuid=...

i.e., it seems that wlan0 is associated with the AP but finally don't gets IP via DHCP.

Running "network-setup.sh start" sometimes everything works properly, but sometimes the problem above is repeated.


Can it be a similar problem like Fatdog64 reported here?
http://murga-linux.com/puppy/viewtopic. ... &start=173

Edit: This is in beta 4. In Beta 3 no such problem

[don570]

I re installed fatdog arm , this time using http://ftp.cc.uoc.gr/mirrors/linux/fatd ... fd-arm.sfs

This works well . No sound problems.

Here is my cmdline.txt to recognize ethernet...

pkeys=en waitdev=3 savefile=none basesfs=device:mmcblk0p2:/fatdogarm/fd-arm.sfs net=wired:eth0:dhcp

______________________________________________

[don570]

to james...

Would it be possible to use a sdcard entirely formatted as fat32.
Then boot up entirely in RAM like most users of BarryK 's Puppy linux.

If this was possible then the fatdog arm distro could be easier to install.

________________________________________________

Another thing I noticed. The general instructions to install fatdog arm
recommend 500mb for the first partition.

I checked the Berryboot installation method and they have a first partition
that is much smaller (under 200mb)

________________________________________________

[Ted Dog]

I agree with Don, I think its the only Raspberry Pi distro that IS made to use a un-reformatted Fat-type SDcard. Eariler versions allowed move to RAM and also move to usb harddrive with NTFS for both the SFSes and savefile.
Which is why I want to be able to FatBerryBoot, his method is BETTTER since the SDcard does not have to be modified and all chopped up. Also savebacks using multisession keep writes down to a very very small number.

[Ted Dog]

Do we have these in Beta4 and could they beused to run other distros sfs image files in parallel to fatdog-arm?

Code: Select all

(* Security fix *)
patches/packages/xorg-server-xephyr-1.14.3-arm-3.txz: Rebuilt.
patches/packages/xorg-server-xnest-1.14.3-arm-3.txz: Rebuilt.
patches/packages/xorg-server-xvfb-1.14.3-arm-3.txz: Rebuilt.

Found these in Slackware changelog.

[Ted Dog]

the method BerryBoot uses is copied on page 14 of this thread,
http://www.murga-linux.com/puppy/viewto ... 158#864158

see how easy ! just need to merge the two ( possibly get newest version of BerryBoot )
opening BerryBoot found here:

http://www.murga-linux.com/puppy/viewto ... 161#864161

[Ted Dog]

How to setup FatDogArm for both main files (SFSes) and save files on a usb type harddrive: (made on Mele1000, will require slight mod to which file is edited but setup string is whats important)

http://murga-linux.com/puppy/viewtopic. ... 372#729372

will confirm, looking for more historic posts on how I setup stuff years ago
[on in town free to me highspeed internet ]

[jamesbond]

nope too old or missing something. In Town downloading packages.

You miss the package list. Here is one for

[jamesbond]

At boot, sometimes (not always) I am having problems with wlan0.
Can it be a similar problem like Fatdog64 reported here?
http://murga-linux.com/puppy/viewtopic. ... &start=173

Edit: This is in beta 4. In Beta 3 no such problem

Yes, beta3 and beta4 has changed in the way it gets the IP address. I tried to make it more resistant and able to handle roaming, but apparently there are race issues. The issue seems familiar to Fatdog64 - but your dmesg output is a bit different. Which board is this, raspi2?

[jamesbond]

Would it be possible to use a sdcard entirely formatted as fat32.
Then boot up entirely in RAM like most users of BarryK 's Puppy linux.

If this was possible then the fatdog arm distro could be easier to install.

Possible. I have not tested it (XU4 chugging along doing something now), but you can use base2ram=yes just like Fatdog64.

Another thing I noticed. The general instructions to install fatdog arm
recommend 500mb for the first partition.

I checked the Berryboot installation method and they have a first partition
that is much smaller (under 200mb)

You can use any size as long as it fits Fatdog's vmlinuz and initrd. You can put all the SFS on the 2nd partition, if you wish. I recommend 500MB with the idea that beginners want to have vmlinuz, initrd, fd-arm.sfs, fd-devx.sfs etc on the same (first) partition, so 500MB should be enough space for that. It is also good if you want to put multiple kernels for on the same (first) partition for testing purposes. But if you don't need to do that.

[jamesbond]

Do we have these in Beta4 and could they beused to run other distros sfs image files in parallel to fatdog-arm?

Code: Select all

(* Security fix *)
patches/packages/xorg-server-xephyr-1.14.3-arm-3.txz: Rebuilt.
patches/packages/xorg-server-xnest-1.14.3-arm-3.txz: Rebuilt.
patches/packages/xorg-server-xvfb-1.14.3-arm-3.txz: Rebuilt.

Found these in Slackware changelog.

No. I haven't rebuilt the xorg servers for a long time. But I'll keep this in view.