Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Intel 3160 wifi and Atheros Killer E220x both fail
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
ExecutorElassus
Veteran
Veteran


Joined: 11 Mar 2004
Posts: 1181
Location: Stuttgart, Germany

PostPosted: Fri Jan 08, 2016 9:20 pm    Post subject: Intel 3160 wifi and Atheros Killer E220x both fail Reply with quote

I'm trying to install gentoo onto a newly-bought (heaven help me) MSI GP72 Leopard Pro. ifconfig shows both cards are detected:

Code:
$ifconfig
enp4s0  flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
             inet6  fe80::c5bd:b36a:e3a5:bac2 prefixlen 64 scopeid 0x20<link>
             ether d8:cb:8a:82:ae:4d  txqueuelen 1000 (Ethernet)

wlp3s0   flags=4099(UP,BROADCAST,MULTICAST>  mtu 1500
             inet 192.168.1.31   netmask 255.255.255.0 broadcast 192.168.1.255
             inet6 fe80::2c2e:9211:8cee:b0c4 prefixlen 64 scopeid 0x20<link>
             ether b4:6d:83:d2:74:54 txqueuelen 1000 (Ethernet)



I skipped the bits with RX and TX, because they all show zero.

So, the drivers are loaded, but neither interface is transmitting or receiving data. ping returns nothing. So, what's going on here? What am I doing wrong?

Thanks in advance,

EE
PS- this looks a lot similar to this post, where the user somehow got the problem fixed, but didn't explain how.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43213
Location: 56N 3W

PostPosted: Sat Jan 09, 2016 1:45 pm    Post subject: Reply with quote

ExecutorElassus,

You cannot conclude that the drivers are loaded and working because the interfaces appear in ifconfig -a.
That just means that there is enough loaded for the interfaces to appear.

The wifi may need firmware and its not been provided. dmesg will tell you about that.
The wired interface is harder. Wired interfaces rarely need firmware to get them to operate but a few use firmware for bug fixes.

Lets start at the beginning.
Post the lines from lspci and/or lsusb that show these devices.

-- edit --
The kernel wiki page says your WiFi needs firmware.
There is a good selection of iwlwifi firmware in linux-firmware.

While you are messing about with firmware, be sure that iwlwifi is compiled as a loadable kernel module.
This avoids rebuilding your kernel to test different firmware.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
ExecutorElassus
Veteran
Veteran


Joined: 11 Mar 2004
Posts: 1181
Location: Stuttgart, Germany

PostPosted: Sat Jan 09, 2016 5:53 pm    Post subject: Reply with quote

Hi Neddy!

At the moment I'm still on the LiveCD. Can I load firmware into that kernel? Quite obviously, without working network interface on that laptop, I can't proceed with an install.

Or can I? If the liveCD can run fusermount, I can mount my USB stick with 64GB of storage. Is there a way to get a snapshot of a portage tree and requisite packages that I can copy over?

But for now, I'll start posting stuff from lspci.

Code:
03.00.0 Network controller: Intel Corporation Wireless 3160 (rev 83)
04.00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 13)


dmesg shows this at the end:
Code:
IPv6: ADDRCONF(NETDEV_UP): enp4s0: link is not ready
alx 0000:04:00.0: irq 32 for MSI/MSI-X
IPv6: ADDRCONF(NETDEV_UP): enp4s0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
iwlwifi 0000:03:00.0: L1 Disabled - LTR Enabled
iwlwifi 0000:03:00.0: L1 Disabled - LTR Enabled
IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready


How's that? Anything helpful (besides that the interface is not working)?

Cheers,

EE
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43213
Location: 56N 3W

PostPosted: Sat Jan 09, 2016 8:05 pm    Post subject: Reply with quote

ExecutorElassus,

The firmware is not loaded into the kernel, its loaded into the device when the kernel module loads.
If you must use the LiveCD, the firmware needs to be in /lib/firmware when the kernel module loads.
You can put the firmware there and try
Code:
modprobe -r iwlwifi
modprobe iwlwifi


