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

Thks for reply, You do know this problem might not get resolved, Yes I did carry out both things you suggested. To no avail.
" I did try this "Workaround B: Switch to -vesa

Code:

Paste the following into /etc/X11/xorg.conf:



Section "Device"

        Identifier      "Configured Video Device"

        Driver          "vesa"

EndSection



Section "Monitor"

        Identifier      "Configured Monitor"

EndSection



Section "Screen"

        Identifier      "Default Screen"

        Monitor        "Configured Monitor"

        Device          "Configured Video Device"

EndSection"

I did realise that it was similar to 1 of your instrctions but thought I would give it a go.
Still all progress not remeding.

A difference I have seen is when running cd ~ && Xorg -config The font size reduces and if I want to copy, the cursor only comes down half way on the screen!!
I have booted a ubuntu harddrive it,s using
Kernel 2.6.31-22-generic ( Just for info)

Hi,

Quote:

You do know this problem might not get resolved

I have to admit that this is "an interesting" problem and might not be solved with what you have currently installed (especially the kernel).

One thing I really like about the linux community is the fact that problems are being reported and worked on and most, if not all, problems get solved in a very reasonable time frame. Sometimes problems get fixed, but can only be solved by using newer versions.

Seeing that a lot of people have had this problem in the (near) past, I'm hoping the problem you are having is already solved and fixed in one of the newer kernels.

You haven't answered my question about giving a newer stable kernel (2.6.38) a try. I'll start writing a little guide to help you do just that.

Do let me know if you've "had it" for now and want to lay this problem to rest (for a while). I'm still game :)

You've picked up the Gauntlet then lol. Yes Seems I,m like you, wont let it rest.
Is it not just a case of downloading new kernel unpacking then rebuild as in book???
Dont knock yourself out trying to fix plenty of time. Thks for support, glad I given you something to get your teeth into.

Hi,

Quote:

Originally Posted by spiky0011 (Post 4326365)

You've picked up the Gauntlet then lol. Yes Seems I,m like you, wont let it rest.

It would be a shame if this wouldn't be resolved. You're already this far with building a (B)LFS system, not being able to continue because of this "bug" seems not right.

Quote:

Is it not just a case of downloading new kernel unpacking then rebuild as in book???

You could go that way, but it has a major setback: You would need to recheck and re-set all the options in the kernel. A better approach is available (see my comment about this in the guide below).

- - - A small guide to switch from one kernel version to a newer one (LFS specific) - - -

You first need to clean up what's been done this far, which is the following (you might or might not have done so already):

- remove created xorg.conf file(s),
- remove i915.modeset=1,
- remove /etc/modrprobe.d/<i915-related-file>
- remove i915 related entry from /etc/modprobe.conf,
-

Time to install the newer kernel......

Download the newest stable kernel (which is 2.6.38.3 when I type this): linux-2.6.38.3 (kernel.org) or linux-2.6.38.3 (xs4all)

Copy new kernel, extract, prepare for setting the options:

Code:

cp /x/y/z/linux-2.6.38.3.tar.bz2 /usr/src

cd /usr/src

tar jxf linux-2.6.38.3.tar.bz2

cd linux-2.6.38.3

make mrproper

Nothing new thus far, except the version number and you now have 2 kernel directories in /usr/src.

Because a newer kernel has extra, other and/or different option, you cannot use a config file from another kernerl version by just copying it to the correct place. Being able to use your current configuration has a big advantage: All changes made would also be reflected in the new kernel configuration, which would save you the trouble of having to set them all over again.

You do need to tell the make process it is going to use a config file from an older version:

Code:

# import old/current config file:

cp /boot/config-2.6.35.4 .config

make silentoldconfig

To avoid having to answer all (most?) of the questions about new/changed options, make silentoldconfig is used, you could also use make oldconfig, but it will ask conformation about a lot of stuff. If you do get questions: Accept all defaults (just press enter).

