Ask Your Question
0

failed to find cpu0 device node error

asked 2015-10-23 02:49:12 -0500

Ashishdixit gravatar image

after installing fedora 22 updated, getting error"failed to find cpu0 device node error" and boot stucks.

issuing is coming with linux kernel update 4.2. as i am able to boot in older kernel i.e. 4.0 from grub menu.

I am using dell mini laptop with intel atom processor N455.

edit retag flag offensive close merge delete

Comments

Same issue, after upgrading from Fedora 21 to 22 via Fedup. I'm now getting a message "failed to find cpu0 device node error" and boot hangs.

issue is with linux kernel 4.2.6-201.fc22.i686 (Twenty Two) I am able to boot using an older kernel 3.19.8-100.fc20.i686 (Heisenbug) from the GNU Grub menu. I'm using Dell Inspiron mini laptop 1012 (32-bit) Intel Atom processor CPU N450 1.66Ghz x 2. Hit F2 and msg logs indicate it's stuck on starting Load/Save RF Kill Switch Status of rfkill1& rfkill0. Any suggestions.

Amardis gravatar imageAmardis ( 2015-12-08 03:17:25 -0500 )edit

Checked this list https://en.wikipedia.org/wiki/List_of... . My Fedora 22 setup was using atm kernel 3.19.8-100.fc20 9 GNOME 3.16, it's possibly that Fedora 22 is associated with kernel 4.0 and not 4.2. So I installed using $ sudo dnf --realeasever=22 install kernel-4.0.4-301.fc22 the latest compatible kernel version for Fedora 22 based on that list above. No boot messages "failed to find cpu0" core issues when I select 4.04 from grub2 menu. All is well.

Amardis gravatar imageAmardis ( 2015-12-08 07:05:22 -0500 )edit

@Amardis were you able to boot properly even when getting the error? I'm getting the error, but my laptop boots normally after that. Just curious on whether it does impact performance.

mikechav gravatar imagemikechav ( 2016-04-11 12:27:09 -0500 )edit

4 Answers

Sort by ยป oldest newest most voted
1

answered 2016-07-23 09:23:20 -0500

PaulD gravatar image

Supposed to be a warning linked to CONFIG_OF (Open Firmware) in the kernel. Supposed to be used mostly on PowerPC, that contains a way to ask the computer for the graph a connected hardware information. I believe Linux begin to ask for the CPU, and because the computer does not contains this information graph, it results in this warning.

https://bugzilla.redhat.com/show_bug.... https://www.kernel.org/doc/Documentat...

edit flag offensive delete link more
0

answered 2017-05-16 22:28:49 -0500

David McCracken gravatar image

I think that this has been addressed as not really a problem but more of a heads up. However, it seems to frequently be the last printed message before some subsequent unrelated problem crashes the installation, giving the impression that it is not as benign as it really is.

edit flag offensive delete link more
0

answered 2015-12-09 00:39:07 -0500

I ran into this problem today. After Googling and trying out different solutions, I believe I've found the solution. The problem appears to be caused by the liveusb-creator (available at https://fedorahosted.org/liveusb-crea... ) for creating bootable USB drive for installing Fedora. The problem is gone after switching to using Rawrite32 ( http://www.netbsd.org/~martin/rawrite... ) to create the USB drive for installation and re-install Fedora 23 to my Acer Aspire One (D150).

Detail explanation of this issue can be found at the below site.

https://www.happyassassin.net/2014/02...

edit flag offensive delete link more
0

answered 2016-03-31 13:51:14 -0500

Just had the same problem installing f23 i686 to an old Samsung N150+. The error came up on the screen but we left it for a few second and it continued on to install ok. The USB drive was created using dd so the error is not unique to liveusb-creator.

edit flag offensive delete link more

Question Tools

1 follower

Stats

Asked: 2015-10-23 02:49:12 -0500

Seen: 13,180 times

Last updated: May 16 '17