I don't have a liveCD to hand but it supports a very limited range of wifi. I would have expected the liveCD to provide proper support for your wifi or none at all.
Putting the firmware in /lib/firmware on the live CD is not persistent either.

Its time you migrated to SystemRescueCD for your Gentoo installs.
It has much better WiFi support, its Gentoo based and it has an optional GUI.
It also has a script to install it onto a USB device without hogging the entire device.

Anyway, your wifi needs iwlwifi plus matching firmware.
Your wired interface needs the alx module.
Try
Code:
modprobe -r alx
modprobe alx

If there are any error messages, cut your losses and move to System Rescue CD.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
ExecutorElassus
Veteran
Veteran


Joined: 11 Mar 2004
Posts: 1181
Location: Stuttgart, Germany

PostPosted: Sat Jan 09, 2016 8:19 pm    Post subject: Reply with quote

Hi Neddy,

actually, I'm now on SystemRescueCD (the current version: 4.7.0). It has the alx module loaded, but for some reason still isn't working with the ethernet interface.

On boot, I see "No network device automatically detected" as part of the bootup scroll.

Lemme try unloading and reloading alx. Ok, unloading and reloading, dmesg reports that the interface was identified as "Qualcomm Atheros AR816x/AR817x Ethernet" and then reports that the link is "not ready."

So, if I'm on SystemRescueCD, how do I load external firmware for the interface? What might be going wrong with the Ethernet interface?

Cheers,

EE
UPDATE: 'lspci -nn' reports that this interface has the identifier 1969-e091, which is not on the list of supported devices for the alx kernel module (but then again, that page is two years old).
UPDATE2: the version of the firmware that comes with SystemRescueCD 4.7.0 is the same that I downloaded, so I'm still stumped as to why it doesn't work.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43213
Location: 56N 3W

PostPosted: Sat Jan 09, 2016 9:38 pm    Post subject: Reply with quote

ExecutorElassus,

The 4.3.3 kernel
/usr/src/linux/drivers/net/ethernet/atheros/alx/reg.h:
#define ALX_DEV_ID_AR8161                               0x1091
#define ALX_DEV_ID_E2200                                0xe091
Knows your Ethernet card.
While thats interesting, it doesn't help. Reading the source code shows that alx does not take any module parameters.
It either works or it doesn't.
Don't confuse IPv6 messages in dmesg with IPv4. The two are quite separate. You only care about IPv4.


For your wifi look in /lib/firmware.
I have
Code:
ls /lib/firmware/iwlwifi-3160-*
/lib/firmware/iwlwifi-3160-10.ucode  /lib/firmware/iwlwifi-3160-13.ucode  /lib/firmware/iwlwifi-3160-8.ucode
/lib/firmware/iwlwifi-3160-12.ucode  /lib/firmware/iwlwifi-3160-7.ucode   /lib/firmware/iwlwifi-3160-9.ucode
provided by linux-firmware.
System-rescueCD will have its own selection.

The Wiki page says you need iwlwifi-3160-ucode-25.30.13.0 for kernel 4.1 or later. I can see several issues here.
Code:
modprobe -r iwlwifi
modprobe iwlwifi
will produce some commentary at the end of dmesg.
It will talk about firmware loading or failing. It should tell the firmware filename(s) it wants.

If you have SystemRescueCD on USB, you can use the rest of the USB stick to pass files in and out.

You will need to start the interfaces after modprobing.

Going back to your first post, you said ...
Code:
wlp3s0   flags=4099(UP,BROADCAST,MULTICAST>  mtu 1500
             inet 192.168.1.31   netmask 255.255.255.0 broadcast 192.168.1.255

That looks like it worked. The interface has an IP address. How did that happen?
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
ExecutorElassus
Veteran
Veteran


Joined: 11 Mar 2004
Posts: 1181
Location: Stuttgart, Germany

PostPosted: Sat Jan 09, 2016 9:45 pm    Post subject: Reply with quote

Hi Neddy,

I specified the IP addresses with net-setup. When I tried with dhcpcd, it timed out. SystemRescueCD runs a 3.18 kernel, for which the iwlwifi-3160-10.ucode is the appropriate firmware, and is already in SRCD's /lib/firmware directory (though I was also able to copy the same file from the website over from a USB stick).

I'll check back tomorrow and see what IPv4 messages I get (if any). So far, all I see is that the device is "not ready," with no messages about modprobe failing.

Cheers,

EE
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43213
Location: 56N 3W

PostPosted: Sat Jan 09, 2016 10:09 pm    Post subject: Reply with quote

ExecutorElassus,

The System Rescue CD change log says
Code:
4.7.0) 2016-01-01:

    Standard kernels: Long-Term-Supported linux-3.18.25 (rescue32 + rescue64)
    Alternative kernels: Long-Term-Supported linux-4.1.15 (altker32 + altker64)

Try the Alternative kernel.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
ExecutorElassus
Veteran
Veteran


Joined: 11 Mar 2004
Posts: 1181
Location: Stuttgart, Germany

PostPosted: Sun Jan 10, 2016 5:32 am    Post subject: Reply with quote

HI Neddy,

tried the alternative kernel. Unloading and reloading alx and iwlwifi. Both of them return messages in dmesg that the "link is not ready." I don't see any messages at all for IPv4. Running dhcpcd on them still ends in a timeout.

So, both of them, for whatever reason, still aren't working. :(

Cheers,

EE
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43213
Location: 56N 3W

PostPosted: Sun Jan 10, 2016 11:19 am    Post subject: Reply with quote

ExecutorElassus,

Using the Alt kernel, put your dmesg onto your usb stick and post it on a pastebin site.
Link not ready covers a multitude of things.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
ExecutorElassus
Veteran
Veteran


Joined: 11 Mar 2004
Posts: 1181
Location: Stuttgart, Germany

PostPosted: Sun Jan 10, 2016 11:42 am    Post subject: Reply with quote

Hi Neddy,

here's the output of dmesg posted to a pastebin.

Enjoy?

Thanks for the help,

EE
UPDATE: I read up a bit, and found that this revision number needs the iwlwifi-3160-13.ucode firmware, which SRCD-4.7.0 does not yet have. I downloaded it from intel, copied it over from the USB stick, and then did reloaded the iwlwifi module with modprobe. The new pastebin is here.
UPDATE2: WHAAAAAAT. I tried, in a last desperate act, swapping out the FREAKING ETHERNET CABLE. Suddenly, dhcpcd works for enp4s0. I have pings to gentoo.org and everything. Man, of all the stupid things to break in a home setup, that's a fascinating one.

Okay, so now I at least have a wired connection. I can proceed with the installation to get to a working setup on ethernet. Still, any idea why the wifi won't work? See anything useful? I'm going to be travelling tomorrow, so I'd still like to have wifi working if at all possible.

Anyway, protip: if all else fails, swap out the cable.


Last edited by ExecutorElassus on Sun Jan 10, 2016 12:35 pm; edited 1 time in total
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43213
Location: 56N 3W

PostPosted: Sun Jan 10, 2016 12:21 pm    Post subject: Reply with quote

ExecutorElassus

First, wired.
Code:
[   45.386107] alx 0000:04:00.0 eth0: Qualcomm Atheros AR816x/AR817x Ethernet [d8:cb:8a:83:ae:4d]
[   45.388761] alx 0000:04:00.0 enp4s0: renamed from eth0


Code:
[  211.488470] alx 0000:04:00.0 eth0: Qualcomm Atheros AR816x/AR817x Ethernet [d8:cb:8a:83:ae:4d]
[  211.492788] alx 0000:04:00.0 enp4s0: renamed from eth0


That looks good. That's the autoload and your modprobe.
With a known good ethernet cable connected, try
Code:
dhcpcd enp4s0

You will either get error messages or your wired interface configured.

Now Wifi.
Code:
[   46.670120] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-3160-13.ucode failed with error -2

Thats a Go to Jail, Go directly to jail, Do not pass Go, Do not collect 200 <insert local currency here> sort of error.
You need to put the file iwlwifi-3160-13.ucode into /lib/firmware/ to get the wifi to work but
Code:
[   50.633914] iwlwifi 0000:03:00.0: loaded firmware version 25.15.12.0 op_mode iwlmvm
it found some firmware.
I don't know if the wifi needs both firmware files or not. Try it.

It all looks promising but there is no attempt to associate or authenticate.
To make that work you will need a wpa_supplicant.conf file, so the Wifi can connect to your AP.

Code:
dhcpcd wlp3s0
will attempt to bring up the Wifi. You will get progress messages in dmesg but until wpa_supplicant.conf is correct, authentication will fail.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
DONAHUE
Watchman
Watchman


Joined: 09 Dec 2006
Posts: 7552
Location: Goose Creek SC

PostPosted: Sun Jan 10, 2016 4:54 pm    Post subject: Reply with quote

may have better luck by running startx after booting the SRCD alternative kernel and then using the networkmanager icon in the lower right of the xfce4 desktop.
or
/etc/init.d/NetworkManager restart in the CLI
_________________
Defund the FCC.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43213
Location: 56N 3W

PostPosted: Sun Jan 10, 2016 5:29 pm    Post subject: Reply with quote

ExecutorElassus,

NeddySeagoon wrote:
... known good ethernet cable connected ...
Been there, done that. More than once. :(

The
Code:
0000:03:00.0: Direct firmware load for iwlwifi-3160-13.ucode failed with error -2
is gone. That has to be good.
There is no attempt to associate or authenticate in dmesg. I guess you have a switch or keyboard combination that turns off WiFi and its off by default?

Anyway, now you have wired you can continue with your install.
WiFi will be a pain until your install is complete as you will need to recreate wpa_supplicant.conf every time you reboot. You can save it on your USB stick.

Do your install over wired and fix wireless once you build your own kernel.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
ExecutorElassus
Veteran
Veteran


Joined: 11 Mar 2004
Posts: 1181
Location: Stuttgart, Germany

PostPosted: Sun Jan 10, 2016 6:03 pm    Post subject: Reply with quote

roger, am doing. Thanks for the help. BTW, I'm still following your guide for setting up an initramfs/initrd to boot, though I have less reason to do so (everything but /home is on an SSD, and I forgot to set it up to be encrypted before I started installing the portage tree and everything, and now I'm too tired to go back). I suppose it'll come in handy for later when I want HOTT framebuffer graphics or whatever.

Anyway, I'll get as far as I can with the install on wired, then get back to you when I have a working, rebootable system.

Thanks, as always, for the help. You are a gentleman and a scholar,

EE
Back to top
View user's profile Send private message
ExecutorElassus
Veteran
Veteran


Joined: 11 Mar 2004
Posts: 1181
Location: Stuttgart, Germany

PostPosted: Tue Jan 12, 2016 10:10 pm    Post subject: Reply with quote

okay, system is installed and in a rebootable state (ie, I can get to a login without a CD). I built the iwlwifi module into the kernel, and it isn't showing up. Should I have built it instead as a loadable module? I'll look into the guide/sample .conf file for wpa_supplicant tomorrow (just got off a long train ride; too tired for now).

Totally OT (maybe I should start another thread?): I'd like /home to be an encrypted volume, to mount at boot time (thus requiring a password). The guides I see are for dm-crypt using LUKS, but are all a couple years old (and some are badly written). Is there a good guide for achieving what I want? I'd like to wait to log in with a regular user until I can get the /home volume properly encrypted.

Cheers,

