From owner-freebsd-current@FreeBSD.ORG Fri Feb 24 17:30:52 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 1BD4B1065676; Fri, 24 Feb 2012 17:30:52 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: matt Date: Fri, 24 Feb 2012 12:30:40 -0500 User-Agent: KMail/1.6.2 References: <4F470DFF.3070906@gmail.com> In-Reply-To: <4F470DFF.3070906@gmail.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201202241230.43762.jkim@FreeBSD.org> Cc: freebsd-current@freebsd.org Subject: Re: Syscons issue Intel D2700 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Feb 2012 17:30:52 -0000 On Thursday 23 February 2012 11:11 pm, matt wrote: > I'm currently trying to boot an intel evaluation board (D2700) with > 10-CURRENT. > Installation was > make installworld DESTDIR=/mnt/disk > make installkernel DESTDIR=/mnt/disk > make distribution DESTDIR=/mnt/disk > vi /mnt/disk/fstab (added lines for root, swap) > unmount /mnt/disk > > Boot goes fine until the kernel is loaded. > Once the kernel is loaded, boot continues, however only the very > bottom line is showing kernel messages...the rest of the screen > still "looks" like loader. > > Once booted, a number of silly attempts with vidcontrol 80x25, > vidcontrol -C, vidcontrol VESA_800x600 do not fix the situation. > > Interestingly, typing clear moves the prompt up, but the screen > still looks like loader. > I can see my text, but command output is not written to the > console. > > This is weird. I am actually not that interested in much about the > graphics on this board...it's gma500 all over again. > Getting basic syscons working would be nice, however...I don't want > to have to use a null modem cable during development. > > If it helps I'll fire up sshd and make a bunch of diagnostic files, > although I can't see ifconfig output I assume em drivers are fine. > It is a nice board otherwise, with two intel nics...am interested > in developing a freebsd-based product if possible :) > > If this is something I hosed with the above minimal installation I > apologize in advance! It sounds like a timer issue. Try "set kern.eventtimer.periodic=1". It's a long shot, though. Jung-uk Kim