Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
And finally below is my new .config file (2.6.8 kenel)
#
# SCSI device support
#
CONFIG_SCSI=m
CONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=m
CONFIG_CHR_DEV_ST=m
CONFIG_CHR_DEV_OSST=m
CONFIG_BLK_DEV_SR=m
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=m
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y
#
# SCSI Transport Attributes
#
CONFIG_SCSI_SPI_ATTRS=m
# CONFIG_SCSI_FC_ATTRS is not set
#
# SCSI low-level drivers
#
CONFIG_BLK_DEV_3W_XXXX_RAID=m
# CONFIG_SCSI_3W_9XXX is not set
CONFIG_SCSI_7000FASST=m
CONFIG_SCSI_ACARD=m
CONFIG_SCSI_AHA152X=m
CONFIG_SCSI_AHA1542=m
CONFIG_SCSI_AHA1740=m
CONFIG_SCSI_AACRAID=m
CONFIG_SCSI_AIC7XXX=m
CONFIG_AIC7XXX_CMDS_PER_DEVICE=253
CONFIG_AIC7XXX_RESET_DELAY_MS=15000
# CONFIG_AIC7XXX_PROBE_EISA_VL is not set
# CONFIG_AIC7XXX_BUILD_FIRMWARE is not set
CONFIG_AIC7XXX_DEBUG_ENABLE=y
CONFIG_AIC7XXX_DEBUG_MASK=0
CONFIG_AIC7XXX_REG_PRETTY_PRINT=y
CONFIG_AIC7XXX_REG_PRETTY_PRINT=y
CONFIG_SCSI_AIC7XXX_OLD=m
CONFIG_SCSI_AIC79XX=m
CONFIG_AIC79XX_CMDS_PER_DEVICE=253
CONFIG_AIC79XX_RESET_DELAY_MS=15000
# CONFIG_AIC79XX_BUILD_FIRMWARE is not set
CONFIG_AIC79XX_ENABLE_RD_STRM=y
# CONFIG_AIC79XX_DEBUG_ENABLE is not set
CONFIG_AIC79XX_DEBUG_MASK=0
CONFIG_AIC79XX_REG_PRETTY_PRINT=y
CONFIG_SCSI_DPT_I2O=m
CONFIG_SCSI_IN2000=m
CONFIG_SCSI_MEGARAID=m
# CONFIG_SCSI_SATA is not set
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=y
# CONFIG_SCSI_EATA_LINKED_COMMANDS is not set
CONFIG_SCSI_EATA_MAX_TAGS=16
CONFIG_SCSI_EATA_PIO=m
CONFIG_SCSI_FUTURE_DOMAIN=m
CONFIG_SCSI_GDTH=m
CONFIG_SCSI_GENERIC_NCR5380=m
# CONFIG_SCSI_GENERIC_NCR5380_MMIO is not set
# CONFIG_SCSI_GENERIC_NCR53C400 is not set
CONFIG_SCSI_IPS=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_53C700_IO_MAPPED=y
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 is not set
CONFIG_SCSI_PAS16=m
CONFIG_SCSI_PSI240I=m
CONFIG_SCSI_QLOGIC_FAS=m
CONFIG_SCSI_QLOGIC_ISP=m
CONFIG_SCSI_QLOGIC_FC=m
# CONFIG_SCSI_QLOGIC_FC_FIRMWARE is not set
CONFIG_SCSI_QLOGIC_1280=m
CONFIG_SCSI_QLA2XXX=m
# CONFIG_SCSI_QLA21XX is not set
# CONFIG_SCSI_QLA22XX is not set
# CONFIG_SCSI_QLA2300 is not set
# CONFIG_SCSI_QLA2322 is not set
# CONFIG_SCSI_QLA6312 is not set
# CONFIG_SCSI_QLA6322 is not set
CONFIG_SCSI_SIM710=m
CONFIG_SCSI_SYM53C416=m
# CONFIG_SCSI_DC395x is not set
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
title Red Hat Linux (2.6.8MiKeBigmem)
root (hd0,0)
kernel /vmlinuz-2.6.8MiKeBigmem ro root=LABEL=/ vga=791
initrd /initrd-2.6.8MiKeBigmem.img
title Red Hat Linux (2.6.8MiKesmp)
root (hd0,0)
kernel /vmlinuz-2.6.8MiKesmp ro root=LABEL=/ vga=791
initrd /initrd-2.6.8MiKesmp.img
title Red Hat Linux (2.4.20-8bigmem)
root (hd0,0)
kernel /vmlinuz-2.4.20-8bigmem ro root=LABEL=/ vga=791
initrd /initrd-2.4.20-8bigmem.img
title Red Hat Linux (2.4.20-8smp)
root (hd0,0)
kernel /vmlinuz-2.4.20-8smp ro root=LABEL=/ vga=791
initrd /initrd-2.4.20-8smp.img
My question is what is the reason why is it that when i use ny newly compiled kernel, i got a KERNEL panic ERROR:
Pls help me ive been doing this for a week and i am run out of ideas....
And finally below is my new .config file (2.6.8 kenel) (cropped a lot)
CONFIG_SCSI=m
CONFIG_BLK_DEV_SD=m
CONFIG_SCSI_GENERIC_NCR5380=m
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_SYM53C416=m
Notice that in your existing kernel there are no low level SCSI modules loaded. This is because the SCSI support is compiled into the kernel, rather than as modules, so that it is available to bring up any SCSI drives prior to loading modules. (Yes, the kernel itself probably comes off the SCSI drive, but, to oversimplify it, this has to do with the way IA32 systems boot up that gives them basic access to the drives prior to needing the kernel to have support for it.)
You need to compile the SCSI support INTO the new kernel as well. This means setting the appropriate options to Y and not M. I'm not sure which one is the correct one for your controller, but it should be one of the ones I didn't crop in this list, probably the CONFIG_SCSI_SYM53C8XX_2. In your current install, there should be a file in the /boot directory with a name like config-(current kernel version number) and in it you can look and see which low level SCSI options are set to [i]Y for your existing kernel.
Tnx for the quick reply, I dis what you told me, but still the same error occur. Kernel Panic
Below is the .config of the working kernel as i notice the driver:
CONFIG_SCSI_NCR53C8XX_SYNC=40
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_PCMCIA_NINJA_SCSI=m
Originally posted by mcalizo CONFIG_SCSI_SYM53C8XX_2=m
needs to be
Code:
CONFIG_SCSI_SYM53C8XX_2=y
Quote:
Originally posted by mcalizo My question is what is the reason why is it that when i use ny newly compiled kernel, i got a KERNEL panic ERROR:
Quote:
Originally posted by Darin This is because the SCSI support is compiled into the kernel, rather than as modules, so that it is available to bring up any SCSI drives prior to loading modules. (Yes, the kernel itself probably comes off the SCSI drive, but, to oversimplify it, this has to do with the way IA32 systems boot up that gives them basic access to the drives prior to needing the kernel to have support for it.)
Actually the SCSI controller is not compiled into the kernel for the 2.4 kernel. The SCSI controller modules is mptscsih as indicated in the posting from lsmod.
RH uses an initrd (Initial Ramdisk) which is the method used to load required modules during boot before the kernel is loaded. Did you recompile the modules? How did you create the new initrd?
Does the 2.6 kernel include support for the SCSI controller? Did you make modules, make modules_install?
Michaelk is correct, systems can use an initrd to load required modules, and that must be how the default Redhad kernel does it. I missed the mptscsih module, I have a system with an O/B Symbios SCSI and I just assumed yours was like mine and used the sym53c8xx low level driver. It is also possible to just compile the appropriate SCSI driver into the kernel, as you found out. I find the compiled in method simpler, but I'm partially biased since Slackware does it this way and the first time I tried to make a new initrd it failed miserably
Either way, your system is working and you and anyone else with a boot drive on SCSI now know two ways to make sure the system still boots after rebuilding the kernel. Compile the SCSI low level driver for the controller into the kernel, instead of as a module, or make an initrd image so the module can load.
After compiling a new kernel you should run this to create a new initrd (ramdisk) for your kernel. Typically I've seen it include the appropriate modules, however you can specify the modules you would like included with the --with=<module> directives.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.