Re: xserver-xsun broken!
Did you link /dev/fb to you frame buffer device eg /dev/fb0? This is a recent
small bug, but if you read the docs on xserver-xsun it'll tell you.
Regards,
Peter Firmstone.
Dayton Turner wrote:
> Hi, I just installed debian on my sparc the other day as well and I get
>
> pivo:~# startx
> (using VT number 7)
>
> PEXExtensionInit: Couldn't open default PEX font file Roman_M
> sunMouseProc ioctl VUIDFORMAT: Invalid argument
>
> Fatal server error:
> failed to initialize core devices
>
> Now, I do have the xfonts-pex installed and the font exists in
> /usr/X11R6/lib/X11/fonts/PEX (Roman_M.phont) although running mkfontdir
> doesnt seem to find it. so that's one problem, but i also seem to be
> having the same problem you are with the core devices.
>
> Unfortunately, I dont have an old Xsun binary to fall back on, can you
> either tell me where i might find one or give me a little insight to if
> you have seen this problem fixed yet?
>
> Thanks alot
> Dayton
>
> > Hi,
> > Yesterday, I have confidently convert a Sun sparc-solaris to
> > sparc-debian. No particular problem, but when I launch startx I found
> > that the xserver package isn't installed : in fact it has been
> > dselected when I select gpm. No problem, I reinstall xserver-xsun
> > which remove gpm. However, startx yields the following error message
> >
> > SunMouseProc ioctl VUIDGFORMAT: invalid argument
> > Fatal server error
> > Fail to initialize core devices
> >
> > Sound familiar, I remove the link /dev/mouse -> gpmdata and reling to
> > /dev/sunmouse then relaunch startx: same error ! I purge gpm: same
> > error, purge xserver-xsun and reinstall xserver-xsun: same error,
> > reboot retart: same error
> >
> > Panic, going back and reinstall solaris would be too much a hassle.
> > Fortunately I remember having a Sun machine running sparc-debian. I
> > copy the file Xsun on this machine to this one. It works !
> >
>
> > I would like to point out that this other Sun have been upgradded
> > several day ago and for some reason the xserver-xsun have been kept
> > back (perhaps because of the presence of gpm ?). I also notice that
> > adter upgrading my xserver crashed and I have to remove gpm.
> > Apparently, this upgrade have nevertheless change the behaviour of the
> > X server: it crash in the presence of gpm while before gpm get kill.
> > That's no big deal. But I am very upset that at this advance stage (of
> > freeze), one still tinkers with a critical and working package like X
> > and introduce new bug. Just two days ago? I have reported a bug in the
> > new file /etc/Xsession (it no longer loads the Xresources)
> >
> > Please go back to the xserver-xsun which works
> >
> > --
> > PHAM Dinh Tuan | e-mail: Dinh-Tuan.Pham@imag.fr
> > Laboratoire de Modelisation et Calcul | Tel: +33 4 76 51 44 23
> > BP 53, 38041 Grenoble cedex 9 (France) | Fax: +33 4 76 63 12 63
> > -----------------------------------------------------------------------
> >
> >
> --
> `~ ~'
> O.O
> ---------------------------UUU-V-UUU---------------------------------
> Dayton Turner UNIX Systems and Network Administrator
> E-Mail: turnerd@intouch.ca Cell: (604) 809-7742
> WWW: http://www.turnerd.com Richmond, BC, Canada
>
> --
> To UNSUBSCRIBE, email to debian-sparc-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: