ubuntu-x-swat team mailing list archive
-
ubuntu-x-swat team
-
Mailing list archive
-
Message #115972
[Bug 621756] Re: Monitor Detection Problem in upgrade to 10.04.1
apport information
** Tags added: apport-collected
** Description changed:
Ubunutu upgrade from 9.10 to 10.04.1, new problem with Monitor (was always unknown but did not bring the following error: after booting the monitor displays the message 'not optimum mode' and recommends 1280x1024 @ 60 Hz. Monitor is in 1280x1024, but supposedly at 0 Hz (!?)
It appears that the EDID is in error for this monitor?
Do not notice any problems with display, and so will probably not fool with xorg.conf.
This mail ends with the listing from get-edid (rather long), Xorg.0.log attached. TIA. Ch.Keller
Background Info:
In menu.lst there is xforcesvesa and vga=795 (this is supported by graphic card, hwinfo confirms this).
graphic card Matrox G550): 01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G550 AGP (rev 01)
xorg-server 2:1.7.6-2ubuntu7.3 .
Samsung Monitor Samsung 910t, specs: sync horizontal: 30-81, vertical: 56-75, optimum refresh 60, max 75.
xrandr -q:
Screen 0: minimum 640 x 480, current 1280 x 1024, maximum 1280 x 1024
default connected 1280x1024+0+0 0mm x 0mm
1280x1024 0.0*
1024x768 0.0
800x600 0.0
640x480 0.0
Following is the result of sudo get-edid|parse-edid:
chris@P4:~$ sudo get-edid|parse-edid
parse-edid: parse-edid version 2.0.0
get-edid: get-edid version 2.0.0
Performing real mode VBE call
Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0
Function supported
Call successful
VBE version 300
VBE string at 0xc5743 "Matrox Graphics Inc."
VBE/DDC service about to be called
Report DDC capabilities
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0
Function supported
Call successful
Monitor and video card combination does not support DDC1 transfers
Monitor and video card combination supports DDC2 transfers
0 seconds per 128 byte EDID block transfer
Screen is not blanked during DDC transfer
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call failed
The EDID data should not be trusted as the VBE call failed
EDID claims 32 more blocks left
*********** Something special has happened!
Please contact the author, Matthew Kern
E-mail: pyrophobicman@xxxxxxxxx
Please include full output from this program (especially that to stderr)
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call successful
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call failed
The EDID data should not be trusted as the VBE call failed
EDID claims 32 more blocks left
EDID blocks left is wrong.
Your EDID is probably invalid.
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call successful
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call failed
The EDID data should not be trusted as the VBE call failed
EDID claims 32 more blocks left
EDID blocks left is wrong.
Your EDID is probably invalid.
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call successful
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call failed
The EDID data should not be trusted as the VBE call failed
EDID claims 32 more blocks left
EDID blocks left is wrong.
Your EDID is probably invalid.
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call successful
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call failed
The EDID data should not be trusted as the VBE call failed
EDID claims 32 more blocks left
EDID blocks left is wrong.
Your EDID is probably invalid.
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call successful
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call failed
The EDID data should not be trusted as the VBE call failed
EDID claims 32 more blocks left
EDID blocks left is wrong.
Your EDID is probably invalid.
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call successful
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call failed
The EDID data should not be trusted as the VBE call failed
EDID claims 32 more blocks left
EDID blocks left is wrong.
Your EDID is probably invalid.
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call successful
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call failed
The EDID data should not be trusted as the VBE call failed
EDID claims 32 more blocks left
EDID blocks left is wrong.
Your EDID is probably invalid.
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call successful
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call failed
The EDID data should not be trusted as the VBE call failed
EDID claims 32 more blocks left
EDID blocks left is wrong.
Your EDID is probably invalid.
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call successful
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call failed
The EDID data should not be trusted as the VBE call failed
EDID claims 32 more blocks left
EDID blocks left is wrong.
Your EDID is probably invalid.
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call successful
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call failed
The EDID data should not be trusted as the VBE call failed
EDID claims 32 more blocks left
EDID blocks left is wrong.
Your EDID is probably invalid.
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call successful
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call failed
The EDID data should not be trusted as the VBE call failed
EDID claims 32 more blocks left
EDID blocks left is wrong.
Your EDID is probably invalid.
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call successful
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call failed
The EDID data should not be trusted as the VBE call failed
EDID claims 32 more blocks left
EDID blocks left is wrong.
Your EDID is probably invalid.
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call successful
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call failed
The EDID data should not be trusted as the VBE call failed
EDID claims 32 more blocks left
EDID blocks left is wrong.
Your EDID is probably invalid.
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call successful
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call failed
The EDID data should not be trusted as the VBE call failed
EDID claims 32 more blocks left
EDID blocks left is wrong.
Your EDID is probably invalid.
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call successful
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call failed
The EDID data should not be trusted as the VBE call failed
EDID claims 32 more blocks left
EDID blocks left is wrong.
Your EDID is probably invalid.
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call successful
Reading next EDID block
VBE/DDC service about to be called
Read EDID
Performing real mode VBE call
Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0
Function supported
Call failed
The EDID data should not be trusted as the VBE call failed
parse-edid: EDID checksum failed - data is corrupt. Continuing anyway.
EDID claims 32 more blocks left
EDID blocks left is wrong.
Your EDID is probably invalid.
parse-edid: first bytes don't match EDID version 1 header
parse-edid: do not trust output (if any).
# EDID version 14 revision 1
Section "Monitor"
Identifier "@BL:2d0f"
VendorName "@BL"
ModelName "@BL:2d0f"
# DPMS capabilities: Active off:yes Suspend:yes Standby:no
Mode "2346x593" # vfreq 8.870Hz, hfreq 27.968kHz
DotClock 122.890000
HTimings 2346 2410 2458 4394
VTimings 593 600 648 3153
EndMode
Mode "3840x1024" # vfreq 0.011Hz, hfreq 0.042kHz
DotClock 0.300000
HTimings 3840 3870 3951 7168
VTimings 1024 1024 1038 3896
EndMode
Mode "3840x1792" # vfreq 0.011Hz, hfreq 0.046kHz
DotClock 0.320000
HTimings 3840 3966 4065 6912
VTimings 1792 1796 1825 4179
EndMode
Mode "3840x1280" # vfreq 0.020Hz, hfreq 0.042kHz
DotClock 0.320000
HTimings 3840 3907 4027 7680
VTimings 1280 1283 1288 2120
EndMode
EndSection
+
+
+ ---
+ Architecture: i386
+ CurrentDmesg:
+ [ 18.199648] skge 0000:02:05.0: eth0: Link is up at 100 Mbps, full duplex, flow control both
+ [ 18.199907] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
+ [ 29.048015] eth0: no IPv6 routers present
+ DistroRelease: Ubuntu 10.10
+ InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
+ MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
+ Package: xserver-xorg-video-mga 1:1.4.11.dfsg-4build1
+ PackageArchitecture: i386
+ ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-28-generic-pae root=UUID=f5572ec1-c557-486e-82d2-65d19c79e5e0 ro splash vga=769 quiet splash
+ ProcEnviron:
+ LANG=en_US.utf8
+ SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 2.6.35-28.49-generic-pae 2.6.35.11
+ Tags: maverick maverick
+ Uname: Linux 2.6.35-28-generic-pae i686
+ UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
+ dmi.bios.date: 09/20/2004
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 080009
+ dmi.board.name: P4P800
+ dmi.board.vendor: ASUSTeK Computer Inc.
+ dmi.board.version: Rev 1.xx
+ dmi.chassis.asset.tag: Asset-1234567890
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Chassis Manufacture
+ dmi.chassis.version: Chassis Version
+ dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080009:bd09/20/2004:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASUSTeKComputerInc.:rnP4P800:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
+ dmi.product.name: To Be Filled By O.E.M.
+ dmi.product.version: To Be Filled By O.E.M.
+ dmi.sys.vendor: To Be Filled By O.E.M.
+ glxinfo: Error: [Errno 2] No such file or directory
+ system:
+ distro: Ubuntu
+ codename: maverick
+ architecture: i686
+ kernel: 2.6.35-28-generic-pae
** Attachment added: "BootDmesg.txt"
https://bugs.edge.launchpad.net/bugs/621756/+attachment/1949572/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-mga in Ubuntu.
https://bugs.launchpad.net/bugs/621756
Title:
Monitor Detection Problem in upgrade to 10.04.1
