Re: Problem with installation and SCSI CD/R.
Hi. I have a problem installing Suse 7.3 on my machine (which had suse 7.0). I should say on the outset that this is a PPC machine, but I think the problem is probably not CPU-related, so maybe the experience of people here may help. Basically, I have an internal IDE hard disk (on which I install), an external SCSI hard disk, and an external SCSI cd/r (from which I install). Kernel 2.2.16 (the old one I used) recognizes the SCSI devices without a problem. However, the SuSE installer runs kernel 2.4.12 (I think), and that one displays the devices correctly (e.g. disk at scsi bus 0, id 1, lun 0, cd at...). But then it gets stuck. As if, once recognizing the devices, it can't actually access the CD/R. Once or twice it got past this stage, and into linuxrc, but then linuxrc did not find the CD/R. So, I was thinking that one of two things are possible: 1. This kernel is overly sensitive to SCSI quirks (such as cable length, SCSI ID voodoo, and stuff). If 2.2.16 worked with this CD rom and you did not change the hardware then cabling problems is not much likely. What is the behavior with MS (in case you have it installed)? 2. The kernel, as compiled by SuSE, lacks some crucial module of which I'm not aware. If the first case is true, I guess I can shorten the cables by replacing my dysfunctional internal SCSI cd/rom with some new device (probably cd/rw, while I'm at it), so I only have one external device and about 1.5 meter less of cable. Of course, this is a bit of an expense with some added problems, such as - is a Yamaha CRW2100SNB supported by kernel 2.4.x). If the second case is true, I need to know what module I'm missing. The external CD/R is an old TEAC (I can find out the exact model once I'm back home). You might try to compare the .config of the 2.2 and the 2.4 kernels. Any help appreciated. Herouth Perhaps the scsitools package can help? The CD-ROM HOWTO? Posting the relevant boot messages? -- Shaul Karl email: shaulka(at-no-spam)bezeqint.net Please replace (at-no-spam) with an at - @ - character. (at-no-spam) is meant for unsolicitate mail senders only. = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: Problem with installation and SCSI CD/R.
On Sun, 13 Jan 2002, Shaul Karl wrote: suse 7.0). I should say on the outset that this is a PPC machine, but What is the behavior with MS (in case you have it installed)? well, when you find MSwin for PPC on the shelf, tell me. Herouth: ppc is quite rare in Israel, and you haven't even said if we're talking here about a Mac, IBM RS6000 or something else. I think higher quality support and info will be found in some LinuxPPC forum or mailing list... Good luck. -- (@-Please do NOT cc: me answers posted also to the list //\Send me private mail at YourName (at) ira.abramov.org v_/_ to send me spam please use: cat spam.txt /dev/hda = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: Problem with installation and SCSI CD/R.
Hi! I have A SCSI CDRW on a regular Intell system with SuSE 7.3. I did the text mode install with yast1 from diskette. After the inital boot, it asks if you have any modules to install. Well, you sure do. Say yes, and you are asked to use the second diskette to select modules for your SCSI peripherals. At the end of the day, it creates an initrd image with these things built in so you can see them after a normal boot (otherwise you have to insmod everything by hand!). Most of this stuff is covered in the supplied Reference Manual. One gotcha: mkinitrd is NOT supplied with SuSE. They have there own thing called mk_initrd which does much the same thing. I found 7.1 and 7.3 to be quite different from 7.0 in the way it does this stuff - probably because of the move from the 2.2.x to the 2.4.x kernels. Bottom line is that once you have preselected the modules for your SCSI CDR, you can then use it for the rest of the install. Regards, DAF Shaul Karl wrote: Hi. I have a problem installing Suse 7.3 on my machine (which had suse 7.0). I should say on the outset that this is a PPC machine, but I think the problem is probably not CPU-related, so maybe the experience of people here may help. Basically, I have an internal IDE hard disk (on which I install), an external SCSI hard disk, and an external SCSI cd/r (from which I install). Kernel 2.2.16 (the old one I used) recognizes the SCSI devices without a problem. However, the SuSE installer runs kernel 2.4.12 (I think), and that one displays the devices correctly (e.g. disk at scsi bus 0, id 1, lun 0, cd at...). But then it gets stuck. As if, once recognizing the devices, it can't actually access the CD/R. Once or twice it got past this stage, and into linuxrc, but then linuxrc did not find the CD/R. So, I was thinking that one of two things are possible: 1. This kernel is overly sensitive to SCSI quirks (such as cable length, SCSI ID voodoo, and stuff). If 2.2.16 worked with this CD rom and you did not change the hardware then cabling problems is not much likely. What is the behavior with MS (in case you have it installed)? 2. The kernel, as compiled by SuSE, lacks some crucial module of which I'm not aware. If the first case is true, I guess I can shorten the cables by replacing my dysfunctional internal SCSI cd/rom with some new device (probably cd/rw, while I'm at it), so I only have one external device and about 1.5 meter less of cable. Of course, this is a bit of an expense with some added problems, such as - is a Yamaha CRW2100SNB supported by kernel 2.4.x). If the second case is true, I need to know what module I'm missing. The external CD/R is an old TEAC (I can find out the exact model once I'm back home). You might try to compare the .config of the 2.2 and the 2.4 kernels. Any help appreciated. Herouth Perhaps the scsitools package can help? The CD-ROM HOWTO? Posting the relevant boot messages? = To unsubscribe, send mail to [EMAIL PROTECTED] with the word unsubscribe in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
