290289 – SATA DVD is not accessible after reboot, but hwinfo --cdrom puts it back to life

Bug 290289 - SATA DVD is not accessible after reboot, but hwinfo --cdrom puts it back to life

Summary: SATA DVD is not accessible after reboot, but hwinfo --cdrom puts it back to life

Status:	RESOLVED DUPLICATE of bug 286132

Alias:	None

Product:	openSUSE 10.3
Classification:	openSUSE
Component:	Other (show other bugs)
Version:	Alpha 5
Hardware:	x86-64 openSUSE 10.3

Priority:	P5 - None Severity: Major (vote)
Target Milestone:	---
Assignee:	E-mail List
QA Contact:	E-mail List

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2007-07-07 15:23 UTC by Mészáros Gyula
Modified:	2007-07-10 20:28 UTC (History)
CC List:	1 user (show)

See Also:
Found By:	Beta-Customer
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Mészáros Gyula 2007-07-07 15:23:22 UTC

Hardware: Asus M2A-VM motherboard (AMD 690G/ATI SB600 chipsets), a Samsung SATA HDD as SATA-1 and an LG SATA DVD as SATA-4. The SATA controller is set to AHCI in BIOS. I'm afraid no released operating system (openSUSE 10.2, Ubuntu 7.04, Solaris 10.2 were tried) can be installed to this bloody MB, and no Windows XP either.
After booting /dev/sr0 is not accessible. Then I enter hwinfo --cdrom and /dev/sr0 magically starts to work. The phenomenon happens at every boot.
This bug may be similar to 229260 and/or 263361 but I wasn't sure so I entered it  as a separate one.

Comment 1 Jogchum Reitsma 2007-07-10 18:53:55 UTC

The bug occurs here too, on 10.3 alpha5. The workaround with hdinfo --cdrom works with me too. If the workaround is applied when k3b is open, k3b scrashes, but after restarting k3b the dvd station is seen OK.

System is MSI K8N Master2FAR mb, two single core Opterons, 2GB memory, Maxtor 200GB IDE, 1 Maxtor 300GB SATA, one Seagate 320 GB SATA.

The system is dual boot, 10.3 and 10.2; 10.2 doesn't show this behaviour.

Comment 2 Hans-Peter Holler 2007-07-10 20:28:11 UTC


*** This bug has been marked as a duplicate of bug 286132 ***