I use SuSE Linux on my Thinkpat A31p since, since I have forgotten my first version. The last one was 10.3 with KDE 4.0. It was not perfect, but working.
Now I did a new install of 11.1 (KDE 4.1) and my laptop freezes after a short time. The freeze is complete, no mouse move, no ctrl-alt-backspace, no ctrl-alt-F1 and so on.
The fan keeps working hard, so the cpu seems to do something.
I reinstalled: freeze. I installed Gnome: freeze. I changed the xorg.conf from the one of my backup: freeze.
I suspected the sound driver (snd_intel8x0) and tried to delete it in yast: freeze.
I tried to boot with brokenmodule=snd_intel8x0: freeze. May be it’s not the sound driver.
Obviously I tried the failsafe boot: freeze.
ext3 and reiserfs are really robust! :-)(
When I boot from the DVD to do the install it works for hours. It’s the resulting system which has somewhere a hitchup. I don’t know how to trace it. Sometimes it freezes after some minutes, sometimes after some seconds.
When I reboot and do nothing, it freezes also.
I am using another operating system to write this and will revert back to 10.3. But it’s a pity. Has someone an idea how to trace it?
I don’t give up so easily. Yes, I will revert soon to 10.3, but there is a bug and I want to help to find it.
The help I need is how to isolate the wrong module. But I am not a deep linux expert.
when I boot failsafe the display resolution is a different one. Without studying the boot parameters I supporse that failsafe uses the frame buffer instead of the radeon driver. Is it right? If yes the error is not in the radeon driver.
when I boot in init 3, there are no problems. It’s the desktop which freezes. But both kde4 and gnome freezed, so it’s not the desktop itself.
it might be the X-server. Is there a chance to play with different X-Servers?
when I boot from the install DVD all works. Which is the environment which is in use during install? Where is the difference to the normal use?
I have detected the sysconfig file and will try different window managers.
I don’t love to boot windows to write to this forum. Is there somewhere a how-to to install a second linux upon the same partition and insert it into grub?
another note: it seems to be correlated with closing windows (just experienced it twice with terminal windows); I think it freezes before the window actually closes. This is now occurring on my desktop, which has a core2 4300, 4gb of ram, and an nvidia gtx 260 driver version 177.82 on 64-bit opensuse 11.1.
purna chakra wrote:
> It is related to network card. Here are two kernel failure messages that
> popped up on my desktop.
> I find Ubuntu guys have released a patch. Is there any news
> from Suse folks?
The code is completely different in current kernels, thus I think
there is a fix. I cannot speak for the openSUSE time frame to
implement these changes, but if you want the latest wireless drivers,
download the campat-wireless code from http://wireless.kernel.org/en/users/Download and build it.
Unfortunately, there is no RPM package for this material.
Having the same problem on a Dell Vostro 1400, core2 2.4, 4GB, intel wireless. System freezes 5-10 minutes after login. Numlock and scoll lock flash on off at a steady rate. Same thing with a brand new install of Ubuntu 8.10. Sometimes Ubuntu lasts long enough to patch. I turned off the wireless and it has been running for about an hour fine. Sort of useless without wireless but hopefully I’ll find a fix I can handle.
Linux oliver 126.96.36.199-9-default #1 SMP 2008-12-04 18:10:04 +0100 x86_64 x86_64 x86_64 GNU/Linux
It always happens when I try to close windows. Some applications, e.g. kwrite, never freeze, whereas others, such as Firefox, freeze sporadically, and kate – when I’m using my default 3-window session, almost always freezes. The freezes are of varying length: sometimes as short as 20 seconds, usually around 30-40, and I’m sure they’ve exceeded a minute.
Also, audio continues to play but Amarok won’t advance to the next track (waiting for a UI update?). All X11 actions (keyboard and mouse input) are delayed until the screen un-freezes, where they happen all at once.
Any updates would be appreciated; after living with it for quite a while, I’m finally starting to think about switching distros…
I had a similar problem that i solved changing the defaults into yeast partitioning tool.
Into the fstab options dialog, the partitioning tool is set normally to mount your hdd partitions identifying them by id.
So you have an /etc/fstab file with rows like:
I solved the problem changing the radio button, into fstab options dialog of the partitioning tool, to “device name” from “id name”.
When you apply your change you will have an /etc/fstab file with rows like: