Broken xserver-xsun (3.3.6-7)
Now after some weeks without functional xsun, I have started wondering if I could get the previous version back. I supposedly upgraded from version 3.3.5 soon after the new one reached the local Debian mirror. Are the old packages available anywhere? Computer is SPARCstation LC with CG3 and I have used X on it very much since it is my workstation. Many other X-related packages got upgraded at the same time with xserver-xsun and I am not sure if they would need to be replaced with old versions as well. -- "pienena / Paavo "Rainbow Rat" Hartikainen minusta / E-mail: [EMAIL PROTECTED] tulee / URL: http://www.sci.fi/~pahartik/ rotta" / EFnet: pahartik at #Atari and #LionKing
Option for XSun log file location?
Hi there, is it possible to change the file XSun writes its error messages to? I had a look at the man page, tried "Xsun -help" and searched across newgroups, but didn't find anything. :( The man page from XServer(1) says: /usr/adm/Xnmsgs Error log file for display number n if run from init(8) (Yes, I do run XSun from init..) Background: I'd like to have the logs from the X server, but in my case /usr is a shared file system which is write protected as well... So logging isn't very successful yet. ;) And what does the X server do if it can't write its log file, as in my case? By the way, I'd create log files somewhere below /var, not /usr... maybe /var/X11/.. Any help is greatly appreciated! Thanks! Andreas Jaehnigen
Re: SMP Sparc32...
Something I thought of... they sure look like I would think Dual MBus processors would look like. Anyone know where I can find 5016224001130 (also has 55 03 9335 -3 Rev b). If it really isn't a Dual processor module then that would explain some of it. Brian Macy Brian Macy wrote: > > I have a Sparc 10... just got a v2.25 PROM and a pair of Ross Dual 55MHz > modules. A couple of things (some not Debian related): > - I have to set the system buss to 72MHz (4x16.6MHz) or it will never > complete post > - Even though each module is a Dual processor module the PROM only shows > one processor per card... which is what Linux also what sees > - When booting into Linux with a non-SMP kernel (2.2.17pre1) it detects > both processors and boots fine until the SCSI driver loads. It then > locks where it would normally show the results of the buss scan. The > debian 2.2.15 (I think) kernel that I tftpboot'd with also gives the > identical results. > > I'll try an SMP kernel later but this has got me a bit perplexed... > almost like I forgot a jumper or something that scans for multiple > processors on an MBus module (like SCSI LUNs). > > Brian Macy > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: test this ! (hard lockups)
On 21 Jun 2000, Tibor Simko wrote: > Sergey V Kovalyov <[EMAIL PROTECTED]> writes: > > > strace -ff -p `pidof ident` > > and telnet from another machine to e.g. port 113 > > Assuming you meant "inetd" here. My Ultra-5 box (synced with current Oops... Of course inetd ! > potato) survives without problems. Aha.. So Ultra works fine. Others ? Sergey.
Re: test this ! (hard lockups)
Sergey V Kovalyov <[EMAIL PROTECTED]> writes: > strace -ff -p `pidof ident` > and telnet from another machine to e.g. port 113 Assuming you meant "inetd" here. My Ultra-5 box (synced with current potato) survives without problems. cheers -- TS
Re: new Ultra 5 "reproducible" XF86_Mach64 lockups
Hein Roehrig <[EMAIL PROTECTED]> writes: > I have a problem with XF86_Mach64 crashing and/or locking up the > system when the "jigsaw" screen saver has run for a few minutes. I was able to reproduce the XF86_Mach64 crash by running xscreensaver overnight. (No lockup, but the screen gets into an unusable state; the 3-key soft reset works.) > Thanks in advance for any advice, FWIW I'm using xlockmore and have not seen such a problem, even when xlock runs for a long time (overnight). cheers -- TS
SMP Sparc32...
I have a Sparc 10... just got a v2.25 PROM and a pair of Ross Dual 55MHz modules. A couple of things (some not Debian related): - I have to set the system buss to 72MHz (4x16.6MHz) or it will never complete post - Even though each module is a Dual processor module the PROM only shows one processor per card... which is what Linux also what sees - When booting into Linux with a non-SMP kernel (2.2.17pre1) it detects both processors and boots fine until the SCSI driver loads. It then locks where it would normally show the results of the buss scan. The debian 2.2.15 (I think) kernel that I tftpboot'd with also gives the identical results. I'll try an SMP kernel later but this has got me a bit perplexed... almost like I forgot a jumper or something that scans for multiple processors on an MBus module (like SCSI LUNs). Brian Macy
