maemo.org - Talk - debian jessie image for N900

Page 1 of 4

Next >

Last »

Show 40 post(s) from this thread on one page

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

- Alternatives (https://talk.maemo.org/forumdisplay.php?f=36)

- - debian jessie image for N900 (https://talk.maemo.org/showthread.php?t=93251)

caveman

2014-05-28 20:28

debian jessie image for N900

3 Attachment(s)

I prepared a card image of debian jessie to try on the N900. I am posting the torrent here for those willing to have some fun with it :-)

This is a minimal image, and not meant to be production-ready, but I find it worth a look.

The image is to be flashed to a 2Gb+ micro SD card:

Code:

xzcat jessie.dd.xz > /dev/sdX

where sdX is your device. This will destroy the contents on the card!

The image uses upstream linux 3.12 kernel from

Code:

git://gitorious.org/linux-n900/linux-n900.git

with branch

Code:

v3.12-rc5-n900

Check http://elinux.org for the current kernel status.

To boot, Pali's u-boot is required. Use the following file in

Code:

/etc/bootmenu.d

Code:

ITEM_NAME="debian jessie @ SD"

ITEM_KERNEL="uImage"

ITEM_INITRD="uInitrd"

ITEM_DEVICE="${EXT_CARD}p1"

ITEM_FSTYPE="vfat"

ITEM_OMAPATAG="1"

ITEM_CMDLINE="root=/dev/mmcblk0p2 rootwait vram=12M console=tty0 quiet"

Then run

Code:

u-boot-update-bootmenu

and if all goes well, you can reboot and choose debian at the menu.

It boots to the console and there is only the root user. The password is

Code:

rootme

By executing

Code:

startx

you can start enlightenment. Choosing the mobile profile gives a nice touch friendly interface.

You can load the n900 keyboard tweaks from the Arch Linux thread with

Code:

loadkeys /usr/share/keymaps/rx51_us.map

In that thread there is even a map of the keyboard http://talk.maemo.org/showpost.php?p...&postcount=205

To quickly connect to wifi, use the following:

Code:

wpa_supplicant -B -i interface -c <(wpa_passphrase MYSSID passphrase)

dhclient wlan0 &

When you are satisfied, you may proceed to network configuration in

Code:

/etc/network/interfaces

or using the network manager of choice.

I am thankful to the authors of all the pieces that have been used here to make this possible!

Have fun ;-)

thread hilights:
* for keyboard led, see post 53
* for battery info, see post 54
* to chroot into maemo, see post 57
* to set keyboard under X, see post 58
* kernel 3.16.0-rc1 on post 99; instructions on post 98

Boemien

2014-05-28 21:16

Re: debian jessie image for N900

Thanks for your efforts and your work. I'm going to have more informations about debian jessie and test this image. I will post my feedbacks or problems! :D

wicket

2014-05-28 22:22

Re: debian jessie image for N900

Thanks. I've been working on something similar. I plan to release some helper scripts very soon that will make it easy for anyone to bootstrap and customise their own Debian Jessie system with a recent kernel. I hope that eventually Debian will be a real alternative to Maemo. I'll be sure to check out your image to see what you've done and if there's anything useful I can use in my scripts.

nokiabot

2014-05-29 03:42

Re: debian jessie image for N900

Some screenshots will do great :)

Estel

2014-05-29 06:29

Re: debian jessie image for N900

Quote:

Originally Posted by wicket (Post 1427115)

I hope that eventually Debian will be a real alternative to Maemo.

I appreciate your work and like your optimism, so not mean to discourage at all... But as history of such efforts have shown, I'm afraid that, if we add up all the bits to have Maemo-comparable battery usage in Debian-like system (thus, implementing power-saving features and rules) - not to mention such "fancy" things like phone functionality - we will end up with something like Mer. Realizing, that we've re-created work that others did already, years ago.

One of the Mer developers just told me, once (in another "Debian-as-alternative-to-Maemo" thread), that it starts with patch to ignore screen input when locked. Then, it proceeds to actually shutting down touchpad (which eats lotta hell of power, if compared to really idle standby), not only ignoring it. Then you add... And, after months of work what started as mainstream any-distro on N900/whatever device, becomes a patched together frankenstein, or, at best, a Mer clone.

/Estel

wicket

2014-05-29 07:18

Re: debian jessie image for N900

Quote:

Originally Posted by Estel (Post 1427172)

If I wanted Mer I would be using and contributing to Nemo. Whilst I appreciate the work that the Mer team have put into their project, I'm afraid it's not an acceptable solution for my usage. The beauty of Debian is that it's very modular and components can easily be swapped out with an "apt-get install". Try running an init system other than systemd on Mer. It can be done but not without porting effort and even so, I doubt it they would accept it as part of their project as they intentionally have a very specific base system. Mer is also plagued by being business-focused which means they stick to outdated GPLv2 packages to allow vendors to Tivoise their products. Not to mention the array of software that Debian has accumulated over the years which you will never see in Mer.

I realise there will be many patches involved to achieve the power saving performance of Maemo but I don't see why it has to be a Frankenstein. Focusing on a specific Debian release means that it will be far less of a Frankenstein than the Etch+Lenny+Squeeze monster we like to refer to as Fremantle.

The Debian effort will be far from a Mer clone. We may have to recreate a lot of the work that others have done in Mer but it will be worthwhile in the end in order have a mobile operating system that excels where Mer and Maemo don't.

AapoRantalainen

2014-05-29 11:59

Re: debian jessie image for N900

Seeders? Or direct download link?
--------
How you did this image? How about adding user-account, autostarting X, and keymap (things mentioned on first post)? I know it will still not be production-ready, but little closer.

I see lot of potential of this (more than my latest attempt to seriously update Fremantle: http://talk.maemo.org/showthread.php?t=91709).

--------
Can I use repartitioned internal flash instead of card? (No spare cards on hands.)
--------

Android_808

2014-05-29 14:11

Re: debian jessie image for N900

Does qt5 work with touch and hw keyboard? If so I could be really interested here.

Aapo: Maybe you could try building hildon or qildon using this image. See how much fremantle stuff can be shoe-horned into jessie as opposed to trying to shove jessie into fremantle.

As its targeting a specific debian release, why not make it its own release instead of trying to keep 100% compatible with fremantle. We now have mce and bme replacements. Replacement apps in qt4 should be easy to port to qt5. microbe was based off sailfish-browser, so that can easily be changed to qt5. FMG, Pail and co. have been working on upstream kernel.

Maybe even swap in connman.

Estel

2014-05-29 18:35

Re: debian jessie image for N900

Quote:

Originally Posted by wicket (Post 1427180)

Incidentally, it's my situation, as well ;) I just lost hope for a N900'ized Debian long time ago, amongst ashesh of plentora of projects that were left unfinished, due to overhelming amount of work needed, and to few hands willing (or able, skill-wise) to do the job.

Anyway, if it would ever happen, I would be very, very glad. Count me in for any testing, or anything else that I'm not short on knowledge, for :)

/Estel

szopin

2014-05-29 19:40

Re: debian jessie image for N900

Would also be interested in booting/testing from internal, mmc currently in use in Jolla. (and count me in if you need testers or other low skilled helpers)

taixzo

2014-05-29 19:43

Re: debian jessie image for N900

Is there a way to set up u-boot without flashing? I have a broken USB port and thus can't flash a new kernel.

misiak

2014-05-29 21:03

Re: debian jessie image for N900

Quote:

Originally Posted by taixzo (Post 1427298)

Is there a way to set up u-boot without flashing? I have a broken USB port and thus can't flash a new kernel.

You can install it from the debs provided by pali (I'm not sure they are in any repo... I think so, but you should ask in u-boot thread to be sure). Then the phone flashes itself (the u-boot package flashes the kernel booting part of memory with u-boot and attached kernel). USB is not needed to flash u-boot.

elros34

2014-05-29 21:25

Re: debian jessie image for N900

Quote:

Originally Posted by wicket (Post 1427115)

That would be cool. Check this ubuntu installer maybe it will speed up your progress :)

sulu	2014-05-29 21:40

Re: debian jessie image for N900

Quote:

Originally Posted by AapoRantalainen (Post 1427208)

Seeders? Or direct download link?

Same here.
If I get the image I can provide a quite stable though slow seed.

Boemien

2014-05-30 00:09

Re: debian jessie image for N900

Quote:

Originally Posted by szopin (Post 1427297)

Would also be interested in booting/testing from internal, mmc currently in use in Jolla. (and count me in if you need testers or other low skilled helpers)

Oh please, it's been a long time that we didn't have a project like this about the N900, please, please, don't break my joy with Jolla / Sailfish stuff!!!! :D ;)

:p

caveman

2014-05-30 11:05

Re: debian jessie image for N900

Quote:

Originally Posted by wicket (Post 1427115)

I'll be sure to check out your image to see what you've done and if there's anything useful I can use in my scripts.

My script is really simple, as it is just a debootstrap on steroids :-) There are lots of info in the ubuntu and arch threads. I have another post on another debian thread that outlines the steps.

The most important tweaks are the keyboard configuration, X calibration and choice of packages.

Of course, the devil is in the details, so to make a script to create a really tweaked system ready for use requires a lot of work.

caveman

2014-05-30 11:06

Re: debian jessie image for N900

Quote:

Originally Posted by nokiabot (Post 1427159)

Some screenshots will do great :)

Just added ;-)

caveman

