warnings after saving .config file under xconfig

kushalkoolwal · 02-21-2006, 06:04 PM

Recently I decided to upgrade from kernel 2.6.13 to 2.6.15. I simply the copied the config-2.6.13 to /usr/src/linux-source-2.6.15 as .config and then ran make xconfig. After make kernel changes, when I saved the file and exited from xconfig I got the following warning messages:

Code:

debian:/usr/src/linux-source-2.6.15# cp /boot/config-2.6.13 .config
debian:/usr/src/linux-source-2.6.15# make xconfig
  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/basic/split-include
  HOSTCC  scripts/basic/docproc
  CHECK   qt
  HOSTCC  scripts/kconfig/conf.o
sed < scripts/kconfig/lkc_proto.h > scripts/kconfig/lkc_defs.h 's/P(\([^,]*\),.* /#define \1 (\*\1_p)/'
  HOSTCC  scripts/kconfig/kconfig_load.o
  HOSTCC  scripts/kconfig/kxgettext.o
  HOSTCC  scripts/kconfig/mconf.o
  SHIPPED scripts/kconfig/zconf.tab.c
  SHIPPED scripts/kconfig/lex.zconf.c
  SHIPPED scripts/kconfig/zconf.hash.c
  HOSTCC  scripts/kconfig/zconf.tab.o
/usr/bin/moc -i scripts/kconfig/qconf.h -o scripts/kconfig/qconf.moc
  HOSTCXX scripts/kconfig/qconf.o
  HOSTLD  scripts/kconfig/qconf
scripts/kconfig/qconf arch/i386/Kconfig
#
# using defaults found in .config
#
.config:148:warning: trying to assign nonexistent symbol HAVE_DEC_LOCK
.config:170:warning: trying to assign nonexistent symbol ACPI_BOOT
.config:171:warning: trying to assign nonexistent symbol ACPI_INTERPRETER
.config:188:warning: trying to assign nonexistent symbol ACPI_BUS
.config:191:warning: trying to assign nonexistent symbol ACPI_PCI
.config:265:warning: trying to assign nonexistent symbol PCI_NAMES
.config:358:warning: trying to assign nonexistent symbol IP_TCPDIAG
.config:359:warning: trying to assign nonexistent symbol IP_TCPDIAG_IPV6
.config:583:warning: trying to assign nonexistent symbol NET_QOS
.config:977:warning: trying to assign nonexistent symbol MEGARAID_NEWGEN
.config:1038:warning: trying to assign nonexistent symbol SCSI_QLOGIC_1280_1040
.config:1293:warning: trying to assign nonexistent symbol 2BUFF_MODE
.config:1745:warning: trying to assign nonexistent symbol I2C_SENSOR
.config:1895:warning: trying to assign nonexistent symbol FB_SOFT_CURSOR
.config:1981:warning: trying to assign nonexistent symbol SND_GENERIC_PM
.config:2279:warning: trying to assign nonexistent symbol USB_GENESYS
.config:2280:warning: trying to assign nonexistent symbol USB_NET1080
.config:2281:warning: trying to assign nonexistent symbol USB_PL2301
.config:2282:warning: trying to assign nonexistent symbol USB_KC2190
.config:2289:warning: trying to assign nonexistent symbol USB_ZAURUS
.config:2290:warning: trying to assign nonexistent symbol USB_CDCETHER
.config:2295:warning: trying to assign nonexistent symbol USB_AX8817X
.config:2469:warning: trying to assign nonexistent symbol DEVPTS_FS_XATTR
.config:2470:warning: trying to assign nonexistent symbol DEVPTS_FS_SECURITY
.config:2472:warning: trying to assign nonexistent symbol TMPFS_XATTR
.config:2473:warning: trying to assign nonexistent symbol TMPFS_SECURITY
debian:/usr/src/linux-source-2.6.15#

Are these warnings normal? Also I have read that if we are copying a different version of .config file then we have to run make oldconfig. But then on the contrary many people have suggested that I don;t need to run make oldconfig. make xconfig takes care of it.

Anyone?

noxious · 02-21-2006, 07:33 PM

It's just trying to tell you that your 2.6.13 .config file doesn't address the changes present in your new 2.6.15 kernel. It probably went with whatever the defaults are for those configurations... look them over and see if those are ones you may need, or want. The biggest difference (to me, anyways) going from a 2.6.13 to a 2.6.15 kernel is built in Intel Pro Wireless support.

dracae · 02-21-2006, 07:35 PM

