Kasper Sandberg wrote:
> to put some timeline perspective into this.
> i believe it was in 2005 i assembled the system, and when i realized it
> was faulty, on old ide driver, i stopped using it - that miht have been
> in beginning of 2006. then for almost a year i werent using it, hoping
> to
Kasper Sandberg wrote:
to put some timeline perspective into this.
i believe it was in 2005 i assembled the system, and when i realized it
was faulty, on old ide driver, i stopped using it - that miht have been
in beginning of 2006. then for almost a year i werent using it, hoping
to somehow
Gene Heskett wrote:
I doubt libata has that capability now, or ever will, cuz these ide/atapi
devices are generally dumber than rocks about that. But any device claiming
to be scsi-II is supposed to be able to do those sorts of things while the
cpu is off crunching numbers for BOINC or
> From: [EMAIL PROTECTED]
>>if this works then it really needs to move and be renamed. I am compiling
>> with DEV_SR set.
>>
> That fixed me right up, Adam, & k3b is once again as happy as a clam.
Fixed it for me too. I just realized the default config in 2.6.24 is way
different than the
> By the linux software definition maybe. But I've defined scsi as that which
> uses a 50 wire cable using 50 contact centronics connectors since the
> mid '70's, and which often needs a ready supply of nubile virgins t
25, 50 or 68, with multiple voltage levels, plus of course it might be
On Tuesday 29 January 2008, Alan Cox wrote:
>> That could stand to be moved or renamed, it is well buried in the menu for
>> the REAL scsi stuffs, which I don't have any of.
>
>Yes you do - USB storage and ATAPI are SCSI
By the linux software definition maybe. But I've defined scsi as that which
> I've seen a lot of verbosity out of SCSI messages, but I haven't seen a
> straightforward interpretation of the problem in there. It's all
> information useful for debugging, not information useful for system
> administration.
It tells you what is going on. Unfortunately that frequently
On Tue, 29 Jan 2008, Alan Cox wrote:
> > The SCSI error reporting really ought to include a simple interpretation
> > of the error for end users ("The drive doesn't support this command" "A
> > sector's data got lost" "The drive timed out" "The drive failed" "The
> > drive is entirely gone").
> That could stand to be moved or renamed, it is well buried in the menu for
> the
> REAL scsi stuffs, which I don't have any of.
Yes you do - USB storage and ATAPI are SCSI
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
> The SCSI error reporting really ought to include a simple interpretation
> of the error for end users ("The drive doesn't support this command" "A
> sector's data got lost" "The drive timed out" "The drive failed" "The
> drive is entirely gone"). There's too much similarity between the
On Tuesday 29 January 2008, Jeff Garzik wrote:
>Gene Heskett wrote:
>> On Tuesday 29 January 2008, Jeff Garzik wrote:
>>> Gene Heskett wrote:
Does anyone know why my dvdwriter isn't being assigned a '/dev/sdx'
number when dmesg says its found ok at ata2.00? I've turned on an
option
Mark Lord wrote:
rgheck wrote:
Alan Cox wrote:
not one problem but lots---is sufficiently widespread that a Mini
HOWTO, say, would be really welcome and, I'm guessing, widely used.
We don't see very many libata problems at the distro level and they for
the most part boil down to
-
rgheck wrote:
Mark Lord wrote:
rgheck wrote:
Alan Cox wrote:
not one problem but lots---is sufficiently widespread that a Mini
HOWTO, say, would be really welcome and, I'm guessing, widely used.
We don't see very many libata problems at the distro level and they for
the most part boil
On Tue, 29 Jan 2008, Alan Cox wrote:
> > not one problem but lots---is sufficiently widespread that a Mini HOWTO,
> > say, would be really welcome and, I'm guessing, widely used.
>
> We don't see very many libata problems at the distro level and they for
> the most part boil down to
>
> -
rgheck wrote:
Alan Cox wrote:
not one problem but lots---is sufficiently widespread that a Mini
HOWTO, say, would be really welcome and, I'm guessing, widely used.
We don't see very many libata problems at the distro level and they for
the most part boil down to
- sata_nv with >4GB of
On Tue, 29 Jan 2008, Alan Cox wrote:
> > things in the kernel that refer to SCSI probably should say "storage" (or
> > "ATA", really, but that would make the acronyms confusing).
>
> SCSI is a command protocol. It is what your CD-ROM drive and USB storage
> devices talk (albeit with a bit of an
Gene Heskett wrote:
On Tuesday 29 January 2008, Mark Lord wrote:
Gene Heskett wrote:
..
Does anyone know why my dvdwriter isn't being assigned a '/dev/sdx' number
when dmesg says its found ok at ata2.00? I've turned on an option that
says something about using the bios for device access this
On Tuesday 29 January 2008, Daniel Barkalow wrote:
>On Tue, 29 Jan 2008, Gene Heskett wrote:
>> >For starters, enable CONFIG_BLK_DEV_SR.
>>
>> That could stand to be moved or renamed, it is well buried in the menu for
>> the REAL scsi stuffs, which I don't have any of. Enabled & building now.
>
On Tuesday 29 January 2008, Adam Turk wrote:
>I just found this thread and it looks like it will fix my problem too. I
> have an IDE cd-rw drive and 2 SCSI hard drives. My ide cd-rw drive hasn't
> been showing up. I looked at setting scsi cdrom support
> (CONFIG_BLOCK_DEV_SR) but it doesn't
> things in the kernel that refer to SCSI probably should say "storage" (or
> "ATA", really, but that would make the acronyms confusing).
SCSI is a command protocol. It is what your CD-ROM drive and USB storage
devices talk (albeit with a bit of an accent).
Alan
--
To unsubscribe from this
I just found this thread and it looks like it will fix my problem too. I have
an IDE cd-rw drive and 2 SCSI hard drives. My ide cd-rw drive hasn't been
showing up. I looked at setting scsi cdrom support (CONFIG_BLOCK_DEV_SR) but
it doesn't mention anything about ide drives using libata.
I
On Tue, 29 Jan 2008, Gene Heskett wrote:
> >For starters, enable CONFIG_BLK_DEV_SR.
>
> That could stand to be moved or renamed, it is well buried in the menu for
> the
> REAL scsi stuffs, which I don't have any of. Enabled & building now.
The "SCSI support type (disk, tape, CD-ROM)"
Gene Heskett wrote:
On Tuesday 29 January 2008, Jeff Garzik wrote:
Gene Heskett wrote:
Does anyone know why my dvdwriter isn't being assigned a '/dev/sdx' number
when dmesg says its found ok at ata2.00? I've turned on an option that
says something about using the bios for device access this
> Is this >4GB or >=4GB? I've seen contradictory reports, and I've got 4GB.
Depends how the memory is mapped. Any memory physically above the 4GB
boundary
Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More
On Tuesday 29 January 2008, Jeff Garzik wrote:
>Gene Heskett wrote:
>> Does anyone know why my dvdwriter isn't being assigned a '/dev/sdx' number
>> when dmesg says its found ok at ata2.00? I've turned on an option that
>> says something about using the bios for device access this build, but I'll
Alan Cox wrote:
not one problem but lots---is sufficiently widespread that a Mini HOWTO,
say, would be really welcome and, I'm guessing, widely used.
We don't see very many libata problems at the distro level and they for
the most part boil down to
- sata_nv with >4GB of RAM, knowing
On Tuesday 29 January 2008, Mikael Pettersson wrote:
>Gene Heskett writes:
> > On Tuesday 29 January 2008, Alan Cox wrote:
> > >> As slight change here, I was going to use the same .config as
> > >> 2.6.24-rc8, but just discovered that neither rc8 nor final is finding
> > >> the drivers for my
> >
Gene Heskett wrote:
Does anyone know why my dvdwriter isn't being assigned a '/dev/sdx' number
when dmesg says its found ok at ata2.00? I've turned on an option that says
something about using the bios for device access this build, but I'll be
surprised if that's it. :)
I think you mean
Mark Lord wrote:
Gene Heskett wrote:
..
Does anyone know why my dvdwriter isn't being assigned a '/dev/sdx'
number when dmesg says its found ok at ata2.00? I've turned on an
option that says something about using the bios for device access
this build, but I'll be surprised if that's it. :)
Gene Heskett writes:
> On Tuesday 29 January 2008, Alan Cox wrote:
> >> As slight change here, I was going to use the same .config as 2.6.24-rc8,
> >> but just discovered that neither rc8 nor final is finding the drivers for
> >> my
> >
> >If it is not finding a driver that is nothing to do
On Tuesday 29 January 2008, Mark Lord wrote:
>Gene Heskett wrote:
>>..
>> Does anyone know why my dvdwriter isn't being assigned a '/dev/sdx' number
>> when dmesg says its found ok at ata2.00? I've turned on an option that
>> says something about using the bios for device access this build, but
Gene Heskett wrote:
..
Does anyone know why my dvdwriter isn't being assigned a '/dev/sdx' number
when dmesg says its found ok at ata2.00? I've turned on an option that says
something about using the bios for device access this build, but I'll be
surprised if that's it. :)
..
It should
> As slight change here, I was going to use the same .config as 2.6.24-rc8, but
> just discovered that neither rc8 nor final is finding the drivers for my
If it is not finding a driver that is nothing to do with libata. It means
it's not being loaded by the distribution, or the distribution
On Tuesday 29 January 2008, Florian Attenberger wrote:
>On Mon, 28 Jan 2008 14:13:21 -0500
>
>Gene Heskett <[EMAIL PROTECTED]> wrote:
>> >> I had to reboot early this morning due to a freezeup, and I had a
>> >> bunch of these in the messages log:
>> >> ==
>> >> Jan 27 19:42:11 coyote
On Tuesday 29 January 2008, Alan Cox wrote:
>> not one problem but lots---is sufficiently widespread that a Mini HOWTO,
>> say, would be really welcome and, I'm guessing, widely used.
>
>We don't see very many libata problems at the distro level and they for
>the most part boil down to
>
>- error
On Tuesday 29 January 2008, Alan Cox wrote:
>> not one problem but lots---is sufficiently widespread that a Mini HOWTO,
>> say, would be really welcome and, I'm guessing, widely used.
>
>We don't see very many libata problems at the distro level and they for
>the most part boil down to
>
>- error
> not one problem but lots---is sufficiently widespread that a Mini HOWTO,
> say, would be really welcome and, I'm guessing, widely used.
We don't see very many libata problems at the distro level and they for
the most part boil down to
- error messages looking different - Most bugs I get are
As slight change here, I was going to use the same .config as 2.6.24-rc8, but
just discovered that neither rc8 nor final is finding the drivers for my
If it is not finding a driver that is nothing to do with libata. It means
it's not being loaded by the distribution, or the distribution kernel
Gene Heskett writes:
On Tuesday 29 January 2008, Alan Cox wrote:
As slight change here, I was going to use the same .config as 2.6.24-rc8,
but just discovered that neither rc8 nor final is finding the drivers for
my
If it is not finding a driver that is nothing to do with libata.
On Tuesday 29 January 2008, Mikael Pettersson wrote:
Gene Heskett writes:
On Tuesday 29 January 2008, Alan Cox wrote:
As slight change here, I was going to use the same .config as
2.6.24-rc8, but just discovered that neither rc8 nor final is finding
the drivers for my
If it is not
Gene Heskett wrote:
Does anyone know why my dvdwriter isn't being assigned a '/dev/sdx' number
when dmesg says its found ok at ata2.00? I've turned on an option that says
something about using the bios for device access this build, but I'll be
surprised if that's it. :)
I think you mean
Mark Lord wrote:
Gene Heskett wrote:
..
Does anyone know why my dvdwriter isn't being assigned a '/dev/sdx'
number when dmesg says its found ok at ata2.00? I've turned on an
option that says something about using the bios for device access
this build, but I'll be surprised if that's it. :)
On Tuesday 29 January 2008, Mark Lord wrote:
Gene Heskett wrote:
..
Does anyone know why my dvdwriter isn't being assigned a '/dev/sdx' number
when dmesg says its found ok at ata2.00? I've turned on an option that
says something about using the bios for device access this build, but I'll
be
Gene Heskett wrote:
..
Does anyone know why my dvdwriter isn't being assigned a '/dev/sdx' number
when dmesg says its found ok at ata2.00? I've turned on an option that says
something about using the bios for device access this build, but I'll be
surprised if that's it. :)
..
It should
On Tuesday 29 January 2008, Alan Cox wrote:
not one problem but lots---is sufficiently widespread that a Mini HOWTO,
say, would be really welcome and, I'm guessing, widely used.
We don't see very many libata problems at the distro level and they for
the most part boil down to
- error messages
On Tuesday 29 January 2008, Florian Attenberger wrote:
On Mon, 28 Jan 2008 14:13:21 -0500
Gene Heskett [EMAIL PROTECTED] wrote:
I had to reboot early this morning due to a freezeup, and I had a
bunch of these in the messages log:
==
Jan 27 19:42:11 coyote kernel:
On Tuesday 29 January 2008, Alan Cox wrote:
not one problem but lots---is sufficiently widespread that a Mini HOWTO,
say, would be really welcome and, I'm guessing, widely used.
We don't see very many libata problems at the distro level and they for
the most part boil down to
- error messages
not one problem but lots---is sufficiently widespread that a Mini HOWTO,
say, would be really welcome and, I'm guessing, widely used.
We don't see very many libata problems at the distro level and they for
the most part boil down to
- error messages looking different - Most bugs I get are
Alan Cox wrote:
not one problem but lots---is sufficiently widespread that a Mini HOWTO,
say, would be really welcome and, I'm guessing, widely used.
We don't see very many libata problems at the distro level and they for
the most part boil down to
- sata_nv with 4GB of RAM, knowing
things in the kernel that refer to SCSI probably should say storage (or
ATA, really, but that would make the acronyms confusing).
SCSI is a command protocol. It is what your CD-ROM drive and USB storage
devices talk (albeit with a bit of an accent).
Alan
--
To unsubscribe from this list: send
On Tuesday 29 January 2008, Adam Turk wrote:
I just found this thread and it looks like it will fix my problem too. I
have an IDE cd-rw drive and 2 SCSI hard drives. My ide cd-rw drive hasn't
been showing up. I looked at setting scsi cdrom support
(CONFIG_BLOCK_DEV_SR) but it doesn't mention
On Tuesday 29 January 2008, Daniel Barkalow wrote:
On Tue, 29 Jan 2008, Gene Heskett wrote:
For starters, enable CONFIG_BLK_DEV_SR.
That could stand to be moved or renamed, it is well buried in the menu for
the REAL scsi stuffs, which I don't have any of. Enabled building now.
The SCSI
On Tue, 29 Jan 2008, Gene Heskett wrote:
For starters, enable CONFIG_BLK_DEV_SR.
That could stand to be moved or renamed, it is well buried in the menu for
the
REAL scsi stuffs, which I don't have any of. Enabled building now.
The SCSI support type (disk, tape, CD-ROM) section of
I just found this thread and it looks like it will fix my problem too. I have
an IDE cd-rw drive and 2 SCSI hard drives. My ide cd-rw drive hasn't been
showing up. I looked at setting scsi cdrom support (CONFIG_BLOCK_DEV_SR) but
it doesn't mention anything about ide drives using libata.
I
Gene Heskett wrote:
On Tuesday 29 January 2008, Jeff Garzik wrote:
Gene Heskett wrote:
Does anyone know why my dvdwriter isn't being assigned a '/dev/sdx' number
when dmesg says its found ok at ata2.00? I've turned on an option that
says something about using the bios for device access this
Is this 4GB or =4GB? I've seen contradictory reports, and I've got 4GB.
Depends how the memory is mapped. Any memory physically above the 4GB
boundary
Alan
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo
Gene Heskett wrote:
On Tuesday 29 January 2008, Mark Lord wrote:
Gene Heskett wrote:
..
Does anyone know why my dvdwriter isn't being assigned a '/dev/sdx' number
when dmesg says its found ok at ata2.00? I've turned on an option that
says something about using the bios for device access this
rgheck wrote:
Alan Cox wrote:
not one problem but lots---is sufficiently widespread that a Mini
HOWTO, say, would be really welcome and, I'm guessing, widely used.
We don't see very many libata problems at the distro level and they for
the most part boil down to
- sata_nv with 4GB of
On Tue, 29 Jan 2008, Alan Cox wrote:
things in the kernel that refer to SCSI probably should say storage (or
ATA, really, but that would make the acronyms confusing).
SCSI is a command protocol. It is what your CD-ROM drive and USB storage
devices talk (albeit with a bit of an accent).
On Tue, 29 Jan 2008, Alan Cox wrote:
not one problem but lots---is sufficiently widespread that a Mini HOWTO,
say, would be really welcome and, I'm guessing, widely used.
We don't see very many libata problems at the distro level and they for
the most part boil down to
- error
On Tue, 29 Jan 2008, Alan Cox wrote:
The SCSI error reporting really ought to include a simple interpretation
of the error for end users (The drive doesn't support this command A
sector's data got lost The drive timed out The drive failed The
drive is entirely gone). There's too much
I've seen a lot of verbosity out of SCSI messages, but I haven't seen a
straightforward interpretation of the problem in there. It's all
information useful for debugging, not information useful for system
administration.
It tells you what is going on. Unfortunately that frequently requires
That could stand to be moved or renamed, it is well buried in the menu for
the
REAL scsi stuffs, which I don't have any of.
Yes you do - USB storage and ATAPI are SCSI
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
On Tuesday 29 January 2008, Jeff Garzik wrote:
Gene Heskett wrote:
On Tuesday 29 January 2008, Jeff Garzik wrote:
Gene Heskett wrote:
Does anyone know why my dvdwriter isn't being assigned a '/dev/sdx'
number when dmesg says its found ok at ata2.00? I've turned on an
option that says
Mark Lord wrote:
rgheck wrote:
Alan Cox wrote:
not one problem but lots---is sufficiently widespread that a Mini
HOWTO, say, would be really welcome and, I'm guessing, widely used.
We don't see very many libata problems at the distro level and they for
the most part boil down to
-
rgheck wrote:
Mark Lord wrote:
rgheck wrote:
Alan Cox wrote:
not one problem but lots---is sufficiently widespread that a Mini
HOWTO, say, would be really welcome and, I'm guessing, widely used.
We don't see very many libata problems at the distro level and they for
the most part boil
The SCSI error reporting really ought to include a simple interpretation
of the error for end users (The drive doesn't support this command A
sector's data got lost The drive timed out The drive failed The
drive is entirely gone). There's too much similarity between the message
you get
On Tuesday 29 January 2008, Alan Cox wrote:
That could stand to be moved or renamed, it is well buried in the menu for
the REAL scsi stuffs, which I don't have any of.
Yes you do - USB storage and ATAPI are SCSI
By the linux software definition maybe. But I've defined scsi as that which
uses
By the linux software definition maybe. But I've defined scsi as that which
uses a 50 wire cable using 50 contact centronics connectors since the
mid '70's, and which often needs a ready supply of nubile virgins t
25, 50 or 68, with multiple voltage levels, plus of course it might be
over
From: [EMAIL PROTECTED]
if this works then it really needs to move and be renamed. I am compiling
with DEV_SR set.
That fixed me right up, Adam, k3b is once again as happy as a clam.
Fixed it for me too. I just realized the default config in 2.6.24 is way
different than the default config
Gene Heskett wrote:
I doubt libata has that capability now, or ever will, cuz these ide/atapi
devices are generally dumber than rocks about that. But any device claiming
to be scsi-II is supposed to be able to do those sorts of things while the
cpu is off crunching numbers for BOINC or
On Mon, 28 Jan 2008 14:13:21 -0500
Gene Heskett <[EMAIL PROTECTED]> wrote:
> >> I had to reboot early this morning due to a freezeup, and I had a
> >> bunch of these in the messages log:
> >> ==
> >> Jan 27 19:42:11 coyote kernel: [42461.915961] ata1.00: exception Emask 0x0
> >> SAct
On Mon, Jan 28, 2008 at 08:31:57PM -0500, Gene Heskett wrote:
>
> In my script, its one line:
> mkinitrd -f initrd-$VER.img $VER && \
>
> where $VER is the shell variable I edit to = the version number, located at
> the top of the script.
>
> Unforch, its failing:
> No module pata_amd found
On Mon, 2008-01-28 at 23:49 -0500, Gene Heskett wrote:
> On Monday 28 January 2008, Kasper Sandberg wrote:
> [...]
> >
> >I can invalidate this theory...
> >i helped a guy on irc debug this problem, and he had ati. I tried having
> >him stop using fglrx, and go to r300.. same problem, and same
On Monday 28 January 2008, Kasper Sandberg wrote:
[...]
>> >We have no way of debugging that module, so please try 2.6.24 without it.
>>
>> Sorry, I can't do this and have a working machine. The nv driver has
>> suffered bit rot or something since the FC2 days when it COULD run a 19"
>> crt at
On Mon, 2008-01-28 at 11:35 -0500, Gene Heskett wrote:
> On Monday 28 January 2008, Mikael Pettersson wrote:
> >Gene Heskett writes:
> > > On Monday 28 January 2008, Peter Zijlstra wrote:
> > > >On Mon, 2008-01-28 at 09:17 +0100, Mikael Pettersson wrote:
> > > >> 1. Wrong mailing list; use
On Monday 28 January 2008, Mark Lord wrote:
>Gene Heskett wrote:
>..
>
>> That's ok, dd seemed to do the job also.
>
>..
>
>The two programs operate entirely differently from each other,
>so it may still be worth trying the make_bad_sector utility there.
>
>dd goes through the regular kernel I/O
Gene Heskett wrote:
On Monday 28 January 2008, Gene Heskett wrote:
On Monday 28 January 2008, Robert Hancock wrote:
[...]
Check the /etc/modprobe.conf file, a lot of distributions use this to
generate the initrd. If there's references to pata_amd it'll try and
include it.
Bingo! Thanks
Gene Heskett wrote:
..
That's ok, dd seemed to do the job also.
..
The two programs operate entirely differently from each other,
so it may still be worth trying the make_bad_sector utility there.
dd goes through the regular kernel I/O calls,
whereas make_bad_sector sends raw ATA commands
On Monday 28 January 2008, Gene Heskett wrote:
>On Monday 28 January 2008, Robert Hancock wrote:
>[...]
>
>>Check the /etc/modprobe.conf file, a lot of distributions use this to
>>generate the initrd. If there's references to pata_amd it'll try and
>>include it.
>
>Bingo! Thanks Robert, I'll try
On Mon, 28 Jan 2008, Gene Heskett wrote:
> On Monday 28 January 2008, Daniel Barkalow wrote:
> >On Mon, 28 Jan 2008, Gene Heskett wrote:
> >> On Monday 28 January 2008, Daniel Barkalow wrote:
> >> >Building this and installing it along with the appropriate initrd (which
> >> >might be handled by
On Monday 28 January 2008, Robert Hancock wrote:
[...]
>Check the /etc/modprobe.conf file, a lot of distributions use this to
>generate the initrd. If there's references to pata_amd it'll try and
>include it.
Bingo! Thanks Robert, I'll try it again with that line commented. I wasn't
aware of
On Monday 28 January 2008, Daniel Barkalow wrote:
>On Mon, 28 Jan 2008, Gene Heskett wrote:
>> On Monday 28 January 2008, Daniel Barkalow wrote:
>> >Building this and installing it along with the appropriate initrd (which
>> >might be handled by Fedora's install scripts)
>>
>> Or mine, which I've
Gene Heskett wrote:
On Monday 28 January 2008, Robert Hancock wrote:
Gene Heskett wrote:
And so far no one has tried to comment on those 2 dmesg lines I've quoted
a couple of times now, here's another:
[0.00] Nvidia board detected. Ignoring ACPI timer override.
[0.00] If you
On Monday 28 January 2008, Robert Hancock wrote:
>Gene Heskett wrote:
>> And so far no one has tried to comment on those 2 dmesg lines I've quoted
>> a couple of times now, here's another:
>> [0.00] Nvidia board detected. Ignoring ACPI timer override.
>> [0.00] If you got timer
On Mon, 28 Jan 2008, Gene Heskett wrote:
> On Monday 28 January 2008, Daniel Barkalow wrote:
> >Building this and installing it along with the appropriate initrd (which
> >might be handled by Fedora's install scripts)
>
> Or mine, which I've been using for years.
You're ahead of a surprising
Gene Heskett wrote:
And so far no one has tried to comment on those 2 dmesg lines I've quoted a
couple of times now, here's another:
[0.00] Nvidia board detected. Ignoring ACPI timer override.
[0.00] If you got timer trouble try acpi_use_timer_override
what the heck is that
On Monday 28 January 2008, Mark Lord wrote:
>Gene Heskett wrote:
>>..
>> And so far no one has tried to comment on those 2 dmesg lines I've quoted
>> a couple of times now, here's another:
>> [0.00] Nvidia board detected. Ignoring ACPI timer override.
>> [0.00] If you got timer
On Monday 28 January 2008, Mark Lord wrote:
>Gene Heskett wrote:
>> On Monday 28 January 2008, Mark Lord wrote:
>>..
>>
>>> Another way is to use the "make_bad_sector" utility that
>>> is included in the source tarball for hdparm-7.7, as follows:
>>>
>>> make_bad_sector --readback /dev/sda
On Monday 28 January 2008, Daniel Barkalow wrote:
>On Mon, 28 Jan 2008, Richard Heck wrote:
>> Daniel Barkalow wrote:
>> > Can you switch back to old IDE to get your work done (and to make sure
>> > it's not a hardware issue that's developed recently)?
>>
>> I think it'd be really, REALLY helpful
Gene Heskett wrote:
On Monday 28 January 2008, Mark Lord wrote:
..
Another way is to use the "make_bad_sector" utility that
is included in the source tarball for hdparm-7.7, as follows:
make_bad_sector --readback /dev/sda 474507
Apparently not in the rpm, darnit.
..
That's okay. It
Mark Lord wrote:
Gene Heskett wrote:
..
And so far no one has tried to comment on those 2 dmesg lines I've quoted a
couple of times now, here's another:
[0.00] Nvidia board detected. Ignoring ACPI timer override.
[0.00] If you got timer trouble try acpi_use_timer_override
what
Gene Heskett wrote:
..
And so far no one has tried to comment on those 2 dmesg lines I've quoted a
couple of times now, here's another:
[0.00] Nvidia board detected. Ignoring ACPI timer override.
[0.00] If you got timer trouble try acpi_use_timer_override
what the heck is that
On Mon, 28 Jan 2008, Richard Heck wrote:
> Daniel Barkalow wrote:
> > Can you switch back to old IDE to get your work done (and to make sure it's
> > not a hardware issue that's developed recently)?
> I think it'd be really, REALLY helpful to a lot of people if you, or someone,
> could explain
Andrey Borzenkov wrote:
Richard Heck wrote:
Daniel Barkalow wrote:
Can you switch back to old IDE to get your work done (and to make sure
it's not a hardware issue that's developed recently)?
I think it'd be really, REALLY helpful to a lot of people if you, or
someone, could
On Monday 28 January 2008, Andrey Borzenkov wrote:
>On Monday 28 January 2008, Gene Heskett wrote:
>> On Monday 28 January 2008, Andrey Borzenkov wrote:
>> >Richard Heck wrote:
>> >> Daniel Barkalow wrote:
>> >>> Can you switch back to old IDE to get your work done (and to make sure
>> >>> it's
On Monday 28 January 2008, Gene Heskett wrote:
> On Monday 28 January 2008, Andrey Borzenkov wrote:
> >Richard Heck wrote:
> >> Daniel Barkalow wrote:
> >>> Can you switch back to old IDE to get your work done (and to make sure
> >>> it's not a hardware issue that's developed recently)?
> >>
> >>
On Monday 28 January 2008, Jeff Garzik wrote:
>Gene Heskett wrote:
>> Greeting;
>>
>> I had to reboot early this morning due to a freezeup, and I had a
>> bunch of these in the messages log:
>> ==
>> Jan 27 19:42:11 coyote kernel: [42461.915961] ata1.00: exception Emask 0x0
>> SAct 0x0
On Monday 28 January 2008, Andrey Borzenkov wrote:
>Richard Heck wrote:
>> Daniel Barkalow wrote:
>>> Can you switch back to old IDE to get your work done (and to make sure
>>> it's not a hardware issue that's developed recently)?
>>
>> I think it'd be really, REALLY helpful to a lot of people if
Gene Heskett wrote:
Greeting;
I had to reboot early this morning due to a freezeup, and I had a
bunch of these in the messages log:
==
Jan 27 19:42:11 coyote kernel: [42461.915961] ata1.00: exception Emask 0x0 SAct
0x0 SErr 0x0 action 0x2 frozen
Jan 27 19:42:11 coyote kernel:
1 - 100 of 180 matches
Mail list logo
