Kernel 3.6.11

[bmarkus]

The very first cut of piCore with kernel 3.6.11 is ready. Send me a PM if you want to try it.

[sbp]

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:

Code: [Select]

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

[bmarkus]

Steen, thanks. Nice list.

[tinypoodle]

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.

[bmarkus]

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.

[bmarkus]

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)

[bmarkus]

New image uploaded issue 2) fixed.

Tested ALSA with speaker-test right after installation, works as expected, no errors displayed.

[bmarkus]

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:

Code: [Select]

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.

[sbp]

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

[bmarkus]

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:

Code: [Select]

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.

[sbp]

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.

[bmarkus]

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.

[sbp]

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.

 

[bmarkus]

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:

Code: [Select]

# 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

[bmarkus]

Extension loading issue solved, see new cut.