EE
UPDATE: I found this guide, which is surprisingly straightforward and clear. Does that still look current to you? Hope so! I'm filling the partition with random data overnight. I'll check back in the morning.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43213
Location: 56N 3W

PostPosted: Tue Jan 12, 2016 11:24 pm    Post subject: Reply with quote

ExecutorElassus,

With the iwlwifi module built into the kernel, you must also build in its firmware.
That's OK after it works. Its easier to fix if you make iwlwifi until that time.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
ExecutorElassus
Veteran
Veteran


Joined: 11 Mar 2004
Posts: 1181
Location: Stuttgart, Germany

PostPosted: Wed Jan 13, 2016 8:45 pm    Post subject: Reply with quote

Sigh. Also OT (but I'm not to a WM yet!), I can't get xorg to start. Here's the log:

Code:
[  2268.340]
X.Org X Server 1.17.4
Release Date: 2015-10-28
[  2268.340] X Protocol Version 11, Revision 0
[  2268.340] Build Operating System: Linux 4.3.3-gentoo x86_64 Gentoo
[  2268.340] Current Operating System: Linux choriac 4.3.3-gentoo #1 SMP Sun Jan 10 19:22:57 CET 2016 x86_64
[  2268.340] Kernel command line: BOOT_IMAGE=/vmlinuz-4.3.3-gentoo root=/dev/sdb4 ro
[  2268.340] Build Date: 11 January 2016  02:29:09PM
[  2268.340] 
[  2268.340] Current version of pixman: 0.33.6
[  2268.340]    Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
[  2268.340] Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  2268.340] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Jan 14 05:38:42 2016
[  2268.340] (==) Using config file: "/etc/X11/xorg.conf"
[  2268.340] (==) Using config directory: "/etc/X11/xorg.conf.d"
[  2268.340] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  2268.340] (==) No Layout section.  Using the first Screen section.
[  2268.340] (==) No screen section available. Using defaults.
[  2268.340] (**) |-->Screen "Default Screen Section" (0)
[  2268.340] (**) |   |-->Monitor "<default monitor>"
[  2268.341] (==) No device specified for screen "Default Screen Section".
        Using the first device section listed.
[  2268.341] (**) |   |-->Device "Nvidia Card"
[  2268.341] (==) No monitor specified for screen "Default Screen Section".
        Using a default monitor configuration.
[  2268.341] (==) Automatically adding devices
[  2268.341] (==) Automatically enabling devices
[  2268.341] (==) Automatically adding GPU devices
[  2268.341] (WW) The directory "/usr/share/fonts/misc/" does not exist.
[  2268.341]    Entry deleted from font path.
[  2268.341] (WW) The directory "/usr/share/fonts/TTF/" does not exist.
[  2268.341]    Entry deleted from font path.
[  2268.341] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[  2268.341]    Entry deleted from font path.
[  2268.341] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[  2268.341]    Entry deleted from font path.
[  2268.341] (WW) The directory "/usr/share/fonts/100dpi/" does not exist.
[  2268.341]    Entry deleted from font path.
[  2268.341] (WW) The directory "/usr/share/fonts/75dpi/" does not exist.
[  2268.341]    Entry deleted from font path.
[  2268.341] (==) FontPath set to:
       
[  2268.341] (**) ModulePath set to "/usr/lib64/opengl/nvidia,/usr/lib64/xorg/modules"
[  2268.341] (II) The server relies on udev to provide the list of input devices.
        If no devices become available, reconfigure udev or disable AutoAddDevices.
