Re: X on latest potato?

2000-06-08 Thread Sergio Mendoza
-> From [EMAIL PROTECTED] Thu Jun 08 20:07:51 2000
-> Date: Thu, 8 Jun 2000 15:07:36 -0400 (EDT)
-> From: Rich Sahlender <[EMAIL PROTECTED]>
-> 
-> Huh? I have run X as normal user for years via startx. This worked
-> as always on sparc64 until apt-get upgrade a few days ago. I should
-> not have to run xdm. I should also not need to be root to run X as
-> the /usr/bin/X11/X suid wrapper takes care things for normal user.
-> My /etc/X11/Xserver contains:
-> 
-> /usr/bin/X11/Xsun24
-> Console
-> 
-> This should permit anyone logged in at the console to run X. Have
-> I missed something?

  Depending on your necessities, "Console" is usually a good alternative.

Sergio.



Re: X on latest potato?

2000-06-08 Thread Rich Sahlender
Huh? I have run X as normal user for years via startx. This worked
as always on sparc64 until apt-get upgrade a few days ago. I should
not have to run xdm. I should also not need to be root to run X as
the /usr/bin/X11/X suid wrapper takes care things for normal user.
My /etc/X11/Xserver contains:

/usr/bin/X11/Xsun24
Console

This should permit anyone logged in at the console to run X. Have
I missed something?

Regards,
Rich

On Thu, 8 Jun 2000, Sergio Mendoza wrote:

> -> It turns out there was a little more to this than just a symlink
> -> for /dev/fb to /dev/fb0. In my case, /dev/fb0 somehow had perms
> -> 
> -> crw--w--w-1 root tty   29,   0 Mar 30 22:46 /dev/fb0
> 
> This looks correct to me, it should be like that, shouldn't it?
> 
> -> 
> -> so running X as root worked fine after the symlink but still
> -> failed for normal user. Once I added the user to group tty and
> -> added read to the group perms X starts fine for normal user.
> 
> I think that you were trying to run X as a normal user, which by default
> should not happen.  You can overwrite the default by adding "Anybody"
> after the line which says /usr/bin/X11/X-something in your
> /etc/X11/Xserver file.  However, you are at risk here!  A better option is
> to run xdm and let X to be run only by root.  
> 
> Sergio.
> 
> 
> --  
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> 



Re: X on latest potato?

2000-06-08 Thread Sergio Mendoza
-> From: Rich Sahlender <[EMAIL PROTECTED]>
-> X-Sender: [EMAIL PROTECTED]
-> To: debian-sparc@lists.debian.org
-> Subject: Re: X on latest potato?
-> 
-> It turns out there was a little more to this than just a symlink
-> for /dev/fb to /dev/fb0. In my case, /dev/fb0 somehow had perms
-> 
-> crw--w--w-1 root tty   29,   0 Mar 30 22:46 /dev/fb0

This looks correct to me, it should be like that, shouldn't it?

-> 
-> so running X as root worked fine after the symlink but still
-> failed for normal user. Once I added the user to group tty and
-> added read to the group perms X starts fine for normal user.

I think that you were trying to run X as a normal user, which by default
should not happen.  You can overwrite the default by adding "Anybody"
after the line which says /usr/bin/X11/X-something in your
/etc/X11/Xserver file.  However, you are at risk here!  A better option is
to run xdm and let X to be run only by root.  

Sergio.



Re: X on latest potato?

2000-06-08 Thread Rich Sahlender
It turns out there was a little more to this than just a symlink
for /dev/fb to /dev/fb0. In my case, /dev/fb0 somehow had perms

crw--w--w-1 root tty   29,   0 Mar 30 22:46 /dev/fb0

so running X as root worked fine after the symlink but still
failed for normal user. Once I added the user to group tty and
added read to the group perms X starts fine for normal user.

What should the perms be for the /dev/fb* devices? Should MAKEDEV
have run for one of the updates and didn't?

Regards,
Rich

On Tue, 6 Jun 2000, Rich Sahlender wrote:

