Gentoo Archives: gentoo-user

From: Nikos Chantziaras <realnc@×××××.de>
To: gentoo-user@l.g.o
Subject: [gentoo-user] Re: xorg 1.9
Date: Thu, 20 Jan 2011 07:24:17
Message-Id: ih8nr8$55j$1@dough.gmane.org
In Reply to: Re: [gentoo-user] Re: xorg 1.9 by dan blum
1 On 01/20/2011 06:57 AM, dan blum wrote:
2 > Nikos,
3 >
4 > Thanks for the help. My system is looking for the i915 module. Would you
5 > know where the module needs to be?
6
7 Not sure what you mean with "system." Do you mean X.Org tells you it
8 can't find the kernel module for i915 graphics? Enable it in the kernel
9 menuconfig:
10
11 Device Drivers -> Graphics support -> Direct Rendering Manager
12
13 There's an entry: "Intel 830M, 845G, 852GM, 855GM, 865G (i915 driver)".
14 Make sure it's not build as a module and mark it with a "<*>". Enter
15 that submenu and select "i915 driver". Also select the "Enable
16 modesetting on intel by default" option.
17
18
19 > --- On *Tue, 1/18/11, Nikos Chantziaras /<realnc@×××××.de>/* wrote:
20 >
21 >
22 > From: Nikos Chantziaras <realnc@×××××.de>
23 > Subject: [gentoo-user] Re: xorg 1.9
24 > To: gentoo-user@l.g.o
25 > Date: Tuesday, January 18, 2011, 10:58 PM
26 >
27 > On 01/19/2011 06:46 AM, dan blum wrote:
28 > > I upgraded my xorg from 1.76 to 1.9 yesterday, including
29 > downloading the
30 > > most recent drivers. When the new system did not work, I checked the
31 > > xorg log (attached) and I thought that the problem was the mode
32 > setting.
33 > > So in the kernel, I "enabled the modesetting by default" and now the
34 > > card does not send any signals to the screen at all.
35 > >
36 > > I can go back to the old kernel settings. But does anyone know
37 > what was
38 > > the initial problem, and what needs to be done to correct this.
39 > >
40 > > Thanks for any advice.
41 >
42 > You seem to be using kernel 2.6.32. That *might* be the problem. Try
43 > 2.6.36.
44 >
45 > Other than that, the usual stuff applies: Delete your xorg.conf (so
46 > that X.Org can automatically configure everything) and make sure you
47 > don't have VESAFB enabled in the kernel.
48 >
49 >
50 >