View previous topic :: View next topic |
Author |
Message |
Akela NDE n00b

Joined: 18 Jan 2012 Posts: 14 Location: France
|
Posted: Wed Jan 18, 2012 6:06 pm Post subject: [Solved] Blank screen at first reboot - and nothing |
|
|
Hello,
I tried to install my first Gentoo on a new computer, following the Handbook. Then at reboot, GRUB passed OK, the kernel boot messages seemed to be OK for 2 or 3 seconds, then ... black. Nothing but a blank screen, and no way to move between tty1, 2 etc. I didn't see a single line looking like a kernel panic or whatever.
I tried to connect from another computer using ssh but I can't find it on my network.
Then I booted an Ubuntu live CD and mounted the partitions to have a look at dmesg, but I can't find anything looking like a deadly error message (But I'm probably no good at analyzing it). Here's the dmesg log.
I really don't know what it can be, is it that I made huge mistakes while configuring my kernel? (Here is the .config it saved after make menuconfig)
The hardware is a Xeon E3-1245 CPU, Gigabyte Z68XP-UD3 motherboard with Intel Z68 chipset, Nvidia GTS450 video card, 2*4 GB DDR3 and old SATA hard drives.
Thank you for your help.
Last edited by Akela NDE on Sat Jan 21, 2012 5:56 pm; edited 1 time in total |
|
Back to top |
|
 |
comprookie2000 Retired Dev


Joined: 25 Jul 2004 Posts: 925 Location: Sun City Center, Florida
|
Posted: Thu Jan 19, 2012 4:44 pm Post subject: |
|
|
Boot up the livecd and chroot and add an entry without;
video=uvesafb:mtrr:3,ywrap,1920x1200-32@60 _________________ http://dev.gentoo.org/~dabbott/ |
|
Back to top |
|
 |
Akela NDE n00b

Joined: 18 Jan 2012 Posts: 14 Location: France
|
Posted: Thu Jan 19, 2012 7:17 pm Post subject: |
|
|
Hi comprookie2000, thanks for your help.
I tried it and it didn't work, the symptoms are the same.
I chrooted and emerged nvidia-drivers to see if it would do something, but it didn't and it's still the same.
So I'll try re-compiling a kernel and see ...
A Gentoo install a bit more complicated than that of a Debian or CentOS ! |
|
Back to top |
|
 |
NeddySeagoon Administrator


Joined: 05 Jul 2003 Posts: 55450 Location: 56N 3W
|
Posted: Thu Jan 19, 2012 7:37 pm Post subject: |
|
|
Akela NDE,
I tried to reply last night but my post did not reach the forums.
Your dmesg looks OK ... it tells that your have the intel KMS driver compiled, which is good on intel hardware.
Your kernel config shows that uvesafb support is not included so video=uvesafb:mtrr:3,ywrap,1920x1200-32@60 was always doomed to fail.
Further Kernel Mode Switching provides a framebuffer console at no extra change but you must not build any other framebuffer support.
You have both VESA and EFI framebuffer support in your kernel.
You need to rebuild the kernel with those items removed.
If you don't have an intel graphics chip, you don't want Intel KMS support. You mentioned nvidia-drivers ... thats for Xorg and nvidia cards only.
I think we need sight of yourbefore you do much more, so we can see what hardware you actually have, then we will know what to configure in the kernel to support it. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
 |
Akela NDE n00b

Joined: 18 Jan 2012 Posts: 14 Location: France
|
Posted: Thu Jan 19, 2012 7:58 pm Post subject: |
|
|
Hello NeddySeagoon, thanks for that.
Here's the lspci -k (in the chrooted environment) :
Code: | (chroot) / # lspci -k
00:00.0 Host bridge: Intel Corporation Device 0108 (rev 09)
00:01.0 PCI bridge: Intel Corporation Device 0101 (rev 09)
00:02.0 Display controller: Intel Corporation Sandy Bridge Integrated Graphics Controller (rev 09)
Subsystem: Giga-byte Technology Device d000
00:16.0 Communication controller: Intel Corporation Cougar Point HECI Controller #1 (rev 04)
Subsystem: Giga-byte Technology Device 1c3a
00:1a.0 USB Controller: Intel Corporation Cougar Point USB Enhanced Host Controller #2 (rev 05)
Subsystem: Giga-byte Technology Device 5006
00:1b.0 Audio device: Intel Corporation Cougar Point High Definition Audio Controller (rev 05)
Subsystem: Giga-byte Technology Device a102
00:1c.0 PCI bridge: Intel Corporation Cougar Point PCI Express Root Port 1 (rev b5)
00:1c.3 PCI bridge: Intel Corporation 82801 PCI Bridge (rev b5)
00:1c.4 PCI bridge: Intel Corporation Cougar Point PCI Express Root Port 5 (rev b5)
00:1c.5 PCI bridge: Intel Corporation Cougar Point PCI Express Root Port 6 (rev b5)
00:1c.6 PCI bridge: Intel Corporation Cougar Point PCI Express Root Port 7 (rev b5)
00:1c.7 PCI bridge: Intel Corporation Cougar Point PCI Express Root Port 8 (rev b5)
00:1d.0 USB Controller: Intel Corporation Cougar Point USB Enhanced Host Controller #1 (rev 05)
Subsystem: Giga-byte Technology Device 5006
00:1f.0 ISA bridge: Intel Corporation Device 1c44 (rev 05)
Subsystem: Giga-byte Technology Device 5001
00:1f.2 SATA controller: Intel Corporation Cougar Point 6 port SATA AHCI Controller (rev 05)
Subsystem: Giga-byte Technology Device b005
00:1f.3 SMBus: Intel Corporation Cougar Point SMBus Controller (rev 05)
Subsystem: Giga-byte Technology Device 5001
01:00.0 VGA compatible controller: nVidia Corporation Device 1245 (rev a1)
Subsystem: ASUSTeK Computer Inc. Device 83a6
01:00.1 Audio device: nVidia Corporation Device 0bee (rev a1)
Subsystem: ASUSTeK Computer Inc. Device 83a6
03:00.0 PCI bridge: Integrated Technology Express, Inc. Device 8892 (rev 30)
04:02.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306 Fire II IEEE 1394 OHCI Link Layer Controller (rev c0)
Subsystem: Giga-byte Technology GA-7VT600-1394 Motherboard
05:00.0 USB Controller: Device 1b6f:7023 (rev 01)
Subsystem: Giga-byte Technology Device 5007
06:00.0 USB Controller: Device 1b6f:7023 (rev 01)
Subsystem: Giga-byte Technology Device 5007
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
Subsystem: Giga-byte Technology GA-EP45-DS5 Motherboard
08:00.0 SATA controller: Device 1b4b:9172 (rev 11)
Subsystem: Giga-byte Technology Device b000 |
The funny thing is that it isn't the same as the lspci -k in the host environment (actually an Ubuntu live USB, as I have no CD available) :
Code: | $ lspci -k
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 Processor Family DRAM Controller (rev 09)
Kernel driver in use: agpgart-intel
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:02.0 Display controller: Intel Corporation Xeon E3-1200 Processor Family Integrated Graphics Controller (rev 09)
Subsystem: Giga-byte Technology Device d000
Kernel driver in use: i915
Kernel modules: i915
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
Subsystem: Giga-byte Technology Device 1c3a
Kernel driver in use: mei
Kernel modules: mei
00:1a.0 USB Controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05)
Subsystem: Giga-byte Technology Device 5006
Kernel driver in use: ehci_hcd
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05)
Subsystem: Giga-byte Technology Device a102
Kernel driver in use: HDA Intel
Kernel modules: snd-hda-intel
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.3 PCI bridge: Intel Corporation 82801 PCI Bridge (rev b5)
00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.6 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 7 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.7 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 8 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1d.0 USB Controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05)
Subsystem: Giga-byte Technology Device 5006
Kernel driver in use: ehci_hcd
00:1f.0 ISA bridge: Intel Corporation Z68 Express Chipset Family LPC Controller (rev 05)
Subsystem: Giga-byte Technology Device 5001
Kernel modules: iTCO_wdt
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 05)
Subsystem: Giga-byte Technology Device b005
Kernel driver in use: ahci
Kernel modules: ahci
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
Subsystem: Giga-byte Technology Device 5001
Kernel modules: i2c-i801
01:00.0 VGA compatible controller: nVidia Corporation Device 1245 (rev a1)
Subsystem: ASUSTeK Computer Inc. Device 83a6
Kernel driver in use: nouveau
Kernel modules: nouveau, nvidiafb
01:00.1 Audio device: nVidia Corporation Device 0bee (rev a1)
Subsystem: ASUSTeK Computer Inc. Device 83a6
Kernel driver in use: HDA Intel
Kernel modules: snd-hda-intel
03:00.0 PCI bridge: Integrated Technology Express, Inc. Device 8892 (rev 30)
04:02.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller (rev c0)
Subsystem: Giga-byte Technology GA-7VT600-1394 Motherboard
Kernel driver in use: firewire_ohci
Kernel modules: firewire-ohci
05:00.0 USB Controller: Etron Technology, Inc. EJ168 USB 3.0 Host Controller (rev 01)
Subsystem: Giga-byte Technology Device 5007
Kernel driver in use: xhci_hcd
Kernel modules: xhci-hcd
06:00.0 USB Controller: Etron Technology, Inc. EJ168 USB 3.0 Host Controller (rev 01)
Subsystem: Giga-byte Technology Device 5007
Kernel driver in use: xhci_hcd
Kernel modules: xhci-hcd
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
Subsystem: Giga-byte Technology GA-EP45-DS5 Motherboard
Kernel driver in use: r8169
Kernel modules: r8169
08:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9172 SATA 6Gb/s Controller (rev 11)
Subsystem: Giga-byte Technology Device b000
Kernel driver in use: ahci
Kernel modules: ahci |
|
|
Back to top |
|
 |
NeddySeagoon Administrator


Joined: 05 Jul 2003 Posts: 55450 Location: 56N 3W
|
Posted: Thu Jan 19, 2012 8:54 pm Post subject: |
|
|
Akela NDE,
Code: | 00:02.0 Display controller: Intel Corporation Sandy Bridge Integrated Graphics Controller (rev 09) |
Is the important line
or Code: | 00:02.0 Display controller: Intel Corporation Xeon E3-1200 Processor Family Integrated Graphics Controller (rev 09)
Subsystem: Giga-byte Technology Device d000
Kernel driver in use: i915
Kernel modules: i915 |
lspci works by looking up the vendor and device IDs read from each PCI device in a database. Intels Vendor ID is 0x8086. Different versions of the database may have different text strings for the samedevice.
To ensure that they report the same thing, tryin both environments. The numbers should be the same and thats all lspci reads from the hardware.
I don't see any sign of any nvidia hardware but you certainly have an intel chipset.
Remove the video= line grom your grub.conf kernel line, you don't want to use any framebuffer driver in the kernel.
Rebuild your kernel without VESA Framebuffer support and without EFI framebuffer support reinstall your kernel and reboot.
Based on your lspci output, you can't use the nvidia-driver. If your system is a laptop with two graphics chips, thats a feature for another day.
Make it work first - make it better/faster/etc when you have something that works you can revert to to lickk your wounds if better/faster/etc fails first time.
Putting all the bits in, switching on and tuning for maximum smoke is not a good way to build a gentoo system, the problem space is just too big. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
 |
Akela NDE n00b

Joined: 18 Jan 2012 Posts: 14 Location: France
|
Posted: Thu Jan 19, 2012 9:09 pm Post subject: |
|
|
Yup, both lspci -n are the same.
There actually is an nVidia graphic card (I mounted it), but the motherboard seems to include an Intel graphical controller as well. So you're right, let's try to have it working first, graphics will come later.
I just hope it doesn't need the screen to be plugged on the motherboard then, cause it only has an HDMI port and I don't have an HDMI cable! (But I can buy one...) |
|
Back to top |
|
 |
NeddySeagoon Administrator


Joined: 05 Jul 2003 Posts: 55450 Location: 56N 3W
|
Posted: Thu Jan 19, 2012 9:22 pm Post subject: |
|
|
Akela NDE,
Both graphics chips should drive both the internal and external displays at the same time.
The idea is tht the built in graphics are lower power, which is good for battery life but not as good for high performace graphical applications, so you switch (seamlessly) between them as the application demands.
Linux isn't quite there yet. It works with some chips in some combinations and there is no support for seamless switching in Xorg. You need to quit Xorg, switch graphics chips (and maybe xorg.conf files) then restart Xorg. I did not check your kernel to see if you selected support for multiple graphics chips but its on and set for two by default. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
 |
Akela NDE n00b

Joined: 18 Jan 2012 Posts: 14 Location: France
|
Posted: Thu Jan 19, 2012 10:34 pm Post subject: |
|
|
OK. I don't remember playing with that multiple chips option, so it's probably by default. Anyway, we'll see later for the nVidia support.
I tried to recompile a kernel excluding the framebuffer options but apparently there was still some nvidia stuff cause it did the same black screen again, and after looking at dmesg from my live-USB, it ends like this:
Code: | [ 7.913383] nvidia: module license 'NVIDIA' taints kernel.
[ 7.913385] Disabling lock debugging due to kernel taint
[ 7.944774] nvidia 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 7.944779] nvidia 0000:01:00.0: setting latency timer to 64
[ 7.944782] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
[ 7.944958] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 290.10 Wed Nov 16 17:39:29 PST 2011
[ 8.393333] EXT4-fs (sdc2): re-mounted. Opts: (null)
[ 8.472823] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) |
So I'm going to emerge --unmerge nvidia-drivers, hunt for anything nvidia-like in make.conf, emerge --update --newuse --deep world and then recompile a kernel, looking for and excluding anything that looks nvidia-ish.
I hope works... |
|
Back to top |
|
 |
Akela NDE n00b

Joined: 18 Jan 2012 Posts: 14 Location: France
|
Posted: Thu Jan 19, 2012 11:16 pm Post subject: |
|
|
OK, so now it works ! Well, somehow
Apparently there is STILL some trace of an nvidia module, but it doesn't matter since it's not actually loaded.
And there is no network, which is a bit more annoying; according to the last messages before the welcome prompt, I should "ensure that [I] have loaded the correct kernel module for [my] hardware".
We'll see that tomorrow, but I'm really glad to have been able to log in my first Gentoo! Thanks guys. |
|
Back to top |
|
 |
comprookie2000 Retired Dev


Joined: 25 Jul 2004 Posts: 925 Location: Sun City Center, Florida
|
Posted: Fri Jan 20, 2012 2:25 am Post subject: |
|
|
From your lspci;
Code: |
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
Subsystem: Giga-byte Technology GA-EP45-DS5 Motherboard
Kernel driver in use: r8169
Kernel modules: r8169
|
From your .config
Code: |
# CONFIG_R8169 is not set
|
don't forget to emerge dhcpcd _________________ http://dev.gentoo.org/~dabbott/ |
|
Back to top |
|
 |
Akela NDE n00b

Joined: 18 Jan 2012 Posts: 14 Location: France
|
Posted: Fri Jan 20, 2012 1:54 pm Post subject: |
|
|
And it works.
Well it was quite obvious when you think about it, but you have to get used to compiling kernels and doing things the Gentoo way.
I really like it when it works and you learns things like that. Gentoo rocks!
Now, time for X, then Gnome, then maybe I'll try nVidia again ... Hours of fun
Thanks a lot, again. |
|
Back to top |
|
 |
Akela NDE n00b

Joined: 18 Jan 2012 Posts: 14 Location: France
|
Posted: Fri Jan 20, 2012 7:59 pm Post subject: |
|
|
... and it doesn't work any more.
I tried to install X following the instructions on that page for Intel integrated graphics, and it does the same again, blank screen and impossible to access tty1 2 etc.
On the other hand, networking does work and I can connect using ssh.
I tried a dmesg, here ; and here's the kernel's .config.
I can't see anything that's wrong in the dmesg (with my limited capacities), but when I try startx from the ssh console, here's what I get : Code: | # startx
xauth: file /root/.serverauth.2614 does not exist
X.Org X Server 1.11.2
Release Date: 2011-11-04
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.1.6-gentoo x86_64 Gentoo
Current Operating System: Linux Hades 3.1.6-gentoo #6 SMP Fri Jan 20 18:41:07 CET 2012 x86_64
Kernel command line: root=/dev/sdc2
Build Date: 20 January 2012 06:14:45PM
Current version of pixman: 0.24.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Jan 20 20:49:17 2012
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE) Failed to load module "nouveau" (module does not exist, 0)
(EE) Failed to load module "vesa" (module does not exist, 0)
(EE) Failed to load module "fbdev" (module does not exist, 0)
(EE) No drivers available.
Fatal server error:
no screens found
Please consult the The X.Org Foundation support at http://wiki.x.org for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information. |
Here's the Xorg.0.log, just in case, but I didn't find anything more in it.
I can't understand why it's trying to use nouveau or vesa modules since I did not choose them in the kernel configuration.
But maybe I did something wrong again?
And moreover there is no xorg.conf in /etc which I could try to use ... I tried X -configure but it gave me a similar error message again, this time about an fbcon module that would be missing.
Any idea? I'm a bit lost there... |
|
Back to top |
|
 |
NeddySeagoon Administrator


Joined: 05 Jul 2003 Posts: 55450 Location: 56N 3W
|
Posted: Fri Jan 20, 2012 8:38 pm Post subject: |
|
|
Akela NDE,
Very close ...
What do you have in your VIDEO_CARDS= in /etc/make.conf ?
It looks like its missing intel. Further, its needs to be set properly before you build Xorg. Add intel into the list now and Code: | emerge -1 xf85-video-intel | as you need the intel driver.
Code: | [ 1395.181] (==) Matched nouveau as autoconfigured driver 0
[ 1395.181] (==) Matched vesa as autoconfigured driver 1
[ 1395.181] (==) Matched fbdev as autoconfigured driver 2
[ 1395.181] (==) Assigned the driver to the xf86ConfigLayout | is a little worrying. This suggests that Xorg wants to use your nvidia chip, as nouveau would be the favorate open source driver for that chip.
The other drivers work almost anywhere.
You may need an xorg.conf file to tell Xorg to use the intel chip and the intel driver if it (incorrectly at the moment) wants to defualt to nvidia.
Modules here means Xorg modules not kernel modules. However its not that clear cut as some drivers come in two parts, an Xorg module and a Kernel module. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
 |
comprookie2000 Retired Dev


Joined: 25 Jul 2004 Posts: 925 Location: Sun City Center, Florida
|
Posted: Fri Jan 20, 2012 9:06 pm Post subject: |
|
|
@Akela NDE
Is this a motherboard with 2 graphic cards where one is the default and then the nvidia kicks in when graphics intensive, that comes with some of the newer laptops?
Or is this a motherboard with onboard graphics and you added a nvidia card to it for improved graphics? _________________ http://dev.gentoo.org/~dabbott/ |
|
Back to top |
|
 |
Akela NDE n00b

Joined: 18 Jan 2012 Posts: 14 Location: France
|
Posted: Fri Jan 20, 2012 9:22 pm Post subject: |
|
|
Well, in make.conf I had written :
Code: | VIDEO_CARDS="intel" | ... which I suppose is correct.
As for xf86-video-intel (Apparently, there is no xf85), it has already been installed when I installed xserver-xorg, but I reinstalled it.
How could I create a valid xorg.conf file if there is none? Just put one with Driver "intel" in an empty "Device" section?
Cause it did the same blank screen at reboot, after reinstalling the intel driver.
@comprookie2000: it's a motherboard with onboard graphics (Gigabyte Z68XP-UD3) to which I added an nvidia card. It's a desktop, not a laptop. |
|
Back to top |
|
 |
