On Tue, 21 Sep 1999, Bill Studenmund wrote:

> On Tue, 21 Sep 1999, Andreas Wrede wrote:
> 
> > I am successfully running 1.4.1 via netboot, but I am running into the
> > following porblems when I try to run 1.4K (current as of yesterday):
> 
> I'm having a few of the same problems with today's kernel on my Blue G3.
> 
> > 1. USB 
> > I get 'port x did not power up' for both USB ports. See boot messages
> > below for details.
> 
> Not this one.. Do you have anything on the usb bus? It could be OF only
> powers it up if there's something there.

I tried a USB keyboard/mouse combo from an iMac - made no difference.

> > 2. X
> > Under 1.4.1 the X server runs fine, but with 1.4K I get the messages
> > 
> > OsVendorInit
> > X: open kbd/mouse: No such file or directory
> > 
> > ktrace reveals that the open of /dev/wskbd0 returns errno 16 (busy).
> > According to fstat, there is no process that has /dev/wdkbd0 open, ie
> > no getty or login session is running on the consoile. Again, the same
> > X server can open the kbd when running a 1.4.1 kernel. 
> 
> But I do get this one!
> 
> I think it's partly due to the fact that the keyboard's grabbed by the
> display. See below..

> > bm0 at obio0 offset 0x11000 irq 42,33: address 00:50:e4:50:9e:5e
> > ofb0 at pci0 dev 17 function 0: ATI Technologies Mach64 LI
> > ofb0: 1024 x 768, 8bpp
> > wsdisplay0 at ofb0: console (std, vt100 emulation), using wskbd0
>                                                             ^^^^^^
> 
> That's where the keyboard went, I think..
> 
> What I don't know is what to do about it. Do we need a new X server??

On the i386 port, the X servers use a ttyEx port, not the wskbdx.
Maybe we need a new Xserver.

> Also, on the subject of wscons stuff, I have the problem that I can't add
> extra screens (which I thought the wscons x server wanted)... ?? I think
> the problem's that I'm in a 1152 by somethign big video mode, which is a
> lot of pixels. Assuming I understand what it's doing...

Same here - wsconscfg failes with: WSDISPLAYIO_ADDSCREEN: Cannot
allocate memory


    - aew