From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IuvQY-0004kh-1H for qemu-devel@nongnu.org; Wed, 21 Nov 2007 14:40:02 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IuvQW-0004k9-Pa for qemu-devel@nongnu.org; Wed, 21 Nov 2007 14:40:01 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IuvQW-0004k6-KW for qemu-devel@nongnu.org; Wed, 21 Nov 2007 14:40:00 -0500 Received: from web50907.mail.re2.yahoo.com ([206.190.38.127]) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1IuvQW-0006Te-3H for qemu-devel@nongnu.org; Wed, 21 Nov 2007 14:40:00 -0500 Date: Wed, 21 Nov 2007 11:39:59 -0800 (PST) From: dara burke MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1918836835-1195673999=:13581" Message-ID: <538531.13581.qm@web50907.mail.re2.yahoo.com> Subject: [Qemu-devel] Problem with qemu on Ubuntu Gutsy ... Reply-To: dara burke , qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org --0-1918836835-1195673999=:13581 Content-Type: text/plain; charset=us-ascii 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 ? 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. Any help is greatfully accepted, Thanks, Dara ____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs --0-1918836835-1195673999=:13581 Content-Type: text/html; charset=us-ascii
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 ?

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.

Any help is greatfully accepted,

Thanks,

Dara

Never miss a thing. Make Yahoo your homepage. --0-1918836835-1195673999=:13581-- 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IvbX9-00051F-C8 for qemu-devel@nongnu.org; Fri, 23 Nov 2007 11:37:39 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IvbX7-0004yT-Aw for qemu-devel@nongnu.org; Fri, 23 Nov 2007 11:37:38 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IvbX7-0004yF-0h for qemu-devel@nongnu.org; Fri, 23 Nov 2007 11:37:37 -0500 Received: from rv-out-0910.google.com ([209.85.198.187]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IvbX6-0003ti-E3 for qemu-devel@nongnu.org; Fri, 23 Nov 2007 11:37:36 -0500 Received: by rv-out-0910.google.com with SMTP id g11so9934774rvb for ; Fri, 23 Nov 2007 08:37:34 -0800 (PST) Message-ID: <474701D1.2010704@codemonkey.ws> Date: Fri, 23 Nov 2007 10:37:37 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Problem with qemu on Ubuntu Gutsy ... References: <538531.13581.qm@web50907.mail.re2.yahoo.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: dara burke andrzej zaborowski wrote: > 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. > DISPLAY isn't set. This often happens when you 'sudo su -'. If you instead 'sudo su' or just 'sudo qemu ...' then DISPLAY will remain set and things will work as expected. Regards, Anthony Liguori > Regards > > > >