(old)Puppy Linux Discussion Forum

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

_____________________________________

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.


__________________________________________

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].}

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

_______________________________________________________


____________________________________

don570 wrote:New version available at first post :
File: fatdogarm-07-25-2016.zip
Size: 231.68 MB

Hi,
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.

hey barry

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.

_______________________________________________

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:

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

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.32, BuildID[sha1]=24269390fe2a07b3bc8478e284f387c5d49a596f, stripped

Maybe the problem is because the libc back in 2013 was compiled against kernel 2.6.16, too old?

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.

BarryK wrote:'ldd' just reports them as not executable

When I try to use other arm distros packages on fatdog arm I often get
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/

.

I received my Raspberry Pi 3 a few days ago and have finally had a chance to try it out. I am using the Cana Kit 5V 2.5 Amp power supply.

Raspbian for the RPi 3 boots and runs OK. Ubuntu Mate 16.04 boots OK but seems to have a problem with the wi-fi which is supposed to be corrected with version 16.04.1.

I downloaded the July 25 2016 version of Fatdog Arm , unzipped it and copied the files to a fat32-formatted single-partition microSD card. As others have described, boot attempt resulted in the appearance of a large rainbow square and in the upper right-hand corner of the screen, a small rainbow square.

In order to try to get it to boot, on the Fatdog Arm card, I moved bootcode.bin to bootcode.bin.old, and start.elf to start.elf.old. Then, from the RPi 3 Raspian microSD card, I copied over to the Fatdog Arm card the following files: bcm2710-rpi-3-b.dtb, bcm2710-rpi-cm3.dtb, bootcode.bin and start.elf.

But no luck! The result was the same big rainbow square on the screen (the small rainbow square was no longer present).

I would really enjoy being able to boot Fatdog Arm on my Raspberry Pi 3.

Hi eowen2,

Raspi3 requires different kernel than Raspi2. What you did above is just replacing the bootloader and the DTB files. That is necessary but not sufficient - you need a new kernel too. I'll see if I can build a new kernel for Raspi3.

@Barry - let me know what you need.

cheers!

stumbled across docker on my news app last night

used for cross compiling arm, thought may be of interest:

https://github.com/dockcross/dockcross

jamesbond wrote:Hi eowen2,

Raspi3 requires different kernel than Raspi2. What you did above is just replacing the bootloader and the DTB files. That is necessary but not sufficient - you need a new kernel too. I'll see if I can build a new kernel for Raspi3.

@Barry - let me know what you need.

cheers!

I used the kernel from Ubuntu Mate, 4.1.17 I think. It has 'kernel.img' and 'kernel7.img' in the fat partition, and from reading up on it, it seems that kernel.img is for the pi1 (present even though Ubuntu Mate is armv7).

If that is the case, then kernel7.img is ok for both Pi2 and Pi3, as it my Quirky boots on both.

I need to verify this, delete kernel.img and see if it still boots on the Pi2 and Pi3.

Note, have upgraded to the 4.4.19 kernel. Haven't tested it yet, building it now in woofQ.

I downloaded everything precompiled from here:
https://github.com/raspberrypi/firmware

Instead of downloading the zip file, I used git, um, let's see, think I did this:

git clone git://github.com/raspberrypi/firmware.git

...which was a mighty big download, about 5.5GB. I used up my monthly data allowance (I am on 4G Optus network, costs AU$40 for 12GB per month, AU$15 for extra 1GB), had to buy more!

Anyway, that had everything, and I created a new skeleton SD card image file.

Not yet tested!

I compiled mhwaveedit with my rpi2 to edit wave and mp3 files.
I believe lame is needed to mp3 files.
mhwaveedit-fatdogarm-1.4.23.tbz
__________________________

I updated my utility to connect fatdogarm to a server. Small bug fix.
fatdog_connect-1.12.tbz

_______________________________________________

I made a right click utility to open microsoft DOCX documents.
Just right click on docx file and choose ' DOCX Reader'

https://www.mydrive.ch/download/3471418 ... rm-1.4.tbz

However it needs perl to be installed and leafpad to open the text file.
These are already installed in my version of fatdogarm.
__________________________________________


All are available for download :
http://www.mydrive.ch
USER: porteus@don570
PASSWORD: porteus

__________________________________________________

BarryK deserves wired broadband, dangit!!!

Moat wrote:BarryK deserves wired broadband, dangit!!!

The problem is, currently I am not stable at one place. Right now I am living in the guest room of my step-mothers house.

I might buy a place in a country town sometime next year, but don't know if I want to get back into having a homeline.

BarryK wrote:Note, have upgraded to the 4.4.19 kernel. Haven't tested it yet, building it now in woofQ.

I downloaded everything precompiled from here:
https://github.com/raspberrypi/firmware

Instead of downloading the zip file, I used git, um, let's see, think I did this:

git clone git://github.com/raspberrypi/firmware.git

...which was a mighty big download, about 5.5GB. I used up my monthly data allowance (I am on 4G Optus network, costs AU$40 for 12GB per month, AU$15 for extra 1GB), had to buy more!

Anyway, that had everything, and I created a new skeleton SD card image file.

Not yet tested!

OK, I can confirm that 'kernel7.img' works for both Pi2 and Pi3.

Ubuntu Mate developers don't seem to have understood. They left in 'kernel.img' and /lib/modules/4.1.17+, even though Ubuntu Mate only works on the Pi2 and Pi3 (all that is needed is 'kernel7.img' and /lib/modules/4.1.17+v7)

tried raspi-pi2-sd-8gb-skeleton-20160902.img.xz on a raspberry pi 2

dd'd to 16gb micro but getting kernel panic on boot (md5 checked ok)