maemo.org - Talk - debian jessie image for N900

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)

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.

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.

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

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/

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)

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

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.

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

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.

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