On 2014-11-17 08:58, Dag-Erling Smørgrav wrote:
Dag-Erling Smørgrav d...@des.no writes:
Steve Kargl s...@troutmask.apl.washington.edu writes:
I'll try that tomorrow. But, I now know that this is related to using
hal from ports. If I comment out both enable_dbus and enable_hal in
On Sat, Nov 15, 2014 at 09:44:18PM -0800, Adrian Chadd wrote:
On 15 November 2014 21:41, Steve Kargl s...@troutmask.apl.washington.edu
wrote:
On Thu, Nov 13, 2014 at 01:22:06PM -0800, Steve Kargl wrote:
On Thu, Nov 13, 2014 at 09:34:07PM +0100, Hans Petter Selasky wrote:
On 11/13/14
On 16 Nov 2014, at 17:51, Steve Kargl s...@troutmask.apl.washington.edu
wrote:
Is there a 'random: device_detach():' missing between the 'umass0'
and 'da0' messages in the last 4 lines.
No. At attach time, the RNG grabs some probe entropy. At detach time it does
nothing.
M
--
Mark R V
On Sun, 2014-11-16 at 18:17 +, Mark R V Murray wrote:
On 16 Nov 2014, at 17:51, Steve Kargl s...@troutmask.apl.washington.edu
wrote:
Is there a 'random: device_detach():' missing between the 'umass0'
and 'da0' messages in the last 4 lines.
No. At attach time, the RNG grabs some
On 16 Nov 2014, at 18:21, Ian Lepore i...@freebsd.org wrote:
On Sun, 2014-11-16 at 18:17 +, Mark R V Murray wrote:
On 16 Nov 2014, at 17:51, Steve Kargl s...@troutmask.apl.washington.edu
wrote:
Is there a 'random: device_detach():' missing between the 'umass0'
and 'da0' messages in
On Sun, 2014-11-16 at 18:23 +, Mark R V Murray wrote:
On 16 Nov 2014, at 18:21, Ian Lepore i...@freebsd.org wrote:
On Sun, 2014-11-16 at 18:17 +, Mark R V Murray wrote:
On 16 Nov 2014, at 17:51, Steve Kargl s...@troutmask.apl.washington.edu
wrote:
Is there a 'random:
On 16 Nov 2014, at 18:31, Ian Lepore i...@freebsd.org wrote:
The point I'm trying to make here is that you trimmed away the important
part of the prior messages and replied only to the part where Steve's
debugging efforts were somewhat speculating. The non-speculative part
was where he
On Sun, Nov 16, 2014 at 06:34:42PM +, Mark R V Murray wrote:
On 16 Nov 2014, at 18:31, Ian Lepore i...@freebsd.org wrote:
The point I'm trying to make here is that you trimmed away the important
part of the prior messages and replied only to the part where Steve's
debugging
On 16 Nov 2014, at 18:51, Steve Kargl s...@troutmask.apl.washington.edu
wrote:
I?m sorry my commit caused the problem.
Nothing to be sorry about. This is -current after all.
Thanks :-)
I?m also trying to find out why, but I don?t know enough about USB or
mass-storage devices to
On Sun, Nov 16, 2014 at 06:55:53PM +, Mark R V Murray wrote:
On 16 Nov 2014, at 18:51, Steve Kargl s...@troutmask.apl.washington.edu
wrote:
If you have not read the entire thread, once the laptop keyboard and
video output lock up, I can ssh into the laptop. If I run usbconfig,
On 11/16/14 20:03, Steve Kargl wrote:
On Sun, Nov 16, 2014 at 06:55:53PM +, Mark R V Murray wrote:
On 16 Nov 2014, at 18:51, Steve Kargl s...@troutmask.apl.washington.edu wrote:
If you have not read the entire thread, once the laptop keyboard and
video output lock up, I can ssh into the
On Sun, Nov 16, 2014 at 08:16:36PM +0100, Hans Petter Selasky wrote:
On 11/16/14 20:03, Steve Kargl wrote:
On Sun, Nov 16, 2014 at 06:55:53PM +, Mark R V Murray wrote:
On 16 Nov 2014, at 18:51, Steve Kargl s...@troutmask.apl.washington.edu
wrote:
If you have not read the entire
On 11/16/14 20:29, Steve Kargl wrote:
On Sun, Nov 16, 2014 at 08:16:36PM +0100, Hans Petter Selasky wrote:
On 11/16/14 20:03, Steve Kargl wrote:
On Sun, Nov 16, 2014 at 06:55:53PM +, Mark R V Murray wrote:
On 16 Nov 2014, at 18:51, Steve Kargl s...@troutmask.apl.washington.edu wrote:
... or since you can ssh into the thing, try as root:
procstat -ka
-adrian
On 16 November 2014 11:33, Hans Petter Selasky h...@selasky.org wrote:
On 11/16/14 20:29, Steve Kargl wrote:
On Sun, Nov 16, 2014 at 08:16:36PM +0100, Hans Petter Selasky wrote:
On 11/16/14 20:03, Steve Kargl
On Sun, Nov 16, 2014 at 04:34:38PM -0800, Adrian Chadd wrote:
... or since you can ssh into the thing, try as root:
procstat -ka
I'll try that tomorrow. But, I now know that this is
related to using hal from ports. If I comment out both
enable_dbus and enable_hal in /etc/rc.conf, the
On Sun, Nov 16, 2014 at 08:33:15PM +0100, Hans Petter Selasky wrote:
thread apply all bt
That will give you the backtrace of all threads. Grep for usbconfig, and
figure out which line is causing the problem in the kernel. Then look at
the USB explore threads and see where they are stuck
Steve Kargl s...@troutmask.apl.washington.edu writes:
I'll try that tomorrow. But, I now know that this is related to using
hal from ports. If I comment out both enable_dbus and enable_hal in
/etc/rc.conf, the system works as I would expect (ie., usb now works
for unplugging devices!). I
Dag-Erling Smørgrav d...@des.no writes:
Steve Kargl s...@troutmask.apl.washington.edu writes:
I'll try that tomorrow. But, I now know that this is related to using
hal from ports. If I comment out both enable_dbus and enable_hal in
/etc/rc.conf, the system works as I would expect (ie.,
On Thu, Nov 13, 2014 at 01:22:06PM -0800, Steve Kargl wrote:
On Thu, Nov 13, 2014 at 09:34:07PM +0100, Hans Petter Selasky wrote:
On 11/13/14 19:15, Steve Kargl wrote:
On Thu, Nov 13, 2014 at 10:03:32AM -0800, Steve Kargl wrote:
On Thu, Nov 13, 2014 at 09:25:33AM -0800, Steve Kargl wrote:
On 15 November 2014 21:41, Steve Kargl s...@troutmask.apl.washington.edu
wrote:
On Thu, Nov 13, 2014 at 01:22:06PM -0800, Steve Kargl wrote:
On Thu, Nov 13, 2014 at 09:34:07PM +0100, Hans Petter Selasky wrote:
On 11/13/14 19:15, Steve Kargl wrote:
On Thu, Nov 13, 2014 at 10:03:32AM -0800,
On Sat, Nov 15, 2014 at 09:44:18PM -0800, Adrian Chadd wrote:
On 15 November 2014 21:41, Steve Kargl s...@troutmask.apl.washington.edu
wrote:
On Thu, Nov 13, 2014 at 01:22:06PM -0800, Steve Kargl wrote:
On Thu, Nov 13, 2014 at 09:34:07PM +0100, Hans Petter Selasky wrote:
On 11/13/14
On Wed, Nov 12, 2014 at 02:42:13PM -0800, Steve Kargl wrote:
I have a kernel/world from r274273 sources, which is exhibiting a new
issue on my old laptop. Neither 'shutdown -p now' nor 'shutdown -r now'
work. I get to the end of shutdown and see for example
All buffers synced
Uptime:
CCing hps and mav..
On Nov 13, 2014, at 09:25, Steve Kargl s...@troutmask.apl.washington.edu
wrote:
On Wed, Nov 12, 2014 at 02:42:13PM -0800, Steve Kargl wrote:
I have a kernel/world from r274273 sources, which is exhibiting a new
issue on my old laptop. Neither 'shutdown -p now' nor
On Thu, Nov 13, 2014 at 09:25:33AM -0800, Steve Kargl wrote:
On Wed, Nov 12, 2014 at 02:42:13PM -0800, Steve Kargl wrote:
I have a kernel/world from r274273 sources, which is exhibiting a new
issue on my old laptop. Neither 'shutdown -p now' nor 'shutdown -r now'
work. I get to the end of
On Thu, Nov 13, 2014 at 10:03:32AM -0800, Steve Kargl wrote:
On Thu, Nov 13, 2014 at 09:25:33AM -0800, Steve Kargl wrote:
On Wed, Nov 12, 2014 at 02:42:13PM -0800, Steve Kargl wrote:
I have a kernel/world from r274273 sources, which is exhibiting a new
issue on my old laptop. Neither
On 11/13/14 19:15, Steve Kargl wrote:
On Thu, Nov 13, 2014 at 10:03:32AM -0800, Steve Kargl wrote:
On Thu, Nov 13, 2014 at 09:25:33AM -0800, Steve Kargl wrote:
On Wed, Nov 12, 2014 at 02:42:13PM -0800, Steve Kargl wrote:
I have a kernel/world from r274273 sources, which is exhibiting a new
On Thu, Nov 13, 2014 at 09:34:07PM +0100, Hans Petter Selasky wrote:
On 11/13/14 19:15, Steve Kargl wrote:
On Thu, Nov 13, 2014 at 10:03:32AM -0800, Steve Kargl wrote:
On Thu, Nov 13, 2014 at 09:25:33AM -0800, Steve Kargl wrote:
On Wed, Nov 12, 2014 at 02:42:13PM -0800, Steve Kargl wrote:
I have a kernel/world from r274273 sources, which is exhibiting a new
issue on my old laptop. Neither 'shutdown -p now' nor 'shutdown -r now'
work. I get to the end of shutdown and see for example
All buffers synced
Uptime: 4h23m15s
and then the laptop just sits there. It does not power off
On Wed, Nov 12, 2014 at 2:42 PM, Steve Kargl
s...@troutmask.apl.washington.edu wrote:
I have a kernel/world from r274273 sources, which is exhibiting a new
issue on my old laptop. Neither 'shutdown -p now' nor 'shutdown -r now'
work. I get to the end of shutdown and see for example
All
On Wed, Nov 12, 2014 at 02:42:13PM -0800, Steve Kargl wrote:
I have a kernel/world from r274273 sources, which is exhibiting a new
issue on my old laptop. Neither 'shutdown -p now' nor 'shutdown -r now'
work. I get to the end of shutdown and see for example
All buffers synced
Uptime:
On Wed, Nov 12, 2014 at 03:12:46PM -0800, NGie Cooper wrote:
On Wed, Nov 12, 2014 at 2:42 PM, Steve Kargl
s...@troutmask.apl.washington.edu wrote:
I have a kernel/world from r274273 sources, which is exhibiting a new
issue on my old laptop. Neither 'shutdown -p now' nor 'shutdown -r now'
On Wed, 12 Nov 2014 15:26:55 -0800 Steve Kargl
s...@troutmask.apl.washington.edu wrote
On Wed, Nov 12, 2014 at 03:12:46PM -0800, NGie Cooper wrote:
On Wed, Nov 12, 2014 at 2:42 PM, Steve Kargl
s...@troutmask.apl.washington.edu wrote:
I have a kernel/world from r274273 sources, which is
On Wed, Nov 12, 2014 at 06:03:43PM -0800, Chris H wrote:
On Wed, 12 Nov 2014 15:26:55 -0800 Steve Kargl
s...@troutmask.apl.washington.edu wrote
I run 'make delete-old' and 'make delete-old-libs' after
each installworld. In this case, I was upgrading from
r271492 to r274273. The
On Wed, 12 Nov 2014 18:08:52 -0800 Steve Kargl
s...@troutmask.apl.washington.edu wrote
On Wed, Nov 12, 2014 at 06:03:43PM -0800, Chris H wrote:
On Wed, 12 Nov 2014 15:26:55 -0800 Steve Kargl
s...@troutmask.apl.washington.edu wrote
I run 'make delete-old' and 'make delete-old-libs'
On Wed, Nov 12, 2014 at 6:27 PM, Chris H bsd-li...@bsdforge.com wrote:
...
How so? It's been necessary for as long
as I can remember. Just to confirm, I looked to see if anything
had changed:
https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
seems not. Do note; I'm
On Wed, Nov 12, 2014 at 6:43 PM, NGie Cooper yaneurab...@gmail.com wrote:
On Wed, Nov 12, 2014 at 6:27 PM, Chris H bsd-li...@bsdforge.com wrote:
...
How so? It's been necessary for as long
as I can remember. Just to confirm, I looked to see if anything
had changed:
On Wed, Nov 12, 2014 at 06:27:13PM -0800, Chris H wrote:
On Wed, 12 Nov 2014 18:08:52 -0800 Steve Kargl
s...@troutmask.apl.washington.edu wrote
On Wed, Nov 12, 2014 at 06:03:43PM -0800, Chris H wrote:
On Wed, 12 Nov 2014 15:26:55 -0800 Steve Kargl
s...@troutmask.apl.washington.edu
Hi Nate,
On Tuesday 02 December 2003 23:34, Nate Lawson wrote:
Try other states (acpiconf -s 1, 2, 4). If one works, use it. If not,
try disabling acpi and using apm(4) to suspend and resume.
Normally that would be grand, but now that I've not compiled acpi into the
kernel, I have no
On Wed, 3 Dec 2003, Melvyn Sopacua wrote:
On Tuesday 02 December 2003 23:34, Nate Lawson wrote:
Try other states (acpiconf -s 1, 2, 4). If one works, use it. If not,
try disabling acpi and using apm(4) to suspend and resume.
Normally that would be grand, but now that I've not compiled
On Wednesday 03 December 2003 21:57, Nate Lawson wrote:
On Wed, 3 Dec 2003, Melvyn Sopacua wrote:
On Tuesday 02 December 2003 23:34, Nate Lawson wrote:
Try other states (acpiconf -s 1, 2, 4). If one works, use it. If not,
try disabling acpi and using apm(4) to suspend and resume.
Hello,
I have a Sony VAIO PCG-GRX626P, and I'm using a two days old FreeBSD
current, and pretty much everything works, except that when I move
into sleep mode 3 (acpiconf -s 3) I cannot bring my lap back. :-(
The fan starts again, but nothing else happens, after a while I just
power off the
Try other states (acpiconf -s 1, 2, 4). If one works, use it. If not,
try disabling acpi and using apm(4) to suspend and resume.
Suspend/resume is far down my list of things to troubleshoot and most of
the problems are very hw-specific.
-Nate
___
If you are currently having ACPI problems, please submit a PR through the
send-pr mechanism. After you have been assigned a number, please report
it to [EMAIL PROTECTED] Information to include is a full dmesg of
your system and links to the output of:
acpidump -t -d -o my.dsdt my.asl
In
On Thu, 17 Jul 2003, Danny Braniss wrote:
Your asl seems bogus since there are a lot of unexpected values (i.e. for
TZ and EC port values). Since it worked in 4.8R, follow the instructions
for disabling ACPI.
-Nate
thanks, that did it, but now, is there anyway i can help fix
On Fri, 18 Jul 2003, Danny Braniss wrote:
On Thu, 17 Jul 2003, Danny Braniss wrote:
Your asl seems bogus since there are a lot of unexpected values (i.e. for
TZ and EC port values). Since it worked in 4.8R, follow the instructions
for disabling ACPI.
-Nate
thanks, that
Your asl seems bogus since there are a lot of unexpected values (i.e. for
TZ and EC port values). Since it worked in 4.8R, follow the instructions
for disabling ACPI.
-Nate
thanks, that did it, but now, is there anyway i can help fix this so
acpi will work? i have several of this boxes and
On Thu, 17 Jul 2003, Danny Braniss wrote:
Your asl seems bogus since there are a lot of unexpected values (i.e. for
TZ and EC port values). Since it worked in 4.8R, follow the instructions
for disabling ACPI.
-Nate
thanks, that did it, but now, is there anyway i can help fix this so
Your asl seems bogus since there are a lot of unexpected values (i.e. for
TZ and EC port values). Since it worked in 4.8R, follow the instructions
for disabling ACPI.
-Nate
___
[EMAIL PROTECTED] mailing list
hi,
the motherboard is Intel STL2, which works fine with 4.8-stable.
just tried 5.1-current and it hangs on boot:
BIOS drive A: is disk0
BIOS drive C: is disk1
PXE version 2.1, real mode entry point @9d3a:0106
BIOS 637kB/785344kB available memory
FreeBSD/i386 bootstrap loader, Revision
I'm attempting to use an Intel L440GX+ motherboard with 5.x, and am
running into the following problem: when I boot without ACPI, the serial
ports probe, attach, and work fine:
Mar 23 14:21:56 none kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
Mar 23 14:21:56 none kernel: sio0: type
On Sun, 23 Mar 2003, Robert Watson wrote:
When I boot with ACPI, the following appears in dmesg:
Mar 23 14:14:31 none kernel: sio0: configured irq 4 not in bitmap of probed irqs 0
Mar 23 14:14:31 none kernel: sio0: port may not be enabled
Mar 23 14:14:31 none kernel: sio0 port 0x3f8-0x3ff
On Thu, 23 Jan 2003, Bryan Liesner wrote:
On Thu, 23 Jan 2003, Nate Lawson wrote:
On Thu, 23 Jan 2003, Bryan Liesner wrote:
I just upgraded my 4.7 system to 5.0-current via sources. Everything
went smoothly, and I was up and running quickly, but with an acpi related
problem.
On Fri, 24 Jan 2003, Nate Lawson wrote:
On Thu, 23 Jan 2003, Bryan Liesner wrote:
On Thu, 23 Jan 2003, Nate Lawson wrote:
On Thu, 23 Jan 2003, Bryan Liesner wrote:
I just upgraded my 4.7 system to 5.0-current via sources. Everything
went smoothly, and I was up and running
I just upgraded my 4.7 system to 5.0-current via sources. Everything
went smoothly, and I was up and running quickly, but with an acpi related
problem.
When booting, the kernel loads, detects the devices, then hangs right
here:
Mounting root from ufs:/dev/ad0s1a
pid 84 (fsck_ufs), uid 0:
On Thu, 23 Jan 2003, Bryan Liesner wrote:
I just upgraded my 4.7 system to 5.0-current via sources. Everything
went smoothly, and I was up and running quickly, but with an acpi related
problem.
When booting, the kernel loads, detects the devices, then hangs right
here:
Mounting root
On Thu, 23 Jan 2003, Nate Lawson wrote:
On Thu, 23 Jan 2003, Bryan Liesner wrote:
I just upgraded my 4.7 system to 5.0-current via sources. Everything
went smoothly, and I was up and running quickly, but with an acpi related
problem.
When booting, the kernel loads, detects the
Then you'll get thermal operation messages, something like:
Nov 26 19:34:13 mybox kernel: acpi_tz0: _AC0: temperature 60.0 =
setpoint 60.0
Nov 26 19:34:13 mybox kernel: acpi_tz0: switched from NONE to _AC0: 60.0C
We need the messages like this, acpidump output, and sysctl hw.acpi
Mitsuru IWASAKI wrote:
Hi,
Hmm, we need further info. on this.
Please add the following lines into your /boor/loader.conf:
hw.acpi.verbose=1
debug.acpi.layer=ACPI_ALL_COMPONENTS ACPI_BUS
debug.acpi.level=ACPI_LV_WARN ACPI_LV_ERROR ACPI_LV_OBJECTS
Then you'll get thermal
Hello
If I choose to make world under -CURRENT the laptop gets hotter (well
the processor/hd and so on gets used and causes heat) now, the fan
starts to spin faster and so on, but the computer never gets cooler even
a day after a build it still is hot and the fan never stops spinning, is
Hi,
If I choose to make world under -CURRENT the laptop gets hotter (well
the processor/hd and so on gets used and causes heat) now, the fan
starts to spin faster and so on, but the computer never gets cooler even
a day after a build it still is hot and the fan never stops spinning, is
Terry Lambert wrote:
Is this a Dell Lattitude? They are known to have heat problems.
There's also the possibility that the CPU is a desktop CPU in
the laptop; people aren't supposed to do that, either, but it
can crank up the heat.
-- Terry
Hello
No it's a Evo N114 with an Athlon 4 in it,
John Angelmo wrote:
Terry Lambert wrote:
Is this a Dell Lattitude? They are known to have heat problems.
There's also the possibility that the CPU is a desktop CPU in
the laptop; people aren't supposed to do that, either, but it
can crank up the heat.
No it's a Evo N114 with an
Terry Lambert wrote:
Have you applied the most recent ACPI patches, and turned on
debugging output (at least hw.acpi.verbose=1) to see if it
fixes the problem (and if it doesn't, at least report what's
going on)?
It looks like the author of the ACPI code has already replied
to your post;
Hello,
First of all, I do not know much about backtracing,
debugging etc.
I want to use the power key to shutdown the system. It is
compaq evo 300, P4 1.6ghz, 368MB RAM
Yesterday OS was 5.0DP2. I can not power it off. It comes
to a point when it should cut the power off 'System is
shutting down
Ertan Kucukoglu wrote:
I want to use the power key to shutdown the system. It is
compaq evo 300, P4 1.6ghz, 368MB RAM
Yesterday OS was 5.0DP2. I can not power it off. It comes
to a point when it should cut the power off 'System is
shutting down using ACPI' like message is displayed and
On Sat, 23 Nov 2002, Ertan Kucukoglu wrote:
First of all, I do not know much about backtracing, debugging etc.
First advice: we shipped DP2 with two different kernels, the normal kernel
without high debugging features, and then a special debugging kernel
called DEBUG. My first advice when
Hi Folks,
I was unable to boot the kernel for sometime, so I tried doing an
unset acpi_load and the kernel booted fine.
The kernel would hang after reaching Timecounter as show below.
---
Sep 13 18:20:09 calvin kernel: unknown: PNP0501 can't assign resources
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 said
# 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, Maxim is maniac
).
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. :)
If anybody else needs it, I could provide fixed BIOS image
for Tyan-S1590 (Trinity 100AT) mobo, just drop me a note.
Thanks to all who helped
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 signature
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.
this is a BIOS bug, and
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
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
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
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
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 to the
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 have
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
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
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 allocation for floppy disk
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 post-ACPI/KSE and found
that I'm having
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
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 having problem with resource allocation
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 reported this some
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 seems
still here, so I would like to see it resolved.
Thanks!
-Maxim
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
After enabling ACPI in my kernel I get these messages in dmesg:
---snip---
VESA: v2.0, 2496k memory, flags:0x0, mode table:0xc03b82e2 (122)
VESA: MagicGraph 256 AV 44K PRELIMINARY
ACPI-0299: *** Warning: Invalid table signature found
ACPI-0170: *** Error: AcpiLoadTables: Could not
88 matches
Mail list logo
