Does anyone have any experience with the intel hd 2000/hd 3000 integrated graphics set up? I'm having driver issues but I only have squeeze installed with the xserver-xorg-video-intel 2.17 driver from squeeze-backports. Research tells me that the Sandy Bridge issues are resolved in the 3.1 kernel. I am going to install aptosid on the bugger and hope that all is well. Any one have any advice?

I've been using a hd3000 day-to-day now with aptosid on my primary machine for I think nearly 8 months.

I had the odd 3d issue initially where some games would fairly randomly take out X. I don't think that's happened with 3.1 but I play them rarely enough I just might have got lucky (I only really installed them for testing). I'm pretty sure 3.2 has done more to improve the support for these chips though I've yet to get around do doing a d-u myself to have a look. Regressions and small issues are always possible when things are being actively developed though.

No matter, 1920x1080 is what I'm looking for but am only getting 1280x1024.

Also, I did install aptosid and got a blank screen on boot. I went back to squeeze with a minimal install and upgraded to debian sid. I installed lxde which pulled in xserver. I still get the blank screen with any kernel newer than 2.6.32.

Well I can only make wild guesses (looking at your Xorg logs might offer more clues).

Did aptosid work ok when you booted it live to install it, but then after install it just started "black screening" you? Did you do anything manual, like set anything in xorg.conf or add any cheatcodes?

Do you have multiple video outputs? Do you have more then one connected (or does X think you do)? In other words could X be starting up on the "wrong" output which you don't see?

You were probably "stuck" at 1280x1024 on 2.6.32 thanks to it simply using vesa, that kernel is too old really for these graphics devices.

jheaton5

Post subject:Posted: 07.01.2012, 16:11

Joined: 2010-09-18
Posts: 34

Status: Offline

Thank you for your response. Here are my responses to your ideas.

bfree wrote:

Well I can only make wild guesses (looking at your Xorg logs might offer more clues).

Well, I looked at syslog, but overlooked the Xorg logs. I'll do that.

Quote:

Did aptosid work ok when you booted it live to install it, but then after install it just started "black screening" you? Did you do anything manual, like set anything in xorg.conf or add any cheatcodes?

On the live CD, I got the opening menu, but then got a blank screen when I selected aptosid. I erred when I stated that I installed aptosid. I booted the live DVD on another machine with Nvidia graphics and had no trouble. I have not made any manual adjustments because I can't find a clue as to what to adjust.

Quote:

Do you have multiple video outputs? Do you have more then one connected (or does X think you do)? In other words could X be starting up on the "wrong" output which you don't see?

There is a standard external monitor jack. I have an old monitor that I will connect and see what the results are.

Thanks, towo, I agree. While it did get my system out of the blank screen it did not fix the framebuffer issue. I'm still doing RTFM, but have not found the solution yet. At least I now can use the computer directly instead of having to ssh into it from another computer.

Is the frame buffer console built in to the slh kernel? See below and here

Quote:

945GM and 82865G

In my system (HP/Compaq nx7300 with 945GM) enabling of KMS when loading the i915 module caused blank screen (seems not to be related to incorrect mode, rather the system got suspended or hibernated) when booting the system. Problem could be cured by changing of /etc/modprobe.d/i915-kms.conf to options i915 modeset=0. What's interesting, booting with acpi=off also cured the problem. The same problem occured in a desktop system with 82865G (link)

After last (ca. 20th October 2010) update of my debian/testing systems, the xserver-xorg-video-intel stopped to work with i915 modeset set to 0. Therefore the workaround mentioned in the previous point was not applicable any more. Setting of i915 modeset to 1 still caused blank screen, as soon as the i915 module is loaded. After more investigations I've found, that the problem is related to framebuffer console. If KMS is switched on, the framebuffer console support must be selected. In my systems (self compiled kernel without initial ramdisk) I had to to set CONFIG_FRAMEBUFFER_CONSOLE=y, CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y . Maybe with initial ramdisk, compiling it as module would be sufficient, but I've not checked it. Unfortunately the kernel "make menuconfig" doesn't check if the framebuffer console support is selected when CONFIG_DRM_I915_KMS is set to "y"

When I get home I'm going to try booting with acpi off.

jheaton5

Post subject:Posted: 21.01.2012, 15:18

Joined: 2010-09-18
Posts: 34

Status: Offline

I have installed 3.2 kernel and expected that to resolve my issue. The framebuffer does load and provides a higher resolutiion on boot, but about 30 seconds into the boot it unloads and the screen goes blank.
I have the following error in my kern.log

I suspect now that this is the problem. Research suggests patching the DSDT but I'm not up for rebuilding the kernel.

jheaton5

Post subject:Posted: 29.01.2012, 13:20

Joined: 2010-09-18
Posts: 34

Status: Offline

Edit: I changed the title of the thread to more accurately state the issue.

Update:
Some system is looping through brightness settings until it finds the correct one and then the backlight turns on. Whan that occurs, I have 1920x1080 resolution. The time it takes this event to occur varies from a few minutes to a few hours. So, I am leaving my computer on 24/7.