I am very close to a complete Fridge wipeout.
I currently have
- A wonderful big Cauliflower {needs to be used this weekend}
- 2 frozen bananas
- 1 ripe tomato {priority use this weekend}
- 1 orange
- 1/4th lb okra {super priority use maybe tomorrow}
- Ginger
- Garlic
- Some hot chillies
Well.. maybe not that close but still this is a reflection of workload. I think I might reach the wipout this weekend and give the fridge a scrubdown before I go grocery shopping.
Tinypliny's Journal
My Podcast Link
10/19/2011 19:20 #55335
Complete Fridge Wipe OutCategory: eating in
10/17/2011 19:29 #55328
[Solved] External Monitor problems on Fedora 15Category: linux
Found a nice solution to the crazy external monitor problem in Fedora 15:
Download the latest release of ARandR from here:
Extract to some directory and navigate to that directory:
Run arandr.
All external display problems SOLVED! Woohoo. Thank you, Christian Amsuess. You simply rock. I saw they are trying to get this nifty program reviewed to include it in the Fedora yum repository For such a wonderful program that replaces the crap they have in gnome 3, the brutal review process seems somewhat counterproductive.
The Extended monitor display works. However, if I assign the external monitor as the primary display, it doesn't work. It gives me a blank backlit screen. WHYYYY?
I really need one of these counters now.
The number matches. I have the exact expression too.
In addition, I feel like I could outshout the incredible hulk anytime after /var/log/messages records an exception that could have well read, "You wouldn't like me when I'mangry normal".
Last few lines from /var/log/Xorg.0.log
Download the latest release of ARandR from here:
Extract to some directory and navigate to that directory:
cd /arandr-0.1.5/
Run arandr.
./arandr
All external display problems SOLVED! Woohoo. Thank you, Christian Amsuess. You simply rock. I saw they are trying to get this nifty program reviewed to include it in the Fedora yum repository
For such a wonderful program that replaces the crap they have in gnome 3, the brutal review process seems somewhat counterproductive.The Extended monitor display works. However, if I assign the external monitor as the primary display, it doesn't work. It gives me a blank backlit screen. WHYYYY?
I really need one of these counters now.
The number matches. I have the exact expression too.
In addition, I feel like I could outshout the incredible hulk anytime after /var/log/messages records an exception that could have well read, "You wouldn't like me when I'm
Last few lines from /var/log/Xorg.0.log
[ 2244.948] (II) intel(0): EDID vendor "HWP", prod id 9896
[ 2244.948] (II) intel(0): Using hsync ranges from config file
[ 2244.948] (II) intel(0): Using vrefresh ranges from config file
[ 2244.948] (II) intel(0): Printing DDC gathered Modelines:
[ 2244.948] (II) intel(0): Modeline "1680x1050"x0.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz)
[ 2244.948] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
[ 2244.948] (II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
[ 2244.948] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
[ 2244.948] (II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
[ 2244.948] (II) intel(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
[ 2244.948] (II) intel(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz)
[ 2244.948] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
[ 2244.948] (II) intel(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz)
[ 2244.948] (II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
[ 2244.948] (II) intel(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz)
[ 2244.948] (II) intel(0): Modeline "1152x720"x60.0 67.32 1152 1208 1328 1504 720 721 724 746 -hsync +vsync (44.8 kHz)
[ 2244.948] (II) intel(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz)
[ 2244.948] (II) intel(0): Modeline "1440x900"x0.0 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz)
[ 2244.948] (II) intel(0): Modeline "1600x1000"x60.0 133.14 1600 1704 1872 2144 1000 1001 1004 1035 -hsync +vsync (62.1 kHz)
[ 2261.254] (II) intel(0): EDID vendor "SEC", prod id 21825
[ 2261.254] (II) intel(0): Printing DDC gathered Modelines:
[ 2261.254] (II) intel(0): Modeline "1366x768"x0.0 72.33 1366 1414 1446 1526 768 770 775 790 -hsync -vsync (47.4 kHz)
[ 2262.258] (II) intel(0): EDID vendor "SEC", prod id 21825
[ 2262.258] (II) intel(0): Printing DDC gathered Modelines:
[ 2262.258] (II) intel(0): Modeline "1366x768"x0.0 72.33 1366 1414 1446 1526 768 770 775 790 -hsync -vsync (47.4 kHz)
[ 2262.353] (II) intel(0): EDID vendor "SEC", prod id 21825
[ 2262.353] (II) intel(0): Printing DDC gathered Modelines:
[ 2262.353] (II) intel(0): Modeline "1366x768"x0.0 72.33 1366 1414 1446 1526 768 770 775 790 -hsync -vsync (47.4 kHz)
[ 2262.467] (II) intel(0): Allocated new frame buffer 1728x1050 stride 7168, tiled
[ 2293.167] (II) intel(0): EDID vendor "SEC", prod id 21825
[ 2293.167] (II) intel(0): Printing DDC gathered Modelines:
[ 2293.167] (II) intel(0): Modeline "1366x768"x0.0 72.33 1366 1414 1446 1526 768 770 775 790 -hsync -vsync (47.4 kHz)
[ 2293.280] (II) intel(0): Allocated new frame buffer 3072x1050 stride 12288, tiled
10/16/2011 20:39 #55323
Nvidia and Intel Graphics in Fedora 15Category: linux
There's something really wrong with my setup here:
Even though there is now a driver in use (installed from here: ) I still cannot adjust my resolution. I didn't install nVidia's own driver because of this article:
There is only ONE resolution in the display settings (1024X768). Attaching an external monitor results in the computer shutting down on its own. And there is no way to adjust brightness.
Aarrgh. Frustration ++. I am just going to ignore this today. I have too much work piled up.
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: nvidia
Kernel modules: nvidia, nouveau, nvidiafb
Even though there is now a driver in use (installed from here:
) I still cannot adjust my resolution. I didn't install nVidia's own driver because of this article: There is only ONE resolution in the display settings (1024X768). Attaching an external monitor results in the computer shutting down on its own. And there is no way to adjust brightness.
Aarrgh. Frustration ++. I am just going to ignore this today. I have too much work piled up.
10/16/2011 16:42 #55318
Fedora 15 with XFCE. Some NotesCategory: linux
Remove irritating desktop icons from view.
Getting information about package versions from Yum
Side note to (e:paul): R does pull in the following dependencies:
It's such a pity the packages it pulls are from 2007! :/
And Gnumeric doesn't even start up now. Something about:
- desktop settings > icons > icon type > choose "None"
Getting information about package versions from Yum
- yum info packagename
Side note to (e:paul): R does pull in the following dependencies:
texlive.x86_64 0:2007-62.fc15
texlive-dvips.x86_64 0:2007-62.fc15
texlive-latex.x86_64 0:2007-62.fc15
texlive-texmf.noarch 0:2007-37.fc15
texlive-texmf-dvips.noarch 0:2007-37.fc15
texlive-texmf-fonts.noarch 0:2007-37.fc15
texlive-texmf-latex.noarch 0:2007-37.fc15
texlive-utils.x86_64 0:2007-62.fc15
It's such a pity the packages it pulls are from 2007! :/
And Gnumeric doesn't even start up now. Something about:
gnumeric: symbol lookup error: /usr/lib64/libspreadsheet-1.10.17.so: undefined symbol: go_direction_get_name
- In Debian, you can actually, copy the entire /var/apt/cache files into a new installation and have the apt manager pull the .deb files from there without having to download packages over and over. But I don't see any such package repository in Fedora in the /var/cache/yum/ directory. It's all rolled into some sort of a database file. I found from this link that yum *deletes* everything after install. This is kind of wasteful for people who have enough space but not enough bandwidth(ME!). To prevent yum from deleting all the packages after install, apparently, I need to make keepcache=1 in /etc/yum.conf Now I only need to remember this detail next time.
- These are my detailed specs just for reference...
10/16/2011 07:10 #55314
Making a bootable USB in LinuxCategory: linux
Sometimes the simplicity of things across all distributions of linux are most refreshing. To burn an iso into a USB and create a bootable USB, I was glad to find out that I didn't need to hunt for programs as I usually do. I could do it in 4 steps.
(e:Paul) would like to remind everyone that this method completely gets rid of all the existing data on the USB drive so do it on an expendable one not somewhere you have all your backup files.
Pull up a terminal.
Pull up the system messages by
This records the realtime happenings on your system
Plug in your USB, you'll see it coming up on the messages window
Let's say its /dev/sdb
At this point (e:uncutsaniflush) would like to say:
You should also note that this only works if your usb drive is "/dev/sdb." If a box has multiple hard drives, it is unlikely that "/dev/sdb" would be your usb drive. If someone had for example two hard drives, "dev/sdb" would be the second one. And thus, all data on the second hard drive would be destroyed. "dd" is a wonderful tool but rather easy to misuse if one isn't absolutely clear which drive is which.
On the terminal again, umount it first
Go to the directory containing the iso image
Then give the simple command to burn the iso into the USB
This will take a while to finish, but yes, it's that simple.
(e:Paul) would like to remind everyone that this method completely gets rid of all the existing data on the USB drive so do it on an expendable one not somewhere you have all your backup files.
Pull up a terminal.
Pull up the system messages by
tail -f /var/log/messages
This records the realtime happenings on your system
Plug in your USB, you'll see it coming up on the messages window
Let's say its /dev/sdb
At this point (e:uncutsaniflush) would like to say:
You should also note that this only works if your usb drive is "/dev/sdb." If a box has multiple hard drives, it is unlikely that "/dev/sdb" would be your usb drive. If someone had for example two hard drives, "dev/sdb" would be the second one. And thus, all data on the second hard drive would be destroyed. "dd" is a wonderful tool but rather easy to misuse if one isn't absolutely clear which drive is which.
On the terminal again, umount it first
umount /dev/sdb
Go to the directory containing the iso image
cd /directory/that/contains/iso
Then give the simple command to burn the iso into the USB
dd if=file.iso of=/dev/sdb
This will take a while to finish, but yes, it's that simple.
tinypliny - 10/16/11 19:48
Yes! That is an important point. My two hard drives were attached to the comp when I did this and my USB was actually scc or some such thing. Unetbootin is good, but sometimes, it doesnt work for some distros. I wonder why...
Haven't tried imagewriter.
Yes! That is an important point. My two hard drives were attached to the comp when I did this and my USB was actually scc or some such thing. Unetbootin is good, but sometimes, it doesnt work for some distros. I wonder why...
Haven't tried imagewriter.
uncutsaniflush - 10/16/11 18:33
You should also note that this only works if your usb drive is "/dev/sdb." If a box has multiple hard drives, it is unlikely that "/dev/sdb" would be your usb drive. If someone had for example two hard drives, "dev/sdb" would be the second one. And thus, all data on the second hard drive would be destroyed. "dd" is a wonderful tool but rather easy to misuse if one isn't absolutely clear which drive is which.
Both unetbootin :::link::: and imagewriter :::link::: are good gui alternatives to using ""dd" in a cli.
You should also note that this only works if your usb drive is "/dev/sdb." If a box has multiple hard drives, it is unlikely that "/dev/sdb" would be your usb drive. If someone had for example two hard drives, "dev/sdb" would be the second one. And thus, all data on the second hard drive would be destroyed. "dd" is a wonderful tool but rather easy to misuse if one isn't absolutely clear which drive is which.
Both unetbootin :::link::: and imagewriter :::link::: are good gui alternatives to using ""dd" in a cli.
tinypliny - 10/16/11 09:22
done, though I sometimes think everyone gets what they deserve for stupidity including me ;-)
done, though I sometimes think everyone gets what they deserve for stupidity including me ;-)
paul - 10/16/11 09:17
You should note this destroys all data on the USB drive before some reads this and does it with a drive that conatins all of their backup files.
You should note this destroys all data on the USB drive before some reads this and does it with a drive that conatins all of their backup files.
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?