Although you could skip this step, I always do it, just to make sure:

Code:

make menuconfig

You should at least check the intel settings to see if they are still the same. I do realize that your knowledge about all the other options are probably still somewhat limited, but if you did set/change anything important in the 2.6.35 kernel: Check if those are still what you want them to be.

Compile and place the new kernel:

Code:

safe/exit menuconfig

make

make modules_install

cp arch/x86/boot/bzImage /boot/vmlinux-2.6.38.3-lfs-6.7

cp System.map /boot/System.map-2.6.38.3

cp .config /boot/config-2.6.38.3

If all went as planned you now have 4 kernel versions, and their accompanying files, present in /boot:

vmlinux-2.6.35.4-lfs-6.7.new
vmlinux-2.6.35.4-lfs-6.7.org
vmlinux-2.6.35.4-lfs-6.7
vmlinux-2.6.38.3-lfs-6.7

Make changes to /boot/grub.cfg.

Replace all between ### BEGIN /etc/grub.d/10_linux ### and ### END /etc/grub.d/10_linux ### with:

Code:

### BEGIN /etc/grub.d/10_linux ###

menuentry "LFS 6.7 - 2.6.38.3" --class gnu-linux --class gnu --class os {

        insmod ext2

        set root='(/dev/hd0,1)'

        search --no-floppy --fs-uuid --set ad95dfa8-fdf9-47b5-ad1f-e0d35145c38c

        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 {

        insmod ext2

        set root='(/dev/hd0,1)'

        search --no-floppy --fs-uuid --set ad95dfa8-fdf9-47b5-ad1f-e0d35145c38c

        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 {

        insmod ext2

        set root='(/dev/hd0,1)'

        search --no-floppy --fs-uuid --set ad95dfa8-fdf9-47b5-ad1f-e0d35145c38c

        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 {

        insmod ext2

        set root='(/dev/hd0,1)'

        search --no-floppy --fs-uuid --set ad95dfa8-fdf9-47b5-ad1f-e0d35145c38c

        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 {

        insmod ext2

        set root='(/dev/hd0,1)'

        search --no-floppy --fs-uuid --set ad95dfa8-fdf9-47b5-ad1f-e0d35145c38c

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

The first 2 menu entries are the new 2.6.38.3 kernel, menu entries 3 and 4 are the previously used kernel and the last menu entry is the original first kernel you installed. The first menu entry should be started automatically.

In case you don't yet know: The recovery mode entries are there to boot into runlevel 1, which could be useful to fix the system if something goes wrong.

Now reboot into your new kernel and start testing X again.

Lets hope I didn't forget anything ;)

Hi,

Re-reading my previous post (# 64) I see that you still have "leftovers" that can be removed.

the vmlinux-2.6.35.4-lfs-6.7.new kernel and its accompanying files are still present and are not in the grub.cfg file. You can safely remove them:

Code:

cd /boot

rm *2.6.35.4.new

You now should have 3 sets of kernel files:

- vmlinux-2.6.35.4-lfs-6.7.org
- vmlinux-2.6.35.4-lfs-6.7
- vmlinux-2.6.38.3-lfs-6.7

All three have one ore two entries in the grub.cfg file.

Ok sorry been so long. I have installed new kernel ok done all you have said all went well, sort of. The machine reboots but grub only shows new kernel? /boot has all the old kernels in it, config-2,6,35.4 config-2,6,35.4.org and the system map and vmlinux??? They dont show up when booting not the end of the world I know that can be fixed. Not proceeded to Xorg yet. I would like to have a spare grub option

Hi,

Error checking time....

- I just double checked the grub part I posted (#64) and I don't see any mistakes. Make sure its all ok on your and as well. Post the grub.cfg file from beginning to ### END /etc/grub.d/10_linux ### if you are unsure.

- Can you post the output of

Code:

ls -l /boot/

ls -l /usr/src/linux-2.6.*/.config

I want to make sure all the files needed are there and they have the same names as used in the grub.cfg part I posted.

Boot contents

Code:

-rw-r--r-- 1 root root  73532 Apr 12 21:27 config-2.6.35.4

-rw-r--r-- 1 root root  73532 Apr 17 15:40 config-2.6.35.4.org

-rw-r--r-- 1 root root  76545 Apr 17 15:09 config-2.6.38.3

drwxr-xr-x 3 root root    4096 Apr 17 15:45 grub

-rw-r--r-- 1 root root 1885527 Apr 17 15:05 System.map

-rw-r--r-- 1 root root 1815936 Apr 12 21:26 System.map-2.6.35.4

-rw-r--r-- 1 root root 1779911 Apr 12 19:55 System.map-2.6.35.4.org

-rw-r--r-- 1 root root 1885527 Apr 17 15:08 System.map-2.6.38.3

-rw-r--r-- 1 root root 4198144 Apr 12 21:25 vmlinux-2.6.35.4-lfs-6.7

-rw-r--r-- 1 root root 4114976 Apr 12 19:55 vmlinux-2.6.35.4-lfs-6.7.old

-rw-r--r-- 1 root root 4321088 Apr 15 21:19 vmlinux-2.6.35.4-lfs-6.7.org

-rw-r--r-- 1 root root 4258000 Apr 17 15:07 vmlinux-2.6.38.3-lfs-6.7

-rw-r--r-- 1 root root 4258000 Apr 17 15:05 vmlinuz

and linux .config

Code:

-rw-r--r-- 1 root root 73532 Apr 12 20:41 /usr/src/linux-2.6.35.4/.config

-rw-r--r-- 1 root root 76545 Apr 17 14:18 /usr/src/linux-2.6.38.3/.config

Hi,

Output from both looks good.

You do have 3 "leftovers" present in /boot (vmlinux-2.6.35.4-lfs-6.7.old, System.map and vmlinuz), but they don't do any harm and you can remove them if you want to.

I was going to but didn't wanna tempt fate, grub.cfg has the appropriate entrys as well. "Now". I can try the Xorg command, I can get back in with live cd if the worst happens

Hi,

Can you confirm you booted into the new kernel? (uname -a).

Yea shows 38.3 I had checked that earlier, learning a lot here

Hi,

Guess we can fix the grub problem later, it seems you boot into the correct kernel.

Give X a try!

Ok still no X. I have tried changing intel>vesa in xorg.confg.new Do you think we are looking in the right place? I have in Xorg.0.log Fatel sever error. Could we have a problem with Part of things installed for Xorg or a driver problem, Just tossing a few things in the mix. Dont knock yourself out trying to fix there is no rush

Hi,

Quote:

Originally Posted by spiky0011 (Post 4327124)

Ok still no X. I have tried changing intel>vesa in xorg.confg.new

Mmmm..... that's kinda disappointing. You did check if the correct options are present in the kernel (the layout is different then before in this kernel version)?

I would like to have a look at the Xorg log (when started with the intel driver) and the output of lsmod.

Another thought: Have you tried starting X using a minimal config file (xorg.conf):

Code:

Section "Device"

    Identifier    "Configured Video Device"

    Driver        "intel"

EndSection



Section "Monitor"

    Identifier    "Configured Monitor"

EndSection



Section "Screen"

    Identifier    "Default Screen"

    Monitor        "Configured Monitor"

    Device        "Configured Video Device"

    DefaultDepth    24

EndSection

Quote:

Do you think we are looking in the right place? I have in Xorg.0.log Fatel sever error. Could we have a problem with Part of things installed for Xorg or a driver problem, Just tossing a few things in the mix.

I'm not excluding anything at the moment, you could be right.

Did you have any luck with other linux distro's on the hardware you are now building (B)LFS on (including X running on the intel driver)?

If so: You could check the settings that are used (xorg.conf, kernel version and options, lsmod output, Xorg.log.0 ....) and try to use those settings.