From: "Tomasz B±tor" <tomba@bartek.tu.kielce.pl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: What is the SiI 0680 chipset status?
Date: Thu, 4 Sep 2003 12:53:44 +0200 [thread overview]
Message-ID: <20030904105344.GA14315@bartek.tu.kielce.pl> (raw)
In-Reply-To: <1062669964.21777.1.camel@dhcp23.swansea.linux.org.uk>
Witam,
Dnia Thu, Sep 04, 2003 at 11:06:06AM +0100 Alan Cox napisal(a):
> On Iau, 2003-09-04 at 02:42, Tomasz B??tor wrote:
> > It doesn't for me. I have no idea what could I possibly do wrong, but
> > I've tried dozens of possibilities without any luck. Compiling in
> > siimage.c = drive errors, ide2 reset and infinite loop of "lost
> > interrupt" messages at boot time. Without siimage.c compiled and with
> > ide2=xxx ide3=xxx parameters in lilo, disks are visible, but of course
> > there is no DMA.
> >
> > Any ideas?
>
> If you disable both APIC and ACPI support is it any happier ?
Now it's:
CONFIG_X86_GOOD_APIC=y
# CONFIG_X86_UP_APIC is not set
# CONFIG_X86_UP_IOAPIC is not set
# CONFIG_ACPI is not set
At night I'll try turning APIC on (I've never used this before) and disable
it in cmos like Bob said. We'll see.
t.
--
Tomasz Bator e-mail: tomba@bartek.tu.kielce.pl ICQ: 101194886
------ ---- -- - - - - - - - - - - - -- ---- ------
"Today it's a race between programmers making better idiot proof software,
and the universe making better idiots. So far the universe is winning"
next prev parent reply other threads:[~2003-09-04 10:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-02 16:55 What is the SiI 0680 chipset status? Tomasz B±tor
2003-09-03 11:49 ` Alan Cox
2003-09-04 1:42 ` Tomasz B±tor
2003-09-04 10:06 ` Alan Cox
2003-09-04 10:53 ` Tomasz B±tor [this message]
2003-09-04 2:19 ` "bleating edge" " Resident Boxholder
2003-09-03 12:42 ` Sebastian Piecha
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=20030904105344.GA14315@bartek.tu.kielce.pl \
--to=tomba@bartek.tu.kielce.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).