Reply
Thread Tools
Posts: 256 | Thanked: 92 times | Joined on Oct 2010
#311
Originally Posted by artron View Post
its ubuntu 10.10 run on PR 1.3 ?
no! pr1.3 is closed maemo stuff and ubuntu != maemo.
you can however with a /capable kernel/ copy the whole pr1.3 stuff and everything else from maemo to the ubuntu and boot that. that works .but that actually is replacing ubuntu with maemo so that it is no longer ubuntu but maemo with some parts from ubuntu. further you cannot make it available for the public as it is cruftware.

and as a sidenode: while running different binaryformats is possible it is not totally stable so might break sometimes.

EDIT: in more understandable: it is illegal for ubuntu to use pr 1.3 so you can't use it. nokia forbids it. plain and simplified.

Last edited by lunat; 2010-11-07 at 09:03.
 
Posts: 255 | Thanked: 61 times | Joined on Feb 2010
#312
I really dont think ofono is gonna be to a big problem, its in the ubuntu mobile ppa
__________________
Desktop: 2.8ghz Athlon x2 Kuma 4gb DDR2 OCZ Platinum XFX Geforce 260GTX BE
 
Posts: 256 | Thanked: 92 times | Joined on Oct 2010
#313
Originally Posted by ear0wax View Post
I really dont think ofono is gonna be to a big problem, its in the ubuntu mobile ppa
hope so. up to now i get it detecting n900. listmodems tells me it is there. but i cannot enable it.... also tried it with the lates git ofono stuff. if i know more i let you know!

and there is the other isi stack but see for yourself:
https://elektranox.org/n900/libisi/index.html


edit: if somone gets ofono running, the next problem is pulseaudio and telepathy and see what is usable and what is cruft...

another edit: i still charge the phone with a modified version of joergs script is there a better way?

Last edited by lunat; 2010-11-07 at 09:57.
 
Posts: 256 | Thanked: 92 times | Joined on Oct 2010
#314
Originally Posted by ear0wax View Post
I really dont think ofono is gonna be to a big problem, its in the ubuntu mobile ppa
drivers needed to make a call, correct me if i missed something:
----
#modem
phonet
cdc-phonet
cmt
cmt-speech
---
+ a hack from meego pulling up the lines. think it is all free stuff.
*smiles*
 
Posts: 327 | Thanked: 383 times | Joined on Aug 2010 @ alex , egypt
#315
oh my god
finally got it working
and it's so so so fast on my 8 giga class 6 memory card
thanks to nicola
 
Posts: 111 | Thanked: 33 times | Joined on Sep 2010
#316
I need an tutorial...Oh God...
 
Posts: 11 | Thanked: 4 times | Joined on Oct 2010 @ Poland
#317
Yes, please sb make tutorial for 10.10 because it's really hard to find out step by step procedure of getting it to work just by skimming previous posts ( keyboard + touchscreen + etc. ).

mido.fayad : try installing on eMMc. I have just installed nitdroid on extra primary partiton on eMMc, and it's running faster than installed on class 10 sdhc.
 
Posts: 327 | Thanked: 383 times | Joined on Aug 2010 @ alex , egypt
#318
i already run nitdroid on emmc and i know it's better and i will try to run it also
 
Posts: 256 | Thanked: 92 times | Joined on Oct 2010
#319
Originally Posted by LucianoBraga View Post
I need an tutorial...Oh God...
sure.. once i am done.
this is work in progress. all at your own risk. you may, but it's unlikely, destroy your phone if you do something wrong. and you may void your warranty if you do sth wrong. so all at your own risk and responsibility. also no warranty that everything works by copy and pasting. i wrote it solely in the hope to help if you are stuck. don't blame me: you've been warned.

one more hint: take care if you are editing on your pc. pathnames in the following are relativ to the mountpoint or the volume in win machines. you have to prepend YOUR path to the mountpoint. don't edit the files on your pc but only those on the sd!
another hint: if you are using a windows pc for this you need (obviously)something capable of reading ext2(actually it is an ext3 but ext3 /is/ ext2 with some additional files, so ext2 is sufficient)

