13.1 cannot select and run at max resolution on Sony VGN-C13G

English Hardware
21

Ok. Check that you have the package “kernel-firmware” installed. I’m not sure if the intel driver needs this, but it is definitely needed with certain radeon cards and the open source driver.
And please do try to run “sudo /sbin/mkinitrd”.

zbyszek@linux-44wk:~> /sbin/lspci -nnk | grep -A3 VGA00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03)
        Subsystem: Sony Corporation Device [104d:820f]
        Kernel modules: i915
00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03)
zbyszek@linux-44wk:~>

Ok, as Miuku already wrote, the i915 kernel module seems to be loaded and used.

zbyszek@linux-44wk:~> ls /etc/X11/xorg.xonf.d/
ls: cannot access /etc/X11/xorg.xonf.d/: No such file or directory
zbyszek@linux-44wk:~> sudo ls /etc/X11/xorg.xonf.d/
root's password:
ls: cannot access /etc/X11/xorg.xonf.d/: No such file or directory
zbyszek@linux-44wk:~>

Sorry, that was a typo.
It should have been this of course:

ls /etc/X11/xorg.conf.d/

I wonder if it’s possible to somehow force the installation to use the correct intel driver. If yes I’m willing to start the new installation of SUSE.

Yes, it is.
Edit the file /etc/X11/xorg.conf.d/50-device.conf to look like this: (or create a new file, /etc/X11/xorg.conf.d/50-mydevice.conf f.e., with this content)

Section "Device"
  Identifier "Default Device"
  Driver "intel"
EndSection

But beware: if the intel driver is not working, Xorg will fail to start and you will drop to text mode.
If that’s the case, please boot to “Recovery Mode” (“Advanced Options” in the boot menu) and post the file /var/log/Xorg.0.log.old .
Maybe this will tell in more detail then why the intel driver fails.

Another thing that could be worth a try is to disable plymouth (the boot splash) by adding “plymouth.enable=0” to the boot options.
Either do that in YaST->System->Boot Loader->Boot Loader Options, or press ‘e’ at the boot menu to edit the entry for one boot (search for the line starting with “linux” and append it there, then press ‘F10’ to boot).

22

I do have “kernel-firmware” installed

Here contents of sudo /sbin/mkinitrd

zbyszek@linux-44wk:~> sudo /sbin/mkinitrdroot's password:


Kernel image:   /boot/vmlinuz-3.11.10-17-desktop
Initrd image:   /boot/initrd-3.11.10-17-desktop
KMS drivers:     i915
Root device:    /dev/disk/by-id/ata-TOSHIBA_MK8032GSX_X6IJF5AHS-part5 (/dev/sda5) (mounted on / as ext4)
Resume device:  /dev/disk/by-id/ata-TOSHIBA_MK8032GSX_X6IJF5AHS-part3 (/dev/sda3)
Microcode: Adding Intel microcode 06-0f-06
Kernel Modules: thermal_sys thermal processor fan scsi_dh scsi_dh_emc scsi_dh_hp_sw scsi_dh_alua scsi_dh_rdac video button i2c-algo-bit drm drm_kms_helper i915 ata_piix xhci-hcd hid-logitech-dj hid-holtek-kbd hid-lenovo-tpkbd hid-ortek hid-roccat hid-roccat-common hid-roccat-arvo hid-roccat-isku hid-samsung ohci-pci 
Features:       acpi intel_microcode kms plymouth block usb resume.userspace resume.kernel


Kernel image:   /boot/vmlinuz-3.11.6-4-desktop
Initrd image:   /boot/initrd-3.11.6-4-desktop
KMS drivers:     i915
Root device:    /dev/disk/by-id/ata-TOSHIBA_MK8032GSX_X6IJF5AHS-part5 (/dev/sda5) (mounted on / as ext4)
Resume device:  /dev/disk/by-id/ata-TOSHIBA_MK8032GSX_X6IJF5AHS-part3 (/dev/sda3)
Microcode: Adding Intel microcode 06-0f-06
Kernel Modules: thermal_sys thermal processor fan scsi_dh scsi_dh_emc scsi_dh_hp_sw scsi_dh_alua scsi_dh_rdac video button i2c-algo-bit drm drm_kms_helper i915 ata_piix xhci-hcd hid-logitech-dj hid-holtek-kbd hid-lenovo-tpkbd hid-ortek hid-roccat hid-roccat-common hid-roccat-arvo hid-roccat-isku hid-samsung ohci-pci 
Features:       acpi intel_microcode kms plymouth block usb resume.userspace resume.kernel
zbyszek@linux-44wk:~> 


