Arch image - boot probelm

[BrendonShaw]

I have been using the new Arch boot image archlinux-hf-2012-09-18 and have create SD cards without any problems. I recently updated my system using Pacman -Syu and after a reboot it got stuck at the boot up screen. I thought I can screw up and created a new clean SD card with the same image and now I have the same problem.

After the boot up I get the following messages

Code: Select all

Arch Linux 3.2.27-ARCH+ (tty1)

alarmpi login [OK] Started OpenNTP Daemon.
[OK] Reached target Multi-user
[OK] Reached target Graphical Interface

Nothing works, keyboard is lock, no IP address etc.

Do you know what I have done wrong or how to fix it?

[yomp]

Hi,
I did the update as well, but I am not getting to see anything when I boot. The screen just stays dark after the last pacman update. Has anyone figured out a solution already?

Regards,
yo

[pepedog]

The latest kernel is 3days old now, it's ok for me.
I did notice that the raspberry pi source for the kernel reverted backwards, not a good sign.

The most obvious thing is that you must sync before reboot (or halt), so things to be written which is still in merory completes. The command is sync

[BrendonShaw]

Odd thing is I have created a fresh SD card from the orginal image and it does not work. It feels like the last systems updates changed/modified something within the RPi and now using this image does not work. I have a brand new RPi I will try my latest SD card on this board and see what happens.

When you say latest "kernel is 3days old now" I am using the 2012-09-18 image, which is nearly a month old. Does this mean there is a new kernel or am I missing something?

I did read somewhere there was an issue and the HDMI interface, which need to be plugged in but I have not yet tried it.

[pepedog]

Newer kernels come at the rate of 1 or 2 a week.
pacman -Syu
That takes care of it. Always sync before reboot or halt

[BrendonShaw]

Cheers for the help, my problem is I cannot login via directly, ssh etc. I just get the above error message and then everything is locked. It's like the complete o/s has crashed, I have tried to re-create the SD card again but still the same problem.

Is there is a shortcut to stop the Arch startup as I think it's trying to start the GUI and making the board fall over.

[sdjf]

What hardware are you using to try to ssh in? The old image, if it saw a keyboard on initial boot, it assumed a monitor of some sort for GUI.

Unless it has changed, I understood the only way to complete the initial boot was via Ethernet.

[BrendonShaw]

I am using a Rapsberry Pi for a few months and never had any problems, I have created loads of SD cards from "archlinux-hf-2012-09" image and never had any problems.

This would have been one of the original boards. I have boot it up with the keyboard & monitor and login in via ssh or directly via the keyboard & display, several times before without any problems. Odd thing is the Ethernet is not working either, I have directly plugged into my router and still no connection. I never had these type of problems before?

It's odd with a fresh SD image, it's trying to start the "Graphical Interface" which never happen before? Why has it decided now to start the graphical interface?

I have a new board so I will give it ago and see what happens.

[maribu]

The target "graphical interface" is defined by systemd. Systemd does not use runlevels like old init did. For example multiuser.target is almost the same as runlevel 3 and graphical target is pretty much the same as runlevel 5.

Systemd defaults to boot to graphical target. But to actually get a graphical interface you have to first install same sort of display manager (for example lxdm) and than active the service.

Without activating any graphical system via systemctl booting to the graphical target does not include booting any graphical system.

Regards,
Maribu

PS: Double check your SD-Card, the ethernet cable and the power supply.

[pepedog]

That really doesn't look like an arch kernel
You have
Arch Linux 3.2.27-ARCH+ (tty1)
our kernels look like (this is latest kernel)---
Arch Linux 3.2.27-11-ARCH+ (tty1)
Debian, Raspbian, or using rpi-updater would do that

If your system was up, I would ask you to run these
uname -a
ls -l /usr/lib/modules

[pepedog]

Ok, a new kernel and firmware uploaded, please
pacman -Syu

[dyladan]

I was getting the same message. turns out if you just hit enter a login prompt will come up. ^C also worked for me

[BrendonShaw]

Just for your information, I tried with a new board and everything is okay. Somehow I managed to damage my board, really not sure as it's been cased and not really heavily used, odd but problem resolved.

