[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

X on 712/100

Hi there,

I'm running debian-hppa on a 712/100 and everything installed OK 
except for X windows. I get the following error (from the log file):

XFree86 Version / X Window System
(protocol Version 11, revision 0, vendor release 6510)
Release Date: 21 December 2001
        If the server is older than 6-12 months, or if your card is
        newer than the above date, look for a newer version before
        reporting problems.  (See http://www.XFree86.Org/FAQ)
Build Operating System: Linux 2.4.16-64 parisc64 [ELF]
(==) Log file: "/var/log/XFree86.0.log", Time: Tue Feb  5 20:06:39 2002
(==) Using config file: "/etc/X11/XF86Config-4"
Markers: (--) probed, (**) from config file, (==) default setting,
         (++) from command line, (!!) notice, (II) informational,
         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) ServerLayout "Default Layout"
(**) |-->Screen "Default Screen" (0)
(**) |   |-->Monitor "ADI MicroScan 5AP"
(**) |   |-->Device "Generic Video Card"
(**) |-->Input Device "Generic Keyboard"
(**) Option "XkbRules" "xfree86"
(**) XKB: rules: "xfree86"
(**) Option "XkbModel" "pc102"
(**) XKB: model: "pc102"
(**) Option "XkbLayout" "es"
(**) XKB: layout: "es"
(==) Keyboard: CustomKeycode disabled
(**) |-->Input Device "Configured Mouse"
(**) |-->Input Device "Generic Mouse"
(WW) The directory "/usr/lib/X11/fonts/cyrillic" does not exist.
        Entry deleted from font path.
(**) FontPath set to "unix/:7100,/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/100dpi/:unscaled,/usr/lib/X11/fonts/75dpi/:unscaled,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/Speedo,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts/75dpi"
(==) RgbPath set to "/usr/X11R6/lib/X11/rgb"
(--) using VT number 7

(WW) Cannot open APM
(EE) No OS PCI support available
(II) Addressable bus resource ranges are
        [0] -1 0        0x00000000 - 0xffffffff (0x0) MX[B]
        [1] -1 0        0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) OS-reported resource ranges:
        [0] -1 0        0xffffffff - 0xffffffff (0x1) MX[B]
        [1] -1 0        0x00000000 - 0x00000000 (0x1) MX[B]
        [2] -1 0        0x0000ffff - 0x0000ffff (0x1) IX[B]
        [3] -1 0        0x00000000 - 0x00000000 (0x1) IX[B]
(II) OS-reported resource ranges after removing overlaps with PCI:
        [0] -1 0        0xffffffff - 0xffffffff (0x1) MX[B]
        [1] -1 0        0x00000000 - 0x00000000 (0x1) MX[B]
        [2] -1 0        0x0000ffff - 0x0000ffff (0x1) IX[B]
        [3] -1 0        0x00000000 - 0x00000000 (0x1) IX[B]
(II) All system resource ranges:
        [0] -1 0        0xffffffff - 0xffffffff (0x1) MX[B]
        [1] -1 0        0x00000000 - 0x00000000 (0x1) MX[B]
        [2] -1 0        0x0000ffff - 0x0000ffff (0x1) IX[B]
        [3] -1 0        0x00000000 - 0x00000000 (0x1) IX[B]
(II) MGA: driver for Matrox chipsets: mga2064w, mga1064sg, mga2164w,
        mga2164w AGP, mgag100, mgag100 PCI, mgag200, mgag200 PCI, mgag400
(II) GLINT: driver for 3Dlabs chipsets: gamma, ti_pm2, ti_pm, pm3, pm2v,
        pm2, pm, 300sx, 500tx, mx, delta
(II) S3VIRGE: driver (version 1.6.13) for S3 ViRGE chipsets: virge, 86C325,
        virge vx, 86C988, virge dx, virge gx, 86C375, 86C385, virge gx2,
        86C357, virge mx, 86C260, virge mx+, 86C280, trio 3d, 86C365,
        trio 3d/2x, 86C362, 86C368
(II) SIS: driver for SiS chipsets: SIS5597, SIS5598, SIS530, SIS6326,
        SIS300, SIS630, SIS540
(II) SAVAGE: driver (version 1.1.16) for S3 Savage chipsets: Savage4,
        Savage3D, Savage3D-MV, Savage2000, Savage/MX-MV, Savage/MX,
        Savage/IX-MV, Savage/IX, ProSavage PM133, ProSavage KM133, Twister,
(II) TRIDENT: driver for Trident chipsets: tvga8900d, cyber9320, cyber9388,
        cyber9397, cyber9397dvd, cyber9520, cyber9525dvd, cyberblade/e4,
        tgui9420dgi, tgui9440agi, tgui9660, tgui9680, providia9682,
        providia9685, cyber9382, cyber9385, 3dimage975, 3dimage985, blade3d,
        cyberbladei7, cyberbladei7d, cyberbladei1, cyberbladei1d,
        cyberbladeAi1, cyberbladeAi1d, cyberbladeXP, cyberbladeXPm
(II) CHIPS: Driver for Chips and Technologies chipsets: ct65520, ct65525,
        ct65530, ct65535, ct65540, ct65545, ct65546, ct65548, ct65550,
        ct65554, ct65555, ct68554, ct69000, ct69030, ct64200, ct64300
(II) TDFX: Driver for 3dfx Banshee/Voodoo3 chipsets: 3dfx Banshee,
        3dfx Voodoo3, 3dfx Voodoo5
(II) FBDev: driver for framebuffer: fbdev, afb
(II) ATI: ATI driver (version 6.3.6) for chipsets: ati
(II) R128: Driver for ATI Rage 128 chipsets: ATI Rage 128 RE (PCI),
        ATI Rage 128 RF (AGP), ATI Rage 128 RG (AGP), ATI Rage 128 RK (PCI),
        ATI Rage 128 RL (AGP), ATI Rage 128 Pro PD (PCI),
        ATI Rage 128 Pro PF (AGP), ATI Rage 128 Pro PP (PCI),
        ATI Rage 128 Pro PR (PCI), ATI Rage 128 Mobility LE (PCI),
        ATI Rage 128 Mobility LF (AGP), ATI Rage 128 Mobility MF (AGP),
(II) RADEON: Driver for ATI Radeon chipsets: ATI Radeon QD (AGP),
        ATI Radeon QE (AGP), ATI Radeon QF (AGP), ATI Radeon QG (AGP),
        ATI Radeon VE (AGP)
(II) imstt: driver (version 1.0.0 for IMS TwinTurbo chipsets : imstt128,
(II) VGA: Generic VGA driver (version 4.0) for chipsets: generic
(II) v4l driver for Video4Linux
        S3VProbe begin
(II) FBDev(0): using default device
(II) Running in FRAMEBUFFER Mode
(**) FBDev(0): Depth 16, (--) framebuffer bpp 16
(==) FBDev(0): RGB weight 565
(==) FBDev(0): Default visual is TrueColor
(==) FBDev(0): Using gamma correction (1.0, 1.0, 1.0)
(II) FBDev(0): Hardware:  (vidmem: 2048k)
(II) FBDev(0): Checking Modes against framebuffer device...
(II) FBDev(0):  mode "1024x768" ok
(II) FBDev(0): Checking Modes against monitor...
(--) FBDev(0): Virtual size is 1024x768 (pitch 1024)
(**) FBDev(0): Default mode "1024x768": 44.9 MHz (scaled from 0.0 MHz), 35.5 kHz, 87.0 Hz (I)
(II) FBDev(0): Modeline "1024x768"   44.90  1024 1032 1208 1264  768 768 776 817 interlace +hsync +vsync
(++) FBDev(0): DPI set to (100, 100)
(**) FBDev(0): Using "Shadow Framebuffer"

Fatal server error:
AddScreen/ScreenInit failed for driver 0


I read on the mailing list that someone had the same problem with a 715. 
Anybody knows what's going wrong??? Thanks a lot,


Reply to: