From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IvDJw-0002r3-Kp for qemu-devel@nongnu.org; Thu, 22 Nov 2007 09:46:24 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IvDJs-0002kN-DU for qemu-devel@nongnu.org; Thu, 22 Nov 2007 09:46:21 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IvDJr-0002ju-QP for qemu-devel@nongnu.org; Thu, 22 Nov 2007 09:46:19 -0500 Received: from rv-out-0910.google.com ([209.85.198.184]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IvDJr-0000uL-8s for qemu-devel@nongnu.org; Thu, 22 Nov 2007 09:46:19 -0500 Received: by rv-out-0910.google.com with SMTP id g11so9118549rvb for ; Thu, 22 Nov 2007 06:46:18 -0800 (PST) Message-ID: Date: Thu, 22 Nov 2007 15:46:18 +0100 From: "andrzej zaborowski" Subject: Re: [Qemu-devel] Problem with qemu on Ubuntu Gutsy ... In-Reply-To: <538531.13581.qm@web50907.mail.re2.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <538531.13581.qm@web50907.mail.re2.yahoo.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dara burke , qemu-devel@nongnu.org On 21/11/2007, dara burke wrote: > Hi Guys, > > I've been looking around for a solution to this problem that I've been > having with qemu on ubuntu Gutsy. It seemed to work fine on Feisty, but I > haven't been able to find anyone else with a similar complaint in the ubuntu > forums or on google or on irc, so maybe a simple upgrade problem isn't the > issue. I hope it's OK to post to the dev mailing list ? It is quite clearly an SDL issue, rather than qemu. > > The system seems to have a problem locating the framebuffer, also SDL > doesn't get initialized. > > babo@eire:/home/babo/qemu_dir# qemu -localtime -cdrom /dev/cdrom -m 384 > -boot d c.img > Warning: No DNS servers found > > ---------------------- DirectFB v0.9.25 --------------------- > (c) 2000-2002 convergence integrated media GmbH > (c) 2002-2004 convergence GmbH > > ----------------------------------------------------------- > > (*) DirectFB/Core: Single Application Core. (2007-08-07 19:21) > (*) Direct/Memcpy: Using linux kernel memcpy() > (!) Direct/Util: opening '/dev/fb0' and '/dev/fb/0' failed > --> No such file or directory > (!) DirectFB/FBDev: Error opening framebuffer device! > (!) DirectFB/FBDev: Use 'fbdev' option or set FRAMEBUFFER environment > variable. > (!) DirectFB/Core: Could not initialize 'system' core! > --> Initialization error! > Could not initialize SDL - exiting > > I'd try to start the system from X, but there doesn't seem to be any method > of doing that. Obviously there is a framebuffer somewhere, but the command > line qemu can't seem to find it. Your SDL may be built with no X support, if you're sure it supports X then try forcing it with SDL_VIDEODRIVER. The message above actually indicates there's no framebuffer. Regards