I have installed kernel 3.2-rc1 tonight without incident using my bash script sakc. I obtained the kernel using the script sgtb. It compiled just fine and I was able to install the most recent nVIDIA driver 285.05.09 64 bit driver with the help of my bash script lnvhw. I also now have a really fast way to reboot using my bash script fastboot.
Of course, the main thing here is the new kernel 3.2-rc1 is working properly. As always, I want to hear any comments on the new kernel that you might want to make.
After many failed attempts I finally have kernel 3.2-rc1-8 installed and running
My failed attempts were a comedy of errors on my part. the first three attempts using sakc was that I forgot that I did a clean install of openSUSE 12.1rc2 and didn’t install any kernel sources on my forth attempt I went to bed and woke up with sakc
ready to install but in my befuddled waking I entered the wrong key strokes but my fifth attempt worked like a charm.
the kernel seems to be working. Is there anything I should be looking for?
So I might ask that you download my bash script called S.L.A.V.E. and check out option 11 and see if you are getting any xserve errors. It seems I am seeing some with kernel 3.2-rc1 loaded that were not there before. Since I also load the nVIDIA driver, its hard to know what is causing what.
I did the kernel install into openSUSE 11.4 on my main system. I did have success installing kernel 3.1.1 into openSUSE 12.1 the other night in a VM. This weekend, I will spend more time with openSUSE 12.1 and the latest kernel.
Installing on openSUSE 12.2 milestone 0
using sakc I could not configure the kernel. I wanted to change the processor family to atom
make menuconfig gave me
dale@linux-zo9h:~/Kernel/linux-3.2-rc2> make menuconfig
/usr/lib64/gcc/x86_64-suse-linux/4.6/../../../../x86_64-suse-linux/bin/ld: scripts/kconfig/lxdialog/util.o: undefined reference to symbol 'nodelay'
/usr/lib64/gcc/x86_64-suse-linux/4.6/../../../../x86_64-suse-linux/bin/ld: note: 'nodelay' is defined in DSO /lib64/libtinfo.so.5 so try adding it to the linker command line
/lib64/libtinfo.so.5: could not read symbols: Invalid operation
collect2: ld returned 1 exit status
make: *** [scripts/kconfig/mconf] Error 1
make: *** [menuconfig] Error 2
I got make xconfig to work so I changed line 560 of sakc from make menuconfig to make xconfig after that sakc compiled the 3.2.0rc2 kernel and that is up and running
I tried to compile kernel-3.2-rc3 today using sakc on a openSUSE 12.1 PC and the compile fails with error code 2. I have not tried it on any other machine yet, but kernel-3.2-rc2 compiles just fine on the very same system so I am not sure just what this problem may mean.
On 11/25/2011 04:16 PM, dale14846 wrote:
> jdmcdaniel3;2410311 Wrote:
>> I tried to compile kernel-3.2-rc3 today using sakc on a openSUSE 12.1 PC
>> and the compile fails with error code 2. I have not tried it on any
>> other machine yet, but kernel-3.2-rc2 compiles just fine on the very
>> same system so I am not sure just what this problem may mean.
>> Thank You,
> I tried on a openSUSE 12.2 pc and that failed too will retry later
> using a manual make
FWIW, error 2 is only the final one from make. You need to see the actual error
from gcc. I use 3.2-rc2 from wireless-testing, and 3.2-rc3 from Linus’s tree.
Both build OK, but I don’t use the openSUSE standard configuration.
CC [M] drivers/staging/iio/trigger/iio-trig-periodic-rtc.o
CC [M] drivers/staging/iio/trigger/iio-trig-gpio.o
CC [M] drivers/staging/iio/trigger/iio-trig-sysfs.o
CC [M] drivers/staging/iio/industrialio-core.o
drivers/staging/iio/industrialio-core.c: In function ‘iio_event_getfd’:
drivers/staging/iio/industrialio-core.c:262:32: error: ‘ev_int’ undeclared (first use in this function)
drivers/staging/iio/industrialio-core.c:262:32: note: each undeclared identifier is reported only once for each function it appears in
make: *** [drivers/staging/iio/industrialio-core.o] Error 1
make: *** [drivers/staging/iio] Error 2
make: *** [drivers/staging] Error 2
make: *** [drivers] Error 2
dale14846, so there is something wrong with kernel-3.2-rc3 such that using our default .config file it errors out with a two. If the final product is in the head repository, then someone got it to compile. Let us know how it works.
On 11/26/2011 08:26 AM, dale14846 wrote:
> jdmcdaniel3;2410370 Wrote:
>> This is the error I get in my sakc log file. I tried three times and
>> every time the output is the very same.
> > > LD drivers/video/built-in.o
> > make: *** [drivers] Error 2
>> This is the last two lines in the log and then my script exits.
>> Thank You,
> Using make clean and make I got the error
> LD drivers/staging/iio/trigger/built-in.o
> CC [M] drivers/staging/iio/trigger/iio-trig-periodic-rtc.o
> CC [M] drivers/staging/iio/trigger/iio-trig-gpio.o
> CC [M] drivers/staging/iio/trigger/iio-trig-sysfs.o
> LD drivers/staging/iio/built-in.o
> CC [M] drivers/staging/iio/industrialio-core.o
> drivers/staging/iio/industrialio-core.c: In function ‘iio_event_getfd’:
> drivers/staging/iio/industrialio-core.c:262:32: error: ‘ev_int’ undeclared (first use in this function)
> drivers/staging/iio/industrialio-core.c:262:32: note: each undeclared identifier is reported only once for each function it appears in
> make: *** [drivers/staging/iio/industrialio-core.o] Error 1
> make: *** [drivers/staging/iio] Error 2
> make: *** [drivers/staging] Error 2
> make: *** [drivers] Error 2
> So now I will go the lazy way and install from ‘Index of
The patch to fix this is as follows:
From Andy Whitcroft <>
Subject [PATCH 1/1] iio: iio_event_getfd – fix ev_int build failure
Date Fri, 25 Nov 2011 10:56:22 +0000
Fix build failure in staging iio driver:
…/drivers/staging/iio/industrialio-core.c: In function ‘iio_event_getfd’:
‘ev_int’ undeclared (first use in this function)
Also convert the rest of the function to use the new variable.
Today I was able to successfully compile kernel 3.2-rc4 without any issues. It reads as following in openSUSE 11.4: Linux 3.2.0-rc4-0.5-desktop x86_64 AND I was able to install the nVIDIA driver 290.10 also without any issues.
Here is more inform on what to expect in kernel 3.2:
Well today I have upgraded my kernel to version kernel-3.2-rc5 without incident and again installed the nVIDIA driver 290.10 also without difficulty. With the exception of rc3, kernel 3.2 seems to be working very well for me. And I see a new info release on the kernel at H Open Source.
This weekend I updated to kernel 3.2-rc6 and again it did load without any problems. I have installed the nVIDIA driver 290.10 again as well, All is working as it is supposed to. I see that the H Open Source has yet another Article for us to read: