[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#248011: installation-reports: Partial installation report on Dell Latitude X200 (Firewire CD)

On Sat, May 08, 2004 at 12:53:40PM -0400, Joey Hess wrote:
> Christian Perrier wrote:
> > 0000:02:03.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C551 IEEE 1394 Controller
> Discover-data has the following for Ricoh controllers:
>         11800522        unknown unknown R5C522 IEEE 1394 Controller
>         11800551        unknown unknown R5C551 IEEE 1394 Controller
>         11800552        unknown unknown R5C552 IEEE 1394 Controller
> Can you provide lspci -n output too, so we can see which of these is
> your controller, and make it load ieee1394.

AFAIK to module to load is not ieee1394, but ohci1394 (see below). The
ieee1394 is the common code of all 1394 controllers and when you load one of
the host controller modules with modprobe it is automatically loaded as a

> FWIW, my firewire controller is this:
> 00:13.0 FireWire (IEEE 1394): Texas Instruments TSB43AB21 IEEE-1394a-2000 Controller (PHY/Link)
> 00:13.0 Class 0c00: 104c:8026
> Listed in discover1-data as:
>         104c8026        unknown unknown TSB43AB21 IEEE-1394a-2000 Controller (PHY/Link)
> I can load ieee1394 and it finds the controller, I have no firewire
> stuff to test further. discover1-data seems to have a lot of firewire
> controllers that are listed as "unknown" and so load no module. I don't
> know if the procedure is to wait for a report from a user for each
> before turning it on, or what.
> > With 2.6 kernel, all went fine as soon as I manually loaded the following
> > modules (order is important):
> > 
> > -ieee1394
> > -ohci1394
> > -sbp2
> > -sr_mod
> If discover can find the controller, then loading the rest of these
> modules can be taken care of by hw-detect or something.
> -- 
> see shy jo

Attachment: signature.asc
Description: Digital signature

Reply to: