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.
About your boot problem (just one menu entry present if I'm correct). You could try the one below, it is the most minimalistic I can produce, which makes checking for typos etc easier.
Make a backup of your current /boot/grub/grub/cfg and replace it by this one:
Code:
### BEGIN /etc/grub.d/00_header ###
set default=0
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry "LFS 6.7 - 2.6.38.3" --class gnu-linux --class gnu --class os {
echo Loading Linux 2.6.38.3-lfs-6.7 ...
linux /boot/vmlinux-2.6.38.3-lfs-6.7 root=/dev/sda1 ro
}
menuentry "LFS 6.7 - 2.6.38.3 (recovery mode)" --class gnu-linux --class gnu --class os {
echo Loading Linux 2.6.38.3-lfs-6.7 ...
linux /boot/vmlinux-2.6.38.3-lfs-6.7 root=/dev/sda1 ro single
}
menuentry "LFS 6.7 - 2.6.35.4" --class gnu-linux --class gnu --class os {
echo Loading Linux 2.6.35.4-lfs-6.7 ...
linux /boot/vmlinux-2.6.35.4-lfs-6.7 root=/dev/sda1 ro
}
menuentry "LFS 6.7 - 2.6.35.4 (recovery mode)" --class gnu-linux --class gnu --class os {
echo Loading Linux 2.6.35.4-lfs-6.7 ...
linux /boot/vmlinux-2.6.35.4-lfs-6.7 root=/dev/sda1 ro single
}
menuentry "LFS 6.7 - original kernel 2.6.35.4" --class gnu-linux --class gnu --class os {
echo Loading Linux 2.6.35.4-lfs-6.7.org ...
linux /boot/vmlinux-2.6.35.4-lfs-6.7.org root=/dev/sda1 ro
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
### END /etc/grub.d/40_custom ###
I,m going to try swaping the hard drive into another laptop it has a nivada graphics card. Will it work if I redo the kernel again in new machine, Hopefully loading the drivers for that card????
If you do so, you do need to go through the kernel options again: Disable the Intel settings and enable the appropriate nvidia settings. You might also notice that some nvidia specific drivers are not where you might expect them.
Nvidia (also Ati) need extra (semi) proprietary software and a separate install method if you want to fully use them under Linux. Although the Nvidia software is getting easier to work with (Ati is still a disaster...), it isn't the most Linux friendly.
But: You would be able to test a basic nvidia setup and/or the vesa driver. If those work then you can probably exclude an error in building X.
Although you still don't have a working X, this looks a lot better! The graphics driver is successfully detected and all that is associated is set. I think we can safely assume that you did not make a mistake when building X.
Quote:
[ 173.200] (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 173.200] (WW) Disabling Mouse0
[ 173.200] (WW) Disabling Keyboard0
together with
[ 174.752] Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config.
I do believe I mentioned this one before and can be solved by adding the following to your ServerLayout section:
Code:
Option "AllowEmptyInput" "off"
(see post #11)
You might not be able to use ctrl-alt-bksp to exit X, if that is so add the following to your InputDevice section (Keyboard part):
Although I personally think setting the appropriate options is the better way of doing this, you can also try using the minimal xorg.conf I mentioned before (see post #75).
Thks Druuna for all your work, I now have a GREY SCREEN WITH A CURSOR, I did have to redo xkeyboard again as stiil an issue with that but the ctrl-alt-bksp works great.
Jst as a thought It looks like it was driver problem on the intel laptop. I would like to try again, Is it possible to get all intel drivers and see what happens???
I'm not sure what you mean by 'getting all the intel drivers'. Those drivers are part of the kernel. A native set of drivers is present and there might be a possibility to download specific drivers from Intel.
If you still want to trouble shoot this specific problem you need to start systematically trying different combinations; Not only different kernels, but also different kernel options and the use of the boot option (i915.modeset=1).
As you have noticed the problem also arises when you use the vesa driver in the xorg.conf file, which in general should work (this is the first time I come across a situation that it does not work).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
