Re: Bildschirm an KVM-Switch zuerst vorhanden, beim starten vonWheezykein Bild mehr

12/10/2014 - 13:20 von Alexander Albert | Report spam
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.


Danke für die Antworten bisher, leider haben die das Problem bisher nicht gelöst.

Aus der Log-Datei /var/log/messages habe ich mal die Zeilen direkt nach den letzten Zeilen die ich noch sehen kann unten aufgelistet.

Oct 12 11:46:15 server4 kernel: [ 28.239130] md1: unknown partition table
Oct 12 11:46:15 server4 kernel: [ 28.440577] device-mapper: uevent: version 1.0.3
Oct 12 11:46:15 server4 kernel: [ 28.440619] device-mapper: ioctl: 4.22.0-ioctl (2011-10-19) initialised: dm-devel@redhat.com<mailto:dm-devel@redhat..com>
Oct 12 11:46:15 server4 kernel: [ 28.654311] PM: Starting manual resume from disk
Oct 12 11:46:15 server4 kernel: [ 28.711674] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Oct 12 11:46:15 server4 kernel: [ 30.910881] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
Oct 12 11:46:15 server4 kernel: [ 30.910886] ACPI: Power Button [PWRB]
Oct 12 11:46:15 server4 kernel: [ 30.910921] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
Oct 12 11:46:15 server4 kernel: [ 30.910923] ACPI: Power Button [PWRF]
Oct 12 11:46:15 server4 kernel: [ 30.991161] iTCO_vendor_support: vendor-support=0
Oct 12 11:46:15 server4 kernel: [ 30.991765] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07
Oct 12 11:46:15 server4 kernel: [ 30.991815] iTCO_wdt: Found a Cougar Point TCO device (Version=2, TCOBASE=0x0460)
Oct 12 11:46:15 server4 kernel: [ 30.991855] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
Oct 12 11:46:15 server4 kernel: [ 31.027032] [drm] Initialized drm 1.1.0 20060810
Oct 12 11:46:15 server4 kernel: [ 31.100312] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni)
Oct 12 11:46:15 server4 kernel: [ 31.115888] input: PC Speaker as /devices/platform/pcspkr/input/input3
Oct 12 11:46:15 server4 kernel: [ 31.228671] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver
Oct 12 11:46:15 server4 kernel: [ 31.228686] Console: switching to colour dummy device 80x25
Oct 12 11:46:15 server4 kernel: [ 31.252150] mtrr: type mismatch for c0000000,10000000 old: write-back new: write-combining
Oct 12 11:46:15 server4 kernel: [ 31.252152] [drm] MTRR allocation failed.. Graphics performance may suffer.
Oct 12 11:46:15 server4 kernel: [ 31.252272] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
Oct 12 11:46:15 server4 kernel: [ 31.252273] [drm] Driver supports precise vblank timestamp query.
Oct 12 11:46:15 server4 kernel: [ 31.252296] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
Oct 12 11:46:15 server4 kernel: [ 31.355423] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
Oct 12 11:46:15 server4 kernel: [ 31.545262] No connectors reported connected with modes
Oct 12 11:46:15 server4 kernel: [ 31.545266] [drm] Cannot find any crtc or sizes - going 1024x768
Oct 12 11:46:15 server4 kernel: [ 31.547882] fbcon: inteldrmfb (fb0) is primary device
Oct 12 11:46:15 server4 kernel: [ 31.547937] Console: switching to colour frame buffer device 128x48
Oct 12 11:46:15 server4 kernel: [ 31.549692] fb0: inteldrmfb frame buffer device
Oct 12 11:46:15 server4 kernel: [ 31.549693] drm: registered panic notifier
Oct 12 11:46:15 server4 kernel: [ 31.549702] No ACPI video bus found
Oct 12 11:46:15 server4 kernel: [ 31.549723] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0

Ich denke das Problem liegt an dem inteldrmfb. Wie kann ich das unterbinden?

Danke!

Alex

_______________________________________________________________________________
Virus checked by G Data AntiVirus | Version: AVA 24.4430 dated 11.10.2014

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="GENERATOR" content="MSHTML 11.00.9600.17280">
</head>
<body>
<div><span class="351265310-12102014"><font size="2" face="Arial">Danke für die Antworten bisher, leider haben die das Problem bisher nicht gelöst.
</font></span></div>
<div><span class="351265310-12102014"><font size="2" face="Arial"></font></span>&nbsp;</div>
<div><span class="351265310-12102014"><font size="2" face="Arial">Aus der Log-Datei /var/log/messages habe ich mal die Zeilen direkt nach den letzten Zeilen die ich noch sehen kann unten aufgelistet.
</font></span></div>
<div><span class="351265310-12102014"><font size="2" face="Arial"></font></span>&nbsp;</div>
<div><span class="351265310-12102014"><font size="2" face="Arial">Oct 12 11:46:15 server4 kernel: [&nbsp;&nbsp; 28.239130]&nbsp; md1: unknown partition table<br>
Oct 12 11:46:15 server4 kernel: [&nbsp;&nbsp; 28.440577] device-mapper: uevent: version 1.0.3<br>
Oct 12 11:46:15 server4 kernel: [&nbsp;&nbsp; 28.440619] device-mapper: ioctl: 4.22.0-ioctl (2011-10-19) initialised:
<a href="mailto:dm-devel@redhat.com">dm-devel@redhat.com</a><br>
Oct 12 11:46:15 server4 kernel: [&nbsp;&nbsp; 28.654311] PM: Starting manual resume from disk<br>
Oct 12 11:46:15 server4 kernel: [&nbsp;&nbsp; 28.711674] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)<br>
Oct 12 11:46:15 server4 kernel: [&nbsp;&nbsp; 30.910881] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1<br>
Oct 12 11:46:15 server4 kernel: [&nbsp;&nbsp; 30.910886] ACPI: Power Button [PWRB]<br>
Oct 12 11:46:15 server4 kernel: [&nbsp;&nbsp; 30.910921] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2<br>
Oct 12 11:46:15 server4 kernel: [&nbsp;&nbsp; 30.910923] ACPI: Power Button [PWRF]<br>
Oct 12 11:46:15 server4 kernel: [&nbsp;&nbsp; 30.991161] iTCO_vendor_support: vendor-support=0<br>
Oct 12 11:46:15 server4 kernel: [&nbsp;&nbsp; 30.991765] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07<br>
Oct 12 11:46:15 server4 kernel: [&nbsp;&nbsp; 30.991815] iTCO_wdt: Found a Cougar Point TCO device (Version=2, TCOBASE=0x0460)<br>
Oct 12 11:46:15 server4 kernel: [&nbsp;&nbsp; 30.991855] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)<br>
Oct 12 11:46:15 server4 kernel: [&nbsp;&nbsp; 31.027032] [drm] Initialized drm 1.1.0 20060810<br>
Oct 12 11:46:15 server4 kernel: [&nbsp;&nbsp; 31.100312] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni)<br>
Oct 12 11:46:15 server4 kernel: [&nbsp;&nbsp; 31.115888] input: PC Speaker as /devices/platform/pcspkr/input/input3<br>
Oct 12 11:46:15 server4 kernel: [&nbsp;&nbsp; 31.228671] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver<br>
Oct 12 11:46:15 server4 kernel: [&nbsp;&nbsp; 31.228686] Console: switching to colour dummy device 80x25<br>
Oct 12 11:46:15 server4 kernel: [&nbsp;&nbsp; 31.252150] mtrr: type mismatch for c0000000,10000000 old: write-back new: write-combining<br>
Oct 12 11:46:15 server4 kernel: [&nbsp;&nbsp; 31.252152] [drm] MTRR allocation failed.&nbsp; Graphics performance may suffer.<br>
Oct 12 11:46:15 server4 kernel: [&nbsp;&nbsp; 31.252272] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).<br>
Oct 12 11:46:15 server4 kernel: [&nbsp;&nbsp; 31.252273] [drm] Driver supports precise vblank timestamp query.<br>
Oct 12 11:46:15 server4 kernel: [&nbsp;&nbsp; 31.252296] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io&#43;mem,decodes=io&#43;mem:owns=io&#43;mem<br>
Oct 12 11:46:15 server4 kernel: [&nbsp;&nbsp; 31.355423] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off<br>
Oct 12 11:46:15 server4 kernel: [&nbsp;&nbsp; 31.545262] No connectors reported connected with modes<br>
Oct 12 11:46:15 server4 kernel: [&nbsp;&nbsp; 31.545266] [drm] Cannot find any crtc or sizes - going 1024x768<br>
Oct 12 11:46:15 server4 kernel: [&nbsp;&nbsp; 31.547882] fbcon: inteldrmfb (fb0) is primary device<br>
Oct 12 11:46:15 server4 kernel: [&nbsp;&nbsp; 31.547937] Console: switching to colour frame buffer device 128x48<br>
Oct 12 11:46:15 server4 kernel: [&nbsp;&nbsp; 31.549692] fb0: inteldrmfb frame buffer device<br>
Oct 12 11:46:15 server4 kernel: [&nbsp;&nbsp; 31.549693] drm: registered panic notifier<br>
Oct 12 11:46:15 server4 kernel: [&nbsp;&nbsp; 31.549702] No ACPI video bus found<br>
Oct 12 11:46:15 server4 kernel: [&nbsp;&nbsp; 31.549723] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0</font></span></div>
<div><span class="351265310-12102014"><font size="2" face="Arial"></font></span>&nbsp;</div>
<div><span class="351265310-12102014"><font size="2" face="Arial">Ich denke das Problem liegt an dem inteldrmfb. Wie kann ich das unterbinden?</font></span></div>
<div><font face="Calibri"></font>&nbsp;</div>
<div><span class="351265310-12102014"><font face="Calibri">Danke!</font></span></div>
<div><span class="351265310-12102014"><font face="Calibri"></font></span>&nbsp;</div>
<div><span class="351265310-12102014"><font face="Calibri">Alex</font></span></div>
<BR>
_______________________________________________________________________________<BR>
Virus checked by G Data AntiVirus | Version: AVA 24.4430 dated 11.10.2014<BR>
</body>
</html>


