[SOLVED]Hang at 'triggering uevents' when booting from USB

stephanboy2030 · 2012-10-23 10:56:50

I'm new in the forum. In the past I tried to install it on a virtual machine and following the various guides, I did it. Now I am convince to replace my Kubuntu. I created the USB following the official guide ( with LiLi on Windows XP ), but the boot hangs on the line "uevents triggering", one of the first after starting the boot. I tried to enter the option "acpi = off" but nothing change. How to fix ?

HP Pavilion DV4379ea Notebook, Intel Centrino M740 1.73 GHz, Ati Mobility Radeon x700, 2 GB Ram, Intel Pro / Wireless Broadcom Ethernet.

Thanks a lot

Last edited by stephanboy2030 (2012-10-25 18:17:53)

DSpider · 2012-10-23 11:06:12

Bad choice for a title. I was going to suggest this but then I read some of the content. Try a different method. Here, try this one: https://wiki.archlinux.org/index.php/US … O_from_RAM

PS: Welcome to the forum.

Last edited by DSpider (2012-10-23 11:06:43)

Trilby · 2012-10-23 11:15:44

I was also a bit mislead by the title - but I think it is not necesarily a 'bad' choice, there just exists an unfortunate and not entirely easy-to-avoid ambiguity. Perhaps "Hang at 'triggering uevents' when booting from USB" would keep it more clear.

To address this, I'd be surprised if it were USB specific. Have you looked through the various previous threads on boot hangs at that line? There are quite a few of them, they should give some ideas.

brain0 · 2012-10-23 11:51:35

Try the option 'loglevel=7'. This sounds like a specific hardware problem.

stephanboy2030 · 2012-10-23 13:56:52

Yes, you are right, the title is confusing. Thanks Trilby to suggest me a new title.

Using the option loglevel=7, I get the boot stops at the same line when I try to boot from the USB Kubuntu 12.10, it's the following:

[3.732195] radeon 0000:01:00.0 > radeon : using MSI

I'm facing the same problem...

brain0 · 2012-10-24 11:29:06

You probably can boot when you pass modprobe.blacklist=radeon. However, the non-functioning radeon driver will be a problem later, after installation when you want to have a graphical environment. Another alternative: radeon.modeset=0 - if this works, you can at least get an X server.

stephanboy2030 · 2012-10-24 12:51:35

I solved using the "nomodeset" option as boot parameter, but what does mean?

brain0 · 2012-10-25 14:29:03

Traditionally, the Xorg driver configured the radeon by directly communicating with it. This is a bad idea. With "modesetting", there is a clear kernel API that the driver uses.

radeon still supports both modes - however, the modesetting mode fails for your specific card. This is a bug that should be reported to the radeon people - however, the latest Arch live image uses Linux 3.5.5, and our latest version is 3.6.3 - this means that after installation, this bug may already be fixed (at least you should test if it is).

stephanboy2030 · 2012-10-25 16:23:47

Thanks a lot.

Is this option change something in the install process and/or the installation result respect without using it?

brain0 · 2012-10-25 16:24:36

No, it doesn't change anything - you can add it into the bootloader configuration of the installed system, if you still need it with the latest versions.

zidarsk8 · 2012-11-14 19:53:50

stephanboy2030 wrote:

I solved using the "nomodeset" option as boot parameter, but what does mean?

Could you please tell me how and where did you set that. I have the same problem, and don't know where these parameters are.

Thank you.

brain0 · 2012-11-15 09:46:22

stephanboy2030 wrote:

I solved using the "nomodeset" option as boot parameter, but what does mean?

That's not a solution (people have been using that as a "solution" for a while, instead of reporting bugs, and therefore radeon still has this problem. Yay). Current versions of the radeon driver will not work this way.

DSpider · 2012-11-15 10:15:55

zidarsk8 wrote:

Could you please tell me how and where did you set that. I have the same problem, and don't know where these parameters are.

https://wiki.archlinux.org/index.php/KM … odesetting
https://wiki.archlinux.org/index.php/Kernel_parameters

Otsdarva · 2014-06-03 07:03:02

Where in the process (Downloading iso, writing to usb, booting machine, getting stuck at 'triggering uevents') do you do things like set these parameters? I read those two wiki pages that DSpider posted just above, but I didn't understand where that content fit into this overall story. I am having the exact same problem and am anxious to try things, but I just don't know how to implement all of your helpful fixes.

Thanks for your patience; I'm still learning.

Otsdarva · 2014-06-05 22:01:27

Aha! I answered my own question.

For future n00bs:

I have a UEFI motherboard and my graphical output is through a GTX 780 Ti. The motherboard is a Sabertooth X79, and has no standard VGA output. When I tried to boot an archiso (from a usb stick) in UEFI mode, it would hang at 'triggering uevents', as described above. It would boot normally is BIOS/Legacy mode.

By pressing 'e' at the bootloader menu, I had the opportunity for the input that I was looking for. There was only a single line, so I stuck the following in at the beginning:

linux /boot/vmlinux-linux root=UUID=978e3e81-8048-4ae1-8a06-aa727458e8ff nomodeset nouveau.modeset=0

Your parameters (nomodeset, nouveau.modeset=0) will vary by hardware. Through my reading, it seems to be tied to the graphics card.

You can find the proper parameters here.

P0stal · 2024-01-17 01:13:04

I have found out how to solve this problem another way. First, I put in a second graphics card then installed AMDGPU and switched back to the other graphics card.

V1del · 2024-01-17 01:40:11

Pretty much an overkill if you don't have another card at hand.

Also please note you're replying to a 10 year old topic with a solution that isn't a solution for most people.

Closing this old topic, please don't necrobump.

Arch Linux

#1 2012-10-23 10:56:50

[SOLVED]Hang at 'triggering uevents' when booting from USB

#2 2012-10-23 11:06:12

Re: [SOLVED]Hang at 'triggering uevents' when booting from USB

#3 2012-10-23 11:15:44

Re: [SOLVED]Hang at 'triggering uevents' when booting from USB

#4 2012-10-23 11:51:35

Re: [SOLVED]Hang at 'triggering uevents' when booting from USB

#5 2012-10-23 13:56:52

Re: [SOLVED]Hang at 'triggering uevents' when booting from USB

#6 2012-10-24 11:29:06

Re: [SOLVED]Hang at 'triggering uevents' when booting from USB

#7 2012-10-24 12:51:35

Re: [SOLVED]Hang at 'triggering uevents' when booting from USB

#8 2012-10-25 14:29:03

Re: [SOLVED]Hang at 'triggering uevents' when booting from USB

#9 2012-10-25 16:23:47

Re: [SOLVED]Hang at 'triggering uevents' when booting from USB

#10 2012-10-25 16:24:36

Re: [SOLVED]Hang at 'triggering uevents' when booting from USB

#11 2012-11-14 19:53:50

Re: [SOLVED]Hang at 'triggering uevents' when booting from USB

#12 2012-11-15 09:46:22

Re: [SOLVED]Hang at 'triggering uevents' when booting from USB

#13 2012-11-15 10:15:55

Re: [SOLVED]Hang at 'triggering uevents' when booting from USB

#14 2014-06-03 07:03:02

Re: [SOLVED]Hang at 'triggering uevents' when booting from USB

#15 2014-06-05 22:01:27

Re: [SOLVED]Hang at 'triggering uevents' when booting from USB

#16 2024-01-17 01:13:04

Re: [SOLVED]Hang at 'triggering uevents' when booting from USB

#17 2024-01-17 01:40:11

Re: [SOLVED]Hang at 'triggering uevents' when booting from USB

Board footer