[SOLVED] Nvidea card problem on Samsung 300E5A notebook

a4necromant · 07-25-2012, 10:30 AM

Quote:

Originally Posted by H_TeXMeX_H

You can make a simple xorg.conf:

Code:

Section "Device"
    Identifier     "intel"
    Driver         "intel"
    VendorName     "Intel Corporation"
EndSection

It doesn't work.
---
After the installation, before I tried to install nvidea driver, 2D worked and x-system worked too. But now only terminal mod.
If there will be some way to restore default x-window parameters, all will be perfect. But I don't know how to restore thiese parameters......

H_TeXMeX_H · 07-25-2012, 10:35 AM

If it worked before it was probably using nouveau, so just delete /etc/X11/xorg.conf and let it handle everything.

T3slider · 07-25-2012, 12:46 PM

The nVidia proprietary driver overwrites some system files. You may have to reinstall xorg-server and mesa to restore the original xorg files. I think in theory the nVidia installer backs these files up to /var/lib/nvidia and when uninstalling should copy them back, so perhaps this is not the issue...but to make sure that X is fully restored it couldn't hurt to reinstall xorg-server and mesa. Then try messing around with xorg.conf.

Didier Spaier · 07-25-2012, 01:48 PM

The problem is that when you start X on a computer with a hybrid graphics you can hardly know which graphical processor will be active.

But there is a very simple workaround which is fallback to the "vesa" driver, as both Intel and nVidia chipsets should comply to the vesa standard.

So do this:

1) Get rid of any config files (whose name end in .conf) in /etc/X11 and /etc/X11/xorg.conf.d in removing it or renaming it (so the name don't end in .conf anymore).
You may keep files copied from /usr/share/X11/xorg.conf.d though if any.

2) As root type:

Code:

cd /etc/X11
mv xorg.conf-vesa xorg-vesa.conf

3) Before rebooting, edit lilo.conf to have

Code:

vga=normal

and in the image section add a line with

Code:

append="nomodeset"

then run: "lilo -t -v" and if all goes well: "lilo"

If you prefer, you can append aforementioned kernel parameters to lilo's command line. Hit Tab when you see lilo's greeting screen and type this for instance

Code:

Linux vga=normal nomodeset

You should then have X working though without hardware acceleration and may be with a different definition than the one you would have expected.

And to make sure what are your graphical processors please post the output of following command:

Code:

lspci -k | grep -A3 VGA

a4necromant · 07-26-2012, 01:04 AM

thankyou Didier Spaier, your method is working.

---
(Graffical effects still not working. but I think they will work after I will install bumblebee)

a4necromant · 07-26-2012, 02:08 AM

Faled to install bumblebee. It doesn't work.
Brings an error:

Code:

[error] The bumblebee demon has not been started yet or the socket pass /var/run/bumblebee.socket was incorrect
[error] Could not connect to bublebee daemon - is it running?

Didier Spaier · 07-26-2012, 02:52 AM

Vesa is a very basic driver, so it's normal that you don't get graphical effects with it.

The goal of this first step was only to get you a working display under X.

Next step will be to use a driver with more features, but to give you further guidance please post the output of:

Code:

lspci -k | grep -A3 VGA

EDIT To be complete, please attach file /var/log/Xorg.0.log (renamed as xlog.txt if needed) to your next post.

a4necromant · 07-26-2012, 04:09 AM

here is an output from terminal:

Code:

root@darkstar:~# lspci -k | grep -A3 VGA
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
        Subsystem: Samsung Electronics Co Ltd Device c606
        Kernel driver in use: i915
        Kernel modules: i915

Didier Spaier · 07-26-2012, 04:38 AM

These output shows that you don't have a nVidia GeForce® GT 520MX card, but only an Intel integrated graphic processor and it is *not* an Optimus model, unless the nVidia card (if any) be completely disabled. May be you can check if there is a BIOS setting or a physical switch for that?

By the way, what make you think you have a nVidia card? is it stated on some spec, or did you check by yourself?

Chances are you shouldn't have installed the nVidia driver at all.

If I am correct, just reinstall mesa and xorg-server as suggested by T3slider.

I remind you that the command to do that is:
upgradepkg --reinstall <package_name>

EDIT. For this to work, you should rename xorg-vesa.conf as xorg.conf-vesa otherwise the vesa driver will still be used.

a4necromant · 07-26-2012, 05:24 AM

Quote:

Originally Posted by Didier Spaier

May be you can check if there is a BIOS setting or a physical switch for that?

There is no switch in bios

Quote:

By the way, what make you think you have a nVidia card? is it stated on some spec, or did you check by yourself?

I know, that I have Nvidea card. In win7 Nvidea driver is downloading automatically. I have checked a lot. There is also an nvidea optimus logo on these notebook(you can see it in attach)....
(These notebook is designed by imperialists and capitalists to run the only one type of OS - Windows NT, by the way I have these problem)
----
After I installed OS on notebook all effects worked, 3D graffics was not warking. Now after all these manipulations I haven't got 2D graffical effects too....

Didier Spaier · 07-26-2012, 06:59 AM

As lspci only shows the Intel graphical processor, then sorry but I am out of ideas.

I suggest you just reinstall mesa, xorg-server and libdrm, make sure nouveau be not blacklisted in /etc/modprobe.conf/*.conf, rename xorg-vesa.conf as xorg.conf-vesa, and make sure you (re)start the system without the "nomodeset" parameter.

At least you should get back the level of performance you had at time of install.

But maybe somebudddy has a better idea?

PS If you issue following command:

Code:

lspci -vnn | grep '\''[030[02]\]'

You should see two lines, one for Intel and one for nVidia. Is that right?

To know more, see here.

a4necromant · 07-26-2012, 08:09 AM

yes, it's right

Code:

root@darkstar:~# lspci -vnn | grep '\''[030[02]\]'
00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
01:00.0 3D controller [0302]: nVidia Corporation Device [10de:1051] (rev a1)

but how will it help me. As I recognized from Samsung support, there are no official drivers for linux for thiese notebook...

Didier Spaier · 07-26-2012, 08:41 AM

Last resort, you could try the recently released 304.22 BETA driver from nVidia.

H_TeXMeX_H · 07-26-2012, 12:45 PM

Something interesting I found recently, but not for your laptop:
https://sites.google.com/site/mtrons/projects/eee1015pn

If you can only see the Intel card in lspci, maybe it is that the nvidia card is completely disabled. I'm not sure how to enable it, but you could try using acpi_call somehow. The link above is specific to my netbook, so I doubt the commands there will work, it's just an example.

Didier Spaier · 07-26-2012, 02:15 PM

@H TeXMeX H: In fact the card do show in lspci, not as a "VGA compatible controller" but as a "3D controller". That's my fault somehow, as I suggested to pipe the output to "grep VGA" first.

Anyhow, a4necromant could try bumblebee, but he seems to be more interested by graphical performance than by power saving at the moment, that's why I suggested him to try the beta nVidia driver first.

Would he be satisfied with it, he could then try again bumblebee as it is supposed to be able to cooperate with he blob as well as with nouveau, according to their supported drivers page.

I notice though this warning on the same page:

Quote:

WARNING:You must install the Nvidia binaries in a way that won't break Mesa's LibGL, it's needed for 3D acceleration on the intel card. This means that on most distros you will need a Bumblebee specific package for it to run, the stock packages on most cases will break LibGL. See #33

Unfortunately, I didn't find at what this "#33" refer.

Anyway, if you have bumblebee installed on your Slackware, maybe you could help the OP to install it as he had a problem running it (see his post #21).