Ether driver misbehaving?

[Bruce Lilly]

In article <1991Jan3.155117.20389 at sci.ccny.cuny.edu> jeffrey at sci.ccny.cuny.edu (Jeffrey L Bromberger) writes:
>
>Here's something else to think about.  Running 3.51 (Yeah, I know :-)
>with an ethernet card.  When the machine boots, it comes up like
>usual.  But here's the twist - if, instead of logging in, you move the
>mouse, strange characters come out!  In fact, I can't see the mouse
>pointer anywhere.  Button presses give things like hf, if, gf.  Moving
>the mouse prints out letters interspersed with 'f's.  The problem goes
>away when you press return.   The /etc/lddrv/drivers file has the
>drivers listed in this order:
>	lipc
>	xt
>	ate
>	cmb
>	ether
>	kbd
>
>Is this the mysterious "Load the Ether First" syndrome in a different
>incarnation?

Never heard of that one. I have ether loaded on 3 machines, never saw this
problem -- but I use nipc (enhanced IPC) rather than lipc.  (currently
rumming 3.51m, so no kbd either, but I had had no problems with this under
3.51)

contents of
/etc/lddrv/drivers:
nipc
xt
ether
cmb
vid
rom
dup

Thanks to those who posted the vid, rom, and dup drivers!

output from running
/etc/lddrv/lddrv -s:
 DEVNAME  ID  BLK CHAR  LINE   SIZE    ADDR     FLAGS
    wind   0   -1    7   -1  0x9000   0x4d000 ALLOC BOUND 
    nipc   1   -1   -1   -1  0x7000   0x56000 ALLOC BOUND 
      xt   2   -1    9    1  0x3000   0x5d000 ALLOC BOUND 
   ether   3   -1   10   -1 0x13000  0x360000 ALLOC BOUND 
     cmb   4   -1   -1   -1  0x3000  0x37c000 ALLOC BOUND 
     vid   5   -1   14   -1  0x1000  0x37f000 ALLOC BOUND 
     rom   6   -1   15   -1  0x1000  0x3de000 ALLOC BOUND 
     dup   7   -1   18   -1  0x1000  0x3df000 ALLOC BOUND 

I don't use the ate driver either (it never seemed worth the trouble).

Try (1) changing to nipc, (2) remove ate, unless you absolutely,
positively must have it, in which case move it to the end, (3) put cmb
after ether.

Hope this helps.
--
	Bruce Lilly		blilly!balilly!bruce at sonyd1.Broadcast.Sony.COM