LinuxQuestions.org - [SOLVED] Creating an X11R6 Compatibility Symlink

- Linux From Scratch (https://www.linuxquestions.org/questions/linux-from-scratch-13/)

- - Creating an X11R6 Compatibility Symlink (https://www.linuxquestions.org/questions/linux-from-scratch-13/creating-an-x11r6-compatibility-symlink-874031/)

Hi,

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 ###

Hope this helps.

This might help lsmod no output? "Module Size Used by check /proc/modules empty.

Xorg.0.log http://pastebin.com/RivjR8SQ

I will try basic conf.new

Do we need to run lilo? found a post http://www.linuxquestions.org/questi...odules-328657/ just a thought?

Hi,

Quote:

Originally Posted by spiky0011 (Post 4327168)

This might help lsmod no output? "Module Size Used by check /proc/modules empty.

Xorg.0.log http://pastebin.com/RivjR8SQ

I do believe no output for the lsmod command seems correct (the kernel settings are for a static kernel and not a modular one).

The Xorg log output doesn't show anything new that could be useful...

Quote:

Originally Posted by spiky0011

Do we need to run lilo? found a post http://www.linuxquestions.org/questi...odules-328657/ just a thought?

Nope. One uses either grub or lilo to boot. LFS 6.7 uses grub.

Hope this helps.

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????

Hi,

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.

Hope this helps.

ok thks for input will post later next option I,m gonna try if this dont work is redo Chapter 23 again but lets see 1st

Ok swapped hard drive still no X xorg.conf.new

Code:

Section "ServerLayout"

        Identifier    "X.org Configured"

        Screen      0  "Screen0" 0 0

        InputDevice    "Mouse0" "CorePointer"

        InputDevice    "Keyboard0" "CoreKeyboard"

EndSection



Section "Files"

        ModulePath  "/usr/lib/X11/modules"

        FontPath    "/usr/share/fonts/X11/misc/"

        FontPath    "/usr/share/fonts/X11/TTF/"

        FontPath    "/usr/share/fonts/X11/OTF/"

        FontPath    "/usr/share/fonts/X11/Type1/"

        FontPath    "/usr/share/fonts/X11/100dpi/"

        FontPath    "/usr/share/fonts/X11/75dpi/"

EndSection



Section "Module"

        Load  "dbe"

        Load  "record"

        Load  "dri2"

        Load  "dri"

        Load  "glx"

        Load  "extmod"

EndSection



Section "InputDevice"

        Identifier  "Keyboard0"

        Driver      "kbd"

EndSection



Section "InputDevice"

        Identifier  "Mouse0"

        Driver      "mouse"

        Option            "Protocol" "auto"

        Option            "Device" "/dev/input/mice"

        Option            "ZAxisMapping" "4 5 6 7"

EndSection



Section "Monitor"

        Identifier  "Monitor0"

        VendorName  "Monitor Vendor"

        ModelName    "Monitor Model"

EndSection



Section "Device"

        ### Available Driver options are:-

        ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",

        ### <string>: "String", <freq>: "<f> Hz/kHz/MHz",

        ### <percent>: "<f>%"

        ### [arg]: arg optional

        #Option    "SWcursor"                  # [<bool>]

        #Option    "HWcursor"                  # [<bool>]

        #Option    "NoAccel"                    # [<bool>]

        #Option    "ShadowFB"                  # [<bool>]

        #Option    "UseFBDev"                  # [<bool>]

        #Option    "Rotate"                    # [<str>]

        #Option    "VideoKey"                  # <i>

        #Option    "FlatPanel"                  # [<bool>]

        #Option    "FPDither"                  # [<bool>]

        #Option    "CrtcNumber"                # <i>

        #Option    "FPScale"                    # [<bool>]

        #Option    "FPTweak"                    # <i>

        #Option    "DualHead"                  # [<bool>]

        Identifier  "Card0"

        Driver      "nv"

        BusID      "PCI:1:0:0"

EndSection



Section "Screen"

        Identifier "Screen0"

        Device    "Card0"

        Monitor    "Monitor0"

        SubSection "Display"

                Viewport  0 0

                Depth    1

        EndSubSection

        SubSection "Display"

                Viewport  0 0

                Depth    4

        EndSubSection

        SubSection "Display"

                Viewport  0 0

                Depth    8

        EndSubSection

        SubSection "Display"

                Viewport  0 0

                Depth    15

        EndSubSection

        SubSection "Display"

                Viewport  0 0

                Depth    16

        EndSubSection

        SubSection "Display"

                Viewport  0 0

                Depth    24

        EndSubSection

EndSection

Xorg.0.log is here http://pastebin.com/JUjs5nW9

Hi,

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):

Code:

    Option      "CoreKeyboard"

    Option      "XkbOptions" "terminate:ctrl_alt_bksp"

Both entries would now look like this:

Code:

Section "ServerLayout"

        Identifier    "X.org Configured"

        Screen      0  "Screen0" 0 0

        InputDevice    "Mouse0" "CorePointer"

        InputDevice    "Keyboard0" "CoreKeyboard"

      Option      "AllowEmptyInput" "off"

EndSection



and



Section "InputDevice"

        Identifier  "Keyboard0"

        Driver      "kbd"

      Option      "CoreKeyboard"

      Option      "XkbOptions" "terminate:ctrl_alt_bksp"

EndSection

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).

Hope this helps.

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.

Hi,

I'm really glad to see you took this hurdle!

And: You're welcome :)

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???

Hi,

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).

Hope this helps.