Tiny Core Base > Raspberry Pi

Please help a beginner

(1/5) > >>

sbp:
Hi
I have been trying to use TCE 4.7.2 on my Raspberry (256 RAM).

It boots fine (and very quickly), but my problem starts when I try to install packages, I'm sure that I have done something wrong when preparing the SD-card - eventhough I tried to follw the instructions.

1. I copied the image to the card.
2. Next I used Gparted to fill up the rest of the card with a "data" partition - so I marked the unused part and made a new primary partition as ext2 file format called data. Gparted finished the job without any problems.
3. I started my Raspberry with the new image, and it started fine.
4. I tried to setup my tce directory, so used: tce-setdrive
5. Here I could onle see               1.   /mnt/mmcblk0p1
                                                  2.  /mnt/mmcblk0p2
So I was unable to see my newly created "data" partition.

I tried to use either 1 or 2 (that is /mnt/mmcblk0p1 or /mnt/mmcblk0p2) but then the packages that I dowloaded couldn't be touched, probably because that the directories are read-only.

So in short I think my problem is in point no 2 - where I should make the directory where the packages are stored. Any help is appreciated.

Thanks
Steen

PS: I'm very interested in the ALSA package, but the info on this package states that they are not RPI compatible - so do they not work at the moment?   

bmarkus:
Hi

First, do not use all of the unused part of the SD for data, create a SWAP partition with 256MB size and only the rest for data. Forget ext2, use journaling file system, ext4 is perfect.

This is not enough to mark partition type but you must format it, both data and swap partion. Best is to do it with piCore itself using fdisk, mkfs.ext4 and mkswap commands as root.

When ready, either reboot or use rebuildfstab command as root.

New data partition is not mounted automatically as base system do not need it. Mount, create a directory /tce and reboot.

Now if everything is OK, downloaded extensions will be stored in /tce on the data partition and kept for next reboot.

bmarkus:
Regarding ALSA, at the moment only the sound kernel moduls are available, ALSA tools itself will come in 1-2 weeks.

'Not PPI compatible' doesn't mean it doesnt work, it indicates only it is not within /usr/local. Everything is repo expected to work. If not, it's a bug.

sbp:
Hi bmarkus

Thank you very much for your help. I now have everything running very smoothly - and I can even install packages that will be present after a reboot.

So once again thank you.

EDIT::: Skip this part - I forgot to install libasound!!!!!!!
I have been trying the alsa package, but unfortunately the program that I want to use is complaining about a specific file it is missing:
"error while loading shared libraries: libasound.so.2: cannot open shared object file; No such file or directory"

The error after installing Libasound is ALSA lib conf.c:3705(snd_config_update_r) Cannot access file /usr/local/share/alsa/alsa.conf
Output devices

So I will have to wait some weeks before you hopefully will have build the rest.

Steen

sbp:
Hi, I'm seeking advise on two issues .

1. I'm using the piCore 4.7.3, but as far as can see the raspberry part of this image is not the newest, so I was wondering if it would be possible for me to update this part? Especially there seems to have been some development in the Gpu driver, which have improved the sound from the raspberry.

2. Does anybody know which USB  wifi dongle would be easiest to use in the piCore image?

Thanks

Navigation

[0] Message Index

[#] Next page