When did you build the image? The Ui is broken for several weeks I was told. Edit your kickstart file, so it links no longer to the daily build but an older build like 0706. > I created the image myself from the kistart file from the daily build meego-handset-armv7l-n900-1.0.80.11.20100720, and used the corresponding vmlinuz file, and flashed the phone, and it booted (not using QEMU), but got a bash command line only. No UX. I tried to type startx but nothing happened. > > I thought that it would have more functionalities than the Day 1 1.0 UX. > > So does anyone know if it is possible to get a UI with any build newer than the day 1 codedrop? > > Rami > > From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of Tobias Renz > Sent: Thursday, August 05, 2010 10:45 AM > To: Development for the MeeGo Project (discussion list) > Subject: Re: [MeeGo-dev] Dose anyone run Meego of N900 image in QEMU successfully? > > > There is no ready made image including Handset Ux ( version 1.08). You are using Version 1.0 the first release without Ux. You have to build the image from the kickstart file for 1.08. But be cautious it uses the daily builds. These are broken for several weeks. Regards Tobias >> Hello, >> >> Meego can boot in qemu now, but there is only a bash shell. From the console it ends with >> ----------------------------------------------------------------- >> Welcome to Moblin >> [ OK ] >> >> MeeGo release 1.0 (MeeGo) >> Kernel 2.6.28-2.1-n900 on an armv7l >> >> localhost.localdomain login: udevd-work[71]: error opening ATTR{/sys/class/sound/controlC0/../uevent} for writing: No such file or directory >> >> Unknown HZ value! (93) Assume 100. >> ----------------------------------------------------------------- >> >> The command line is "qemu-system-arm -M n900 -mtdblock meego_qemu_nand.img -sd empty -sd meego-codedrop-arm-n900-closed-201003311635.ubiimg -serial stdio". >> >> Adding/removing those -sd options make no difference. Any suggestions? >> >> ---------------- >> Best Regards, >> Brook Hong >> >>>-----Original Message----- >>>From: meego-dev-boun...@meego.com<mailto:meego-dev-boun...@meego.com> [mailto:meego-dev-boun...@meego.com<mailto:meego-dev-boun...@meego.com>] >>>On Behalf Of Riihimaki Juha (Nokia-MS/Helsinki) >>>Sent: Wednesday, August 04, 2010 1:12 PM >>>To: meego-dev@meego.com<mailto:meego-dev@meego.com> >>>Subject: Re: [MeeGo-dev] Dose anyone run Meego of N900 image in QEMU >>>successfully? >>> >>> >>>On Aug 4, 2010, at 04:55, ext Sylvia Liu wrote: >>> >>>> I wonder if another method will also work: >>>> - with qflasher, replace both kernel and ubi-fs on the >>>> meego_qemu_nand.img, and start the img as mtdblock. >>>> I used to try it, but failed. I want to know is the idea a right >>>> direction? Is that possible to start the img that way? >>> >>>In principle it is possible, we used that approach with the first code >>>drop qemu image where everything was installed on the nand image. Using >>>this method of course requires that the rootfs image is small enough to >>>fit in the nand and the kernel you are using is capable of locating and >>>mounting the ubifs volume. >>> >>> >>>Regards, >>>Juha >>>_______________________________________________ >>>MeeGo-dev mailing list >>>MeeGo-dev@meego.com<mailto:MeeGo-dev@meego.com> >>>http://lists.meego.com/listinfo/meego-dev >> _______________________________________________ >> MeeGo-dev mailing list >> MeeGo-dev@meego.com<mailto:MeeGo-dev@meego.com> >> http://lists.meego.com/listinfo/meego-dev > --------------------------------------------------------------------- > Intel GmbH > Dornacher Strasse 1 > 85622 Feldkirchen/Muenchen Germany > Sitz der Gesellschaft: Feldkirchen bei Muenchen > Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer > Registergericht: Muenchen HRB 47456 Ust.-IdNr. > VAT Registration No.: DE129385895 > Citibank Frankfurt (BLZ 502 109 00) 600119052 > > This e-mail and any attachments may contain confidential material for > the sole use of the intended recipient(s). Any review or distribution > by others is strictly prohibited. If you are not the intended > recipient, please contact the sender and delete all copies.
_______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
