Visit Jeremy's Blog.
Go Back > Forums > Linux Forums > Linux - Newbie
User Name
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!


  Search this Thread
Old 02-11-2008, 02:56 PM   #1
LQ Newbie
Registered: Feb 2008
Posts: 1

Rep: Reputation: 0
OpenSUSE 10.3 Isues

Hey everyone this is my first post and I hope you guys can help me out.

For a long time i've wanted to install opensuse 10.3 on my machine and i finally got the internet connection to download it. I downloaded the DVD and installed KDE version and everything was fine but when i booted into OpenSUSE the monitor just went idle ( led turned yellow). If i turned monitor off then on it would say "no input". I tried using OpenSUSE live CD (KDE) and same thing happens. With the installed version i could boot into failsafe but that doesn't really help with anything. I installed Ubuntu on the machine and it worked fine.

Please help me !

Below i've included my DxDiag file

System Information
Time of this report: 2/11/2008, 12:53:13
Machine name: YOUR-5FFB587E79
Operating System: Windows XP Home Edition (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_gdr.050301-1519)
Language: English (Regional Setting: English)
System Manufacturer: Gateway
System Model: T6410
BIOS: Phoenix - Award BIOS v6.00PG
Processor: AMD Athlon(tm) 64 Processor 3200+, MMX, 3DNow, ~2.2GHz
Memory: 382MB RAM
Page File: 322MB used, 2019MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.2600.2180 32bit Unicode
Display Devices
Card name: ATI RADEON Xpress 200 Series
Manufacturer: ATI Technologies Inc.
Chip type: ATI RADEON XPRESS 200 Series (0x5954)
DAC type: Internal DAC(400MHz)
Device Key: Enum\PCI\VEN_1002&DEV_5954&SUBSYS_71411462&REV_00
Display Memory: 128.0 MB
Current Mode: 1024 x 768 (32 bit) (60Hz)
Monitor: Plug and Play Monitor
Monitor Max Res: 1600,1200
Driver Name: ati2dvag.dll
Driver Version: 6.14.0010.6525 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 3/14/2005 16:54:00, 225280 bytes
WHQL Logo'd: n/a
WHQL Date Stamp: n/a
VDD: n/a
Mini VDD: ati2mtag.sys
Mini VDD Date: 3/14/2005 16:54:00, 1032192 bytes
Device Identifier: {D7B71EE2-1A14-11CF-AF6E-4B51A1C2CB35}
Vendor ID: 0x1002
Device ID: 0x5954
SubSys ID: 0x71411462
Revision ID: 0x0000
Revision ID: 0x0000
Video Accel: ModeMPEG2_C ModeMPEG2_D
Deinterlace Caps: {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{552C0DAD-CCBC-420B-83C8-74943CF9F1A6}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
Registry: OK
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
DDraw Test Result: Not run
D3D7 Test Result: Not run
D3D8 Test Result: Not run
D3D9 Test Result: Not run
Old 02-11-2008, 04:24 PM   #2
LQ Guru
Registered: Aug 2001
Location: Fargo, ND
Distribution: SuSE AMD64
Posts: 15,733

Rep: Reputation: 671Reputation: 671Reputation: 671Reputation: 671Reputation: 671Reputation: 671
If you enter [CTRL]-[ALT]-[F2], can you get into a virtual terminal? If so, then I'd recommend running yast2 in the text mode.
The first thing I would do is run the "Community Repositories" module and add a repository for ATI. The run the Software Installation module and from the ATI repository, install the ati proprietory drivers for your graphics card.
After that is done, run "sax2".

As an alternative, you could try using the generic "vesa" driver in your /etc/X11/xorg.conf config file. This may allow you to run graphically. I don't have an ATI chip but I have had a similar problem initially with my NVidia card. The video was twice as high as it should have been and the bottom half was cut off. Installing the nvidia driver fixed the problem. (nvidia vs nv)

Something else that can cause a problem is if you have both a built in graphics driver on the MB and a second graphics card. If that is the case, you may need to add busID statements in your /etc/X11/xorg.conf file.

From the xorg.conf manpage:
       BusID  "bus-id"
              This  specifies  the bus location of the graphics card.  For PCI/AGP cards, the
              bus-id string has the form PCI:bus:device:function (e.g., “PCI:1:0:0” might  be
              appropriate  for  an  AGP card).  This field is usually optional in single-head
              configurations when using the primary graphics card.  In multi-head  configura‐
              tions,  or when using a secondary graphics card in a single-head configuration,
              this entry is mandatory.  Its main purpose is to make an unambiguous connection
              between  the device section and the hardware it is representing.  This informa‐
              tion can usually be found by running the Xorg server with the -scanpci  command
              line option.
If you look at the output of /sbin/lspic, you can get the bus-id to use. Example from my laptop:
01:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 440 Go 64M] (rev a3)
So in my "Device" section of /etc/X11/xorg.conf, I could have a BusID entry:
Section "Device"
  BoardName    "GeForce4 440 Go 64M"
  BusID        "1:0:0"
  Driver       "nvidia"
  Identifier   "Device[0]"
  Screen       0
  VendorName   "NVidia"
This will prevent the 'Section "Device"' for one graphics controller from being confused for the other. The 'Section "Screen"' section will contain a line near the bottom identifying which graphics device should be used:
  SubSection "Display"
    Depth      8
    Modes      "1280x800" "1280x768" "1024x768" "1280x600" "1024x600" "800x600" "768x576" "640x4
  Device       "Device[0]"
  Identifier   "Screen[0]"
  Monitor      "Monitor[0]"
This will help the X server identify which controller is which.

Good Luck!


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
OpenSuSE 10.3 failing to uninstall openSuSE installer from the windows boot Lucens Linux - Newbie 5 10-11-2008 08:08 AM
opensuse 10.3 gothicbob SUSE / openSUSE 1 05-31-2007 06:39 AM
OpenSuse 10.2 is out johann_p Linux - News 13 02-18-2007 11:27 AM
SATA isues redhat_help Linux - Hardware 3 03-18-2004 04:20 PM
moniter isues or card bob c Linux - Hardware 1 04-03-2003 10:22 AM > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 09:47 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration