Just moved from 11.3 to 11.4. I have an Intel DX58SO MB with an I7 cpu. Upgrade failed, so did a fresh install from the dvd media. For what ever reason, it did not detect multiple cpu’s and I am running on 1! ??? What is going on, and how do I fix this? I’m suspecting a bug at this point, but will hold off until I can get some validation, or input.
cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 26
model name : Intel(R) Core™ i7 CPU 930 @ 2.80GHz
stepping : 5
cpu MHz : 2837.241
cache size : 8192 KB
physical id : 0
siblings : 1
core id : 0
cpu cores : 1
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc up arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm ida dts tpr_shadow vnmi flexpriority ept vpid
bogomips : 5674.48
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
I might try typing in the kernel load option **ACPI **just before you press enter on the standard openSUSE startup (NOT Failsafe) and see if this makes any difference. It should be typed in caps, but I just put it in bold to show up better. If this option helps, you can edit the file /boot/grub/menu.lst as root and add this kernel load option. I found a good listing of kernel options here:
Thanks. I will go try that now. And since I’m a dork and put smtp instead of smp. DOH! Are you able to change a thread title somehow?
Only mods can change the title. I must say that I would use only the kernel-desktop or kernel-default and not anything esle, though I am not sure just which kernel you say you are loading. It is possible to install the most recent kernel in several ways I can give you, but I stick with kernel-desktop myself. I have installed the hot off the presses kernel version 2.6.39 just this very day. You can find it right here:
Well I just borked it big time. I got too clever. I just went into the boot loader and noted that acpi=off. Well it was on in 11.3, so I just changed it back. It locks up and will no longer boot. Which made me recall. Using the 11.4 DVD it would lock up unless I modified the parameters to “safe” as one of the options. Something is seriously wrong with ll.4 I’m sorry to say. This is an Intel MB with i7 cpu. Nothing tricky. 11.3 and older have all worked for a year. No issues. I think I’m going to go look at Ubuntu. I have wasted Sunday, through today trying to undo all the things that are hosed from my 11.3 to 11.4 upgrade and now fresh install. Very disappointed.
Sorry guys… I think 11.4 has fallen WAY WAY short this time. I’m burning Ubuntu and if it is as good as the 50% that use it thinks it is, I won’t be back. I have fought and fought with it since Sunday. It is almost Friday, and I’d like to think I know what I’m doing. Maybe it is part my fault for not participating in the beta/ RC copies and providing feedback, but listen, if it isn’t ready for release, postpone it. Don’t destroy your reputation to keep a schedule it. The damage can be irreparable. Fire away… I’m sure this will ruffle some feathers. I may be back but right this second, I’ve had it.
Sorry guys… I think 11.4 has fallen WAY WAY short this time. I’m burning Ubuntu and if it is as good as the 50% that use it thinks it is, I won’t be back. I have fought and fought with it since Sunday. It is almost Friday, and I’d like to think I know what I’m doing. Maybe it is part my fault for not participating in the beta/ RC copies and providing feedback, but listen, if it isn’t ready for release, postpone it. Don’t destroy your reputation to keep a schedule it. The damage can be irreparable. Fire away… I’m sure this will ruffle some feathers. I may be back but right this second, I’ve had it.
First off, the more participation and bug reporting that is done, the better openSUSE can become. However, I have loaded openSUSE on lots of configurations to find it works like a champ. I do think that loading it on any new Laptop or Desktop can show some issues with new hardware. I can also say that some issues are created by users who think they know what they are doing and whom modify too many defaults and end up taking a wrong turn somewhere. One thing is for sure, there are a lot of Linux Distros out there and perhaps a different one will work better for you. If you do find that perfect one, just let us know of your success and good luck.
Well well well… I am so glad I tried Ubuntu. It has uncovered an issue that is NOT Suse’s fault!! The new kernel has had a major bug introduced into it. I could not even boot to it! Just a blinking cursor. So I started there. Made sure the media was good. It was. So now I’m thinking hardware. Unplugged all non standard USB stuff. same thing. So then I went into CMOS to make sure I didn’t have anything odd configured. Nothing. Next I started experimenting with settings, since I was getting 1 cpu on an SMP kernel. I ended up discovering that the new kernel will not work right with extended CPUID on!! I had to turn it back to off for old legacy systems. Up came Ubuntu. So figuring it was a kernel issue, I pulled the disk out and up came Suse!! It now sees 4 cpus as well. This is a kernel bug!! HAS to be, since 11.3 works just fine. Now I have to figure out how to report it, or see if it is already discovered so we can get it stamped out quickly.
Well well well... I am so glad I tried Ubuntu. It has uncovered an issue that is NOT Suse's fault!! The new kernel has had a major bug introduced into it. I could not even boot to it! Just a blinking cursor. So I started there. Made sure the media was good. It was. So now I'm thinking hardware. Unplugged all non standard USB stuff. same thing. So then I went into CMOS to make sure I didn't have anything odd configured. Nothing. Next I started experimenting with settings, since I was getting 1 cpu on an SMP kernel. I ended up discovering that the new kernel will not work right with extended CPUID on!! I had to turn it back to off for old legacy systems. Up came Ubuntu. So figuring it was a kernel issue, I pulled the disk out and up came Suse!! It now sees 4 cpus as well. This is a kernel bug!! HAS to be, since 11.3 works just fine. Now I have to figure out how to report it, or see if it is already discovered so we can get it stamped out quickly.
So good to hear you were able to overcome the problem. I would follow malcolmlewis suggestion to report a bug about the BIOS CPUID setting as I am sure they would want to know that. Also, I did post instructions on adding in a newer kernel, which might already have fixed the issue, if BIOS CPUID setting problem is kernel related.
I will try. It is giving me grief. I have had to re-validate my email, which is a good thing, but so far, no joy. I will definitely get in there though and if not already reported make it a point to report it. This is huge, since I need it enable for Virtualbox. Thanks again, and I’m calming down some, but still not fixed.
On 05/20/2011 11:36 AM, lshantz wrote:
>
> I will try. It is giving me grief. I have had to re-validate my email,
> which is a good thing, but so far, no joy. I will definitely get in
> there though and if not already reported make it a point to report it.
> This is huge, since I need it enable for Virtualbox. Thanks again, and
> I’m calming down some, but still not fixed.
Operating systems that run on a wide variety of machines will suffer from these
kinds of problems. My suspicion is that your BIOS does not follow the rules
exactly, which shows up as a kernel bug. Is it really? One the appropriate
developer is aware of the problem, a workaround will likely be found, if it has
not already been addressed.
As Windows is more ubiquitous, the MB vendors will usually tweak the BIOS to
satisfy whatever M$ wants, thus the board will work there.
As suggested above, file a bug with the Novell bugzilla, but I would also file
one at bugzilla.kernel.org and list it as a regression for kernel 2.6.37 as
2.6.34 works. Cross reference the bug numbers on both lists.
Okay, here is what I have learned after many hours of futizing around. “Apprently” there was a bug in the firmware for the Intel chip! ?? Or at least they made some changes to it, and this solved the problem. So please modify the note that IF CPUID changes do not solve the problem, to go to the Intel site and get an updated firmware. It seems that this may in fact have been 90% of my problems, including the 5+ minute delay as it sat trying to figure out an unknown usb device with -110 errors. I’m running out of time to tinker to verify this, but felt I owed it to everyone to post the latest information that seems to have solved my issue. I’m guessing others will have this issue, since this mb/cpu combo is only a couple of years old at this point.
Thanks guys.
Now if I could just get the derned audio loopback to work for my tv card. But that is another thread.
Okay, here is what I have learned after many hours of futizing around. “Apprently” there was a bug in the firmware for the Intel chip! ?? Or at least they made some changes to it, and this solved the problem. So please modify the note that IF CPUID changes do not solve the problem, to go to the Intel site and get an updated firmware. It seems that this may in fact have been 90% of my problems, including the 5+ minute delay as it sat trying to figure out an unknown usb device with -110 errors. I’m running out of time to tinker to verify this, but felt I owed it to everyone to post the latest information that seems to have solved my issue. I’m guessing others will have this issue, since this mb/cpu combo is only a couple of years old at this point.
Thanks guys.
Now if I could just get the derned audio loopback to work for my tv card. But that is another thread.
When you say firmware, firmware to what? CPU? Hard Drive? Motherboard chipset? Wireless or something else?
Sorry I wasn’t more clear. The Motherboard=mb firmware I assume. It is an intel mb, with an intel cpu. I went to their website and looked for my model and it said there was an updated firmware for it.
4/5/2011
BIOS Update [SOX5810J.86A]
This download record provides three options for updating the BIOS of the Intel® Desktop Board DX58SO.
It has fixed a couple of issues that popped up in the 11.4. One was the HUGE wait for an un-identified USB device. A usb tv DVR. the other was the freezing. In safe mode, it installed, but only 1 cpu showed up etc. Something was introduced into the newest kernel that brought out the worst in this system. VERY ugly. I was thinking it was Opensuse, but Ubuntu did the same thing, so that got me to thinking. Older boot CD’s worked fine, new ones didn’t, so I started digging deeper. Now if I could just get my lost time back. At least I figured it out.
Sorry I wasn’t more clear. The Motherboard=mb firmware I assume. It is an intel mb, with an intel cpu. I went to their website and looked for my model and it said there was an updated firmware for it.
4/5/2011
BIOS Update [SOX5810J.86A]
This download record provides three options for updating the BIOS of the Intel® Desktop Board DX58SO.
It has fixed a couple of issues that popped up in the 11.4. One was the HUGE wait for an un-identified USB device. A usb tv DVR. the other was the freezing. In safe mode, it installed, but only 1 cpu showed up etc. Something was introduced into the newest kernel that brought out the worst in this system. VERY ugly. I was thinking it was Opensuse, but Ubuntu did the same thing, so that got me to thinking. Older boot CD’s worked fine, new ones didn’t, so I started digging deeper. Now if I could just get my lost time back. At least I figured it out.
OK I see, the old BIOS update. I have updated many a computer BIOS and turned a few motherboards into bricks. It can sometimes help as in your case, ever so often it can hurt a lot and most of the time, it does not seem to do very much at all.
I have fought and fought with it since Sunday. It is almost Friday, and I’d like to think I know what I’m doing. Maybe it is part my fault for not participating in the beta/ RC copies and providing feedback, but listen, if it isn’t ready for release, postpone it. Don’t destroy your reputation to keep a schedule it. The damage can be irreparable. Fire away… I’m sure this will ruffle some feathers. I may be back but right this second, I’ve had it.
Go here for creating a bug 