[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: sid: Console problems after starting X



On Fri, Sep 03, 2010 at 12:58:21AM -1000, Joel Roth wrote:
> Hello all,
> 
> Here's what happening.
> 
> After boot: normal console font (about 80 characters wide)
> 
> After startx: small console font (maybe 132 characters?)
> 
> A little later: no display in console at all (Alt-F7
> still gets me back to X)
> 
> This problem appeared soon after converting to 
> dependency-based boot process using insserv.
> 
> I've been using a self-compiled amd64 kernel with 32-bit userland.
> No such problems before insserv.
> 
> Thanks for any possible leads. I have no idea where to
> even start.

Yeah, that happened to me too, a while ago.  It's the X driver.
Specifically, it's the KMS settings that are messing you up.
I hate KMS.  It does solve certain problems for developers,
but causes other problems for users.  Maybe in a few years all
these KMS-related bugs will get sorted out.  But for now, they
are a pain.

How to fix it depends on your chipset.  In one case, I had
an nvidia card, and the upgrade switched me from the nv
driver to the nouveau driver.  I could get around it by
blacklisting the nouveau driver and creating an explicit
/etc/X11/xorg.conf file that specifies

   driver = "nv"

in the appropriate place.  For other chipsets, such as Intel,
you may be able to set a module parameter like "kms=0",
or some such thing.  Search the internet for your card
manufacturer, Linux, and KMS, and maybe you'll find something.
These techniques are only a temporary stopgap measure.
Eventually, there will be no option.  You will either have
to use KMS or not use an X server at all.  Oh joy.

-- 
  .''`.     Stephen Powell    
 : :'  :
 `. `'`
   `-


Reply to: