Page 8 of 23

Posted: Sun 15 Apr 2012, 19:42
by Dave_G
Lobster wrote:
New one. Verbatim. Class 4.
OK.
The ones that you originally tried, what were they used for in the past
and what were they formatted to?
Did they have any partitions and were any of them bootable?

It would be very interesting to format them again then use dd and see if they work.
I was told by the geek in the games shop that you can get up to class 10 - 10 is the best?
It depends on what you need/using it for.
Class 10 is certainly the fastest for general use but in your case not compatible with Pi.

As regards the possible dd problems with the version used in Puppy,
have you tried copying the dd that comes with another distro over to
Puppy and use that?
Since it's not a GUI type app, the dependencies will be much lower
and it may just work on Puppy.
I have had many CLI apps work across various distros with no problems at all.

I have also compiled many of my own apps in Puppy and successfully used
them on Gentoo.
Generally "normal" ELF (non-X) binaries will work across distros and kernel versions.
It's only .ko (kernel object files) that are very picky about kernel versions.

Do a "ldd" on both dd's to see if the dependencies are the same.

Posted: Sun 15 Apr 2012, 20:03
by Lobster
Dave_G wrote:.
The ones that you originally tried, what were they used for in the past
and what were they formatted to?
One was formatted in and for a camera
the other one was originally used in an Eeepc and probably formatted to
ext 2 or 3 - maybe fat3 (can not remember to be honest)
Did they have any partitions and were any of them bootable
no partitions and one may have been bootable
It would be very interesting to format them again then use dd and see if they work.
- it would and I may do that
The thing that annoys me is this simple step of formatting is crucial
and because of senility or lack of vitamins, proper instructions or [insert cause] I have been mucking about with possibly working hardware and SD cards . . . :roll:

Posted: Sun 15 Apr 2012, 20:32
by Dave_G
Lobster wrote:
One was formatted in and for a camera
the other one was originally used in an Eeepc and probably formatted to
ext 2 or 3 - maybe fat3 (can not remember to be honest)
Very interesting.
Did you know that some cameras actually format SD cards to FAT16
and not FAT32? (it's simpler to implement and less resource hungry).

One way to check this on XP (don't know about 7) is to insert the SD card
and then right click on it and click on properties.
If it says FAT32 then it is just that but if it says only FAT then it's either
FAT12 or FAT16 (what were M$ thinking? perhaps they have fixed it in SP3).

In Puppy you can mount the drive (SD card) then from the command line type:
mount
It should give you details of all drives and filesystems currently mounted.

What I'm starting to think is perhaps between dd and the image of Debian Squeeze,
it/they get confused if the target drive is not pre-formatted to FAT32.

Posted: Sun 15 Apr 2012, 23:04
by aarf
from pussy http://www.thepussycatforest.info/linux/README.txt maybe something of use
Download the .img version and use the linux dd command to image a USB stick or other removable media. Unzip the file first.
A HDD can also be imaged but any existing bootloader will be over written, not good for dual booting systems. Syslinux is used
as the bootloader. Syslinux can be edited to boot other OSes but that is not within the scope of this documentation.
Note: when you use the linux dd command to image the USB stick, you must unmount any partitions on the USB stick first.
The syntax for using dd to image a drive is:

dd if=<filename.img> of=/dev/sdX

Where <filename> is the USB image filename and the X in the /dev/sdX is the drive letter. Note you must specify the drive
NOT the partition on the drive (ie. /dev/sda not /dev/sda1) this is because the .img file contains partition info already.
The .img is an exact copy of a working Pussy USB stick in every detail and imaging a a USB stick with this file will result
in a working, booting USB stick that give the user write access and the ability to use compressed save files. Do not open
the .img file in another program and drag files accross to another partition, hoping this will work as this is not what the
.img is for. The .img file MUST be used with the dd command or an imaging program that does exactly the same thing.
What I'm starting to think is perhaps between dd and the image of Debian Squeeze,
it/they get confused if the target drive is not pre-formatted to FAT32.
also recall reading something of this nature somewhere

good news

Posted: Mon 16 Apr 2012, 00:39
by raffy
Lobster wrote:It is good news. I was really happy with LXDE in Squeeze. It will be very familiar to Puppys. To give you an example of speed; Midori took about 10 seconds to load. Next time (now Midori was loading from memory cache) was aprox. 3 seconds.
...
Tomorrow I will be looking at the tools in Squeeze and doing some sort of tutorial. Frankly I think it is a great base to boot strap Puppy from.
I may look at Fedora next but I was very content with Debian Squeeze
Happy for you, Lobster, and Iguleder, Pemasu and company will be happy, too that you are getting Squeeze'd. :D

Posted: Mon 16 Apr 2012, 01:03
by rcrsn51
Lobster wrote:Is it possible the SD card needs formatting before writing
I can't see why. The dd command would just erase any current filesystem structure on the card and over-write it with the new filesystem contained in the image file.

In any case, most (all?) SD cards are factory-formatted so they are ready to put in a device.

After using the dd command, you should have been able to mount the SD card's partitions in Puppy to verify that the copy was successful.

Posted: Mon 16 Apr 2012, 01:12
by Aitch
Rapberry Pi's are being offered on ebay starting at £100

Ready installed 8GB SD cards for Pi's are about £10 - choice of OS

add-on boards and extras increasingly advertised

Lobster, how did you sort the HDMI problem?

Aitch :)

Posted: Mon 16 Apr 2012, 02:14
by rcrsn51
Just out of curiosity, I downloaded the Debian image, unzipped it and dd'ed it to a hard drive.

Code: Select all

dd if=debian6-13-04-2012.img of=/dev/sdb
When done, the Raspi partitions were visible to Puppy.

I then tried to boot the drive. That failed (of course).

Posted: Mon 16 Apr 2012, 06:02
by Lobster
I will be doing screenshots but for now taking pics with ipad.

task1 mark territory :oops:
This was very easy, I created the wallpaper using xara sfs and existing PARM graphics last night

this morning . . .
Right click on desktop
change desktop or wallpaper (can not remember which - must have sardines) and then drag the file from USB keydrive (I added a lime coloured USB hub to the Raspberry) to the file selector
job done

Puppy boarding party arrives on the Squeeze box . . . :)

