public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joseph <syscon780@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: kernel 3.8 and external drivers
Date: Mon, 11 Mar 2013 12:13:08 -0600	[thread overview]
Message-ID: <20130311181308.GC1672@syscon7.inet> (raw)
In-Reply-To: <khj5a2$dlt$1@ger.gmane.org>

On 03/11/13 01:34, Nikos Chantziaras wrote:
[snip]
>>>>> config R8169
>>>>>          tristate "Realtek 8169 gigabit ethernet support"
>>>>>
>>>>>           Say Y here if you have a Realtek 8169 PCI Gigabit
>>>>> Ethernet adapter.
>>>>>
>>>>>            To compile this driver as a module, choose M here: the
>>>>> module will be called r8169.  This is recommended.
>>>>>
>>>>
>>>> oh great, so I actually mixed it up…
>>>> the 8169 is in the Kernel yes, but what i need is the 8168
>>>
>>> The in-kernel drive (supposedly) supports 8168:
>>>
>>> r8169.c: RealTek 8169/8168/8101 ethernet driver.
>>
>> Thanks for encouraging me, the in-kernel driver actually works.
>
>Note that you also need to emerge sys-kernel/linux-firmware.  The driver
>will work without it, but the ethernet connection can hang after an hour
>or so.
>
>You can verify whether you need to install the firmware or not by
>inspecting the kernel log:
>
>   dmesg | grep -i firmware
>
>This should show the kernel trying to load the firmware for your R8168
>chip but failing.

I had my share of problems with recent kernels and Realtek 8168 so I went and bought and internal network card:
Intel Corporation 82574L Gigabit Network Connection card.

I did know that I'm suppose to install "sys-kernel/linux-firmware"
I just did (just in case) but running: dmesg | grep -i firmware

doesn't show that kernel is trying to load anything.

-- 
Joseph


  reply	other threads:[~2013-03-11 18:12 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-10 18:28 [gentoo-user] kernel 3.8 and external drivers Daniel Wagener
2013-03-10 18:36 ` Canek Peláez Valdés
2013-03-10 18:42   ` Daniel Wagener
2013-03-10 18:49     ` Canek Peláez Valdés
2013-03-10 19:04       ` Daniel Wagener
     [not found]       ` <20130310190458.A041FE07A7@pigeon.gentoo.org>
2013-03-10 23:34         ` [gentoo-user] " Nikos Chantziaras
2013-03-11 18:13           ` Joseph [this message]
2013-03-10 19:57 ` [gentoo-user] " Alan McKinnon
2013-03-10 20:53 ` Volker Armin Hemmann
2013-03-10 23:05   ` Daniel Wagener
     [not found]   ` <20130310230521.C5A06E07CC@pigeon.gentoo.org>
2013-03-11 13:00     ` Yuri K. Shatroff
2013-03-11 17:47       ` Volker Armin Hemmann
2013-03-12  7:33         ` Yuri K. Shatroff
2013-03-12  8:46           ` Alexander Schwarz
2013-03-12 10:01             ` Yuri K. Shatroff
2013-03-12 10:30               ` Alan McKinnon
2013-03-12 10:44                 ` Neil Bothwick
2013-03-12 11:51                   ` Yuri K. Shatroff
2013-03-12 12:58                     ` Neil Bothwick
2013-03-12 18:09                     ` Volker Armin Hemmann
2013-03-13  6:50                       ` Yuri K. Shatroff
2013-03-12 11:35                 ` Yuri K. Shatroff
2013-03-12 11:51                   ` Dale
2013-03-12 12:13                     ` Yuri K. Shatroff
2013-03-12 12:28                       ` Alan McKinnon
2013-03-12 11:51                   ` Alan McKinnon
2013-03-12 10:43               ` Alexander Schwarz
     [not found]   ` <20130310230521.A4DBBE07C8@pigeon.gentoo.org>
2013-03-11 17:49     ` Volker Armin Hemmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130311181308.GC1672@syscon7.inet \
    --to=syscon780@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox