I will pastebin the contents of my kernel .config file as soon as possible and drop the link here.

that is why I say I am more and more amazed at Crux, as it is not auto-configured. up to now I have run Arch and Slack but Crux is even more challenging and makes you study more and more. I hope one day I evolve and be able to contribute.:)

concerning the network connection I think I did everything I should to make it be established..what makes me think about it is that the first time I installed without making any changes on the kernel and just editing /etc/rc.d/net with dhcp the connection was established immediately with the ethernet controller being recognized with no problem and not demanding any other procedure. Maybe I should make a fresh install and after that make the changes little by little.:)

2014-12-31 14:42 GMT-02:00 Don Cupp <doncuppjr@yahoo.com>:
I believe, that by default, you must create your network connection after a fresh install of crux. It's not auto-configured for you like most distro's, nor should it be really. Follow the yellow brick road, follow follow follow, follow the yellow brick road.:) 



On Wednesday, December 31, 2014 8:36 AM, James Trimbee <james.trimbee@gmail.com> wrote:



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.

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





--
       Cezar Rangel
cezar.rangel@gmail.com