Posted: Mon 16 Apr 2012, 06:09
by Lobster
After using the dd command, you should have been able to mount the SD card's partitions in Puppy to verify that the copy was successful.
dd does overwrite as I thought

I probably did something wrong on the console
this is what I put in

Code: Select all

# dd bs=1M if=debian6-17-02-2012.img of=/dev/sdc1

Posted: Mon 16 Apr 2012, 06:14
by Lobster
Rapberry Pi's are being offered on ebay starting at £100
Sharks. :roll:
Pi's are priceless and worth every penny.
Lobster, how did you sort the HDMI problem?
4 for £5 on ebay (including delivery)
there was no problem with them - working fine

Posted: Mon 16 Apr 2012, 06:33
by Lobster
Happy for you, Lobster, and Iguleder, Pemasu and company will be happy, too that you are getting Squeeze'd.
Have not yet played with Squeeze
but boot up
is
login pi
password raspberry
startx
for desktop

Leaving that for now
- straight to desktop not a priority.

I am thinking very much of doing documentation here on the forum
or more likely here
http://puppylinux.info/topic/arm-puppy

Thanks for the Pussy info
I was really hoping we might have a Qemu ISO
. . . having me as a developer, is my last choice :oops:

I'll be doing my best to prepare our smarter dogs.
Early batches of Pi may be coming through the letter box this morning
If so . . . let us know

The speed issue:
Midori running slow - but connection speed is often more of an issue - so not to worry.
For those delving into the dark arts (aka programming) this is spot on.

My next tasks are to explore if I can write a bash script to download (apt-get mtpaint) Puppy essentials.

I also need to know how to change, output or remaster a modified Squeeze.
Any info on that welcome

Posted: Mon 16 Apr 2012, 06:53
by Lobster
gonna be grateful for any help developing this page:
http://puppylinux.org/wikka/PuppySchoolRaspberryPi

the PARM page is for Puppy on ARM
http://puppylinux.org/wikka/PARM

New one is for Puppy specifically on Rpi

Posted: Mon 16 Apr 2012, 08:50
by Lobster
Sausages and lemons [Lobsterian cussing/swearing]
Just checked out the ipad power supply again . . .

It has a USB and I have the USB to micro SD cable
it is rated as 5.1v and 2.1A

I thought it was 10v - I am sure I checked it out on the Apple site
- oh well, time to up medication to the red pills (only thing is I imagined those pills too) :wink:
I am told that 5.1v is acceptable for the Raspberry?
2.1A would be good.
Would have saved £6 for power supply yesterday
Would 5.1v caramelize the raspberry?

Posted: Mon 16 Apr 2012, 11:46
by rcrsn51
Lobster wrote:this is what I put in

Code: Select all

..../sdc1
That should be sdc.

Posted: Mon 16 Apr 2012, 12:24
by Lobster
You mean I was only out by 1? :oops:

I used your suggestion rcrsn51
You are right 8)
It worked and I was able to install to a 2GB SD card from Puppy and boot from that. :D

Why is it displaying sdc1 on screen (the parameter I used) and yet sdc is the correct input?

Posted: Mon 16 Apr 2012, 12:30
by Lobster
In Debian Squeeze
I need to be su to use apt-get or aptitude

Tried return (no password)
raspberry (it should be this surely)
and suse (I think that was for the previous debian not sure why)

None of those work - got to find the Squeeze password :roll:
Sugarpuffs and lemons [more cussing from the Lobsterian depths]

Any ideas/clues?

Posted: Mon 16 Apr 2012, 12:43
by rcrsn51
Why is it displaying sdc1 on screen
Because the current structure on the card has one partition, which Puppy sees as sdc1.

But the dd command will write a new structure onto the card that contains several partitions. So dd must copy the image to the card starting at its root location - sdc.

Posted: Mon 16 Apr 2012, 12:48
by aarf
Lobster wrote:
Why is it displaying sdc1 on screen (the parameter I used) and yet sdc is the correct input?
from the previous post from pussy
The syntax for using dd to image a drive is:

dd if=<filename.img> of=/dev/sdX

Where <filename> is the USB image filename and the X in the /dev/sdX is the drive letter. Note you must specify the drive
NOT the partition on the drive (ie. /dev/sda not /dev/sda1) this is because the .img file contains partition info already.

Posted: Mon 16 Apr 2012, 19:51
by antiloquax
Lobster wrote:In Debian Squeeze
I need to be su to use apt-get or aptitude

Tried return (no password)
raspberry (it should be this surely)
and suse (I think that was for the previous debian not sure why)
sudo passwd

Then you can set root password.
:)