say how it would affect others.
I'm still using your patch (on 2.6.24-rc8 now) but I'll test whatever
other solutions you folks may come up with.
Mike Houston
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More m
still using your patch (on 2.6.24-rc8 now) but I'll test whatever
other solutions you folks may come up with.
Mike Houston
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo
d
My sensors work.
Thanks for this patch,
Mike Houston
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
for me.
From /proc/ioports:
0290-029f : pnp 00:01
0290-0294 : pnp 00:01
0295-0296 : it87
0295-0296 : it87
From dmesg:
system 00:01: ioport range 0x290-0x29f has been reserved
...
system 00:01: ioport range 0x290-0x294 has been reserved
My sensors work.
Thanks for this patch,
Mike Houston
r me.
Now, in dmesg, I get:
system 00:01: ioport range 0x290-0x29f has been reserved
(...)
system 00:01: ioport range 0x290-0x294 could not be reserved
In /proc/ioports I see:
0290-029f : pnp 00:01
0290-0297 : it87
0290-0297 : it87
The it87 sensor now works without disabling acpipnp
Mike H
if it could access that it87 chip or not.
So this pretty much confirms that it's a motherboard/bios issue.
Mike Houston
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.
-e003 : :00:1f.2
e400-e41f : 0000:00:1f.2
Mike Houston
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
roducts/Motherboard/Products_Overview.aspx?ProductID=2456
Unfortunately, there has been no change to the situation. The same
ioport ranges are being reserved when booting with 2.6.24-rc4 and
it87 does not work. No change to the situation in 2.6.23.9 either, the
io conflict is not occuring and it87
to the situation. The same
ioport ranges are being reserved when booting with 2.6.24-rc4 and
it87 does not work. No change to the situation in 2.6.23.9 either, the
io conflict is not occuring and it87 still works there.
Mike Houston
--
To unsubscribe from this list: send the line unsubscribe linux
e400-e41f : :00:1f.2
Mike Houston
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
this pretty much confirms that it's a motherboard/bios issue.
Mike Houston
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http
range 0x290-0x29f has been reserved
(...)
system 00:01: ioport range 0x290-0x294 could not be reserved
In /proc/ioports I see:
0290-029f : pnp 00:01
0290-0297 : it87
0290-0297 : it87
The it87 sensor now works without disabling acpipnp
Mike Houston
--
To unsubscribe from this list: send
On Sun, 9 Dec 2007 01:05:54 +0100
Adrian Bunk <[EMAIL PROTECTED]> wrote:
> On Tue, Dec 04, 2007 at 09:51:54PM -0500, Mike Houston wrote:
> > I finally got around to testing Linux 2.6.24 (2.6.24-rc4) and
> > found that the it87 driver fails to probe and consequently, my
>
On Sun, 9 Dec 2007 01:05:54 +0100
Adrian Bunk [EMAIL PROTECTED] wrote:
On Tue, Dec 04, 2007 at 09:51:54PM -0500, Mike Houston wrote:
I finally got around to testing Linux 2.6.24 (2.6.24-rc4) and
found that the it87 driver fails to probe and consequently, my
sensors no longer work
-2.6.24-rc4.txt
Thanks for any help or suggestions,
Mike Houston
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
-2.6.24-rc4.txt
Thanks for any help or suggestions,
Mike Houston
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
"move acpi_sleep_prepare outside of CONFIG_SUSPEND" and the last
"ACPI: suspend: fix ACPI_SLEEP states"
Thanks Alexey and Rafael.
Mike Houston
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo
and the last
ACPI: suspend: fix ACPI_SLEEP states
Thanks Alexey and Rafael.
Mike Houston
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http
eta driver if applicable.
To build nvidia kernel module failed in
kernel-2.6.23-0.41.rc0.git14.fc8
http://www.nvnews.net/vbulletin/showthread.php?t=95296
Mike Houston
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTE
kernel module failed in
kernel-2.6.23-0.41.rc0.git14.fc8
http://www.nvnews.net/vbulletin/showthread.php?t=95296
Mike Houston
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org
On Mon, 28 May 2007 12:11:35 +0200
"Michal Piotrowski" <[EMAIL PROTECTED]> wrote:
> Hi Mike,
>
> On 27/05/07, Mike Houston <[EMAIL PROTECTED]> wrote:
> > While building kernels for vmware guests, I noticed that the
> > paravirt VMI driver in 2.6.22-rc
On Mon, 28 May 2007 12:11:35 +0200
Michal Piotrowski [EMAIL PROTECTED] wrote:
Hi Mike,
On 27/05/07, Mike Houston [EMAIL PROTECTED] wrote:
While building kernels for vmware guests, I noticed that the
paravirt VMI driver in 2.6.22-rc3 does not compile when highmem
support is disabled
: dereferencing pointer to
incomplete type
arch/i386/kernel/vmi.c:441: error: `init_mm' undeclared (first use in
this function)
make[1]: *** [arch/i386/kernel/vmi.o] Error 1
make: *** [arch/i386/kernel] Error 2
This does not occur if himem support is enabled.
Mike Houston
-
To unsubscribe from this list: send
: dereferencing pointer to
incomplete type
arch/i386/kernel/vmi.c:441: error: `init_mm' undeclared (first use in
this function)
make[1]: *** [arch/i386/kernel/vmi.o] Error 1
make: *** [arch/i386/kernel] Error 2
This does not occur if himem support is enabled.
Mike Houston
-
To unsubscribe from this list: send
, but it had no effect
on the problem. The device gets IRQ 16 in Linux without MSI and it
still croaks with the same messages.
Mike Houston
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://
On Wed, 23 May 2007 10:46:05 -0700 (PDT)
Linus Torvalds <[EMAIL PROTECTED]> wrote:
>
>
> On Wed, 23 May 2007, Mike Houston wrote:
> >
> > I still happen to have a Windows Vista install kicking around, so
> > to make sure we're not flogging a dead horse I
On Wed, 23 May 2007 10:46:05 -0700 (PDT)
Linus Torvalds [EMAIL PROTECTED] wrote:
On Wed, 23 May 2007, Mike Houston wrote:
I still happen to have a Windows Vista install kicking around, so
to make sure we're not flogging a dead horse I booted that and
let it set up the yukon2 chip
IRQ 16 in Linux without MSI and it
still croaks with the same messages.
Mike Houston
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http
to have a Windows Vista install kicking around, so to
make sure we're not flogging a dead horse I booted that and let it
set up the yukon2 chip and I tested it. (more to make sure that
eeprom update didn't break it). I used it for a bit and successfully
transferred some large files from box running
the yukon2 chip and I tested it. (more to make sure that
eeprom update didn't break it). I used it for a bit and successfully
transferred some large files from box running Samba. MS must be using
some specific workaround or something.
Mike Houston
-
To unsubscribe from this list: send the line
grab the dmesg output from the last
attempt to use sky2 on my normal (from scratch) system in case it
would be useful. This is not to be confused with the PATA experiment
above:
http://www.mikeserv.org/files/dmesg-2.6.22-rc2.txt
Mike Houston
-
To unsubscribe from this list: send the line "unsu
from the last
attempt to use sky2 on my normal (from scratch) system in case it
would be useful. This is not to be confused with the PATA experiment
above:
http://www.mikeserv.org/files/dmesg-2.6.22-rc2.txt
Mike Houston
-
To unsubscribe from this list: send the line unsubscribe linux-kernel
On Mon, 21 May 2007 10:37:55 -0700
Stephen Hemminger <[EMAIL PROTECTED]> wrote:
> On Mon, 21 May 2007 13:10:55 -0400
> Mike Houston <[EMAIL PROTECTED]> wrote:
>
> > On Mon, 21 May 2007 08:45:49 -0700
> > Stephen Hemminger <[EMAIL PROTECTED]> wrote:
>
n't share well.
It works well in that other OS that came with the hardware, but
that's beside the point.
Mike Houston
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordom
that came with the hardware, but
that's beside the point.
Mike Houston
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Mon, 21 May 2007 10:37:55 -0700
Stephen Hemminger [EMAIL PROTECTED] wrote:
On Mon, 21 May 2007 13:10:55 -0400
Mike Houston [EMAIL PROTECTED] wrote:
On Mon, 21 May 2007 08:45:49 -0700
Stephen Hemminger [EMAIL PROTECTED] wrote:
It's almost certainly a problem with the BIOS
fig-2.6.22-rc2
Oh well, back to trusty rtl8139 based PCI card for now.
Thanks for working on this stuff,
Mike Houston
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org
card for now.
Thanks for working on this stuff,
Mike Houston
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Wed, 31 Jan 2007 00:52:15 +0100
Adrian Bunk <[EMAIL PROTECTED]> wrote:
> On Mon, Jan 29, 2007 at 04:04:48PM -0500, Mike Houston wrote:
> > I've been using Adrian's 2.6.16 kernel releases on two internet
> > servers that I look after remotely. One of them is RHEL 4 the
>
On Wed, 31 Jan 2007 00:52:15 +0100
Adrian Bunk [EMAIL PROTECTED] wrote:
On Mon, Jan 29, 2007 at 04:04:48PM -0500, Mike Houston wrote:
I've been using Adrian's 2.6.16 kernel releases on two internet
servers that I look after remotely. One of them is RHEL 4 the
other is Fedora Core 2 (Ensim
erfectly except for the
hald not starting (but that doesn't matter on that server). The stock
RHEL 4 kernels exhibit some awful VM behaviour, with crippling iowait
on that system (mainly php/mysql workload)
Mike Houston
-
To unsubscribe from this list: send the line "unsubscribe linux
for the
hald not starting (but that doesn't matter on that server). The stock
RHEL 4 kernels exhibit some awful VM behaviour, with crippling iowait
on that system (mainly php/mysql workload)
Mike Houston
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
On Thu, 08 Sep 2005 21:27:42 +0200
Andreas Baer <[EMAIL PROTECTED]> wrote:
> I think it's 2TB for the file size and 2e73 for the file system, but
> I don't understand the second reference and the part about the
> CONIFG_LBD. What is exactly the CONFIG_LBD option?
> -
This is "Support for Large
On Thu, 08 Sep 2005 21:27:42 +0200
Andreas Baer [EMAIL PROTECTED] wrote:
I think it's 2TB for the file size and 2e73 for the file system, but
I don't understand the second reference and the part about the
CONIFG_LBD. What is exactly the CONFIG_LBD option?
-
This is Support for Large Block
On Sun, 16 Jan 2005 13:18:23 +0100
Helge Hafting <[EMAIL PROTECTED]> wrote:
> On Sun, Jan 16, 2005 at 06:04:32AM -0500, Jon Smirl wrote:
> > you need to check the output from "modprobe drm debug=1" "modprobe
> > radeon" and see if drm is misidentifying the board as AGP. We
> > don't want to fix
On Sun, 16 Jan 2005 13:18:23 +0100
Helge Hafting [EMAIL PROTECTED] wrote:
On Sun, Jan 16, 2005 at 06:04:32AM -0500, Jon Smirl wrote:
you need to check the output from modprobe drm debug=1 modprobe
radeon and see if drm is misidentifying the board as AGP. We
don't want to fix something if
46 matches
Mail list logo
