Gentoo Archives: gentoo-user

From: meino.cramer@×××.de
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] New monitor problems. < sighs >
Date: Wed, 15 Dec 2010 09:21:46
Message-Id: 20101215091701.GB5494@solfire
In Reply to: [gentoo-user] New monitor problems. < sighs > by Dale
1 Dale <rdalek1967@×××××.com> [10-12-15 09:48]:
2 > Hi again,
3 >
4 > For those mot up to date. I built a new rig that has a Nvidia GT220
5 > card in it. I bought a brand new monitor this morning, a LG W2253, and
6 > it worked one time. I had to reboot to move some things around and
7 > when I rebooted, the GUI doesn't come up. The BIOS screen shows up and
8 > I can see the services start up as well but when it switches to vt7, it
9 > just has a little blinking cursor at the top.
10 >
11 > This is a grep of the log:
12 >
13 > root@smoker / # cat /media/disk/files/Xorg.0.log | grep EE
14 > [ 2081.047] Current Operating System: Linux fireball 2.6.36-gentoo-r4
15 > #15 SMP PREEMPT Mon Dec 13 01:15:13 CST 2010 x86_64
16 > (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
17 > [ 2081.048] (II) Loading extension MIT-SCREEN-SAVER
18 > [ 2081.057] (EE) Failed to load module "dri" (module does not exist,
19 > 0)
20 > [ 2081.057] (EE) Failed to load module "dri2" (module does not exist,
21 > 0)
22 > [ 2082.101] (EE) NVIDIA(0): Failed to obtain a shared memory
23 > identifier: Function not
24 > [ 2082.101] (EE) NVIDIA(0): implemented
25 > [ 2082.118] (EE) NVIDIA: Failed to load module "dri2" (module does not
26 > exist, 0)
27 > [ 2082.120] (EE) Failed to initialize GLX extension (Compatible NVIDIA
28 > X driver not found)
29 > root@smoker / #
30 >
31 > I have tried X -configure, Xorg -configure and nvidia-xconfig and none
32 > of them do any better. I also did a emerge -e all the way up to
33 > nvidia-driver as well then reconfiged everything. Still no joy. I'm
34 > not going to mention all the reinstalls of the nvidia drivers and
35 > different versions I tried.
36 >
37 > I attached my xorg.conf file too. I can send the whole xorg.log file
38 > if needed. Oh, I always get the dri load error. I also used eselect
39 > to switch to nvidia's opengl to, many times.
40 >
41 > Could it be something weird with the card maybe? This is monitor two
42 > that has issues with it.
43 >
44 > I have a ATI card handy. If someone knows of a idiot proof guide I
45 > could follow. You know, one that you used and are confident it will
46 > work if followed. I don't have much hair left right now. :-(
47 >
48 > Just for fun, I got a Mandriva install CD and booted it up and even
49 > installed it on a spare drive. After the install, it boots just like
50 > Gentoo does. I can see the BIOS, the services and such but when it
51 > switches to vt7, just a blinking cursor.
52 >
53 > This new rig is turning into a nightmare. No wonder I waited almost 8
54 > years. lol
55 >
56 > Thoughts? Ideas? Suggestions, other than jumping in the creek.
57 >
58 > Dale
59 >
60 > :-) :-)
61
62
63 Hi Dale,
64
65 me again ... 8)
66
67 Dont hesitate...I think everything is alright.
68
69 First of all: In grub add a "2" at the end of the kernel command line.
70 This will boot you into runlevel 2 (console) without trying to switch
71 to X. This way you will have a "clean" machine with no confused nvidia
72 driver hanging a around and a polling X waiting to something to
73 connect to.
74
75 Next is:
76 Make yourself a cup of tea (or coffee, if you prefer) cause the next
77 steps may take some compilation time...
78
79 As root:
80 1.) Add "hal" to the USE flags of /etc/make.conf.
81 Do a
82 emerge --color=n -p -v --newuse --update --deep world
83
84 to find those packages, which need to be updated/recompiled due
85 to the changes to the USE flags. This morning there was an update
86 to the nvidia driver also.
87
88 I does not harm to execute the emerge command, even if you have
89 hal already installed and configured.
90
91 2.) cd to /etc
92 mkdir hal
93 and extract the fdi rulesset, I will send you in a personal mail
94 soon. If you have already a rulesset installed DONT overwrite it
95 with mine. May be you can use mine for comparison reasons, if
96 something goes wrong. The rulesset works for me -- but that is
97 no reason, that it have to work for you. BE WARNED :)
98
99 Folder layout:
100
101 /etc/hal/fdi/......
102
103 3.) Strip you xorg.conf. I will you send mine with the
104 hal/fdi-ruleset. I have a different monitori/mouse and a different
105 nvidia card. But these differences should be hidden behind hal and
106 the nvidia driver. Before installing it, check it against your
107 hardware. Again: YOU HAVE BEEN WARNED ! :)
108
109 4.) Add input_devices_evdev video_cards_nvidia to the USE flags of
110 xorg-drivers.
111
112 Add hal to the USE-flags of your xorg-server.
113
114 5.) Check your kernel config file for
115
116 CONFIG_INPUT_EVDEV=y
117
118 If not set, configured it and recompile the kernel. Reboot.
119
120
121 5.) Recompile xorg-drivers, xorg-servers, xf86-input-evdev
122 xf86-input-keyboard xf86-input-mouse, nvidia-drivers
123
124
125
126 6.) Reboot
127
128 7.) Submit
129
130 telinit 3
131
132 as root from the commandline.
133
134
135 Should work....
136
137
138 I cannot make responsible for any consequences directly or
139 indirectly resulting from the usage of these instructions....
140
141 Good luck!
142
143 Best regards,
144
145 mcc

Replies

Subject Author
Re: [gentoo-user] New monitor problems. < sighs > Neil Bothwick <neil@××××××××××.uk>
Re: [gentoo-user] New monitor problems. < sighs > Neil Bothwick <neil@××××××××××.uk>