> Just did an "apt-get update;apt-get upgrade" on an Ultra1 from frozen.
> Havn't done one in about two weeks and some thirty packages were updated.
> Among the updates was xserver-xsun/xserver-xsun24 which no longer seem
> to work.
> 
> $ startx
> 
> (using VT number 7)
> 
> 
> Fatal server error:
> no screens found
> X connection to :0.0 broken (explicit kill or server shutdown).
> $
> 
> Anyone know what's up before I spend time debugging a known problem?
> 
> Thanks,
> Rich
> 
> 
> --  
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> 



Re: X on latest potato?

2000-06-06 Thread Rich Sahlender
Interesting. I'm not using xdm here but tried the "-dev /dev/fb0"
in .xserverrc and also tried "startx -- -dev /dev/fb0". Neither
seems to make any difference. I'll keep trying things...

On Tue, 6 Jun 2000, Peter Haworth wrote:

> Rich Sahlender wrote:
> > Just did an "apt-get update;apt-get upgrade" on an Ultra1 from frozen.
> > Havn't done one in about two weeks and some thirty packages were updated.
> > Among the updates was xserver-xsun/xserver-xsun24 which no longer seem
> > to work.
> > 
> > $ startx
> > 
> > (using VT number 7)
> > 
> > 
> > Fatal server error:
> > no screens found
> > X connection to :0.0 broken (explicit kill or server shutdown).
> 
> I had the same problem this morning. I fixed it by changing the last line of
> /etc/X11/xdm/Xservers from:
>   :0 local /usr/bin/X11/X vt7 -deferglyphs 16
> to
>   :0 local /usr/bin/X11/X vt7 -deferglyphs 16 -dev /dev/fb0
> 
> I thought that was odd at the time, since Xsun's manual claims it will try
> /dev/fb0, but this did the trick.
> 
> -- 
>   Peter Haworth   [EMAIL PROTECTED]
> Q: Why do ducks have flat feet?  A: To stamp out forest fires.
> Q: Why do elephants have flat feet?  A: To stamp out flaming ducks
>   -- UNIX fortune
> 
> 
> --  
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> 



Re: X on latest potato?

2000-06-06 Thread Peter Haworth
Rich Sahlender wrote:
> Just did an "apt-get update;apt-get upgrade" on an Ultra1 from frozen.
> Havn't done one in about two weeks and some thirty packages were updated.
> Among the updates was xserver-xsun/xserver-xsun24 which no longer seem
> to work.
> 
> $ startx
> 
> (using VT number 7)
> 
> 
> Fatal server error:
> no screens found
> X connection to :0.0 broken (explicit kill or server shutdown).

I had the same problem this morning. I fixed it by changing the last line of
/etc/X11/xdm/Xservers from:
  :0 local /usr/bin/X11/X vt7 -deferglyphs 16
to
  :0 local /usr/bin/X11/X vt7 -deferglyphs 16 -dev /dev/fb0

I thought that was odd at the time, since Xsun's manual claims it will try
/dev/fb0, but this did the trick.

-- 
Peter Haworth   [EMAIL PROTECTED]
Q: Why do ducks have flat feet?  A: To stamp out forest fires.
Q: Why do elephants have flat feet?  A: To stamp out flaming ducks
-- UNIX fortune



Re: X on latest potato?

2000-06-06 Thread Rich Sahlender
Hi Sergio,

I'm afraid the solution does not work here.

