Ok I was tired of windows crashing so I get SuSE 8.0 & the thing freezes most of the time it comes back in a few secs, but the last few times it has not come back, lasted atleast a min, it sems to only realy happen when I enter YaST2, or some part of it & I had to reboot the last few times (3 I think) someone said I might need to recompile my kernel. Well I can't do that it is annoying and a awful reminder of windows. Maybe I need to end some survices, I got rid of sendmail, and everthing to do with it. I stopped the NSCD. What else should I stop?

It might as well be an hardware issue. Post your setup.

ECS K7S5A motherboard with SiS 7012 wave onboard sound & onboard SiS 900 PCI fast Ethernet, AMD Thunderbird 1Gig, 256meg SDRAM, AGP Elsa Gladiac 511 Geforce2 MX400 with 64meg of video ram with USB mouse abd keyboard

ok try so-called fix for Athlon bug
in the /etc/lilo.conf
after root entry on a separate line add:
append="mem=nopentium"
and rerun lilo
/sbin/lilo
everything must be done as root
See if it clears the problem.
Also I encourage you to have a look at memtest86 http://www.memtest86.com/ it is a little utility to stress test your computer's memory.

what do you mean rerun lilo? I added it at the begining of lilo, that should do it right?

It must be the entry within image definition and path to working kernel
like this

image=/boot/must_work
label=linux_athy
root=/dev/hda8
append="hdc=ide-scsi mem=nopentium"
read-only
initrd=/boot/initrd-2.5.20.img

After you edited lilo configuration file re-run lilo as root
/sbin/lilo -v

So just adding mem=nopentium to lilo.conf won't work?

This was a snapshot of my /etc/lilo.conf. If yours has an append entry already add mem=nopentium as I highlighted it, if there is no append statement in the file then add it
append="mem=nopentium" teh best place to add it is below the root=/.... entry

so put append="mem=nopentium" just likke that with quotes and everything is there a certain place or just add it to the file anyware? Is this good?

append="mem=nopentium"
boot = /dev/hda
change-rules
reset
read-only
menu-scheme = Wg:kw:Wg:Wg
lba32
prompt
timeout = 120
message = /boot/message
default = windows

other = /dev/hda1
label = windows

image = /boot/vmlinuz
label = linux

It still locks up, and I don't think it is a AMD bug, SuSE's site says 8.0 Personal is amd compatible. Could upgrading konqueror help?

Sup. First of all, I have used SuSE (still do) on several boxes.
8.0 is by far the most stable of the SuSEs. (That I have found, other than 7.3 for sparc but thats a differnt story all together)

I currently have SuSE running on a number of boxes ranging from a really really old 486x166MHz to the most up-to-date i386 archs out there.
Personally, I use NOTHING but AMD. Intel (to me) is like the M$ horde of hardware. It's fine for multimedia, and PC snooping, but not for an actual computer that requires power.

As far as your problems:
I wouldn't use Konq. It's just not worth it. SuSE comes shipped with a crap load of other proggies that can do as much and more than KingKonq.
The "locking" up problem is most likely your SiS chipsets. SiS is known to have buggy equip. On-board works fine with SuSE, but I still normally frown on on-board. You just get better perfomance and quality from external to mobo parts. At least in my world.

If you like, I'll send you a detailed list of all the systems I've used. I have actually used a mobo with SiS onboard for SuSE, but that was a while back.

L8rz

So it is my SiS chipset? Anyway around it?

No I didn't say that. Not necessarily.
I'll have to dabble a bit in my post notes to see what I can retrieve/remember.
Gimme 'bout a day or so to tread back thru all my "shtuff" and I'll see what I can do.

Deal? Pickle...

L8rz