Date: Mon, 18 Dec 1995 14:35:09 +0000 () From: Nik Clayton <nik@blueberry.co.uk> To: questions@freebsd.org Subject: X problems (D Stealth 64 (S3 Trio 64)) Message-ID: <199512181435.OAA00636@elbereth.blueberry.co.uk>
next in thread | raw e-mail | index | archive | help
How do,
With my 2.1 system I've got the XFree86 3.1.2 installed. My graphics
card is a Diamond Stealth 64 (1 Mbyte) on the PCI bus. Apparently it
uses the S3 Trio 64 chipset.
After configuring X, I then do 'startx'.
It all starts up quite nicely. The desktop appears, twm fires up and
xclock starts running.
I then get dumped back at my command prompt. The complete error log
looks like this:
XFree86 Version 3.1.2 / X Window System
(protocol Version 11, revision 0, vendor release 6001)
Operating System: FreeBSD 2.0.5
Configured drivers:
S3: accelerated server for S3 graphics adaptors (Patchlevel 0)
mmio_928, s3_generic
Using syscons driver with X support (version 2.0)
(using VT number 4)
XF86Config: /usr/X11R6/lib/X11/XF86Config
(**) stands for supplied, (--) stands for probed/default values
(**) Mouse: type: PS/2, device: /dev/psm0, baudrate: 1200,
3 button emulation (timeout: 50ms)
(**) S3: Graphics device ID: "Diamond Stealth 64 DRAM with S3-Trio64"
(**) S3: Monitor ID: "AOC CM-326"
(--) S3: Mode "1024x768" needs hsync freq of 56.48 kHz. Deleted.
(--) S3: Mode "1280x1024" needs hsync freq of 51.02 kHz. Deleted.
(--) S3: Mode "1024x768" needs hsync freq of 62.50 kHz. Deleted.
(--) S3: Mode "1280x1024" needs hsync freq of 64.25 kHz. Deleted.
(--) S3: Mode "1280x1024" needs hsync freq of 78.86 kHz. Deleted.
(--) S3: Mode "1280x1024" needs hsync freq of 81.13 kHz. Deleted.
(**) FontPath set to "/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/"
(--) S3: card type: PCI
(--) S3: chipset: Trio64 rev. 21
(--) S3: chipset driver: mmio_928
(--) S3: videoram: 1024k
(--) S3: Ramdac type: s3_trio64
(--) S3: Ramdac speed: 135
(--) S3: Using Trio32/64 programmable clock (MCLK 59.957 MHz)
(--) S3: Maximum allowed dot-clock: 135.000 MHz
(**) S3: Mode "1024x768": mode clock = 65.000
(**) S3: Mode "800x600": mode clock = 50.000
(**) S3: Mode "640x480": mode clock = 31.500
(--) S3: Using 6 bits per RGB value
(**) S3: Virtual resolution set to 1024x768
(--) S3: Local bus LAW is 0xF3000000
(--) S3: Using a banksize of 1024k, line width of 1024
(--) S3: Using a single 64x64 area at (960,769) for expanding pixmaps
(--) S3: Using 8 planes of 960x255 at (0,769) aligned 8 as font cache
xterm: Error 23, errno 25: Inappropriate ioctl for device
xterm: Error 23, errno 25: Inappropriate ioctl for device
login: Error 23, errno 25: Inappropriate ioctl for device
waiting for X server to shut down X connection to :0.0 broken (explicit kill or server shutdown).
If I change my xinitrc to not run any xterms (say, by deleting them, and
having xclock as the last running program) then things work without a
hitch. However, I cannot start any xterms at all.
As you can imagine, this is a bit of a problem. Anyone bumped into this?
I'm posting this to FreeBSD first because I've not had any problems with
X before, and this is my first outing with 2.1 (previously I've used
2.0R and 2.0.5 with X3.1 with no problems), although I'm fully prepared
to believe this is a problem with X.
Cheers, N
--
--+=[ Blueberry Hill Blueberry Design ]=+--
--+=[ http://www.blueberry.co.uk/ 1/9 Chelsea Harbour Design Centre, ]=+--
--+=[ WebMaster@blueberry.co.uk London, England, SW10 0XE ]=+--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199512181435.OAA00636>