Switched From Analog TV to Digital

Finally made the switch from our old analog TV to a digital flat screen.  Do I still need the converter box or can I hook the incoming cable straight to the back of the new TV? If I still need a converter box is the one I had for the analog TV okay or will I need a new one?

Because Comcast's digital signal is encrypted, you still need a cable box to decrypt the signal and authorize the proper channels for your TV plan.
If you have a older cable box or DTA digital adapter, you can continue to use that and it will give you std def channels, the quality might not look as good on a high quality larger screen HDTV.
You can upgrade to a HD box so you see the HD channels available on your subscription.  HD boxes will connect to a HDTV with a HDMI cable to give you the HD picture quality.
You can swap the box at your local Comcast office, take the old box and remote with.  If you don't have HD service now on other boxes in the house, then you will need the HD technology fee on your accout at 9.95 a month, covers all boxes in the home.

Similar Messages

  • Sound Preferences: switches from Internal Speakers to Digital Out

    I've been having this problem recently. I sent the computer off to Apple a few weeks ago and it helped for a while, but no longer.
    My computer has a problem with it's sound output jack or something. Without inserting anything into the plug, the Sound will change for "Internal Speakers" to "Digital Out" and to "Built-in Output" in the Sound Preferences Panel.
    Any suggestions?
    Message was edited by: davidszcz

    I have a 4 month old macbook and experiencing the same problem. Just realized it after installing itunes 8 and since then having a stuttering audio playback problem too. When i plug my headphones into the audiojack the sound switches from headphones to speakers and back as well as itunes playing tracks in a stop and go mode. I repaired the rights several times, installed quicktime 7.5.5 again, reinstalled itunes 8 and for sure running the latest leopard version 10.5.5.
    Also thought it could be a hardware problem but after reading this it seems more software related.
    Any idea?

  • Switching from analog feedback to encoder feedback

    Greetings,
                    I am having problems with switching feedback sources in my Labview App.  I am using a 7344 board.  I initialize the board in encoder feedback as primary.  Then I am able to switch to analog feedback, but then the problem is when I switch back to encoder feedback it acts like it is still using analog feeback as a Primary.  I can only get it back to encoder feedback only if I reinitialize the controller.  I am disabling the axis before I am making config changes and then re enabling axis to run axis on both accounts.  However it doesn't seem to be getting back to encoder feedback.  Any Ideas?
    Wade

    Hey wade,
    As mentioned in this Forum Thread, you should be able to switch back and forth between feedback sources on the 733X motion controller by disabling/enabling the axis. However, this is what you say you are doing. Perhaps changing the order in which you make the feedback switch. What happens if you make the feedback change and then simple disable/enable the axis? Are you seeing this same behavior on all of your axis? What version of the NI Motion driver are you using?
    Hope this helps.
    -Ben
    WaterlooLabs

  • Switching from Digital Performer 7.24...?

    I have been using Digital Performer for 12+ years, but have been thinking about purchasing Logic Pro X for a variety of reasons.  I would love to hear from anyone who has done the same.  Have you found it easy to learn Logic, and how to use it to do the things you did with DP?  Was it worth the $199 to purchase Logic to try it?  If you have both DP and Logic, which one do you use the most, and why?
    Thanks for any opinions/comments about this.
    Michael

    I haven't used DP for ages, but what I hear from friends is that there are some key features that are not available in Logic. However, that is true when switching from any app A to app B. You just have to make a pro/con chart and see if there are any deal breakers.
    Logic always gets a bad rap for its steep learning curve. The main reason for that is that it has so many features to learn and most importantly, its open object-based structure. In my opinion, this is the most powerful feature from a power-user point of view because you can customize so many things. When you work with with it every day, you really start to appreciate it. For a seasonal user, this might be overkill.
    There is one important aspect about learning an app. It is often more difficult to learn a different app, that it is to learn a new app. You have to unlearn concepts and workflows which sometimes appear strange at first. That's why it is very important, for example, not to find where the new Record Button or Play Button is, but discover the many different actions that happen when you press those buttons and where to configure them (and knowing that you can configure them in the first place).
    As I mentioned, the different concepts and underlying architecture is the most important thing to wrap your head around it. I wrote a manual in my Graphically Enhanced Manuals (GEM) series, "Logic Pro X - How it Works", that explains those concepts with lots of graphics and diagrams that are not found in any other book or tutorial. I discuss and illustrate the various topics in great details, providing all the various commands for specific actions, not just one, so you can choose which one suits your workflow best.
    One more thing ...
    You can download GarageBand X for free. It is based on the same code as Logic Pro X (it is actually the new Logic Express). Although, most of the advanced features are not available, you still can get an overall feel for the app: layout, color codes, terminology, etc.
    Hope that helps
    Edgar Rothermich
    http://DingDingMusic.com/Manuals/
    'I may receive some form of compensation, financial or otherwise, from my recommendation or link.'

  • I just switch from tape to digital. The video  has a little bounce when played on tv. I copyied the DVD to a folder

    I just switch from tape to digital. The video  has a little bounce when played on tv. I copyied the DVD to a folder, and burned it to a dvd.
    I can see in bounce at the bottom of the screen.

    David
    Premiere Elements 11, 12, or 13 on Windows 7, 8, or 8.1 64 bit....
    You could go back to the project and, in the Edit area, scale out the bouncing bottom edge. I am assuming that it will be visible there.
    Then do another burn to folder, and then take the saved folder's VIDEO_TS to DVD disc with your 3rd party software, presumed ImgBurn.
    If you want to scale width and height together, then leave the check mark next to Constrain Proportions in Applied Effects Tab/Applied Effects Palette/Motion Panel expanded. If you want to scale width and height separately, the remove the check mark next to Constrain Proportions in Motion Panel expanded.
    Please let us know the results. We might consider the Crop Effect also. (fx Effects/Transform/Crop with edits of it int Applied Effects Tab/Applied Effects Palette/Crop Panel expanded).
    Thank you.
    ATR

  • AD5541/5542 Digital-to-Analog converters from Analog DEvices

    Dear Friends,
    Does anybody have experience programming in Labview the AD5541 or
    AD5542 boards (Digital-to-Analog converters) from Analog Devices (http://www.analog.com/en/prod/0%2C2877%2CAD5541%2C00.html)?
    LabView code examples or description of the general approach to this task would be much appreciated!
    Thanks in advance

    ampm <[email protected]> wrote in news:[email protected]:
    > Update: My PXI system has NI-6534 board which I can use
    > for digital output. But I need to perform Digital-to-Analog conversion
    > by the remote AD5541 board.Is there a way to do this?
    That's a chip, not a board. Get the data sheet, look at the logic
    diagrams, and you should be able to bit-bang the three logic inputs (well,
    two plus a chip select) with your 6534.
    Alternatively, the chip uses SPI communication. You can probably find some
    help by searching for SPI on the NI site. It also looks like a third party
    has a $200 solution the will let you do this via a parallel port, complete
    with labview drivers, at http://www.calbay.com/product16.html
    Scott
    Reverse name to reply

  • Using USB-8451, and AD7747 from Analog Devices to measure capacitance and convert the capacitance to digital output

    Hello,
    I am new to LabView and data aqusition. I have LabView 8.5.1 installed on my laptop, and I studied the Getting Started document of LabView, except the data aqusition chapter.
    I have microfabricated a differential capacitive sensor, and now I want to test the capabilities of my sensor.
    After asking NI engineers, I have been suggested to use USB-8451 with AD7747 (24-Bit Capacitance-to-Digital Converter) from Analog Devices because AD7747 has I2C serial interface.
    I have ordered USB-8451, AD7747, and Evaluation Board for AD7747. And I am waiting for them.
    Are there any suggestions about how to connect my differential capacitive sensor to AD7747, and eventually to USB-8451?
    You may want to know some further information to answer my question:
    *The sensor is similar to the sensor on pages 501, 514, and 515 of "Microsystem Design" book from author Stephen D. Senturia.
    *The datasheet for AD7747 can be reached from this link: http://www.analog.com/static/imported-files/data_sheets/AD7747.pdf
    *My purpose is to make a very precise and accurate "displacement measurement micodevice" by using "the change in the capacitance" during the motion of the mobile fingers of the sensor.
    As an initial challenge for myself, I will feel satisfied if I can measure the capacitance change in my sensor when I apply an external mechanical disturbance to my sensor. For example, there must be a change in capacitance if I just swing my hand from top of the sensor region.
    I am looking forward for your reply,
    Thanks in advance,
    Sincerely,
    sriverfxtr

    Hi Aaron,
    Here you go, this is made with a USB-8452.
    When you run the code tick the power en dac enable box on.
    Maybe you can help me with my problem, I want to use a fiber to sense light from a led.
    Do you use any fiber hardware with the TCS3414?
    gr,
    Attachments:
    TCS3414.vi ‏63 KB

  • E_LIC_ALREADY_FULFILLED_BY_ANOTHER_USER after I switched from authorized by computer to authorized by ID on the same book,  how can I open open that same book?  I downloaded the book again, reinstalled the digital edition but no help? If anybody can answe

    E_LIC_ALREADY_FULFILLED_BY_ANOTHER_USER after I switched from authorized by computer to authorized by ID on the same book,  how can I open open that same book?  I downloaded the book again, reinstalled the digital edition but no help? If anybody can answer that would be a great help.

    Hi Shreya,
    That answer seems to work in purchased books but in my case I dont know who is the ebook provider in lebrary.  I asked library people and they did not give me any contact to reset the activation.  I will try again to find out that contact. I was wondering if there is any way at our side so we can fix this.  Probably there is nothing. Thanks anyway.

  • Switching of analog measurment signals

    Hello,
    in our LabView applications we have to measure several voltages and
    currents. We use a AT MIO 16 E 10 DAQ card, but it is not good enough
    for 2 voltages 2 currents. Therefore, we use exernal GPIB measuring
    instruments for them (Keithley 2000 a.a.).
    However, I think we could come along with only one Keithley 2000 since
    the timing is no issue (1 scan per sec is enough). I need some switch
    controlled by LabView that switches the analog measuring signals to
    two Keithley 2000 (analog) inputs (one for voltage, the other for
    current measurement, respectively).
    I found out that I can't do this with the DAQ card alone. I can't use
    the analog outputs since I don't want a A/D - D/A conversion included.
    Note that the measuring volta
    ges can be ~100 mV.
    But I could be wrong since I am actually a software guy so please
    correct me if this is possible with the DAQ card only.
    My idea is as follows:
    I could use the digital outputs of the DAQ card and connect them to
    some opto coupler or relais with TTL input. The opto couplers or
    relais would switch the analog measuring signals according to the
    digital outputs of the DAQ card and finally according to LabView.
    I couldn't find such a switcher board in the NI catalog. They have
    switchers, but they seem to switch voltages >3V only. But maybe
    someone suggests a board from another company which suits better.
    I just wouldn't like so much soldering my own board since my knowlege
    of opto couplers, relais and hardware in general is really limited.
    Best regards
    Johannes

    Hi Marcus,
    thanks for your answer.
    I was probably not clear about what I want. The solutions you suggest
    seem to be far to complex. As Nirmal pointed out, I actually only need
    high quality optocouplers, no more.
    On Thu, 25 Mar 2004 09:30:26 -0600 (CST), Marcus G wrote:
    >Hello Johannes,
    >It sounds like you're setting up a system that requires four analog
    >inputs (two voltage and two current), and you would like to use an
    >analog trigger to switch between which signals are measured.
    No. I just want to use the digital outputs of the DAQ card to switch
    optocouplers. The optocouplers will switch between several analog
    measuring signals. They should route these signals to one analog input
    of a Keithley 2000.
    >There are
    >several options of
    how you can set up such a system.
    >In terms of measuring the four analog inputs, you should be able to do
    >this with a DAQ card alone. Many of our cards, including the
    >AT-MIO-16E-10 (also called a 6020E), have 16 analog input channels
    >that have an input range of +/-10V.
    I don't want to measure the four analog inputs with the DAQ card since
    it isn't precise enough. The input range is too high for some of the
    analog inputs and the resolution is too low. Also, I can't modify the
    input range of the DAQ card at runtime. Therfore, we are using
    external instruments (Keithley 2000 a.a.) for the measurements. My
    idea was to only use one instrument for the four analog input signals.
    Then I must provide the switching between the four analog inputs. The
    idea was to control (switch) some optocouplers with the digital
    outputs of the DAQ card. The optocouplers should route one of the four
    analog signals to one Keithley 2000. I set the digital outputs of the
    DAQ card in the LabView program. Also, t
    he LabView program configures
    the Keithley 2000 and reads the measuring values from the GPIB. That's
    all.
    Regards
    Johannes

  • I switched from vista and lost all my music and stuff I can't get it back nor can i get all my purchesed items back. Is there anyway I can??

    I really need this fixed its driving me crazy. I wish iTunes had a way of taking all the songs from the iPod and just downloading them to the itunes without having to delete all that is on there. I really want my Purchesed Items back. I wasted probably over 100$ on this....

    Okay, doing my best to ignore the EXTREMELY annoying font you chose to use.
    Is there a reason why you did not create a backup of your media and other important files before switching from Vista?
    It is the users responsibility to back up their media, it is NOT Apple's responsibility.
    When you purchase CD's or DVD's, if you lose them, you repurchase them.  Same deal with digital media.
    If you have a backup of your media, simply copy the files from the backup to your computer.
    If you still have access to your old computer, simply copy the files from it to your new computer.

  • I am writing to this forum to ask for help in determining whether Aperture will satisfy my needs when I switch from Windows to MAC in the near future.

     I am writing to this forum to ask for help in determining whether Aperture will satisfy my needs when I switch from Windows to MAC in the near future.  
    I am currently using Photoshop Elements 8 on Windows 7.  After several years of use, I am self taught and adequately proficient for an amateur.  What I didn't realize (until I started researching my upcoming migration on the Internet) is that I actually use PE8 for two functions: digital asset management and digital editing. 
    Regarding Digital Asset Management: My research leads me to understand that PE on MAC does not provide the same level of organizational capability that I am used to having on Windows, instead providing Adobe's Bridge which does not look very robust.  Furthermore, iPhoto, which come on MAC will not support the hierarchical keyword tagging that I require to organize my library of photos. The two SW applications which I am thinking of switching to are either Aperture or Adobe's Lightroom.  Frankly, I'm thinking that it would be smoother to stay within the Apple product line. 
    So the remaining question is whether Aperture will support my digital editing needs. The tweaks that I do to my photos are not very complex (no, I do not want to put people's heads on other animal bodies).  But could someone who uses Aperture tell me whether It will allow me to do the following kinds of edits?:
    - If I have a photo where someone's face is too shadowed, can I lighten just that person's face, and leave the rest of the photo as-is?  
    - if I have a photo where the background is cluttered (eg, 2 people in front of the Parthenon which is undergoing renovation), can I remove just the construction cranes?  
    - Can it splice together several separate photos to give a panoramic?  
    If, once I get Aperture, I find that it cannot enable the kinds of editing that I do, I would probably get PE11 in the future. However, if people in this forum tell me that Aperture will definitely not  support the kinds of editing which I've described in the previous paragraph, I would prefer to get PE11 with my initial configuration (since someone will be helping me with my migration).  
    Thanks in advance for your consideration and help! 

    I am concerned, however,  about using a non-Apple Digital Asset Manager in OSX. I would really like to avoid integration problems. Is using PE11 to import and catalog my digital photos likely to cause conflicts?
    Thanks for any insight on this
    Amy,
    Not so much conflicts as maybe a little less seamless integration with Apple software and perhaps some third-party software providers in the Mac App Store where some programs build in direct access to iPhoto and Aperture libraries for getting images into those programs easily. Typically, there is a manual command to go to Finder (think Windows Explorer) to browse folders.
    One caution to mention however, is that the organization you set-up in PE Organizer is unlikely to transfer over to either iPhoto or Aperture if you decide to change at some point.
    The only real stumbling block that I see in your opening comment is that you want hierarchical keywording (Kirby or Léonie can go into the details on keywording limitations as I stay at one level). If you can work with the keywording schemes of either iPhoto or Aperture, then using PE for your external editor (either program supports setting an external editor) would probably be ideal since you know PE well. This is the idea with the Mac App Store version of PE (editor with no organizer).
    Note - I use Photoshop CS6 (full version) with Aperture and it works really well. The only downside is that Aperture has to make either a TIFF or PSD file to send to an external editor so that the original file is protected by not sending it to the pixel editor. While TIFF or PSD files protect the integrity of the image information without degrading it, they are typically much larger file sizes on disk than either RAW or JPEG files. Therefore, your library size (iPhoto or Aperture) will balloon quite a bit if you send a lot of files to external editors.
    One other possibility for an external editor would be a program called Pixelmator. It is pretty similar to early versions of Photoshop, but built for Mac. Other than the panoramics you want, it will do most pixel editing that PE can do. It is not an organizer, so it is built to go with either iPhoto or Aperture. It does have differences in how you complete certain procedures, so there is bit of a learning curve when you are used to doing it the Adobe way.

  • Analog Signal to Digital a Primer

    Many users have analog material sitting around, and they would like to get it into digital form, so that it can be edited. As this material is below SD (Standard Definition) quality, I will address the methods for digitizing it, so that it can be best edited in a DV Project. The output can be a DVD-Video, or other format, depending on what one wishes.
    The process of getting this analog material into a digital form, is referred to as Capturing, and it is digitizing the analog material and writing it to a file, that can be edited.
    One will need some method of getting the analog signals into digital form, and for connecting the analog output from their analog playback device to the computer. Though the analog signal could come from all sorts of devices, I’ll use a VHS tape deck in this example.
    Since a VHS tape deck does not have an A-D (Analog to Digital) processor, and also does not have a a digital signal Out, one needs something in between it, and the computer. That “something” serves two needs: mechanical connection of cables and the ability to convert the analog to digital for use in an NLE (Non Linear Editor). That “something” can be a digital video camera with pass-through capabilities, a device, called a “bridge,” or a capture card inserted into a bus slot in the computer. All three have pluses and minuses.
    The first two methods rely on one having a FireWire connection on the computer and will use the Capture module in the NLE software.
    The digital video camera route is good, as one already owns it. Having one with pass-through capabilities is getting more difficult. The camera also has to have FireWire (FW, IEEE-1394a, or iLink) output, and the computer must have a matching connection.
    An A-D bridge will do the same thing: allow one to connect the analog cables to one end/side, process the analog signals to digital and then output via FW to the computer. There are various such bridges available and two of the most often recommended makes/models are: the ADS-Pryo, and theCanopus/Grass Valley ADVC-110. Products, like the Dazzle lineup, just do not seem to work, or work well. I would avoid such.
    A dedicated capture card performs the same task, with one exception. The card will mount into an empty PCI slot on the MoBo, and have inputs for the analog cables. The card will have chips on it, to digitize the analog signals and feed these to the computer via the PCI slot. These do not connect via FW, but have one drawback: they must, in virtually every instance, use additional software to do the actual Capture, as most NLE’s cannot directly see and work with them. Some of the included software Capture programs are better, than others. One common issue with many of these cards is a loss of sync, between the Audio and the Video. This is usually static OOS (Out Of Sync), in that it is usually off by a fixed number of frames, and does not drift over time. This can be fixed in the NLE, but is extra work. This ARTICLE will give you tips on correcting OOS.
    Now, we are ready to begin the Capture, as our equipment and cables are all ready to go. We have a big decision in front of us - what format/CODEC do we use to Capture our digital files? Since we are doing an SD Project with non-HD (High Def) material, there is one fine choice: DV-AVI Type II w/ 48KHz 16-bit PCM/WAV Audio, using the DV/DVC CODEC. These files will be approximately 13GB / hour of Duration. Storage will need to be considered. These files are also I-frame, meaning that each “Frame” is rendered and available, so that frame-accurate editing is possible. The NLE will not need to do any processing, or conversion of these files, as even the Audio is ready for DVD-Video. Note: there will still be Conforming and the generation of PEK (Waveform Display) files, but the NLE will be able to do this quickly and efficiently.
    Using AVI Uncompressed will get you nothing that you can see, other than larger files. Do NOT use any compressed format/CODEC, like MPEG-2, WMV, MOV, etc., as these will loose data from an already inferior source, and will then need conversion to be used, either with a stand-alone conversion program, or internally by the NLE. You loose quality and then have more work to be done. Do not let the temptation of smaller files lure you into using anything but DV-AVI Type II, and just accommodate the larger file sizes.
    With the file format/CODEC decision made, the cables and devices hooked up, we’re ready to start the Capture. The exact operation will depend on what our equipment choice has been. See above for talk about additional Capture software, if one uses a capture card. Otherwise, we should be able to use the Capture module of our NLE. The first issue is that we will NOT have Device Control, as we would with a Capture from a miniDV tape-based digital camera, where we can control the mechanical aspects of the camera, during this process. As our VHS deck is hooked up to the A-D bridge, or digital camera w/ pass-through, via analog cables, our control signals cannot be sent to it. One would cue up the tape in the VHS deck, and then choose Record/Capture in the NLE’s Capture module, starting the Capture. Instantly, they would hit Play on the VHS deck, or via that deck’s remote control. This is easier the second time that one does it. I sit with the mouse in my right hand, poised over the Record/Capture button, and the VHS deck’s remote in my left hand, finger hovering over Play. It’s then a 1 - 2 push, and all starts. One can stop the Capture, if an unwanted section of tape comes up. The Capture module of the NLE will direct us on how to proceed from there, should more Captures be wanted. Some will just start up at a later point, and write an additional file for that portion of the tape, but some might require that one basically sets up a new Capture session One should investigate just what their NLE will require for doing multiple Capture sessions from one VHS tape.
    When done, one closes the Capture module, and then navigates to the location that these DV-AVI Type II files have been stored in, and Imports them into the Project. This differs slightly from doing the Capture from a miniDV tape camera, as those Captured files are already in the Project.
    Edit away, and Export/Share to the necessary output settings, file type and CODEC.
    What about those VHS - DVD decks, the ones that will burn a DVD directly from the VHS tape? They seem so simple to use, and for the most part are. However, those DVD-Video discs, contain pretty heavily-compressed MPEG-2 AV streams. These MPEG-2's, besides being compressed, are in aGOP structure and are muxed (Multiplexed into one file with both a Video & Audio stream), plus there is often some Menus and navigation in the first VOB, the main container components of a DVD-Video. Many NLE’s can Import the VOB’s, and basically rip the MPEG-2 out of them, but that first VOB can be highly problematic, due to the way that most of those decks do the Menus and navigation. It is seldom 100% DVD-compliant by the DVD-specs. This can be a major problem. This ARTICLE will give you some background and tips on DVD VOB's.
    Those dual-decks are good for doing one thing, regarding the DVD’s that they produce - provide one with an archival DVD-Video of the VHS tape, and not to be edited. However, the VHS side of these works well with an A-D bridge, just like a pure VHS deck does. I would strongly recommend that one does NOT use the DVD-Video portion of these, if editing will be desired. They cause many more problems, than they solve - just use them for an “archive” copy of the tape to a DVD-Video, for playback on a computer via DVD software or a set-top player, hooked to a TV.
    What about film? Well, film is obviously analog, and one needs to digitize this to edit on the computer. The process of this digitizing is referred to as telecineing the film. While one can buy equipment to do this, it is expensive, and involves a lot of setup and testing to get the job done. There are many service bureaus, that offer telecining. Some are better than others. The main considerations are: care in handling of fragile film, how the telecining is done, i.e. frame by frame w/ a liquid gate, or just by straight projection, and then output format for the digitized files. Some of these services will offer a DVD-Video disc. Do not be tempted to do this. See above. Others will offer to write these digitized files to a miniDV tape, and this is just fine. One does then need a miniDV camera, or miniDV tape deck, to then do the Capture from, but the quality and editability will be preserved. The final delivery format would be to put these DV-AVI Type II files onto an external HDD. This saves one from having to do the Capture from miniDV tape, having to have a miniDV camera, or miniDV deck, and only Importing of those files would be required to get them into the Project. Many of these service bureaus will either sell you the external, or use one provided to them. Check out specifications for things like format of the external. FAT-32 will limit the file sizes to ~ 4GB max, and NTSF will have no such limitations. However, if the service bureau is on Mac, and you’re on the PC, their Mac’s can ONLY see FAT-32 HDD’s. Talk this over with the service bureau first, so that there are no surprises later on.
    Hope that this helps,
    Hunt
    PS - also see this FAQ Entry for more detail.

    the_wine_snob wrote:
     Products, like the Dazzle lineup, just do not seem to work, or work well. I would avoid such.
    Although I now have a Canopus ADVC300 I previously used a Magix 'Movies on DVD' USB device. I found the results from this to be particularly good and, to my ageing eyes, I see very little quality difference.
    I think this is because Magix use their proprietary high quality codec (from their Pro products) to capture the footage. Like DV-AVI it runs around 10GB+ per hour. This can then, very simply, be exported to DV-AVI Type 2 for use in PRE. Note that there are some sound synchronisation issues with the 'out of the box' settings - but the fix is quick and I posted details to the Magix forum.
    Would I revert if I could return my ADVC300 bridge? Probably not - the firewire connection and the PC seeing the box as a camcorder adds to ease of use. In fact I am pleased to have both. There are some things Magix does better than PRE7 (batch exporting each scene as an individual DV-AVI file being just one) and it has smart-rendering which is handy for quick clip splitting/exporting.
    Cheers,
    Neale
    Insanity is hereditary, you get it from your children

  • Trying to switch from nvidia to nouveau; startx freezes system

    I'm having high cpu issues, possibly related to nvidia and want to switch to nouveau to test this out. I followed the Arch Wiki for nouveau but am having issues being able to startx. My process:
    - Logout of openbox
    - Remove nvidia stuff:
    # pacman -Rsc nvidia nvidia-utils opencl-nvidia
    # pacman -S xf86-video-nouveau
    Installing nouveau also prompted the removal of nvidia-libgl and replaced it with mesa-libgl, as well as the installation of nouvea-dri.
    - Removed my existing monitor config file:
    # mv /etc/X11/xorg.conf.d/10-monitor.conf /etc/X11/xorg.conf.d/10-monitor.conf.bk
    - Verified that I have no modeset options specified to kernel options via syslinux, nor blacklisting of nouveau in /etc/modprobe.d/ files.
    $ cat /etc/modprobe.d/modprobe.conf
    # /etc/modprobe.d/modprobe.conf
    blacklist uvcvideo
    blacklist pcspkr
    $ ls /etc/X11/xorg.conf.d/
    10-evdev.conf 10-monitor.conf.bk 10-quirks.conf 50-synaptics.conf
    Nothing related to monitors or screens in 10-evdev, 10-quirks or 50-synaptics, and the 10-monitor.conf.bk file has the following contents (just in the event it *is* picked up by Xorg):
    $ cat /etc/X11/xorg.conf.d/10-monitor.conf.bk
    Section "Monitor"
    Identifier "Monitor0"
    ModelName "LGD"
    HorizSync 28.0 - 33.0
    VertRefresh 43.0 - 72.0
    Option "DPMS"
    # Option "Enable" "True"
    # Option "PreferredMode" "1600x900"
    EndSection
    Section "Device"
    Identifier "Device0"
    Driver "nouveau"
    # Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "Quadro FX 1800M"
    BusID "PCI:1:0:0"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Device0"
    Monitor "Monitor0"
    DefaultDepth 24
    SubSection "Display"
    Depth 24
    Modes "1600x900"
    EndSubSection
    # Option "SLI" "Auto"
    # Option "AddARGBGLXVisuals" "True"
    EndSection
    - Reboot
    I am at work and have my computer docked. Nouveau seemed to be active, observed by the fact that it auto-switched to KMS during boot. It also picked up my external monitor, which was off, and started duplicating the display on my external monitor and laptop during text boot (which nvidia does not do). The laptop had what I'll call "screen artifacts" on the lower right (white lines, jumbled pixels) after switching to KMS, but not a huge deal. I went to startx and it just froze after spitting out the various initialization lines. I have to hard kill and reboot. From there, I uninstall nouveau, re-install nvidia (which replaces mesa-libgl with nvidia-libgl), and reboot again to a working system.
    Any suggestions?
    Last edited by jwhendy (2013-10-24 16:36:15)

    Here's the recent Xorg.log:
    X.Org X Server 1.14.3
    Release Date: 2013-09-12
    [ 102.581] X Protocol Version 11, Revision 0
    [ 102.581] Build Operating System: Linux 3.11.1-1-ARCH x86_64
    [ 102.581] Current Operating System: Linux bigBang 3.11.6-1-ARCH #1 SMP PREEMPT Fri Oct 18 23:22:36 CEST 2013 x86_64
    [ 102.581] Kernel command line: root=/dev/mapper/root cryptdevice=/dev/sda3:root ro initrd=../initramfs-linux.img BOOT_IMAGE=../vmlinuz-linux
    [ 102.581] Build Date: 08 October 2013 08:48:10PM
    [ 102.581]
    [ 102.581] Current version of pixman: 0.30.2
    [ 102.581] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 102.581] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 102.582] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Oct 24 19:46:30 2013
    [ 102.599] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 102.618] (==) No Layout section. Using the first Screen section.
    [ 102.618] (==) No screen section available. Using defaults.
    [ 102.618] (**) |-->Screen "Default Screen Section" (0)
    [ 102.618] (**) | |-->Monitor "<default monitor>"
    [ 102.618] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 102.618] (==) Automatically adding devices
    [ 102.618] (==) Automatically enabling devices
    [ 102.618] (==) Automatically adding GPU devices
    [ 102.666] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 102.666] Entry deleted from font path.
    [ 102.666] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 102.667] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 102.667] Entry deleted from font path.
    [ 102.667] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 102.667] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/OTF/,
    /usr/share/fonts/Type1/
    [ 102.667] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 102.667] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 102.667] (II) Loader magic: 0x7fdc20
    [ 102.667] (II) Module ABI versions:
    [ 102.667] X.Org ANSI C Emulation: 0.4
    [ 102.667] X.Org Video Driver: 14.1
    [ 102.667] X.Org XInput driver : 19.1
    [ 102.667] X.Org Server Extension : 7.0
    [ 102.667] (II) xfree86: Adding drm device (/dev/dri/card0)
    [ 102.671] (--) PCI:*(0:1:0:0) 10de:0cbc:103c:1521 rev 162, Mem @ 0xd2000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x00005000/128, BIOS @ 0x????????/524288
    [ 102.671] Initializing built-in extension Generic Event Extension
    [ 102.672] Initializing built-in extension SHAPE
    [ 102.672] Initializing built-in extension MIT-SHM
    [ 102.672] Initializing built-in extension XInputExtension
    [ 102.672] Initializing built-in extension XTEST
    [ 102.672] Initializing built-in extension BIG-REQUESTS
    [ 102.672] Initializing built-in extension SYNC
    [ 102.672] Initializing built-in extension XKEYBOARD
    [ 102.673] Initializing built-in extension XC-MISC
    [ 102.674] Initializing built-in extension SECURITY
    [ 102.675] Initializing built-in extension XINERAMA
    [ 102.676] Initializing built-in extension XFIXES
    [ 102.677] Initializing built-in extension RENDER
    [ 102.678] Initializing built-in extension RANDR
    [ 102.679] Initializing built-in extension COMPOSITE
    [ 102.680] Initializing built-in extension DAMAGE
    [ 102.681] Initializing built-in extension MIT-SCREEN-SAVER
    [ 102.682] Initializing built-in extension DOUBLE-BUFFER
    [ 102.683] Initializing built-in extension RECORD
    [ 102.684] Initializing built-in extension DPMS
    [ 102.684] Initializing built-in extension X-Resource
    [ 102.685] Initializing built-in extension XVideo
    [ 102.686] Initializing built-in extension XVideo-MotionCompensation
    [ 102.687] Initializing built-in extension XFree86-VidModeExtension
    [ 102.688] Initializing built-in extension XFree86-DGA
    [ 102.689] Initializing built-in extension XFree86-DRI
    [ 102.690] Initializing built-in extension DRI2
    [ 102.690] (II) LoadModule: "glx"
    [ 102.691] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 102.719] (II) Module glx: vendor="X.Org Foundation"
    [ 102.719] compiled for 1.14.3, module version = 1.0.0
    [ 102.719] ABI class: X.Org Server Extension, version 7.0
    [ 102.719] (==) AIGLX enabled
    [ 102.721] Loading extension GLX
    [ 102.721] (==) Matched nouveau as autoconfigured driver 0
    [ 102.721] (==) Matched nvidia as autoconfigured driver 1
    [ 102.721] (==) Matched nv as autoconfigured driver 2
    [ 102.721] (==) Matched nouveau as autoconfigured driver 3
    [ 102.721] (==) Matched nvidia as autoconfigured driver 4
    [ 102.721] (==) Matched nv as autoconfigured driver 5
    [ 102.721] (==) Matched vesa as autoconfigured driver 6
    [ 102.721] (==) Matched modesetting as autoconfigured driver 7
    [ 102.721] (==) Matched fbdev as autoconfigured driver 8
    [ 102.721] (==) Assigned the driver to the xf86ConfigLayout
    [ 102.721] (II) LoadModule: "nouveau"
    [ 102.721] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
    [ 102.751] (II) Module nouveau: vendor="X.Org Foundation"
    [ 102.751] compiled for 1.14.2, module version = 1.0.9
    [ 102.751] Module class: X.Org Video Driver
    [ 102.751] ABI class: X.Org Video Driver, version 14.1
    [ 102.751] (II) LoadModule: "nvidia"
    [ 102.765] (WW) Warning, couldn't open module nvidia
    [ 102.765] (II) UnloadModule: "nvidia"
    [ 102.765] (II) Unloading nvidia
    [ 102.765] (EE) Failed to load module "nvidia" (module does not exist, 0)
    [ 102.765] (II) LoadModule: "nv"
    [ 102.765] (WW) Warning, couldn't open module nv
    [ 102.765] (II) UnloadModule: "nv"
    [ 102.765] (II) Unloading nv
    [ 102.765] (EE) Failed to load module "nv" (module does not exist, 0)
    [ 102.765] (II) LoadModule: "vesa"
    [ 102.765] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
    [ 102.776] (II) Module vesa: vendor="X.Org Foundation"
    [ 102.776] compiled for 1.14.0, module version = 2.3.2
    [ 102.776] Module class: X.Org Video Driver
    [ 102.776] ABI class: X.Org Video Driver, version 14.1
    [ 102.776] (II) LoadModule: "modesetting"
    [ 102.776] (WW) Warning, couldn't open module modesetting
    [ 102.776] (II) UnloadModule: "modesetting"
    [ 102.776] (II) Unloading modesetting
    [ 102.776] (EE) Failed to load module "modesetting" (module does not exist, 0)
    [ 102.776] (II) LoadModule: "fbdev"
    [ 102.776] (WW) Warning, couldn't open module fbdev
    [ 102.776] (II) UnloadModule: "fbdev"
    [ 102.776] (II) Unloading fbdev
    [ 102.776] (EE) Failed to load module "fbdev" (module does not exist, 0)
    [ 102.776] (II) NOUVEAU driver
    [ 102.776] (II) NOUVEAU driver for NVIDIA chipset families :
    [ 102.776] RIVA TNT (NV04)
    [ 102.776] RIVA TNT2 (NV05)
    [ 102.776] GeForce 256 (NV10)
    [ 102.776] GeForce 2 (NV11, NV15)
    [ 102.776] GeForce 4MX (NV17, NV18)
    [ 102.776] GeForce 3 (NV20)
    [ 102.776] GeForce 4Ti (NV25, NV28)
    [ 102.776] GeForce FX (NV3x)
    [ 102.776] GeForce 6 (NV4x)
    [ 102.776] GeForce 7 (G7x)
    [ 102.776] GeForce 8 (G8x)
    [ 102.776] GeForce GTX 200 (NVA0)
    [ 102.776] GeForce GTX 400 (NVC0)
    [ 102.776] (II) VESA: driver for VESA chipsets: vesa
    [ 102.776] (++) using VT number 1
    [ 102.776] (II) [drm] nouveau interface version: 1.1.1
    [ 102.777] (WW) Falling back to old probe method for vesa
    [ 102.777] (II) Loading sub module "dri2"
    [ 102.777] (II) LoadModule: "dri2"
    [ 102.777] (II) Module "dri2" already built-in
    [ 102.777] (--) NOUVEAU(0): Chipset: "NVIDIA NVA3"
    [ 102.777] (II) NOUVEAU(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 102.777] (==) NOUVEAU(0): Depth 24, (--) framebuffer bpp 32
    [ 102.777] (==) NOUVEAU(0): RGB weight 888
    [ 102.777] (==) NOUVEAU(0): Default visual is TrueColor
    [ 102.777] (==) NOUVEAU(0): Using HW cursor
    [ 102.777] (==) NOUVEAU(0): GLX sync to VBlank disabled.
    [ 102.777] (==) NOUVEAU(0): Page flipping enabled
    [ 102.777] (==) NOUVEAU(0): Swap limit set to 2 [Max allowed 2]
    [ 102.845] (II) NOUVEAU(0): Output LVDS-1 has no monitor section
    [ 102.950] (II) NOUVEAU(0): Output DP-1 has no monitor section
    [ 103.056] (II) NOUVEAU(0): Output DP-2 has no monitor section
    [ 103.056] (II) NOUVEAU(0): Output eDP-1 has no monitor section
    [ 103.163] (II) NOUVEAU(0): Output DP-3 has no monitor section
    [ 103.184] (II) NOUVEAU(0): Output VGA-1 has no monitor section
    [ 103.211] (II) NOUVEAU(0): EDID for output LVDS-1
    [ 103.211] (II) NOUVEAU(0): Manufacturer: CMO Model: 1595 Serial#: 0
    [ 103.211] (II) NOUVEAU(0): Year: 2009 Week: 12
    [ 103.211] (II) NOUVEAU(0): EDID Version: 1.3
    [ 103.211] (II) NOUVEAU(0): Digital Display Input
    [ 103.211] (II) NOUVEAU(0): Max Image Size [cm]: horiz.: 34 vert.: 19
    [ 103.211] (II) NOUVEAU(0): Gamma: 2.20
    [ 103.211] (II) NOUVEAU(0): No DPMS capabilities specified
    [ 103.211] (II) NOUVEAU(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
    [ 103.211] (II) NOUVEAU(0): First detailed timing is preferred mode
    [ 103.211] (II) NOUVEAU(0): redX: 0.610 redY: 0.343 greenX: 0.342 greenY: 0.581
    [ 103.211] (II) NOUVEAU(0): blueX: 0.162 blueY: 0.083 whiteX: 0.313 whiteY: 0.329
    [ 103.211] (II) NOUVEAU(0): Manufacturer's mask: 0
    [ 103.211] (II) NOUVEAU(0): Supported detailed timing:
    [ 103.211] (II) NOUVEAU(0): clock: 107.8 MHz Image Size: 344 x 193 mm
    [ 103.211] (II) NOUVEAU(0): h_active: 1600 h_sync: 1626 h_sync_end 1686 h_blank_end 1892 h_border: 0
    [ 103.211] (II) NOUVEAU(0): v_active: 900 v_sync: 909 v_sync_end 919 v_blanking: 949 v_border: 0
    [ 103.212] (II) NOUVEAU(0): N156O6-L01
    [ 103.212] (II) NOUVEAU(0): CMO
    [ 103.212] (II) NOUVEAU(0): N156O6-L01
    [ 103.212] (II) NOUVEAU(0): EDID (in hex):
    [ 103.212] (II) NOUVEAU(0): 00ffffffffffff000daf951500000000
    [ 103.212] (II) NOUVEAU(0): 0c130103802213780a7b959c57579429
    [ 103.212] (II) NOUVEAU(0): 15505400000001010101010101010101
    [ 103.212] (II) NOUVEAU(0): 0101010101011c2a4024618431301a3c
    [ 103.212] (II) NOUVEAU(0): 9a0058c110000018000000fe004e3135
    [ 103.212] (II) NOUVEAU(0): 364f362d4c30310a2020000000fe0043
    [ 103.212] (II) NOUVEAU(0): 4d4f0a202020202020202020000000fe
    [ 103.212] (II) NOUVEAU(0): 004e3135364f362d4c30310a2020001c
    [ 103.212] (II) NOUVEAU(0): Printing probed modes for output LVDS-1
    [ 103.212] (II) NOUVEAU(0): Modeline "1600x900"x60.0 107.80 1600 1626 1686 1892 900 909 919 949 -hsync -vsync (57.0 kHz eP)
    [ 103.212] (II) NOUVEAU(0): Modeline "1152x864"x60.0 81.75 1152 1216 1336 1520 864 867 871 897 -hsync +vsync (53.8 kHz e)
    [ 103.212] (II) NOUVEAU(0): Modeline "1024x768"x59.9 63.50 1024 1072 1176 1328 768 771 775 798 -hsync +vsync (47.8 kHz e)
    [ 103.212] (II) NOUVEAU(0): Modeline "800x600"x59.9 38.25 800 832 912 1024 600 603 607 624 -hsync +vsync (37.4 kHz e)
    [ 103.212] (II) NOUVEAU(0): Modeline "640x480"x59.4 23.75 640 664 720 800 480 483 487 500 -hsync +vsync (29.7 kHz e)
    [ 103.212] (II) NOUVEAU(0): Modeline "720x400"x59.6 22.25 720 744 808 896 400 403 413 417 -hsync +vsync (24.8 kHz e)
    [ 103.212] (II) NOUVEAU(0): Modeline "640x400"x60.0 20.00 640 664 720 800 400 403 409 417 -hsync +vsync (25.0 kHz e)
    [ 103.212] (II) NOUVEAU(0): Modeline "640x350"x59.8 17.50 640 664 720 800 350 353 363 366 -hsync +vsync (21.9 kHz e)
    [ 103.316] (II) NOUVEAU(0): EDID for output DP-1
    [ 103.423] (II) NOUVEAU(0): EDID for output DP-2
    [ 103.423] (II) NOUVEAU(0): EDID for output eDP-1
    [ 103.530] (II) NOUVEAU(0): EDID for output DP-3
    [ 103.550] (II) NOUVEAU(0): EDID for output VGA-1
    [ 103.550] (II) NOUVEAU(0): Output LVDS-1 connected
    [ 103.550] (II) NOUVEAU(0): Output DP-1 disconnected
    [ 103.550] (II) NOUVEAU(0): Output DP-2 disconnected
    [ 103.551] (II) NOUVEAU(0): Output eDP-1 disconnected
    [ 103.551] (II) NOUVEAU(0): Output DP-3 disconnected
    [ 103.551] (II) NOUVEAU(0): Output VGA-1 disconnected
    [ 103.551] (II) NOUVEAU(0): Using exact sizes for initial modes
    [ 103.551] (II) NOUVEAU(0): Output LVDS-1 using initial mode 1600x900
    [ 103.551] (II) NOUVEAU(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    [ 103.551] (--) NOUVEAU(0): Virtual size is 1600x900 (pitch 0)
    [ 103.551] (**) NOUVEAU(0): Driver mode "1600x900": 107.8 MHz (scaled from 0.0 MHz), 57.0 kHz, 60.0 Hz
    [ 103.551] (II) NOUVEAU(0): Modeline "1600x900"x60.0 107.80 1600 1626 1686 1892 900 909 919 949 -hsync -vsync (57.0 kHz eP)
    [ 103.551] (**) NOUVEAU(0): Driver mode "1152x864": 81.8 MHz (scaled from 0.0 MHz), 53.8 kHz, 60.0 Hz
    [ 103.551] (II) NOUVEAU(0): Modeline "1152x864"x60.0 81.75 1152 1216 1336 1520 864 867 871 897 -hsync +vsync (53.8 kHz e)
    [ 103.551] (**) NOUVEAU(0): Driver mode "1024x768": 63.5 MHz (scaled from 0.0 MHz), 47.8 kHz, 59.9 Hz
    [ 103.551] (II) NOUVEAU(0): Modeline "1024x768"x59.9 63.50 1024 1072 1176 1328 768 771 775 798 -hsync +vsync (47.8 kHz e)
    [ 103.551] (**) NOUVEAU(0): Driver mode "800x600": 38.2 MHz (scaled from 0.0 MHz), 37.4 kHz, 59.9 Hz
    [ 103.551] (II) NOUVEAU(0): Modeline "800x600"x59.9 38.25 800 832 912 1024 600 603 607 624 -hsync +vsync (37.4 kHz e)
    [ 103.551] (**) NOUVEAU(0): Driver mode "640x480": 23.8 MHz (scaled from 0.0 MHz), 29.7 kHz, 59.4 Hz
    [ 103.551] (II) NOUVEAU(0): Modeline "640x480"x59.4 23.75 640 664 720 800 480 483 487 500 -hsync +vsync (29.7 kHz e)
    [ 103.551] (**) NOUVEAU(0): Driver mode "720x400": 22.2 MHz (scaled from 0.0 MHz), 24.8 kHz, 59.6 Hz
    [ 103.551] (II) NOUVEAU(0): Modeline "720x400"x59.6 22.25 720 744 808 896 400 403 413 417 -hsync +vsync (24.8 kHz e)
    [ 103.551] (**) NOUVEAU(0): Driver mode "640x400": 20.0 MHz (scaled from 0.0 MHz), 25.0 kHz, 60.0 Hz
    [ 103.551] (II) NOUVEAU(0): Modeline "640x400"x60.0 20.00 640 664 720 800 400 403 409 417 -hsync +vsync (25.0 kHz e)
    [ 103.551] (**) NOUVEAU(0): Driver mode "640x350": 17.5 MHz (scaled from 0.0 MHz), 21.9 kHz, 59.8 Hz
    [ 103.551] (II) NOUVEAU(0): Modeline "640x350"x59.8 17.50 640 664 720 800 350 353 363 366 -hsync +vsync (21.9 kHz e)
    [ 103.551] (==) NOUVEAU(0): DPI set to (96, 96)
    [ 103.551] (II) Loading sub module "fb"
    [ 103.551] (II) LoadModule: "fb"
    [ 103.551] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 105.504] (II) Module fb: vendor="X.Org Foundation"
    [ 105.504] compiled for 1.14.3, module version = 1.0.0
    [ 105.504] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 105.504] (II) Loading sub module "exa"
    [ 105.504] (II) LoadModule: "exa"
    [ 105.504] (II) Loading /usr/lib/xorg/modules/libexa.so
    [ 105.508] (II) Module exa: vendor="X.Org Foundation"
    [ 105.508] compiled for 1.14.3, module version = 2.6.0
    [ 105.508] ABI class: X.Org Video Driver, version 14.1
    [ 105.508] (II) Loading sub module "shadowfb"
    [ 105.508] (II) LoadModule: "shadowfb"
    [ 105.508] (II) Loading /usr/lib/xorg/modules/libshadowfb.so
    [ 105.518] (II) Module shadowfb: vendor="X.Org Foundation"
    [ 105.518] compiled for 1.14.3, module version = 1.0.0
    [ 105.518] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 105.518] (II) UnloadModule: "vesa"
    [ 105.518] (II) Unloading vesa
    [ 105.518] (--) Depth 24 pixmap format is 32 bpp
    [ 105.521] (II) NOUVEAU(0): Opened GPU channel 0
    [ 105.547] (II) NOUVEAU(0): [DRI2] Setup complete
    [ 105.547] (II) NOUVEAU(0): [DRI2] DRI driver: nouveau
    [ 105.547] (II) NOUVEAU(0): [DRI2] VDPAU driver: nouveau
    [ 108.224] (II) EXA(0): Driver allocated offscreen pixmaps
    [ 108.224] (II) EXA(0): Driver registered support for the following operations:
    [ 108.224] (II) Solid
    [ 108.224] (II) Copy
    [ 108.224] (II) Composite (RENDER acceleration)
    [ 108.224] (II) UploadToScreen
    [ 108.224] (II) DownloadFromScreen
    [ 108.224] (==) NOUVEAU(0): Backing store disabled
    [ 108.224] (==) NOUVEAU(0): Silken mouse enabled
    [ 108.226] (II) NOUVEAU(0): [XvMC] Associated with Nouveau GeForce 8/9 Textured Video.
    [ 108.226] (II) NOUVEAU(0): [XvMC] Extension initialized.
    [ 108.226] (==) NOUVEAU(0): DPMS enabled
    [ 108.226] (II) NOUVEAU(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 108.228] (--) RandR disabled
    [ 142.503] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
    [ 142.503] (II) AIGLX: enabled GLX_INTEL_swap_event
    [ 142.504] (II) AIGLX: enabled GLX_ARB_create_context
    [ 142.504] (II) AIGLX: enabled GLX_ARB_create_context_profile
    [ 142.504] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
    [ 142.504] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
    [ 142.504] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
    [ 142.505] (II) AIGLX: Loaded and initialized nouveau
    [ 142.505] (II) GLX: Initialized DRI2 GL provider for screen 0
    [ 159.503] (II) NOUVEAU(0): NVEnterVT is called.
    [ 159.532] (II) NOUVEAU(0): Setting screen physical size to 423 x 238
    [ 159.532] resize called 1600 900
    [ 160.324] (II) config/udev: Adding input device Power Button (/dev/input/event3)
    [ 160.324] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 160.324] (II) LoadModule: "evdev"
    [ 160.324] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 160.355] (II) Module evdev: vendor="X.Org Foundation"
    [ 160.355] compiled for 1.14.3, module version = 2.8.2
    [ 160.355] Module class: X.Org XInput Driver
    [ 160.355] ABI class: X.Org XInput driver, version 19.1
    [ 160.355] (II) Using input driver 'evdev' for 'Power Button'
    [ 160.355] (**) Power Button: always reports core events
    [ 160.355] (**) evdev: Power Button: Device: "/dev/input/event3"
    [ 160.355] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 160.355] (--) evdev: Power Button: Found keys
    [ 160.355] (II) evdev: Power Button: Configuring as keyboard
    [ 160.355] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event3"
    [ 160.355] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 160.355] (**) Option "xkb_rules" "evdev"
    [ 160.355] (**) Option "xkb_model" "pc104"
    [ 160.355] (**) Option "xkb_layout" "us"
    [ 160.392] (II) config/udev: Adding input device Video Bus (/dev/input/event4)
    [ 160.392] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
    [ 160.392] (II) Using input driver 'evdev' for 'Video Bus'
    [ 160.392] (**) Video Bus: always reports core events
    [ 160.392] (**) evdev: Video Bus: Device: "/dev/input/event4"
    [ 160.392] (--) evdev: Video Bus: Vendor 0 Product 0x6
    [ 160.392] (--) evdev: Video Bus: Found keys
    [ 160.392] (II) evdev: Video Bus: Configuring as keyboard
    [ 160.392] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:03/LNXVIDEO:00/input/input4/event4"
    [ 160.392] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
    [ 160.392] (**) Option "xkb_rules" "evdev"
    [ 160.392] (**) Option "xkb_model" "pc104"
    [ 160.393] (**) Option "xkb_layout" "us"
    [ 160.393] (II) config/udev: Adding input device Lid Switch (/dev/input/event2)
    [ 160.393] (II) No input driver specified, ignoring this device.
    [ 160.393] (II) This device may have been added with another device file.
    [ 160.394] (II) config/udev: Adding input device Sleep Button (/dev/input/event1)
    [ 160.394] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
    [ 160.394] (II) Using input driver 'evdev' for 'Sleep Button'
    [ 160.394] (**) Sleep Button: always reports core events
    [ 160.394] (**) evdev: Sleep Button: Device: "/dev/input/event1"
    [ 160.394] (--) evdev: Sleep Button: Vendor 0 Product 0x3
    [ 160.394] (--) evdev: Sleep Button: Found keys
    [ 160.394] (II) evdev: Sleep Button: Configuring as keyboard
    [ 160.394] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input1/event1"
    [ 160.394] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 8)
    [ 160.394] (**) Option "xkb_rules" "evdev"
    [ 160.394] (**) Option "xkb_model" "pc104"
    [ 160.394] (**) Option "xkb_layout" "us"
    [ 160.395] (II) config/udev: Adding drm device (/dev/dri/card0)
    [ 160.396] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event13)
    [ 160.396] (II) No input driver specified, ignoring this device.
    [ 160.396] (II) This device may have been added with another device file.
    [ 160.396] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event14)
    [ 160.396] (II) No input driver specified, ignoring this device.
    [ 160.396] (II) This device may have been added with another device file.
    [ 160.397] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event15)
    [ 160.397] (II) No input driver specified, ignoring this device.
    [ 160.397] (II) This device may have been added with another device file.
    [ 160.397] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event16)
    [ 160.397] (II) No input driver specified, ignoring this device.
    [ 160.397] (II) This device may have been added with another device file.
    [ 160.398] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event6)
    [ 160.398] (II) No input driver specified, ignoring this device.
    [ 160.398] (II) This device may have been added with another device file.
    [ 160.398] (II) config/udev: Adding input device HDA Intel MID Mic (/dev/input/event10)
    [ 160.398] (II) No input driver specified, ignoring this device.
    [ 160.398] (II) This device may have been added with another device file.
    [ 160.399] (II) config/udev: Adding input device HDA Intel MID Dock Headphone (/dev/input/event7)
    [ 160.399] (II) No input driver specified, ignoring this device.
    [ 160.399] (II) This device may have been added with another device file.
    [ 160.399] (II) config/udev: Adding input device HDA Intel MID Headphone (/dev/input/event8)
    [ 160.399] (II) No input driver specified, ignoring this device.
    [ 160.399] (II) This device may have been added with another device file.
    [ 160.400] (II) config/udev: Adding input device HDA Intel MID Line (/dev/input/event9)
    [ 160.400] (II) No input driver specified, ignoring this device.
    [ 160.400] (II) This device may have been added with another device file.
    [ 160.400] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
    [ 160.400] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
    [ 160.401] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
    [ 160.401] (**) AT Translated Set 2 keyboard: always reports core events
    [ 160.401] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
    [ 160.401] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
    [ 160.401] (--) evdev: AT Translated Set 2 keyboard: Found keys
    [ 160.401] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
    [ 160.401] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
    [ 160.401] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 9)
    [ 160.401] (**) Option "xkb_rules" "evdev"
    [ 160.401] (**) Option "xkb_model" "pc104"
    [ 160.401] (**) Option "xkb_layout" "us"
    [ 160.402] (II) config/udev: Adding input device PS/2 Generic Mouse (/dev/input/event11)
    [ 160.402] (**) PS/2 Generic Mouse: Applying InputClass "evdev pointer catchall"
    [ 160.402] (II) Using input driver 'evdev' for 'PS/2 Generic Mouse'
    [ 160.402] (**) PS/2 Generic Mouse: always reports core events
    [ 160.402] (**) evdev: PS/2 Generic Mouse: Device: "/dev/input/event11"
    [ 160.402] (--) evdev: PS/2 Generic Mouse: Vendor 0x2 Product 0x1
    [ 160.402] (--) evdev: PS/2 Generic Mouse: Found 3 mouse buttons
    [ 160.402] (--) evdev: PS/2 Generic Mouse: Found relative axes
    [ 160.402] (--) evdev: PS/2 Generic Mouse: Found x and y relative axes
    [ 160.402] (II) evdev: PS/2 Generic Mouse: Configuring as mouse
    [ 160.402] (**) evdev: PS/2 Generic Mouse: YAxisMapping: buttons 4 and 5
    [ 160.402] (**) evdev: PS/2 Generic Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 160.402] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input11/event11"
    [ 160.402] (II) XINPUT: Adding extended input device "PS/2 Generic Mouse" (type: MOUSE, id 10)
    [ 160.402] (II) evdev: PS/2 Generic Mouse: initialized for relative axes.
    [ 160.402] (**) PS/2 Generic Mouse: (accel) keeping acceleration scheme 1
    [ 160.403] (**) PS/2 Generic Mouse: (accel) acceleration profile 0
    [ 160.403] (**) PS/2 Generic Mouse: (accel) acceleration factor: 2.000
    [ 160.403] (**) PS/2 Generic Mouse: (accel) acceleration threshold: 4
    [ 160.403] (II) config/udev: Adding input device PS/2 Generic Mouse (/dev/input/mouse0)
    [ 160.403] (II) No input driver specified, ignoring this device.
    [ 160.403] (II) This device may have been added with another device file.
    [ 160.403] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event17)
    [ 160.403] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
    [ 160.403] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
    [ 160.403] (II) LoadModule: "synaptics"
    [ 160.403] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
    [ 160.415] (II) Module synaptics: vendor="X.Org Foundation"
    [ 160.415] compiled for 1.14.1, module version = 1.7.1
    [ 160.415] Module class: X.Org XInput Driver
    [ 160.415] ABI class: X.Org XInput driver, version 19.1
    [ 160.415] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
    [ 160.415] (**) SynPS/2 Synaptics TouchPad: always reports core events
    [ 160.415] (**) Option "Device" "/dev/input/event17"
    [ 160.503] (II) synaptics: SynPS/2 Synaptics TouchPad: ignoring touch events for semi-multitouch device
    [ 160.503] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5600 (res 57)
    [ 160.503] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4884 (res 123)
    [ 160.503] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
    [ 160.503] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
    [ 160.503] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left right middle double triple
    [ 160.503] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
    [ 160.503] (**) Option "VertScrollDelta" "250"
    [ 160.503] (**) Option "VertTwoFingerScroll" "on"
    [ 160.504] (**) Option "HorizTwoFingerScroll" "off"
    [ 160.504] (**) Option "TapButton1" "1"
    [ 160.504] (**) Option "TapButton2" "2"
    [ 160.504] (**) Option "TapButton3" "3"
    [ 160.504] (**) Option "CoastingSpeed" "0"
    [ 160.504] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 160.504] (**) SynPS/2 Synaptics TouchPad: always reports core events
    [ 160.530] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio4/input/input17/event17"
    [ 160.530] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 11)
    [ 160.530] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
    [ 160.530] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
    [ 160.530] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.037
    [ 160.531] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
    [ 160.531] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
    [ 160.531] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
    [ 160.531] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
    [ 160.531] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 160.531] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse1)
    [ 160.531] (II) No input driver specified, ignoring this device.
    [ 160.531] (II) This device may have been added with another device file.
    [ 160.532] (II) config/udev: Adding input device ST LIS3LV02DL Accelerometer (/dev/input/event5)
    [ 160.532] (II) No input driver specified, ignoring this device.
    [ 160.532] (II) This device may have been added with another device file.
    [ 160.532] (II) config/udev: Adding input device ST LIS3LV02DL Accelerometer (/dev/input/js0)
    [ 160.532] (II) No input driver specified, ignoring this device.
    [ 160.532] (II) This device may have been added with another device file.
    [ 160.533] (II) config/udev: Adding input device HP WMI hotkeys (/dev/input/event12)
    [ 160.533] (**) HP WMI hotkeys: Applying InputClass "evdev keyboard catchall"
    [ 160.533] (II) Using input driver 'evdev' for 'HP WMI hotkeys'
    [ 160.533] (**) HP WMI hotkeys: always reports core events
    [ 160.533] (**) evdev: HP WMI hotkeys: Device: "/dev/input/event12"
    [ 160.533] (--) evdev: HP WMI hotkeys: Vendor 0 Product 0
    [ 160.533] (--) evdev: HP WMI hotkeys: Found keys
    [ 160.533] (II) evdev: HP WMI hotkeys: Configuring as keyboard
    [ 160.533] (**) Option "config_info" "udev:/sys/devices/virtual/input/input12/event12"
    [ 160.533] (II) XINPUT: Adding extended input device "HP WMI hotkeys" (type: KEYBOARD, id 12)
    [ 160.533] (**) Option "xkb_rules" "evdev"
    [ 160.533] (**) Option "xkb_model" "pc104"
    [ 160.533] (**) Option "xkb_layout" "us"
    [ 164.083] (II) AIGLX: Suspending AIGLX clients for VT switch
    [ 164.083] (II) NOUVEAU(0): NVLeaveVT is called.
    [ 181.123] (II) AIGLX: Resuming AIGLX clients after VT switch
    [ 181.123] (II) NOUVEAU(0): NVEnterVT is called.
    [ 181.179] (II) NOUVEAU(0): EDID vendor "CMO", prod id 5525
    [ 181.179] (II) NOUVEAU(0): Printing DDC gathered Modelines:
    [ 181.179] (II) NOUVEAU(0): Modeline "1600x900"x0.0 107.80 1600 1626 1686 1892 900 909 919 949 -hsync -vsync (57.0 kHz eP)
    [ 181.517] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 181.517] setversion 1.4 failed
    (EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed.
    (EE)
    (EE) Backtrace:
    (EE) 0: /usr/bin/X (xorg_backtrace+0x3d) [0x57f67d]
    (EE) 1: /usr/bin/X (mieqEnqueue+0x22b) [0x5615bb]
    (EE) 2: /usr/bin/X (QueueKeyboardEvents+0x52) [0x44d452]
    (EE) 3: /usr/bin/X (xf86PostKeyboardEvent+0x44) [0x483e84]
    (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f4f79e94000+0x5591) [0x7f4f79e99591]
    (EE) 5: /usr/bin/X (0x400000+0x73da8) [0x473da8]
    (EE) 6: /usr/bin/X (0x400000+0x9c330) [0x49c330]
    (EE) 7: /usr/lib/libpthread.so.0 (0x7f4f7f8af000+0xf870) [0x7f4f7f8be870]
    (EE) 8: /usr/lib/libc.so.6 (ioctl+0x7) [0x7f4f7e9eef17]
    (EE) 9: /usr/lib/libdrm.so.2 (drmCommandWrite+0x5d) [0x7f4f8055e9fd]
    (EE) 10: /usr/lib/libdrm_nouveau.so.2 (nouveau_bo_wait+0x8a) [0x7f4f8058446a]
    (EE) 11: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f4f7d349000+0x716b) [0x7f4f7d35016b]
    (EE) 12: /usr/lib/xorg/modules/libexa.so (0x7f4f7cd05000+0xb308) [0x7f4f7cd10308]
    (EE) 13: /usr/bin/X (0x400000+0x170563) [0x570563]
    (EE) 14: /usr/bin/X (0x400000+0xc0f95) [0x4c0f95]
    (EE) 15: /usr/bin/X (0x400000+0x104193) [0x504193]
    (EE) 16: /usr/bin/X (0x400000+0x373be) [0x4373be]
    (EE) 17: /usr/bin/X (0x400000+0x2693a) [0x42693a]
    (EE) 18: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7f4f7e932bc5]
    (EE) 19: /usr/bin/X (0x400000+0x26c81) [0x426c81]
    (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+0x3d) [0x57f67d]
    (EE) 1: /usr/bin/X (QueueKeyboardEvents+0x52) [0x44d452]
    (EE) 2: /usr/bin/X (xf86PostKeyboardEvent+0x44) [0x483e84]
    (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f4f79e94000+0x5591) [0x7f4f79e99591]
    (EE) 4: /usr/bin/X (0x400000+0x73da8) [0x473da8]
    (EE) 5: /usr/bin/X (0x400000+0x9c330) [0x49c330]
    (EE) 6: /usr/lib/libpthread.so.0 (0x7f4f7f8af000+0xf870) [0x7f4f7f8be870]
    (EE) 7: /usr/lib/libc.so.6 (ioctl+0x7) [0x7f4f7e9eef17]
    (EE) 8: /usr/lib/libdrm.so.2 (drmCommandWrite+0x5d) [0x7f4f8055e9fd]
    (EE) 9: /usr/lib/libdrm_nouveau.so.2 (nouveau_bo_wait+0x8a) [0x7f4f8058446a]
    (EE) 10: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f4f7d349000+0x716b) [0x7f4f7d35016b]
    (EE) 11: /usr/lib/xorg/modules/libexa.so (0x7f4f7cd05000+0xb308) [0x7f4f7cd10308]
    (EE) 12: /usr/bin/X (0x400000+0x170563) [0x570563]
    (EE) 13: /usr/bin/X (0x400000+0xc0f95) [0x4c0f95]
    (EE) 14: /usr/bin/X (0x400000+0x104193) [0x504193]
    (EE) 15: /usr/bin/X (0x400000+0x373be) [0x4373be]
    (EE) 16: /usr/bin/X (0x400000+0x2693a) [0x42693a]
    (EE) 17: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7f4f7e932bc5]
    (EE) 18: /usr/bin/X (0x400000+0x26c81) [0x426c81]
    (EE)
    [ 216.437] [mi] Increasing EQ size to 512 to prevent dropped events.
    [ 216.438] [mi] EQ processing has resumed after 188 dropped events.
    [ 216.438] [mi] This may be caused my a misbehaving driver monopolizing the server's resources.
    [ 216.438] Failed to switch from vt01 to vt06: Input/output error
    [ 216.438] Failed to switch from vt01 to vt06: Input/output error
    [ 216.438] Failed to switch from vt01 to vt06: Input/output error
    [ 216.438] Failed to switch from vt01 to vt02: Input/output error
    [ 216.438] Failed to switch from vt01 to vt03: Input/output error
    [ 216.438] Failed to switch from vt01 to vt04: Input/output error
    [ 216.438] Failed to switch from vt01 to vt05: Input/output error
    [ 216.438] Failed to switch from vt01 to vt06: Input/output error
    [ 216.438] Failed to switch from vt01 to vt07: Input/output error
    [ 216.438] Failed to switch from vt01 to vt08: Input/output error
    [ 216.438] Failed to switch from vt01 to vt09: Input/output error
    [ 216.438] Failed to switch from vt01 to vt10: Input/output error
    [ 216.438] Failed to switch from vt01 to vt11: Input/output error
    [ 216.438] Failed to switch from vt01 to vt02: Input/output error
    [ 216.810] (II) evdev: HP WMI hotkeys: Close
    [ 216.811] (II) UnloadModule: "evdev"
    [ 216.811] (II) UnloadModule: "synaptics"
    [ 216.811] (II) evdev: PS/2 Generic Mouse: Close
    [ 216.811] (II) UnloadModule: "evdev"
    [ 216.811] (II) evdev: AT Translated Set 2 keyboard: Close
    [ 216.811] (II) UnloadModule: "evdev"
    [ 216.811] (II) evdev: Sleep Button: Close
    [ 216.811] (II) UnloadModule: "evdev"
    [ 216.811] (II) evdev: Video Bus: Close
    [ 216.811] (II) UnloadModule: "evdev"
    [ 216.811] (II) evdev: Power Button: Close
    [ 216.811] (II) UnloadModule: "evdev"
    In addition, I can't seem to find any other files related nvidia that seem like they would matter, except for ~/.nvidia-settings-rc, which I moved to ~/.nvidia-settings-rc.bk (prior to the attempt which created the log above). Keep in mind that this is after re-installing nvidia so I can startx and have a working system... Is there anything that looks like it wouldn't be removed by the nvidia package?
    # find / -name *nvidia*
    /proc/irq/63/nvidia
    /proc/driver/nvidia
    /home/jwhendy/.nvidia-settings-rc.bk
    [hits from /usr/share/icons excluded]
    [hits from /usr/share/ excluded]
    /usr/lib/libnvidia-tls.so
    /usr/lib/modules/extramodules-3.11-ARCH/nvidia.ko.gz
    /usr/lib/modules/3.11.6-1-ARCH/kernel/drivers/net/ethernet/nvidia
    /usr/lib/nvidia
    /usr/lib/libnvidia-tls.so.325.15
    /usr/lib/libnvidia-ml.so
    /usr/lib/libnvidia-glcore.so
    /usr/lib/vdpau/libvdpau_nvidia.so
    /usr/lib/vdpau/libvdpau_nvidia.so.1
    /usr/lib/vdpau/libvdpau_nvidia.so.325.15
    /usr/lib/libnvidia-glcore.so.325.15
    /usr/lib/libnvidia-ml.so.325.15
    /usr/lib/libnvidia-cfg.so
    /usr/lib/xorg/modules/drivers/nvidia_drv.so
    /usr/lib/libnvidia-cfg.so.325.15
    /usr/lib/modprobe.d/nvidia.conf # owned by nvidia; removed when I switch to nouveau
    /usr/lib/libnvidia-cfg.so.1
    /usr/lib/libnvidia-ml.so.1
    /usr/bin/nvidia-settings
    /usr/bin/nvidia-xconfig
    /usr/bin/nvidia-smi
    /usr/bin/nvidia-bug-report.sh
    /usr/bin/nvidia-debugdump
    /root/.nvidia-settings-rc
    [hits from /var/abs/ removed]
    /dev/nvidia0
    /dev/nvidiactl
    /sys/bus/pci/drivers/nvidia
    /sys/kernel/slab/nvidia_p2p_page_t
    /sys/module/drm/holders/nvidia
    /sys/module/i2c_core/holders/nvidia
    /sys/module/nvidia
    /sys/module/nvidia/drivers/pci:nvidia
    Anything look odd in the log or the files?
    As always, feel free to suggest other things to try -- I can pipe ls into files to show what files are available when I'm pre-startx with nouveau installed, or more Xorg logs... My computer is not happy wtih nvidia at all and is nearly unusable. I really need to solve this until nvidia is compatible with 3.11 kernels again.

  • Elements 9  Switching from Windows to Mac - two big issues

    I've just started looking into the process of switching from Elements on Windows to Elements on the Mac.  For the most part, the two versions appear to be quite similar in looks and functionality.  There are however two major gaps (in my opinion) in functionality that really make me question whether I'll move forward with Elements on the MAC.  Hopefully these are planned enhancements and I was hoping that someone would have some insight on the issue.
    First, there is no EXPORT feature that I can see on the Mac version.  I used this all the time on Windows(Organizer->File->Export as New File).  A huge gap if one uses the product for building personal photo websites.
    Second, and maybe I just missed some setting, but the SAVE behavior when you EDIT photos places both the original and Edited version of the photo in the default Save Location as indicated in the product Preferences.  So what I have seen is that it takes both the originals and edited versions and moves them.  Again, this seems to be a major difference from how the Windows versions handles this.  Seems as if the default should be to leave the photo's where they are.
    If anyone has a solution to these issues I'd appreciate the help.

    First of all, I know for a fact there was another user on a Windows platform indicating Shutterfly was an option.
    Secondly, right on Elements' website it indicates it is partnered with Kodak, Shutterfly and even Costco (now Costco, I think you need to buy the program right at Costco warehouse if I understand the disclaimer, which would mean a trial, downloaded or purchased anywhere else would not have Costco listed as an option). http://www.adobe.com/products/photoshop/family/partneroffers/
    PRINT
    Turn your photos into professional-quality prints, photo books, and greeting cards.
    Turn your photos into real U.S. postage.
    Create personalized photo books, greeting cards, and digital scrapbooks.
    NEW
    Enjoy the convenience of printing directly to Costco Photo Center from Photoshop Elements 9* purchased at Costco Wholesale, U.S., only.  * Available through product purchased at Costco Wholesale, U.S., only (not available with product purchased in Canada, at Costco.com, or through any other retailer). ^
    and, then another member on this forum had posted this visual:
    But I have Shutterfly available on Windows PSE9 Photo Book.
    AGAIN, I AM WONDERING WHY MY SCREEN DOES NOT OFFER THESE SAME OPTIONS ON MY MAC??????

  • Analog distortion and digital's lack thereof

    Djokes wrote:
    "analog is distorting - without a doubt - tape decks were like compressors in a way and that is what being simulated by e.g. mcdsp or crane song... However, using no eq or tape deck - the distortion is minimal.... but analog is distorting what is actually there - digital is not - cuz it aint "Seeing" it all....so the distortion will be false...And we dont need to start a discussion about that we like the distortion that analog brings - do we now?"
    Let's start one though shall we.
    First I fail to see how digital isn't seeing it all. Unless you're talking about inaudible frequency ranges which I will admit may be more important than not. Digital lays it all on the table. No compensation, no analogesque minimal distortion. So this would be a true picture of the audio right.
    I mean if you're talking about the nuances of environment then digital still captures that stuff as it's mic'd. The thing digital doesn't capture is the distortion signature of the analog device. Now if you've been trained over decades to appreciate that distortion, hearing digital which lacks that of course would lead one to say it sounds cold.
    The question is whether that distortion is the signature of quality music, or whether a talented producer/mixing engineer, can create a signature digital distortion which is either as good or better than analog. I'm a firm believer in the latter though I will admit we haven't surpassed analog yet. But I also believe the answer isn't in trying to emulate analog, but rather using the digital for its own strengths to create something all together new.

    then we'd have to start a new topic called what is accurate:-))) Anyway, listening to a guy playing an acoustic guitar live would by many be considered a true source of audio.... So if we have a mic that can actually capture the movements the gas molecules in air makes and translate those correctly into currents - then we can assume that at least the mic is giving us the true source...If the mic "Which it cant" could translate the audio one 100 percent accurately into current the mixing board would only "see" current actually VOLTS and treat those as such...if we were to apply no eqs and no effect at all - the next step of inaccuracy would be your speakers which would have to translate the currents and make the membranes vibrate - which would then again compress and rare-fact the gas molecules in the air - thus making u able to hear it....
    The mixing board is treating the current coming from the mic more or less constantly the way it came from the mic - the digital converters are only treating what comes from the mic 44100 times per second - this is why analog is called analog and is seen as treating the signal the way we hear it....
    What do we hear - and what is there and what is our brain doing.....
    the air that is being put in motion by a source being a true source or speakers is hitting our ears with the speed of sound - our ears are like a mic we a picking up differences in the molecules and our brain is translating it into what we call sound... Digital audio is actually exploiting our imperfections this is why we only need to sample 22050 times per second (Hearing Threshold) - the actually reason for sampling at twice the freq of hearing is because of the problem that causes the low pass filters to be there in the first place...(why the lowpass filters are needed would be too long to desribe)
    The reason for 44100 is the hearing threshold of 22050 Hz - I dont really no anyone above thirty that can hear above 18000 Hz and make use of what he is hearing - so why not sample at 16000HZ - or 32000 Hz - the reason is mirroring cuz of imperfect sinuses - and facts of a physical law : There can be no 90° Low pass filter....
    An EQ works with phase displacement - what actually happens when u cut 4 KZ by 4 db. is that the original signal is being phase displaced at the freq. u enter - what happens is that those freq.'s are being less amplified - There are physical laws about waveforms e.g. when two waves layer each other at the same maxima you will gain 6 db aka doubling the amplitude...when two waves hit each other where one has maxima and the other minimum you'll achieve complete cancelation...
    what really happens when u talk analog dist. is that the sinus(Wavesform) is being distorted so it looks more like a triangular waves form.... This gives us a feeling of loudness and warmth...
    If u want your digital mix to sound loud - take the "beautiful" sinus and turn it into a triangle by changing the gain - after that you will see the wave form being cut at the top and bottom but it aint sounding bad - only louder - Unless u overdo it:-))))
    There's a lot more to it than what I just described - and it is quite interesting - If u go to amazon.com there are two kind a books about his stuff...1) The book describing it fragmental like I just did and Books that really describing it according to physics....Latter mentioned are VERY dry but if u take the time and have the interest you will find them real helpful and it will also change the way you "Look" at audio and mixing and recording
    This is a huge topic consuming man since the day of recording audio...
    analog |ˈanlˌôg; -ˌäg| (also analogue) noun a person or thing seen as comparable to another : the idea that the fertilized egg contains a miniature analog of every adult structure. • Chemistry a compound with a molecular structure closely similar to that of another.
    G5 Dual 2.3 GHZ   Mac OS X (10.4.5)   PT HD3 / 4x ApoGee Rosetta 800 / 8GB RAM / 1TB HD
    G5 Dual 2.3 GHZ   Mac OS X (10.4.5)   PT HD3 / 4x ApoGee Rosetta 800 / 8GB RAM / 1TB HD
    G5 Dual 2.3 GHZ   Mac OS X (10.4.5)   PT HD3 / 4x ApoGee Rosetta 800 / 8GB RAM / 1TB HD
    G5 Dual 2.3 GHZ   Mac OS X (10.4.5)   PT HD3 / 4x ApoGee Rosetta 800 / 8GB RAM / 1TB HD

Maybe you are looking for

  • Airport Express just stopped working

    I have been using the airport express fine just until few days ago. I've being it using it with an ethernet cable connecting it fron my linksys router. (had it in bridge mode) Everything was fine until few days ago, when the "airport express" just di

  • I have a macbook pro.How do I stop the color wheel from spinning?

    I have a macbook pro.How do I stop the color wheel from spinning? I can not get the computer to shut down w/out doing a force quit.

  • Why a different Plug In Icon?

    I've been getting different results running Applets on a web page depending what system I'm running them on. Have tried different versions of Internet Explorer, Java Plug-In etc. but can't understand why the different results. VISUALLY THERE IS ONE B

  • Can't open any iWork apps

    Just upgraded to this iMac from my 2002 G4, and had iWork pre-loaded, just because. I can't open any of the applications, just get an error message. I tried removing and reinstalling, starting form the OSX install disc and using disc utility to corre

  • How to use IMAC CD drive from MBA

    We have a new MBA i want to install a game that i have that came on a CD.  I have installed the game on our IMAC and am told that i can access the cd drive on the IMAC from the AIR to install things to the AIR that come on CD. How do i do this?  Any