Testing Mageia3 Beta1 KDE Live DVD Computer with ASUS M2N SLI mainboard Nvidia Geforce 210 graphic card two internal SATA harddisks (using sata_nv module) one internal IDE harddisk (using pata_amd module) one external usb harddisk one external firewire harddisk one internal IDE DVD writer (using pata_amd module) one internal IDE DVD reader (using pata_amd module) The Live DVD is inserted in the DVD writer slot and used as a live DVD https://bugs.mageia.org/show_bug.cgi?id=4997 doesn't appear anymore : no need to use the workaround adding kernel option rdloaddriver=pata_amd ... Nice the dvd drives appear as sr0 and sr1 in /dev/ and the IDE harddisk as sdc but, both of sr0 and sr1 are linked to /dev/cdrom :-( => Kscd can't display the content nor play the audioCD in DVD reader slot this may be similar to https://bugs.mageia.org/show_bug.cgi?id=5533#c7 NB : on an installed Mageia2 (using the kernel option rdloaddriver=pata_amd) the dvd writer sr0 is linked to /dev/cdrom to /dev/cdrw to dev/dvd to dev/dvdrw the dvd reader sr1 is linked to /dev/cdrom1 and to /dev/dvd1
Whiteboard: (none) => MGA3 Beta1 LiveDVD
also not a dup of bug 7919 ?
Hi Manuel ! Nothing linked to bug 7919 Perhaps a typo ?
yes, bug 7913 in fact
Ah ! OK ! So it's not really a duplicate ... but they may be linked : in bug 7913, (alpha release) the pata module was not loaded and the ide drives were not identified as srx but as hdx... needing a workaround. now this problem is corrected : the pata_module is loaded, so bug 7913 seems to be resolved and fixed... I will investigate later . but there still remains a linkage problem in /dev/ directory when there are two dvd slots : like in https://bugs.mageia.org/show_bug.cgi?id=5533#c7
arf ok (I swim in all these bugs :s)
Hi Manuel ! You won't have to swim any more with bug 7913 and bug 5533 : I proposed to close them (bug 5533 surely but for bug 7913 we need other tests) This bug 8524 seems to be only a udev problem (some rules to add in the LiveDVD ?)
CC: (none) => mageia, mageia, tmb
Can this be closed now?
No answer to #c7 for almost a year. Closing as old. If you have good reason you can reopen it against current release media (5beta1 or higher), older ones can not be fixed at this stage.
Status: NEW => RESOLVEDResolution: (none) => OLD