Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Sat 24 Aug 2019, 07:29
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
Puppy Raspi Zap6
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 3 of 4 [51 Posts]   Goto page: Previous 1, 2, 3, 4 Next
Author Message
amj

Joined: 28 Jan 2011
Posts: 75

PostPosted: Fri 06 Mar 2015, 04:53    Post subject: Raspberry Pi 2  

A week ago today I took delivery of a Raspberry Pi 2. I've run the current Raspbian on it (a joyless experience) but am now slightly suprised to be able to say that I have Puppy zap6 running on the RPi2.

The methodology I followed is derivative of that described by woodenshoe here and by MU here. The sequence was as follows:

  • Download the latest rpi-firmware from Git (see posts by woodenshoe and MU). That got me kernel version 3.18.8 plus associated modules.
  • Write the zap6 image onto a micro-SD card (open a terminal box and use the dd command).
  • Mount the boot partition on the micro-SD card and delete bootcode.bin, kernel.img and start.elf.
  • From the rpi-firmware master, copy the following files to the boot partition: bootcode.bin, COPYING.linux, fixup_cd.dat, fixup.dat, fixup_x.dat, kernel7.img, kernel.img, LICENCE.broadcom, Module7.symvers, Module.symvers, README.md, start_cd.elf, start.elf and start_x.elf. (This is probably overkill, working out a minimal set is for later. However previous experiments using sub-sets of these files did not work).
  • Edit config.txt. I added to the start of the file a device_tree= command (i.e. no device tree). My understanding is this tells bootcode.bin to boot up the old-fashioned way and not to go looking for .dtb files.
  • Unmount the boot partition and mount the Puppy partition.
  • From the rpi-firmware master, copy the 3.18.8+ and 3.18.8-v7+ directories to lib/modules (so that they co-reside with the original 3.1.9-zapu-cutdown modules).
  • Put the micro-SD card in the RPi2 and boot-up.
  • If you have a system, be patient, allow the system time to execute first-boot procedures and then run through the usual Puppy startup tasks of choosing locale, timezone, keyboard layout etc.
  • Once all is stable, open a terminal box and type depmod.
  • From the menu, go to System -> Info -> Hardinfo hardware information and look at the summary. I was told Puppy had 949Mb of RAM. That seems to imply that 64Mb was allocated to the GPU by default.


I've not started developing a system as yet. This is just a quick post to say that it is possible to run zap6 on RPi2.
Back to top
View user's profile Send private message 
starhawk

Joined: 22 Nov 2010
Posts: 5056
Location: Everybody knows this is nowhere...

PostPosted: Wed 25 Mar 2015, 19:52    Post subject:  

Now that 01micko might actually read this since he's back... Wink

starhawk wrote:
What is the status of this PupPi version? I now have a RasPi (a friend gave me one) and I would like to get Puppy running on it. I can assist with testing but my dev skills are barely there so I can't really program anything Sad


My Pi is a Model B, not a B+ and not a 2 Smile

_________________

Back to top
View user's profile Send private message 
don570


Joined: 10 Mar 2010
Posts: 5345
Location: Ontario

PostPosted: Wed 25 Mar 2015, 20:24    Post subject:  

Barry Kauler wrote that he ordered a Raspy 2 when it was first announced
but he hasn't mentioned it since.

_________________________________
Back to top
View user's profile Send private message 
starhawk

Joined: 22 Nov 2010
Posts: 5056
Location: Everybody knows this is nowhere...

PostPosted: Thu 26 Mar 2015, 21:01    Post subject:  

Doesn't help me, I've got the original...

01micko, you around here somewhere? Wink

_________________

Back to top
View user's profile Send private message 
01micko


Joined: 11 Oct 2008
Posts: 8699
Location: qld

PostPosted: Thu 26 Mar 2015, 21:44    Post subject:  

Starhawk.

It should work (on a B or B+), but I'm not supporting any more. Too much other stuff to do. You'll have to find a work around for the 256MB RAM limit, I think MU in an earlier post changed the kernel; not so difficult as it only supports full installs.

_________________
Puppy Linux Blog - contact me for access
Back to top
View user's profile Send private message Visit poster's website 
starhawk

Joined: 22 Nov 2010
Posts: 5056
Location: Everybody knows this is nowhere...

PostPosted: Fri 27 Mar 2015, 11:49    Post subject:  

01micko wrote:
I'm not supporting any more


Crying or Very sad Crying or Very sad Crying or Very sad

_________________

Back to top
View user's profile Send private message 
amj

Joined: 28 Jan 2011
Posts: 75

PostPosted: Tue 01 Dec 2015, 16:54    Post subject:  

Over the past couple of weeks I've put together a zap6 system running with 3.18.8 kernel to run on a RPi2. I've played around with zap6 several times but this time I've put together a system I intend use. I'm not displeased with the rusult, so I decided to re-read this thread and see if there was anything 'useful' I could add to what has already been posted.

Several of the early posts above refer to kernel issues/bugs. It has amused me to see how several of the early examples of 'odd behaviour' (in both alpha4 and zap6) have simply disappeared as the kernel has progressed and various shortcomings eliminated.

By the way, the latest kernel I have downloaded is 4.1.13. For the hell of it I ran zap6 with 4.1.13 half expecting it not to work at all, but found it behaved OK. I've not done enough with that kernel to be able to say that it works, but I did not encounter any obvious problems.

There is an issue with gparted that has not been mentioned above. There is a missing dependency. You need to download and install libatkmm-1.6-1_2.22.6-1_armel.deb. Once that is done gparted will work OK.

As has been pointed out above, the processor in the original RPi simply was not powerful enough to facilitate web-surfing (no matter which browser you installed or how you configured your system). It's a different story with the RPi2. The RPi2 is a much more capable device and the version of Seamonkey/Iceape built into zap6 works well.

Now that Debian have taken the squeeze armel repository offline, anyone who wants to run Puppy on RPi/RPi2 and enhance it with pre-compiled binary packages (rather than compiling applications via devx) has no other option than zap6.

Transmission-gtk (bit torrent) works extremely well on alpha4. On zap6 you run into the same problem that prevented the inclusion of gnome-mplayer. Transmission wants GTK 3 and zap6 doesn't have it. One way to sidestep this issue is to install Tranmission-qt (plus the QT4 modules it needs). That will give you a prefectly usable bit torrent client. The menu entry created when you install Transmission-qt does not work. I suggest you add a script to /usr/local/bin to launch Transmission and create a desktop icon to launch the script. That does work.

Audio players are a matter of taste. I've never been a big fan of gnome-mplayer and am not bothered by it's absence. By the way, pmusic works fine. You can edit the 'play' icon on the desktop to point to it. I experimented with quite a few audio players on alpha4 but Aqualung was the only one that worked really well. That said I've not tried it on zap6. I have tried xmms2 on zap6 and gave it a definite thumbs down. However what I have done on both alpha 4 and zap6 is to install VLC. Of course Debian builds of VLC will not run as root, but you can run VLC from a console as spot. As an audio player it works perfectly on default settings (and it gives me the functionality I want).

Other applications that run OK on zap6 are XFE file manager, Sylpheed mail client, Pan newsreader and Geeqie image viewer. I also have a few multimedia tools installed including mhWaveEdit and MKVtoolnix.

At a practical level, putting together a RPi/RPI2 system is easier than it used to be. There are now very good HDMI to VGA converters available that work and are inexpensive. Lots of people have an old VGA monitor in their spare room, not everyone has a spare HDMI monitor doing nothing. My local hobbyshop sells HDMI to VGA converters for 15 euro each. I have a 15 year old CRT monitor attached to a RPI via a converter and it gives a very good result.

To my way of thinking, the Raspberry Pi and Puppy Linux are a natural fit. Both being rooted in essentially similar minamalist philosophies.
Back to top
View user's profile Send private message 
don570


