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 some
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 whate
Gene,
If you still want to try it, I did manage to get the old IDE subsystem
working. The issue with pata_amd concerns modprobe.conf. You probably
have an alias to it there, as Fedora seems to insert these. (I don't
know if they're actually needed or not.) If you comment out that line,
then
> 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
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 requi
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"). T
> 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-ide" in
the body of a message to [EMAIL PROTECTED]
Mor
> 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
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
- sata_
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 d
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:
> > 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
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 RA
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 b
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.
>
>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 list:
> Don't know. Is there an easy way to find out?
E820 map on boot shows you I think.
> By the way, and on a totally different subject. I wonder if this:
> MODULE_DESCRIPTION("low-level driver for AMD PATA IDE");
> mightn't be changed to something like:
> MODULE_DESCRIPTION("low-level driver for A
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)" sectio
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 bu
Alan Cox wrote:
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
Don't know. Is there an easy way to find out?
By the way, and on a totally different subject. I wonder if thi
> 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-ide" in
the body of a message to [EMAIL PROTECTED]
More majordomo in
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 bein
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 /dev
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 w
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'
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 show
> 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 kerne
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 k
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 m
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 m
> 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 th
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 for
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 pr
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 16
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 linux-id
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 ca
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
dire
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 F
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 b
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 num
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 474507
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 t
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 shoul
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 t
Alan Cox wrote:
On Mon, Jan 28, 2008 at 01:38:40PM -0500, Mark Lord wrote:
[ 31.195305] ata2.00: ATAPI: LITE-ON DVDRW SHM-165H6S, HS06, max UDMA/66
[ 31.243813] ata2.01: ATA-7: MAXTOR STM3320620A, 3.AAE, max UDMA/100
[ 31.243816] ata2.01: 625142448 sectors, multi 16: LBA48
[ 31.243825]
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 in
On Mon, Jan 28, 2008 at 01:38:40PM -0500, Mark Lord wrote:
> >[ 31.195305] ata2.00: ATAPI: LITE-ON DVDRW SHM-165H6S, HS06, max UDMA/66
> >[ 31.243813] ata2.01: ATA-7: MAXTOR STM3320620A, 3.AAE, max UDMA/100
> >[ 31.243816] ata2.01: 625142448 sectors, multi 16: LBA48
> >[ 31.243825] ata2.00
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
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: [424
On Monday 28 January 2008, Mark Lord wrote:
>> [ 64.037975] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
>> [ 64.038102] ata1.00: BMDMA stat 0x65
>> [ 64.038227] ata1.00: cmd c8/00:58:89:3d:07/00:00:00:00:00/e0 tag 0 dma
>> 45056 in [ 64.038229] res 51/40:58:8b:3d:07/0
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: [4246
Added Alan to CC: list.
[ 30.703188] scsi0 : pata_amd
[ 30.709313] scsi1 : pata_amd
[ 30.710076] ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xf000 irq 14
[ 30.710079] ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xf008 irq 15
[ 30.864753] ata1.00: ATA-6: WDC WD2000JB-00EVA0
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 in moderate detail how this might be done. I
tried doi
[ 64.037975] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 64.038102] ata1.00: BMDMA stat 0x65
[ 64.038227] ata1.00: cmd c8/00:58:89:3d:07/00:00:00:00:00/e0 tag 0 dma 45056
in
[ 64.038229] res 51/40:58:8b:3d:07/00:00:00:00:00/e0 Emask 0x9
(media error)
[ 64.03843
On Mon, 28 Jan 2008, Gene Heskett wrote:
> I believe at this point, its moot. I captured quite a few instances of that
> error message while rebooting the last time, all of which occurred long
> before I logged in and did a startx (I boot to runlevel 3 here), so the
> kernel was NOT tainted at
On Monday 28 January 2008, Gene Heskett wrote:
>On Monday 28 January 2008, Zan Lynx wrote:
>>On Mon, 2008-01-28 at 11:50 -0500, Calvin Walton wrote:
>>> On Mon, 2008-01-28 at 11:35 -0500, Gene Heskett wrote:
>>> > On Monday 28 January 2008, Mikael Pettersson wrote:
>>> > >Unfortunately we also see:
On Mon, 2008-01-28 at 11:50 -0500, Calvin Walton wrote:
> On Mon, 2008-01-28 at 11:35 -0500, Gene Heskett wrote:
> > On Monday 28 January 2008, Mikael Pettersson wrote:
> > >Unfortunately we also see:
> > > > [ 48.285456] nvidia: module license 'NVIDIA' taints kernel.
> > > > [ 48.549725] ACPI
On Monday 28 January 2008, Zan Lynx wrote:
>On Mon, 2008-01-28 at 11:50 -0500, Calvin Walton wrote:
>> On Mon, 2008-01-28 at 11:35 -0500, Gene Heskett wrote:
>> > On Monday 28 January 2008, Mikael Pettersson wrote:
>> > >Unfortunately we also see:
>> > > > [ 48.285456] nvidia: module license 'NVI
On Jan 28, 2008 11:35 AM, Gene Heskett <[EMAIL PROTECTED]> wrote:
>
> On Monday 28 January 2008, Mikael Pettersson 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
On Monday 28 January 2008, Richard Heck wrote:
>I've recently seen this kind of error myself, under Fedora 8, using the
>
>Fedora 2.6.23 kernels: I'd see a train of the same sort of error:
>> Jan 28 04:46:25 coyote kernel: [26550.290016] ata1.00: exception Emask
>> 0x0 SAct 0x0 SErr 0x0 action 0x2
On Monday 28 January 2008, Gene Heskett wrote:
While reading this msg as it came back, I locked up again and rebooted to
2.6.24, and got lucky (maybe) as the attached dmesg will show quite a few
instances of this LNNNGG before the nvidia driver is loaded to taint the
kernel. Have fun guys!
On Mon, 2008-01-28 at 11:35 -0500, Gene Heskett wrote:
> On Monday 28 January 2008, Mikael Pettersson wrote:
> >Unfortunately we also see:
> > > [ 48.285456] nvidia: module license 'NVIDIA' taints kernel.
> > > [ 48.549725] ACPI: PCI Interrupt :02:00.0[A] -> Link [APC4] -> GSI
> > > 19 (lev
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 linux-ide (@vger) instead.
> > >
> > >What, and keep all us other interes
I've recently seen this kind of error myself, under Fedora 8, using the
Fedora 2.6.23 kernels: I'd see a train of the same sort of error:
Jan 28 04:46:25 coyote kernel: [26550.290016] ata1.00: exception Emask 0x0
SAct 0x0 SErr 0x0 action 0x2 frozen
Jan 28 04:46:25 coyote kernel: [26550.290028
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 linux-ide (@vger) instead.
> >
> >What, and keep all us other interested people in the dark?
>
> As a test, I tried rebootin
On Monday 28 January 2008, Gene Heskett wrote:
>[ 0.00] If you got timer trouble try acpi_use_timer_override
This is from the dmesg of my previous post.
Can anyone tell me what it actually means?
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury,
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 linux-ide (@vger) instead.
>
>What, and keep all us other interested people in the dark?
As a test, I tried rebooting to the latest fedora kernel and found it
73 matches
Mail list logo
