From mboxrd@z Thu Jan 1 00:00:00 1970 From: tarawa1943@comcast.net Subject: (no subject) Date: Mon, 18 Apr 2005 16:43:52 +0000 Message-ID: <041820051643.925.4263E3C800001C610000039D2200762302CCCBC7CE0E990E9D0E9B@comcast.net> Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: m+Ian.Pratt@cl.cam.ac.uk Cc: xen-devel@lists.xensource.com, christopher.w.clark@gmail.com List-Id: xen-devel@lists.xenproject.org Ian Thank you sir, I will check that. I did do another build with 12apr05 xen-unstable and it did not have the same symptom/problem, xen-unstable changed around 16-17apr05, to expose this symptom on a thinkpad. Will look deeper. woody ======================================== Date: Mon, 18 Apr 2005 10:26:16 +0100 From: "Ian Pratt" Subject: RE: [Xen-devel] "Floppy drive(s): fd0 is 1.44M" To: , Cc: christopher.w.clark@gmail.com Message-ID: Content-Type: text/plain; charset="us-ascii" > Subject: [Xen-devel] "Floppy drive(s): fd0 is 1.44M" > > Thanks for your response, and how would you suggest that one > would fix that? > It hangs in the boot process! Have you tried messing with the 'floppy=' parameter on the kernel command line? See Documentation/floppy.txt Alternatively, just config the driver out of your kernel, to confirm that this is what is causing the hang. We use the floppy driver in PIO rather than DMA mode, and this is must be causing the probe code to get confused under some circumstances. (thinkpad floppy drives are somewhat notorious, and there's lots of work arounds in the probe code) Ian