comprookie2000 Retired Dev


Joined: 25 Jul 2004 Posts: 925 Location: Sun City Center, Florida
|
Posted: Fri Jan 20, 2012 10:20 pm Post subject: |
|
|
Quote: |
@comprookie2000: it's a motherboard with onboard graphics (Gigabyte Z68XP-UD3) to which I added an nvidia card. It's a desktop, not a laptop.
|
Then I would use the nvidia card and disable the intel in the bios. Is the monitor connected to the nvidia card? _________________ http://dev.gentoo.org/~dabbott/ |
|
Back to top |
|
 |
Akela NDE n00b

Joined: 18 Jan 2012 Posts: 14 Location: France
|
Posted: Sat Jan 21, 2012 12:09 am Post subject: |
|
|
OK, I tried that, and it works a good bit.
No more blank screen: the systems loads normally, then classical login prompt , and I can even do startx and have an actual X server starting
I had installed twm and xterm as suggested in the handbook, so startx gave an xterm window, which is definitely an improvement over previous situations.
Well, actually there was still no xorg.conf created when emerging xorg-server, nor after update world after editing make.conf to add the VIDEO_CARDS="nvidia", so I created manually a tiny xorg.conf with just a few lines... This is probably why, while in X, I have no keyboard nor mouse! A problem which I'll try to fix tomorrow; there should be a way to have a proper xorg.conf generated. Just have to find how
(And yes, the monitor is connected to the nVidia card) |
|
Back to top |
|
 |
comprookie2000 Retired Dev


Joined: 25 Jul 2004 Posts: 925 Location: Sun City Center, Florida
|
Posted: Sat Jan 21, 2012 12:24 am Post subject: |
|
|
If you are going to use the nvidia proprietary driver, (thats what i use) :
eselect opengl set nvidia
Make sure you have this in /etc/make.conf
INPUT_DEVICES="evdev"
VIDEO_CARDS="nvidia"
then run this now and whenever you boot into a new kernel
emerge $(qlist -C -I x11-drivers/) -1av
That will rebuild the drivers
Then run nvidia-xconfig
and restart X
and one more thing
rc-update add dbus default _________________ http://dev.gentoo.org/~dabbott/ |
|
Back to top |
|
 |
Akela NDE n00b

Joined: 18 Jan 2012 Posts: 14 Location: France
|
Posted: Sat Jan 21, 2012 1:19 pm Post subject: |
|
|
OK, it works! Thanks a lot.
Now I'll continue with the install: Gnome, etc. Just hope it will be easier  |
|
Back to top |
|
 |
comprookie2000 Retired Dev


Joined: 25 Jul 2004 Posts: 925 Location: Sun City Center, Florida
|
Posted: Sat Jan 21, 2012 1:30 pm Post subject: |
|
|
Add your user to the video group for the nvidia driver.
gpasswd -a youruser_here video _________________ http://dev.gentoo.org/~dabbott/ |
|
Back to top |
|
 |
Akela NDE n00b

Joined: 18 Jan 2012 Posts: 14 Location: France
|
Posted: Sat Jan 21, 2012 1:32 pm Post subject: |
|
|
Yep, did it. |
|
Back to top |
|
 |
NeddySeagoon Administrator


Joined: 05 Jul 2003 Posts: 55450 Location: 56N 3W
|
Posted: Sat Jan 21, 2012 6:16 pm Post subject: |
|
|
Akela NDE,
The nvidia driver has a very nasty wart for the mildly paranoid like myself.
The 3D acceleration writes things to /tmp then executes them. The mildlly paranod put /tmp in tmpfs and mount it -o noexec, as nothing should ever be executed from /tmp.
Its an attack vector. Mounting /tmp with -o noexec will crash the nvidia driver (it segfaults) when it attempts 3D acceleration. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
 |
|