take the ubuntu image(armel+omap.img.gz).
http://cdimage.ubuntu.com/ubuntu-net...10.10/release/
put it on a sd just the way they explain it on the ubuntu page.
https://wiki.ubuntu.com/ARM/OMAPMaverickInstall

HOLDON: unmount everything if it is mounted and try a fsck on the second partition.
eg.
Code:
fsck /dev/mmcblk1p2
either it is imidately done and says everything is fine.

important or it gives you crap of a destroyed superblock or partitiontable or something alike: that means your sd and the image don't fit together(no problem of n900 but a problem of rawimages and sds of differrent sizes etc). unfortunately that will stop the bootprocess later as well as the kernel runs fsck on the disk.
in that case: accept the offer of fsck and abort the check! mount the partition 2 , make a backup of it, partition and format the sd anew and play the backup back.[backup e.g. with rsync -Hax source target ] (anyways good for you can increase the size of the partition)


how you acces the sd doesn't matter. have the 2nd partition mounted,
eg. if you are on the phone:

Code:
mkdir -p /mnt/ubu
mount /dev/mmcblk1p2 /mnt/ubu
OR if you put in the sd in on a pc and have it in a filemanager/explorer you are good as well.

take a kernel from meego and an image. you have to mount the image somehow and grab the modules from there. do it the way they explain it on their page(but don't use the old image there, see below) :
http://wiki.meego.com/ARM/N900/Install/chroot
the important part is:


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 ).

put the modules from the meego /lib/modules/ to /lib/modules/ on the sd.(the whole directory so that you get a new subdirectory with the kernels version as its name - just drag and drop and you are good). we only grab the kerneldrivers off the image.
eg.
Code:
cp -a /mnt/meego/lib/modules/* /mnt/ubu/lib/modules/
OR your way of copying files in windows
btw firmware is also in /lib/firmware

after that you can unmount the image. don't need it any further.
e.g.
Code:
umount /mnt/meego
rm /mnt/meego
you can save you the trouble with the meego image if you compile your kernel yourself :P
now back to our ubuntu sd:
go to /etc modules(any /simple/ editor that can handle unix lineendings):
add /at least/ the following modules to it(copy and paste). might need to add some others. and uncomment some.[is on my TODO] )
Code:
#----
#modem
phonet
cdc-phonet
cmt
cmt-speech
#keyboard
gpio_keys
twl4030_keypad
matrix_keypad
#touchscreen
tsc2005
#light_meter
tsl2563
#acelerometer
lis3lv02d_i2c
lis3lv02d

#screen
#ACX565AKM (compiled in needs spi master)
#audio compiled in
#TLV320AIC3 compiled in audio, bug: can't be compiled as mod
twl4030-vibra
#leds
ledslp5523
#wlan
cfg80211
mac80211
wl1251_spi
wl1251
#bluetooth

#battery meter
bq27x00_battery
#power
power_supply
#twl4030support (compiled in)
#charger
isp1704_charger
#usb gadget
g_nokia

#multifunction
#TWL4030 (co)
#+TWL5030 MADC (audio-digital)
#MMC #all (compiled in: bootdevice on mmc)
now you edit /etc/X11/xorg.conf and put in:
Code:
Section "InputClass"
        Identifier "tslib touchscreen"
        Driver "tslib"
        MatchIsTouchscreen "yes"
EndSection

Section "InputClass"
        Identifier      "Touchscreen"
        MatchProduct    "TSC2005 touchscreen"
        Option          "Calibration" "225 3931 3740 231"
        Option          "SendCoreEvents" "yes"
        Driver          "evdev"
EndSection

Section "InputClass"
        Identifier      "Keyboard"
        MatchProduct    "TWL4030 Keypad|gpio-keys"
        Option          "XkbModel" "nokiarx51"
        Option          "XkbLayout" "us"
        Option          "XkbOptions" "grp:ctrl_shift_toggle"
        Driver          "evdev"
EndSection
for the usb net add to /etc/network/interfaces:

Code:
auto lo
iface lo inet loopback

auto usb0
allow-hotplug usb0
iface usb0 inet static
     address 192.168.3.101
     netmask 255.255.255.0
     gateway 192.168.3.100

noauto phonet0  wlan0 wmaster0
adjust the internetadress such, that the gateway is the ip of the usb interface of your pc and choose any free ip as address in the same network(that is: everything but the last number should be equal).
go to /etc/resolv.conf and put a dns server address in(create the file).
Code:
nameserver 192.168.10.1
use a /real/ nameserver address.
turn your pc into a gateway. for linux you can do it eg (you may want to have it more sophisticated):
Code:
iptables -A  FORWARD -j ACCEPT
iptables -tnat -A  POSTROUTING -o eth0 -j MASQUERADE
echo 1 > /proc/sys/net/ipv4/ip_forward
now add a 3rd vfat partition. put the kernel on it(just the way you would do it if you were installing meego).
Code:
mkimage  -A arm -O linux -T kernel -C none -a 80008000 -e 80008000 -n zImage -d zImage uImage
mkdir -p /mnt/kern
mount /dev/mmcblck1p3 /mnt/kern
cp uImage /mnt/kern
grab the uboot from extras devel and install it.

either
a) make sure that you have the correct root= attribute in the boot.scr. it should be /dev/mmcblk0p2. and have a rootwait (or rootdelay=) attribute. and so on... look at the bootparams meego has, it should be what you want. [nb: it might be that your kernel uses a fixed bootparam string in that case go for option b ]
put a script in a file say bootscript.txt(from top of my head):
Code:
kernaddr=0x80300000
setenv bootargs root=/dev/mmcblk0p2 rootwait ..
fatload mmc 1:3 ${kernaddr} uImage
bootm ${kernaddr}
and roll it and put it on the vfat
Code:
mkimage -A arm -O linux -T script -n bootscript -C none -d bootscript.txt boot.scr
cp boot.scr /mnt/kern
OR
b) make a backup of the sd. reformat it and put the stuff back on the partition that gets booted(and have the kernel on a 3rd vfat).
if you reformat you may want to increase the size of the partition. ubuntu recommends at least 3-4GB.
unmount everything.

maybe you need this if you don't see the configuration on first boot:

Code:
touch /var/lib/oem-config/run
boot.

if the keyboard is not working. connect via usb and ssh with the phone
[workaround if you don't know how to do it. take the sd +battery out. but wait some time so that the (log)files are really written on the sd and you don't end up with a corrupted sd.
boot into maemo OR look at the sd on your pc. mount it the way you did it before ]
have a look at the /etc/xorg.conf at the MatchProduct strings. they unfortunately vary sometimes slightly depending on the patches used.
compare it with the similar strings in the X logs.( /var/log/Xorg.0.log )
take the similar string you find in the log and replace the string in the xorg.conf with that exact string(the bar in the keyboard product is an "or". so this are two strings separated by the bar -> it catches two drivers. if you have one of them working you are good. don't need both, either works).
finally restart gdm or reboot.

if you want to use the phone install ofono.
Code:
apt-get update
apt-get upgrade
apt-get install ofono
....
so far. maybe i look later for spelling mistakes and the like in this post.... maybe not...

Last edited by lunat; 2010-11-10 at 10:00.
 

The Following 11 Users Say Thank You to lunat For This Useful Post:
juandp77's Avatar
Posts: 203 | Thanked: 201 times | Joined on Jun 2010 @ Ecuador
#320
I follow your steps but i can get to boot it, can you please explain the last part about the kernel and how to configurate u-boot
 
Reply

Tags
bada rox

Thread Tools

 
Forum Jump


All times are GMT. The time now is 19:44.