# ls -l /dev/fb*
lrwxrwxrwx1 root root8 Jun  6 14:43 /dev/fb -> /dev/fb0
crw--w--w-1 root tty   29,   0 Mar 30 22:46 /dev/fb0
crw--w--w-1 root tty   29,   1 Mar 30 22:46 /dev/fb0autodetect
crw--w--w-1 root tty   29,   0 Mar 30 22:46 /dev/fb0current
crw--w--w-1 root tty   29,  32 Mar 30 22:46 /dev/fb1
crw--w--w-1 root tty   29,  33 Mar 30 22:46 /dev/fb1autodetect
crw--w--w-1 root tty   29,  32 Mar 30 22:46 /dev/fb1current
crw--w--w-1 root tty   29,  64 Mar 30 22:46 /dev/fb2
crw--w--w-1 root tty   29,  65 Mar 30 22:46 /dev/fb2autodetect
crw--w--w-1 root tty   29,  64 Mar 30 22:46 /dev/fb2current
crw--w--w-1 root tty   29,  96 Mar 30 22:46 /dev/fb3
crw--w--w-1 root tty   29,  97 Mar 30 22:46 /dev/fb3autodetect
crw--w--w-1 root tty   29,  96 Mar 30 22:46 /dev/fb3current
crw--w--w-1 root tty   29, 128 Mar 30 22:46 /dev/fb4
crw--w--w-1 root tty   29, 129 Mar 30 22:46 /dev/fb4autodetect
crw--w--w-1 root tty   29, 128 Mar 30 22:46 /dev/fb4current
crw--w--w-1 root tty   29, 160 Mar 30 22:46 /dev/fb5
crw--w--w-1 root tty   29, 161 Mar 30 22:46 /dev/fb5autodetect
crw--w--w-1 root tty   29, 160 Mar 30 22:46 /dev/fb5current
crw--w--w-1 root tty   29, 192 Mar 30 22:46 /dev/fb6
crw--w--w-1 root tty   29, 193 Mar 30 22:46 /dev/fb6autodetect
crw--w--w-1 root tty   29, 192 Mar 30 22:46 /dev/fb6current
crw--w--w-1 root tty   29, 224 Mar 30 22:46 /dev/fb7
crw--w--w-1 root tty   29, 225 Mar 30 22:46 /dev/fb7autodetect
crw--w--w-1 root tty   29, 224 Mar 30 22:46 /dev/fb7current
#

Thanks,
Rich

On Tue, 6 Jun 2000, Sergio Mendoza wrote:

> Hi,
> 
>   This problem has a solution and it has already been reported:
> 
> http://www.debian.org/Bugs/db/65/65150.html
> 
> Sergio
> 
> 
> --  
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> 



Re: X on latest potato?

2000-06-06 Thread Rich Sahlender
# dpkg -l xserver-\*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name   VersionDescription
+++-==-==-
un  xserver-agx (no description available)
ii  xserver-common 3.3.6-7files and utilities common to all X 
servers
un  xserver-ggi (no description available)
un  xserver-mach32  (no description available)
un  xserver-mach64  (no description available)
un  xserver-p9000   (no description available)
un  xserver-s3  (no description available)
un  xserver-s3v (no description available)
un  xserver-tga (no description available)
un  xserver-vga16   (no description available)
un  xserver-w32 (no description available)
ii  xserver-xsun   3.3.6-7X server for 8-bit Sun framebuffers
un  xserver-xsun-mono   (no description available)
ii  xserver-xsun24 3.3.6-7X server for 24-bit Sun framebuffers
#

A symlink for /dev/fb to /dev/fb0 did not help.

# ls -l /dev/fb*
lrwxrwxrwx1 root root8 Jun  6 14:43 /dev/fb -> /dev/fb0
crw--w--w-1 root tty   29,   0 Mar 30 22:46 /dev/fb0
crw--w--w-1 root tty   29,   1 Mar 30 22:46 /dev/fb0autodetect
crw--w--w-1 root tty   29,   0 Mar 30 22:46 /dev/fb0current
crw--w--w-1 root tty   29,  32 Mar 30 22:46 /dev/fb1
crw--w--w-1 root tty   29,  33 Mar 30 22:46 /dev/fb1autodetect
crw--w--w-1 root tty   29,  32 Mar 30 22:46 /dev/fb1current
crw--w--w-1 root tty   29,  64 Mar 30 22:46 /dev/fb2
crw--w--w-1 root tty   29,  65 Mar 30 22:46 /dev/fb2autodetect
crw--w--w-1 root tty   29,  64 Mar 30 22:46 /dev/fb2current
crw--w--w-1 root tty   29,  96 Mar 30 22:46 /dev/fb3
crw--w--w-1 root tty   29,  97 Mar 30 22:46 /dev/fb3autodetect
crw--w--w-1 root tty   29,  96 Mar 30 22:46 /dev/fb3current
crw--w--w-1 root tty   29, 128 Mar 30 22:46 /dev/fb4
crw--w--w-1 root tty   29, 129 Mar 30 22:46 /dev/fb4autodetect
crw--w--w-1 root tty   29, 128 Mar 30 22:46 /dev/fb4current
crw--w--w-1 root tty   29, 160 Mar 30 22:46 /dev/fb5
crw--w--w-1 root tty   29, 161 Mar 30 22:46 /dev/fb5autodetect
crw--w--w-1 root tty   29, 160 Mar 30 22:46 /dev/fb5current
crw--w--w-1 root tty   29, 192 Mar 30 22:46 /dev/fb6
crw--w--w-1 root tty   29, 193 Mar 30 22:46 /dev/fb6autodetect
crw--w--w-1 root tty   29, 192 Mar 30 22:46 /dev/fb6current
crw--w--w-1 root tty   29, 224 Mar 30 22:46 /dev/fb7
crw--w--w-1 root tty   29, 225 Mar 30 22:46 /dev/fb7autodetect
crw--w--w-1 root tty   29, 224 Mar 30 22:46 /dev/fb7current
#