Joined: 10 Mar 2010
Posts: 5345
Location: Ontario

PostPosted: Thu 03 Dec 2015, 20:42    Post subject:  

Playmusic works well as audio player in Puppy Linux alpha4 version.
It's one version behind. version 0.1.8 is the final version

PLAYMUSIC code

_____________________________________________

There are deb packages that can be downloaded from official site
for instance mtpaint 3.40. I wonder if they can be used??
http://archive.raspbian.org/raspbian/pool/main/m/

____________________________________________

If people had apps they wanted to distribute for Zap6,
The easiest way would be to make SLACK txz archives.
This maintains folder structure.

______________________________________________
Back to top
View user's profile Send private message 
amj

Joined: 28 Jan 2011
Posts: 75

PostPosted: Thu 24 Dec 2015, 09:34    Post subject:  

Device Tree boot

When I first got my hands on a RPi2 in March and set about trying to see if zap6 (and alpha4) would run on the new board I stuck with the legacy boot sequence. At the time the new device tree boot sequence was an extra unknown in a situation that already had enough unknowns.

Recently I decided it really was time to see if I could switch to the new boot sequence. It turned out to be ludicrously simple. Remove the device_tree= instruction from config.txt which instructs the bootloader to use legacy mode and add to the boot partition (/dev/mmcblk0p1) the standard device tree file for Raspberry Pi 2 Model B, called bcm2709-rpi-2-b.dtb. That's it.

I've been running with the device tree boot for a while now and as far as I can tell the system functionality is not effected in any way. The boot sequence is a little faster and a couple of error messages that used to be logged during start-up (see: /tmp/bootkernel.log) have now disappeared.

VLC

Another change I've made to my system concerns VLC. I've been running the Debian build of VLC as spot (since it won't run as root). If you navigate to /root/.config, add a directory called vlc and make spot owner of that directory, VLC will be able to save it's settings. But VLC will still be under some restrictions that may at times be inconvenient.

I wondered if there was an alternative approach (short of re-compiling VLC). Various web sites have multiple procedures listed which supposedly allow Debian builds of VLC to run as root. Some are OS specific, others apply to specific versions of VLC. But it seems there is a simple procedure, a two byte change to the VLC binary with a hex editor, that is likely to work under all circumstances. It tried it. I'm now running VLC as root and have made it default media player for zap6 (see: /usr/local/bin/defaultmediaplayer).

Open the VLC binary in a hex editor, search for text string geteuid and modify it so that it reads getppid. Save the file. Obviously this change is best applied before you start VLC for the first time, but it can be applied retrospectively as well. My retrospective change brought a message from VLC saying 'can't find /root/%U'. So I created a zero byte file in /root called %U. VLC was happy and the message disappeared.

On the subject of hex editors, the ghex binary from the Debian wheezy armel repository will not run on zap6 because of the GTK 2 vs 3 issue. But there are other hex editors that will work.
Back to top
View user's profile Send private message 
ally


Joined: 19 May 2012
Posts: 1915
Location: lincoln, uk

PostPosted: Thu 24 Dec 2015, 12:40    Post subject:  

berryboot has a version of BKs builds that works on the rpi2

had the issue of no repository, with infinite patience you can still find file mirrors but it's a pain in the butt

amj, could you look at getting fatdog arm working on the rpi2, I do not have the skills.....

agree the rpi2 is a much better machine, even the pi zero is pretty nippy

Smile
Back to top
View user's profile Send private message Visit poster's website 
amj

Joined: 28 Jan 2011
Posts: 75

PostPosted: Thu 24 Dec 2015, 15:03    Post subject:  

@ally

zap6 is based on Debian wheezy. The Debian wheezy armel repository is still online. It's the squeeze armel repository that is gone.

ally wrote:
amj, could you look at getting fatdog arm working on the rpi2, I do not have the skills.....


Neither do I. As you know I played around with fd-arm recently and am convinced that it could be ported to RPi2. But I know nothing of the internals of fd-arm and don't have any of the devices it runs on.

Although a port of fd-arm would be nice, it's probably not the solution we really need. fd-arm is not compatable with a major repository.

What is needed is a Puppy armhf build based upon Debian jessie or an equivelent Ubuntu. I'm happy to work towards that but at my current rate of progress Debian 9 will be out before it's done.
Back to top
View user's profile Send private message 
amj

Joined: 28 Jan 2011
Posts: 75

PostPosted: Wed 09 Mar 2016, 17:10    Post subject:  

RPi3

A quick note to say that I have zap6 running on an RPi3 with the current 4.1.19 (v7+) kernel. In terms of modifying/upgrading zap6, it's the same procedure as for the RPi2.

I've run zap6 on RPi2 with 4.1.13 kernel. That seemed to work perfectly and I'm not (yet) seeing any problems with 4.1.19.

In terms of the hardware, this seems to be a much smaller upgrade than the RPi to RPi2 upgrade. In terms of performance, maybe web pages load slightly faster but its not a significant difference.

Unless you specifically need more power for your USB devices or a built-in wireless and/or bluetooth interface, I can't see any urgent need to upgrade from RPi2 to RPi3. But if you do upgrade, you can still run Puppy Linux.
Back to top
View user's profile Send private message 
don570


Joined: 10 Mar 2010
Posts: 5345
Location: Ontario

PostPosted: Mon 14 Mar 2016, 14:46    Post subject:  

I used the instructions of forum member amj
http://www.murga-linux.com/puppy/viewtopic.php?p=832280#832280

It was easy to install zap6 on a raspberry pi2

(Using Precise Puppy) First start with the instruction....
Code:
unxz --stdout raspi-sd-4gb-zap6-5.100-ALPHA1.img.xz | dd bs=4M of=/dev/sdYOURDRIVE;sync


Quote:
From the rpi-firmware master, copy the 3.18.8+ and 3.18.8-v7+ directories to lib/modules (so that they co-reside with the original 3.1.9-zapu-cutdown modules).


I accidently left out this step but zap6 still booted anyway.
There was no sound so these modules are necessary for sound.

Rox filer has a nasty bug ----> finding info of a folder.
I had to restart X

_______________

Some comments:

Installed pclock and countdown worked
uextract ---> will allow extraction of a pet file
raspi date-time ---> Set the date and time easily on arm machine

___________________________________
raspi-date-time-1.1.pet
Description  Set the date and time easily on arm machine
pet

 Download 
Filename  raspi-date-time-1.1.pet 
Filesize  5.71 KB 
Downloaded  207 Time(s) 

Last edited by don570 on Sat 02 Apr 2016, 15:07; edited 1 time in total
Back to top
View user's profile Send private message 
don570


Joined: 10 Mar 2010
Posts: 5345
Location: Ontario

PostPosted: Thu 17 Mar 2016, 12:59    Post subject:  

I made a mtpaint 3.45.01 zap pet package.
Also updated gtkdialog from 0.8.0 to 0.8.4 to test pmusic

gtkdialog-zap-0.8.4.pet
mtpaint-zap-3.45.01.pet
mtpaint-zap_NLC-3.45.01.pet
pmusic-zap-4.9.5.pet

Available:
www.mydrive.ch

User: porteus@don570
Password: porteus
Back to top
View user's profile Send private message 
don570


Joined: 10 Mar 2010
Posts: 5345
Location: Ontario

PostPosted: Sat 19 Mar 2016, 16:34    Post subject:  

Added viewnior 1.6 slideshow presenter to mydrive.ch

viewnior-zap-1.6.pet

_______________________________
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 3 of 4 [51 Posts]   Goto page: Previous 1, 2, 3, 4 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Projects
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1732s ][ Queries: 12 (0.0344s) ][ GZIP on ]