You are not logged in.
Pages: 1
Hi,
Since the kernel upgrade I've gotten a boot delay during identification of ata devices. It takes up to 4 tries (with a 5 sec delay in between) before my cdrom drive is properly detected. Anyone knows of a solution to this?
from dmesg
SCSI subsystem initialized
libata version 3.00 loaded.
pata_amd 0000:00:09.0: version 0.3.10
PCI: Setting latency timer of device 0000:00:09.0 to 64
scsi0 : pata_amd
scsi1 : pata_amd
ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xf000 irq 14
ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xf008 irq 15
ata1.00: ATA-6: ST3120026A, 3.06, max UDMA/100
ata1.00: 234441648 sectors, multi 16: LBA48
ata1.01: ATA-7: Maxtor 6B300R0, BAH41B10, max UDMA/133
ata1.01: 586114704 sectors, multi 16: LBA48
ata1: nv_mode_filter: 0x3f39f&0x3f01f->0x3f01f, BIOS=0x3f000 (0xc6c7c000) ACPI=0x3f01f (20:15:0x1f)
ata1: nv_mode_filter: 0x7f39f&0x7f01f->0x7f01f, BIOS=0x7f000 (0xc6c7c000) ACPI=0x7f01f (20:15:0x1f)
ata1.00: configured for UDMA/100
ata1.01: configured for UDMA/133
ata2.01: failed to IDENTIFY (I/O error, err_mask=0x1)
ata2: failed to recover some devices, retrying in 5 secs
ieee1394: Host added: ID:BUS[0-01:1023] GUID[00023c002105b2d9]
ata2.01: failed to IDENTIFY (I/O error, err_mask=0x1)
ata2: failed to recover some devices, retrying in 5 secs
ata2.01: failed to IDENTIFY (I/O error, err_mask=0x1)
ata2: failed to recover some devices, retrying in 5 secs
ata2.00: ATAPI: SONY CD-RW CRX160E, 1.0e, max UDMA/33
ata2: nv_mode_filter: 0x739f&0x701f->0x701f, BIOS=0x7000 (0xc6c7c000) ACPI=0x701f (60:600:0x13)
ata2.00: configured for UDMA/33
scsi 0:0:0:0: Direct-Access ATA ST3120026A 3.06 PQ: 0 ANSI: 5
scsi 0:0:1:0: Direct-Access ATA Maxtor 6B300R0 BAH4 PQ: 0 ANSI: 5
scsi 1:0:0:0: CD-ROM SONY CD-RW CRX160E 1.0e PQ: 0 ANSI: 5
vanum est vobis ante lucem surgere
Offline
I've now done some googling and searching for similar bugs, but I still don't see where this problem comes from. Would be nice with some guidance of where I should look for a possible solution.
Not that it is that a great deal, the kernel boots and all, but boot errors and delays can get quite irritating now and then.
vanum est vobis ante lucem surgere
Offline
I had similar issues a while back. Look at this thread:
Offline
Hmm, ok. So you solved your problem by reverting from libata/pata to the old ide drivers?
vanum est vobis ante lucem surgere
Offline
Exactly! I'm pretty impressed how fast you figured that one out by reading the above thread. I realized after posting that my thread didn't really offer any clear solution, but was rather linking to one.
What I did - if I remember correctly - was to remove pata from the hooks insert ide instead and alter the modules to include piix and ide_disk, ran a "mkinitcpio -p kernel26" and then renamed the drives in fstab from sdx to hdx before rebooting.
Offline
I guess that would be a solution to my problem. But it, of course, *should* work with libata though. And it actually does, but with a delay before the cdrw drive is detected. Maybe I should file a bug report.
Thanks Ashren, i'll use your solution if I don't find a way through the libata craziness!
edit: Bug report: http://bugs.archlinux.org/task/10570
Last edited by Xappe (2008-06-02 22:30:53)
vanum est vobis ante lucem surgere
Offline
I think, this bug may report directly to kernel developers.
Offline
I think, this bug may report directly to kernel developers.
Hmm, maybe. Doesen't seem to get any answer on flyspray anyhow...
vanum est vobis ante lucem surgere
Offline
i had the same problem but have found a fix. Just edit /etc/mkinitcpio.conf
and remove pata_acpi from the MODULES line
remove pata from HOOKS line and enter ide
then type
mkinitcpio -g /boot/kernel26.img
that should fix it... good luck
Offline
Pages: 1