I recently removed my xorg.conf and x refused to start. Ob the screen I saw 
blinking and then. Well nothing.
Maybe if you put some basic conf it will help?
-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

Kevin Thomas <[email protected]> wrote:

I just read over that, but I didn't get much out of it other than "the intel 
stuff worked" (there wasn't really any explanation on that) and that bumblee is 
the proclaimed solution, unless I'm missing something.  I don't know what you 
mean by the latest and greatest driver. Are you referring to Intel or Nvidia? I 
don't even have an xorg.conf file on my system.

On 09/12/2011 09:36 PM, Andrew Z wrote: 

hmmmm. Did you see this : https://bbs.archlinux.org/viewtopic.php?id=124918 ?
(silly question, but i'll still try) - are you sure you have the latest and 
greatest driver?

get rid of xorg.conf  and see if you get anything.


On Mon, Sep 12, 2011 at 7:31 PM, Kevin Thomas <[email protected]> wrote:

Here's the relevant lines from /var/log/messages:
<cut of by AZ>
Sep 11 21:09:55 xps kernel: [drm] nouveau 0000:01:00.0: Disabling fbcon 
acceleration...
Sep 11 21:09:55 xps kernel: [drm] nouveau 0000:01:00.0: Unpinning 
framebuffer(s)...II) intel(0): Modeline "800x600"x60.3   40.00  800 840 968 
1056  600 601 605 628 +hsync +vsync (37.9 kHz)
(II) intel(0): Modeline "800x600"x56.2   36.00  800 824 896 1024  600 601 603 
625 +hsync +vsync (35.2 kHz)
(II) intel(0): Modeline "848x480"x60.0   33.75  848 864 976 1088  480 486 494 
517 +hsync +vsync (31.0 kHz)
(II) intel(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 
525 -hsync -vsync (31.5 kHz)
(II) intel(0): EDID for output VGA2
(II) intel(0): EDID for output HDMI2
(II) intel(0): EDID for output DP1 



On 09/11/2011 11:07 PM, Andrew Z wrote: 

Kevin,
I'm sure you went over this. Already, but maybe you can tell us what last 
(relevant ) lines are in messages are and what X.log has?
-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

Kevin Thomas <[email protected]> wrote: 

You are correct that when you install the kmod-nvidia package, it automatically 
disables nouveau and blacklists it for you, but I didn't know there was a new 
nvidia xorg.conf file created. After I installed the kmod-nvidia package again, 
I restarted and modified the kernel arguements to include the intel.disable=1 
arguement, but the result was the same....eventually the screen flickered a few 
times and it stopped booting, although I could still open a terminal via 
alt+F2. I'm not sure what to try next. Someone requested some command output 
from me in a different email, which I provided, but I'm lost now. I didn't 
think it would be this difficult. Kevin On 09/11/2011 01:10 PM, Phil Perry 
wrote: > On 11/09/11 18:39, Chris Pemberton wrote: > >> Some good info over at 
the archlinux forums: >> >> https://bbs.archlinux.org/viewtopic.php?pid=881549 
>> >> http://linux-hybrid-graphics.blogspot.com/ >> >> To test the nvidia 
driver: blacklist the nouveau and intel graphic >> modules, di
 sable
kernel mode-setting, and boot to runlevel 3 (all via >> the kernel command line 
args below). Then run nvidia's xorg creation >> tool (nvidia-xconfig). Give X a 
try and see if it works. >> >> nouveau.disable=1 intel.disable=1 nomodeset 3 
<--append this to grub >> kernel line >> > > The elrepo.org kmod-nvidia package 
already disables nouveau > mode-setting (nouveau.modeset=0), blacklists the 
nouveau driver and > runs nvidia-xconfig to create a suitable xorg.conf file. > 
> Perhaps in the case of these hybrid systems we also need to blacklist > the 
Intel driver too as suggested above. Do we know which Intel driver > is being 
loaded? > > Once you have worked out what works for you through testing, you > 
should file a bug at http://elrepo.org/bugs/ and we can get these > fixes 
incorporated into the package. > >> If that wont work, black list nouveau and 
nvidia, and try the intel >> module (delete the xorg.conf made by 
nvidia-xconfig) >> >> nouveau.disable=1 nomodeset 3 <-- append t
 his to
grub kernel line >> >> Hope that helps. >> >> Chris >> 


Reply via email to