From: Thomas Renninger <trenn@suse.de>
To: Maik Broemme <mbroemme@plusserver.de>
Cc: Christian Birchinger <joker@netswarm.net>,
linux-acpi <linux-acpi@vger.kernel.org>,
Len Brown <lenb@kernel.org>, "Li, Shaohua" <shaohua.li@intel.com>,
ibm-acpi-devel <ibm-acpi-devel@lists.sourceforge.net>
Subject: Re: [PATCH 2/2] Recent Lenovo ThinkPads define a dummy grahpics device, find it and ignore it
Date: Wed, 17 Oct 2007 10:25:37 +0200 [thread overview]
Message-ID: <1192609537.9847.630.camel@queen.suse.de> (raw)
In-Reply-To: <20071016180919.GH7262@bart.intergenia.de>
On Tue, 2007-10-16 at 20:09 +0200, Maik Broemme wrote:
> Hi,
>
> Christian Birchinger <joker@netswarm.net> wrote:
> > On Mon, Oct 15, 2007 at 06:33:15PM +0200, Thomas Renninger wrote:
> > > Recent Lenovo ThinkPads define a dummy grahpics device, find it and ignore it
> >
> > I think it's ok. dmesg says:
> >
> > ACPI: Video device VID not physically connected, ignoring
> > input: Video Bus as /devices/virtual/input/input11
> > ACPI: Video Device [VID] (multi-head: yes rom: no post: no)
> >
>
> No i think thats not enough because not everyone is using the ACPI video
> extension at this moment and at least for my ThinkPad X61 i got:
>
> babyface@bart:~$ ls /proc/acpi/video/VID
> CRT0 DOS DVI0 LCD0 POST POST_info ROM info
> babyface@bart:~$ ls /proc/acpi/video/VID1
> CRT0 DOS DVI0 LCD0 POST POST_info ROM info
>
> input: Video Bus as /devices/virtual/input/input3
> ACPI: Video Device [VID] (multi-head: yes rom: no post: no)
> input: Video Bus as /devices/virtual/input/input4
> ACPI: Video Device [VID1] (multi-head: yes rom: no post: no)
>
> Anyway, also tools like lspci should show you the fake vga device and
> the X.org will complaint about it like:
>
> (WW) intel: No matching Device section for instance (BusID PCI:0:2:1) found
>
> And if you add this section (just for people who want to fix those
> warnings) your X server will no longer start. :) Can someone correct me if
> i am wrong?
Can you send lspci output and check your BIOS version (dmidecode |less,
there should be a string like KEWWT456 and a version, not sure, AFAIK
2.01 should be about the latest...).
Thanks,
Thomas
next prev parent reply other threads:[~2007-10-17 8:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 16:33 [PATCH 2/2] Recent Lenovo ThinkPads define a dummy grahpics device, find it and ignore it Thomas Renninger
[not found] ` <1192465995.9847.587.camel-X8wR35IVlAxolqkO4TVVkw@public.gmane.org>
2007-10-16 17:50 ` Christian Birchinger
2007-10-16 18:09 ` Maik Broemme
2007-10-17 8:25 ` Thomas Renninger [this message]
2007-10-17 10:12 ` Maik Broemme
2007-10-17 10:40 ` Thomas Renninger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1192609537.9847.630.camel@queen.suse.de \
--to=trenn@suse.de \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=joker@netswarm.net \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=mbroemme@plusserver.de \
--cc=shaohua.li@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox