Lads, I don't know if this is a coincidence of not, but since I brought my PC home after alug3, if I connect to it from any other PC using X the machine hangs totally. The only cure is the reset button. Telnet works just fine, and X works fine on the machine itself. Does anyone have any idea what this might be or how to get around it? I recompiled to kernel cleanly and from scratch (we did that a few times on Sunday!), and that didn't help at all. Cheers, Laurie. [ This email came to you via the Anglian Linux User Group list ] [ If you only wish to recieve event announcements, email the ] [ SUBJECTs of "unsubscribe alug" and "subscribe alug-announce" ] [ to listserver@stu.uea.ac.uk -- We do need your support, tho' ]
On 06-Sep-99 Laurie Brown wrote:
Lads,
I don't know if this is a coincidence of not, but since I brought my PC home after alug3, if I connect to it from any other PC using X the machine hangs totally. The only cure is the reset button. Telnet works just fine, and X works fine on the machine itself.
Does anyone have any idea what this might be or how to get around it?
I recompiled to kernel cleanly and from scratch (we did that a few times on Sunday!), and that didn't help at all. At ALUG you may have set up a route to a host that is no longer on your network. If so, eventually (about 5-10 mins) the system will time out and the normal login prompt will appear.
In any case, since telnet works, it is something between when inetd is started and the end of the rc.d processing. -- Politics: The conduct of public affairs for private advantage Ambrose Bierce Raphael Mankin E-Mail: raph@panache.demon.co.uk ---------------------------------- [ This email came to you via the Anglian Linux User Group list ] [ If you only wish to recieve event announcements, email the ] [ SUBJECTs of "unsubscribe alug" and "subscribe alug-announce" ] [ to listserver@stu.uea.ac.uk -- We do need your support, tho' ]
Raphael Mankin wrote:
On 06-Sep-99 Laurie Brown wrote:
Lads,
I don't know if this is a coincidence of not, but since I brought my PC home after alug3, if I connect to it from any other PC using X the machine hangs totally. The only cure is the reset button. Telnet works just fine, and X works fine on the machine itself.
Does anyone have any idea what this might be or how to get around it?
I recompiled to kernel cleanly and from scratch (we did that a few times on Sunday!), and that didn't help at all. At ALUG you may have set up a route to a host that is no longer on your network. If so, eventually (about 5-10 mins) the system will time out and the normal login prompt will appear.
In any case, since telnet works, it is something between when inetd is started and the end of the rc.d processing. -- Politics: The conduct of public affairs for private advantage Ambrose Bierce Raphael Mankin
Routing is fine, Raphael, I have no idea what's causing this. Cheers, Laurie. [ This email came to you via the Anglian Linux User Group list ] [ If you only wish to recieve event announcements, email the ] [ SUBJECTs of "unsubscribe alug" and "subscribe alug-announce" ] [ to listserver@stu.uea.ac.uk -- We do need your support, tho' ]
Laurie Brown wrote:
Raphael Mankin wrote:
On 06-Sep-99 Laurie Brown wrote:
Lads,
I don't know if this is a coincidence of not, but since I brought my PC home after alug3, if I connect to it from any other PC using X the machine hangs totally. The only cure is the reset button. Telnet works just fine, and X works fine on the machine itself.
can you explain what you mean by 'connecting to it from any other PC using X'.. are you using another linux box to connect from an xterm, or are you 'setenv DISPLAY okmachine:0' and trying to run X apps ?? Also is it the machine which hangs, or just X.. I have had some experiences with q3test which takes out X, and because X has the keyboard I can't hit ctrl-bkspace.. If you can telnet in though it would much nicer to your box if you 'su' and 'shutdown -r now' ;).. anything in the mesage logs which you might want to share with us ?? Scoobz
Does anyone have any idea what this might be or how to get around it?
I recompiled to kernel cleanly and from scratch (we did that a few times on Sunday!), and that didn't help at all.
At ALUG you may have set up a route to a host that is no longer on your network. If so, eventually (about 5-10 mins) the system will time out and the normal login prompt will appear.
In any case, since telnet works, it is something between when inetd is started and the end of the rc.d processing. -- Politics: The conduct of public affairs for private advantage Ambrose Bierce Raphael Mankin
Routing is fine, Raphael, I have no idea what's causing this.
Cheers, Laurie.
[ This email came to you via the Anglian Linux User Group list ] [ If you only wish to recieve event announcements, email the ] [ SUBJECTs of "unsubscribe alug" and "subscribe alug-announce" ] [ to listserver@stu.uea.ac.uk -- We do need your support, tho' ]
-- ---------------------------------------------------------------------- Neill Newman Tel: Mobile 07970 673722 Department of Electronics Systems Engineering Work 01206 873708 University of Essex Fax: Work 01206 872900 http://wearables.essex.ac.uk/index.html email: njnewm@essex.ac.uk ---------------------------------------------------------------------- [ This email came to you via the Anglian Linux User Group list ] [ If you only wish to recieve event announcements, email the ] [ SUBJECTs of "unsubscribe alug" and "subscribe alug-announce" ] [ to listserver@stu.uea.ac.uk -- We do need your support, tho' ]
Neill Newman wrote:
Laurie Brown wrote:
Raphael Mankin wrote:
On 06-Sep-99 Laurie Brown wrote:
Lads,
I don't know if this is a coincidence of not, but since I brought my PC home after alug3, if I connect to it from any other PC using X the machine hangs totally. The only cure is the reset button. Telnet works just fine, and X works fine on the machine itself.
can you explain what you mean by 'connecting to it from any other PC using X'.. are you using another linux box to connect from an xterm, or are you 'setenv DISPLAY okmachine:0' and trying to run X apps ??
I'm using x-win32 from one of 2 '95 PCs, into my home Linux box. I've never had a problem with this before.
Also is it the machine which hangs, or just X.. I have had some experiences with q3test which takes out X, and because X has the keyboard I can't hit ctrl-bkspace.. If you can telnet in though it would much nicer to your box if you 'su' and 'shutdown -r now' ;)..
It's the whole machine, whatever kernel I use (including the standard 2.2.5 which came with SuSE 6.1). I can't telnet in, and can get no response from any key strokes, mouse, SFA.
anything in the mesage logs which you might want to share with us ??
Can't find anything, but I may not be looking in the right place, of course! Pointers? The main reason I posted here (I'd probably rebuild, to be honest), is that we mucked about with the PC a fair bit at alug3, and someone might remember somnething they or I did. Cheers, Laurie.
Scoobz
[ This email came to you via the Anglian Linux User Group list ] [ If you only wish to recieve event announcements, email the ] [ SUBJECTs of "unsubscribe alug" and "subscribe alug-announce" ] [ to listserver@stu.uea.ac.uk -- We do need your support, tho' ]
Raphael Mankin wrote: [SNIP]
In any case, since telnet works, it is something between when inetd is started and the end of the rc.d processing.
Telnet works up until I use X, and then it just dies on me. I'll try again, and give it a while to see if it times out. Cheers, Laurie. [ This email came to you via the Anglian Linux User Group list ] [ If you only wish to recieve event announcements, email the ] [ SUBJECTs of "unsubscribe alug" and "subscribe alug-announce" ] [ to listserver@stu.uea.ac.uk -- We do need your support, tho' ]
Laurie Brown wrote:
Raphael Mankin wrote:
[SNIP]
In any case, since telnet works, it is something between when inetd is started and the end of the rc.d processing.
Telnet works up until I use X, and then it just dies on me. I'll try again, and give it a while to see if it times out.
hhmm logs/kernel version/X version needed.. try running X and piping the output to a file and posting.. Sz
Cheers, Laurie.
[ This email came to you via the Anglian Linux User Group list ] [ If you only wish to recieve event announcements, email the ] [ SUBJECTs of "unsubscribe alug" and "subscribe alug-announce" ] [ to listserver@stu.uea.ac.uk -- We do need your support, tho' ]
-- ---------------------------------------------------------------------- Neill Newman Tel: Mobile 07970 673722 Department of Electronics Systems Engineering Work 01206 873708 University of Essex Fax: Work 01206 872900 http://wearables.essex.ac.uk/index.html email: njnewm@essex.ac.uk ---------------------------------------------------------------------- [ This email came to you via the Anglian Linux User Group list ] [ If you only wish to recieve event announcements, email the ] [ SUBJECTs of "unsubscribe alug" and "subscribe alug-announce" ] [ to listserver@stu.uea.ac.uk -- We do need your support, tho' ]
Neill Newman wrote:
Laurie Brown wrote:
Raphael Mankin wrote:
[SNIP]
In any case, since telnet works, it is something between when inetd is started and the end of the rc.d processing.
Telnet works up until I use X, and then it just dies on me. I'll try again, and give it a while to see if it times out.
hhmm logs/kernel version/X version needed.. try running X and piping the output to a file and posting..
Sz
No problem (I'm running 2.2.12 kernel, not 2.0.36 as it says here): ---- cut here ---- XFree86 Version 3.3.3.1 / X Window System (protocol Version 11, revision 0, vendor release 6300) Release Date: January 4 1999 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (see http://www.XFree86.Org/FAQ) Operating System: Linux 2.0.36 i686 [ELF] Configured drivers: S3: accelerated server for S3 graphics adaptors (Patchlevel 0) newmmio, mmio_928, s3_generic (using VT number 7) XF86Config: /etc/XF86Config (**) stands for supplied, (--) stands for probed/default values (**) XKB: rules: "xfree86" (**) XKB: model: "pc104" (**) XKB: layout: "gb" (**) Mouse: type: PS/2, device: /dev/psaux, samplerate: 60 (**) Mouse: buttons: 3 (**) S3: Graphics device ID: "Primary-Card" (**) S3: Monitor ID: "Primary-Monitor" (--) S3: Mode "1600x1000" needs vert refresh rate of 33.14 Hz. Deleted. (--) S3: Mode "1280x960" needs vert refresh rate of 43.07 Hz. Deleted. (--) S3: Mode "1600x1200" needs vert refresh rate of 27.61 Hz. Deleted. (--) S3: Mode "1280x1024" needs vert refresh rate of 40.37 Hz. Deleted. (**) FontPath set to "/usr/X11R6/lib/X11/fonts/75dpi:unscaled,/usr/X11R6/lib/X11/fonts/100dpi:unscaled,/usr/X11R6/lib/X11/fonts/Type1,/usr/X11R6/lib/X11/fonts/URW,/usr/X11R6/lib/X11/fonts/Speedo,/usr/X11R6/lib/X11/fonts/misc,/usr/X11R6/lib/X11/fonts/75dpi,/usr/X11R6/lib/X11/fonts/100dpi" (--) S3: PCI: Trio32/64 rev 0, Linear FB @ 0xe5000000 (--) S3: chipset: Trio64 rev. 2 (--) S3: chipset driver: mmio_928 (--) S3: card type: PCI (--) S3: Diamond Stealth BIOS found (**) S3: videoram: 2048k (--) S3: Ramdac type: s3_trio64 (--) S3: Ramdac speed: 135 MHz (--) S3: Using Trio32/64 programmable clock (MCLK 59.957 MHz) (--) S3: Maximum allowed dot-clock: 80.000 MHz (**) S3: Mode "800x600": mode clock = 52.000 (**) S3: Using 16 bpp. Color weight: 565 (--) S3: Virtual resolution set to 800x600 (--) S3: Local bus LAW is 0xE5000000 (--) S3: Using a banksize of 2048k, line width of 800 (--) S3: Using a single 64x64 area at (736,601) for expanding pixmaps (--) S3: Using 16 planes of 736x709 at (0,601) aligned 8 as font cache Starting kfm -d...Done. Starting kcontrol -init...Done. Starting kbgndwm...Done. Starting krootwm...Done. Starting kpanel...Done. Some pixmaps are not valid: GimmickMode dissabled KBackground::KBackground KScreenSaver::KScreenSaver KFonts::KFonts KGeneral::KGeneral inserted keys read settings got key dict KKeyChooser::readGlobalKeys() Make key chooser standard Change: Replace Change: Next Change: Copy Change: Undo Change: Close Change: Prior Change: Open Change: Find Change: Insert Change: End Change: Print Change: New Change: Quit Change: Save Change: Home Change: Paste Change: Cut Change: Help read scheme done KKeyConfig destructor inserted keys read settings got key dict KKeyChooser::readGlobalKeys() Make key chooser standard Change: Replace Change: Next Change: Copy Change: Undo Change: Close Change: Prior Change: Open Change: Find Change: Insert Change: End Change: Print Change: New Change: Quit Change: Save Change: Home Change: Paste Change: Cut Change: Help read scheme done KKeyConfig destructor add top window add top window [ This email came to you via the Anglian Linux User Group list ] [ If you only wish to recieve event announcements, email the ] [ SUBJECTs of "unsubscribe alug" and "subscribe alug-announce" ] [ to listserver@stu.uea.ac.uk -- We do need your support, tho' ]
Laurie Brown wrote:
Neill Newman wrote:
Laurie Brown wrote:
Raphael Mankin wrote:
[SNIP]
In any case, since telnet works, it is something between when inetd is started and the end of the rc.d processing.
Telnet works up until I use X, and then it just dies on me. I'll try again, and give it a while to see if it times out.
hhmm logs/kernel version/X version needed.. try running X and piping the output to a file and posting..
Sz
No problem (I'm running 2.2.12 kernel, not 2.0.36 as it says here):
hhmm this is very weird.. ok, there is a new version of XFree86 out I would first try that.. also how long have you been using 2.2.12 ?? maybe there is a weird race which is causign it, do you still have another kernel (a 2.0 perhaps) can you verify the problem under other kernel versions ?? mmhhh.. interesting.. let me know what happens ;).. Neill
---- cut here ----
XFree86 Version 3.3.3.1 / X Window System (protocol Version 11, revision 0, vendor release 6300) Release Date: January 4 1999 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (see http://www.XFree86.Org/FAQ) Operating System: Linux 2.0.36 i686 [ELF] Configured drivers: S3: accelerated server for S3 graphics adaptors (Patchlevel 0) newmmio, mmio_928, s3_generic (using VT number 7)
XF86Config: /etc/XF86Config (**) stands for supplied, (--) stands for probed/default values (**) XKB: rules: "xfree86" (**) XKB: model: "pc104" (**) XKB: layout: "gb" (**) Mouse: type: PS/2, device: /dev/psaux, samplerate: 60 (**) Mouse: buttons: 3 (**) S3: Graphics device ID: "Primary-Card" (**) S3: Monitor ID: "Primary-Monitor" (--) S3: Mode "1600x1000" needs vert refresh rate of 33.14 Hz. Deleted. (--) S3: Mode "1280x960" needs vert refresh rate of 43.07 Hz. Deleted. (--) S3: Mode "1600x1200" needs vert refresh rate of 27.61 Hz. Deleted. (--) S3: Mode "1280x1024" needs vert refresh rate of 40.37 Hz. Deleted. (**) FontPath set to "/usr/X11R6/lib/X11/fonts/75dpi:unscaled,/usr/X11R6/lib/X11/fonts/100dpi:unscaled,/usr/X11R6/lib/X11/fonts/Type1,/usr/X11R6/lib/X11/fonts/URW,/usr/X11R6/lib/X11/fonts/Speedo,/usr/X11R6/lib/X11/fonts/misc,/usr/X11R6/lib/X11/fonts/75dpi,/usr/X11R6/lib/X11/fonts/100dpi" (--) S3: PCI: Trio32/64 rev 0, Linear FB @ 0xe5000000 (--) S3: chipset: Trio64 rev. 2 (--) S3: chipset driver: mmio_928 (--) S3: card type: PCI (--) S3: Diamond Stealth BIOS found (**) S3: videoram: 2048k (--) S3: Ramdac type: s3_trio64 (--) S3: Ramdac speed: 135 MHz (--) S3: Using Trio32/64 programmable clock (MCLK 59.957 MHz) (--) S3: Maximum allowed dot-clock: 80.000 MHz (**) S3: Mode "800x600": mode clock = 52.000 (**) S3: Using 16 bpp. Color weight: 565 (--) S3: Virtual resolution set to 800x600 (--) S3: Local bus LAW is 0xE5000000 (--) S3: Using a banksize of 2048k, line width of 800 (--) S3: Using a single 64x64 area at (736,601) for expanding pixmaps (--) S3: Using 16 planes of 736x709 at (0,601) aligned 8 as font cache Starting kfm -d...Done. Starting kcontrol -init...Done. Starting kbgndwm...Done. Starting krootwm...Done. Starting kpanel...Done. Some pixmaps are not valid: GimmickMode dissabled KBackground::KBackground KScreenSaver::KScreenSaver KFonts::KFonts KGeneral::KGeneral inserted keys read settings got key dict KKeyChooser::readGlobalKeys() Make key chooser standard Change: Replace Change: Next Change: Copy Change: Undo Change: Close Change: Prior Change: Open Change: Find Change: Insert Change: End Change: Print Change: New Change: Quit Change: Save Change: Home Change: Paste Change: Cut Change: Help read scheme done KKeyConfig destructor inserted keys read settings got key dict KKeyChooser::readGlobalKeys() Make key chooser standard Change: Replace Change: Next Change: Copy Change: Undo Change: Close Change: Prior Change: Open Change: Find Change: Insert Change: End Change: Print Change: New Change: Quit Change: Save Change: Home Change: Paste Change: Cut Change: Help read scheme done KKeyConfig destructor add top window add top window
[ This email came to you via the Anglian Linux User Group list ] [ If you only wish to recieve event announcements, email the ] [ SUBJECTs of "unsubscribe alug" and "subscribe alug-announce" ] [ to listserver@stu.uea.ac.uk -- We do need your support, tho' ]
-- ---------------------------------------------------------------------- Neill Newman Tel: Mobile 07970 673722 Department of Electronics Systems Engineering Work 01206 873708 University of Essex Fax: Work 01206 872900 http://wearables.essex.ac.uk/index.html email: njnewm@essex.ac.uk ---------------------------------------------------------------------- [ This email came to you via the Anglian Linux User Group list ] [ If you only wish to recieve event announcements, email the ] [ SUBJECTs of "unsubscribe alug" and "subscribe alug-announce" ] [ to listserver@stu.uea.ac.uk -- We do need your support, tho' ]
Neill Newman wrote:
hhmm this is very weird.. ok, there is a new version of XFree86 out I would first try that.. also how long have you been using 2.2.12 ?? maybe there is a weird race which is causign it, do you still have another kernel (a 2.0 perhaps) can you verify the problem under other kernel versions ?? mmhhh.. interesting.. let me know what happens ;)..
I've tried 2.2.5 and 2.2.12, same result. I think I've still got 2.0.36 on the PC, I'll check. I've got hiold of SuSE 6.2, and I'll run that in over the weekend. It'll update a few bits and pieces, and maybe it'll clear it. However, I'm sure we did something on Sunday to cause this! Cheers, Laurie. [ This email came to you via the Anglian Linux User Group list ] [ If you only wish to recieve event announcements, email the ] [ SUBJECTs of "unsubscribe alug" and "subscribe alug-announce" ] [ to listserver@stu.uea.ac.uk -- We do need your support, tho' ]
participants (3)
-
Laurie Brown -
Neill Newman -
Raphael Mankin