From: "Mica Telodico" <maria_libera2000-whZMOeQn8C0@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: lenb-XTxW/v6ovjE2f5eHYArz+9J4WFQ9Qw4wrRtG1Fwl4lA@public.gmane.org
Subject: Re: _CRS returns NULL! message , problems?
Date: Thu, 4 Mar 2004 20:13:06 +0100 (CET) [thread overview]
Message-ID: <20040304191306.61831.qmail@web41902.mail.yahoo.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 960 bytes --]
Sorry for the late answer .
So , my BIOS has a little fault? I may have problems in the future? It's an important fault or just something that you can skip over?
This motherboard is new , and I wouldn't like to know to have done a bad buy :-(
Thanks marcello
Len Brown <lenb-XTxW/v6ovjE2f5eHYArz+9J4WFQ9Qw4wrRtG1Fwl4lA@public.gmane.org> wrote:
On Sun, Feb 29, 2004 at 02:49:42PM +0100, Mica Telodico wrote:
> Hi all,
>
> I'm the owner of a Abit KV7 Motherboard (VIA KT600),
> and I get these messages at the boot time :
>
> _CRS returns NULL! Using IRQ 21 fordevice (PCI
...
>
> what do mean those _CRS returns NULL! ?
>
> Does this message means problems with some hardware?
sub-standard BIOS, but non-fatal error.
it is on my list to hide this error with !acpi_force -- thanks for the reminder.
Sorry
---------------------------------
Yahoo! Mail: 6MB di spazio gratuito, 30MB per i tuoi allegati, l'antivirus, il filtro Anti-spam
[-- Attachment #2: Type: text/html, Size: 1536 bytes --]
next reply other threads:[~2004-03-04 19:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 19:13 Mica Telodico [this message]
[not found] ` <20040304191306.61831.qmail-GkPDygcub42A/QwVtaZbd3CJp6faPEW9@public.gmane.org>
2004-03-06 6:23 ` _CRS returns NULL! message , problems? Len Brown
[not found] ` <1078554200.12991.3193.camel-D2Zvc0uNKG8@public.gmane.org>
2004-03-06 18:12 ` Mica Telodico
-- strict thread matches above, loose matches on Subject: below --
2004-02-29 13:49 Mica Telodico
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=20040304191306.61831.qmail@web41902.mail.yahoo.com \
--to=maria_libera2000-whzmoeqn8c0@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=lenb-XTxW/v6ovjE2f5eHYArz+9J4WFQ9Qw4wrRtG1Fwl4lA@public.gmane.org \
/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