Raspberry Puppi
- antiloquax
- Posts: 405
- Joined: Fri 27 Jan 2012, 09:17
Okay, I am trying to host these files on my website instead.
ftp PupPi files
account name: a3804781
password: puppi1
So far, it's just the rubix tar.gz that's there.
Edit
Adding rxvt, gfrename, bcrypt, xorg-server and puppi.tar.gz (the image of the Arch File system I've made look a bit like Puppy!)
By the way, I did a pacman -Syyu on the arch OS yesterday and lots of updates came through. I think Arch are about to release a new version ...
I am going to add a little text file here which shows the steps I take to get to a basic graphical environment from the arch image (using xorg-twm).
mark
ftp PupPi files
account name: a3804781
password: puppi1
So far, it's just the rubix tar.gz that's there.
Edit
Adding rxvt, gfrename, bcrypt, xorg-server and puppi.tar.gz (the image of the Arch File system I've made look a bit like Puppy!)
By the way, I did a pacman -Syyu on the arch OS yesterday and lots of updates came through. I think Arch are about to release a new version ...
I am going to add a little text file here which shows the steps I take to get to a basic graphical environment from the arch image (using xorg-twm).
mark
- Attachments
-
- archsetup.tar.gz
- (525 Bytes) Downloaded 331 times
My System:Arch-Arm on RPi!
"[url=http://murga-linux.com/puppy/viewtopic.php?t=76049l]RacyPy[/url]" puplet on Toshiba Tecra 8200. PIII, 256 MB RAM.
[url=http://raspberrypy.tumblr.com/]RaspberryPy[/url]: Lobster and I blog about the RPi.
"[url=http://murga-linux.com/puppy/viewtopic.php?t=76049l]RacyPy[/url]" puplet on Toshiba Tecra 8200. PIII, 256 MB RAM.
[url=http://raspberrypy.tumblr.com/]RaspberryPy[/url]: Lobster and I blog about the RPi.
Here are generic .configure options for Puppy ( it varies, according to the Linux distro ):Lobster wrote:Are there generic options for ARM that I should look out for?./configure [add your options]
Code: Select all
./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var
make
make install DESTDIR=/tmp/MyPackage
Antiloquax, I tried your puppi.img in qemu and managed to login as root.
However, I can seem to get X running at the moment. And how did you get a window that says "Qemu" in the titlebar? This is just a quick report; I will try some more tommorrow...signing off after this message. When I run "startx", I get the following error messages:
However, I can seem to get X running at the moment. And how did you get a window that says "Qemu" in the titlebar? This is just a quick report; I will try some more tommorrow...signing off after this message. When I run "startx", I get the following error messages:
Code: Select all
[root@alarmpi ~]# startx
X.Org X Server 1.12.1
Release Date: 2012-04-13
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.1.10-6-ARCH armv5tel
Current Operating System: Linux alarmpi 3.1.9 #3 Tue Mar 6 05:34:11 GMT 2012 armv6l
Kernel command line: root=/dev/sda
Build Date: 15 April 2012 04:42:06PM
Current version of pixman: 0.24.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun May 6 03:46:42 2012
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using config directory: "/etc/X11/xorg.conf.d"
JWM: warning: key binding: root menu 1 not defined
- Attachments
-
- qemu-puppi.jpg
- (32.12 KiB) Downloaded 917 times
- antiloquax
- Posts: 405
- Joined: Fri 27 Jan 2012, 09:17
Hi Tman,
I don't think the JWM warning is the problem here. I get that as well, I must have made some mistake in my .jwmrc, but it doesn't ususally stop X from starting.
I'll get back to you when I've seen if I can sort this out.
mark
As for the "qemu" title bar. That's just how it has always looked since I installed it!
I don't think the JWM warning is the problem here. I get that as well, I must have made some mistake in my .jwmrc, but it doesn't ususally stop X from starting.
I'll get back to you when I've seen if I can sort this out.
mark
As for the "qemu" title bar. That's just how it has always looked since I installed it!
My System:Arch-Arm on RPi!
"[url=http://murga-linux.com/puppy/viewtopic.php?t=76049l]RacyPy[/url]" puplet on Toshiba Tecra 8200. PIII, 256 MB RAM.
[url=http://raspberrypy.tumblr.com/]RaspberryPy[/url]: Lobster and I blog about the RPi.
"[url=http://murga-linux.com/puppy/viewtopic.php?t=76049l]RacyPy[/url]" puplet on Toshiba Tecra 8200. PIII, 256 MB RAM.
[url=http://raspberrypy.tumblr.com/]RaspberryPy[/url]: Lobster and I blog about the RPi.
- antiloquax
- Posts: 405
- Joined: Fri 27 Jan 2012, 09:17
Hi Tman. I have just downloaded the puppi.tar.gz and unpacked it.
The md5sum was okay:
I am using this zImage.
When I boot it up and login, X starts automatically.
I'm not sure why it didn't work for you. Let me know if you have any more information, or if you do get it going!
mark
The md5sum was okay:
Code: Select all
66a141b3cb1f1c5b51007b6ae677c789 puppi.img
When I boot it up and login, X starts automatically.
I'm not sure why it didn't work for you. Let me know if you have any more information, or if you do get it going!
mark
My System:Arch-Arm on RPi!
"[url=http://murga-linux.com/puppy/viewtopic.php?t=76049l]RacyPy[/url]" puplet on Toshiba Tecra 8200. PIII, 256 MB RAM.
[url=http://raspberrypy.tumblr.com/]RaspberryPy[/url]: Lobster and I blog about the RPi.
"[url=http://murga-linux.com/puppy/viewtopic.php?t=76049l]RacyPy[/url]" puplet on Toshiba Tecra 8200. PIII, 256 MB RAM.
[url=http://raspberrypy.tumblr.com/]RaspberryPy[/url]: Lobster and I blog about the RPi.
I dunno why i can't get a graphical interface going. I compiled it with the following settings:
My guess is, that I am missing some dependencies. If all else fails, I guess run a pre-compiled qemu in another linux distro.
Is there a way for qemu to write its contents somewhere outside of the .img file?
Or would I have to use "dd" and extract the needed files?
Code: Select all
./configure --prefix=/usr --sysconfdir=/etc --target-list=arm-softmmu,arm-linux-user --enable-uuid --cpu=i686 --enable-linux-user --enable-system
Is there a way for qemu to write its contents somewhere outside of the .img file?
Or would I have to use "dd" and extract the needed files?
Good news,
I downloaded Slacko, and tried compiling it again. And it worked!
I have uploaded a pet for Slacko, if anyone wishes to try it out.
Qemu-arm 1.0.1 for Slacko
I downloaded Slacko, and tried compiling it again. And it worked!
I have uploaded a pet for Slacko, if anyone wishes to try it out.
Qemu-arm 1.0.1 for Slacko
- antiloquax
- Posts: 405
- Joined: Fri 27 Jan 2012, 09:17
Glad to hear that it's working!
mark
I think there is. I haven't found out how. I will do so, as it would save time!Tman wrote:
Is there a way for qemu to write its contents somewhere outside of the .img file?
Or would I have to use "dd" and extract the needed files?
mark
My System:Arch-Arm on RPi!
"[url=http://murga-linux.com/puppy/viewtopic.php?t=76049l]RacyPy[/url]" puplet on Toshiba Tecra 8200. PIII, 256 MB RAM.
[url=http://raspberrypy.tumblr.com/]RaspberryPy[/url]: Lobster and I blog about the RPi.
"[url=http://murga-linux.com/puppy/viewtopic.php?t=76049l]RacyPy[/url]" puplet on Toshiba Tecra 8200. PIII, 256 MB RAM.
[url=http://raspberrypy.tumblr.com/]RaspberryPy[/url]: Lobster and I blog about the RPi.
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
You guys are doing great
I tried setting up woof2
have done it previously (at least initial stages)
http://puppylinux.info/topic/getting-started
Could not even download woof
even reregistered with a new woof name . . .
May have to try compiling programs again
or try learning some Chinese for light relief . . .
gou = dog
I tried setting up woof2
have done it previously (at least initial stages)
http://puppylinux.info/topic/getting-started
Could not even download woof
even reregistered with a new woof name . . .
May have to try compiling programs again
or try learning some Chinese for light relief . . .
gou = dog
- antiloquax
- Posts: 405
- Joined: Fri 27 Jan 2012, 09:17
@Tman - I think you can use Samba to set up a shared folder. I'm not sure how (yet). I am just DDing things back and to. It's slow, but it works!
If anyone can tell me how to use Samba, I'd appreciate it.
I've tried pnethood, but nothing seems to happen. Do I need to install Samba, or is it already there?
I am downloading a Samba pet to have a go with that.
EDIT
I installed Samba, but it gave me a segmentation fault!
I have compiled a few more things.
ftp index
If anyone can tell me how to use Samba, I'd appreciate it.
I've tried pnethood, but nothing seems to happen. Do I need to install Samba, or is it already there?
I am downloading a Samba pet to have a go with that.
EDIT
I installed Samba, but it gave me a segmentation fault!
I have compiled a few more things.
ftp index
My System:Arch-Arm on RPi!
"[url=http://murga-linux.com/puppy/viewtopic.php?t=76049l]RacyPy[/url]" puplet on Toshiba Tecra 8200. PIII, 256 MB RAM.
[url=http://raspberrypy.tumblr.com/]RaspberryPy[/url]: Lobster and I blog about the RPi.
"[url=http://murga-linux.com/puppy/viewtopic.php?t=76049l]RacyPy[/url]" puplet on Toshiba Tecra 8200. PIII, 256 MB RAM.
[url=http://raspberrypy.tumblr.com/]RaspberryPy[/url]: Lobster and I blog about the RPi.
I've never used samba, but i thought it was for sharing files between a Linux System and Windows System.
Anyhow, I have discovered an easier method: you can mount your puppi.img ...
Example: First, create a folder called /mnt/imgdisk (or whatever name you prefer), then use the following terminal command:
mount -o loop /path/to/puppi.img /mnt/imgdisk
Unfortunately, I don't know what the unmount command in Puppy is:
I thought it was "unmount" but, I guess that doesn't exist in Puppy.
EDIT: I just found out that the unmount command would be: umount /mnt/imgdisk
umount, not unmount
-
Anyhow, I have discovered an easier method: you can mount your puppi.img ...
Example: First, create a folder called /mnt/imgdisk (or whatever name you prefer), then use the following terminal command:
mount -o loop /path/to/puppi.img /mnt/imgdisk
Unfortunately, I don't know what the unmount command in Puppy is:
I thought it was "unmount" but, I guess that doesn't exist in Puppy.
EDIT: I just found out that the unmount command would be: umount /mnt/imgdisk
umount, not unmount
-
Last edited by Tman on Sat 12 May 2012, 22:49, edited 1 time in total.
- antiloquax
- Posts: 405
- Joined: Fri 27 Jan 2012, 09:17
[quote="Tman"
Anyhow, I have discovered an easier method: you can mount your puppi.img ...
[/quote]
Good point ... why didn't I think of that?
I have been trying to have go at Assembly code today. I kept getting segmentation faults!
Do I use "as" or do I need a specific arm assembler?
Anyhow, I have discovered an easier method: you can mount your puppi.img ...
[/quote]
Good point ... why didn't I think of that?
I have been trying to have go at Assembly code today. I kept getting segmentation faults!
Do I use "as" or do I need a specific arm assembler?
My System:Arch-Arm on RPi!
"[url=http://murga-linux.com/puppy/viewtopic.php?t=76049l]RacyPy[/url]" puplet on Toshiba Tecra 8200. PIII, 256 MB RAM.
[url=http://raspberrypy.tumblr.com/]RaspberryPy[/url]: Lobster and I blog about the RPi.
"[url=http://murga-linux.com/puppy/viewtopic.php?t=76049l]RacyPy[/url]" puplet on Toshiba Tecra 8200. PIII, 256 MB RAM.
[url=http://raspberrypy.tumblr.com/]RaspberryPy[/url]: Lobster and I blog about the RPi.
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
I am not sure that qemu would work on the assembly level?
. . . apparently it does . . . wow
and comparing wth Slacko 5.3.3
Some partial success with the Rpi, then I messed up the SD image using apt-get
Back to square 1 but have some trouble shooting leads here
http://elinux.org/R-Pi_Troubleshooting
from the new official Rpi forum
http://www.raspberrypi.org/phpBB3/index.php
My learning curve:
. . . apparently it does . . . wow
I have been looking at compiling in wxglade in Rpi DebianQEMU works well for testing program correction (i.e. whether the code would properly run on an actual ARM or PowerPC) but it is not good for testing program efficiency: the emulation is not cycle accurate, and speed measured with QEMU cannot be reliably (or even unreliably) correlated with speed on true hardware.
Also, QEMU will not trap unaligned memory accesses, which is not a problem for PowerPC emulation (the PowerPC tolerates unaligned accesses) but may be for ARM (an unaligned access, e.g. reading a 32-bit word in RAM from an address which is not a multiple of 4, will work fine with QEMU but would trigger an exception on a true ARM processor).
and comparing wth Slacko 5.3.3
Some partial success with the Rpi, then I messed up the SD image using apt-get
Back to square 1 but have some trouble shooting leads here
http://elinux.org/R-Pi_Troubleshooting
from the new official Rpi forum
http://www.raspberrypi.org/phpBB3/index.php
My learning curve:
Antiloquax,
I have no idea how to code in Assembly. I think learning how to program in C is hard enough for my tastes.
Lobster,
If you are able to get the RaspberryPi Arch image running, it would offer you newer tools than Debian...you have a better chance of compiling bleeding-edge software with Arch, which is very bleeding-edge itself.
I have no idea how to code in Assembly. I think learning how to program in C is hard enough for my tastes.
Lobster,
If you are able to get the RaspberryPi Arch image running, it would offer you newer tools than Debian...you have a better chance of compiling bleeding-edge software with Arch, which is very bleeding-edge itself.
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
You may be right.If you are able to get the RaspberryPi Arch image running
I will give it another go.
Just got some sound out of the Rpi for the first time (just a test)
I was connected to mini speakers and I was worried that they would require more power than headphones (these are unpowered speakers) but it worked . . .
For future ref this is the advice I followed
Ay chihuahua - I have to make (compile) the hello_audio program . . .The ALSA sound driver is "alpha" and has issues, but some applications do work. If you are running Debian, try
cd /opt/vc/src/hello_pi/hello_audio
make
./hello_audio.bin
to test analogue output. And
./hello_audio.bin 1
for HDMI
Fortunately it was as easy as pie (so to speak)
OK gonna go through the Raspberry Pi wiki and forums
for any other tips . . .
Last edited by Lobster on Sun 13 May 2012, 08:18, edited 1 time in total.
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
Tried again . . .I tried setting up woof2
have done it previously (at least initial stages)
http://puppylinux.info/topic/getting-started
This time I used the 1.20 binary of Fossil (rather than the updated)
I also created a separate partition for the process
This enabled me to go through the whole of the woof2 process
- including the setting up of an image to an SD card
This is near the start of the process
and this near the end# ./merge2out
This script merges woof-arch, woof-code and woof-distro, to ../woof-out_*.
woof-arch: architecture-dependent (x86, arm) files, mostly binary executables.
woof-code: the core of Woof. Mostly scripts.
woof-distro: distro-configuration (Debian, Slackware, etc.) files.
Important: the host architecture is distinct from the target architecture.
The host is the machine you are running Woof on, the target is the machine
in which the Puppy that you build is going to run. Typically, you will build
on a x86 machine, and the target may be x86 or arm.
1 arm
2 x86
Type number of host architecture: 2
...ok, x86
1 arm
2 x86
Type number of target architecture: 1
...ok, arm
Not successfulUncompressing image, please wait...
Writing skeleton image to /dev/sdc, please wait very patiently...
7727264+0 records in
7727264+0 records out
3956359168 bytes (4.0 GB) copied, 2240.47 s, 1.8 MB/s
mount: wrong fs type, bad option, bad superblock on /dev/sdc2,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Something is wrong. There should be two partitions on the SD card,
vfat and ext4. There was an error mounting them. Aborting script.
#
I have sent Barry more of this process to his gmail address.
A lot of error messages came up . . . however woof2
may be the most complete option
For the ARM build only Debian Squeeze and the Mele compiled kernel
were available
Progress.
Geeky
Slow.
Spurts
Getting there . . .
Last edited by Lobster on Fri 11 May 2012, 05:09, edited 1 time in total.
- antiloquax
- Posts: 405
- Joined: Fri 27 Jan 2012, 09:17
Hi Lobster,
I have tried using woof before and got very confused.
I was wondering about trying the "Linux from Scratch" approach. However, I only got as far as compiling binutils following the instructions in the book. When I tried to move on to gcc, my luck evaporated
I have tried using woof before and got very confused.
I was wondering about trying the "Linux from Scratch" approach. However, I only got as far as compiling binutils following the instructions in the book. When I tried to move on to gcc, my luck evaporated
My System:Arch-Arm on RPi!
"[url=http://murga-linux.com/puppy/viewtopic.php?t=76049l]RacyPy[/url]" puplet on Toshiba Tecra 8200. PIII, 256 MB RAM.
[url=http://raspberrypy.tumblr.com/]RaspberryPy[/url]: Lobster and I blog about the RPi.
"[url=http://murga-linux.com/puppy/viewtopic.php?t=76049l]RacyPy[/url]" puplet on Toshiba Tecra 8200. PIII, 256 MB RAM.
[url=http://raspberrypy.tumblr.com/]RaspberryPy[/url]: Lobster and I blog about the RPi.