2014-05-30 11:22

Re: debian jessie image for N900

Quote:

Originally Posted by AapoRantalainen (Post 1427208)

Seeders? Or direct download link?

I will look into it, but I don't have a suitable system available.

Quote:

How you did this image? How about adding user-account, autostarting X, and keymap (things mentioned on first post)? I know it will still not be production-ready, but little closer.

For the image creation, see
http://talk.maemo.org/showpost.php?p...2&postcount=14
and
https://wiki.debian.org/n900-wheezy-armhf

Regarding the lack of configuration, that was intentional, so as to make clear that this is not a end-user image. Nonetheless:
* to add a user account user, adduser <username> and add the user to goups audio, video, netdev and plugdev
* to have X autostart, apt-get install a display manager such as slim
* the keymap is configured, but a loadkeys is required to load the arch-thread version of the keymap, which I like a lot but is non-standard. This can easily be automated by placing the command in /etc/rc.local.

Quote:

I see lot of potential of this (more than my latest attempt to seriously update Fremantle: http://talk.maemo.org/showthread.php?t=91709).

I believe this has potential as well, but the lack of touch-enabled apps impair casual use, as opposed to dedicated use (where you can really use the stylus to pick a desktop app menu item).

Maybe a thumb-patched nemo kernel would even be used to run hildon in a chroot.

Quote:

--------
Can I use repartitioned internal flash instead of card? (No spare cards on hands.)
--------

Yes, sure. My n900 has this installation on a 11Gb partition in the eMMC. The only required modification is to change /etc/fstab to use UUIDs and change the u-boot item file to point to the correct root device.

caveman

2014-05-30 11:25

Re: debian jessie image for N900

Quote:

Originally Posted by Android_808 (Post 1427222)

Maybe even swap in connman.

As a quick note, connman is in the image.

caveman

2014-05-30 11:36

Re: debian jessie image for N900

I will try to make this link available for a few days:
https://187.115.25.181/public/n900/jessie.dd.xz

szopin

2014-05-30 18:33

Re: debian jessie image for N900

Quote:

Originally Posted by caveman (Post 1427420)

I will try to make this link available for a few days:
https://187.115.25.181/public/n900/jessie.dd.xz

uploaded to dropbox:
https://db.tt/UvPwWoUm

AapoRantalainen

2014-05-30 20:52

Re: debian jessie image for N900

I didn't yet get this working. I have one major problem with booting and couple on details.

I have one ext2-partition for jessie on my internal card: /dev/mmcblk0p4

I downloaded and mounted jessie.dd on my computer and this is what I got:

Code:

fdisk -l jessie.dd

jessie.dd1   *        4096      253951      124928    c  W95 FAT32 (LBA)

jessie.dd2          253952     3911679     1828864   83  Linux



sudo mount jessie.dd -o offset=$((4096 * 512)) partition1

sudo mount jessie.dd -o offset=$((253952 * 512)) partition2

I copied files to N900:/dev/mmcblk0p4. Files from partition1 (uImage,uInitrd,initrd.img-3.12.0-rc5+) under the /boot (on that 0p4 partition).

Then I installed u-boot (package name u-boot-flasher), do I need something more?

Then created item:

Code:

echo 'ITEM_NAME="debian jessie"

ITEM_KERNEL="/boot/uImage"

ITEM_INITRD="/boot/uInitrd"

ITEM_DEVICE="${INT_CARD}p4"

ITEM_FSTYPE="ext2"

ITEM_OMAPATAG="1"

ITEM_CMDLINE="root=/dev/mmcblk0p4 rootwait vram=12M console=tty0 quiet" ' > /etc/bootmenu.d/jessie.item

And run u-boot-update-bootmenu. (No errors).

Reboot with keyboard open and I can see penguin-menu, very same than on first post on U-boot thread http://talk.maemo.org/showthread.php?t=81613 (but version number is 2013.04). So where is my jessie-entry?

-----
I compiled kernel from v3.12-rc5-n900 branch (with your instructions: http://talk.maemo.org/showpost.php?p...2&postcount=14). And I got uImage generated with mkimage (help with u-boot -thread #1).

How will I generate initrd.img-3.12.0-rc5+ and uInitrd?

-------
I tried 'debootstrap jessie' on Maemo, but it won't work because dpkg is too old. At least libaudit is compressed with xz and it needs something like dpkg-0.8.13.1 (and maemo5 has 0.7.20.2maemo13.1). Do you get workaround for that?

I run 'debootstrap -foreign' on ubuntu computer and then planning to run 'debootstrap/debootstrap --second-stage' on N900, but chroot gives "too old kernel" or "Exec format error". Do you have workaround for that?

caveman

2014-05-30 22:18

Re: debian jessie image for N900

Quote:

Originally Posted by AapoRantalainen (Post 1427511)

Then I installed u-boot (package name u-boot-flasher), do I need something more?

You need u-boot-tools, but it is probably in as a dep.

Quote:

ITEM_CMDLINE="root=/dev/mmcblk0p4 rootwait vram=12M console=tty0 quiet" ' > /etc/bootmenu.d/jessie.item[/CODE]

This seems weird, but probably a typo.

Quote:

Reboot with keyboard open and I can see penguin-menu, very same than on first post on U-boot thread http://talk.maemo.org/showthread.php?t=81613 (but version number is 2013.04). So where is my jessie-entry?

I am running the same u-boot version. If you don't see the jessie entry, there must be a problem in your u-boot config. Check the messages when you run u-boot-update-bootmenu and look for messages related to the jessie item file.

Quote:

How will I generate initrd.img-3.12.0-rc5+ and uInitrd?

inside debian or in a chroot, you should configure your fstab and run

Code:

update-initramfs -k 3.12.0-rc5+ -c

This will build the initrd inside /boot. Then you run mkimage as described in https://elektranox.org/n900/kernel/uboot.html at the very end.

Quote:

I tried 'debootstrap jessie' on Maemo, but it won't work because dpkg is too old. At least libaudit is compressed with xz and it needs something like dpkg-0.8.13.1 (and maemo5 has 0.7.20.2maemo13.1). Do you get workaround for that?

I installed on device debootstraping to wheezy, and then upgrading to jessie. This has one additional advantage, as chroot works, and you can chroot into debian to make things boot quickly. Once you upgrade to jessie, chroot says that kernel is too old.

So why not stay in wheezy? Because e17 with illume is available in jessie, and in my view this is the most touch friendly option we have atm.

That being said, I built the jessie image using another arm device. A rooted android phone or tablet with external card should do the job. I used a cubieboard. In the end, that's why I published the image, as there are several annoying details to overcome.

AapoRantalainen

2014-05-31 17:14

Re: debian jessie image for N900

Still uboot -problem:
(Yes, this is my first time to use u-boot)

1) I wrote jessie.dd to the SD-card. (with 'fdisk -l' I can verity this step worked)

2) installed u-boot-flasher which also installs u-boot-tools. (I also installed and then removed bootmenu, can it affect? )

3) Created file: /etc/bootmenu.d/10-jessie.item with content from post#1 (using ssh copy-paste -> no typos)

4) run u-boot-update-bootmenu, full log:

Code:

Adding bootmenu entry for: 'Maemo 5 with attached kernel 2.6.28-omap1 (Internal Nand)'



Configuration file: /etc/bootmenu.d/10-jessie.item

Adding bootmenu entry for: 'debian jessie @ SD'



Generating u-boot bootmenu script...

And it generates /home/user/MyDocs/bootmenu.scr, which is binary file, but I can see it contains also jessie-entry:

Code:

strings /home/user/MyDocs/bootmenu.scr

bootmenu

setenv bootmenu_0 'Maemo 5 with attached kernel 2.6.28-omap1 (Internal Nand)=run attachboot';setenv bootmenu_1 'debian jessie @ SD=setenv mmcnum 0;setenv mmcpart 1;setenv mmctype fat;setenv bootargs root=/dev/mmcblk0p2 rootwait vram=12M console=tty0 quiet;setenv setup_omap_atag 1;setenv mmckernfile /boot/uImage;setenv mmcinitrdfile /boot/uInitrd;setenv mmcscriptfile;run trymmckerninitrdboot;';setenv bootmenu_2;

Folder /home/user/MyDocs/bootmenu.img.d/ is empty. (I don't know how it should be, but it has same timestamp than bootmenu.scr)

5) reboot with keyboard open
-> uboot-menu without jessie-entry:

There are these five entries:
*Attached kernel
*Internal eMMC
*External SD Card
*U-boot boot order
*U-boot console

What I'm missing?

[EDIT]
I found that maemo5 can't mount ext4 partition on jessie.dd. So could this be an issue? (even u-boot supports ext4).
[/EDIT]

elros34

2014-05-31 18:28

Re: debian jessie image for N900

Formating fat partition probably solve this issue. Check u-boot thread and similar problems: http://213.128.137.28/showpost.php?p...&postcount=618

AapoRantalainen

2014-06-01 07:15

Re: debian jessie image for N900

Quote:

Originally Posted by elros34 (Post 1427614)

Formating fat partition probably solve this issue. Check u-boot thread [...]

Indeed problem was ~corrupted MyDocs-partition. I had repartitioned internal card with backupmenu+gparted and there was something happened to the vfat-partition. Even Fremantle can read it, u-boot can't.

Code:

#backup MyDocs (if needed)

#cp -r MyDocs/ MyDocs_backup



root

umount /home/user/MyDocs

#if 'device is busy' use:

#lsof /home/user/MyDocs

#kill 





mkfs.vfat /dev/mmcblk0p1



#reboot to remount, or 

mount /dev/mmcblk0p1 /home/user/MyDocs -o rw,noauto,nodev,noexec,nosuid,noatime,nodiratime,utf8,uid=29999,shortname=mixed,dmask=000,fmask=0133,rodir

exit

#roll backups back

#cp -a MyDocs_backup/. MyDocs

#You will get a lot of: "cannot preserve ownership of XXX #Operation not permitted" (because copying from ext to fat)

And then I got my entries visible on bootmenu.

AapoRantalainen

2014-06-01 10:24

Re: debian jessie image for N900

Next problem:

Now I have jessie on my bootmenu, but choosing it doesn't work.

(With ubuntu computer) I downloaded jessie.dd.xz and uncompressed it. Then attached SD-card and checked what device it is. Run:

Code:

sudo dd if=jessie.dd of=/dev/mmcblk0

(With N900)
Attached SD-card and booted keyboard closed. Checked that first partition of SD card got automounted "/dev/mmcblk1p1 on /media/mmc1" and it contains files "initrd.img-3.12.0-rc5+ uImage uInitrd".
Note: it is /dev/mmcblk1p1. Is this wrong? What I can do for it?

Second partition (/dev/mmcblk1p2) can't be mounted because it is ext4 (and default kernel doesn't support ext4, I think). Is this critical?

Booted keyboard open and selected jessie on bootmenu, but it ends:

Code:

mmc0 is current device

reading /boot/uInitrd

** Unable to read file /boot/uInitrd



Extra commands

...

How to proceed? If my external card goes to mmc1, what is mmc0 then? And how to fix it?

peterleinchen

2014-06-01 11:24

Re: debian jessie image for N900

Maybe just typo now?

In bootmenu.scr you wrote /boot/uImage and in above post just /uImage?
Double check that.

About mmcblk: in the bootmenu mmcnum0 is the SD card and mmcnum1 is eMMC device. In the config entries you should use ${EXT_CARD} to avoid confusion.

caveman

2014-06-01 11:32

Quote:

Originally Posted by AapoRantalainen (Post 1427700)

And how to fix it?

I suggest you install kp52 for two reasons: you will be able to validate your u-boot setup and it has support for ext4.

In a previous post you had an item file pointing to the emmc partition. Have you reverted that back to vfat on the sd?

sakrabojski

2014-06-01 12:16

Re: debian jessie image for N900

Hello Aapo, I had the same problem (** Unable to read file /boot/uInitrd) and it took me hours to see that uInitrd and other files wasn't in folder /boot.
So mkdir boot and then mv files in boot dir.

Hope this helps.:)

AapoRantalainen

2014-06-01 12:53

Re: debian jessie image for N900

Quote:

Originally Posted by peterleinchen (Post 1427703)

In bootmenu.scr you wrote /boot/uImage and in above post just /uImage?
Double check that.

Thanks. Jessie.item on first post uses /boot/uImage, but uImage is on /uImage on the disk-image.
-> I got it running.

peterleinchen

2014-06-01 13:21

Re: debian jessie image for N900

Quote:

Originally Posted by AapoRantalainen (Post 1427713)

Thanks.
-> I got it running.

You are welcome.
It was a pleasure to be able to help you.

AapoRantalainen

2014-06-01 13:35

Re: debian jessie image for N900

Next problem (I'm feeling newbie again):

I can't connect to wifi. I'm trying to connect open access point.

I thought that this will work:

Code:

iwconfig wlan0 essid ESSID

dhclient -v wlan0

But it doesn't get IP. Is there something blocking it. Dmesg contains "wlan0: deauthentication from XX: by local choise (reson=3)"
(connman or wpa_supplicant maybe?)

caveman

2014-06-01 15:23

Quote:

Originally Posted by AapoRantalainen (Post 1427716)

Check that connman is not running and disable wifi power save. Have you checked that wifi fw has been loaded?

See http://www.aboutcher.co.uk/2012/07/l...-reason-codes/

AapoRantalainen

2014-06-01 19:02

Re: debian jessie image for N900

Quote:

Originally Posted by caveman (Post 1427722)

Check that connman is not running and disable wifi power save. Have you checked that wifi fw has been loaded?

'ps -Af' showed pid of connman and I killed it.

I don't know how to disable wifi power save.
I can guess: 'iwconfig wlan0 txpower fixed', close enough?

wifi firmware log is somewhere on dmesg right? As I first tried without X, I didn't figure how to produce pipe or redirect output (| and >).

Should firmware get started automatically?

But somehow I get it connected and ssh running. Now I'm afraid to reboot device.

--------

I'm so excited about this. I'm planning something like this:

Add to /etc/apt/sources.list

Code:

deb-src http://repository.maemo.org/ fremantle/sdk free

deb-src http://repository.maemo.org/ fremantle/tools free

free

deb-src http://repository.maemo.org/community-testing/ fremantle free



deb-src http://repository.maemo.org/extras-devel fremantle free

and then:

Code:

apt-get source libhildon1

dpkg-buildpackage

-> missing bunch of stuff

apt-get install .... (from jessie) 

dpkg-buildpackage

fix-the-code

And then some other packages which 'are part of fremantle, but not yet (or anymore) in debian'.

I'm open for comments.
----
Another idea (which is not yet working): add your secret nokia-binaries-key to the /etc/apt/sources.list

Code:

deb http://repository.maemo.org/ fremantle/SECRET nokia-binaries

And then

Code:

apt-get install X

or

apt-get download X

where X is 'really useful but not yet liberated'-package from:
http://wiki.maemo.org/Fremantle_closed_packages

But apt-get update encounter error, because it is looking for

http://repository.maemo.org/dists/fremantle/SECRET/nokia-binaries/binary-armhf/Packages
but file on the server is
http://repository.maemo.org/dists/fremantle/SECRET/nokia-binaries/binary-armel/Packages
(verified with wget)

This armhf is not part of the deb-row, so is it resolved runtime, maybe by dpkg-architecture? So how to spoof it? (I haven't yet tested is there any possibility they could work at all)

misiak

2014-06-01 20:19

Re: debian jessie image for N900

Quote:

Originally Posted by AapoRantalainen (Post 1427750)

I'm so excited about this. I'm planning something like this:

Add to /etc/apt/sources.list

Code:

deb-src http://repository.maemo.org/ fremantle/sdk free

deb-src http://repository.maemo.org/ fremantle/tools free

free

deb-src http://repository.maemo.org/community-testing/ fremantle free



deb-src http://repository.maemo.org/extras-devel fremantle free

and then:

Code:

apt-get source libhildon1

dpkg-buildpackage

-> missing bunch of stuff

apt-get install .... (from jessie) 

dpkg-buildpackage

fix-the-code

And then some other packages which 'are part of fremantle, but not yet (or anymore) in debian'.

I'm open for comments.

I say: go for it :D

Quote:

Originally Posted by AapoRantalainen (Post 1427750)

Another idea (which is not yet working): add your secret nokia-binaries-key to the /etc/apt/sources.list

Code:

deb http://repository.maemo.org/ fremantle/SECRET nokia-binaries

And then

Code:

apt-get install X

or

apt-get download X

where X is 'really useful but not yet liberated'-package from:
http://wiki.maemo.org/Fremantle_closed_packages

But apt-get update encounter error, because it is looking for

http://repository.maemo.org/dists/fr...naries/binary-armhf/Packages
but file on the server is
http://repository.maemo.org/dists/fr...naries/binary-armel/Packages
(verified with wget)

This armhf is not part of the deb-row, so is it resolved runtime, maybe by dpkg-architecture? So how to spoof it? (I haven't yet tested is there any possibility they could work at all)

According to this: http://unix.stackexchange.com/questi...-ubuntu-system armel packages should work on armhf. See also https://wiki.debian.org/Multiarch/HOWTO - you should be able to install armel binaries using apt if you configure it properly ("dpkg --add-architecture armel" and later "apt-get update" should be enough I guess?)

caveman

2014-06-02 11:58

Re: debian jessie image for N900

Quote:

Originally Posted by AapoRantalainen (Post 1427750)

I can guess: 'iwconfig wlan0 txpower fixed', close enough?

Close enough :-)

Code:

iwconfig wlan0 power off

should do it.

Quote:

I didn't figure how to produce pipe or redirect output (| and >).

In the console, with the arch keymap, you can use shift+blue+\.

Quote:

Should firmware get started automatically?

Yes it should.

Quote:

I'm so excited about this. I'm planning something like this:

That is going to be *very* interesting :-)

Quote:

This armhf is not part of the deb-row, so is it resolved runtime, maybe by dpkg-architecture? So how to spoof it? (I haven't yet tested is there any possibility they could work at all)

There is a debian armel repo as well. So you should be able to

Code:

dpkg --add-architecture armel

dpkg --print-architecture

apt-get update

apt-get install <package>:armel

I suggest you configure apt preferences placing debian armel with higher priority than fremantle, so you can pull from upstream debian as many packages as possible.

sulu	2014-06-02 12:54

Re: debian jessie image for N900

Quote:

Originally Posted by AapoRantalainen (Post 1427511)

I run 'debootstrap -foreign' on ubuntu computer and then planning to run 'debootstrap/debootstrap --second-stage' on N900, but chroot gives "too old kernel" or "Exec format error". Do you have workaround for that?

Just in case this is still of interest:
Jessie's glibc has 2.6.32 hardcoded (i.e. not just a debian dependency) as a minimum requirement. So if you want to run a Jessie glibc on top of Maemo's 2.6.28 kernel you need to patch and recompile the glibc sources. [1]
The result apparently works but since I have done only very basic testing in Easy Debian I can't tell if there are any subtle problems I just didn't see.

[1] http://talk.maemo.org/showpost.php?p...postcount=3030

Android_808

2014-06-02 13:16

Re: debian jessie image for N900

I would stick with upstream n900 kernel. fmg pointed me to the patch for the driver which contains test instructions for using ofono. I would use that along with a replacement "phone" app to remove more of the closed apps.

AapoRantalainen

2014-06-03 20:36

Re: debian jessie image for N900

Now my wireless are connecting easily without tricks (iwconfig essid + dhclient), don't know what happened.

What is the preferred way to get same MAC-adddress on every boot?
-----------------------------
I also think that now is the moment to drop maemo's 2.x kernel.

Do we have gles-driver which work with new kernel?
What is the way (in the meantime) use software openGL? E.g. I tested glxgears from mesa-utils, I have installed libgl1-mesa-glx and glx-alternative-mesa, but no success:

Code:

Error: couldn't get an RGB, Double-buffered visual

and glxinfo

Code:

name of display: :0

Error: couldn't find RGB GLX visual or fbconfig

Error: couldn't find RGB GLX visual or fbconfig

-----------------------------

By the way: This is dmesg, just after boot http://paste.ubuntu.com/7581763/
There are couple of things I would like to point for somebody deep in kernel (even they are not show-stoppers yet):

Code:

row 105: 

[    4.440856] ------------[ cut here ]------------

[    4.440917] WARNING: CPU: 0 PID: 1 at drivers/video/omap2/dss/dss.c:540 dss_set_clock_div+0x9c/0xcc()

[    4.440917] clk rate mismatch: 86400000 != 172800000

[    4.440948] Modules linked in:

[    4.440979] CPU: 0 PID: 1 Comm: swapper Not tainted 3.12.0-rc5+ #2

[    4.441040] [<c00124c0>] (unwind_backtrace+0x0/0xe0) from [<c0010a64>] (show_stack+0x10/0x14)

[    4.441070] [<c0010a64>] (show_stack+0x10/0x14) from [<c0032024>] (warn_slowpath_common+0x64/0x84)

[    4.441101] [<c0032024>] (warn_slowpath_common+0x64/0x84) from [<c00320c4>] (warn_slowpath_fmt+0x2c/0x3c)

[    4.441131] [<c00320c4>] (warn_slowpath_fmt+0x2c/0x3c) from [<c01d7468>] (dss_set_clock_div+0x9c/0xcc)

[    4.441162] [<c01d7468>] (dss_set_clock_div+0x9c/0xcc) from [<c0538460>] (omap_dsshw_probe+0x1e0/0x2f4)

[    4.441192] [<c0538460>] (omap_dsshw_probe+0x1e0/0x2f4) from [<c0224bc8>] (platform_drv_probe+0x14/0x18)

[    4.441223] [<c0224bc8>] (platform_drv_probe+0x14/0x18) from [<c0223ad0>] (driver_probe_device+0xac/0x1f8)

[    4.441284] [<c0223ad0>] (driver_probe_device+0xac/0x1f8) from [<c0223c84>] (__driver_attach+0x68/0x8c)

[    4.441314] [<c0223c84>] (__driver_attach+0x68/0x8c) from [<c02221f8>] (bus_for_each_dev+0x50/0x88)

[    4.441345] [<c02221f8>] (bus_for_each_dev+0x50/0x88) from [<c0223230>] (bus_add_driver+0xcc/0x244)

[    4.441375] [<c0223230>] (bus_add_driver+0xcc/0x244) from [<c02242e8>] (driver_register+0x9c/0xe0)

[    4.441406] [<c02242e8>] (driver_register+0x9c/0xe0) from [<c0224e4c>] (platform_driver_probe+0x1c/0xb4)

[    4.441436] [<c0224e4c>] (platform_driver_probe+0x1c/0xb4) from [<c05381ec>] (omap_dss_init+0x1c/0xb0)

[    4.441436] [<c05381ec>] (omap_dss_init+0x1c/0xb0) from [<c00086f8>] (do_one_initcall+0x94/0x138)

[    4.441497] [<c00086f8>] (do_one_initcall+0x94/0x138) from [<c0517b08>] (kernel_init_freeable+0xe4/0x1ac)

[    4.441528] [<c0517b08>] (kernel_init_freeable+0xe4/0x1ac) from [<c037c668>] (kernel_init+0x8/0xe4)

[    4.441558] [<c037c668>] (kernel_init+0x8/0xe4) from [<c000de38>] (ret_from_fork+0x14/0x3c)

[    4.441619] ---[ end trace 8290e8a9c3e69da2 ]---



row 284:

[   11.652435] hci_h4p hci_h4p: Valid bluetooth address not found, setting some random



row 295:

[   12.606506] bq27x00-battery 2-0055: battery is not calibrated! ignoring capacity values





row 311:

[   12.904876] ------------[ cut here ]------------

[   12.905029] WARNING: CPU: 0 PID: 402 at drivers/media/v4l2-core/v4l2-dev.c:779 __video_register_device+0x44/0x1308 [videodev]()

[   12.905059] Modules linked in: radio_bcm2048(+) lis3lv02d input_polldev et8ek8 smiaregs bq2415x_charger(+) leds_lp5523(+) omap3_isp(+) bq27x00_battery leds_lp55xx_common omap_iovmm v4l2_common videodev rtc_twl twl4030_wdt tsl2563 industrialio twl4030_vibra cfg80211 ff_memless media tsc2005 hci_h4p bluetooth isp1704_charger ext4 mbcache jbd2 smc91x mii

[   12.907775] CPU: 0 PID: 402 Comm: modprobe Tainted: G        W    3.12.0-rc5+ #2

[   12.907836] [<c00124c0>] (unwind_backtrace+0x0/0xe0) from [<c0010a64>] (show_stack+0x10/0x14)

[   12.907867] [<c0010a64>] (show_stack+0x10/0x14) from [<c0032024>] (warn_slowpath_common+0x64/0x84)

[   12.907897] [<c0032024>] (warn_slowpath_common+0x64/0x84) from [<c003205c>] (warn_slowpath_null+0x18/0x1c)

[   12.908020] [<c003205c>] (warn_slowpath_null+0x18/0x1c) from [<bf1ec5e0>] (__video_register_device+0x44/0x1308 [videodev])

[   12.908172] [<bf1ec5e0>] (__video_register_device+0x44/0x1308 [videodev]) from [<bf27b6f8>] (bcm2048_i2c_driver_probe+0x118/0x354 [radio_bcm2048])

[   12.908233] [<bf27b6f8>] (bcm2048_i2c_driver_probe+0x118/0x354 [radio_bcm2048]) from [<c028b5ac>] (i2c_device_probe+0x78/0xa0)

[   12.909393] [<c028b5ac>] (i2c_device_probe+0x78/0xa0) from [<c0223ad0>] (driver_probe_device+0xac/0x1f8)

[   12.909423] [<c0223ad0>] (driver_probe_device+0xac/0x1f8) from [<c0223c84>] (__driver_attach+0x68/0x8c)

[   12.909454] [<c0223c84>] (__driver_attach+0x68/0x8c) from [<c02221f8>] (bus_for_each_dev+0x50/0x88)

[   12.909484] [<c02221f8>] (bus_for_each_dev+0x50/0x88) from [<c0223230>] (bus_add_driver+0xcc/0x244)

[   12.909515] [<c0223230>] (bus_add_driver+0xcc/0x244) from [<c02242e8>] (driver_register+0x9c/0xe0)

[   12.909545] [<c02242e8>] (driver_register+0x9c/0xe0) from [<c028c5fc>] (i2c_register_driver+0x8c/0xb0)

[   12.909576] [<c028c5fc>] (i2c_register_driver+0x8c/0xb0) from [<c00086f8>] (do_one_initcall+0x94/0x138)

[   12.914184] [<c00086f8>] (do_one_initcall+0x94/0x138) from [<c007a8dc>] (load_module+0x1914/0x1bf4)

[   12.914245] [<c007a8dc>] (load_module+0x1914/0x1bf4) from [<c007ad04>] (SyS_finit_module+0x5c/0x6c)

[   12.914276] [<c007ad04>] (SyS_finit_module+0x5c/0x6c) from [<c000dda0>] (ret_fast_syscall+0x0/0x30)

[   12.914306] ---[ end trace 8290e8a9c3e69da4 ]---





row 332:

[   12.914367] bcm2048: probe of 3-0022 failed with error -5

Maybe they are known, but if there are some workarounds, and will they be fixed for next kernel? (Or is there already newer kernel working equally well?)

--------
I'm using 'user' -account, and I can startx and then over ssh start e.g. DISPLAY=:0 xterm

When I try startx over ssh, it doesn't work:

Code:

X: user not authorized to run the X server, aborting.

xinit: giving up

xinit: unable to connect to X server: Connection refused

xinit: server error

I think I soon need this (when libmatchbox2 takes turn).

All times are GMT. The time now is 20:13.

Page 1 of 4

Next >

Last »

Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8