On Saturday 08 July 2006 04:29, gentuxx wrote: > "YEEE, Ultrasparc sbus > not found". Um, this is an Ultra5 with PCI/IDE, so why is the sbus > becoming an issue? I've found the following two config options in the > kernel config: > > CONFIG_SBUS=y > CONFIG_SBUSCHAR=y
If a driver being built relies on one of those, then it is not viewable/selectable. In drivers/atm, drivers/parport, drivers/net and drivers/scsi selecting certain hardware/drivers automatically enables them (from memory of a similar problem trying to tftpboot an ultra5/10 with a config modified from an e3000 kernel) You can find out what is actually making those "invisible" by grepping your kernel sources for SBUS or SBUSCHAR and piping the results through grep again and finding "depends" grep -r SBUS "/path/to/kernel-sources/" | grep depends then look at the Kconfig files listed and see what is "depending" on SBUS and turn it off. HIH Hamish -- [email protected] mailing list
