Jelly Bean porting - not a demand but a "I've almost got it working, need some help"

[Quinny899]

I've been working on getting Intel's Jelly Bean builds working with GRUB, and therefore you not having to wipe your hard disk, and I've got it to start booting, using the initrd from 4.0 RC2, and the rest extracted from the build, including the kernel and the system.
Debug during boot shows a kernel panic as follows:
http://www.imgur.com/2yh1h.jpeg
And non debug just sticks at "Not an ASUS product"

There's an existing fix for this error, but it's on source level, is there any other way to fix it?
Thanks
Quinny

[Stefan Matthäus]

Isn't that "not an asus product" an android-x86.org build specific message?

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To view this discussion on the web visit https://groups.google.com/d/msg/android-x86/-/Zd0OMRt0qlgJ.
To post to this group, send email to andro...@googlegroups.com.
To unsubscribe from this group, send email to android-x86...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.

[Quinny899]

Yes, but that's because it's using the Android x86 initramfs, which contains that message

[shumifan schumacher]

What platform are you running on. The RC2 says that the eeepc version must not be used on other platforms, you should use the generic version. I guess that message says it is not an eeepc.

[Quinny899]

I was using the asus_laptop one, but now I'm going to try with the generic 4.0.4 one from tabletsx86

[Quinny899]

Does the same thing, debug shows the same kernel panic code

[Quinny899]

On the subject of the kernel, is it the one in droidboot.img of the android-ia or the boot.img of it do you think?

[shumifan schumacher]

Which platform are you using?

I used the binaries from the tegra2 on my Inspiron Duo and although it spewed out a message of unknown hardware, it works quite sweetly, with some hardware, like the clock, not working.
The thing is to find a platform with similar drivers to your platform, which is why "what platform'.

I have not looked at the build, it will be best answered by someone with a lot more knowledge than me. When I have some time I will get into that.

[Quinny899]

Is that jelly bean you're talking about? I'm using a Intel CPU (Atom N450) on a Acer D255 netbook

[shumifan schumacher]

No 4.0RC2

[Quinny899]

I'm talking about jelly bean, it's different

[shumifan schumacher]

I realise jellybean is different, but it will still require the correct drivers for the hardware you intend to use. So a good place to start to is make ICS work on your hardware, then you know which drivers are required.
You can then copy the drivers from the ICS installation to the jellybean project, which should make life a little easier. But I am no expert at this, so I will leave it to the experts to help you sort the problem
Good luck, it will be nice to get jellybean.

[Quinny899]

ICS does work, that's not the problem here

[Christopher Campbell]

Mr. Matthaus (Sorry about not getting the name Perfectly right), I hope you do get this done (I'm cheering for yeah). I heard Kitkat has a Godless Bug and Marshmellow is Strict with Internal Storage so for me they don't have good rep -though x86 versions might not- and I'm a 4.1.2 User who well never upgrade my Android OS.