下達startx指令後，出現以下錯誤訊息

[KTC]

安裝完x-window-system-core後，
再安裝kde，
下達startx指令之後出現以下訊息：

(ww) S3: No matching Device section for instance (Bus ID PCI 129:25:0) not found
(EE) No devices detected

Fatal server error:
no screens found

XIO: fatal IO error 104 (Connection reset by peer) on X server "X0:0" after 0 requests (0 known processed) with 0 events remaining.

請問一下，
像這個樣子是顯示卡方面的問題，
還是IO的問題?(如鍵盤或滑鼠)

P.S. 我的練習機是用KVM的，
也就是說有多台主機但用KVM來共用一台螢幕、鍵盤及滑鼠的，
不知現在的問題跟KVM有沒有關連?

[Tetralet]

下達startx指令之後出現以下訊息：

(ww) S3: No matching Device section for instance (Bus ID PCI 129:25:0) not found
(EE) No devices detected

Fatal server error:
no screens found

應該是沒有載入正確的顯示模組時所產生的錯誤訊息。

請問您的顯示晶片是？

P.S. 我的練習機是用KVM的，
也就是說有多台主機但用KVM來共用一台螢幕、鍵盤及滑鼠的，
不知現在的問題跟KVM有沒有關連?

您的 KVM 是電子式的嗎？

在啟動 X 時要記得切換過去，
不然可能會發生一些怪怪的現象。

[KTC]

To Tetralet(俺是博士):

1.我下達lspci指令後，
顯示出VGA compatible unclassified device: S3 Inc. 86c864[vision 864 DRAM] vers0
如果是沒有載入正確VGA的模組，
那我應該怎麼解決呢?
是不是到/lib/modules/2.4.27-2-386/kernel/drivers/video底下找S3的驅動程式?


2.我的KVM是得用手按KVM上的按鍵才能接換四台主機的畫面。
不過你說startx後切換過去，
我不太懂你的意思耶~
因為現在我其它三台都是關機的狀態，
所以我一開機時的畫面就是DEBIAN這一台的。

[Franklin]

To Tetralet(俺是博士):

1.我下達lspci指令後，
顯示出VGA compatible unclassified device: S3 Inc. 86c864[vision 864 DRAM] vers0
如果是沒有載入正確VGA的模組，
那我應該怎麼解決呢?
是不是到/lib/modules/2.4.27-2-386/kernel/drivers/video底下找S3的驅動程式?


2.我的KVM是得用手按KVM上的按鍵才能接換四台主機的畫面。
不過你說startx後切換過去，
我不太懂你的意思耶~
因為現在我其它三台都是關機的狀態，
所以我一開機時的畫面就是DEBIAN這一台的。

2. 那 KVM 應該就不是問題

我家的 KVM 也是這樣, 如果開機啟動 X 的時候沒有先切過去,
等它啟動完再切過去, 鍵盤滑鼠就會不聽話...

[KTC]

To Tetralet(俺是博士):

1.我下達lspci指令後，
顯示出VGA compatible unclassified device: S3 Inc. 86c864[vision 864 DRAM] vers0
如果是沒有載入正確VGA的模組，
那我應該怎麼解決呢?
是不是到/lib/modules/2.4.27-2-386/kernel/drivers/video底下找S3的驅動程式?


2.我的KVM是得用手按KVM上的按鍵才能接換四台主機的畫面。
不過你說startx後切換過去，
我不太懂你的意思耶~
因為現在我其它三台都是關機的狀態，
所以我一開機時的畫面就是DEBIAN這一台的。

2. 那 KVM 應該就不是問題

我家的 KVM 也是這樣, 如果開機啟動 X 的時候沒有先切過去,
等它啟動完再切過去, 鍵盤滑鼠就會不聽話...

所以我現在的問題很有可能就是顯示卡的驅動出問題囉?!

[訪客]

Fatal server error:
no screens found

這個是螢幕(screen)找不到..
可能是設錯了顯示卡或螢幕.

[Tetralet]

