T30 Problems and Questions

Ok I have a T30 that I do not know what could cause the problem and thought I could post the question here and see what other users could recommend trying.
First off all Keyboard functions work properly.
Second the power button and such works properly
Now the led lights for power, hard drive activity, battery indication, these do not work.
I think the power button and these LED's are on the same board, although I could be wrong. But it just seems odd that none of the LEDs including the ones on the lower side of the display are working.
Any ideas on what could cause this? Anything I can check? All assistance greatly appreciated.

It's been years since I've last opened a T30. And even back then, I was not playing around with the fuses.
To make one thing perfectly clear: these fuses are *NOT* meant to be user replaceable and you're looking at a board level repair involving components that are beyond tiny. Unless you're very experienced with a soldering iron, you may just want to get a replacement board or an entire barebone T30...at today's prices, that's what I would do.
Good luck.
Cheers,
George
In daily use: R60F, R500F, T61, T410
Collecting dust: T60
Enjoying retirement: A31p, T42p,
Non-ThinkPads: Panasonic CF-31 & CF-52, HP 8760W
Starting Thursday, 08/14/2014 I'll be away from the forums until further notice. Please do NOT send private messages since I won't be able to read them. Thank you.

Similar Messages

Some problems and questions using OWB

For Igor or anyone who can help me :-)
Hello Igor,
Thanks for all your help concerning my mapping deployment problem! Now its working better ;-)
I used the OWB Runtime Assistant to create a new runtime target schema and i use the owner of this schema as user while logging to OWB.
Now i can create and deploy without problems mappings, tables, functions, procedures, packages, dimensions, views, materialized views, process flows (i have installed the Oracle Workflow Client 2.6.2.0.0 with OWF builder and OWF mailer ).
However I have still some problems and questions :-)
a) After deploying a mapping or process flow i can execute them from OWB Deployment Manager. How can i schedule the execution of a deployed precess without using OWBDM ? (I want to execute a process every day to perform ETL).
b) I think i have a problem deploying cubes. I create a cube in OWB, the validation is OK, the deploment succeds, but if i look with OEMC in the tree in the Warehouse OLAP section no cube is created. Only the fact tabe is created. If i look to the scripts from the Pre Deployment generation results i found DDLs only for TABLE, INDEX, UNIQUE KEY, FOREIGN KEY and ANALYZE object types, meanwhile during a dimension deployment i found also a DDL for the DIMENSION type object. WHY ?
c) If I look in the procedures of the new created OWB Runtime Target Schema I found 3 procedures which are in error and when I try to compile them I receive the following error messages :
- procedure WB_OLAP_LOAD_CUBE
PLS-00201: identifier 'DBMS_AWM.CREATE_AWCUBELOAD_SPEC' must be declared
- procedure WB_OLAP_LOAD_DIMENSION
PLS-00201: identifier 'DBMS_AWM.CREATE_AWDIMLOAD_SPEC' must be declared
- procedure WB_OLAP_LOAD_DIMENSION_GENUK
PLS-00201: identifier 'DBMS_AWM.CREATE_AWDIMLOAD_SPEC' must be declared
How can solve this problem? Is there any link with the fact that the cube is not generated?
d) When I first acces the deployed DIM in the OEMC tree I receive a message saying that the dimension does not have complete metadata as needed for use by Oracle OLAP services (because is created either in an earlier version of Oracle database or it was created by an an other application than OEMC) and OEMC automatically generates the default needed metadata. Is this normal ?
I work in an environment with
- Oracle 9i Database 9.2.0.1.0
- Oracle 9i Client 9.2.0.1.0
- Oracle 9i Warehouse Builder Products 9.2.0.2.8
Best Regards:
Vlad
PS Sorry for my poor English ;-)

Answered in your "Getting RPE-01008 when deploying mappings" post.
Regards:
Igor

Some problems and questions

I have some problems and questions about my MSI MEGA PC 180 system...
One problem is that MSI live monitor only works one time after every new installation then is just say "The URL is invalid" every other time I try to search for updates.
One problem is that one of the fans doesn't turn off when I turn of the computer and the only way to get i to turn off is to turn on the hifi mode and turn it off then the fan stops. And some times the fan can start after a while when the computer has been turned off.
There are two fans for the cooling of the CPU but PCALERT only shows the speed of one of them.. why? according to the manual one of the is called CPU fan and the other one is called sysfan but only CPU fan showes i PCALERT.
Are there no other way to control the Tv other than with the Home Teather system than I find way to slow if you use 1280x1024 resolution on the screen like I do. And are there no way to sort and remove channels in home teather? As i is now I can't move the channels in the order I want and I can't remover channels that the auto search thaught was channels but aren't?
An other thing that I find annoying is that the fullscreen mode of home teather doens't cover all off the screen it doesn't hide the systray and leaves a small but annoying kolumn to the right that showes the backgrund and that is very annoying to watch tv if you have a light backgrund because the kolumn are so bright.

Welcome Kabbo,
I see you agree that MC III is far from perfect. Perhaps you can try the combination of Media Portal and Ir2Key. Just read some of the other posts including "WinIRX.ocx internals/usage" by ddookie. Another possibility is to try Dscaler, but this program is only for watching TV.
Regarding the processor fans: its normal that only one of the two shows up in PcAlert; when you look closely to both fans you'll see that one has only a two-wired connection.
The problem of a fan not shutting down is new to me, I suppose you have checked the connections to your mobo?
Greetz,
JaDi

PlayBook .. problem and question

hi
I have a problem and a question
the problem is i connect my bold 9700 with the playbook by the bridge. it connected sucsseful and i can open the files, messeges, notes, calendar.. etc. the problem is the bbm cant opened. it stuck in the loading wheel screen. i wait for more than 30 min. but nothing happened.
the bbm version is 5.0.3.22
the bridge in the bold is 1.0.0.83
the playbook software is 1.0.3.1868
thanks

Well, I'm surprised that this is playing you up. Anyway, before doing anything else I'd try deleting ALL bluetooth associations on the BB and the PB, uninstall the Bridge App. Reboot both devices and try again. You never know...
If it STILL doesn't work:
I'd suggest a couple of things.
1 - I'm running 6.0.0.534 with no trouble - give that a go. Backup first, obviously.
2 - Try installing and connecting the Bridge before you restore all of your data and apps. If it works, then restore and try again.
I'm working on the assumption that either that particular OS is causing trouble (unlikely), or that there is something on your phone that is meddling with the Bluetooth connection somehow.
Good luck!
1. If any post helps you please click the below the post(s) that helped you.
2. Please resolve your thread by marking the post "Solution?" which solved it for you!

E50 problems and questions

Hello, I have a few questions aboyt e50.
i own to phones model e50 and this is what i need:
- big font size for contacts
- is there any way to have wireless on e50?
- the multi task doesnt work ... i tried to upgrade the software...but the same problem
- and the last question is:
how to activate PTT? is says to check the settings...but i dont know these settings.
thanks.
Message Edited by alexrose on 26-Jan-2008 01:37 PM

You cannot increase the font size of S60 3rd edition handsets as it is not a feature they support, you can however download an application called font magnifier from Nokia Software Market http://www.softwaremarket.nokia.com
You unfortunatlye cannot get WLAN for the E50-1 either as there needs to be hardware support for this feature too. The E50-1 was the entry level Eseries handset more voice centric therefore no 3G or Wi Fi.
As for the multi tasking, all S60 devices support multi tasking, simply hold down the menu key to open task bar, if you need to minimize an app and keep it running in the backround, simply press the menu key once when in that app, do whatever you need to then hold down the menu key again and select your previous app from the task bar to continue!
PS: Don't keep to many apps running to prevent slowness and?or freezing
iPhone 5 32GB
MacBook Pro Retina 15" Mac OS X Mountain Lion 10.8.4

Udev kernel 2.6 boot problems and questions

