On 2014-11-17 08:58, Dag-Erling Smørgrav wrote:
> Dag-Erling Smørgrav writes:
>> Steve Kargl 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 ex
Dag-Erling Smørgrav writes:
> Steve Kargl 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
Steve Kargl 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 further suspect that the problem
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 s
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
... or since you can ssh into the thing, try as root:
procstat -ka
-adrian
On 16 November 2014 11:33, Hans Petter Selasky 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 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 wrote:
On Sun, Nov 16, 2014 at 06:55:53PM +, Mark R V Murray wrote:
On 16 Nov 2014, at 18:51, Steve Kargl wrote:
If you have not read the entire thr
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
> >>> wrote:
> >>>
> >>> If you have not read the entire thread, once
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 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,
it ha
On Sun, Nov 16, 2014 at 06:55:53PM +, Mark R V Murray wrote:
>
> > On 16 Nov 2014, at 18:51, Steve Kargl
> > 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,
> > it hangs, ^T tells m
> On 16 Nov 2014, at 18:51, Steve Kargl
> 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 know why, so this m
On Sun, Nov 16, 2014 at 06:34:42PM +, Mark R V Murray wrote:
>
> > On 16 Nov 2014, at 18:31, Ian Lepore 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
> On 16 Nov 2014, at 18:31, Ian Lepore 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 bisected the
On Sun, 2014-11-16 at 18:23 +, Mark R V Murray wrote:
> > On 16 Nov 2014, at 18:21, Ian Lepore wrote:
> >
> > On Sun, 2014-11-16 at 18:17 +, Mark R V Murray wrote:
> >>> On 16 Nov 2014, at 17:51, Steve Kargl
> >>> wrote:
> >>>
> >>> Is there a 'random: device_detach():' missing between
> On 16 Nov 2014, at 18:21, Ian Lepore wrote:
>
> On Sun, 2014-11-16 at 18:17 +, Mark R V Murray wrote:
>>> On 16 Nov 2014, at 17:51, Steve Kargl
>>> wrote:
>>>
>>> Is there a 'random: device_detach():' missing between the 'umass0'
>>> and 'da0' messages in the last 4 lines.
>>
>> No. At
On Sun, 2014-11-16 at 18:17 +, Mark R V Murray wrote:
> > On 16 Nov 2014, at 17:51, Steve Kargl
> > 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 deta
> On 16 Nov 2014, at 17:51, Steve Kargl
> 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 Murray
_
On Sat, Nov 15, 2014 at 09:44:18PM -0800, Adrian Chadd wrote:
> On 15 November 2014 21:41, Steve Kargl
> 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 Sat, Nov 15, 2014 at 09:44:18PM -0800, Adrian Chadd wrote:
> On 15 November 2014 21:41, Steve Kargl
> 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 15 November 2014 21:41, Steve Kargl
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, Steve Kargl 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, Steve Kargl wrote:
> > >> On Thu, Nov 13, 2014 at 09:25:33AM -0800, Steve Kar
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
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
iss
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. Nei
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
CCing hps and mav..
> On Nov 13, 2014, at 09:25, 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.
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 06:27:13PM -0800, Chris H wrote:
> On Wed, 12 Nov 2014 18:08:52 -0800 Steve Kargl
> 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
> > > wrote
> > >
> > > > I run 'make delete-old' and 'make delet
On Wed, Nov 12, 2014 at 6:43 PM, NGie Cooper wrote:
> On Wed, Nov 12, 2014 at 6:27 PM, Chris H 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/handbo
On Wed, Nov 12, 2014 at 6:27 PM, Chris H 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 not trying to be ar
On Wed, 12 Nov 2014 18:08:52 -0800 Steve Kargl
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
> > wrote
> >
> > > I run 'make delete-old' and 'make delete-old-libs' after
> > > each installworld. In this case, I was upgradin
On Wed, Nov 12, 2014 at 06:03:43PM -0800, Chris H wrote:
> On Wed, 12 Nov 2014 15:26:55 -0800 Steve Kargl
> 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 procedure I use is
> >
> > cd
On Wed, 12 Nov 2014 15:26:55 -0800 Steve Kargl
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
> > wrote:
> > > I have a kernel/world from r274273 sources, which is exhibiting a new
> > > issue on my old laptop. Neither 'shut
On Wed, Nov 12, 2014 at 03:12:46PM -0800, NGie Cooper wrote:
> On Wed, Nov 12, 2014 at 2:42 PM, 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 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 2:42 PM, 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
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 wi
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
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 compil
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 /dev
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
___
[EMA
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 machi
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 prep
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.
> > > >
> > > > -Na
> 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 anyw
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 fi
> 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
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
http://lists.freebsd.org/mailman/listinfo/fre
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 1
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-0x3f
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 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
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
> > > prob
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 t
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 r
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: exited
> > 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 sy
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
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;
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
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,
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
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
there
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 st
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
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
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: can't assign resources (port)
# 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.
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.
header by the difference of the
checksums in the DSDT_old and DSDT_new (0x10 in this
particular case).
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 provid
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
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
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 l
89 matches
Mail list logo