All of lore.kernel.org
 help / color / mirror / Atom feed
From: Didier Spaier <didier.spaier-GqzDj6/B2j8@public.gmane.org>
To: Marcin Slusarz <marcin.slusarz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: Blank screen at startup (conflict with VESA VGA)
Date: Tue, 06 Apr 2010 10:27:42 +0200	[thread overview]
Message-ID: <4BBAF07E.9070005@epsm.fr> (raw)
In-Reply-To: <20100405214559.GA4230-OI9uyE9O0yo@public.gmane.org>

Thansk for your answer, kernel logs are attached.

Please note that this time I tried with a 2.6.32.2 kernel (nouveau works under X).

Marcin Slusarz wrote:
> On Mon, Apr 05, 2010 at 10:59:40PM +0200, Didier Spaier wrote:
>> Hi all,
>>
>> new to this list ;)
>>
>> I have a Lenovo Thinkpad T61. lspci|grep VGA says:
>> 01:00.0 VGA compatible controller: nVidia Corporation Quadro NVS 140M (rev a1)
>>
>> I have Slacware64-13.0 and Slackware64-current installed.
>>
>> Nouveau is modularized in all my kernels for -current.
>>
>> A problem arise even if I don't want to use nouveau under X: unless nouveau be blacklisted in /etc/modprobe.d/blacklist.conf at startup,
>> - when using one of the VESA modes at startup after a while screen goes blank and I get a warning in syslog e.g:
>>    Apr  2 18:58:56 darkstar kernel: fb: conflicting fb hw usage nouveaufb vs VESA VGA - removing generic driver,
> 
> It should work. Please provide full kernel log.

Kernel logs are attached for both cases. Unfortunately I don't see many differences ??

> 
>> - no problem when using a VGA mode (text only),
> 
> But Nouveau framebuffer activates without errors, right?
> 
Yes, switching to nouveau framebuffer OK in the latter case but not in the former

>> this disregarding which X driver I use afterwards (I always start in console mode).
>>
>> But according to this page:
>> http://nouveau.freedesktop.org/wiki/KernelModeSetting
>> I thought nouveaufb shouldn't conflict with vesafb ? Am I wrong ?
>>
>> I tried with modules shipped in vanilla 2.6.33.1 as well as the last Nouveau kernel repository pulled from git: no luck in both cases.
>>
>> I know there are easy workarounds: either use "VGA=ask", "VGA=ext" or "VGA=normal" as a lilo.conf option or blacklist nouveau -- which doesn't hurt anyway as nouveau will be loaded at X startup anyhow.
>>
>> But this is still is an annoyance for newcomers as when they are trapped all they can do if they have a VESA mode in lilo.conf is launch another system or live CD/DVD and either edit lilo.conf and run lilo again or edit blacklist.conf to blacklist nouveau.
>>
>> But still, before kindly requesting Patrick Volkerding to blacklist nouveau in -current for the time being, I wanted to now of another way to go if possible.
>>
>> Thanks in advance for your answers,
>>
>> Didier
> 

  parent reply	other threads:[~2010-04-06  8:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-05 20:59 Blank screen at startup (conflict with VESA VGA) Didier Spaier
     [not found] ` <4BBA4F3C.9070606-GqzDj6/B2j8@public.gmane.org>
2010-04-05 21:45   ` Marcin Slusarz
     [not found]     ` <20100405214559.GA4230-OI9uyE9O0yo@public.gmane.org>
2010-04-06  8:27       ` Didier Spaier [this message]
     [not found]         ` <4BBAF07E.9070005-GqzDj6/B2j8@public.gmane.org>
2010-04-06  8:48           ` Didier Spaier
2010-04-06 17:20           ` Marcin Slusarz
     [not found]             ` <20100406172019.GA2744-OI9uyE9O0yo@public.gmane.org>
2010-04-06 18:43               ` Didier Spaier
     [not found]                 ` <4BBB80B8.5000806-GqzDj6/B2j8@public.gmane.org>
2010-04-06 19:21                   ` Marcin Slusarz
     [not found]                     ` <20100406192109.GA2943-OI9uyE9O0yo@public.gmane.org>
2010-04-06 19:29                       ` Didier Spaier
     [not found]                         ` <20100410220119.GA2949@joi.lan>
     [not found]                           ` <4BC1DF11.3000603@epsm.fr>
     [not found]                             ` <20100411153919.GA12618@joi.lan>
     [not found]                               ` <4BC1FA45.1050808@epsm.fr>
     [not found]                                 ` <20100411170535.GA4016@joi.lan>
     [not found]                                   ` <4BC2231C.2060509@epsm.fr>
     [not found]                                     ` <4BC2BA76.8040509@epsm.fr>
     [not found]                                       ` <20100412101413.GA2733@joi.lan>
     [not found]                                         ` <4BC2F69E.6000905@epsm.fr>
     [not found]                                           ` <4BC2F69E.6000905-GqzDj6/B2j8@public.gmane.org>
2010-04-12 10:50                                             ` Marcin Slusarz
     [not found]                                               ` <20100412105013.GA2789-OI9uyE9O0yo@public.gmane.org>
2010-04-12 11:17                                                 ` Didier Spaier
2010-04-12 17:04                                                 ` Pekka Paalanen
     [not found]                                                   ` <20100412200458.0380a4fe-cxYvVS3buNOdIgDiPM52R8c4bpwCjbIv@public.gmane.org>
2010-04-13  1:15                                                     ` Christopher James Halse Rogers
2010-04-13 11:34                                                       ` Marcin Slusarz
     [not found]                                                         ` <20100413113451.GA10009-OI9uyE9O0yo@public.gmane.org>
2010-04-15 20:19                                                           ` Aaron Plattner
     [not found]                                                             ` <20100415201941.GA20030-J3EY2hv0KmgMOYszX5p1ytBPR1lH4CV8@public.gmane.org>
2010-04-16 17:19                                                               ` Marcin Slusarz
2010-04-05 22:43   ` Pekka Paalanen
     [not found]     ` <20100406014338.752ab0a3-cxYvVS3buNOdIgDiPM52R8c4bpwCjbIv@public.gmane.org>
2010-04-06  8:47       ` Didier Spaier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BBAF07E.9070005@epsm.fr \
    --to=didier.spaier-gqzdj6/b2j8@public.gmane.org \
    --cc=marcin.slusarz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.