Intel Graphics Not Recognized in 12.1

I just installed 12.1 last week. It’s not recognizing the Intel onboard graphics card 3400 Series 5 Chipset. This apparently handles the sound too so I am not getting any sound. I get a message that I can’t run Gnome 3. I checked on the Intel website and their download for this chipset does NOT include Linux. Does anyone know a way I can get this working? Thanks in advance.

Actually I am getting sound. When I looked in the hardware information it did display that it’s recognizing the Intel 3400 5 Series Chipset. However, it isn’t for the graphics.

Perhaps this has something to do with having to set acpi=off during the installation from ISO image. I read something somewhere that it will automatically set to resolution 1024 VESA?

In Hardware information I see this for graphics driver: Arrandale Integrated Graphics Controller, for Frame Buffer, the highest resolution listed is 1024 by 768 (should be much higher), for Frame Buffer Device: Intel Ironlake Mobile Graphics Controller, class VESA framebuffer

This is what I see in /var/log/messages

vesafb: mode is 1024x768x16, linelength=2048, pages=20
Apr 7 15:25:41 0.464770] vesafb: scrolling: redraw
Apr 7 15:25:41 0.464772] vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
Apr 7 15:25:41 0.465270] vesafb: framebuffer at 0xa0000000, mapped to 0xffffc90001080000, using 3072k, total 32704k
Apr 7 15:25:41 0.465396] bootsplash 3.2.0-2010/03/31: looking for picture…
Apr 7 15:25:41 0.465398] bootsplash: silentjpeg size 89863 bytes
Apr 7 15:25:41 0.472375] bootsplash: …found (1024x768, 36220 bytes, v3).
Apr 7 15:25:41 0.551118] Console: switching to colour frame buffer device 124x44
Apr 7 15:25:41 0.629489] fb0: VESA VGA frame buffer device

In my boot config I see this: 1024x768, 16 bits (mode 0x317), but I it doesn’t display any higher resolution for an option.

On 2012-04-07 17:46, imterpsfan2 wrote:
> I checked on the Intel website and their download for this
> chipset does NOT include Linux

Drivers are already inside.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

You might want to look at /var/log/Xorg.0.log for any errors.

There is also a system file ‘/etc/X11/xorg.conf.d/50-device.conf’ which you could edit to explicitly load the intel driver. That might work for you.

Sorry I didn’t reply for a long time. I got involved in other issues.

When I go into Hardware Information, I see Arrandale Integrated Graphics Controller. In the Drivers section it says: Active:NO.

In the Xorg log this is what I have:


24.114] (II) Loading extension DRI2
    24.114] (==) Matched intel as autoconfigured driver 0
    24.121] (==) Matched fbdev as autoconfigured driver 1
    24.121] (==) Matched vesa as autoconfigured driver 2
    24.121] (==) Assigned the driver to the xf86ConfigLayout
    24.121] (II) LoadModule: "intel"
    24.126] (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so
    24.131] (II) Module intel: vendor="X.Org Foundation"
    24.131] 	compiled for 1.10.4, module version = 2.16.0
    24.131] 	Module class: X.Org Video Driver
    24.131] 	ABI class: X.Org Video Driver, version 10.0
    24.131] (II) LoadModule: "fbdev"
    24.137] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so
    24.141] (II) Module fbdev: vendor="X.Org Foundation"
    24.141] 	compiled for 1.10.4, module version = 0.4.2
    24.141] 	ABI class: X.Org Video Driver, version 10.0
    24.141] (II) LoadModule: "vesa"
    24.146] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
    24.147] (II) Module vesa: vendor="X.Org Foundation"
    24.147] 	compiled for 1.10.4, module version = 2.3.0
    24.147] 	Module class: X.Org Video Driver
    24.147] 	ABI class: X.Org Video Driver, version 10.0
    24.147] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
	i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
	E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
	965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
	4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
	Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
	Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
	Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
	Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
	Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server
    24.147] (II) FBDEV: driver for framebuffer: fbdev
    24.147] (II) VESA: driver for VESA chipsets: vesa
    24.147] (++) using VT number 7

    24.288] (II) Loading sub module "fbdevhw"
    24.288] (II) LoadModule: "fbdevhw"
    24.289] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
    24.289] (II) Module fbdevhw: vendor="X.Org Foundation"
    24.289] 	compiled for 1.10.4, module version = 0.0.2
    24.289] 	ABI class: X.Org Video Driver, version 10.0
    24.289] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so
    24.289] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
    24.289] (**) FBDEV(0): claimed PCI slot 0@0:2:0
    24.289] (II) FBDEV(0): using default device
    24.289] (WW) Falling back to old probe method for vesa
    24.289] (II) FBDEV(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 16/16
    24.289] (==) FBDEV(0): Depth 16, (==) framebuffer bpp 16
    24.289] (==) FBDEV(0): RGB weight 565
    24.289] (==) FBDEV(0): Default visual is TrueColor
    24.289] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
    24.289] (II) FBDEV(0): hardware: VESA VGA (video memory: 3072kB)
    24.289] (II) FBDEV(0): checking modes against framebuffer device...
    24.289] (II) FBDEV(0): checking modes against monitor...
    24.289] (--) FBDEV(0): Virtual size is 1024x768 (pitch 1024)
    24.289] (**) FBDEV(0):  Built-in mode "current": 78.7 MHz, 59.9 kHz, 75.7 Hz
    24.289] (II) FBDEV(0): Modeline "current"x0.0   78.65  1024 1056 1184 1312  768 772 776 792 -hsync -vsync -csync (59.9 kHz)
    24.289] (==) FBDEV(0): DPI set to (96, 96)
    24.289] (II) Loading sub module "fb"
    24.289] (II) LoadModule: "fb"
    24.294] (II) Loading /usr/lib64/xorg/modules/libfb.so
    24.295] (II) Module fb: vendor="X.Org Foundation"
    24.295] 	compiled for 1.10.4, module version = 1.0.0
    24.295] 	ABI class: X.Org ANSI C Emulation, version 0.4
    24.295] (**) FBDEV(0): using shadow framebuffer



