- learning a somewhat new language (R)
- trying to code in it using concepts from statistics that I already have
- trying to generalize code so that it could be less repetitive and automate chores and processing
- trying to splice other languages such as latex and perl to interact with R code
- learning THOSE other languages
- trying to prevent errors in their interaction
- trying to write functions that would serve a purpose similar to "macros" on SAS but yet be understandable to me at a somewhat-novice level.
- debugging to see where it all goes wrong when errors turn up
- differentiating what is my code's fault, what can be changed in R preferences, and what is inherently the fault of the R build on the particular linux distro I am using.
Why am I doing this when I have a data manager for the data I am dealing with? Because it's insane to go whining to the manager the minute you want some data processing done. He has own Ph.D. to complete and has limited time and innumerable demands. So there is really no option but to power through all of this on my own. Besides, I think population sciences are *really* about statistics and data processing even though population scientists who don't do all this dirty work may persuade themselves that it is just about interpretation. It is as much about quality control in the data and seemingly trivial logical checks as it is about analyzing super-clean data in the end and figuring out what it could mean in the bigger picture of million other studies. I think it's important to acquire this skill so I can use it in my future. Not everyone has a data manager, a software coding bloke and a statistician to always help them.
The process itself is exhausting because it's like learning a completely new language without having ANY experience in how the semantics work. Apparently some people have observed this exhaustion and set up sites like "Software Carpentry":
It sets up a formalized framework within which you could learn these skills. I think courses like this should be mandatory to population sciences coursework. At some point, we need to realize that population sciences and bioinformatics are very similar in their scope and application. This is more true than ever as we progress rapidly towards HUGE datasets, complex data structures, multidimensional variables and the necessity of channeling all of this into interpretations simple enough to make sense to health-related and population policy-making.
Even better commands (thanks to (e:paul))
sudo geany /var/log/yum.log - just shows you a log of everything ordered by name
to order the last command
rpm -qa --queryformat '%{NAME}%{VERSION}%{RELEASE} was installed on %{INSTALLTIME:date}\n' --last
the --last works just as well as sorting
Better tracking: rpm -qa --queryformat '%{NAME}%{VERSION}%{RELEASE} was installed on %{INSTALLTIME:date}\n' > package
Got it!! rpm -qa --queryformat '%{NAME} was installed on %{INSTALLTIME:date}\n'
As a general rule, it is a good idea to update after an fresh install unless you have a specific reason not to. Some installers will do it for you. Sometimes you will end up with library, kernel, and/or dependency problems if you only update/install specific apps without doing a general update.
As to upgrading from one version of a distro to new one, I always perfer to do a fresh install of the new version instead of an "update" install. As to updating to a new version from inside a distro, it all depends. I don't have a general rule.
If nouveau is working you don't need nvidiafb. At the very least blacklist it. Also remember that you shouldn't have nvidia and nvidiafb at the same time. They don't like each other and do not play nice.
The brightness thing may be a permission thing since the settings only work for a session. You may need to add your user to the admin or wheel or something like that.
Do you do a complete update every time you install a distribution? sudo yum update? Or do you let things be if they are running fine after the fresh install?
Not going back to xfce version even though gnome 3 is a pain to deal with (for me). A working stable environment is way more important than a few inconveniences.
thanks, taking all your advice. Is this the correct virtual box site? :::link:::
(e:uncut): I tried the live gnome cd and this is the output:
01:00.0 VGA compatible controller [0300]: nVidia Corporation Device [10de:0df4] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Toshiba America Info Systems Device [1179:fc31]
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at f6000000 (32-bit, non-prefetchable) [size=16M]
Memory at e0000000 (64-bit, prefetchable) [size=256M]
Memory at f0000000 (64-bit, prefetchable) [size=32M]
I/O ports at e000 [size=128]
Expansion ROM at f7000000 [disabled] [size=512K]
Capabilities: [60] Power Management version 3
Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [78] Express Endpoint, MSI 00
Capabilities: [b4] Vendor Specific Information: Len=14
Capabilities: [100] Virtual Channel
Capabilities: [128] Power Budgeting
Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024
Kernel driver in use: nouveau
Kernel modules: nouveau, nvidiafb
Brightness and external monitors work but brightness settings are never remembered.
I didn't try the fedora live xfce version because I had to wipe it out to put the gnome version on (I lost a couple usbs recently so I am running short of spare ones).
I concur with (e:paul). but still I would run the live fedora (be it xfce or gnome) to confirm that the nouveux driver works before doing a reinstall. But I tend to trust (e:paul) that it would work.
I wouldn't even play with the nvidia drivers as nouveux should be working fine for what you need.
Here is my advice. Reinstall Fedora, install virtual box from the oracle site. Install another copy of fedora in there. Test anything in the virtual fedora before you apply to the real fedora. That way you won't keep messing up your comp and can continue to work.
Ok, here's my advice, run Fedora-xfce live. If it works, you know it is something you installed post-install that is fucking up your system. Look at what kernel modules are loaded. If the live cd works, make sure only that module is loaded on your installed system.
When you installed did you do a fresh install or an update? to put in other words, did you format your root partition before installing fedora-xfce? If you didn't everything from the old install is probably still floating around.
My experience is that you can't have both the nvidia and the nouveau kernel modules loaded at the same time without bad shit happening.
Somehow you managed to install nvidia kernel modules from somewhere. At the very least blacklist one or the other.
Nothing that you installed with :::link::: should have kernel module graphics drivers. I'm with (e:paul) on that.
Its just a theory though. In addition, I added
-- texmaker
-- texstudio
-- gnumeric
-- pinta
there were mpeg and other video codecs in the bundle. :::link:::
Okay, thats crazy. Something else must have been installed. The mp3 codecs have nothing to do with the display driver.
I think the mp3 and other codecs caused the nvidia card Optimus thingy to kick in and this stalled the OS. It's my theory, because the error screen was only intermittent before. But after the codecs, it just stalled the entire OS from booting.
Nope. It stalled in the black screen of death after I put in the mp3 codecs. I couldn't rescue it so I put in fedora xfce. This is the state after fedora xfce.
How did you get it to this point. It was not like this originally from your bro, was it?