Hello there.. During these days I'm trying to install a new linux kernel. I have the insane Idea of installing an old kernel. I compiled the "new" old kernel and I can't manege to get it to work efficently..
I keep receiving a message this message during the boot.
Failed to start udev Kernel Device Manager
Although I followed the requirements for undev related to the kernel 2.6
Why am I trying to install and older kernel? Well, the my reason is simple: my laptop keyboard that it's so annoying.. Every once and then it's not recognized at boot and it force me to reboot the system even for 4 or 5 times consequintely..
With the kernel 2.6 I never had such problems and so I thought It was worth trying..
Another interesting question that keep coming to my mind is related to the kernel that it's been update after pacman -Syu.
I notice that in /usr/src there is a a new directory eithe the new kernel called linux-3.9.5-1-ARCH, well if I try to build the kernel inside thi directory I get a message
linux-3.9.5-1-ARCH]# make
scripts/Makefile.build:44: /usr/src/linux-3.9.5-1-ARCH/arch/x86/syscalls/Makefile: No such file or directory
make[1]: *** No rule to make target `/usr/src/linux-3.9.5-1-ARCH/arch/x86/syscalls/Makefile'. Stop.
make: *** [archheaders] Error 2
The linux-headers are seems to be correctly installed to me...
Any Idea or explanation or suggestion would be very appreciated.
Thank you

Arch userspace is too new to survive with an older kernel. This isn't going to end well for you.
If you want your keyboard to function properly, I suggest you file bugs against the relevant parties and work with them to get actually get it fixed rather than go down this bizzare rabbit hole.
edit: even our LTS kernel (3.0.x) is too old for Arch userspace.
Last edited by falconindy (2013-06-14 15:00:23)

K7N2-L motherboard problems, and questions!

I'm not sure if this is the right place for this, but I think it is.
I have a K7N2-L motherboard that is giving me fits! I can't find this board in the data base to try and trouble shoot my issue, either.
Here's my questions:
Problem 1) There are three empty spaces in the floppy drive connection (plug) of this motherboard. Two of the spaces are in the second row, and are side by side, and don't appear to have ever had pins installed. This may be normal. These two empty spaces (blue X's) correspond to spots that don't even have holes through the motherboard to even install any pins. However, the third missing connector pin does appear to have had a pin soldered into it (red X), but now there is no pin. Also, when I attempt to start the system, the motherboard does post and will allow you to enter the BIOS set up. However, at the same time, I get a "Floppy Drive - FAILURE" warning during this part of the start up. This indicates to me that the drive is not being detected, and it may be caused by the suspected missing pin (red X). Here is a crude visual of the floppy plug lay out in question. The green I's indicate existing pins, and the X's the missing pins. The blue X's are the ones that appear to never have had pins, but the red X appears to have had a pin, as it's soldered, but is missing. Please, note the notch at the top of this crude illustration for proper orientation of the plug. If you have any info on this, please, give me some insight as I can't find any way of referencing this problem.
----------- ------------- ^ motherboard edge is here ^
I I I I I I I I I I I I I I X I I
I I I I I I I I I I I I I I X X I
Floppy Connector Layout
Problem 2) It's possible this problem is a BIOS problem, and could be corrected with a BIOS update. However, since I don't currently have a floppy drive, I can't update the BIOS. I've set the BOOT priority in the BIOS as, 1-Floppy; 2-CD-Rom; 3-HDD0. However, the board selecting the devices in the proper order, and thus I can't get any of my drive to boot from either a CD or a Hard disc. I do know that the processor I'm using is good, as it came out of another operating system board. The processor is an AMD Duron 1800/266 FSB. Here's what is being seen with the BIOS with regards to the processor. If, in the BIOS, I set the FSB to 100MHz the processor shows as a 1200MHz processor instead of an 1800. However, when I reset the BIOS FSB to 133MHz (as it should be) the BIOS now shows the processor as a 1900+. Neither of these is correct. Any ideas as to what may be going on?
Thanks in advance.........
kudzu48

Hi
I just checked 8 motheboards that I have laying around from MSI, Asus, Intel and Biostar. The pin location that you have marked in red does not have a pin in it. The ones that you marked in blue do have pins in them. If you are not the original owner, it may be that someone tried to replace a couple of broken pins and gave up.
A bios update should take care of the failure to recognize your Duron 1800. I have provided a link where you can see the later bios revisions.
http://www.msi.com.tw/program/support/bios/bos/spt_bos_detail.php?UID=393&kind=1

VOD - Problems and Questions

I'm in VHO 7 and use VOD all the time mainly for the network shows and premium subscriptions. Been having a tone of problems with VOD not being updated for days/ sometimes weeks at a time on and off for these past 6+ months . Also have the bizzar hourglass icon which has taken the place of the 'new' and red triangle icons. None of the free titles show the avaiable until date. A big problem also is that many times the HD VOD does not match the SD vod - folders available in both sections will not have the same episodes or HD will be missing episode thats available in SD. I've contacted Verizon nearly every way possible, so now I'm turning to this forum to see if anyone else is having the same problems and to see if anyone has any support? Maybe by chance someone at verizon will offer an explanation? Twitter has failed, emailing them through contact us has failed, tech support has failed - what else is there?
I'd also like to know why verizon does not offer all the HD VOD available on the market? I have used Comcast, TImeWarner, and Cablevision VOD in the past and they all have a ton of free HD VOD from the networks that verizon does not offer. They even offer HD VOD of networks not even aviable in HD on the network. I sent the same message to the person who runs FIOSTV twitter and he replyed the with standard issue PR message claiming Verizon offers nearly all HDVOD available and its up to the providers. We all know thats a load of crap. I like the service or I wouldn't still be with them. Just do not like lame excuses and poor response to problems.

Hi we just went to a one bill with fios TV int and wireless and within the first week of service I was already on the phone trying to find out why I lied to too. vod is advertised as to be on demand within 24hrs of original air date but I wasn't receiving most of them for several days later if not a week later. So I called and spent several hours on the phone and all they told me was everything on their end was working fine and they put out a trouble ticket so I got a phone call and we talk and I said why I'm I not getting them on time and I was told bc it's up to when the tv stations release it to them and then they would release to us and I told them that's not the way vod works I told them to provide a service like that theirs a contract between Verizon and the carrier's so he said he would keep a trouble ticket and I would here something back within 48hrs I waited 3 days and I called back only to find that the ticket was gone they told me the reason for that was he put in problem resolved and we were no where close to fixing the issue so I spent more time on the phone with someone different only to here the same thing and I told them the same thing and he finally called someone else and he got back on the phone and said I was right the reason why I don't get vod on time BC I'm not in a high volume market Verizon has states and county's broke down into blocks and were I live is a low volume market so it doesn't get released to me within the 24hrs. But if I lived in a high volume market like a big city with lots of customers I would get it. After my one year contract I'm done withem. comcast has no issues with this problem in my area and that's were I'm headed and this is not the only issue I've had hope this helped

Library problem and question.

I'm sure that if I could check through the whole of the topic list and read all of the threads that seem to be relevant, I might find the answer,but I don't have enough time, and I don't know how to compose a search that would find me the answers I need accurately enough. I have two matters I need help with.
(1) When the betas of LightRoom came out, I thought I would give it a try as it seemed to do what I wanted in terms of importing my photos and maintaining a database. Fundamentally it does, but as a result of the experimentation I did, things are a little confused in terms of the library.
I'm using a MacBook Pro with an external desktop HD, and I have recently bought a 120GB "pocket" HD. I am now shooting in RAW all the time, but some of the photos in the library are JPGs from my previous camera. My plan is to use the pocket drive to store the photos on, with a back-up on the desktop external. What I am currently doing is using DNG Converter to pull them off the card and save them on the pocket drive. Then I import the DNGs into LightRoom and organise them in collections. However, I also have many many JPGs from my previous camera which I would like to import. They are rather scattered in terms of where they are located.
The Library is currently the one that I set up when originally trialling the beta; it is on the HD of the MacBook Pro, backed up to the desktop HD, but there is another library on that HD that I set up while experimenting which contains other photos which I need to bring into a single library. I really feel I need to redo it completely starting again from scratch so that I can bring everything together in a better organised manner. What would be the best way to do that? And what is the best location for the library database?
(2) The last time I imported some photos -- having done the DNG conversion and saved them to the pocket drive -- I then dragged them in batches to appropriate collection folders. However, for some of them, they do not appear in the folder I dragged them to, nor in any of the others ... they only appear in the overall "Library: all photographs" and "Library: Previous import". How can I retrieve them so that I can put them in the appropriate collection folder so that I can include them in the gallery based on that? The original DNGs are still in the folder on the pocket drive.
Sorry, this has been long and rambling, but I would really appreciate any help and advice.
Mark in China

Thanks for the reply Sean. <It sounds like you expect to be able to drag images from Previous Import into a folder. > I fear that is what I may have tried to do with these particular photos the first time when they got lost, but it is not what I normally do. I have a folder on the pocket drive called DNGs. Within this are a number of sub-folders for different sets of photos, Xiada, Longyan, Wuyishan, etc. When I use DNG Converter to take the RAW images off the card I have it put them in the main DNG folder, because for instance there may be some photos of flowers among them that I want eventually to go in the Flora sub-folder and photos of buildings that I want to go in the Xiada folder, even though all the photos were actually taken on the Xiada campus. When I import them into LR, they are found in a folder in the left pane of LR called DNGs. From there I drag them into the appropriate sub-folders, each time getting an alert about moving the photos on the disk. As I say, with the 9 photos in question, thinking back I may have dragged them from the "Previous Import". The result is that although the DNGs in question are invisible within LR, even though I deleted them rather than removed them, and I have gone through the whole process starting from getting them off the card again using DNG Converter, and they are now visible in the DNG folder in LR, when I drag them from there to the folder I want them in, LR issues an alert that "A file named P1000xxx.dng already exists at the destination" and doesn't move it, even though that photo is not visible. Again, as I said, on my desktop external drive, there is a parallel folder structure to the one on the pocket drive, and looking at the relevant folder using the finder, photos of those names are in that. I can delete them using the finder, but am worried that if I do so, the LR database will be corrupted. On the other hand, as they are there, but LR doesn't show them in the library, perhaps it is only the system that knows they are there and not LR, so deleting them will not affect the library. I guess the thing to do is to export all the photos in the library to a new location as DNGs with the metadata to XMPs, ready to redo the whole library set up from scratch fortunately I am only dealing with a few hundred photos, not thousands or tens of thousands and then try deleting them. If the current library is corrupted, then I can make a new one I was going to wait until 1.1 and do that anyway and if it doesn't then I should be able to do the move into the folders without problem. Also thinking round this, I should perhaps be using collections rather than folders anyway, so I must explore that for future reference. Mark in China

Alarm clock problem and question

My son is having problems with the alarm on his iPhone 3G. Sometimes it simply does not go off. He has tried resetting, it didn't help. I searched the forums and noticed that some other people have had the same problem. Perhaps the upcoming software update may help.
In the meantime, here is my question. There are several alarm clock apps in the app store. If he downloads one of those to use, will the battery drain be increased? He has heard that non apple apps like alarm clocks really drink up the battery life.
Any hints, clarifications, etc. greatly appreciated.
Thanks.

I'm in Iraq and I use my alarm daily, to wake me up. I haven't had a problem, until I updated my phone to the 3.0 version software. I'm going to try to email support to see if there is a fix coming out; and if not, to notify them of the problem. I suggest anyone with this problem, do the same.
Dustin
USMC

DBT-120 Problems and Questions

I'm having two different problems with two different DBT-120s. The DBT-120 (H/W B3) which I've been using for nearly two years is suddenly working sporadically at best. The lights only come on for about 10-20 sec and then go dark, and the only way to lite them is to remove and replace it in the USB. I have to try this time and again for 20 minutes before it will finally discover my Apple wireless keyboard and mouse. The problem exists without regard to the USB port used, so that's not the issue. I suspected that it was simply failing after a lifetime of solid use, so I purchased another one. The new DBT-120, now H/W C1, lights perfectly but does not discover the keyboard or mouse at all, under any circumstances that I can determine. My system meets the minimum standards as listed on the packaging. I've also tried to update the firmware, but my system informed me that it was not needed.
Two questions: 1) Is there some underlying reason why the C1 120 will not work with my K/M, which were both the first such bluetooths released by Apple?
2) Am I right in assuming that the B3 120 was failing, or is there something else going on here?
G4 1 GHz x 2 Mac OS X (10.4.7) maxed out RAM, stunningly high HD availability

I, too, have just encountered a significant problem with the DBT-120 (v. 3). It worked fine for several weeks (I purchased it from the Apple online store at the end of March), but, I think, BT was interfering with my Apple Airport base station, so I disabled BT--although I kept the DBT plugged in to a USB port. Yesterday I attempted to connect a new Mighty Mouse using the DBT-120. Nada. The light on the DBT-120 would not work. I plugged it into several different USB ports (and even my Windows laptop) and it still wouldn't work. I checked with D-Link. The technician told me the problem was with the BT software on the Mighty Mouse CD. I tried to uninstall the software, but I don't think I succeeded. At any rate, I believe the problem is with the DBT and have so advised D-Link. Awaiting a response. (There's supposed to be a year warranty. Apple, by the way, will not honor this; the company refers buyers of 3rd-party equipment to the manufacturer.)
The Mighty Mouse works fine on my G4 PowerBook, which has built-in BT.
I'm inclined to agree with one of the posts: Bluetooth, at least as an add-on to the PowerMac G5, is not ready for prime time.

Backup problems and questions (v3)

Hi,
I've been reading the information regarding backups, and I want to make sure I'm safe. I want to maintain a "hot failover" in the event that my current environment becomes corrupt or unusable. My failover directory is close to 100% safe. I want to maintain two or three versions back of the data, without taking an extraordinary amount of disk space.
I had originally tried using db_hotbackup for a failover backup, yet I kept running into strange problems, namely: the db_recover step seemed to run on my prodcution environment, and was taking an extraordinariliy long time to run. Long story short, after a very tedious trial and error period, I've decided to use dbxml_dump as a backup. I'd like to know what all steps it takes when dumping the data.
My procedure is currently:
1) Run a checkpoint on current environment.
2) Copy containers, and then all active and inactive database files to my failover directory ("failover_dir").
3) Dump from the failover_dir to dump files.
4) Once dbxml_dump is done, I will run db_archive -d on both the production database.
Few questions:
1) First, of course, is this an acceptable "backup"? 2) Does dbxml_dump do any kind of verification (db_verify) prior to running? If not, what will happen if it is run against a corrput database? 3) After I get the above working, I want to make sure about #4: Can I safely delete the log files that are no longer needed (db_archive -d)? That is, I can safely run dbxml_dump again without those files.
Thanks,
Kevin

Thanks, George!
I would have liked to had db_hotbackup instead of dbxml_dump/load, but, strangely, it's one of a few things that isn't working as advertised. I run a checkpoint every half hour, and db_recover still takes forever. I think dbxml_dump/load is going to work for me--except for one potential issue. If I change my mind, I will post on BDB forum.
(2) As for ceasing operations, yes, I am temporarily stopping the reads/writes, copying the dbxml/log files to another directory, and performing dbxml_dump on it.
My one potential issue is related to indexes that you mention: "dbxml_dump will copy only content/metadata and no index databases; those are recreated during dbxml_load"
Does that mean that 1) dbxml_dump will output the list of indexes and when dbxml_load is run, it will recreate them. Or 2) that there is no index info dumped and I will have to maintain the list and reindex the container after dbxml_load is done? (I'm currently having an issue with 'addIndex', asked in another thread.)
Also, the docs seem to indicate that you can dbxml_load into an existing container. Yet, when I try to do this, I get "Error: File exists". I can successfully run dbxml_load and have it create the container.
#3 is a great idea--I will incorporate it into my backup routine.
--kevin

Multiseat problems and questions

I am trying to get a multiseat configuration running, so I used the wiki to set one up. I used a combination of existing configurations that are in my xorg.conf and the configurations found in the wiki to make a new configuration named xorg.cfg.x2. At first i thought the new configuration worked (the other gpu and monitor activated and displayed the screen correctly), until i tried to use my keyboard and mouse. The keyboard and mouse seem to do random things when they are used at all. Thankfully some of the random things got me back in a position to kill the misbehaving x-server and get the log it dumped.
this command is used to activate seat1, seat0 has the exact same problem
startx -- -layout u1 -config xorg.cfg.x2
this is xorg.cfg.x2
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/OTF/"
FontPath "/usr/share/fonts/Type1/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/75dpi/"
EndSection
Section "ServerFlags"
# Option "AutoAddDevices" "false"
# Option "AutoEnableDevices" "false"
Option "AllowMouseOpenFail" "true"
# Option "AllowEmptyInput" "on"
# Option "ZapWarning" "on"
# Option "HandleSepcialKeys" "off" # Zapping on
# Option "DRI2" "on"
Option "Xinerama" "0"
EndSection
Section "InputDevice"
Identifier "keyboard0"
Driver "kbd"
Option "Device" "/dev/input/by-id/usb-Logitech_USB_Receiver-event-kbd"
# Option "GrabDevice" "on" # prevent send event to other X-servers
EndSection
Section "InputDevice"
Identifier "keyboard1"
Driver "kbd"
Option "Device" "/dev/input/by-id/usb-Dell_Dell_USB_Keyboard-event-kbd"
# Option "GrabDevice" "on" # prevent send event to other X-servers
EndSection
Section "InputDevice"
Identifier "mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/by-id/usb-Microsoft_Microsoft®_Nano_Transceiver_v2.0-if01-event-mouse"
# Option "GrabDevice" "on" # prevent send event to other X-servers
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "InputDevice"
Identifier "mouse1"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/by-id/usb-Areson_USB_Device-event-mouse"
# Option "GrabDevice" "on" # prevent send event to other X-servers
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Device"
Identifier "gpu0"
Driver "nvidia"
Option "NoLogo" "1"
BusId "PCI:1:0:0"
Option "ProbeAllGpus" "false" # Only required for nvidia
EndSection
Section "Device"
Identifier "gpu1"
Driver "nvidia"
Option "NoLogo" "1"
BusId "PCI:6:0:0"
Option "ProbeAllGpus" "false" # Only required for nvidia
EndSection
Section "Monitor"
Identifier "m0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "Monitor"
Identifier "m1"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "Screen"
Identifier "screen0"
Device "gpu0"
Monitor "m0"
Subsection "Display"
Depth 24
EndSubsection
EndSection
Section "Screen"
Identifier "screen1"
Device "gpu1"
Monitor "m1"
Subsection "Display"
Depth 24
EndSubsection
EndSection
Section "ServerLayout"
Identifier "u0"
Screen "screen0" 0 0
InputDevice "mouse0" "CorePointer"
InputDevice "keyboard0" "CoreKeyboard"
# Option "Clone" "off"
Option "AutoAddDevices" "off"
# Option "DisableModInDev" "true"
Option "SingleCard" "on" # use this to simplfied isolatedevice option
EndSection
Section "ServerLayout"
Identifier "u1"
Screen "screen1" 0 0
InputDevice "mouse1" "CorePointer"
InputDevice "keyboard1" "CoreKeyboard"
# Option "Clone" "off"
Option "AutoAddDevices" "off"
# Option "DisableModInDev" "true"
Option "SingleCard" "on" # use this to simplfied isolatedevice option
EndSection
this is the working xorg.conf that i currently use
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 310.19 ([email protected]) Thu Nov 8 02:09:12 PST 2012
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
Screen 1 "Screen1" RightOf "Screen0"
Screen 2 "Screen2" RightOf "Screen1"
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/OTF/"
FontPath "/usr/share/fonts/Type1/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/75dpi/"
EndSection
Section "Module"
Load "glx"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "Monitor"
Identifier "Monitor1"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "Monitor"
Identifier "Monitor2"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "Device"
### Available Driver options are:-
### Values: : integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
### <percent>: "<f>%"
### [arg]: arg optional
#Option "SWcursor" # [<bool>]
#Option "HWcursor" # [<bool>]
#Option "NoAccel" # [<bool>]
#Option "ShadowFB" # [<bool>]
#Option "UseFBDev" # [<bool>]
#Option "Rotate" # [<str>]
#Option "VideoKey" # 
#Option "FlatPanel" # [<bool>]
#Option "FPDither" # [<bool>]
#Option "CrtcNumber" # 
#Option "FPScale" # [<bool>]
#Option "FPTweak" # 
#Option "DualHead" # [<bool>]
Identifier "Card0"
Driver "nvidia"
BusID "PCI:1:0:0"
EndSection
Section "Device"
### Available Driver options are:-
### Values: : integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
### <percent>: "<f>%"
### [arg]: arg optional
#Option "ShadowFB" # [<bool>]
#Option "Rotate" # <str>
#Option "fbdev" # <str>
#Option "debug" # [<bool>]
Identifier "Card1"
Driver "nvidia"
BusID "PCI:1:0:0"
EndSection
Section "Device"
### Available Driver options are:-
### Values: : integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
### <percent>: "<f>%"
### [arg]: arg optional
#Option "ShadowFB" # [<bool>]
#Option "DefaultRefresh" # [<bool>]
#Option "ModeSetClearScreen" # [<bool>]
Identifier "Card2"
Driver "nvidia"
BusID "PCI:1:0:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
Section "Screen"
Identifier "Screen1"
Device "Card1"
Monitor "Monitor1"
SubSection "Display"
Viewport 0 0
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
Section "Screen"
Identifier "Screen2"
Device "Card2"
Monitor "Monitor2"
SubSection "Display"
Viewport 0 0
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
this is the logfile for the failed multiseat attempt
[ 1307.736]
X.Org X Server 1.13.1
Release Date: 2012-12-13
[ 1307.736] X Protocol Version 11, Revision 0
[ 1307.736] Build Operating System: Linux 3.7.0-1-ARCH x86_64
[ 1307.736] Current Operating System: Linux FX-l0vot 3.7.1-2-ARCH #1 SMP PREEMPT Thu Dec 20 17:57:00 CET 2012 x86_64
[ 1307.737] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=aade275d-e863-44be-b27a-e41e2fca2c30 ro quiet init=/usr/lib/systemd/systemd
[ 1307.737] Build Date: 16 December 2012 04:45:14PM
[ 1307.737]
[ 1307.737] Current version of pixman: 0.28.2
[ 1307.737] Before reporting problems, check [url]http://wiki.x.org[/url]
to make sure that you have the latest version.
[ 1307.737] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 1307.738] (==) Log file: "/var/log/Xorg.1.log", Time: Fri Jan 4 14:30:57 2013
[ 1307.763] (++) Using config file: "xorg.cfg.x2"
[ 1307.763] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 1307.775] (++) ServerLayout "u1"
[ 1307.775] (**) |-->Screen "screen1" (0)
[ 1307.775] (**) | |-->Monitor "m1"
[ 1307.775] (**) | |-->Device "gpu1"
[ 1307.775] (**) |-->Input Device "mouse1"
[ 1307.775] (**) |-->Input Device "keyboard1"
[ 1307.775] (**) Option "SingleCard" "on"
[ 1307.776] (**) Option "AllowMouseOpenFail" "true"
[ 1307.776] (**) Option "Xinerama" "0"
[ 1307.776] (**) Not automatically adding devices
[ 1307.776] (==) Automatically enabling devices
[ 1307.776] (==) Automatically adding GPU devices
[ 1307.776] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 1307.776] Entry deleted from font path.
[ 1307.776] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 1307.776] Entry deleted from font path.
[ 1307.776] (**) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/,
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 1307.776] (**) ModulePath set to "/usr/lib/xorg/modules"
[ 1307.776] (II) Loader magic: 0x7fcc40
[ 1307.776] (II) Module ABI versions:
[ 1307.776] X.Org ANSI C Emulation: 0.4
[ 1307.776] X.Org Video Driver: 13.1
[ 1307.776] X.Org XInput driver : 18.0
[ 1307.776] X.Org Server Extension : 7.0
[ 1307.779] (--) PCI:*(0:6:0:0) 10de:10c3:3842:1303 rev 162, Mem @ 0xf9000000/16777216, 0xa0000000/268435456, 0xbe000000/33554432, I/O @ 0x00009f00/128, BIOS @ 0x????????/524288
[ 1307.779] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 1307.779] Initializing built-in extension Generic Event Extension
[ 1307.779] Initializing built-in extension SHAPE
[ 1307.779] Initializing built-in extension MIT-SHM
[ 1307.780] Initializing built-in extension XInputExtension
[ 1307.780] Initializing built-in extension XTEST
[ 1307.780] Initializing built-in extension BIG-REQUESTS
[ 1307.780] Initializing built-in extension SYNC
[ 1307.780] Initializing built-in extension XKEYBOARD
[ 1307.780] Initializing built-in extension XC-MISC
[ 1307.780] Initializing built-in extension SECURITY
[ 1307.780] Initializing built-in extension XINERAMA
[ 1307.780] Initializing built-in extension XFIXES
[ 1307.780] Initializing built-in extension RENDER
[ 1307.780] Initializing built-in extension RANDR
[ 1307.781] Initializing built-in extension COMPOSITE
[ 1307.781] Initializing built-in extension DAMAGE
[ 1307.781] Initializing built-in extension MIT-SCREEN-SAVER
[ 1307.781] Initializing built-in extension DOUBLE-BUFFER
[ 1307.781] Initializing built-in extension RECORD
[ 1307.781] Initializing built-in extension DPMS
[ 1307.781] Initializing built-in extension X-Resource
[ 1307.781] Initializing built-in extension XVideo
[ 1307.781] Initializing built-in extension XVideo-MotionCompensation
[ 1307.781] Initializing built-in extension XFree86-VidModeExtension
[ 1307.781] Initializing built-in extension XFree86-DGA
[ 1307.782] Initializing built-in extension XFree86-DRI
[ 1307.782] Initializing built-in extension DRI2
[ 1307.782] (II) LoadModule: "glx"
[ 1307.782] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 1307.794] (II) Module glx: vendor="NVIDIA Corporation"
[ 1307.794] compiled for 4.0.2, module version = 1.0.0
[ 1307.794] Module class: X.Org Server Extension
[ 1307.794] (II) NVIDIA GLX Module 310.19 Thu Nov 8 01:12:43 PST 2012
[ 1307.794] Loading extension GLX
[ 1307.794] (II) LoadModule: "nvidia"
[ 1307.794] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 1307.795] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 1307.795] compiled for 4.0.2, module version = 1.0.0
[ 1307.795] Module class: X.Org Video Driver
[ 1307.795] (II) LoadModule: "mouse"
[ 1307.795] (II) Loading /usr/lib/xorg/modules/input/mouse_drv.so
[ 1307.805] (II) Module mouse: vendor="X.Org Foundation"
[ 1307.805] compiled for 1.13.0, module version = 1.8.1
[ 1307.805] Module class: X.Org XInput Driver
[ 1307.806] ABI class: X.Org XInput driver, version 18.0
[ 1307.806] (II) LoadModule: "kbd"
[ 1307.806] (II) Loading /usr/lib/xorg/modules/input/kbd_drv.so
[ 1307.812] (II) Module kbd: vendor="X.Org Foundation"
[ 1307.812] compiled for 1.13.0, module version = 1.6.2
[ 1307.812] Module class: X.Org XInput Driver
[ 1307.812] ABI class: X.Org XInput driver, version 18.0
[ 1307.812] (II) NVIDIA dlloader X Driver 310.19 Thu Nov 8 00:53:33 PST 2012
[ 1307.812] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 1307.812] (--) using VT number 2
[ 1307.831] (II) Loading sub module "wfb"
[ 1307.832] (II) LoadModule: "wfb"
[ 1307.832] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 1307.832] (II) Module wfb: vendor="X.Org Foundation"
[ 1307.832] compiled for 1.13.1, module version = 1.0.0
[ 1307.832] ABI class: X.Org ANSI C Emulation, version 0.4
[ 1307.832] (II) Loading sub module "ramdac"
[ 1307.832] (II) LoadModule: "ramdac"
[ 1307.832] (II) Module "ramdac" already built-in
[ 1307.832] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[ 1307.832] (==) NVIDIA(0): RGB weight 888
[ 1307.833] (==) NVIDIA(0): Default visual is TrueColor
[ 1307.833] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 1307.833] (**) NVIDIA(0): Option "NoLogo" "1"
[ 1307.833] (**) NVIDIA(0): Option "ProbeAllGpus" "false"
[ 1307.833] (**) NVIDIA(0): Enabling 2D acceleration
[ 1307.908] (II) NVIDIA(GPU-0): Display (DELL E193FP (CRT-1)) does not support NVIDIA 3D
[ 1307.908] (II) NVIDIA(GPU-0): Vision stereo.
[ 1307.910] (II) NVIDIA(0): NVIDIA GPU GeForce 8400GS (GT218) at PCI:6:0:0 (GPU-0)
[ 1307.910] (--) NVIDIA(0): Memory: 1048576 kBytes
[ 1307.910] (--) NVIDIA(0): VideoBIOS: 70.18.5f.00.00
[ 1307.910] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 1307.919] (--) NVIDIA(0): Valid display device(s) on GeForce 8400GS at PCI:6:0:0
[ 1307.919] (--) NVIDIA(0): CRT-0
[ 1307.919] (--) NVIDIA(0): DELL E193FP (CRT-1) (connected)
[ 1307.919] (--) NVIDIA(0): DFP-0
[ 1307.919] (--) NVIDIA(0): DFP-1
[ 1307.919] (--) NVIDIA(0): CRT-0: 400.0 MHz maximum pixel clock
[ 1307.919] (--) NVIDIA(0): DELL E193FP (CRT-1): 400.0 MHz maximum pixel clock
[ 1307.919] (--) NVIDIA(0): DFP-0: 330.0 MHz maximum pixel clock
[ 1307.919] (--) NVIDIA(0): DFP-0: Internal Single Link TMDS
[ 1307.919] (--) NVIDIA(0): DFP-1: 165.0 MHz maximum pixel clock
[ 1307.919] (--) NVIDIA(0): DFP-1: Internal Single Link TMDS
[ 1307.919] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 1307.919] (**) NVIDIA(0): device DELL E193FP (CRT-1) (Using EDID frequencies has
[ 1307.919] (**) NVIDIA(0): been enabled on all display devices.)
[ 1307.921] (==) NVIDIA(0):
[ 1307.921] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[ 1307.921] (==) NVIDIA(0): will be used as the requested mode.
[ 1307.921] (==) NVIDIA(0):
[ 1307.921] (II) NVIDIA(0): Validated MetaModes:
[ 1307.921] (II) NVIDIA(0): "CRT-1:nvidia-auto-select"
[ 1307.921] (II) NVIDIA(0): Virtual screen size determined to be 1280 x 1024
[ 1307.931] (--) NVIDIA(0): DPI set to (85, 86); computed from "UseEdidDpi" X config
[ 1307.931] (--) NVIDIA(0): option
[ 1307.931] (--) Depth 24 pixmap format is 32 bpp
[ 1307.931] (II) NVIDIA: Using 768.00 MB of virtual memory for indirect memory access.
[ 1307.939] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 1307.939] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 1307.939] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 1307.939] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 1307.939] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 1307.939] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 1307.939] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 1307.939] (II) NVIDIA(0): Config Options in the README.
[ 1307.948] (II) NVIDIA(0): Setting mode "CRT-1:nvidia-auto-select"
[ 1307.978] Loading extension NV-GLX
[ 1307.996] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 1307.996] (==) NVIDIA(0): Backing store disabled
[ 1307.996] (==) NVIDIA(0): Silken mouse enabled
[ 1307.997] (==) NVIDIA(0): DPMS enabled
[ 1307.997] Loading extension NV-CONTROL
[ 1307.997] Loading extension XINERAMA
[ 1307.997] (II) Loading sub module "dri2"
[ 1307.997] (II) LoadModule: "dri2"
[ 1307.997] (II) Module "dri2" already built-in
[ 1307.997] (II) NVIDIA(0): [DRI2] Setup complete
[ 1307.997] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 1307.997] (--) RandR disabled
[ 1308.001] (II) Initializing extension GLX
[ 1308.153] (II) Using input driver 'mouse' for 'mouse1'
[ 1308.153] (**) Option "CorePointer"
[ 1308.153] (**) mouse1: always reports core events
[ 1308.153] (**) Option "Protocol" "auto"
[ 1308.153] (**) Option "Device" "/dev/input/by-id/usb-Areson_USB_Device-event-mouse"
[ 1308.154] (II) mouse1: Setting mouse protocol to "PS/2"
[ 1308.154] (**) mouse1: Protocol: "auto"
[ 1308.154] (**) mouse1: always reports core events
[ 1308.160] (==) mouse1: Emulate3Buttons, Emulate3Timeout: 50
[ 1308.160] (**) Option "ZAxisMapping" "4 5 6 7"
[ 1308.160] (**) mouse1: ZAxisMapping: buttons 4, 5, 6 and 7
[ 1308.160] (**) mouse1: Buttons: 11
[ 1308.160] (II) XINPUT: Adding extended input device "mouse1" (type: MOUSE, id 6)
[ 1308.160] (**) mouse1: (accel) keeping acceleration scheme 1
[ 1308.160] (**) mouse1: (accel) acceleration profile 0
[ 1308.160] (**) mouse1: (accel) acceleration factor: 2.000
[ 1308.160] (**) mouse1: (accel) acceleration threshold: 4
[ 1308.163] (II) mouse1: Setting mouse protocol to "PS/2"
[ 1313.423] (II) Using input driver 'kbd' for 'keyboard1'
[ 1313.423] (**) Option "CoreKeyboard"
[ 1313.423] (**) keyboard1: always reports core events
[ 1313.423] (**) keyboard1: always reports core events
[ 1313.423] (**) Option "Protocol" "standard"
[ 1313.423] (**) Option "Device" "/dev/input/by-id/usb-Dell_Dell_USB_Keyboard-event-kbd"
[ 1313.423] (**) Option "XkbRules" "base"
[ 1313.423] (**) Option "XkbModel" "pc105"
[ 1313.423] (**) Option "XkbLayout" "us"
[ 1313.423] (II) XINPUT: Adding extended input device "keyboard1" (type: KEYBOARD, id 7)
[ 1313.427] (II) config/udev: Adding input device Power Button (/dev/input/event8)
[ 1313.427] (II) AutoAddDevices is off - not adding device.
[ 1313.428] (II) config/udev: Adding input device Power Button (/dev/input/event7)
[ 1313.428] (II) AutoAddDevices is off - not adding device.
[ 1313.428] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event18)
[ 1313.428] (II) AutoAddDevices is off - not adding device.
[ 1313.428] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event19)
[ 1313.428] (II) AutoAddDevices is off - not adding device.
[ 1313.429] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event20)
[ 1313.429] (II) AutoAddDevices is off - not adding device.
[ 1313.429] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event21)
[ 1313.429] (II) AutoAddDevices is off - not adding device.
[ 1313.430] (II) config/udev: Adding input device Dell Dell USB Keyboard (/dev/input/event0)
[ 1313.430] (II) AutoAddDevices is off - not adding device.
[ 1313.430] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event1)
[ 1313.430] (II) AutoAddDevices is off - not adding device.
[ 1313.431] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event2)
[ 1313.431] (II) AutoAddDevices is off - not adding device.
[ 1313.431] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/mouse0)
[ 1313.431] (II) AutoAddDevices is off - not adding device.
[ 1313.432] (II) config/udev: Adding input device Microsoft Microsoft® Nano Transceiver v2.0 (/dev/input/event3)
[ 1313.432] (II) AutoAddDevices is off - not adding device.
[ 1313.432] (II) config/udev: Adding input device Microsoft Microsoft® Nano Transceiver v2.0 (/dev/input/event4)
[ 1313.432] (II) AutoAddDevices is off - not adding device.
[ 1313.433] (II) config/udev: Adding input device Microsoft Microsoft® Nano Transceiver v2.0 (/dev/input/mouse1)
[ 1313.433] (II) AutoAddDevices is off - not adding device.
[ 1313.433] (II) config/udev: Adding input device Microsoft Microsoft® Nano Transceiver v2.0 (/dev/input/event5)
[ 1313.433] (II) AutoAddDevices is off - not adding device.
[ 1313.434] (II) config/udev: Adding input device Microsoft Microsoft® Nano Transceiver v2.0 (/dev/input/js0)
[ 1313.434] (II) AutoAddDevices is off - not adding device.
[ 1313.434] (II) config/udev: Adding input device Areson USB Device (/dev/input/event6)
[ 1313.434] (II) AutoAddDevices is off - not adding device.
[ 1313.435] (II) config/udev: Adding input device Areson USB Device (/dev/input/mouse2)
[ 1313.435] (II) AutoAddDevices is off - not adding device.
[ 1313.435] (II) config/udev: Adding input device HDA ATI SB Line (/dev/input/event10)
[ 1313.435] (II) AutoAddDevices is off - not adding device.
[ 1313.436] (II) config/udev: Adding input device HDA ATI SB Rear Mic (/dev/input/event11)
[ 1313.436] (II) AutoAddDevices is off - not adding device.
[ 1313.436] (II) config/udev: Adding input device HDA ATI SB Front Mic (/dev/input/event12)
[ 1313.436] (II) AutoAddDevices is off - not adding device.
[ 1313.436] (II) config/udev: Adding input device HDA ATI SB Front Headphone (/dev/input/event13)
[ 1313.436] (II) AutoAddDevices is off - not adding device.
[ 1313.437] (II) config/udev: Adding input device HDA ATI SB Line Out Side (/dev/input/event14)
[ 1313.437] (II) AutoAddDevices is off - not adding device.
[ 1313.437] (II) config/udev: Adding input device HDA ATI SB Line Out CLFE (/dev/input/event15)
[ 1313.437] (II) AutoAddDevices is off - not adding device.
[ 1313.437] (II) config/udev: Adding input device HDA ATI SB Line Out Surround (/dev/input/event16)
[ 1313.438] (II) AutoAddDevices is off - not adding device.
[ 1313.438] (II) config/udev: Adding input device HDA ATI SB Line Out Front (/dev/input/event17)
[ 1313.438] (II) AutoAddDevices is off - not adding device.
[ 1313.438] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event22)
[ 1313.438] (II) AutoAddDevices is off - not adding device.
[ 1313.439] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event23)
[ 1313.439] (II) AutoAddDevices is off - not adding device.
[ 1313.439] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event24)
[ 1313.439] (II) AutoAddDevices is off - not adding device.
[ 1313.439] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event25)
[ 1313.440] (II) AutoAddDevices is off - not adding device.
[ 1313.440] (II) config/udev: Adding input device PC Speaker (/dev/input/event9)
[ 1313.440] (II) AutoAddDevices is off - not adding device.
[ 1313.687] (II) NVIDIA(GPU-0): Display (DELL E193FP (CRT-1)) does not support NVIDIA 3D
[ 1313.687] (II) NVIDIA(GPU-0): Vision stereo.
[ 1313.687] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 1313.687] (**) NVIDIA(0): device DELL E193FP (CRT-1) (Using EDID frequencies has
[ 1313.687] (**) NVIDIA(0): been enabled on all display devices.)
[ 1313.724] (II) NVIDIA(GPU-0): Display (DELL E193FP (CRT-1)) does not support NVIDIA 3D
[ 1313.724] (II) NVIDIA(GPU-0): Vision stereo.
[ 1313.724] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 1313.724] (**) NVIDIA(0): device DELL E193FP (CRT-1) (Using EDID frequencies has
[ 1313.724] (**) NVIDIA(0): been enabled on all display devices.)
[ 1313.761] (II) NVIDIA(GPU-0): Display (DELL E193FP (CRT-1)) does not support NVIDIA 3D
[ 1313.761] (II) NVIDIA(GPU-0): Vision stereo.
[ 1313.761] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 1313.761] (**) NVIDIA(0): device DELL E193FP (CRT-1) (Using EDID frequencies has
[ 1313.762] (**) NVIDIA(0): been enabled on all display devices.)
(EE) BUG: triggered 'if (inSignalContext)'
(EE) BUG: log.c:484 in LogVMessageVerb()
(EE) Warning: attempting to log data in a signal unsafe manner while in signal context.
Please update to check inSignalContext and/or use LogMessageVerbSigSafe() or ErrorFSigSafe().
The offending log format message is:
3rd Button detected: disabling emulate3Button
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x58a426]
(EE) 1: /usr/bin/X (LogVMessageVerb+0x195) [0x595765]
(EE) 2: /usr/bin/X (xf86Msg+0x8f) [0x48283f]
(EE) 3: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x7742) [0x7fac34707742]
(EE) 4: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x7a3b) [0x7fac34707a3b]
(EE) 5: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x432d) [0x7fac3470432d]
(EE) 6: /usr/bin/X (0x400000+0x75b97) [0x475b97]
(EE) 7: /usr/bin/X (0x400000+0x9f258) [0x49f258]
(EE) 8: /usr/lib/libpthread.so.0 (0x7fac3a418000+0xf1e0) [0x7fac3a4271e0]
(EE) 9: /usr/lib/libc.so.6 (__select+0x13) [0x7fac39149d33]
(EE) 10: /usr/bin/X (WaitForSomething+0x190) [0x587850]
(EE) 11: /usr/bin/X (0x400000+0x37bb1) [0x437bb1]
(EE) 12: /usr/bin/X (0x400000+0x2696a) [0x42696a]
(EE) 13: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7fac39089a15]
(EE) 14: /usr/bin/X (0x400000+0x26cad) [0x426cad]
(EE)
(II) 3rd Button detected: disabling emulate3Button
(EE) BUG: triggered 'if (inSignalContext)'
(EE) BUG: log.c:484 in LogVMessageVerb()
(EE) Warning: attempting to log data in a signal unsafe manner while in signal context.
Please update to check inSignalContext and/or use LogMessageVerbSigSafe() or ErrorFSigSafe().
The offending log format message is:
Option "%s"
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x58a426]
(EE) 1: /usr/bin/X (LogVMessageVerb+0x195) [0x595765]
(EE) 2: /usr/bin/X (xf86DrvMsgVerb+0x7d) [0x48116d]
(EE) 3: /usr/bin/X (0x400000+0x7742b) [0x47742b]
(EE) 4: /usr/bin/X (0x400000+0x77a15) [0x477a15]
(EE) 5: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x89e3) [0x7fac347089e3]
(EE) 6: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x55ad) [0x7fac347055ad]
(EE) 7: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x67ef) [0x7fac347067ef]
(EE) 8: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x43f6) [0x7fac347043f6]
(EE) 9: /usr/bin/X (0x400000+0x75b97) [0x475b97]
(EE) 10: /usr/bin/X (0x400000+0x9f258) [0x49f258]
(EE) 11: /usr/lib/libpthread.so.0 (0x7fac3a418000+0xf1e0) [0x7fac3a4271e0]
(EE) 12: /usr/lib/libc.so.6 (__select+0x13) [0x7fac39149d33]
(EE) 13: /usr/bin/X (WaitForSomething+0x190) [0x587850]
(EE) 14: /usr/bin/X (0x400000+0x37bb1) [0x437bb1]
(EE) 15: /usr/bin/X (0x400000+0x2696a) [0x42696a]
(EE) 16: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7fac39089a15]
(EE) 17: /usr/bin/X (0x400000+0x26cad) [0x426cad]
(EE)
(EE) BUG: triggered 'if (inSignalContext)'
(EE) BUG: log.c:484 in LogVMessageVerb()
(EE) Warning: attempting to log data in a signal unsafe manner while in signal context.
Please update to check inSignalContext and/or use LogMessageVerbSigSafe() or ErrorFSigSafe().
The offending log format message is:
%s: Setting mouse protocol to "%s"
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x58a426]
(EE) 1: /usr/bin/X (LogVMessageVerb+0x195) [0x595765]
(EE) 2: /usr/bin/X (xf86Msg+0x8f) [0x48283f]
(EE) 3: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x8c35) [0x7fac34708c35]
(EE) 4: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x55ad) [0x7fac347055ad]
(EE) 5: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x67ef) [0x7fac347067ef]
(EE) 6: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x43f6) [0x7fac347043f6]
(EE) 7: /usr/bin/X (0x400000+0x75b97) [0x475b97]
(EE) 8: /usr/bin/X (0x400000+0x9f258) [0x49f258]
(EE) 9: /usr/lib/libpthread.so.0 (0x7fac3a418000+0xf1e0) [0x7fac3a4271e0]
(EE) 10: /usr/lib/libc.so.6 (__select+0x13) [0x7fac39149d33]
(EE) 11: /usr/bin/X (WaitForSomething+0x190) [0x587850]
(EE) 12: /usr/bin/X (0x400000+0x37bb1) [0x437bb1]
(EE) 13: /usr/bin/X (0x400000+0x2696a) [0x42696a]
(EE) 14: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7fac39089a15]
(EE) 15: /usr/bin/X (0x400000+0x26cad) [0x426cad]
(EE)
(WW) Warned 3 times about sigsafe logging. Will be quiet now.
(II) mouse1: Setting mouse protocol to "PS/2"
(II) 3rd Button detected: disabling emulate3Button
(II) Mouse autoprobe: selecting PS/2 protocol
(EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x58a426]
(EE) 1: /usr/bin/X (mieqEnqueue+0x26b) [0x56b78b]
(EE) 2: /usr/bin/X (0x400000+0x4c632) [0x44c632]
(EE) 3: /usr/bin/X (xf86PostButtonEvent+0xd6) [0x485f26]
(EE) 4: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x7251) [0x7fac34707251]
(EE) 5: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x7a3b) [0x7fac34707a3b]
(EE) 6: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x432d) [0x7fac3470432d]
(EE) 7: /usr/bin/X (0x400000+0x75b97) [0x475b97]
(EE) 8: /usr/bin/X (0x400000+0x9f258) [0x49f258]
(EE) 9: /usr/lib/libpthread.so.0 (0x7fac3a418000+0xf1e0) [0x7fac3a4271e0]
(EE) 10: /usr/lib/libc.so.6 (__select+0x13) [0x7fac39149d33]
(EE) 11: /usr/bin/X (WaitForSomething+0x190) [0x587850]
(EE) 12: /usr/bin/X (0x400000+0x37bb1) [0x437bb1]
(EE) 13: /usr/bin/X (0x400000+0x2696a) [0x42696a]
(EE) 14: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7fac39089a15]
(EE) 15: /usr/bin/X (0x400000+0x26cad) [0x426cad]
(EE)
(EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack.
(EE) [mi] mieq is *NOT* the cause. It is a victim.
(EE) [mi] EQ overflow continuing. 100 events have been dropped.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x58a426]
(EE) 1: /usr/bin/X (0x400000+0x4c632) [0x44c632]
(EE) 2: /usr/bin/X (xf86PostButtonEvent+0xd6) [0x485f26]
(EE) 3: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x7251) [0x7fac34707251]
(EE) 4: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x7a3b) [0x7fac34707a3b]
(EE) 5: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x432d) [0x7fac3470432d]
(EE) 6: /usr/bin/X (0x400000+0x75b97) [0x475b97]
(EE) 7: /usr/bin/X (0x400000+0x9f258) [0x49f258]
(EE) 8: /usr/lib/libpthread.so.0 (0x7fac3a418000+0xf1e0) [0x7fac3a4271e0]
(EE) 9: /usr/lib/libc.so.6 (__select+0x13) [0x7fac39149d33]
(EE) 10: /usr/bin/X (WaitForSomething+0x190) [0x587850]
(EE) 11: /usr/bin/X (0x400000+0x37bb1) [0x437bb1]
(EE) 12: /usr/bin/X (0x400000+0x2696a) [0x42696a]
(EE) 13: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7fac39089a15]
(EE) 14: /usr/bin/X (0x400000+0x26cad) [0x426cad]
(EE)
(EE) [mi] EQ overflow continuing. 200 events have been dropped.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x58a426]
(EE) 1: /usr/bin/X (0x400000+0x4c632) [0x44c632]
(EE) 2: /usr/bin/X (xf86PostButtonEvent+0xd6) [0x485f26]
(EE) 3: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x7251) [0x7fac34707251]
(EE) 4: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x7a3b) [0x7fac34707a3b]
(EE) 5: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x432d) [0x7fac3470432d]
(EE) 6: /usr/bin/X (0x400000+0x75b97) [0x475b97]
(EE) 7: /usr/bin/X (0x400000+0x9f258) [0x49f258]
(EE) 8: /usr/lib/libpthread.so.0 (0x7fac3a418000+0xf1e0) [0x7fac3a4271e0]
(EE) 9: /usr/lib/libc.so.6 (__select+0x13) [0x7fac39149d33]
(EE) 10: /usr/bin/X (WaitForSomething+0x190) [0x587850]
(EE) 11: /usr/bin/X (0x400000+0x37bb1) [0x437bb1]
(EE) 12: /usr/bin/X (0x400000+0x2696a) [0x42696a]
(EE) 13: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7fac39089a15]
(EE) 14: /usr/bin/X (0x400000+0x26cad) [0x426cad]
(EE)
(EE) [mi] EQ overflow continuing. 300 events have been dropped.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x58a426]
(EE) 1: /usr/bin/X (0x400000+0x4c632) [0x44c632]
(EE) 2: /usr/bin/X (xf86PostButtonEvent+0xd6) [0x485f26]
(EE) 3: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x7251) [0x7fac34707251]
(EE) 4: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x7a3b) [0x7fac34707a3b]
(EE) 5: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x432d) [0x7fac3470432d]
(EE) 6: /usr/bin/X (0x400000+0x75b97) [0x475b97]
(EE) 7: /usr/bin/X (0x400000+0x9f258) [0x49f258]
(EE) 8: /usr/lib/libpthread.so.0 (0x7fac3a418000+0xf1e0) [0x7fac3a4271e0]
(EE) 9: /usr/lib/libc.so.6 (__select+0x13) [0x7fac39149d33]
(EE) 10: /usr/bin/X (WaitForSomething+0x190) [0x587850]
(EE) 11: /usr/bin/X (0x400000+0x37bb1) [0x437bb1]
(EE) 12: /usr/bin/X (0x400000+0x2696a) [0x42696a]
(EE) 13: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7fac39089a15]
(EE) 14: /usr/bin/X (0x400000+0x26cad) [0x426cad]
(EE)
(EE) [mi] EQ overflow continuing. 400 events have been dropped.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x58a426]
(EE) 1: /usr/bin/X (0x400000+0x4c632) [0x44c632]
(EE) 2: /usr/bin/X (xf86PostButtonEvent+0xd6) [0x485f26]
(EE) 3: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x7251) [0x7fac34707251]
(EE) 4: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x7a3b) [0x7fac34707a3b]
(EE) 5: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x432d) [0x7fac3470432d]
(EE) 6: /usr/bin/X (0x400000+0x75b97) [0x475b97]
(EE) 7: /usr/bin/X (0x400000+0x9f258) [0x49f258]
(EE) 8: /usr/lib/libpthread.so.0 (0x7fac3a418000+0xf1e0) [0x7fac3a4271e0]
(EE) 9: /usr/lib/libc.so.6 (__select+0x13) [0x7fac39149d33]
(EE) 10: /usr/bin/X (WaitForSomething+0x190) [0x587850]
(EE) 11: /usr/bin/X (0x400000+0x37bb1) [0x437bb1]
(EE) 12: /usr/bin/X (0x400000+0x2696a) [0x42696a]
(EE) 13: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7fac39089a15]
(EE) 14: /usr/bin/X (0x400000+0x26cad) [0x426cad]
(EE)
(EE) [mi] EQ overflow continuing. 500 events have been dropped.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x58a426]
(EE) 1: /usr/bin/X (0x400000+0x4c632) [0x44c632]
(EE) 2: /usr/bin/X (xf86PostMotionEvent+0xd0) [0x485a60]
(EE) 3: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x7497) [0x7fac34707497]
(EE) 4: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x7a3b) [0x7fac34707a3b]
(EE) 5: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x432d) [0x7fac3470432d]
(EE) 6: /usr/bin/X (0x400000+0x75b97) [0x475b97]
(EE) 7: /usr/bin/X (0x400000+0x9f258) [0x49f258]
(EE) 8: /usr/lib/libpthread.so.0 (0x7fac3a418000+0xf1e0) [0x7fac3a4271e0]
(EE) 9: /usr/lib/libc.so.6 (__select+0x13) [0x7fac39149d33]
(EE) 10: /usr/bin/X (WaitForSomething+0x190) [0x587850]
(EE) 11: /usr/bin/X (0x400000+0x37bb1) [0x437bb1]
(EE) 12: /usr/bin/X (0x400000+0x2696a) [0x42696a]
(EE) 13: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7fac39089a15]
(EE) 14: /usr/bin/X (0x400000+0x26cad) [0x426cad]
(EE)
(EE) [mi] EQ overflow continuing. 600 events have been dropped.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x58a426]
(EE) 1: /usr/bin/X (0x400000+0x4c632) [0x44c632]
(EE) 2: /usr/bin/X (xf86PostMotionEvent+0xd0) [0x485a60]
(EE) 3: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x7497) [0x7fac34707497]
(EE) 4: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x7a3b) [0x7fac34707a3b]
(EE) 5: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x432d) [0x7fac3470432d]
(EE) 6: /usr/bin/X (0x400000+0x75b97) [0x475b97]
(EE) 7: /usr/bin/X (0x400000+0x9f258) [0x49f258]
(EE) 8: /usr/lib/libpthread.so.0 (0x7fac3a418000+0xf1e0) [0x7fac3a4271e0]
(EE) 9: /usr/lib/libc.so.6 (__select+0x13) [0x7fac39149d33]
(EE) 10: /usr/bin/X (WaitForSomething+0x190) [0x587850]
(EE) 11: /usr/bin/X (0x400000+0x37bb1) [0x437bb1]
(EE) 12: /usr/bin/X (0x400000+0x2696a) [0x42696a]
(EE) 13: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7fac39089a15]
(EE) 14: /usr/bin/X (0x400000+0x26cad) [0x426cad]
(EE)
(EE) [mi] EQ overflow continuing. 700 events have been dropped.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x58a426]
(EE) 1: /usr/bin/X (0x400000+0x4c632) [0x44c632]
(EE) 2: /usr/bin/X (xf86PostMotionEvent+0xd0) [0x485a60]
(EE) 3: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x7497) [0x7fac34707497]
(EE) 4: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x7a3b) [0x7fac34707a3b]
(EE) 5: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x432d) [0x7fac3470432d]
(EE) 6: /usr/bin/X (0x400000+0x75b97) [0x475b97]
(EE) 7: /usr/bin/X (0x400000+0x9f258) [0x49f258]
(EE) 8: /usr/lib/libpthread.so.0 (0x7fac3a418000+0xf1e0) [0x7fac3a4271e0]
(EE) 9: /usr/lib/libc.so.6 (__select+0x13) [0x7fac39149d33]
(EE) 10: /usr/bin/X (WaitForSomething+0x190) [0x587850]
(EE) 11: /usr/bin/X (0x400000+0x37bb1) [0x437bb1]
(EE) 12: /usr/bin/X (0x400000+0x2696a) [0x42696a]
(EE) 13: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7fac39089a15]
(EE) 14: /usr/bin/X (0x400000+0x26cad) [0x426cad]
(EE)
(EE) [mi] EQ overflow continuing. 800 events have been dropped.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x58a426]
(EE) 1: /usr/bin/X (0x400000+0x4c632) [0x44c632]
(EE) 2: /usr/bin/X (xf86PostButtonEvent+0xd6) [0x485f26]
(EE) 3: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x7251) [0x7fac34707251]
(EE) 4: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x7a3b) [0x7fac34707a3b]
(EE) 5: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x432d) [0x7fac3470432d]
(EE) 6: /usr/bin/X (0x400000+0x75b97) [0x475b97]
(EE) 7: /usr/bin/X (0x400000+0x9f258) [0x49f258]
(EE) 8: /usr/lib/libpthread.so.0 (0x7fac3a418000+0xf1e0) [0x7fac3a4271e0]
(EE) 9: /usr/lib/libc.so.6 (__select+0x13) [0x7fac39149d33]
(EE) 10: /usr/bin/X (WaitForSomething+0x190) [0x587850]
(EE) 11: /usr/bin/X (0x400000+0x37bb1) [0x437bb1]
(EE) 12: /usr/bin/X (0x400000+0x2696a) [0x42696a]
(EE) 13: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7fac39089a15]
(EE) 14: /usr/bin/X (0x400000+0x26cad) [0x426cad]
(EE)
(EE) [mi] EQ overflow continuing. 900 events have been dropped.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x58a426]
(EE) 1: /usr/bin/X (0x400000+0x4c632) [0x44c632]
(EE) 2: /usr/bin/X (xf86PostButtonEvent+0xd6) [0x485f26]
(EE) 3: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x7251) [0x7fac34707251]
(EE) 4: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x7a3b) [0x7fac34707a3b]
(EE) 5: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x432d) [0x7fac3470432d]
(EE) 6: /usr/bin/X (0x400000+0x75b97) [0x475b97]
(EE) 7: /usr/bin/X (0x400000+0x9f258) [0x49f258]
(EE) 8: /usr/lib/libpthread.so.0 (0x7fac3a418000+0xf1e0) [0x7fac3a4271e0]
(EE) 9: /usr/lib/libc.so.6 (__select+0x13) [0x7fac39149d33]
(EE) 10: /usr/bin/X (WaitForSomething+0x190) [0x587850]
(EE) 11: /usr/bin/X (0x400000+0x37bb1) [0x437bb1]
(EE) 12: /usr/bin/X (0x400000+0x2696a) [0x42696a]
(EE) 13: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7fac39089a15]
(EE) 14: /usr/bin/X (0x400000+0x26cad) [0x426cad]
(EE)
(II) mouse1: Setting mouse protocol to "PS/2"
(II) mouse1: Setting mouse protocol to "PS/2"
(II) mouse1: Setting mouse protocol to "PS/2"
(II) mouse1: Setting mouse protocol to "PS/2"
(II) mouse1: Setting mouse protocol to "PS/2"
(II) mouse1: Setting mouse protocol to "PS/2"
(II) mouse1: Setting mouse protocol to "PS/2"
(II) mouse1: Setting mouse protocol to "PS/2"
(II) mouse1: Setting mouse protocol to "PS/2"
(II) mouse1: Setting mouse protocol to "PS/2"
(II) mouse1: Setting mouse protocol to "PS/2"
(II) mouse1: Setting mouse protocol to "PS/2"
(II) mouse1: Setting mouse protocol to "PS/2"
(II) mouse1: Setting mouse protocol to "PS/2"
(II) mouse1: Setting mouse protocol to "PS/2"
(II) 3rd Button detected: disabling emulate3Button
(EE) [mi] EQ overflow continuing. 1000 events have been dropped.
(EE) [mi] No further overflow reports will be reported until the clog is cleared.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x58a426]
(EE) 1: /usr/bin/X (0x400000+0x4c632) [0x44c632]
(EE) 2: /usr/bin/X (xf86PostButtonEvent+0xd6) [0x485f26]
(EE) 3: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x7251) [0x7fac34707251]
(EE) 4: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x7a3b) [0x7fac34707a3b]
(EE) 5: /usr/lib/xorg/modules/input/mouse_drv.so (0x7fac34700000+0x432d) [0x7fac3470432d]
(EE) 6: /usr/bin/X (0x400000+0x75b97) [0x475b97]
(EE) 7: /usr/bin/X (0x400000+0x9f258) [0x49f258]
(EE) 8: /usr/lib/libpthread.so.0 (0x7fac3a418000+0xf1e0) [0x7fac3a4271e0]
(EE) 9: /usr/lib/libc.so.6 (__select+0x13) [0x7fac39149d33]
(EE) 10: /usr/bin/X (WaitForSomething+0x190) [0x587850]
(EE) 11: /usr/bin/X (0x400000+0x37bb1) [0x437bb1]
(EE) 12: /usr/bin/X (0x400000+0x2696a) [0x42696a]
(EE) 13: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7fac39089a15]
(EE) 14: /usr/bin/X (0x400000+0x26cad) [0x426cad]
(EE)
(II) Mouse autoprobe: selecting PS/2 protocol
(II) mouse1: Setting mouse protocol to "PS/2"
(II) mouse1: Setting mouse protocol to "PS/2"
[ 1330.150] [mi] Increasing EQ size to 512 to prevent dropped events.
[ 1330.151] [mi] EQ processing has resumed after 1558 dropped events.
[ 1330.151] [mi] This may be caused my a misbehaving driver monopolizing the server's resources.
[ 1365.538] (II) UnloadModule: "kbd"
[ 1365.538] (II) UnloadModule: "mouse"
[ 1365.554] Server terminated successfully (0). Closing log file.
Any help would be appreciated.
Last edited by l0vot (2013-01-04 23:15:53)

I used the endev driver for all of the input devices, and now the mice and keyboards work, however the arrow keys are mapped to other random keys on both keyboards. The up arrow on both keyboards is mapped to print screen, I may be able to fix that with xmodmap.
I can't seem to start seat 0 and 1 at the same time, and endev does weird things to my Logitech keyboard, so I used a roundabout way of starting both seats: first I activate seat one, and then switch to a different vt, which causes the x server to stop sending video to monitor one, but seat1 still grabbed keyboard1 and mouse1, then i use startx without any additional arguments, which activates screen0 by default and then hotplugs keyboard0 and mouse0 because they are available, but it does not interfere with seat1 because seat1 already grabbed all of it's devices. I open a terminal on seat0 and try to start seat1, which is already active, just not being displayed, so seat1 starts sending video to moniter1, it appears trying to start an x server on a screen that is already in use will fail, and drop you back into the vt that you tried to start it from, in this case it put me back in screen0 while allowing screen1 to be active.
This is a very crude method of getting both seats to work at the same time, and i stumbled upon this solution by accident, originally i made a multi-threaded program that should have activated both seats at the same time from the same vt, that did not work for some reason, so i will have to use my crude solution until i can find a better one. an answer to question 3 would probably help, i will do some more research on question3.
Last edited by l0vot (2013-01-05 20:26:54)

Problems and questions re merging of MobileMe and iCloud

Please bear with me - this is all rather complicated!
At sometime in my early years with Mac, I signed up for an Apple ID - can't even remember what it was. Many, many years ago at the beginning of the internet, I signed up for another Apple ID - it was <[email protected]>. Later, I bought/signed up for .Mac which later became MobileMe. When I first signed up, I had an Apple ID of <[email protected]>. At some time, I quit using the insightbb email and switched to Mail - my email address became <[email protected]>. Then MobileMe came along and wanted my address to be <[email protected]> but it did allow me to keep the mac.com address. I also had two aliases through MobileMe. I still occasionally need to use the insightbb.com account so while I never sign up for anything using that address, there are a few VERY old accounts I have that use it as it was the address with which I originally signed up. I don't remember which ones in order to change it, so I just keep it active and only rarely get email addressed to the insightbb acc't.
Today, I upgraded to Lion and then to iCloud. I used the "migrate from MobileMe to iCloud" format, and low and behold, it told me that my Apple ID is now <[email protected]>. This is going to cause me BIG problems as there is no way to merge Apple ID's!
My first question is how do I get back my correct AppleID for iCloud?
My second is I now have multiple accounts on my iPhone and iPad. I have an insightbb.com account - must keep it. But I also have my new iCloud account and I still have my MobileMe account. Should I delete these accounts? What has happened to my MobileMe aliases? I have subscriptions using them, too!
Aggghhh!!! I LOVED MobileME! So far, I HATE iCloud! I don't need these complications! Any advice on how to reconcile these problems?

I just got off the phone after an hour with Apple Support. The bottom line is that somehow iCloud has decided to use my .mac address as my Apple ID. Yes, I can change it, but if I do, I lose everything - contacts, mail, bookmarks, calendar - everything. For iTunes and this Community help forum, I will have to continue to use the insightbb Apple ID. They could not figure out how this happened, as for MobileMe, I ALWAYS used the insightbb Apple ID. Gremlins in moving from MobileMe to iCloud.
He did say that Apple is working very hard to figure out how to merge multiple Apple ID's as this is becoming more and more of a problem. So, until they sort it all out, at least I know what to do.

Problems and Questions using Time capsule for first time...

I recently purchased a new MBP 13" and time capsule. I hooked up time capsule to my router and made a backed up (slow) . I turned off Time Machine. Then, I hooked up my old mac via ethernet (faster, I learned), and mounted the sparsebundle via Shared in the Finder. I manually dragged and dropped the contents of my external harddrives(s) [connected to my old mac] to the sparsebundle. Thus;
[Mounted sparsebundle]
- Backups.backupdb
 - Mac Book Pro 13" <<< new mac time machine backups
 - 2012-11-25-5543
 - 2012-11-23-3453
 - 2012-11-19-6654
 - 2012-11-17-3422
- My Media Backup <<< Created new folder, Then dragged and dropped files from external disk
- My Business Harddrive <<< Created new folder, Then dragged and dropped files from external disk
- My Personal Harddrive <<< Created new folder, Then dragged and dropped files from external disk
Questions 1; Are external files manually moved to Time capsule "safe?"
ie. Will time capsule erase my files once it starts to run out of space? I read something about having to limit time machin'se sparsebundle size? Do I have to worry about this?
Question 2: Or, Is my setup wrong? Is the following workflow sound for Time Capsule?
I really want to consolidate all my data [external drives] to Time Capsule as my MBPro has limited space. As a avid amateur photographer, my drive fills up fast. Thus, I thought to use this as my workflow;
WORKFLOW;
- I take photos and transfer to my macbook pro. As the drive fills up, I edit and delete as necessary.
- Old media projects [photos / films] are moved to "My Media Backup" folder on Time Capsule and deleted on my macbook pro.
This way, the media files are still accessible through Time Machine, AND still accessible via shared folder on "My Media Backup". I am afraid that once the Time Capsule drive starts to fill up, files that are no longer on my computer will be overwritten in Time Machine, eventually.
- I also will from time to time backup "My Media Backup" folder on Time Capsule to an External Harddrive and move offsite for added security.
Problem 1; "resource temporarily unavailable"
My old mac, connected via ethernet sees the sparsebundle and mounts no problem. But after manually dropping files, my new mac doesn't connect and I get the dreaded "resource temporarily unavailable"; though it's not temporary as I can never connect. So, I cannot access the backup [manually dropped] files on Time Capsule from my new mac via wireless. Note: My new MacBook Pro 13" retina does not have ethernet port [I did not think to purchase adapters], Nor does it have firewire port for my old external firelite drives. Thus I have a new mac, but I haven't used it hardly at all as I cannot access any of my old data (without emailing everything).
Kind regards,

You have basically destroyed the sparsebundle. This is just wrong. The sparsebundle is created by TM for its exclusive use.. what it will do to the files inside it is a mystery.. but you cannot now delete them.. you have permission to create and copy the files to the sparse bundle but not to delete them.
M*rde. I was afraid of that. Makes sense that if you modify the sparsebundle file exterior of Time Machine; how could it know what changes were made? So, I've got to start over. (groan).
*** NOTE TO APPLE: Make it clear what NOT to do to the sparsebundle in the setup instructions.
It's too easy to simply mount the sparsebundle and drag and drop files I also wanted backed up. Apparently, this is a false method and can apparently ruin your sparsebundle and your valuable data.
If you wanted to copy files to the TC you should have created a new disk image..
http://pondini.org/TM/TCQ3.html
Thanks! This, I think, does exactly what I was trying to do manually. I'll mark problem solved.
Apple needs to address the gaping hole in the; functionality, ease of use, reliability, transparency of potential data loss if used incorrectly.
*** APPLE: Add to Time Machine.app a management tool to better manage shared space of manual backups and time capsule sparsebundles. In any case, in the installation if a time capsule, give the TC drive a special id/permissions or something that does not allow drag and drop to a sparsebundle (if this does indeed corrupt the integrity of the sparsebundle).
Since this could result in data loss, special attention needs to paid to;
 - Notifify the user of the potental of data loss
 - Prevent the casual and intermediate user of through special permissions or special disk id in the installation process (I've really no idea how it might work - I'll leave that up to Apple)
 - Create an interface to allow the user to do the tasks that everybody buys a the time machine for - back up data. No matter what the source; USB key, portable drive, temp space to organize large files. etc. An interface that won't let you screw up the sparsebundle like any idiot can do (me!)
Kind regards,

T30 Problems and Questions

Similar Messages

Maybe you are looking for