Those are warnings not errors, not running oldconfig will just set them to the default values instead of asking you what you want.

kushalkoolwal · 02-21-2006, 07:52 PM

Quote:

Originally Posted by dracae

Those are warnings not errors, not running oldconfig will just set them to the default values instead of asking you what you want.

That means those symbols are present there in the configuration file(new file for 2.6.15), just that they will be set to the default values.

But if that is the case why does the warning says:
"trying to assign nonexistent symbol ACPI_BUS" and so.

At first glance it looks as if the new kernel(2.6.15) will not have those options which are listed as nonexistent.

I am a bit confused.

???

Thank you guys for looking into this..

dracae · 02-21-2006, 07:57 PM

It isn't adding it to the config, but the makefile/kernel has defaults that it will use

kushalkoolwal · 02-22-2006, 07:26 PM

ok. Does that mean that I don;t need to worry about those warnings. Actually I thought that the new kernel(which is being compiled) won;t have all those options which appeared in the warnings.

dracae · 02-22-2006, 08:09 PM

I would run make oldconfig just because it is the right thing to do.

kushalkoolwal · 02-22-2006, 08:35 PM

Quote:

Originally Posted by dracae

I would run make oldconfig just because it is the right thing to do.

Even I thought so. Co-incidentally I had a similar long thread on this forum itself related to this issue. And I had a mixed opinion whether to use oldconfig or not?

If you have time, take a look at this. I really get confused when it comes to this issue.

http://www.linuxquestions.org/questi...d.php?t=407097

Thanks

dracae · 02-22-2006, 08:53 PM

Well according to that thread menuconfig/xconfig should see that you are using an old config and run oldconfig for you. Either you are not saving you config after running it or it is not doing that. Either way, there is no harm in running make oldconfig and IMHO its the right thing to do.

Consider this.
New kernel has a new option, it defaults to compile as a module. This module has a dependency on some feature which you have removed/disabled. Will the make modules generate the module anyway even though it shouldn't? I can't answer that, but if it does can you imagine the headache of tracking down the unresolved symbols? Especially when it is so easy to run make oldconfig.

Now considering this is a Debian forum and make-kpkg is "The Debian Way" to compile a kernel, which will run make oldconfig for you, this is a moot point.

kushalkoolwal · 02-22-2006, 09:45 PM

Quote:

Originally Posted by dracae

Well according to that thread menuconfig/xconfig should see that you are using an old config and run oldconfig for you. Either you are not saving you config after running it or it is not doing that. Either way, there is no harm in running make oldconfig and IMHO its the right thing to do.

Consider this.
New kernel has a new option, it defaults to compile as a module. This module has a dependency on some feature which you have removed/disabled. Will the make modules generate the module anyway even though it shouldn't? I can't answer that, but if it does can you imagine the headache of tracking down the unresolved symbols? Especially when it is so easy to run make oldconfig.

Now considering this is a Debian forum and make-kpkg is "The Debian Way" to compile a kernel, which will run make oldconfig for you, this is a moot point.

Ok so for once and all these are the steps that one needs to follow in upgrading kernel(from 2.6.13 to 2.6.15).

Code:

#make clean

#cp /boot/config-2.6.13 /usr/src/linux-source-2.6.15/.config

#make oldconfig(answer the questions about new options, although it is tedious to answer so many new options, I literally get tired of answering the options)

#make xconfig (Configure the way you want)
save the file as .config(just to be sure)

#make-kpkg clean

#fakeroot make-kpkg --appened-to-version=-<date> kernel_image

and so on.....

Kindly confirm this?

Thanks once again for all the help.

kushalkoolwal · 02-23-2006, 05:47 PM

Quote:

Originally Posted by kushalkoolwal

Ok so for once and all these are the steps that one needs to follow in upgrading kernel(from 2.6.13 to 2.6.15).

Code:

#make clean

#cp /boot/config-2.6.13 /usr/src/linux-source-2.6.15/.config

#make oldconfig(answer the questions about new options, although it is tedious to answer so many new options, I literally get tired of answering the options)

#make xconfig (Configure the way you want)
save the file as .config(just to be sure)

#make-kpkg clean

#fakeroot make-kpkg --appened-to-version=-<date> kernel_image

and so on.....

Kindly confirm this?

Thanks once again for all the help.

anyone???

Thanks

dracae · 02-23-2006, 05:59 PM

That is what I would do.

kushalkoolwal · 02-23-2006, 06:28 PM

thanks dracae a lot. From now on I will try to following the mentioned procedure.

Thank you once again..