Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It contains a systemd unit, but an lfs sysvinit compatible init script can be easily written. The script was written for 4.3.20 or something like that, but unless the guest additions iso layout changed, it should still work with 5.0 series.
It requires a kernel source (or a subset of it) for the currently running kernel in order to build and install the out-of-tree module.
Given all that, I prefer VMWare Player due to its OSS graphics stack. I like Qemu/virt-manager more, but it doesn't have a proper graphics stack yet and it doesn't emulate VMWare's SVGAII GPU properly (probably a seabios limitation).
Given that you are using vbox, you don't need any of the drivers from the book.
vesa should be temporarily used and the binary vbox module should be installed as soon as permitted.
That's it!
You hit the nail on the head!
I messed up by creating that file. By creating that file I was telling X to use ATI.
I removed that file, and now it does not try to use ati.
It's still not working yet, but I'm one step closer.
Thanks!
As for the why I have all the other drivers; I want this system that I am building to replace my main linux system, and it needs to be able to run on whatever computer I put it on. But I don't want it to be wrongly assuming the wrong video card like it was, and you figured out my problem there.
It contains a systemd unit, but an lfs sysvinit compatible init script can be easily written. The script was written for 4.3.20 or something like that, but unless the guest additions iso layout changed, it should still work with 5.0 series.
It requires a kernel source (or a subset of it) for the currently running kernel in order to build and install the out-of-tree module.
Given all that, I prefer VMWare Player due to its OSS graphics stack. I like Qemu/virt-manager more, but it doesn't have a proper graphics stack yet and it doesn't emulate VMWare's SVGAII GPU properly (probably a seabios limitation).
Thanks, I changed it back to vesa.
I'll consider installing the vboxvideo or the complete guest additions. Though it should still work with vesa, but having the vbox installed would be useful.
I was trying to modprobe vesa.
Then I tried others to see if I got the same error, and I did.
Then I was able to modprobe i915 without error, but it did not show up when doing a lsmod.
I installed vbox guest additions, or at least mostly. :-)
Being a bit proprietary, it took a lot of hacking to get it to install as an install user. But X still would not start.
Then I uninstalled all of the vbox stuff.
It should be possible to run X inside Virtualbox without any vbox installations, with just very basic graphics.
If I have to, I'll just move it to a real computer. Eventually I plan to do that anyway.
Unfortunately, most vbox stuff with not build as a build specific user and requires running as root to work correctly. You can blame Oracle for this. Unless your build user has all the necessary read/write permissions and root level resource access, the vbox additions might fail to work, and even then it's still unknown. I've built it with root always and it works.
Distribution: LFS 9.0 Custom, Merged Usr, Linux 4.19.x
Posts: 616
Rep:
Does the computer have a KMS driver?
Where you get into trouble, in my experience, is when you're trying to load competing systems. For instance: I have 2 kernel configs for VMware, one has NO DRI, or more specifically, anything not required by from the "gpu" tree of the kernel source. It does have video/simplefb vbe vesa, etc. The other config has the VMware DRI, vmfbwhatver and stuff from the GPU tree. For that one, the only thing selected from the video tree is the fbcon framework, which I believe is populated by the DRI fb driver when it's loaded.
Boot a LiveCD of some kind (with a desktop) on that computer and look at dmesg, should tell you what's driving the hardware.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
