Xorg 7.0 modular

rayzorblayde · 2006-01-08 21:15:31

wow. thanks for the fast replies... now i'm having trouble with the nvidia screen just freezing. it's right before kde actually starts loading... i will post my xorg log again ... (with just the EE lines)

rayzorblayde · 2006-01-08 21:23:15

well, it was a problem with evdev. I changed to just 'mouse' as the driver for now, but here is the errors:

(EE) ioctl EVIOCGBIT failed: Inappropriate ioctl for device
(EE) PreInit failed for input device "MX700"

(WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi".
(WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi".
(WW) xf86OpenConsole: Could not save ownership of VT
(WW) xf86OpenConsole: chown /dev/tty0 failed: No such file or directory

thanks for the help so far! )

jinn · 2006-01-08 21:36:50

Np, btw why do you need evdev anyway? for scrolling with the mouse? I dont use evdev and scrolling works just fine.

rayzorblayde · 2006-01-08 21:47:58

no, scrolling works fine. it's for the back and forward buttons on my MX700. or any 'extra' buttons for that matter. at least that's what i've used before to get it work. is there some new thing now to get those buttons to work?

jinn · 2006-01-08 21:54:39

not really, just add some lines in xorg and it should work fine. I dont think you need the evdev driver in xorg 7.0. But I am not sure.

rayzorblayde · 2006-01-08 22:09:43

well i hope i don't need it any more. that would be great! if anyone knows how to get this to work w/o evdev, i'm all ears! )

ganja_guru · 2006-01-09 03:34:39

evdev is really easy, go back a bit on this thread and youll find help on setting up evdev. See this..

http://www.linux-gamers.net/modules/wfs … ticleid=46

you HAVE to set up a custom udev node for your mouse to get evdev to work.

vacant · 2006-01-09 11:06:09

Just in case some people don't know much about grep ...

Komodo wrote:

When you post your xorg.conf, it's best to post it without the comment lines (the ones that start with a # symbol), since this makes finding things easier.

grep -v "^#" /etc/X11/xorg.conf > my_xorg.conf

komodo wrote:

Additionally, when posting the Xorg.0.log, you only need to include (EE) lines, as these indicate errors.

grep "^(EE)" /var/log/Xorg.0.log > my_xorg.log

^ means "start of line" in this case

Komodo · 2006-01-09 14:59:46

good call vacant

JGC · 2006-01-09 16:09:10

ganja_guru wrote:

evdev is really easy, go back a bit on this thread and youll find help on setting up evdev. See this..
http://www.linux-gamers.net/modules/wfs … ticleid=46
you HAVE to set up a custom udev node for your mouse to get evdev to work.

It's not needed, you can use /dev/input/event1 instead, if you're sure your mouse will have that device node assigned each and every time.

ganja_guru · 2006-01-10 06:41:55

JGC wrote:

It's not needed, you can use /dev/input/event1 instead, if you're sure your mouse will have that device node assigned each and every time.

JGC, I tried quite a few times to get things working without creating the node, but always ended up with the frozen nvidia screen. IMHO, I think its simpler to create the node so that even if you forget which USB port your mouse was plugged into(like during a hardware upgrade), you don't have to worry about X crashing/editing driver to "mouse"

This is how I set up my MS Intellimouse Explorer :

this is what i get with

#cat /proc/bus/input/devices

I: Bus=0003 Vendor=045e Product=008c Version=0057
N: Name="Microsoft Microsoft Wireless Optical Mouse® 1.0A"
P: Phys=usb-0000:06:08.1-1/input0
S: Sysfs=/class/input/input0
H: Handlers=mouse0 event0
B: EV=7
B: KEY=1f0000 0 0 0 0 0 0 0 0
B: REL=1c3

# Microsoft appearing twice is not a typo. This is important when you set up the rule. See below.

This is my custom udev rule, saved as 10-local.rules in /etc/udev/rules.d

KERNEL=="event*", SYSFS{manufacturer}=="Microsoft", SYSFS{product}=="Microsoft Wireless Optical Mouse® 1.0A", NAME=="input/ms1000", MODE=="0644"

I just used ms1000 cause I couldn't think of anything better. Just copy-paste whatever you get in /proc/bus/input/devices into the SYSFS{manufacturer} and SYSFS{product} part.

Eliatamby · 2006-01-10 11:25:02

I enableed testing and current, and did pacman -S xorg-server to install. Install went fine, but X craps out when running Xorg -configure

I get a message saying Caught signal 11, and it exits without configuring.

NP, I though running xorgconfig would give me a conf file. Ran it fine, but when I run startx I get a message saying that it cannot find kbd, mouse, and nv drivers??! I was sure that this was an all inclusive install.

Anyone have any suggestions?

Gullible Jones · 2006-01-10 11:38:35

You have to install them separately:

pacman -S xf86-input-keyboard xf86-input-mouse xf86-video-nv

You should probably also install the VESA driver (xf86-video-vesa).

Eliatamby · 2006-01-10 11:51:04

Never mind, I'm a goose

Arch Linux

#126 2006-01-08 21:15:31

Re: Xorg 7.0 modular

#127 2006-01-08 21:23:15

Re: Xorg 7.0 modular

#128 2006-01-08 21:36:50

Re: Xorg 7.0 modular

#129 2006-01-08 21:47:58

Re: Xorg 7.0 modular

#130 2006-01-08 21:54:39

Re: Xorg 7.0 modular

#131 2006-01-08 22:09:43

Re: Xorg 7.0 modular

#132 2006-01-09 03:34:39

Re: Xorg 7.0 modular

#133 2006-01-09 11:06:09

Re: Xorg 7.0 modular

#134 2006-01-09 14:59:46

Re: Xorg 7.0 modular

#135 2006-01-09 16:09:10

Re: Xorg 7.0 modular

#136 2006-01-10 06:41:55

Re: Xorg 7.0 modular

#137 2006-01-10 11:25:02

Re: Xorg 7.0 modular

#138 2006-01-10 11:38:35

Re: Xorg 7.0 modular

#139 2006-01-10 11:51:04

Re: Xorg 7.0 modular

Board footer