I am wondering if anyone has encountered the same problems. I have installed dual boot with Mandrake 10 and windows XP. When i turn on my computer if either frozes before the LILO or restarts after i have chosen the operating. Recently when Windows was chosen the computer didn't load XP at all. In addition while i am working with linux, the computer frozes at any time, or just reboots. i would appreciate any help from people who have had the same experience with their PC.
I had a similar experience with an old pc, when, um, the cpu heatsink fell off... surprisingly it would actually run for a little while although it was a P60 or something.... and it was in a cold room. :) On 24/02/06, Paul, Jean R <jrpaul@essex.ac.uk> wrote:
I am wondering if anyone has encountered the same problems. I have installed dual boot with Mandrake 10 and windows XP. When i turn on my computer if either frozes before the LILO or restarts after i have chosen the operating. Recently when Windows was chosen the computer didn't load XP at all.
In addition while i am working with linux, the computer frozes at any time, or just reboots. i would appreciate any help from people who have had the same experience with their PC.
_______________________________________________ main@lists.alug.org.uk http://www.alug.org.uk/ http://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!
On 2/24/06, Paul, Jean R <jrpaul@essex.ac.uk> wrote:
I am wondering if anyone has encountered the same problems. I have installed dual boot with Mandrake 10 and windows XP. When i turn on my computer if either frozes before the LILO or restarts after i have chosen the operating. Recently when Windows was chosen the computer didn't load XP at all.
In addition while i am working with linux, the computer frozes at any time, or just reboots. i would appreciate any help from people who have had the same experience with their PC.
If Linux is freezing, suddenly rebooting and struggling to reach the LILO prompt, I would suspect either bad memory, bad CPU, bad something else on the motherboard, or maybe a bad disk. Good luck, Tim.
On Fri, 2006-02-24 at 15:37 +0000, Paul, Jean R wrote:
In addition while i am working with linux, the computer frozes at any time, or just reboots. i would appreciate any help from people who have had the same experience with their PC.
The first place to start is with the Memory...Bad ram can cause the problems you mention and be very very intermittent...I have seen RAM pass tests reliably until it is a certain temperature, ram fail until it is removed and reinserted into it's socket and ram fail until the BIOS settings are changed. Grab a memtest iso and make yourself a memtest CD....Some distributions include this on the installation media and offer it as a boot option. http://www.memtest86.com/ Run it overnight (or for at least 6-10 full passes) to be sure. Also if your bios supports PC health status (a lot of modern ones do) then check the CPU temp is within normal operating limits (what these are will depend on your CPU) I've had faulty PSU's cause a similar problem, so if you have access to a spare one then try it....I also had this repeatedly with a particular Epox mainboard (8RGA I think). Unfortunately without the right test equipment fault finding these problems can come down to replacing components until the problem goes away...
This is a very good first test when assessing a second hand unit. This can be simply installed with debian. see below, for package details, I was trawling debian for some good packages and one day I rebooted and saw memtest86 in grub, now its part of my computer recycling routine. Pentium III 500 computers are very cheap and provide a fast responsive desktop for windows users who can live with the debian stability and low maintenance while using a slightly older gnome desktop which is just fine. Myself icewm, xterm, skippy. regards Owen $apt-cache search memtest hwtools - collection of tools for low-level hardware management kernel-patch-badram - Kernel patch allowing to use partly-bad RAM modules memtest86 - A thorough real-mode memory tester memtest86+ - thorough real-mode memory tester memtester - A utility for testing the memory subsystem sysutils - Miscellaneous small system utilities. $apt-cache show memtest86 Package: memtest86 Priority: optional Section: misc Installed-Size: 152 Maintainer: Yann Dirson <dirson@debian.org> Architecture: i386 Version: 3.2-1.1 Suggests: hwtools, sysutils, kernel-patch-badram, memtest86+, grub (>=0.95+cvs2 0040624), mtools Filename: pool/main/m/memtest86/memtest86_3.2-1.1_i386.deb Size: 57510 MD5sum: b05e1f2608d79aef64840183584ed119 Description: A thorough real-mode memory tester Memtest86 scans your RAM for errors. . This version is apparently not as actively maintained upstream as memtest86+ is. Especially if you own a recent computer on which it does not work, you should consider looking at the memtest86+ package. . This tester runs independently of any OS - it is run at computer boot-up, so that it can test *all* of you memory. You may want to look at `memtest' (in package `sysutils'), which allows to test your memory within Linux, but this one won't be able to test your whole RAM. . This used to be part of the hwtools package, which still contains another real-mode memory tester (memmxtest) optimized for mmx machines (but apparently not maintained any more). . It can output a list of bad RAM regions usable by the BadRAM kernel patch, so that you can still use you old RAM with one or 2 bad bits. . A convenience script is also provided to make a grub-based floppy or image. $apt-cache search memtest hwtools - collection of tools for low-level hardware management kernel-patch-badram - Kernel patch allowing to use partly-bad RAM modules memtest86 - A thorough real-mode memory tester memtest86+ - thorough real-mode memory tester memtester - A utility for testing the memory subsystem sysutils - Miscellaneous small system utilities. $apt-cache show memtest86 Package: memtest86 Priority: optional Section: misc Installed-Size: 152 Maintainer: Yann Dirson <dirson@debian.org> Architecture: i386 Version: 3.2-1.1 Suggests: hwtools, sysutils, kernel-patch-badram, memtest86+, grub (>= 0.95+cvs2 0040624), mtools Filename: pool/main/m/memtest86/memtest86_3.2-1.1_i386.deb Size: 57510 MD5sum: b05e1f2608d79aef64840183584ed119 Description: A thorough real-mode memory tester Memtest86 scans your RAM for errors. . This version is apparently not as actively maintained upstream as memtest86+ is. Especially if you own a recent computer on which it does not work, you should consider looking at the memtest86+ package. . This tester runs independently of any OS - it is run at computer boot-up, so that it can test *all* of you memory. You may want to look at `memtest' (in package `sysutils'), which allows to test your memory within Linux, but this one won't be able to test your whole RAM. . This used to be part of the hwtools package, which still contains another real-mode memory tester (memmxtest) optimized for mmx machines (but apparently not maintained any more). . It can output a list of bad RAM regions usable by the BadRAM kernel patch, so that you can still use you old RAM with one or 2 bad bits. . A convenience script is also provided to make a grub-based floppy or image. On Fri, 24 Feb 2006 23:01:12 +0000 Wayne Stallwood <ALUGlist@digimatic.plus.com> wrote:
On Fri, 2006-02-24 at 15:37 +0000, Paul, Jean R wrote:
In addition while i am working with linux, the computer frozes at any time, or just reboots. i would appreciate any help from people who have had the same experience with their PC.
The first place to start is with the Memory...Bad ram can cause the problems you mention and be very very intermittent...I have seen RAM pass tests reliably until it is a certain temperature, ram fail until it is removed and reinserted into it's socket and ram fail until the BIOS settings are changed.
Grab a memtest iso and make yourself a memtest CD....Some distributions include this on the installation media and offer it as a boot option.
Run it overnight (or for at least 6-10 full passes) to be sure.
Also if your bios supports PC health status (a lot of modern ones do) then check the CPU temp is within normal operating limits (what these are will depend on your CPU)
I've had faulty PSU's cause a similar problem, so if you have access to a spare one then try it....I also had this repeatedly with a particular Epox mainboard (8RGA I think).
Unfortunately without the right test equipment fault finding these problems can come down to replacing components until the problem goes away...
_______________________________________________ main@lists.alug.org.uk http://www.alug.org.uk/ http://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!
Apologies for random post - ergates was asking in #alug earlier today about various latex stuff - i suggested using smarty as a template engine to generate different looking systems for generating the latex code as opposed to hardcoding the latex code into the php engine (the idea is that you hve a set of data stored in a database, pull out into a latex document that you then compile). I've just written the sort of thing that I was trying to explain and wondered if anyone else had any ideas on how to improve such a system - mine is now sitting at: http://cornflakes.imen.org.uk/~jt/smartytex/ Issues atm... 1) I was having trouble with auto loading the pdf in the right pane on compile - I couldnt seem to get an onload() function to call the myload javascript call - but javascript is not my strong point... 2) You can select between an Article (with the content in sections) or a Book (with the content in chapters). 3) It dosnt remember on the frame=left the values you put in for last time - partially this is because I am very tired and its only a demo atm... 4) You can only use it one person at a time - i could tie the file it writes and works with in as being tied to a random number attached to a session to allow more then one person work on it at once, but again, that takes it beyond the scope for this current session. 5) Some people may have security concerns over certain files on the server having to be written to by root in the public directory, but I think these files are tied down enough. However ... I am a little concerned about runing the latex command because i *THINK* there may be a shell execute command inside of latex, - because of that, I am passing through a simple clean function which screws up any attempts at latex commands... of course better regex should be put in place to clean latex to allow latex commands but not any dangerous ones Thanks JT
participants (6)
-
James Taylor -
Owen Synge -
Paul, Jean R -
rob page -
Tim Green -
Wayne Stallwood