zbyszek@linux-44wk:~> ls /etc/X11/xorg.conf.d/05-glamor.conf  10-libvnc.conf  50-device.conf   50-screen.conf     50-vmmouse.conf  90-keytable.conf                                          
10-evdev.conf   11-evdev.conf   50-monitor.conf  50-synaptics.conf  50-wacom.conf                                                              
zbyszek@linux-44wk:~>

I edited /etc/X11/xorg.conf.d/50-device.conf to:
Section “Device”
Identifier “Default Device”
Driver “intel”
EndSection

rebooted and now Intel driver is not working, Xorg failed to start, I cannot access Grub menu. Upon pressing either left Shift key or “e” laptop stopps responding. I had to use the Live CD to boot.
Now I cannot neither boot SUSE from hard disk nor access Grub menu.
After I booted from Live CD I discovered that /var/log/Xorg.0.log.old does not exist. Do you need /var/log/Xorg.0.log?

I am loosing hope that would be possible to run SUSE on this laptop in a native resolution!

23

Ok, I don’t see any file that shouldn’t be there.

rebooted and now Intel driver is not working, Xorg failed to start, I cannot access Grub menu. Upon pressing either left Shift key or “e” laptop stopps responding. I had to use the Live CD to boot.

???
Shift doesn’t do anything, that’s normal.
And ‘e’ is for editing the boot entry.

Try to select “Advanced Options” with the cursor keys and select “Recovery Mode” there (should be the second entry).

Now I cannot neither boot SUSE from hard disk nor access Grub menu.

What do you mean with “access Grub menu”?
Isn’t it shown any more?
That shouldn’t have happened if you did what I suggested, as none of those things would mess with grub.

Did you maybe use KDE’s options to select a particular boot menu entry and are using an LVM or btrfs?
Then remove the file /boot/grub2/grubenv to get back the boot menu.

After I booted from Live CD I discovered that /var/log/Xorg.0.log.old does not exist. Do you need /var/log/Xorg.0.log?

In that case, yes.
That should be the log from the failed boot. If you would have booted to recovery mode afterwards, it would have been renamed to /var/log/Xorg.0.log.old .

PS: If you cannot get back the grub menu, you should be able to boot your system again by removing that changed /etc/X11/xorg.conf.d/50-device.conf or changing it back to the original state.

24

[QUOTE=wolfi323;2656245

That shouldn’t have happened if you did what I suggested, as none of those things would mess with grub.

Did you maybe use KDE’s options to select a particular boot menu entry and are using an LVM or btrfs?
Then remove the file /boot/grub2/grubenv to get back the boot menu.

In that case, yes.
That should be the log from the failed boot. If you would have booted to recovery mode afterwards, it would have been renamed to /var/log/Xorg.0.log.old .

PS: If you cannot get back the grub menu, you should be able to boot your system again by removing that changed /etc/X11/xorg.conf.d/50-device.conf or changing it back to the original state.[/QUOTE]

Hello wolfi323
From day one after I installed SUSE I NEVER EVER saw grub menu. Just “Grub loading. Welcome to grub”, black screen for about 30sec and than login screen.
Now I cannot select anything because SUSE is not booting. I REALLY followed up all your suggestions.

“Did you maybe use KDE’s options to select a particular boot menu entry and are using an LVM or btrfs?”
During the installation I did not select LVM or btrfs. Just ext4.

Then removed the file /boot/grub2/grubenv to get back the boot menu.
I deleted grubenv, restarted PC, was shown again “Grub loading. Welcome to grub” and black screen. After a few minutes I decided to press the power button

Please find contents of Xorg.0.log here:

By puszkin, 1 Second ago, written in Text. This post will expire in 1 Week


URL: http://susepaste.org/81885950

and contents of Xorg.0.log.old here:

By puszkin, 1 Second ago, written in Text. This post will expire in 1 Week


URL: http://susepaste.org/93262227

PS: If you cannot get back the grub menu, you should be able to boot your system again by removing that changed /etc/X11/xorg.conf.d/50-device.conf or changing it back to the original state.

I restored /etc/X11/xorg.conf.d/50-device.conf to the previous state, rebooted PC and again I am shown “Grub loading. Welcome to grub”, no grub menu, than I can log in. Shortly speaking I’m back where I was when started my first post.

Let me indicate one particular error:
ERROR drm/i915 can’t work without intel_agp module!
which occurs many times in /var/log/warn
I tried to upload the contents for your perusal but after I clicked “Create” I was shown 404 Page Not Found. Maybe there’s a limit of uploads?

25

Could you post the result of lsmod as root here between code blocks - it’s a bunch of text.

26

Well, but you didn’t tell that.
I would have never suggested to deliberately break X and then select “Recovery Mode” in the boot menu if I would have known that. I would rather have tried to fix the boot menu first.

And you could have suspected yourself that selecting “Recovery Mode” in the boot menu would prove to be difficult if there is no boot menu…:wink:

Now I cannot select anything because SUSE is not booting. I REALLY followed up all your suggestions.

And what suggestions exactly?
Did you remove /etc/X11/xorg.conf.d/50-device.conf? Then your system should boot again.

“Did you maybe use KDE’s options to select a particular boot menu entry and are using an LVM or btrfs?”
During the installation I did not select LVM or btrfs. Just ext4.

Ok, then this should not be the problem.

Then removed the file /boot/grub2/grubenv to get back the boot menu.
I deleted grubenv, restarted PC, was shown again “Grub loading. Welcome to grub” and black screen. After a few minutes I decided to press the power button

So you did have a grubenv?
But removing that should not break your boot.
It just contains certain settings for Grub2, like the default boot entry f.e., and therefore can prevent the menu to be shown.

Please find contents of Xorg.0.log here:

By puszkin, 1 Second ago, written in Text. This post will expire in 1 Week

URL: SUSE Paste

and contents of Xorg.0.log.old here:

By puszkin, 1 Second ago, written in Text. This post will expire in 1 Week

URL: SUSE Paste

Ok, I will have a look at it.

PS: If you cannot get back the grub menu, you should be able to boot your system again by removing that changed /etc/X11/xorg.conf.d/50-device.conf or changing it back to the original state.

I restored /etc/X11/xorg.conf.d/50-device.conf to the previous state, rebooted PC and again I am shown “Grub loading. Welcome to grub”, no grub menu, than I can log in. Shortly speaking I’m back where I was when started my first post.

Ok, so at least your system is booting again. And we hopefully have some useful error messages now.

I would suggest you try to select a particular resolution in YaST->System->Boot Loader->Boot Loader Options (“Console Resolution”, set it to something different than “Autodetect by Grub2”). Maybe the boot menu will appear then?

Let me indicate one particular error:
ERROR drm/i915 can’t work without intel_agp module!
which occurs many times in /var/log/warn

This sounds crucial, yes.
I will have a look at your Xorg.0.log and think about this…

Could you please also post the output of:

dmesg|egrep "intel|i915"

Maybe that would contain something interesting?

27

I would suggest you try to select a particular resolution in YaST->System->Boot Loader->Boot Loader Options (“Console Resolution”, set it to something different than “Autodetect by Grub2”). Maybe the boot menu will appear then?

I tried: 800x600, 1024x600, 1024x768, 1280x800 and left at Autodetect by grub2. No difference, grub menu is not shown.

Let me give you all values I have in YaST->System->Boot Loader

Type: GRUB2 Boot loader location: Boot from extended partition - ticked
 
 Under boot loader options:
 Distributor: openSUSE 13.1: blank
 Probe Foreign OS:ticked
 Set active Flag in Partition Table for Boot Partition: ticked
 Write generic Boot Code to MBR: ticked
 Timeout in Seconds: 8
 Vga Mode: Unspecified
 Optional Kernel Command Line Parameter:  resume=/dev/disk/by-id/ata-TOSHIBA_MK8032GSX_X6IJF5AHS-part3 splash=silent quiet showopts
 Failsafe Kernel Command Line Parameter: showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe
 Default Boot Section: openSUSE 13.1
 Use graphical console: ticked
 Console resolution: Autodetect by grub2
 console theme: /boot/grub2/themes/openSUSE/theme.txt
 Use serial console: blank

 zbyszek@linux-44wk:~> dmesg|egrep "intel|i915"    0.026000] perf_event_intel: PEBS disabled due to CPU errata
    0.781295] intel_idle: does not run on family 6 model 15
    0.783735] agpgart-intel 0000:00:00.0: Intel 945GM Chipset
    0.783819] agpgart-intel 0000:00:00.0: detected gtt size: 0K total, 0K mappable
    0.783829] agpgart-intel 0000:00:00.0: Intel (null) Chipset
    0.783837] agpgart-intel 0000:00:00.0: can't determine aperture size
    0.783842] agpgart-intel 0000:00:00.0: agp_backend_initialize() failed
    0.783846] agpgart-intel: probe of 0000:00:00.0 failed with error -22
    1.896331] [drm:i915_pci_probe] *ERROR* drm/i915 can't work without intel_agp module!
   14.273420] intel_rng: FWH not detected
   15.867002] snd_hda_intel 0000:00:1b.0: irq 46 for MSI/MSI-X
