Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't boot kernel built using build-kernel-qemu #7

Closed
hpeyerl opened this issue Feb 4, 2016 · 10 comments
Closed

Can't boot kernel built using build-kernel-qemu #7

hpeyerl opened this issue Feb 4, 2016 · 10 comments

Comments

@hpeyerl
Copy link

hpeyerl commented Feb 4, 2016

Using a raspbian-ua-netinst-v1.0.8.1.img, I can boot using both kernel-qemu-4.1.7-jessie and kernel-qemu-4.1.13-jessie which is awesome. Unfortunately, after install is finished, systemd has trouble with dev-sda1.device and dev-ttyAMA0.device; presumably due to 'CONFIG_FHANDLE is not set'. So I modified build-kernel-qemu to include 'CONFIG_FHANDLE=y' and rebuilt the kernel. Unfortunately, on boot I get:

Error: unrecognized/unsupported processor variant (0x410fb767).

I get the same error if I try to build without modifications.

Is this the script that was actually used to build kernel-qemu-4.1.7-jessie and qemu-4.1.13-jessie? If so, does anyone has a .config I can borrow to compare against?

@dhruvvyas90
Copy link
Owner

May I have the link of the image file that you're using ?

@hpeyerl
Copy link
Author

hpeyerl commented Feb 4, 2016

https://github.com/debian-pi/raspbian-ua-netinst/releases/tag/v1.0.8.1

It needs to be prepared using all the usual s/mmcblk0p1/sda1/ and ld.so.preload stuff... Also add/grow a second partition to about 500MB's. I can post the prep script I used after I get home.

That's an installer image. After you boot it, it will apt-get install a bunch of stuff and then try to reboot to multi-user... Reboot with root=/dev/sda2 and

@hpeyerl
Copy link
Author

hpeyerl commented Feb 4, 2016

@hpeyerl
Copy link
Author

hpeyerl commented Feb 5, 2016

Here is the problematic output when booting one of your pre-built kernels..

[ *** ](1 of 2) A start job is running for dev-sda1.devi...41s / 1min 30s)
[ *** ](2 of 2) A start job is running for dev-ttyAMA0.devi...43s / 1min 30s)

@dhruvvyas90
Copy link
Owner

@hpeyerl: Were you able to find a fix for your particular rootfs ?

@hpeyerl
Copy link
Author

hpeyerl commented Mar 1, 2016

No. I would have to downgrade systemd to something from 2012 and I wasn't able to find a binary package in the repo for it.

rimmington added a commit to rimmington/qemu-rpi-kernel that referenced this issue Apr 19, 2016
@rimmington
Copy link
Contributor

@hpeyerl In case you're still working on this:

@hpeyerl
Copy link
Author

hpeyerl commented Apr 20, 2016

Thanks. That works for me. I had already tried adding CONFIG_FHANDLE=y but I wasn't doing it with 4.1.18 plus it seems you have a few extra CONFIG_*'s in there ... shrug.

I had to modify the build script due to a problem with unzip on Ubuntu 14.04 with github .zip files .. I switched to .tar.gz instead of .zip instead of arguing with unzip...

hpeyerl@9645bf4

(reference: raspberrypi/linux#34 )

@dhruvvyas90
Copy link
Owner

@hpeyerl: Does solution by rimmington solve your problem ? May I close this issue ?

@hpeyerl
Copy link
Author

hpeyerl commented May 17, 2016

Yes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants