Description of problem: Dual core cpu not recognised on MGA2 Dell D630 Intel Cure 2 Duo, only 1 core recognized after clean CD install. Worked perfectly on MDK 2010.2 & 2011 PWP until this new install. Bios reports 2 cores, /proc/cpuinfo and Control Center hardware detection only reports 1 core. Default install with kernel 3.3.6-desktop-2.mga2. 4GB ram Version-Release number of selected component (if applicable): [johan@localhost ~]$ uname -r 3.3.6-desktop-2.mga2 [johan@localhost ~]$ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Duo CPU T8300 @ 2.40GHz stepping : 6 microcode : 0x60f cpu MHz : 2394.094 cache size : 3072 KB physical id : 0 siblings : 1 core id : 0 cpu cores : 1 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 10 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 lm constant_tsc up arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 lahf_lm ida dts tpr_shadow vnmi flexpriority bogomips : 4788.18 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: How reproducible: Every time the systen boots up. Steps to Reproduce: 1. Switch on 2. log in, open terminal 3. cat /proc/cpuinfo During the 1st reboot I immediately noticed how slugish the system responded compared to the previous Mandriva 2011 KDE PWP install. Upon investigation, I noticed that only 1 core was active.
Priority: Normal => HighCC: (none) => johanmboxHardware: i586 => x86_64
CC: (none) => sander.lepikComponent: Release (media or process) => RPM PackagesSource RPM: (none) => kernel
CC: sysadmin-bugs => (none)
Attach /var/log/dmesg
CC: (none) => tmb
Created attachment 2404 [details] /var/log/dmesg
Summary: Dual core CPU not recognised on an Intel Core 2 Duo Dell D930 Laptop => Dual core CPU not recognised on an Intel Core 2 Duo Dell D630 Laptop
Just to make sure, I booted an older live cd distro today, kernel 2.6.33 and the 2 cores showed up no problems.
I see you boot with "acpi=off", why? can you try to boot with that removed ?
Hmmmm... "I see you boot with "acpi=off", why?" That was the default after install. "can you try to boot with that removed ?" Yes I did, it fixed 2 problems. 1. Shutdown now works as expected. 2. I can see 2 CPU's :) I'm going to do another clean install since I need more root space on the HDD (120GB total) and will report back about the acpi settings for booting from the live CD and after the install. It may have to have something to do with the way I'm force to install because to screen locks up hard if I boot straight off the live CD. I have to do a safe boot, config X with a Vesa driver, then start X and install. Once I have the Vesa setup and reboot, it auto configures itself with the i810 and later driver. The hardware is actually an Intel 965 with a Nvidia. Will try to get the Nvidia to work later. Thanks for the help so far!
As noted in errata, try to boot with either xdriver=nvidia or xdriver=intel to get past the dual/hybrdid gpu bug.
I did the xdriver=* thingy but it kept on locking up. Will try again tonight after I've made a backup of /home because of the root resizing. Thanks
Just did another install with 1 difference. This time I used a live usb stick rather than a CD to install (same iso as before). Pressed F6, Normal install and added xdriver=nvidia. Everything worked as expected. After reboot the graphics driver shows up as Intel. Would like to run the NVidia all the time, but will sort that out later. Both CPU's come up, everything seems to work 100% Question: Does the install pick up the boot parameters for the live CD desktop that I have used as the default for the HD install? Remember I used "Safe Mode" and a VESA driver initially to get X running via startx. If that is the case, it will explain why acpi was missing in the final install because it used the live CD /proc/cmdline. Thanks!
Status: NEW => RESOLVEDResolution: (none) => FIXED