Published on 3rd December 2009 by
Just because he didn't do it "The package manager way", doesn't mean you CAN'T do it "The package manager way".
Originally Posted by Phil RhodesSo why didn't he? Because he's a linux user and he has an unquenchable need to prove how clever he is by doing everything in the most complicated and difficult way possible? Does he walk everywhere on his hands as well?
One of the main causes I find for advanced text-file hackery on Linux is doing exactly this sort of thing. In my experience in order to install anything the community has arbitrarily decided is "non-free" you end up "adding repositories", which involves adding things to various text files and typing commands beginning with "apt-get" which invariably fail. That's what I mean, and yes, yes, that is very much too complex for me just for the sake of installing a single program. Only someone who's been stuck on Linux for years could possibly consider this normal or appropriate.
Originally Posted by steveo_mcgPhil since you clearly have no interest in using linux why do you bother coming in a trolling the threads regarding it?
Fact is there are menu options to do things in this distro but since the internet is text based its actually easier to read then copy paste text commands than it is to follow your way through a 4 level deep hierarchical menu to then follow a serise of click here do this click here do that sequence of help that if you miss a bit can land you even more confused.
I would strongly recomend that anyone connecting via the HDMI to start learning about Mode Lines for the xorg.conf.
Originally Posted by Phil RhodesSometimes you have to research your examples, and sometimes, well, they're just handed to you on a plate :)
Originally Posted by Phil RhodesYes Steve.
That's Windows in a failure mode being about half as complex as Linux is as a matter of course.
I mean - what exactly is a mode line, and what would be an appropriate one for my Toshiba TV?
Validating Mode "1920x1080":
(II) Dec 03 17:23:02 NVIDIA(0): 1920 x 1080 @ 60 Hz
(II) Dec 03 17:23:02 NVIDIA(0): For use as DFP backend.
(II) Dec 03 17:23:02 NVIDIA(0): Mode Source: EDID
(II) Dec 03 17:23:02 NVIDIA(0): Pixel Clock : 148.35 MHz
(II) Dec 03 17:23:02 NVIDIA(0): HRes, HSyncStart : 1920, 2008
(II) Dec 03 17:23:02 NVIDIA(0): HSyncEnd, HTotal : 2052, 2200
(II) Dec 03 17:23:02 NVIDIA(0): VRes, VSyncStart : 1080, 1084
(II) Dec 03 17:23:02 NVIDIA(0): VSyncEnd, VTotal : 1089, 1125
(II) Dec 03 17:23:02 NVIDIA(0): H/V Polarity : +/+
(II) Dec 03 17:23:02 NVIDIA(0): Mode is valid.
ModeLine "1920x1080@60" 148.35 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
I had the same issue with a Dell optiplex 620 at work, use the xp driver, however when running the driver install/setup .exe file, make sure you set the copmpatability mode* to XP and that you run it as an administrator**, it should work.
*Right click on the .exe select properties, select the compatability tab, enable and select XP SP3.
**Right click the file and select "Run as administrator".
Code Listing 3.2: Invoking alsaconf
You will now see a neat menu guided interface that will automatically probe your devices and try to find out your sound card. You will be asked to pick your sound card from a list. Once that's done, it will ask you permission to automatically make required changes to /etc/modprobe.d/alsa.conf. It will then adjust your volume settings to optimum levels, run update-modules and start the /etc/init.d/alsasound service. Once alsaconf exits, you can proceed with setting up the ALSA initscript.
If you want me to copy my Xorg.conf file and post it ill gladly do that if it helps :)
Originally Posted by Phil Rhodes
No thankyou I'll use professionally-written graphics software so that it works without any of this needless shenanigans...
You are not logged in, please login with your forum account below. If you don't already have an account please register to start contributing.
27th September 2016
26th September 2016
23rd September 2016
© Copyright bit-tech