Acer AL1715 resolutions not properly detected

Bug #32476 reported by Jerome Lacoste
12
Affects Status Importance Assigned to Milestone
xserver-xorg-driver-i810 (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Using Daper Live Alpha4, the only detected screen resolution was 640x480.

relevant xorg.conf Xorg.log extracts

Section "Device"
        Identifier "Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device"
        Driver "i810"
        BusID "PCI:0:2:0"
EndSection

Section "Monitor"
        Identifier "AL1715"
        Option "DPMS"
EndSection

Section "Screen"
        Identifier "Default Screen"
        Device "Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device"
        Monitor "AL1715"
        DefaultDepth 16
        SubSection "Display"
                Depth 1
                Modes "1280x1024" "1024x768" "832x624" "800x600" "720x400" "640x480"
        EndSubSection
        SubSection "Display"
                Depth 4
                Modes "1280x1024" "1024x768" "832x624" "800x600" "720x400" "640x480"
        EndSubSection
        SubSection "Display"
                Depth 8
                Modes "1280x1024" "1024x768" "832x624" "800x600" "720x400" "640x480"
        EndSubSection
        SubSection "Display"
                Depth 15
                Modes "1280x1024" "1024x768" "832x624" "800x600" "720x400" "640x480"
        EndSubSection
        SubSection "Display"
                Depth 16
                Modes "1280x1024" "1024x768" "832x624" "800x600" "720x400" "640x480"
        EndSubSection
        SubSection "Display"
                Depth 24
                Modes "1280x1024" "1024x768" "832x624" "800x600" "720x400" "640x480"
        EndSubSection
EndSection

(II) I810(0): Supported VESA Video Modes:
(II) I810(0): 720x400@70Hz
(II) I810(0): 640x480@60Hz
(II) I810(0): 640x480@72Hz
(II) I810(0): 640x480@75Hz
(II) I810(0): 800x600@56Hz
(II) I810(0): 800x600@60Hz
(II) I810(0): 800x600@72Hz
(II) I810(0): 800x600@75Hz
(II) I810(0): 1024x768@60Hz
(II) I810(0): 1024x768@70Hz
(II) I810(0): 1024x768@75Hz
(II) I810(0): 1280x1024@75Hz
(II) I810(0): Manufacturer's mask: 0
(II) I810(0): Supported Future Video Modes:
(II) I810(0): #0: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
(II) I810(0): Supported additional Video Mode:
(II) I810(0): clock: 108.0 MHz Image Size: 338 x 270 mm
(II) I810(0): h_active: 1280 h_sync: 1328 h_sync_end 1440 h_blank_end 1688 h_border: 0
(II) I810(0): v_active: 1024 v_sync: 1025 v_sync_end 1028 v_blanking: 1066 v_border: 0
(II) I810(0): Ranges: V min: 50 V max: 75 Hz, H min: 30 H max: 83 kHz, PixClock max 140 MHz
(II) I810(0): Monitor name: AL1715
(II) I810(0): ACER
(II) I810(0): Will use BIOS call 0x5f05 to set refresh rates for CRTs.
(--) I810(0): Maximum space available for video modes: 832 kByte
(II) I810(0): Using detected DDC timings
(II) I810(0): HorizSync 30-83
(II) I810(0): VertRefresh 50-75
(WW) I810(0): config file hsync range 28-33kHz not within DDC hsync range 30-83kHz
(WW) I810(0): config file vrefresh range 43-72Hz not within DDC vrefresh range 50-75Hz
[...]
(II) I810(0): AL1715: Using default hsync range of 30.00-83.00 kHz
(II) I810(0): AL1715: Using default vrefresh range of 50.00-75.00 Hz
(II) I810(0): Not using mode "1280x1024" (no mode of this name)
(II) I810(0): Not using mode "1024x768" (no mode of this name)
(II) I810(0): Not using mode "832x624" (no mode of this name)
(II) I810(0): Not using mode "800x600" (no mode of this name)
(II) I810(0): Not using mode "720x400" (no mode of this name)
(II) I810(0): Increasing the scanline pitch to allow tiling mode (640 -> 1024).
(--) I810(0): Virtual size is 640x480 (pitch 1024)
(**) I810(0): *Built-in mode "640x480"
(II) I810(0): Attempting to use 75.00Hz refresh for mode "640x480" (841)
(--) I810(0): Display dimensions: (340, 270) mm
(--) I810(0): DPI set to (47, 45)
(II) Loading sub module "fb"

Revision history for this message
Jerome Lacoste (jerome-lacoste) wrote : xorg.conf

The full xorg conf

Revision history for this message
Jerome Lacoste (jerome-lacoste) wrote : Xorg.log

full xorg log

Revision history for this message
Jerome Lacoste (jerome-lacoste) wrote :

I've further investigate the issue. I have 3 identical IBM machines that we are planning to migrate to ubuntu. They are to be used as test systems for a part of a 30+ machines network.

These 3 machines exhibit the same problem.

So the problem is maybe not related to the Screen (which is different on all 3) but to the chipset.

All 3 have a "Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device" and use the i810 module.

All screens should be able to get 1280x1024 but all end up with 640x480.

I have XFree 4.3 logs and configs from installed Suse Desktop 1.0 on these machines (where the screen resolution is better).

Can someone tell me where to look for to investigate further the issue?

Revision history for this message
Jerome Lacoste (jerome-lacoste) wrote : Diff between X86 log and XFree log

Seems like X detects a depth of 8 with Xorg 6.99:

-(**) I810(0): Depth 16, (--) framebuffer bpp 16
-(==) I810(0): RGB weight 565
-(==) I810(0): Default visual is TrueColor
+(II) Loading /usr/X11R6/lib/modules/libvgahw.a
+(II) Module vgahw: vendor="The XFree86 Project"
+ compiled for 4.3.0, module version = 0.1.0
+ ABI class: XFree86 Video Driver, version 0.6
+(**) I810(0): Depth 8, (--) framebuffer bpp 8
+(==) I810(0): RGB weight 888
+(==) I810(0): Default visual is PseudoColor

Revision history for this message
Jerome Lacoste (jerome-lacoste) wrote :

No Forget about my last comment: XFree detected 8 bits depth (hence the ugly colors) and Xorg detected 16 bits. So I really should get better colors (once I get a better resolution).

Now more interesting are these extracts from 2 X logs (2 different screens):

(II) I810(0): HorizSync 31-61
(II) I810(0): VertRefresh 56-75
(WW) I810(0): config file hsync range 28-33kHz not within DDC hsync range 31-61kHz
(WW) I810(0): config file vrefresh range 43-72Hz not within DDC vrefresh range 56-75Hz

(II) I810(0): HorizSync 30-83
(II) I810(0): VertRefresh 50-75
(WW) I810(0): config file hsync range 28-33kHz not within DDC hsync range 30-83kHz
(WW) I810(0): config file vrefresh range 43-72Hz not within DDC vrefresh range 50-75Hz

It seems like the DDC detected ranges are not used. I don't see any specified hsync/vrefresh rates in my generated config. I will try to manually set them up.

Revision history for this message
Fabian Kreutz (fabian-fs-maphy) wrote :

The same for me.
I also tried a working xorg.conf from my gentoo installation, but always "not using mode 1024x786 (no mode of this name)" comes up and the resolution ends up in 640x480.

Additionally there are problems in the textmode, starting in the installation process and then always on a text-terminal. These range from flickering, dim display to shifted lines (not at the same time). So maybe it's not the X-server's fault alone...?!

The computer is an Acer Travelmate 230. Ubuntu is 5.10 (freshly downloaded) and X:
X Window System Version 6.8.2 (Ubuntu 6.8.2-77 20051010174523 <email address hidden>)

Revision history for this message
Fabio Massimo Di Nitto (fabbione) wrote :

Can you please attach the full log and full config?

Is this card sharing the RAM with the system? If so how much
ram the BIOS does allocate to it?

Fabio

Changed in xorg-server:
status: Unconfirmed → Needs Info
Revision history for this message
Jerome Lacoste (jerome-lacoste) wrote : Re: [Bug 32476] Acer AL1715 resolutions not properly detected

On 3/21/06, Fabio Massimo Di Nitto <email address hidden> wrote:
[...]
> Status: Unconfirmed => Needs Info
>
> Comment:
> Can you please attach the full log and full config?

They are already attached... (for one of the 3 machines)

> Is this card sharing the RAM with the system? If so how much
> ram the BIOS does allocate to it?

No idea. I don't have access to the machines now.

I will have access to them later this week, and will try to install
dapper flight 5 then try to fix the issue after installation.

Revision history for this message
Jerome Lacoste (jerome-lacoste) wrote :

I think I ve solved the issue. I ve first changed the depth from 16 to 8 and restarted X. This allowed me to use 1024x768. I then rebooted the machine and changed the BIOS value from 1M to 8M. Rebooting allowed me to boot into ubuntu with 1024x768 and 24bits depth.

I haven t tried with the Live version but the results should be the same. Not sure if there s something X could do better. I will let you guys decide whether this issue can be closed.

Now I ve got to set the keyboard right...

Revision history for this message
Fabio Massimo Di Nitto (fabbione) wrote :

> then rebooted the machine and changed the BIOS value from 1M to 8M.
> Rebooting allowed me to boot into ubuntu with 1024x768 and 24bits depth.

Yup that's it. The driver can't do anything to force more RAM into the card.
Changing the BIOS setting is the only solution.

Changed in xserver-xorg-driver-i810:
status: Needs Info → Rejected
Revision history for this message
Paul Sladen (sladen) wrote :

Hi Jerome. Could you check whether the 'agpgart' module is being loaded with:

  /sbin/lsmod | grep agpgart

Revision history for this message
Jerome Lacoste (jerome-lacoste) wrote :

Paul,

yes the agpart module is loaded:

$ /sbin/lsmod | grep agpgart
agpgart 34888 3 drm,intel_agp

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.