# Congratulations, Maxim!
> On Thu, Oct 25, 2001 at 05:13:56PM +0300, Maxim Sobolev wrote:
> >
> > 6. And finally I've put back corrected ACPI table back into
> > BIOS image using CBROM.EXE, flashed resulting BIOS image and
> > voila - the ACPI problem gone. :)
> >
>
> Way cool. :)
Yeah, Maxi
Maxim Sobolev wrote:
> I know several local guys with exactly the same
> bug (some time ago I've convinced some them to swith to -current
> and test/report any problems) and it is very sad to see my efforts
> vanished, especially considering that the source of the problem is
> located and as you s
On Thu, Oct 25, 2001 at 05:13:56PM +0300, Maxim Sobolev wrote:
>
> 6. And finally I've put back corrected ACPI table back into
> BIOS image using CBROM.EXE, flashed resulting BIOS image and
> voila - the ACPI problem gone. :)
>
Way cool. :)
Joe
msg32007/pgp0.pgp
Description: PGP signatur
Mitsuru IWASAKI wrote:
>
> Hi, Maxim. Thanks for reporting and reminding us.
>
> I think this is very difficult to fix, because;
> 1. Basically, this is a bug in BIOS, should be reported to vendor.
> 2. ACPI CA is developed by Intel. We'd like to have less local
> workaround changes as p
Mitsuru IWASAKI wrote:
>
> Hi, Maxim. Thanks for reporting and reminding us.
>
> I think this is very difficult to fix, because;
> 1. Basically, this is a bug in BIOS, should be reported to vendor.
I understood that, but it is a discontinued model, so it is
unlikely that they will bother to p
Hi, Maxim. Thanks for reporting and reminding us.
I think this is very difficult to fix, because;
1. Basically, this is a bug in BIOS, should be reported to vendor.
2. ACPI CA is developed by Intel. We'd like to have less local
workaround changes as possible.
3. I'm not sure whether sugg
>
> > > The problem is still here as of today's kernel. Please do
> > > something about it.
> >
> > Should I reapeat how sad it is that this longstanding
> > problem is being completely ignored by the acpi
> > maintainer(s)?
>
> No, I'd prefer that you found something constructive to do with yo
> > The problem is still here as of today's kernel. Please do
> > something about it.
>
> Should I reapeat how sad it is that this longstanding
> problem is being completely ignored by the acpi
> maintainer(s)?
No, I'd prefer that you found something constructive to do with your time.
I'm not in
Maxim Sobolev wrote:
>
> Maxim Sobolev wrote:
> >
> > Mike Smith wrote:
> >
> > > This just isn't going to work. The _CRS data stream stops at byte 0x17,
> > > and these extra items are simply mis-aimed.
> > >
> > > The 0x19 should really be 0x11, and the 0x1c should really be 0x14, ie.
> > > th
Maxim Sobolev wrote:
>
> Mike Smith wrote:
>
> > This just isn't going to work. The _CRS data stream stops at byte 0x17,
> > and these extra items are simply mis-aimed.
> >
> > The 0x19 should really be 0x11, and the 0x1c should really be 0x14, ie.
> > this is a BIOS bug, and should be reported
Mike Smith wrote:
> This just isn't going to work. The _CRS data stream stops at byte 0x17,
> and these extra items are simply mis-aimed.
>
> The 0x19 should really be 0x11, and the 0x1c should really be 0x14, ie.
> this is a BIOS bug, and should be reported to the vendor. (It should
> also hav
This just isn't going to work. The _CRS data stream stops at byte 0x17,
and these extra items are simply mis-aimed.
The 0x19 should really be 0x11, and the 0x1c should really be 0x14, ie.
this is a BIOS bug, and should be reported to the vendor. (It should
also have failed the Microsoft ACP
>
> Hi, I've just made a workaround for this. Intel folks, could you review
> it as always?
>
> > The problem is here, right?
> > > can't fetch resources for \\_SB_.PCI0.ISA_.FDC0 - AE_AML_BUFFER_LIMIT
> >
> > I'm sure _SB_.PCI0.ISA_.FDC0._CRS (Current Resource Settings) have some
> > problems
Hi, I've just made a workaround for this. Intel folks, could you review
it as always?
> The problem is here, right?
> > can't fetch resources for \\_SB_.PCI0.ISA_.FDC0 - AE_AML_BUFFER_LIMIT
>
> I'm sure _SB_.PCI0.ISA_.FDC0._CRS (Current Resource Settings) have some
> problems (not sure in BIOS
Hi,
> > I'm not sure exactly what's the problem you are having, but it's too
> > little information to track it down...
> > Could you send [EMAIL PROTECTED] ;
> > - acpidump output; like
> ># acpidump -o your_machine_name.dsdt > your_machine_name.dsdt.asl
> > I'll add them to
> > http://
Mitsuru IWASAKI wrote:
> Hi,
>
> > Maxim Sobolev wrote:
> >
> > > Maxim Sobolev wrote:
> > >
> > > > "Andrey A. Chernov" wrote:
> > > >
> > > > > On Mon, Sep 17, 2001 at 16:26:20 +0300, Maxim Sobolev wrote:
> > > > > > Hi,
> > > > > >
> > > > > > Finally decided to upgrade my current box to the p
Hi,
> Maxim Sobolev wrote:
>
> > Maxim Sobolev wrote:
> >
> > > "Andrey A. Chernov" wrote:
> > >
> > > > On Mon, Sep 17, 2001 at 16:26:20 +0300, Maxim Sobolev wrote:
> > > > > Hi,
> > > > >
> > > > > Finally decided to upgrade my current box to the post-ACPI/KSE and found
> > > > > that I'm havi
Maxim Sobolev wrote:
> Maxim Sobolev wrote:
>
> > "Andrey A. Chernov" wrote:
> >
> > > On Mon, Sep 17, 2001 at 16:26:20 +0300, Maxim Sobolev wrote:
> > > > Hi,
> > > >
> > > > Finally decided to upgrade my current box to the post-ACPI/KSE and found
> > > > that I'm having problem with resource al
"Andrey A. Chernov" wrote:
> On Mon, Sep 17, 2001 at 16:26:20 +0300, Maxim Sobolev wrote:
> > Hi,
> >
> > Finally decided to upgrade my current box to the post-ACPI/KSE and found
> > that I'm having problem with resource allocation for floppy disk controller.
> > I'm sure somebody already reporte
On Mon, Sep 17, 2001 at 16:26:20 +0300, Maxim Sobolev wrote:
> Hi,
>
> Finally decided to upgrade my current box to the post-ACPI/KSE and found
> that I'm having problem with resource allocation for floppy disk controller.
> I'm sure somebody already reported this some time ago, but the problems
20 matches
Mail list logo
