raspbian kernel alpha


17 posts
by plugwash » Tue Jun 26, 2012 11:15 pm
I have just uploaded a kernel package to raspbian based on incorporating bootc's patches with the debian kernel source.

I do not currently reccomend this kernel for general use because i'm having freezeup problems with it ( see: viewtopic.php?f=71&t=9468 ). Nevertheless I would appreciate people taking a look at it and telling me if anything they want is missing.

To install it (once it hits the public repo) use

apt-get install linux-image-3.2.0-3-rpi

There is nothing in place to automatically make this kernel bootable (a tool to do that will come later). You will have to manually copy the newly installed kernel from /boot/vmlinuz-3.2.0-3-rpi to /boot/kernel.img to use it. I recommend making a backup of your current kernel.img first so you can revert to it.
Forum Moderator
Forum Moderator
Posts: 2341
Joined: Wed Dec 28, 2011 11:45 pm
by jui-feng » Wed Jun 27, 2012 8:48 am
Works fine so far. Thanks!

I'm not really sure about this: I have a feeling that "-buffers/cache" memory usage with my setup (few daemons) as measured by the "free" command line tool has increased from ~25MB with 3.1.9+ to ~39MB with 3.2.0-3-rpi. Maybe this is to be expected though, because the kernel now has more features built-in?

When I have the time I will try booting the older kernel again, re-check if I remember the 25MB correctly and compare "ps" output.
Posts: 57
Joined: Sun Mar 04, 2012 11:02 am
by chrisw2 » Wed Jun 27, 2012 12:14 pm
Works fine so far and the support for iptables, SCSI tape & NFS kernel server are working.

My tip for booting the new kernel would be instead of copying from /boot/vmlinuz-3.2.0-3-rpi to /boot/kernel.img to add a line to your /boot/config.txt file like so:

Code: Select all
#kernel=kernel.img-3.1.9-clw
kernel=vmlinuz-3.2.0-3-rpi


On my setup I don't have a /boot/kernel.img but simply point to the kernel to be booted via /boot/config.txt. I find this easier to figure out where I am up to and there is no need to copy the kernel image about all the time.

I'll be unable to do any more testing for about a week.
Posts: 106
Joined: Sat Apr 07, 2012 11:22 am
Location: Manchester, UK
by mkhllr » Thu Jun 28, 2012 3:22 am
No crashes so far, but I noticed that the SD slot performance regressed from the 3.1.9+ kernel.

3.1.9+
/dev/mmcblk0:
Timing cached reads: 388 MB in 2.01 seconds = 193.15 MB/sec
Timing buffered disk reads: 54 MB in 3.01 seconds = 17.93 MB/sec

3.2.0-3-rpi
/dev/mmcblk0:
Timing cached reads: 152 MB in 2.01 seconds = 75.77 MB/sec
Timing buffered disk reads: 10 MB in 5.43 seconds = 1.84 MB/sec
Posts: 2
Joined: Thu Jun 14, 2012 2:49 pm
by Steep » Thu Jun 28, 2012 1:42 pm
I've got it installed and it seems to be running nicely. Purely anecdotally since I've done no proper testing, everything seems to be running smoother and quicker than before. No lock ups yet.
Posts: 145
Joined: Fri May 18, 2012 8:03 pm
by jui-feng » Sat Jun 30, 2012 3:14 pm
Forget about my suspicion of higher memory usage. Not exactly sure what caused it to use 39MB, but after a fresh boot, the 3.2 kernel uses only a few MB more than 3.1.9+ (if at all..). [Can't edit my post unfortunately.]

Just like you, I experienced a few hangs/freezes. I use the rpi headless, so my SSH client would eventually stop visually responding to input, and after some time I'd pull the plug and reboot. It seems like "heavy" I/O can lead to a hang. It happened once during a "dpkg -i" call with relatively big packages (all of the chromium debs), and I believe it also occured when I used apt-get one time, and once after starting chromium via VNC. I couldn't find anything interesting in the logs.. :?

If there's any way in which we could help with debugging the problem, let us know. I got tired of pulling the plug every now and then (which corrupted my rootfs once, boot failure).. So for now I reverted to 3.1.9+ to enjoy some 24hours+ uptime. ;) Again, thanks for your hard work!
Posts: 57
Joined: Sun Mar 04, 2012 11:02 am
by Aydan » Wed Jul 04, 2012 5:18 pm
Hi plugwash,

I just installed your kernel because Bootc's didn't recognize my KVM switch properly and blocked the network as well and I wanted to play with the SPI and I2C busses.
Unfortunately your kernel is missing the I2C device.
SD-Performance is at over 20MB/s sequential read, so no problems there for me.

Regards
Aydan
Posts: 244
Joined: Fri Apr 13, 2012 11:48 am
Location: Germany, Lake Constance
by Aydan » Thu Jul 05, 2012 6:05 pm
Hi again,

forget the I2C thing, I didn't know I had to modprobe it.
Otherwise it's been running OK. I'm seeding the Pisces image with transmission and haven't had any hangs or anything.
Only my USB harddrive doesn't work at all with this kernel, see here

Regards
Aydan
Posts: 244
Joined: Fri Apr 13, 2012 11:48 am
Location: Germany, Lake Constance
by morob65 » Thu Jul 12, 2012 2:31 pm
Hello,

i have a little problem with this kernel. i use qemu and by start freeze this system.

the qemu call is
qemu-system-arm -M versatilepb -cpu arm1136 -m 256 -kernel vmlinuz-3.2.0-3-rpi -initrd initrd.img-3.2.0-3-rpi -hda raspbian.img -append "root=/dev/sda1"

a idea? thanks for information

Regards
Posts: 2
Joined: Thu Jul 12, 2012 2:25 pm
by plugwash » Thu Jul 12, 2012 5:17 pm
Thanks to various people (foundation members included) being sloppy when discussing such things a lot of people seem to think that qemu can emulate a Pi.

This is not true. It can emulate a system with the same CPU core and the same ammount of memory as a Pi but the similarites between qemu-system-arm and a Pi pretty much end there. In particular the hardware surrounding the CPU core is different enough that different kernels are required.
Forum Moderator
Forum Moderator
Posts: 2341
Joined: Wed Dec 28, 2011 11:45 pm
by mali100 » Sat Jul 14, 2012 6:18 pm
Hi,
I'm currently using your kernel and it works great for me. I have no problems with freezups even with heavy load over long time (although I'm using the RPi headless without X).

Maybe you could add the CONFIG_MODULE_FORCE_LOAD=y in a future build?

I have another question: Is apt-get source linux-image-3.2.0-3-rpi the correct way to obtain the source the kernel was built with?

Regards Peter
Posts: 3
Joined: Sat Jul 14, 2012 6:09 pm
by flightvision » Sun Jul 29, 2012 4:20 pm
Thank you plugwash!
Installed your kernel as described in the first post.

I use it together with an up-to-date Raspbian.
Is stable, tested GPIO, UART/serial and am just now trying to do my first steps in I2C (which is why I upraded to your kernel for the i2c_bcm2708 module...).

Thanks (to you and your team) for Raspbian and all your dedicated and professional work!
Posts: 21
Joined: Sat Apr 21, 2012 9:04 am
by anwe79 » Tue Jul 31, 2012 7:45 pm
Just to let you know (not sure if this is the right place for it), I'm getting errors when installing:

Code: Select all
Setting up linux-image-3.2.0-3-rpi (3.2.21-1+rpi1) ...
Running depmod.
Error setting debconf substitutions in linux-image-3.2.0-3-rpi/postinst/missing-firmware-3.2.0-3-rpi: Unsupported command "removing" (full line was "Removing 'diversion of /boot/vmlinuz-3.2.0-3-rpi to /usr/share/rpikernelhack/vmlinuz-3.2.0-3-rpi by rpikernelhack'") received from confmodule. at /var/lib/dpkg/info/linux-image-3.2.0-3-rpi.postinst line 606, <STDIN> line 3.
dpkg: error processing linux-image-3.2.0-3-rpi (--configure):
 subprocess installed post-installation script returned error exit status 255
Errors were encountered while processing:
 linux-image-3.2.0-3-rpi
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up linux-image-3.2.0-3-rpi (3.2.21-1+rpi1) ...
Running depmod.
Error setting debconf substitutions in linux-image-3.2.0-3-rpi/postinst/missing-firmware-3.2.0-3-rpi: Unsupported command "no" (full line was "No diversion 'diversion of /boot/vmlinuz-3.2.0-3-rpi by rpikernelhack', none removed.") received from confmodule. at /var/lib/dpkg/info/linux-image-3.2.0-3-rpi.postinst line 606, <STDIN> line 3.
dpkg: error processing linux-image-3.2.0-3-rpi (--configure):
 subprocess installed post-installation script returned error exit status 255
Errors were encountered while processing:
 linux-image-3.2.0-3-rpi


At first i thought this may have had to do with me using a swedish locale, and the postinst trying to interpret some unexpected command output (since the "full line" message was originally in swedish), but i retried using LC_LANG=C (as seen above) with the same symptoms.

I see something in there about missing firmware, but the rest of the message doesn't make sense to me, at least in that context...
I do have a manually installed firmware for my wifi-plug (carl9170), could that be part of the issue?
Is this a bug or just something weird with my system?
Posts: 26
Joined: Sat Oct 08, 2011 10:30 pm
by bslande » Tue Jul 31, 2012 11:49 pm
So I downloaded this kernel and then the source so I could add the easycap driver. It seems that the easycap directory was empty. I copied over from a different source and then compiled the module. It seemed to compile OK, but I am now getting just a green screen.

Thought I would post here to see if anyone had ideas: Here is a snippet from dmesg log:

1432.251055] bcm2708_fb_check_var info(cb8d0400) 1024x768 (1024x768), 1572864, 16
[ 1432.251079] bcm2708_fb_check_var var(c0fd5de0) 1024x768 (1024x1536), 16, 786432
[ 1432.251105] bcm2708_fb_set_par info(cb8d0400) 1024x768 (1024x1536), 1572864, 16
[ 1432.264941] BCM2708FB: start = cd800000,4d506000 width=1024, height=768, bpp=16, pitch=2048 size=3145728 success=0
[ 1440.266058] easycap::0easycap_complete: easycap driver shutting down on condition green
[ 1441.800855] easycap::0adjust_standard: selected standard: PAL_BGHIN
[ 1442.190022] easycap::0adjust_format: sought: 640x480,UYVY(0x59565955),1=field,0x00=std mask
[ 1442.190061] easycap::0adjust_format: sought: V4L2_FIELD_NONE
[ 1442.190092] easycap::0adjust_format: actioning: 640x480 PAL_BGHIN_AT_640x480_FMT_UYVY-n
[ 1442.219908] easycap::0adjust_brightness: adjusting brightness to 0x7F
[ 1442.249906] easycap::0adjust_contrast: adjusting contrast to 0x3F
[ 1442.279894] easycap::0adjust_saturation: adjusting saturation to 0x2F
[ 1442.309905] easycap::0adjust_hue: adjusting hue to 0x00
[ 1449.682596] easycap::0easycap_complete: easycap driver shutting down on condition green
[ 1451.391390] easycap::0adjust_standard: selected standard: PAL_BGHIN
[ 1451.780185] easycap::0adjust_format: sought: 640x480,UYVY(0x59565955),1=field,0x00=std mask
[ 1451.780214] easycap::0adjust_format: sought: V4L2_FIELD_NONE
[ 1451.780243] easycap::0adjust_format: actioning: 640x480 PAL_BGHIN_AT_640x480_FMT_UYVY-n
[ 1451.810038] easycap::0adjust_brightness: adjusting brightness to 0x7F
[ 1451.840056] easycap::0adjust_contrast: adjusting contrast to 0x3F
[ 1451.870038] easycap::0adjust_saturation: adjusting saturation to 0x2F
[ 1451.900055] easycap::0adjust_hue: adjusting hue to 0x00
[ 1451.907300] easycap::0adjust_mute: adjusting mute: 1=peasycap->audio_idle
[ 1451.912866] bcm2708_fb_check_var info(cb8d0400) 1024x768 (1024x1536), 3145728, 16
[ 1451.912890] bcm2708_fb_check_var var(c0fd5de0) 1024x768 (1024x768), 16, 1572864
[ 1451.913195] bcm2708_fb_set_par info(cb8d0400) 1024x768 (1024x768), 3145728, 16
[ 1451.930388] BCM2708FB: start = cdc00000,4d385000 width=1024, height=768, bpp=16, pitch=2048 size=1572864 success=0
Posts: 10
Joined: Tue Jul 31, 2012 11:44 pm
by chrisw2 » Thu Aug 02, 2012 6:52 pm
I have found that this kernel will not boot (doesn't get beyond multi-colour screen & sits with constant red pwr led & blinking green ok led) with the latest Foundation firmwares (20120714-1 or 20120801-2)
Same problem with the bootc kernel.

1) I'm guessing this is because the firmware no longer handles vmlinuz type kernels?

2) is there a workaround to this?

3) Does this scupper the idea of producing a fully debianised kernel package if this is a permanent firmware feature (assuming it is of course)?
Posts: 106
Joined: Sat Apr 07, 2012 11:22 am
Location: Manchester, UK
by chrisw2 » Thu Aug 02, 2012 7:29 pm
re above post: when I ask about a workaround I mean "a workaround that will allow the use of this kernel and latest firmwares" (obviously using a Foundation kernel allows the RPI to boot)
Posts: 106
Joined: Sat Apr 07, 2012 11:22 am
Location: Manchester, UK
by plugwash » Thu Aug 02, 2012 11:53 pm
Work on the kernel package will continue if/when someone can point me at usable* 3.2 based kernel sources for the Pi.

* by which I mean of similar stability to the foundation's 3.1 stuff.
Forum Moderator
Forum Moderator
Posts: 2341
Joined: Wed Dec 28, 2011 11:45 pm