Perhaps I should try on another machine, but I tried booting Default Meego Atom
Netbook image on my Nokia Booklet 3G and that booted to shell, the one I
created (USB image) did not boot on the same device. It complained that there
is no bootable image found. I also built a CD image with the
Even better. I wrote to the USB disk using the Windows utility. I could not
make the linux mic-image-writer utility work since my USB drive was not
/dev/sdb and I could not configure the utility to use any other device (any
pointers here?)
-Adhyas
From: ext Wan, Shuang
I think I complained about it yesterday as well. Editing the .ks file to
comment out the Core package made it work for me but I still wonder if we
necessarily have to do that.
Thanks,
Adhyas
From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On
Behalf Of ext Bill Varney
I still think this is a bug. I did some more experiment to verify my statement.
I used the same USB stick and wrote the standard Atom netbook image from
meego.com (using Windows) and that worked fine. I wrote the USB image I have
created myself on my Ubuntu box (vanilla image, no packages added
Hello
Can someone answer when we can expect to see Meego with a UI support? Is there
a plan to it, and if so, can you please tell me the timeline?
Thanks,
Adhyas
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
Alright, seems like it was trying to use the full graphics boot by default and
not working (possibly because it did not like my VMware Virtual Graphics
Controller.
Did we already introduce UI to meego, so we have a desktop?
I stepped into the boot menu and then removed all quiet options from
Overall, your image is good. I tried to install using that CD and that worked
fine as well.
But there are still some issues.
I tried building my own image with the .ks file you have provided but
mic-image-creator threw an error:
Retrieving
I installed the IVI image on a Virtual Box VM (8GB hard disk). I added more
packages to bring it to my satisfaction. Now I wish to create a live usb image
out of it.
So I converted the vdi image to raw image using VBoxManager internalcommands
converttoraw and that worked fine.
When I use the
I tried the same. Now it complains about the package
libopensync-plugin-evolution2 and does not find it anywhere.
Are you sure this .ks file is sufficient to build the image? Maybe you have
some more packages in a local repo, or your cache and you are including them in
your image. Because I
Thanks for the pointer. I tried searching online but could not find the 0.18
version. Maybe it is for internal use only. It would be nice if the updated
version can be shared. I also tried looking into the various mic-image-creator
options and could not find anything that helps in overlooking
Is there a code review policy for bugs filed on core meego components (like
meego tools, kernel-sources etc.) ? Can someone please point me to some
information on it, and if I need to subscribe to specific mailing lists to be a
part of those reviews, and track development on a particular
I tried syncing my image-creator tree, built it and tried using the utility but
it crashed with the following error:
[r...@aavasthi-fedora12vm image-creator]# ./build/scripts-2.6/mic-image-creator
-v
Traceback (most recent call last):
File ./build/scripts-2.6/mic-image-creator, line 31, in
The installation works fine. I should say, pretty fast as well. Touch screen
works out of the box (Could not make the pointer's right click work on Meego
though).
Then I pointed meego-updates.repo file to builds/trunk/daily/core packages and
ran yum update (installed all the packages).
On
I installed from my original USB image again (after your email). And changed
the inittab to read /usr/sbin/meego-dm instead of moblin-dm
But there is no /usr/sbin/meego-dm on this installation (there is a
/usr/sbin/moblin-dm though)
I have used the provided IVI 1.0 .ks file to build the final
How can I subscribe myself to receive bugs in various components and
categories? (Maybe this is obvious and I could not locate it at bugs.meego.com)
When I create a bug, I can see that default cc is to base-os.bugs.meego or
something like that. Where are these lists maintained? How can I join
My /usr/src/kernels is empty. The symlink is pointing to the right place but
there is nothing there anyway.
Why is that so? What package do I need to install?
Thanks,
Adhyas
-Original Message-
From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On
Behalf Of ext Mark
I installed kernel-netbook-devel and it seemed to give me the headers now.
Kvm-kmod also compiles now.
Thanks for the pointers.
-Adhyas
-Original Message-
From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On
Behalf Of Avasthi Adhyas (Nokia-NRC/PaloAlto)
Sent:
I want to know a bit more about the 3D support present in Meego (or planned to
be present). What features of 3D is supported/present and what is not? Like,
I've heard that compressed textures are mostly closed source and there is no
open source driver (yet) that provides it. Can someone please
The wiki at http://wiki.meego.com/Kernel_Process that it is obsolete now. What
is the location of the new wiki that talks about the kernel process, if any?
Thanks,
Adhyas
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
I know people are already working on the modified Kernel Process. I am not
writing to remind about that.
Perhaps this is a very naive question, but it would be nice if someone can help
me out with this query.
Thanks for providing the workaround for kernel compilation in the bug update. I
can
This morning I synced my kernel sources tree and compiled a fresh 2.6.34 kernel
without changing the configurations. The resulting bzImage panics with 100%
frequency. It says Cannot open root device sda2 or unknown-block(0,0). Please
append a correct root= boot option;
My extlinux.conf file
I used the config provided by git tree (from kernel sources of meego).
Shouldn't that suffice? I double checked that my config file had BTRFS enabled.
What I don't understand is why the default image can boot to the same partition
but the newly compiled kernel cannot.
I am applying patches and
http://daringfireball.net/2007/07/on_top
Alright. This is just a pain in Outlook (or I don't know how to use it in
Outlook). Let's hope the manual insertion of '' works.
No, think driver that talks to the disk not the filesystem.
Yes, I got that. I was trying to identify the controller. It
MeeGo does not support NFS currently.
We recommend using sshfs instead more reliable and more secure.
Is this a decision or the feature is NOT YET implemented? I don't agree with it
if it is a decision. I have an NFS server at home (and I am sure many others
would have one as well), and I
does your nfs server run ssh? that's all you need.
It did not have direct ssh access when I bought it. I had to add it myself.
But my point was more generic. There would be users out there who want NFS
mounting.
- Adhyas
___
MeeGo-dev mailing list
25 matches
Mail list logo
