Greetings, all. I didn't find an SDB entry or FAQ about this specific symptom, and Google was not helpful because I'm not quite sure what to call it. Can somebody tell me: a) is this [below] expected/proper behavior b) what to fix, if it's not correct? I have my hard drives on my primary IDE. On my secondary IDE, I have: PLEXTOR PLEXWriter 16/10/40A (sd0) and Pioneer 116 DVD-ROM (sd1) In SuSE 8.1 (fresh install, not an update), the KDE Control Module Available Hardware app reports them as: PIONEER PLEXTOR CD-R PX-W1610A (wrench symbol) ( /dev/sd0 ) and PLEXTOR CD-R PX-W1610A (wrench symbol) ( /dev/sd1 ) and PLEXTOR CD-R PX-W1610A (X-stopsign symbol) ( /dev/hdd ) and Pioneer DVD-ROM ATAPIModel DVD-116 -122 (X-stopsign symbol) ( /dev/hdc ) If I click for "Details", the first two device representations show: configured No available Yes nedeed No while the second two device names (with status X on red stopsign) show: configured Yes available No nedeed No If I select "Configure" for ANY of them, YaST demands my root pw and then opens to a CD/DVD device integration dialog, which shows all detected drives. The YaST list contains only the first two of the four items that were shown in "Available Hardware - KDE Control Module"... the ones with the WRONG, INCORRECT, MIXED-UP, INTERMINGLED device identifiers, with empty check boxes beside the names (meaning that they are not "integrated into the system", yet). The dialog explicitly does not give me an opportunity to declare or integrate the third and fourth (properly named?) devices in my list, above, and I similarly can't just overtype the broken names with "correct" device names. So, I abort before commiting to something that seems broken. Why would SuSE 8.1 / YaST2 (installer from DVD) mix parts of the names of the two drives, when it detects them? By that, I mean, why would it take the word "Pioneer" from the Pioneer DVD drive and insert it into the the name of the Plextor CD-R? These are two different physical devices, from two different companies. Yes, before anybody asks, one is Master and the other is jumpered as Slave. What is a SAFE approach to fixing this broken naming? Is it necessary/desirable to have the names correct, or should I just let YaST "Configure/integrate" them as it finds them, with screwy names? Should I expect to have grief later on? Does IDE bus care about which drive is physically connected to the nearer or farther connector on a cable (I thought it did not, if the cable contained no crossover), or is it only important that one drive be jumpered as Master and one as Slave (my current belief, but I'm trying to understand what would have confused YaST2 hardware detection)?? /kevin