[Fwd: Re: Kernel building]

[Paul F. Johnson]

Hi,

Somehow, this bounced - any clues as to why?

TTFN

Paul

[Dwaine Garden]

Paul wrote:
> Hi,
>
> Somehow, this bounced - any clues as to why?
>
> TTFN
>
> Paul
>
> Subject:
> Re: Kernel building
> From:
> Paul 
> Date:
> Wed, 29 Dec 2004 11:23:12 +0000
> To:
> [e-mail], For testers of Fedora Core development releases 
>
> To:
> [e-mail], For testers of Fedora Core development releases 
>
> Hi,
> > > by RH or if it doesn't, is one available? The kernels work fine, I just
> > > want to tweak it so DETECT_ALL_LUNS (I think it is) is enabled for USB
> > > so I can get my 8 in 2 reader working (there is a bugzilla job in for
> > > this problem)
> >
> > fwiw that is a *runtime* option where the default is set compile time...
> > so you don't need to recompile your kernel for that at all, you just
> > need to add the module parameter
> >
> > (and please make sure to file the output of cat /proc/scsi/scsi into RH
> > bugzilla so that your device can be added to the whitelist)
>
> Before I do that, this is the output of /proc/scsi/scsi and /sbin/lsusb
> I'm not sure they marry up!
>
> Attached devices:
> Host: scsi1 Channel: 00 Id: 00 Lun: 00
>  Vendor: OEI-USB  Model: CompactFlash     Rev: 1.01
>  Type:   Direct-Access                    ANSI SCSI revision: 02
>
> Bus 002 Device 002: ID 55aa:b012 OnSpec Electronic, Inc. 
> Bus 002 Device 001: ID 0000:0000  
> Bus 001 Device 003: ID 03f0:3004 Hewlett-Packard 
> Bus 001 Device 002: ID 05a9:a511 OmniVision Technologies, Inc. OV511+
> WebCam
> Bus 001 Device 001: ID 0000:0000
>
> It is the device on Bus 002 Device 002 that I need to get working. It
> looks like it should be the correct one, but I'd like to make sure
> before filing a bugzilla.
>
> For reference, the bugzilla related to this is
>
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=141384
>
> TTFN
>
> Paul

Paul, add this.  It worked for my 6-1 USB reader.  Stick it in modprobe.conf

options scsi_mod max_luns=8

Let me know if it works.  It's better than a recompile of the kernel.

Dwaine.

[Paul F. Johnson]

Hi,
> > Attached devices:
> > Host: scsi1 Channel: 00 Id: 00 Lun: 00
> >  Vendor: OEI-USB  Model: CompactFlash     Rev: 1.01
> >  Type:   Direct-Access                    ANSI SCSI revision: 02
> >
> > Bus 002 Device 002: ID 55aa:b012 OnSpec Electronic, Inc. 
> > Bus 002 Device 001: ID 0000:0000  
> > Bus 001 Device 003: ID 03f0:3004 Hewlett-Packard 
> > Bus 001 Device 002: ID 05a9:a511 OmniVision Technologies, Inc. OV511+
> > WebCam
> > Bus 001 Device 001: ID 0000:0000
> Paul, add this.  It worked for my 6-1 USB reader.  Stick it in modprobe.conf
>
> options scsi_mod max_luns=8
>
> Let me know if it works.  It's better than a recompile of the kernel.

Did nothing at all :-(

TTFN

Paul

[Aaron Scott]

On Thu, 2004-12-30 at 01:00 +0000, Paul wrote:
> Did nothing at all :-(
>
> TTFN
> Paul

There's gratitude for you :-)

[Arjan van de Ven]

On Thu, 2004-12-30 at 01:00 +0000, Paul wrote:
> Hi,
> > > Attached devices:
> > > Host: scsi1 Channel: 00 Id: 00 Lun: 00
> > >  Vendor: OEI-USB  Model: CompactFlash     Rev: 1.01
> > >  Type:   Direct-Access                    ANSI SCSI revision: 02
> > >
> > > Bus 002 Device 002: ID 55aa:b012 OnSpec Electronic, Inc. 
> > > Bus 002 Device 001: ID 0000:0000  
> > > Bus 001 Device 003: ID 03f0:3004 Hewlett-Packard 
> > > Bus 001 Device 002: ID 05a9:a511 OmniVision Technologies, Inc. OV511+
> > > WebCam
> > > Bus 001 Device 001: ID 0000:0000
> > Paul, add this.  It worked for my 6-1 USB reader.  Stick it in modprobe.conf
> >
> > options scsi_mod max_luns=8
> >
> > Let me know if it works.  It's better than a recompile of the kernel.
>
> Did nothing at all :-(

after you do this you need to recreate the initrd (with mkinitrd) or
install a new kernel

[Paul F. Johnson]

Hi,
> after you do this you need to recreate the initrd (with mkinitrd) or
> install a new kernel

My brain isn't in gear

cd /boot
/sbin/mkinitrd initrd-2.6.9-1.1049_FC4

should be all that I need to use

However, all that comes up with is the how to use mkinitrd options. I've
tried adding -f before the initrd-2.6.9-1.1049 and still get the same.

Is this me needing more sleep or mkinitrd being silly?

TTFN

Paul

[Arjan van de Ven]

On Thu, Dec 30, 2004 at 09:17:27AM +0000, Paul wrote:
> Hi,
> > after you do this you need to recreate the initrd (with mkinitrd) or
> > install a new kernel
>
> My brain isn't in gear
>
> cd /boot
> /sbin/mkinitrd initrd-2.6.9-1.1049_FC4

mkinitrd initrd-2.6.9-1.1049_FC4.img 2.6.9-1.1049_FC4

I think

[Paul F. Johnson]

Hi,
> > My brain isn't in gear
> >
> > cd /boot
> > /sbin/mkinitrd initrd-2.6.9-1.1049_FC4
>
> mkinitrd initrd-2.6.9-1.1049_FC4.img 2.6.9-1.1049_FC4

Spot on.

For future releases of the kernel, will I need to do that every time or
will it just be picked up on install?

TTFN

Paul

[Arjan van de Ven]

On Thu, Dec 30, 2004 at 11:14:09AM +0000, Paul wrote:
> Hi,
> > > My brain isn't in gear
> > >
> > > cd /boot
> > > /sbin/mkinitrd initrd-2.6.9-1.1049_FC4
> >
> > mkinitrd initrd-2.6.9-1.1049_FC4.img 2.6.9-1.1049_FC4
>
> Spot on.
>
> For future releases of the kernel, will I need to do that every time or
> will it just be picked up on install?

nah;
the key thing is that *at the time the initrd is created* the module option
is in the /etc file. Every rpm install of a kernel will create it's own
initrd at that time, so as long as you keep the option in the /etc file
you're fine from now on. You did have to fix up the existing initrd because
at the time that was created the option wasn't in there yet.

[Michal Jaegermann]

On Thu, Dec 30, 2004 at 10:30:28AM +0100, Arjan van de Ven wrote:
> mkinitrd initrd-2.6.9-1.1049_FC4.img 2.6.9-1.1049_FC4
>
> I think

If you are remaking initrd for the _currently running_ kernel
then try

mkinitrd -f /boot/initrd-$(uname -r).img  $(uname -r)

It will save you some memory strain. :-)

Michal