1 |
On Saturday 08 July 2006 04:29, gentuxx wrote: |
2 |
> "YEEE, Ultrasparc sbus |
3 |
> not found". Um, this is an Ultra5 with PCI/IDE, so why is the sbus |
4 |
> becoming an issue? I've found the following two config options in the |
5 |
> kernel config: |
6 |
> |
7 |
> CONFIG_SBUS=y |
8 |
> CONFIG_SBUSCHAR=y |
9 |
|
10 |
If a driver being built relies on one of those, then it is not |
11 |
viewable/selectable. In drivers/atm, drivers/parport, drivers/net and |
12 |
drivers/scsi selecting certain hardware/drivers automatically enables them |
13 |
(from memory of a similar problem trying to tftpboot an ultra5/10 with a |
14 |
config modified from an e3000 kernel) |
15 |
You can find out what is actually making those "invisible" by grepping your |
16 |
kernel sources for SBUS or SBUSCHAR and piping the results through grep again |
17 |
and finding "depends" |
18 |
grep -r SBUS "/path/to/kernel-sources/" | grep depends |
19 |
|
20 |
then look at the Kconfig files listed and see what is "depending" on SBUS and |
21 |
turn it off. |
22 |
|
23 |
HIH |
24 |
|
25 |
Hamish |
26 |
|
27 |
-- |
28 |
gentoo-sparc@g.o mailing list |