BT5r3 on Alienware m14x R2 - Problems with Intel HD4000 (Brightness + Resolution)

[santhrax]

Hello to everyone!

I am completely new to Backtrack and I installed it on my Alienware m14x R2. Everything is working exept the brightness and the resolution.
A friend of mine figured out that my intel drivers are NOT loaded. Instead my system uses the VESA driver.


Actually I don't have any clue how to tell Backtrack to load the correct driver for my Intel HD Card.

NVIDIA is running without problems - optirun and pyrit are working using this [Guide] Installing Backtrack 5r3 on Acer Aspire 5742zg (Nvidia Optimus)

Notebook:
- Alienware M14x R2
- Backtrack 5r3 Gnome 64bit
- Intel HD 4000
- NVIDIA GT 650m (Optimus-Style Switching)

root@bt:~# cat /var/log/Xorg.0.log | grep -i vesa
(==) Matched vesa as autoconfigured driver 1
(II) LoadModule: "vesa"
(II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
(II) Module vesa: vendor="X.Org Foundation"
(II) VESA: driver for VESA chipsets: vesa
(II) VESA(0): initializing int10
(II) VESA(0): Primary V_BIOS segment is: 0xc000
(II) VESA(0): VESA BIOS detected
(II) VESA(0): VESA VBE Version 3.0
(II) VESA(0): VESA VBE Total Mem: 65472 kB
(II) VESA(0): VESA VBE OEM: Intel(R) Sandybridge/Ivybridge Graphics Chipset Accelerated VGA BIOS
(II) VESA(0): VESA VBE OEM Software Rev: 1.0
(II) VESA(0): VESA VBE OEM Vendor: Intel Corporation
(II) VESA(0): VESA VBE OEM Product: Intel(R) Sandybridge/Ivybridge Graphics Controller
(II) VESA(0): VESA VBE OEM Product Rev: Hardware Version 0.0
(II) VESA(0): Creating default Display subsection in Screen section
(==) VESA(0): Depth 24, (--) framebuffer bpp 32
(==) VESA(0): RGB weight 888
(==) VESA(0): Default visual is TrueColor
(==) VESA(0): Using gamma correction (1.0, 1.0, 1.0)
(II) VESA(0): VESA VBE DDC supported
(II) VESA(0): VESA VBE DDC Level 2
(II) VESA(0): VESA VBE DDC transfer in appr. 1 sec.
(II) VESA(0): VESA VBE DDC read successfully
(II) VESA(0): Manufacturer: LGD  Model: 366  Serial#: 0
(II) VESA(0): Year: 2011  Week: 0
(II) VESA(0): EDID Version: 1.4
(II) VESA(0): Digital Display Input
(II) VESA(0): 6 bits per channel
(II) VESA(0): Digital interface is undefined
(II) VESA(0): Max Image Size [cm]: horiz.: 31  vert.: 17
(II) VESA(0): Gamma: 2.20
(II) VESA(0): No DPMS capabilities specified
(II) VESA(0): Supported color encodings: RGB 4:4:4 
(II) VESA(0): First detailed timing is preferred mode
(II) VESA(0): Preferred mode is native pixel format and refresh rate
(II) VESA(0): redX: 0.585 redY: 0.347   greenX: 0.335 greenY: 0.570
(II) VESA(0): blueX: 0.157 blueY: 0.125   whiteX: 0.313 whiteY: 0.329
(II) VESA(0): Manufacturer's mask: 0
(II) VESA(0): Supported detailed timing:
(II) VESA(0): clock: 121.2 MHz   Image Size:  309 x 174 mm
(II) VESA(0): h_active: 1600  h_sync: 1760  h_sync_end 1856 h_blank_end 2104 h_border: 0
(II) VESA(0): v_active: 900  v_sync: 903  v_sync_end 908 v_blanking: 960 v_border: 0
(II) VESA(0): Supported detailed timing:
(II) VESA(0): clock: 80.8 MHz   Image Size:  309 x 174 mm
(II) VESA(0): h_active: 1600  h_sync: 1760  h_sync_end 1856 h_blank_end 2104 h_border: 0
(II) VESA(0): v_active: 900  v_sync: 903  v_sync_end 908 v_blanking: 960 v_border: 0
(II) VESA(0):  3NPR6�140WD2
(II) VESA(0): Unknown vendor-specific block 0
(II) VESA(0): EDID (in hex):
(II) VESA(0): 	00ffffffffffff0030e4660300000000
(II) VESA(0): 	00150104901f117802fc459558559228
(II) VESA(0): 	20505400000001010101010101010101
(II) VESA(0): 	010101010101582f40f861843c30a060
(II) VESA(0): 	350035ae1000001a901f40f861843c30
(II) VESA(0): 	a060350035ae1000001a000000fe0033
(II) VESA(0): 	4e505236803134305744320a00000000
(II) VESA(0): 	000041319e0110000002010a202000a7
(II) VESA(0): EDID vendor "LGD", prod id 870
(II) VESA(0): Printing DDC gathered Modelines:
(II) VESA(0): Modeline "1600x900"x0.0  121.20  1600 1760 1856 2104  900 903 908 960 +hsync -vsync (57.6 kHz)
(II) VESA(0): Modeline "1600x900"x0.0   80.80  1600 1760 1856 2104  900 903 908 960 +hsync -vsync (38.4 kHz)
(II) VESA(0): Searching for matching VESA mode(s):
(II) VESA(0): Total Memory: 1023 64KB banks (65472kB)
(II) VESA(0): <default monitor>: Using hsync range of 38.40-57.60 kHz
(II) VESA(0): <default monitor>: Using vrefresh range of 40.00-60.00 Hz
(WW) VESA(0): Unable to estimate virtual size
(II) VESA(0): Not using built-in mode "1024x768" (no mode of this name)
(II) VESA(0): Not using built-in mode "800x600" (no mode of this name)
(II) VESA(0): Not using built-in mode "640x480" (no mode of this name)
(--) VESA(0): Virtual size is 1600x900 (pitch 1600)
(**) VESA(0): *Built-in mode "1600x900"
(**) VESA(0): Display dimensions: (310, 170) mm
(**) VESA(0): DPI set to (131, 134)
(**) VESA(0): Using "Shadow Framebuffer"
(II) VESA(0): initializing int10
(II) VESA(0): Primary V_BIOS segment is: 0xc000
(II) VESA(0): VESA BIOS detected
(II) VESA(0): VESA VBE Version 3.0
(II) VESA(0): VESA VBE Total Mem: 65472 kB
(II) VESA(0): VESA VBE OEM: Intel(R) Sandybridge/Ivybridge Graphics Chipset Accelerated VGA BIOS
(II) VESA(0): VESA VBE OEM Software Rev: 1.0
(II) VESA(0): VESA VBE OEM Vendor: Intel Corporation
(II) VESA(0): VESA VBE OEM Product: Intel(R) Sandybridge/Ivybridge Graphics Controller
(II) VESA(0): VESA VBE OEM Product Rev: Hardware Version 0.0
(II) VESA(0): virtual address = 0x7f03faf5c000,
(II) VESA(0): Setting up VESA Mode 0x17F (1600x900)
(==) VESA(0): Default visual is TrueColor
(==) VESA(0): Backing store disabled
(==) VESA(0): DPMS enabled

and

00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:0166] (rev 09)
	Subsystem: Dell Device [1028:0552]
	Flags: bus master, fast devsel, latency 0, IRQ 7
	Memory at d2000000 (64-bit, non-prefetchable) [size=4M]
	Memory at c0000000 (64-bit, prefetchable) [size=256M]
	I/O ports at 4000 [size=64]
	Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
	Capabilities: [d0] Power Management version 2
	Capabilities: [a4] PCIe advanced features <?>

Can someone please tell me how to load the Intel Drivers instead of the VESA?



Thanks a lot

[santhrax]

Hi,

yesterday I figured out how to load the i915 driver.

[GUIDE] Loading the i915 driver in the 3.2.6 kernel without adding unsupported PPA's

I follow the guide including the /etc/default/grub options and when I am loadin the driver via

modprobe i915 modeset=1

When startx --> my screen starts flickering and thats all what happen. No way back to switch to console via CTRL+ALT+F1, F2,...

System is running but I don't have a screen output.

So in my opinion the i915 driver is not working properly with Intel HD 4000 at the moment.

Any other tipps?

[maverik35]

First you need to make sure the driver loaded, that is not the way....

When posting, include the command, not only the output.

Now, post the output of: lspci | grep -i vga

Then get the pci id and do: lspci -vvs xx:xx.x (the xx:xx.x is the pci id). Post output.

[santhrax]

hi maverik35,

here is the output:

lspci | grep -i vga

00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
01:00.0 VGA compatible controller: NVIDIA Corporation GK107 [GeForce GT 650M] (rev ff)

lspci -vvs 00:02.0

00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
	Subsystem: Dell Device 0552
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 7
	Region 0: Memory at d2000000 (64-bit, non-prefetchable) [size=4M]
	Region 2: Memory at c0000000 (64-bit, prefetchable) [size=256M]
	Region 4: I/O ports at 4000 [size=64]
	Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
		Address: 00000000  Data: 0000
	Capabilities: [d0] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [a4] PCIe advanced features <?>

