Hello World, [SuSE] -=( this was posted before but is not resolved, please help out)- I recently bought an 'Ultra Wide Adaptec 2940'. Useing aic7xxx4.1.1 that came with SuSE 5.1, (normal lilo bootup) it fails with: scsi devices : 1 device scsi: Scanning channel A for devices scsi:aborting command due to time out: pid 0 scsi 0 channel 0 id 0 lun 0x00 00 00 00 00 00 scsi host 0 abort(pid0) timedout-resetting scsi bus is being reset for host 0 channel 0 "" "" a few more times with like .......trying harder.... scsi host probably an unrecoverable SCSI bus or device hang. Now whats up with that? When: 1)a SuSE Distro boot disk (its the only way I can use my scsi devices) a) will load kernel module aic7xxx and dectect everything just fine. 2)a normal lilo boot of my kernel, will lock up or loop the aic7xxx driver when it is kernel uncompressing. 3) I now have removed aic7xxx from direct kernel support and am attempting to load it as just a module (when I need it) but here agian it is not working, as like the SuSE distro boot disk will. ***Someone said to use the lx-linux? Eh that was the kernel I was useing and that does not work either. Now I have just a basic out-of-the-box 2.0.33 kernel with aic7xxx updated patches applyed What would be the (sigh) difference of the SuSE distros boot disk aic7xxx kernel support than the kernel that SuSE loaded up for me?? When I picked aic7xxx to be installed........ Now I have been for the past few days talking with Doug Ledford (dledford@dialnet.net) He suggested a few things, including getting patches to the aic7xxx module for 2.0.33kernel. at ftp.dialnet.net -the current version of aic7xxx is 5.0.5 and SuSE5.1 came with 4.1.1/3.2.1 These patches DO NOT apply cleanly to 2.0.33(pre33SuSE.3) (or something) but do apply cleanly to 2.0.33 out-of-the-box kernel. put the 5.0.0 patch on then the 5.0.0 to 5.0.1 and so on or just 5.0.5patch.gz Well all of this didn't work either. I need to know if there is more info that what I have to correct this. things are that everything 1) works fine and detects when booting from SuSE distros boot disk (I hope Idont loose this)!! 2)windows(ick)95 detects everything and works 3) so I don't think it is a termination problem 4) and I dunno Steven Udelhoffen hettar@teleport.com -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e