[  2268.341] (II) Loader magic: 0x7fbb80
[  2268.341] (II) Module ABI versions:
[  2268.341]    X.Org ANSI C Emulation: 0.4
[  2268.341]    X.Org Video Driver: 19.0
[  2268.341]    X.Org XInput driver : 21.0
[  2268.341]    X.Org Server Extension : 9.0
[  2268.342] (--) PCI:*(0:0:2:0) 8086:0416:1462:114d rev 6, Mem @ 0xa1400000/4194304, 0xb0000000/268435456, I/O @ 0x00005000/64
[  2268.342] (--) PCI: (0:1:0:0) 10de:1347:1462:114d rev 162, Mem @ 0xa0000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x00004000/128, BIOS @ 0x????????/524288
[  2268.342] (II) LoadModule: "dbe"
[  2268.342] (II) Module "dbe" already built-in
[  2268.342] (II) LoadModule: "nvidia"
[  2268.342] (II) Loading /usr/lib64/xorg/modules/drivers/nvidia_drv.so
[  2268.342] (II) Module nvidia: vendor="NVIDIA Corporation"
[  2268.342]    compiled for 4.0.2, module version = 1.0.0
[  2268.342]    Module class: X.Org Video Driver
[  2268.342] (II) NVIDIA dlloader X Driver  358.16  Mon Nov 16 18:32:40 PST 2015
[  2268.342] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[  2268.342] (++) using VT number 7

[  2268.344] (EE) No devices detected.
[  2268.344] (EE)
Fatal server error:
[  2268.344] (EE) no screens found(EE)
[  2268.344] (EE)
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
[  2268.344] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[  2268.344] (EE)


Do I need to go into xorg.conf and put in a section for my screen, or is this some other error? Everything else looks fine.

I'll look at the settings for iwlwifi (ie, whether it's a module or not) in the meantime.

Cheers,

EE
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43213
Location: 56N 3W

PostPosted: Wed Jan 13, 2016 8:56 pm    Post subject: Reply with quote

ExecutorElassus,

Code:
[  2268.342] (--) PCI:*(0:0:2:0) 8086:0416:1462:114d rev 6, Mem @ 0xa1400000/4194304, 0xb0000000/268435456, I/O @ 0x00005000/64
[  2268.342] (--) PCI: (0:1:0:0) 10de:1347:1462:114d rev 162, Mem @ 0xa0000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @


Is that an Optimus system?
If so, you need to make the Intel graphics work first.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
ExecutorElassus
Veteran
Veteran


Joined: 11 Mar 2004
Posts: 1181
Location: Stuttgart, Germany

PostPosted: Wed Jan 13, 2016 9:18 pm    Post subject: Reply with quote

lspci shows:

Code:
00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06)
and
Code:
01:00.0 3D controller [0302]: NVIDIA Corporation GM108M [GeForce 940M] [10de:1347] (rev a2)
, so, yes?

ohgod, and here I thought nvidia-based laptop wer more or less stable.

OK, now I'm reading the wiki. I'll report back tomorrow.

Cheers,

EE
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43213
Location: 56N 3W

PostPosted: Wed Jan 13, 2016 9:26 pm    Post subject: Reply with quote

ExecutorElassus,

Not always.

Optimus is a grahics system and a half.
Some systems really do have two complete graphics systems.

Optimus provides a conventional Intel Graphics system. It can both draw in the pixel buffer and read the pixel buffer out to the display surface.
The nvidia graphics can only draw in the pixel buffer. You need to use the intel graphics to refresh the display at all times.

You need to read the small print to see which you have.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
ExecutorElassus
Veteran
Veteran


Joined: 11 Mar 2004
Posts: 1181
Location: Stuttgart, Germany

PostPosted: Thu Jan 14, 2016 3:25 pm    Post subject: Reply with quote

btw, I copied the firmware into my new drive, re-loaded iwlwifi, and lo! the wifi now works. Huzzah!

So now that both interfaces are working, I suppose either I close this thread as [SOLVED] and open another for getting my graphics working, or re-name this to some general install topic or whatever.

Anyway, I'm still figuring out which video setup I have. The spec page doesn't mention Optimus, just that there's an integrated graphics set. I'll keep digging.

Is Bumblebee any good? I see horror stories from 2013, and then a pretty straightforward guide from this year. Not sure which to believe.

Thanks again for the help.

Cheers,

EE
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum