maemo.org - Talk - debian jessie image for N900

Page 2 of 4

< Prev

Next >

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-06-03 23:08

Re: debian jessie image for N900

Quote:

Originally Posted by AapoRantalainen (Post 1428091)

What is the preferred way to get same MAC-adddress on every boot?

Configure in /etc/network/interfaces:

Code:

iface wlan0 inet dhcp

  hwaddress address

Quote:

Do we have gles-driver which work with new kernel?

Skry had one accelerated driver for the 3.5 kernel in the arch thread, but my experience with it was not stable, so I migrated to fbdev.

Quote:

What is the way (in the meantime) use software openGL? E.g. I tested

I don't know :-(

Quote:

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

Check here for btaddr configuration: https://elektranox.org/n900/installation/hardware.html

Quote:

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

This reminds me that I have to check if battery charges on debian!

misiak

2014-06-04 09:05

Re: debian jessie image for N900

Quote:

Originally Posted by AapoRantalainen (Post 1428091)

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

Did you try something like "DISPLAY=:0 startx" (or maybe even export the DISPLAY variable set to :0 before starting X)? I remember having similar problems on Raspberry Pi at some point with Raspbian (but either I changed something in config files permanently and don't remember or the newer version of Raspbian is configured differently, because I cannot reproduce it now).

edit: on my other machine (home server) I get similar output (unable to start X) unless I type on my home computer "ssh -X server_ip", but then it starts X remotely on the screen of my home computer. If I find a moment, I'll try debug that and give you more useful information, but just wanted to step in now and note that this may not be related to Debian/N900, but it might be either generic Debian problem (my server runs Debian) or generic Linux/X.org/ssh problem.

mouzg

2014-06-04 12:58

Re: debian jessie image for N900

I love it.But what about charging?is there any way to charge n900 while in jessie?

saponga

2014-06-04 14:34

Re: debian jessie image for N900

Quote:

Originally Posted by mouzg (Post 1428174)

I love it.But what about charging?is there any way to charge n900 while in jessie?

I just tried to plug in charger but it seems that isn't charging because the led is continous yellow... not blinking. The device is a bit warmer than when running maemo. It has been 4 hours since i boot jessie but it stayed almost all that time on idle. Lets see how long time the bl-5j will last.

reinob

2014-06-04 14:35

Re: debian jessie image for N900

Quote:

Originally Posted by mouzg (Post 1428174)

I love it.But what about charging?is there any way to charge n900 while in jessie?

kernel-power (by Pali) has in-kernel charging (and it works :)

Obviously, the kernel being used here is not kernel-power, but perhaps includes the necessary modules/patches to make it work. Can't check now, but the module was bq2415x_charger.

Somebody with debian running on the N900 could try: modprobe bq2415x_charger and see what happens.

reinob

2014-06-04 14:38

Re: debian jessie image for N900

Quote:

Originally Posted by saponga (Post 1428189)

Hey, solid yellow IS the in-kernel charging. BME does the blinking, but we don't need BME :)
Please report if you can figure out whether the battery is charging or not.

My (short) experience[*] with this is that the battery actually charges but much more slowly than normal, but that may have been due to a faulty USB port.
[*] http://talk.maemo.org/showpost.php?p...&postcount=484

saponga

2014-06-04 15:17

Re: debian jessie image for N900

Quote:

Originally Posted by reinob (Post 1428190)

Somebody with debian running on the N900 could try: modprobe bq2415x_charger and see what happens.

No output here...

Code:

lsmod |grep bq2415x_charger

returns:

Code:

bq2415x_charger 14125 0

Quote:

Originally Posted by reinob (Post 1428191)

Thanks for the info :) Is there any way to check if its charging without boot maemo ?

mouzg

2014-06-04 18:07

Re: debian jessie image for N900

Im pretty sure it charges.I booted up jessie with two wires connected to my battery terminals.while voltage was 2.75 it went up to 2.85 when the charger connected (every time) and led solid yellow.I know its a little difference (100mv) but i think is enough for its voltage.

AapoRantalainen

2014-06-04 18:11

Re: debian jessie image for N900

My n900 have been running jessie on couple of last days all the time attached to the charger. Led is orange/yellow as stated earlier.

Now I booted it to the maemo and detached charger. Battery is fully charged.

wicket

2014-06-04 19:49

Re: debian jessie image for N900

I also have the same issue with the charging LED in my build. It definitely does charge and also the kernel seems to know when it's fully charged so it's unlikely that there's a risk overcharging our batteries. You can find battery info under /sys/class/power_supply/bq27200-0. I don't know if anyone else has experienced this but I get a kernel panic when I plug in the wall charger directly into the mains. Charging works fine however when connecting a USB cable to the USB port of my PC. I'm using freemangordon's 3.14-rc3 kernel by the way.

My main issues right now are that I've not yet got USB networking to work, the keyboard mapping doesn't work under E17 (even though it works fine on the console) but the most critical issue that I don't have a solution for something equivalent to Maemo's xprot to prevent blowing up the speakers.

I'm hoping to create a Git repo for my scripts within the next few days once I've tidied up a few things and done a bit more testing.

sakrabojski

2014-06-04 20:16

Re: debian jessie image for N900

1 Attachment(s)

Hy

I have installed Xmonad on our little beast and it works suprisingly well, it is fast, stable, low on mem ...
only downside is pretty large ghc as dependency (cca 600 mb) and lack of n900 Alt_l aka Mod1 key,
so I assign it to volume key and it works well.

Is there a way to assign '$ xset dpms force off' to kb_lock?
I found workaround but doesn't involve kb_lock.

