Bug 18395 - [IGP 320M] No internal/LVDS detected (regression since 6.6.3)
Summary: [IGP 320M] No internal/LVDS detected (regression since 6.6.3)
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: 7.4 (2008.09)
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL: https://bugs.edge.launchpad.net/ubunt...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-05 13:56 UTC by Bryce Harrington
Modified: 2008-11-06 12:48 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Xorg.0.log from Intrepid Alpha 4 (47.33 KB, text/plain)
2008-11-05 13:56 UTC, Bryce Harrington
no flags Details
possible fix (659 bytes, patch)
2008-11-05 16:33 UTC, Alex Deucher
no flags Details | Splinter Review
BIOS requested for IGP 320M on HP4325us (60.00 KB, application/octet-stream)
2008-11-06 06:18 UTC, Matthias Johnson
no flags Details
improvised patch (87 bytes, patch)
2008-11-06 08:23 UTC, Matthias Johnson
no flags Details | Splinter Review

Description Bryce Harrington 2008-11-05 13:56:26 UTC
Created attachment 20087 [details]
Xorg.0.log from Intrepid Alpha 4

Forwarding this bug from a Ubuntu reporter:
https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/190857

[Problem]
The LVDS on this system is not detected on the laptop.  The external VGA can be made to work by adding modes to it.

[Original Report]
On HP4300 laptop with ATI IGP 320M card, the current xserver-xorg-video-ati package fails to find the internal/LVDS screen. I've had to switch the MonitorLayout in the past but under Gutsy it doesn't detect it at all. Down grading to package from Feisty (xserver-xorg-video-ati_6.6.3-2ubuntu6_i386.deb) worked.  [But 6.6.3 is unavailable in Intrepid.]

I then upgraded to Hoary and the behaviour as changed slightly. Now the LVDS displays a partial screen. The resolution is set to 1280x768, while the LVDS only supports 1024x768. Any attempt to change this fails.

So I kept on playing with it a little more with the default xorg.conf file, which produces the 1280x768 output on the LVDS.

Like I said the LVDS is still not being detected, but since X assumes a default screen size of 1280x768 on the non-attached external display I did some more experimentation and found that the following results in something useful on the screen with direct rendering enabled:

  # build a modeline - the following works for me
  gtf 1024 768 78.654
  # then use the output from above (everything after the word modeline)
  # to set the resolution of the non-existent external monitor
  xrandr --newmode "1024x768_78.65" 87.02 1024 1088 1200 1376 768 769 772 804 -HSync +Vsync

  xrandr --addmode VGA-0 "1024x768_78.65"

  xrandr --output VGA-0 --mode "1024x768_78.65"

I think it's still problematic that the LVDS is not detected, since it keeps me from running dual headed, but at least the laptop is semi-functional. [Here is] the current xrandr output after the above tweaks:

 Screen 0: minimum 320 x 200, current 1024 x 768, maximum 1280 x 1200
 VGA-0 disconnected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1024x768_78.65   78.7* 
 S-video disconnected (normal left inverted right x axis y axis)

In Intrepid Alpha 4, the xrandr output looks like this:

Screen 0: minimum 320 x 200, current 1152 x 864, maximum 1360 x 1200
VGA-0 disconnected 1152x864+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
S-video disconnected (normal left inverted right x axis y axis)
  1152x864 (0x4f)   81.6MHz
        h: width  1152 start 1216 end 1336 total 1520 skew    0 clock   53.7KHz
        v: height  864 start  865 end  868 total  895           clock   60.0Hz

Still no LVDS...


[lspci]
00:00.0 Host bridge: ATI Technologies Inc AGP Bridge [IGP 320M] (rev 13)
00:01.0 PCI bridge: ATI Technologies Inc PCI Bridge [IGP 320M] (rev 01)
00:02.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
00:06.0 Multimedia audio controller: ALi Corporation M5451 PCI AC-Link Controller Audio Device (rev 02)
00:07.0 ISA bridge: ALi Corporation M1533/M1535 PCI to ISA Bridge [Aladdin IV/V/V+]
00:08.0 Modem: ALi Corporation M5457 AC'97 Modem Controller
00:0a.0 CardBus bridge: O2 Micro, Inc. OZ601/6912/711E0 CardBus/SmartCardBus Controller
00:10.0 IDE interface: ALi Corporation M5229 IDE (rev c4)
00:11.0 Bridge: ALi Corporation M7101 Power Management Controller [PMU]
00:12.0 Ethernet controller: National Semiconductor Corporation DP83815 (MacPhyter) Ethernet Controller
01:05.0 VGA compatible controller: ATI Technologies Inc Radeon IGP 320 M
Comment 1 Alex Deucher 2008-11-05 16:33:17 UTC
Created attachment 20095 [details] [review]
possible fix

Does this patch fix the issue?  If not please send me a copy of your video bios:
(as root)
cd /sys/bus/pci/devices/<pci bus id>/
echo 1 > rom
cat rom > /tmp/video.bios
echo 0 > rom
Comment 2 Matthias Johnson 2008-11-06 06:18:04 UTC
Created attachment 20112 [details]
BIOS requested for IGP 320M on HP4325us

Here is the requested BIOS.  I'll see if I can give the patch a shot today.
Comment 3 Matthias Johnson 2008-11-06 08:23:19 UTC
Created attachment 20116 [details] [review]
improvised patch

I just built a new package based on the source for Ubuntu 8.04 (Hardy).  The patch failed to apply against the 6.8.0-1 source release, but I improvised and applied the attached diff, which only adds the info->IsIGP to one line of the source I was working with.  This appears to work and xrandr now produces:

Screen 0: minimum 320 x 200, current 1024 x 768, maximum 1024 x 1024

VGA-0 disconnected (normal left inverted right x axis y axis)

LVDS connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm

   1024x768       60.0*+   60.0  

   800x600        60.3  

   640x480        59.9  

S-video disconnected (normal left inverted right x axis y axis)



WOoo Wooo.  there is the LVDS!
Comment 4 Alex Deucher 2008-11-06 12:48:20 UTC
fix pushed: 902eaf768142c6c7dcc487e10775027b84cd1f9a


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.