On Wed, 20 Oct 1999 15:27:09 +0200, Sean Groarke wrote:
Stanley
Yes - Passing kernel parameters from lilo, but I'm a little confused by Jon's idea that this is "ugly and unnecessary"!!
Ahh, well, we'll just forget that I said that, okay :)?
The way I do it is edit /etc/lilo.conf to add the line append="hdd=ide-scsi" to the appropriate boot image, then re-run lilo and there you have it - fully automated kernel parameter passing.
You can also do this in YaST :)
Ugly and unnecessary? Elegant and essential, at least IMHO!
Let's explore this, shall we :)? I've always been a DIY kind of guy. I always enjoyed building my own kernels, hacking my own rc.config, and other things that Old-Skool (tm) hackers like to do. I suppose that lately I've gotten lazy ;), and I'm trying some new angles. One of the things I'd like to do before I go to the MULUG Expo this weekend is to make a couple of CDs to take with me. My problem is that when I compile my own kernels, cdrecord -scanbus locks up my system so hard that I have to cycle the power. I think that an elegant way to handle this would probably be to use the ide-scsi module, loaded by the kernel from LILO. The CD-R is /dev/hdd, and the only thing I use it for is burning (with limited success, we now have more coasters than table top space at home ;). Does this actually work for you? -- -=|JP|=- (Resident GNUbie) Jon Pennington | SuSE Linux 6.2 -o) super-suser@excite.com | Kernel 2.2.10 /\\ Kansas City, Missouri | AMD K6-III 450 _\_V ________________________________________________________________ Get FREE voicemail, fax and email at http://voicemail.excite.com Talk online at http://voicechat.excite.com -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Jon Pennington wrote:
On Wed, 20 Oct 1999 15:27:09 +0200, Sean Groarke wrote:
Stanley
Yes - Passing kernel parameters from lilo, but I'm a little confused by Jon's idea that this is "ugly and unnecessary"!!
Ahh, well, we'll just forget that I said that, okay :)?
The way I do it is edit /etc/lilo.conf to add the line append="hdd=ide-scsi" to the appropriate boot image, then re-run lilo and there you have it - fully automated kernel parameter passing.
You can also do this in YaST :)
Ugly and unnecessary? Elegant and essential, at least IMHO!
Let's explore this, shall we :)? I've always been a DIY kind of guy. I always enjoyed building my own kernels, hacking my own rc.config, and other things that Old-Skool (tm) hackers like to do. I suppose that lately I've gotten lazy ;), and I'm trying some new angles.
One of the things I'd like to do before I go to the MULUG Expo this weekend is to make a couple of CDs to take with me. My problem is that when I compile my own kernels, cdrecord -scanbus locks up my system so hard that I have to cycle the power. I think that an elegant way to handle this would probably be to use the ide-scsi module, loaded by the kernel from LILO. The CD-R is /dev/hdd, and the only thing I use it for is burning (with limited success, we now have more coasters than table top space at home ;). Does this actually work for you?
I may just be lucky and I'm certainly too much of a newbie to do too much command line stuff but my major success with SuSE has been getting my cd writer to actually work. It's an HP7200i ATAPI drive and is connected as slave. Burning cd's had got so unreliable in W95 that I had virtually decided that the drive itself was faulty. Anyway I recompiled the kernel with SCSI emulation, SCSI generic support etc, built in, not as modules, edited fstab to include the ordinary cdrom drive as scd0 and the writer as scd1 and tried xcdroast. The result has been unqualified success. I have not yet tried burning any data cd's but have successfully burnt about 20 audio cds with no coasters at all. I must say that I find xcdroast brilliant, as I say I'm not much up on command lines so couldn't get cdrecord by itself to work, and none of the CDR gui's that now come with KDE seems to find the drives. But xcdroast does, so I'm more than happy with that. So the original problem was the complete instability of Windoze. Mike
-- -=|JP|=- (Resident GNUbie) Jon Pennington | SuSE Linux 6.2 -o) super-suser@excite.com | Kernel 2.2.10 /\\ Kansas City, Missouri | AMD K6-III 450 _\_V
________________________________________________________________ Get FREE voicemail, fax and email at http://voicemail.excite.com Talk online at http://voicechat.excite.com
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Michael, Hmmm - that's given me an idea too! I setup the CD-RW pretty much as you, except I haven't listed either CD in the fstab - I just let xcdroast go find 'em itself (and I fear it's using cdrecord -scanbus underneath the posh exterior, so Jon might still be stuffed... :-( ) The only prob I get is that when my CD-RW is running as emulated SCSI it cannot read audio tracks under xcdroast, although it can under other tools. I've tried the -usecdparanoia option, but it makes no difference. Having said that, I still stick with xcdroast as it is a completely fabulous piece of software, and there's a new version coming out sometime soon which looks absolutely fantabulous from the web-site! I was amused to hear that you had problems under Windows - my CD-RW has marked an important watershed for me, that I'm sure every ex-Windows-moving-to-Linux-person gets to at some stage. When I received my shiny new CD-RW, I set it up under Linux and have never even bothered to install the Windows software. Trivial, but a "first" for me!! Oh yeah - Jon: just thought - if cdrecord -scanbus fails, howsabout sgcheck ? It's part of a scsi tools packge on the CDs (the one that comes with dire warnings about the end of the world if you misue it, or some such off-putting welcome!) Give that a whirl. Cheers, Sean Michael Norman wrote:
Jon Pennington wrote:
On Wed, 20 Oct 1999 15:27:09 +0200, Sean Groarke wrote:
Stanley
Yes - Passing kernel parameters from lilo, but I'm a little confused by Jon's idea that this is "ugly and unnecessary"!!
Ahh, well, we'll just forget that I said that, okay :)?
The way I do it is edit /etc/lilo.conf to add the line append="hdd=ide-scsi" to the appropriate boot image, then re-run lilo and there you have it - fully automated kernel parameter passing.
You can also do this in YaST :)
Ugly and unnecessary? Elegant and essential, at least IMHO!
Let's explore this, shall we :)? I've always been a DIY kind of guy. I always enjoyed building my own kernels, hacking my own rc.config, and other things that Old-Skool (tm) hackers like to do. I suppose that lately I've gotten lazy ;), and I'm trying some new angles.
One of the things I'd like to do before I go to the MULUG Expo this weekend is to make a couple of CDs to take with me. My problem is that when I compile my own kernels, cdrecord -scanbus locks up my system so hard that I have to cycle the power. I think that an elegant way to handle this would probably be to use the ide-scsi module, loaded by the kernel from LILO. The CD-R is /dev/hdd, and the only thing I use it for is burning (with limited success, we now have more coasters than table top space at home ;). Does this actually work for you?
I may just be lucky and I'm certainly too much of a newbie to do too much command line stuff but my major success with SuSE has been getting my cd writer to actually work. It's an HP7200i ATAPI drive and is connected as slave. Burning cd's had got so unreliable in W95 that I had virtually decided that the drive itself was faulty.
Anyway I recompiled the kernel with SCSI emulation, SCSI generic support etc, built in, not as modules, edited fstab to include the ordinary cdrom drive as scd0 and the writer as scd1 and tried xcdroast. The result has been unqualified success. I have not yet tried burning any data cd's but have successfully burnt about 20 audio cds with no coasters at all. I must say that I find xcdroast brilliant, as I say I'm not much up on command lines so couldn't get cdrecord by itself to work, and none of the CDR gui's that now come with KDE seems to find the drives. But xcdroast does, so I'm more than happy with that.
So the original problem was the complete instability of Windoze.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Sean Groarke wrote:
Michael,
Hmmm - that's given me an idea too! I setup the CD-RW pretty much as you, except I haven't listed either CD in the fstab - I just let xcdroast go find 'em itself (and I fear it's using cdrecord -scanbus underneath the posh exterior, so Jon might still be stuffed... :-( )
The only prob I get is that when my CD-RW is running as emulated SCSI it cannot read audio tracks under xcdroast, although it can under other tools. I've tried the -usecdparanoia option, but it makes no difference
Have you set Audio-Read-Mode to "ATAPI" ?
Having said that, I still stick with xcdroast as it is a completely fabulous piece of software, and there's a new version coming out sometime soon which looks absolutely fantabulous from the web-site!
I was amused to hear that you had problems under Windows - my CD-RW has marked an important watershed for me, that I'm sure every ex-Windows-moving-to-Linux-person gets to at some stage. When I received my shiny new CD-RW, I set it up under Linux and have never even bothered to install the Windows software. Trivial, but a "first" for me!!
Oh yeah - Jon: just thought - if cdrecord -scanbus fails, howsabout sgcheck ? It's part of a scsi tools packge on the CDs (the one that comes with dire warnings about the end of the world if you misue it, or some such off-putting welcome!) Give that a whirl.
Cheers, Sean
Michael Norman wrote:
Jon Pennington wrote:
On Wed, 20 Oct 1999 15:27:09 +0200, Sean Groarke wrote:
Stanley
Yes - Passing kernel parameters from lilo, but I'm a little confused by Jon's idea that this is "ugly and unnecessary"!!
Ahh, well, we'll just forget that I said that, okay :)?
The way I do it is edit /etc/lilo.conf to add the line append="hdd=ide-scsi" to the appropriate boot image, then re-run lilo and there you have it - fully automated kernel parameter passing.
You can also do this in YaST :)
Ugly and unnecessary? Elegant and essential, at least IMHO!
Let's explore this, shall we :)? I've always been a DIY kind of guy. I always enjoyed building my own kernels, hacking my own rc.config, and other things that Old-Skool (tm) hackers like to do. I suppose that lately I've gotten lazy ;), and I'm trying some new angles.
One of the things I'd like to do before I go to the MULUG Expo this weekend is to make a couple of CDs to take with me. My problem is that when I compile my own kernels, cdrecord -scanbus locks up my system so hard that I have to cycle the power. I think that an elegant way to handle this would probably be to use the ide-scsi module, loaded by the kernel from LILO. The CD-R is /dev/hdd, and the only thing I use it for is burning (with limited success, we now have more coasters than table top space at home ;). Does this actually work for you?
I may just be lucky and I'm certainly too much of a newbie to do too much command line stuff but my major success with SuSE has been getting my cd writer to actually work. It's an HP7200i ATAPI drive and is connected as slave. Burning cd's had got so unreliable in W95 that I had virtually decided that the drive itself was faulty.
Anyway I recompiled the kernel with SCSI emulation, SCSI generic support etc, built in, not as modules, edited fstab to include the ordinary cdrom drive as scd0 and the writer as scd1 and tried xcdroast. The result has been unqualified success. I have not yet tried burning any data cd's but have successfully burnt about 20 audio cds with no coasters at all. I must say that I find xcdroast brilliant, as I say I'm not much up on command lines so couldn't get cdrecord by itself to work, and none of the CDR gui's that now come with KDE seems to find the drives. But xcdroast does, so I'm more than happy with that.
So the original problem was the complete instability of Windoze.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (3)
-
michael.norman1＠which.net -
sgroarke＠nortelnetworks.com -
super-suser＠excite.com