Profile

Cover photo
John Glotzer
Attended University of North Carolina at Chapel Hill
344 followers|60,535 views
AboutPostsPhotosVideos

Stream

John Glotzer

Shared publicly  - 
 
Rolling Stones guitarist records video to raise awareness for children's art and music charity
1
Add a comment...

John Glotzer

Shared publicly  - 
 
Fedora 19: Swap left and right pulseaudio channels
Why would anyone want to swap left and right pulseaudio channels? After some web searching I found that I am hardly alone. The classic probl...
1
Add a comment...

John Glotzer

Discussion  - 
 
Strange - thunderbird wouldn't start - would just exit after upgrade to 3.8.9-200.fc18.x86_64 - yum reinstall thunderbird fixed it. Never seen that before.
1
dr johnson's profile photo
 
You can see what would run on install with "rpm -q --scripts thunderbird".

In this case, "gtk-update-icon-cache /usr/share/icons/hicolor"
Add a comment...

John Glotzer

Discussion  - 
 
Windows 7 VM on Fedora18 x86_64 using Virtual box. 

I have Windows 7 VM was originally configured as 1 CPU, 1024 MB with Virtualbox config. My host is Fedora 18 x86_64.

Now I decide I want to add more CPU and more memory. 

I can safely increase the memory (once I shutdown the VM) but any attempt to increase the number of CPU's beyond 1 causes me to first see windows contemplating the new change for a while (black screen with a slightly changing windows graphic) but then an eventual windows bluescreen with a "badconfig info" msg.

These guys http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/82b420b6-c0b5-4253-b3a7-d1af47b6e86c/

say this can be done - that windows eventually figures out that it's now multiprocessor. But my experience is different. Can it, in fact be done? Right now, I'm going to say no.
1
John Glotzer's profile photoAdam DiFrischia's profile photo
14 comments
 
+Adam DiFrischia so for what it's worth I repeated this exercise on another F18 x86_64 machine and it worked just as you said! The windows kernel detected the "hardware" change, asked for a reboot, rebooted and then showed the new "processor". Aside from pure randomness the only other explanation I can come up with is that the machien on which it worked I had a windows 7 home edition. That which it didn't work was an enterprise version of win7 that I got from work. I can't explain why that would necessarily make a difference but it might be playing a role nonetheless.
Add a comment...
Have him in circles
344 people
lisa huang's profile photo
Max Patrick Haynes's profile photo

John Glotzer

Troubleshooting  - 
 
https://forums.virtualbox.org/viewtopic.php?f=10&t=54551

So after upgrading to 3.9.2 kernel my virtualbox kernel module wouldn't recompile.
Long story short - add 
      #include <linux/sched/rt.h>
to
     /usr/share/virtualbox/src/vboxhost/vboxdrv/r0drv/linux/thread2-r0drv-linux.c
2
1
Dzero Serghei's profile photoStefano Manocchio's profile photoPascal Kaufmann's profile photoLars Schotte's profile photo
17 comments
 
I think only need is virt-manager.
Add a comment...

John Glotzer

Discussion  - 
 
https://extensions.gnome.org/extension/442/drop-down-terminal/

This is a cool idea. Simple, useful, intuitive to use, no downside that I can see.
1
4
Sitaram Chamarty's profile photoLiam Bulkley's profile photoAshwini Patankar's profile photoAlexei Panov's profile photo
5 comments
 
Gnome?  They'll wait 3 years till you get used to it then remove it ;-)

/me runs and hides
Add a comment...

John Glotzer

Discussion  - 
 
Upgraded a desktop and a laptop to F18 this weekend using fedup. 

Desktop install went smoothly except for the fact that the servers were slow to the tune of 20-30 KBps. But OK. 

Laptop - I shot myself in the foot. For virtualization purposes I had had noapic in the kernel command line (else I couldn't turn on virtualization in the BIOS).

For Nvidia drivers I had nouveau.modeset=0 rd.driver.blacklist=nouveau. However at the end of the upgrade I ran grub2-install and these parameters (which I had not added to /etc/default/grub GRUB_CMDLINE_LINUX - only got added to the commandline in /boot/grub2/grub.cfg and then copied each time by grubby when kernels are upgraded) were dropped as soon as I ran grub2-install and grub2-mkconfig. 

So the machine wouldn't boot. I went through a series of maneuvers, changed the BIOS virtualization, uninstalled nvidia stuff, reran dracut, and got back to a working system. Now I plan to fix up the grub2.cfg, reinstall nvidia, re-enable virtualization in the BIOS etc. etc. 

But basically fedup worked fine for me - I basically wasn't careful enough to make sure my kernel command line survived the upgrade process.
1
John Glotzer's profile photoPatrick Massey's profile photoKhairil Ushan's profile photo
8 comments
 
I saw that sort of thing the 2nd time I upgraded because it went much faster and I could stand to look. I would NOT interrupt it - just let it run would be my advice. Good luck.
Add a comment...
People
Have him in circles
344 people
lisa huang's profile photo
Max Patrick Haynes's profile photo
Work
Occupation
Network Engineer.
Basic Information
Gender
Male
Story
Introduction
In my work life I'm a software developer for Cisco. In the rest of my life it sorta depends - kind of a mixture of a lot of things.
Bragging rights
Leaps tall buildings at a single bound? Maybe on a good day.
Education
  • University of North Carolina at Chapel Hill
    Computer Science
  • Harvard Medical School
  • University of Wisconsin-Madison
  • University of Chicago
Links
Contributor to