Hi!
Since yesterday (not sure when was my last restart, but at most 3-4 days before) my T60 gives me a "Failed to find cpu0 device node" right at boot and stay there.
I have tried to boot with previous kernel (4.1.5, 4.1.2 I think) but I get the same results.
The recovery mode also doesn't work.
Any idea what this could be and most importantly how to fix it?
Thank you.
Fred
On 08/29/15 11:44, Frederic Muller wrote:
ince yesterday (not sure when was my last restart, but at most 3-4 days before) my T60 gives me a "Failed to find cpu0 device node" right at boot and stay there.
I have tried to boot with previous kernel (4.1.5, 4.1.2 I think) but I get the same results.
The recovery mode also doesn't work.
Any idea what this could be and most importantly how to fix it?
A quick google search reveals you're not alone.
https://bugzilla.kernel.org/show_bug.cgi?id=101621
may be relevant to your situation.
But, it doesn't seem as if others with the same message can't boot. Do you have a LiveCD that you can try to boot? These run earlier 3 series kernels.
On 08/29/2015 12:54 PM, Ed Greshko wrote:
On 08/29/15 11:44, Frederic Muller wrote:
ince yesterday (not sure when was my last restart, but at most 3-4 days before) my T60 gives me a "Failed to find cpu0 device node" right at boot and stay there.
I have tried to boot with previous kernel (4.1.5, 4.1.2 I think) but I get the same results.
The recovery mode also doesn't work.
Any idea what this could be and most importantly how to fix it?
A quick google search reveals you're not alone.
https://bugzilla.kernel.org/show_bug.cgi?id=101621
may be relevant to your situation.
But, it doesn't seem as if others with the same message can't boot. Do you have a LiveCD that you can try to boot? These run earlier 3 series kernels.
Yes I did a Google search before but didn't find the same exact issue (as I am stuck looking at the error message). I'll make a 32 bit USB key but then again, should I reinstall and update? I fear it'll take me to the same problem. Should I downgrade to 3 kernels before (something before 4.1.x) and if so how would I do that from the LiveCD?
Thank you.
Fred
On 08/29/15 14:05, Frederic Muller wrote:
Yes I did a Google search before but didn't find the same exact issue (as I am stuck looking at the error message). I'll make a 32 bit USB key but then again, should I reinstall and update? I fear it'll take me to the same problem. Should I downgrade to 3 kernels before (something before 4.1.x) and if so how would I do that from the LiveCD?
Just to confirm, you're CPU is 32 bit right?
Second, I would first boot from a live image just to confirm that it will work with the 3.X series kernels. You never know, you may have an actual HW problem. You said "recovery mode" also failed and I'm not sure if that was a 3.X kernel or not.
On 08/29/2015 02:13 PM, Ed Greshko wrote:
On 08/29/15 14:05, Frederic Muller wrote:
Yes I did a Google search before but didn't find the same exact issue (as I am stuck looking at the error message). I'll make a 32 bit USB key but then again, should I reinstall and update? I fear it'll take me to the same problem. Should I downgrade to 3 kernels before (something before 4.1.x) and if so how would I do that from the LiveCD?
Just to confirm, you're CPU is 32 bit right?
Second, I would first boot from a live image just to confirm that it will work with the 3.X series kernels. You never know, you may have an actual HW problem. You said "recovery mode" also failed and I'm not sure if that was a 3.X kernel or not.
Well strangely I thought it was a 64 bits but F22 didn't install in 64 bits. I've had this machine for 8 or 9 years and don't remember what I've run on it. I know I was slow to migrate to 64 bits so.. Right now it's running F22 32bits since its release and has been running Fedora for years. Just as it's a spare machine which recently got promoted to Kodi next to my TV I never really paid attention. It just worked.
And so the recovery mode has to be a 4.x kernel since I always reinstall from scratch, so it's F22 recovery mode and kernel.
I'll probably look into it later today and keep the list updated.
Thank you.
Fred
Try adding nosmp to the kernel boot option?? I've seen the same thing with my phenomii quad core system when booting with a 4.1x or 4.2x kernel? Same kernels work fine on a quad core i7, so not sure if it is a phenomii or kernel issue with some bios. Same kernels boot fine if I use nosmp option? I'm using virtual box on this system that is running an older version of fedora at moment that has no issue with latest kernel it had, but with virtualbox have it set to assign 2 cups, and I get the same error before kernel panic. If I change the Virtualbox setting to 1 cpu, it boots fine, and if I add the nosmp it boots fine.
What CPU does the machine have? Never saw this with any of the 3.x or 4.0x kernels, only once the 4.1x and 4.2x kernels. I'm buiding these kernels from source for my g4l project, but the configs are just copied from the earler versions.
On 29 Aug 2015 at 10:44, Frederic Muller wrote:
To: users@lists.fedoraproject.org From: Frederic Muller fred@cm17.com Subject: Failed to find cpu0 device node Date sent: Sat, 29 Aug 2015 10:44:12 +0700 Send reply to: Community support for Fedora users users@lists.fedoraproject.org
Hi!
Since yesterday (not sure when was my last restart, but at most 3-4 days before) my T60 gives me a "Failed to find cpu0 device node" right at boot and stay there.
I have tried to boot with previous kernel (4.1.5, 4.1.2 I think) but I get the same results.
The recovery mode also doesn't work.
Any idea what this could be and most importantly how to fix it?
Thank you.
Fred
users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
+----------------------------------------------------------+ Michael D. Setzer II - Computer Science Instructor Guam Community College Computer Center mailto:mikes@kuentos.guam.net mailto:msetzerii@gmail.com http://www.guam.net/home/mikes Guam - Where America's Day Begins G4L Disk Imaging Project maintainer http://sourceforge.net/projects/g4l/ +----------------------------------------------------------+
http://setiathome.berkeley.edu (Original) Number of Seti Units Returned: 19,471 Processing time: 32 years, 290 days, 12 hours, 58 minutes (Total Hours: 287,489)
BOINC@HOME CREDITS ROSETTA 33611820.231538 | SETI 60597169.100626 ABC 16613838.513356 | EINSTEIN 69553649.821895
On 08/29/2015 04:33 PM, Michael D. Setzer II wrote:
Try adding nosmp to the kernel boot option?? I've seen the same thing with my phenomii quad core system when booting with a 4.1x or 4.2x kernel? Same kernels work fine on a quad core i7, so not sure if it is a phenomii or kernel issue with some bios. Same kernels boot fine if I use nosmp option? I'm using virtual box on this system that is running an older version of fedora at moment that has no issue with latest kernel it had, but with virtualbox have it set to assign 2 cups, and I get the same error before kernel panic. If I change the Virtualbox setting to 1 cpu, it boots fine, and if I add the nosmp it boots fine.
What CPU does the machine have? Never saw this with any of the 3.x or 4.0x kernels, only once the 4.1x and 4.2x kernels. I'm buiding these kernels from source for my g4l project, but the configs are just copied from the earler versions.
Ok, added nosmp in the line starting with linux16 ... and right before rhgb. Same thing happens though :(
Thank you.
Fred
On 29 Aug 2015 at 10:44, Frederic Muller wrote:
To: users@lists.fedoraproject.org From: Frederic Muller fred@cm17.com Subject: Failed to find cpu0 device node Date sent: Sat, 29 Aug 2015 10:44:12 +0700 Send reply to: Community support for Fedora users users@lists.fedoraproject.org
Hi!
Since yesterday (not sure when was my last restart, but at most 3-4 days before) my T60 gives me a "Failed to find cpu0 device node" right at boot and stay there.
I have tried to boot with previous kernel (4.1.5, 4.1.2 I think) but I get the same results.
The recovery mode also doesn't work.
Any idea what this could be and most importantly how to fix it?
Thank you.
Fred
users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
+----------------------------------------------------------+ Michael D. Setzer II - Computer Science Instructor Guam Community College Computer Center mailto:mikes@kuentos.guam.net mailto:msetzerii@gmail.com http://www.guam.net/home/mikes Guam - Where America's Day Begins G4L Disk Imaging Project maintainer http://sourceforge.net/projects/g4l/ +----------------------------------------------------------+
http://setiathome.berkeley.edu (Original) Number of Seti Units Returned: 19,471 Processing time: 32 years, 290 days, 12 hours, 58 minutes (Total Hours: 287,489)
BOINC@HOME CREDITS ROSETTA 33611820.231538 | SETI 60597169.100626 ABC 16613838.513356 | EINSTEIN 69553649.821895
On 08/29/2015 06:40 PM, Frederic Muller wrote:
On 08/29/2015 04:33 PM, Michael D. Setzer II wrote:
Try adding nosmp to the kernel boot option?? I've seen the same thing with my phenomii quad core system when booting with a 4.1x or 4.2x kernel? Same kernels work fine on a quad core i7, so not sure if it is a phenomii or kernel issue with some bios. Same kernels boot fine if I use nosmp option? I'm using virtual box on this system that is running an older version of fedora at moment that has no issue with latest kernel it had, but with virtualbox have it set to assign 2 cups, and I get the same error before kernel panic. If I change the Virtualbox setting to 1 cpu, it boots fine, and if I add the nosmp it boots fine.
What CPU does the machine have? Never saw this with any of the 3.x or 4.0x kernels, only once the 4.1x and 4.2x kernels. I'm buiding these kernels from source for my g4l project, but the configs are just copied from the earler versions.
Ok, added nosmp in the line starting with linux16 ... and right before rhgb. Same thing happens though :(
Thank you.
Fred
and sorry, yes it is an Intel Core Duo T2500 @ 2Ghz * and indeed a 32bit processor *
Currently booting on the LiveCD is giving me strange things... so still investigating.
Fred
On 08/29/2015 07:04 PM, Frederic Muller wrote:
On 08/29/2015 06:40 PM, Frederic Muller wrote:
On 08/29/2015 04:33 PM, Michael D. Setzer II wrote:
Try adding nosmp to the kernel boot option?? I've seen the same thing with my phenomii quad core system when booting with a 4.1x or 4.2x kernel? Same kernels work fine on a quad core i7, so not sure if it is a phenomii or kernel issue with some bios. Same kernels boot fine if I use nosmp option? I'm using virtual box on this system that is running an older version of fedora at moment that has no issue with latest kernel it had, but with virtualbox have it set to assign 2 cups, and I get the same error before kernel panic. If I change the Virtualbox setting to 1 cpu, it boots fine, and if I add the nosmp it boots fine.
What CPU does the machine have? Never saw this with any of the 3.x or 4.0x kernels, only once the 4.1x and 4.2x kernels. I'm buiding these kernels from source for my g4l project, but the configs are just copied from the earler versions.
Ok, added nosmp in the line starting with linux16 ... and right before rhgb. Same thing happens though :(
Thank you.
Fred
and sorry, yes it is an Intel Core Duo T2500 @ 2Ghz * and indeed a 32bit processor *
Currently booting on the LiveCD is giving me strange things... so still investigating.
Fred
Thank you everyone, the machine doesn't seem to want to boot from the USB stick anymore. I think it just died.... :'(
So I guess we can close this thread.
Fred
-
Ed Greshko -
Frederic Muller -
Michael D. Setzer II