On Tue, 6 Jun 2000, Ben Collins wrote:

> On Tue, Jun 06, 2000 at 02:21:58PM -0400, Rich Sahlender wrote:
> > Just did an "apt-get update;apt-get upgrade" on an Ultra1 from frozen.
> > Havn't done one in about two weeks and some thirty packages were updated.
> > Among the updates was xserver-xsun/xserver-xsun24 which no longer seem
> > to work.
> > 
> > $ startx
> > 
> > (using VT number 7)
> > 
> > 
> > Fatal server error:
> > no screens found
> > X connection to :0.0 broken (explicit kill or server shutdown).
> > $
> > 
> > Anyone know what's up before I spend time debugging a known problem?
> 
> Can you show me the output of "dpkg -l xserver-\*" so I can forward this
> problem to the X maintainer?
> 
> Thanks,
>   Ben
> 
> -- 
>  ---===-=-==-=---==-=--
> /  Ben Collins  --  ...on that fantastic voyage...  --  Debian GNU/Linux   \
> `  [EMAIL PROTECTED]  --  [EMAIL PROTECTED]  --  [EMAIL PROTECTED]  '
>  `---=--===-=-=-=-===-==---=--=---'
> 
> 
> --  
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> 



Re: X on latest potato?

2000-06-06 Thread Sergio Mendoza
Hi,

  This problem has a solution and it has already been reported:

http://www.debian.org/Bugs/db/65/65150.html

Sergio



Re: X on latest potato?

2000-06-06 Thread Ben Collins
On Tue, Jun 06, 2000 at 02:21:58PM -0400, Rich Sahlender wrote:
> Just did an "apt-get update;apt-get upgrade" on an Ultra1 from frozen.
> Havn't done one in about two weeks and some thirty packages were updated.
> Among the updates was xserver-xsun/xserver-xsun24 which no longer seem
> to work.
> 
> $ startx
> 
> (using VT number 7)
> 
> 
> Fatal server error:
> no screens found
> X connection to :0.0 broken (explicit kill or server shutdown).
> $
> 
> Anyone know what's up before I spend time debugging a known problem?

Can you show me the output of "dpkg -l xserver-\*" so I can forward this
problem to the X maintainer?

Thanks,
  Ben

-- 
 ---===-=-==-=---==-=--
/  Ben Collins  --  ...on that fantastic voyage...  --  Debian GNU/Linux   \
`  [EMAIL PROTECTED]  --  [EMAIL PROTECTED]  --  [EMAIL PROTECTED]  '
 `---=--===-=-=-=-===-==---=--=---'



X on latest potato?

2000-06-06 Thread Rich Sahlender
Just did an "apt-get update;apt-get upgrade" on an Ultra1 from frozen.
Havn't done one in about two weeks and some thirty packages were updated.
Among the updates was xserver-xsun/xserver-xsun24 which no longer seem
to work.

$ startx

(using VT number 7)


Fatal server error:
no screens found
X connection to :0.0 broken (explicit kill or server shutdown).
$

Anyone know what's up before I spend time debugging a known problem?

Thanks,
Rich