Creating an X11R6 Compatibility Symlink
 

OK I,m here now http://www.linuxfromscratch.org/blfs...x/x-setup.html
I ran I got, "ln: missing file operand". There is an empty file in /usr/X11R6. Also I take it these commands can be run from anywhere.

I guess my first two questions would be:

(1) Is $XORG_PREFIX defined? What is the output of `echo $XORG_PREFIX'?

(2) You're not actually typing the '<' and '>' characters, are you?

Opps Sorry

Ok swiftly moving on, I ran the next command and nothing it created the xorg.conf.new but no screen "Fatal server error no screen found" as reported in /var/log/Xorg.0.log, I am using a laptop if this helps
Last part of xorg.conf.new

This is the results of running Also results of

Hi,

Just to make sure:
- You ran the cd ~ && Xorg -configure step, which created a ~/xorg.conf.new file in ~
- You tested the created xorg.conf.new file with the X -retro -config ~/xorg.conf.new command and that one gave you the above mentioned error(s)?

It looks like the intel driver is loaded and rejected. Find the Section "Device" part and look for the Driver "xyz" line. xyz is probably intel in your case. Try changing that to vesa and see if that works. This vesa driver is very generic and you do want to change that to the driver that is specific for your hardware (probably intel), but you might need to change some kernel settings.

Also: All the available drivers can be found in /usr/lib/X11/modules/drivers, check to see if the inte driver is present.

PS: The ctrl-alt-backspace might not work unless you add/edit the xorg.conf file, solution was mentioned by me in your previous post: (this post).

Hope this helps.

PPSS: Just noticed your newest reply, which seems to strengthen my believe that the intel driver is missing/misconfigured.

Right I added "Option" as stated in post, mine is slightly different. Still wont go back to term?.
You were correct with Vesa got me a black screen, Nothing on it No mouse!! is this correct or still more probs?

Hi,

I don't think that is correct. When you start X using the X -retro ... line you should get a gray/grid-like screen with an X (the mouse pointer, which should be working). You cannot do anything yet, but that should prove a working, be it very basic, X.

Depending on the option in the Section "InputClass" you should be able to use ctrl-alt-bksp to exit X. If that is not possible you can always open a second terminal (ctrl-alt-F2) and kill the associated process from there.

Can you post the original xorg.conf.new file and the /var/log/Xorg.0.log file that goes with it (re-run the cd ~ && Xorg -configure and X -retro -config ~/xorg.conf.new steps to make sure we look at the original, unedited file).

Hope this helps.

Xorg.0.log
xorg.conf.new output of X-retro

I just tried it again still no screen but I did find that Ctrl+alt+F2,F3 etc wont work either? As if it,s not changing TTY

Hi,

The Xorg.0.log shows that:

1 - Multiple screens/monitors and devices are found (2 of each to be precise),
2 - intel is used as driver, but that one is not valid. You do eventually need the intel driver, the lspci output does show 82852/855GM. You probably need to configure this in the kernel, I'll focus on the vesa driver for the moment.
3 - there is a problem with xgi (ignore for now).

I removed the second device/screen/monitor from your xorg.conf.new, edited the ServerLayout and changed the intel driver to vesa, try this one:I added the Option "AllowEmptyInput" "off" entry due to this message from the Xorg.0.log:The Option "Xinerama" "off" makes sure that no dual screen or twin view is activated.

I do believe the blue entry is the correct one, although your lspci output does show 2 entries. If you still have problems try changing it to BusID "PCI:0:2:1" or remove that line altogether.

Hope this helps.

Edit: I added the Option "XkbOptions" "terminate:ctrl_alt_bksp" line to the keyboard Section "InputClass" section.

The error from the log files is quite clear. You do not have kernel modesetting enabled. Did you build the kernel with CONFIG_DRM_I915_KMS=y ?

Adam

Hi adamk75
Proberbly not I have stuck to the book and I dont remember it. In opinions which way do I go? Druuna is a great help I like all advice, All advice and direction has got me this far,

I have tried the modded xorg.conf.new still end up with the same result. Also changed the BUS:ID 0.2.0 >0:2:1

Hi,

Assuming you use a 2.6.37.X kernel and looking at your lspci output I do believe these should be activated in the kernel:

- AGP support for intel [855GM]:
Device Drivers -> Graphics support -> /dev/agpgart -> Intel 440LX/BX/GX, I8xx and E7x05 chipset support

- DRM/DRI suipport for intel [855GM]:
Device Drivers -> Graphics support -> Direct Rendering Manager -> Intel 830M, 845G, 852GM, 855GM, 865G

Also choose the i915 driver (this one is for the newer xorg version)

After you made the kernel changes, compiled and moved the appropriate files into place you do need to reboot for them to take effect. If all went well you should be able to use the intel driver instead of the vesa driver (xorg.conf file).

I first wanted to make sure you have a running X using vesa (the "easy one") that has a working keyboard and mouse, before going into this but my hand got forced ;)

Anyway, hope this helps.

I have 2.6.35.4 kernel as per LFS6.7

Hi,

I just checked, the options and location are the same for the 2.6.35 kernel.

Ok this is beyond me I will need help, never done this before, I have tried with google but cant get the hang of it :confused:

Hi,

You have done this before ;)

When building LFS, this chapter: 8.3. Linux-2.6.35.4.

If that is the only time you tinkered with the kernel I would suggest doing the following:

1) Unpack the kernel source at the proper location.2) Safe the current kernel files. You can boot from these at the moment so they work and you can fall back on them if something goes wrong.3) Edit kernel options and compile kernel.At the next boot the newly configured kernel will be booted.

I created an extra entry in grub so I can always boot from a working kernel. The entry is almost identical to the LFS line that is present, but instead of vmlinux-2.6.35.4-lfs-6.7 the original vmlinux-2.6.35.4-lfs-6.7.org is used. Post your grub.conf if you want this and don't know how to add this.

All steps mentioned as root user.

Hope this helps.

EDIT: Steps 1 and 2 are only needed once. Step 3 is all you need from now on to (re)compile your kernel.

I have been reading that amongst others when I did it I dont think I got to involved Not Brave enough

Hi,
LOL

I still remember my first kernel compile, took a lot longer then it does nowadays (8-9 hours vs less then half an hour, depending on your hardware). Boy, was I nervous during that long wait.....

But if you have a working kernel (you do, the ".org" version) on the side, you can edit/try as much as you want. That is the main reason I have a second LFS entry in grub. If the new kernel does not boot: Start the original one and try again.

If you don't have the extra entry in grub you can always use a liveCD to copy the .org files over the new files and reboot (the long way around, but it is a valid option).

Hope this helps.

Ok got through that rebooted ran x window commands again still no screen, I checked the xorg.log file still same error "No Kernel modesetting driver detected" xorg.conf.new shows the same as before

I have a thought I have a hard drive that I think boots this lappy with Ubuntu on, Is it worth getting information off the files that run that system?

Hi,

Without knowing which xorg.conf.new you are using at the moment I cannot comment.

I would start with the version I posted in post #11. Do change the Driver "vesa" into Driver "intel". Then run the X -retro -config ~/xorg.conf.new command.

Please post the output of the Xorg.0.log file after that (and possibly what is printed to screen by the X -retro ... command).

If you do get an X as prompt:
- does the mouse work?
- can you exit using ctrl-alt-bksp?

Hi,
The Xorg.0.log file should give us enough information (for now).

In general: It is always good to know what hardware you are using. X and the kernel both benefit when having this information (other parts do as well, but those 2 benefit the most). Both can/should be tailored to your hardware. It also means you need to feel comfortable with editing and compiling the kernel options.

Before I ran cd && I deleted old xorg.conf file xorg.conf.new
Xorg.0.log
Output from retro

What's the output of 'dmesg | grep drm'?

dmesg

OK, sounds like your kernel still isn't compiled with the correct options. Why not pastebin or attach your .config file?

Adam

Isn't that what I said needs to be enabled?

Ok so I have do rebuild the kernel again? If so where do I change the setting

Either edit the .config file and rebuild, or use 'make menuconfig' and find the setting in the DRM section (somewhere under device drivers). Alternatively, you can try booting with the option 'intel.modeset=1' passed to the kernel, but I'm not really all the familiar with the intel DRM stuff.

Adam

Ok thks That will have to wait till tomorro now tho

Hi,

To activate the i915 modesetting you indeed need to activate another option, which appears when selecting the i915 driver and is called: Enable modesetting on intel by default.

Recompile your kernel again and activate this option (section 3 from post #20):

Device Drivers -> Graphics support -> Direct Rendering Manager (as M) -> Intel 830M, 845G, 852GM, 855GM, 865G - > i915 driver -> Enable modesetting on intel by default.

Don't forget to reboot.

After the above is done create a new xorg.conf.new file using the cd ~ && Xorg -configure command and test with the X -retro -config ~/xorg.conf.new command.

Assuming that the intel/modesetting driver problem is now solved, it could be that you do not yet have a working keyboard and/or mouse and that you cannot yet exit X using the crtl-alt-bksp combo.

Mouse/keyboard -> Add the following to your ServerLayout section: Option "AllowEmptyInput" "off"
Ctrl-alt-bksp -> Add the following to your InputDevice / keyboard section: Option "XkbOptions" "terminate:ctrl_alt_bksp"

Hope this helps.

Ok I,m loosing the wil to live retro output
xorg.conf.newXorg.0.log
Xorg.0.log
http://pastebin.com/Z3dihzJf

CONFIG_DRM_I915=m
CONFIG_DRM_I915_KMS=y

Based on the "invalid module format" error, it sounds like you're trying to load an intel kernel module that is not compatible with the current running kernel. After rebuilding the kernel, did you boot off the new one you compiled?

Adam

Yes made as per instructions In earlier post "Druuna" then rebooted. I deleted the 3 files in boot then copied new ones over.

lsmod shows nothing?

lspci -v

Sorry, but I'm out of ideas. I don't know why your recompiled kernel would have this problem loading the i915 kernel module.

Adam

A thought. 1 try another kernel? 2 another intel driver?

Hi,

@spiky0011: I'm on my way to work and don't have time to look at this right now. I'll have a look when I get back home.

PS: I would not recommend using another kernel yet.

PPSS: You might want to try getting X to work using the vesa driver, this way you can create a working xorg.conf. The intel part can be done later.

Got to go, my train is about to arrive at my stop.....

Hi,

This looks to be an interesting problem.... An internet search shows that many people struggle with this driver.

Looking at the .config file you posted, a few of my doubts are already taken away (are these drivers compiled as a module: Yes. Are there any other framebuffer devices present: No). No need to double check that.

You could try adding the following line to the /etc/modprobe.conf file: options i915 modeset=1. I don't think a reboot is needed (not 100% sure).

I also read that the following should be set: Framebuffer Console support and Framebuffer Console Rotation (Device Drivers -> Graphics support -> Console display driver support -> Framebuffer Console support + Framebuffer Console Rotation).

The above need to be static (a *) and _not_ modular (no M)!! Looking at your .config file, the Framebuffer Console support is present, but it is set as a module, not static. The other option is not set in your kernel.

Just to make sure you install a clean module tree add the following step to the compile steps mentioned before:
Ok, that should be enough to keep you busy for a while :)

Seriously: I hope this will work for you, but like I stated before, a lot of people seem to have problems with this driver and X. We might not be out of the woods yet.....

Ok we have a new problem to start the evening off, turn laptop on grub ran through system then a black screen, no cursor nothing. I booted a live cd changed xorg.conf.new file from INTEL to VESA reboot black screen no cursor again, Typed in user name and password nothing? Typed "startx" as user eventually it started at command prompt as user logged in, with a msg about x.server connection refused. Anyway we back in the system If I reboot same thing again It wont start till I type startx. ANYONE FOR A CHALLENGE LOL

Hi,

X and booting don't (shouldn't...) influence each other. At the moment you boot into runlevel 3 (CLI) and to start X you need to run startx. So changing xorg.conf won't change anything in this case (it is only used when starting X).

Have you tried restoring the .org kernel files? As root, after booting from liveCD and mounting lfsreboot.

If your machine boots normally you now know that one of the options in the .new kernel is either missing or wrong (do have a look at my previous reply about the framebuffer settings).

BTW: You can use the liveCD to compile anew kernel, just make sure you copy the files to the appropriate location ($LFS/boot and not /boot).

You probably noticed that you are now doing the fun stuff :D Playing with the kernel and setting up X can be a challenge, which I see as "Fun!" Hopefully you look at it the same way, although you might not have the full skill-set to understand it all yet. I do hope you do learn from all this and start to feel more comfortable compiling a kernel (to name just one).

Hope this helps.

I did think of restoring old files earlier but didn't know if I had to redo kernel, You have cleared that up. Do I have to use live cd to replace old kernel files or can it be done while booted into system as root?

Hi,

If you can still boot into LFS you can do it from there. But......

If you are able to use your current LFS, you might first want to try recompiling the kernel with the Framebuffer Console Rotation and the added modprobe entry (see post #44 for details). That might solve the problem.

At the moment I'm not sure what it is you can/cannot do with your current system.

Hope this helps.

OK still no x system I have recompiled kernel as per post#44 and carried out file coping as nessecary, The system now starts as it did yesterday (as it should :D which is nice )
x -retro output
xorg.conf.new
Xorg logThe only file in /etc/modprobe.d is "usb.config"Yes I am having fun but i'm way out of depth now. Learnt a fair bit now Kernel dont scare me any more, As for moving round system with only terminal getting qiute swift lol

Hi,

A normal running system again,that is nice, but that wasn't the problem.

Can you also post your kernel configuration file (/boot/config-2.6.35.4)?

About the /etc/modprobe.conf file: Did you try adding the line I mentioned before (options i915 modeset=1)? Reboot after the change is made,just in case.

Does lsmod show any output?

I'll wait for your reply before trying other stuff.

PS: To make things easier for you I would like you to also post part of the /boot/grub/grub.cfg file. The part between: ### BEGIN /etc/grub.d/10_linux ### and ### END /etc/grub.d/10_linux ###. I would like to add some entries which would make switching between kernel version easier (and I'm also thinking about the next step, but lets not got there just yet).