Just tried putting 11.4 on a Lenovo L412, and I’m getting random freeze-ups that can only be cleared by killing power. Booting to the Windows 7 partition shows no problems.
I have several suspects:
The Linux/Windows partitioning done during the Linux install
The compilation and installation of the driver required to support the Realtek wireless chipset
The new openSuSE kernel itself
Before I start ripping the guts out of this thing, I thought I’d see if anyone has seen something similar. Any clues?
Indeed there has been on our 11.3 and other linux distros, but we were hoping that with 11.4’s upgrades to kernel 2.6.37, and to xorg-xserver, Mesa, DRI/DRM, and the “intel” driver (i915), the problems would be over. Given this is the second thread today involving Arrandale, that may not be the case.
If you want to look at past openSUSE threads, I suggest you do a forum search on terms: arrandale ironlake gma. User SeanMc98 did a lot of work on this type of Intel graphics hardware and made considerable progress with kernel 2.6.37 and onto 2.6.38 with some regressions on the way. Some other users had varying success depending on processor configuration (cores) and laptop make. Can you confirm the processor model in your machine, and just to get a bit more detail please do the following.
I suggest you post the first few lines (in CODE tags) to cover processor and graphics chipsets from running the following command (as root: su -) in a terminal:
lspci -nnk
I don’t wish to pre-judge the reason for your problems, but this should at least be on your suspect list.
It certainly looks like you both have the same processor, chipset, graphics GMA and a similar problem with 11.4 that may require a bug report.
Have you (and same question to @nrickert) tried booting and running with the nomodeset boot option (also used in failsafe boot)? If it works, this will avoid Kernel Mode Setting (KMS) and default to the more basic “fbdev” graphics driver. It may not perform as well, but you could avoid the freezes. If you haven’t already, I suggest you try this before doing any bug reporting. Please post back here with any results.
Sure. But that’s like saying that the system shouldn’t be freezing. I’m just doing what seems to make the system usable (other than booting to Windows).
Currently booting with “nomodeset xforcevesa acpi_osi=Linux.” I left the machine running on AC power overnight, came back this morning and the laptop was off for some reason. I’ve restarted it with the same settings, and have it on the desktop running Gnome System Monitor.
As it was, it ran for several hours on AC with the above settings; if it keeps going for several more I’ll try trimming-back to just “nomodeset acpi_osi=Linux.”
How hot? You could try acpi -V at the command line as normal user. On 11.3 the short report included temperature, but not on my 11.4 although the other inf about battery battery and Ac power is quite useful. To get temperature, you can install the “sensors” package and run it at command line. With my ThinkPad the fan kicks in above 40degC and the safety margins are much, much higher than that.
It was uncomfortable-to-the-touch hot, and the CPU area was markedly higher than that.
acpi -V is currently showing 52.0C. After installing the coretemp module via sensors-detect, I get the following from sensors:
Well, I’ve been watching it for hours now, and Fan never leaves zero RPM. I don’t hear it running, either. Temp1 is currently at 57C, though, so the laptop doesn’t seem to be in any hurry to melt-down.
