Re: QLOGIC Fibre Channel init
On Thu, 26 Oct 2000, Klaus Naumann wrote: > Byeong-ryeol Kim wrote: > > > > On Thu, 26 Oct 2000, Klaus Naumann wrote: > > > > > I was having some little trouble with the QLOGIC Fibre Channel SCSI > > > cards. > > > The issue is, that I have a box with an internal SCSI controller/disk > > > and a QLOGIC card which is connected to an external RAID. The probelm > > > is, that the internal disk is my root disk but is the second in the > > > chain (sdb) after bootup. This gives a lot of problems, because it's > > > impossible to get the system to boot (LILO isn't working). > > > Since I've modified the hosts.c it's working perfectly (at least the > > > order is better now). Patch is attached. > > > Can anyone give a comment on that please ? > > > > > > Hello, > > Your patch would be good, but there is another simple method. > > Did you happen to make the BIOS of Qlogic FC adapter enable to > > boot the machine? > > If so, while POST, timely hit 'Ctrl + Q', and disable boot > > ability in BIOS setting of it. > > No, I have the bios of the controller disabled. > The problem with that is that on boot up (for lilo) the internal disk > is disk number one. But when I'm in the system and want to install lilo > it's disk number two - that's what lilo is complaining about on boot up. > (By spewing out an L and a 01 01 01 01 and so on). > Activating the bios of the QLOGIC (to make the internal disk appear > to be the 2nd one on bootup) didn't solve the problem too - I simply > got a message saying I should insert a system disk ;) Aha, I forgot to describe about making qlogic drivers as a module. While I had been setting and testing SAN switch(Brocade, Gadzoox), RAID with Qlogic 2100(or 2200A), I had the same experience that you described in the previous mail, and solved the problem by patching drivers/scsi/hosts.c as you did. It was a good solution. But, I became aware of the convenience and flexibility of modular drivers(or initrd) in this case. Because, I thought, whenever I do the same test or benchmarking, rebooting the system each is terrible. In that method, I experienced no problem such that you described in the previous E-mail. -- "Where there is a will, there is a way." [EMAIL PROTECTED] For the future of you and me!hitel: jinbo21 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
RE: QLOGIC Fibre Channel init
You can use an initial ramdisk (initrd), and specify the load order of your drivers (driver for internal disk first, qlogic driver second). That removes the dependency on the static link order in hosts.c. Thanks, Matt -Original Message- From: Klaus Naumann [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 26, 2000 7:23 AM Cc: [EMAIL PROTECTED] Subject: Re: QLOGIC Fibre Channel init > On Thu, 26 Oct 2000, Klaus Naumann wrote: > > > I was having some little trouble with the QLOGIC Fibre Channel SCSI > > cards. > > The issue is, that I have a box with an internal SCSI controller/disk > > and a QLOGIC card which is connected to an external RAID. The probelm > > is, that the internal disk is my root disk but is the second in the > > chain (sdb) after bootup. This gives a lot of problems, because it's > > impossible to get the system to boot (LILO isn't working). > > Since I've modified the hosts.c it's working perfectly (at least the > > order is better now). Patch is attached. > > Can anyone give a comment on that please ? > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: QLOGIC Fibre Channel init
On Thu, 26 Oct 2000 14:22:54 +0200, Klaus Naumann <[EMAIL PROTECTED]> wrote: >The problem with that is that on boot up (for lilo) the internal disk >is disk number one. But when I'm in the system and want to install lilo >it's disk number two - that's what lilo is complaining about on boot up. >(By spewing out an L and a 01 01 01 01 and so on). I missed the start of this thread but if it is just a mismatch between LILO and BIOS, this might help in lilo.conf. disk=/dev/sdb bios=0x80 Tells lilo that sdb is the boot disk. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: QLOGIC Fibre Channel init
Byeong-ryeol Kim wrote: > > On Thu, 26 Oct 2000, Klaus Naumann wrote: > > > I was having some little trouble with the QLOGIC Fibre Channel SCSI > > cards. > > The issue is, that I have a box with an internal SCSI controller/disk > > and a QLOGIC card which is connected to an external RAID. The probelm > > is, that the internal disk is my root disk but is the second in the > > chain (sdb) after bootup. This gives a lot of problems, because it's > > impossible to get the system to boot (LILO isn't working). > > Since I've modified the hosts.c it's working perfectly (at least the > > order is better now). Patch is attached. > > Can anyone give a comment on that please ? > > > Hello, > Your patch would be good, but there is another simple method. > Did you happen to make the BIOS of Qlogic FC adapter enable to > boot the machine? > If so, while POST, timely hit 'Ctrl + Q', and disable boot > ability in BIOS setting of it. No, I have the bios of the controller disabled. The problem with that is that on boot up (for lilo) the internal disk is disk number one. But when I'm in the system and want to install lilo it's disk number two - that's what lilo is complaining about on boot up. (By spewing out an L and a 01 01 01 01 and so on). Activating the bios of the QLOGIC (to make the internal disk appear to be the 2nd one on bootup) didn't solve the problem too - I simply got a message saying I should insert a system disk ;) CU, Klaus -- Klaus Naumann (mailto:[EMAIL PROTECTED]) http://www.mgnet.de/ Phone: ++49/8761727852 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: QLOGIC Fibre Channel init
On Thu, 26 Oct 2000, Klaus Naumann wrote: > I was having some little trouble with the QLOGIC Fibre Channel SCSI > cards. > The issue is, that I have a box with an internal SCSI controller/disk > and a QLOGIC card which is connected to an external RAID. The probelm > is, that the internal disk is my root disk but is the second in the > chain (sdb) after bootup. This gives a lot of problems, because it's > impossible to get the system to boot (LILO isn't working). > Since I've modified the hosts.c it's working perfectly (at least the > order is better now). Patch is attached. > Can anyone give a comment on that please ? Hello, Your patch would be good, but there is another simple method. Did you happen to make the BIOS of Qlogic FC adapter enable to boot the machine? If so, while POST, timely hit 'Ctrl + Q', and disable boot ability in BIOS setting of it. -- "Where there is a will, there is a way." [EMAIL PROTECTED] For the future of you and me!hitel: jinbo21 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
QLOGIC Fibre Channel init
Hi, I was having some little trouble with the QLOGIC Fibre Channel SCSI cards. The issue is, that I have a box with an internal SCSI controller/disk and a QLOGIC card which is connected to an external RAID. The probelm is, that the internal disk is my root disk but is the second in the chain (sdb) after bootup. This gives a lot of problems, because it's impossible to get the system to boot (LILO isn't working). Since I've modified the hosts.c it's working perfectly (at least the order is better now). Patch is attached. Can anyone give a comment on that please ? CU, Klaus -- Klaus Naumann (mailto:[EMAIL PROTECTED]) http://www.mgnet.de/ Phone: ++49/8761727852 diff -Nur linux.orig/drivers/scsi/hosts.c linux/drivers/scsi/hosts.c --- linux.orig/drivers/scsi/hosts.c Thu Oct 26 12:09:58 2000 +++ linux/drivers/scsi/hosts.c Thu Oct 26 12:09:46 2000 @@ -505,6 +505,12 @@ #ifdef CONFIG_SCSI_NCR53C406A /* 53C406A should come before QLOGIC */ NCR53c406a, #endif +#ifdef CONFIG_SCSI_SYM53C8XX /* [SYM|NCR]53C8XX should also be before QLOGIC */ +SYM53C8XX, +#endif +#ifdef CONFIG_SCSI_NCR53C8XX +NCR53C8XX, +#endif #ifdef CONFIG_SCSI_SYM53C416 SYM53C416, #endif @@ -531,12 +537,6 @@ #endif #ifdef CONFIG_SCSI_NCR53C7xx NCR53c7xx, -#endif -#ifdef CONFIG_SCSI_SYM53C8XX -SYM53C8XX, -#endif -#ifdef CONFIG_SCSI_NCR53C8XX -NCR53C8XX, #endif #ifdef CONFIG_SCSI_EATA_DMA EATA_DMA,
QLOGIC Fibre Channel init
Hi, I was having some little trouble with the QLOGIC Fibre Channel SCSI cards. The issue is, that I have a box with an internal SCSI controller/disk and a QLOGIC card which is connected to an external RAID. The probelm is, that the internal disk is my root disk but is the second in the chain (sdb) after bootup. This gives a lot of problems, because it's impossible to get the system to boot (LILO isn't working). Since I've modified the hosts.c it's working perfectly (at least the order is better now). Patch is attached. Can anyone give a comment on that please ? CU, Klaus -- Klaus Naumann (mailto:[EMAIL PROTECTED]) http://www.mgnet.de/ Phone: ++49/8761727852 diff -Nur linux.orig/drivers/scsi/hosts.c linux/drivers/scsi/hosts.c --- linux.orig/drivers/scsi/hosts.c Thu Oct 26 12:09:58 2000 +++ linux/drivers/scsi/hosts.c Thu Oct 26 12:09:46 2000 @@ -505,6 +505,12 @@ #ifdef CONFIG_SCSI_NCR53C406A /* 53C406A should come before QLOGIC */ NCR53c406a, #endif +#ifdef CONFIG_SCSI_SYM53C8XX /* [SYM|NCR]53C8XX should also be before QLOGIC */ +SYM53C8XX, +#endif +#ifdef CONFIG_SCSI_NCR53C8XX +NCR53C8XX, +#endif #ifdef CONFIG_SCSI_SYM53C416 SYM53C416, #endif @@ -531,12 +537,6 @@ #endif #ifdef CONFIG_SCSI_NCR53C7xx NCR53c7xx, -#endif -#ifdef CONFIG_SCSI_SYM53C8XX -SYM53C8XX, -#endif -#ifdef CONFIG_SCSI_NCR53C8XX -NCR53C8XX, #endif #ifdef CONFIG_SCSI_EATA_DMA EATA_DMA,
Re: QLOGIC Fibre Channel init
On Thu, 26 Oct 2000, Klaus Naumann wrote: I was having some little trouble with the QLOGIC Fibre Channel SCSI cards. The issue is, that I have a box with an internal SCSI controller/disk and a QLOGIC card which is connected to an external RAID. The probelm is, that the internal disk is my root disk but is the second in the chain (sdb) after bootup. This gives a lot of problems, because it's impossible to get the system to boot (LILO isn't working). Since I've modified the hosts.c it's working perfectly (at least the order is better now). Patch is attached. Can anyone give a comment on that please ? Hello, Your patch would be good, but there is another simple method. Did you happen to make the BIOS of Qlogic FC adapter enable to boot the machine? If so, while POST, timely hit 'Ctrl + Q', and disable boot ability in BIOS setting of it. -- "Where there is a will, there is a way." [EMAIL PROTECTED] For the future of you and me!hitel: jinbo21 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: QLOGIC Fibre Channel init
Byeong-ryeol Kim wrote: On Thu, 26 Oct 2000, Klaus Naumann wrote: I was having some little trouble with the QLOGIC Fibre Channel SCSI cards. The issue is, that I have a box with an internal SCSI controller/disk and a QLOGIC card which is connected to an external RAID. The probelm is, that the internal disk is my root disk but is the second in the chain (sdb) after bootup. This gives a lot of problems, because it's impossible to get the system to boot (LILO isn't working). Since I've modified the hosts.c it's working perfectly (at least the order is better now). Patch is attached. Can anyone give a comment on that please ? Hello, Your patch would be good, but there is another simple method. Did you happen to make the BIOS of Qlogic FC adapter enable to boot the machine? If so, while POST, timely hit 'Ctrl + Q', and disable boot ability in BIOS setting of it. No, I have the bios of the controller disabled. The problem with that is that on boot up (for lilo) the internal disk is disk number one. But when I'm in the system and want to install lilo it's disk number two - that's what lilo is complaining about on boot up. (By spewing out an L and a 01 01 01 01 and so on). Activating the bios of the QLOGIC (to make the internal disk appear to be the 2nd one on bootup) didn't solve the problem too - I simply got a message saying I should insert a system disk ;) CU, Klaus -- Klaus Naumann (mailto:[EMAIL PROTECTED]) http://www.mgnet.de/ Phone: ++49/8761727852 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: QLOGIC Fibre Channel init
On Thu, 26 Oct 2000 14:22:54 +0200, Klaus Naumann [EMAIL PROTECTED] wrote: The problem with that is that on boot up (for lilo) the internal disk is disk number one. But when I'm in the system and want to install lilo it's disk number two - that's what lilo is complaining about on boot up. (By spewing out an L and a 01 01 01 01 and so on). I missed the start of this thread but if it is just a mismatch between LILO and BIOS, this might help in lilo.conf. disk=/dev/sdb bios=0x80 Tells lilo that sdb is the boot disk. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: QLOGIC Fibre Channel init
On Thu, 26 Oct 2000, Klaus Naumann wrote: Byeong-ryeol Kim wrote: On Thu, 26 Oct 2000, Klaus Naumann wrote: I was having some little trouble with the QLOGIC Fibre Channel SCSI cards. The issue is, that I have a box with an internal SCSI controller/disk and a QLOGIC card which is connected to an external RAID. The probelm is, that the internal disk is my root disk but is the second in the chain (sdb) after bootup. This gives a lot of problems, because it's impossible to get the system to boot (LILO isn't working). Since I've modified the hosts.c it's working perfectly (at least the order is better now). Patch is attached. Can anyone give a comment on that please ? Hello, Your patch would be good, but there is another simple method. Did you happen to make the BIOS of Qlogic FC adapter enable to boot the machine? If so, while POST, timely hit 'Ctrl + Q', and disable boot ability in BIOS setting of it. No, I have the bios of the controller disabled. The problem with that is that on boot up (for lilo) the internal disk is disk number one. But when I'm in the system and want to install lilo it's disk number two - that's what lilo is complaining about on boot up. (By spewing out an L and a 01 01 01 01 and so on). Activating the bios of the QLOGIC (to make the internal disk appear to be the 2nd one on bootup) didn't solve the problem too - I simply got a message saying I should insert a system disk ;) Aha, I forgot to describe about making qlogic drivers as a module. While I had been setting and testing SAN switch(Brocade, Gadzoox), RAID with Qlogic 2100(or 2200A), I had the same experience that you described in the previous mail, and solved the problem by patching drivers/scsi/hosts.c as you did. It was a good solution. But, I became aware of the convenience and flexibility of modular drivers(or initrd) in this case. Because, I thought, whenever I do the same test or benchmarking, rebooting the system each is terrible. In that method, I experienced no problem such that you described in the previous E-mail. -- "Where there is a will, there is a way." [EMAIL PROTECTED] For the future of you and me!hitel: jinbo21 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
