PDA

View Full Version : MDK 9.1 come avviare X con driver standard ?


nix.nix
28-08-2003, 15:09
Come posso avviare XSERVER con un driver standard per poi ricompilare il kernel visto che proprio non vuole partire ?

ho MDK 9.1

Ciao

nix.nix
28-08-2003, 15:48
Cosa modifico ?

Section "Device"
Identifier "device1"
VendorName "ATI"
BoardName "ATI Rage 128"
Driver "r128"
Screen 0
BusID "PCI:1:0:0"
Option "DPMS"
Option "UseCCEFor2D" "false"
EndSection

Section "Device"
Identifier "device2"
VendorName "ATI" (II) Reloading /usr/X11R6/lib/modules/linux/libint10.a
(II) R128(1): initializing int10
(II) Multi Device Card detected: [1:0:0][1:1:0]
(EE) R128(1): Cannot read V_BIOS
(==) R128(1): Using gamma correction (1.0, 1.0, 1.0)
------------------------------------------------------------------
Questo è l'errore riportato:

Fatal server error:
xf86MapPciMem: Could not mmap PCI memory [base=0xdc000000,hostbase=0xdc000000,siz

e=0] (Invalid argument)

BoardName "ATI Rage 128"
Driver "r128"
Screen 0
BusID "PCI:1:1:0"
Option "DPMS"
EndSection

ilsensine
28-08-2003, 16:09
Driver "r128"
Driver "vesa"
Lascia inalterato il resto, e partirai con il driver vesa standard.

xf86MapPciMem: Could not mmap PCI memory [base=0xdc000000,hostbase=0xdc000000,size=0] (Invalid argument)
Molto strano il "size=0".

nix.nix
28-08-2003, 16:23
Grazie !

quel il "size=0". per caso indica la memoria video ?

potrebbe essere un problema di AGP apertur size settato a 128MB dal bios ?

ilsensine
28-08-2003, 16:25
No. Cosa riposta lspci -nv?

nix.nix
28-08-2003, 16:41
Originariamente inviato da ilsensine
No. Cosa riposta lspci -nv?

Non sono a casa ma ho questi file:

lspcidrake -v

agpgart : VIA Technologies|VT82C691 [Apollo PRO] [BRIDGE_HOST] (vendor:1106 device:0691)
unknown : VIA Technologies|VT82C598 [Apollo MVP3 AGP] [BRIDGE_PCI] (vendor:1106 device:8598)
unknown : VIA Technologies|VT82C596 ISA [Apollo PRO] [BRIDGE_ISA] (vendor:1106 device:0596 subv:1106 subd:0000)
unknown : VIA Technologies|VT82C586 IDE [Apollo] [STORAGE_IDE] (vendor:1106 device:0571)
usb-uhci : VIA Technologies|VT82C586B USB [SERIAL_USB] (vendor:1106 device:3038 subv:0925 subd:1234)
unknown : VIA Technologies Inc|Power Management Controller [BRIDGE_HOST] (vendor:1106 device:3051)
unknown : NEC|PowerVR PCX2 [midas] [MULTIMEDIA_OTHER] (vendor:1033 device:0046)
unknown : 3Dfx Interactive, Inc.|Voodoo 2 [MULTIMEDIA_VIDEO] (vendor:121a device:0002)
unknown : 3Dfx Interactive, Inc.|Voodoo 2 [MULTIMEDIA_VIDEO] (vendor:121a device:0002)
snd-emu10k1 : Creative Labs|SB Live! (audio) [MULTIMEDIA_AUDIO] (vendor:1102 device:0002 subv:1102 subd:8061)
emu10k1-gp : Creative Labs|SB Live! (joystick) [INPUT_OTHER] (vendor:1102 device:7002 subv:1102 subd:0020)
Card:ATI Rage 128: ATI|Rage 128 Pro AGP 4x [DISPLAY_VGA] (vendor:1002 device:5046 subv:1002 subd:2000)
Card:ATI Rage 128: ATI|Rage 128 Pro AGP 4x [DISPLAY_OTHER] (vendor:1002 device:5046 subv:1002 subd:2001)
unknown : Unknown|USB UHCI Root Hub [Hub|Root Hub] (vendor:0000 device:0000)

lspci -v

00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev 44)
Flags: bus master, medium devsel, latency 0
Memory at d0000000 (32-bit, prefetchable) [size=128M]
Capabilities: [a0] AGP version 1.0

00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP] (prog-if 00 [Normal decode])
Flags: bus master, 66Mhz, medium devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 0000d000-0000dfff
Memory behind bridge: e0000000-e1ffffff
Prefetchable memory behind bridge: d8000000-dfffffff
Capabilities: [80] Power Management version 2

00:07.0 ISA bridge: VIA Technologies, Inc. VT82C596 ISA [Mobile South] (rev 12)
Subsystem: VIA Technologies, Inc. VT82C596/A/B PCI to ISA Bridge
Flags: bus master, stepping, medium devsel, latency 0

00:07.1 IDE interface: VIA Technologies, Inc. VT82C586/B/686A/B PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
Flags: bus master, medium devsel, latency 32
I/O ports at e000 [size=16]

00:07.2 USB Controller: VIA Technologies, Inc. USB (rev 08) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
Flags: bus master, medium devsel, latency 32, IRQ 5
I/O ports at e400 [size=32]

00:07.3 Host bridge: VIA Technologies, Inc. VT82C596 Power Management (rev 20)
Flags: medium devsel

00:09.0 Multimedia controller: NEC Corporation PowerVR PCX2 [midas] (rev 01)
Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 11
Memory at e4400000 (32-bit, prefetchable) [size=64K]
Memory at e4000000 (32-bit, prefetchable) [size=4M]

00:0b.0 Multimedia video controller: 3Dfx Interactive, Inc. Voodoo 2 (rev 02)
Flags: fast devsel
Memory at e2000000 (32-bit, prefetchable) [size=16M]

00:0f.0 Multimedia video controller: 3Dfx Interactive, Inc. Voodoo 2 (rev 02)
Flags: fast devsel
Memory at e3000000 (32-bit, prefetchable) [size=16M]

00:11.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 07)
Subsystem: Creative Labs SBLive! Player 5.1
Flags: bus master, medium devsel, latency 32, IRQ 5
I/O ports at e800 [size=32]
Capabilities: [dc] Power Management version 1

00:11.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 07)
Subsystem: Creative Labs Gameport Joystick
Flags: bus master, medium devsel, latency 32
I/O ports at ec00 [size=8]
Capabilities: [dc] Power Management version 1

01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS (prog-if 00 [VGA])
Subsystem: ATI Technologies Inc Rage Fury MAXX AGP 4x (TMDS) (VGA device)
Flags: bus master, VGA palette snoop, stepping, 66Mhz, medium devsel, latency 32, IRQ 11
Memory at d8000000 (32-bit, prefetchable) [size=64M]
I/O ports at d000 [size=256]
Memory at e1000000 (32-bit, non-prefetchable) [size=16K]
Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities: [50] AGP version 2.0
Capabilities: [5c] Power Management version 2

01:01.0 Display controller: ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS
Subsystem: ATI Technologies Inc Rage Fury MAXX AGP 4x (TMDS) (Extra device?!)
Flags: bus master, stepping, 66Mhz, medium devsel, latency 32, IRQ 10
Memory at dc000000 (32-bit, prefetchable) [size=64M]
I/O ports at d400 [size=256]
Memory at e1004000 (32-bit, non-prefetchable) [size=16K]
Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities: [50] AGP version 2.0
Capabilities: [5c] Power Management version 2

:confused:

AnonimoVeneziano
28-08-2003, 16:54
Ma hai 2 schede?

Ciao

nix.nix
28-08-2003, 17:06
La ati fury maxx monta 2 processori Rage Fury Pro 128 che lavorano in parallelo:

http://www.megaoverclock.it/ATIFURYMAXX64A.html

http://www.ati.com/support/faq/cmosagp.html

http://www.ati.com/support/infobase/3571.html

E anche su windows rileva 2 schede,

ho provato anche a eliminarne una ma nisba!!

ilsensine
28-08-2003, 17:32
01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS (prog-if 00 [VGA])
Subsystem: ATI Technologies Inc Rage Fury MAXX AGP 4x (TMDS) (VGA device)
Flags: bus master, VGA palette snoop, stepping, 66Mhz, medium devsel, latency 32, IRQ 11
Memory at d8000000 (32-bit, prefetchable) [size=64M]
I/O ports at d000 [size=256]
Memory at e1000000 (32-bit, non-prefetchable) [size=16K]
Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities: [50] AGP version 2.0
Capabilities: [5c] Power Management version 2

01:01.0 Display controller: ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS
Subsystem: ATI Technologies Inc Rage Fury MAXX AGP 4x (TMDS) (Extra device?!)
Flags: bus master, stepping, 66Mhz, medium devsel, latency 32, IRQ 10
Memory at dc000000 (32-bit, prefetchable) [size=64M]
I/O ports at d400 [size=256]
Memory at e1004000 (32-bit, non-prefetchable) [size=16K]
Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities: [50] AGP version 2.0
Capabilities: [5c] Power Management version 2

Non so cosa si è fumato xfree, ma deve essere roba pesante. Il sistema rileva la dimensione corretta della regione (64M) ma xfree rileva...0M. Puoi allegare l'output completo di xfree?

Non è un problema di facile soluzione, dovresti scrivere alla mailing list mandrake-cooker oppure riempire un report bugzilla sul sito della Mandrake. Credo che possano essere interessati al tuo caso.

ilsensine
28-08-2003, 17:39
Niente ho letto nell'altro thread (non ne aprire 2 però, chiudo questo e continuiamo nell'altro). Per me devi scrivere alla mandrake-cooker ml.