Kubuntu Feisty Beta 1 Live CD boot stops after Floppy drive error

Bug #96104 reported by Colin Pinkney on 2007-03-25
10
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: kubuntu-live

When booting in 'Safe Graphics' mode (the nv driver doesn't like my GeForce 6600 card) or even just trying to run a check for CD defects, the Kubuntu Feisty Fawn Beta 1 Live CD fails to boot early in the process after apparently trying to access a floppy disc for several seconds. Eventually it drops to a busybox console and the following error appears over the prompt:

ata2.00: failed to set xfermode (err_mask=0x4)

If I put a floppy in the drive and try to boot again, it accesses the floppy disc for a while and then proceeds to boot as normal. dmesg and /var/log/messages contain the following after the successful boot:

[ 35.968478] ata_piix 0000:00:1f.1: version 2.10ac1
[ 35.968524] PCI: Setting latency timer of device 0000:00:1f.1 to 64
[ 35.968619] ata1: PATA max UDMA/100 cmd 0x000101f0 ctl 0x000103f6 bmdma 0x0001f000 irq 14
[ 35.968681] ata2: PATA max UDMA/100 cmd 0x00010170 ctl 0x00010376 bmdma 0x0001f008 irq 15
[ 35.968711] scsi0 : ata_piix
[ 36.026151] usb 1-1: new full speed USB device using uhci_hcd and address 2
[ 36.036598] Floppy drive(s): fd0 is 1.44M
[ 36.111818] FDC 0 is a post-1991 82077
[ 36.130278] ata1.00: ATA-7: SAMSUNG SP2014N, VC100-33, max UDMA/100
[ 36.130286] ata1.00: 390721968 sectors, multi 16: LBA48
[ 36.138282] ata1.00: configured for UDMA/33
[ 36.141069] scsi1 : ata_piix
[ 36.224568] usb 1-1: configuration #1 chosen from 1 choice
[ 36.457942] ata2.00: ATAPI, max UDMA/33
[ 36.465710] usb 1-2: new full speed USB device using uhci_hcd and address 3
[ 36.621840] ata2.01: ATAPI, max UDMA/33
[ 36.720078] usb 1-2: configuration #1 chosen from 1 choice
[ 66.593489] ata2.00: qc timeout (cmd 0xef)
[ 66.593505] ata2.00: failed to set xfermode (err_mask=0x4)
[ 66.593513] ata2: failed to recover some devices, retrying in 5 secs
[ 72.240396] ata2.00: configured for UDMA/33

All the hard drives and optical drives are detected and operate correctly and so does the floppy drive once I'm in KDE. This didn't happen in Dapper or Edgy.

IDE/PCI Details:
00:00.0 Host bridge: Intel Corporation 82845 845 (Brookdale) Chipset Host Bridge (rev 04)
00:01.0 PCI bridge: Intel Corporation 82845 845 (Brookdale) Chipset AGP Bridge (rev 04)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 05)
00:1f.0 ISA bridge: Intel Corporation 82801BA ISA Bridge (LPC) (rev 05)
00:1f.1 IDE interface: Intel Corporation 82801BA IDE U100 (rev 05)

