Bryan, I changed and chose "m" instead of  "y" and there has been a little progress as after the change the output of #lspci -v concerning the ethernet controller shows the   Kernel modules: e1000e.

however, there is not a kernel drive in use yet

I have tried #modprobe e1000e and the result was the same a got before #modprobe:ERROR: could not insert 'e1000e' unknown symbol in mocule, or unknown parameter (see dmesg)

2015-01-01 13:05 GMT-02:00 Bryan Bennett <bbenne10@gmail.com>:

Many network drivers require being compiled as a module and not built directly into the kernel. Have you tried choosing "m" instead of "y"?


On Thu, Jan 1, 2015, 9:41 AM Cezar Rangel <cezar.rangel@gmail.com> wrote:
this is another pastebin.

this is the one concerning the  #lspci -v output I ran to check the driver in use.

In fact, I have made a test: I ran the same command in 2 partitions on which the same ethernet controller is in use.

If I am not mistaken, the ethernet controller on the partition on which crux 3.1 is installed is missing the driver e1000e as it has not been shown on the output. 

nevertheless, I shall remark that when I ran #make menuconfig I used the (/) tool to find out where the driver e1000e was in order to mark it as built in (y), I think I have made
a mistake...


2014-12-31 14:13 GMT-02:00 James Trimbee <james.trimbee@gmail.com>:


On Dec 31, 2014 11:06 AM, "Cezar Rangel" <cezar.rangel@gmail.com> wrote:
>
> I have run 'make menuconfig' and I have configured everything as it has been told.
> In the end, everything seemed perfect, no error message, no kernel panic when I rebooted.
> The graphic mode was ok.
>
> However no connection. I have edited /etc/rc.d/net with DHCP. However, when I run #ping 8.8.8.8 the result is that the network is unreachable
> either with the intel card or with the RTL8169.
>
> If I run #ip link show there is only lo, no device corresponding to an ethernet controller is recognized but if I run #lspci the intel controller is there:Ethernet controller: Intel Corporation 82574L Gigabit Network Connection.
>
> I shall remark that when I first installed Crux 3.1 I made no changes concerning the kernel (linux-3.12.24) contained on the installation disc
> and I had no problem with the network. the ethernet controller  was recognized as enp3s6 when I first rebooted and I could connect to the internet. 
>
>
>
>
>
>

It is still missing drivers. 'lspci' will enumerate devices it polls - it doesn't mean they have drivers loaded. The missing items when you run ip suggests that.

The Intel hardware in particular should be very straightforward. I'll take a look at the kernel config items when I get a moment.

In the meantime please pastebin the contents of your kernel .config file and drop the link here.




--
       Cezar Rangel
_______________________________________________
CRUX mailing list
CRUX@lists.crux.nu
http://lists.crux.nu/mailman/listinfo/crux



--
       Cezar Rangel
cezar.rangel@gmail.com