[SOLVED] What happened to Xorg in Slackware 13.0? (Intel chipset)

bifferos · 10-17-2009, 01:22 PM

I'm just upgrading my laptop from Slackware 12.2 (which I had working perfectly) to 13.0. I have an Intel 82852/855GM Intel chipset.

First thing I noticed is that xorgconfig is just *not there*. Is there some package I can install to get this? xorgsetup doesn't work. When I run X it just gives me a blank screen.

Of course, I've tried to copy my old xorg.conf from 12.2, but that gives me a blank screen as well, and after, the message:

(EE)(EE) intel(1): [drm] failed to set drm interface version.
(EE) intel(1): Failed to become DRM master.
(EE) intel(1): No valid modes.
Setting master
Dropping master
error setting MTRR (base = 0xe8000000, size = 0x08000000, type = 1) Invalid argument

I've tried to load the DRM module, the intel module, agpgart, i810 and every other intel-related module I can think of but it doesn't help. I've tried the supplied SMP kernel, the experimental 2.6.30.5 kernel and the 2.6.31.4 kernel (with 'make oldconfig') and that doesn't work.

I've booted a KNOPPIX 6.01 CD (which at least gave me a display, although it perhaps needs the addition of 855resolution to give me the highest resolution), and copied the xorg.conf over, and tried that and it didn't work.

I've tried the other xf86 stuff in 'Testing' and that didn't help.

I am just on the verge of giving up and going back to 12.2 - this is really annoying, and I'd be glad of any hints.

thanks,
Biff.

dugan · 10-17-2009, 01:27 PM

Try it without an xorg.conf. The current version of X should auto-detect the correct settings.

And have a look at these two threads:
[TESTING REQUEST] Xorg in -current (yes, again)
Request For Testing - Intel Graphics Drivers in -current

jedi_sith_fears · 10-17-2009, 01:31 PM

Starting from 13.0, you can make it work without an xorg.conf file. But it will detect the vesa driver for intel chipsets, you need to run xorgsetup to make an xorg.conf and edit it to get the "intel" driver working for video acceleration.

bifferos · 10-17-2009, 01:37 PM

Thanks for the amazingly fast responses! I tried without the xorg.conf - Vesa would be a lot better than nothing...

But I now get:

(==) Using default built-in configuration (39 lines)
(EE) LoadModule: Module i810 does not have a i810ModuleData data object.
(EE) Failed to load module "i810" (invalid module, 0)
(EE) Failed to load module "fbdev" (module does not exist, 0)
Setting master
Dropping master

lumak · 10-17-2009, 01:38 PM

The only thing that needs to be in the xorg.conf is anything that isn't auto detected and configured.

The new xorg has problems with some intel chipsets. It may be possible to upgrade or downgrade the drivers for your chipset. see the packages and text in /extras/xf86-video-intel-alternate of the CD/DVD

Code:

# This will upgrade and or downgrade to the package listed on the commandline
upgradepkg path/to/the/other/package.tgz

Always read CHANGES_AND_HINTS.TXT that comes with the CD.

cwwilson721 · 10-17-2009, 01:51 PM

Other threads in this forum have given same advice...Go back to the DVD /extras/xf86-video-intel-alternate and install that package. It works.

bifferos · 10-17-2009, 02:37 PM

Quote:

Originally Posted by cwwilson721

Other threads in this forum have given same advice...Go back to the DVD /extras/xf86-video-intel-alternate and install that package. It works.

I'm not sure I have the same problem, here's what I get with all the various alternate packages:

2.5.1
=====

(EE) Failed to load module "fbdev" (module does not exist, 0)
(EE) intel(0): Failed to set tiling on front buffer: Invalid argument
(EE) intel(0): Failed to set tiling on back buffer: Invalid argument
(EE) intel(0): Failed to set tiling on depth buffer: Invalid argument
error setting MTRR (base = 0xe8000000, size = 0x08000000, type = 1) Invalid argument (22)

2.6.3
=====

(EE) Failed to load module "fbdev" (module does not exist, 0)
(EE) intel(0): Failed to pin front buffer: No space left on device

Fatal server error:
Couldn't bind memory for BO front buffer

2.7.1
=====

(EE) Failed to load module "i810" (module does not exist, 0)
(EE) Failed to load module "fbdev" (module does not exist, 0)
Setting master
Dropping master
error setting MTRR (base = 0xe8000000, size = 0x08000000, type = 1) Invalid argument (22)
(EE) intel(0): I830 Dma Cleanup Failed
(EE) intel(0): failed to destroy server context

2.8.1
=====

(EE) Failed to load module "i810" (module does not exist, 0)
(EE) Failed to load module "fbdev" (module does not exist, 0)
Setting master
Dropping master
error setting MTRR (base = 0xe8000000, size = 0x08000000, type = 1) Invalid argument (22)

bifferos · 10-17-2009, 02:45 PM