CPU: Intel Core i7 3630QM

I am sorry for my further post but this problem drives my nuts!
Actually something wrong but I cannot figure out where the problem could be. Also I am not sure if the i915 is the correct one.



Thanks for help!

[WepWapWee]

Hi,
First of all, make sure you have this line in the "lspci -vvs 00:02.0" output:

Kernel driver in use: i915

I can't see it in your previous post...I'm thinking it might be a copy/paste typo? Anyway...

1) If you have the line (the i915 kernel driver is in use), then check out my post here: http://www.backtrack-linux.org/forum...ad.php?t=47860
Updating the Xorg intel drivers solved my problem, for a similar(but not identical) VGA adapter, namely Intel HD 3000.

2) If your i915 driver is not in use, then maybe the Nvidia VGA adapter is enabled and it prevents the Intel HD4000 to "come to live". I'm just guessing here... If I am right, then try to disable the Nvidia VGA card (BIOS ?), and then take care of i915 and Xorg intel drivers.

On short, make sure i915 is used by your Intel HD4000, then update Xorg drivers and your problem should be fixed.

[maverik35]

Hi,
First of all, make sure you have this line in the "lspci -vvs 00:02.0" output:


I can't see it in your previous post...I'm thinking it might be a copy/paste typo? Anyway...

1) If you have the line (the i915 kernel driver is in use), then check out my post here: http://www.backtrack-linux.org/forum...ad.php?t=47860
Updating the Xorg intel drivers solved my problem, for a similar(but not identical) VGA adapter, namely Intel HD 3000.

2) If your i915 driver is not in use, then maybe the Nvidia VGA adapter is enabled and it prevents the Intel HD4000 to "come to live". I'm just guessing here... If I am right, then try to disable the Nvidia VGA card (BIOS ?), and then take care of i915 and Xorg intel drivers.

On short, make sure i915 is used by your Intel HD4000, then update Xorg drivers and your problem should be fixed.

I totally agree with WepWap, Video module was not loaded, at the end of lspci -vvs xx:xx.x should be the driver/module loaded by kernel.

Now, what video card is using your machine? The intel or nvidia?..After that, you have to see if you install the Intel or the nvidia module...

[santhrax]

I managed to get the i915 driver loaded. On CLI erverything is ok until I STARTX - then my notebook screen gets flickering in all colours with no way to turn it off
so I thought to connect an external screen and see what will happen. As you can see I will have a working external screen with changeable resolution but the notebook screen is flickering.

Any ideas?

IMG_20130117_152444.jpg

[santhrax]

picture attached

[maverik35]

I managed to get the i915 driver loaded. On CLI erverything is ok until I STARTX - then my notebook screen gets flickering in all colours with no way to turn it off
so I thought to connect an external screen and see what will happen. As you can see I will have a working external screen with changeable resolution but the notebook screen is flickering.

Any ideas?

IMG_20130117_152444.jpg

Let me be more clear: if you activated the modeset=1 (i915.nmodeset=1), that will not be enough, the KMS (Kernel Mode Setting) is a Kernel feature that the only thing it does is let you manage high resolution in Text Mode, it will show graphics in text mode, before starting the X's...Period.

Now, again, what is the default video card used by Laptop?..After knowing that, you must load proper driver if not loaded...

You have to know that info, is not about doing what this post says, or the other post says, and bla bla bla.....Make sure what you have, what has been loded by kernel and then analyze problem.

[santhrax]

Now, again, what is the default video card used by Laptop?..After knowing that, you must load proper driver if not loaded...

How can I find out? I got 2 - Intel HD 4000 (Core i7 3630QM) and the NVIDIA GT650m - I would like to use the Intel for normal desktop if that is possible.
I also tried to install the xserver-xorg-video-intel driver from different ppa's.
But when the i915 driver is load (ex. via modprobe i915) my screen starts flickering with all colours.