Unable to compile kernel-2.6.x on Slackware 10.1
 

Hello,

Could anyone please help me to compile kernel-2.6.x on Slackware 10.1? I have tried several guides but all my attempts have failed so far. My last attempt was with kernel-2.6.13.tar.bz2 from kernel.org and config-2.6.13 from /testing.
Here is a list of my system specifications:

Processor: AMD64 Athlon 3000+ 939 Socket
Mainboard: MSI K8N Neo2
HD: Serial ATA 200GB
RAM: 1GB DDR
AGP: nVidia FX5200-TD128 MB DDR 8X
Monitor: Samsung TFI700
Printer: HP LaserJet1100
CDs Drivers: GYGABYTE DVD-RW and Samsung CD-R
Modem: External USRobotics – serial port /dev/ttyS1
External USB2.0 HD SATA

Thanks,
Basel Mahdi

Since you don't tell us what is the problem we cannot help you. Take a look at this guide to help you upgrade your kernel. Make sure you meet the requirements of Step 3.

Regards

I get "Kernel panic" most of the times. With other compilations I get a blank screen after selecting the new kernel from Lilo.

It sounds drivers for SATA or your filesystem (etx3,reseir etc...) are not loaded at boot time.
From your post I understand you compiled the kernel from scratch using a config file from Slackware site.
Make sure the required drivers (SATA and filesystem in use) are not compiled as loadable modules
Not sure, but using kernel packages from Slackware you should set up an initrd image which includes the required modules for correct booting. (this happens for sure with 2.6.7 and 2.6.10 kernel packages).
Make also sure your /etc/lilo.conf is properly set up. If using SATA drives you must indicate the root partition as /sdax since SATA drives are recognised as scsi block dev.
Hope this helps
Ciao

That is a possibility.
That is true. I got the kernel from kernel.org and the config file from Slackware site.
I did that.
I guess this does not apply to me since I am using a kernel from kernel.org
I did that as well.

What do you think the problem is folk? :confused:

This should be the config-2.6.13 file from slack
SCSI low-level drivers
#
CONFIG_BLK_DEV_3W_XXXX_RAID=m
CONFIG_SCSI_3W_9XXX=m
CONFIG_SCSI_7000FASST=m
CONFIG_SCSI_ACARD=m
CONFIG_SCSI_AHA152X=m
CONFIG_SCSI_AHA1542=m
CONFIG_SCSI_AACRAID=m
CONFIG_SCSI_AIC7XXX=m
CONFIG_AIC7XXX_CMDS_PER_DEVICE=4
CONFIG_AIC7XXX_RESET_DELAY_MS=15000
# CONFIG_AIC7XXX_DEBUG_ENABLE is not set
CONFIG_AIC7XXX_DEBUG_MASK=0
# CONFIG_AIC7XXX_REG_PRETTY_PRINT is not set
CONFIG_SCSI_AIC7XXX_OLD=m
CONFIG_SCSI_AIC79XX=m
CONFIG_AIC79XX_CMDS_PER_DEVICE=4
CONFIG_AIC79XX_RESET_DELAY_MS=15000
# CONFIG_AIC79XX_ENABLE_RD_STRM is not set
# CONFIG_AIC79XX_DEBUG_ENABLE is not set
CONFIG_AIC79XX_DEBUG_MASK=0
# CONFIG_AIC79XX_REG_PRETTY_PRINT is not set
CONFIG_SCSI_DPT_I2O=m
CONFIG_SCSI_IN2000=m
CONFIG_MEGARAID_NEWGEN=y
CONFIG_MEGARAID_MM=m
CONFIG_MEGARAID_MAILBOX=m
CONFIG_SCSI_SATA=y
CONFIG_SCSI_SATA_AHCI=m
CONFIG_SCSI_SATA_SVW=m
CONFIG_SCSI_ATA_PIIX=m
CONFIG_SCSI_SATA_NV=m
CONFIG_SCSI_SATA_PROMISE=m
CONFIG_SCSI_SATA_QSTOR=m
CONFIG_SCSI_SATA_SX4=m
CONFIG_SCSI_SATA_SIL=m
CONFIG_SCSI_SATA_SIS=m
CONFIG_SCSI_SATA_ULI=m
CONFIG_SCSI_SATA_VIA=m
CONFIG_SCSI_SATA_VITESSE=m
CONFIG_SCSI_BUSLOGIC=m
# CONFIG_SCSI_OMIT_FLASHPOINT is not set
CONFIG_SCSI_DMX3191D=m
CONFIG_SCSI_DTC3280=m
CONFIG_SCSI_EATA=m
# CONFIG_SCSI_EATA_TAGGED_QUEUE is not set
# CONFIG_SCSI_EATA_LINKED_COMMANDS is not set
CONFIG_SCSI_EATA_MAX_TAGS=16
CONFIG_SCSI_FUTURE_DOMAIN=m
CONFIG_SCSI_GDTH=m
CONFIG_SCSI_GENERIC_NCR5380=m
CONFIG_SCSI_GENERIC_NCR5380_MMIO=m
CONFIG_SCSI_GENERIC_NCR53C400=y
CONFIG_SCSI_IPS=m
CONFIG_SCSI_INITIO=m
CONFIG_SCSI_INIA100=m
CONFIG_SCSI_PPA=m
CONFIG_SCSI_IMM=m
# CONFIG_SCSI_IZIP_EPP16 is not set
# CONFIG_SCSI_IZIP_SLOW_CTR is not set
CONFIG_SCSI_NCR53C406A=m
CONFIG_SCSI_SYM53C8XX_2=m
CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1
CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16
CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64
# CONFIG_SCSI_SYM53C8XX_IOMAPPED is not set
CONFIG_SCSI_IPR=m
# CONFIG_SCSI_IPR_TRACE is not set
# CONFIG_SCSI_IPR_DUMP is not set
CONFIG_SCSI_PAS16=m
CONFIG_SCSI_PSI240I=m
CONFIG_SCSI_QLOGIC_FAS=m
CONFIG_SCSI_QLOGIC_FC=m
# CONFIG_SCSI_QLOGIC_FC_FIRMWARE is not set
CONFIG_SCSI_QLOGIC_1280=m
# CONFIG_SCSI_QLOGIC_1280_1040 is not set
CONFIG_SCSI_QLA2XXX=y
CONFIG_SCSI_QLA21XX=m
CONFIG_SCSI_QLA22XX=m
CONFIG_SCSI_QLA2300=m
CONFIG_SCSI_QLA2322=m
CONFIG_SCSI_QLA6312=m
CONFIG_SCSI_LPFC=m
CONFIG_SCSI_SYM53C416=m
CONFIG_SCSI_DC395x=m
CONFIG_SCSI_DC390T=m
CONFIG_SCSI_T128=m
CONFIG_SCSI_U14_34F=m
# CONFIG_SCSI_U14_34F_TAGGED_QUEUE is not set
# CONFIG_SCSI_U14_34F_LINKED_COMMANDS is not set
CONFIG_SCSI_U14_34F_MAX_TAGS=8
CONFIG_SCSI_ULTRASTOR=m
CONFIG_SCSI_NSP32=m
CONFIG_SCSI_DEBUG=m

So SATA controllers drivers seem compiled as loadable modules. I'd try to get them built in
Also check you filesystem drivers are not the same
Ciao

Ciao,

Do I need to install of the low-level driver for SCSI?

EDIT: I have just noticed that Slackware 10.1 uses udev version 050 while the required version by kernel2.6.13 is 058.Will the compilation work with udev 050?

Yes, you should. Same happens for IDE controllers.
Sorry, I don't know what UDEV version is required for 2.6.13 kernel, I guess updating doesn't hurt the system.... (usually)
Ciao

Hey Basel.

I have a SATA HD and a nForce 2 MoBo and I run a 2.6.12.5 Kernel on it.

I only compiled the following SCSI low-level drivers into the Kernel:

CONFIG_SCSI_SATA=y
CONFIG_SCSI_SATA_PROMISE=y
CONFIG_SCSI_QLA2XXX=y

Hope that helps.



Oops, just realised, you got an external USB2 SATA drive. Then things might be totally different.

Are you booting off the ramdisk? I had the same problem until I set lilo to boot from a initrd and edited the fstab and changed it to sda1 from hda1.

Could anyone comment of udev? Is it safe to update it?
I will give it a try.

I don't think so. I did not add an entry for initrd in lilo.conf for the new kernel.

READ THIS? This was my problem.
ftp://mirrors.usc.edu/pub/linux/dist.../README.initrd

Thanks jnorcal, I will give it a try today afternoon.
What about udev? Could anyone comment on that?

Well, seeing as how I was *SO* far out of date (2.6.11.5), this afternoon I figured I'd better get 2.6.13, and see if I had any problems.
Nope - other than running out of (disk) space.

Compiled (and ran) fine, udev shouldn't be an issue.

I've never used Pats configs for 2.6.*, except the first time when I used the 2.4 config from 10.1 to do my initial 2.6 build.
I just take the current config over, then do a "make oldconfig", "make menuconfig", etc ...

Worked fine, as I said.
If you are getting panics, we'd better see some messages if we are to help you. If you compile everything in, you don't need an initrd - I've never used one except on my first foray in Linux with RH9.
The blank screen is usually a FB issue with 2.6 kernels - there should be a post here in Slackware with all the options you need.

I guess you mean "make oldconfig" or "make menuconfig"
What does FB stand for?