Announcement

Collapse
No announcement yet.

Drivers for AMD (ATI) Radeon HD 5670 in Ubuntu 12.04 LTS (Precise Pangolin).

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Drivers for AMD (ATI) Radeon HD 5670 in Ubuntu 12.04 LTS (Precise Pangolin).

    Hello,

    I've got problems with my AMD (ATI) Radeon HD 5670 in Ubuntu 12.04 LTS (Precise Pangolin).

    I had 2GB of RAM (DDR2, PC6400, 800MHz), I added another 2GB so now I have 4GB (2x2GB) and I'm not able to use fglrx drivers.

    I've applied patch for new kernel http://phoronix.com/forums/showthrea...86-32-bit-arch and installed latest Catalyst 12.4 drivers succesfully without any errors according to WIKI pages http://wiki.cchtml.com/index.php/Ubu...TI.27s_site.29 but unfortunately after system restart I get black or violet screen and I'm not even able to switch to other virtual console with Ctrl+Alt+F1...F6. When I remove 2GB (only 2GB left) system starts normally and everything works fine.

    It's not RAM issue, because I've got Windows 7 installed as well and it works fine, 4GB of memory are visible in the system. Besides when I installed Backtrack 5 which is based on Ubuntu 10.04 LTS, 12.4 catalyst drivers were working correctly with 4GB RAM inserted.


    All installations were made on fresh and updated system. After I install drivers and execute
    Code:
    sudo amdconfig --initial -f
    fglrxinfo output and xorg.conf (before this command there was no /etc/X11/xorg.conf) are as follows (right after installation and before system restart):
    Code:
    przemek@pc:~/catalyst12.4$ sudo amdconfig --initial -f
    Uninitialised file found, configuring.
    Using /etc/X11/xorg.conf
    Saving back-up to /etc/X11/xorg.conf.original-1
    przemek@pc:~/catalyst12.4$ cat /etc/X11/xorg.conf
    Section "ServerLayout"
        Identifier     "aticonfig Layout"
        Screen      0  "aticonfig-Screen[0]-0" 0 0
    EndSection
    
    Section "Module"
    EndSection
    
    Section "Monitor"
        Identifier   "aticonfig-Monitor[0]-0"
        Option        "VendorName" "ATI Proprietary Driver"
        Option        "ModelName" "Generic Autodetecting Monitor"
        Option        "DPMS" "true"
    EndSection
    
    Section "Device"
        Identifier  "aticonfig-Device[0]-0"
        Driver      "fglrx"
        BusID       "PCI:1:0:0"
    EndSection
    
    Section "Screen"
        Identifier "aticonfig-Screen[0]-0"
        Device     "aticonfig-Device[0]-0"
        Monitor    "aticonfig-Monitor[0]-0"
        DefaultDepth     24
        SubSection "Display"
            Viewport   0 0
            Depth     24
        EndSubSection
    EndSection
    
    przemek@pc:~/catalyst12.4$ fglrxinfo
    display: :0  screen: 0
    OpenGL vendor string: VMware, Inc.
    OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 0x300)
    OpenGL version string: 1.4 (2.1 Mesa 8.0.2)
    
    przemek@pc:~/catalyst12.4$
    I moved xorg.conf file to see if it causes problems, but after
    Code:
    sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.disabled
    the problem was still present- black or violet screen.

    After xorg.conf restoration
    Code:
    sudo mv /etc/X11/xorg.conf.disabled /etc/X11/xorg.conf
    I tried to tune it according to wiki
    Code:
    sudo amdconfig --tls=0
    
    sudo amdconfig --acpi-services=off
    but without success...

    Blacklisting radeon modules also did not help...
    Code:
    echo "blacklist radeon" | sudo tee -a /etc/modprobe.d/blacklist-radeon.conf
    sudo depmod -a


    Ofcourse when I remove 2GB RAM and leave 2GB- system boots normally and fglrxinfo looks very good:
    Code:
    przemek@pc:~$ fglrxinfo
    display: :0  screen: 0
    OpenGL vendor string: Advanced Micro Devices, Inc.
    OpenGL renderer string: ATI Radeon HD 5670
    OpenGL version string: 4.2.11631 Compatibility Profile Context
    
    przemek@pc:~$ fgl_glxgears
    Using GLX_SGIX_pbuffer
    3178 frames in 5.0 seconds = 635.600 FPS
    4172 frames in 5.0 seconds = 834.400 FPS
    4163 frames in 5.0 seconds = 832.600 FPS
    4153 frames in 5.0 seconds = 830.600 FPS
    4165 frames in 5.0 seconds = 833.000 FPS
    4152 frames in 5.0 seconds = 830.400 FPS
    4141 frames in 5.0 seconds = 828.200 FPS
    4160 frames in 5.0 seconds = 832.000 FPS
    4162 frames in 5.0 seconds = 832.400 FPS
    ^C
    przemek@pc:~$
    Problem is present only when 4GB are inserted... I borrowed 1GB of RAM and tested configuration with 3GB and it was working fine!

    Used kernel supports 4GB of RAM (visible after free -m when fglrx drivers are not installed)
    Code:
    przemek@pc:~$ uname -r
    3.2.0-25-generic-pae
    przemek@pc:~$
    The same situation is with fglrx drivers from repos...


    What kind of logs can I check? Can anyone help me with this issue?

    Looking forward,
    Przemek.

    P.S. I tried also 12.6 Beta version of catalyst drivers, mentioned patch was not need to successfully generate packages, but after installation situation is still the same- black or violet screen when 4GB are inserted...

  • #2
    With the new ram inserted, try to startx and check /var/log/Xorg.0.log to see what the problem is.
    We would need to see the log, to be able to suggest anything.

    Comment


    • #3
      Hello,

      when X server starts I get violet screen with Ubuntu logo and system freezes- I can not switch to other virtual consoles with Ctrl+Alt+F1...F6.

      So what I did was: I inserted 4GB of RAM, started the system which got stuck (screen with logo), restarted computer, entered recovery mode (in GRUB there i always recovery mode entry below normal entry), entered root console and copied the content of /var/log.Xorg.0.log. The result can be found here http://ubuntuone.com/1aV8Rqz8KGybj4Be25Cem9

      Do you see any errors? What other logs can I check (I wanted to check /var/log/messages as well but such file does not exist)???

      Looking forward,
      Przemek.
      Last edited by przemnet; 06-28-2012, 02:13 PM.

      Comment


      • #4
        Xorg.0.log SECOND PART

        Code:
        [     4.890] (II) fglrx(0): Supported established timings:
        [     4.890] (II) fglrx(0): 720x400@70Hz
        [     4.890] (II) fglrx(0): 640x480@60Hz
        [     4.890] (II) fglrx(0): 640x480@67Hz
        [     4.890] (II) fglrx(0): 640x480@72Hz
        [     4.890] (II) fglrx(0): 640x480@75Hz
        [     4.890] (II) fglrx(0): 800x600@56Hz
        [     4.890] (II) fglrx(0): 800x600@60Hz
        [     4.890] (II) fglrx(0): 800x600@72Hz
        [     4.890] (II) fglrx(0): 800x600@75Hz
        [     4.890] (II) fglrx(0): 832x624@75Hz
        [     4.890] (II) fglrx(0): 1024x768@60Hz
        [     4.890] (II) fglrx(0): 1024x768@70Hz
        [     4.890] (II) fglrx(0): 1024x768@75Hz
        [     4.890] (II) fglrx(0): 1280x1024@75Hz
        [     4.890] (II) fglrx(0): 1152x864@75Hz
        [     4.890] (II) fglrx(0): Manufacturer's mask: 0
        [     4.890] (II) fglrx(0): Supported standard timings:
        [     4.890] (II) fglrx(0): #0: hsize: 1280  vsize 1024  refresh: 60  vid: 32897
        [     4.890] (II) fglrx(0): #1: hsize: 1280  vsize 960  refresh: 60  vid: 16513
        [     4.890] (II) fglrx(0): #2: hsize: 1152  vsize 864  refresh: 75  vid: 20337
        [     4.890] (II) fglrx(0): Supported detailed timing:
        [     4.890] (II) fglrx(0): clock: 108.0 MHz   Image Size:  338 x 270 mm
        [     4.891] (II) fglrx(0): h_active: 1280  h_sync: 1328  h_sync_end 1440 h_blank_end 1688 h_border: 0
        [     4.891] (II) fglrx(0): v_active: 1024  v_sync: 1025  v_sync_end 1028 v_blanking: 1066 v_border: 0
        [     4.891] (II) fglrx(0): Ranges: V min: 56 V max: 75 Hz, H min: 30 H max: 81 kHz, PixClock max 145 MHz
        [     4.891] (II) fglrx(0): Monitor name: SyncMaster
        [     4.891] (II) fglrx(0): Serial No: H9NY902609
        [     4.891] (II) fglrx(0): EDID (in hex):
        [     4.891] (II) fglrx(0): 	00ffffffffffff004c2d970137314544
        [     4.891] (II) fglrx(0): 	250f010380221b782aee95a3544c9926
        [     4.891] (II) fglrx(0): 	0f5054bfef8081808140714f01010101
        [     4.891] (II) fglrx(0): 	010101010101302a009851002a403070
        [     4.891] (II) fglrx(0): 	1300520e1100001e000000fd00384b1e
        [     4.891] (II) fglrx(0): 	510e000a202020202020000000fc0053
        [     4.891] (II) fglrx(0): 	796e634d61737465720a2020000000ff
        [     4.891] (II) fglrx(0): 	0048394e593930323630390a202000cb
        [     4.891] (II) fglrx(0): End of Display0 EDID data --------------------
        [     4.892] (II) fglrx(0): EDID for output DFP1
        [     4.892] (II) fglrx(0): EDID for output DFP2
        [     4.892] (II) fglrx(0): Manufacturer: SAM  Model: 197  Serial#: 1145385271
        [     4.892] (II) fglrx(0): Year: 2005  Week: 37
        [     4.892] (II) fglrx(0): EDID Version: 1.3
        [     4.892] (II) fglrx(0): Digital Display Input
        [     4.892] (II) fglrx(0): Max Image Size [cm]: horiz.: 34  vert.: 27
        [     4.892] (II) fglrx(0): Gamma: 2.20
        [     4.892] (II) fglrx(0): DPMS capabilities: Off
        [     4.892] (II) fglrx(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4 
        [     4.892] (II) fglrx(0): First detailed timing is preferred mode
        [     4.892] (II) fglrx(0): redX: 0.640 redY: 0.330   greenX: 0.300 greenY: 0.600
        [     4.892] (II) fglrx(0): blueX: 0.150 blueY: 0.060   whiteX: 0.313 whiteY: 0.329
        [     4.892] (II) fglrx(0): Supported established timings:
        [     4.892] (II) fglrx(0): 720x400@70Hz
        [     4.892] (II) fglrx(0): 640x480@60Hz
        [     4.892] (II) fglrx(0): 640x480@67Hz
        [     4.892] (II) fglrx(0): 640x480@72Hz
        [     4.892] (II) fglrx(0): 640x480@75Hz
        [     4.892] (II) fglrx(0): 800x600@56Hz
        [     4.892] (II) fglrx(0): 800x600@60Hz
        [     4.892] (II) fglrx(0): 800x600@72Hz
        [     4.892] (II) fglrx(0): 800x600@75Hz
        [     4.892] (II) fglrx(0): 832x624@75Hz
        [     4.892] (II) fglrx(0): 1024x768@60Hz
        [     4.892] (II) fglrx(0): 1024x768@70Hz
        [     4.892] (II) fglrx(0): 1024x768@75Hz
        [     4.892] (II) fglrx(0): 1280x1024@75Hz
        [     4.892] (II) fglrx(0): 1152x864@75Hz
        [     4.892] (II) fglrx(0): Manufacturer's mask: 0
        [     4.892] (II) fglrx(0): Supported standard timings:
        [     4.892] (II) fglrx(0): #0: hsize: 1280  vsize 1024  refresh: 60  vid: 32897
        [     4.892] (II) fglrx(0): #1: hsize: 1280  vsize 960  refresh: 60  vid: 16513
        [     4.892] (II) fglrx(0): #2: hsize: 1152  vsize 864  refresh: 75  vid: 20337
        [     4.892] (II) fglrx(0): Supported detailed timing:
        [     4.892] (II) fglrx(0): clock: 108.0 MHz   Image Size:  338 x 270 mm
        [     4.892] (II) fglrx(0): h_active: 1280  h_sync: 1328  h_sync_end 1440 h_blank_end 1688 h_border: 0
        [     4.893] (II) fglrx(0): v_active: 1024  v_sync: 1025  v_sync_end 1028 v_blanking: 1066 v_border: 0
        [     4.893] (II) fglrx(0): Ranges: V min: 56 V max: 75 Hz, H min: 30 H max: 81 kHz, PixClock max 145 MHz
        [     4.893] (II) fglrx(0): Monitor name: SyncMaster
        [     4.893] (II) fglrx(0): Serial No: H9NY902609
        [     4.893] (II) fglrx(0): EDID (in hex):
        [     4.893] (II) fglrx(0): 	00ffffffffffff004c2d970137314544
        [     4.893] (II) fglrx(0): 	250f010380221b782aee95a3544c9926
        [     4.893] (II) fglrx(0): 	0f5054bfef8081808140714f01010101
        [     4.893] (II) fglrx(0): 	010101010101302a009851002a403070
        [     4.893] (II) fglrx(0): 	1300520e1100001e000000fd00384b1e
        [     4.893] (II) fglrx(0): 	510e000a202020202020000000fc0053
        [     4.893] (II) fglrx(0): 	796e634d61737465720a2020000000ff
        [     4.893] (II) fglrx(0): 	0048394e593930323630390a202000cb
        [     4.893] (II) fglrx(0): Printing probed modes for output DFP2
        [     4.893] (II) fglrx(0): Modeline "1280x1024"x60.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
        [     4.893] (II) fglrx(0): Modeline "1280x1024"x75.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
        [     4.893] (II) fglrx(0): Modeline "1280x960"x60.0  108.00  1280 1376 1488 1800  960 961 964 1000 +hsync +vsync (60.0 kHz)
        [     4.893] (II) fglrx(0): Modeline "1152x864"x75.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz)
        [     4.893] (II) fglrx(0): Modeline "1152x864"x60.0  108.00  1152 1328 1440 1688  864 1025 1028 1066 +hsync +vsync (64.0 kHz)
        [     4.893] (II) fglrx(0): Modeline "1280x768"x60.0  108.00  1280 1376 1488 1800  768 961 964 1000 +hsync +vsync (60.0 kHz)
        [     4.893] (II) fglrx(0): Modeline "1280x720"x60.0  108.00  1280 1376 1488 1800  720 961 964 1000 +hsync +vsync (60.0 kHz)
        [     4.893] (II) fglrx(0): Modeline "1024x768"x75.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz)
        [     4.893] (II) fglrx(0): Modeline "1024x768"x70.0   75.00  1024 1048 1184 1328  768 771 777 806 -hsync -vsync (56.5 kHz)
        [     4.893] (II) fglrx(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz)
        [     4.893] (II) fglrx(0): Modeline "800x600"x72.0   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync (48.1 kHz)
        [     4.893] (II) fglrx(0): Modeline "800x600"x75.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz)
        [     4.893] (II) fglrx(0): Modeline "800x600"x60.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz)
        [     4.893] (II) fglrx(0): Modeline "800x600"x56.0   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz)
        [     4.893] (II) fglrx(0): Modeline "640x480"x75.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz)
        [     4.893] (II) fglrx(0): Modeline "640x480"x72.0   31.50  640 656 696 832  480 481 484 520 -hsync -vsync (37.9 kHz)
        [     4.893] (II) fglrx(0): Modeline "640x480"x67.0   27.28  640 664 728 816  480 481 484 499 -hsync +vsync (33.4 kHz)
        [     4.893] (II) fglrx(0): Modeline "640x480"x60.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz)
        [     4.893] (II) fglrx(0): EDID for output CRT1
        [     4.893] (II) fglrx(0): EDID for output CRT2
        [     4.893] (II) fglrx(0): Output DFP1 disconnected
        [     4.893] (II) fglrx(0): Output DFP2 connected
        [     4.893] (II) fglrx(0): Output CRT1 disconnected
        [     4.893] (II) fglrx(0): Output CRT2 disconnected
        [     4.893] (II) fglrx(0): Using exact sizes for initial modes
        [     4.893] (II) fglrx(0): Output DFP2 using initial mode 1280x1024
        [     4.893] (II) fglrx(0): DPI set to (96, 96)
        [     4.893] (II) fglrx(0): Eyefinity capable adapter detected.
        [     4.893] (II) fglrx(0): Adapter ATI Radeon HD 5670 has 4 configurable heads and 1 displays connected.
        [     4.893] (==) fglrx(0):  PseudoColor visuals disabled
        [     4.893] (II) Loading sub module "ramdac"
        [     4.893] (II) LoadModule: "ramdac"
        [     4.893] (II) Module "ramdac" already built-in
        [     4.894] (==) fglrx(0): NoDRI = NO
        [     4.894] (==) fglrx(0): Capabilities: 0x00000000
        [     4.894] (==) fglrx(0): CapabilitiesEx: 0x00000000
        [     4.894] (==) fglrx(0): OpenGL ClientDriverName: "fglrx_dri.so"
        [     4.894] (==) fglrx(0): UseFastTLS=0
        [     4.894] (--) Depth 24 pixmap format is 32 bpp
        [     4.894] (II) Loading extension ATIFGLRXDRI
        [     4.894] (II) fglrx(0): doing swlDriScreenInit
        [     4.894] (II) fglrx(0): swlDriScreenInit for fglrx driver
        [     4.894] ukiDynamicMajor: found major device number 250
        [     4.894] ukiDynamicMajor: found major device number 250
        [     4.895] ukiDynamicMajor: found major device number 250
        [     4.895] ukiOpenByBusid: Searching for BusID PCI:1:0:0
        [     4.895] ukiOpenDevice: node name is /dev/ati/card0
        [     4.895] ukiOpenDevice: open result is 17, (OK)
        [     4.895] ukiOpenByBusid: ukiOpenMinor returns 17
        [     4.895] ukiOpenByBusid: ukiGetBusid reports PCI:1:0:0
        [     4.895] (II) fglrx(0): [uki] DRM interface version 1.0
        [     4.895] (II) fglrx(0): [uki] created "fglrx" driver at busid "PCI:1:0:0"
        [     4.895] (II) fglrx(0): [uki] added 8192 byte SAREA at 0x2000
        [     4.895] (II) fglrx(0): [uki] mapped SAREA 0x2000 to 0xb6f20000
        [     4.895] (II) fglrx(0): [uki] framebuffer handle = 0x3000
        [     4.895] (II) fglrx(0): [uki] added 1 reserved context for kernel
        [     4.895] (II) fglrx(0): swlDriScreenInit done
        [     4.895] (II) fglrx(0): Kernel Module Version Information:
        [     4.895] (II) fglrx(0):     Name: fglrx
        [     4.895] (II) fglrx(0):     Version: 8.96.4
        [     4.895] (II) fglrx(0):     Date: Apr  5 2012
        [     4.895] (II) fglrx(0):     Desc: ATI FireGL DRM kernel module
        [     4.895] (II) fglrx(0): Kernel Module version matches driver.
        [     4.895] (II) fglrx(0): Kernel Module Build Time Information:
        [     4.895] (II) fglrx(0):     Build-Kernel UTS_RELEASE:        3.2.0-25-generic-pae
        [     4.895] (II) fglrx(0):     Build-Kernel MODVERSIONS:        no
        [     4.895] (II) fglrx(0):     Build-Kernel __SMP__:            yes
        [     4.895] (II) fglrx(0):     Build-Kernel PAGE_SIZE:          0x1000
        [     4.895] (II) fglrx(0): [uki] register handle = 0x00004000
        Do you see any errors? What other logs can I check (I wanted to check /var/log/messages as well but such file does not exist)???

        Comment


        • #5
          Originally posted by przemnet View Post
          Hello,

          when X server starts I get violet screen with Ubuntu logo and system freezes- I can not switch to other virtual consoles with Ctrl+Alt+F1...F6.

          So what I did was: I inserted 4GB of RAM, started the system which got stuck (screen with logo), restarted computer, entered recovery mode (in GRUB there i always recovery mode entry below normal entry), entered root console and copied the content of /var/log.Xorg.0.log. The result can be found here http://ubuntuone.com/1aV8Rqz8KGybj4Be25Cem9

          Do you see any errors? What other logs can I check (I wanted to check /var/log/messages as well but such file does not exist)???

          Looking forward,
          Przemek.
          By any chance is the install of ubuntu 12.04 lts a 32-bit install or 64-bit install? The 32-bit installs might be a problem.


          Also, on ubuntu the logs you want are as follows:
          /var/log/syslog
          /var/log/kern.log
          /var/log/Xorg.0.log

          Comment


          • #6
            Hello Experts,

            sory for late reply, but finally I managed to collect logs.

            Yes, I am using 32-bit version of Ubuntu.

            I've installed the newest kernel avalible in repos (3.2.0-26-generic-pae), uninstalled old and installed the newest version of Catalyst drivers (version 12.6- this time I did not have to install the patch http://phoronix.com/forums/showthrea...86-32-bit-arch) but unfortunatelly situation is still the same- violet screen...

            Here http://ubuntuone.com/1aFILwwVLV9f6jMqUdjDTN you can find logs (/var/log folder) that were collected via root console in recovery mode (still can not switch to other consoles with Ctrl+Alt+F1...F6):
            - in folder 4GB_12_4 there are logs collected when 4GB are inserted with 12.4 Catalyst drivers installed
            - in folder 4GB_NO_12_4_fglrx there are logs when 4GB are inserted and 12.4 Catalyst drivers were removed
            - in folder 4GB_12_6 there are logs collected when 4GB are inserted with 12.6 Catalyst drivers installed

            Could you have a look on provided logs- I'll appreciate your advices.

            Looking forward,
            Przemek.

            Comment


            • #7
              Originally posted by przemnet View Post
              Could you have a look on provided logs- I'll appreciate your advices.
              I check this logs, but can't find any error messages or warnings related to your problem. I recommend you register bugreport on fglrx bugtracker (with attached report generated by /usr/share/fglrx/atigetsysteminfo.sh utility) and/or contact with tech. support. If you need immediate solution, that probably will be switch from x86 to x86_64 Ubuntu installation.

              Comment


              • #8
                Hello,

                thanks for advices. I filed a bug: http://ati.cchtml.com/show_bug.cgi?id=560 so lets wait what will happen next.

                Unfortunatelly I can not install 64-bit version of Ubuntu 12.04, because I can not start Live CD- I get kernel panic errors...

                Looking forward,
                Przemek.

                Comment


                • #9
                  According to your atisysteminfo-report.txt, motherboard model is GA-MA69G-S3H, and BIOS version is F4a. Latest BIOS for this motherboard is F8E:
                  http://www.gigabyte.com/products/pro...2554&dl=1#bios
                  May you please try update BIOS, as John Bridgman recommends?

                  Comment


                  • #10
                    Funny you should post that. Foolishly swayed by russianneuromancer I tried it again, ubuntu 12.04 x64 + fglrx.

                    I installed server and upgraded it to desktop. On booting, I had the same problem with the black screen, which would eventually vanish, just having hidden the boot messages.
                    Not really a problem so far, only it also does not shutdown cleanly, which means it scans the filesystem on boot. That takes a while, and meanwhile you get nothing but that faintly dark violet screen to look at. I suggest you try booting in recovery mode where the boot process is in textmode and you can see what's going on. It may be just some error prompt or a kernel panic or whatever but you can't see it since ubuntu hides it.

                    All in all I found fglrx to be almost as bad as I expected, and switched back to the oss driver, which is quite difficult btw.

                    Comment


                    • #11
                      Originally posted by barkas View Post
                      Foolishly swayed by russianneuromancer
                      Asking for XBMC crash dump is not "fooling".
                      Originally posted by barkas View Post
                      I had the same problem with the black screen
                      "Same problem with the black screen" doesn't mean same "problem with the motherboard" this topic about. At first I doesn't sure you follow installation guide.
                      Originally posted by barkas View Post
                      switched back to the oss driver, which is quite difficult btw.
                      What exactly difficult in removing fglrx package for someone who know about recovery mode?
                      Last edited by RussianNeuroMancer; 07-08-2012, 01:02 PM.

                      Comment


                      • #12
                        Originally posted by RussianNeuroMancer View Post
                        Asking for XBMC crash dump is not "fooling".
                        "Same problem with the black screen" doesn't mean same "problem with the motherboard" this topic about. At first I doesn't sure you follow installation guide.
                        What exactly difficult in removing fglrx package for someone who know about recovery mode?
                        I earn my money partly with linux, so, not that difficult, if you know where to look.
                        But it sure is strange that installing fglrx overwrites stuff of mesa and X and you have to repair that damage afterward.

                        You asked for a crashdump but I have none, so I decided to give it a try again. Sorry I can't send you my beautiful kernel panics while shutting down.

                        There is an installation guide? How nice. And here I thought you open jockey and click on "install" . Worked fine, too, except that it sometimes has to be reset by switching to console and back to graphics to get rid of a completely garbled screen and that it crashes on shutdown.

                        Comment


                        • #13
                          Originally posted by barkas View Post
                          But it sure is strange that installing fglrx overwrites stuff of mesa and X and you have to repair that damage afterward.
                          fglrx Ubuntu packages uses alternatives system.
                          Originally posted by barkas View Post
                          You asked for a crashdump but I have none, so I decided to give it a try again. Sorry I can't send you my beautiful kernel panics while shutting down.
                          There is an installation guide? How nice. And here I thought you open jockey and click on "install" . Worked fine, too, except that it sometimes has to be reset by switching to console and back to graphics to get rid of a completely garbled screen and that it crashes on shutdown.
                          I also asking you check bugs with 12.6 release, not 12.4 Ubuntu stock driver (because there is a lot of kernel module crash, ASIC hang and graphics corruption fixes in 12.6 for wide range of hardware and software). If bugs still reproducibly with 12.6 release - posting bugs on forum doesn't get it magically fixed. You need to at least register it in bugtracker, with atigetsysteminfo.sh report and step-by-step how-to-reproduce-it guide, or contact with tech. support. And, just in case, don't forget to update BIOS too

                          Comment


                          • #14
                            Next month you'll tell me to update to 12.7 because 12.6 is crap.

                            I'm not ATIs unpaid beta tester. The GPU in question has been supported for years, if they haven't managed to produce a working driver yet, I don't believe one additional update will substantially change things. Next driver update for me may be with ubuntu 12.10. Certainly not sooner.

                            EDIT: I hope you know that the cchtml bugtracker is unofficial and not necessarily monitored by ati staff, as was made clear when the fglrx + gnome3 bugs were posted there. Additionally most bugs with that driver are of the trivial to find kind and should have been caught by inhouse beta testing, if there is such a thing.
                            Excuse me if I'm pissed off but I've been having those problems and the selfsame argument for going on 15 years now, first with the windows driver, now with windows and, worse, linux.
                            Last edited by barkas; 07-08-2012, 02:45 PM.

                            Comment


                            • #15
                              Originally posted by barkas View Post
                              Next month you'll tell me to update to 12.7 because 12.6 is crap.
                              I just tell you what I actually read and hear from people about 12.6 release.
                              Originally posted by barkas View Post
                              I'm not ATIs unpaid beta tester. The GPU in question has been supported for years, if they haven't managed to produce a working driver yet
                              Doesn't work in your setup != doesn't work anywhere.
                              Originally posted by barkas View Post
                              EDIT: I hope you know that the cchtml bugtracker is unofficial and not necessarily monitored by ati staff
                              Because of that I mention tech. support.
                              Originally posted by barkas View Post
                              as was made clear when the fglrx + gnome3 bugs were posted there.
                              Gnome Shell topic was already discussed.
                              Originally posted by barkas View Post
                              Additionally most bugs with that driver are of the trivial to find kind and should have been caught by inhouse beta testing, if there is such a thing.
                              For example you talk about some "trivial bugs" in this thread: screen is black on boot, kernel panic at shutdown, graphic corruption after VT switch, but I doesn't have this bugs (for obvious reason - different hardware). What make this bugs "trivial" if nobody properly report it?
                              Or topic starter issue, that probably related to motherboard BIOS bug (or even maybe hardware failure as Kep P. assume) but not fglrx bug.
                              Originally posted by barkas View Post
                              Excuse me if I'm pissed off but I've been having those problems and the selfsame argument for going on 15 years now, first with the windows driver, now with windows and, worse, linux.
                              And you doesn't report bugs to vendor for all 15 years? If you doesn't report bugs, don't be surprised is your bugs doesn't get fixed. There is no AMD telepathists department.
                              Last edited by RussianNeuroMancer; 07-08-2012, 03:20 PM.

                              Comment

                              Working...
                              X