linux-kernel - Re: 2.6.23-rc7 + radeonfb/s2ram

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] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 23 Sep 2007 22:22:28 +0300
From:	Mihai Donțu <mihai.dontu@...il.com>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: 2.6.23-rc7 + radeonfb/s2ram

On Sunday 23 September 2007, Rafael J. Wysocki wrote:
> On Sunday, 23 September 2007 20:31, Mihai Donțu wrote:
> > On Sunday 23 September 2007, Mihai Donțu wrote:
> > > I'll to do a full cleanup and start all over. I'm going to nail this thing down if
> > > it's the last thing I do! (so help me God) :)
> > 
> >   Found it!
> > 
> >   The problem was "Framebuffer Console support". It was enabled by default in older
> >   configs (like 2.6.22.7) but I think someone noticed this was bad and put it to
> >   default N in newer (2.6.23-rc7); and since I reused the .config from 2.6.21.3 ...
> > 
> >   So there, if one wants "ATI Radeon display support" on Radeon XPRESS 200M with
> >   X using radeon_drv.so, *should* put "Framebuffer Console support" to N (if it's
> >   not already).
> > 
> >   Now all I have to do is figure out what's the equivalent of "vga=791" on the new
> >   kernel (default text console looks really bad on my laptop).
> > 
> >   Sorry for all the noise (and spam),
> 
> No, this actually is valuable information, thanks for it. :-)
> 
> [I have missed your first post, sorry for that.]

  Don't worry.

  Now, one last update (I've just ran into it): I was preparing my laptop (to brag
  tomorrow with my new s2ram thinggie) when I noticed that after powering up from a
  suspend-to-ram, X doesn't like radeonfb working behind it's back, as a result
  it goes crazy (corrupted pixmaps and such). I should have tested these two together :|

  Bottom line: no radeonfb for me :( at least, not now; but I have to be honest with
  you: I don't see what commit dd1447134454b169d5ae353aceb93f2368db8547 brought new
  into the picture. The previous radeonfb worked just great, but then, again, maybe I'm
  not using the console at it's full power :)

  I have attached the dmesg after power up.

  Thanks,

  (last post today, I swear to God!)

-- 
Mihai Donțu

View attachment "dmesg-radeonfb.txt" of type "text/plain" (38475 bytes)