My new deadline is December 31. I am dead serious about this and want to finish it once and for all. Even if lake Erie burst into flames right now and it was a grand public spectacle, I wouldn't want to go see it more than I want to finish my dissertation writing.
So I am taking off the internets and (e:strip) till the next year.
All of you, happy holidays and behave yourselves.
cheerio,
TP
Tinypliny's Journal
My Podcast Link
12/23/2011 15:38 #55788
Off.Category: goals
12/19/2011 21:13 #55775
Graphic detailsCategory: linux
rpm -qa *\nvidia\* *\kernel\*|sort;uname -r;lsmod |grep -e nvidia -e nouveau;cat /etc/X11/xorg.conf
Hmmm.. that doesn't look so good
rpm -qa *\nvidia\* *\kernel\*|sort;uname -r;lsmod |grep -e nvidia -e nouveau;cat /etc/X11/xorg.conf
nouveau;cat /etc/X11/xorg.conf
abrt-addon-kerneloops-2.0.6-1.fc16.x86_64
kernel-3.1.4-1.fc16.x86_64
kernel-3.1.5-1.fc16.x86_64
kernel-3.1.5-2.fc16.x86_64
kernel-headers-3.1.5-2.fc16.x86_64
libreport-plugin-kerneloops-2.0.7-1.fc16.x86_64
texlive-l3kernel-2011-4.SVN_2966.svn24657.fc16.noarch
3.1.5-2.fc16.x86_64
nouveau 754554 0
ttm 61533 1 nouveau
drm_kms_helper 30277 2 i915,nouveau
drm 213647 7 i915,nouveau,ttm,drm_kms_helper
i2c_algo_bit 5572 2 i915,nouveau
i2c_core 28203 7 videodev,i2c_i801,i915,nouveau,drm_kms_helper,drm,i2c_algo_bit
mxm_wmi 1743 1 nouveau
video 12388 2 i915,nouveau
cat: /etc/X11/xorg.conf: No such file or directory
PS: I would like a decent lighter background code box for christmas.
With
- Inconsolata monospace font
- line-wrapping
- syntax highlighting (even without syntax highlighting is fine really)
- for perl and bash.
tinypliny - 12/19/11 23:20
Yes, it works for me too. Just posted that for reference. No particular reason. I guess I like having information about my hardware/software out in the internets! :))
Yes, it works for me too. Just posted that for reference. No particular reason. I guess I like having information about my hardware/software out in the internets! :))
uncutsaniflush - 12/19/11 22:10
Fedora doesn't use xorg.conf. because X is configured automagically during the boot process. For most users that just works.
I think you could make yourself a xorg.conf file if you want.
Fedora doesn't use xorg.conf. because X is configured automagically during the boot process. For most users that just works.
I think you could make yourself a xorg.conf file if you want.
12/17/2011 20:51 #55762
More fedora 16 freezesCategory: linux
Thankfully, I waited for a complete 5 minutes (took (e:metalpeter)'s advice and went to get tea) instead of jumping on the power button. It recovered after taking its own sweet time.
This is the tail of the /var/log/messages. With all those mentions of killings and daemons, it totally looks like notes from a homicidal maniac with a medieval tilt.
Farther back the log has these entries:
It killed something in cold blood and is now gloating over it?
Apparently it is some bios issue as described here: 
According to the followup to that post, it's a kernel issue that sprang up after 2.6.38.7 The kernel is not able to balance loads on the CPU/GPU well in processors with a sandy bridge and gives rise to these errors. Updating the bios does not solve the issue.
Why does it ALL have to happen in my machine?! Seriously, this is not even my super-sucky original machine. It's a machine from my bro. Does the linux universe hate me or what?!
Dec 17 20:20:26 why udevd[11705]: timeout: killing '/sbin/blkid -o udev -p /dev/sdb1' [12021] Dec 17 20:20:27 why udevd[11705]: timeout: killing '/sbin/blkid -o udev -p /dev/sdb1' [12021] Dec 17 20:20:28 why udevd[11705]: timeout: killing '/sbin/blkid -o udev -p /dev/sdb1' [12021] Dec 17 20:20:28 why dbus-daemon[1173]: dbus[1173]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper) Dec 17 20:20:28 why dbus[1173]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper) Dec 17 20:20:28 why dbus-daemon[1173]: Launching FprintObject Dec 17 20:20:28 why dbus[1173]: [system] Successfully activated service 'net.reactivated.Fprint' Dec 17 20:20:28 why dbus-daemon[1173]: dbus[1173]: [system] Successfully activated service 'net.reactivated.Fprint' Dec 17 20:20:28 why dbus-daemon[1173]: ** Message: D-Bus service launched with name: net.reactivated.Fprint Dec 17 20:20:28 why dbus-daemon[1173]: ** Message: entering main loop Dec 17 20:20:29 why udevd[11705]: timeout: killing '/sbin/blkid -o udev -p /dev/sdb1' [12021] Dec 17 20:20:30 why udevd[11705]: timeout: killing '/sbin/blkid -o udev -p /dev/sdb1' [12021] Dec 17 20:20:31 why udevd[11705]: timeout: killing '/sbin/blkid -o udev -p /dev/sdb1' [12021]
This is the tail of the /var/log/messages. With all those mentions of killings and daemons, it totally looks like notes from a homicidal maniac with a medieval tilt.
Farther back the log has these entries:
Dec 17 16:17:19 why dbus-daemon[1173]: dbus[1173]: [system] Successfully activated service 'org.freedesktop.PackageKit' Dec 17 16:26:35 why kernel: [65687.762948] CPU6: Package power limit notification (total events = 2) Dec 17 16:26:35 why kernel: [65687.762956] CPU2: Package power limit notification (total events = 2) Dec 17 16:26:35 why kernel: [65687.762956] CPU1: Package power limit notification (total events = 2) Dec 17 16:26:35 why kernel: [65687.762965] CPU0: Package power limit notification (total events = 2) Dec 17 16:26:35 why kernel: [65687.762969] CPU4: Package power limit notification (total events = 2) Dec 17 16:26:35 why kernel: [65687.762972] CPU7: Package power limit notification (total events = 2) Dec 17 16:26:35 why kernel: [65687.762977] CPU5: Package power limit notification (total events = 2) Dec 17 16:26:35 why kernel: [65687.762977] CPU3: Package power limit notification (total events = 2) Dec 17 16:26:35 why kernel: [65687.773971] CPU5: Package power limit normal Dec 17 16:26:35 why kernel: [65687.773975] CPU2: Package power limit normal Dec 17 16:26:35 why kernel: [65687.773982] CPU4: Package power limit normal Dec 17 16:26:35 why kernel: [65687.773984] CPU6: Package power limit normal Dec 17 16:26:35 why kernel: [65687.773988] CPU3: Package power limit normal Dec 17 16:26:35 why kernel: [65687.773992] CPU7: Package power limit normal Dec 17 16:26:35 why kernel: [65687.773997] CPU1: Package power limit normal Dec 17 16:26:35 why kernel: [65687.773999] CPU0: Package power limit normal Dec 17 16:26:48 why kernel: [65700.686031] [Hardware Error]: Machine check events logged Dec 17 16:26:48 why mcelog[1166]: Hardware event. This is not a software error. Dec 17 16:26:48 why mcelog[1166]: MCE 0 Dec 17 16:26:48 why mcelog[1166]: CPU 2 THERMAL EVENT TSC 7740a8dc9110 Dec 17 16:26:48 why mcelog[1166]: TIME 1324157195 Sat Dec 17 16:26:35 2011 Dec 17 16:26:48 why mcelog[1166]: Processor 2 below trip temperature. Throttling disabled Dec 17 16:26:48 why mcelog[1166]: STATUS c0000000881b0c00 MCGSTATUS 0 Dec 17 16:26:48 why mcelog[1166]: MCGCAP c09 APICID 4 SOCKETID 0 Dec 17 16:26:48 why mcelog[1166]: CPUID Vendor Intel Family 6 Model 42 Dec 17 16:26:48 why mcelog[1166]: Hardware event. This is not a software error. Dec 17 16:26:48 why mcelog[1166]: MCE 1 Dec 17 16:26:48 why mcelog[1166]: CPU 1 THERMAL EVENT TSC 7740a8dcb633 Dec 17 16:26:48 why mcelog[1166]: TIME 1324157195 Sat Dec 17 16:26:35 2011 Dec 17 16:26:48 why mcelog[1166]: Processor 1 below trip temperature. Throttling disabled Dec 17 16:26:48 why mcelog[1166]: STATUS c0000000881b0c00 MCGSTATUS 0 Dec 17 16:26:48 why mcelog[1166]: MCGCAP c09 APICID 2 SOCKETID 0 Dec 17 16:26:48 why mcelog[1166]: CPUID Vendor Intel Family 6 Model 42 Dec 17 16:26:48 why mcelog[1166]: Hardware event. This is not a software error.
It killed something in cold blood and is now gloating over it?
According to the followup to that post, it's a kernel issue that sprang up after 2.6.38.7
The kernel is not able to balance loads on the CPU/GPU well in processors with a sandy bridge and gives rise to these errors. Updating the bios does not solve the issue.Why does it ALL have to happen in my machine?! Seriously, this is not even my super-sucky original machine. It's a machine from my bro. Does the linux universe hate me or what?!
tinypliny - 12/17/11 23:44
I followed that thread to the bugzilla on kernels: :::link:::
Its apparently not a bios issue anymore. Its now seen as an issue with how the kernel handling CPU and GPU loads in intel chips with a sandy bridge processor. They made a patch for it, but now are worried how it would affect performance on these chips.
So if /var/log/messages claims its a hardware issue, it might not really be true and might actually be about how the new kernel is treating the CPU/GPU. Confusion ++
I followed that thread to the bugzilla on kernels: :::link:::
Its apparently not a bios issue anymore. Its now seen as an issue with how the kernel handling CPU and GPU loads in intel chips with a sandy bridge processor. They made a patch for it, but now are worried how it would affect performance on these chips.
So if /var/log/messages claims its a hardware issue, it might not really be true and might actually be about how the new kernel is treating the CPU/GPU. Confusion ++
tinypliny - 12/17/11 22:46
Not that the productivity ruining freezes are not serious, but the freezes don't seem to be near these bios related hardware thermal problems...
Not that the productivity ruining freezes are not serious, but the freezes don't seem to be near these bios related hardware thermal problems...
tinypliny - 12/17/11 22:45
With my fabulous luck, what if I run into one of these issues with the new BIOS: :::link:::
I am wondering if it might not be a safer bet to live these thermal issues (or non-issues) rather than inherit some really serious problems...
With my fabulous luck, what if I run into one of these issues with the new BIOS: :::link:::
I am wondering if it might not be a safer bet to live these thermal issues (or non-issues) rather than inherit some really serious problems...
tinypliny - 12/17/11 22:41
Btw, I posted that VLC related error in the earlier post. Something connected with LIRC.
Btw, I posted that VLC related error in the earlier post. Something connected with LIRC.
tinypliny - 12/17/11 22:38
I have had this issue for quite a while. He didn't run into it. I am updating my bios as soon as I can (if there is an update, that is).
How about the other 1000 errors that are not connected to this particular error? :) The bios related error was a whole 3 hours before the freeze actually happened. The errors with the freeze (and around that pointframe) have no mentions of any thermal problems. They seem to be glitches in how fedora is handling mounted drives.
I have had this issue for quite a while. He didn't run into it. I am updating my bios as soon as I can (if there is an update, that is).
How about the other 1000 errors that are not connected to this particular error? :) The bios related error was a whole 3 hours before the freeze actually happened. The errors with the freeze (and around that pointframe) have no mentions of any thermal problems. They seem to be glitches in how fedora is handling mounted drives.
paul - 12/17/11 21:39
Oh I have the latest bios firmware on my laptops. However, if your bios is trigger thermal events it really is not fedora's fault. I never though to mention that but it does seem to be related to a hardware issue "Hardware event. This is not a software error." I guess that's a good thing in a way. There is also the possibility that you device is truly having thermal issues. Did you brother not run into this?
Oh I have the latest bios firmware on my laptops. However, if your bios is trigger thermal events it really is not fedora's fault. I never though to mention that but it does seem to be related to a hardware issue "Hardware event. This is not a software error." I guess that's a good thing in a way. There is also the possibility that you device is truly having thermal issues. Did you brother not run into this?
12/17/2011 05:58 #55757
Found it. DeaDBeeFCategory: music
VLC is misbehaving on my system. The GUI doesn't start up unless I invoke it on the terminal. I can't find a solution to the error that comes up and I don't have time to look. I just erased it out of frustration.
Here's the crazy error, (e:paul). Knock yourself out.
{and then VLC gui starts. It's insane to have to pull it up with the terminal.}
Which meant I looked for alternatives, and I found the beyond perfect replacement.
DeaDBeeF
It sounds gruesome but it is fantastic.
It has cuesheet support, a smashing 10 channel equalizer, tabbed playlist support, customizable colours, plays every lossless format and submits information to last.fm.
I suddenly and completely stopped missing foobar2000.
More importantly, the programs I miss from Windoze is now down to exactly 1.
PDFXchange Reader.
Here's the crazy error, (e:paul). Knock yourself out.
$ vlc
VLC media player 1.1.12 The Luggage (revision exported)
Blocked: call to unsetenv("DBUS_ACTIVATION_ADDRESS")
Blocked: call to unsetenv("DBUS_ACTIVATION_BUS_TYPE")
[0x13216c0] [rc] lua interface: Listening on host "*console".
VLC media player 1.1.12 The Luggage
Remote control interface initialized. Type `help' for help.
> vlc: could not connect to socket
vlc: No such file or directory
[0x13497d0] lirc interface error: lirc initialisation failed
[0x13497d0] main interface error: no suitable interface module
[0x134e1d0] oldtelnet interface: using the VLM interface plugin...
[0x134e1d0] oldtelnet interface: telnet interface started on interface localhost 4212
[0x121d120] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface.
Blocked: call to setlocale(6, "")
Blocked: call to setlocale(6, "")
(process:12794): Gtk-WARNING **: Locale not supported by C library.
Using the fallback 'C' locale.{and then VLC gui starts. It's insane to have to pull it up with the terminal.}
Which meant I looked for alternatives, and I found the beyond perfect replacement.
DeaDBeeF
It sounds gruesome but it is fantastic.
It has cuesheet support, a smashing 10 channel equalizer, tabbed playlist support, customizable colours, plays every lossless format and submits information to last.fm.
I suddenly and completely stopped missing foobar2000.
More importantly, the programs I miss from Windoze is now down to exactly 1.
PDFXchange Reader.
dhtj - 12/23/11 17:32
How you changed the interface/colors of DeadBeef? Mine is light gray with orange. I want it dark with green like yours.
How you changed the interface/colors of DeadBeef? Mine is light gray with orange. I want it dark with green like yours.
tinypliny - 12/17/11 20:33
I just re-installed it just so I could post the error. I am chucking it out now.
I just re-installed it just so I could post the error. I am chucking it out now.
paul - 12/17/11 18:04
I wonder what was up with you VLC. It always seems pretty reliable to me. We almost exclusively use it to watch video on our TV.
I wonder what was up with you VLC. It always seems pretty reliable to me. We almost exclusively use it to watch video on our TV.
tinypliny - 12/17/11 13:53
Eugh. Who knew?!
I just searched rather desperately for something that would play my cue files and submit info to last.fm
Eugh. Who knew?!
I just searched rather desperately for something that would play my cue files and submit info to last.fm
ajay - 12/17/11 12:45
"deadbeef" has a long history. It can be spelled in hexadecimal in a 32-bit word (0xdeadbeef), so in the days of yore, it was used to indicate a memory location that had not been initialized (by first initializing everything to 0xdeadbeef).
"deadbeef" has a long history. It can be spelled in hexadecimal in a 32-bit word (0xdeadbeef), so in the days of yore, it was used to indicate a memory location that had not been initialized (by first initializing everything to 0xdeadbeef).
12/16/2011 14:07 #55752
Fedora 16 UpdatesCategory: linux
I think I am going to document all the "transactions" of updates here so I can go back and see what changed when.
I also found out recently that someone called Ben Williams uploads updated Fedora livecds and images when kernels are updated. I think I will be using his images from now on if I do any new install so that all updates are incorporated in the newly installed system.
Starting with the update today:
I really wish the code box were lighter and easier on the eye. :(
I also found out recently that someone called Ben Williams uploads updated Fedora livecds and images when kernels are updated.
I think I will be using his images from now on if I do any new install so that all updates are incorporated in the newly installed system.Starting with the update today:
Installing: kernel x86_64 3.1.5-2.fc16 updates 26 M Updating: createrepo noarch 0.9.9-9.fc16 updates 97 k dhclient x86_64 12:4.2.3-4.P1.fc16 updates 258 k dhcp-common x86_64 12:4.2.3-4.P1.fc16 updates 273 k dhcp-libs x86_64 12:4.2.3-4.P1.fc16 updates 123 k diffutils x86_64 3.2-5.fc16 updates 259 k dracut noarch 013-20.fc16 updates 164 k folks x86_64 1:0.6.5-2.fc16 updates 440 k fprintd x86_64 0.4.1-1.fc16 updates 56 k fprintd-pam x86_64 0.4.1-1.fc16 updates 13 k gnome-python2 x86_64 2.28.1-7.fc16 updates 46 k gnome-python2-bonobo x86_64 2.28.1-7.fc16 updates 79 k gnome-python2-canvas x86_64 2.28.1-7.fc16 updates 32 k gnome-python2-gconf x86_64 2.28.1-7.fc16 updates 42 k gnome-python2-gnome x86_64 2.28.1-7.fc16 updates 74 k gnome-python2-gnomevfs x86_64 2.28.1-7.fc16 updates 78 k gtk2 i686 2.24.8-3.fc16 updates 3.2 M gtk2 x86_64 2.24.8-3.fc16 updates 3.2 M gtk2-immodule-xim x86_64 2.24.8-3.fc16 updates 62 k kernel-headers x86_64 3.1.5-2.fc16 updates 772 k libfprint x86_64 0.4.0-1.fc16 updates 114 k libimobiledevice x86_64 1.1.1-3.fc16 updates 101 k mdadm x86_64 3.2.2-15.fc16 updates 317 k memtest86+ x86_64 4.20-4.fc16 updates 77 k openssh x86_64 5.8p2-23.fc16 updates 257 k openssh-clients x86_64 5.8p2-23.fc16 updates 396 k openssh-server x86_64 5.8p2-23.fc16 updates 313 k tracker x86_64 0.12.8-2.fc16 updates 1.2 M vte x86_64 0.28.2-2.fc16 updates 349 k vte3 x86_64 0.30.1-3.fc16 updates 317 k Removing: kernel x86_64 3.1.2-1.fc16 @updates 112 M Installing for dependencies: pyliblzma x86_64 0.5.3-5.fc15 fedora 44 k Transaction Summary ================================================================================ Install 2 Packages Upgrade 29 Packages Remove 1 Package
I really wish the code box were lighter and easier on the eye. :(
So Is this Time to Say Happy New Year!?
Happy dissertation writing.