93 replies to this topic

[WizardStan]

It's a wiki. Just sign up and edit it yourself.

edit: and I mean that in an entirely serious and helpful way, not sarcastic. No need to wait on others, just dive right on in

Edited by WizardStan, 31 March 2011 - 02:59 AM.

[Custom Processing Unlimite]

no, it's cool... I get that a lot, but not every wiki is the same, so I usually don't just jump in... so I don't screw something up.

[Cloudef]

This is awesome, now If I just had a pandora.

[Custom Processing Unlimite]

rummaging around for a spare SD card to test this out on... how small of an SD is ok for that?

[IsSuE]

I tried it on a 1Gb, but you are not having fun with that! Installed a couple of things and the SD was full. Go at least for 4 imho

[Custom Processing Unlimite]

need to get my hands on a 32GB... will definitely do so next paycheck... I might just hold out a little longer and wait till I get enough to get my hands on a 64GB SDXC.... then have all the fun I want!

[kaprikawn]

Can someone tell me how to extract the .tar.xz file please, Google isn't turning up much. I've tried it using the default package on Ubuntu and I get a bunch of 'cannot mknod' errors.

If I've got the .tar.xz file in the root directory of the SD card I intend to extract to, what's the command to extract in Terminal on the Pandora?

Cheers

[Tempel]

The terminal command to extract is:

tar xJvf filename.tar.xz

Do this from within the SD card's directory to extract there.

I can think of two potential causes of the mknod issue. See, it's trying to extract block devices to the SD card, since these are an important part of any Linux root filesystem, but creating them is restricted. It could be restricted to the root user only; try running that command I gave earlier with "sudo" in front of it. It could also be restricted by the rules used when mounting your SD card; try remounting with the "dev" option enabled. The command should look something like this:

sudo mount -o remount,dev /media/mmcblk0p1

Make sure to replace "/media/mmcblk0p1" with the actual path to your SD card. Then, run the extraction command again, with sudo if you need to.

I hope that helps, but let us know if it doesn't.

Edited by Tempel, 09 April 2011 - 08:31 PM.

[Letalis Sonus]

Maybe the rootfs tarballs should be generated using tar's --one-file-system option, so that it isn't trashed with temporary files or device nodes causing trouble while extracting. All device nodes should be generated dynamically within a virtual file system and therefore don't need to be saved.

[wejp]

The terminal command to extract is:

tar xJvf filename.tar.xz

Do this from within the SD card's directory to extract there.

Actually, you do not need to specify the compression mehtod at all with almost all tar versions currently in use. So all you need to do is "tar xfv archive", where archive can be uncompressed tar, .tar.gz, .tar.bz2 or .tar.xz .

I can think of two potential causes of the mknod issue. See, it's trying to extract block devices to the SD card, since these are an important part of any Linux root filesystem, but creating them is restricted. It could be restricted to the root user only; try running that command I gave earlier with "sudo" in front of it. It could also be restricted by the rules used when mounting your SD card; try remounting with the "dev" option enabled. The command should look something like this:

sudo mount -o remount,dev /media/mmcblk0p1

Make sure to replace "/media/mmcblk0p1" with the actual path to your SD card. Then, run the extraction command again, with sudo if you need to.

Mounting with the dev option should not be necessary, but should not do any harm either.

Maybe the rootfs tarballs should be generated using tar's --one-file-system option, so that it isn't trashed with temporary files or device nodes causing trouble while extracting. All device nodes should be generated dynamically within a virtual file system and therefore don't need to be saved.

I'll keep that option in mind or the next version. This might save some bytes, but even then the archive should still be extracted with the root user. If anyone has trouble extracting the archive as it is now, you are doing something wrong - either you aren't extracting as root or the filesystem on the target device is incompatible, e.g. fat instead of ext2. As said in my blog, the filesystem should be ext2 and nothing else (yes, this includes ext3 as well - do not use it).

[Custom Processing Unlimite]

mine wouldn't boot... maybe I did something wrong... but I will find out tonight...

[wejp]

I have tracked down the kernel bug causing the keyboard problems, which you have probably all noticed.

You'll find some more information and a package with the new kernel on my blog: Kernel update

[Custom Processing Unlimite]

so does that mean we officially (inadvertantly) have a kernel package now?

[wejp]

so does that mean we officially (inadvertantly) have a kernel package now?

Yes, indeed.

[mcobit]

NOTE: this project should be added to the wiki... not sure who to contact about that...

http://pandorawiki.o...ftware_projects

was it gruso?

Just add it yourself!