Does anyone got audio working?
I've tried alsamixer, but moc doesn't give any response. :(
Then I tried with jack, in moc you can see that song is at least playing but there is no sound.:confused:

saponga

2014-06-04 21:48

Re: debian jessie image for N900

What about that keyboard LEDs ?

sakrabojski

2014-06-05 11:06

Re: debian jessie image for N900

Quote:

What about that keyboard LEDs ?

I've managed something with keyboard leds.

Here is a simple script:

Code:

#!/bin/sh



# there are different modes: run disabled load. I use run for ON and disabled for OFF

mode="run"



# 0-255

brightness="50"



echo $mode > /sys/class/i2c-adapter/i2c-2/2-0032/engine3_mode



echo $brightness > /sys/class/i2c-adapter/i2c-2/2-0032/leds/lp5523:kb1/brightness

echo $brightness > /sys/class/i2c-adapter/i2c-2/2-0032/leds/lp5523:kb2/brightness

echo $brightness > /sys/class/i2c-adapter/i2c-2/2-0032/leds/lp5523:kb3/brightness

echo $brightness > /sys/class/i2c-adapter/i2c-2/2-0032/leds/lp5523:kb4/brightness

echo $brightness > /sys/class/i2c-adapter/i2c-2/2-0032/leds/lp5523:kb5/brightness

echo $brightness > /sys/class/i2c-adapter/i2c-2/2-0032/leds/lp5523:kb6/brightness

Create two of those (with changed values), chmod it, put in path, add a line in visudo so you don't have to write password every time and enjoy typing in dark:cool:

Probably there is some more elegant way to achieve keyboard led on/off but...

sakrabojski

2014-06-05 18:55

Re: debian jessie image for N900

Script for voltage, capacity and temperature

Code:

#!/bin/sh





# status

stat=$(cat /sys/class/power_supply/bq27200-0/status) 



# time

if grep Charging /sys/class/power_supply/bq27200-0/status > /dev/null

        then

time=$(cat /sys/class/power_supply/bq27200-0/time_to_full_now)

        else

time=$(cat /sys/class/power_supply/bq27200-0/time_to_empty_avg) 

fi





# capacity

cfd=$(cat /sys/class/power_supply/bq27200-0/charge_full)

cn=$(cat /sys/class/power_supply/bq27200-0/charge_now)



# voltage

vmd=$(cat /sys/class/power_supply/rx51-battery/voltage_max_design)

vn=$(cat /sys/class/power_supply/bq27200-0/voltage_now)



# temp

temp=$(cat /sys/class/power_supply/bq27200-0/temp)



# out

echo status: $stat

if grep Charging /sys/class/power_supply/bq27200-0/status > /dev/null

        then 

echo $time | awk  '{ printf  ("time to full: %.2d:%.2d\n" , ($1/3600%24) , ($1/60%60)) }' 

        else

echo $time | awk  '{ printf  ("time to empty: %.2d:%.2d\n" , ($1/3600%24) , ($1/60%60)) }'         

fi

echo $cn $cfd | awk '{ printf ("capacity: %.1f%%\n" ,  ($1/$2*100) ) }'

echo $vn $vmd | awk '{ printf ("voltage: %.1f%%\n"  ,  ($1/$2*100) ) }'

echo $temp | awk '{ print "temp: " $1/10 "°C" }'

AapoRantalainen

2014-06-06 04:53

Re: debian jessie image for N900

Quote:

Originally Posted by sakrabojski (Post 1428334)

I've managed something with keyboard leds.

Here is a simple script:
...

This works. But row:

Code:

echo 3 > /sys/class/i2c-adapter/i2c-2/2-0032/select_engine

gives error

Code:

lp5523x 2-0032: firmware request failed

sakrabojski

2014-06-06 06:36

Re: debian jessie image for N900

Thanks for pointing it out, I overlooked it.
It seems that when you set mode run in engine_mode it automatically set which engine is active in select_engine, so

Code:

echo 3 > /sys/class/i2c-adapter/i2c-2/2-0032/select_engine

is unnecessary.

I've edited batt_info and kbd_led script.
bat_info is now more verbose and kbd_led doesn't produce error.

caveman

2014-06-06 12:44

Re: debian jessie image for N900

Here follows how to mount maemo fs from inside debian (from http://talk.maemo.org/showpost.php?p...2&postcount=61).

Code:

apt-get install mtd-utils

modprobe ubifs

ubiattach /dev/ubi_ctrl -m 5

mount -t ubifs ubi0:rootfs /mnt

mount /dev/mmcblk0p2 /mnt/home/

mount /dev/mmcblk0p1 /mnt/home/user/MyDocs/

For a chroot shell:

Code:

for i in sys dev proc; do mount -o bind /$i /mnt/$i; done

chroot /mnt /bin/sh

When done, undo:

Code:

fuser -k -M -m /mnt/

for i in sys dev proc; do umount /mnt/$i; done

umount /mnt/home/user/MyDocs/

umount /mnt/home/

umount /mnt

caveman

2014-06-06 13:29

Re: debian jessie image for N900

For a proper keyboard on X, run the following:

Code:

setxkbmap -rules evdev -model nokiarx51 -option grp:ctrl_shift_toggle -layout us

Please post if you know how to properly configure this in e17.

AapoRantalainen

2014-06-06 18:04

Re: debian jessie image for N900

Quote:

Originally Posted by caveman (Post 1428500)

Code:

apt-get install mtd-utils

modprobe ubifs

ubiattach /dev/ubi_ctrl -m 5

mount -t ubifs ubi0:rootfs /mnt

mount /dev/mmcblk0p2 /mnt/home/

mount /dev/mmcblk0p1 /mnt/home/user/MyDocs/

I have some difference when booted to jessie from sd-card:

Code:

/dev/mmcblk0p2 on / type ext4 (rw,noatime,data=ordered)

And maemo's home is: /dev/mmcblk1p2
And maemo's vfat MyDocs is: /dev/mmcblk1p1

mouzg

2014-06-06 18:39

Re: debian jessie image for N900

Quote:

Originally Posted by caveman (Post 1428509)

For a proper keyboard on X, run the following:
[CODE]
setxkbmap -rules evdev -model nokiarx51 -option grp:ctrl_shift_toggle -layout us

Please post if you know how to properly configure this in e17.

First create the following file

Code:

nano /usr/share/applications/keybset.desktop

with the following

Code:

[Desktop Entry]

Name=Keybset

Comment=Sets the RX-51 keyboard layout

Exec=setxkbmap -rules evdev -model nokiarx51 -option grp:ctrl_shift_toggle -layout us

Icon=false

NoDisplay=false

Terminal=true

Type=Application

Categories=

StartupNotify=true

After that make it executable

Code:

chmod a+x /usr/share/applications/keybset.desktop

Then goto Settings panel>Extensions Tab > Modules > Settings Tab And activate Applications module.
After its activated in Settings panel,Apps tab find Startup applications and activate Keybset.Your done
The only problem is that left and right arrows dont work for me.

mouzg

2014-06-06 23:40

Re: debian jessie image for N900

Has anyone managed to get usb hostmode working?
I tried pausing udev and then

Code:

echo host > /sys/devices/platform/musb_omap2340/musb-hdrc.0.auto/mode

as mentioned in
http://http://wiki.maemo.org/USB_host_mode and it doesnt work.
I understand that musb_omap2340 is another driver but hostmode is implemented in it.

radiochickenwax

2014-06-07 05:28

Re: debian jessie image for N900

Quote:

Originally Posted by AapoRantalainen (Post 1428091)

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:

Instead of libgl1-mesa-glx try libgl1-mesa-swx11

AapoRantalainen

2014-06-07 14:25

Re: debian jessie image for N900

Quote:

Originally Posted by radiochickenwax (Post 1428582)

Instead of libgl1-mesa-glx try libgl1-mesa-swx11

Yijpee!
glxinfo

Code:

direct rendering: Yes

server glx version string: 1.4 Mesa 10.1.4

glxgears

Code:

226 frames in 5.0 seconds = 45.104 FPS

153 frames in 5.0 seconds = 30.489 FPS

First is with screen dimmed and second is when screen is showing.

clutter-0.8 (compiled from fremantle) examples works too.

-----
I decided (at this phase) to not install/use any closed-source package. I have now compiled packages from maemo5, debian-squeeze and cordia (github).

My first milestone is hildon-desktop. It needs many libhildon related packages (including clutter) to compile and then bunch of more to install (and maybe some more to run).

Cordia contains hildon stuff for gtk3. I'm not sure that gtk3 is better (in any measure) than gtk2, but critical point is that original hildon uses forked gtk2 (it contains some 1000 commits over six years period by Nokia), and I definitely want get rid of it, so upstream gtk3 sounds way to go. Problem is that cordia doesn't contain proper debianization so I might been compiling more packages than really needed.

Squeeze is used because it is only debian which contains some hildon-stuff.
---------------
I'm also pondering what packages we need to achieve system which 'looks and feels as Fremantle'. (I think this is my goal?)

E.g. libosso:

Quote:

All maemo-compliant applications must use Libosso to respond coherently to system changes and signals, such as the battery low, pre-shutdown and state saving signals.

Android_808

2014-06-07 15:52

Re: debian jessie image for N900

Gtk3, as I stated elsewhere, has some changes which cater better for tablets so that should automatically drop some of the required changes. I'd really like to see Gtk3 and Qt5 as the main toolkits, or even just Qt5 if using a ported version of qildon.

I've been looking into required changes for hildon-components and they seem to be pretty straight forward. Replace declarative module with qml, rename included headers and so forth. Only big deal is if anything needs to use new scene graph from what I've read up on.
----
Have you had any luck with underlying components, if needed/worthwhile like bme, mce? Might simplify some of the scripts we've had posted so far.

sakrabojski

2014-06-08 11:30

Re: debian jessie image for N900

Quote:

Originally Posted by mouzg (Post 1428576)

Has anyone managed to get usb hostmode working?
I tried pausing udev and then

Code:

echo host > /sys/devices/platform/musb_omap2340/musb-hdrc.0.auto/mode

as mentioned in
http://http://wiki.maemo.org/USB_host_mode and it doesnt work.
I understand that musb_omap2340 is another driver but hostmode is implemented in it.

Are you sure it's not a typo?
On my device there is only musb-omap2430

mouzg

2014-06-08 21:24

Re: debian jessie image for N900

Yeah you're right.It was a typo posted in here but in my machine i typed it right.

Boemien

2014-06-09 17:18

Re: debian jessie image for N900

Hi Guys,

I tried by all the ways but i can't boot to Jessie. I followed all the steps from post 1 but no success! Trying to xzcat the file takes me an hour, with weird thing in the terminal, but does nothing to the card.
So I used Win32DiskImager-0.9.5-install under windows, to copy the image to the memory card, then copied the files inside 0.fat to /boot folder in the card.

When updating the boot menu, everything goes well, but when it boots it says no emmc0 or something like that!!!

I'm desperate :o :( lol! Okay, not so desperate but i'm like :mad: then I start over and over. What do I do wrong? Is it a problem of Ext2/vfat format or something else???

caveman

2014-06-09 18:35

Re: debian jessie image for N900

Quote:

Originally Posted by Boemien (Post 1428849)

Trying to xzcat the file takes me an hour, with weird thing in the terminal, but does nothing to the card.

Assuming you are on linux, use

Code:

lsblk

Code:

cat /proc/partitions

to identify the device name of your card. Then use this device name in the xzcat jessie.dd.xz. I hope this helps.

Boemien

2014-06-09 18:44

Re: debian jessie image for N900

thanks, i'm trying again under windows. If it goes bad, i'll try it under Ubuntu and post the results!!!

Edit: I put the SD card to the PC under Ubuntu, then i did

Code:

lsblk

the card is mmcblk0

so i did the zcat to /dev/mmcblk0

the weird symbols are showing in the terminal. I'll wait untill it finish!!

Boemien

2014-06-09 19:21

Re: debian jessie image for N900

Wow, i think that i missed something!!!

the first command i typed was

Code:

xzcat jessie.dd.xz /dev/mmcblk0

without the " > ".

now when I type

Code:

xzcat jessie.dd.xz > /dev/mmcblk0

the result is:

Code:

boemien@boemien-VPCEL23FD:~$ xzcat jessie.dd.xz > /dev/mmcblk0

bash: /dev/mmcblk0: Permission non accordée

boemien@boemien-VPCEL23FD:~$ sudo xzcat jessie.dd.xz > /dev/mmcblk0

bash: /dev/mmcblk0: Permission non accordée

boemien@boemien-VPCEL23FD:~$

same result with:

Code:

boemien@boemien-VPCEL23FD:~$ xzcat /home/boemien/Téléchargements/jessie.dd.xz > /dev/mmcblk0

bash: /dev/mmcblk0: Permission non accordée

boemien@boemien-VPCEL23FD:~$

:confused:

What is the right command?

PS: Permission non accordée means Permission Denied. :D

caveman

2014-06-09 21:04

Re: debian jessie image for N900

Quote:

Originally Posted by Boemien (Post 1428878)

Code:

boemien@boemien-VPCEL23FD:~$ xzcat /home/boemien/Téléchargements/jessie.dd.xz > /dev/mmcblk0

bash: /dev/mmcblk0: Permission non accordée

boemien@boemien-VPCEL23FD:~$

:confused:

What is the right command?

PS: Permission non accordée means Permission Denied. :D

If under ubuntu, run

Code:

sudo xzcat jessie.dd.xz > /dev/mmcblk0

Please be aware that this image is not ready for end-users ;-)

Boemien

2014-06-09 21:27

Re: debian jessie image for N900

Quote:

Originally Posted by caveman (Post 1428907)

If under ubuntu, run

Code:

sudo xzcat jessie.dd.xz > /dev/mmcblk0

here is the result:

Code:

boemien@boemien-VPCEL23FD:~$ sudo xzcat /home/boemien/Téléchargements/jessie.dd.xz > /dev/mmcblk0

bash: /dev/mmcblk0: Permission non accordée

Quote:

Originally Posted by caveman (Post 1428907)

Please be aware that this image is not ready for end-users ;-)

