Page 1 of 2 12 LastLast
Results 1 to 10 of 15

Thread: X1250 + fglrx + HDMI: X will not start

  1. #1
    Join Date
    Nov 2008
    Posts
    14

    Default X1250 + fglrx + HDMI: X will not start

    Hi,

    I've connected my IGP X1250 to my 1080p monitor using a hdmi-cable. After that, Ubuntu 8.04 does not start X any more, when using fglrx 8.10 (radeonhd and radeon 6.9.0 work). What happens is, that GDM gets started but the screen stays black and there are some kind of flickering. After a some seconds X starts in filesave mode.

    My xorg.conf looks like this:

    Code:
    Section "InputDevice"
    	Identifier	"Generic Keyboard"
    	Driver		"kbd"
    	Option		"XkbRules"	"xorg"
    	Option		"XkbModel"	"pc105"
    	Option		"XkbLayout"	"de"
    EndSection
    
    Section "InputDevice"
    	Identifier	"Configured Mouse"
    	Driver		"mouse"
    EndSection
    
    Section "Device"
    	Identifier	"Configured Video Device"
    	Boardname	"ATI X1250 IGP"
    	Busid		"PCI:1:5:0"
    	Driver		"fglrx"
    #	Screen	0
    	Vendorname	"ATI"
    EndSection
    
    Section "Monitor"
    	Identifier	"Configured Monitor"
    	Vendorname	"FujitsuSiemens
    	Modelname	"LCD Panel 1920x1080"
    	Horizsync	28.0-82.0
    	Vertrefresh	56.0 - 75.0
    	Gamma	1.0
    EndSection
    
    Section "Screen"
    	Identifier	"Default Screen"
    	Device		"Configured Video Device"
    	Monitor		"Configured Monitor"
    	Defaultdepth	24
    	SubSection "Display"
    		Depth	24
    		Modes		"1920x1080" "1680x1050" "1440x900"	"1280x720"	"1280x768"	"800x600"	"800x600"
    	EndSubSection
    	SubSection "Display"
    		Depth 16	
    		Modes		"1920x1080" "1680x1050" "1440x900"	"1280x720"	"1280x768"	"800x600"	"800x600"
    	EndSubSection
    EndSection
    
    Section "ServerLayout"
    	Identifier	"Default Layout"
      screen 0 "Default Screen" 0 0
    EndSection
    Section "Module"
    	Load		"dri"
    	Load		"v4l"
      Load    "ddc"
      Load    "freetype"
      Load    "glx"
    EndSection
    Section "ServerFlags"
    EndSection
    And here you'll find the Xorg.0.log http://uploaded.to/?id=m6d2zp
    There are no errors in the log. Since I need sound over HDMI and 3D, which will not work using radeonhd, I have to use fglrx.

  2. #2
    Join Date
    Aug 2007
    Posts
    6,632

    Default

    Use 1680x1050 as res - everything else is not native and does not work or at least looks bad.

  3. #3
    Join Date
    Nov 2008
    Posts
    14

    Default

    Sorry, but this is not true. RadeonHD and Radeon both are running at 1080p and it looks really greate! fglrx connected over an vga-cable was running at 1080p, too. After connecting with hdmi it was running 1080p, but with underscaling, which I could disable, and again, everything was great!

    But I had to use ranr to disable underscaling. Now, it does not work anymore with fgltx. But if running with 1080p the pixels are displayed 1:1 since my lcd display is native 1920x1080.

    Oh, and I tried 1680x1050, just to be sure there is nothing wrong with the resolution. X did not start, when connected thru hdmi and using fglrx.

  4. #4
    Join Date
    Aug 2007
    Posts
    6,632

    Default

    Well ddc in fglrx detected it as 1680x1050 native. I don't see a 7a7 model from Fujitsu Siemens, how is it called usually? Most easy way to have got always a picture is to remove all the forced modes from xorg.conf.

  5. #5
    Join Date
    Nov 2008
    Posts
    14

    Default

    Look some lines above in the log:

    (II) fglrx(0): Supported additional Video Mode:
    (II) fglrx(0): clock: 148.5 MHz Image Size: 509 x 286 mm
    (II) fglrx(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
    (II) fglrx(0): v_active: 1080 v_sync: 1089 v_sync_end 1095 v_blanking: 1125 v_border: 0
    (II) fglrx(0): Ranges: V min: 49 V max: 76 Hz, H min: 15 H max: 82 kHz, PixClock max 170 MHz

    There is also a monitor name: LSL 3230T. A new device build this year near 39th week.

  6. #6
    Join Date
    Nov 2008
    Posts
    14

    Default

    I can't believe that now even ati/radeon will not start X. Fortunately there is still the working radeonhd. But I would like to know if there are some hidden places, where Xorg stores some configurations apart from xorg.conf. Otherwise I can't imagine why x want start using fglrx and radeon.

    Any ideas?

  7. #7
    Join Date
    Nov 2008
    Posts
    14

    Default

    Ok, after installing Hardy's own fglrx driver, X is up and running. But underscalling is activated, so that I have to type xrandr --rate 50 into console to disable underscalling.

    Is there a way to set rate 50 somehow in xorg.conf?

  8. #8
    Join Date
    Sep 2006
    Posts
    353

    Default

    Quote Originally Posted by mactas View Post
    Hi,

    I've connected my IGP X1250 to my 1080p monitor using a hdmi-cable. After that, Ubuntu 8.04 does not start X any more, when using fglrx 8.10 (radeonhd and radeon 6.9.0 work). What happens is, that GDM gets started but the screen stays black and there are some kind of flickering. After a some seconds X starts in filesave mode.
    What you really need is the FULL EDID information.

    Run the command startx -- -logverbose 6 from the console. The EDID information should be in /var/log/Xorg.0.log (or /var/log/XFree86.0.log).

    Note that the -logverbose level 6 gives much more information than level 5 (it lists all the inbuilt X-server modes and why each is acceptable or not to the particular monitor/TV in question).

    The -logverbose level tops out at 7.

    On my amd64 box I get something like this:

    Code:
     --- EDID for Philips 170S (CRT-0) ---
    
     EDID Version                 : 1.3
     Manufacturer                 : PHL
     Monitor Name                 : Philips 170S
     Product ID                   : 2078
     32-bit Serial Number         : 693129
     Serial Number String         :  CF  693129
     Manufacture Date             : 2003, week 32
     DPMS Capabilities            : Standby Suspend Active Off
     Prefer first detailed timing : Yes
     Supports GTF                 : No
     Maximum Image Size           : 340mm x 270mm
     Valid HSync Range            : 30.0 kHz - 82.0 kHz
     Valid VRefresh Range         : 56 Hz - 76 Hz
     EDID maximum pixel clock     : 140.0 MHz
     
     Established Timings:
       640  x 480  @ 60 Hz
       640  x 480  @ 72 Hz
       640  x 480  @ 75 Hz
       800  x 600  @ 56 Hz
       800  x 600  @ 60 Hz
       800  x 600  @ 72 Hz
       800  x 600  @ 75 Hz
       1024 x 768  @ 60 Hz
       1024 x 768  @ 70 Hz
       1024 x 768  @ 75 Hz
       1280 x 1024 @ 75 Hz
     
     Standard Timings:
       1152 x 864  @ 70 Hz
       1152 x 864  @ 75 Hz
       1280 x 960  @ 60 Hz
     
     Detailed Timings:
       1280 x 1024 @ 60 Hz
         Pixel Clock      : 108.00 MHz
         HRes, HSyncStart : 1280, 1328
         HSyncEnd, HTotal : 1440, 1688
         VRes, VSyncStart : 1024, 1025
         VSyncEnd, VTotal : 1028, 1066
         H/V Polarity     : +/+
    Code:
     Validating Mode "1280x1024":
       1280 x 1024 @ 60 Hz
       Mode Source: EDID
         Pixel Clock      : 108.00 MHz
         HRes, HSyncStart : 1280, 1328
         HSyncEnd, HTotal : 1440, 1688
         VRes, VSyncStart : 1024, 1025
         VSyncEnd, VTotal : 1028, 1066
         H/V Polarity     : +/+
       Mode is valid.
     
     Validating Mode "1280x960":
       1280 x 960 @ 60 Hz
       Mode Source: EDID
         Pixel Clock      : 108.00 MHz
         HRes, HSyncStart : 1280, 1376
         HSyncEnd, HTotal : 1488, 1800
         VRes, VSyncStart :  960,  961
         VSyncEnd, VTotal :  964, 1000
         H/V Polarity     : +/+
       Mode is valid.
     
     Validating Mode "1152x864":
       1152 x 864 @ 70 Hz
       Mode Source: EDID
         Pixel Clock      : 96.76 MHz
         HRes, HSyncStart : 1152, 1224
         HSyncEnd, HTotal : 1344, 1536
         VRes, VSyncStart :  864,  865
         VSyncEnd, VTotal :  868,  900
         H/V Polarity     : -/+
       Mode is valid.
    
       AND MUCH MORE.
    Last edited by Jade; 11-10-2008 at 05:56 PM.

  9. #9
    Join Date
    Nov 2008
    Posts
    14

    Default

    I could finally fix it by using an older fglrx (8.8). After migrating to ubuntu 8.10 i compiled radeonhd with dri enabled and thats enough.

    But for some reasons the ati/radeon driver want start saying it could not find /dev/dir/card0. Don't know how to create this dev. radeonhd works.

  10. #10
    Join Date
    Sep 2006
    Posts
    353

    Default

    Quote Originally Posted by mactas View Post
    I could finally fix it by using an older fglrx (8.8).
    The EDID information would still be useful.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •