Dmesg has:
[ 3.516235] ata3.00: ATAPI: TSSTcorp CDDVDW SH-222BB, SB00, max
UDMA/100
[ 4.204228] ata4.00: ATAPI: TSSTcorp CDDVDW SH-222BB, SB00, max
UDMA/100
So both look alike. I cannot find the text 'sr0' in Dmesg.
Actually the text around the line above is a bit disconcerting;
[ 4.196078] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 3F0)
[ 4.204228] ata4.00: ATAPI: TSSTcorp CDDVDW SH-222BB, SB00, max
UDMA/100
[ 4.220223] ata4.00: configured for UDMA/100
[ 4.221613] scsi 3:0:0:0: CD-ROM TSSTcorp CDDVDW
SH-222BB SB00 PQ: 0 ANSI: 5
[ 4.222628] ata4.00: exception Emask 0x100 SAct 0x0 SErr 0x0 action
0x6
[ 4.222639] ata4: hard resetting link
[ 4.540071] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 3F0)
[ 4.564222] ata4.00: configured for UDMA/100
[ 4.564646] ata4: EH complete
Let's try re-installing kb3 and see if it is happier with these as
they seem to favour UDMA.
I'll have to look into that.
Thanks everybody.
Update. Drive works well in XP, wrote a fedora 17 cd with it. The Mint
13 disc wrote, started to boot, but won't run, came up with a bad
kernel error.
On Mint 7 it gave the same errors as Kubuntu - as above. Not surprising
as my Mint 7 disk is dated 2009, and Mint has the same forbears as ubuntu.
Fedora 17 has the following in dmesg after booting in the new drive:
I can't find it- I think I saved it in the wrong place.
But anyway, it loaded without errors.
So my conclusion is that the Drive is OK, but ubuntu has a problem
communicating with it.
Peter M.
--
Next meeting: Bournemouth, Tuesday 2012-06-12 20:00
Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/
New thread on mailing list: mailto:[email protected]
How to Report Bugs Effectively: http://goo.gl/4Xue