Yeah, I know!!! :D

Boemien

2014-06-09 21:31

Re: debian jessie image for N900

it seems to work without the " > " but there is nothing on the card!!!!

Code:

# Note: nfsnobdy is 4294967294 on 64-bit platforms (-2)

wicket

2014-06-09 21:58

Re: debian jessie image for N900

Quote:

Originally Posted by Boemien (Post 1428878)

Wow, i think that i missed something!!!

the first command i typed was

Code:

xzcat jessie.dd.xz /dev/mmcblk0

without the " > ".

now when I type

Code:

xzcat jessie.dd.xz > /dev/mmcblk0

the result is:

Code:

boemien@boemien-VPCEL23FD:~$ xzcat jessie.dd.xz > /dev/mmcblk0

bash: /dev/mmcblk0: Permission non accordée

boemien@boemien-VPCEL23FD:~$ sudo xzcat jessie.dd.xz > /dev/mmcblk0

bash: /dev/mmcblk0: Permission non accordée

boemien@boemien-VPCEL23FD:~$

same result with:

Code:

boemien@boemien-VPCEL23FD:~$ xzcat /home/boemien/Téléchargements/jessie.dd.xz > /dev/mmcblk0

bash: /dev/mmcblk0: Permission non accordée

boemien@boemien-VPCEL23FD:~$

:confused:

What is the right command?

PS: Permission non accordée means Permission Denied. :D

sudo doesn't work very well with console redirection. Any of the following should work:

Code:

$ sudo sh -c "xzcat jessie.dd.xz > /dev/mmcblk0"

Code:

$ sudo su

# xzcat jessie.dd.xz > /dev/mmcblk0

Code:

$ xzcat jessie.dd.xz | sudo dd of=/dev/mmcblk0 bs=1M

[EDIT]
Note: If you're running this on a PC /dev/mmcblk0 is not likely to be the name of the SD card device node. You can find out what name has been assigned using dmesg or fdisk.
[/EDIT]

Boemien

2014-06-09 22:35

Re: debian jessie image for N900

Thanks.

Typing dmesg, i can see that the device is mmcblk0

I typed

Code:

boemien@boemien-VPCEL23FD:~$ sudo su

[sudo] password for boemien: 

root@boemien-VPCEL23FD:/home/boemien# xzcat /home/boemien/Téléchargements/jessie.dd.xz > /dev/mmcblk0

root@boemien-VPCEL23FD:/home/boemien#

The files has been copied to the card. When i plug it, I see two partition on it : Boot and System.

I will follow the steps to update the bootmenu and see if it works.
Thanks in advance :-)

Boemien

2014-06-09 22:45

Re: debian jessie image for N900

Okay, everything seems to work. I have Unable to read file /boot/uIntrd **

I will try to copy them from first partition to boot folder on the second!!!

EDIT: Okay!! It seems to boot now. The solution was said here:

Quote:

Originally Posted by sakrabojski (Post 1427708)

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

Thanks Guys for your help. I'M going to play a bit with!!!! :D

AapoRantalainen

2014-06-14 17:31

Re: debian jessie image for N900

cordia:
https://github.com/Cordia

Quote:

The project's primary mission is that we make Hildon Desktop installable on MeeGo with all the goodies it has on Maemo.

Talk: (50pages about running hildon-desktop on meego) http://talk.maemo.org/showthread.php?t=56822

There are plenty of git-repositories and I managed to build hildon-desktop top of GTK3 (it had some gtk2 functions left but I dropped them).

I got it running, but it is not looking anything yet.

I'm planning to push source level instructions and deb-packages, but I will double check them first and maybe I want some real milestone achieved also.

Short summary of building-order and origin of sources:
M=maemo5 (apt-get source)
C=cordia (git)
J=jessie (apt-get source)
S=squeezie (dget)

cairo [J] (need tuning for dependencies, or it uninstall mesa-GL)

hildon-libs-l10n-public [M]
osso-system-lock-l10n-public [M]
hildon-fm-l10n-public [M]
hildon-icons [S]
hildon-theme-plankton [S] (deb is not installable, but copy directory to right place)

