Bug#268188: a workaround...

[Giacomo Mulas <gmulas@ca.astro.it>]

	regarding the bug report I had previously sent about serial ata 
modules having unresolved symbols, I narrowed down the bug and found a 
workaround. The problem arose with CONFIG_SCSI_SATA_VITESSE=y and all 
other SCSI_SATA options selected as modules, i.e.
ONFIG_SCSI_SATA=y
CONFIG_SCSI_SATA_SVW=m
CONFIG_SCSI_SATA_PROMISE=m
CONFIG_SCSI_SATA_SX4=m
CONFIG_SCSI_SATA_SIL=m
CONFIG_SCSI_SATA_SIS=m
CONFIG_SCSI_SATA_VIA=m

I then changed CONFIG_SCSI_SATA_VITESSE to build as a module as well, and 
the problem went away. It seems that if CONFIG_SCSI_SATA_VITESSE is built 
into the kernel then libata.o does not get build nor installed as a 
module, causing all other SCSI_SATA modules to have unresolved symbols. 
This should not happen, or at least it should be documented. In 
particular, if the problem cannot be fixed quickly I suggest to add in the 
README.Debian file a note saying that SCSI_SATA drivers must be either 
compiled _all_ as modules or _all_ into the kernel, to avoid this problem.

Bye, thanks
Giacomo

--
_________________________________________________________________

Giacomo Mulas <gmulas@ca.astro.it>
_________________________________________________________________

OSSERVATORIO ASTRONOMICO DI CAGLIARI
Str. 54, Loc. Poggio dei Pini * 09012 Capoterra (CA)

Tel. (OAC): +39 070 71180 248     Fax : +39 070 71180 222
Tel. (UNICA): +39 070 675 4916
_________________________________________________________________

"When the storms are raging around you, stay right where you are"
                         (Freddy Mercury)
_________________________________________________________________