linuxgeek: [LINUX_Newbies] Re: Graphics problem with Mint 13? SOLVED

Hi Roy and Paul,

Many thanks for your helpful advice. What a great group this is!

I am pleased to report that the problem has now been resolved - checking Synaptic this morning, I found that there were further upgrades of the kernel and Xorg available. I applied them both, updated grub to remove nomodeset, restarted and, hey presto, all is working beautifully! No more choppiness with the cursor. I'm not sure which of the upgrades sorted it but that doesn't really matter. Roy, you were right about being patient linux does catch up sooner or later - usually sooner! Better than that "other" OS!

Life is beautiful with linux!

Thanks once again.

Frank

--- In LINUX_Newbies@yahoogroups.com, "Paul" wrote:
>
>
>
> --- In LINUX_Newbies@yahoogroups.com, Roy wrote:
> >
> > no reason for concern. Unlike Windows Linux drivers are not usually loaded
> > separately. Most come with the kernel.
> >
>
> Drivers may come with kernel source, but depending on how a kernel is configured they may not be built, or installed, to use on a system. In some rare cases the kernel itself may even be broken to not include the hardware device ID that would enable the kernel to use the driver with some hardware.
>
> But enough speculating let's get back to the problem at hand. I reviewed the thread and the graphics adapter in question has been identified as being an "Intel" but Intel makes a few, which one exactly?
>
> Find out by issuing the command lspci -v in a terminal and looking for "VGA compatible controller:" in the output. I just looked up your motherboard and if you mean on board you mean in your CPU with Intel.
>
> $ cat /proc/cpuinfo | grep "model name"
>
> might be useful? lspci should say though.
>
> Then issue the command uname -a and report back what that says.
>
> Observing dmesg might offer clues as to what is not working too.
>
> Issue the command:
> $ dmesg | less
>
> As soon as you've logged in. A lot of that is going to be pretty cryptic but try to pick something out that relates to your graphics adapter. Or just paste the whole mess into pastebin and I'll give it a look.
>
> Something I found in my notes file:
>
> Dec 9 11:26:44 giga kernel: [ 4.029999] agpgart-intel 0000:00:00.0: Intel HD Graphics Chipset
>
>
> $ dmesg > bootup.txt
>
> then copy and paste the contents of bootup.txt at http://pastebin.com/
> Give us the URL of your paste here of course. If you're really adventurous you can figure out how this works:
>
> https://www.stgraber.org/category/pastebinit/
>
> I don't use pastebinit enough to guide you. But you might as well be aware that it exists.
>
> With that information we may begin to figure out what you are missing and what you need to do to rectify it.
>
> We should be able to get you all sorted out. I have an i3 that I've managed to get to work in accelerated mode. Which is to say fully. So I am somewhat familiar with Intel graphics. My i3 configured properly is on par with a nVidia GT220 graphics adapter for 3D so it isn't too bad. It plays video great too. I'm not entirely sure what it is equivalent to for video decoding, but it is nice. Intel has put more effort into video than 3D.
>
> I have heard some rumors lately that Intel is not supporting some of their newest hardware in Linux as of now. I'm hoping that doesn't include what you have. They've been pretty good up to now though.
>
> P.S. Apparently I had issues with something called MTRR initially when I configured my Intel graphics so you might want to be on the lookout for that when you examine your kernel dmesg.
>
> Dec 9 11:26:44 giga kernel: [ 6.550944] mtrr: type mismatch for e0000000,10000000 old: write-back new: write-combining
> Dec 9 11:26:44 giga kernel: [ 6.550946] [drm] MTRR allocation failed. Graphics performance may suffer.
> Dec 9 11:26:44 giga kernel: [ 6.550949] [drm] detected 127M stolen memory, trimming to 32M
> Dec 9 11:26:44 giga kernel: [ 6.551089] pci 0000:00:02.0: irq 41 for MSI/MSI-X
> Dec 9 11:26:44 giga kernel: [ 6.551168] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
>
> To fix that I had to change a kernel configuration option:
>
> CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=1
>
> But if that is what is going on with you we'll cross that bridge when we get to it.
>