General :: Fedora - Display Has Red Tint When Using DVI Input
Jun 12, 2011
My monitor seems to have a slightly reddish tint when using the DVI input (it's a LCD, not a CRT). On the VGA input I can adjust the colors, but not on DVI. On OSX/Windows what I would do is create a custom color profile for that display with changed gamma/etc settings, but I cannot seem to find out how to do this under Linux. Is there any way to change the color profile under linux (short of buying color calibration hardware and using dispcalgui)?
Have a Compaq Presario SR1915AN desktop with a NVIDIA GeForce 6150 LE it has a dual boot of Windows XP and Debian 5.0.6 which would only run in 800x600 mode.I decided to install Ubuntu 10.10 Desktop as this is what is on another different machine, thought it would be safe.The install wouldn't work, I would get the purple selections screen and first time chose the normal graphic mode, 10 seconds or so in to the install the scrren goes dead and i see the "No Signal Input" display show on the screen. Rebooted and selected text mode install, this time it fully installed but on reboot it again has the screen goes dead 10 seconds after you select from the Grub screen.
I am using LuckyBackup to back up my laptop disk to a USB disk. I would like to display to the user the message "Please mount backup disk" and have the user click "OK". LuckyBackup has a feature to allow issuing commands before it does the backup. I have been investigating scripts (I have never written one.), but do not understand how to use them to this end.
My problem is on bootup and shut down I get: analog input cannot display this video mode. I've got a dell monitor nvidia graphics card. Don't really know how to provide much more info than that. From what I've searched on the net is that it probably has to do with the refresh rate.
I suddenly seem to be having a small issue with my laptops LCD. Recently, when I cold boot the laptop I will get a line of single pixel width running from the top to the bottom of the screen. This only seems to appear when the x server or the windows gui starts. Now if I turn off the screen after the line appears (e.g. closing the laptop lid while switched on) the line will sometimes disappear and all will be as normal. However, on the next boot I may see the line again. The line has a yellow-ish tint and always appears on the same spot. It appears on both windows XP and Ubuntu, so I assume it's a hardware issue? The line appears even when I have a blank screensaver on.
I did not have any /etc/X11/xorg.conf, so I read on these forums that system-config-display would create one for me. I ran system-config-display and it created an xorg.conf. But now my display is all messed up!! So, I deleted the xorg.conf and nothing changed. Why on earth would the display still be messed up if I deleted the file that was causing it?? Does system-config-display change somethign else?
I have the following scenario that doesn't seem to work normally. I have a windows 7 pc from which I am using putty to connect to my other linux servers (all running redhat 5 and 6). So here is the scenario that works and one that does not work. And I'm trying to figure out the one that does not work. Scenario that works:
From windows 7 (putty) I ssh into Linux_Server_1. echo $DISPLAY localhost:10.0
I run xclock and I see it pop up on my windows 7 pc. I am using xming on windows 7 to help me populate the display from linux to windows. One that does not work:
From windows 7 (putty) I ssh into Linux_Server_1. Then from Linux_Server_1 I ssh into Linux_Server_2. echo $DISPLAY <no output>
I try to setup $DISPLAY with localhost:10.0 or 0.0 or even my windows 7 pc ip address:0.0 ....etc Then when I try to run xclock I doesn't work.
I get these error messages: Error: Can't open display: <ip of display>
Also as a side note all our Linux servers are sitting on one subnet. My pc is sitting on another subnet. I use vpn to connect to the subnet where the servers sit from my pc.
I have just installed KDE 4.4 on Fedora 12 in addition to GNOME. The default Display resolution is the highest available. I changed it to a lower resolution. However, when I reboot, the resolution switches back to the default setting.
I recently got a real fancy unidirectional microphone, but when I go and use it, something strange happens. The mic is a mono mic, but when I record something, it appears to think it's stereo. Instead of having the same thing on both channels, it puts it all in the left channel, and silence on the right channel.
I tried fiddling with alsamixer. In capture (F4), adjusting the "Capture" device has an effect. However, it doesn't do anything useful. Lowering the right channel to zero does nothing, lowering the left channel to zero creates silence, and disabling the right channel creates silence.
In my System>Preferences>Sound (or pavucontrol, or what-have-you), there are "Analog Stereo Input" and "Analog Stereo Duplex" options there, but no "Analog Mono Input" or "Analog Stereo Output + Analog Mono Input" options (the latter being ideal).
Something interesting, though, if I do this: Code: arecord -r 96000 -D pulse -c 1 -vv -V mono /dev/null it works correctly and outputs on both channels. But if I do Code: arecord -r 96000 -D pulse -c 2 -vv -V stereo /dev/null then it's back to the same behavior. The VU meter on the second command shows the left channel going up and down as I make noise, but the right one always at zero.
The machine does have a crap internal mic built in to the screen bezel. If I do either of the above commands, they both work correctly. The stereo VU shows the same activity for both channels.
The machine is a Eee 1015PED, which has Intel integrated sound. Something probably insignificant is that the mic has a 1/4 inch mono plug, and to get it to plug into the Eee, I needed to get a 1/4 female to 1/8 male adapter. The mic's 1/4 plug is mono (duh) and therefore two-conductor, but the adapter I got is stereo, or three conductor (L, R, GND). I don't know if this is tripping something in hardware to tell it it's stereo or something.
I tried the mic on my desktop, which has a SB Audigy 4 (the non-pro flavor) and that has the "Analog Mono Input" function, so that works fine. Is there some way to turn this stereo input into mono input?
I am Currently attempting to set up a Dual Screen setup at my work but seem to be having some strange results. For some reason the O/S is only recognising one of the monitors, it knows exactly what the Make and model of the monitor is but doesnt appear to know that there is another monitor plugged in. It constantly says that there is 2 screens plugged in but lists the second screen as "CRT-0" even if no DVI cable is plugged into the second screen. This has really troubled me and has really got me thinking. I have set-up other Dual-screen setups with exactly the same hardware previously and it has worked fine? I am using a Lenovo A58 Tower with an Nvidia Quadro FX-380 Graphics card that I know is capable of dual Dual-link DVI output! With 2 x LG W3000-H Monitors running Fedora 12.
I have installed fedora 10 successfully but when reboot the system after installation not initrd or vmlinuz load and display first blue screen and some processing show after this blank screen display and held the system please tell me what should I do? I have reinstall many times but the problem is same.
I installed Lucid. I used to have Ubuntu 9.10 and to connect my iPod to my laptop's speakers. There was an option in 9.10 in the Sound Options to change the Mic Input into a Line Input. But now unfortunately I can't find it in Lucid have only 2 audio ports in the laptop: Headphone port, Mic port.
I would like to use Japanese kana (hiragana, katakana, kanji) on Ubuntu but everything that I've tried to get it set up and running isn't working. The Spanish that I have set up is working perfectly so far.
I've read, the SCIM input program should start up automatically when loading a program, it doesn't. When I have it loaded I cannot seem to get the input working.
I use the bios to dual boot between two disks, (1) this op sys and (2)win98se - where I have a driver that fully supports the nvidia.
The disadvantage to my current situation is that there are some programs - eg Evolution - that assume I can see more than you see with this setup - eg the buttons at the bottom of the screen do not appear and i have to do a trial and error tabbing to get what i want. I just downloaded openoffice and i see that it wants 1000x2000 or so. Thus I wont even try to install it unless i can resolve the adapter thing.
I'm very happy with this fedora - use it for software development. But as I become more fond of it, I would like to use it instead of windows - which I can't unless i can see the whole screen
At one point - in response to a suggestion that I download security updates - I did so and got 18.104.22.168-115.fc12.i686. It was incompatible with my config - put up a screen that looked like a tv test pattern and went into a loop. So I went back to 22.214.171.124-127.fc12.i686.
I booted my Fedora 13 live CD on my Dell server, and configured networking and SSHd. On my desktop I logged into the live cd and started copying over a big file (1.5 GB) (i.e. copying from the desktop computer to the server). After copying about half the fil, the download fails with an error message about the filesystem being read-only.I've seen this exact same behavior on both i386 and x86_64 of the same live CD, but don't know why it's happening. I've also had the same issue when copying small files. In /var/log/messages these messages are repeated many times:
Code: Dec 20 12:32:23 localhost kernel: Buffer I/O error on device dm-0, logical block 684075 Dec 20 12:32:23 localhost kernel: lost page write due to I/O error on dm-0
The microphone input of the soundcard itself (it is an on-board Realtek card, standard with most Nforce4 boards) works just fine. Recording quality is very good. But when I try to use the mic input on the front of my PC case, pulseaudio receives no signal from the microphone. Skype doesn't work, Audacity can't record anything either.
Everything is wired inside the case just fine, Windows XP has no problems in using the input on the front. Also the Line-out at the same panel on the front works in F12 without problems, it is just the mic input that doesn't work.
I'd like to use Korean but have an English keyboard, an English environment, and need to input via this method. It appears that there is currently no way to use ibus and have the functionality of the "hangul-romaja" tables that SCIM had. For example, it used to be, using Hangul-romaja, that I could type the letters "g" and "a" to get the Korean "가" (ga).
Now, the moment I type "g" it automatically writes. Typing "g" and "a" produces: Am I just doing something wrong? Using Anthy in Japanese works just fine...typing "g" and "a" produces a "が" just like it's supposed to. Anyone out there know what to do to get Hangul-romaja (or something similar!) working in ibus? Am I stuck having to just guess at the Korean keyboard layout or memorize it somewhere? Might there already be an ibus-compatible solution for this?
I have a Kore Controller from Native Instruments [URL] using it as a sound card on Fedora 12. Its input knobs are supported by Linux, too, but they are pretty useless for me.It came out that these input knobs send mouse movements from time to time, letting my mouse pointer jumping to the upper left corner of the screen.
So I want to disable the knobs, i.e. I want X to not interpret these "knob actions" as mouse movements. What is the best way to achive this? Can I disable it somewhere in HAL configuration or do I have to modify xorg.conf? And how do I do this?Simply plugging out the Kore Controller is not an option for me because I use it as sound card.
I recently installed Fedora 12 -- a brand new install, not an upgrade. The system was previously using Fedora 11 without any problems. Fedora 12 installed without any issues, and I haven't really done any customization to it. I am running KDE. The system is hooked up a KVM switch.
When I am on system #2 (a Windows system) and I switch back to system #1 (Fedora) after a few minutes of time, the Fedora screen will be blank and the monitor will present an "input signal out of range" error. I can SSH into the box and kill X to get the screen back. This has not happened on this system with any previous versions of Fedora that had been running on it (everything since Fedora 7).
Yesterday my Japanese input on F11x64 broke horribly. I have been using iBus all along, and didn't think I did any upgrades, but maybe there was a restart that picked up something previous. As soon as I hit the key to turn on the input method to type Japanese there would be a python process using 100% cpu, but no keyboard input. After fiddling about reinstalling python, iBus, scim and anthy and anything I else I could think of, I decided to upgrade to F13 to see if it would fix it. (trying to use scim instead of iBus hung the machine during start-up after login (I'm using KDE too if that makes any difference)). I did an upgrade instead of a fresh install fyi...
F13 is no better, and has the same issues with the python process. I have tried reinstalling everything again, as well as trying to avoid scim altogether, and just running iBus and Anthy. (The only other issue that I can think of (that prompted the initial restart) was that my .xsession-errors file in my home directory became huge -> 1.7gb!) Japanese input is crucial to my work (It doesn't even work if the default language of the system is set to Japanese), so hope someone has some ideas on how to resolve this, or even just knowing tha japanese is working for someone on a x64 KDE install would be encouraging...
So I want to be able to listen to sound coming in on the line in port. The sound does work as I have tested with Gnome sound recorder. However, I would like to be able to hear it all the time. I don't want to have to record to be able to hear it. Is there a way to mix the line input sound with the normal system sounds? This is so I can run sound from my Xbox 360 into my computer. I currently use a audio splitter but I get problems with volume levels due to voltage changes going to the speakers.
I upgraded from FC12 to FC14. I have a Samsung P2250 monitor which has both analog and DVI input. I have a Nvidia GE Force 8500 GT video card that also has analog and DVI ports. With FC12 I was using the DVI with no problem. After converting to FC14, the DVI does not work. If I use the analog ports, all is fine. I tried connecting both cables to see the results.
System - Preferences - Monitor shows 2 monitors. I assume that it is pickup both cables and thinks there are two monitors. I can turn either one off or on. If I turn the analog one off, the screen goes black until the 'Do you like this ' times out. It then comes back and I can work again. If I turn the digital one off, all works fine. If I disconnect the analog cable and boot the system, the POST messages show up, the GRUB menu shows up, but the screen goes black when FC14 loads.