How to build a RedHat driver disk (fusion mpt)

How to build a RedHat driver disk (fusion mpt)

[Nir Livni]

Hi all,

I am trying to install RedHat Advanced Server 2.1 Developer Edition on my
Dell PowerEdge 1750, who needs the fusion mpt scsi driver.

Unfortunately, I could not find any driver disk for this kernel
(2.4.9-e.5smp).
This version is not supported by RedHat.

I would like to know how can I build a driver disk for this kernel, using
the driver sources I downloaded from LSI Logic site.

Thanks,
Nir

RE: How to build a RedHat driver disk (fusion mpt)]]

[Nir Livni]

So far so good...
That's almost identical to what I've done.
I took the original driver disk (2.4.9-e.3smp), and replaced the modname.o with a compiled modname.o of my kernel.
RedHat identifies the modules in the driver disk, but when I ask to load the driver (using linux dd noprobe when installing) - 
I always get "failed to insert modname.o module".

I suspect I do not compile the module as I should.

The kernel rpm is kernel-smp-2.4.9-e.5.i686.rpm.

I installed this rpm on a temporary smp PC, with an IDE controller.
I uploaded the sources and tried to follow the build instructions, with no special configuration.

The replaced the *.o files in the disk with my new built modules. But still - no good.

Any suggestions ?

Thanks for the effort,
Nir

> 
> 
> I've asked my colleague who does all the drivers ...
> 
> > Wilck Martin wrote:
> > 
> > >>Nir Livni wrote:
> >  >>I would like to know how can I build a driver disk for 
> this kernel,
> > 
> > create a driectory structure that looks like this
> > 
> > 2.4.9-e.5
> >         modname.o
> >         ...
> > 2.4.9-e.5BOOT
> >         modname.o
> >         ...
> > 2.4.9-e.5smp
> >         modname.o
> >         ...
> > ...
> > 
> > Of course, the respective .o files must have been compiled 
> against a 
> > properly configured kernel. "modname" stands for the name of your 
> > driver.
> > 
> > At the top of that structure, create a compressed cpio archive like
> > this:
> > 
> > find . -depth | cpio -H crc 2>/dev/null | gzip -qc - >modules.cgz
> > 
> > copy the file "modules.cgz" to a DOS- or ext2-formatted floppy. 
> > Besides "modules.cgz", the floppy must contain
> > 
> > 1. a file "modinfo" in the following format:
> > 
> > modname
> >         scsi
> >         "description of driver"
> > 
> > Caution: TABs at the beginning line 2 and 3!
> > 
> > 2. a file "modules.dep" in the following format:
> > modname:        scsi_mod
> > 
> > (scsi_mod is usually the only prerequisite needed)
> > 
> > 3. a file "pcitable" in the following format:
> > 0xdead  0xbeef  "modname"       "description of device"
> > ...
> > 
> > Caution: TAB as field separator!
> > This list must contain the PCI vendor and device IDs of  
> your device 
> > in the 1st and 2nd field. The easiest way to obtain these is from an
> > existing driver disk for a different kernel. Alternatively, you can
> > read
> > the driver source to find them out.
> > 
> > 4. a file called "rhdd-6.1" with a free-format description
> > of the floppy
> > 
> > 5. an empty file called "up"
> > 
> > Good luck,
> > Martin
> > 
> > --
> > Martin Wilck                Phone: +49 5251 8 15113
> > Fujitsu Siemens Computers   Fax:   +49 5251 8 20409
> > Heinz-Nixdorf-Ring 1        mailto:Martin.Wilck@Fujitsu-Siemens.com
> > D-33106 Paderborn           http://www.fujitsu-siemens.com/primergy
> 
> -- 
> Josef Möllers (Pinguinpfleger bei FSC)
> 	If failure had no penalty success would not be a prize
> 						-- T.  Pratchett
> -
> To unsubscribe from this list: send the line "unsubscribe 
> linux-scsi" in the body of a message to 
> majordomo@vger.kernel.org More majordomo info at  
> http://vger.kernel.org/majordomo-info.html
> 
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: How to build a RedHat driver disk (fusion mpt)]]

[Josef Möllers]

