LinuxQuestions.org
Help answer threads with 0 replies.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 12-04-2004, 02:04 AM   #1
mcalizo
Member
 
Registered: Aug 2003
Location: Manila, Philippines
Distribution: RH
Posts: 43

Rep: Reputation: 15
Kernel upgrade problem on SCSI


Hi all,

I have been upgrading my RH9 Kernel listed below:

[root@intDNS mike]# uname -a
Linux intDNS 2.4.20-8bigmem #1 SMP Thu Mar 13 17:32:29 EST 2003 i686 i686 i386 GNU/Linux
[root@intDNS mike]#

Here are the modules that currently enable on kernel my 2.4.20-8bigmem:


[root@intDNS mike]# /sbin/lsmod
Module Size Used by Not tainted
loop 12856 0 (autoclean)
autofs 13684 0 (autoclean) (unused)
iptable_filter 2412 0 (autoclean) (unused)
ip_tables 15864 1 [iptable_filter]
tg3 53128 1
mousedev 5656 0 (unused)
keybdev 2976 0 (unused)
hid 22308 0 (unused)
input 6208 0 [mousedev keybdev hid]
usb-ohci 23560 0 (unused)
usbcore 82624 1 [hid usb-ohci]
ext3 73376 6
jbd 56272 6 [ext3]
mptscsih 40016 7
mptbase 43488 3 [mptscsih]
sd_mod 13452 14
scsi_mod 111224 2 [mptscsih sd_mod]

Here are the LSPCI output:

[root@intDNS linux-2.6.8]# /sbin/lspci
00:00.0 Host bridge: ServerWorks CNB20-HE Host Bridge (rev 33)
00:00.1 Host bridge: ServerWorks CNB20-HE Host Bridge
00:00.2 Host bridge: ServerWorks CNB20-HE Host Bridge
00:06.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
00:0f.0 Host bridge: ServerWorks CSB5 South Bridge (rev 93)
00:0f.1 IDE interface: ServerWorks CSB5 IDE Controller (rev 93)
00:0f.2 USB Controller: ServerWorks OSB4/CSB5 OHCI USB Controller (rev 05)
00:0f.3 ISA bridge: ServerWorks GCLE Host Bridge
00:10.0 Host bridge: ServerWorks: Unknown device 0101 (rev 05)
00:10.2 Host bridge: ServerWorks: Unknown device 0101 (rev 05)
00:11.0 Host bridge: ServerWorks: Unknown device 0101 (rev 05)
00:11.2 Host bridge: ServerWorks: Unknown device 0101 (rev 05)
02:03.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5703 Gigabit Ethernet (rev 02)
04:04.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5703 Gigabit Ethernet (rev 02)
06:08.0 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (Copper) (rev 01)
06:08.1 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (Copper) (rev 01)
08:07.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 (rev 07)
08:07.1 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 (rev 07)
[root@intDNS linux-2.6.8]#

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

#
# PCMCIA SCSI adapter support
#
CONFIG_PCMCIA_AHA152X=m
CONFIG_PCMCIA_FDOMAIN=m
CONFIG_PCMCIA_NINJA_SCSI=m
CONFIG_PCMCIA_QLOGIC=m


HERE ARE MY GRUB.CONF FILE:


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....

Tnx
 
Old 12-04-2004, 04:10 AM   #2
Darin
Senior Member
 
Registered: Jan 2003
Location: Portland, OR USA
Distribution: Slackware, SLAX, Gentoo, RH/Fedora
Posts: 1,024

Rep: Reputation: 45
Re: Kernel upgrade problem on SCSI

Quote:
Originally posted by mcalizo
[root@intDNS mike]# /sbin/lsmod
Module Size Used by Not tainted
loop 12856 0 (autoclean)
autofs 13684 0 (autoclean) (unused)
iptable_filter 2412 0 (autoclean) (unused)
ip_tables 15864 1 [iptable_filter]
tg3 53128 1
mousedev 5656 0 (unused)
keybdev 2976 0 (unused)
hid 22308 0 (unused)
input 6208 0 [mousedev keybdev hid]
usb-ohci 23560 0 (unused)
usbcore 82624 1 [hid usb-ohci]
ext3 73376 6
jbd 56272 6 [ext3]
mptscsih 40016 7
mptbase 43488 3 [mptscsih]
sd_mod 13452 14
scsi_mod 111224 2 [mptscsih sd_mod]

Here are the LSPCI output:

[root@intDNS linux-2.6.8]# /sbin/lspci
(cropped)
08:07.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 (rev 07)
08:07.1 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 (rev 07)

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.

Cheers!
 
Old 12-04-2004, 04:45 AM   #3
mcalizo
Member
 
Registered: Aug 2003
Location: Manila, Philippines
Distribution: RH
Posts: 43

Original Poster
Rep: Reputation: 15
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

What do you think is happening?
 
Old 12-04-2004, 08:50 AM   #4
Darin
Senior Member
 
Registered: Jan 2003
Location: Portland, OR USA
Distribution: Slackware, SLAX, Gentoo, RH/Fedora
Posts: 1,024

Rep: Reputation: 45
Quote:
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.)
 
Old 12-04-2004, 09:21 AM   #5
michaelk
Moderator
 
Registered: Aug 2002
Posts: 25,680

Rep: Reputation: 5894Reputation: 5894Reputation: 5894Reputation: 5894Reputation: 5894Reputation: 5894Reputation: 5894Reputation: 5894Reputation: 5894Reputation: 5894Reputation: 5894
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?

Last edited by michaelk; 12-04-2004 at 09:28 AM.
 
Old 12-04-2004, 01:25 PM   #6
mcalizo
Member
 
Registered: Aug 2003
Location: Manila, Philippines
Distribution: RH
Posts: 43

Original Poster
Rep: Reputation: 15
I solve the problem by editing my .config file and enabling scsi driver

CONFIG_SCSI_SYM53C8XX_2=y

And i also edit my grub.conf by adding:

hdd=ide-scsi

Tnx a lot guys...
 
Old 12-05-2004, 07:56 AM   #7
Darin
Senior Member
 
Registered: Jan 2003
Location: Portland, OR USA
Distribution: Slackware, SLAX, Gentoo, RH/Fedora
Posts: 1,024

Rep: Reputation: 45
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.
 
Old 08-03-2006, 09:09 PM   #8
flipbit
LQ Newbie
 
Registered: Aug 2006
Location: Madison, AL
Distribution: most
Posts: 1

Rep: Reputation: 0
mkinitrd

You can also use mkinitrd to create your ramdisks for you.

usage: mkinitrd [--version] [-v] [-f] [--preload <module>]
[--omit-scsi-modules] [--omit-raid-modules]
[--omit-lvm-modules] [--with=<module>] [--image-version]
[--fstab=<fstab>] [--nocompress] [--builtin=<module>]
[--nopivot] <initrd-image> <kernel-version>

(ex: mkinitrd /boot/initrd-2.2.5-15.img 2.2.5-15)

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.

- Mike
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Problem with driver SCSI on kernel boot manstt Linux - Enterprise 2 11-22-2005 11:20 AM
Problem with AIC7880 SCSI chipset and kernel 2.6.x Filosofem Linux - Hardware 0 05-04-2005 02:52 PM
Problem with symbios SCSI and 2.6 kernel series (?) GD_19 Linux - Hardware 2 04-17-2005 09:25 PM
Box wont boot after kernel upgrade "Dump Card State Ends" error with scsi card abefroman Mandriva 0 03-25-2004 03:42 PM
Upgrade Redhat 9 to 2.6 kernel with tekram dc395 scsi controller jimieee Linux - Newbie 0 10-19-2003 03:45 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 03:04 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration