DG33BU - Intel GMA 3100 - loaded -vesa rather than -intel

Bug #218242 reported by Radha Krishna. S.
20
Affects Status Importance Assigned to Milestone
xserver-xorg-video-intel (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: xorg

Hi,

I've just assembled a new PC with an Intel DG33BU mother board - has Intel GMA3100 graphics subsystem. Installation of Ubuntu Hardy Heron Beta went through fine. However, vesa driver was loaded, and not the intel driver.

I tried changing the graphics driver using Applications->Other->Screens and Graphics. This is the behavior I noticed:

1. In the Choose Graphics Driver dialog, choose driver by name lists intel in the available driver list.
2. Choose Driver by model, however doesn't list G33/ GMA 3100.
3. When I select intel in choose driver by name list and hit Test, the screen gets to a default black and white X screen with a very low resolution.
4. Attached herewith is the latest Xorg.0.log.

Please do let me know if I can be of any help!

Regards,
Radha.

Revision history for this message
Radha Krishna. S. (sradhakrishna) wrote :
Revision history for this message
Ashish SHUKLA (wahjava) wrote :

Hi,

Can you paste the resolutions supported by Xorg with 'intel' driver by running xrandr in some terminal. You can also try switching to your desired resolution using xrandr. e.g. to switch to 1024x768 @ 75 Hz (vertical refresh rate), use 'xrandr -s 1024x768 -r 75' .

HTH
Ashish Shukla

Revision history for this message
Radha Krishna. S. (sradhakrishna) wrote : Re: [Bug 218242] Re: DG33BU - Intel GMA 3100 - graphics driver problems

Am not at my pc right now and it would be tough for me to do as suggested,
but here's something that I've already done.

When I select 'intel' driver in the list of drivers, a default X display
loads up with 640 x 480 resolution. When I look into the resolutions
supported on the display, there is no other resolution available for
selection, other than 640 X 480.

Does that information help in any manner??

Had to get to a terminal session, stop gdm, remove all xorg.conf files and
restart to get back to a session driven out of vesa. Or is it? because,
there was dist upgrade pushed on my PC. After the upgrade, the other ->
Screen and Graphics settings is not available anymore. Is there a way to
figure out which graphics driver is in use??

Regards,
Radha.

On Fri, Apr 18, 2008 at 11:36 AM, आशीष शुक्ल Ashish Shukla <
<email address hidden>> wrote:

> Hi,
>
> Can you paste the resolutions supported by Xorg with 'intel' driver by
> running xrandr in some terminal. You can also try switching to your
> desired resolution using xrandr. e.g. to switch to 1024x768 @ 75 Hz
> (vertical refresh rate), use 'xrandr -s 1024x768 -r 75' .
>
> HTH
> Ashish Shukla
>
> --
> DG33BU - Intel GMA 3100 - graphics driver problems
> https://bugs.launchpad.net/bugs/218242
> You received this bug notification because you are a direct subscriber
> of the
>

Revision history for this message
Ashish SHUKLA (wahjava) wrote :

>>>>> Radha Krishna S writes:
    Radha> Am not at my pc right now and it would be tough for me to do as suggested,
    Radha> but here's something that I've already done.

    Radha> When I select 'intel' driver in the list of drivers, a default X display
    Radha> loads up with 640 x 480 resolution. When I look into the resolutions
    Radha> supported on the display, there is no other resolution available for
    Radha> selection, other than 640 X 480.

I'm not sure but I think it uses xrandr to query what modes are
available. Which version of Ubuntu are you running when you tried
this ? What kind of monitor are you using ?

    Radha> Does that information help in any manner??

    Radha> Had to get to a terminal session, stop gdm, remove all xorg.conf files and
    Radha> restart to get back to a session driven out of vesa. Or is it?

vesa is a generic driver. You can try following, after stopping gdm, and wiping off xorg.conf:

1. Login to a TTY (using Ctrl-Alt-F1).
2. Execute following in one shot at your TTY.

abbe [~] chateau $ Xorg & ; sleep 5 ; export DISPLAY=:0 ; xrandr >xrandr-output.txt ; killall Xorg

3. Now, back at TTY, xrandr-output.txt contains output of xrandr.

You can also execute 'ddcprobe' in a root shell, to get list of
resolutions, refresh rates supported by your monitor. ddcprobe doesn't need X
running.

    Radha> because, there was dist upgrade pushed on my PC. After the
    Radha> upgrade, the other -> Screen and Graphics settings is not
    Radha> available anymore. Is there a way to figure out which
    Radha> graphics driver is in use??

abbe [~] chateau $ fgrep drivers/ /var/log/Xorg.0.log

HTH
--
Ashish Shukla आशीष शुक्ल http://wahjava.wordpress.com/
·-- ·- ···· ·--- ·- ···- ·- ·--·-· --· -- ·- ·· ·-·· ·-·-·- -·-· --- --

Bryce Harrington (bryce)
Changed in xserver-xorg-video-intel:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Nigel Ridley (nigel-rmk) wrote :

I had a similar problem on a Dell Inspiron 1525n Laptop, which has, according to lspci, a:

00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated
Graphics Controller (rev 0c)

Up until recently it was loading the vesa driver instead of the intel. Whenever I tried to change to the intel driver I would loose x and have to 'sudo dpkg-reconfigure -phigh xserver-xorg' to get X back again.

However, yesterday (18.04), after the usual updates/upgrades, I decided to try again and wanted to see what a 'sudo dpkg-reconfigure -phigh xserver-xorg' would give me.
This is now the results:
nigel@laptop:~$ fgrep drivers/ /var/log/Xorg.0.log
(II) Loading /usr/lib/xorg/modules/drivers//intel_drv.so

and, just to encourage you:

nigel@laptop:~$ glxgears
5675 frames in 5.0 seconds = 1134.881 FPS
5783 frames in 5.0 seconds = 1156.530 FPS
5757 frames in 5.0 seconds = 1151.319 FPS
93043 frames in 5.0 seconds = 18608.536 FPS
138082 frames in 5.0 seconds = 27616.367 FPS
138271 frames in 5.0 seconds = 27654.023 FPS
138449 frames in 5.0 seconds = 27689.762 FPS
89689 frames in 5.0 seconds = 17937.004 FPS
5789 frames in 5.0 seconds = 1157.721 FPS
6324 frames in 5.0 seconds = 1264.755 FPS
6335 frames in 5.0 seconds = 1266.824 FPS
6340 frames in 5.0 seconds = 1267.815 FPS

So perhaps this bug has been fixed??

Revision history for this message
Nigel Ridley (nigel-rmk) wrote : Re: [Bug 218242] Re: DG33BU - Intel GMA 3100 - loaded -vesa rather than -intel

Bryce Harrington wrote:
> ** Changed in: xserver-xorg-video-intel (Ubuntu)
> Importance: Undecided => Medium
> Status: New => Confirmed
>
Thanks Bryce,

I just added a comment to the bug page. It would seem that the problem is fixed.
Yesterday I did a 'sudo dpkg-reconfigure -phigh xserver-xorg' and now the intel driver loads:
nigel@laptop:~$ fgrep drivers/ /var/log/Xorg.0.log
(II) Loading /usr/lib/xorg/modules/drivers//intel_drv.so

It might be related: I checked using 'Adept' to see which 'intel' packages were installed
and I had two:
xserver-xorg-video-i810
and
xserver-xorg-video-intel

I removed the xserver-xorg-video-i810 and then did the 'sudo dpkg-reconfigure -phigh
xserver-xorg'.

Blessings,

Nigel

--
OliveRoot Ministries
http://www.oliveroot.net/

PrayingForIsrael.net
http://www.prayingforisrael.net/

Revision history for this message
Id2ndR (id2ndr) wrote :

[My comment is probably useless, but this is just an information]
This is not the case for me with : Intel Corporation 82G33/G31 Express Integrated Graphics Controller (rev 02)
However I haved nvidia-glx-new package installed (because I used an nvidia card on pci-e port), and after removing the card and the driver line, and "load glx" option in xorg.conf, I didn't get glx : glx module installed by nvidia driver was in conflict and I needed to remove the package.
[/..]

Revision history for this message
Radha Krishna. S. (sradhakrishna) wrote : Re: [Bug 218242] Re: DG33BU - Intel GMA 3100 - graphics driver problems

Hey, thanks for the info!

Here's the output of 'fgrep drivers/ /var/log/Xorg.0.log' on my system:

(II) Loading /usr/lib/xorg/modules/drivers//intel_drv.so
(II) Loading /usr/lib/xorg/modules/drivers//fbdev_drv.so
(II) Loading /usr/lib/xorg/modules/drivers//vesa_drv.so
(II) Loading /usr/lib/xorg/modules/drivers//vga_drv.so
(II) Unloading /usr/lib/xorg/modules/drivers//fbdev_drv.so
(II) Unloading /usr/lib/xorg/modules/drivers//vesa_drv.so
(II) Unloading /usr/lib/xorg/modules/drivers//vga_drv.so

So, am guessing that 'intel' is the driver loaded?? Mostlikely. I see that
in System -> Preferences -> Appearance, Extra effects do get loaded without
an issue. Will try and enable compiz and see what I get.

Will keep you updated.

Regards,
Radha.

On Fri, Apr 18, 2008 at 12:51 PM, आशीष शुक्ल Ashish Shukla <
<email address hidden>> wrote:

> >>>>> Radha Krishna S writes:
> Radha> Am not at my pc right now and it would be tough for me to do as
> suggested,
> Radha> but here's something that I've already done.
>
> Radha> When I select 'intel' driver in the list of drivers, a default X
> display
> Radha> loads up with 640 x 480 resolution. When I look into the
> resolutions
> Radha> supported on the display, there is no other resolution available
> for
> Radha> selection, other than 640 X 480.
>
> I'm not sure but I think it uses xrandr to query what modes are
> available. Which version of Ubuntu are you running when you tried
> this ? What kind of monitor are you using ?
>
> Radha> Does that information help in any manner??
>
> Radha> Had to get to a terminal session, stop gdm, remove all xorg.conf
> files and
> Radha> restart to get back to a session driven out of vesa. Or is it?
>
> vesa is a generic driver. You can try following, after stopping gdm, and
> wiping off xorg.conf:
>
> 1. Login to a TTY (using Ctrl-Alt-F1).
> 2. Execute following in one shot at your TTY.
>
> abbe [~] chateau $ Xorg & ; sleep 5 ; export DISPLAY=:0 ; xrandr
> >xrandr-output.txt ; killall Xorg
>
> 3. Now, back at TTY, xrandr-output.txt contains output of xrandr.
>
> You can also execute 'ddcprobe' in a root shell, to get list of
> resolutions, refresh rates supported by your monitor. ddcprobe doesn't
> need X
> running.
>
> Radha> because, there was dist upgrade pushed on my PC. After the
> Radha> upgrade, the other -> Screen and Graphics settings is not
> Radha> available anymore. Is there a way to figure out which
> Radha> graphics driver is in use??
>
> abbe [~] chateau $ fgrep drivers/ /var/log/Xorg.0.log
>
> HTH
> --
> Ashish Shukla आशीष शुक्ल
> http://wahjava.wordpress.com/
> ·-- ·- ···· ·--- ·- ···- ·- ·--·-· --· -- ·- ·· ·-·· ·-·-·- -·-· --- --
>
> --
> DG33BU - Intel GMA 3100 - graphics driver problems
> https://bugs.launchpad.net/bugs/218242
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Radha Krishna. S. (sradhakrishna) wrote :
Download full text (3.2 KiB)

Compiz - Cube and 3D windows work fine! :-) Haven't played around it
extensively, but looks like its good to go!!