Zum AUSTRAGEN schicken Sie eine Mail an debian-user-german-REQUEST@lists.debian.org
mit dem Subject "unsubscribe". Probleme? Mail an listmaster@lists.debian.org (engl)
Archive: https://lists.debian.org/1902D2C0F2...425C61CACD@GC-DOMAIN.goecom.local
 

Lesen sie die antworten

#1 Marco Maske
12/10/2014 - 14:10 | Warnen spam
Alexander Albert schrieb:

Bitte im thread reply'en (Reply-To: Header fehlt) und kein html an die Liste.

Ich denke das Problem liegt an dem inteldrmfb. Wie kann ich das
unterbinden?


Kernelkomandline: 'nomodeset' tut das für alle Grafic-chips.

https://wiki.debian.org/KernelModesetting


PS:
Ich vergaß im letzen Post:
Bei meiner KVM-switch Monitor Kombi, benötige ich auch modelines in
der 'xorg.conf'.

Ciao Marco!

Das, was heute als Wachstum propagiert wird, ist der Wohlstandsverlust
der Zukunft. Weil es die natürlichen Ressourcen nicht miteinbezieht,
weil es die sozialen Fragen nicht mit einbezieht. Deswegen ist es
zwingend notwendig, hier neu nachzudenken und neue Modelle zu finden.
- O. Tschimpke (NABU-Pràsident)


Zum AUSTRAGEN schicken Sie eine Mail an
mit dem Subject "unsubscribe". Probleme? Mail an (engl)
Archive: https://lists.debian.org/

Ähnliche fragen