The Following 85 Users Say Thank You to Skry For This Useful Post: | ||
-Tyler-, 15jamie20, abubakar, ahmadamaj, anthonie, ArchiMark, azad1top, Bad_Habit, Bahador, bingomion, c4rl05, caveman, Cornu, Cue, demolition, Doctor Colossus, don_falcone, ersanpermana, Estel, foobar, freemangordon, fw190, goodgod261, GrimyHR, handaxe, ibrakalifa, iDont, imo, int_ua, ja-pc, jackburton, Joseph9560, joshgillies, Keneraali, kinchan, klinglerware, kornolio, LavaCroft, lenoch, m750, malfunctioning, manojkumaru, Marcus, melisa queen, MetalGearSolid, mosiomm, munozferna, n900_, nahci13, Netweaver, nkirk, Nobless, nokiabot, panjgoori, PanzerSajt, pedsarjon, phapsubongtoi, ranbaxy, reinob, robotanarchy, samipower, saponga, shanttu, sifo, sLumPia, Sohil876, Sourav.dubey, sowwhatyoureap, starkwiz, stlpaul, strange1712, szopin, tamas2001, teddydestodes, tetris11_, theonelaw, ThomasAH, turbovomit, Wikiwide, Wreck, Xagoln, xprism, Zaerc, zamorph, Älä hakkaa |
|
2012-01-28
, 08:31
|
|
Posts: 1,789 |
Thanked: 1,699 times |
Joined on Mar 2010
|
#3
|
The Following User Says Thank You to Kangal For This Useful Post: | ||
|
2012-01-28
, 16:08
|
|
Posts: 173 |
Thanked: 72 times |
Joined on Mar 2010
@ Denmark
|
#4
|
|
2012-01-28
, 16:20
|
Posts: 204 |
Thanked: 754 times |
Joined on Jan 2012
@ Finland
|
#5
|
I'd like to thank you for the guide.
I succesfully managed to boot into ArchLinux using multiboot, but it immediatly started throwing "udevd[XXX]: unable to receive ctrl connection: Function not implemented"-errors at me.
I had to do a reflash (no problem tho' - my phone was messed up), but I'll gladly try it out once again.
One question tho': What do you mean when you say "remember to sync" after having put all the files onto the partition?
|
2012-02-04
, 10:28
|
|
Posts: 173 |
Thanked: 72 times |
Joined on Mar 2010
@ Denmark
|
#6
|
You need to install udev-oxnas in chroot.
Type sync and hit enter It makes sure that everything is written into filesystem.
Nokia-N900:/# pacman -S udev-oxnas resolving dependencies... looking for inter-conflicts... :: udev-oxnas and udev are in conflict. Remove udev? [y/N] y error: failed to prepare transaction (could not satisfy dependencies) :: mkinitcpio: requires udev>=177-1
The Following User Says Thank You to Marcus For This Useful Post: | ||
|
2012-06-14
, 18:14
|
Posts: 34 |
Thanked: 15 times |
Joined on Jan 2010
|
#8
|
|
2012-06-19
, 08:59
|
Posts: 2 |
Thanked: 0 times |
Joined on Jun 2012
@ Czech rep. / Prague
|
#9
|
|
2012-07-02
, 07:32
|
Posts: 34 |
Thanked: 15 times |
Joined on Jan 2010
|
#10
|
The Following User Says Thank You to pinoverclock For This Useful Post: | ||
Introduction
This is the documentation part of my take on bringing the Arch Linux ARM (referred to as Alarm from now on) to your Nokia N900 device. This is not an official effort in any way, and I'm not related to Arch Linux or Alarm in any other way besides being a long time user. Please, settle down for a moment to carefully read through this post and the links I provide before plunging yourself any further.
About
https://www.archlinux.org/
The Arch Way v2.0.
Why would I want to use Arch?
http://alarm-n900.org/
Troubleshooting
Read this and see this.
I offer you a kernel and some more or less necessary packages. Kernel is known to boot with both U-Boot and Flasher, if it does not work for you, I'm not the guy to solve it or complain about to.
Any issues you might have with kernel or packages by me, you will report to me, and me only.
Anything Alarm, not related to kernel and packages I offer, you address to Alarm forums or IRC channel.
Everything N900 specific relating to Alarm, be it help with configuration, hardware issues or such, you can, again, address to me, this thread or the so very friendly chaps at #maemo-alternatives.
Documentation
Introduction
Beginners Guide
Installation Guide
Package Manager
Credits
Pali, Freemangordon, guys at #maemo-alternatives
Developers of Arch Linux and Arch Linux ARM
Arch wiki contributors
Installation
For your convenience, a small cheatsheet to help you install Alarm.
Install U-Boot
Get U-Boot.
Get your system to boot to Maemo first. This is the most trivial part of the installation, and you need to get this done and tested before continuing. I don't want or need any reports of not being able to boot.
NOTE:
You need to use U-Boot from Extras-devel.
Partitioning
I recommend partition size over 4GB. When partitioning uSD, you don't necessarily have to create separate swap partition, it is highly recommended to use the existing swap on eMMC. For eMMC installs, I suggest creating swap partition on uSD. Filesystems of choice are ext2, ext3 or ext4. For anything else, you need a separate /boot partition with filesystem readable by U-Boot and an uinitrd, or kernel with the fs you want built in. See Partitioning.
If you find that new partition table is not getting read, try
http://alarm-n900.org/files/ArchLinu...-rootfs.tar.gz
ftp://bokmal.de/arch-n900/ArchLinuxA...-rootfs.tar.gz
http://www45.zippyshare.com/v/91278544/file.html
- Untar to a partition (ext2/3/4) of your choice, sync.
- Skip to "Add U-Boot menu entry".
You can use wpa_supplicant, netcfg or wifi-menu for networking. Note that you'll get random MAC for wlan interface, on every boot, by default.
Option 2: Get official rootfs
Untar Latest OMAP rootfs to your dedicated partition.
When done, sync.
Chroot into your new Alarm install
Before we can boot to the fresh system, we need to do some trivial work in chroot.
See Chroot.
Update and configure system
Choose local mirror for pacman
Add my repository to /etc/pacman.conf
Example for Arch on first partition of uSD-card:
Good luck and have fun!
Suggestions and tips
Persistent MAC-address for WLAN interface
If you use netcfg, and have one static connection you start at boot, you can add
More appropriate way to handle this would be the use of macchanger and a systemd service; see MAC Address Spoofing.
I also suggest to set MAC-address to something different than what you have in Maemo, to avoid possible problems with SSH.
Xorg
So, you want Xorg on your device? The drivers in question are xf86-video-fbdev (unaccelerated) and xf86-video-fbdev-sgx-git (accelerated). The SGX stuff is highly experimental and a WIP, it works for me but can't promise it will work for you. If you have trouble with it, revert to xf86-video-fbdev. So, pick your poison.
For input device configuration, install n900-configs.
For n900 keymaps, install xkeyboard-config-n900-git.
DSP
To test the modem, install ofono-git from my repo. If you want calls, in addition to ofono you need everything from pulseaudio-n900 package group (EDIT: currently not in repo). For testing, there are command line tools in ofono-git package and you can find dbus examples via Google and from Maemo wiki. However, I don't currently recommend doing this, as it includes downgrading PA and it breaks support for it in most apps.
Modem initializing is done by systemd service n900_modem, which you need to either start and/or enable manually with systemctl.
To actually enable and online modem you need to run the very appropriately named tools from ofono called enable-modem and online-modem, in that order. Modem itself is very cunningly named /n900_0 in ofono.
FAQ
Blank screen after U-Boot
a) U-Boot is badly set up. b) You have wrong version/build of it.
Cant connect to WLAN
If you're not doing it wrong, and happen to have your AP doing MAC filtering, see Persistent MAC-address for WLAN interface.
Pacman complains about SSL/certificates
Clock is off.
No audio, wrong time, mysterious troubles, nothing works
Power off once in Alarm and boot again. I mean power off, not reboot. Alternatively, you could make a habit of going U-Boot console and typing reset every time you come from Maemo and intend to boot Alarm. Annoyance, I know, but hey, at least it works.
Last edited by Skry; 2014-04-12 at 23:01.