Devuan on N900 - Revision history

enrico_menotti: Typo

enrico_menotti — Wed, 10 May 2017 17:21:29 GMT

Typo

← Older revision		Revision as of 17:21, 10 May 2017
Line 155:		Line 155:
	(if suggested by the system, also <code> apt-get autoremove </code>).		(if suggested by the system, also <code> apt-get autoremove </code>).

-	To supply for the missing udev at boot and mount the <code> /dev </code> nodes anyway, we need to modify the <code> /etc/init.d/mountkernfs.h </code> script (remember we are in the chroot jail, so the leading / is correct). Add the following lines:	+	To supply for the missing udev at boot and mount the <code> /dev </code> nodes anyway, we need to modify the <code> /etc/init.d/mountkernfs.sh </code> script (remember we are in the chroot jail, so the leading / is correct). Add the following lines:

	#		#

enrico_menotti: Minor typesetting

enrico_menotti — Sat, 06 May 2017 21:04:42 GMT

Minor typesetting

← Older revision		Revision as of 21:04, 6 May 2017
Line 15:		Line 15:
	cd ../linux-4.10.8		cd ../linux-4.10.8

-	I used Pali’s [https://github.com/pali/linux-n900/blob/v4.6-rc1-n900/arch/arm/configs/rx51_defconfig] as a configuration file:	+	I used Pali’s <code> rx51_defconfig </code> <ref> https://github.com/pali/linux-n900/blob/v4.6-rc1-n900/arch/arm/configs/rx51_defconfig </ref> as a configuration file:

	curl -o arch/arm/configs https://raw.githubusercontent.com/pali/linux-n900/v4.6-rc1-n900/arch/arm/configs/rx51_defconfig		curl -o arch/arm/configs https://raw.githubusercontent.com/pali/linux-n900/v4.6-rc1-n900/arch/arm/configs/rx51_defconfig
Line 43:		Line 43:


-	Now we may compile the kernel<ref> http://elinux.org/N900 </ref>. Let’s first cd back to the <code> linux-4.10.8 </code> directory. Then select the desired target architecture and cross-toolchain:	+	Now we may compile the kernel <ref> http://elinux.org/N900 </ref>. Let’s first cd back to the <code> linux-4.10.8 </code> directory. Then select the desired target architecture and cross-toolchain:

	export ARCH=arm		export ARCH=arm
Line 52:		Line 52:
	make rx51_defconfig		make rx51_defconfig

-	At this point it is wise to hack a bit the kernel configuration by setting the two watchdogs (OMAP and TWL4030) to be included into the kernel itself and not separated as loadable modules<ref> Actually the system may boot also with the watchdogs in the modules, but in this case it is very unstable: to avoid reboot, the watchdogs need to be loaded in a few seconds, which may not be possible in some cases (namely, I had a problem due to udev waiting for the loopback lo device to be mounted, which did not happen due to the lack of an initrd). </ref>. This is done by calling	+	At this point it is wise to hack a bit the kernel configuration by setting the two watchdogs (OMAP and TWL4030) to be included into the kernel itself and not separated as loadable modules <ref> Actually the system may boot also with the watchdogs in the modules, but in this case it is very unstable: to avoid reboot, the watchdogs need to be loaded in a few seconds, which may not be possible in some cases (namely, I had a problem due to udev waiting for the loopback lo device to be mounted, which did not happen due to the lack of an initrd). </ref>. This is done by calling

	make menuconfig		make menuconfig
Line 84:		Line 84:
	== Devuan file system ==		== Devuan file system ==

-	For the following steps it is essential to be root on a Devuan system<ref> https://wiki.debian.org/EmDebian/CrossDebootstrap </ref>. Let’s install some packages:	+	For the following steps it is essential to be root on a Devuan system <ref> https://wiki.debian.org/EmDebian/CrossDebootstrap </ref>. Let’s install some packages:

	apt-get install binfmt-support qemu qemu-user-static debootstrap		apt-get install binfmt-support qemu qemu-user-static debootstrap
Line 138:		Line 138:
	Pin-Priority: -1		Pin-Priority: -1

-	Now, in order to perform our customisation, we have to chroot again. To this aim, we first mount the <code> /proc </code> file system of the host to the <code> n900 </code> directory, and tell the system to install packages without starting their associated services. So let’s create <code> usr/sbin/policy-rc.d </code> with<ref> https://serverfault.com/questions/567474/how-can-i-install-packages-without-starting-their-associated-services </ref>:	+	Now, in order to perform our customisation, we have to chroot again. To this aim, we first mount the <code> /proc </code> file system of the host to the <code> n900 </code> directory, and tell the system to install packages without starting their associated services. So let’s create <code> usr/sbin/policy-rc.d </code> with <ref> https://serverfault.com/questions/567474/how-can-i-install-packages-without-starting-their-associated-services </ref>:

	#!/bin/sh		#!/bin/sh
Line 217:		Line 217:
	WARNING: ckbcomp reads <code> /etc/default/keyboard </code>, and then files in <code> /usr/share/X11/xkb/ </code>. The first file to be read is <code> rules/xorg </code>, which specifies other files to be read for the keyboard model and layout specified in <code> /etc/default/keyboard </code>. Based on the rules, files are read in <code> geometry/, keycodes/ </code> and <code> symbols/ </code>. At present (and probably also in the future) ckbcomp does not read files in <code> types/ </code>: the types for modifier keys are hardcoded in ckbcomp itself. As a consequence, there is a particular issue: the version of ckbcomp included in Jessie does not know about <code> PC_FN_LEVEL2 </code>, a type which allows on some keyboard layouts (e.g. Italian and German) to switch from left/right to up/down arrows by pressing (and holding) the function (blue) key. This results in a warning, and the arrow switch is instead obtained by means of shift. To correct the behaviour, I installed console-setup version 1.164 (from Debian sid), or rather installed it on Debian and copied <code> /usr/bin/ckbcomp </code> to the Devuan file system.		WARNING: ckbcomp reads <code> /etc/default/keyboard </code>, and then files in <code> /usr/share/X11/xkb/ </code>. The first file to be read is <code> rules/xorg </code>, which specifies other files to be read for the keyboard model and layout specified in <code> /etc/default/keyboard </code>. Based on the rules, files are read in <code> geometry/, keycodes/ </code> and <code> symbols/ </code>. At present (and probably also in the future) ckbcomp does not read files in <code> types/ </code>: the types for modifier keys are hardcoded in ckbcomp itself. As a consequence, there is a particular issue: the version of ckbcomp included in Jessie does not know about <code> PC_FN_LEVEL2 </code>, a type which allows on some keyboard layouts (e.g. Italian and German) to switch from left/right to up/down arrows by pressing (and holding) the function (blue) key. This results in a warning, and the arrow switch is instead obtained by means of shift. To correct the behaviour, I installed console-setup version 1.164 (from Debian sid), or rather installed it on Debian and copied <code> /usr/bin/ckbcomp </code> to the Devuan file system.

-	If one wants to customise the keyboard, the layout is defined in <code> symbols/nokia_vndr/rx-51 </code>; edit the file<ref> https://wiki.maemo.org/Remapping_keyboard </ref> and run again <code> dpkg-reconfigure console-setup </code>.	+	If one wants to customise the keyboard, the layout is defined in <code> symbols/nokia_vndr/rx-51 </code>; edit the file <ref> https://wiki.maemo.org/Remapping_keyboard </ref> and run again <code> dpkg-reconfigure console-setup </code>.

	In order to have a working power button for shutdown, we need:		In order to have a working power button for shutdown, we need:
Line 247:		Line 247:
	wl1251_spi		wl1251_spi

-	to <code> /etc/modules </code>. At this point the wifi interface should be ready. In order to connect to my wlan, I also set up the wpa-psk protocol<ref> https://wiki.debian.org/WiFi/HowToUse </ref>. This requires:	+	to <code> /etc/modules </code>. At this point the wifi interface should be ready. In order to connect to my wlan, I also set up the wpa-psk protocol <ref> https://wiki.debian.org/WiFi/HowToUse </ref>. This requires:

	apt-get install wpasupplicant		apt-get install wpasupplicant
Line 264:		Line 264:
	and giving, at prompt, the corresponding passphrase. (Actually, I did <code> wpa_passhprase <myssid> <mypassphrase> > /path/to/n900/etc/network/interfaces.d/wlan0 </code>, and edited this file.)		and giving, at prompt, the corresponding passphrase. (Actually, I did <code> wpa_passhprase <myssid> <mypassphrase> > /path/to/n900/etc/network/interfaces.d/wlan0 </code>, and edited this file.)

-	I also added ssh support<ref> https://wiki.debian.org/SSH </ref>:	+	I also added ssh support <ref> https://wiki.debian.org/SSH </ref>:

	apt-get install openssh-server		apt-get install openssh-server
Line 298:		Line 298:


-	My main computer is a Mac, so I downloaded Nokia’s proprietary flasher<ref> It may be found at http://web.archive.org/web/20131117073524/http://skeiron.org/tablets-dev/maemo_dev_env_downloads/. </ref> (I have also a binary for 0xFFFF, built from the sources with a few modifications, but it is prone to hanging the whole system) and installed it (actually, since newer macs have some restrictions due to the System Integrity Protection, I had to unpack the files and copy them manually to proper positions. But this is another story). Then transferred the kernel zImage from the Devuan host to the Mac.	+	My main computer is a Mac, so I downloaded Nokia’s proprietary flasher <ref> It may be found at http://web.archive.org/web/20131117073524/http://skeiron.org/tablets-dev/maemo_dev_env_downloads/. </ref> (I have also a binary for 0xFFFF, built from the sources with a few modifications, but it is prone to hanging the whole system) and installed it (actually, since newer macs have some restrictions due to the System Integrity Protection, I had to unpack the files and copy them manually to proper positions. But this is another story). Then transferred the kernel zImage from the Devuan host to the Mac.

	This is the way I boot Devuan on the N900: turn off the device, hold “u”, connect to Mac by usb cable, wait for the usb symbol to appear on the top right corner (usually with backlight off) and on the Mac, from the directory containing the kernel zImage, issue:		This is the way I boot Devuan on the N900: turn off the device, hold “u”, connect to Mac by usb cable, wait for the usb symbol to appear on the top right corner (usually with backlight off) and on the Mac, from the directory containing the kernel zImage, issue:

enrico_menotti at 16:01, 6 May 2017

enrico_menotti — Sat, 06 May 2017 16:01:02 GMT

← Older revision		Revision as of 16:01, 6 May 2017
Line 1:		Line 1:
-	~~== Devuan on N900 ==~~
-
	What follows is an account about how I managed to get Devuan running on a Nokia N900 (console only, no desktop environment for now).		What follows is an account about how I managed to get Devuan running on a Nokia N900 (console only, no desktop environment for now).


-	=== Linux kernel ===	+	== Linux kernel ==

	I first cloned mainline (or rather stable) kernel:		I first cloned mainline (or rather stable) kernel:
Line 84:		Line 82:


-	=== Devuan file system ===	+	== Devuan file system ==

	For the following steps it is essential to be root on a Devuan system<ref> https://wiki.debian.org/EmDebian/CrossDebootstrap </ref>. Let’s install some packages:		For the following steps it is essential to be root on a Devuan system<ref> https://wiki.debian.org/EmDebian/CrossDebootstrap </ref>. Let’s install some packages:
Line 274:		Line 272:


-	=== Boot ===	+	== Boot ==

	Instead of flashing u-boot, I decided to test the system by:		Instead of flashing u-boot, I decided to test the system by:
Line 322:		Line 320:


-	=== Footnotes ===	+	== Footnotes ==

	<references />		<references />

enrico_menotti at 15:58, 6 May 2017

enrico_menotti — Sat, 06 May 2017 15:58:37 GMT

← Older revision		Revision as of 15:58, 6 May 2017
Line 124:		Line 124:
	# jessie		# jessie
	deb http://auto.mirror.devuan.org/merged/ jessie main contrib non-free		deb http://auto.mirror.devuan.org/merged/ jessie main contrib non-free
-		+
	# jessie-security, previously known as 'volatile'		# jessie-security, previously known as 'volatile'
	deb http://auto.mirror.devuan.org/merged/ jessie-security main contrib non-free		deb http://auto.mirror.devuan.org/merged/ jessie-security main contrib non-free
Line 135:		Line 135:
	Pin: release o=Debian		Pin: release o=Debian
	Pin-Priority: -1		Pin-Priority: -1
-		+
	Package: udev		Package: udev
	Pin: release o=Devuan		Pin: release o=Devuan

enrico_menotti at 15:56, 6 May 2017

enrico_menotti — Sat, 06 May 2017 15:56:51 GMT

← Older revision		Revision as of 15:56, 6 May 2017
Line 219:		Line 219:
	WARNING: ckbcomp reads <code> /etc/default/keyboard </code>, and then files in <code> /usr/share/X11/xkb/ </code>. The first file to be read is <code> rules/xorg </code>, which specifies other files to be read for the keyboard model and layout specified in <code> /etc/default/keyboard </code>. Based on the rules, files are read in <code> geometry/, keycodes/ </code> and <code> symbols/ </code>. At present (and probably also in the future) ckbcomp does not read files in <code> types/ </code>: the types for modifier keys are hardcoded in ckbcomp itself. As a consequence, there is a particular issue: the version of ckbcomp included in Jessie does not know about <code> PC_FN_LEVEL2 </code>, a type which allows on some keyboard layouts (e.g. Italian and German) to switch from left/right to up/down arrows by pressing (and holding) the function (blue) key. This results in a warning, and the arrow switch is instead obtained by means of shift. To correct the behaviour, I installed console-setup version 1.164 (from Debian sid), or rather installed it on Debian and copied <code> /usr/bin/ckbcomp </code> to the Devuan file system.		WARNING: ckbcomp reads <code> /etc/default/keyboard </code>, and then files in <code> /usr/share/X11/xkb/ </code>. The first file to be read is <code> rules/xorg </code>, which specifies other files to be read for the keyboard model and layout specified in <code> /etc/default/keyboard </code>. Based on the rules, files are read in <code> geometry/, keycodes/ </code> and <code> symbols/ </code>. At present (and probably also in the future) ckbcomp does not read files in <code> types/ </code>: the types for modifier keys are hardcoded in ckbcomp itself. As a consequence, there is a particular issue: the version of ckbcomp included in Jessie does not know about <code> PC_FN_LEVEL2 </code>, a type which allows on some keyboard layouts (e.g. Italian and German) to switch from left/right to up/down arrows by pressing (and holding) the function (blue) key. This results in a warning, and the arrow switch is instead obtained by means of shift. To correct the behaviour, I installed console-setup version 1.164 (from Debian sid), or rather installed it on Debian and copied <code> /usr/bin/ckbcomp </code> to the Devuan file system.

-	If one wants to customise the keyboard, the layout is defined in <code> symbols/nokia_vndr/rx-51 </code>; edit the file and run again <code> dpkg-reconfigure console-setup </code>.	+	If one wants to customise the keyboard, the layout is defined in <code> symbols/nokia_vndr/rx-51 </code>; edit the file<ref> https://wiki.maemo.org/Remapping_keyboard </ref> and run again <code> dpkg-reconfigure console-setup </code>.

	In order to have a working power button for shutdown, we need:		In order to have a working power button for shutdown, we need:
Line 249:		Line 249:
	wl1251_spi		wl1251_spi

-	to <code> /etc/modules </code>. At this point the wifi interface should be ready. In order to connect to my wlan, I also set up the wpa-psk protocol. This requires:	+	to <code> /etc/modules </code>. At this point the wifi interface should be ready. In order to connect to my wlan, I also set up the wpa-psk protocol<ref> https://wiki.debian.org/WiFi/HowToUse </ref>. This requires:

	apt-get install wpasupplicant		apt-get install wpasupplicant
Line 266:		Line 266:
	and giving, at prompt, the corresponding passphrase. (Actually, I did <code> wpa_passhprase <myssid> <mypassphrase> > /path/to/n900/etc/network/interfaces.d/wlan0 </code>, and edited this file.)		and giving, at prompt, the corresponding passphrase. (Actually, I did <code> wpa_passhprase <myssid> <mypassphrase> > /path/to/n900/etc/network/interfaces.d/wlan0 </code>, and edited this file.)

-	I also added ssh support:	+	I also added ssh support<ref> https://wiki.debian.org/SSH </ref>:

	apt-get install openssh-server		apt-get install openssh-server
Line 300:		Line 300:


-	My main computer is a Mac, so I downloaded Nokia’s proprietary flasher (I have also a binary for 0xFFFF, built from the sources with a few modifications, but it is prone to hanging the whole system) and installed it (actually, since newer macs have some restrictions due to the System Integrity Protection, I had to unpack the files and copy them manually to proper positions. But this is another story). Then transferred the kernel zImage from the Devuan host to the Mac.	+	My main computer is a Mac, so I downloaded Nokia’s proprietary flasher<ref> It may be found at http://web.archive.org/web/20131117073524/http://skeiron.org/tablets-dev/maemo_dev_env_downloads/. </ref> (I have also a binary for 0xFFFF, built from the sources with a few modifications, but it is prone to hanging the whole system) and installed it (actually, since newer macs have some restrictions due to the System Integrity Protection, I had to unpack the files and copy them manually to proper positions. But this is another story). Then transferred the kernel zImage from the Devuan host to the Mac.

	This is the way I boot Devuan on the N900: turn off the device, hold “u”, connect to Mac by usb cable, wait for the usb symbol to appear on the top right corner (usually with backlight off) and on the Mac, from the directory containing the kernel zImage, issue:		This is the way I boot Devuan on the N900: turn off the device, hold “u”, connect to Mac by usb cable, wait for the usb symbol to appear on the top right corner (usually with backlight off) and on the Mac, from the directory containing the kernel zImage, issue:
Line 325:		Line 325:

	<references />		<references />
-
-
-
-
-
-	~~ https://wiki.maemo.org/Remapping_keyboard~~
-	~~ https://wiki.debian.org/WiFi/HowToUse~~
-	~~ https://wiki.debian.org/SSH~~
-	~~ It may be found at http://web.archive.org/web/20131117073524/http://skeiron.org/tablets-dev/maemo_dev_env_downloads/.~~

enrico_menotti at 15:53, 6 May 2017

enrico_menotti — Sat, 06 May 2017 15:53:17 GMT

← Older revision		Revision as of 15:53, 6 May 2017
Line 45:		Line 45:


-	Now we may compile the kernel. Let’s first cd back to the <code> linux-4.10.8 </code> directory. Then select the desired target architecture and cross-toolchain:	+	Now we may compile the kernel<ref> http://elinux.org/N900 </ref>. Let’s first cd back to the <code> linux-4.10.8 </code> directory. Then select the desired target architecture and cross-toolchain:

	export ARCH=arm		export ARCH=arm
Line 54:		Line 54:
	make rx51_defconfig		make rx51_defconfig

-	At this point it is wise to hack a bit the kernel configuration by setting the two watchdogs (OMAP and TWL4030) to be included into the kernel itself and not separated as loadable modules. This is done by calling	+	At this point it is wise to hack a bit the kernel configuration by setting the two watchdogs (OMAP and TWL4030) to be included into the kernel itself and not separated as loadable modules<ref> Actually the system may boot also with the watchdogs in the modules, but in this case it is very unstable: to avoid reboot, the watchdogs need to be loaded in a few seconds, which may not be possible in some cases (namely, I had a problem due to udev waiting for the loopback lo device to be mounted, which did not happen due to the lack of an initrd). </ref>. This is done by calling

	make menuconfig		make menuconfig
Line 86:		Line 86:
	=== Devuan file system ===		=== Devuan file system ===

-	For the following steps it is essential to be root on a Devuan system. Let’s install some packages:	+	For the following steps it is essential to be root on a Devuan system<ref> https://wiki.debian.org/EmDebian/CrossDebootstrap </ref>. Let’s install some packages:

	apt-get install binfmt-support qemu qemu-user-static debootstrap		apt-get install binfmt-support qemu qemu-user-static debootstrap
Line 140:		Line 140:
	Pin-Priority: -1		Pin-Priority: -1

-	Now, in order to perform our customisation, we have to chroot again. To this aim, we first mount the <code> /proc </code> file system of the host to the <code> n900 </code> directory, and tell the system to install packages without starting their associated services. So let’s create <code> usr/sbin/policy-rc.d </code> with:	+	Now, in order to perform our customisation, we have to chroot again. To this aim, we first mount the <code> /proc </code> file system of the host to the <code> n900 </code> directory, and tell the system to install packages without starting their associated services. So let’s create <code> usr/sbin/policy-rc.d </code> with<ref> https://serverfault.com/questions/567474/how-can-i-install-packages-without-starting-their-associated-services </ref>:

	#!/bin/sh		#!/bin/sh
Line 326:		Line 326:
	<references />		<references />

-	~~http://elinux.org/N900~~	+
-	Actually the system may boot also with the watchdogs in the modules, but in this case it is very unstable: to avoid reboot, the watchdogs need to be loaded in a few seconds, which may not be possible in some cases (namely, I had a problem due to udev waiting for the loopback lo device to be mounted, which did not happen due to the lack of an initrd).	+
-	~~https://wiki.debian.org/EmDebian/CrossDebootstrap~~	+
-	~~https://serverfault.com/questions/567474/how-can-i-install-packages-without-starting-their-associated-services~~	+
	https://wiki.maemo.org/Remapping_keyboard		https://wiki.maemo.org/Remapping_keyboard
	https://wiki.debian.org/WiFi/HowToUse		https://wiki.debian.org/WiFi/HowToUse
	https://wiki.debian.org/SSH		https://wiki.debian.org/SSH
	It may be found at http://web.archive.org/web/20131117073524/http://skeiron.org/tablets-dev/maemo_dev_env_downloads/.		It may be found at http://web.archive.org/web/20131117073524/http://skeiron.org/tablets-dev/maemo_dev_env_downloads/.

enrico_menotti at 15:48, 6 May 2017

enrico_menotti — Sat, 06 May 2017 15:48:46 GMT

← Older revision		Revision as of 15:48, 6 May 2017
Line 30:		Line 30:
	apt-get install gcc-arm-none-eabi		apt-get install gcc-arm-none-eabi

-	The latter is more complicated, but may be useful later on. It may be downloaded from emdebian.org. By following Debian’s wiki, we first create <code> /etc/apt/sources.list.d/crosstools.list </code> containing:	+	The latter is more complicated, but may be useful later on. It may be downloaded from emdebian.org. By following Debian’s wiki <ref> https://wiki.debian.org/CrossToolchains </ref>, we first create <code> /etc/apt/sources.list.d/crosstools.list </code> containing:

	deb http://emdebian.org/tools/debian/ jessie main		deb http://emdebian.org/tools/debian/ jessie main
Line 324:		Line 324:
	=== Footnotes ===		=== Footnotes ===

-	~~https:~~/~~/wiki.debian.org/CrossToolchains~~	+	<references />
		+
	http://elinux.org/N900		http://elinux.org/N900
	Actually the system may boot also with the watchdogs in the modules, but in this case it is very unstable: to avoid reboot, the watchdogs need to be loaded in a few seconds, which may not be possible in some cases (namely, I had a problem due to udev waiting for the loopback lo device to be mounted, which did not happen due to the lack of an initrd).		Actually the system may boot also with the watchdogs in the modules, but in this case it is very unstable: to avoid reboot, the watchdogs need to be loaded in a few seconds, which may not be possible in some cases (namely, I had a problem due to udev waiting for the loopback lo device to be mounted, which did not happen due to the lack of an initrd).

enrico_menotti at 15:41, 6 May 2017

enrico_menotti — Sat, 06 May 2017 15:41:48 GMT

← Older revision		Revision as of 15:41, 6 May 2017
Line 274:		Line 274:


-	Boot	+	=== Boot ===

	Instead of flashing u-boot, I decided to test the system by:		Instead of flashing u-boot, I decided to test the system by:

-	copying the n900 Devuan file system to sd card;	+	# copying the n900 Devuan file system to sd card;
-	uploading the kernel to memory and booting from there by using Nokia’s proprietary flasher and NOLO.	+	# uploading the kernel to memory and booting from there by using Nokia’s proprietary flasher and NOLO.

-	I created an ext3 partition on the sd card (ext3 is readable from Maemo, so one may change things on the new filesystem by booting into Maemo and mounting the sd card partition). I did it this way: connected the N900 to my host Devuan system by usb, turned it on and selected “Mass storage mode.” Novel nodes appear at /dev (on the host), one for the /home partition in the internal eMMC and one for the external sd card (with subnodes for the partitions). Let’s call sdb the node related to the sd card. I did (from /dev):	+	I created an ext3 partition on the sd card (ext3 is readable from Maemo, so one may change things on the new filesystem by booting into Maemo and mounting the sd card partition). I did it this way: connected the N900 to my host Devuan system by usb, turned it on and selected “Mass storage mode.” Novel nodes appear at <code> /dev </code> (on the host), one for the <code> /home </code> partition in the internal eMMC and one for the external sd card (with subnodes for the partitions). Let’s call <code> sdb </code> the node related to the sd card. I did (from <code> /dev </code>):

-	parted -a optimal sdb	+	parted -a optimal sdb

	Then used parted commands to resize the original FAT primary partition, created an extended partition, and a logical partition inside the extended one. Lastly,		Then used parted commands to resize the original FAT primary partition, created an extended partition, and a logical partition inside the extended one. Lastly,

-	partprobe sdb	+	partprobe sdb

-	to re-read the partition table. At this point, inside /dev there should be sdb1 (primary), sdb2 (extended) and sdb5 (logical) nodes. Format sdb5:	+	to re-read the partition table. At this point, inside <code> /dev </code> there should be <code> sdb1 </code> (primary), <code> sdb2 </code> (extended) and <code> sdb5 </code> (logical) nodes. Format <code> sdb5 </code>:

-	mkfs.ext3 sdb5	+	mkfs.ext3 sdb5

-	Now I created a directory /media/devuan, and mounted sdb5 there. Then cd /path/to/n900 (the new Devuan file system) and:	+	Now I created a directory <code> /media/devuan </code>, and mounted <code> sdb5 </code> there. Then <code> cd /path/to/n900 </code> (the new Devuan file system) and:

-	rsync -avh * /media/devuan	+	rsync -avh * /media/devuan

	This copies the new Devuan file system to the new ext3 partition on the sd card.		This copies the new Devuan file system to the new ext3 partition on the sd card.
Line 304:		Line 304:
	This is the way I boot Devuan on the N900: turn off the device, hold “u”, connect to Mac by usb cable, wait for the usb symbol to appear on the top right corner (usually with backlight off) and on the Mac, from the directory containing the kernel zImage, issue:		This is the way I boot Devuan on the N900: turn off the device, hold “u”, connect to Mac by usb cable, wait for the usb symbol to appear on the top right corner (usually with backlight off) and on the Mac, from the directory containing the kernel zImage, issue:

-	flasher-3.5 -k zImage -l	+	flasher-3.5 -k zImage -l
-	flasher-3.5 -b”rootwait root=/dev/mmcblk0p5 rw”	+	flasher-3.5 -b”rootwait root=/dev/mmcblk0p5 rw”

	or, in a single line,		or, in a single line,

-	flasher-3.5 -k zImage -l -b”rootwait root=/dev/mmcblk0p5 rw”	+	flasher-3.5 -k zImage -l -b”rootwait root=/dev/mmcblk0p5 rw”

-	Explanation: the first command uploads the kernel to ram. The second tells NOLO to boot it and pass to the kernel the specified command line. There, rootwait tells the kernel to wait for the root file system to be mounted before passing it the control, the root parameter tells the location of the root fs (mmcblk0 is the sd card, in contrast to Maemo, where it is mmcblk1; p5 is the partition where the Devuan fs is located) and the rw flag tells to mount the root fs as read and write.	+	Explanation: the first command uploads the kernel to ram. The second tells NOLO to boot it and pass to the kernel the specified command line. There, <code> rootwait </code> tells the kernel to wait for the root file system to be mounted before passing it the control, the <code> root </code> parameter tells the location of the root fs (<code> mmcblk0 </code> is the sd card, in contrast to Maemo, where it is <code> mmcblk1 </code>; <code> p5 </code> is the partition where the Devuan fs is located) and the <code> rw </code> flag tells to mount the root fs as read and write.

	This is what happens: the usb symbol on the N900 screen disappears, after about one second the Nokia logo fades out, and after a while messages appear on the screen reporting a regular kernel boot, ending in a login prompt. One should be able to login as root with the password previously specified, and then issue “light” to run the script which turns on the screen backlight. Also, the device should appear on the wlan with a dynamically assigned IP address; I can issue (on the Mac, as standard user - with the same name as the standard user previously defined for the N900 Devuan file system):		This is what happens: the usb symbol on the N900 screen disappears, after about one second the Nokia logo fades out, and after a while messages appear on the screen reporting a regular kernel boot, ending in a login prompt. One should be able to login as root with the password previously specified, and then issue “light” to run the script which turns on the screen backlight. Also, the device should appear on the wlan with a dynamically assigned IP address; I can issue (on the Mac, as standard user - with the same name as the standard user previously defined for the N900 Devuan file system):

-	ssh <N900 IP>	+	ssh <N900 IP>

	enter the standard user’s password, get a remote shell, issue “su”, enter the root password, and enjoy the new system from my Mac.		enter the standard user’s password, get a remote shell, issue “su”, enter the root password, and enjoy the new system from my Mac.

-	There are indeed a few things to tune, and I still miss a desktop environment. https://wiki.debian.org/CrossToolchains	+	There are indeed a few things to tune, and I still miss a desktop environment.
		+
		+
		+	=== Footnotes ===
		+
		+	https://wiki.debian.org/CrossToolchains
	http://elinux.org/N900		http://elinux.org/N900
	Actually the system may boot also with the watchdogs in the modules, but in this case it is very unstable: to avoid reboot, the watchdogs need to be loaded in a few seconds, which may not be possible in some cases (namely, I had a problem due to udev waiting for the loopback lo device to be mounted, which did not happen due to the lack of an initrd).		Actually the system may boot also with the watchdogs in the modules, but in this case it is very unstable: to avoid reboot, the watchdogs need to be loaded in a few seconds, which may not be possible in some cases (namely, I had a problem due to udev waiting for the loopback lo device to be mounted, which did not happen due to the lack of an initrd).

enrico_menotti at 15:35, 6 May 2017

enrico_menotti — Sat, 06 May 2017 15:35:13 GMT

← Older revision		Revision as of 15:35, 6 May 2017
Line 190:		Line 190:


-	Third problem: adding a few packages. Again chroot n900 (with proc mounted). I did what follows.	+	Third problem: adding a few packages. Again <code> chroot n900 </code> (with <code> proc </code> mounted). I did what follows.

-	passwd (to set root password)	+	passwd (to set root password)
-	adduser <user> (to create a std user)	+	adduser <user> (to create a std user)
-	apt-get install locales	+	apt-get install locales
-	apt-get install keyboard-configuration	+	apt-get install keyboard-configuration
-	apt-get install console-setup	+	apt-get install console-setup

	To set up the correct locale, just do:		To set up the correct locale, just do:

-	dpkg-reconfigure locales	+	dpkg-reconfigure locales

	and follow the instructions.		and follow the instructions.

-	To set up correctly the keyboard, modify /etc/default/keyboard as follows:	+	To set up correctly the keyboard, modify <code> /etc/default/keyboard </code> as follows:

-	…	+	…
-	XKBMODEL=“nokiarx51”	+	XKBMODEL=“nokiarx51”
-	XKBLAYOUT=“<two letter country code>”	+	XKBLAYOUT=“<two letter country code>”
-	…	+	…

	and do:		and do:

-	dpkg-reconfigure console-setup	+	dpkg-reconfigure console-setup

	following the instructions. This, besides other things, runs ckbcomp to compile the XKB keyboard description to a keymap suitable for the console.		following the instructions. This, besides other things, runs ckbcomp to compile the XKB keyboard description to a keymap suitable for the console.

-	WARNING: ckbcomp reads /etc/default/keyboard, and then files in /usr/share/X11/xkb/. The first file to be read is rules/xorg, which specifies other files to be read for the keyboard model and layout specified in /etc/default/keyboard. Based on the rules, files are read in geometry/, keycodes/ and symbols/. At present (and probably also in the future) ckbcomp does not read files in types/: the types for modifier keys are hardcoded in ckbcomp itself. As a consequence, there is a particular issue: the version of ckbcomp included in Jessie does not know about PC_FN_LEVEL2, a type which allows on some keyboard layouts (e.g. Italian and German) to switch from left/right to up/down arrows by pressing (and holding) the function (blue) key. This results in a warning, and the arrow switch is instead obtained by means of shift. To correct the behaviour, I installed console-setup version 1.164 (from Debian sid), or rather installed it on Debian and copied /usr/bin/ckbcomp to the Devuan file system.	+	WARNING: ckbcomp reads <code> /etc/default/keyboard </code>, and then files in <code> /usr/share/X11/xkb/ </code>. The first file to be read is <code> rules/xorg </code>, which specifies other files to be read for the keyboard model and layout specified in <code> /etc/default/keyboard </code>. Based on the rules, files are read in <code> geometry/, keycodes/ </code> and <code> symbols/ </code>. At present (and probably also in the future) ckbcomp does not read files in <code> types/ </code>: the types for modifier keys are hardcoded in ckbcomp itself. As a consequence, there is a particular issue: the version of ckbcomp included in Jessie does not know about <code> PC_FN_LEVEL2 </code>, a type which allows on some keyboard layouts (e.g. Italian and German) to switch from left/right to up/down arrows by pressing (and holding) the function (blue) key. This results in a warning, and the arrow switch is instead obtained by means of shift. To correct the behaviour, I installed console-setup version 1.164 (from Debian sid), or rather installed it on Debian and copied <code> /usr/bin/ckbcomp </code> to the Devuan file system.

-	If one wants to customise the keyboard, the layout is defined in symbols/nokia_vndr/rx-51; edit the file and run again dpkg-reconfigure console-setup.	+	If one wants to customise the keyboard, the layout is defined in <code> symbols/nokia_vndr/rx-51 </code>; edit the file and run again <code> dpkg-reconfigure console-setup </code>.

	In order to have a working power button for shutdown, we need:		In order to have a working power button for shutdown, we need:

-	apt-get install acpi-support-base	+	apt-get install acpi-support-base

-	The way I will use to boot the system provides (sometimes…) a dark screen (no backlight). It is a good idea to prepare at this time a script to turn on the light: create /root/light with	+	The way I will use to boot the system provides (sometimes…) a dark screen (no backlight). It is a good idea to prepare at this time a script to turn on the light: create <code> /root/light </code> with

-	echo 200 > /sys/class/backlight/acx565akm/brightness	+	echo 200 > /sys/class/backlight/acx565akm/brightness

-	then chmod +x /root/light and create /root/.bash_profile with	+	then <code> chmod +x /root/light </code> and create <code> /root/.bash_profile </code> with

-	PATH+=:/root	+	PATH+=:/root

-	To enable battery charging, edit /etc/modules adding:	+	To enable battery charging, edit <code> /etc/modules </code> adding:

-	bq27xxx_battery	+	bq27xxx_battery
-	bq2415x_charger	+	bq2415x_charger
-	isp1704_charger	+	isp1704_charger

	This tells the kernel to load the three needed modules.		This tells the kernel to load the three needed modules.
Line 243:		Line 243:
	Last thing: wireless networking. First we need the firmware (which is non-free):		Last thing: wireless networking. First we need the firmware (which is non-free):

-	apt-get install firmware-ti-connectivity	+	apt-get install firmware-ti-connectivity

	Then we need the kernel module: add		Then we need the kernel module: add

-	wl1251_spi	+	wl1251_spi

-	to /etc/modules. At this point the wifi interface should be ready. In order to connect to my wlan, I also set up the wpa-psk protocol. This requires:	+	to <code> /etc/modules </code>. At this point the wifi interface should be ready. In order to connect to my wlan, I also set up the wpa-psk protocol. This requires:

-	apt-get install wpasupplicant	+	apt-get install wpasupplicant

-	and create /etc/network/interfaces.d/wlan0 containing	+	and create <code> /etc/network/interfaces.d/wlan0 </code> containing

-	auto wlan0	+	auto wlan0
-	iface wlan0 inet dhcp	+	iface wlan0 inet dhcp
-	wpa-ssid <myssid>	+	wpa-ssid <myssid>
-	wpa-psk <mypsk>	+	wpa-psk <mypsk>

-	I got <mypsk> from the Devuan host, by running (from outside the chroot):	+	I got <code> <mypsk> </code> from the Devuan host, by running (from outside the chroot):

-	wpa_passphrase <myssid>	+	wpa_passphrase <myssid>

-	and giving, at prompt, the corresponding passphrase. (Actually, I did wpa_passhprase <myssid> <mypassphrase> > /path/to/n900/etc/network/interfaces.d/wlan0, and edited this file.)	+	and giving, at prompt, the corresponding passphrase. (Actually, I did <code> wpa_passhprase <myssid> <mypassphrase> > /path/to/n900/etc/network/interfaces.d/wlan0 </code>, and edited this file.)

	I also added ssh support:		I also added ssh support:

-	apt-get install openssh-server	+	apt-get install openssh-server


-	The file system should be quite ready for booting into console. Exit the chroot jail, unmount proc and remove usr/sbin/policy-rc.d.	+	The file system should be quite ready for booting into console. Exit the chroot jail, unmount <code> proc </code> and remove <code> usr/sbin/policy-rc.d </code>.

enrico_menotti at 15:27, 6 May 2017

enrico_menotti — Sat, 06 May 2017 15:27:50 GMT

← Older revision		Revision as of 15:27, 6 May 2017
Line 172:		Line 172:


-	The second problem of our system is SELinux. It is probably not needed (and if I am not wrong it is disabled in the kernel); in any case, at boot the /sys/fs/selinux node is not mounted, and the init process, calling a function from libselinux to check whether ~~selinux~~ is enabled, tries anyway to mount the selinux filesystem: being unable to do that, it complains “loudly.” I found two solutions to this “issue:” an easy workaround, and a modification of the init code.	+	The second problem of our system is SELinux. It is probably not needed (and if I am not wrong it is disabled in the kernel); in any case, at boot the <code> /sys/fs/selinux </code> node is not mounted, and the init process, calling a function from libselinux to check whether SELinux is enabled, tries anyway to mount the <code> selinux </code> filesystem: being unable to do that, it complains “loudly.” I found two solutions to this “issue:” an easy workaround, and a modification of the init code.

-	The workaround consists in simply creating a /selinux (empty) folder. In this way, the functions from libselinux, when they don’t find /sys/fs/selinux, mount the selinux fs at /selinux (and don’t complain anymore). Besides this, I disabled ~~selinux~~ in /etc/selinux/config by changing the declaration of the SELINUX variable to:	+	The workaround consists in simply creating a <code> /selinux </code> (empty) folder. In this way, the functions from libselinux, when they don’t find <code> /sys/fs/selinux </code>, mount the <code> selinux </code> fs at <code> /selinux </code> (and don’t complain anymore). Besides this, I disabled SELinux in <code> /etc/selinux/config </code> by changing the declaration of the <code> SELINUX </code> variable to:

-	SELINUX=disabled	+	SELINUX=disabled

-	If one does not like the /selinux workaround, it is possible to modify the init code (and disable ~~selinux~~ in its config file as above). I think there is a bug here, since the code should not try to mount selinux in any case; however, the simplest thing to do is to get the source code for sysvinit and re-build it without declaring the WITH_SELINUX variable: this cancels out the pieces of code which take care of ~~selinux~~. Here however we need the arm-linux-gnueabihf toolchain, due to a missing crypt library in the arm-none-eabi one.	+	If one does not like the <code> /selinux </code> workaround, it is possible to modify the init code (and disable SELinux in its config file as above). I think there is a bug here, since the code should not try to mount selinux in any case; however, the simplest thing to do is to get the source code for sysvinit and re-build it without declaring the <code> WITH_SELINUX </code> variable: this cancels out the pieces of code which take care of SELinux. Here however we need the arm-linux-gnueabihf toolchain, due to a missing crypt library in the arm-none-eabi one.

-	So let’s exit the chroot jail and the n900 directory, and do:	+	So let’s exit the chroot jail and the <code> n900 </code> directory, and do:

-	apt-get source sysvinit	+	apt-get source sysvinit
-	cd sysvinit* (the actual name of the directory has the version appended)	+	cd sysvinit* (the actual name of the directory has the version appended)
-	export CC=arm-linux-gnueabihf-gcc	+	export CC=arm-linux-gnueabihf-gcc
-	make	+	make

-	This should build the init code; I got a few warnings, but no errors. The new init binary is at src/init, and should replace the sbin/init in the n900 directory.	+	This should build the init code; I got a few warnings, but no errors. The new init binary is at <code> src/init </code>, and should replace the <code> sbin/init </code> in the <code> n900 </code> directory.