Date: Thu, 04 Oct 2012 22:24:01 +0200 From: Marek Salwerowicz <marek_sal@wp.pl> To: lev@FreeBSD.org Cc: freebsd-current@FreeBSD.org Subject: Re: [SPAM]Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection Message-ID: <506DF061.4080403@wp.pl> In-Reply-To: <13310645740.20121004225119@serebryakov.spb.ru> References: <80840563.20120920002200@serebryakov.spb.ru> <506C8F4F.3040703@wp.pl> <13310645740.20121004225119@serebryakov.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
W dniu 2012-10-04 20:51, Lev Serebryakov pisze: > Hello, Marek. > You wrote 3 октября 2012 г., 23:17:35: > >>> atrtc0: <AT realtime clock> port 0x70-0x71 on acpi0 > MS> still the same in my environment, running FreeBSD 9.1 under ESXi5.1 host > MS> Do you have any solution? > In my case it was local patch for exotic embedded chipset... Can you send me the patch so I can have a look if I don't use the same chipset ? Regards, -- Marek Salwerowicz
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?506DF061.4080403>