Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Thanks for the bump(s) I didn't see this yesterday
Ok, so it looks like you don't have the append line in there, let's make it global, so just below timeout enter:
To do this with vi, type, put your cursor on the timeout line and then type:
The space between o and the append statement is only to show the different commands, but for you the o and append should be together, so looking at your keys would look like this:
But looking at the screen you'll see that the o starts a new line and puts you in edit mode in vi. So now we just need to save and exit, easiest way in vi is:
SHIFT plus ZZ and that's it. It'll save and exit. Then we need to rerun lilo to save the changes to the MBR so:
And watch for any errors, if you see one, post it up.
Reboot, if there are no errors, and then:
cdrecord -scanbus (as root)
and see if your drive gets detected this time.
ok 3 things. im not really sure how to edit it. and i dont know what vi is either. and its both my drives that wont detect. main cdrom dirve and Cdburner. i was mainly focusing on the burner. because i dont need to copy any cds as of yet. thx
vi is a text editor. You don't have to use vi, but it's just universal and I've been doing my best lately to not be distro specific. You can use any text editor you'd like to add that line. Any. So if you can get into a gui, you can use gedit, kwrite, kate... in the command line you can use joe, nano, pico, vim...
If you wanted to you could probably even use OpenOffice
Yeah, this will only set it up for the burner for now (your burner is the CR-48X5TE and not the Samsung correct?). We need to make sure that works before moving on
Distribution: openSuSE 42.1_64+Tumbleweed-KDE, Mint 17.3
Originally posted by BmxFace
...do i do the same just below the other one? with hda=ide-scsi?
Sure. Worst case is that hda doesn't work.
If I remember correctly (I use GRUB) LILO displays a boot-up screen, where you can interrupt the boot process (<F2> in KNOPPIX) to type in options. You can type in exactly the same (append="hda=ide-scsi"), and it should work without the need to edit -- which you can still do later.
Your symlinks are going to pointing to /dev/hdb and /dev/hda respectively. Your devices are no longer known as this, but rather scd0 and scd1 because of the scsi emulation. You will need to recreate the symlinks to show this new device so applications that use "/dev/cdrom" and "/dev/dvd" can properly find them. To create (or recreate) symlinks, use this format:
ln -sf /dev/scdX /dev/cdrom
And so on, where X is the device that is your main cdrom (scd1 or scd0 likely use 'eject scd0 and eject scd1 to find out which is which, you can also grep your dmesg:
dmesg | grep scd*
And look for your scd0/1 drives and which is which )