Many thanks for the offer of help & support, with this issue.

[davidkennedy85]

I was getting the same message. turns out if you just hit enter a login prompt will come up. ^C also worked for me

Took me a while to figure this out too. Output looks like this:

Code: Select all

alarmpi login: [ OK ] Started OpenNTP Daemon.
[ OK ] Reached target Multi-User.
[ OK ] Reached target Graphical Interface.
_ <-- Type your username here

Other than this minor annoyance the new image is awesome

[pepedog]

I suppose this is a compromise. No doubt there is a quiet option but no progress would be shown until login popped up.
Things are happening in parallel, you can actually login befor the other message pops up.
Also things could been more extreme if loglevel was different, every kernel event appearing (which is interesting, for a short time)
https://wiki.archlinux.org/index.php/Sy ... ess_output put quiet in /boot/cmdline.txt

[BrendonShaw]

In the long term I managed to solve this problem, it was the power supply !!!!! I cannot believe all the problems it was something really stupid. I had a working configuration and was switching PSU & then had the same problems.

Tip only use good/recommended PSU's.....

Thanks for all your help & support....

[go61t]

Hi there,

i´ve expeceted exactly the same. For me I havn´t found a solution yet. I´ve tried several power switches. all in line with power specifications (for R-PI Rev b 800 to 1200 mA).
the system gives me just around 5 seconds to type anything then hangs.

to be more precisely there are two scenarios:

1. giving the device more time until the next restart gives me the opportunitiy to even log in (root).
The 'failure of dhcp' always makes the system hang.
2. restarting with no big interruption of power supply sometimes 'failure of dhcp' even occures before the login and therefore at login which is still offered no keyboad is listening, (as 'systemd' is working always parallel at a different pace, it seems.)

last entrence displayed at spash is always as often referred to over the net.
[ OK ] Reached target Graphical Interface.

What power supplys are you using? I could barely believe that this really is the responsible issue.

Any suggestions.

This all happend on first boot activity!!


Thanks for replies,
Sebastian

[sdjf]

How much power is available to the Pi is the critical factor, not how much the device says it delivers. You need to measure between TP1-TP2 to make sure that it is staying at 4.75-5.25.

[jiri]

I have the same issue posted by go61t .
Raspbian is working fine.
I am using stock charger which provides enough energy.
Any other suggestion?
I would like to run archlinux on my RPi.

[sdjf]

If you have access to another linux system (and those with raspbian working do) then I would suggest mounting partition 2 of the Arch SD card on your other linux box or functioning Pi with another Linux system, and then examining the logs quite carefully in /var/log to see if you can decipher a pattern that might explain why your systems hang. I sure do that, If I cannot get back in, I mount a goofy rootfs on another running Linux system (actually, on my Pi running another good Arch SD card) and then examine the logs.

I know they are hard to make out, when there is so much there, but you should be able to spot the errors or code just before it crashed.

I also am struggling with connections going down, but I am at least able to get in and do stuff for a while, sometimes even hours. But am still debugging, this stuff is not fun.

One thing that helped me, when I saw the issue was with usb, was to write a script that detects when the connection goes down, and then have it run a udevadm rule that reloads selected udev rules. But it sounds like you are not getting far enough along to be sure of that. What is cool is that I was declaring the system in a coma and requiring pulling the power plug to reboot, as the keyboard light was going out (I am running headless), but now that I trigger the usb rules to get reloaded, the keyboard gets recognized again after a while and I can reboot with CTL-ALT-DEL

Unable to paste in code right now for how detect dropped connection, maybe later if you guys are interested.

[jiri]

I have found only two errors. They are reported in several log files.

in daemon.log
Jan 1 01:00:07 alarmpi [ 3.232230] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. See system logs and 'systemctl status display-manager.service' for details.

errors.log
Jan 1 01:00:07 alarmpi kernel: [ 2.388208] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)

Any idea?

[pepedog]

Ignore these errors.
On the video console, are there any words? What happens if you hit enter?

[jiri]

no other errors, nothing else is displayed even if I hit enter ...
When is shown this line
[ OK ] Reached target Graphical Interface.

raspberry hang ...

[NoirCZ]

Same problem with the latest arch linux build