Arch Linux

Lotto320

Member

Registered: 2014-10-04

Posts: 2

Install hangs on started udev

When installing Archlinux 2014.10.01, my system hangs after "Started udev", the "underscore" stops blinking and input is disallowed. Does anyone have any clue why this is?

I'm installing the x86_64 version from an USB stick using http://sourceforge.net/projects/usbwriter/. I tried i686 but the screen just froze and displayed 4 boxes of wiggly characters when doing so.

Thanks in advance.

Last edited by Lotto320 (2014-10-05 09:14:44)

jasonwryan

Anarchist

From: .nz

Registered: 2009-05-09

Posts: 30,424

Website

Re: Install hangs on started udev

Use `dd`, everything else sucks to some greater or more than greater extent.

Not a Kernel issue, moving to NC...

---

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Lotto320

Member

Registered: 2014-10-04

Posts: 2

Re: Install hangs on started udev

Use `dd`, everything else sucks to some greater or more than greater extent.

Thanks for the reply, however, I've now tried using dd on my other PC which has Debian and it still hangs after "Started udev Kernel Device Manager".

I've also tried 2014.09.03, to no avail.

EDIT:

With the "debug" parameter on boot, the last output is this:

[ OK ] Started udev Kernel Device Manager
    7.952681] agpgart-amd64 0000:00:00.0: AGP bridge [1106/0336]

Last edited by Lotto320 (2014-10-05 09:30:55)

Thrall

Member

Registered: 2012-04-24

Posts: 15

Re: Install hangs on started udev

Does it get as far as setting the display resolution? Is there any change if you add nomodeset to the kernel parameters?
(Just a wild stab in the dark, based on something I experienced)

dylanmckay

Member

Registered: 2014-10-07

Posts: 2

Re: Install hangs on started udev

I am having the exact same problem on my brand new Acer Aspire E15.

It occurs when trying to run the Arch Linux install disc (I've tried dd'ing to USB, XFburning to CD, an older ISO image). What happens is that the computer starts, GRUB loads up from the LiveCD/USB, all goes well until Arch starts loading, and then it gets stuck on "Starting udev kernel device manager" (which is reports as OK). The fan completely stops making noises (I'm assuming the CPU is halted), and it stays off for 10 seconds, until spinning fast again for a few seconds and then repeating. It occurs on both UEFI and legacy boot modes, and it is irrespective of whether x86_64 or i686 is selected. Note that the only way to turn off the computer when this error occurs is to hold the power key - Arch doesn't respond to any input, including Ctrl+Alt+Delete.

I tried i686 but the screen just froze and displayed 4 boxes of wiggly characters when doing so

The problem still occurs for me when using i686, although at the point I did just get 4 boxes of wiggly characters at the top left of my screen. I don't remember what circumstances caused it or why it doesn't do it anymore.

Does it get as far as setting the display resolution? Is there any change if you add nomodeset to the kernel parameters?

It starts in a low resolution (640x480 VESA I presume) and does change to a higher resolution. Adding 'nomodeset' to the kernel arguments does not change anything but the resolution - the error still occurs.

The strange thing is that this happens 7/10 times - if I try booting the image over and over again, it occasionally does get past 'starting udev', but it doesn't work for long because after some arbitrary amount of time, the screen turns off and the PC halts, with the CPU fan doing the same spinning/slow down combination.

Perhaps the stranger thing is that to my knowledge, this happens solely on Arch - my (debian) GParted LiveCD works fine, and I was able to install (debian) Linux Mint.

Last edited by dylanmckay (2014-10-08 11:09:02)

dylanmckay

Member

Registered: 2014-10-07

Posts: 2

Re: Install hangs on started udev

This problem also exists on my friend's (very similar model) Acer Aspire. It occurs both with Arch Linux and Manjaro Linux (a derivative of Arch).

He discovered (and I confirmed) that plugging an HDMI cord in and having it output to an external screen stops the error.