Active Topics
-
The N900 is now 15 years old! (7)
to Nokia N900 by Danct12 - 1 day ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 1 day, 19 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 4 days, 4 hrs ago - more...
| The Following User Says Thank You to kingoddball For This Useful Post: | ||
 |
|
2011-03-07
, 22:33
|
|
Moderator |
Posts: 2,622 |
Thanked: 5,447 times |
Joined on Jan 2010
|
#12
|
That item file you made was also for BootMenu, not multiboot (check your source)
Why are you putting a kernel there??
Code:
cp -a /lib/modules/2.6.28-omap1/ /mnt/debian/lib/modules/
Anyway I flashed now and multiboot is out of here so when I manage to make a uboot + power46wl I will try with the debian kernel.
Last edited by qwazix; 2013-06-25 at 19:01.
|
|
2011-04-03
, 11:32
|
|
Moderator |
Posts: 2,622 |
Thanked: 5,447 times |
Joined on Jan 2010
|
#13
|
I have been trying to boot a full debian system off the N900. After unsuccessfully trying to boot with multiboot and maemo kernel I decided to give uboot and 2.6.35 from shr a try. So:
1. I unpacked shr from here http://build.shr-project.org/shr-uns...ages/nokia900/ on my microsd
2. Got uboot from here and loaded it (didn't flash - because I have power46wl1 and the image there is normal maemo kerner - tried to combine power46wl with u-boot and failed)
3. Booted into shr, touchscreen and screen backlight worked fine, didn't try anything else.
4. Cleaned up the sd, unpacked the image found here and copied the boot folder from shr image.
5. booted ok into console, without backlight, I managed to read some errors (modules.dep not found etc) just as they passed by real quick
6. copied the /lib/modules/ folder over from shr and now those errors are gone, but still no backlight. When I try ifconfig wlan0 up the system responds with 'could not find firmware' but I checked and the firmwares from maemo are already in /lib/firmware on the sd
7. Installed lxde via chroot from maemo and booted again. Now I get into X but the device becomes non responsive. No touchscreen and surprisingly no keyboard. The cursor is a watch if I boot directly into lxde, while if I boot to the console, and startx the cursor is normal but still no response at all.
8. Tried the other kernel uImage-2.6.28.10power-omap1 in the shr image but this does not boot at all: after the 'loading kernel' label in uboot screen the device restarts and goes into the nokia logo.
I don't know what else to do, I am not very experienced with combining different things to make a linux distribution but I think I am near the solution. (we know that basic things work - touchscreen, wifi, keyboard, backlight) so there must be a way to make them work on debian. Any ideas appreciated.
Last edited by qwazix; 2013-06-25 at 18:59.
1. I unpacked shr from here http://build.shr-project.org/shr-uns...ages/nokia900/ on my microsd
2. Got uboot from here and loaded it (didn't flash - because I have power46wl1 and the image there is normal maemo kerner - tried to combine power46wl with u-boot and failed)
3. Booted into shr, touchscreen and screen backlight worked fine, didn't try anything else.
4. Cleaned up the sd, unpacked the image found here and copied the boot folder from shr image.
5. booted ok into console, without backlight, I managed to read some errors (modules.dep not found etc) just as they passed by real quick
6. copied the /lib/modules/ folder over from shr and now those errors are gone, but still no backlight. When I try ifconfig wlan0 up the system responds with 'could not find firmware' but I checked and the firmwares from maemo are already in /lib/firmware on the sd
7. Installed lxde via chroot from maemo and booted again. Now I get into X but the device becomes non responsive. No touchscreen and surprisingly no keyboard. The cursor is a watch if I boot directly into lxde, while if I boot to the console, and startx the cursor is normal but still no response at all.
8. Tried the other kernel uImage-2.6.28.10power-omap1 in the shr image but this does not boot at all: after the 'loading kernel' label in uboot screen the device restarts and goes into the nokia logo.
I don't know what else to do, I am not very experienced with combining different things to make a linux distribution but I think I am near the solution. (we know that basic things work - touchscreen, wifi, keyboard, backlight) so there must be a way to make them work on debian. Any ideas appreciated.
Last edited by qwazix; 2013-06-25 at 18:59.
|
|
2013-06-25
, 16:13
|
|
Posts: 191 |
Thanked: 415 times |
Joined on Jan 2012
|
#14
|
I have debian wheezy running on the N900. I will document the procedure in this post. Corrections and suggestions for further details and/or discussions are welcome.
All the information here comes from the following sources:
* http://wiki.debian.org/pkg-n900 and its references
* the ubuntu thread http://talk.maemo.org/showthread.php?t=82819
* the arch linux thread http://talk.maemo.org/showthread.php?t=81892
These instructions are to be run from the N900. It is not necessary to use the PC (although possible; check the refs).
Disclaimer: only try this if you are comfortable with the cli and willing to risk a reflash.
Choose installation target
Choose a partition to install debian. I have tried both the uSD and the eMMC. In this post I will assume the installation target is the uSD.
Create a partition of the desired size and type. If you are not familiar with command line tools to create partitions, stop now ;-)
Create a filesystem on the partition. In my case I used ext4, but notice that ext4 requires the power kernel.
Install basic system
Install debootstrap directly from debian repository:
http://packages.debian.org/wheezy/al...strap/download
and install it with dpkg:
Mount the target partition:
and install the basic system:
chroot and continue the installation
After the first phase of the installation is completed, chroot to our new system:
Once inside, continue the installation:
Adjust the package list to your liking.
In the arch linux thread referenced above, Skry et al. have developed a very nice keyboard configuration. I strongly suggest it is used:
Do not forget to set root password:
For a graphical environment one may install xorg, lxde, awesome or e17 (from jessie).
My touchscreen required a bit of configuration:
When done, leave the chroot.
kernel
I have tried 4 kernels:
* pali's linux-n900 versions 3.8-rc3 and 3.9 (hand-compiled);
* debian linux-image-omap
* nemo's kernel
In all cases the corresponding modules and firmware must be installed to the target system.
Best results were obtained with the kernel from nemo. Both compiled kernels failed to boot and reset the device after a few seconds. I have not yet investigated further.
The debian omap kernel fails to bootstrap my system as well.
With the kernel from nemo the system fully boots and is functional with wifi and e17/X.
kernel notes
Nemo kernel and images are here
The debian kernel can be installed with
Pali's kernels were compiled in x86 debian box using a cross-compiler. The procedure is as follows:
1. add emdebian repo to apt config: deb http://www.emdebian.org/debian wheezy main
2. install emdebian gcc 4.7 cross compiler
3. add one alternative to the cross compiler using update-alternatives
4. clone pali's repository from https://gitorious.org/linux-n900/linux-n900
5. build with
6. place kernel and modules in /boot and /lib/modules, respectively.
7. I have not changed the default kernel config and I am no kernel expert, and possibly some config changes will be enough for a successful boot (if you know better, please share)
u-boot
To finally boot into debian, we have to configure u-boot. Notice that some versions of u-boot seem to have problems booting 3.x kernels. I believe latest version in extras-devel has fixed this.
I have tried 4 variations, one for each kernel. In all cases the kernels and initrd have been placed inside maemo's /opt/boot as zimages.
Personal considerations
1. the boot takes much longer that arch linux in the same device, but boot times are comparable to maemo
2. debian has a packaged ofono, but I have not yet investigated further
3. once booted, the system feels stable and functional
Last edited by caveman; 2013-06-25 at 20:22. Reason: update X information
All the information here comes from the following sources:
* http://wiki.debian.org/pkg-n900 and its references
* the ubuntu thread http://talk.maemo.org/showthread.php?t=82819
* the arch linux thread http://talk.maemo.org/showthread.php?t=81892
These instructions are to be run from the N900. It is not necessary to use the PC (although possible; check the refs).
Disclaimer: only try this if you are comfortable with the cli and willing to risk a reflash.
Choose installation target
Choose a partition to install debian. I have tried both the uSD and the eMMC. In this post I will assume the installation target is the uSD.
Create a partition of the desired size and type. If you are not familiar with command line tools to create partitions, stop now ;-)
Create a filesystem on the partition. In my case I used ext4, but notice that ext4 requires the power kernel.
Install basic system
Install debootstrap directly from debian repository:
http://packages.debian.org/wheezy/al...strap/download
and install it with dpkg:
Code:
wget http://ftp.us.debian.org/debian/pool/main/d/debootstrap/debootstrap_1.0.48+deb7u1_all.deb dpkg -i debootstrap_1.0.48+deb7u1_all.deb
Code:
mount -t ext4 /dev/mmcblk1p1 /mnt
Code:
debootstrap --arch=armhf --variant=minbase wheezy /mnt http://ftp.br.debian.org/debian
After the first phase of the installation is completed, chroot to our new system:
Code:
for i in dev proc sys; do mount -o bind /$i /mnt/$i; done chroot /mnt bash -l
Code:
echo N900 > /etc/hostname echo "nameserver 8.8.8.8" > /etc/resolv.conf cat << EOF > /etc/network/interfaces auto lo iface lo inet loopback allow-hotplug wlan0 iface wlan0 inet dhcp EOF cat << EOF > /etc/default/keyboard: XKBMODEL="nokiarx51" XKBLAYOUT="us" EOF echo "deb http://ftp.us.debian.org/debian/ wheezy main contrib non-free" > etc/apt/sources.list.d/wheezy.list echo "deb http://security.debian.org/ wheezy/updates main contrib non-free" >> etc/apt/sources.list.d/wheezy.list apt-get update apt-get install ssh wicd wicd-curses wireless-tools wget keyboard-configuration
In the arch linux thread referenced above, Skry et al. have developed a very nice keyboard configuration. I strongly suggest it is used:
Code:
mkdir -p /usr/share/keymaps dpkg-reconfigure keyboard-configuration # get keyboard maps wget --no-check-certificate -O /usr/share/keymaps/rx51_us.map https://raw.github.com/archlinuxarm-n900/n900-keymaps/master/rx51_us.map loadkeys /usr/share/keymaps/rx51_us.map
Code:
passwd
My touchscreen required a bit of configuration:
Code:
n900:~# cat /etc/X11/xorg.conf.d/99-calibration.conf
Section "InputClass"
Identifier "Calibration"
MatchIsTouchscreen "on"
Option "Calibration" "194 3901 3739 241"
EndSection
kernel
I have tried 4 kernels:
* pali's linux-n900 versions 3.8-rc3 and 3.9 (hand-compiled);
* debian linux-image-omap
* nemo's kernel
In all cases the corresponding modules and firmware must be installed to the target system.
Best results were obtained with the kernel from nemo. Both compiled kernels failed to boot and reset the device after a few seconds. I have not yet investigated further.
The debian omap kernel fails to bootstrap my system as well.
With the kernel from nemo the system fully boots and is functional with wifi and e17/X.
kernel notes
Nemo kernel and images are here
The debian kernel can be installed with
Code:
apt-get install linux-image-omap
1. add emdebian repo to apt config: deb http://www.emdebian.org/debian wheezy main
2. install emdebian gcc 4.7 cross compiler
3. add one alternative to the cross compiler using update-alternatives
4. clone pali's repository from https://gitorious.org/linux-n900/linux-n900
Code:
git clone git://gitorious.org/linux-n900/linux-n900.git git checkout v3.9
Code:
ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- make rx51_defconfig ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- make -j 2 INSTALL_MOD_PATH=../linux/ ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- make modules_install
7. I have not changed the default kernel config and I am no kernel expert, and possibly some config changes will be enough for a successful boot (if you know better, please share)
u-boot
To finally boot into debian, we have to configure u-boot. Notice that some versions of u-boot seem to have problems booting 3.x kernels. I believe latest version in extras-devel has fixed this.
I have tried 4 variations, one for each kernel. In all cases the kernels and initrd have been placed inside maemo's /opt/boot as zimages.
Code:
ITEM_NAME="Debian Wheezy nemo kernel"
ITEM_KERNEL="uImage"
ITEM_DEVICE="${EXT_CARD}p1"
ITEM_FSTYPE="vfat"
ITEM_OMAPATAG="1"
ITEM_CMDLINE="root=/dev/mmcblk0p3 rootwait vram=12M console=tty0"
ITEM_NAME="Debian Wheezy omap kernel"
ITEM_KERNEL="vmlinuz-3.2.0-4-omap"
ITEM_INITRD="initrd.img-3.2.0-4-omap"
ITEM_OMAPATAG="1"
ITEM_CMDLINE="root=UUID=XXXXXXX vram=12M console=tty0"
ITEM_NAME="Debian Wheezy kernel v3.8-rc3"
ITEM_KERNEL="linux-n900-3.8-rc3"
ITEM_INITRD="initrd.img-3.8.0-rc3+"
ITEM_OMAPATAG="1"
ITEM_CMDLINE="root=UUID=XXXXXXX vram=12M console=tty0"
ITEM_NAME="Debian Wheezy kernel v3.9"
ITEM_KERNEL="linux-n900-3.9"
ITEM_INITRD="initrd.img-3.9.0+"
ITEM_OMAPATAG="1"
ITEM_CMDLINE="root=UUID=XXXXXXX vram=12M console=tty0"
1. the boot takes much longer that arch linux in the same device, but boot times are comparable to maemo
2. debian has a packaged ofono, but I have not yet investigated further
3. once booted, the system feels stable and functional
Last edited by caveman; 2013-06-25 at 20:22. Reason: update X information
| The Following 18 Users Say Thank You to caveman For This Useful Post: | ||
|
|
2013-06-25
, 18:38
|
|
Posts: 191 |
Thanked: 415 times |
Joined on Jan 2012
|
#15
|
So how does armel (maemo) compare to armhf (wheezy)? Some basic tests:
openssl speed sha512
armel:
openssl speed rsa1024
armel:
armhf:
openssl speed sha512
armel:
Code:
type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes sha512 465.80k 1959.38k 2816.85k 3900.45k 4417.63k
Code:
armhf: type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes sha512 388.15k 1645.95k 2334.09k 3195.16k 3578.92k
armel:
Code:
sign verify sign/s verify/s rsa 1024 bits 0.022798s 0.001074s 43.9 930.7
Code:
sign verify sign/s verify/s rsa 1024 bits 0.020597s 0.001000s 48.6 999.7
| The Following 5 Users Say Thank You to caveman For This Useful Post: | ||
|
|
2013-06-25
, 19:43
|
|
Community Council |
Posts: 685 |
Thanked: 1,235 times |
Joined on Sep 2010
@ Mbabane
|
#16
|
the debian kernel will not work because debian does not accept patches from 'obscure' sources :P
however, I did get it to boot to some extent (ended up with an oops somewhere) Basically, you need to prepare an initrd with the important modules.
as for ofono, it works ok with nemo's kernel. i could use 3G/GPRS, as well as receive SMS.
i found xfce to suit my needs. better than the other DEs/WMs.
however, I did get it to boot to some extent (ended up with an oops somewhere) Basically, you need to prepare an initrd with the important modules.
as for ofono, it works ok with nemo's kernel. i could use 3G/GPRS, as well as receive SMS.
i found xfce to suit my needs. better than the other DEs/WMs.
| The Following User Says Thank You to sicelo For This Useful Post: | ||
|
|
2013-06-25
, 20:24
|
|
Posts: 191 |
Thanked: 415 times |
Joined on Jan 2012
|
#17
|
Originally Posted by qhubekela
How are you dealing with battery charging with the nemo kernel? Manually running the script?
the debian kernel will not work because debian does not accept patches from 'obscure' sources :P
however, I did get it to boot to some extent (ended up with an oops somewhere) Basically, you need to prepare an initrd with the important modules.
|
|
2013-06-25
, 20:55
|
|
Community Council |
Posts: 685 |
Thanked: 1,235 times |
Joined on Sep 2010
@ Mbabane
|
#18
|
Yes, I was running the script manually. i think Pali's kernel auto-detects, but I never tried it.
|
|
2013-06-25
, 20:58
|
|
Community Council |
Posts: 685 |
Thanked: 1,235 times |
Joined on Sep 2010
@ Mbabane
|
#19
|
BTW, another kernel you can try is Skry's, from his alarm project. I had a few problems booting the uImage, but after extracting the zImage from it, I could use it successfully.
| The Following User Says Thank You to sicelo For This Useful Post: | ||
|
|
2013-08-11
, 06:58
|
|
Posts: 34 |
Thanked: 66 times |
Joined on Jul 2010
|
#20
|
Originally Posted by qhubekela
How did you do this? Did you have to build the ofono sources?
as for ofono, it works ok with nemo's kernel. i could use 3G/GPRS, as well as receive SMS.
I'm trying to use ofono from apt-get on wheezy.
I have phonet0 showing in ifconfig -a
and /dev/cmt in filesystem.
ofono -d -n gives:
Code:
ofonod -d -n ofonod[2849]: oFono version 1.6 ofonod[2849]: src/plugin.c:__ofono_plugin_init() ofonod[2849]: plugins/push-notification.c:push_notification_init() ofonod[2849]: plugins/smart-messaging.c:smart_messaging_init() ofonod[2849]: src/cdma-provision.c:ofono_cdma_provision_driver_register() driver: 0xb61cc name: CDMA provisioning ofonod[2849]: src/gprs-provision.c:ofono_gprs_provision_driver_register() driver: 0xb61a0 name: Provisioning ofonod[2849]: plugins/connman.c:connman_init() ofonod[2849]: src/private-network.c:ofono_private_network_driver_register() driver: 0xb6174, name: ConnMan Private Network ofonod[2849]: plugins/dun_gw.c:dun_gw_init() ofonod[2849]: src/modem.c:ofono_modem_driver_register() driver: 0xb6094, name: hfp ofonod[2849]: src/modem.c:ofono_modem_driver_register() driver: 0xb603c, name: sap ofonod[2849]: src/modem.c:ofono_modem_driver_register() driver: 0xb5fc8, name: telit ofonod[2849]: src/modem.c:ofono_modem_driver_register() driver: 0xb5f5c, name: sim900 ofonod[2849]: src/modem.c:ofono_modem_driver_register() driver: 0xb5f14, name: samsung ofonod[2849]: src/modem.c:ofono_modem_driver_register() driver: 0xb5ecc, name: speedupcdma ofonod[2849]: src/modem.c:ofono_modem_driver_register() driver: 0xb5e7c, name: speedup ofonod[2849]: src/modem.c:ofono_modem_driver_register() driver: 0xb5e34, name: alcatel ofonod[2849]: src/modem.c:ofono_modem_driver_register() driver: 0xb5dec, name: icera ofonod[2849]: src/modem.c:ofono_modem_driver_register() driver: 0xb5da4, name: linktop ofonod[2849]: src/modem.c:ofono_modem_driver_register() driver: 0xb5d5c, name: nokiacdma ofonod[2849]: src/modem.c:ofono_modem_driver_register() driver: 0xb5d14, name: nokia ofonod[2849]: src/modem.c:ofono_modem_driver_register() driver: 0xb5ccc, name: tc65 ofonod[2849]: src/modem.c:ofono_modem_driver_register() driver: 0xb5c44, name: ste ofonod[2849]: src/modem.c:ofono_modem_driver_register() driver: 0xb5bec, name: ifx ofonod[2849]: src/modem.c:ofono_modem_driver_register() driver: 0xb5ba4, name: palmpre ofonod[2849]: src/modem.c:ofono_modem_driver_register() driver: 0xb5b54, name: novatel ofonod[2849]: src/modem.c:ofono_modem_driver_register() driver: 0xb5b0c, name: sierra ofonod[2849]: src/modem.c:ofono_modem_driver_register() driver: 0xb5a94, name: huawei ofonod[2849]: src/modem.c:ofono_modem_driver_register() driver: 0xb5a4c, name: zte ofonod[2849]: src/modem.c:ofono_modem_driver_register() driver: 0xb59ec, name: hso ofonod[2849]: src/modem.c:ofono_modem_driver_register() driver: 0xb599c, name: mbm ofonod[2849]: src/modem.c:ofono_modem_driver_register() driver: 0xb594c, name: calypso ofonod[2849]: src/modem.c:ofono_modem_driver_register() driver: 0xb5904, name: wavecom ofonod[2849]: src/modem.c:ofono_modem_driver_register() driver: 0xb58bc, name: gobi ofonod[2849]: src/modem.c:ofono_modem_driver_register() driver: 0xb5874, name: g1 ofonod[2849]: src/cdma-voicecall.c:ofono_cdma_voicecall_driver_register() driver: 0xb581c, name: cdmamodem ofonod[2849]: src/modem.c:ofono_devinfo_driver_register() driver: 0xb5844, name: cdmamodem ofonod[2849]: src/cdma-connman.c:ofono_cdma_connman_driver_register() driver: 0xb5860, name: cdmamodem ofonod[2849]: src/modem.c:ofono_modem_driver_register() driver: 0xb5784, name: phonesim ofonod[2849]: src/modem.c:ofono_modem_driver_register() driver: 0xb57b4, name: localhfp ofonod[2849]: src/gprs.c:ofono_gprs_context_driver_register() driver: 0xb5770, name: phonesim ofonod[2849]: src/ctm.c:ofono_ctm_driver_register() driver: 0xb575c, name: phonesim ofonod[2849]: plugins/phonesim.c:parse_config() filename /etc/ofono/phonesim.conf ofonod[2849]: src/ussd.c:ofono_ussd_driver_register() driver: 0xb5748, name: speedupmodem ofonod[2849]: src/voicecall.c:ofono_voicecall_driver_register() driver: 0xb563c, name: hfpmodem ofonod[2849]: src/modem.c:ofono_devinfo_driver_register() driver: 0xb56e0, name: hfpmodem ofonod[2849]: src/network.c:ofono_netreg_driver_register() driver: 0xb5694, name: hfpmodem ofonod[2849]: src/call-volume.c:ofono_call_volume_driver_register() driver: 0xb56c8, name: hfpmodem ofonod[2849]: src/handsfree.c:ofono_handsfree_driver_register() driver: 0xb570c, name: hfpmodem ofonod[2849]: src/network.c:ofono_netreg_driver_register() driver: 0xb55bc, name: dunmodem ofonod[2849]: src/gprs.c:ofono_gprs_driver_register() driver: 0xb55e0, name: dunmodem ofonod[2849]: src/voicecall.c:ofono_voicecall_driver_register() driver: 0xb54f8, name: stemodem ofonod[2849]: src/gprs.c:ofono_gprs_context_driver_register() driver: 0xb5580, name: stemodem ofonod[2849]: src/radio-settings.c:ofono_radio_settings_driver_register() driver: 0xb5548, name: stemodem ofonod[2849]: src/voicecall.c:ofono_voicecall_driver_register() driver: 0xb53e0, name: ifxmodem ofonod[2849]: src/audio-settings.c:ofono_audio_settings_driver_register() driver: 0xb5438, name: ifxmodem ofonod[2849]: src/radio-settings.c:ofono_radio_settings_driver_register() driver: 0xb544c, name: ifxmodem ofonod[2849]: src/gprs.c:ofono_gprs_context_driver_register() driver: 0xb5480, name: ifxmodem ofonod[2849]: src/stk.c:ofono_stk_driver_register() driver: 0xb54a4, name: ifxmodem ofonod[2849]: src/ctm.c:ofono_ctm_driver_register() driver: 0xb54c4, name: ifxmodem ofonod[2849]: src/gprs.c:ofono_gprs_context_driver_register() driver: 0xb5378, name: hsomodem ofonod[2849]: src/radio-settings.c:ofono_radio_settings_driver_register() driver: 0xb5394, name: hsomodem ofonod[2849]: src/gprs.c:ofono_gprs_context_driver_register() driver: 0xb52fc, name: mbmmodem ofonod[2849]: src/stk.c:ofono_stk_driver_register() driver: 0xb5318, name: mbmmodem ofonod[2849]: src/location-reporting.c:ofono_location_reporting_driver_register() driver: 0xb5338, name: mbmmodem ofonod[2849]: src/voicecall.c:ofono_voicecall_driver_register() driver: 0xb5264, name: calypsomodem ofonod[2849]: src/stk.c:ofono_stk_driver_register() driver: 0xb52b4, name: calypsomodem ofonod[2849]: src/ussd.c:ofono_ussd_driver_register() driver: 0xb5174, name: huaweimodem ofonod[2849]: src/voicecall.c:ofono_voicecall_driver_register() driver: 0xb5188, name: huaweimodem ofonod[2849]: src/audio-settings.c:ofono_audio_settings_driver_register() driver: 0xb51d8, name: huaweimodem ofonod[2849]: src/radio-settings.c:ofono_radio_settings_driver_register() driver: 0xb5208, name: huaweimodem ofonod[2849]: src/gprs.c:ofono_gprs_context_driver_register() driver: 0xb51ec, name: huaweimodem ofonod[2849]: src/cdma-netreg.c:ofono_cdma_netreg_driver_register() driver: 0xb5234, name: huaweimodem ofonod[2849]: src/radio-settings.c:ofono_radio_settings_driver_register() driver: 0xb5128, name: ztemodem ofonod[2849]: src/gprs.c:ofono_gprs_context_driver_register() driver: 0xb50ec, name: swmodem ofonod[2849]: src/radio-settings.c:ofono_radio_settings_driver_register() driver: 0xb50a8, name: nwmodem ofonod[2849]: src/voicecall.c:ofono_voicecall_driver_register() driver: 0xb4f28, name: atmodem ofonod[2849]: src/modem.c:ofono_devinfo_driver_register() driver: 0xb4fc0, name: atmodem ofonod[2849]: src/call-barring.c:ofono_call_barring_driver_register() driver: 0xb4f78, name: atmodem ofonod[2849]: src/call-forwarding.c:ofono_call_forwarding_driver_register() driver: 0xb4d30, name: atmodem ofonod[2849]: src/call-meter.c:ofono_call_meter_driver_register() driver: 0xb4d70, name: atmodem ofonod[2849]: src/call-settings.c:ofono_call_settings_driver_register() driver: 0xb4c7c, name: atmodem ofonod[2849]: src/phonebook.c:ofono_phonebook_driver_register() driver: 0xb4fa8, name: atmodem ofonod[2849]: src/ussd.c:ofono_ussd_driver_register() driver: 0xb4f04, name: atmodem ofonod[2849]: src/sms.c:ofono_sms_driver_register() driver: 0xb4cec, name: atmodem ofonod[2849]: src/sim.c:ofono_sim_driver_register() driver: 0xb4e44, name: atmodem ofonod[2849]: src/sim.c:ofono_sim_driver_register() driver: 0xb4e8c, name: atmodem-noef ofonod[2849]: src/stk.c:ofono_stk_driver_register() driver: 0xb4edc, name: atmodem ofonod[2849]: src/network.c:ofono_netreg_driver_register() driver: 0xb4dcc, name: atmodem ofonod[2849]: src/cbs.c:ofono_cbs_driver_register() driver: 0xb4d14, name: atmodem ofonod[2849]: src/call-volume.c:ofono_call_volume_driver_register() driver: 0xb4fec, name: atmodem ofonod[2849]: src/gprs.c:ofono_gprs_driver_register() driver: 0xb501c, name: atmodem ofonod[2849]: src/gprs.c:ofono_gprs_context_driver_register() driver: 0xb5030, name: atmodem ofonod[2849]: src/sim-auth.c:ofono_sim_auth_driver_register() driver: 0xb504c, name: atmodem ofonod[2849]: src/gnss.c:ofono_gnss_driver_register() driver: 0xb506c, name: atmodem ofonod[2849]: src/modem.c:ofono_modem_driver_register() driver: 0xb4a60, name: u8500 ofonod[2849]: src/modem.c:ofono_devinfo_driver_register() driver: 0xb4a44, name: u8500 ofonod[2849]: src/modem.c:ofono_modem_driver_register() driver: 0xb49fc, name: n900 ofonod[2849]: src/modem.c:ofono_modem_driver_register() driver: 0xb49b4, name: isiusb ofonod[2849]: src/modem.c:ofono_devinfo_driver_register() driver: 0xb476c, name: isimodem ofonod[2849]: src/phonebook.c:ofono_phonebook_driver_register() driver: 0xb475c, name: isimodem ofonod[2849]: src/network.c:ofono_netreg_driver_register() driver: 0xb4788, name: isimodem ofonod[2849]: src/voicecall.c:ofono_voicecall_driver_register() driver: 0xb47ac, name: isimodem ofonod[2849]: src/sms.c:ofono_sms_driver_register() driver: 0xb47f4, name: isimodem ofonod[2849]: src/cbs.c:ofono_cbs_driver_register() driver: 0xb4814, name: isimodem ofonod[2849]: src/sim.c:ofono_sim_driver_register() driver: 0xb4828, name: isimodem ofonod[2849]: src/ussd.c:ofono_ussd_driver_register() driver: 0xb4870, name: isimodem ofonod[2849]: src/call-forwarding.c:ofono_call_forwarding_driver_register() driver: 0xb4884, name: isimodem ofonod[2849]: src/call-settings.c:ofono_call_settings_driver_register() driver: 0xb48a4, name: isimodem ofonod[2849]: src/call-barring.c:ofono_call_barring_driver_register() driver: 0xb48d4, name: isimodem ofonod[2849]: src/call-meter.c:ofono_call_meter_driver_register() driver: 0xb48ec, name: isimodem ofonod[2849]: src/radio-settings.c:ofono_radio_settings_driver_register() driver: 0xb4914, name: isimodem ofonod[2849]: src/gprs.c:ofono_gprs_driver_register() driver: 0xb4938, name: isimodem ofonod[2849]: src/gprs.c:ofono_gprs_context_driver_register() driver: 0xb494c, name: isimodem ofonod[2849]: src/audio-settings.c:ofono_audio_settings_driver_register() driver: 0xb4960, name: isimodem ofonod[2849]: src/sim.c:ofono_sim_driver_register() driver: 0xb496c, name: wgmodem2.5 ofonod[2849]: plugins/udevng.c:udev_start() ofonod[2849]: plugins/udevng.c:enumerate_devices() ofonod[2849]: src/modem.c:ofono_modem_create() name: (null), type: n900 ofonod[2849]: src/modem.c:set_modem_property() modem 0xa10528 property Path ofonod[2849]: plugins/udev.c:add_modem() /devices/platform/omap_ssi.0/ssi0/port0/ssi_protocol/net/phonet0 (n900) ofonod[2849]: plugins/udev.c:add_isi() modem 0xa10528 ofonod[2849]: src/modem.c:get_modem_property() modem 0xa10528 property Interface ofonod[2849]: src/modem.c:set_modem_property() modem 0xa10528 property Address ofonod[2849]: src/modem.c:set_modem_property() modem 0xa10528 property Interface ofonod[2849]: plugins/udev.c:add_isi() interface phonet0 ofonod[2849]: src/modem.c:ofono_modem_register() 0xa10528 ofonod[2849]: src/modem.c:get_modem_property() modem 0xa10528 property Interface ofonod[2849]: src/modem.c:get_modem_property() modem 0xa10528 property Address ofonod[2849]: plugins/n900.c:n900_probe() (0xa10528) with phonet0 ofonod[2849]: plugins/nokia-gpio.c:gpio_probe_links() Using /dev/cmt ofonod[2849]: plugins/nokia-gpio.c:gpio_line_probe() cmt_en: not found ofonod[2849]: plugins/nokia-gpio.c:gpio_line_probe() cmt_rst_rq: not found ofonod[2849]: plugins/nokia-gpio.c:gpio_line_probe() cmt_rst: not found ofonod[2849]: plugins/nokia-gpio.c:gpio_line_probe() cmt_bsi: not found ofonod[2849]: plugins/nokia-gpio.c:gpio_line_probe() cmt_apeslpx: not found ofonod[2849]: plugins/nokia-gpio.c:gpio_probe() Modem control GPIO lines are not available ofonod[2849]: plugins/n900.c:n900_probe() gpio for phonet0: No such device
https://build.merproject.org/package...2713fd4823ccb2
Other problems....
Code:
dbus-send --system --print-reply --dest=org.ofono /isimodem0 org.ofono.Modem.GetProperties Error org.freedesktop.DBus.Error.UnknownObject: Method "GetProperties" with signature "" on interface "org.ofono.Modem" doesn't exist
| The Following User Says Thank You to radiochickenwax For This Useful Post: | ||
Try boot your Debian using M-AG's Ubuntu Kernel if this debian won't work. SHOULD do the trick to at least get a boot.
As for Multiboot.
Just use ANY xxx.item file and just test with any kernel.
Please post up all the steps you have done so far.
Guru Meditation is because it can not find a kernel.
Make you file*.item in /etc/multiboot
Edit:
Looking over your messages again...
It does not matter what Maemo PR you are on.
Place the debian kernel you are using in /boot/multiboot
and name is as vmlinuz-2.6.28*blahblah
I have done a few things like this when bored, I will help.
But really, try MAG's Ubuntu kernel first, or even possible try:
take all NITDroid files from partition two (SAVE THESE!) and extract the Debian tarball into P2 and try boot (using droid kernel) see what happens!
Mini Edit: That item file you made was also for BootMenu, not multiboot
The thanks button? Sure! You can press it!
Last edited by kingoddball; 2011-03-07 at 20:33.