| Summary: | uvesafb is required to be a module on qemux86/qemux86-64 target | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Kevin Tian <kevin.tian> |
| Component: | virtual machines | Assignee: | Anuj Mittal <anuj.mittal> |
| Status: | RESOLVED OBSOLETE | QA Contact: | |
| Severity: | normal | ||
| Priority: | Low | CC: | dvhart, edwin.zhai, jessica.zhang, josh, ke.yu, kevin.tian, poky.bs.watcher, poky.watcher, richard.purdie, sgw |
| Version: | unspecified | ||
| Target Milestone: | 4.99 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Kevin Tian
2010-10-08 23:42:35 UTC
Just to make this clear we need to address whatever the reason is uvesa has to be a module and allow it to be built in and still work. The reason it fails when built-in is that the uvesafb driver tries and fails to start /sbin/v86d via call_usermode_helper() before the rootfs containing it has been mounted, and the probe that called it fails. We need to arrange for this to happen after the rootfs has been mounted. According to the kernel documentation in Documentation/fb/uvesafb.txt: Note that the v86d userspace helper has to be available at all times in order for uvesafb to work properly. If you want to use uvesafb during early boot, you will have to include v86d into an initramfs image, and either compile it into the kernel or use it as an initrd. So apparently we'll need to have the qemu targets using initramfs for this to work compiled-in. Moving to 1.2. Reassiging to Anuj, as the meta-intel owner so effectively the best available for the qemux86 machines too. This is a very old bug that might be able to be closed once it's actually understood. uvesa is now not loaded at all for qemux86 or genericx86. |