Hi Alexey, Thank you for the suggestion. Yes I will try that. I also experience monitor going into energy save mode but then you can not "wake" the system up. I have to do a hard power cycle again. Do you think this is also related to ACPI? Sorry I was short on temper. I am on my 3rd download attempt... Babu --- Alexey Eremenko wrote:

I strongly believe that your lockups may be connected to ACPI. My recommendation is to disable ACPI. Either Install with a new SUSE system with "ACPI=off" or add that line to config file at /boot/grub/menu.lst

__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

On Sun, 2006-05-21 at 21:09 +0200, Andre Truter wrote:

On 5/21/06, babu Avedissian wrote:

...

I am experiencing periodic lockup under SuSE 10.0 x64. The machine runs fine but at random times (hours to days) will spontaneously lockup... I am using a Tyan Thunder (k8we) mobo.

I am sorry, but our magic wands are all out of order today, so you will have to give us a bit more information. Basic things, like any suspicious log messages, or did you check your memory with memtest, or did Google give any information on possible Linux problems on that specific motherboard.

[...]

...

What's up with the Crappy progress bar that shows the size of the file as 2068MB (instead of 3570MB) and once download progresses past 100% (which it must do), the precent downloaded becomes NEGATIVE, the file size becomes CRAP/JUNK and the download speed shows up as CRAP/JUNK. How hard is it to get this damn progress bar to function correct?

It would appear that you are using a webbrowser and the http protocol to download a file greater than 2G in size. This is a known problem. Try using an ftp client to do the download and the problem should go away. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998

On May 21, 2006, at 2:09 PM, Andre Truter wrote:

On 5/21/06, babu Avedissian wrote:

...

I am experiencing periodic lockup under SuSE 10.0 x64. The machine runs fine but at random times (hours to days) will spontaneously lockup... I am using a Tyan Thunder (k8we) mobo.

I am sorry, but our magic wands are all out of order today, so you will have to give us a bit more information. Basic things, like any suspicious log messages, or did you check your memory with memtest, or did Google give any information on possible Linux problems on that specific motherboard.

[...]

...

What's up with the Crappy progress bar that shows the size of the file as 2068MB (instead of 3570MB) and once download progresses past 100% (which it must do), the precent downloaded becomes NEGATIVE, the file size becomes CRAP/JUNK and the download speed shows up as CRAP/JUNK. How hard is it to get this damn progress bar to function correct?

Well, again our faulty magic wands fail to inform us which progress bar you are talking about. I am seeing many progress bars here and none is doing what you describe.

Maybe I did not install the CRAP/JUNK progress bar, but I searched for it in YaST and did not find it. Where did you download the CRAP/JUNK progress bar?

Maybe your existing SuSE system has just decided that your ATTITUDE does not give you the privilege to use Linux anymore.

Oh, and yes, we are all subscribed to this list for the sole purpose of ensuring that you have a flawless SuSE experience.

Please get your attitude in order and maybe people might actually help you. Maybe you may even solve the problem yourself if your attiude is more positive.

There are a million things that can go wrong on a computer. It could be hardware, software, temperature, network, humididy, user error, etc.

Hi, Everyone here is a customer/user like you; we try to help each other when possible. Most hangs and lockups are from HW, particularly RAM. The kernel uses memory like big systems and can quickly find bad memory, but it has little ability to tell you besides the hang. Please run Memtest86 on the whole memory sub-system (Main and all levels of Cache) for 24 hrs. Let us know what happens. Don't worry, the bad memory will probably run ok in a XP system without hangs; just passing bad data. PeterB