clutter [C] (against GL, not GLES)

libhildon-1 [C] (gtk3)

(do not use libosso-gnomevfs2-dev but libgnomevfs2-dev)

libdsme [M]
libiphb [MEEGO] (was liberated for harmattan)
libhildondesktop [C]

libmatchbox2 [C] (against clutter-0.8, not 1.0)

libhildonmime-dev [M]

libhildondesktop1 [C]

hildondesktop [C] (without maemo-launcher)

*
(It seems to me that) hildon-desktop acts as a window manager and Matchbox2 is statically compiled inside hildon-desktop.
-there are no matchbox -process running on maemo
-hildon-desktop should be very next to start after X

Starting:
On device, as root, start X (command is 'X', not startx)
And then over ssh, as user, run hildon-desktop

I'm not sure what is next package, maybe hildon-home?

Here is some selection of log when hildon-desktop is started:

Code:

** (hildon-desktop:2378): WARNING **: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files



** (./hildon-desktop:2378): CRITICAL **: SelectionColor: unknown color



(./hildon-desktop:2378): GLib-GObject-WARNING **: /build/glib2.0-ioZeJ5/glib2.0-2.40.0/./gobject/gsignal.c:2462: signal 'key-pressed-event' is invalid for instance '0x2d3138' of type 'HdLauncher'



** (./hildon-desktop:2378): WARNING **: Error loading cached background image /home/user/.backgrounds/background-1.pvr. Failed to open file '/home/user/.backgrounds/background-1.pvr': No such file or directory



** (./hildon-desktop:2378): WARNING **: hd_launcher_tile_set_icon_name: couldn't find icon tasklaunch_default_application

---------------
qildon:
https://gitorious.org/qildon

Quote:

Qildon is a set of Qt Widgets to work together with Hildon Desktop without dependencies on Hildon or Gtk+

I tried to compile it (gtk2-dev not-installed) but compile aborted because of missing gtk2. a) I failed to configure it correctly OR b) it is depending on GTK.

I'm waiting more info about this until I continue. (Is somebody ever got this compiled and running on any system? How ready it is?)
---------------
bme:
Closed source on fremantle, liberated for harmattan. Sources:
bme-rx-51 https://gitorious.org/rx51-bme-replacement/bme-rx-51
hald-addon-bme https://gitorious.org/rx51-bme-repla...hald-addon-bme
libbmeipc0 https://gitorious.org/rx51-bme-replacement/libbmeipc

And some more: https://gitorious.org/rx51-bme-replacement

These depends on libhal, which is not anymore on jessie. Maybe version from squeeze is better than wheezy or fremantle.Got it build, but not yet tested installation.
---------------
mce:
From harmattan.