Regards,
Radha.

On Mon, Apr 21, 2008 at 8:48 AM, Radha Krishna Srimanthula <
<email address hidden>> wrote:

> Hey, thanks for the info!
>
> Here's the output of 'fgrep drivers/ /var/log/Xorg.0.log' on my system:
>
> (II) Loading /usr/lib/xorg/modules/drivers//intel_drv.so
> (II) Loading /usr/lib/xorg/modules/drivers//fbdev_drv.so
> (II) Loading /usr/lib/xorg/modules/drivers//vesa_drv.so
> (II) Loading /usr/lib/xorg/modules/drivers//vga_drv.so
> (II) Unloading /usr/lib/xorg/modules/drivers//fbdev_drv.so
> (II) Unloading /usr/lib/xorg/modules/drivers//vesa_drv.so
> (II) Unloading /usr/lib/xorg/modules/drivers//vga_drv.so
>
> So, am guessing that 'intel' is the driver loaded?? Mostlikely. I see that
> in System -> Preferences -> Appearance, Extra effects do get loaded without
> an issue. Will try and enable compiz and see what I get.
>
> Will keep you updated.
>
> Regards,
> Radha.
>
>
>
> On Fri, Apr 18, 2008 at 12:51 PM, आशीष शुक्ल Ashish Shukla <
> <email address hidden>> wrote:
>
> > >>>>> Radha Krishna S writes:
> > Radha> Am not at my pc right now and it would be tough for me to do
> > as suggested,
> > Radha> but here's something that I've already done.
> >
> > Radha> When I select 'intel' driver in the list of drivers, a default
> > X display
> > Radha> loads up with 640 x 480 resolution. When I look into the
> > resolutions
> > Radha> supported on the display, there is no other resolution
> > available for
> > Radha> selection, other than 640 X 480.
> >
> > I'm not sure but I think it uses xrandr to query what modes are
> > available. Which version of Ubuntu are you running when you tried
> > this ? What kind of monitor are you using ?
> >
> > Radha> Does that information help in any manner??
> >
> > Radha> Had to get to a terminal session, stop gdm, remove all
> > xorg.conf files and
> > Radha> restart to get back to a session driven out of vesa. Or is it?
> >
> > vesa is a generic driver. You can try following, after stopping gdm, and
> > wiping off xorg.conf:
> >
> > 1. Login to a TTY (using Ctrl-Alt-F1).
> > 2. Execute following in one shot at your TTY.
> >
> > abbe [~] chateau $ Xorg & ; sleep 5 ; export DISPLAY=:0 ; xrandr
> > >xrandr-output.txt ; killall Xorg
> >
> > 3. Now, back at TTY, xrandr-output.txt contains output of xrandr.
> >
> > You can also execute 'ddcprobe' in a root shell, to get list of
> > resolutions, refresh rates supported by your monitor. ddcprobe doesn't
> > need X
> > running.
> >
> > Radha> because, there was dist upgrade pushed on my PC. After the
> > Radha> upgrade, the other -> Screen and Graphics settings is not
> > Radha> available anymore. Is there a way to figure out which
> > Radha> graphics driver is in use??
> >
> > abbe [~] chateau $ fgrep drivers/ /var/log/Xorg.0.log
> >
> > HTH
> > --
> > Ashish Shukla आशीष शुक्ल
> > http://wahjava.wordpress.com/
> > ·-- ·- ···· ·--- ·- ···- ·- ·--·-· --· -- ·- ·· ·-·· ·-·-·- -·-· --- --
> >
> > --
> > DG33BU - Intel GMA 3100 - graphics driver problems
> > https://bugs.launchpad.net/bugs/218242
> > ...

Read more...

Revision history for this message
Bryce Harrington (bryce) wrote :

Thanks; closing as fixed as per comments 6, 8, and 9.

Changed in xserver-xorg-video-intel:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.