| View previous topic :: View next topic |
| Author |
Message |
Spectre85
n00b
Joined: 19 Oct 2009
Posts: 29
|
 Posted: Fri Oct 30, 2009 12:06 am Post subject: [solved] X "no screens found" after depclean |
 |
|
I had my system all setup and working perfectly, and then decided to do emerge --depclean (I know, bad idea). I followed all of the advice for updating the system beforehand, etc, etc. That's in the past now though.
After running this, X will no longer start. I have no xorg.conf file (it was working perfectly before without it). Here is the relevant part of the log file:
| Code: |
...
(--) PCI:*(0:0:1:0) 8086:7125:0e11:b165 Intel Corporation 82810E DC-133 (CGC) Chipset Graphics Controller rev 3, Mem @ 0x44000000/67108864, 0x40100000/524288
(==) Using default built-in configuration (39 lines)
(==) --- Start of built-in configuration ---
Section "Device"
Identifier "Builtin Default intel Device 0"
Driver "intel"
EndSection
Section "Screen"
Identifier "Builtin Default intel Screen 0"
Device "Builtin Default intel Device 0"
EndSection
Section "Device"
Identifier "Builtin Default i810 Device 0"
Driver "i810"
EndSection
Section "Screen"
Identifier "Builtin Default i810 Screen 0"
Device "Builtin Default i810 Device 0"
EndSection
Section "Device"
Identifier "Builtin Default vesa Device 0"
Driver "vesa"
EndSection
Section "Screen"
Identifier "Builtin Default vesa Screen 0"
Device "Builtin Default vesa Device 0"
EndSection
Section "Device"
Identifier "Builtin Default fbdev Device 0"
Driver "fbdev"
EndSection
Section "Screen"
Identifier "Builtin Default fbdev Screen 0"
Device "Builtin Default fbdev Device 0"
EndSection
Section "ServerLayout"
Identifier "Builtin Default Layout"
Screen "Builtin Default intel Screen 0"
Screen "Builtin Default i810 Screen 0"
Screen "Builtin Default vesa Screen 0"
Screen "Builtin Default fbdev Screen 0"
EndSection
(==) --- End of built-in configuration ---
(==) ServerLayout "Builtin Default Layout"
(**) |-->Screen "Builtin Default intel Screen 0" (0)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default intel Device 0"
(==) No monitor specified for screen "Builtin Default intel Screen 0".
Using a default monitor configuration.
(**) |-->Screen "Builtin Default i810 Screen 0" (1)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default i810 Device 0"
(==) No monitor specified for screen "Builtin Default i810 Screen 0".
Using a default monitor configuration.
(**) |-->Screen "Builtin Default vesa Screen 0" (2)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default vesa Device 0"
(==) No monitor specified for screen "Builtin Default vesa Screen 0".
Using a default monitor configuration.
(**) |-->Screen "Builtin Default fbdev Screen 0" (3)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default fbdev Device 0"
(==) No monitor specified for screen "Builtin Default fbdev Screen 0".
Using a default monitor configuration.
...
...
...
(II) LoadModule: "intel"
(WW) Warning, couldn't open module intel
(II) UnloadModule: "intel"
(EE) Failed to load module "intel" (module does not exist, 0)
(II) LoadModule: "i810"
(WW) Warning, couldn't open module i810
(II) UnloadModule: "i810"
(EE) Failed to load module "i810" (module does not exist, 0)
(II) LoadModule: "vesa"
(WW) Warning, couldn't open module vesa
(II) UnloadModule: "vesa"
(EE) Failed to load module "vesa" (module does not exist, 0)
(II) LoadModule: "fbdev"
(WW) Warning, couldn't open module fbdev
(II) UnloadModule: "fbdev"
(EE) Failed to load module "fbdev" (module does not exist, 0)
(EE) No drivers available.
Fatal server error:
no screens found
...
|
So it seems to be trying to load them as modules (i810 is built into the kernel and specified under make.conf). I noticed that the depclean unmerged the 2.6.30-r7 gentoo-sources and merged the 2.6.30-r8 gentoo-sources. So I decided to just make the leap to r8...I used the same .config file (double checked it in make menuconfig and it was the same as the r7 file that worked). I then compiled a new kernel, updated the /usr/src/linux link, added it to grub, etc, etc. However, this did not solve my problem - I get the exact same error. I then decided to remerge xorg, which did not help. Now I just finshed remerged EVERYTHING I have (emerge -av world). I still get the same error. I'm not sure why it is even checking for them as modules when i810 is built into the kernel.
Any suggestions?
As always, thanks!
Scott
Last edited by Spectre85 on Fri Oct 30, 2009 10:49 pm; edited 1 time in total |
|
| Back to top |
|
 |
Spectre85
n00b
Joined: 19 Oct 2009
Posts: 29
|
| Posted: Fri Oct 30, 2009 1:28 am Post subject: |
|
|
| I think I know what the problem is....doing some remerging and I'll report back later... |
|
| Back to top |
|
|
Spectre85
n00b
Joined: 19 Oct 2009
Posts: 29
|
| Posted: Fri Oct 30, 2009 2:03 am Post subject: |
|
|
Ah...yes  I have now touched the fire and learned my lesson (with depclean)
For anyone that may stumble upon this in the future...here was my problem:
1. I originally emerged xorg-server using VIDEO_CARDS="intel i810" in my make.conf
2. I decided (incorrectly) that I only needed VIDEO_CARDS="i810", so I made this change and remerged things (using "emerge --update --deep --newuse world"). I expected that this would remerge xorg-server (as it did), but without ANYTHING from "intel". However, unmerging/remerging does NOT get rid of other packages that were installed as dependencies (depclean does). So I thought my system was configured as if I had used VIDEO_CARDS="i810" from the beginning, when in fact, the "intel" stuff was still installed on my system. This is why it still worked fine at this point - the files I needed were still installed.
3. By doing the depclean, I then removed the files created from "intel"
4. My system was "broken" since those files were removed.
5. Confusion...followed by research that sparked my idea of what went wrong...
7. Changed VIDEO_CARDS back to "intel i810" and remerged xorg-server. Viola - things are back to the way I like them. Valuable lesson learned.
-Scott |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
