[Gutsy Beta] 82865G Integrated Graphics Controller Not Correctly Identiified during setup

Bug #146284 reported by andrew.46
22
Affects Status Importance Assigned to Milestone
xserver-xorg-video-intel (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Hi,

 I have an 82865G Integrated Graphics Controller that I believe has been incorrectly identified by the install of Gutsy beta release.

 My /etc/X11/xorg.conf file is:

[..... edited out beginning commented out blurb ...]

Section "Files"
EndSection

Section "InputDevice"
 Identifier "Generic Keyboard"
 Driver "kbd"
 Option "CoreKeyboard"
 Option "XkbRules" "xorg"
 Option "XkbModel" "pc105"
 Option "XkbLayout" "us"
EndSection

Section "InputDevice"
 Identifier "Configured Mouse"
 Driver "mouse"
 Option "CorePointer"
 Option "Device" "/dev/input/mice"
 Option "Protocol" "ImPS/2"
 Option "ZAxisMapping" "4 5"
 Option "Emulate3Buttons" "true"
EndSection

Section "InputDevice"
 Driver "wacom"
 Identifier "stylus"
 Option "Device" "/dev/input/wacom"
 Option "Type" "stylus"
 Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
 Driver "wacom"
 Identifier "eraser"
 Option "Device" "/dev/input/wacom"
 Option "Type" "eraser"
 Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
 Driver "wacom"
 Identifier "cursor"
 Option "Device" "/dev/input/wacom"
 Option "Type" "cursor"
 Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "Device"
 Identifier "Generic Video Card"
 Driver "vesa"
 BusID "PCI:0:2:0"
EndSection

Section "Monitor"
 Identifier "DELL E153FP"
 Option "DPMS"
EndSection

Section "Screen"
 Identifier "Default Screen"
 Device "Generic Video Card"
 Monitor "DELL E153FP"
 DefaultDepth 24
 SubSection "Display"
  Modes "1024x768" "832x624" "800x600" "720x400" "640x480"
 EndSubSection
EndSection

Section "ServerLayout"
 Identifier "Default Layout"
 Screen "Default Screen"
 InputDevice "Generic Keyboard"
 InputDevice "Configured Mouse"

# Uncomment if you have a wacom tablet
# InputDevice "stylus" "SendCoreEvents"
# InputDevice "cursor" "SendCoreEvents"
# InputDevice "eraser" "SendCoreEvents"
EndSection

 And a partial section of my lspci is:

andrew@ilium:~$ lspci -vv
00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02)
        Subsystem: Dell Unknown device 0151
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
        Latency: 0
        Region 0: Memory at f0000000 (32-bit, prefetchable) [size=128M]
        Capabilities: <access denied>

00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02) (prog-if 00 [VGA])
        Subsystem: Dell Unknown device 0151
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Latency: 0
        Interrupt: pin A routed to IRQ 11
        Region 0: Memory at e8000000 (32-bit, prefetchable) [size=128M]
        Region 1: Memory at feb80000 (32-bit, non-prefetchable) [size=512K]
        Region 2: I/O ports at ed98 [size=8]
        Capabilities: <access denied>

 Thanks for your trouble,

     Andrew

Bryce Harrington (bryce)
Changed in xorg:
assignee: nobody → bryceharrington
Revision history for this message
Bryce Harrington (bryce) wrote :

Hi Andrew,

Is this still occurring for Gutsy-rc? Sorry we didn't get to this sooner, possibly we'll be able to get this into an -update if the fix is simple enough.

Changed in xorg:
status: New → Incomplete
Revision history for this message
andrew.46 (andrew.46-deactivatedaccount) wrote :

Hi Bryce,

 Thank you for getting back to me on this one. Can I apologise profusely to you on this one? I am no longer using Ubuntu and have no easy way of seeing if this is a continuing problem. Certainly at the time I simply made the changes to xorg.conf manually.

  Please accept my apologies for filing a bug report and then moving to another distro!

                Regards,

                     Andrew

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

Hi Andrew, thanks for getting back to me, but sorry to hear you've moved on to another distro! I'll go ahead and close out this bug.

Changed in xorg:
status: Incomplete → Invalid
Revision history for this message
jvivenot (jvivenot) wrote : Should be reopened...

Hi,

Well, you closed this bug, but I actually think it still isn't working.
I've downloaded the Gutsy release, and tested on the same chip.
The live CD freezes the whole computer at X starting up.
I've tried the "safe graphics mode" but finally, X answered that the screen wasn't suitable for any of the possible modes.

Anyway, the configuration made by the live CD was exactly the same that the one above (I actually have the same screen.)

Thanks
Julien

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

Reopening. jvivenot could you attach /var/log/Xorg.0.log after encountering this issue?

Changed in xorg:
status: Invalid → Incomplete
Revision history for this message
napchan (napchan) wrote :

Same problem here.
When trying to use Intel i810 does not get any image.
Vesa works...

Would like to know if there is any solution.
Could you please cc any reply to <email address hidden>?
Thanks.
Eli

Revision history for this message
Peter Clifton (pcjc2) wrote :

have you tried the "intel" driver?

Revision history for this message
brow96 (brow96) wrote :

I'm having the same problem. The Live CD won't work with the Dell version of a 82865G graphics controller. I dual boot so I know it's NOT a standard Intel chipset. How do I know this? When you try to install the drivers from Intel in Windows 2000 the operation aborts with a dialog box that says you are to contact the vendor for drivers. Simply put the Intel drivers will not load under Windows. Thus if the Intel drivers won't work under Windows (W2k) then it's not very likely that the standard Intel driver under Linux will work either.

I'm trying different configurations now. Dell has had their stinking hands in the works, again. It seems that every time I try to get Linux (any flavor) to work on a Dell system it's "iffy" at best. They love to customize the hardware, in tiny ways that make it, almost, impossible to get "regulation" software or drivers to work properly.

What surprises me is that this is still a problem after all these years. Or maybe it's soemthing new with Ubuntu?

Bill

Revision history for this message
Alex Mendez (martin-amendez) wrote :

I have the same problem on a Dell Optiplex 170L. I was putting together this computer for a friend of mine who does not have a computer at all. Using the Ubuntu 7.10 Intel x86 live CD, I ended up booting the live CD in Safe Graphics Mode. After installation, I restarted and found that it did not detect my graphics card correctly. After configuring the drivers and resolutions using the handy "configure" button, I was able to see the login and desktop correctly. I thought maybe that was the end to my problem, but I was wrong. After installing all the Ubuntu updates and restarting, the same thing happened again. It seemed to have reset itself again to the settings I had before I changed them. Using the "Start-up Manager" program I found in the Add/Remove, I changed the resolution of my Startup Splash Screen to 1024x768. I also saved the configuration of the Graphics card inside the Screens and Graphics application found in the System->Administration menu. I used the Intel i810 driver and set my resolution to 1024x768 at 75 hertz.

Revision history for this message
Alex Mendez (martin-amendez) wrote :

After all of the above, I restarted one more time, and it works fine. But it's still to question, Ubuntu did not detect my graphics card using just the installer. It even enabled compiz-fusion which means that hardware acceleration worked. Hopefully, this can help you fix your problems as well.

Bryce Harrington (bryce)
Changed in xserver-xorg-video-intel:
assignee: bryceharrington → nobody
importance: Undecided → High
status: Incomplete → Confirmed
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Please try booting a Hardy livecd (alpha4 or newer), this should work now.

Changed in xserver-xorg-video-intel:
status: Confirmed → Incomplete
Revision history for this message
Bryce Harrington (bryce) wrote :

We believe this works now. Please test with a recent version of Hardy (beta or newer) and reopen if the issue still occurs.

Changed in xserver-xorg-video-intel:
status: Incomplete → Fix Released
Revision history for this message
unixnewbie (darfsten) wrote :

this still does not work. I just did a fresh install which has a Intel Corporation 82865G Integrated Graphics built in graphics card. Xorg would only run in 800x600 or whatever. I don't even know what resolution is my optimal hjighest res? I'll have to google around and enter it in xorg.conf myself. I edited xorg to make it use either the i810 or the intel driver but I wish there was a tool that would allow me to chose the best res.

Revision history for this message
minkkinenk (minkkinenk) wrote :

I have same problem I am running Ubuntu 10.4
I have an 82865G Integrated Graphics Controller on a Vaio VGC-V174RB.
The only way I can boot is if I hold shift to get the Grub menu and edit the boot commands by replacing quiet splash by nomodeset, otherwise it freezes at startup...
It runs 800x600 Monitor Preferences doesn't recognize my display..
I tried all the above nothing works.

Karl

Revision history for this message
anna marti (anna-marti-gomez) wrote :

I have the same problem with the Intel Corporation 82865G Integrated Graphics Controller (rev 02) and Ubuntu10.04.
I could boot from LiveCD with i915.modeset=0 and install it afterwards but it isn't working that well with the ressolution.

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.