Red Hat Bugzilla – Bug 444577
Optical drive HL-DT-ST DVDRAM GSA-T20N not detected on fedora 10 ( amilo xa 2528 and 2529)
Last modified: 2009-12-18 01:07:52 EST
Description of problem:
I have a fujitsu siemens amilo xa 2529-7006 laptop with an internal dvd optical
drive from LG, model : HL-DT-ST DVDRAM GSA-T20N
I can boot but not install fedora, the drive seems to not be found after the
driver detection process ( before the launch of anaconda).
I managed to run fedora 8 after a long netinstall ( about 3 hours ), but when I
boot fedora, I have a bunch of errors during 5 mins ( see attached file below. )
And then I can use fedora ( my dmesg is full of this errors anyway )
Version-Release number of selected component (if applicable):
Fedora core 8 Linux version 220.127.116.11-64.fc8
(firstname.lastname@example.org) (gcc version 4.1.2 20070925 (Red Hat
4.1.2-33)) #1 SMP Sat Mar 29 09:54:46 EDT 2008
Just boot fc8 disc or fc9 disc to have the same errors
I must wait over 5 minutes to reach the login screen of fedora because I have
thoses errors when I boot.
I can't see the drive with fdisk -l
Using my optical drive to install linux / read dvd movies etc...
I have also a bios bug #81 found when I start fedora
Created attachment 304099 [details]
The drive reporting diagnositic failure would seem indicative of a hardware
fault of some sort.
The BIOS bug is just that, nothing we can do about it (we work around it enough
already, we're just reporting that we did so).
This is a common problem with the amilo xa series.
The fujitsu amilo xa 2528 have the same problem (
Follow-up sent to linux-ata@vger
Thank you dave.
I don't know why but I can run the fedora core 6 dvd installer without problem,
my optical drive work like a charm ... but this is fedora core 6 :-/
Updated today to kernel 18.104.22.168-85.fc8 #1 SMP Sat Apr 19 12:39:34 EDT 2008 i686
athlon i386 GNU/Linux, still no progress
(In reply to comment #3)
> This is a common problem with the amilo xa series.
> The fujitsu amilo xa 2528 have the same problem (
> http://forum.ubuntu-nl.org/message/214415 )
That is reported as rawhide bug 441752
Could you update this bug for fedora 9 ? the problem still persist
There is a fix for kernel 2.6.28-rc3 here :
Hope to see this fix on the next fedora release !
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.
More information and reason for this action is here:
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '10'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 10's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.