Hey all you newbies! I have seen many questions on this and very good directions on how to do this, but as a newbie, I thought I would offer my help after going thru the setup. These instructions come from the SuSE site, but I will try to simplify them further. The site is: http://sdb.suse.de/en/sdb/html/tbraza_ide_brenner.html My newbie interpretation follows: Problem: You want to use your IDE CD writer with SuSE Linux Solution: You must switch off the IDE support for all installed CD devices. To switch off the IDE support you have to login as root and start Yast, not Yast2, just Yast. Open a shell window, terminal window, whatever you want to call it and log in as root. At the prompt, type "su" (without quotes), which will prompt you for root password. Once in, type "Yast" to start it. Move to the "System Adminstration" selection, press enter, "Kernel", press enter, then "Boot Configuration", press enter, and then "LILO configuration", press enter. Once there you will see the "Appendline" text window where you will insert your devices. Here you will type: hdX=ide-scsi, where "X" is the device. (If you only have one, you will insert only one device, but if you have both a CDRW & a CDROM, you MUST insert both divided by a space or blank.) Here is a list of the available devices, it helps to know how your hardware is set up. hda=primary master (usually your main hard drive) hdb=primary slave hdc=secondary master (usually your first CD) hdd=secondary slave (usually your 2nd CD) *One device EX: hdc=ide-scsi *Two devices EX: hdc=ide-scsi hdd=ide-scsi (You have to load the scsi-emulation for all CDs, you can't change just one!) After typing in the appropriate devices, save the settings and leave Yast with the Esc key. This should take you back out to your shell prompt. Next you have to open the file: /etc/init.d/boot.local (7.2) or /sbin/init.d/boot.local (7.1 or earlier) and ADD this line to the end of the file in your editor: /sbin/modprobe ide-scsi The file (/etc/init.d/boot.local) should look like this: #!/bin/sh # #Copyright (c) 1996 SuSE GmbH Nuemberg, Germany. All rights reserved # #Author: Florian La Roche, 1996 # Werner Fink, 1996 # Burchard Steinbild, 1996 # #/sbin/init.d/boot.local # #script with local commands to be executed from init on system start up # ./etc/re.config # #Here you should add things, that should happen directly after booting #before we're going to the first run level # /sbin/modprobe ide-scsi (The kernal at this point doesn't recognize the cd drives as IDE devices any longer, they are now /dev/scd0 or scd1 or both, depending on the number of CDs you have installed. They are no longer known as /dev/hdc or hdd.) To change the settings, use these commands in the shell/terminal (console): ln -sf /dev/scd0 /dev/cdrecorder (if your first CD is the recorder). This creates the new link. If you use a second cd drive with scsi emualtion you need also: ln -sf /dev/scd1 /dev/cdrom (if you second CD is cd-rom only, otherwise switch the two commands */dev/cdrom or /dev/cdrecorder*) To mount the devices correctly, edit the file: /etc/fstab Replace the line for the cd writer (if it exists, otherwise create it) with: /dev/cdrecorder /media/cdrecorder auto ro,noauto,user,exec 0 0 The line for the cd-rom device should look like this (if not already there): /dev/cdrom/ /media/cdrom auto ro,noauto,user,exec 0 0 (For versions earlier than <7.2, leave the /media out and write only /cdrecorder and /cdrom) The directories /media/cdrecorder and /media/cdrom (or without /media for versions earlier than <7.2) should already exist, if not create them with: mkdir /media/cdrecorder mkdir /media/cdrom If you are using KDE gui, then also make sure your device icons for CD-R and CDROM have the right properties which should be /dev/cdrecorder and /dev/cdrom (read only checked). You check this by right clicking on the device icon and selecting properties from the menu. After all this, reboot the computer and all devices should be recognized correctly now and these scsi-emulated devices can be used by your cd burning software while logged in as "root", unless you have given your user "super privileges" for such things. I always just log in as root myself, but your mileage may vary. ;-) And as always, "Have a lot of fun!" Hope this helps other newbies. And this wasn't done to say other explanations weren't good also, but the others are not always in "newbie" talk! :-) end of line Tracer -- ---KMail 1.3--- SuSE Linux v7.2--- Registered Linux User #225206 /tracerb@sprintmail.com/ *Magic Page Products* *Team Amiga* http://home.sprintmail.com/~tracerb
On Mon, Sep 03, 2001 at 01:00:42PM -0400, Tracer Bullet wrote:
Hey all you newbies! I have seen many questions on this and very good directions on how to do this, but as a newbie, I thought I would offer my help after going thru the setup. These instructions come from the SuSE site, but I will try to simplify them further. The site is: http://sdb.suse.de/en/sdb/html/tbraza_ide_brenner.html
My newbie interpretation follows: Problem: You want to use your IDE CD writer with SuSE Linux Solution: You must switch off the IDE support for all installed CD devices.
This is an incorrect statement. ide-scsi is needed for CD writer only.
To switch off the IDE support you have to login as root and start Yast, not Yast2, just Yast. Open a shell window, terminal window, whatever you want to call it and log in as root. At the prompt, type "su" (without quotes), which will prompt you for root password. Once in, type "Yast" to start it. Move to the "System Adminstration" selection, press enter, "Kernel", press enter, then "Boot Configuration", press enter, and then "LILO configuration", press enter. Once there you will see the "Appendline" text window where you will insert your devices. Here you will type: hdX=ide-scsi, where "X" is the device. (If you only have one, you will insert only one device, but if you have both a CDRW & a CDROM, you MUST insert both divided by a space or blank.) Here is a list of the available devices, it helps to know how your hardware is set up.
hda=primary master (usually your main hard drive) hdb=primary slave hdc=secondary master (usually your first CD) hdd=secondary slave (usually your 2nd CD)
*One device EX: hdc=ide-scsi *Two devices EX: hdc=ide-scsi hdd=ide-scsi (You have to load the scsi-emulation for all CDs, you can't change just one!)
It IS possible to use scsi emulation for just one device. I use this in my lilo.conf: image = /boot/vmlinuz_24 label = 24 root = /dev/hda5 append="hdd=ide-scsi" I have a normal CD connected as secondary master (hdc) and CD-writer as secondary slave. I specify scsi emulation for CD-writer only.
After typing in the appropriate devices, save the settings and leave Yast with the Esc key. This should take you back out to your shell prompt. Next you have to open the file: /etc/init.d/boot.local (7.2) or /sbin/init.d/boot.local (7.1 or earlier) and ADD this line to the end of the file in your editor: /sbin/modprobe ide-scsi
The file (/etc/init.d/boot.local) should look like this: #!/bin/sh # #Copyright (c) 1996 SuSE GmbH Nuemberg, Germany. All rights reserved # #Author: Florian La Roche, 1996 # Werner Fink, 1996 # Burchard Steinbild, 1996 # #/sbin/init.d/boot.local # #script with local commands to be executed from init on system start up # ./etc/re.config # #Here you should add things, that should happen directly after booting #before we're going to the first run level # /sbin/modprobe ide-scsi
I also don't load ide-scsi module explicitely. I have a line alias scsi_hostadapter ide-scsi in my /etc/modules.conf file. Module is loaded when needed automatically.
(The kernal at this point doesn't recognize the cd drives as IDE devices any longer, they are now /dev/scd0 or scd1 or both, depending on the number of CDs you have installed. They are no longer known as /dev/hdc or hdd.) To change the settings, use these commands in the shell/terminal (console): ln -sf /dev/scd0 /dev/cdrecorder (if your first CD is the recorder). This creates the new link. If you use a second cd drive with scsi emualtion you need also: ln -sf /dev/scd1 /dev/cdrom (if you second CD is cd-rom only, otherwise switch the two commands */dev/cdrom or /dev/cdrecorder*)
To mount the devices correctly, edit the file: /etc/fstab Replace the line for the cd writer (if it exists, otherwise create it) with: /dev/cdrecorder /media/cdrecorder auto ro,noauto,user,exec 0 0
The line for the cd-rom device should look like this (if not already there): /dev/cdrom/ /media/cdrom auto ro,noauto,user,exec 0 0
(For versions earlier than <7.2, leave the /media out and write only /cdrecorder and /cdrom)
The directories /media/cdrecorder and /media/cdrom (or without /media for versions earlier than <7.2) should already exist, if not create them with: mkdir /media/cdrecorder mkdir /media/cdrom
If you are using KDE gui, then also make sure your device icons for CD-R and CDROM have the right properties which should be /dev/cdrecorder and /dev/cdrom (read only checked). You check this by right clicking on the device icon and selecting properties from the menu.
After all this, reboot the computer and all devices should be recognized correctly now and these scsi-emulated devices can be used by your cd burning software while logged in as "root", unless you have given your user "super privileges" for such things. I always just log in as root myself, but your mileage may vary. ;-)
Logging in as root is a bad security practice. You better use su to become root, or even better, configure sudo for use with cdrecord. -Kastus
And as always, "Have a lot of fun!" Hope this helps other newbies. And this wasn't done to say other explanations weren't good also, but the others are not always in "newbie" talk! :-)
end of line Tracer
On Monday 03 September 2001 02:14 pm, Konstantin (Kastus) Shchuka, you wrote: The site is:
This is an incorrect statement. ide-scsi is needed for CD writer only.
Kastus, go to the site, these are simplified instructions from SuSE! I realized as many do, that there are ways around everything and different ways to do them by users in the know, but these instructions work with no problems and are generally easy to follow. Think back to the time you were a "newbie" and then maybe you can understand better what it feels like to us. end of line Tracer ---------------------------
Logging in as root is a bad security practice. You better use su to become root, or even better, configure sudo for use with cdrecord.
-Kastus
You are right, logging in as root is hazardous for sure, but sometimes you have to take the risk! ;-) Also, some of us are actually using SuSE as a standard replacement OS on a desktop, no networking, etc involved. Yes, it's true, Linux is ready for the desktop! ;-) And there you go again with your expert thoughts talking over my head at least, what the heck is "sudo"? -- ---KMail 1.3--- SuSE Linux v7.2--- Registered Linux User #225206 /tracerb@sprintmail.com/ *Magic Page Products* *Team Amiga* http://home.sprintmail.com/~tracerb
On Mon, Sep 03, 2001 at 05:55:37PM -0400, Tracer Bullet wrote:
On Monday 03 September 2001 02:14 pm, Konstantin (Kastus) Shchuka, you wrote: The site is:
This is an incorrect statement. ide-scsi is needed for CD writer only.
Kastus, go to the site, these are simplified instructions from SuSE! I realized as many do, that there are ways around everything and different ways to do them by users in the know, but these instructions work with no problems and are generally easy to follow. Think back to the time you were a "newbie" and then maybe you can understand better what it feels like to us.
The page at the URL does not say in any place that if you use ide-scsi then you need to use it on all IDE drives. It is possible, but not required. That was my point. The problem is with TIMTOWTDI - there is more than one way to do it. Sometimes it may be confusing :-)
end of line Tracer ---------------------------
Logging in as root is a bad security practice. You better use su to become root, or even better, configure sudo for use with cdrecord.
-Kastus
You are right, logging in as root is hazardous for sure, but sometimes you have to take the risk! ;-) Also, some of us are actually using SuSE as a standard replacement OS on a desktop, no networking, etc involved.
Being root may be dangerous even on a standalone machine. One typo may cost you a lot. E.g. if you run cd / ; rm -rf as root it will just delete ALL your filesystem. If you run it as a regular user, it will may hurt just your home directory. It's usually recommended to "sit on your hands" before hitting Enter key being root.
Yes, it's true, Linux is ready for the desktop! ;-) And there you go again with your expert thoughts talking over my head at least, what the heck is "sudo"?
From man page for sudo:
sudo allows a permitted user to execute a command as the superuser or another user, as specified in the sudoers file. The real and effective uid and gid are set to match those of the target user as specified in the passwd file (the group vector is also initialized when the target user is not root). By default, sudo requires that users authenticate themselves with a password (NOTE: this is the user's password, not the root password). Once a user has been authenticated, a timestamp is updated and the user may then use sudo without a password for a short period of time (five minutes by default). In Linux (or UNIX generally) it is not the amount of information you have in your head which matters (though it is useful). Much more important is to know the way how to get information, use man pages, howto's, or even use google. And don't be afraid to learn. -Kastus
ide-scsi then you need to use it on all IDE drives. It is possible, but not required. That was my point. The problem is with TIMTOWTDI - there is more than one way to do it. Sometimes it may be confusing :-) -------------------------- Yes, it does Kastus, where in the world do you think I got it from? I didn't just come up with that, I don't know enough about such
------------------------ And thank you very much for stating the obvious! Being logged in as "root" is dangerous everyone, be careful you dolts! ;-) Still many
On Monday 03 September 2001 06:31 pm, Konstantin (Kastus) Shchuka, you wrote: KS> The page at the URL does not say in any place that if you use things yet to come up with obscure items yet, like TIMTOWTDI? What's that all about? Of course, there are different ways to do most everything, but you gotta learn the basics first, right? ******************** KS> Being root may be dangerous even on a standalone machine. One typo KS> may cost you a lot. E.g. if you run cd / ; rm -rf as root it will KS> just delete ALL your filesystem. If you run it as a regular KS> user, it will may hurt just your home directory. It's usually KS> recommended to "sit on your hands" before hitting Enter key being KS> root. things require you to do that, so there is no way to completely avoid being root sometimes, ya just gotta be careful. ***************
In Linux (or UNIX generally) it is not the amount of information you have in your head which matters (though it is useful). Much more important is to know the way how to get information, use man pages, howto's, or even use google. And don't be afraid to learn.
-Kastus
Thanks again for stating the obvious! That's what we are trying to do, in case you missed it, is learn the safe way of doing things then we can get wild & crazy later! :-) Explanations of things & how to do them are usually done by someone knowledgable or the writer of the programs. Anytime you, me or anyone else tries to explain something we are quite familar with, we often overlook the beginning things we had to struggle through to get to our present status. These are things we have to think about when explaining to others that are at a point we once were, otherwise frustration levels go way up, things are done wrong and we are sometimes scared away from things we were sure to enjoy. I don't want that to happen to potential new SuSE Linux users, I want them to come aboard and get into it like we all have!! Take care end of line Tracer -- ---KMail 1.3--- SuSE Linux v7.2--- Registered Linux User #225206 /tracerb@sprintmail.com/ *Magic Page Products* *Team Amiga* http://home.sprintmail.com/~tracerb
do: rpm -q xf86 here is what I get: poincare@linux:~ > rpm -q xf86 xf86-4.0.3-35
Thanks, I downloaded 4.1.0 and installed it, now how do switch it to 4.1.0? __________________________________________________ Do You Yahoo!? Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com
** Reply to message from telco soltn
Thanks, I downloaded 4.1.0 and installed it, now how do switch it to 4.1.0?
Look in /usr/X11R6/bin. There should be several executables that start "switch2xxx". Choose one and try it out. Ed Harrison, broadcasting on ----/ / _ ---/ / (_)__ __ ____ __ --/ /__/ / _ \/ // /\ \/ / -/____/_/_//_/\_,_/ /_/\_\ by SuSE(7.2), Kernel 2.4.6, X 4.1 or Windows98 (running in vmware 2.0.4 for fun) PolarBarMailer 1.20 with IBM JDK 1.3.0
Rafeal put up a make shift howto yesterday and that pretty much solved my problem. The only thing beyond that was to make the dev sr0(formerly hdc) and hdd with permission for user as myself and group as disk. Now I can run KOnCD from my user account without any problems. I starts up all the time. The howto at the website is essentially the same thing as was posted by Rafeal. However, I did not make the the 2nd cdrom (hdd) ide-scsi, I just kept it as generic. CD to CDR writing works fine. Now, if I can just figure out how to get both/either drives to read audio cds then I'm set. I can't mount audio cds - sends me a message the no file format was indicated. And If I use XMMS or Noatun I can see it reading the CD and can get a TOC but hear no sound. Tried to set the artswrapper to various permissions but no luck. I would like to copy the audio cds to the HD so I can pick various tracks for compilation on a CDR. Any Idea about this? Cheers, Curtis On Monday 03 September 2001 08:12 pm, Tracer Bullet wrote:
On Monday 03 September 2001 06:31 pm, Konstantin (Kastus) Shchuka, you wrote: KS> The page at the URL does not say in any place that if you use
ide-scsi then you need to use it on all IDE drives. It is possible, but not required. That was my point. The problem is with TIMTOWTDI - there is more than one way to do it. Sometimes it may be confusing :-) --------------------------
Yes, it does Kastus, where in the world do you think I got it from? I didn't just come up with that, I don't know enough about such things yet to come up with obscure items yet, like TIMTOWTDI? What's that all about? Of course, there are different ways to do most everything, but you gotta learn the basics first, right? ******************** KS> Being root may be dangerous even on a standalone machine. One typo KS> may cost you a lot. E.g. if you run cd / ; rm -rf as root it will KS> just delete ALL your filesystem. If you run it as a regular KS> user, it will may hurt just your home directory. It's usually KS> recommended to "sit on your hands" before hitting Enter key being KS> root.
------------------------
And thank you very much for stating the obvious! Being logged in as "root" is dangerous everyone, be careful you dolts! ;-) Still many things require you to do that, so there is no way to completely avoid being root sometimes, ya just gotta be careful. ***************
In Linux (or UNIX generally) it is not the amount of information you have in your head which matters (though it is useful). Much more important is to know the way how to get information, use man pages, howto's, or even use google. And don't be afraid to learn.
-Kastus
----------------------- Thanks again for stating the obvious! That's what we are trying to do, in case you missed it, is learn the safe way of doing things then we can get wild & crazy later! :-) Explanations of things & how to do them are usually done by someone knowledgable or the writer of the programs. Anytime you, me or anyone else tries to explain something we are quite familar with, we often overlook the beginning things we had to struggle through to get to our present status. These are things we have to think about when explaining to others that are at a point we once were, otherwise frustration levels go way up, things are done wrong and we are sometimes scared away from things we were sure to enjoy. I don't want that to happen to potential new SuSE Linux users, I want them to come aboard and get into it like we all have!! Take care end of line Tracer
On Mon, Sep 03, 2001 at 09:40:59PM -0500, Curtis Rey wrote:
Rafeal put up a make shift howto yesterday and that pretty much solved my problem. The only thing beyond that was to make the dev sr0(formerly hdc) and hdd with permission for user as myself and group as disk. Now I can run KOnCD from my user account without any problems. I starts up all the time. The howto at the website is essentially the same thing as was posted by Rafeal. However, I did not make the the 2nd cdrom (hdd) ide-scsi, I just kept it as generic. CD to CDR writing works fine.
Now, if I can just figure out how to get both/either drives to read audio cds then I'm set. I can't mount audio cds - sends me a message the no file format
It's really impossible to mount audio CD. Only data CDs can be mounted.
was indicated. And If I use XMMS or Noatun I can see it reading the CD and can get a TOC but hear no sound. Tried to set the artswrapper to various permissions but no luck. I would like to copy the audio cds to the HD so I can pick various tracks for compilation on a CDR. Any Idea about this?
Did you try cdparanoia? It's a command-line tool to rip audio CDs. Pretty simple in usage and very reliable. If all you need is to copy some (all) tracks from CD to HD, this is definitely a good thing to try. -Kastus
Cheers, Curtis
Yep, that be the one! Thanx much Kastus. :) On Monday 03 September 2001 10:04 pm, Konstantin (Kastus) Shchuka wrote:
On Mon, Sep 03, 2001 at 09:40:59PM -0500, Curtis Rey wrote:
Rafeal put up a make shift howto yesterday and that pretty much solved my problem. The only thing beyond that was to make the dev sr0(formerly hdc) and hdd with permission for user as myself and group as disk. Now I can run KOnCD from my user account without any problems. I starts up all the time. The howto at the website is essentially the same thing as was posted by Rafeal. However, I did not make the the 2nd cdrom (hdd) ide-scsi, I just kept it as generic. CD to CDR writing works fine.
Now, if I can just figure out how to get both/either drives to read audio cds then I'm set. I can't mount audio cds - sends me a message the no file format
It's really impossible to mount audio CD. Only data CDs can be mounted.
was indicated. And If I use XMMS or Noatun I can see it reading the CD and can get a TOC but hear no sound. Tried to set the artswrapper to various permissions but no luck. I would like to copy the audio cds to the HD so I can pick various tracks for compilation on a CDR. Any Idea about this?
Did you try cdparanoia? It's a command-line tool to rip audio CDs. Pretty simple in usage and very reliable. If all you need is to copy some (all) tracks from CD to HD, this is definitely a good thing to try.
-Kastus
Cheers, Curtis
On Monday 03 September 2001 11:04 pm, Konstantin (Kastus) Shchuka, you wrote:
Now, if I can just figure out how to get both/either drives to read audio cds then I'm set. I can't mount audio cds - sends me a message the no file format
It's really impossible to mount audio CD. Only data CDs can be mounted.
-Kastus
Now there you go again Kastus, giving out bogus information! If you check the latest KDE 2.2 update you will maybe notice that reading audio CDs has been enabled in the new setup! SIASD! end of line Tracer -- ---KMail 1.3--- SuSE Linux v7.2--- Registered Linux User #225206 /tracerb@sprintmail.com/ *Magic Page Products* *Team Amiga* http://home.sprintmail.com/~tracerb
On Tuesday 04 September 2001 17.16, Tracer Bullet wrote:
On Monday 03 September 2001 11:04 pm, Konstantin (Kastus) Shchuka,
you wrote:
Now, if I can just figure out how to get both/either drives to read audio cds then I'm set. I can't mount audio cds - sends me a message the no file format
It's really impossible to mount audio CD. Only data CDs can be mounted.
-Kastus
---------------------------------- Now there you go again Kastus, giving out bogus information! If you check the latest KDE 2.2 update you will maybe notice that reading audio CDs has been enabled in the new setup! SIASD! end of line Tracer
Read, yes. Mounted, no. If you try to mount an audio CD you'll get the error Curtis mentions, because there is no file system on an audio CD. That doesn't mean konqueror can't read them (although I haven't been able to get it to work while using scsi emulation), but you really can't mount them. EOT Anders
participants (6)
-
Anders Johansson -
Curtis Rey -
Ed Harrison -
Konstantin (Kastus) Shchuka -
telco soltn -
Tracer Bullet