IMM is the zip-plus driver which is supported in the newer one, but, I doubt that is at all related to the problem, that just happens coincidentally to be a message present in the new boot.
-Tom On Wed, 13 Aug 2003, John Lumby wrote: > Date: Wed, 13 Aug 2003 22:33:24 -0400 > From: John Lumby <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Re: [tomsrtbt] hang during boot on 2.0.103 (not tomsrtbt's > faultbut anyway ...) > > In my previous append I said: > > > Can you confirm (or tell me how to confirm) that the kernel in 2.0.103 > > auto-detects devices in the same order as the one in 1.7.361? > > Which would then imply that the problem is definitely with the scsi > detection. > > Today my brain surprised me by suggesting to watch the boot messages > from the successful boot of 2.0.103 on the other computer (the workstation). > It's hard to catch them (are tomsrtbt boot msgs logged anythere? I > couldn't see anywhere) but after the > FDC 0 is a National Semi... > line, I saw something about > > ppa 2.07 linux > no ppa > Iomega something someting about a parallel port for ZIP > then > IMM V1.03 > and then resumed with the scsi stuff that is common with 1.7.361 > > Any idea what either ppa and/or Iomega and/or IMM are? I guess if I > could make a kernel with none of those, it might boot ok on the thinkpad. > > JOhn >
