FreeBSD hangs while booting with USB legacy support off

2011-01-15 Thread Norihiko Murase
Hi, My name is Norihiko Murase. I would like you to give me the comments/suggestions about the symptom described below. When I started the FreeBSD installation system via DVD (FreeBSD-***-RELEASE-i386-dvd1.iso), the system hangs while the devices are being probed. The last lines displayed was

Re: FreeBSD hangs while booting with USB legacy support off

2011-01-16 Thread Norihiko Murase
wired to IRQ 19 atapci0: port ..(snip!).. irq 19 at device 0.0 on pci4 -------- Best regards, --- Norihiko Murase ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listi

Re: FreeBSD hangs while booting with USB legacy support off

2011-01-21 Thread Norihiko Murase
l/xhci.ko boot -v # The screenshot of the FreeBSD Boot Loader Menu is # available at 2.4.1.1 of the FreeBSD handbook # (as you already know) # http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install-start.html Best regards, --- Norihiko Murase __

Re: FreeBSD hangs while booting with USB legacy support off

2011-01-29 Thread Norihiko Murase
Can I ask you the way of booting the *installation* system with xhci.ko loaded? I couldn't succeed even with the 9-CURRENT-201101 snapshot... |Date: 22 Jan 2011 14:42:44 +0900(JST) |From: Norihiko Murase |To: freebsd-usb@freebsd.org |Subject: Re: FreeBSD hangs while booting with USB l

Re: FreeBSD hangs while booting with USB legacy support off

2011-01-30 Thread Norihiko Murase
Mr. Hans Petter Selasky, Thank you very much for your quick reply. On Sunday 30 Jan 2011 10:33:26 +0100 Hans Petter Selasky wrote: > On Sunday 30 January 2011 03:39:16 Norihiko Murase wrote: > > Can I ask you the way of booting the *installation* system > > with xhci.ko loa

RESOLVED: FreeBSD hangs while booting with USB legacy support off

2011-03-27 Thread Norihiko Murase
reebsd-usb@freebsd.org From: Norihiko Murase Subject: FreeBSD hangs while booting with USB legacy support off (The full text of it is available also at the bottom of this message.) Fortunately this problem is now RESOLVED. Briefly, the root cause of it is * the wrong connection method b