Subject: Re: Problems installing i386 1.2.1 -- EHPL!!...uh, HELP!!
To: None <James.Graham@schwab.com>
From: Jason Thorpe <thorpej@nas.nasa.gov>
List: port-i386
Date: 07/28/1997 17:23:32
On Mon, 28 Jul 1997 17:17:11 -0700
James.Graham@Schwab.COM wrote:
> greywolf@alderaan.dev.schwab.com:/usr/src/sys/arch/i386/compile/ALDERAAN
> CPU: Pentium (GenuineIntel 586-class CPU)
> real mem = 66711552
> avail mem = 59682816 <??
> Where'd 8MB go?
> using 839 buffers containing 3436544 bytes of memory <<< Found 3 of
> it...
>
> ??? where's the other 5?
kernel text + data + bss + pmap overhead + vm system overhead + ...
> mainbus0 (root)
> isa0 at mainbus0
> <?? ... is this _really_ an ISA?
> com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
> lpt0 at isa0 port 0x378-0x37f irq 7
> # Why'd it find this? :
> sea0: board type unknown at address 0xf8351000
> mcd0: timeout in getresult
> mcd0: timeout in getresult
> mcd0: timeout in getresult <<< No mitsumi cd rom, OK.
> wdc0 at isa0 port 0x1f0-0x1f7 irq 14 <<< Found wdc0, cool...
> wd0 at wdc0 drive 0: 2014MB, 4092 cyl, 16 head, 63 sec, 512 bytes/sec
> <QUANTUM FIREBALL_TM2110A>
> wd0: using 16-sector 16-bit pio transfers, lba addressing
> # ?? ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Is this because it's ISA?
Yes. NetBSD doens't (yet) use PCI native mode on IDE controllers.
> ie0: unknown AT&T board type code 15
> ^^^<?? Why'd it find this?
> ie1: unknown AT&T board type code 15
> ^^^ <?? ...or this?
Those ie* and sea* and mcd* aren't really "found" ... it's just bogus
debugging output that happened to be enabled in the 1.2* kernels.
> sb0 at isa0 port 0x220-0x237 irq 7 drq 1: dsp v3.02 <<< Sound board.
>
> <[[ Cool.
> wss0 at isa0 port 0x530-0x537 irq 10 drq 0: broken (vers 63)
> ^^^?? What's this? ^^^^^^
> wss: could not attach to audio pseudo-device driver (22)
"Windows Sound System" .. do you have 2 sound boards?
> npx0 at isa0 port 0xf0-0xff: using exception 16
> ^^^^?? What's this?
Numeric Processor eXtension, I think... the FPU.
> pc0 at isa0 port 0x60-0x6f irq 1: color <<? I think I get this...
> fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
> fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
> pci0 at mainbus0 bus 0: configuration mode 1 <<< Finds pci bus...?
> vendor 0x8086 product 0x1250 (class bridge, subclass host, revision
> 0x03) at pci0 dev 0 function 0 not configured
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<?? What's this?
That's the PCI-Host bridge...
> vendor 0x8086 product 0x7000 (class bridge, subclass ISA, revision 0x01)
> at pci0 dev 7 function 0 not configured
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<?? What's this?
...and the PCI-ISA bridge. Don't worry that they're not configured.
(It is possible to attach drivers to them in -current, though.)
> vendor 0x5333 product 0x8811 (class display, subclass VGA, revision
> 0x44) at pci0 dev 16 function 0 not configured
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<?? What's this?
That's your VGA card - it has a native mode PCI interface, too. Don't
worry about it.
> ep1 at pci0 dev 17 function 0: 3Com 3C905 Ethernet <<< Found it,
> BUT:
> ep1: no connectors! address 00:c0:4f:bd:3b:0b <?? What's this mean?
> ep1: interrupting at irq 11
...means that the 905 probably didn't work properly in 1.2.1. *shrug*
I'm told it works well in -current.
Jason R. Thorpe thorpej@nas.nasa.gov
NASA Ames Research Center Home: +1 408 866 1912
NAS: M/S 258-6 Work: +1 415 604 0935
Moffett Field, CA 94035 Pager: +1 415 428 6939