LinuxQuestions.org - Unable to compile kernel-2.6.x on Slackware 10.1

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Unable to compile kernel-2.6.x on Slackware 10.1 (https://www.linuxquestions.org/questions/slackware-14/unable-to-compile-kernel-2-6-x-on-slackware-10-1-a-358361/)

Quote:

Originally posted by Basel
I guess you mean "make oldconfig" or "make menuconfig"

No, I generally try to say what I mean - *both*. I find it easier to manage that way - determine the new options with oldconfig, customise with menuconfig.

Quote:

What does FB stand for?

Sorry, FrameBuffer - I can't do any better than to use a reference I saw in a post recently. Have a look here

Hello,

Do I have to compile all of the these drivers? I am currently configuring the kernel.
These are the default selections by Slackware-config-2.6.12.3

Device Drivers --->
ATA/ATAPI/MFM/RLL support --->

<*> AEC62XX chipset support
<*> ALI M15x3 chipset support
[ ] ALI M15x3 WDC support (DANGEROUS)
<*> AMD and nVidia IDE support
<*> ATI IXP chipset IDE support
<*> CMD64{3|6|8|9} chipset support
<*> Compaq Triflex IDE support
<*> CY82C693 chipset support
<*> Cyrix CS5510/20 MediaGX chipset support (VERY EXPERIMENTAL)
<*> Cyrix/National Semiconductor CS5530 MediaGX chipset support
<*> HPT34X chipset support
[ ] HPT34X AUTODMA support (EXPERIMENTAL)
<*> HPT36X/37X chipset support
< > National SCx200 chipset support
<*> Intel PIIXn chipsets support
< > IT821X IDE support (NEW)
< > NS87415 chipset support
<*> PROMISE PDC202{46|62|65|67} support[*] Special UDMA Feature
<*> PROMISE PDC202{68|69|70|71|75|76|77} support[*] Enable controller even if disabled by BIOS
<*> ServerWorks OSB4/CSB5/CSB6 chipsets support
<*> Silicon Image chipset support
<*> SiS5513 chipset support
<*> SLC90E66 chipset support
<M> Tekram TRM290 chipset support
<*> VIA82CXXX chipset support[*] Other IDE chipset support
--- Note: most of these also require special kernel boot parameters[*] Generic 4 drives/port support
<M> ALI M14xx support
<M> DTC-2278 support
<M> Holtek HT6560B support
<M> QDI QD65xx support
<M> UMC-8672 support
[ ] IGNORE word93 Validation BITS

I managed to compile the kernel :D
How can I make sure that I am running off the new kernel. Is it enough to use uname?

Code:

basel@slackware:~$ uname -a

Linux slackware 2.6.13 #1 Wed Aug 31 19:06:42 AST 2005 i686 unknown unknown GNU/Linux

I am not able to install nVidia now :(
Here is some output from /var/log/nvidia-installer.log

Code:

ERROR: Unable to load the kernel module 'nvidia.ko'.  This is most likely

      because the kernel module was built using the wrong kernel source files.

      Please make sure you have installed the kernel source files for your

      kernel; on Red Hat Linux systems, for example, be sure you have the

      'kernel-source' rpm installed.  If you know the correct kernel source

      files are installed, you may specify the kernel source path with the

      '--kernel-source-path' commandline option.

-> Kernel module load error: insmod: error inserting './usr/src/nv/nvidia.ko':

  -1 No such device

-> Kernel messages:

  NVRM: No NVIDIA graphics adapter probed!

  NVRM: The NVIDIA probe routine was not called for 1 device(s).

  NVRM: This can occur when a driver such as rivafb or rivatv was

  NVRM: loaded and obtained ownership of the NVIDIA device(s).

  NVRM: Try unloading the rivafb (and/or the rivatv) kernel module

  NVRM: (or reconfigure your kernel without rivafb support), then

  NVRM: try loading the NVIDIA kernel module again.

  NVRM: No NVIDIA graphics adapter probed!

  NVRM: The NVIDIA probe routine was not called for 1 device(s).

  NVRM: This can occur when a driver such as rivafb or rivatv was

  NVRM: loaded and obtained ownership of the NVIDIA device(s).

  NVRM: Try unloading the rivafb (and/or the rivatv) kernel module

  NVRM: (or reconfigure your kernel without rivafb support), then

  NVRM: try loading the NVIDIA kernel module again.

  NVRM: No NVIDIA gra

Quote:

Originally posted by Basel
Do I have to compile all of the these drivers? I am currently configuring the kernel.
These are the default selections by Slackware-config-2.6.12.3

This is *precisely* why people compile their own kernel - build for your own box. Throw out all the crap you don't need.

Quote:

How can I make sure that I am running off the new kernel. Is it enough to use uname?

Yep

As for nvidia, I don't use them, but they seem much better supported than ATI - have a look around the support sites. Including here on LQ.
I'd be taking note of those messages re FB selections - I hope you didn't select them all. It's usually a matter of picking the most relevant one.

hi i am using kernel 2.6.12.3 now it is working like charm (me too downloaded it from kernel.org )

start from 0 (do a fresh compilation)
untar the kernel to ur home dir mine is /home/build/linux-2.6.XXX
so u dont have to su, so tht, this folder u have all control

also dont do make oldconfig, u satart fresh config

me uses "make xconfig" tht will build necessary things when u run first time :)
doing first time dont go for much editting, first make all thing work, then u can remove or add or change to modules later
in the end i short listed all commands ;)

the black screen is due to frame buffer consol, dont make these things as modules make it built in
here is my config
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FONTS=y
# CONFIG_FONT_8x8 is not set
CONFIG_FONT_8x16=y

also file system support if u uses reiserfs u have to enable this in kernel make t built in
kernel panic may b due to (add scsi support theny have to be built in )
# CONFIG_BLK_DEV_IDE_SATA make built in Y

please edit ur lilo with corect vmlinuz

cd to your linux-2.6.12.3/ directory, then issue:
$ make xconfig (make your changes then save the file)
$ make
then su to root and
# cp System.map /boot/System.map-2.6.12.3 ; ln -sf /boot/System.map-2.6.12.3 /boot/System.map
# make modules_install
# cp arch/i386/boot/bzImage /boot/vmlinuz-2.6.12.3 (i uses this name)
# lilo
# reboot

best of luck

edit:now only i saw the 2nd page so :(

rkrishna,

I am glad to know that you managed to compile the kernel :)