2.8.0 Gives the same result as 2.8.1.

This is all with 2.6.31.4 kernel. I'm starting to wonder if I should now try each and every combination with the default kernel, and also 2.6.30.5.

I wonder could something have changed so the default setting is to try to display on an external monitor, when it wasn't before? I have an SVGA out on the laptop. There doesn't seem much activity on that port either though.

Note that I just get a blank screen. There are no artifacts like there were in some other threads on this subject.

Didier Spaier · 10-17-2009, 03:12 PM

fbdev and i810 are kernel modules. it's easy to check if they are are here or not. As root :

Code:

modprobe -l|grep i810
modprobe -l|grep fbdev

If output is empty, chances are you forgot to configure it as modules. This is also easy to check, for instance :

Code:

bash-3.1$ grep -i i810 /boot/config-2.6.29.6-didier 
CONFIG_DRM_I810=m
bash-3.1$

With such an output all goes well.

In any other case you should configure again, make bzImage, make modules, make modules_install etc .

But my best advice is to first try with stock Slackware kernel & modules, i.e. generic-2.6.26.6.

witek · 10-17-2009, 03:29 PM

This is not Slackware to blame but developers of xorg and intel driver. I have very unstable X on my i810 intel video. Anyway latest intel driver seems to be best, grab it from here:
http://advamacs.com/pub/xf86-video-i...9.0-i486-1.tgz

agentdcooper · 10-17-2009, 03:45 PM

bifferos I wish u best of luck!

I have(had?) similar problems, I got a dell insprion 1100 laptop with intel 845G video, and 2x dell desktops running intel 82865G video hardware {{ as noted in my post in the [TESTING REQUEST] Xorg in -current (yes, again) thread }}. ALL the xf86-video-intel packages that came with slackware 13.0 (the default 2.8.0 + ALL the ones in /extra) gave me many headaches, and black screens + lockups when starting X using KDE4 as the window manager.

I have a working setup with slackware 13.0 using witek's xorg intel 2.9.0 package {{ downloadable @ http://advamacs.com/pub/xf86-video-i...9.0-i486-1.tgz }} + going with fluxbox as my default window manager (window maker, xfce, and all the window managers work with DRI enabled, EXCEPT KDE4). I cannot for the life of me get KDE4 that came with slackware 13 working with DRI enabled on any of my 3x computers that have intel video hardware.

in that [TESTING REQUEST] Xorg in -current (yes, again) thread, folkenfanel quotes from http://intellinuxgraphics.org/2009Q3.html

Quote:

Multiple fixes (need 2.6.32-rc1+ kernel) to make the driver stable for 8xx chipsets (The 2.8 driver series were extremely unstable with many of these chipsets)

so I'd like to try out 2.6.32-rc1+, I just havent done that yet... kinda waiting to hear back from someone more brave then I to report back on that

good luck tho! please let us know what you end up going with, especially if u get KDE4 working with DRI enabled on yr intel video hardware with slackware 13.

agentdcooper · 10-17-2009, 03:45 PM

Quote:

Originally Posted by witek

This is not Slackware to blame but developers of xorg and intel driver. I have very unstable X on my i810 intel video. Anyway latest intel driver seems to be best, grab it from here:
http://advamacs.com/pub/xf86-video-i...9.0-i486-1.tgz

hah, witek beat me to mention it! hi witek! and he is ABSOLUTELY right, slackware devs are not to blame! crappy linux drivers for xorg are...

bifferos · 10-17-2009, 04:27 PM

This didn't work either:
http://advamacs.com/pub/xf86-video-i...9.0-i486-1.tgz

I switched to 2.6.30.5 kernel and tried some driver combos, same story. I am just downloading Ubuntu, to see what that makes of my Intel chipset. Unfortunately pulling the intel driver from 12.2 slackware doesn't seem to work either. I guess I have to replace all X packages if I want to go that route :-(.

I remember this laptop was always a bit of a pig to get working with X, but I always managed in the past. I've had it for about 4 years, and several Slackware versions, but this is the first one I'm up against a brick wall on.

thanks,
Biff.

witek · 10-17-2009, 04:39 PM

Quote:

Originally Posted by bifferos

This didn't work either:
http://advamacs.com/pub/xf86-video-i...9.0-i486-1.tgz
I switched to 2.6.30.5 kernel[....]

Could you try it with 2.6.29.6? One important issue with changing intel video driver is they require machine reboot. Killing and restarting X is not enough.

agentdcooper · 10-17-2009, 04:42 PM

Quote:

Originally Posted by witek

Could you try it with 2.6.29.6? One important issue with changing intel video driver is they require machine reboot. Killing and restarting X is not enough.

I will also mention here, that I too am on 2.6.29.6 on each of my computers (I never tried with 2.6.30 yet). give it a try, sorry to hear of yr troubles. have u tried another window manager then KDE by chance as well?