Baslinux mailing list

[baslinux AT lists.ibiblio.org]

On Sat, 24 Mar 2007 baslinux AT lists.ibiblio.org wrote:

> some AMD cpus (the k6 and k7 in particular) suffer from the "hlt bug"
> when used with ceartain chipsets (youll never know which they wont get
> along with till you try -- it even happenes to some OEM boxen) and the
> bug only shows when using NT/2k/xp versions of the 'doze and of course
> linux... dos and 9x arent affected because they dont issue the 'hlt'
> instruction... AFAIK there is no workaround for windows but in linux
> just add append=no-hlt to lilo.conf or to the loadlin line and linux
> will run fine...

Thanks.  How do we determine if this is such a cpu?  He gave us the 
computer (to use the case) and I offered to fix it.  If it is not fixable 
we get to keep it.  He said it 'runs hot' and has voltage spikes (we found 
neither yet, but did not do the burn-in).  He drilled holes in the case. 
He said it worked fine for a couple of years then became unreliable as a 
server.

> if the owner of that k7 insists on XP there -might- be a workaround
> thats not well known to fix it but it may not be easy to find
>
> if the system uses a VIA chipset install the "via pci latency patch"
> (windows) and it will (should anyway) cure the hangs;
> http://www.georgebreese.com/net/software/

ALI chipset.

A computer which originally had Win95 is coming Tuesday, which 'crashes 
after 2 weeks' every time she reloads XP, or ME.  For use only on the 
internet (instead of WebTV).  I will offer BL3.50 instead of XP, which is 
probably REALLY slow on a 10 year old computer.  With Sylpheed except I 
could not find any way to Compose - it is greyed out.  I probably botched 
setup.

> On 24/03/07, baslinux AT lists.ibiblio.org <baslinux AT lists.ibiblio.org> wrote:
> > http://keesan.freeshell.org/bl/cpuburn-static.tgz
> > 6263 bytes mostly documentation.
> >
> > Unpackage to a floppy disk, and copy one (or all - about 3K total) of
> > these tiny files (pick the one that matches your CPU type such as AMD K7)
> > to the free space on a BL #2 boot disk. (Steven has provided lots of extra
> > space in BL3.50).  Boot to linux, do NOT mount any file systems, and then
> > from the floppy disk run burnK7, for example, to try to crash your system.
> > It stresses the cpu and board and preserves errors - code 254 for
> > integer/memory error and 255 for FP/MMX error.  There are also two RAM
> > testers included.
> >
> > Intel burnP5 burnP6
> > AMD   burnK6 burnK7
> >
> > Someone asked us to try to fix a K7 system that 'hangs' and we would like
> > to make it crash without adding XP first.
> >
> > Billed as the cpu equivalent of memtest, but this was compiled to be run
> > from a linux root/boot disk.  It passed memtest and the PSU voltages are
> > correct.  We have a spare CPU.
> >
> > Sindi
> >
> > keesan AT sdf.lonestar.org
> > SDF Public Access UNIX System - http://sdf.lonestar.org
>
>
>
> --
> --
> --sam
> --
> Web; http://mephitus.no-ip.org/
> Skype; Mephitus
> ICQ; 51687964
> --
> "When you've done something right, no one will be sure you've done
> anything at all." -- Futurama
> --
>
> -----------------------
> BasicLinux mailing list
> -----------------------
> http://www.basiclinux.com.ru
> http://www.ibiblio.org/pub/linux/distributions/baslinux/
> ------------------------------------
> To exit, send subject=unsubscribe to
> baslinux-request AT lists.ibiblio.org

keesan AT sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org