[Install] Marvell 88SE6145 PATA - CDROM not recognised

Bug #213284 reported by Nigel Gale
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Using Hardy 64 beta alternate install CD on Asus P5E WS Pro with Intel Q6600.

DVD drives are connected via IDE but these are controlled by Marvell 88SE6145 SATA/PATA controller. CD boots OK but when starting the install the DVD drive is not recognised. Am prompted to install drivers via floppy but don't have a floppy installed. Then asked for DVD device
but this is not shown via ls /dev.

I have checked the forums and others have had the same problem but no solutions found.

The install works fine for 7.10 x64 alternate CD, so currently have installed 7.10 and have sucessfully carried out upgrade from 8.04 alternate CD as a workaround.

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include as attachments the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance!

Revision history for this message
Nigel Gale (nigel-gale) wrote :

Brian

Unless I have completely lost the plot this is impossible to do any of this as this is during install.

This is happening when booting Hardy x64 beta CDROM to carry out an install on the hardware already detailed in the bug report.

Revision history for this message
velde064 (a-j-w-vandervelde) wrote :

Ls,

Having the same problem also using Asus P5E WS PRO.
I did an upgrade from feisty to hardy and since that moment i am not able to use the cdrom / dvd anymore

Regards,

Andre

Changed in linux:
assignee: nobody → ubuntu-kernel-team
importance: Undecided → Medium
status: Incomplete → Confirmed
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Peter Funk (pf-artcom-gmbh) wrote :

We build a PC with an ASUS P5E3 WS Pro motherboard carrying also the Marvell 88SE6145 SATA/PATA controller.
We have tried the following Ubuntu CDs 7.04, 7.10, 8.04 and 8.10 in different flavours. None of them was
able to boot from the PATA DVD Drive; installing 8.04 from a SATA drives worked though. Since SuSE 11.0
and the well known http://www.sysresccd.org/ are also effected, I assume the problem is still present upstream
even in kernel 2.6.27

My son discovered the following thread about this matter:

http://kerneltrap.org/mailarchive/linux-kernel/2008/9/2/3172244

There is a discussion between Alan Cox and Jeff Garzik about this matter.

Changed in linux:
status: Confirmed → Triaged
Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Triaged a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-triage
Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
amorangi (5-launchpad-deltanine-net) wrote :

The problem still exists in 10.04

Changed in linux (Ubuntu):
status: Incomplete → New
Revision history for this message
Ben (ben-j-dover) wrote :

Using the same Marvell controller "88SE6145" on an Intel Dx975XBX2 motherboard. The BIOS reports the drives in system load - however Ubuntu does not see them - ever. I used the same platform for 9.xx and accessed the Marvel attached drives without a problem. I have not seen any possible solution - or work around.
I am more than willing to provide any detail I can - or better, that I can comprehend implementation - needed to address this problem. As it stands I am unable to access more than 60% of the attached storage on this system. Not a good thing.

Revision history for this message
Ben (ben-j-dover) wrote :

Did more research on my system - I use dual boot Windows 7 Enterprise and Ubuntu 10.4. The W7 OS sees the driver and loads the Marvell drives without a problem. There is no corresponding action in Ubuntu.

I do have the Marvell 88SE6145 PATA controller recognized in Disk Utility 2.30.1 - only as a PATA controller. I do not have a drive of any kind attached to the PATA ports on the Marvell controller. I do have two SATA drives connected which do not appear in Disk Utility, nor in any other directory application that I have tried.

This bug is listed as of medium importance - - - in my case that is an understatement. Until I can use the Marvell attached drives in Ubuntu I really am not able to use Ubuntu on a regular, successful basis. I really believe that this should be at least serious importance - or whatever a couple of levels up would be. If someone can assure me that the issue is resolved in the coming release I might be less concerned. As it is, it seems that this problem is being ignored; and that does not make me comfortable committing to using Ubuntu on a long term basis.

Andy Whitcroft (apw)
Changed in linux (Ubuntu):
status: New → Triaged
Revision history for this message
penalvch (penalvch) wrote :

Nigel Gale, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

tags: added: needs-kernel-logs needs-upstream-testing
Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.