所以我現在的問題很有可能就是顯示卡的驅動出問題囉?!

至少個人是這麼認為，
因為有部份 sis 顯示晶片是 Xorg 所不支援的。

建議您換用 vesa 模組試試看！

[KTC]

1.我的DEBIAN的X好像是XFree86的耶，
因為我下達X -version的指令後，
出現的是XFree86

2.關於你所說的VESA模組，
我到/usr/X11R6/lib/modules/drivers的目錄底下，
用ls看內容後發現，
裡面有S3_drv.o、S3virge_drv.o、savage_drv.o、sis_drv.o及你所說的vesa_drv.o，
而我把VGA拆下來看，
矽晶片上的打印是寫著S3 SDAC GACD2 86C716-MG 9422 F21697，
而我到S3的網站上找關於以上的這一張VGA的相關資料，
結果並沒有找到任何相關DRIVER。
(S3官網寫著obsolete products)
(Drivers for new operating systems or any other support for these devices is not provided. )
(不知是不是也指沒有技援LINUX的DRIVER?)

所以我想問，
這張VGA是屬於S3_drv.0還是S3virge_drv.o或你所說的vesa_drv.o模組?

3.因為現在不確定到底問題出在哪兒，
所以我決定用SSH把錯誤訊息顯示到我WINDOWS的CMD上，
再把它覆製到文章串來。
(因為太長了，怕會影響這篇文章的閱讀的方便性)
(所以我用回覆的方式發表)

[KTC]

以下是我下達startx指令後，
所顯示出來的錯誤畫面。
[root@debian:~]#startx
Using authority file /root/.Xauthority
Writing authority file /root/.Xauthority
Using authority file /root/.Xauthority
Writing authority file /root/.Xauthority

X: warning; process set to priority -11 instead of requested priority -10
XFree86 Version 4.3.0.1 (Debian 4.3.0.dfsg.1-14sarge1 20050901212727 fjp@localhost.localdomain)
Release Date: 15 August 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: Linux 2.6.8-16.0508-2 i686 [ELF]
Build Date: 02 September 2005

This version of XFree86 has been extensively modified by the Debian
Project, and is not supported by the XFree86 Project, Inc., in any
way. Bugs should be reported to the Debian Bug Tracking System; see
<URL: http://www.debian.org/Bugs/Reporting >.

We strongly encourage the use of the "reportbug" package and command
to ensure that bug reports contain as much useful information as
possible.

Before filing a bug report, you may want to consult the Debian X FAQ:
XHTML version: file:///usr/share/doc/xfree86-common/FAQ.xhtml
plain text version: file:///usr/share/doc/xfree86-common/FAQ.gz

Module Loader present
OS Kernel: Linux version 2.4.27-2-386 (horms@tabatha.lab.ultramonkey.org) (gcc version 3.3.5 (Debian 1:3.3.5-13)) #1 Wed Aug 17 09:33:35 UTC 2005
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/XFree86.0.log", Time: Mon Jul 10 14:59:16 2006
(==) Using config file: "/etc/X11/XF86Config-4"
Skipping "/usr/X11R6/lib/modules/extensions/libGLcore.a:m_debug_clip.o": No symbols found
Skipping "/usr/X11R6/lib/modules/extensions/libGLcore.a:m_debug_norm.o": No symbols found
Skipping "/usr/X11R6/lib/modules/extensions/libGLcore.a:m_debug_xform.o": No symbols found
Skipping "/usr/X11R6/lib/modules/extensions/libGLcore.a:m_debug_vertex.o": No symbols found
Skipping "/usr/X11R6/lib/modules/fonts/libspeedo.a:spencode.o": No symbols found
(WW) s3: No matching Device section for instance (BusID PCI:0:12:0) found
(WW) s3: No matching Device section for instance (BusID PCI:128:0:0) found
(WW) s3: No matching Device section for instance (BusID PCI:128:1:0) found
(WW) s3: No matching Device section for instance (BusID PCI:128:2:0) found
(WW) s3: No matching Device section for instance (BusID PCI:128:3:0) found
(WW) s3: No matching Device section for instance (BusID PCI:128:4:0) found
(WW) s3: No matching Device section for instance (BusID PCI:128:5:0) found
(WW) s3: No matching Device section for instance (BusID PCI:128:6:0) found
(WW) s3: No matching Device section for instance (BusID PCI:128:7:0) found
(WW) s3: No matching Device section for instance (BusID PCI:128:8:0) found
(WW) s3: No matching Device section for instance (BusID PCI:128:9:0) found
(WW) s3: No matching Device section for instance (BusID PCI:128:10:0) found
(WW) s3: No matching Device section for instance (BusID PCI:128:11:0) found
(WW) s3: No matching Device section for instance (BusID PCI:128:12:0) found
(WW) s3: No matching Device section for instance (BusID PCI:128:13:0) found
(WW) s3: No matching Device section for instance (BusID PCI:128:14:0) found
(WW) s3: No matching Device section for instance (BusID PCI:128:15:0) found
(WW) s3: No matching Device section for instance (BusID PCI:128:16:0) found
(WW) s3: No matching Device section for instance (BusID PCI:128:17:0) found
(WW) s3: No matching Device section for instance (BusID PCI:128:18:0) found
(WW) s3: No matching Device section for instance (BusID PCI:128:19:0) found
(WW) s3: No matching Device section for instance (BusID PCI:128:20:0) found
(WW) s3: No matching Device section for instance (BusID PCI:128:21:0) found
(WW) s3: No matching Device section for instance (BusID PCI:128:22:0) found
(WW) s3: No matching Device section for instance (BusID PCI:128:23:0) found
(WW) s3: No matching Device section for instance (BusID PCI:128:24:0) found
(WW) s3: No matching Device section for instance (BusID PCI:128:25:0) found
(WW) s3: No matching Device section for instance (BusID PCI:128:26:0) found
(WW) s3: No matching Device section for instance (BusID PCI:128:27:0) found
(WW) s3: No matching Device section for instance (BusID PCI:128:28:0) found
(WW) s3: No matching Device section for instance (BusID PCI:128:29:0) found
(WW) s3: No matching Device section for instance (BusID PCI:128:30:0) found
(WW) s3: No matching Device section for instance (BusID PCI:128:31:0) found
(WW) s3: No matching Device section for instance (BusID PCI:129:0:0) found
(WW) s3: No matching Device section for instance (BusID PCI:129:1:0) found
(WW) s3: No matching Device section for instance (BusID PCI:129:2:0) found
(WW) s3: No matching Device section for instance (BusID PCI:129:3:0) found
(WW) s3: No matching Device section for instance (BusID PCI:129:4:0) found
(WW) s3: No matching Device section for instance (BusID PCI:129:5:0) found
(WW) s3: No matching Device section for instance (BusID PCI:129:6:0) found
(WW) s3: No matching Device section for instance (BusID PCI:129:7:0) found
(WW) s3: No matching Device section for instance (BusID PCI:129:8:0) found
(WW) s3: No matching Device section for instance (BusID PCI:129:9:0) found
(WW) s3: No matching Device section for instance (BusID PCI:129:10:0) found
(WW) s3: No matching Device section for instance (BusID PCI:129:11:0) found
(WW) s3: No matching Device section for instance (BusID PCI:129:12:0) found
(WW) s3: No matching Device section for instance (BusID PCI:129:13:0) found
(WW) s3: No matching Device section for instance (BusID PCI:129:14:0) found
(WW) s3: No matching Device section for instance (BusID PCI:129:15:0) found
(WW) s3: No matching Device section for instance (BusID PCI:129:16:0) found
(WW) s3: No matching Device section for instance (BusID PCI:129:17:0) found
(WW) s3: No matching Device section for instance (BusID PCI:129:18:0) found
(WW) s3: No matching Device section for instance (BusID PCI:129:19:0) found
(WW) s3: No matching Device section for instance (BusID PCI:129:20:0) found
(WW) s3: No matching Device section for instance (BusID PCI:129:21:0) found
(WW) s3: No matching Device section for instance (BusID PCI:129:22:0) found
(WW) s3: No matching Device section for instance (BusID PCI:129:23:0) found
(WW) s3: No matching Device section for instance (BusID PCI:129:24:0) found
(WW) s3: No matching Device section for instance (BusID PCI:129:25:0) found
(EE) No devices detected.

Fatal server error:
no screens found

When reporting a problem related to a server crash, please send
the full server output, not just the last messages.
This can be found in the log file "/var/log/XFree86.0.log".
Please report problems to submit@bugs.debian.org.

XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"
after 0 requests (0 known processed) with 0 events remaining.

[訪客]

這個狀況,我以前好像遇過,
應該是顯示卡pci的位址指定錯了....

像我這裡lspci結果是:
00:00.0 Host bridge: Silicon Integrated Systems [SiS] 5597 [SiS5582] (rev 02)
00:01.0 ISA bridge: Silicon Integrated Systems [SiS] SiS85C503/5513 (LPC Bridge) (rev 01)
00:01.1 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0)
00:0b.0 VGA compatible controller: Cirrus Logic GD 5446 (rev 45)
00:0f.0 Ethernet controller: Advanced Micro Devices [AMD] 79c978 [HomePNA] (rev 52)

表示我的顯示卡是Cirrus Logic GD 5446 (rev 45),pci位置是00:0b.0
當時我把16進位的00:0b.0改成10進位的0:11:0寫進xorg.conf就成功了:
Section "Device"
Identifier "Cirrus Logic GD 5446"
Driver "cirrus"
BusID "PCI:0:11:0"
VideoRam 2048
EndSection

你可以試試看

[KTC]

這個狀況,我以前好像遇過,
應該是顯示卡pci的位址指定錯了....

像我這裡lspci結果是:
00:00.0 Host bridge: Silicon Integrated Systems [SiS] 5597 [SiS5582] (rev 02)
00:01.0 ISA bridge: Silicon Integrated Systems [SiS] SiS85C503/5513 (LPC Bridge) (rev 01)
00:01.1 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0)
00:0b.0 VGA compatible controller: Cirrus Logic GD 5446 (rev 45)
00:0f.0 Ethernet controller: Advanced Micro Devices [AMD] 79c978 [HomePNA] (rev 52)

表示我的顯示卡是Cirrus Logic GD 5446 (rev 45),pci位置是00:0b.0
當時我把16進位的00:0b.0改成10進位的0:11:0寫進xorg.conf就成功了:
Section "Device"
Identifier "Cirrus Logic GD 5446"
Driver "cirrus"
BusID "PCI:0:11:0"
VideoRam 2048
EndSection

你可以試試看

可是我的是0000:00:0c.0耶，
要怎麼換算成10進位的呢?

[訪客]

可是我的是0000:00:0c.0耶，
要怎麼換算成10進位的呢?

ㄟ...怎麼這多位?
那你這幾個都試看看好了:
PCI:0:0:12:0
PCI:0:12:0
PCI:0:0:12

[KTC]

可是我的是0000:00:0c.0耶，
要怎麼換算成10進位的呢?

ㄟ...怎麼這多位?
那你這幾個都試看看好了:
PCI:0:0:12:0
PCI:0:12:0
PCI:0:0:12

都試過了，
沒有效，
跑出來的還是以上的錯誤訊息.....

我下達lspci後，
其中VGA那一項如下：
0000:00:0c.0 VGA compatible unclassified device: S3 Inc. 86c864 [Vision 864 DRAM] vers 0

還有啊，
如何知道自己VGA的RAM大小呢?

還有我的是XF86Config的，
不是Xorg的。

[訪客]

先試 vesa 再試 S3、S3virge

VRAM 不用設

[KTC]

已經弄好了。
我執行dpkg-reconfigure xserver-xfree86後設定為VESA的驅動後，
再把Bus ID改成PCI:0:12:0後，
就可以執行KDE了。

多謝各位!