> Nir Livni wrote:
> 
> So far so good...
> That's almost identical to what I've done.
> I took the original driver disk (2.4.9-e.3smp), and replaced the
> modname.o with a compiled modname.o of my kernel.
> RedHat identifies the modules in the driver disk, but when I ask to
> load the driver (using linux dd noprobe when installing) -
> 
> I always get "failed to insert modname.o module".

You should be able to get some more information by switching to an
alternate console.

> I suspect I do not compile the module as I should.
> 
> The kernel rpm is kernel-smp-2.4.9-e.5.i686.rpm.
> 
> I installed this rpm on a temporary smp PC, with an IDE controller.
> I uploaded the sources and tried to follow the build instructions,
> with no special configuration.

As Martin wrote, you do need to use the exact configuration of the
kernel.
If you have the kernel source installed on y system, check the
/usr/src/linux/configs directory. There should be a file ...BOOT...
which you should use as the .config file for your installation kernel.

> The replaced the *.o files in the disk with my new built modules. But
> still - no good.

> > I've asked my colleague who does all the drivers ...
> >
> > > Wilck Martin wrote:
> > >
> > > >>Nir Livni wrote:
> > >  >>I would like to know how can I build a driver disk for
> > this kernel,
> > >
> > > create a driectory structure that looks like this
> > >
> > > 2.4.9-e.5
> > >         modname.o
> > >         ...
> > > 2.4.9-e.5BOOT
> > >         modname.o
> > >         ...
> > > 2.4.9-e.5smp
> > >         modname.o
> > >         ...
> > > ...
> > >
> > > Of course, the respective .o files must have been compiled
> > against a
> > > properly configured kernel. "modname" stands for the name of your
> > > driver.
> > >
> > > At the top of that structure, create a compressed cpio archive
> like
> > > this:
> > >
> > > find . -depth | cpio -H crc 2>/dev/null | gzip -qc - >modules.cgz
> > >
> > > copy the file "modules.cgz" to a DOS- or ext2-formatted floppy.
> > > Besides "modules.cgz", the floppy must contain
> > >
> > > 1. a file "modinfo" in the following format:
> > >
> > > modname
> > >         scsi
> > >         "description of driver"
> > >
> > > Caution: TABs at the beginning line 2 and 3!
> > >
> > > 2. a file "modules.dep" in the following format:
> > > modname:        scsi_mod
> > >
> > > (scsi_mod is usually the only prerequisite needed)
> > >
> > > 3. a file "pcitable" in the following format:
> > > 0xdead  0xbeef  "modname"       "description of device"
> > > ...
> > >
> > > Caution: TAB as field separator!
> > > This list must contain the PCI vendor and device IDs of
> > your device
> > > in the 1st and 2nd field. The easiest way to obtain these is from
> an
> > > existing driver disk for a different kernel. Alternatively, you
> can
> > > read
> > > the driver source to find them out.
> > >
> > > 4. a file called "rhdd-6.1" with a free-format description
> > > of the floppy
> > >
> > > 5. an empty file called "up"
> > >
> > > Good luck,
> > > Martin
> > >
> > > --
> > > Martin Wilck                Phone: +49 5251 8 15113
> > > Fujitsu Siemens Computers   Fax:   +49 5251 8 20409
> > > Heinz-Nixdorf-Ring 1
> mailto:Martin.Wilck@Fujitsu-Siemens.com
> > > D-33106 Paderborn
> http://www.fujitsu-siemens.com/primergy
> >
> > --
> > Josef Möllers (Pinguinpfleger bei FSC)
> >       If failure had no penalty success would not be a prize
> >                                               -- T.  Pratchett
> > -
> > To unsubscribe from this list: send the line "unsubscribe
> > linux-scsi" in the body of a message to
> > majordomo@vger.kernel.org More majordomo info at
> > http://vger.kernel.org/majordomo-info.html
> >

-- 
Josef Möllers (Pinguinpfleger bei FSC)
	If failure had no penalty success would not be a prize
						-- T.  Pratchett
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

RE: How to build a RedHat driver disk (fusion mpt)]]

[Nir Livni]

I am trying to compile the mpt modules again.
It seems that kernel < 2.4.18 require a kernel patch to support fusion mpt.

I used make oldconfig to reconfigure the kernel, and added the MPT FUSION support for modules.

How can I re-create the kernel rpm , so I can replace the rpm exists in my installation cd ?

Thanks,
Nir

> 
> 
> > Nir Livni wrote:
> > 
> > So far so good...
> > That's almost identical to what I've done.
> > I took the original driver disk (2.4.9-e.3smp), and replaced the 
> > modname.o with a compiled modname.o of my kernel. RedHat identifies 
> > the modules in the driver disk, but when I ask to load the driver 
> > (using linux dd noprobe when installing) -
> > 
> > I always get "failed to insert modname.o module".
> 
> You should be able to get some more information by switching 
> to an alternate console.
> 
> > I suspect I do not compile the module as I should.
> > 
> > The kernel rpm is kernel-smp-2.4.9-e.5.i686.rpm.
> > 
> > I installed this rpm on a temporary smp PC, with an IDE 
> controller. I 
> > uploaded the sources and tried to follow the build 
> instructions, with 
> > no special configuration.
> 
> As Martin wrote, you do need to use the exact configuration 
> of the kernel. If you have the kernel source installed on y 
> system, check the /usr/src/linux/configs directory. There 
> should be a file ...BOOT... which you should use as the 
> .config file for your installation kernel.
> 
> > The replaced the *.o files in the disk with my new built 
> modules. But 
> > still - no good.
> 
> > > I've asked my colleague who does all the drivers ...
> > >
> > > > Wilck Martin wrote:
> > > >
> > > > >>Nir Livni wrote:
> > > >  >>I would like to know how can I build a driver disk for
> > > this kernel,
> > > >
> > > > create a driectory structure that looks like this
> > > >
> > > > 2.4.9-e.5
> > > >         modname.o
> > > >         ...
> > > > 2.4.9-e.5BOOT
> > > >         modname.o
> > > >         ...
> > > > 2.4.9-e.5smp
> > > >         modname.o
> > > >         ...
> > > > ...
> > > >
> > > > Of course, the respective .o files must have been compiled
> > > against a
> > > > properly configured kernel. "modname" stands for the 
> name of your 
> > > > driver.
> > > >
> > > > At the top of that structure, create a compressed cpio archive
> > like
> > > > this:
> > > >
> > > > find . -depth | cpio -H crc 2>/dev/null | gzip -qc - 
> >modules.cgz
> > > >
> > > > copy the file "modules.cgz" to a DOS- or ext2-formatted floppy. 
> > > > Besides "modules.cgz", the floppy must contain
> > > >
> > > > 1. a file "modinfo" in the following format:
> > > >
> > > > modname
> > > >         scsi
> > > >         "description of driver"
> > > >
> > > > Caution: TABs at the beginning line 2 and 3!
> > > >
> > > > 2. a file "modules.dep" in the following format:
> > > > modname:        scsi_mod
> > > >
> > > > (scsi_mod is usually the only prerequisite needed)
> > > >
> > > > 3. a file "pcitable" in the following format:
> > > > 0xdead  0xbeef  "modname"       "description of device"
> > > > ...
> > > >
> > > > Caution: TAB as field separator!
> > > > This list must contain the PCI vendor and device IDs of
> > > your device
> > > > in the 1st and 2nd field. The easiest way to obtain 
> these is from
> > an
> > > > existing driver disk for a different kernel. Alternatively, you
> > can
> > > > read
> > > > the driver source to find them out.
> > > >
> > > > 4. a file called "rhdd-6.1" with a free-format 
> description of the 
> > > > floppy
> > > >
> > > > 5. an empty file called "up"
> > > >
> > > > Good luck,
> > > > Martin
> > > >
> > > > --
> > > > Martin Wilck                Phone: +49 5251 8 15113
> > > > Fujitsu Siemens Computers   Fax:   +49 5251 8 20409
> > > > Heinz-Nixdorf-Ring 1
> > mailto:Martin.Wilck@Fujitsu-Siemens.com
> > > > D-33106 Paderborn
> > http://www.fujitsu-siemens.com/primergy
> > >
> > > --
> > > Josef Möllers (Pinguinpfleger bei FSC)
> > >       If failure had no penalty success would not be a prize
> > >                                               -- T.  Pratchett
> > > -
> > > To unsubscribe from this list: send the line "unsubscribe 
> > > linux-scsi" in the body of a message to majordomo@vger.kernel.org 
> > > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > >
> 
> -- 
> Josef Möllers (Pinguinpfleger bei FSC)
> 	If failure had no penalty success would not be a prize
> 						-- T.  Pratchett
> 
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: How to build a RedHat driver disk (fusion mpt)]]

[Josef Möllers]

> Nir Livni wrote:
> 
> I am trying to compile the mpt modules again.
> It seems that kernel < 2.4.18 require a kernel patch to support fusion
> mpt.

I can't help any further.
Sorry.

> I used make oldconfig to reconfigure the kernel, and added the MPT
> FUSION support for modules.
> 
> How can I re-create the kernel rpm , so I can replace the rpm exists
> in my installation cd ?
> 
> Thanks,
> Nir
> 
> >
> >
> > > Nir Livni wrote:
> > >
> > > So far so good...
> > > That's almost identical to what I've done.
> > > I took the original driver disk (2.4.9-e.3smp), and replaced the
> > > modname.o with a compiled modname.o of my kernel. RedHat
> identifies
> > > the modules in the driver disk, but when I ask to load the driver
> > > (using linux dd noprobe when installing) -
> > >
> > > I always get "failed to insert modname.o module".
> >
> > You should be able to get some more information by switching
> > to an alternate console.
> >
> > > I suspect I do not compile the module as I should.
> > >
> > > The kernel rpm is kernel-smp-2.4.9-e.5.i686.rpm.
> > >
> > > I installed this rpm on a temporary smp PC, with an IDE
> > controller. I
> > > uploaded the sources and tried to follow the build
> > instructions, with
> > > no special configuration.
> >
> > As Martin wrote, you do need to use the exact configuration
> > of the kernel. If you have the kernel source installed on y
> > system, check the /usr/src/linux/configs directory. There
> > should be a file ...BOOT... which you should use as the
> > .config file for your installation kernel.
> >
> > > The replaced the *.o files in the disk with my new built
> > modules. But
> > > still - no good.
> >
> > > > I've asked my colleague who does all the drivers ...
> > > >
> > > > > Wilck Martin wrote:
> > > > >
> > > > > >>Nir Livni wrote:
> > > > >  >>I would like to know how can I build a driver disk for
> > > > this kernel,
> > > > >
> > > > > create a driectory structure that looks like this
> > > > >
> > > > > 2.4.9-e.5
> > > > >         modname.o
> > > > >         ...
> > > > > 2.4.9-e.5BOOT
> > > > >         modname.o
> > > > >         ...
> > > > > 2.4.9-e.5smp
> > > > >         modname.o
> > > > >         ...
> > > > > ...
> > > > >
> > > > > Of course, the respective .o files must have been compiled
> > > > against a
> > > > > properly configured kernel. "modname" stands for the
> > name of your
> > > > > driver.
> > > > >
> > > > > At the top of that structure, create a compressed cpio archive
> 
> > > like
> > > > > this:
> > > > >
> > > > > find . -depth | cpio -H crc 2>/dev/null | gzip -qc -
> > >modules.cgz
> > > > >
> > > > > copy the file "modules.cgz" to a DOS- or ext2-formatted
> floppy.
> > > > > Besides "modules.cgz", the floppy must contain
> > > > >
> > > > > 1. a file "modinfo" in the following format:
> > > > >
> > > > > modname
> > > > >         scsi
> > > > >         "description of driver"
> > > > >
> > > > > Caution: TABs at the beginning line 2 and 3!
> > > > >
> > > > > 2. a file "modules.dep" in the following format:
> > > > > modname:        scsi_mod
> > > > >
> > > > > (scsi_mod is usually the only prerequisite needed)
> > > > >
> > > > > 3. a file "pcitable" in the following format:
> > > > > 0xdead  0xbeef  "modname"       "description of device"
> > > > > ...
> > > > >
> > > > > Caution: TAB as field separator!
> > > > > This list must contain the PCI vendor and device IDs of
> > > > your device
> > > > > in the 1st and 2nd field. The easiest way to obtain
> > these is from
> > > an
> > > > > existing driver disk for a different kernel. Alternatively,
> you
> > > can
> > > > > read
> > > > > the driver source to find them out.
> > > > >
> > > > > 4. a file called "rhdd-6.1" with a free-format
> > description of the
> > > > > floppy
> > > > >
> > > > > 5. an empty file called "up"
> > > > >
> > > > > Good luck,
> > > > > Martin
> > > > >
> > > > > --
> > > > > Martin Wilck                Phone: +49 5251 8 15113
> > > > > Fujitsu Siemens Computers   Fax:   +49 5251 8 20409
> > > > > Heinz-Nixdorf-Ring 1
> > > mailto:Martin.Wilck@Fujitsu-Siemens.com
> > > > > D-33106 Paderborn
> > > http://www.fujitsu-siemens.com/primergy
> > > >
> > > > --
> > > > Josef Möllers (Pinguinpfleger bei FSC)
> > > >       If failure had no penalty success would not be a prize
> > > >                                               -- T.  Pratchett
> > > > -
> > > > To unsubscribe from this list: send the line "unsubscribe
> > > > linux-scsi" in the body of a message to
> majordomo@vger.kernel.org
> > > > More majordomo info at
> http://vger.kernel.org/majordomo-info.html
> > > >
> >
> > --
> > Josef Möllers (Pinguinpfleger bei FSC)
> >       If failure had no penalty success would not be a prize
> >                                               -- T.  Pratchett
> >

-- 
Josef Möllers (Pinguinpfleger bei FSC)
	If failure had no penalty success would not be a prize
						-- T.  Pratchett
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: How to build a RedHat driver disk (fusion mpt)

[Matt Domsch]

DKMS can generate driver disks for Red Hat; other distros are possible
too if someone familiar with them sends the code.

http://freshmeat.net/projects/dkms

I find this much simpler than generating them by hand.
Feedback about DKMS can be sent to dkms-devel@lists.us.dell.com
(subscribe at http://lists.us.dell.com).

Thanks,
Matt

-- 
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com

RE: How to build a RedHat driver disk (fusion mpt)]]

[Nir Livni]

Problem Solved!
Apparently a kernel patch was not needed.
I created the driver disk as you instructed and it worked just fine!

Appreciate your help,
Nir

> 
> 
> > Nir Livni wrote:
> > 
> > I am trying to compile the mpt modules again.
> > It seems that kernel < 2.4.18 require a kernel patch to 
> support fusion 
> > mpt.
> 
> I can't help any further.
> Sorry.
> 
> > I used make oldconfig to reconfigure the kernel, and added the MPT 
> > FUSION support for modules.
> > 
> > How can I re-create the kernel rpm , so I can replace the 
> rpm exists 
> > in my installation cd ?
> > 
> > Thanks,
> > Nir
> > 
> > >
> > >
> > > > Nir Livni wrote:
> > > >
> > > > So far so good...
> > > > That's almost identical to what I've done.
> > > > I took the original driver disk (2.4.9-e.3smp), and 
> replaced the 
> > > > modname.o with a compiled modname.o of my kernel. RedHat
> > identifies
> > > > the modules in the driver disk, but when I ask to load 
> the driver 
> > > > (using linux dd noprobe when installing) -
> > > >
> > > > I always get "failed to insert modname.o module".
> > >
> > > You should be able to get some more information by 
> switching to an 
> > > alternate console.
> > >
> > > > I suspect I do not compile the module as I should.
> > > >
> > > > The kernel rpm is kernel-smp-2.4.9-e.5.i686.rpm.
> > > >
> > > > I installed this rpm on a temporary smp PC, with an IDE
> > > controller. I
> > > > uploaded the sources and tried to follow the build
> > > instructions, with
> > > > no special configuration.
> > >
> > > As Martin wrote, you do need to use the exact 
> configuration of the 
> > > kernel. If you have the kernel source installed on y 
> system, check 
> > > the /usr/src/linux/configs directory. There should be a file 
> > > ...BOOT... which you should use as the .config file for your 
> > > installation kernel.
> > >
> > > > The replaced the *.o files in the disk with my new built
> > > modules. But
> > > > still - no good.
> > >
> > > > > I've asked my colleague who does all the drivers ...
> > > > >
> > > > > > Wilck Martin wrote:
> > > > > >
> > > > > > >>Nir Livni wrote:
> > > > > >  >>I would like to know how can I build a driver disk for
> > > > > this kernel,
> > > > > >
> > > > > > create a driectory structure that looks like this
> > > > > >
> > > > > > 2.4.9-e.5
> > > > > >         modname.o
> > > > > >         ...
> > > > > > 2.4.9-e.5BOOT
> > > > > >         modname.o
> > > > > >         ...
> > > > > > 2.4.9-e.5smp
> > > > > >         modname.o
> > > > > >         ...
> > > > > > ...
> > > > > >
> > > > > > Of course, the respective .o files must have been compiled
> > > > > against a
> > > > > > properly configured kernel. "modname" stands for the
> > > name of your
> > > > > > driver.
> > > > > >
> > > > > > At the top of that structure, create a compressed 
> cpio archive
> > 
> > > > like
> > > > > > this:
> > > > > >
> > > > > > find . -depth | cpio -H crc 2>/dev/null | gzip -qc -
> > > >modules.cgz
> > > > > >
> > > > > > copy the file "modules.cgz" to a DOS- or ext2-formatted
> > floppy.
> > > > > > Besides "modules.cgz", the floppy must contain
> > > > > >
> > > > > > 1. a file "modinfo" in the following format:
> > > > > >
> > > > > > modname
> > > > > >         scsi
> > > > > >         "description of driver"
> > > > > >
> > > > > > Caution: TABs at the beginning line 2 and 3!
> > > > > >
> > > > > > 2. a file "modules.dep" in the following format:
> > > > > > modname:        scsi_mod
> > > > > >
> > > > > > (scsi_mod is usually the only prerequisite needed)
> > > > > >
> > > > > > 3. a file "pcitable" in the following format:
> > > > > > 0xdead  0xbeef  "modname"       "description of device"
> > > > > > ...
> > > > > >
> > > > > > Caution: TAB as field separator!
> > > > > > This list must contain the PCI vendor and device IDs of
> > > > > your device
> > > > > > in the 1st and 2nd field. The easiest way to obtain
> > > these is from
> > > > an
> > > > > > existing driver disk for a different kernel. Alternatively,
> > you
> > > > can
> > > > > > read
> > > > > > the driver source to find them out.
> > > > > >
> > > > > > 4. a file called "rhdd-6.1" with a free-format
> > > description of the
> > > > > > floppy
> > > > > >
> > > > > > 5. an empty file called "up"
> > > > > >
> > > > > > Good luck,
> > > > > > Martin
> > > > > >
> > > > > > --
> > > > > > Martin Wilck                Phone: +49 5251 8 15113
> > > > > > Fujitsu Siemens Computers   Fax:   +49 5251 8 20409
> > > > > > Heinz-Nixdorf-Ring 1
> > > > mailto:Martin.Wilck@Fujitsu-Siemens.com
> > > > > > D-33106 Paderborn
> > > > http://www.fujitsu-siemens.com/primergy
> > > > >
> > > > > --
> > > > > Josef Möllers (Pinguinpfleger bei FSC)
> > > > >       If failure had no penalty success would not be a prize
> > > > >                                               -- T.  Pratchett
> > > > > -
> > > > > To unsubscribe from this list: send the line "unsubscribe 
> > > > > linux-scsi" in the body of a message to
> > majordomo@vger.kernel.org
> > > > > More majordomo info at
> > http://vger.kernel.org/majordomo-info.html
> > > > >
> > >
> > > --
> > > Josef Möllers (Pinguinpfleger bei FSC)
> > >       If failure had no penalty success would not be a prize
> > >                                               -- T.  Pratchett
> > >
> 
> -- 
> Josef Möllers (Pinguinpfleger bei FSC)
> 	If failure had no penalty success would not be a prize
> 						-- T.  Pratchett
> 
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html