2.6.16-rc1-mm2 pata driver confusion
I have an nforce4 based motherboard. Currently i'm using the amd/nvidia driver under the normal ide,ata driver section (2.6.14).
It appears that the new ata code is hiding under scsi/sata drivers, including apparently pata code. This alone reads confusing, pata drivers under the sata driver section, but that's not really the problem. The problem is that there appears to be two nvidia/amd ata drivers and I'm unsure which I should try using, if i compile both in, which get loaded first (i assume scsi is second to ide) and if i want my pata disks loaded under the new libata drivers, will my cdrom work under them too, or do i still need some sort of regular ide drivers loaded just for cdrom (to use native ata mode for recording access).
I couldn't find anything to explain how to deal with the new libata when it apparently overlaps functionality with the old ata/ide code in the Documentation directory, nor is it apparent if atapi is supported under the new libata code, or if either should be loaded first or not for best performance (if it matters). Or if they can both be loaded at the same time at all.
I have booted numerous configurations and have found the following to be true.
1. Atapi is most definitely not supported by libata, right now.
2. whether libata sets the controller up better or not, ide cdroms MUST be loaded before libata is or the ide controller will be detected as "already in use" and the cdrom drivers wont have any device to attach to, since unlike scsi drivers, ide drivers dont probe the hardware on controllers to see if any driver has claimed them.
3. For hdd's alone, the pata libata + sata drivers are a "complete" replacement for the ide drivers and thus, if you dont have atapi devices, you dont need to compile in ide support.
4. moving to pata libata drivers _will_ change the enumeration of your sata devices, it seems that pata is initialized first, so when setting up your fstab entries and grub, you'll have to take into account how many pata devices you have and offset your current sata device names by that amount.
Quoted 5 lines · Ed Sweetman
I have an nforce4 based motherboard. Currently i'm using the amd/nvidia driver under the normal ide,ata driver section (2.6.14).
It appears that the new ata code is hiding under scsi/sata drivers, including apparently pata code. This alone reads confusing, pata
libata PATA support is under development. Use only if you feel lucky. Really lucky. I mean, really really lucky.
Quoted 1 line
1. Atapi is most definitely not supported by libata, right now.
Not true.
Quoted 5 lines
2. whether libata sets the controller up better or not, ide cdroms MUST be loaded before libata is or the ide controller will be detected as "already in use" and the cdrom drivers wont have any device to attach to, since unlike scsi drivers, ide drivers dont probe the hardware on controllers to see if any driver has claimed them.
Either use drivers/ide or libata for PATA, not both.
Quoted 3 lines
3. For hdd's alone, the pata libata + sata drivers are a "complete" replacement for the ide drivers and thus, if you dont have atapi devices, you dont need to compile in ide support.
Again, ATAPI works just fine.
Quoted 5 lines
4. moving to pata libata drivers _will_ change the enumeration of your sata devices, it seems that pata is initialized first, so when setting up your fstab entries and grub, you'll have to take into account how many pata devices you have and offset your current sata device names by that amount.
Enumeration of devices depends on which driver is loaded first. Check your /etc/modprobe.conf.
Jeff
Quoted 6 lines · Ed Sweetman
problem. The problem is that there appears to be two nvidia/amd ata drivers and I'm unsure which I should try using, if i compile both in, which get loaded first (i assume scsi is second to ide) and if i want my pata disks loaded under the new libata drivers, will my cdrom work under them too, or do i still need some sort of regular ide drivers loaded just for cdrom (to use native ata mode for recording access).
The goal of the drivers/scsi/pata_* drivers is to replace drivers/ide in its entirity with code using the newer and cleaner libata logic. There is still much to do but my SIL680, SiS, Intel MPIIX, AMD and VIA boxes are using libata and the additional patch patches still queued.
Quoted 1 line
1. Atapi is most definitely not supported by libata, right now.
It works in the -mm tree.
Quoted 5 lines
4. moving to pata libata drivers _will_ change the enumeration of your sata devices, it seems that pata is initialized first, so when setting up your fstab entries and grub, you'll have to take into account how many pata devices you have and offset your current sata device names by that amount.
Or use labels. As you move into the world of hot pluggable hardware it becomes more and more impractical to guarantee drive ordering by name.
You can mix and match the drivers providing you don't try and load both libata and old ide drives for the same chip. Even then it should fail correctly with one of them reporting resources unavailable.
In fact I do this all the time when debugging so I've got a stable disk for debug work and a devel disk.
Alan
Quoted 8 lines · Alan Cox
Quoted 6 lines · Ed Sweetman
problem. The problem is that there appears to be two nvidia/amd ata drivers and I'm unsure which I should try using, if i compile both in, which get loaded first (i assume scsi is second to ide) and if i want my pata disks loaded under the new libata drivers, will my cdrom work under them too, or do i still need some sort of regular ide drivers loaded just for cdrom (to use native ata mode for recording access).
Quoted 4 lines
The goal of the
drivers/scsi/pata_*drivers is to replacedrivers/idein its entirity with code using the newer and cleaner libata logic. There is still much to do but my SIL680, SiS, Intel MPIIX, AMD and VIA boxes are using libata and the additional patch patches still queued.
What is "MPIIX" anyway?
and while I'm looking at the config menu, why do both Compaq Triflex and Intel PATA MPIIX say (Raving Lunatic)?
Quoted 19 lines
Quoted 1 line
1. Atapi is most definitely not supported by libata, right now.
It works in the -mm tree.
Quoted 5 lines
4. moving to pata libata drivers _will_ change the enumeration of your sata devices, it seems that pata is initialized first, so when setting up your fstab entries and grub, you'll have to take into account how many pata devices you have and offset your current sata device names by that amount.
Or use labels. As you move into the world of hot pluggable hardware it becomes more and more impractical to guarantee drive ordering by name.
You can mix and match the drivers providing you don't try and load both libata and old ide drives for the same chip. Even then it should fail correctly with one of them reporting resources unavailable.
In fact I do this all the time when debugging so I've got a stable disk for debug work and a devel disk.
Signature · 1 line
~Randy
Quoted 15 lines · Randy.Dunlap
Quoted 8 lines · Alan Cox
Quoted 6 lines · Ed Sweetman
problem. The problem is that there appears to be two nvidia/amd ata drivers and I'm unsure which I should try using, if i compile both in, which get loaded first (i assume scsi is second to ide) and if i want my pata disks loaded under the new libata drivers, will my cdrom work under them too, or do i still need some sort of regular ide drivers loaded just for cdrom (to use native ata mode for recording access).
Quoted 4 lines
The goal of the
drivers/scsi/pata_*drivers is to replacedrivers/idein its entirity with code using the newer and cleaner libata logic. There is still much to do but my SIL680, SiS, Intel MPIIX, AMD and VIA boxes are using libata and the additional patch patches still queued.
Quoted 4 lines
What is "MPIIX" anyway?
and while I'm looking at the config menu, why do both Compaq Triflex and Intel PATA MPIIX say (Raving Lunatic)?
Lots of them say Raving Lunatic. Are all of these Alan's libata patches?
Quoted 21 lines
Quoted 19 lines
Quoted 1 line
1. Atapi is most definitely not supported by libata, right now.
It works in the -mm tree.
Quoted 5 lines
4. moving to pata libata drivers _will_ change the enumeration of your sata devices, it seems that pata is initialized first, so when setting up your fstab entries and grub, you'll have to take into account how many pata devices you have and offset your current sata device names by that amount.
Or use labels. As you move into the world of hot pluggable hardware it becomes more and more impractical to guarantee drive ordering by name.
You can mix and match the drivers providing you don't try and load both libata and old ide drives for the same chip. Even then it should fail correctly with one of them reporting resources unavailable.
In fact I do this all the time when debugging so I've got a stable disk for debug work and a devel disk.
Signature · 1 line
~Randy
Quoted 5 lines · Randy.Dunlap
Quoted 2 lines
and while I'm looking at the config menu, why do both Compaq Triflex and Intel PATA MPIIX say (Raving Lunatic)?
Lots of them say Raving Lunatic. Are all of these Alan's libata patches?
They are a subset of them. The full patch now covers all the PCI devices that are not platform specific except CMD640B if I counted right. It also supports generic ISA, ISAPnP, PCMCIA and some VLB devices.
Needless to say not all of this works and less of it has been heavily tested yet.
Quoted 1 line · Randy.Dunlap
What is "MPIIX" anyway?
MPIIX was an early intel mobile chip. Its a PCI bridge, glue and the like for pentium laptops with a built in PIO ATA controller.
Quoted 2 lines
and while I'm looking at the config menu, why do both Compaq Triflex and Intel PATA MPIIX say (Raving Lunatic)?
So people don't casually select them. The current MPIIX driver will remove the raving lunatic once it gets upstream.
Quoted 14 lines · Alan Cox
Quoted 3 lines · Ed Sweetman
problem. The problem is that there appears to be two nvidia/amd ata drivers and I'm unsure which I should try using, if i compile both in, which get loaded first (i assume scsi is second to ide) and if i want my pata disks loaded under the new libata drivers, will my cdrom work under them too, or do i still need some sort of regular ide drivers loaded just for cdrom (to use native ata mode for recording access).
The goal of the
drivers/scsi/pata_*drivers is to replacedrivers/idein its entirity with code using the newer and cleaner libata logic. There is still much to do but my SIL680, SiS, Intel MPIIX, AMD and VIA boxes are using libata and the additional patch patches still queued
Quoted 7 lines
Quoted 3 lines
1. Atapi is most definitely not supported by libata, right now.
It works in the -mm tree.
Intriguing, when I had no ide chipset compiled in kernel, only libata drivers, I got no mention at all about my dvd writer. I even had the scsi cd driver installed and generic devices, still nothing seemed to initialize the dvd drive. It detected the second pata bus but no devices attached to it.
this is using the kernel mentioned in the subject header. 2.6.16-rc1-mm2. using the amd/nvidia drivers for pata and sata.
Is there anything i can do to give more info to the list to figure out why my atapi writer is being ignored by pata even when there are no ide drivers loaded?
Quoted 7 lines
Quoted 3 lines
4. moving to pata libata drivers _will_ change the enumeration of your sata devices, it seems that pata is initialized first, so when setting up your fstab entries and grub, you'll have to take into account how many pata devices you have and offset your current sata device names by that amount.
Or use labels. As you move into the world of hot pluggable hardware it becomes more and more impractical to guarantee drive ordering by name.
Quoted 10 lines
You can mix and match the drivers providing you don't try and load both libata and old ide drives for the same chip. Even then it should fail correctly with one of them reporting resources unavailable.
In fact I do this all the time when debugging so I've got a stable disk for debug work and a devel disk.
Alan
I'm not familiar with labeling ...will have to look into it, since borking a kernel after changing the drivers can result in a non-bootable system depending on how the partitions are setup across the devices. (since you'd have to change them in fstab and such before a reboot). A way around that would be very useful.
Quoted 34 lines · Ed Sweetman
Quoted 19 lines · Alan Cox
Quoted 8 lines · Ed Sweetman
problem. The problem is that there appears to be two nvidia/amd ata drivers and I'm unsure which I should try using, if i compile both in, which get loaded first (i assume scsi is second to ide) and if i want my pata disks loaded under the new libata drivers, will my cdrom work under them too, or do i still need some sort of regular ide drivers loaded just for cdrom (to use native ata mode for recording access).
The goal of the
drivers/scsi/pata_*drivers is to replacedrivers/idein its entirity with code using the newer and cleaner libata logic. There is still much to do but my SIL680, SiS, Intel MPIIX, AMD and VIA boxes are using libata and the additional patch patches still queuedQuoted 7 lines
Quoted 3 lines
1. Atapi is most definitely not supported by libata, right now.
It works in the -mm tree.
Intriguing, when I had no ide chipset compiled in kernel, only libata drivers, I got no mention at all about my dvd writer. I even had the scsi cd driver installed and generic devices, still nothing seemed to initialize the dvd drive. It detected the second pata bus but no devices attached to it.
Quoted 6 lines
this is using the kernel mentioned in the subject header. 2.6.16-rc1-mm2. using the amd/nvidia drivers for pata and sata.
Is there anything i can do to give more info to the list to figure out why my atapi writer is being ignored by pata even when there are no ide drivers loaded?
Currently you need to use libata.atapi_enabled=1
(assuming that libata is in the kernel image, not a loadable module).
I just built/tested this also, working for me as well. (hard drives, not ATAPI)
Quoted 27 lines
Quoted 11 lines
Quoted 7 lines
4. moving to pata libata drivers _will_ change the enumeration of your sata devices, it seems that pata is initialized first, so when setting up your fstab entries and grub, you'll have to take into account how many pata devices you have and offset your current sata device names by that amount.
Or use labels. As you move into the world of hot pluggable hardware it becomes more and more impractical to guarantee drive ordering by name.
Quoted 10 lines
You can mix and match the drivers providing you don't try and load both libata and old ide drives for the same chip. Even then it should fail correctly with one of them reporting resources unavailable.
In fact I do this all the time when debugging so I've got a stable disk for debug work and a devel disk.
Alan
I'm not familiar with labeling ...will have to look into it, since borking a kernel after changing the drivers can result in a non-bootable system depending on how the partitions are setup across the devices. (since you'd have to change them in fstab and such before a reboot). A way around that would be very useful.
Signature · 1 line
~Randy
Quoted 56 lines · Randy.Dunlap
Quoted 43 lines · Ed Sweetman
Quoted 23 lines · Alan Cox
Quoted 10 lines · Ed Sweetman
problem. The problem is that there appears to be two nvidia/amd ata drivers and I'm unsure which I should try using, if i compile both in, which get loaded first (i assume scsi is second to ide) and if i want my pata disks loaded under the new libata drivers, will my cdrom work under them too, or do i still need some sort of regular ide drivers loaded just for cdrom (to use native ata mode for recording access).
The goal of the
drivers/scsi/pata_*drivers is to replacedrivers/idein its entirity with code using the newer and cleaner libata logic. There is still much to do but my SIL680, SiS, Intel MPIIX, AMD and VIA boxes are using libata and the additional patch patches still queuedQuoted 10 lines
Quoted 5 lines
1. Atapi is most definitely not supported by libata, right now.
It works in the -mm tree.
Intriguing, when I had no ide chipset compiled in kernel, only libata drivers, I got no mention at all about my dvd writer. I even had the scsi cd driver installed and generic devices, still nothing seemed to initialize the dvd drive. It detected the second pata bus but no devices attached to it.
Quoted 8 lines
this is using the kernel mentioned in the subject header. 2.6.16-rc1-mm2. using the amd/nvidia drivers for pata and sata.
Is there anything i can do to give more info to the list to figure out why my atapi writer is being ignored by pata even when there are no ide drivers loaded?
Quoted 7 lines
Currently you need to use libata.atapi_enabled=1
(assuming that libata is in the kernel image, not a loadable module).I just built/tested this also, working for me as well. (hard drives, not ATAPI)
I assume libata.atapi_enabled=1 is a boot arg, not some structure member in the source for the pata driver that i need to set to 1, correct?
And you just built and tested it, how did you test if the atapi argument worked when you then say "not ATAPI" as something you tested?
In any case, i'll try out libata.atapi_enabled=1 and see if it detects the dvd drive.
Quoted 46 lines · Ed Sweetman
Quoted 44 lines · Randy.Dunlap
Quoted 31 lines · Ed Sweetman
Quoted 17 lines · Alan Cox
Quoted 8 lines · Ed Sweetman
problem. The problem is that there appears to be two nvidia/amd ata drivers and I'm unsure which I should try using, if i compile both in, which get loaded first (i assume scsi is second to ide) and if i want my pata disks loaded under the new libata drivers, will my cdrom work under them too, or do i still need some sort of regular ide drivers loaded just for cdrom (to use native ata mode for recording access).
The goal of the
drivers/scsi/pata_*drivers is to replacedrivers/idein its entirity with code using the newer and cleaner libata logic. There is still much to do but my SIL680, SiS, Intel MPIIX, AMD and VIA boxes are using libata and the additional patch patches still queuedQuoted 6 lines
Quoted 3 lines
1. Atapi is most definitely not supported by libata, right now.
It works in the -mm tree.
Intriguing, when I had no ide chipset compiled in kernel, only libata drivers, I got no mention at all about my dvd writer. I even had the scsi cd driver installed and generic devices, still nothing seemed to initialize the dvd drive. It detected the second pata bus but no devices attached to it.
Quoted 7 lines
this is using the kernel mentioned in the subject header. 2.6.16-rc1-mm2. using the amd/nvidia drivers for pata and sata.
Is there anything i can do to give more info to the list to figure out why my atapi writer is being ignored by pata even when there are no ide drivers loaded?
Currently you need to use libata.atapi_enabled=1
(assuming that libata is in the kernel image, not a loadable module).
Quoted 6 lines
Quoted 4 lines
I just built/tested this also, working for me as well. (hard drives, not ATAPI)
I assume libata.atapi_enabled=1 is a boot arg, not some structure member in the source for the pata driver that i need to set to 1, correct?
Yes, it's a kernel boot option if libata is in the kernel image. If libata is a loadable module, just use something like
modprobe libata atapi_enabled=1
Quoted 2 lines
And you just built and tested it, how did you test if the atapi argument worked when you then say "not ATAPI" as something you tested?
Sorry, I mean that I built and booted a kernel with libata/PATA hard drive (vs. legacy drivers/ide/ PATA support). I have not tested ATAPI at all and didn't mean to imply that I had.
I reported on libata.atapi_enabled=1 based on documentation and other emails that I have read.
Quoted 2 lines
In any case, i'll try out libata.atapi_enabled=1 and see if it detects the dvd drive.
HTH. Please continue to post any questions or problems.
Signature · 1 line
~Randy
Quoted 98 lines · Randy.Dunlap
Quoted 63 lines · Ed Sweetman
Quoted 59 lines · Randy.Dunlap
Quoted 43 lines · Ed Sweetman
Quoted 23 lines · Alan Cox
Quoted 10 lines · Ed Sweetman
problem. The problem is that there appears to be two nvidia/amd ata drivers and I'm unsure which I should try using, if i compile both in, which get loaded first (i assume scsi is second to ide) and if i want my pata disks loaded under the new libata drivers, will my cdrom work under them too, or do i still need some sort of regular ide drivers loaded just for cdrom (to use native ata mode for recording access).
The goal of the
drivers/scsi/pata_*drivers is to replacedrivers/idein its entirity with code using the newer and cleaner libata logic. There is still much to do but my SIL680, SiS, Intel MPIIX, AMD and VIA boxes are using libata and the additional patch patches still queuedQuoted 10 lines
Quoted 5 lines
1. Atapi is most definitely not supported by libata, right now.
It works in the -mm tree.
Intriguing, when I had no ide chipset compiled in kernel, only libata drivers, I got no mention at all about my dvd writer. I even had the scsi cd driver installed and generic devices, still nothing seemed to initialize the dvd drive. It detected the second pata bus but no devices attached to it.
Quoted 9 lines
this is using the kernel mentioned in the subject header. 2.6.16-rc1-mm2. using the amd/nvidia drivers for pata and sata.
Is there anything i can do to give more info to the list to figure out why my atapi writer is being ignored by pata even when there are no ide drivers loaded?
Currently you need to use libata.atapi_enabled=1
(assuming that libata is in the kernel image, not a loadable module).Quoted 10 lines
Quoted 6 lines
I just built/tested this also, working for me as well. (hard drives, not ATAPI)
I assume libata.atapi_enabled=1 is a boot arg, not some structure member in the source for the pata driver that i need to set to 1, correct?
Yes, it's a kernel boot option if libata is in the kernel image. If libata is a loadable module, just use something like
modprobe libata atapi_enabled=1Quoted 4 lines
And you just built and tested it, how did you test if the atapi argument worked when you then say "not ATAPI" as something you tested?
Sorry, I mean that I built and booted a kernel with libata/PATA hard drive (vs. legacy
drivers/ide/PATA support). I have not tested ATAPI at all and didn't mean to imply that I had.I reported on libata.atapi_enabled=1 based on documentation and other emails that I have read.
Quoted 8 lines
Quoted 4 lines
In any case, i'll try out libata.atapi_enabled=1 and see if it detects the dvd drive.
HTH. Please continue to post any questions or problems.
I Rebooted several times, both setting the option in the kernel boot args and editing the source to have it set by default. No atapi devices are found/mentioned or even described as not found in dmesg/bootup. So apparently, on my chipset, the amd/nvidia pata driver is not detecting atapi devices.
0000:00:06.0 IDE interface: nVidia Corporation CK804 IDE (rev f2) 0000:00:07.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev f3) 0000:00:08.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev f3)
0000:00:06.0 IDE interface: nVidia Corporation CK804 IDE (rev f2) (prog-if 8a [Master SecP PriP])
Subsystem: Unknown device f043:815a
Flags: bus master, 66MHz, fast devsel, latency 0
I/O ports at f000 [size=16]
Capabilities: [44] Power Management version 2
the atapi device in question is a plextor px-712A, it's the only device on the secondary channel.