Raspberry Pi 3.2.23 kernel

Sorry folks, this one was late. So late that I completely skipped 3.2.22. Oh well, here it is at long last. Enjoy! I hope to publish a slightly revised version compiled with a new compiler and a few extra patches later this week, so keep your eyes peeled.

This one has a few additional changes on top of just the 3.2.23 update:

  • Enabled some more modules by popular request.
  • Included some further patches from the official kernel tree.
  • Compiled with Linaro GCC 2012.04 (thanks to crosstool-ng). I hope to use 2012.07 later this week for an updated kernel.
  • Fixed a minor sched_clock bug that printed a harmless warning at boot time.

Please see my kernel project page for download links and instructions.

11 thoughts on “Raspberry Pi 3.2.23 kernel

  1. After updating from 3.2.21 r2, temperature sensor tmp102 is no longer detected while running the “sensors” command.
    “sensors-detect” outputs:
    /sys/bus/pci/devices: No such file or directory at /usr/sbin/sensors-detect line 2547.

    • Ok, after applying this fix: https://bugzilla.redhat.com/attachment.cgi?id=573101&action=diff I get:

      […]
      Lastly, we can probe the I2C/SMBus adapters for connected hardware
      monitoring devices. This is the most risky part, and while it works
      reasonably well on most systems, it has been reported to cause trouble
      on some systems.
      Do you want to probe the I2C/SMBus adapters now? (YES/no): y
      Sorry, no supported PCI bus adapters found.

      Next adapter: bcm2708_i2c.0 (i2c-0)
      Do you want to scan it? (YES/no/selectively): y
      Client found at address 0x48
      Probing for `National Semiconductor LM75’… No
      Probing for `Dallas Semiconductor DS75’… No
      Probing for `National Semiconductor LM77’… No
      Probing for `Analog Devices ADT7411’… No
      Probing for `Dallas Semiconductor DS1621/DS1631’… No
      Probing for `Maxim MAX6650/MAX6651’… No
      Probing for `National Semiconductor LM73’… No
      Probing for `National Semiconductor LM92’… No
      Probing for `National Semiconductor LM76’… No
      Probing for `Maxim MAX6633/MAX6634/MAX6635’… No
      Client found at address 0x49
      Probing for `National Semiconductor LM75’… No
      Probing for `Dallas Semiconductor DS75’… No
      Probing for `National Semiconductor LM77’… No
      Probing for `Dallas Semiconductor DS1621/DS1631’… No
      Probing for `National Semiconductor LM73’… No
      Probing for `National Semiconductor LM92’… No
      Probing for `National Semiconductor LM76’… No
      Probing for `Maxim MAX6633/MAX6634/MAX6635’… No

      Next adapter: bcm2708_i2c.1 (i2c-1)
      Do you want to scan it? (YES/no/selectively): n

      Sorry, no sensors were detected.
      Either your system has no sensors, or they are not supported, or
      they are connected to an I2C or SMBus adapter that is not
      supported. If you find out what chips are on your board, check
      http://www.lm-sensors.org/wiki/Devices for driver status.

      • Did you find any solution to this?
        I also tried skipping the whole PCI related code in sensors-detect, but nothing…
        Not sure how the I2C detection works here…

  2. What do you do to get your kernel and modules so small?

    I rebuild the kernel with hardfp using the same configuration as yours but mine binaries are about 4-8 times bigger.

    • I don’t know what you’re doing to get them so big, but give up trying to build the kernel with hardfp. The kernel doesn’t use floating point, so it makes exactly zero difference, and the same kernel will boot armel and armhf userspace with no difference in performance.

  3. Yep just installed the kernel and got my AX25 software up and running !

    Thanks !!

  4. It seems that when I update to this kernel on my RPi, LXDE will hang after about 10 seconds whenever I try to start an application (e.g. Midori, IDLE 3) and I have to pull the plug. I re-imaged my SD card and started over but the same thing happened again. I’m using the latest firmware and wheezy. Any ideas what I’m doing wrong? Of course I might be blaming the wrong part of the system as I’ve also been installing I2C stuff.

    • I don’t know, sorry – I don’t use any graphical interfaces with my Pis. It may be useful to have a serial console attached to see if you get a kernel panic or something similar, and send me the output.

  5. Hello,
    I’m using your latest kernel with deb wheezy, because I use the i2c and the spi driver part.

    Today I wanted to install a wlan usb stick from edimax (8192c.ko) but without success. Is the problem that I use your i2c/spi kernel, or is something wrong with the installation routine of the wlan stick.

    Thanks,
    Stefan

Comments are closed.