This is completely baffling me…
I have a Lenovo Thinkpad X301, which has been running OpenSUSE 11.1 for a while, with vanilla kernels from kernel.org, built and installed in the standard (i.e. not SUSE) way.
A week ago, I dupped to 11.2, and also installed kernel 126.96.36.199 . This was compiled with the gcc-4.3 available under 11.2.
Everything worked fine (after the necessary messing around to get X working again).
This weekend, I dupped to 11.4 (via 11.3, of course). After more messing around to get X working again, things were working ok - using the same 188.8.131.52 kernel I’d built under 11.2
I then re-built the kernel. It appears to compile and install ok, and I haven’t changed the configuration or the grub configuration. However, it doesn’t load. Normally, I just get a blank screen after grub starts it loading. If I boot in basic VGA mode 0, then I get a few lines of messages before it hangs - it hangs complaining about APIC not connected to io bios, and if I boot noapic, it gets a few lines further before hanging after some message I don’t know about (allocating 4 HET). I don’t suppose that’s relevant, anyway.
I’ve tried three different gcc versions, and two different linux versions (2.31 as well), and the same thing happens.
This sounds like something going badly wrong with ld or as or something - but I don’t see how anything could have happened that wouldn’t have been noticed by thousands of others.
The binary kernels shipped with OpenSUSE are ok, of course.
So, if you want to compile a kernel, I got to throw my two cents in by using SAKC.
Kernel 184.108.40.206 is the most recent stable kernel you can download source to from The Linux Kernel Archives. I am using it on my PC with openSUSE 11.4 and it works great! I don’t think it materially matters where it came from though I would look for a version based on the most recent stable one if possible (220.127.116.11). You can compile your own from source using the SAKC bash script located here in message #17:
S.A.K.C. - SUSE Automated Kernel Compiler - Version 2.00
To compile your own kernels normally you should consider doing the following:
Open YaST / Software / Software Management - Select the View Button on the top left and pick Patterns. Now, you will see several Patterns listed and you want to select:
[X] Base Development
[X] Linux Kernel Development
[X] C/C++ Development
Then Press the Accept button on the bottom right and allow these applications to install. Using SAKC does not remove any previous kernels and all would be there to select from in your grub menu.lst file. If you load a proprietary video driver from nVIDIA or AMD, it must be reloaded into any new kernel that you might install. SAKC is just another option that allows any compatible kernel to be installed from kernel.org without waiting for the version you want to move to one of the repositories.
I appear to have resolved the problem by installing the latest linux binutils from kernel.org, and using that instead of the ld/as shipped with OpenSUSE.
On 04/26/2011 07:06 AM, jcbradfield wrote:
> I appear to have resolved the problem by installing the latest linux
> binutils from kernel.org, and using that instead of the ld/as shipped
> with OpenSUSE.
That cannot be the complete story. I compile standard kernels every day and I am
using the binary utilities from 11.4. I suspect something got messed up in your
dup process. My 11.4 system was a clean install of 11.4 M5 and dup from there to GM.
I dupped from the online repositories, four days ago.
My binutils is release 13.1 Build Date: Thu Feb 17 13:22:49 2011
On 04/26/2011 02:36 PM, jcbradfield wrote:
> I dupped from the online repositories, four days ago.
> My binutils is release 13.1 Build Date: Thu Feb 17 13:22:49 2011
> what’s yours?
2.21-13.1. That is the standard binutils for 11.4. My build date is 7:26 AM CST
on Feb. 17. The difference is probably x86_64 ve i586.