Re: after running nvidia-xconfig the mouse and the keyboard cannot be used in graphic mode
I thank you all for the attention and kindness towards my first questions after installing Crux 3.1. After the answers I got, I have decided to reinstall it, even though I must remark that my first installation did not result kernel panic. The only problem came after the nvidia installation. Nevertheless I have tried now with the new kernel 3.14.27. Everything was perfect except surprisingly for the ethernet controller that has not been recognized by the system. (Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8169 PCI Gigabit Ethernet Controller) it is the same controller that with the kernel that comes with the iso (3.12.24) was recognized by the system...marybe kernel 3.14.27 was not a good choice for Crux 3.1? I apologize for my newbie questions concerning the great Crux which documentation I am still studying a lot. I take the opportunity to wish for all of the list a wonderful 2015 with much health and achievements for Crux. 2014-12-28 20:06 GMT-02:00 Don Cupp <doncuppjr@yahoo.com>:
It does not appear that the Xorg that produced that log is using your xorg.conf file. It appears to be trying to use the nouveau driver for xorg, but AIGLX is not happy. Did you update mesa3d? Do you have the nouveau, drm, ipv6 and kernel modesetting drivers available at the time the udev runs? Why is your Xorg so old? Did glamoregl even work in 1.15.x?
On Sunday, December 28, 2014 10:29 AM, Donald A. Cupp Jr. < doncuppjr@yahoo.com> wrote:
Nice, but can you post the log?
Sent from my Verizon Wireless 4G LTE smartphone
<br><br>-------- Original message --------<br>From: Cezar Rangel < cezar.rangel@gmail.com> <br>Date: 12/28/2014 10:09 AM (GMT-08:00) <br>To: Fredrik Rinnestam <fredrik@rinnestam.se> <br>Cc: crux@lists.crux.nu <br>Subject: Re: after running nvidia-xconfig the mouse and the keyboard cannot be used in graphic mode <br><br>
thanks. you are right. this the xorg.conf:
# nvidia-xconfig: X configuration file generated by nvidia-xconfig # nvidia-xconfig: version 340.65 (buildmeister@swio-display-x64-rhel04-11) Tue Dec 2 09:59:38 PST 2014
Section "ServerLayout" Identifier "Layout0" Screen "Screen0" 0 0 InputDevice "Keyboard0" "CoreKeyboard" InputDevice "Mouse0" "CorePointer" EndSection
Section "Files" EndSection
Section "InputDevice"
# generated from default Identifier "Mouse0" Driver "mouse" Option "Protocol" "IMPS/2" Option "Device" "/dev/psaux" Option "Emulate3Buttons" "no" Option "ZAxisMapping" "4 5" EndSection
Section "InputDevice"
# generated from default Identifier "Keyboard0" Driver "kbd" Option "XkbRules" "xorg" Option "XkbModel" "abnt2" Option "XkbLayout" "br" EndSection
Section "Monitor" Identifier "Monitor0" VendorName "Unknown" ModelName "Unknown" HorizSync 28.0 - 33.0 VertRefresh 43.0 - 72.0 Option "DPMS" EndSection
Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" EndSection
Section "Screen" Identifier "Screen0" Device "Device0" Monitor "Monitor0" DefaultDepth 24 SubSection "Display" Depth 24 EndSubSection EndSection
2014-12-28 14:05 GMT-02:00 Fredrik Rinnestam <fredrik@rinnestam.se>:
On Sat, Dec 27, 2014 at 09:09:25PM -0200, Cezar Rangel wrote:
Hi everyone. It is my first time with Crux 3.1 and after installing it I managed not to get a kernel panic. That was great and I am amazed at Crux 3.1 still studying it a lot. I have installed nvidia to improve the graphic mode. after that, when I run $startx I managed to run openbox but the mouse and the keyboard (both usb) cannot be used. also, there is an error message before startx when I am still in text mode which says: "error opening usb device 'descriptors' file. when I run lsub the result is: lsusb Bus 002 Device 002: ID 04e8:61b6 Samsung Electronics Co., Ltd M3 Portable Hard Drive 1TB Bus 002 Device 003: ID 04e8:61b6 Samsung Electronics Co., Ltd M3 Portable Hard Drive 1TB Bus 003 Device 002: ID 04e8:344f Samsung Electronics Co., Ltd SCX-3400 Series Bus 003 Device 005: ID 046d:0825 Logitech, Inc. Webcam C270 Bus 005 Device 002: ID 045e:00b0 Microsoft Corp. Digital Media Pro Keyboard Bus 006 Device 002: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub I remark that on graphic mode both mouse and keyboard function perfectely well. the problem begins after startx when I boot openbox and the mouse and the keyboard collapse. I would thank so much if a solution could be found cezar
Please post your xorg log. Without it it's all just (poor) guesswork.
--
Fredrik Rinnestam _______________________________________________ CRUX mailing list CRUX@lists.crux.nu http://lists.crux.nu/mailman/listinfo/crux
-- * Cezar Rangel* *cezar.rangel@gmail.com <cezar.rangel@gmail.com>*
thanks. you are right. this the xorg.conf:
# nvidia-xconfig: X configuration file generated by nvidia-xconfig # nvidia-xconfig: version 340.65 ( buildmeister@swio-display-x64-rhel04-11) Tue Dec 2 09:59:38 PST 2014
Section "ServerLayout" Identifier "Layout0" Screen "Screen0" 0 0 InputDevice "Keyboard0" "CoreKeyboard" InputDevice "Mouse0" "CorePointer" EndSection
Section "Files" EndSection
Section "InputDevice"
# generated from default Identifier "Mouse0" Driver "mouse" Option "Protocol" "IMPS/2" Option "Device" "/dev/psaux" Option "Emulate3Buttons" "no" Option "ZAxisMapping" "4 5" EndSection
Section "InputDevice"
# generated from default Identifier "Keyboard0" Driver "kbd" Option "XkbRules" "xorg" Option "XkbModel" "abnt2"
Option "XkbLayout" "br" EndSection
Section "Monitor" Identifier "Monitor0" VendorName "Unknown" ModelName "Unknown" HorizSync 28.0 - 33.0 VertRefresh 43.0 - 72.0 Option "DPMS" EndSection
Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" EndSection
Section "Screen" Identifier "Screen0" Device "Device0" Monitor "Monitor0" DefaultDepth 24 SubSection "Display" Depth 24 EndSubSection EndSection
2014-12-28 14:05 GMT-02:00 Fredrik Rinnestam <fredrik@rinnestam.se>: On Sat, Dec 27, 2014 at 09:09:25PM -0200, Cezar Rangel wrote:
Hi everyone. It is my first time with Crux 3.1 and after installing it I managed not to get a kernel panic. That was great and I am amazed at Crux 3.1 still studying it a lot. I have installed nvidia to improve the graphic mode. after that, when I run $startx I managed to run openbox but the mouse and the keyboard (both usb) cannot be used. also, there is an error message before startx when I am still in text mode which says: "error opening usb device 'descriptors' file. when I run lsub the result is: lsusb Bus 002 Device 002: ID 04e8:61b6 Samsung Electronics Co., Ltd M3 Portable Hard Drive 1TB Bus 002 Device 003: ID 04e8:61b6 Samsung Electronics Co., Ltd M3 Portable Hard Drive 1TB Bus 003 Device 002: ID 04e8:344f Samsung Electronics Co., Ltd SCX-3400 Series Bus 003 Device 005: ID 046d:0825 Logitech, Inc. Webcam C270 Bus 005 Device 002: ID 045e:00b0 Microsoft Corp. Digital Media Pro Keyboard Bus 006 Device 002: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub I remark that on graphic mode both mouse and keyboard function perfectely well. the problem begins after startx when I boot openbox and the mouse and the keyboard collapse. I would thank so much if a solution could be found cezar
Please post your xorg log. Without it it's all just (poor) guesswork.
--
Fredrik Rinnestam _______________________________________________ CRUX mailing list CRUX@lists.crux.nu http://lists.crux.nu/mailman/listinfo/crux
-- Cezar Rangel cezar.rangel@gmail.com
-- * Cezar Rangel* *cezar.rangel@gmail.com <cezar.rangel@gmail.com>*
On 29 December 2014 at 20:17, Cezar Rangel <cezar.rangel@gmail.com> wrote:
I thank you all for the attention and kindness towards my first questions after installing Crux 3.1. After the answers I got, I have decided to reinstall it, even though I must remark that my first installation did not result kernel panic. The only problem came after the nvidia installation.
Nevertheless I have tried now with the new kernel 3.14.27. Everything was perfect except surprisingly for the ethernet controller that has not been recognized by the system. (Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8169 PCI Gigabit Ethernet Controller) it is the same controller that with the kernel that comes with the iso (3.12.24) was recognized by the system...marybe kernel 3.14.27 was not a good choice for Crux 3.1? I apologize for my newbie questions concerning the great Crux which documentation I am still studying a lot.
I take the opportunity to wish for all of the list a wonderful 2015 with much health and achievements for Crux.
You're just missing the module or built-in driver. Easiest way to check is boot the livecd and do lspci -K. This will list detected hardware on the PCI bus and if applicable the drivers. Note the RTL8169 name, probably 'r8169'. When you run 'make menuconfig' to setup your kernel search for the string using the '/' key and just select it as built-in [y] or module [m]. Recompile the kernel and you should be good to go.
*"Easiest way to check is boot the live cd and do lspci -K. This willlist detected hardware on the PCI bus and if applicable the drivers.Note the RTL8169 name, probably 'r8169'."* 1) the result of #lspci K was: *02:00.0 Ethernet Controller: Intel Corporation 82574L Gigabit Network connection* *....................................................................................................................* *kernel modules:e1000e* 2)after that I did a test with: #modprobe e1000e that returned: *modprobe:ERROR: could not insert 'e1000e' unknown symbol in mocule, or unknown parameter (see dmesg)* I still have to run 'make menuconfig' as I was told to do but I do not understand this *modprobe ERROR *as it is not he first time I do #modprobe and this error message comes as result. 3)I must explain that I have changed the ethernet controller just to check it would be recognized but it wasn't either, like the other ethernet controller 2014-12-30 1:06 GMT-02:00 James Trimbee <james.trimbee@gmail.com>:
On 29 December 2014 at 20:17, Cezar Rangel <cezar.rangel@gmail.com> wrote:
I thank you all for the attention and kindness towards my first
questions after installing Crux 3.1. After the answers I got, I have decided to reinstall it, even though I must remark that my first installation did not result kernel panic. The only problem came after the nvidia installation.
Nevertheless I have tried now with the new kernel 3.14.27. Everything
was perfect except surprisingly for the ethernet controller that has not been recognized by the system.
(Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8169 PCI Gigabit Ethernet Controller) it is the same controller that with the kernel that comes with the iso (3.12.24) was recognized by the system...marybe kernel 3.14.27 was not a good choice for Crux 3.1? I apologize for my newbie questions concerning the great Crux which documentation I am still studying a lot.
I take the opportunity to wish for all of the list a wonderful 2015 with much health and achievements for Crux.
You're just missing the module or built-in driver.
Easiest way to check is boot the livecd and do lspci -K. This will list detected hardware on the PCI bus and if applicable the drivers. Note the RTL8169 name, probably 'r8169'.
When you run 'make menuconfig' to setup your kernel search for the string using the '/' key and just select it as built-in [y] or module [m]. Recompile the kernel and you should be good to go.
-- * Cezar Rangel* *cezar.rangel@gmail.com <cezar.rangel@gmail.com>*
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. 2014-12-30 1:06 GMT-02:00 James Trimbee <james.trimbee@gmail.com>:
On 29 December 2014 at 20:17, Cezar Rangel <cezar.rangel@gmail.com> wrote:
I thank you all for the attention and kindness towards my first
questions after installing Crux 3.1. After the answers I got, I have decided to reinstall it, even though I must remark that my first installation did not result kernel panic. The only problem came after the nvidia installation.
Nevertheless I have tried now with the new kernel 3.14.27. Everything
was perfect except surprisingly for the ethernet controller that has not been recognized by the system.
(Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8169 PCI Gigabit Ethernet Controller) it is the same controller that with the kernel that comes with the iso (3.12.24) was recognized by the system...marybe kernel 3.14.27 was not a good choice for Crux 3.1? I apologize for my newbie questions concerning the great Crux which documentation I am still studying a lot.
I take the opportunity to wish for all of the list a wonderful 2015 with much health and achievements for Crux.
You're just missing the module or built-in driver.
Easiest way to check is boot the livecd and do lspci -K. This will list detected hardware on the PCI bus and if applicable the drivers. Note the RTL8169 name, probably 'r8169'.
When you run 'make menuconfig' to setup your kernel search for the string using the '/' key and just select it as built-in [y] or module [m]. Recompile the kernel and you should be good to go.
-- * Cezar Rangel* *cezar.rangel@gmail.com <cezar.rangel@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.
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.:) http://crux.nu/Main/Handbook3-1#ntoc53http://crux.nu/Main/Handbook3-1 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
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.:)
http://crux.nu/Main/Handbook3-1#ntoc53 http://crux.nu/Main/Handbook3-1
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 <cezar.rangel@gmail.com>*
here is the pastebin link of the .config. thanks for all the attention. http://pastebin.com/aHnu6RFM 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* *cezar.rangel@gmail.com <cezar.rangel@gmail.com>*
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... http://pastebin.com/3uujjMXN 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* *cezar.rangel@gmail.com <cezar.rangel@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
In the end, everything seemed perfect, no error message, no kernel
been told. 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* *cezar.rangel@gmail.com <cezar.rangel@gmail.com>* _______________________________________________ CRUX mailing list CRUX@lists.crux.nu http://lists.crux.nu/mailman/listinfo/crux
no Bryan I have not. I have to check again among the many options of #make menuconfig where the e1000e driver is located and choose it as "m". thanks. 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
In the end, everything seemed perfect, no error message, no kernel
has been told. 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* *cezar.rangel@gmail.com <cezar.rangel@gmail.com>* _______________________________________________ CRUX mailing list CRUX@lists.crux.nu http://lists.crux.nu/mailman/listinfo/crux
-- * Cezar Rangel* *cezar.rangel@gmail.com <cezar.rangel@gmail.com>*
however as far as I can remember when I did it before (use the / to locate the driver) the output showed it should be (y). I may be mistaken, for sure. I will test it and drop the result here. 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
In the end, everything seemed perfect, no error message, no kernel
has been told. 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* *cezar.rangel@gmail.com <cezar.rangel@gmail.com>* _______________________________________________ CRUX mailing list CRUX@lists.crux.nu http://lists.crux.nu/mailman/listinfo/crux
-- * Cezar Rangel* *cezar.rangel@gmail.com <cezar.rangel@gmail.com>*
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
In the end, everything seemed perfect, no error message, no kernel
has been told. 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* *cezar.rangel@gmail.com <cezar.rangel@gmail.com>* _______________________________________________ CRUX mailing list CRUX@lists.crux.nu http://lists.crux.nu/mailman/listinfo/crux
-- * Cezar Rangel* *cezar.rangel@gmail.com <cezar.rangel@gmail.com>*
On 1/1/2015 12:49, Cezar Rangel wrote:
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)
First, for clarification: For the vast majority of network drivers, it matters not at all whether you select module <M> or builtin <*> in the kernel config. An exception would be a wifi NIC that needs to load firmware. In that case the driver should be a module rather than builtin so that the appropriate filesystem is mounted and firmware files are available *before* the NIC driver is loaded. Some wired NICs also load firmware files (r8169 might be one of these). If you're not sure, use module <M>. If you're booting from a network or running a diskless install this gets more complicated but that's a different scope and conversation. initrd/initramfs usage is also more complicated and out of scope here. Next, the "unknown symbol in module or unknown parameter" message might indicate that there's some kind of incompatibility between your kernel and its modules. This can happen if you update your kernel but forget to recompile/reinstall the modules or something similar. The "see dmesg" part is good advice, you might be able to spot the problem in dmesg's output. With that said, I'd recommend the following: 1) Build your kernel with E1000E and R8169 set to module <M> 2) Remove the old modules dir (/lib/modules/3.14.27 or whatever version) 3) Build and install new modules 4) Install the new kernel 5) Update boot loader if needed 6) Reboot If you do all this you should theoretically have everything in the proper state. If the NIC *still* doesn't work after that, I'd like to see the outputs from: lspci -k, ip a, ifconfig -a, and dmesg. I know you've posted some of these before but this is only if you still have problems after cleaning up the kernel. Cheers, Matt
participants (5)
-
Bryan Bennett -
Cezar Rangel -
Don Cupp -
James Trimbee -
Matt Housh