Fatdog Arm for Raspberry Pi2
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
don570,
I have recently purchased a pi3, so keen to try armdog!
I followed your instructions on page 1. Created a fat32 partition on my 16GB SD card, starting at 8MB, then copied all the files onto it.
But it won't boot. I just get a big rectangle with rainbow colours in it, and another small rectangle at top right. Then nothing happens.
I have recently purchased a pi3, so keen to try armdog!
I followed your instructions on page 1. Created a fat32 partition on my 16GB SD card, starting at 8MB, then copied all the files onto it.
But it won't boot. I just get a big rectangle with rainbow colours in it, and another small rectangle at top right. Then nothing happens.
[url]https://bkhome.org/news/[/url]
the rainbow top right is an insufficient power warning
https://www.raspberrypi.org/forums/view ... hp?t=82373
iirc a 2A power source is recommended for the pi3
https://www.raspberrypi.org/forums/view ... hp?t=82373
iirc a 2A power source is recommended for the pi3
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
I also own a pi2, so obvious thing is to try that, and yes, it boots!BarryK wrote:don570,
I have recently purchased a pi3, so keen to try armdog!
I followed your instructions on page 1. Created a fat32 partition on my 16GB SD card, starting at 8MB, then copied all the files onto it.
But it won't boot. I just get a big rectangle with rainbow colours in it, and another small rectangle at top right. Then nothing happens.
So, something needs to be changed for the pi3.
[url]https://bkhome.org/news/[/url]
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Thanks for that info. Yes, I only have a 1A supply.ally wrote:the rainbow top right is an insufficient power warning
https://www.raspberrypi.org/forums/view ... hp?t=82373
iirc a 2A power source is recommended for the pi3
Ubuntu-Mate still ran, despite the under-voltage.
[url]https://bkhome.org/news/[/url]
I use a 2.1A tablet charger and haven't had any under-power issues on my days old RaspberryPi3 currently doing a looped playback on mine to see if it will break before 30 day full refund window (shipping box was very abused )
Yet to try the Fatdog version but a up-todate full 64bit puppy version would be great. hint-hint
Yet to try the Fatdog version but a up-todate full 64bit puppy version would be great. hint-hint
Quite a bit of discussion about non-booting RPi-3, not necessarily a power issue. Detailed discussion is out of my range but seems some mods are need to the SW and multiple attempts to boot.a big rectangle with rainbow colours in it
Incidentally, my early Berryboot with Puppyalpha4 still runs fantastically well on B+. Just wondering whether BK could port that over to the RPi -3 64bit ARM iteration? [-and, separately as a single .img, the Zero].
For a power supply to my raspberry pi2 board I use a modified tablet power supply.
I cut off the barrel plug and substituted a micro USB plug.
I checked for 5v with a voltage meter.
______________________________________
Here is my config.txt file.
Note that I must put in the following because the audio stutters otherwise...
hdmi_ignore_edid_audio=1
______________________________________________________
I was able to make a second card work with omxplayer
so it's looking good. Bad news I broke my mouse somehow.
_____________________________________________________
I cut off the barrel plug and substituted a micro USB plug.
I checked for 5v with a voltage meter.
______________________________________
Here is my config.txt file.
Note that I must put in the following because the audio stutters otherwise...
hdmi_ignore_edid_audio=1
Code: Select all
disable_overscan=0
start_x=1
__________________________________
gpu_mem=128
hdmi_group=1
hdmi_mode=4
# Safest video mode
#hdmi_safe=1
hdmi_ignore_edid_audio=1
# Berryboot settings, do not change
#initramfs berryboot.img
#[pi2]
#kernel=kernel_rpi2_aufs.img
initramfs initrd.rpi2
[pi2]
kernel=vmlinuz.rpi2
# Warning: CMA does not work properly in newer firmware versions
#
#cma_lwm=16
#cma_hwm=32
#cma_offline_start=16
I was able to make a second card work with omxplayer
so it's looking good. Bad news I broke my mouse somehow.
_____________________________________________________
Discarded Cisco switched mode PSU from a Virgin (Sky?) box will supply 5V @ 3A. Should be sufficient to run plenty of peripherals, probably including a bank of analogue converters and relays for projects.
Don't think the ARM6/7/9/11 architectures are compatible apart from being 32 or 64bit? BK will know.I thought berryboot kernel would work with rpi3??
there is a different firmware loaded for RPi3 but software wise backwards compatible, there was a long black screen on the media OS I am currently running during boot and not the normal loader messages, liken it to the long boot darkness of changing between BIOS and UFI boot-loaders.
I haven't seen any noticeable speed changes, audio is different or my ears are playing tricks (music and effects louder dialog is muted, etc ) can't see why that could occur with HDMI
I haven't seen any noticeable speed changes, audio is different or my ears are playing tricks (music and effects louder dialog is muted, etc ) can't see why that could occur with HDMI
I made an important upgrade --- Samba and OMX player is now included
inside the package.
File system has been squashed into one file using the command ....
Also some minor improvements as well.
geeqie and puppy units now work properly.
Now boots directly to desktop because there is no save file.
If you want a save file you can set this with the control panel.
Instructions on first post.
_____________________________________
inside the package.
File system has been squashed into one file using the command ....
Code: Select all
mksquashfs squashfs-root fd-arm.sfs -comp xz -Xbcj arm -noappend
geeqie and puppy units now work properly.
Now boots directly to desktop because there is no save file.
If you want a save file you can set this with the control panel.
Instructions on first post.
_____________________________________
Xming and putty for remote control of raspberry pi 2
I was able to get Xming X server to control the raspberry pi2 computer remotely.
I could even get the raspberry pi 2 to play music
(remotely controled by windows XP).
With omxplayer installed the rp2 will play a video (with sound)
on the HDMI monitor of the rpi2 fullscreen.
Check youtube videos to explain how to use Xming.
DropBear needs to be running on the raspberry pi.
Set with the control panel.
Xming must be running on windows XP,
(Xlaunch.exe will set the window options, it's part of the xming package)
then...
Putty makes the connection to the rpi2 over ssh.
Then login as root , password woofwoof
Then you can launch rox or any gui program installed on the rpi2.
__________________________________________
I could even get the raspberry pi 2 to play music
(remotely controled by windows XP).
With omxplayer installed the rp2 will play a video (with sound)
on the HDMI monitor of the rpi2 fullscreen.
Check youtube videos to explain how to use Xming.
DropBear needs to be running on the raspberry pi.
Set with the control panel.
Xming must be running on windows XP,
(Xlaunch.exe will set the window options, it's part of the xming package)
then...
Putty makes the connection to the rpi2 over ssh.
Then login as root , password woofwoof
Then you can launch rox or any gui program installed on the rpi2.
__________________________________________
- Attachments
-
- screenshot-dropbear_zpsfv0bxnqk.PNG
- (9.97 KiB) Downloaded 196 times
-
- screenshot-xming_zpsq5sowp3l.JPG
- (37.91 KiB) Downloaded 191 times
Last edited by don570 on Sun 04 Feb 2018, 21:06, edited 8 times in total.
RPi getting very complicated with ARM6/11, 7, model 1, B, B+, model 2, model 3, 32bit, 64bit and now availability in limited quantities of Zero, but only one per punter.
Not sure whether it's your bag don, but a ZeroPup/Dog, albeit 32bit, would be a master stroke, especially with strong terminal options and comprehensive dongle networking drivers (doesn't have on-board NIC). It's 1GHz with 500Mb so putative strong performer with most Puppy incarnations except FD64, albeit with the intention of device control being a principal objective.
{Anyone writing about HW for Zero and RPi s, generally, on this Forum? The 'official' blurbs on the InterWeb are useless invocations to buy ready-made plug-ins. [Appreciate any links to basic hard wiring projects together with operating code, either here or by PM].}
Not sure whether it's your bag don, but a ZeroPup/Dog, albeit 32bit, would be a master stroke, especially with strong terminal options and comprehensive dongle networking drivers (doesn't have on-board NIC). It's 1GHz with 500Mb so putative strong performer with most Puppy incarnations except FD64, albeit with the intention of device control being a principal objective.
{Anyone writing about HW for Zero and RPi s, generally, on this Forum? The 'official' blurbs on the InterWeb are useless invocations to buy ready-made plug-ins. [Appreciate any links to basic hard wiring projects together with operating code, either here or by PM].}
fatdogarm-07-25-2016.zip
New version available at first post :
File: fatdogarm-07-25-2016.zip
Size: 231.68 MB
-Corrected some right click icons
- background image is now generated without using the disk clipboards.
See this command for more info
http://murga-linux.com/puppy/viewtopic. ... 556#914556
There is no savefile by default, however you are asked if you want to create
a savefile when you quit. Here is some info to read about savefiles.
It applies to fatdogarm as well as fatdog.
http://distro.ibiblio.org/fatdog/web/fa ... l#savefile
_______________________________________________________
____________________________________
File: fatdogarm-07-25-2016.zip
Size: 231.68 MB
-Corrected some right click icons
- background image is now generated without using the disk clipboards.
See this command for more info
http://murga-linux.com/puppy/viewtopic. ... 556#914556
There is no savefile by default, however you are asked if you want to create
a savefile when you quit. Here is some info to read about savefiles.
It applies to fatdogarm as well as fatdog.
http://distro.ibiblio.org/fatdog/web/fa ... l#savefile
_______________________________________________________
____________________________________
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Re: fatdogarm-07-25-2016.zip
Hi,don570 wrote:New version available at first post :
File: fatdogarm-07-25-2016.zip
Size: 231.68 MB
I just now tried the download link on the first page. When I clicked the Download button, it offered to download "fatdogarm-07-25-2016.exe", a 949KB size file.
I didn't download it.
[url]https://bkhome.org/news/[/url]
hey barry
you have to uncheck the download with installer
have mirrored it here: http://archive.org/details/Puppy_Linux_Fatdog_Arm_Beta
you have to uncheck the download with installer
have mirrored it here: http://archive.org/details/Puppy_Linux_Fatdog_Arm_Beta
Yes, unticking the downloader is recommended.
I'll put this in instructions.
________________________________________
When you first install fatdogarm --->
Remember to start dropbear with the control panel
since it is a replacement for ssh. I needed to do this to
make Xming work
_________________________________
Tip for or people who are compiling
Click on the devx-*.sfs file, which will mount it.
Open a terminal in the mounted directory (press back-tick character)
and copy the contents to the root filesystem:
Make your save file 2 gigs so you have lots of room for the copying
and future work space i.e. compiling and making packages.
_______________________________________________
I'll put this in instructions.
________________________________________
When you first install fatdogarm --->
Remember to start dropbear with the control panel
since it is a replacement for ssh. I needed to do this to
make Xming work
_________________________________
Tip for or people who are compiling
Click on the devx-*.sfs file, which will mount it.
Open a terminal in the mounted directory (press back-tick character)
and copy the contents to the root filesystem:
Code: Select all
cp -a -f --remove-destination * /
sync
and future work space i.e. compiling and making packages.
_______________________________________________
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Just a note, I got Quirky Xerus booting on the Pi2, haven't tested Pi3 yet but it should work.
I only got the commandline, not X, as none of the PETs from my armv7 Puppy (for Mele and Odroid boards) work in Pi2 Ubuntu Xerus.
I don't know why. 'ldd' just reports them as not executable. File properties:
Whatever, they don't work, so I am having to recompile all of them. So far, have managed to get a desktop, with jwm and rox-filer running.
James can help me out here, I will "borrow" his fatdogarm armv7 binary packages, turn them into PETs.
That should help me to bootstrap myself to a fully-working Quirky Xerus on Pi2 and Pi3.
I only got the commandline, not X, as none of the PETs from my armv7 Puppy (for Mele and Odroid boards) work in Pi2 Ubuntu Xerus.
I don't know why. 'ldd' just reports them as not executable. File properties:
Whereas, properties of an executable from Ubuntu Xerus:ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.16, BuildID[sha1]=71827819a5a94f1e8a2898d1d31f789d2d9cba5a, stripped
Maybe the problem is because the libc back in 2013 was compiled against kernel 2.6.16, too old?ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=24269390fe2a07b3bc8478e284f387c5d49a596f, stripped
Whatever, they don't work, so I am having to recompile all of them. So far, have managed to get a desktop, with jwm and rox-filer running.
James can help me out here, I will "borrow" his fatdogarm armv7 binary packages, turn them into PETs.
That should help me to bootstrap myself to a fully-working Quirky Xerus on Pi2 and Pi3.
[url]https://bkhome.org/news/[/url]
When I try to use other arm distros packages on fatdog arm I often getBarryK wrote:'ldd' just reports them as not executable
that message as well.
The irony is that packages compiled on fatdog arm will run on
Raspberry pi's Wheezy OS fine as long as libraries are installed.
For instance I had no problems transporting fatdogarm's mtpaint to Wheezy,
except I had to compile for the lack of tiff library.
___________________________________________
The fatdog arm devx is available here
http://ftp.cc.uoc.gr/mirrors/linux/fatd ... ges/beta4/
.