Tiny Core Linux
Tiny Core Base => Raspberry Pi => Topic started by: bmarkus on March 29, 2013, 04:03:18 AM
-
The very first cut of piCore with kernel 3.6.11 is ready. Send me a PM if you want to try it.
-
Hi bmarcus
Thanks for allowing me to try the new kernel.
Here are my observations.
1. when using tce-setdrive, an error about being unable to mount:
Mount: mounting /dev/mmcblk0p2 on /mnt/mmcblk0p2 failed: Invalid argument
BUT next line shows:
Your TCE Drive, /mnt/mmcblk0p2/tce, is now enabled
2. When installing packages using TCE from Cli works fine. However there is an error during ALSA installation:
depmod: /.build: No such file or directory
depmod: /.source: No such file or directory
BUT the last line is:
alsa.tcz: OK
3. When I try to use the squeezelite player which is using ALSA. I can get a fine list of the available ALSA devices - so this is working fine:
Like:
Output devices:
null - Discard all samples (playback) or generate zero samples (capture)
default: - CARD=ALSA - bcm2835 ALSA, brcm2835 ALSA - Default Audio device
sysdefault: - CARD=ALSA - bcm2835 ALSA, brcm2835 ALSA - Default Audio device
AND this is just like it should be.
BUT if I then try to play something using the player - this error pops up, and no sound is coming:
test_open:152 playback open error: Operation not permitted
output_init:1350 unable to open output device
4. Wifi package installs fine, and WiFi is working fine - it detects and connects to the chosen WiFi. There are still a lot of dropped RX packets like this:
RX packets:22954 errors:0 dropped:23257 overruns:0 frame:0 - I think this is unchanged from previous picore kernel and similar to a rasbian kernel.
5. Dropbear installs fine, but when trying to connect from another computer this output comes from the Pi (on the screen which is connected to the Pi).
On the computer which tries to connect I'm asked for a login name - and then asked for a password - and then putty hangs, and there is no connection:
This is displayed on the screen which is connected to the Pi:
Unable to handle kernel paging request at virtuaæ adresss ffffffff
pgd = c8f3c000
[ffffffff] *pgd=0bffe821 *pte=00000000 *ppte=00000000
Internal error: Oops 817 [#1] PREEMPT ARM
Entering kdb (current=0xc0fe0e60), pid 1835) Oops: (null)
Pid: 1835, comm: dropbear
CPU:0 Not tainted (3.6.11piCore #1)
PC is at alloc_fair_sched_group+0xa4/0x10c
LR is at 0x0
and a lot more.......
Steen
-
Steen, thanks. Nice list.
-
On the computer which tries to connect I'm asked for a login name - and then asked for a password - and then putty hangs, and there is no connection:
There couldn't be a connection any longer due to the kernel having killed the dropbear process.
-
Here are my observations.
1. when using tce-setdrive, an error about being unable to mount:
Mount: mounting /dev/mmcblk0p2 on /mnt/mmcblk0p2 failed: Invalid argument
BUT next line shows:
Your TCE Drive, /mnt/mmcblk0p2/tce, is now enabled
Can't repoduce, it works as expected on my system.
-
2. When installing packages using TCE from Cli works fine. However there is an error during ALSA installation:
depmod: /.build: No such file or directory
depmod: /.source: No such file or directory
BUT the last line is:
alsa.tcz: OK
Found, will be corrected in next cut. Possibly it will fix 3)
-
New image uploaded issue 2) fixed.
Tested ALSA with speaker-test right after installation, works as expected, no errors displayed.
-
5. Dropbear installs fine, but when trying to connect from another computer this output comes from the Pi (on the screen which is connected to the Pi).
On the computer which tries to connect I'm asked for a login name - and then asked for a password - and then putty hangs, and there is no connection:
This is displayed on the screen which is connected to the Pi:
Unable to handle kernel paging request at virtuaæ adresss ffffffff
pgd = c8f3c000
[ffffffff] *pgd=0bffe821 *pte=00000000 *ppte=00000000
Internal error: Oops 817 [#1] PREEMPT ARM
Entering kdb (current=0xc0fe0e60), pid 1835) Oops: (null)
Pid: 1835, comm: dropbear
CPU:0 Not tainted (3.6.11piCore #1)
PC is at alloc_fair_sched_group+0xa4/0x10c
LR is at 0x0
and a lot more.......
Dropbear as a server and as ssh client works as expected, at least with the latest image, didn't test with the first.
-
Hi
Thanks
for version 2. The ALSA problem is fixed - and the sound is fine.
I still have the first problem though:
Using: tce-setdrive
then choose option 2 = mmcblk0p2 results in this error:
Mount: mounting /dev/mmcblk0p2 on /mnt/mmcblk0p2 failed: Invalid argument
This result in being unable to do a backup using:
sudo filetool.sh -b
resulting in this error:
Mount: mounting /dev/mmcblk0p2 on /mnt/mmcblk0p2 failed: Invalid argument
I have tried to burn the image on two different cards - and freshly formatted - no change. This error is present all the time.
I must confess that I did not understand your message in your private mail: "Known bug is, that /tce dir is not recognized during boot, always /tmp/tce used by default. You try to specify explicitely in command line."
Should I do something differently in this image compared to what I usually do?
Also I'm stuck at the cli. But that is fine with me I just don't know if you designed it so, or you wanted it to start the desktop?
Steen
-
Also I'm stuck at the cli. But that is fine with me I just don't know if you designed it so, or you wanted it to start the desktop?
It is Core which means CLI-only. If you want X, just intall TC and start:
tce-load -iw TC
startx
That's all :)
R: tce-setdrive issue: I can't reproduce, it works just fine here.
The only bug I see here is what you are asking about, recognition of tce dir. Normally during boot system recognize /tce directories and automatically sets tce dir to the first found, you do not need to execute tce-setdrive. It is not happening now.
-
Thanks but I prefer cli at the moment.
Can you make your installed packages persistent?
I'm struggling with this at the moment, because of the problems I mentioned.
-
Thanks but I prefer cli at the moment.
Can you make your installed packages persistent?
I'm struggling with this at the moment, because of the problems I mentioned.
Sure. Create /tce on a partition which is not the boot and set /etc/sysconfig/tcedir to the used /tce (it is a symlink)
No if you download extensions, it will be stored there.
It is not intended it is a bug.
-
Thanks
Update:
Now the dropbear is working fine
The Wifi is working fine
The ALSA is working fine.
Unfortunately I still have massive drop-outs in the sound when playing music using the WiFi. So the development in the Raspberry kernel did not solve this problem.
As you might remember I just tested the same player using WiFi on a rasbian image, and here the sound is fine.
So I think that somewhere in the wifi or wpa_supplicant pathway in picore there is something different compared to the "pure" rasbian image, which results in this break-down of the sound when using wifi.
-
Steen thanks for testing, now it looks better. At the moment no idea regarding WiFi/sound :(
With 3.6.11 hardware accelerated video is available. It requires a new Xorg stack but it will be done when base is OK.
Now it is possible to measure temperature and other parameters of the chip using vc (video core) components:
# vcgencmd measure_temp
temp=50.3'C
I will upload it during the weekend. Also kernel compiled with CPU frequency scaling enabled.
For reference: http://elinux.org/RPI_vcgencmd_usage
-
Extension loading issue solved, see new cut.
-
Hi bmarcus
Thanks for the new version (version 3).
I few observations.
1.
I still have this mounting problem - so I'm unable to do a backup (filetool.sh -b). I don't know what exactly is the cause of this problem, but I managed to solve it by deleting the mmcblk0p2 partition and then recreate the partition and I formatted it into ext2.
Now I can use tce-setdrive and the filetool.sh -b command is working.
So my conclusion is that there must be something special/wrong with the mmcblk0p2 partition that are included in your image?
2.
During boot, it is halting and waiting for me to press "enter" before it boots the last part.
That is probably the "pause" option in the cmdline.txt - so that I can remove.
Steen
EDIT:
I see that you still uses the older files:
start.elf
bootcode.bin
fixup.dat
etc
Also I have read somewhere that the newer versions of raspberry does not use the loader.bin anymore.
-
Right, in this alpha test image only first (boot) partition, others left over from my system which doesn't reflect to your partitioning. You mast take care repartioning/reformatting your card.
-
hi bmarcus.
I have noticed that you have updated the ALSA module to 3.6.11, however, there some problems:
1. If I choose to install the alsa.tcz it gives an error when trying to download the alsa-modules-3.6.11-piCore.
I think there is a difference in the name. It tries to download alsa-modules-3.6.11piCore.tcz which is returning an error HTTP/1.1 404 Not found.
Notice the difference:
alsa-modules-3.6.11-piCore.tcz
alsa-modules-3.6.11piCore.tcz (written in the alsa.tcz)
2.
If I then manually install alsa-modules-3.6.11-picore.tcz via the tce package manager it installs fine.
I can the play music, but it won't survive a reboot.
But after a reboot I get this error:
error while loading shared libraries: libasound.so.2: cannot open shared object file: No such file or direcory.
I didn't get these errors yesterday.
Regards
Steen
-
Hi sbp
1. If I choose to install the alsa.tcz it gives an error when trying to download the alsa-modules-3.6.11-piCore.
Sounds like a typo in the .dep file for alsa.tcz.
error while loading shared libraries: libasound.so.2: ...
libasound.tcz is not loaded.
-
libasound.tcz is not loaded.
Hi Rich
But why isn't libasound loaded, it is a part of alsa.tcz - and previously all I had to do was to install alsa.tcz - and then I could play music also after a reboot?
Steen
-
Hi sbp
The alsa.tcz.dep file lists:
alsa-modules-KERNEL.tcz
libasound.tcz
libasound-bin.tcz
alsa-utils.tcz
alsa-plugins.tczWhat does:
uname -rreturn? That's what the KERNEL gets replaced with when it tries to fetch the modules.
-
uname -r
returns
3.6.11piCore
Steen
-
Hence:
It tries to download alsa-modules-3.6.11piCore.tcz
-
Hi sbp
That's why the download failed, either your version number is missing a dash, or the following extension names
alsa-modules-3.6.11-piCore.tcz
ax25-3.6.11-piCore.tczin the repository contain an extra dash.
-
Well
that is up to bmarkus to decide which one needs to be changed as I got the image from him.
-
It is a transitional period. In final image kernel version is 3.6.11-piCore, in test versions 3.6.11piCore. Also, test versions have all modules preinstalled while final has just the usual minimum. Wait a bit for the final one.
-
Hi bmarkus
Thanks for the explanation, I just reported the issue as I thought that it was a bug.
Will you prefer that I stop reporting these kind of observations until the final version arrive?
The modules you mentioned, what are those? I haven't really figured out what the modules do.
-
Thanks for testing. Now it is released:
http://forum.tinycorelinux.net/index.php/topic,14330.msg87230.html#msg87230
-
The modules you mentioned, what are those? I haven't really figured out what the modules do.
Linux kernel is modular. Features can be built into the kernek, moved to modules or disabled. Modules are .ko files in /lib/modules and ususally not needed for basic operation but interface specific hardware, implement file systems, etc. Core comes with a minimals set of modules for most common tasks, like Erhernet interface, etc. and less frequently used are not part of base system, but can be installed from the repository. One example is the set of wireless modules. These are loaded by extensions automatically when needed.
-
Dear bmarkus
THANK YOU - fantastic work.
The wifi problems I have had all the time using picore and playing music on my piCorePlayer is now gone.
I can even connect to my Dlink router at 150 Mbit/s and use any kind of protection WEB,WPA or WAP2 and it plays with-out any problems.
So I'm very satisfied.
What was the problem?
I saw that you made a new wifi package for the 3.6.11, do you think that it was a development in the kernel, or was it your new package that solved the problem?
Thanks
Steen
-
What was the problem?
I saw that you made a new wifi package for the 3.6.11, do you think that it was a development in the kernel, or was it your new package that solved the problem?
Do not know exactly, maybe new Broadcom firmware. Anyhow, it works :)
-
Hi bmarcus
I think that there is a problem somewhere.
As reported I can now play music nicely via wifi using the analoq output on the raspberry - and the cpu usage is only about 2-4% for the player.
But if I then use a USB-DAC, the cpu usage increase to about 50% for the player and the music is breaking up.
With the old picore build on 3.2.27 the use of a USB-DAC did not increase the cpu usage, and it was kept low at about 3%
Can you see the same?
Steen
EDIT:
If the USB-DAC is used without the wifi USB dongle the CPU usage is low again about 2-3%.
So it seems like USB-DAC and USB WiFi is not a good combination?
-
Hi bmarcus
I think that there is a problem somewhere.
As reported I can now play music nicely via wifi using the analoq output on the raspberry - and the cpu usage is only about 2-4% for the player.
But if I then use a USB-DAC, the cpu usage increase to about 50% for the player and the music is breaking up.
With the old picore build on 3.2.27 the use of a USB-DAC did not increase the cpu usage, and it was kept low at about 3%
Can you see the same?
Steen
EDIT:
If the USB-DAC is used without the wifi USB dongle the CPU usage is low again about 2-3%.
So it seems like USB-DAC and USB WiFi is not a good combination?
I do not have an USB WiFi stick so can't paly with it.
-
Hi.
I'm having trouble with the new kernel. I have this repeating USB keyboard problem that I have been reading about at the raspberry forum.
I did not have this problem with the 3.2.27 kernel. Maybe this have some relation to the USB dac and USB wifi problem?
Fortunately there seems to be some development in this area, http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=39175 so hopefully it will be solved shortly.
Steen
-
Hi.
I'm having trouble with the new kernel. I have this repeating USB keyboard problem that I have been reading about at the raspberry forum.
I did not have this problem with the 3.2.27 kernel. Maybe this have some relation to the USB dac and USB wifi problem?
Fortunately there seems to be some development in this area, http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=39175 so hopefully it will be solved shortly.
Steen
Well. the latest stable Pi kernel is 3.2.27, 3.6.11 is still a development release. USB driver was a mess according to kernel guys not able to handle higher speeds for example with external HDD's, etc.
What is interesting that I see keyboard issues, for example pressing function keys a digit instead of function key action via SSH not only with directly connected keyboard which show a different bug, not USB and not Xorg.
-
Hi.
I'm having trouble with the new kernel. I have this repeating USB keyboard problem that I have been reading about at the raspberry forum.
I did not have this problem with the 3.2.27 kernel. Maybe this have some relation to the USB dac and USB wifi problem?
Fortunately there seems to be some development in this area, http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=39175 so hopefully it will be solved shortly.
Steen
Well. the latest stable Pi kernel is 3.2.27, 3.6.11 is still a development release. USB driver was a mess according to kernel guys not able to handle higher speeds for example with external HDD's, etc.
What is interesting that I see keyboard issues, for example pressing function keys a digit instead of function key action via SSH not only with directly connected keyboard which show a different bug, not USB and not Xorg.
I have also noticed this via ssh. Even if I copy a text block via ssh, it can be partly garbled.
Steen
-
I have also noticed this via ssh. Even if I copy a text block via ssh, it can be partly garbled.
Steen
i also get 'partly garbled.' text with terminal now and then
-
I have also noticed this via ssh. Even if I copy a text block via ssh, it can be partly garbled.
Steen
i also get 'partly garbled.' text with terminal now and then
True. I will make a release with 3.8.8 kernel soon which looks better.
-
i also get 'partly garbled.' text with terminal now and then
True. I will make a release with 3.8.8 kernel soon which looks better.
is any chance of finding a 'fix' for this in 3.6.11 ?
or put another way
any suggestion how to identify the cause of this problem ?
-
is any chance of finding a 'fix' for this in 3.6.11 ?
or put another way
any suggestion how to identify the cause of this problem ?
Shortly no. Current Raspbian with 3.6.11 is working normally. One way would be to compare Raspbian and piCore kernel config and modules. However 3.6.11 is still tagged as development version and there is 3.8.8 which look better, no reason to waste time for and old dev kernel which will die before born.
-
The latest kernel is now 3.8.11.
Doug
-
The latest kernel is now 3.8.11.
Doug
Current statement at http://elinux.org/RPi_Kernel_Compilation
rpi-3.8-y - This is a Alpha development branch based on the current vanilla kernel( GIT rebased) . It will eventually replace the 3.6 branch.
At the time of writing, the exact version is 3.8.8 ( 22-04-2013 ).
-
That statement is out of date. If you actually go here:
https://github.com/raspberrypi/linux/tree/rpi-3.8.y
and look at the comment for the Makefile, you will see that 3.8.y was updated to 3.8.11 6 days ago. I can confirm this because I downloaded and compiled and ran the kernel and ended up with 3.8.11.
Doug.