Alexander Morgenstern schrieb am Montag, 28. Februar 2005 04:21:
Hallo Falk,
Ich hatte mal ein ähnliches Problem - allerdings benutze ich noch XFree86 (bin Debian-Benutzer).
Hast du zufällig eine nvidia-Karte? Wenn ja welchen Treiber verwendest du für X?
Ich nutze keine nvidia-Karte. Ist ein OnBoard. Habe gerade versucht, heraus zu finden, was es für eine ist. Scheint eine von VIA.
Section "Device" Identifier "Generic Video Card" Driver "nvidia" # ev. ersetzen durch: Driver "nv" EndSection
Section "Device" Identifier "VESA Framebuffer" Driver "vesa" #VideoRam 4096 # Insert Clocks lines here if appropriate EndSection
Falls dir das alles nicht weiterhilft liegt's wahrscheinlich an was anderem (und ich hab wieder mal zu viel geschrieben). Du solltest dann mal etwas genauer werden zum Beispiel 'nen relevanten Ausschnitt des syslog (/var/log/syslog*) und das xorg-logs (wahrscheinlich /var/log/*Xorg*.*.log ?) zeigen.
Hier mal einige logs.
/var/log/syslog:
Feb 25 16:49:21 voyager kernel: agpgart: Unsupported Via chipset (device id: 0605), you might want to try agp_try_unsupported=1. Feb 25 16:49:24 voyager kernel: shpchp: shpc_init : shpc_cap_offset == 0 Feb 25 16:49:24 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device Feb 25 16:49:24 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg Feb 25 16:49:24 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed Feb 25 16:49:24 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device Feb 25 16:49:24 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg Feb 25 16:49:24 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed Feb 25 16:49:24 voyager kernel: shpchp: shpc_init : shpc_cap_offset == 0 Feb 25 16:49:24 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device Feb 25 16:49:24 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg Feb 25 16:49:24 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed Feb 25 16:49:24 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device Feb 25 16:49:24 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg Feb 25 16:49:24 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed Feb 25 16:49:24 voyager kernel: shpchp: shpc_init : shpc_cap_offset == 0 Feb 25 16:49:24 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device Feb 25 16:49:24 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg Feb 25 16:49:24 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed Feb 25 16:49:24 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device Feb 25 16:49:24 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg Feb 25 16:49:24 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed Feb 25 16:49:25 voyager kernel: shpchp: shpc_init : shpc_cap_offset == 0 Feb 25 16:49:25 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device Feb 25 16:49:25 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg Feb 25 16:49:25 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed Feb 25 16:49:25 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device Feb 25 16:49:25 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg Feb 25 16:49:25 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed Feb 25 16:49:25 voyager kernel: shpchp: shpc_init : shpc_cap_offset == 0 Feb 25 16:49:25 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device Feb 25 16:49:25 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg Feb 25 16:49:25 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed Feb 25 16:49:25 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device Feb 25 16:49:25 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg Feb 25 16:49:25 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed Feb 25 16:49:26 voyager kernel: shpchp: shpc_init : shpc_cap_offset == 0 Feb 25 16:49:26 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device Feb 25 16:49:26 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg Feb 25 16:49:26 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed Feb 25 16:49:26 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device Feb 25 16:49:26 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg Feb 25 16:49:26 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed Feb 25 16:49:26 voyager kernel: shpchp: shpc_init : shpc_cap_offset == 0 Feb 25 16:49:26 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device Feb 25 16:49:26 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg Feb 25 16:49:26 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed Feb 25 16:49:26 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device Feb 25 16:49:26 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg Feb 25 16:49:26 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed Feb 25 16:49:26 voyager kernel: shpchp: shpc_init : shpc_cap_offset == 0 Feb 25 16:49:26 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device Feb 25 16:49:26 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg Feb 25 16:49:26 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed Feb 25 16:49:26 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device Feb 25 16:49:26 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg Feb 25 16:49:26 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed Feb 25 16:49:27 voyager kernel: shpchp: shpc_init : shpc_cap_offset == 0 Feb 25 16:49:27 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: init_module: No such device Feb 25 16:49:27 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg Feb 25 16:49:27 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/shpchp.o.gz: insmod shpchp failed Feb 25 16:49:28 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: init_module: No such device Feb 25 16:49:28 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg Feb 25 16:49:28 voyager insmod: /lib/modules/2.4.29/kernel/drivers/hotplug/pciehp.o.gz: insmod pciehp failed Feb 25 17:02:18 voyager kernel: Linux version 2.4.29 (root@midas) (gcc version 3.3.4) #6 Thu Jan 20 16:30:37 PST 2005
scheint so, als ob ich meinen eigenen Kernel backen muss ...
/var/log/Xorg.0.log
II) VESA(0): VESA BIOS detected (II) VESA(0): VESA VBE Version 3.0 (II) VESA(0): VESA VBE Total Mem: 8192 kB (II) VESA(0): VESA VBE OEM: S3 Incorporated. Savage4 (II) VESA(0): VESA VBE OEM Software Rev: 2.0 (II) VESA(0): VESA VBE OEM Vendor: S3 Incorporated. (II) VESA(0): VESA VBE OEM Product: Savage4 (II) VESA(0): VESA VBE OEM Product Rev: Rev B
Aha, VIA Savage4 mit S3-Treiber.
Mein Vorgehen müsste jetzt also sein, einen eigenen Kernel zu backen und Xorg meine Grafikkarte beizubringen. Oder gibts eine andere Möglichkeit?
Ich habe mich noch nie mit X beschäftigen müssen und bin derzeit geistig nicht ganz da, deshalb bitte Tschuldigung für meine Fragen.
Falk