On Tuesday 15 February 2005 17:49, David S. Miller wrote: > On sparc, when "mode" is NULL, we should always use default_var as > setup by PROM probed values. > > Here is the fix: Excellent! Tested the patch with 2.6.11-rc3-bk2 and AFAICT it completely restores the old behavior. I guess that solves the regression since 2.6.10-rc2. Please let me know if this patch will be submitted for inclusion as is so I can also submit it for inclusion in the Debian 2.6.10 kernel. From my experiences in tracing and testing this, I have a couple of questions I'd like to put before you and the lists. (I should add that my experience with sparcs is still very limited.) I would like to set a lower default resolution as my monitor barely supports 1152x900@66. I tried two things: - # eeprom output-device=screen:r1024x768x70 This seems to be completely ignored during boot; resolution is still 1152x900. - boot with parameter 'video=atyfb:1024x768@70' This does work, but csync is not set to high and so the monitor again goes into suspend; after 'fbset -csync high' the monitor turns on. Is csync something that needs to be set by the user or should the driver take care of that also at frequencies other then 1152x900? The second question concerns the use of Stop-A. With the console at 1152x900@66, if I press Stop-A, I get the openprom prompt. The screen has the last display before pressing Stop-A with a white square inside it containing the openprom display (filling about 75% of the screen). If I do the same at 1024x768@70, I get a garbled display (no readable text from the openprom). I can still press go to return to linux though and the display is restored after clearing it. Can/should this be fixed or should the conclusion be that resolutions other than 1152x900@66 are just not supported? Cheers, Frans Pop
Attachment:
pgpNRqlYmenuc.pgp
Description: PGP signature