00:1f.1 IDE interface: Intel Corporation 82801BA IDE U100 (rev 05) (prog-if 80 [Master])
        Subsystem: ABIT Computer Corp. Unknown device 0506
        Flags: bus master, medium devsel, latency 0
        [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [disabled] [size=8]
        [virtual] Memory at 000003f0 (type 3, non-prefetchable) [disabled] [size=1]
        [virtual] Memory at 00000170 (32-bit, non-prefetchable) [disabled] [size=8]
        [virtual] Memory at 00000370 (type 3, non-prefetchable) [disabled] [size=1]
        I/O ports at f000 [size=16]

I double checked the md5sum of the ISO I downloaded against the sums on the download site and also burned another CD and had k3b verify the written data and all checked out ok.

description: updated
description: updated

Has this issue been fixed in the latest Feisty releases?

Changed in kubuntu-meta:
assignee: nobody → freddymartinez9
status: Unconfirmed → Needs Info
Colin Watson (cjwatson) wrote :

Freddy, he said "Beta" - that means he *is* running the latest Feisty release!

Ah my prescription needs to be upped in these glasses, my apologies. Have you tested any nightly builds? also, I notice your video card seems to be one that doesn't play well with Kubuntu (iirc), have you ever had problems doing an install on it?

Colin Pinkney (colin-pinkney) wrote :

Dapper installed from the Live CD without any problems. I could never get the Edgy Live CD to boot full because even in 'Safe Graphics' mode it seemed to try to use the nv driver instead of the vesa driver, so I just did an upgrade to Edgy instead. Even so, I never got this issue with the Edgy Live CD (it only failed at the X windows stage) and am running Edgy on my PC right now without any issues.

My graphics card works fine with either the vesa driver or proprietary Nvidia driver without any extra tweaking.

I've just spotted someone else with the exact same issue:

http://ubuntuforums.org/showthread.php?p=2351965

Is there any extra info about my hardware I can provide that would help?

Are there nightly builds of the ISOs? I'm not able to to install Feisty on to my hard drive at the moment I'm afraid.

G. Wang (ek-lem) wrote :

I have the exact same problem with Ubuntu beta desktop cd on my Dell desktop, running P4 3.06HT/nv fx5200/all IDE drives/no floppy. The problem exists with both regular live cd boot and safe graphics boot.

godot (godotcg-launchpad) wrote :

I probably have the same problem. At the begining of the boot process I have fdo errors during a long time. And also "ata2.00: failed to set xfermode (err_mask=0x4)" errors.
If I set "Drive A" to "none" instead of "1.44Mo" in the bios, I only have "ata2.00: failed to set xfermode (err_mask=0x4)" errors.

My system:
Core 2 Duo E6300
Motherboard - MSI 965 Neo
DVD±RW - Samsung SH-W133A SATA
HDD SATA II

It may be related to this bug : https://launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/90715

I tried Beta live cd and daily live cd from 29 March.

Frank A. Adrian (fadrian) wrote :

I am seeing this on an ASUS A8N-VM/CSM mobo, with an A64 chip.

The issue does not occur in kernel build 6.20.13-386, but does occur in kernel builds 6.20.14-386 and 6.20.15-386.
The mobo has an nVidia MCP51 chip and my hard drive (Quantum Fireball LM30) is attached to the IDE channel as the master device.

The issue appears to occur when the controller tries to check the max speed at which it can talk to the device. For my hard drive, it starts by trying to use UDMA/66 and then tries to reconfigure for UDMA/33 access (which seems to fail in the same way).

In any case, I hope this additional information helps locate the problem...

Colin Pinkney (colin-pinkney) wrote :

Still happens with the final Kubuntu Feisty Desktop CD :(

I pulled the IDE cable from my floppy drive and its boots, but it still seems to hang about doing nothing for a while. Here is part of the dmesg output without the floppy drive connected:

[ 54.489415] end_request: I/O error, dev fd0, sector 0
[ 66.653082] end_request: I/O error, dev fd0, sector 0
[ 66.653094] Buffer I/O error on device fd0, logical block 0
[ 71.871936] ata2.00: qc timeout (cmd 0xef)
[ 71.871950] ata2.00: failed to set xfermode (err_mask=0x4)
[ 71.871957] ata2: failed to recover some devices, retrying in 5 secs
[ 77.518843] ata2.00: configured for UDMA/33
[ 77.682698] ata2.01: configured for UDMA/33

It also seems to set all my IDE drives to UDMA/33 when they and the motherboard are capable of UDMA/100 (which is how Dapper initialises them)

I'm not sure if I want to upgrade to Feisty now as I don't want the same issues with it installed permanently :(

Robin T Cox (robin-cox) wrote :

See also Bug #96826 (Confirmed).

Nanley Chery (nanoman) on 2007-09-17
Changed in linux-source-2.6.20:
status: Incomplete → Confirmed
Oleksij Rempel (olerem) wrote :

Please try if you can reproduce in on Ubutnu Gutsy.

Changed in linux-source-2.6.20:
assignee: freddymartinez9 → nobody
status: Confirmed → Incomplete
wolfger (wolfger) wrote :

Over 5 months with no response. We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux-source-2.6.20:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers