Cool. The file's date is 2001/10/23, but here it is anyway. I'm
crossing my fingers. I had to remove the first dot from the filename
because Mozilla for Mac had problems with it.
Mario
Branden Robinson wrote:
>On Wed, Nov 14, 2001 at 12:24:02PM -0500, Ben Collins wrote:
>
>>I ha
On Thu, Nov 15, 2001 at 12:41:29PM +1000, Alexander Zangerl wrote:
> i've got a bit of a problem with the ultra5 i'm supposed to
> install right now:
> i need support for a 3c905 pci network card which is not enabled
> in the stock kernels for ultrasparcs.
>
> building any kernel (i've tried 2.2
i've got a bit of a problem with the ultra5 i'm supposed to
install right now:
i need support for a 3c905 pci network card which is not enabled
in the stock kernels for ultrasparcs.
building any kernel (i've tried 2.2.19 and 2.4.latest) with that
thing enabled fails with an abysmal internal com
Quoting Donald Wu <[EMAIL PROTECTED]>:
> I have same message on my SS5, I notice it after exiting X window.
>
> I just got that SS5 setup with Debian yesterday. Another problem
> is the gdm die when I logout X window. Now I stop using gdm to start
> gnome and
> X window. Does anyone has come acro
I have same message on my SS5, I notice it after exiting X window.
I just got that SS5 setup with Debian yesterday. Another problem
is the gdm die when I logout X window. Now I stop using gdm to start gnome and
X window. Does anyone has come across same problem.
Donald
Hakan Kuecuekyilmaz wrote:
On Wed, Nov 14, 2001 at 01:16:00PM -0500, Mario Lombardo wrote:
> That's what I thought. In Potato, I got this every time, but in
> reading /usr/share/doc/xfree86-common under the [How do I get the
> Xserver to find the "fixed" font?] section it states:
>
> "If the X server refuses to start, c
That's what I thought. In Potato, I got this every time, but in
reading /usr/share/doc/xfree86-common under the [How do I get the
Xserver to find the "fixed" font?] section it states:
"If the X server refuses to start, complaining that it cannot find the
'fixed' font, then one (or more) of t
On Wed, Nov 14, 2001 at 12:24:02PM -0500, Ben Collins wrote:
> I have a feeling that the fonts are the cause of the failure. They
> should be non-fatal. Can you check the rest of the output (perhaps mouse
> errors)?
$HOME/.xsession-errorsmay have a smoking gun in it.
--
G. Branden Robinson
On Tue, Nov 13, 2001 at 03:15:05PM -0500, Ben Collins wrote:
> Ok, I've narrowed down the problem with init not being pid-1 to 2.4.x
> kernels and the presence of /linuxrc on the root disk. We don't want
> /linuxrc, since we don't need it. However, on 2.2.x, this worked fine,
> and on 2.4.x, the in
On Wed, Nov 14, 2001 at 12:24:02PM -0500, Ben Collins wrote:
> On Wed, Nov 14, 2001 at 12:00:30PM -0500, Mario Lombardo wrote:
> > I purged the xfonts-pex and reinstalled. Same thing happened.
> >
> > In /usr/lib/X11/fonts/misc
> > update-fonts-alias .
> > update-fonts-dir .
> > update-fonts-sca
On Wed, Nov 14, 2001 at 10:31:00AM -0500, Ben Collins wrote:
> > (using VT number 7)
> >
> > PEXExtensionsInit: Couldn't open default PEX font file Roman_M
> > PEXExtensionsInit: Couldn't open default PEX font file Roman_M
> >
> > waiting for X server to shut down
>
> apt-get install xf
On Wed, Nov 14, 2001 at 12:00:30PM -0500, Mario Lombardo wrote:
> I purged the xfonts-pex and reinstalled. Same thing happened.
>
> In /usr/lib/X11/fonts/misc
> update-fonts-alias .
> update-fonts-dir .
> update-fonts-scale .
>
> Tried startx again. Still, I get the same thing. Where else can
I purged the xfonts-pex and reinstalled. Same thing happened.
In /usr/lib/X11/fonts/misc
update-fonts-alias .
update-fonts-dir .
update-fonts-scale .
Tried startx again. Still, I get the same thing. Where else can I
look? Where is this information coming from that would originate such
an
I'd hug you for the SSH idea, but unfortunately my station was off the
network w/o an IP address :^
You did make me think of Serial A and B, but just my luck, getty wasn't
listening on those ports.
There goes my work
B.C.J.O wrote:
On Wed, 14 Nov 2001, Hakan Kuecuekyilmaz wrote:
t
No, those don't work. I know they worked with Intel machines, but I
have a Type 5 keyboard. Could it be some other sequence? I guess you
are talking about a sparc. Right?
Mario
Hakan Kuecuekyilmaz wrote:
typed Xsun, but now I can't shut it down. What's the key sequence to
kill Xsun?
> (using VT number 7)
>
> PEXExtensionsInit: Couldn't open default PEX font file Roman_M
> PEXExtensionsInit: Couldn't open default PEX font file Roman_M
>
> waiting for X server to shut down
apt-get install xfonts-pex
--
.--===-=-==-=---=-
On Wed, 14 Nov 2001, Hakan Kuecuekyilmaz wrote:
> > typed Xsun, but now I can't shut it down. What's the key sequence to
> > kill Xsun? It's stuck at the Debian Welcome screen.
> >
> > Mario
>
> can't you switch your console with ctrl+alt F1, or kill the server with
> ctrl+alt+backspace...
> you
> typed Xsun, but now I can't shut it down. What's the key sequence to
> kill Xsun? It's stuck at the Debian Welcome screen.
>
> Mario
can't you switch your console with ctrl+alt F1, or kill the server with
ctrl+alt+backspace...
you will find following similar line in your startx script:
defa
It's a SPARC 5. With startx there are other things it does than just
the X server. I don't know too much detail, but it also starts the
environment and the window manager etc. (through xinit or something). I
typed Xsun, but now I can't shut it down. What's the key sequence to
kill Xsun? It
> #startx
>
> (using VT number 7)
>
> PEXExtensionsInit: Couldn't open default PEX font file Roman_M
> PEXExtensionsInit: Couldn't open default PEX font file Roman_M
>
> waiting for X server to shut down
>
As far as I know, you have to start 'xsun' or 'Xsun'.
What kind of machine do y
I am stumped. I started reading:
/usr/share/doc/xserver-xsun/README.Debian then
../xserver-common/README.Debian then I finally found what I think I
wanted in
../xfree86-common/FAQ.gz under section [How do I get the Xserver to find
the "fixed" font?]
I've addressed everything under the recomme
21 matches
Mail list logo
