CRUX

Download

crux@lists.crux.nu

January 2015

26 participants
61 discussions

Re: after running nvidia-xconfig the mouse and the keyboard cannot be used in graphic mode
by Cezar Rangel 01 Jan '15

01 Jan '15

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(a)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(a)yahoo.com> wrote: > > > Nice, but can you post the log? > > > Sent from my Verizon Wireless 4G LTE smartphone > > -------- Original message -------- From: Cezar Rangel < > cezar.rangel(a)gmail.com> Date: 12/28/2014 10:09 AM (GMT-08:00) > To: Fredrik Rinnestam <fredrik(a)rinnestam.se> Cc: > crux(a)lists.crux.nu Subject: Re: after running nvidia-xconfig the > mouse and the keyboard cannot be used in graphic mode > > 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(a)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(a)lists.crux.nu > http://lists.crux.nu/mailman/listinfo/crux > > > > > -- > * Cezar Rangel* > *cezar.rangel(a)gmail.com <cezar.rangel(a)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(a)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(a)lists.crux.nu > http://lists.crux.nu/mailman/listinfo/crux > > > > -- > Cezar Rangel > cezar.rangel(a)gmail.com > > -- * Cezar Rangel* *cezar.rangel(a)gmail.com <cezar.rangel(a)gmail.com>*

5 13