> 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]

Reply via email to