zbyszek@linux-44wk:~>
28

This is starting to smell a lot like a kernel driver problem/bug.

29

Yes.
Or maybe even lower level, as also grub2 has problems to show the menu.

You could switch to grub1 in YaST->System->Boot Loader, will that show you a boot menu?

Two more ideas:

  • Look if there’s a BIOS update for your computer, and try to play with the graphics-related settings in the BIOS (graphics aperture size f.e.).

  • Your problem sounds a bit like this:
    Gentoo Forums :: View topic - intel i915
    The last reply there states:

I know it is an old thread but I had recently same problems (from kernel 3.7). The solution was to disable iommu in kernel since dma access on the GPU(i915) had some problems. Hope it helps someone.

So try this, by adding “iommu=off” to the kernel boot options.

30

You could switch to grub1 in YaST->System->Boot Loader, will that show you a boot menu?

Grub1 > accepted “proposed configuration”
Booted with the following menu:

 open SUSE 13.1
 Failsafe -- openSUSE 13.1
 Kernel-3.11.10-17-desktop
 Kernel-3.11.6-4-desktop

accepted the first option and I’ve got the same resolution problem.

Look if there’s a BIOS update for your computer, and try to play with the graphics-related settings in the BIOS (graphics aperture size f.e.).

I only found at Support for VGN-C13G | Sony AP 
BIOS Upgrade Program Version R0035J4 for Windows Vista 26 Jun 2007 R0035J4 (Vista Home Basic 32bit). Frankly speaking I’m very reluctant to try installing BIOS update without any tool to restore the previous one. I lost one PC in similiar circumstances.
On top of this, hey guys Sony Vaio VGN-C13G is a REALLY VERY OLD laptop and there is no possibility to “play with the graphics-related settings”.

So try this, by adding “iommu=off” to the kernel boot options.

I introduced suggested changes via YaST->System->Boot Loader. Let me give all latest value from a window titled Kernel Section

Section Name: Failsafe -- openSUSE 13.1
 Section Settings:
  Do not verify Filesystem before Booting - unticked
  Enable SELinux - dimmed
  Kernel Image: /boot/vmlinuz
  Initial RAM Disk: /boot/initrd
  Root Device: /dev/disk/by-id/ata-TOSHIBA_MK8032GSX_X6IJF5AHS-part5
  VGA mode: Unspecified
  Optional Kernel Command Line Parameter: showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe iommu=off

After booting by selecting Failsafe – openSUSE 13.1from Grub1 menu I’ve got the same low resolution.

One more test. After changing in YaST->System->Boot Loader VGA mode from unspecified to 1280x800, 8bits (mode 0x363) and booting using Failsafe – openSUSE 13.1 I still have low resolution.

31

Of course.
Another boot loader was not expected to fix your resolution problem.

It was meant to get you a working boot menu.

I only found at http://www.sony-asia.com/support/product/VGN-C13G
BIOS Upgrade Program Version R0035J4 for Windows Vista 26 Jun 2007 R0035J4 (Vista Home Basic 32bit). Frankly speaking I’m very reluctant to try installing BIOS update without any tool to restore the previous one. I lost one PC in similiar circumstances.

Well, this was only a suggestion that might solve the problem.
It’s up to you of course…