I quickly check that is has some tough dependency (I don't yet know where to get)
osso-systemui-modechange-dev
libdevlock-dev
osso-systemui-devlock-dev
osso-systemui-splashscreen-dev
libcal-dev (binary version from this can be installed from NOKIA-binaries)

It also needs hald-addon-bme-dev (from meego), not yet tested.

Android_808

2014-06-14 22:43

Re: debian jessie image for N900

great news aapo but i have a couple of questions.

is hal really necessary though? if we (maemo5) are only using it to automount hotplugged devices, udev+udisks would be sufficient. to use old software maybe but are you risking recreating the whole fork/cross version situation we have already.

bme/mce: are those links the same as the replacements were using/got available on maemo5? i thought ours were RE'd.

misiak

2014-06-14 22:51

Re: debian jessie image for N900

Quote:

Originally Posted by Android_808 (Post 1429619)

Really? I thought it was used for more stuff... Is it really only used for automounting hotplugged devices? If so, this looks like a massive overkill...

Quote:

Originally Posted by Android_808 (Post 1429619)

bme/mce: are those links the same as the replacements were using/got available on maemo5? i thought ours were RE'd.

One of the links Aapo wrote (bme-rx-51 one) is the replacement availabe on Maemo5 via cssu(-devel?). AFAIK the replacement was heavily based on the Harmattan open-source version, but you are right that some parts indeed had to be reverse engineered (however, unless my memories are wrong, these were only some parts of it, not the whole bme/mce...).

EDIT:

Quote:

Originally Posted by AapoRantalainen (Post 1429604)

I quickly check that is has some tough dependency (I don't yet know where to get)
osso-systemui-modechange-dev
libdevlock-dev
osso-systemui-devlock-dev
osso-systemui-splashscreen-dev
libcal-dev (binary version from this can be installed from NOKIA-binaries)

I'm not sure about the other ones, but I think dropping osso-systemui-splashscreen-dev as a dependency should be safe... The package osso-systemui-splashscreen only displays Nokia logo when phone is shutting down :D (see file /etc/event.replace.d/osso-systemui-splashscreen - it starts splash display on stopping of dbus or dbus-actdead services) Even if the /usr/lib/systemui/libystemuiplugin_splashscreen.so file in that package needs to provide some functionality, my guess is it should be safe to make a dummy .so file which does nothing (but again, this is software we're talking, so some dumb design flaw may have caused this file to do something important...).

EDIT2:
By the way, Aapo, have you read this thread: http://talk.maemo.org/showthread.php?t=82641 ? I don't want to sound like a douche telling you what to do, but it could be a nice idea to drop all the unneded packages at first stages of your project and not spend too much time on trying to get them working (this is just an idea to consider).

EDIT3:
I have used this link a million times, but maybe I will post it once again, maybe it will be usefull (a.d. your note about using libclutter in specific version): http://linuxtesting.org/compatibilit...at_report.html - it can help detecting which versions of software can be easily used in newer versions (e.g. from Jessie). See e.g. list of possible incompatibilities with newer versions of libc, libexif, libexempi, libglib... libncurses - funny thing is this one is supposed to be in the same version in Fremantle and Harmattan, but they are incompatible somehow... Also, when some libraries reach 1.x state, they sometimes change name in debian (e.g. ssl 0.9.8 is "libssl" and 1.0 is "libssl1" - this is the example that came to my head instantly when you wrote about clutter). I remember seeing (I think on the same server) a comparison of base-system packages compatibility between different version of Debian... that could also be useful here (so you could compare compatibility and then make a decision from which source you would like to build packages for this Jessie-based Maemo).

Android_808

2014-06-15 07:22

Re: debian jessie image for N900

hal: may do more on maemo, i used it as an example really. my laptop doesn't have it, just relies on udisks, upower, rfkill and so on.

clutter: does using gl instead of gles make much difference in terms of performance? if we can build against a newer version even better.

finally, does anyone have instructions for setting up a build environment for this via vbox or scratchbox?

All times are GMT. The time now is 02:05.

Page 2 of 4

< Prev

Next >

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

vBulletin® Version 3.8.8