maemo.org - Talk - [WIP] Ubuntu 9.10 on the N900

maemo.org - Talk (https://talk.maemo.org/index.php)

- Ubuntu (https://talk.maemo.org/forumdisplay.php?f=55)

- - [WIP] Ubuntu 9.10 on the N900 (https://talk.maemo.org/showthread.php?t=58083)

Re: [WIP] Ubuntu 9.10 on the N900

Quote:

Originally Posted by lunat (Post 867538)

Code:

 

mkdir -p /mnt/meego

losetup /dev/loop0 ${MEEGO_IMAGE} -o  <OFFSET>

 mount /dev/loop0 /mnt/meego

OR on the pc:

Code:

mkdir -p /mnt/meego

mount -o loop,offset= <OFFSET> ${MEEGO_IMAGE} /mnt/meego

OR your way of mounting images on windows..

you get the offset via sfdisk -lu
the startnumber it tells you needs to be multiplied with the blocksize and this is the offset.

Code:

 losetup /dev/loop0  ${MEEGO_IMAGE}

 sfdisk -lu /dev/loop0

look up the start of the partition. it's the 1rst number in the line with part.type "linux" or 83 Hex and multiply it with the blocksize, should be 512(it tells you in the head!)

Code:

losetup -d /dev/loop0

wait: don't use that ooold image in the chroot howto but a new one! see for instance:
http://wiki.meego.com/ARM/N900/Install/MMC#Linux
now mount that with the offset of the real image you have( the image i tried had an offset of 512 ).

I cannot mount the meego image.

Code:

sfdisk -lu /dev/loop0

returns

Code:

unrecognized format - using sectors

I have re-downloaded the image to check that it is not corrupt and got the same error. How do I fix this?

Re: [WIP] Ubuntu 9.10 on the N900

Quote:

Originally Posted by skykooler (Post 873660)

I cannot mount the meego image.

Code:

sfdisk -lu /dev/loop0

returns

Code:

unrecognized format - using sectors

I have re-downloaded the image to check that it is not corrupt and got the same error. How do I fix this?

yep - at least this is what sfdisk says..i don't know if you need a different image, or download the same image again or the losetup didn't work out. and maybe try -luB if you dont ge't units in blocks with the -lu - but that shouldn't be the issue in your case(it doesn't show you anything and not something using with wrong unit).

Re: [WIP] Ubuntu 9.10 on the N900

Quote:

Originally Posted by lunat (Post 872644)

----
#
# Processor Features
#
CONFIG_ARM_THUMB=y
CONFIG_ARM_THUMBEE=y
----
edit do you have a link to what goes wrong with v7, please?
edit2: this is from a(running) 36 kernel ubuntu has a 35 atm.

Ive heard qole say is 100 times at least.

So if we compile with

CONFIG_ARM_THUMB=n
CONFIG_ARM_THUMBEE=n

Thumb would be disabled?

Re: [WIP] Ubuntu 9.10 on the N900

Quote:

Originally Posted by ear0wax (Post 873740)

Ive heard qole say is 100 times at least.

So if we compile with

CONFIG_ARM_THUMB=n
CONFIG_ARM_THUMBEE=n

Thumb would be disabled?

yes: if you dissable thumb you cant execute thumbcode anymore(but imo you will want to).

and i don't doubt what you say. it's just that i want to know the issue. for it seems i am quite successfully working around an issue i am not aware of.

Re: [WIP] Ubuntu 9.10 on the N900

im confused read the tutorial before (Install Ubuntu 10.10 from lunat),im beginner on linux.
can create some simple Tutorial, im on PR.1.3 and still using multiboot (multiboot.d/NITDroid.item)

thanks

Re: [WIP] Ubuntu 9.10 on the N900

Quote:

Originally Posted by artron (Post 875223)

it is not simple.
and using the meego kernelis wrong. thats just proof of concept.
... heard nitroid kernel works better... for a better poc
still: roll your own kernel put it on ubuntu and it works fairly.

Re: [WIP] Ubuntu 9.10 on the N900

i want to make something clear. all that thing with patching ubuntu with the meego kernel was to show you can start it.

what it clearly is not, never was, and never was intentend to be: a way of getting a ubuntu you can use in any way. it is not. it does not work!
it is a way to get a start to how to tackle it.

i do not try to get it working with the meego or the maemo kernel or such approaches. what i do is patch up brandnew kernels to the brim with the newest patches i can find. and see if i can apply them. partly manually apply patches. change the kernel again and again and see if it works better. and get better results with every try but it is still not good. and if you go down and look a the a copied part of my modules you will find every module with a little description what it does. and thats only part of it. so you can look at it and see if you have the driver or not and might find a hint who the troublemaker could be - or give me a hint to better use some other drivers/patches.

additionally i take packages and compile them myself take other things from various gits and compile them define new depencdies to make it work and so it goes.

thats nothing you could simple copy and paste and just use.
thats nothing to put on a emmc for it may crash and simple destroy it for good. it may even render your device unusable.

but it can go very fast that we get it working. many things work. actually most. still that doesn't help much for the things that don't work spoil everything. and with ubuntu the spoilers hit one even more for it does many things automaticly which is nice for a enduser but very odd if you have a unstable thing and want to separate the troublemakers and find problems(eg network manager: )

no, a distribution it not just downloading software and installing it. its a lot, lot of work to make them work together.

again i wrote the steps together for the folks who repeatedly begged for instructions how to tackle it and for the ever repeating same questions. especially keyboard which never was an issue. and to get away from the non issue to see a loginscreen to the real issues. and i used the meego kernel only for it is a precompiled kernel good enough for the poc(no need to describe every step necessary to compile a kernel) but it is by no means realy working with it.
also: it makes no sense at all to take a precompiled kerneldriver for a kernel it wasn't built for: might work in some cases. generaly it doesn't. makes no sense to put such a thing online - the source of the patch does make sense and whoever want that will find it(have it for the kernel you use. it may have changed since it was submitted the first time).

i hope that was clear enough to how i think about this.
i really like the comunity thing and realy like to have things in the open. that is all what imo hacking is about: to see whats happening behind the scenes. and i don't keep my stuff to myself and share if it is possible, but until it is not made working: it doesn't work.

Re: [WIP] Ubuntu 9.10 on the N900

help me to compress and upload the firmware and modules from PR 1.2, im already on PR 1.3. i want to try Maemo on PR 1.3 and on Ubuntu 9.10 using PR.1.2...

Please...

Thanks

Re: [WIP] Ubuntu 9.10 on the N900

I'm still having trouble with bluetooth on 10.10 and 2.6.28.10-power45.

I copied everything in /lib/firmware and /lib/modules,
but the system->settings->bluetooth says I have no bluetooth hardware.
I tried:

Quote:

echo "<My bt address>" > /sys/devices/platform/hci_h4p/bdaddr
modprobe -r hci_h4p

but still nothing

Any hints?

Re: [WIP] Ubuntu 9.10 on the N900

Also, everything seems to segfault rather frequently. I can't open gnome-terminal, and it takes a few tries to get wicd to connect without X crashing.

most everything else seems to work ok.