On top of this, hey guys Sony Vaio VGN-C13G is a REALLY VERY OLD laptop and there is no possibility to “play with the graphics-related settings”.

Even REALLY VERY OLD laptops might have extensive BIOS settings…
I don’t know your particular model though.

I introduced suggested changes via YaST->System->Boot Loader. Let me give all latest value from a window titled Kernel Section

Section Name: Failsafe -- openSUSE 13.1
 Section Settings:
  Do not verify Filesystem before Booting - unticked
  Enable SELinux - dimmed
  Kernel Image: /boot/vmlinuz
  Initial RAM Disk: /boot/initrd
  Root Device: /dev/disk/by-id/ata-TOSHIBA_MK8032GSX_X6IJF5AHS-part5
  VGA mode: Unspecified
  Optional Kernel Command Line Parameter: showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe iommu=off

After booting by selecting Failsafe – openSUSE 13.1from Grub1 menu I’ve got the same low resolution.

Of course.
The failsafe modus does not use the intel driver.

One more test. After changing in YaST->System->Boot Loader VGA mode from unspecified to 1280x800, 8bits (mode 0x363) and booting using Failsafe – openSUSE 13.1 I still have low resolution.

See above. The failsafe mode is useless for this, as it will by definition boot into a lower resolution and not use the intel driver.

Please, try to add “iommu=off” to the standard boot entry (i.e. not “failsafe”, the one without “x11failsafe”) and boot that one.
Then please post the Xorg.0.log and the output of "dmesg | egrep “intel|i915” again.

32

Even REALLY VERY OLD laptops might have extensive BIOS settings…
I don’t know your particular model though.

I know only about one option to access ROM BIOS I press F2 and get Phoenix BIOS Setup Utility where I can find the following options:

Main:
BIOS ver
Machine Name
S/N
UUID
System Memory
Hard Disk Drive
System Date
System Time

Advanced:
External drive boot
Network boot
VAIO animation logo
Speaker volume

Security:
Machine Password
User Password
Set machine password
Set user password

Boot:
Boot priority order:
USB flash
Internal optical drive
Internal hard disk drive
Network
Floppy Disk Drive

Exit:
Exit Setup
Get default values
Discard changes
Save changes
Shutdown

That’s it unless there’s another hidden method to find more options. I’m always opened to learn more.

Please, try to add “iommu=off” to the standard boot entry (i.e. not “failsafe”, the one without “x11failsafe”) and boot that one.

At the grub menu, I hit Esc to enter text based menu, selected first menu entry,added “iommu=off”, pressed b to boot

Then please post the Xorg.0.log

By puszkin, 2 Seconds ago, written in Text. This post will expire in 6 Days


URL: http://susepaste.org/10683053

and the output of "dmesg | egrep “intel|i915” again

zbyszek@linux-44wk:~> dmesg | egrep "intel|i915"
    0.027000] perf_event_intel: PEBS disabled due to CPU errata
    0.786623] intel_idle: does not run on family 6 model 15
    0.789083] agpgart-intel 0000:00:00.0: Intel 945GM Chipset
    0.789167] agpgart-intel 0000:00:00.0: detected gtt size: 0K total, 0K mappable
    0.789178] agpgart-intel 0000:00:00.0: Intel (null) Chipset
    0.789185] agpgart-intel 0000:00:00.0: can't determine aperture size
    0.789232] agpgart-intel 0000:00:00.0: agp_backend_initialize() failed
    0.789237] agpgart-intel: probe of 0000:00:00.0 failed with error -22
    1.908341] [drm:i915_pci_probe] *ERROR* drm/i915 can't work without intel_agp module!
   13.666316] intel_rng: FWH not detected
   15.528280] snd_hda_intel 0000:00:1b.0: irq 45 for MSI/MSI-X
zbyszek@linux-44wk:~>
33

Ok, so there really does not seem to be any settings that could help.

That’s it unless there’s another hidden method to find more options. I’m always opened to learn more.

As I said, I don’t know your particular model.
On one of my older systems (a desktop though), you can press Alt+F1 to make some hidden advanced options appear.

At the grub menu, I hit Esc to enter text based menu, selected first menu entry,added “iommu=off”, pressed b to boot

Ok, that was correct.

But unfortunately it didn’t seem to help at all in your case.

