Results 1 to 4 of 4

Thread: Server Graphic Driver isn't working

  1. #1

    Default Server Graphic Driver isn't working

    Hey Guys i've got the Problem that a Driver on my Server isn't working. I changed the xorg.conf so it uses the vesa driver instead of the mach64 wich it has used before. But all i've got is a blackcreen. Because of that i looked if vesa driver is already installed but it is. I used Knoppix 7.2 to change the xorg and lookup the vesa driver and it showed me an usual graphic interface. So i examinated the xorg.conf of the Live CD on vesa driver entrys but it there wasn't one. Hope you can help me out.

    I'm looking forward for an answer.

    sincerely userpi

    Server Specs:

    dmidecode 2.11
    SMBIOS 2.3 present.
    64 structures occupying 2611 bytes.
    Table at 0x000F9A60.

    Handle 0x0000, DMI type 0, 20 bytes
    BIOS Information
    Vendor: American Megatrends Inc.
    Version: 080010
    Release Date: 07/26/2006
    Address: 0xF0000
    Runtime Size: 64 kB
    ROM Size: 512 kB
    Characteristics:
    ISA is supported
    PCI is supported
    PNP is supported
    APM is supported
    BIOS is upgradeable
    BIOS shadowing is allowed
    ESCD support is available
    Boot from CD is supported
    Selectable boot is supported
    BIOS ROM is socketed
    EDD is supported
    5.25"/1.2 MB floppy services are supported (int 13h)
    3.5"/720 kB floppy services are supported (int 13h)
    3.5"/2.88 MB floppy services are supported (int 13h)
    Print screen service is supported (int 5h)
    8042 keyboard services are supported (int 9h)
    Serial services are supported (int 14h)
    Printer services are supported (int 17h)
    CGA/mono video services are supported (int 10h)
    ACPI is supported
    USB legacy is supported
    AGP is supported
    LS-120 boot is supported
    ATAPI Zip drive boot is supported
    BIOS boot specification is supported
    Function key-initiated network boot is supported

    Handle 0x0001, DMI type 1, 25 bytes
    System Information
    Manufacturer: To Be Filled By O.E.M.
    Product Name: To Be Filled By O.E.M.
    Version: To Be Filled By O.E.M.
    Serial Number: To Be Filled By O.E.M.
    UUID: 00020003-0004-0005-0006-000700080009
    Wake-up Type: PCI PME#

    Handle 0x0002, DMI type 2, 8 bytes
    Base Board Information
    Manufacturer: TYAN
    Product Name: TYAN High-End Dual AMD Opteron, S2882
    Version: To be filled by O.E.M.
    Serial Number: To be filled by O.E.M.

    Handle 0x0004, DMI type 4, 35 bytes
    Processor Information
    Socket Designation: CPU 1
    Type: Central Processor
    Family: Opteron
    Manufacturer: AMD
    ID: 12 0F 02 00 FF FB 8B 17
    Signature: Family 15, Model 33, Stepping 2
    Flags:
    FPU (Floating-point unit on-chip)
    VME (Virtual mode extension)
    DE (Debugging extension)
    PSE (Page size extension)
    TSC (Time stamp counter)
    MSR (Model specific registers)
    PAE (Physical address extension)
    MCE (Machine check exception)
    CX8 (CMPXCHG8 instruction supported)
    APIC (On-chip APIC hardware supported)
    SEP (Fast system call)
    MTRR (Memory type range registers)
    PGE (Page global enable)
    MCA (Machine check architecture)
    CMOV (Conditional move instruction supported)
    PAT (Page attribute table)
    PSE-36 (36-bit page size extension)
    CLFSH (CLFLUSH instruction supported)
    MMX (MMX technology supported)
    FXSR (FXSAVE and FXSTOR instructions supported)
    SSE (Streaming SIMD extensions)
    SSE2 (Streaming SIMD extensions 2)
    HTT (Multi-threading)
    Version: Dual Core AMD Opteron(tm) Processor 275
    Voltage: 3.3 V 2.9 V
    External Clock: 200 MHz
    Max Speed: 2200 MHz
    Current Speed: 2200 MHz
    Status: Populated, Enabled
    Upgrade: Socket 940
    L1 Cache Handle: 0x0005
    L2 Cache Handle: 0x0006
    L3 Cache Handle: 0x0007
    Serial Number: To Be Filled By O.E.M.
    Asset Tag: To Be Filled By O.E.M.
    Part Number: To Be Filled By O.E.M.

    Handle 0x0008, DMI type 4, 35 bytes
    Processor Information
    Socket Designation: CPU 2
    Type: Central Processor
    Family: Opteron
    Manufacturer: AMD
    ID: 12 0F 02 00 FF FB 8B 17
    Signature: Family 15, Model 33, Stepping 2
    Flags:
    FPU (Floating-point unit on-chip)
    VME (Virtual mode extension)
    DE (Debugging extension)
    PSE (Page size extension)
    TSC (Time stamp counter)
    MSR (Model specific registers)
    PAE (Physical address extension)
    MCE (Machine check exception)
    CX8 (CMPXCHG8 instruction supported)
    APIC (On-chip APIC hardware supported)
    SEP (Fast system call)
    MTRR (Memory type range registers)
    PGE (Page global enable)
    MCA (Machine check architecture)
    CMOV (Conditional move instruction supported)
    PAT (Page attribute table)
    PSE-36 (36-bit page size extension)
    CLFSH (CLFLUSH instruction supported)
    MMX (MMX technology supported)
    FXSR (FXSAVE and FXSTOR instructions supported)
    SSE (Streaming SIMD extensions)
    SSE2 (Streaming SIMD extensions 2)
    HTT (Multi-threading)
    Version: Dual Core AMD Opteron(tm) Processor 275
    Voltage: 3.3 V 2.9 V
    External Clock: 200 MHz
    Max Speed: 2200 MHz
    Current Speed: 2200 MHz
    Status: Populated, Enabled
    Upgrade: Socket 940
    L1 Cache Handle: 0x0009
    L2 Cache Handle: 0x000A
    L3 Cache Handle: 0x000B
    Serial Number: To Be Filled By O.E.M.
    Asset Tag: To Be Filled By O.E.M.
    Part Number: To Be Filled By O.E.M.


    Handle 0x002A, DMI type 13, 22 bytes
    BIOS Language Information
    Language Description Format: Abbreviated
    Installable Languages: 1
    en|US|iso8859-1
    Currently Installed Language: en|US|iso8859-1

    Handle 0x002B, DMI type 16, 15 bytes
    Physical Memory Array
    Location: System Board Or Motherboard
    Use: System Memory
    Error Correction Type: Single-bit ECC
    Maximum Capacity: 12 GB
    Error Information Handle: Not Provided
    Number Of Devices: 8

    Handle 0x002C, DMI type 19, 15 bytes
    Memory Array Mapped Address
    Starting Address: 0x00000000000
    Ending Address: 0x000FBFFFFFF
    Range Size: 4032 MB
    Physical Array Handle: 0x002B
    Partition Width: 1

    Handle 0x002D, DMI type 17, 27 bytes
    Memory Device
    Array Handle: 0x002B
    Error Information Handle: Not Provided
    Total Width: 72 bits
    Data Width: 64 bits
    Size: 1024 MB
    Form Factor: DIMM
    Set: None
    Locator: DIMM0
    Bank Locator: BANK0
    Type: SDRAM
    Type Detail: Synchronous
    Speed: Unknown
    Manufacturer: Manufacturer0
    Serial Number: SerNum0
    Asset Tag: AssetTagNum0
    Part Number: PartNum0

    Handle 0x002E, DMI type 20, 19 bytes
    Memory Device Mapped Address
    Starting Address: 0x00000000000
    Ending Address: 0x0003FFFFFFF
    Range Size: 1 GB
    Physical Device Handle: 0x002D
    Memory Array Mapped Address Handle: 0x002C
    Partition Row Position: 1

    Handle 0x002F, DMI type 17, 27 bytes
    Memory Device
    Array Handle: 0x002B
    Error Information Handle: Not Provided
    Total Width: 72 bits
    Data Width: 64 bits
    Size: 1024 MB
    Form Factor: DIMM
    Set: None
    Locator: DIMM1
    Bank Locator: BANK1
    Type: SDRAM
    Type Detail: Synchronous
    Speed: Unknown
    Manufacturer: Manufacturer1
    Serial Number: SerNum1
    Asset Tag: AssetTagNum1
    Part Number: PartNum1

    Handle 0x0030, DMI type 20, 19 bytes
    Memory Device Mapped Address
    Starting Address: 0x00040000000
    Ending Address: 0x0007FFFFFFF
    Range Size: 1 GB
    Physical Device Handle: 0x002F
    Memory Array Mapped Address Handle: 0x002C
    Partition Row Position: 1

    Handle 0x0031, DMI type 17, 27 bytes
    Memory Device
    Array Handle: 0x002B
    Error Information Handle: Not Provided
    Total Width: Unknown
    Data Width: Unknown
    Size: No Module Installed
    Form Factor: DIMM
    Set: None
    Locator: DIMM2
    Bank Locator: BANK2
    Type: Unknown
    Type Detail: Unknown
    Speed: Unknown
    Manufacturer: Manufacturer2
    Serial Number: SerNum2
    Asset Tag: AssetTagNum2
    Part Number: PartNum2

    Handle 0x0033, DMI type 17, 27 bytes
    Memory Device
    Array Handle: 0x002B
    Error Information Handle: Not Provided
    Total Width: Unknown
    Data Width: Unknown
    Size: No Module Installed
    Form Factor: DIMM
    Set: None
    Locator: DIMM3
    Bank Locator: BANK3
    Type: Unknown
    Type Detail: Unknown
    Speed: Unknown
    Manufacturer: Manufacturer3
    Serial Number: SerNum3
    Asset Tag: AssetTagNum3
    Part Number: PartNum3

    Handle 0x0035, DMI type 17, 27 bytes
    Memory Device
    Array Handle: 0x002B
    Error Information Handle: Not Provided
    Total Width: 72 bits
    Data Width: 64 bits
    Size: 1024 MB
    Form Factor: DIMM
    Set: None
    Locator: DIMM4
    Bank Locator: BANK4
    Type: SDRAM
    Type Detail: Synchronous
    Speed: Unknown
    Manufacturer: Manufacturer4
    Serial Number: SerNum4
    Asset Tag: AssetTagNum4
    Part Number: PartNum4

    Handle 0x0036, DMI type 20, 19 bytes
    Memory Device Mapped Address
    Starting Address: 0x00080000000
    Ending Address: 0x000BFFFFFFF
    Range Size: 1 GB
    Physical Device Handle: 0x0035
    Memory Array Mapped Address Handle: 0x002C
    Partition Row Position: 1

    Handle 0x0037, DMI type 17, 27 bytes
    Memory Device
    Array Handle: 0x002B
    Error Information Handle: Not Provided
    Total Width: 72 bits
    Data Width: 64 bits
    Size: 1024 MB
    Form Factor: DIMM
    Set: None
    Locator: DIMM5
    Bank Locator: BANK5
    Type: SDRAM
    Type Detail: Synchronous
    Speed: Unknown
    Manufacturer: Manufacturer5
    Serial Number: SerNum5
    Asset Tag: AssetTagNum5
    Part Number: PartNum5

    Handle 0x0038, DMI type 20, 19 bytes
    Memory Device Mapped Address
    Starting Address: 0x000C0000000
    Ending Address: 0x000FFFFFFFF
    Range Size: 1 GB
    Physical Device Handle: 0x0037
    Memory Array Mapped Address Handle: 0x002C
    Partition Row Position: 1

    Handle 0x0039, DMI type 17, 27 bytes
    Memory Device
    Array Handle: 0x002B
    Error Information Handle: Not Provided
    Total Width: Unknown
    Data Width: Unknown
    Size: No Module Installed
    Form Factor: DIMM
    Set: None
    Locator: DIMM6
    Bank Locator: BANK6
    Type: Unknown
    Type Detail: Unknown
    Speed: Unknown
    Manufacturer: Manufacturer4
    Serial Number: SerNum6
    Asset Tag: AssetTagNum6
    Part Number: PartNum6

    Handle 0x003B, DMI type 17, 27 bytes
    Memory Device
    Array Handle: 0x002B
    Error Information Handle: Not Provided
    Total Width: Unknown
    Data Width: Unknown
    Size: No Module Installed
    Form Factor: DIMM
    Set: None
    Locator: DIMM7
    Bank Locator: BANK7
    Type: Unknown
    Type Detail: Unknown
    Speed: Unknown
    Manufacturer: Manufacturer5
    Serial Number: SerNum7
    Asset Tag: AssetTagNum7
    Part Number: PartNum7

  2. #2
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    29,761

    Default Re: Server Graphic Driver isn't working

    Hello and welcome on the openSUSE forums.

    You gave us a lot of information and I did not read all of it, but I doubt that the most important clue is therein: what version of openSUSE do you use?
    Henk van Velden

  3. #3

    Default Re: Server Graphic Driver isn't working

    Hi
    first of all i'm sorry about that and i'm ashamed of myself.

    It's running on SUSE 12.3. x64bit. I tried to change root it but all it get is a Shell Error because I tried it with a 32bit Version of Knoppix. So i tried it with Fedora x64 bit, but the Screen just turns black. But there is one diffrence to the SUSE. Fedora shows the Progress of Booting Data into the RAM (blue bars) so the Graphic Driver should work till runlevel 3. That means that in this case the Xorg produces some errors, am i right?

    Thank you for your Reply, sorry about that huge Text above.
    Next time i just link it and host it on some Cloud.

    yours

    userpi

  4. #4
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    16,287

    Default Re: Server Graphic Driver isn't working

    OK so exactly what vidio card is it? I really don't have the time to parse all that stuff you listed

    Maybe show use the changed xorg.conf files so we can see what you did. The vesa drive should be there unless you removed it. I have no idea if the ??? Matrix card works with vesa. But it should.

    Maybe just rename the xorg.conf file and let the OS chose the driver. In theory at least you should not need an xorg.conf in most cases.

Tags for this Thread

Posting Permissions

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