Bug 219730

Summary: only up to 800*600 dpi possible
Product: [openSUSE] SUSE Linux 10.1 Reporter: Tim Fechtner <timmi>
Component: SaX2Assignee: Marcus Schaefer <ms>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: sndirsch
Version: Final   
Target Milestone: ---   
Hardware: 64bit   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: log.tar.bz2 - the hole /var/log as tar.bz2
hwinfo

Description Tim Fechtner 2006-11-10 07:42:40 UTC
I'm using the Dell notebook "Inspiron 6400".

Sax regocnizes the graphic card corectly as ATI mobility radion X1400. But also when I choose 1280*800 (16:10, this corresponds to the display also recognized corectly as 16:10 display), I get only 800*600 dpi (what is 4:3, so the display makes a bad impression). Also it works only with 16bit, not with 32bit color.

The "second monitor" (the external monitor adapter of the laptop) is also not recognized.
Comment 1 Tim Fechtner 2006-11-10 07:45:14 UTC
Created attachment 104606 [details]
log.tar.bz2 - the hole /var/log as tar.bz2
Comment 2 Tim Fechtner 2006-11-10 07:45:42 UTC
Created attachment 104607 [details]
hwinfo
Comment 3 Marcus Schaefer 2006-11-11 17:34:27 UTC
sorry I don't understand what your problem is ?
Comment 4 Stefan Dirsch 2006-11-11 18:41:30 UTC
X1400 ---> fbdev. Change your framebuffer settings (resolution and color depth) accordingly.
Comment 6 Tim Fechtner 2006-11-12 20:26:31 UTC
There are two problems:

1.) I choose 1280*800 in Sax, but I get only 800*600.

2.) The graphic card has support for two screens (internal LCD of the notebook + external vga port), but Sax lets me configure only the first one (the LCD).
Comment 7 Marcus Schaefer 2006-11-13 09:51:13 UTC
The X1400 is fbdev based so if you call sax2 you will get a message
pointing out that no color and resolution changes are possible. I checked
that it works.

- 1280x800 is not a valid kernel framebuffer resolution. You can only use
  1024x768 by typing vga=0x318 at the kernel boot prompt for example

- dualhead is not supported using the fbdev driver. An accelerated driver is
  needed to do that.

- Stefan according to your suggestion. This problem is solved by not
  offer the possibility to select a resolution other than the current
  fbdev resolution. Problem is within yast I don't have a check for the
  fbdev module... 
Comment 8 Stefan Dirsch 2006-11-13 10:38:54 UTC
Well, my proposal (enhancement for 10.3!) was to offer only valid framebuffer solutions/color depths you get with "hwinfo --framebuffer" and to write this hex value to menu.lst + inform the user the need to reboot.
Comment 9 Marcus Schaefer 2006-11-13 10:49:14 UTC
We had something like this implemented some time ago and it has
been removed for some reasons:

1) fbdev is a temporary solution more like a workaround
2) bootloader configuration is not part of sax
3) people don't understand why they can't setup the resolution
   they want for example 1280x800
4) sync setup is not possible at all
5) dualhead setup is not possible at all

---> according to this fbdev is not a business case to me. Every time
     people have to use fbdev they are complaining about that they
     can't use their prefered resolution or sync ranges or dual-head or
     whatever instead of beeing glad that there is something which works
     but with restrictions

the conflict to yast2-bootloader was the main issue why it has been
removed from sax
Comment 10 Stefan Dirsch 2006-11-13 10:59:21 UTC
Unfortunately nearly all ATI GPUs are now affected by this problem to use fbdev. :-(

Is there no way to adjust the yast2-bootloader? E.g. it could read a meta file written by SaX2 (if it exists), in which the vga hex value is configured?

Comment 11 Marcus Schaefer 2006-11-13 11:02:51 UTC
1) why not use the vesa driver ?

2) good idea you can pass this on as an enhancement to yast2-bootloader
Comment 12 Stefan Dirsch 2006-11-13 11:13:18 UTC
(In reply to comment #11)
> 1) why not use the vesa driver ?
Honestly the fbdev driver works more reliable than the vesa driver.

> 2) good idea you can pass this on as an enhancement to yast2-bootloader
I can do so.

Comment 13 Stefan Dirsch 2006-11-13 11:24:15 UTC
>> 2) good idea you can pass this on as an enhancement to
>>   yast2-bootloader
> I can do so.
done. Bug #220368
Comment 14 Stefan Dirsch 2006-11-13 11:24:54 UTC
reopen to close as duplicate.
Comment 15 Stefan Dirsch 2006-11-13 11:25:12 UTC

*** This bug has been marked as a duplicate of bug 220368 ***