Bug 143311 - No more scsi burner in FC3 Bad
Summary: No more scsi burner in FC3 Bad
Status: CLOSED DUPLICATE of bug 138739
Alias: None
Product: Fedora
Classification: Fedora
Component: udev   
(Show other bugs)
Version: 3
Hardware: x86_64 Linux
medium
high
Target Milestone: ---
Assignee: Harald Hoyer
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-12-18 18:05 UTC by Nicola
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 19:07:44 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Nicola 2004-12-18 18:05:27 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.3)
Gecko/20041020 Galeon/1.3.18

Description of problem:
In FC2 all was fine. In FC3, no more scsi yamaha burner.
cdrecord --scanbus gives:
       0,0,0     0) *
        0,1,0     1) *
        0,2,0     2) *
        0,3,0     3) 'ADAPTEC ' 'ACB-5500        ' 'FAKE' NON CCS Disk
        0,4,0     4) *
        0,5,0     5) *
        0,6,0     6) *
        0,7,0     7) *

The burner disappeared from the system.
It used to be present before.

Version-Release number of selected component (if applicable):
udev-039-10.FC3.6

How reproducible:
Always

Steps to Reproduce:
1. Install FC3 x86_64
2. Fire k3b
3. No more scsi burner
    

Actual Results:  Scsi Yamaha burner disappeared

Expected Results:  It should work as usual

Additional info:

udev doesn't create the relevant device, I suppose.

Comment 1 Sitsofe Wheeler 2004-12-19 22:23:40 UTC
Might be related to bug #138739

Comment 2 Harald Hoyer 2005-01-20 16:13:04 UTC

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

Comment 3 Red Hat Bugzilla 2006-02-21 19:07:44 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


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