Sorry, I have no further idea then. There’s either something wrong with the kernel (intel_agp in particular), or the hardware/BIOS, I’d say.

You could try a newer kernel, just install one from http://download.opensuse.org/repositories/Kernel:/stable/standard/ .
And you maybe should file a bug report. The kernel developers might have more ideas how to debug this and might even fix it.

Other than that, you probably have to stick to the vesa driver (for now at least).
You could try to add another resolution to the X configuration as already indicated, it might even work with vesa (I’m not sure).
See here: SDB:Configuring graphics cards and monitor settings - openSUSE Wiki

In short, calculate a modeline with “cvt” and add it to /etc/xorg.conf.d/50-monitor.conf (after uncommenting the other lines, the article does describe it in detail).
IIRC, you also need a screen section though to “activate” the monitor.conf. So if changing that alone doesn’t work, edit 50-screen.conf as well and just uncomment all lines there. The “Monitor” line there should of course depict the Identifier in 50-monitor.conf.

34

If everything else fails and you’re about to ditch everything and go for something else, you could always try to install a new kernel to see if it has been fixed.

This being after everything else has been tested, of course.

Edit:
Woops, Wolfi suggested the same :slight_smile:

35

I just had a look at the mainboard manual (I’m not near that system), and it’s rather Ctrl+F1, sorry.
But this probably won’t apply to your laptop anyway, I suppose…

36

Hello,
I would like sincerely thank you guys for sharing with me your huge experience. I must admit that I learned a lot during the last few days.
I’ll stick to vesa now.
Let me ask you the last few questions:

You could try a newer kernel, just install one from http://download.opensuse.org/reposit…able/standard/ .
And you maybe should file a bug report. The kernel developers might have more ideas how to debug this and might even fix it.

How to prepare a bug report? I’ve never done it before? Where can I find details how to do it? How to contact kernel developers?

Sorry, I have no further idea then. There’s either something wrong with the kernel (intel_agp in particular), or the hardware/BIOS, I’d say.

I wonder if there are any tools to test hardware/BIOS just to eliminate these possibilities?

As I indicated in my opening post Knoppix and Puppy Linux can detect the native resolution without any problem. How is possible? Maybe I could get/copy something from these distributions?

Thank you again for your great help.

37

I would still advocate, like Wolfi, that you try one of the kernels in his post - upgrade and see if it fixes the problem.

This would help if you want to file a bug report too as you could indicate which kernels are problematic.

38

http://en.opensuse.org/openSUSE:Submitting_bug_reports
You can login to bugzilla with the same username/password as here.

But as Miuku wrote already, you should better try with the latest kernel before you report a bug. The problem might be fixed already.
Just install the correct “kernel-desktop” package (x86_64) from the link above. More than one kernel can be installed at the same time, so you won’t lose the current one. If the new one wouldn’t boot, just select again the old one in the boot menu.

A note (as this has confused people in the past): YaST only shows one kernel-desktop installed/available although there are more.
Select the package and click on “Versions” below the package list to see all available/installed versions and be able to install/uninistall specific ones.

How to contact kernel developers?

By filing a bug against the kernel. :wink:
You could report this directly upstream at kernel.org, but I would say start at openSUSE’s bugzilla, you will reach (some) kernel developers there as well.
If they think it’s better to directly report it upstream, they will tell you.

I wonder if there are any tools to test hardware/BIOS just to eliminate these possibilities?

I’m not aware of any.
But if it works on different distributions/versions, it’s more likely an incompatibility/regression in 13.1’s kernel or something like that.

As I indicated in my opening post Knoppix and Puppy Linux can detect the native resolution without any problem. How is possible? Maybe I could get/copy something from these distributions?

Well, you could have a look what kernel version those are using, for a start. (uname -a)

Thank you again for your great help.

You’re welcome.
But I would be more glad if we could have fixed your problem already… :wink:

39

I’ve installed the latest kernel but it doesn’t make any difference. Now I concentrate on preparing bug report.

40

After installing the latest kernel I can see during the boot:

agpgart-intel 0000:00:00.0: can't determine aperture sizeagpgart-intel: probe of 0000:00:00.0 failed with error -22
[drm:i915_gmch_probe] *ERROR* failed to set up gmch
i915: probe of 0000:00:02.0 failed with error -5

What does it mean? Is it the issue for kernel specialists?