lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20091003151243.GG32486@mea-ext.zmailer.org>
Date:	Sat, 3 Oct 2009 18:12:43 +0300
From:	Matti Aarnio <matti.aarnio@...iler.org>
To:	Alex Deucher <alexdeucher@...il.com>
Cc:	dri-devel@...ts.sf.net, linux-kernel@...r.kernel.org
Subject: Re: How to disable drm/kms actions during boot?

On Sat, Oct 03, 2009 at 10:38:12AM -0400, Alex Deucher wrote:
> From: Alex Deucher <alexdeucher@...il.com>
> 
> On Sat, Oct 3, 2009 at 8:19 AM, Matti Aarnio <matti.aarnio@...iler.org> wrote:
> > I have a display card + display combination that has recently had much problems
> > during system boot.  Some system versions boot just fine to very large text mode,
> > others create entirely black display.
> >
> > Is there any way to forbid the DRM from doing "maximize the text display area"
> > operation at all during the boot?  I do want the DRM/KMS to happen latter, but
> > NOT during system boot!
> 
> Boot with nomodeset or radeon.modeset=0 on the kernel command line.
> That will disable kernel modesetting at boot.  You can then manually
> load the modules with or without modesetting once the system is
> booted.  drm-next also recently got support for forcing the console
> mode.

Thanks, that saved the day.  The kernel boots to text console just fine, and when
I am happy, log in as my non-privileged self and start X, firmware loading and mode
settings are working correctly.

Of course I would be happier without these boot commandline extras, so
current Fedora 12 (Beta) kernel has some bad radeon drm/dri/kms bits on it.
Couple of weeks ago things did work just fine with modesetting happening
early in the boot.  Four weeks ago things failed, and six weeks ago this
modesetting thing did not exist...

Current kernel is:
  2.6.31.1-56.fc12.x86_64 #1 SMP

> Alex

/Matti Aarnio
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