Arch Linux

Pilli

Member

Registered: 2004-09-01

Posts: 46

Problem after update.

Hi.

I have updated archlinux this morning, this works well, but when i have restarted computer i have this problem:

...
...
...
scsi1 : ata_piix
ata2.00: ATAPI, max UDMA/33
ata2.01: qc timeout (cmd 0xa1)
ata2.01: failed to IDENTIFY (I/O error, err_mask=0x4)
ata2: failed to recover some devices, retrying in 5 secs
ata2.01: qc timeout (cmd 0xa1)
ata2.01: failed to IDENTIFY (I/O error, err_mask=0x4)
ata2: failed to recover some devices, retrying in 5 secs
ata2.01: qc timeout (cmd 0xa1)
ata2.01: failed to IDENTIFY (I/O error, err_mask=0x4)
ata2: failed to recover some devices, retrying in 5 secs
ata2.00: configured for UDMA/33
...
...
...

How can i fix it?
Thanks!

ralvy

Member

From: Santa Monica, California

Registered: 2004-12-06

Posts: 275

Re: Problem after update.

Same here. Can't complete the boot and my grub menu never appears. I simply begin the boot process immediately, and get what you posted here.

Follow-up: Actually, I did get the grub menu, just seemed like I didn't because I must have hit <Enter> twice quickly. Anyway, the problem with the eternal boot was soved by adding 'earlymodules=piix' to my kernel command line.

elasticdog

Member

From: Washington, USA

Registered: 2005-05-02

Posts: 995

Website

Re: Problem after update.

I believe the installation messages were updated accordingly...also see the news items posted on the main site:
· Kernel 2.6.19 and Intel chipsets
· kernel 2.6.19 series hits testing (Update)

ralvy

Member

From: Santa Monica, California

Registered: 2004-12-06

Posts: 275

Re: Problem after update.

Unless I add 'earlymodules=piix' to the kernel command line, I get a kernel panic. So I cannot follow the advice to add 'break=y' to the command line and see what drive assignments are made. I can only get the old assignments that 'earlymodules=piix' gives me, unless I'm not following this.

ks1

Member

From: Atlanta, Georgia

Registered: 2006-03-26

Posts: 62

Website

Re: Problem after update.

Have you tried changing your grub menu.lst ? As far as seeing grub maybe the update for grub changed your config or something is broken with it.

The device should have moved to /dev/sd* instead of /dev/hd* with the newer ata stuff. I made two seperate entries to be safe.

In grub to see the menu make sure you have
# general configuration:
timeout   5 (this is in seconds)

Old Entry

# (1) Arch Linux
title  Arch Linux
root   (hd1,1)
kernel /boot/vmlinuz26 root=/dev/hdb2 ro vga=795
initrd /boot/kernel26.img

New Entry

# (3) Arch Linux
title  Arch Linux
root   (hd1,1)
kernel /boot/vmlinuz26 root=/dev/sdb2 ro vga=795
initrd /boot/kernel26-pata.img

ralvy

Member

From: Santa Monica, California

Registered: 2004-12-06

Posts: 275

Re: Problem after update.

/boot/kernel26-pata.img was never created by the update.

ks1

Member

From: Atlanta, Georgia

Registered: 2006-03-26

Posts: 62

Website

Re: Problem after update.

Sorry I forgot to mention that is the one that I specified in addition to the default. The only difference is it has is in HOOKS=( ), is ide is removed and pata is in place of it.

Pilli

Member

Registered: 2004-09-01

Posts: 46

Re: Problem after update.

Hi!

My problem isn't a kernel panic. I can boot my laptop, but that is very slow, about 2 - 3 minutes. My problem is with ata2 device.

When I boot laptop I get this message:

...
...
...
ata1: PATA max UDMA/100 cmd 0x1F0 ctl 0x3F6 bmdma 0x1840 irq 14
ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x1848 irq 15
scsi0 : ata_piix
Time: acpi_pm clocksource has been installed.
ata1.00: ATA-5, max UDMA/100, 78140160 sectors: LBA 
ata1.00: ata1: dev 0 multi count 16
ata1.00: configured for UDMA/100
scsi1 : ata_piix
ata2.00: ATAPI, max UDMA/33
ata2.01: qc timeout (cmd 0xa1)
ata2.01: failed to IDENTIFY (I/O error, err_mask=0x4)
ata2: failed to recover some devices, retrying in 5 secs
ata2.01: qc timeout (cmd 0xa1)
ata2.01: failed to IDENTIFY (I/O error, err_mask=0x4)
ata2: failed to recover some devices, retrying in 5 secs
ata2.01: qc timeout (cmd 0xa1)
ata2.01: failed to IDENTIFY (I/O error, err_mask=0x4)
ata2: failed to recover some devices, retrying in 5 secs
ata2.00: configured for UDMA/33
...
...
...

And the boot process is late enough. It repeats the same message 3 times:

ata2.01: qc timeout (cmd 0xa1)
ata2.01: failed to IDENTIFY (I/O error, err_mask=0x4)
ata2: failed to recover some devices, retrying in 5 secs

And here is where it spends all the time.

Why this happens? How can i fix it?

Thanks.

brain0

Developer

From: Aachen - Germany

Registered: 2005-01-03

Posts: 1,382

Re: Problem after update.

The solution has already been provided in the first reply.

otti

Member

Registered: 2006-12-18

Posts: 64

Re: Problem after update.

Uhm, where exactly was the solution posted?  :shock:

Changing the names of the devices in fstab and in menu.lst from hdx to sdx does not solve the problem...

ralvy

Member

From: Santa Monica, California

Registered: 2004-12-06

Posts: 275

Re: Problem after update.

the problem with the eternal boot was soved by adding 'earlymodules=piix' to my kernel command line.