Upon upgrading from Karmic to Lucid Beta1, no mode gets set for my monitor. Although I successfully reach the login screen (I can hear the GDM ready sound), my monitor just flashes its test-pattern as if disconnected. If during the boot I hold SHIFT to enter the GRUB2 menu and boot with the "nomodeset" option, my monitor and video card work fine. I'm using the free "radeon" driver, not the proprietary ATI driver.
I'll test with another monitor to see if this issue is always present, or if it's unique to this card+monitory combination. My Samsung 305T is a less common resolution (2560x1600), so that might be the issue.
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: jderose 2070 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfb9f8000 irq 22'
Mixer name : 'Analog Devices AD1989B'
Components : 'HDA:11d4989b,10438372,00100300'
Controls : 48
Simple ctrls : 27
Card1.Amixer.info:
Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbbfc000 irq 34'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100100'
Controls : 4
Simple ctrls : 1
Card1.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [off]
Date: Sat Mar 20 15:41:56 2010
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=b899b5f2-13b2-43e2-af7f-5606ca403ced
MachineType: System manufacturer System Product Name
Package: linux-image-2.6.32-16-generic 2.6.32-16.25
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-16-generic root=/dev/mapper/main-root ro quiet splash nomodeset
ProcEnviron:
PATH=(custom, user)
LANG=en_US.utf8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
Regression: Yes
RelatedPackageVersions: linux-firmware 1.33
Reproducible: Yes
RfKill:
SourcePackage: linux
TestedUpstream: No
Uname: Linux 2.6.32-16-generic x86_64
dmi.bios.date: 05/18/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0711
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P6T WS PRO
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.:bvr0711:bd05/18/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TWSPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
KMS works fine with my other monitor, a Samsung 245BW (1920x1200). So this is an issue that for me only occurs with my Samsung 305T. I attached my Xorg.0.log, and here's the output of `xrandr --verbose` when using my 305T monitor (note I had to boot with "nomodeset"):
Screen 0: minimum 320 x 200, current 2560 x 1600, maximum 2560 x 2560
DVI-1 connected 2560x1600+0+0 (0x53) normal (normal left inverted right x axis y axis) 646mm x 406mm
Identifier: 0x51
Timestamp: 20754
Subpixel: horizontal rgb
Clones:
CRTC: 0
CRTCs: 0 1
Transform: 1.000000 0.000000 0.000000
filter:
EDID:
00fffffffffff
0e13010380402
1350540000000
010101010101b
3600869621000
3020360086962
796e634d61737
0048565553343
dvi_monitor_type: auto
scaler: full
coherent_mode: 1 (0x00000001) range: (0,1)
load_detection: 1 (0x00000001) range: (0,1)
2560x1600 (0x53) 268.0MHz +HSync -VSync *current
h: width 2560 start 2608 end 2640 total 2720 skew 0 clock 98.5KHz
v: height 1600 start 1603 end 1609 total 1646 clock 59.9Hz
1280x800 (0x54) 71.0MHz +HSync -VSync
h: width 1280 start 1328 end 1360 total 1440 skew 0 clock 49.3KHz
v: height 800 start 803 end 809 total 823 clock 59.9Hz
DVI-0 disconnected (normal left inverted right x axis y axis)
Identifier: 0x52
Timestamp: 20754
Subpixel: no subpixels
Clones:
CRTCs: 0 1
Transform: 1.000000 0.000000 0.000000
filter:
dvi_monitor_type: auto
scaler: full
coherent_mode: 1 (0x00000001) range: (0,1)
load_detection: 1 (0x00000001) range: (0,1)