Subject: Re: Problems installing i386 1.2.1 -- EHPL!!...uh, HELP!!
To: None <James.Graham@Schwab.COM>
From: Mike Long <mikel@shore.net>
List: port-i386
Date: 07/29/1997 01:49:50
>From: James.Graham@Schwab.COM
>Date: Mon, 28 Jul 1997 17:17:11 -0700

>I'm trying to get NetBSD up and running but am having severe
>difficulties, due likely to 1.2.1 unsupported hardware (guessing
>from the DMESG output); if anyone knows if this is to be fixed 
>in 1.3, please advise, thanks.
>
>Summary:
>	Mouse is not recognized (and subsequently X won't run)

Are you sure X is using the correct protocol?  If you're using the
i386 [lmp]ms driver, don't forget that the result looks like a
busmouse, not a regular PS/2 mouse.

>Could someone -also- please tell me (again) how to label the drive so
>that [W95]:C: will mount properly?  What offsets do I need, etc...?  
>[I have wd0h available for use for an MS-DOS filesystem, and I currently
>have it starting at one track ahead of cyl 0 and extending to the start
>of the NETBSD partition.]

I believe this information is in Dave Burgess' FAQ.

>NetBSD 1.2.1 (ALDERAAN) #2: Mon Jul 28 07:55:06 PDT 1997

>isa0 at mainbus0
><?? ... is this _really_ an ISA?

Not necessarily, although it will work as if it were.  For NetBSD, ISA
is what's left over once PCI and EISA have finished finding and taking
their devices.

># Why'd it find this? :
>sea0: board type unknown at address 0xf8351000

This is a spurious message, which is gone in -current.

>mcd0: timeout in getresult	
>mcd0: timeout in getresult
>mcd0: timeout in getresult		<<< No mitsumi cd rom, OK.

Ditto.

>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?
>ie0: unknown AT&T board type code 15
>^^^<?? Why'd it find this?
>ie1: unknown AT&T board type code 15
>^^^			<?? ...or this?

More spurious messages.  Remember that unused ISA ports usually return
0xff when read....

>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?				  ^^^^^^

Microsoft Windows Sound System, basically an AD1848 codec or variant
thereof plopped directly onto the ISA bus.  I assume you have a
generic ISA soundcard with SB and WSS emulation.

>Where's my mouse; do I need to configure it to find the mouse on the
>eisa
>port...?

What kind of mouse do you have?  If it's not a serial mouse, you
probably need to use one of the pms(4), lms(4), or mms(4) drivers.
-- 
Mike Long <mikel@shore.net>                http://www.shore.net/~mikel
"Every normal man must be tempted at times to spit on his hands,
hoist the black flag, and begin slitting throats." -- H.L. Mencken