I have noticed that my CD-R/W drives, two drives one is just a CD-R and the other is a CD-RW, they will nether read or burn a CD while Beta 5 is running, I did not upgrade to Beta 5+ because RC1 will be out soon so I might as well save my bandwidth, I know the CD-R drive works because it is what I used to boot the Live-cd/installer for Beta 4 when I set the system up. The CD-RW drive I don’t know if it works because I just found it in storage and I was wanting to test if it works. Is this a known problem, with Beta 5, and if details on the drives is needed then ask and you shall receive. 
Yast > Hardware > Hardware Info are they detected?
Best I can do now is opensuse how to detect CD-RW - Google Search
Do You have KDE4-k3b installed?
Maybe you need to install a driver for your model CD-RW controller; check the hardware compatability list on the openSUSE Wiki.
http://www.google.com/linux?hl=en&q=opensuse+how+to+detect+CD-RW+post+install&btnG=Search
Yes they are detected by the system the read-only is sr0 and the burner is sr1. I have the KDE3 version of K3B installed and it detects both drives but it can not detect the medium in the drive whether it is a blank CD or a already burnt one. Sorry for the lack of details in my original post but I wasn’t at the machine and couldn’t get any real details on the system.
I have pastebined details on my drives here, mostly to save space in this post, pastebin - collaborative debugging tool
1st, I’m no expert. You may want to PM ken_yap & ask him to look at this post;)
I would swap those around & make the burner /dev/sr0; since about 10.3 it does make a difference. I have found that my burner works best on sr0 & I make far fewer coasters.
Also in k3b look at settings > configure k3b > devices What does it say there?
Read that part at the top; try “Add” then check permissions.
Also as I recall, with an iso selected & a CD/DVD in the chute, there should be a device check button to try (but you don’t want to do that each time).
snakedriver wrote:
>
> 1st, I’m no expert. You may want to PM ken_yap & ask him to look at
> this post;)
>
> I would swap those around & make the burner /dev/sr0; since about 10.3
> it does make a difference. I have found that my burner works best on
> sr0 & I make far fewer coasters.
>
That seems weird that it would make a difference as to which is the master and which is the slave but I can try it. Also right now being able to burn is not my big concern I need my drives to be able to read more than I need to burn, I can just hook my laptop up to the network pull what needs to be burned to that and have at it.
> Also in k3b look at settings > configure k3b > devices What does it say
> there?
> Read that part at the top; try “Add” then check permissions.
>
The drives are detected and setup correctly in K3B, that was one of the first places I checked after realizing it wasn’t reading CDs.
> Also as I recall, with an iso selected & a CD/DVD in the chute, there
> should be a device check button to try (but you don’t want to do that
> each time).
>
>
Doesn’t help it still is convened that there is no CD in the drive no matter how many disks I put in, and I know there is nothing wrong with the disks because other machines read them just fine.
–
“We must plan for freedom, and not only for security, if for no other reason than only freedom can make security more secure.” Karl Popper
I would disconnect the unknown drive and see if the CD-R works again. A bad drive on an IDE bus can ruin the connection for the other drive. Test them one at a time. Perhaps there was a good reason the CD-RW was in storage, eh?
And of course we’re assuming you set up the jumpers correctly.
I’m guessing so, but if the CD-RW is broken then storage is not the best place for it. I know the jumpers are correct because I had to reset them so that the CD-R (sr0) is set to master and the CD-RW (sr1) is set to slave, and the are connected to the IDE cable correctly. I will post my findings from testing the drives individually Wednesday, the soonest I can get back to that machine. This might be worth pointing out, but this problem only happens when an OS is loaded because I had both drives connected to the system in this configuration when I installed Beta 4, so the system had no problem when it came to booting from CD, of course I used the CD-R for the install and because the Boot from CD system might be able to come over the problem.
Sorry if this question is too much trivial
Did you try to mount it manually (from the CLI)? I remember a problem with hal in beta 5, now solved in 5.2
No I have not tried to manually mount the CDs, but if there is a problem with hal then it would be worth a shot.
- vendion,
my laptop didn’t write CDs until the latest update, so give RC1 a try.
Uwe
Uwe Buckesfeld wrote:
> * vendion,
>
> my laptop didn’t write CDs until the latest update, so give RC1 a try.
>
> Uwe
That is what I was planning on, but RC1 isn’t officially released yet is it? I don’t want to waste bandwidth, I get enough hassle when I run zypper dup and so to cut down on that I’m not going to do any plus releases unless absolutely needed.
“We must plan for freedom, and not only for security, if for no other reason than only freedom can make security more secure.” Karl Popper
On 11/26/2008 Adam Jimerson wrote:
> That is what I was planning on, but RC1 isn’t officially released yet
> is it?
Tomorrow.
Uwe