Tiny Core Linux
Tiny Core Base => Raspberry Pi => Topic started by: sbp on January 09, 2013, 01:33:39 PM
-
Hi I have updated the piCorePlayer.
PiCorePlayer is a dedicated player for the Squeezebox audio system on a raspberry pi board.
Just updated to piCorePlayer version 1.07 - Noevember 10 2013
It is updated to piCorePlayer1.0 - which now allows high resolution streaming through the HDMI connction
Look here: https://sites.google.com/site/picoreplayer/home/news (http://Look here: https://sites.google.com/site/picoreplayer/home/news)
I have updated piCorePlayer to version 09:
You can get it from here:
https://sites.google.com/site/picoreplayer/home/download (https://sites.google.com/site/picoreplayer/home/download)
I have updated piCorePlayer to version 07:
You can get it from here:
http://rapidshare.com/files/2968815248/piCorePlayer_V07.img
http://rapidshare.com/files/521953170/Changelog%20and%20readme%20PicoreplayerV07.txt
I have just uploaded piCorePlayer version 06 and you can get it here: http://rapidshare.com/files/56046039...eplayerV06.txt
http://rapidshare.com/files/12868434...Player_V06.img
On the basis of your feed-back I have included the "audio group" and added user "tc" to this group.
Please test it as - for me personally I have not had any problems before. But on the other hand the addition of the "audio" group has no negative consequences either- so please test it and see if it is working for you now.
PLEASE NOTE - the password has been changed: So user is tc , Password is . nosoup4u
Other changes:
CHANGELOG:
....................................
Version 06
1. Changed password, so it is the same as SqueezePlug. User=TC, Password=nosoup4u
2. Improved script (the restart of the player was not always functional)
3. Improved script - the first line was missing sometimes.
4. Added the "audio group" and user "tc" to group "audio".
Please report back
Steen
piCoPlayer is a dedicated player (like a Duet receiver) build on a small read-only linux (Microcore) and Triodes excellent Squeezelite player.
It is now even smaller than the first version (26 MB in total). There is no writing to the SD-card and therefore no risk of corruption of your card - just pull the power if you need to. After booting everything is sitting in RAM.
Out of the box, the analog audio via the 3.5" jack is working.
If you want to use a USB DAC, you will need to supply the correct squeezelite commands - for this you can use the setup menu.
The setup-script can be used in two different ways:
1. Connect via SSH (use putty from another computer on the same LAN (user=tc, password=nosoup4you)). At the command promt write; picoplayer which will start the setup-script.
2. If you have a keyboard and screen connected to your raspberry. At the command promt write: picoplayer which will start the setup-script.
The WiFi is supposed to work - I have not tested it, but I have seen a few reports that it is working on the piCore linux which is used for building this player. Please test it and report your findings.
Also suggestions in improving the set-up script is welcome.
The piCoPlayer image can be downloaded here:
http://rapidshare.com/files/2536786570/piCoPlayer_v2.img
Regards
STeen
Changes from version 1:
1. WiFi included (needs further testing)
2. Even smaller now (26 MB)
3. Is optimized for both 256 and 512 MB Raspberry boards
4. SSH access via Dropbear. User = tc Password = nosoup4you
5. Analog and USB sound is tested and is working
6. Included is a set-up menu that makes it easy to:
a. Download and update Squeezelite
b. Auto setup for analog audio from 3.5 jack
c. Detect and show the available USB devices
d. Option to easily change the squeezelite options (output, name MAC address etc)
e. Save these changes so they survive a reboot on the "read-only" microcore structure
f. Reboot to start using the changes.
...............................................................
ORIGINAL MESSAGE
Dear bmarcus.
With your help I have been able to make a small robust squeezebox player based on picore and the small squeeze lite player developed by Triode from the squeezebox community.
I have seen others asking about using squeezelite on the tinycore or microcore system in the forum here, therefore I decided to write a How-to:
It is running headless now I only needed a monitor and keyboard during installation. I did not install xorg or any other GUI programs but did everything using CLI.
So here you go:
Burn the Picore image to a CF card ( I use Win32Diskimager)
Then boot the Raspberry.
As Picore is running in read only mode om a partition called mmcblk0p1 you need to make another partition where it can have all the configuration files and the extensions and the Squeezelite player.
In order to make such a partition I did this (It was here I had the most difficulties) Each line is the commands I used:
fdisk /dev/mmcblk0
n new
p primary
2 partition number 1-4
6 first cylinder
+20M I made a 20 MB partition for this - you could choose any size you want (up to the CF-card size)
t change partition Id
83 linux file system
w to write the changes to the card
sudo reboot
Next I formated it to the ext4 format:
mkfs.ext4 /dev/mmcblk0p2
sudo reboot
Then you need to define where Picore will find your extensions, you do that by this command:
tce-setdrive
And then you choose 2= /mnt/mmcblk0p2
Download Squeezelite and put in a writeable place like mnt/mmcblk0p2, you can so that by this command
wget http://squeezelite.googlecode.com/fi...zelite-armv6hf -P /mnt/mmcblk0p2
Then I had some problems that squeezelite would not start - it turned out that I had to allow it to be executed - using this command
chmod 755 /mnt/mmcblk0p2/squeezelite-armv6hf
You need to install Alsa, flac libmad and libvorbis. You do that by using the package manager in Picore called tce. Therefor at command promt write:
tce
s search
a (a in order to search for Alsa) then Enter
select alsa.tcz (at present no 4) enter
q quit
i install
s search
f (f in order to find flac.tcz (present no 9)) Enter
9 enter
q quit
i install
s search
l (l in order to find libmad.tcz (presently no 57)) Enter
57 enter
q quit
i install
s search
l (l in order to find libvorbis.tcz (presently no 88))
88 enter
q quit
i install
sudo reboot
Then in order to automatically to start Squeezelite everytime the Raspberry reboot, you need to add this program to the bootlocal file which is used for this purpose.
As I have been doing this without GUI the only editor present is the vi editor, which also gave me a hard time. But these are the command you have to use:
sudo vi /opt/bootlocal.sh
Then pres i (for insert)
then move the cursor to the first empty line and write:
sudo /mnt/mmcblk0p2/squeezelite-armv6hf -a 80:4
Press "esc" in order to get out of "insert mode"
Then type
:wq and Enter - in order to save and exit vi
These changes is not actually written to the bootlocal.sh file (as it is in read only mode) but instead the changes is saved another place and during reboot used - so in order to get Picore to save these changes and use them the next time you reboot you have to do a manual backup.
So at command promt type
filetool.sh -b
And now you can reboot and your Raspberry should start Squeezelite. I have tried different Alsa buffer sizes and I think that 80:4 is fine - for me the Squeezelite is in perfect sync with both a Duet and A Logitech radio, if I use to high values like 500:4 or 200:4 the sync is not as perfect. Using 50:4 resulted in some stuttering in the sound
Now you have a dedicated very small Squeezelite player, which boots very rapidly, it doesn't use swap and can survive that you just pull the power plug - so it is almost as an embedded hardware player, like a Duet.
I call it the PicoPlayer
I hope this recipe can be used - please ask if there are any questions
Steen
EDIT 1:
In the next days I will try to enable SSH access, so that we can manage and update this player without the need for a keyboard and monitor.
-
Steen,
thanks a lot for sharing it!
Bela
-
Hi bmarkus.
Sorry, but I'm back for some more help.
I installed Dropbear.
I made a password for tc like this:
passwd
Then I added these three lines to opt/.filetool.lst
etc/passwd
etc/shadow
etc/dropbear
next I used backup:
filetool.sh -b
Then reboot.
Now I start dropbear by:
sudo /usr/local/etc/init.d/dropbear start and everything is fine I can connect via Putty by user: tc and password: (the one I supplied).
BUT my problem is how do I get dropbear to automatically start after a reboot.
I tried to add sudo /usr/local/etc/init.d/dropbear start to /opt/bootlocal.sh
And then do a backup - but somehow this does not start dropbear after a reboot?
Thanks
Steen
-
Hi sbp
You don't need to specify sudo in bootlocal.sh since it runs as root anyway. Your syntax looks correct. Double
check your bootlocal.sh to check it matches exactly.
-
Thank you
This was driving me nuts, but I had a small error in my bootlocal.sh file
So everything is sorted
Thanks
-
Hi sbp
You are welcome. Let me guess, an extra space character in the path?
-
Hi
Now I have it running very well with the squeezelite and dropbear. So if I want to share it I can make a img using a program like diskimager for windows. It is working - but as I have it running on a 4 GB CF-card the image is also 4 GB, even-though microcore and the extensions I have installed is not more that max 50 MB in size the rest is empty and a waste of space..
So I have two questions
1. Is there a solution to make a working image that only consists of the important parts and cuts out the empty part (it isn't even put in a partition).
2. When I look into piCore.img from the repro I can see it consists of the following files arm128_start.elf
arm192_start.elf
arm224_start.elf
arm240_start.elf.
I suppose they have something to do with the memmory setting in the raspberry. As the player I'm working on don't need any graphical interfase, I should probably be able to use the minimal amount of mem for the graphic part. Does that mean that I could delete some of these ??_start.elf files to save space?
Steen
-
Steen,
2) These files related to split up of the RAM to system/video. Better to keep them intact and change only config.txt if necessary.
1) Regarding image, create a small second ext4 partion which is big enough to keep your extensions and have same free space for additional extension later and for backap file, mydata.gz Then save it with dd specifying sectors with count=nnn option part of the first two partions.
Files making piCore-X fits to free space of the boot partion. mmcblk0p1, they are in a cde directory. Content of cde is similar to tce and system installs files from cde at boot time, if cd option used in command line (cmdline.txt). You can do the same, put your preinstalled extensions to a cde in either the boot partion or on the second.
If no second partions, like in case of piCore-X, new image is created with
dd if=/dev/mmcblk0 of=newimage.img bs=1M count=40
Please check piCore-X.
-
Hi bmarkus
First thank you for your continued help.
My fdisk - results in this:
Disk /dev/mmcblk0: 7822 MB, 7822376960 bytes
247 heads, 62 sectors/track, 997 cylinders
Units = cylinders of 15314 * 512 = 7840768 bytes
Device Boot Start End Blocks Id System
/dev/mmcblk0p1 1 5 38254 c Win95 FAT32 (LBA)
/dev/mmcblk0p2 6 10 38285 83 Linux
What I would like to is to use dd to save dev/mmcblk0p1 and mmcblk0p2 in a new image.
So as the whole system is less than 90 MB, I used this command:
root@box:/# dd if=/dev/mmcblk0 of=/mnt/sda1/newimage.img bs=1M count=90
And it seems to work.
I just need to confirm that the image can be burned and boot.
Thanks
Steen
-
So as the whole system is less than 90 MB, I used this command:
root@box:/# dd if=/dev/mmcblk0 of=/mnt/sda1/newimage.img bs=1M count=90
And it seems to work.
I just need to confirm that the image can be burned and boot.
It may seem to work, but I'd consider such a procedure most untrustable, have you run a thorough fsck on the dd'ed image?
dd is agnostic towards filesystems and files and metadata and should never be used to resize or truncate a filesystem.
You could possibly resize your filesystem either before or after invoking dd.
-
So as the whole system is less than 90 MB, I used this command:
root@box:/# dd if=/dev/mmcblk0 of=/mnt/sda1/newimage.img bs=1M count=90
And it seems to work.
I just need to confirm that the image can be burned and boot.
It may seem to work, but I'd consider such a procedure most untrustable, have you run a thorough fsck on the dd'ed image?
dd is agnostic towards filesystems and files and metadata and should never be used to resize or truncate a filesystem.
You could possibly resize your filesystem either before or after invoking dd.
Untrustable? Not at all. There are no resizing and no truncate of file system. It is a correct solution. There are two partitions, all sectors are saved plus few of the unpartitioned area for safety (can be reduced but doesn't harm).
-
Oops!
Seeing fdisk showing "Disk /dev/mmcblk0: 7822 MB" and each partition 38000+ blocks I had somehow assumed the disk was partitioned into 2 equal slices of close to 4GB...
The potential existence of unpartitioned space hadn't even crossed my mind.
In that case I think the "count" parameter is not really necessary.
-
We are not saving partititios but raw disk sectors. Without count= whole 4G would be saved.
-
Once more my bad...
Looking at the details again, I think I finally got it now :P
-
Hi
It is working really good. I managed to make an image of this piCoPlayer which is only 33 MB in size including microcore, and dropbear.
I have announced on the raspberry forum, and made a link to Tiny Core Linux webpages, so hopefully there will be increased interest for your very good small linux system.
To connect via Putty: user=tc Password=nosoup4you
See here http://www.raspberrypi.org/phpBB3/viewtopic.php?f=35&t=29539
Thanks for all you help.
I will try to see if I can get WiFi working also in this player - so I have just ordered a WiFi dongle.
Steen
-
Hi thank all for your help with the script issue - I have now been able to make a set-up script for the piCoPlayer. It will build a menu, where you can choose different options.
PS. I have update the first post with a link to the new version
I will post it here so other beginners like myself can learn:
#!/bin/sh
echo "Remember to use menu 5 (save your changes) before leaving this menu"
echo " "
echo " "
showMenu () {
echo "1) Download and update Squeezelite Player"
echo "2) Use Audio from 3.5 jack"
echo "3) Insert USB DAC and press ENTER to get a list of available ALSA device"
echo "4) Use USB DAC - on next screen give the start options you will use"
echo " "
echo "5) IMPORTANT save your changes NOW before reboot"
echo "6) Reboot - in order to use the changes you have made"
echo "7) Exit menu program"
}
while [ 1 ]
do
showMenu
read CHOICE
case "$CHOICE" in
"1")
echo "Download and Update Squeezeplayer"
wget http://squeezelite.googlecode.com/files/squeezelite-armv6hf -P /mnt/mmcblk0p2
;;
"2")
echo "Use analog audio from 3.5 jack"
sed -i '/squeezelite/d' /opt/bootlocal.sh
sudo echo mnt/mmcblk0p2/tce/squeezelite-armv6hf -n piCoPlayer -a 80:4 -m ab:cd:ef:12:34:01 >> /opt/bootlocal.sh
;;
"3")
echo "Insert USB DAC and pres ENTER to get a list of available ALSA device"
sudo /mnt/mmcblk0p2/tce/squeezelite-armv6hf -l
;;
"4")
echo "Please write the commands you would like to use for starting Squeezelite"
echo "Important you MUST use -a 80:4 and then add additional settings like -o front:CARD=Set,DEV=0 -n piCoPlayer -m ab:cd:ef:12:34:56"
read START_STRING
echo "$START_STRING - Will be used"
while true; do
read -p "Do you wish to use these settings? y/n" yn
case $yn in
[Yy]* ) sed -i '/squeezelite/d' /opt/bootlocal.sh; sudo echo mnt/mmcblk0p2/tce/squeezelite-armv6hf "$START_STRING" >> /opt/bootlocal.sh; break;;
[Nn]* ) exit;;
* ) echo "Please answer yes or no.";;
esac
done
#break;;
;;
"5")
echo "IMPORTANT save your changes NOW before reboot"
filetool.sh -b
;;
"6")
echo "Reboot"
# here it ask for a reboot
while true; do
read -p "Do you wish to reboot? y/n" yn
case $yn in
[Yy]* ) sudo reboot; break;;
[Nn]* ) exit;;
* ) echo "Please answer yes or no.";;
esac
done
;;
"7")
exit
;;
esac
done
This script (picoplayer) was made like this:
sudo vi /usr/local/sbin/picoplayer
Then change the permission so it can be executed:
sudo chmod -R 755 /usr/local/sbin/picoplayer
Finally edit opt/.filetool.lst so that you add the line
usr/local/sbin/picoplayer
Then save the changes with
filetool.sh -b
Regards
Steen
-
Hi sbp
Code tags make it easier for readers to copy code, I added them to your post. They also serve as visual markers
between what you are trying to say and code (or other information) you are posting. To use code tags, click
the # icon when you are writing your post.
-
Code tags make it easier for readers to copy code, I added them to your post. They also serve as visual markers between what you are trying to say and code (or other information) you are posting. To use code tags, click the # icon when you are writing your post.
All true with graphical browsers supporting javascript, but a different story when using text browsers and/or without javascript...
-
Hi tinypoodle
As far as I can tell, the only thing JavaScript does is highlight the text in the code box for copying. The box itself
still shows up when I turn JavaScript off.
-
True, but no # icon to click on.
-
Hi
Just for your info, I just update the piCorePlayer for Raspberry - I don't know if any of you are using a Squeezebox system for music? If you are then please try it now, it can be used as an inexpensive player for this system.
Steen
-
Thanks to bmarcus and his new kernel (3.6.11) I have updated the piCorePlayer:
Hi All piCorePlayer users.
I have just updated to piCoPlayer version 07.
Now the wifi and USB is much better for me - so I hope it will good for you too.
Version 07:
1. Kernel upgraded to 3.6.11 which has fixed many USB problems.
2. Tuned the USB sound by adding "options snd-usb-audio nrpacks=1" to the /etc/modprobe.conf file.
3. Added an Empty " /etc/asound.conf" file. You can now tweak the ALSA profile using this file.
EDIT REMOVED THIS AGAIN 4. Added dwc_otg.speed=1 to the cmdline.txt file (to get rid of some USB problems)
5. Overclocked to 800(otherwise I couldn't use USB-wifi and USB-DAC at the same time)
6. Reduced size to 25 MB
You can get it from here:
You can get it from here:
http://rapidshare.com/files/27225515...Player_V07.img
http://rapidshare.com/files/40140835...eplayerV07.txt
Steen
-
Hello,
I tried before to attempt to make my own version of Squeezelte on TinyCore to make one for i386
It is running however i have problems with Dropbear as each time i make a reboot it losses the tc password ???
I have to first changed the tc password and then I can connect through ssh
other thing it generates new rsa-ssh keys each time
i did the following :
1) install Dropbear
2) added these three lines to opt/filetool.lst
etc/passwd
etc/shadow
etc/dropbear
3) added in bootlocal.sh
/usr/local/etc/init.d/dropbear start
3) cd /optI
4) passwd
5) backup:
filetool.sh -b
6) reboot.
What is wrong ?
-
Just for your information...I played with picoreplayer today. I upgraded the kernel to 3.8.11 and added support for my wireless USB dongle, an RT5370 based adapter. The RT5370 needed a module (crc-ccitt.ko) not included in the standard picoreplayer image and the firmware file (rt2870.bin). I was hoping that 3.8.11 might address the problems with running a USB wifi adapter and a USB sound card. However, the problem still remains. Using a wifi adapter and a USB sound card results in garbled sound. Using either WIFI with the built in sound, or wire ethernet with the USB sound results in crystal clear audio.
Doug.
-
Hi, thanks for your Info on the 3.8.11 kernel. Sorry to hear that the USB issues still are not solved.
Did you try to increase the alsa buffer to something like 200?
Just out of interest how did you manage to update the kernel? I'm still trying to learn.
-
Hi Steen,
From your "How to use a newer kernel?" thread it appears you were able to successfully compile the kernel for tc so I won't go into details about that. Where you are stuck is how to handle the modules. Just a bit of background, modules are drivers that can be loaded at runtime rather than being built into the the kernel image. Modules for tinycore can be found in two places, either in the initramfs (also called initrd) or in tc extensions. In your case the initramfs file is piCore3611a.gz. Examples of extensions containing modules are alsa-modules-3.6.11-piCore.tcz and wireless-3.6.11-piCore.tcz. Modules contained in initramfs are usually those that are required for the kernel to boot and provide basic functions such filesystem, mouse and keyboard. Modules found in the extensions are usually those used for specific environments.
It looks like you were able to compile the modules. Those are the files with the .ko extension. The next step is to extract piCore3611a.gz and replace the module files in piCore3611a.gz with the modules from your compile kernel. Here is what I did.
1. Grab a copy of piCore3611a.gz and place it in a working folder
2. In the working folder, execute the following commands (I am assuming your new initramfs is called piCore3611m.ga)
mkdir piCore3611m
cd piCore3611m
zcat ../piCore3611a.gz | sudo cpio -i -H newc -d
Now you will have the extracted piCore3611a. The modules will be found in lib/modules/3.6.11-piCore. You can see which ones are include by executing
find . -name '*ko'. You will need to replace those files with the modules from your compiled kernel. In fact, all the files in lib/modules need to come from you newly compiled kernel. The folder name in lib/modules/ needs to match the version number of your new kernel. In my case it was 3.8.11-piCore.
Once you have replace the appropriate files, you then need to create a new initramfs. You do this with the following set of commands:
From the folder containing your extracted files execute the following:
sudo find | sudo cpio -o -H newc | gzip -2 > ../piCore3611m.gz
cd ..
advdef -z4 piCore3611m.gz
You new initramfs will be called piCore3611m.gz. You need to get the size of this file in hex but that is needed for cmdline.txt. You can get it with the following command
printf '0x%x\n' $(stat -c%s piCore3611m.gz )
Copy piCore3811m.gz to your USB image, and edit cmdline.txt replacing the second hex number in initrd=0xa00000,0x3c02a7 with the number obtained above. Also edit config.txt and change kernel= and ramfsfile= as appropriate.
Note that the actual kernel image is found in arch/arm/boot and is called Image. You can rename Image to whatever you want but make sure you edit the entry in config.txt appropriately.
That should get you enough to be able to boot your new kernel. You will still need to address replacing the modules in the extensions. I'll cover that in another post if you still help.
-
Hi courtjester
Thank you very much for your very detailed instruction, it helped me a lot in better understanding what needs to be done.
It looks like you were able to compile the modules. Those are the files with the .ko extension. The next step is to extract piCore3611a.gz and replace the module files in piCore3611a.gz with the modules from your compile kernel. Here is what I did.
I wanted to try the new fiq_split version that gsh have been working on. It was release a day ago, and should have improved the USB issue a lot. After compiling it shows up as 3.8.12+
In short I fetched the files from github like this:
mkdir linux-rpi-fig.split
cd linux-rpi-fig.split
git init
git fetch git://github.com/raspberry/linux.git fiq_split:refs/remotes/origin/fiq_split
git checkout fiq_split
This seemed to work, it fetched all the files and they were OK on my Debian Cross compile computer
Next I did
make mrproper
Then I copied the .config file from the running tinycore 3.6.11 to linux-rpi-fig.split
Then I did:
make ARCH=arm -j 3
And the I responded to the questions the best I could (new options etc) and then it started compiling
And I found the arch/arm/boot/Image and renamed it to kernel3611a.img (so that I did not need to change anything in the config.txt fil)
NEXT the modules:
1. Grab a copy of piCore3611a.gz and place it in a working folder
2. In the working folder, execute the following commands (I am assuming your new initramfs is called piCore3611m.ga)
mkdir piCore3611m
cd piCore3611m
zcat ../piCore3611a.gz | sudo cpio -i -H newc -d
Now you will have the extracted piCore3611a. The modules will be found in lib/modules/3.6.11-piCore. You can see which ones are include by executing
find . -name '*ko'. You will need to replace those files with the modules from your compiled kernel. In fact, all the files in lib/modules need to come from you newly compiled kernel. The folder name in lib/modules/ needs to match the version number of your new kernel. In my case it was 3.8.11-piCore.
Once you have replace the appropriate files, you then need to create a new initramfs. You do this with the following set of commands:
From the folder containing your extracted files execute the following:
sudo find | sudo cpio -o -H newc | gzip -2 > ../piCore3611m.gz
cd ..
advdef -z4 piCore3611m.gz
You new initramfs will be called piCore3611m.gz. You need to get the size of this file in hex but that is needed for cmdline.txt. You can get it with the following command
printf '0x%x\n' $(stat -c%s piCore3611m.gz )
Copy piCore3811m.gz to your USB image, and edit cmdline.txt replacing the second hex number in initrd=0xa00000,0x3c02a7 with the number obtained above. Also edit config.txt and change kernel= and ramfsfile= as appropriate.
Thanks I build the modules and found then in root/modules/lib/modules. Here was a directory called 3.8.12+-picore with a subdirectory called kernel which contained the following directories
-arch
-crypto
-drivers
-fs
-lib
-net
-sound
And the ko files were present in these directories.
So I untarred the old picore3611a and deleted the directory lib/modules/3.6.11-piCore and placed the 3.8.12+-piCore here instead. Then:
sudo find | sudo cpio -o -H newc | gzip -2 > ../piCore3611m.gz
cd ..
advdef -z4 piCore3611m.gz
And copied this to the SD-card
I also copied new bootcode.bin, fixup.dat, fixup_cd.dat, fixup_x.dat, start.elf, start_cd.elf and start_x.elf to the card. Obtained from here: https://github.com/raspberrypi/firmware/tree/fiq_split/boot
I changed the size of the new piCore3611m.gz in the config.txt file
BUT when I boot on the new card it results in kernel panic:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown block (1,0)
unwind_backtrace+0x0/0xf0) from [>c0525d38>9 mount_block_root+0x21c/0x280)
and 4 more lines
and then:
PANIC VFS: Unable to mount root fs on unknown block (1,0)
Entering kdb (current=0xcd82ac80, pid 1) due to Keyboard Entry
Kdb>
So do you see where I do something wrong?
Steen
-
Hi courtjester, tinypoodle, Rich and bmarcus - I want to thank you all for your help and kind teaching a beginner how to build a new kernel for picore.
Finally I managed to build a new kernel which could boot. The last piece was how to make the modules - which courtjester described in a way, so that I could manage it.
The prolem described above with the kernel panic, was because I put in the size of the picore.gz in hex, the wrong place. I had put it in the config.txt file:
ramfsaddr= which is wrong, I should ave put it in the cmdline.txt (as also written by courtjester).
So in short. I now can boot with kernel 3.8.12+
But there seems to be some problems with ALSA - which I need to figure out.
Thank you for your patience and help
-
Sorry I still need some help.
The two TCE's: ALSA and Wifi which contain a specific 3.6.11 part will not install on my newly build kernel (I now know that it is because the uname is 3.8.12-picore+ whereas it should be 3.6.11-picore).
Therefore I extracted the alsa-modules-3.6.11-piCore.tcz;
In this extracted tcz I renamed \lib\modules\3.6.11-piCore\ to \lib\modules\3.8.12-piCore+\
Then I updated all the files in the original \lib\modules\3.6.11-piCore\kernel\sound\ with the same files from the newly build modules from the 3.8.12 version.
Then I repacked the alsa-modules-3.6.11-piCore.tcz as alsa-modules-3.8.12-piCore+.tcz
I did the same to the
But it does not work - after a reboot this error occurs:
amixer: Mixer attach default error: No such file or directory
/opt/bootlocal.sh line 5: usr/local/bin/wifi.sh; not found
[00:00:17.868869] test_open: 159 playback open error; No such device
[00:00:17.869556] output_init: 1359 unable to open output device
However the Dropbear is working fine. So my kernel seems OK, it is now just a matter of fixing the ALSA and Wireless, so that they allow using a newer kernel.
Any advice?
Steen
-
Doublecheck on matching cases (upper/lower).
Also, never ever substitute slashes by backwards slashes.
-
Use modules built with your new kernel. Kernel modules must match the kernel.
-
Hi Steen,
The next step is to update the modules in the alsa-modules extension (and the wireless modules extension). tinycore extensions are stored in squashfs format. To find which files are in an extension you will have to unsquash the extension as follows:
1. copy the extension to a working folder.
2. from the working folder use the unsquashfs command to unsquash the extension. For example
unsquashfs -d alsa-modules-3.6.11-piCore alsa-modules-3.6.11-piCore.tcz
will unsquash the alsa modules for the 3.6.11 kernel into a folder called alsa-modules-3.6.11-piCore.
Now that you have the alsa modules unsquashed, you can see what files need to be included in the alsa modules file for your kernel.
Now you need to create an alsa modules extension for your kernel 3.8.12+. I would create a folder called alsa-modules-3.8.12+-piCore in your working directory with the same folder structure as alsa-modules-3.6.11-piCore. Note that anywhere you see 3.6.11, you will need to use 3.8.12+. Copy the modules from your compiled kernel to the appropriate places in the new extension folder. There is one more file that you will need from the alsa-modules-3.6.11-piCore folder:
usr/local/tce.installed/alsa-modules-3.6.11-piCore
Copy this file to your new extension folder and rename it to
usr/local/tce.installed/alsa-modules-3.8.12+-piCore
Now from your working folder run the following commands:
mksquashfs alsa-modules-3.8.12+-piCore alsa-modules-3.8.12+-piCore.tcz
md5sum alsa-modules-3.8.12+-piCore.tcz > alsa-modules-3.8.12+-piCore.tcz.md5.txt
This will create two files alsa-modules-3.8.12+-piCore.tcz and alsa-modules-3.8.12+-piCore.tcz.md5.txt. Copy these two files to the tce/optional folder on the sdcard, insert the sdcard into the rpi and reboot. This should get alsa working. You can use the same procedure for the wireless modules.
Hope this helps.
Doug.
-
Doug,
Thank you very much for your detailed explanations - with this help I managed to update the kernel, the modules and the ALSA and WiFi packages in microcore.
I used the 3.8.12+ kernel which gsh from the raspberry foundation is working on. This branch is specifically made in order to improve or hopefully fix the USB issues.
For me the USB handling is now much better, I now can play music via a USB-DAC with a raspberry connected via a WiFi-dongle at full speed (150 Mbit/s) and using WPA2 protection. So it is much better now.
I think you should try it and see if it has improved the situation for you as well.
You can get it from here:https://sites.google.com/site/picoreplayer/home/download (https://sites.google.com/site/picoreplayer/home/download)
-------
BUT I still have a few issues that you might know the answer for:
After having build the kernel and the modules, I could see that I have many modules that I will not need. Can I just delete these modules (the *.ko files) and then do the: sudo find | sudo cpio -o -H newc | gzip -2 > ../piCore3611m.gz thing again?
Or will I have to start all over again and compile a new kernel with the correct options chosen (it is difficult because there are so many options that I don't know the exact meaning of).
Steen
-
Looking at following script may give you an idea, though it may not apply to your case ad verbatim.
http://forum.tinycorelinux.net/index.php/topic,9028.0.html
-
I used the 3.8.12+ kernel which gsh from the raspberry foundation is working on. This branch is specifically made in order to improve or hopefully fix the USB issues.
Is it the kernel at http://elinux.org/RPi_Kernel_Compilation or from different location?
-
Hi bmarkus.
It is from here: https://github.com/raspberrypi/linux/tree/fiq_split (https://github.com/raspberrypi/linux/tree/fiq_split) This is a special experimental branch made by gsh who is hired in order to improve or fix the USB problem on the raspberry pi.
See the discussion here: http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=39175
Steen
-
Hi Steen,
I have been kind of off the grid for the last few days.
Glad you got PicorePlayer working with the experimental USB code.
You can just delete any of the kernel modules you do not need and then regenerate the piCore file. No need to recompile the kernel. Just make sure you do not really need the modules you delete. I don't know if you know this, but you can tell which modules actually get loaded at run time by running lsmod from the PicorePlayer terminal.
If I were you, I would rename the piCore file to be consistent with the kernel you are using. piCore3611m.gz implies you are using the 3.6.11 kernel. You would be better off calling it piCore3812exp.gz or something similar. Since you are already changing the "a" to an "m" you may as well go the rest of the way.
Doug.
-
new version available:
piCorePlayer version 1.0.
It is now possible to stream high resolution audio (up to 192 kHz) through the HDMI connection (previously it would downsample to 48 kHz) - thanks to giantpopples for the suggestion.
The Kernel is updated to version 3.8.13+ the special fiq_split version which hopefully one day will solve the USB problems found in the raspberry.
It is trimmed in size (28 MB again)
There are several tweaks in the cmdline.txt and config.txt
Look here: https://sites.google.com/site/picoreplayer/home/news
Please report back
-
Hi
It seems like the learning curve continue.
Now I can build a update the kernel and make the modules, but as more and more people use the piCorePlayer the demand for support of new WiF cards increase.
It seems like especially those who have a Radlink card have problems.
Ralink RT5370 is reported not working
An adaptor using the Ralink RTL8188S driver is reported not working
but also an adaptor using Realtek RTL8191SU is reported not working
So I'm willing to learn how to support these adaptors, but where do I start?
Steen
-
Steen
as a starting point check wether these cards are supported or not by Raspbian at
http://elinux.org/RPi_VerifiedPeripherals#USB_Wi-Fi_Adapters
Keep in mind that info ther may be obsolate, related to different kernel, etc. But you may find useful info e.g. required firmware, driver, etc.
Next check support status in other distros, not only Raspberry Pi but x86.
Than you may look into kernel source and as usual Google.
Also check the fullo piCore kernel modul pack for drivers, firmware including staging where you find not yet stable experimental modules.
-
Hi all,
This post is partially off-topic, since I use my own install of TinyCore/Squeezelite, but I see the PicoPlayer has the same problem.
I've ordered and received this WiPi dongle from farnell: Link to WiPi dongle (http://nl.farnell.com/element14/wipi/dongle-wifi-usb-for-raspberry-pi/dp/2133900), it's got the RT5370 chipset.
It's working on Raspbian, but not on Tinycore, probably because of this:
Just for your information...I played with picoreplayer today. I upgraded the kernel to 3.8.11 and added support for my wireless USB dongle, an RT5370 based adapter. The RT5370 needed a module (crc-ccitt.ko) not included in the standard picoreplayer image and the firmware file (rt2870.bin).
But I don't know how to install/make/build the modules. Can you point me in the right direction?
-
Hi Gerrelt
I also plan on trying to get that wifi card working but I haven't found the time.
Basicly you have to build the modules - I followed the advice from here: http://elinux.org/RPi_Kernel_Compilation
And if you use the .config file that follows bmarcus builds you will need to change the path to the cross-compiler in this .config file. Then: make ARCH=arm modules
This will build the modules, then you will need to make a new wifi-"kernel".tcz This is described by courtjester a few post above. He describes the Alsa-modules but you will need to change the wifi module.
Furthermore you should make a lib directory here and add the crc-ccitt.ko module which you will need to locate in all your newly build modules (I can't remember where I found it) next you should make a firmware directory and in that add the rt2870.bin.
Then pack it up as described by courtjester below.
Please report back if you succeed.
Do you have the wifi-card?
Steen
The next step is to update the modules in the alsa-modules extension (and the wireless modules extension). tinycore extensions are stored in squashfs format. To find which files are in an extension you will have to unsquash the extension as follows:
1. copy the extension to a working folder.
2. from the working folder use the unsquashfs command to unsquash the extension. For example
unsquashfs -d alsa-modules-3.6.11-piCore alsa-modules-3.6.11-piCore.tcz
will unsquash the alsa modules for the 3.6.11 kernel into a folder called alsa-modules-3.6.11-piCore.
Now that you have the alsa modules unsquashed, you can see what files need to be included in the alsa modules file for your kernel.
Now you need to create an alsa modules extension for your kernel 3.8.12+. I would create a folder called alsa-modules-3.8.12+-piCore in your working directory with the same folder structure as alsa-modules-3.6.11-piCore. Note that anywhere you see 3.6.11, you will need to use 3.8.12+. Copy the modules from your compiled kernel to the appropriate places in the new extension folder. There is one more file that you will need from the alsa-modules-3.6.11-piCore folder:
usr/local/tce.installed/alsa-modules-3.6.11-piCore
Copy this file to your new extension folder and rename it to
usr/local/tce.installed/alsa-modules-3.8.12+-piCore
Now from your working folder run the following commands:
mksquashfs alsa-modules-3.8.12+-piCore alsa-modules-3.8.12+-piCore.tcz
md5sum alsa-modules-3.8.12+-piCore.tcz > alsa-modules-3.8.12+-piCore.tcz.md5.txt
This will create two files alsa-modules-3.8.12+-piCore.tcz and alsa-modules-3.8.12+-piCore.tcz.md5.txt. Copy these two files to the tce/optional folder on the sdcard, insert the sdcard into the rpi and reboot. This should get alsa working. You can use the same procedure for the wireless modules.
Hope this helps.
Doug.
-
Please report back if you succeed.
Do you have the wifi-card?
Thanks, Steen!
I will do some studying, it's more complex then I thought.
Yes, I allready have this wifi card, and I've used it in combination with Raspbian wheezy without problems.
Greetings,
Gerrelt.
-
Status update:
I've been on a rollercoaster ride with this..
At first I was focused at getting the crc-ccitt.ko module to work, but at the end I discovered that it's allready present in TinyCore:
tc@cherry:~$ sudo find / -name crc-ccitt.ko
/lib/modules/3.8.13-002.piCore/kernel/lib/crc-ccitt.ko
I also discovered that the WiPi dongle is recognized by the Raspberry (see the arrows):
tc@cherry:~$ lsusb
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
----> Bus 001 Device 004: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter <----
Bus 001 Device 005: ID 2101:8500 ActionStar
Bus 001 Device 006: ID 2101:8501 ActionStar
Bus 001 Device 007: ID 0d8c:000c C-Media Electronics, Inc. Audio Adapter
At first I used it with an USB extension cable, and then it wasn't recognised. When plugged directly into the raspberry, it was recognised. As shown in the above lsusb output.
But it doesn't work, I cannot get the wlan0 up:tc@cherry:/opt$ ifconfig wlan0 up
ifconfig: SIOCSIFFLAGS: Operation not permitted
I found this in the dmesg:
tc@cherry:~$ dmesg | grep rt2
[ 32.618387] usbcore: registered new interface driver rt2800usb
[ 36.361078] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware.
[ 37.845923] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware.
[ 37.914414] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware.
When googling these errors, people seem to suggest to compile the Ralink drivers.
I started doing that, but then I discovered I had to compile the kernel for this too (maybe not correct?..).
Now, the problem is that compiling the kernel is quite complex, and the only Linux machines I got are Raspberry Pi's.. So cross compiling is out of the question. Compiling for 12 hours and then discovering it doesn't work does not sound like fun. :)
What still puzzles me is that the WiPi dongle has chipset RT5370, and the error messages are about the rt2800usb driver..
-
Hi Gerrelt
I really also would like this wifi stick to be available in microcore.
1. Good that you have the crc-ccitt.ko module in kernel -one problem solved.
2. I think now that the problem is that you are lacking the firmware.
Look here: http://mitchtech.net/realtek-wireless-dongle-rt3070-on-the-raspberry-pi/ (http://mitchtech.net/realtek-wireless-dongle-rt3070-on-the-raspberry-pi/) so according to his blog I think that you should be able to make a RT5370.tcz which include the directory /lib/firmware/rt2870.bin
I think that I can cross-compile a module for you if you need it - but then we need to be clear about which kernel you are using and which module you need.
Steen
-
If it works with Raspbian, check which fw is loaded.
-
I just plugged into a Raspbian Wheeze raspberry, and this is the output from lsmod:
pi@Blueberry ~ $ lsmod
Module Size Used by
snd_bcm2835 16304 0
snd_usb_audio 104097 1
snd_pcm 77560 3 snd_bcm2835,snd_usb_audio
snd_page_alloc 5145 1 snd_pcm
snd_hwdep 5929 1 snd_usb_audio
snd_usbmidi_lib 18067 1 snd_usb_audio
snd_seq_midi 4591 0
snd_seq_midi_event 6544 1 snd_seq_midi
snd_rawmidi 21160 2 snd_usbmidi_lib,snd_seq_midi
arc4 1676 2
snd_seq 53329 2 snd_seq_midi_event,snd_seq_midi
snd_timer 19998 2 snd_pcm,snd_seq
snd_seq_device 6438 3 snd_seq,snd_rawmidi,snd_seq_midi
rt2800usb 14940 0
rt2800lib 55351 1 rt2800usb
crc_ccitt 1522 1 rt2800lib
rt2x00usb 11215 1 rt2800usb
snd 58447 10 snd_bcm2835,snd_usb_audio,snd_hwdep,snd_timer,snd_pcm,snd_seq,snd_rawmidi,snd_usbmidi_lib,snd_seq_device
rt2x00lib 42334 3 rt2x00usb,rt2800lib,rt2800usb
mac80211 273413 3 rt2x00lib,rt2x00usb,rt2800lib
evdev 9426 1
cfg80211 184163 2 mac80211,rt2x00lib
rfkill 18202 2 cfg80211
leds_gpio 2235 0
led_class 3562 2 leds_gpio,rt2x00lib
Hmmm...looks like the same as on TinyCore?
-
I'm working on piCore 5.0 currently with 3.10 kernel. Hope it will be in alpha stage where you can test WiFi. Stay tuned.
-
OK, I will wait for it, I will keep my fingers crossed.. ;D
-
Hi bmarkus.
I'm also looking forward to try this.
Will the directory structure in version 5 be different from the 4.7.7 version?
Please tell me if I can help in any way.
Steen
-
Hi Steen,
5.0 is based on the TC scripts used in the 5.0 x86, which means for example dropped SCM extension type support which was not used here BTW. Other changes:
- EGLIBC 2.18 (current is 2.13)
- Busybox 1.21
- zlib 1.2.8
- GCC 4.7.3
- updated other components (udev, e2fs, ...)
Kernel is not decided, requires more testing. Anyhow, CLI version will be availabe soon hopefully.
-
I see that MicroCore v5.0 has just been released;
Any update on the compatibility of Ralink RT5370 wifi dongles?!!
I bought a Ralink RT5370 based dongle for Raspbian prior to wanting moving to PiCoPlayer, would love to have it working!!
Thanks for great development so far!
-
Hi all
At last I'm ready with a new version.
Please try piCorePlayer version 1.07 - you can read about it here and download it from the piCorePlayer webpages: https://sites.google.com/site/picoreplayer/home/news (https://sites.google.com/site/picoreplayer/home/news)
Changes:
- updated kernel to rpi-linux-3.11.5
- better picoreplayer script, so now it is much easier to change the Squeezelite settings, like name etc - and you can see what the current settings are.
- more wifi adaptors are supported (I think that most the Ralink adaptors are working now)
- better wifi script (thanks to Randy McEuen who made it possible to save non-protected wifi's as well)
- The new version is larger than usual, as this has been requested by many who wanted to add further packages to the piCorePlayer. If needed I can provide a smaller version.
BIG thanks to Randy McEuen who helped by beta-testing the new version and also provided a valuable patch to the wifi.sh script in the microcore community.
Please report your findings.
Steen
PS: bmarkus is so fast with new updates on piCore 5, that I'm behind at the moment :-)
-
Please skip piCorePlayer version 1.07 and go directly to piCorePlayer 1.08
(I forgot to add support for MP3 playback)
Steen
-
Hello,
One silly question. Why are you using a fat16 filesystem instead of ext3 or ext4?
-
Hi Please try the new version of piCorePlayer1.14
(http://s15.postimg.org/isfx59iuj/pi_Core_Player1_14.jpg)
It has build in webserver, so the configuration can be done via your browser.
It supports audio out via:
Analog out (3.5" audio jack)
USB-DAC
HDMI
I2S - either analog DAC or Digital out
STeen
-
....
I installed Dropbear.
I made a password for tc like this:
passwd
Then I added these three lines to opt/.filetool.lst
etc/passwd
etc/shadow
etc/dropbear
next I used backup:
filetool.sh -b
....
Hi Steen,
I think you need to remove "etc/dropbear" from /opt/.filetool.lst as it prevents the backup from completing successfully.
Check the error message in /tmp/backup_status and timestamp of /tmp/backup_done if it exists.
I think, if the backup is successful, both /tmp/backup_status and /tmp/backup_done should exist and be zero bytes (empty). Their timestamp should be the same.
regards
-
Is there any way to speed up the boot of the picoreplayer?
I have it running on a raspberrypi A with a wifi dongle and a Hifiberry. It tooks more than 40 seconds to boot from scratch.
It would be great if the boot time could be optimized.
-
+1 for request to speed up boot.
dmesg shows 40 instances of "waiting module removal not supported: please upgrade"
I have installed IQAudio card which plays beautifully phono to amp. A pendrive solely attached to RPi is powered by a PSU 5V/3A. Usbutils and nano editor also installed yesterday, after which I experienced slow boot. I am also seeing Error opening terminal: xterm-256color. [The warnings disappeared after umount and mounting the pendrive and a reboot]
None of this seems to affect the music :) Thanks Steen and Bela for a fantastic program. Its now booting up smartly.
-
Hello again,
I have just bought a pair of QSB speakers, that work great, but the initial volume is very low. I can increase the base volume using alsamixer but it is cleared on each boot (obviously). It would be great if we can configure it through the web interface.
This is going to be my second picoreplayer on the house and expecting to increase the family soon with a couple more :)
Gabriel
-
Hi Thanks for using piCorePlayer.
I have already included your suggestion in the a version.
But I still have to decide which kernel to use - so stay tuned.
Steen
-
Hi please try the new version.
Your suggestion about custom ALSA settings after reboot, has been added.
Greg rewrote much of the cgi-scripts and web-pages, and the web-server is now busybox httpd server.
Get it from here: http://sourceforge.net/projects/picoreplayer/files/insitu/piCorePlayer1.17/piCorePlayer1.17.img/download
/Steen
-
Hello,
Sorry for the delay, It is great to have the ALSA settings.
Would you mind how can I persist it?
I had modified the alsamixer value, and set on the ALSA output level setting on the picoreplayer "Custom ALSA output level" but the level is still reset after reboot.
What am I missing?
Again, thank you for your awesome work and support.
Gabriel
-
Hey... :)
Maybe ask the quistion, over at @slimserver forum
http://forums.slimdevices.com/showthread.php?97803-piCoPlayer-Squeezelite-on-Microcore-linux-An-embedded-OS-in-RAM-with-Squeezelite (http://forums.slimdevices.com/showthread.php?97803-piCoPlayer-Squeezelite-on-Microcore-linux-An-embedded-OS-in-RAM-with-Squeezelite)
Otherwise, use amixer, and set lines for volume in /opt/bootlocal.lst eg.
Amixer sset 'youre card here' 123 unmute etc... Etc..
Remember to do filetool.sh -b - this will save the line(s) in /opt/bootlocal.lst also after reboot...
Regards;
Jesper.
-
Hi!
I have just downloaded v1.18b tar file, and have a Raspberry Pi B+ with HifiBerry Digi+, specifically for the purpose of turning it into a Squeezebox using your great software. I'm having a few noob teething problems.
I have been able to get the tinycore booted on the RPi by loading the contents of mmcblk0p1 folder onto the SD card, but picoreplayer is 'not found' when I type that. I have seen early posts with command line instructions (e.g. http://forums.slimdevices.com/showthread.php?97046-Announce-Squeezelite-a-small-headless-squeezeplay-emulator-for-linux-(alsa-only)&p=732506&viewfull=1#post732506).
Are those still current / necessary once I'm at the tinycore shell prompt?
Sorry for the probably dumb question but I'm new with this stuff and confused / wary enough to ask before blindly trying it.
Any/all help gratefully received :)
-
Hi thanks for trying piCorePlayer.
I think the easiest way is simply to plug in a LAN cable, then boot your raspberry.
Next from another computer open your browser and go to the IP address of your piCorePlayer, something like 192.168.1.24 or similar.
Then you should be able to change all the settings you need to change.
To find the IP address of your raspberry, you can look in your routers log or use something like "Advanced IP-scanner" there is a link on the piCorePlayer web-page.
Steen
-
thanks for the reply Steen!
Unfortunately I'm not yet at the stage where I can see the picoreplayer on my network via my browser.. (I can see other things, e.g. my wireless printer, router set up pages).
My issue is (I think) in getting the Pi B+'s Micro SD card set up properly. 1.18b unzips into a 'mnt' folder with 'mmcblk0p1' inside it and then:
6.0_3163.gz
bootcode.bin
cmdline.txt
config.txt
COPYING.linux
fixup_cd.dat
fixup_x.dat
fixup.dat
LICENCE.broadcom
LICENCE.piCorePlayer
RELEASE.txt
start_cd.elf
start_x.elf
start.elf
zImage3163B.img
inside that. My current basic question is how to configure the Micro SD card - if I just copy the whole mnt structure into it the Pi B+ doesn't boot up (green light on solidly, no output to TV via HDMI). If I just copy the contents of the 'mmcblk0p1' to the 'top level' of the SD card the Pi boots into tiny core, I can see the prompt on my TV and seemingly interact with it via keyboard, but if I type pcicoreplayer at the prompt it says 'not found'.
So when I get to the tinycore prompt as above do I then still have to do the steps in italics below to get things up and running? Is it right that the necessary files are nested 2 folders down in the tar file and I should ignore that structure? Or have I possibly got some other problems?
Thanks for your patience with me/this.
As Picore is running in read only mode om a partition called mmcblk0p1 you need to make another partition where it can have all the configuration files and the extensions and the Squeezelite player.
In order to make such a partition I did this (It was here I had the most difficulties) Each line is the commands I used:
fdisk /dev/mmcblk0
n new
p primary
2 partition number 1-4
6 first cylinder
+20M I made a 20 MB partition for this - you could choose any size you want (up to the CF-card size)
EDIT I Forgot the following two lines in my first description
t change partition Id
83 linux file system
w to write the changes to the card
sudo reboot
Next I formated it to the ext4 format:
mkfs.ext4 /dev/mmcblk0p2
sudo reboot
Then you need to define where Picore will find your extensions, you do that by this command:
tce-setdrive
And then you choose 2= /mnt/mmcblk0p2
Download Squeezelite and put in a writeable place like mnt/mmcblk0p2, you can so that by this command
wget http://squeezelite.googlecode.com/fi...zelite-armv6hf -P /mnt/mmcblk0p2
Then I had some problems that squeezelite would not start - it turned out that I had to allow it to be executed - using this command
chmod 755 /mnt/mmcblk0p2/squeezelite-armv6hf
You need to install Alsa, flac libmad and libvorbis. You do that by using the package manager in Picore called tce. Therefor at command promt write:
tce
s search
a (a in order to search for Alsa) then Enter
select alsa.tcz (at present no 4) enter
q quit
i install
s search
f (f in order to find flac.tcz (present no 9)) Enter
9 enter
q quit
i install
s search
l (l in order to find libmad.tcz (presently no 57)) Enter
57 enter
q quit
i install
s search
l (l in order to find libvorbis.tcz (presently no 88))
88 enter
q quit
i install
sudo reboot
Then in order to automatically to start Squeezelite everytime the Raspberry reboot, you need to add this program to the bootlocal file which is used for this purpose.
As I have been doing this without GUI the only editor present is the vi editor, which also gave me a hard time. But these are the command you have to use:
sudo vi /opt/bootlocal.sh
Then pres i (for insert)
then move the cursor to the first empty line and write:
sudo /mnt/mmcblk0p2/squeezelite-armv6hf -a 80:4
Press "esc" in order to get out of "insert mode"
Then type
:wq and Enter - in order to save and exit vi
These changes is not actually written to the bootlocal.sh file (as it is in read only mode) but insteas the changes is saved another place and during reboot used - so in order to get Picore to save these changes and use them the next time you reboot you have to do a manual backup.
So at command promt type
filetool.sh -b
And now you can reboot and your Raspberry should start Squeezelite. I have tried different Alsa buffer sizes and I think that 80:4 is fine - for me the Squeezelite is in perfect sync with both a Duet and A Logitech radio, if I use to high values like 500:4 or 200:4 the sync is not as perfect. Using 50:4 resulted in some stuttering in the sound
Now you have a dedicated very small Squeezelite player, which boots very rapidly, it doesn't use swap and can survive that you just pull the power plug - so it is almost as an embedded hardware player, like a Duet.
-
Hi, you don't have to do all this.
You only need to download the picoreplayer1.18b.img.
Next you burn this image to your SD card (I use win32discimager. https://sites.google.com/site/picoreplayer/home/links ).
That's all, now you simply use this SDcard in your raspberry and boot, then it should show up on your network.
Steen
-
Hi all.
Greg and I are happy to release a new version.
Here is the changelog:
- Kernel updated to 4.1.6 with a possible important USB fix for those using Schitt Modi 2 audio box (or similar).
Added tab, so it is easy to jump from one piCorePlayer to another present in your system.
Re-added the controls allowing you to skip tracks and adjust volume up/down.
Automatic select the correct timezone (depending on your location based on IP geo-location).
Added a "mode" tab at the bottom of the "Main Page" allowing us to present more or less options/settings on the pages.
Improved wifi on/off logic, so now a reboot is not needed anymore.
Added a normal cron job option.
Improved boot speed.
Numerous bugfixes.
Please report your findings as always.
Please notice the new options on the screenshot below:
-
December 12 2015
Please try the new release (piCorePlayer 1.22).
Ralphy has been a great support and help during the development - so thank you very much.
https://sites.google.com/site/picoreplayer/home/news
Changes:
- Updated kernel 4.1.12.
- Updated piCore (even faster booting).
- Touchscreen support improved (the official raspberry 7" touchscreen).
- Calibration file included.
- Jivelite can be installed from webpage.
- VU-Meters can be changed from webpage.
- New high quality default VU-Meter made by forum member Kolossos - thank you very much.
- Backlight on/off (Jivelite settings/screen/screensavers/when stopped/Display off ) then the backlight will be off when not playing, and on when you touch the screen.
- Ralphy is providing two versions of squeezelite. The basic version which is shipped with pCP allow playback of pcm, (wav/aiff), flac, mp3, ogg and aac. It is only 1 Mb in size. The ffmpeg version is bigger (12 MB) and allows in addition playback of ALAC and WMA via build in ffmpeg. In the Main page you can choose which version you will use.
- After customizing Jivelite you need to save your changes to the next reboot. This is done on the webpage ("advanced tab" in the bottom and choose "backup").
Download:
https://sites.google.com/site/picoreplayer/home/download
This software has been around for a couple of years now, but has a fairly low profile at diyAudio.
regards
Steen & Greg
-
Hi: Until today I still do not know how the PiCore Player system works:
What RASPI board do I need? Vers B, B+, B2, A ??
What hardware add on board (sound card) do I need? What is the name of the brand and where can I buy it?
Which OS needs to be copied to the sd card? MicroCore plus something else?
What is Sqeezlite?
Sorry for the simple questions but I tried to figure out how that project works but was not able.
What do I need from Logitech?
-
Hi: Until today I still do not know how the PiCore Player system works:
What RASPI board do I need? Vers B, B+, B2, A ??
What hardware add on board (sound card) do I need? What is the name of the brand and where can I buy it?
Which OS needs to be copied to the sd card? MicroCore plus something else?
What is Sqeezlite?
Sorry for the simple questions but I tried to figure out how that project works but was not able.
What do I need from Logitech?
Visit piCorePlayer WEB:
https://sites.google.com/site/picoreplayer/home
-
OK Thanx -
So I just need a PaspberryPI B,or B+ or B2 plus a sd card. I will download the piCorePlayer and dd the image.
So far so good. But what is the " 2. A running Logitech Media Server which you can connect to".
Is that a piece of software or a hardware add on?
Thank you for your help.
-
December 12 2015
Please try the new release (piCorePlayer 1.22).
Ralphy has been a great support and help during the development - so thank you very much.
https://sites.google.com/site/picoreplayer/home/news
Changes:
- Updated kernel 4.1.12.
- Updated piCore (even faster booting).
- Touchscreen support improved (the official raspberry 7" touchscreen).
- Calibration file included.
- Jivelite can be installed from webpage.
- VU-Meters can be changed from webpage.
- New high quality default VU-Meter made by forum member Kolossos - thank you very much.
- Backlight on/off (Jivelite settings/screen/screensavers/when stopped/Display off ) then the backlight will be off when not playing, and on when you touch the screen.
- Ralphy is providing two versions of squeezelite. The basic version which is shipped with pCP allow playback of pcm, (wav/aiff), flac, mp3, ogg and aac. It is only 1 Mb in size. The ffmpeg version is bigger (12 MB) and allows in addition playback of ALAC and WMA via build in ffmpeg. In the Main page you can choose which version you will use.
- After customizing Jivelite you need to save your changes to the next reboot. This is done on the webpage ("advanced tab" in the bottom and choose "backup").
Download:
https://sites.google.com/site/picoreplayer/home/download
This software has been around for a couple of years now, but has a fairly low profile at diyAudio.
regards
Steen & Greg
Hi Steen and Greg
Thanks for providing this great player.
I have three installed here at home and they are always on so that they only need to be controlled from phone/tablet/LMS-webinterface. Unfortunately this level of comfort demands my power-amps to be always-on.
So one suggestion for a future change that would make it perfect for my use:
Could you make it part of the release to toggle one of the GPIO's according to the on/off status of the player as controlled from the LMS.
This I would use to control power for the amps driving my speakers.
Best regards
Claus
-
So one suggestion for a future change that would make it perfect for my use:
Could you make it part of the release to toggle one of the GPIO's according to the on/off status of the player as controlled from the LMS.
I thought they had a polling script that would monitor the status through the LMS cli interface and toggle the GPIO through the use of shell scripts.
If not, I have this functionality compiled into the squeezelite application. GPIO pin is selectabe via a command line switch.
-
I found what I was referring to.
http://www.pinkfishmedia.net/forum/showthread.php?t=165465
Take look down on the thread, Greg posted a script that should do what you want.
-
So one suggestion for a future change that would make it perfect for my use:
Could you make it part of the release to toggle one of the GPIO's according to the on/off status of the player as controlled from the LMS.
I thought they had a polling script that would monitor the status through the LMS cli interface and toggle the GPIO through the use of shell scripts.
If not, I have this functionality compiled into the squeezelite application. GPIO pin is selectabe via a command line switch.
A polling script that looks for activity on the I2C bus. This cannot be the best solution.
When I turn the player on/off a low but audible blob is heard from the player. This indicates that something happens on the player.I have no idea where to find this on/off signal but it must be there.
Since this signal might even be somewhere in Squeezelite I find it best for this to be part of the distribution.
Whether this should be enabled and to what GPIO-port could be a parameter in the settings on the piCorePlayer.
Best regards
Claus
-
A polling script that looks for activity on the I2C bus. This cannot be the best solution.
When I turn the player on/off a low but audible blob is heard from the player. This indicates that something happens on the player.I have no idea where to find this on/off signal but it must be there.
Since this signal might even be somewhere in Squeezelite I find it best for this to be part of the distribution.
Whether this should be enabled and to what GPIO-port could be a parameter in the settings on the piCorePlayer.
Best regards
Claus
It is not polling I2C, it polls the LMS server via network, you can argue if it is the best method, but it is an easy method.
When you turn off the player squeezelite closes the audio stream and closes the hardware. The sound you hear is probably your hardware sound port becoming inactive, or active when you turn it on. It will be related to the specific sound hardware That you use.
It's up to Steen if he wants to add the gpio function to the distribution. I was just giving you an alternative......
-
What RASPI board do I need? Vers B, B+, B2, A ??
Any.
What hardware add on board (sound card) do I need? What is the name of the brand and where can I buy it
There are some many it best to do a google. You can start by just using Analog or HDMI, no add-on.
Which OS needs to be copied to the sd card? MicroCore plus something else?
None. piCorePlayer is a complete image.
What is Sqeezlite?
Squeezebox emulator.
What do I need from Logitech?
LMS
More information here:
http://forums.slimdevices.com/showthread.php?97803-piCoPlayer-Squeezelite-on-Microcore-linux-An-embedded-OS-in-RAM-with-Squeezelite&highlight=picoreplayer
regards
Greg
-
A polling script that looks for activity on the I2C bus. This cannot be the best solution.
When I turn the player on/off a low but audible blob is heard from the player. This indicates that something happens on the player.I have no idea where to find this on/off signal but it must be there.
Since this signal might even be somewhere in Squeezelite I find it best for this to be part of the distribution.
Whether this should be enabled and to what GPIO-port could be a parameter in the settings on the piCorePlayer.
Best regards
Claus
It is not polling I2C, it polls the LMS server via network, you can argue if it is the best method, but it is an easy method.
When you turn off the player squeezelite closes the audio stream and closes the hardware. The sound you hear is probably your hardware sound port becoming inactive, or active when you turn it on. It will be related to the specific sound hardware That you use.
It's up to Steen if he wants to add the gpio function to the distribution. I was just giving you an alternative......
@cnpdk,
It is unlikely that this feature will make it into the version of squeezelite that we use with piCorePlayer. Paul_123's kind offer sounds like a good solution if you don't like a script that polls LMS.
@Paul_123
Thanks for helping out.
regards
Greg
-
Hi Greg: Thank you for your detailed response to my questions. I now have a clou but still do not understand the concept
completely. Is the following correct?
1. PiCore player is just the player which outputs sound to a speaker/audio system
2. The sound files to be played are sitting on a seperate server box running LMS
3. LMS can be downloaded from http://downloads.slimdevices.com/nightly. At this URL there is just a downlaoder named "logitechmediaserver_7.9.0~1452060863_all.deb"
and not the actual .deb file. I have (Debian 8 running on another box) I was not able to install LMS.
Is there another server to replace LMS?
F.i. VLC or similar?
4. Is there a streaming server availabe for piCore (piCorePlayer OS) ?
BTW: There is a good article in Linux Voice Magazine #013 on page 76 about LMS althoug it did not help me to install the server.
-
I don't want to hijack this from Greg, but I want to chime in too. :)
1. PiCore player is just the player which outputs sound to a speaker/audio system
Yes.
2. The sound files to be played are sitting on a seperate server box running LMS
Yes.
And the LMS server is also able to stream internet radio stations. Something I use it for the most.
The biggest advantage of LMS compared to other music (or multi-media) servers is that is able to synchronize the audio on two or more players.
That makes it the only low-budget alternative to a Sonos system, as far as I know.
3. LMS can be downloaded from http://downloads.slimdevices.com/nightly. At this URL there is just a downlaoder named "logitechmediaserver_7.9.0~1452060863_all.deb"
and not the actual .deb file. I have (Debian 8 running on another box) I was not able to install LMS.
Have look at my tutorial, it describes how to install squeezelite and an LMS server on a Raspberry Pi:
http://www.gerrelt.nl/RaspberryPi/wordpress/tutorial-stand-alone-squeezebox-server-and-player-for-bbq/
BUT PLEASE NOTE: The tutorial is in need of a revision. I've changed my squeezelite installation tutorial to use Raspbian Jessie, but this tutorial still needs Raspbian Wheezy.
So, if you only plan to use the LMS part of the tutorial, you're fine. As long as you use Raspbian Wheezy.
A piCorePlayer should be able to connect to a LMS server running on Raspbian Wheezy without any problems.
Is there another server to replace LMS?
F.i. VLC or similar?
Not that I know off.
4. Is there a streaming server availabe for piCore (piCorePlayer OS) ?
As piCorePlayer is a Squeezelite based player, it can only connect to a LMS server.
But please correct me if I am wrong piCorePlayer-people! :)
Greetings,
Gerrelt.
-
thank you so much. --- I am getting closer now.
I still have to find out how to install the LMS on my Debian 8 box or to install the ARM version on RASPI1 or RASPI2
Is there a package for Raspian available which I can just install via sudo apt-get install ?
The article in Linux Voice Magazine (UK) mentioned that the .deb file works on Ubuntus. I think it also should work on Debian 8
Maybe it is easier to install LMS on a seperate RASPI?
Any ideas?
l
-
hi beerstein,
http://wiki.slimdevices.com/index.php/Debian_Package
Use Raspbian Wheezy. There is a perl version mismatch with Jessie.
https://www.raspberrypi.org/downloads/raspbian/
I have installed 7.8.1 and 7.9 on RPiB and RPi2B with older scripts. I assume these newer scripts work. :o
regards
Greg
-
Thanks bmarkus, Paul_123, Gerrelt and others for chiming in.
It's great to have people with your skills and knowledge helping us out.
regards
Greg
-
December 12 2015
Please try the new release (piCorePlayer 1.22).
Ralphy has been a great support and help during the development - so thank you very much.
https://sites.google.com/site/picoreplayer/home/news
Changes:
- Updated kernel 4.1.12.
- Updated piCore (even faster booting).
- Touchscreen support improved (the official raspberry 7" touchscreen).
- Calibration file included.
- Jivelite can be installed from webpage.
- VU-Meters can be changed from webpage.
- New high quality default VU-Meter made by forum member Kolossos - thank you very much.
- Backlight on/off (Jivelite settings/screen/screensavers/when stopped/Display off ) then the backlight will be off when not playing, and on when you touch the screen.
- Ralphy is providing two versions of squeezelite. The basic version which is shipped with pCP allow playback of pcm, (wav/aiff), flac, mp3, ogg and aac. It is only 1 Mb in size. The ffmpeg version is bigger (12 MB) and allows in addition playback of ALAC and WMA via build in ffmpeg. In the Main page you can choose which version you will use.
- After customizing Jivelite you need to save your changes to the next reboot. This is done on the webpage ("advanced tab" in the bottom and choose "backup").
Download:
https://sites.google.com/site/picoreplayer/home/download
This software has been around for a couple of years now, but has a fairly low profile at diyAudio.
regards
Steen & Greg
Hi Steen and Greg
Thanks for providing this great player.
I have three installed here at home and they are always on so that they only need to be controlled from phone/tablet/LMS-webinterface. Unfortunately this level of comfort demands my power-amps to be always-on.
So one suggestion for a future change that would make it perfect for my use:
Could you make it part of the release to toggle one of the GPIO's according to the on/off status of the player as controlled from the LMS.
This I would use to control power for the amps driving my speakers.
Best regards
Claus
I had achived this previously using HDMI CEC - last post at http://forums.slimdevices.com/archive/index.php/t-76220.html
I have requested HDMI-CEC on TinyCore. http://forum.tinycorelinux.net/index.php?topic=18694.0
My old multiroom player was Debian + Squeeze Lite - (I had lag issues) but could control the power state on my soundbar. I moved to piCorePlayer because of its lightweight footprint and the sound output "Worked every time". Unfortunately TinyCore does not support the RPi CEC yet - fingers crossed for the future. Im mentioning it because you could have HDMI on the amp, much easier than a GPIO.
-
I've tested this piCorePlayer distro and it's fine for simplicity and general use. But I've hit several limitations. One was that wifi was not able to connect to hidden network (wifi.tcz is not designed to do so), than some other points. The CEC, or some another ON/OFF command was one of them. I've used my raspidac3 audio card (the same for Hifiberry) which has the activity LED and it may be simply used for the switching of the power amp. The advantage of this is that it reduced consumption in Stand-By, because the power amp had nearly 25W iddle consumption and now is switched off.
Then I've build my own player from scratch. It has only basic TC.7 core and simple wifi script for connection to the hidden network.
No SSH, nor web interface.
-
I've tested this piCorePlayer distro and it's fine for simplicity and general use. But I've hit several limitations. One was that wifi was not able to connect to hidden network (wifi.tcz is not designed to do so), than some other points. The CEC, or some another ON/OFF command was one of them. I've used my raspidac3 audio card (the same for Hifiberry) which has the activity LED and it may be simply used for the switching of the power amp. The advantage of this is that it reduced consumption in Stand-By, because the power amp had nearly 25W iddle consumption and now is switched off.
Then I've build my own player from scratch. It has only basic TC.7 core and simple wifi script for connection to the hidden network.
No SSH, nor web interface.
Hi jgrulich,
Why don't you release your version as a service to those wanting access to hidden SSIDs, CEC and amp on/off relays?
regards
Greg
-
On off relays via gpio is a different mechanism than cec. Just curious how you are doing cec on/off
-
@Paul_123,
yes, my way is different to CEC on/off command, but it works as needed. It is done inside the audio kernel module accordingly to enable / disable the audio sound card. This may be done even via some GPIO pin, but than it need some additional kernel module to do so.
@Greg Erskine,
I'll share it when finished. In the meantime you may use this link: http://www.gerrelt.nl/RaspberryPi/wordpress/
There is very nice tutorial how to do everything around the Logitech Media Server and Squeezelite Player on Rasbian and TinyCore.
-
14 January 2016
Hi all.
We are ready to release a major update to piCorePlayer - so we decided to call it version 2.00.
The major changes are:
- Only one version of piCorePlayer, but it can now run on all known Raspberry Pi boards. So you can use the same piCorePlayer image for all your players.
- Shairport-sync is supported and can be enabled from the "tweaks" page. It will automatically show on your iDevice (iPad or iPhone) with the name you have given your piCorePlayer. This means that you now can stream from your iDevices to piCorePlayer. It will automatically switch from squeezelite to shairport and vice versa. Just stop/pause either squeezelite or Shairport.
- piCorePlayer menu applet in Jivelite. This means that you will have a specific piCorePlayer menu in Jivelite. From here you can reboot and save eventual changes from within Jivelite. This menu is installed from your running LMS server. At the bottom of the Plugin page in LMS you will need to add piCorePlayer repo: http://picoreplayer.sourceforge.net/repo.xml Save.
- Then you go to Jivelite on the piCorePlayer. Settings - Advanced - Applet installer - piCorePlayer menu - Install.
- Next use the arrow in the top left corner to get to the main menu. Choose "quit" in the bottom of the screen (this will restart Jivelite - so the piCorePlayer menu is visible).
- Go to Settings - choose piCorePlayer and select "Save settings to SD-card"
- Kernel updated to 4.1.13 and piCore to version 7.0.
IMPORTANT: Because this version is so different from the others it is not possible to use the "In situ" upgrade/downgrade system to go down from version 2.00 to a previous version. If you for some reason want to use an older version you will have to download the previous version and burn it to your SD-card.
Please try it out. For this version Ralphy has been a tremendous help and he build the shairport-sync with all its dependencies. Kolossos made the piCorePlayer menu script.
Download
https://sites.google.com/site/picoreplayer/home/download
Regards
Greg, Ralphy and Steen
-
On off relays via gpio is a different mechanism than cec. Just curious how you are doing cec on/off
I had quite a bit of success with CEC - but the hardware im controlling is different. All depends on what CEC commands your devices accept.
Here is how I did it, basically when you press the power button on a player, it sends a CEC command to the connected device and powers it on.
I adapted a plugin wernerL started... (happy to post full code)
Plug-in in Squeeze Center:
Reads the button press on the player, and ssh'ed onto the player, then ran a bash script
Then a script on the player is something like this
#!/bin/bash
powerStatus=$(echo "pow 5" | cec-client -s -d 1 |grep "power status" |cut -d ' ' -f 3)
if [ "$powerStatus" = "standby" ]; then
echo "Powering On Amp....."
echo "on 5" | cec-client -s -d 1
fi
powerStatus=$(echo "pow 5" | cec-client -s -d 1 |grep "power status" |cut -d ' ' -f 3)
if [ "$powerStatus" = "on" ]; then
echo "Powering Off Amp....."
echo "standby 5" | cec-client -s -d 1
fi
So cec-client is the tool I used to use to check the power state and send the commands, which is part of LibCEC -http://libcec.pulse-eight.com/
I have gained permission from Pulse Eight to use the Lib and Steen has said we can try to get this working with piCorePlayer - but we need the support from Tiny Core first to enable the RPi's HDMI CEC capability.
-
but we need the support from Tiny Core first to enable the RPi's HDMI CEC capability.
What do you mean? cdc-acm kernel module is part of the base. All others are just userspace programs.
-
So does that mean that cec-client would work?
Im sure we would need lib-cec compiling into the OS ? more than happy to be proved wrong :)
-
As per my knowledge these files related to split up of the RAM to system/video. Better to keep them intact and change only config.txt if necessary.
Regarding image, create a small second ext4 partion which is big enough to keep your extensions and have same free space for additional extension later and for backap file, mydata.gz Then save it with dd specifying sectors with count=nnn option part of the first two partions.
-
How to redirect the jivelite to the attached tft on /dev/fb1?
I've tried to redirect it via fbset, but no lucky.
-
Strange, it's not working on the tft even when I've installed TC and run it from the x-window.
-
Bit more progress with HDMI CEC
I used a package Steen compile for me libCEC.tcz
I was able to load this into the usr/local/lib folder but then got an error libbcm_host.so: cannot open shared object file: No such file or directory
I found this was part of rpi-videocore.tcz - so tried loading that - but now im getting an error about
liblockdev.so.1: cannot open shared object file: No such file or directory
Cannot load libcec.so
http://www.robertbradley.co.uk/libCEC.zip (http://www.robertbradley.co.uk/libCEC.zip)
I cant find liblockdev.so.1 for tiny core - so have hit a bit of a brick wall, can anyone assist, im a total Tiny Core Linux noob so all this tcz installing is a bit new to me(but im learning)
-
The TinyCore is really minimal and highly optimized distro.
I'm using regular Rasbian Light on another SD card to get the libs and other what is not already in the TinyCore repository.
When working on Rasbian, than simply copy/paste to the TC and when make the .tcz from that.
-
18 June 2016 - piCorePlayer 2.06
Please try the new version piCorePlayer 2.06.
http://sourceforge.net/projects/picoreplayer/files/insitu/piCorePlayer2.06/piCorePlayer2.06.img/download (http://sourceforge.net/projects/picoreplayer/files/insitu/piCorePlayer2.06/piCorePlayer2.06.img/download)
This is a bug-fix version. A major part of the underlying code has been rewritten, but the appearance have not changed much.
Changes:
- piCore updated - where the libstdc++ exception bug is fixed.
- Improved ALSA settings on the Squeezelite page.
- Fixed the issue when trying to move LMS cache to attached Fat based USB disk.
- Improved the update process further.
- Numerous small bug-fixes.
NB: Please notice that you will need to install this version from 2.05. In addition, it is not possible to downgrade to a previous version anymore.
This will probably be the latest release based on kernel 4.1.
We have now started working on a major pCP update based on kernel 4.4 that contains a lot of interesting and important fixes for I2S-audio DACs.
-
I wanted to commend this group for your cooperation in developing this fabulous player -- just got it setup on another RPI3, and no issues...so much with so little !
-
-Hi guys,
I'm having a very hard time setting up a Rasberry Pi 2 with the latest version of PcP 2.06. I've also tried an older version (1.19l) because that's what's currently running on another Rasberry Pi 2, and it works great.
I'm running LMS on a MacMini with Snow Leopard. As I said, my one PcP player works great. I use it all the time.
I burned the PcP image to an 16GB SD card and have the Rasberry Pi connected to an ethernet hub plugged into the Airport Extreme. But it doesn't show up in LMS or on the network that I can see. I don't know if there are different settings in the Airport that I can try. I'm racking my brain. What else can I try?
By the way, I did plug the Rasberry Pi into the TV to make sure that it is booting correctly, and it seems to be. I also reboot the MacMini after the Rasberry Pi boots. Maybe I should reboot the router too?
My apologies if this is the wrong place to post this question.
-
Did you change the name of your other player. The images will default to piCorePlayer. But you wouldn't want both to be the same name.
If your still not seeing it on the network, then you will need to watch the boot process.....at the end of the process, it will report it's ip address.
-
Thanks Paul, the other player is named "Picore Digi" because it's equipped with a HiFiBerry Digi DAC. So that shouldn't be a problem.
I'll do as you suggest. We have our Airport Extreme in a rather inconvenient place, but I'll give it a try. Thanks.
-
Well, weird problem. The boot screen goes by so fast I can't read it. And the Page Up on my Mac keyboard doesn't seem to work. What ends up on the screen isthe Tiny Core logo plus "Core is distributed with ABSOLUTELY NO WARRANTY!"
But I videotaped (slow motion) as the screen was flying by and did a screen grab. Is there supposed to be more than this?
(http://wordcentrist.net/picore.png)
(http://wordcentrist.net/picore2.png)
-
hi ghulse,
It doesn't appear to be doing any of the piCorePlayer initialisation, just the piCore stuff.
There should be a log file created, /var/log/pcp_boot.log, that shows the pCP part of the boot process.
I think the easiest thing to do is to create a new pCP SD card image.
regards
Greg
-
Hi Greg,
I flashed the same .img to the SD card and rebooted the RPi2. As you can see, this time the PiCorePlayer stuff loaded. It looks for network for 22 seconds and then completes the boot. I'm still not seeing anything on my network and LMS web interface still doesn't give me a new player to select. My guess is that something in my network setup is preventing the connection.
But also, the "newconfig.cfg not found" in the boot log seems a bit suspicious.
(http://www.wordcentrist.net/picore22.png)
(http://www.wordcentrist.net/picore3.png)
-
Addendum. I got it working. I took the ethernet hub out of the equation, connecting thecable modem to the Airport Extreme. I upgraded the Airport at one point and didn't realize that it provides a few extra ethernet ports. No need for the ethernet hub at all.
Paul_123 was right. The IP address comes through in the boot log. Thanks everyone for your help.
-
Hi Greg,
I flashed the same .img to the SD card and rebooted the RPi2. As you can see, this time the PiCorePlayer stuff loaded. It looks for network for 22 seconds and then completes the boot. I'm still not seeing anything on my network and LMS web interface still doesn't give me a new player to select. My guess is that something in my network setup is preventing the connection.
But also, the "newconfig.cfg not found" in the boot log seems a bit suspicious.
hi ghulse,
22 is the maximum time pCP waits for your network connection. We have just added an error message to make it clearer that the network was not found. The lack on IP address message also indicates no network.
The newconfig.cg not found is normal. There is a mechanism to use a manually added config.cfg (called newconfig,cfg) on your SD card. The process allows you to prepare a config.cfg using a text editor on another computer.
Good you got it working!
regards
Grge