On 16-Oct-2002 John Baldwin wrote:
>
> On 16-Oct-2002 Mitsuru IWASAKI wrote:
>>> > > If still NG, please try the attached patch against SupermicroP3TDE6.asl.
>>> > > # _BBN is bridge bus number, my guess is 0x3. You can try to change it
>>> > > # if failed.
>>> >
>>> > Maybe 0x2 is correct.
>>
Mitsuru IWASAKI writes:
> > > > If still NG, please try the attached patch against SupermicroP3TDE6.asl.
> > > > # _BBN is bridge bus number, my guess is 0x3. You can try to change it
> > > > # if failed.
> > >
> > > Maybe 0x2 is correct.
> >
> > I tried 2, and it seems to work correctl
On 16-Oct-2002 Mitsuru IWASAKI wrote:
>> > > If still NG, please try the attached patch against SupermicroP3TDE6.asl.
>> > > # _BBN is bridge bus number, my guess is 0x3. You can try to change it
>> > > # if failed.
>> >
>> > Maybe 0x2 is correct.
>>
>> I tried 2, and it seems to work correctl
> > > If still NG, please try the attached patch against SupermicroP3TDE6.asl.
> > > # _BBN is bridge bus number, my guess is 0x3. You can try to change it
> > > # if failed.
> >
> > Maybe 0x2 is correct.
>
> I tried 2, and it seems to work correctly now.
>
> Thanks!
Congratulations!
# Now w
--
> > pci3: on pcib2
> > atkbdc0: port 0x64,0x60 irq 1 on acpi0
>
> As I told before, could you change _BBN value in the patch and
> try again?
>
> From: Mitsuru IWASAKI <[EMAIL PROTECTED]>
> Subject: Re: PCI problems with today's cur
-
> before fixup boot-disabled links -
> after fixup boot-disabled links --
> arbitrated configuration -
> pci3: on pcib2
> atkbdc0: port 0x64,0x60 irq 1 on acpi0
As I told before, could you change _BBN value in the patch
On Tue, Oct 15, 2002 at 22:17:53 +0900, Mitsuru IWASAKI wrote:
> Hi,
> > > But never mind, you can force to compile the ASL and generate DSDT;
> > > # iasl -i SupermicroP3TDE6.new.asl
> > > then copy generated acpi_dsdt.aml to /boot/.
> > > # cp acpi_dsdt.aml /boot/
> >
> > Okay, I did that, an
Hi,
> > But never mind, you can force to compile the ASL and generate DSDT;
> > # iasl -i SupermicroP3TDE6.new.asl
> > then copy generated acpi_dsdt.aml to /boot/.
> > # cp acpi_dsdt.aml /boot/
>
> Okay, I did that, and then typed the following at the boot prompt:
>
> set acpi_dsdt_load="YES"
On Sun, Oct 06, 2002 at 14:25:41 +0900, Mitsuru IWASAKI wrote:
> Hi,
>
> > I tried the patches you checked in, and PCI bus 2 on my machine still isn't
> > probed. See the attached dmesg.
> >
> > I'm a bit confused about just what sort of file the ACPI code expects to
> > load on boot.
> >
> >
Hi,
> I tried the patches you checked in, and PCI bus 2 on my machine still isn't
> probed. See the attached dmesg.
>
> I'm a bit confused about just what sort of file the ACPI code expects to
> load on boot.
>
> I installed the acpicatools port, so I've got iasl(1), but it appears to
> have 4
On Sat, Oct 05, 2002 at 12:09:47 +0900, Mitsuru IWASAKI wrote:
> Hi,
>
> > > > Will the patches you just checked in possibly fix the problem? If so, I'll
> > > > cvsup and try them out.
> > >
> > > 99.999%, Yes.
> >
> > Cool! I'll cvsup and try it out.
>
> If still NG, please try the attache
Hi,
> > > Will the patches you just checked in possibly fix the problem? If so, I'll
> > > cvsup and try them out.
> >
> > 99.999%, Yes.
>
> Cool! I'll cvsup and try it out.
If still NG, please try the attached patch against SupermicroP3TDE6.asl.
# _BBN is bridge bus number, my guess is 0x3.
Hi,
> > OK, just committed. Also imported the latest version of ACPI CA.
> >
> > Ken, if your problem still remains with acpi enabled, I'll report this
> > to Intel folks. So, please let me know the result.
>
> Looks like your mail crossed mine on the wire. :)
indeed :)
> I'm having trouble
On Sat, Oct 05, 2002 at 11:22:58 +0900, Mitsuru IWASAKI wrote:
> Hi,
>
> From: John Baldwin <[EMAIL PROTECTED]>
> Subject: RE: PCI problems with today's current
> Date: Fri, 04 Oct 2002 16:03:08 -0400 (EDT)
> Message-ID: <[EMAIL PROTECTED]>
>
>
Hi,
From: John Baldwin <[EMAIL PROTECTED]>
Subject: RE: PCI problems with today's current
Date: Fri, 04 Oct 2002 16:03:08 -0400 (EDT)
Message-ID: <[EMAIL PROTECTED]>
> On 03-Oct-2002 Kenneth D. Merry wrote:
> >
> > I have a Supermicro P3TDE6 motherboard
On Fri, Oct 04, 2002 at 16:03:08 -0400, John Baldwin wrote:
>
> On 03-Oct-2002 Kenneth D. Merry wrote:
> >
> > I have a Supermicro P3TDE6 motherboard (Serverworks HE-SL chipset) that
> > won't boot with today's -current.
> >
> > -current from August 23rd sources boots fine.
> >
> > It looks li
On Fri, Oct 04, 2002 at 18:39:08 -0600, Kenneth D. Merry wrote:
> On Fri, Oct 04, 2002 at 16:03:08 -0400, John Baldwin wrote:
> >
> > On 03-Oct-2002 Kenneth D. Merry wrote:
> > >
> > > I have a Supermicro P3TDE6 motherboard (Serverworks HE-SL chipset) that
> > > won't boot with today's -current.
On Fri, Oct 04, 2002 at 16:03:08 -0400, John Baldwin wrote:
>
> On 03-Oct-2002 Kenneth D. Merry wrote:
> >
> > I have a Supermicro P3TDE6 motherboard (Serverworks HE-SL chipset) that
> > won't boot with today's -current.
> >
> > -current from August 23rd sources boots fine.
> >
> > It looks li
On 03-Oct-2002 Kenneth D. Merry wrote:
>
> I have a Supermicro P3TDE6 motherboard (Serverworks HE-SL chipset) that
> won't boot with today's -current.
>
> -current from August 23rd sources boots fine.
>
> It looks like the PCI bus probe is failing somehow.
>
> I've seen other folks complainin
19 matches
Mail list logo
