Firewire HDs
Natalia Portillo
yellowdog-general@lists.terrasoftsolutions.com
Mon May 19 14:36:01 2003
I think that isnt a question of scripts, if it is solved changing the
kernel
> -----Mensaje original-----
> De: yellowdog-general-admin@lists.terrasoftsolutions.com
> [mailto:yellowdog-general-admin@lists.terrasoftsolutions.com]
> En nombre de Tim Seufert
> Enviado el: lunes, 19 de mayo de 2003 9:16
> Para: yellowdog-general@lists.terrasoftsolutions.com
> Asunto: Re: Firewire HDs
>
>
> On Sunday, May 18, 2003, at 06:07 PM, Ben Hall wrote:
>
> > Hmm, some progress? Here's what dmesg tells me:
> >
> > ieee1394: Node 01:1023 has non-standard ROM format (0
> quads), cannot
> > parse
> > ieee1394: sbp2: Logged into SBP-2 device
> > ieee1394: sbp2: Node[01:1023]: Max speed [S400] - Max payload [2048]
> > ieee1394: Device added: Node[01:1023]
> GUID[0030e001e0005bcc] [Oxford
> > Semiconductor Ltd. ]
> >
> > I still, however, cannot see the device from any programs. I'm
> > assuming it would use /dev/sda, at least that's what
> happened in RH9.
>
> YDL probably doesn't have the hotplug scripts set up to do all the
> necessary tasks. One of them is that you have to rescan the sbp2
> virtual SCSI bus to get the kernel to assign a /dev/sdX node
> to the new
> drive. Do a google search for "rescan-scsi-bus.sh" to find a shell
> script that rescans all available SCSI busses.
>
> _______________________________________________
> yellowdog-general mailing list
> yellowdog-general@lists.terrasoftsolutions.com
> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
>