unsupported io range problem
M. Warner Losh
imp at bsdimp.com
Wed Apr 21 22:16:19 PDT 2004
In message: <20040421202556.AC9178A at toad.stack.nl>
marcov at stack.nl (Marco van de Voort) writes:
: > In message: <20040420164920.24EE2D7 at toad.stack.nl>
: > marcov at stack.nl (Marco van de Voort) writes:
:
: > >Could it be related to the fact that these devises are attached to bus
: > >PCI1 ?
: >
: > It is related to the fact that the pci bridge really passes all
: > addresses back upstream, rather than the addresses listed in the pci
: > bridge registers. newer versions handle this correctly, completely
: > eliminating the allow_unsupported_io_ranage option. You should try a
: > number higher than 0x20000000 since that's kind of low...
:
: I tried a lot of values 0x2.., 0x4.., 0x6.., 0x8.., 0xe....
:
: all the same result. Are you suggesting I'd have to update to a -current
: kernel?
I'm suggesting that you might have to. I'd checkout a separate
5.3-current tree, and installing with KERNEL=current so that it goes
into /boot/current in case there are major issues. At the 'ok'
prompts, you'll need to type 'unload' and then 'boot current'.
Warner
More information about the freebsd-mobile
mailing list