Kernel 3.4 heardes for Raspbian LCD image

Hi, how can I get Kernel headers for Raspbian with LCD touchscreen (Kernel 3.4).

I need to compile a driver and I need the headers

Regards Martin

Hi Martin,

The Banana Pi M2 A31S image is also available from, but I guess even Wheezy comes with 4.4 Kernel

Did you also take a look at: ? Do you have a special reason, that it needs to be Kernel 3.4?

Hi, I just need an LCD image with kernel headers. The only working LCD image is with kernel 3.4. I also want to use LIRC as IR transmitter and need a driver. lirc_gpio.c (adapted from lirc_rpi) seems to be working on kernel 3.4. I’ve tried to make it work under bananian (where I do have kernel sources) but it does not compile, seems to be working under Kernel 3.4. I just need an image with LCD, lirc driver and spi enabled, but seems to be very difficult to get it from sinovoip.

Regards Martin


I don’t know if a v3.4 is available, but I was told that this is not the case. There are some SDK’s available for the A31s

After you read the above I would follow this, so you know much more about your SBC:

Good luck, there is a lot to do /learn

You mean kernel 3.3.0 instead if you’re talking about M2. Before I would use such a junk (the kernel) I would finally accept that you bought a paperweight and throw it away or use it with mainline kernel for something else. It’s the product here that receives even less than zero support as you might have noticed everytime you try to get help?

In case you’re still willing to waste your time: Somewhere here is a kernel repo for your board:

Hi Tido, as Tkaiser mention, I got used to not receive support from Sinovoip. I mean, I dont want to beccame an expert, I want to invest my time in develop IoT software/hardware rather to learn the arquetechture of the board. They sell as fully compatible with RPI, and I have one with many things working on and not being able to migrate. About learning, I had to learn C because wiringPi Python is not working under BPI. Then using C code, wiringPIISR (interrupt) is not working on BPI. I mean, same code working on RPI is not working under BPI-M2. It compiles but detect all the time the interruption (same peripherical).

But, since I nnever loose my hope, I expect get a board with:

  1. 7" LCD support
  2. wiringPI completely working on C and Python.
  3. driver lirc_rpi working. (someone make it work on A10 cubieboard with kernel 3.4. I was unable to comile under bananian with kernel 4.3

I havent tried yet SPI and I2C on BPI, but I’m not optimistic. I mean, those steps took me 5 minutes to get working under RPI, I want them to be working on BPI.

Regards Martin

Then why don’t you throw the M2 away and get a BPi instead? BPi is Banana Pi, Banana Pi M1, Banana Pi M1+, Banana Pi Pro, Lamobo R1. They’re all compatible and you will get all the stuff you’re talking about running on these Bananas easily with either legacy or mainline kernel.

The M2 is incompatble to BPi, the M3 is incompatible and now the M2+ is another totally incompatible variant. But instead of giving these boards the names they deserve, eg ‘Durian Pi M2’ or ‘Lemon Pi M3’, the vendor chose to name them also Banana Pi just to trick as many unfortunate users as possible into believing they would have anything in common with the real Banana Pi.

Your problem is not called BPi but M2 instead. And it should be possible to get both LCD and IR running with mainline kernel but since I donated my M2 to the linux-sunxi community approx. 9 months ago and most if not all M2 users simply gave up on this board (or use it as a headless server) I doubt you will find any help for the incompatible M2 anyway.

I know, another problem is that I live in Argentina, and its not so easy to get a BPI-M1+ (due to customs problems that are going to be solved soon I expect). Of course I regret the purchase of the BPI-M2, but until I can get a BPI-M1+ I’ll give a chance (another may be) to make things work under M2.

Since my application are not CPU extensive, A20 chip will have same perfoormance as A31 I guess. In that case, would you buy the sinovoip BPI-M1+ plus? I mean, I dont wont to have M2 problems, but I do want to have onboard wifi. Regards Martin

I wouldn’t call this a problem! :slight_smile:

But understood. The problem with the M1+ is again a lack of correct hardware description. The M1+ was planned as a clone of LeMaker’s Pro and SinoVoip improved a few things (everything that might get hot on the upper PCB side) and also changed a few things that were not documented properly. A few weeks ago I tried to collect these changes between Pro/M1+ and create appropriate fex files but am not sure whether that’s all:

Anyway: I tried to purchase a M1+ which was impossible since the EU distributor didn’t get what I wanted so I hadn’t the chance to try the stuff out myself. Why don’t you ask SinoVoip/Judy whether they’re kind enough to send you a M1+ as a compensation for all the hassles you had with the M2 (and always politely asking for help again and again without getting answers)?