/usr/sbin/hwinfo --gfxcard
08: PCI 02.0: 0300 VGA compatible controller (VGA)              
  [Created at pci.319]
  Unique ID: _Znp.Q_QP6imJFa9
  SysFS ID: /devices/pci0000:00/0000:00:02.0
  SysFS BusID: 0000:00:02.0
  Hardware Class: graphics card
  Model: "Intel Arrandale Integrated Graphics Controller"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x0046 "Arrandale Integrated Graphics Controller"
  SubVendor: pci 0x103c "Hewlett-Packard Company"
  SubDevice: pci 0x1693 
  Revision: 0x02
  Memory Range: 0xb0000000-0xb03fffff (rw,non-prefetchable)
  Memory Range: 0xa0000000-0xafffffff (ro,non-prefetchable)
  I/O Ports: 0x4050-0x4057 (rw)
  IRQ: 9 (121 events)
  I/O Ports: 0x3c0-0x3df (rw)
  Module Alias: "pci:v00008086d00000046sv0000103Csd00001693bc03sc00i00"
  Driver Info #0:
    Driver Status: i915 is not active
    Driver Activation Cmd: "modprobe i915"
  Config Status: cfg=no, avail=yes, need=no, active=unknown

Primary display adapter: #8

Do I want to make this i915 driver active and, if so, how would I do it?

The intel driver is loading, as are other drivers, but for some reason the FBDEV is being chosen over the Intel driver.

Did you try this suggestion:

Do you need guidance on how to try that ? Before trying that I recommend you install the text editor ‘midnight commander’ (called ‘mc’) as it is an easy edit to use/run in a full screen mode in case one gets ‘caught’ in a text mode and needs to edit a text file.

I see this commented out in the file.


Section "Device"
  Identifier "Default Device"

  Driver "i915"

EndSection

I assume I do something like this?

I am not clear one can load the i915 that way. Try this instead:


Section "Device"
  Identifier "Default Device"

  Driver "intel"

EndSection

Something else to try, is to do a nominal boot, and when the initial grub boot/splash menu appears, is press the ‘arrow’ and ‘backspace’ keys and comment out the entry ‘vga=0x317’ (or something similar) as some users have reported that vga specification at boot start causes them problems with Intel graphics.

Also, I note for the 8086:4046 Arrandale graphics, its not uncommon for that graphics to be on a PC that has hybrid graphics. To put my mind at rest on this (ie confirm NOT hybrid graphics), can you please provide the output of the command (sent from a terminal) :


/sbin/lspci -nnk | grep vga -iA2



 /sbin/lspci -nnk | grep vga -iA2
00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02)
	Subsystem: Hewlett-Packard Company Device [103c:1693]
00:16.0 Communication controller [0780]: Intel Corporation 5 Series/3400 Series Chipset HECI Controller [8086:3b64] (rev 06)

I tried editing the 50-device.conf file, putting “intel” as the driver. However, then I couldn’t even get a display. It sent me to the command prompt after I logged in. I tried to issue an “init 5” and the screen would shake around a bit but not give me a desktop. I noticed that when I pulled up “mc” that the resolution had improved, it was a much higher resolution. So then I commented out all of the lines in the file. Now I am back to where I started with a low resolution and it’s not picking up the driver. Does spacing matter in the conf file? e.g. do I need to indent at a certain number of spaces, etc.

I also tried to issue a “modprobe i915” command. I got a lot of error messages at that point and it was unsuccessful. Error inserting i915 /lib/modules/3.1.9-1.4-desktop/kernel/drivers/gpu/drm/i915/i915.ko no such device.

What should I do next?

Did you try my suggestion to boot without the ‘vga=0x317’ (or what ever its coded as) in the grub boot menu ?

Out of curiousity, what are the settings in your /boot/grub/menu.lst file ? Do you have anything there locking you in to the fbdev driver?

When I deleted vga=0x317 it had no effect.

menu.list


default 0
timeout 8
gfxmenu (hd0,5)/boot/message
##YaST - activate

###Don't change this comment - YaST2 identifier: Original name: linux###
title Desktop -- openSUSE 12.1 - 3.1.9-1.4
    root (hd0,5)
    kernel /boot/vmlinuz-3.1.9-1.4-desktop root=/dev/disk/by-id/ata-ST9500325AS_6VETPDD0-part6 acpi=off resume=/dev/disk/by-id/ata-ST9500325AS_6VETPDD0-part5 splash=silent quiet showopts vga=0x317
    initrd /boot/initrd-3.1.9-1.4-desktop

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 12.1 - 3.1.9-1.4
    root (hd0,5)
    kernel /boot/vmlinuz-3.1.9-1.4-desktop root=/dev/disk/by-id/ata-ST9500325AS_6VETPDD0-part6 showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe vga=0x317
    initrd /boot/initrd-3.1.9-1.4-desktop

###Don't change this comment - YaST2 identifier: Original name: windows 1###
title windows 1
    rootnoverify (hd0,0)
    chainloader +1

###Don't change this comment - YaST2 identifier: Original name: windows 2###
title windows 2
    rootnoverify (hd0,1)
    chainloader +1

Something else I noticed is that in my Hardware Information it has an Intel VESA Framebuffer loaded and the highest resolution it shows is 1024 by 768. I feel I am at my wit’s end on this.