Re: How to recover X display? v.1.1
On 3/25/09, Matt Graham wrote: > You know what all this is saying to me? "PCLinuxOS is buggy. Don't > use it." Having a virtualbox install hose X, having LiveCDs lock > up on multiple machines, and so forth are things that I just would > not put up with. Life's too short, you know? > > If you are worried about your /home , the thing to do is to take > that USB drive, plug it in, mount it, then "tar czf /mnt/usb/ > backup.tar.gz /home" , so even if your reinstall eats your /home, > you have a backup of everything on that USB drive and can get it > retrieved with minimal fuss. Just make sure there's enough space > on the USB drive and it should work fine. You give very good, helpful, and efficient advice, Matt ... and I have sincerely appreciated every answer you've given. I must say, though, that PCLinuxOS is by far the best distro flavor (to my taste) that I have ever experienced. The 2007 release has been rock solid for me for two years on six different computers (until this virtualbox fiasco). I've tried many dozens of other distros and none of them have ever been anywhere near as easy and pleasing to use as PCL. I've tried a half dozen different releases of Ubuntu and Kubuntu and they have all been (in my experience) definitely inferior to PCL -- just very awkward and inefficient (to me). I realize some of my preference is probably just due to familiarity -vs- non-familiarity. But, to me, PCL is just head and shoulders above anything else I've tried. BTW: I couldn't get an Internet connection to work with the latest Kubuntu 8.1 on my thinkpad, whereas everything, even wireless, works "out of the box" on my thinkpad with PCL 2007. --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: How to recover X display? v.1.1
From: Josef Lowder > PCL 2009 doesn't work (live locks up on 3 different computers). > So, I'll just have to reinstall 2007. You know what all this is saying to me? "PCLinuxOS is buggy. Don't use it." Having a virtualbox install hose X, having LiveCDs lock up on multiple machines, and so forth are things that I just would not put up with. Life's too short, you know? If you are worried about your /home , the thing to do is to take that USB drive, plug it in, mount it, then "tar czf /mnt/usb/ backup.tar.gz /home" , so even if your reinstall eats your /home, you have a backup of everything on that USB drive and can get it retrieved with minimal fuss. Just make sure there's enough space on the USB drive and it should work fine. -- Matt G / Dances With Crows The Crow202 Blog: http://crow202.org/wordpress/ There is no Darkness in Eternity/But only Light too dim for us to see --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: How to recover X display? v.1.1
PCL 2009 doesn't work (live locks up on 3 different computers). So, I'll just have to reinstall 2007. On 3/25/09, Lisa Kachold wrote: > Just upgrade to 2009 it should retain your settings. --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
RE: How to recover X display? v.1.1
Just upgrade to 2009 it should retain your settings. Obnosis | (503)754-4452 PLUG Linux Security Labs 2nd Saturday Each mo...@noon - 3PM > Date: Wed, 25 Mar 2009 06:14:41 -0700 > Subject: Re: How to recover X display? v.1.1 > From: j...@actionline.com > To: plug-discuss@lists.plug.phoenix.az.us > > On 3/24/09, Lisa Kachold wrote: > > Well, with PCLinuxOs, I believe that x had the video drivers packaged > > differently between versions, so it might not be so simple. > > Well, I guess I'll just try to reinstall PCLinuxOS 2007 and try to do it > without overwriting my home directory. > --- > PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us > To subscribe, unsubscribe, or to change your mail settings: > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss _ Get quick access to your favorite MSN content with Internet Explorer 8. http://ie8.msn.com/microsoft/internet-explorer-8/en-us/ie8.aspx?ocid=B037MSN55C0701A--- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: How to recover X display? v.1.1
On 3/24/09, Lisa Kachold wrote: > Well, with PCLinuxOs, I believe that x had the video drivers packaged > differently between versions, so it might not be so simple. Well, I guess I'll just try to reinstall PCLinuxOS 2007 and try to do it without overwriting my home directory. --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
RE: How to recover X display? v.1.1
Well, with PCLinuxOs, I believe that x had the video drivers packaged differently between versions, so it might not be so simple. Anyone competent with PCLinuxOs might want to contact him off list and offer a phone session assist? Obnosis | (503)754-4452 PLUG Linux Security Labs 2nd Saturday Each mo...@noon - 3PM > Date: Tue, 24 Mar 2009 15:41:11 -0700 > From: danceswithcr...@usa.net > To: plug-discuss@lists.plug.phoenix.az.us > Subject: Re: How to recover X display? v.1.1 > > From: Josef Lowder > > On 3/24/09, Matt Graham wrote: > >> Are you on dialup? If you've got proper bandwidth, > >> "dhclient eth0" or "dhcpcd eth0" should get a dynamic IP > >> address provided eth0 is plugged in to something. > > I have DSL wireless and it was working fine before the crash. > > Even now, when I boot up, I see lights blinking on the 3-COM > > pci card, but since I can't see anything on F7 I can't use the > > wireless connection that I think I have. > > > And I don't know how to establish that connection on one of the > > other F1-F6 command-line only terminals. > > First find out what your NIC is called. "iwconfig" should list > all NICs, and the wired ones will say "no wireless extensions". > So you might see: > > eth0: no wireless extensions > eth1: 802.11b/g ESSID "blah" Mode managed TxPower 89 FooBar 23 > [more settings like that] > lo: no wireless extensions > > Then, you do "dhcpcd eth1" if you have no encryption on and > don't care which AP you connect to. Things get more complex > when you use WEP/WPA, but say which one you're using, and I or > someone else will be able to tell you what's up. Really, I'd > take a length of Cat5 and plug the thing in, rather than deal > with the hassle of wireless for this reasonably short experiment. > > >> Fix the Net access and apt-get upgrade, and > >> you should be good. (I Could Be Wrong.) > > Wish I could. > > The stuff above may help. > > -- > Matt G / Dances With Crows > The Crow202 Blog: http://crow202.org/wordpress/ > There is no Darkness in Eternity/But only Light too dim for us to see > > > --- > PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us > To subscribe, unsubscribe, or to change your mail settings: > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss _ Hotmail® is up to 70% faster. Now good news travels really fast. http://windowslive.com/online/hotmail?ocid=TXT_TAGLM_WL_HM_70faster_032009--- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
RE: How to recover X display? v.1.1
Good job on the upgrade. It's never indicated to run a system in anything but a fully patched OS. What is your system whining about (logs)? Did you run the dpkg reconfigure against x? Remember to lay your logs on if different. Obnosis | (503)754-4452 PLUG Linux Security Labs 2nd Saturday Each mo...@noon - 3PM > Date: Tue, 24 Mar 2009 18:44:18 -0700 > Subject: Re: How to recover X display? v.1.1 > From: j...@actionline.com > To: plug-discuss@lists.plug.phoenix.az.us > > So now I have done a complete system update: > 618 upgraded > 198 newly installed > 29 replaced > 3 removed > 5 not upgraded > 766 MB of archives - after unpacking > 47.3MB of add'l disk space used > more than 2 hours of installing upgrades > and the result ... drum roll ... > > Still no X > --- > PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us > To subscribe, unsubscribe, or to change your mail settings: > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss _ Express your personality in color! Preview and select themes for Hotmail®. http://www.windowslive-hotmail.com/LearnMore/personalize.aspx?ocid=TXT_MSGTX_WL_HM_express_032009#colortheme--- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
RE: How to recover X display? v.1.1
If you cannot startx without still seeing the whining about the two video drivers mismatch, you do want to reconfigure your xserver.xorg and possibly rerun xconfigurator? It's certainly not going to hurt! Obnosis | (503)754-4452 PLUG Linux Security Labs 2nd Saturday Each mo...@noon - 3PM > Date: Tue, 24 Mar 2009 18:49:54 -0700 > Subject: Re: How to recover X display? v.1.1 > From: j...@actionline.com > To: plug-discuss@lists.plug.phoenix.az.us > > Forgot to mention: > For PCLInuxOS, instead of this: > >> sudo apt-get update && sudo apt-get upgrade > > sudo did not work for me, so searched further and > from a PCLinuxOS source, I learned that as root I needed to do this: > > apt-get clean && apt-get autoclean > apt-get update && apt-get dist-upgrade > > From one of your previous replies, you included this: > >> # sudo dpkg-reconfigure -phigh xserver-xorg > > Do I still need to do that? > --- > PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us > To subscribe, unsubscribe, or to change your mail settings: > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss _ Windows Live™ SkyDrive: Get 25 GB of free online storage. http://windowslive.com/online/skydrive?ocid=TXT_TAGLM_WL_skydrive_032009--- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: How to recover X display? v.1.1
Forgot to mention: For PCLInuxOS, instead of this: >> sudo apt-get update && sudo apt-get upgrade sudo did not work for me, so searched further and from a PCLinuxOS source, I learned that as root I needed to do this: apt-get clean && apt-get autoclean apt-get update && apt-get dist-upgrade >From one of your previous replies, you included this: >> # sudo dpkg-reconfigure -phigh xserver-xorg Do I still need to do that? --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: How to recover X display? v.1.1
So now I have done a complete system update: 618 upgraded 198 newly installed 29 replaced 3 removed 5 not upgraded 766 MB of archives - after unpacking 47.3MB of add'l disk space used more than 2 hours of installing upgrades and the result ... drum roll ... Still no X --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: How to recover X display? v.1.1
On 3/24/09, Matt Graham wrote: > Really, I'd take a length of Cat5 and plug the thing in, rather than deal > with the hassle of wireless for this reasonably short experiment. Duh, why couldn't I have at least thought of that? Thanks again Matt. The Cat5 wired connection worked instantly, so I'll try doing an apt-get full system update on my PCLinuxOS setup and see where that leads. --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: How to recover X display? v.1.1
From: Josef Lowder > On 3/24/09, Matt Graham wrote: >> Are you on dialup? If you've got proper bandwidth, >> "dhclient eth0" or "dhcpcd eth0" should get a dynamic IP >> address provided eth0 is plugged in to something. > I have DSL wireless and it was working fine before the crash. > Even now, when I boot up, I see lights blinking on the 3-COM > pci card, but since I can't see anything on F7 I can't use the > wireless connection that I think I have. > And I don't know how to establish that connection on one of the > other F1-F6 command-line only terminals. First find out what your NIC is called. "iwconfig" should list all NICs, and the wired ones will say "no wireless extensions". So you might see: eth0: no wireless extensions eth1: 802.11b/g ESSID "blah" Mode managed TxPower 89 FooBar 23 [more settings like that] lo: no wireless extensions Then, you do "dhcpcd eth1" if you have no encryption on and don't care which AP you connect to. Things get more complex when you use WEP/WPA, but say which one you're using, and I or someone else will be able to tell you what's up. Really, I'd take a length of Cat5 and plug the thing in, rather than deal with the hassle of wireless for this reasonably short experiment. >> Fix the Net access and apt-get upgrade, and >> you should be good. (I Could Be Wrong.) > Wish I could. The stuff above may help. -- Matt G / Dances With Crows The Crow202 Blog: http://crow202.org/wordpress/ There is no Darkness in Eternity/But only Light too dim for us to see --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: How to recover X display? v.1.1
On 3/24/09, Matt Graham wrote: > Are you on dialup? If you've got proper bandwidth, > "dhclient eth0" or "dhcpcd eth0" should get a dynamic IP > address provided eth0 is plugged in to something. I have DSL wireless and it was working fine before the crash. Even now, when I boot up, I see lights blinking on the 3-COM pci card, but since I can't see anything on F7 I can't use the wireless connection that I think I have. And I don't know how to establish that connection on one of the other F1-F6 command-line only terminals. > Fix the Net access and apt-get upgrade, and > you should be good. (I Could Be Wrong.) Wish I could. --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: How to recover X display? v.1.1
From: Josef Lowder > On 3/24/09, Lisa Kachold wrote: >> Post installation of Virtualbox, your Xorg logs say what? > www.upquick.com/view/Xorg.0.log That one doesn't have any errors in it, though. The .9 log has the "v4l version mismatch" error in it, but the others don't. Very strange. > www.upquick.com/view/xorg.conf That looks fine to me, though I'd use "radeon" instead of "ati", because ati is really for driving Mach64 cards, although it will load radeon or r128 if it detects a Radeon or Rage128 card. >> # sudo Xconfigurator > I can't find 'Xconfigurator' on the system, don't think I have it. The X config is fine, except it's loading v4l (and maybe other modules) that have the wrong versions. I suppose you could comment out v4l, glx, and dri, restart X, and see if it works--that'd take 5 minutes. (It's totally hork up compiz-fusion, but you should get X back.) The non-distro-specific way of generating a good X config file is to back up an existing xorg.conf , then "X -configure", then edit the xorg.conf that gets generated and change the default color depth to something other than 8. It's not insanely great, but it does work. >> sudo apt-get update && sudo apt-get upgrade >> # sudo dpkg-reconfigure -phigh xserver-xorg > Wish I could, but I don't know how to get an internet connection > with only command line access. Are you on dialup? That'd be semi-annoying, but should be possible. You'd need to do something with wvdial or the pppd config though. The last time I used dialup was 5 years ago. If you've got proper bloody bandwidth, "dhclient eth0" or "dhcpcd eth0" should get a dynamic IP address provided eth0 is plugged in to something. > Here are some other files that I copied from the laptop, Heck. From what I can tell, the problem is X and X's modules not being the same version. Fix the Net access and apt-get upgrade, and you should be good. (I Could Be Wrong.) -- Matt G / Dances With Crows The Crow202 Blog: http://crow202.org/wordpress/ There is no Darkness in Eternity/But only Light too dim for us to see --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: How to recover X display? v.1.1
On 3/24/09, Lisa Kachold wrote: > Post installation of Virtualbox, your Xorg logs say what? www.upquick.com/view/Xorg.0.log 42660 Apr 14 2007 Xorg.1.log.old 45158 Mar 19 2008 Xorg.1.log 14929 Mar 22 23:28 Xorg.9.log 14294 Mar 23 10:35 Xorg.0.log.old 14493 Mar 23 10:36 Xorg.0.log I also copied this file: 2974 Apr 6 2007 xorg.conf It can be viewed at this link: www.upquick.com/view/xorg.conf > First try this: > # sudo Xconfigurator > You can try to configure your monitor and video card for X via this utility. > Might work, it's worth a try...[but not highly probable]. I can't find 'Xconfigurator' on the system, don't think I have it. > 2) Update/upgrade your system, although this might have been what caused it. > sudo apt-get update > sudo apt-get upgrade > # sudo dpkg-reconfigure -phigh xserver-xorg Wish I could, but I don't know how to get an internet connection with only command line access. --- Here are some other files that I copied from the laptop, (thanks to Matt's explanation of how to get the USB flash stick mounted) Have not yet uploaded any of these to a web page, but could if they might help. 1408 Mar 21 13:53 vbox-install.log 7073 Mar 22 04:02 warnings.1.gz 22570 Mar 22 04:02 info.1.gz 790 Mar 22 04:02 errors.1.gz 1008834 Mar 23 17:10 messages 13947 Mar 23 17:10 dmesg 16 Mar 23 17:14 kernel.errors 34511 Mar 23 17:15 warnings 588685 Mar 23 17:15 info 829597 Mar 23 17:15 errors 1032 Mar 23 17:21 mar22logs 4022 Mar 23 17:29 vbox.files 972 Mar 23 17:36 boot.dirlist --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: How to recover X display? v.1.1
Lisa, thank you profusely for all of your "far beyond the extra mile" efforts to help me solve this matter. I will get back to work on this asap and follow all of your suggestions. It may take me a while to get back to this because this laptop is not a mission-critical unit and I have to get caught up on my regular work on my old reliable computer before I resume work on trying to get the laptop going again. Again, I sincerely appreciate all of your help! Many, many thanks. Joe On 3/24/09, Lisa Kachold wrote: > > Corrections in red: > > Not exactly > I apologise, I was reading for context, and make sense from within a wealth > of 22 years of Nix experience. > The link is describing difficulty with v41/ABI drivers within Virtualbox > booting into X via PCLinuxOS. When you build a virtualbox client, the > xdrivers modules are created also; sometimes when one installs Virtualbox > (and/or Xen), they decide to run their first system in a virtual under the > OS, which is then described as primary in the grub configuration via the new > kernel that was built during install (which might cause an X and kernel > module mismatch). For instance under Redhat/XEN this is usually what is > called a PAE kernel. You, after installing Virtualbox, verified that you > are still running the same kernel from grub.conf? You can also look at the > file creation date for the kernel that is indicated to boot first into the > grub configuration. > Post installation of Virtualbox, your Xorg logs say what? > > If I remember correctly Xorg was whining we needed a couple of video > modules? Irregardless of whether you are now running in a VirtualBox or > not: > > a) boot fails to go to X > b) you can't startx > Solutions: > > 1) You can try to boot into your system and reconfigure your X drivers via > command line? > First try this: > # sudo Xconfigurator > You can try to configure your monitor and video card for X via this utility. > Might work, it's worth a try...[but not highly probable]. > > 2) Update/upgrade your system, although this might have been what caused it. > There are some major differences between the way that X uses kernel drivers > for video cards in recent versions. > http://distrowatch.com/index.php?distribution=all&month=all&year=2009 > > sudo apt-get update > sudo apt-get upgrade > > 3) Kernel modules and X drivers > Your Xorg errors talked about two drivers: > module ABI major version (1) doesn't match server's version (2) > failed to load module "v41" (module requirement mismatch,0) > # sudo dpkg-reconfigure -phigh xserver-xorg > 4) Revert your failed system > > If these questions do not make sense, and you can't either fix the driver > errors or roll back the changes made adding virtualbox source, it would be > easiest for you to just rebuild. Download a new ISO from distrowatch (or a > new OS) and burn it to CD (or DVD if you have that luxury) carefully > selecting the i386/686 versions and drop the hammer on this failed learning > project, and go on to bigger and better things! > After you rebuild your shiny new system, keep your BUILD DVD/CD, so you can > use it to boot emergency for trouble/rebuild. Always keep a record of all > steps that are done, (especially updates, etc. and test between upgrade > installation steps) for packaging the issues for others. > > 5) If all this fails, take your box back to the InstallFesters and/or call > one of us. > > Obnosis | (503)754-4452 > PLUG Linux Security Labs 2nd Saturday Each mo...@noon - 3PM > > > > Date: Mon, 23 Mar 2009 16:38:32 -0700 > > Subject: Re: How to recover X display? > > From: j...@actionline.com > > To: plug-discuss@lists.plug.phoenix.az.us > > > > Now, I'm even more thoroughly confused. > > > > On 3/23/09, Lisa Kachold wrote: > > > > http://reformedmusings.wordpress.com/2008/12/11/installing-sun-virtualbox-6-guest-additions-in-linux-guests/ > > > > This is describing installing PCLinuxOS as a virtual machine inside a > > working Ubuntu-VirtualBox setup ... which doesn't seem to have > > anything to do with trying to get my installed PCLinuxOS system X > > recovered. > > > > The article says: "Guest Additions installs from a CD iso file. > > > > I don't have any CD iso for this. > > > > The article then says: "So, we need to load the iso as a CD in our > > virtual machine. > > For this, the virtual machine must be shut down (powered off)." > > > > There is no way I can do this when my basic machine is not working. > > --- >
RE: How to recover X display? v.1.1
Corrections in red: Not exactly I apologise, I was reading for context, and make sense from within a wealth of 22 years of Nix experience. The link is describing difficulty with v41/ABI drivers within Virtualbox booting into X via PCLinuxOS. When you build a virtualbox client, the xdrivers modules are created also; sometimes when one installs Virtualbox (and/or Xen), they decide to run their first system in a virtual under the OS, which is then described as primary in the grub configuration via the new kernel that was built during install (which might cause an X and kernel module mismatch). For instance under Redhat/XEN this is usually what is called a PAE kernel. You, after installing Virtualbox, verified that you are still running the same kernel from grub.conf? You can also look at the file creation date for the kernel that is indicated to boot first into the grub configuration. Post installation of Virtualbox, your Xorg logs say what? If I remember correctly Xorg was whining we needed a couple of video modules? Irregardless of whether you are now running in a VirtualBox or not: a) boot fails to go to X b) you can't startx Solutions: 1) You can try to boot into your system and reconfigure your X drivers via command line? First try this: # sudo Xconfigurator You can try to configure your monitor and video card for X via this utility. Might work, it's worth a try...[but not highly probable]. 2) Update/upgrade your system, although this might have been what caused it. There are some major differences between the way that X uses kernel drivers for video cards in recent versions. http://distrowatch.com/index.php?distribution=all&month=all&year=2009 sudo apt-get update sudo apt-get upgrade 3) Kernel modules and X drivers Your Xorg errors talked about two drivers: module ABI major version (1) doesn't match server's version (2) failed to load module "v41" (module requirement mismatch,0) # sudo dpkg-reconfigure -phigh xserver-xorg 4) Revert your failed system If these questions do not make sense, and you can't either fix the driver errors or roll back the changes made adding virtualbox source, it would be easiest for you to just rebuild. Download a new ISO from distrowatch (or a new OS) and burn it to CD (or DVD if you have that luxury) carefully selecting the i386/686 versions and drop the hammer on this failed learning project, and go on to bigger and better things! After you rebuild your shiny new system, keep your BUILD DVD/CD, so you can use it to boot emergency for trouble/rebuild. Always keep a record of all steps that are done, (especially updates, etc. and test between upgrade installation steps) for packaging the issues for others. 5) If all this fails, take your box back to the InstallFesters and/or call one of us. Obnosis | (503)754-4452 PLUG Linux Security Labs 2nd Saturday Each mo...@noon - 3PM > Date: Mon, 23 Mar 2009 16:38:32 -0700 > Subject: Re: How to recover X display? > From: j...@actionline.com > To: plug-discuss@lists.plug.phoenix.az.us > > Now, I'm even more thoroughly confused. > > On 3/23/09, Lisa Kachold wrote: > > http://reformedmusings.wordpress.com/2008/12/11/installing-sun-virtualbox-6-guest-additions-in-linux-guests/ > > This is describing installing PCLinuxOS as a virtual machine inside a > working Ubuntu-VirtualBox setup ... which doesn't seem to have > anything to do with trying to get my installed PCLinuxOS system X > recovered. > > The article says: "Guest Additions installs from a CD iso file. > > I don't have any CD iso for this. > > The article then says: "So, we need to load the iso as a CD in our > virtual machine. > For this, the virtual machine must be shut down (powered off)." > > There is no way I can do this when my basic machine is not working. > --- > PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us > To subscribe, unsubscribe, or to change your mail settings: > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss Windows Live™ SkyDrive: Get 25 GB of free online storage. Check it out. _ Get quick access to your favorite MSN content with Internet Explorer 8. http://ie8.msn.com/microsoft/internet-explorer-8/en-us/ie8.aspx?ocid=B037MSN55C0701A--- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
RE: How to recover X display?
Not exactly I apologise, I was reading for context, and make sense from within a wealth of 22 years of Nix experience. The link is describing difficulty with v41/ABI drivers within Virtualbox booting into X via PCLinuxOS. When you build a virtualbox client, the xdrivers modules are created also; sometimes when one installs Virtualbox (and/or Xen), they decide to run their first system in a virtual under the OS, which is then described as primary in the grub configuration via the new kernel that was built during install (which might cause an X and kernel module mismatch). For instance under Redhat/XEN this is usually what is called a PAE kernel. You, after installing Virtualbox, verified that you are still running the same kernel from grub.conf? You can also look at the file creation date for the kernel that is indicated to boot first into the grub configuration. Post installation of Virtualbox, your Xorg logs say what? If I remember correctly Xorg was whining we needed a couple of kernel modules? Irregardless of whether you are now running in a VirtualBox or not, this post matches what is happening to you? http://www.neowin.net/forum/index.php?showtopic=611644 a) boot fails to go to X b) you can't startx Solutions: 1) You can try to boot into your system and reconfigure your X drivers via command line? First try this: # sudo Xconfigurator You can try to configure your monitor and video card for X via this utility. Might work, it's worth a try...[but not highly probable]. 2) Update/upgrade your system, although this might have been what caused it. There are some major differences between the way that X uses kernel drivers for video cards in recent versions. http://distrowatch.com/index.php?distribution=all&month=all&year=2009 sudo apt-get update sudo apt-get upgrade 3) Kernel modules and X drivers Your Xorg errors talked about two drivers: module ABI major version (1) doesn't match server's version (2) failed to load module "v41" (module requirement mismatch,0) # sudo dpkg-reconfigure -phigh xserver-xorg 4) Revert your failed system If these questions do not make sense, and you can't either fix the driver errors or roll back the changes made adding virtualbox source, it would be easiest for you to just rebuild. Download a new ISO from distrowatch (or a new OS) and burn it to CD (or DVD if you have that luxury) carefully selecting the i386/686 versions and drop the hammer on this failed learning project, and go on to bigger and better things! After you rebuild your shiny new system, keep your BUILD DVD/CD, so you can use it to boot emergency for trouble/rebuild. Always keep a record of all steps that are done, (especially updates, etc. and test between upgrade installation steps) for packaging the issues for others. 5) If all this fails, take your box back to the InstallFesters and/or call one of us. Obnosis | (503)754-4452 PLUG Linux Security Labs 2nd Saturday Each mo...@noon - 3PM > Date: Mon, 23 Mar 2009 16:38:32 -0700 > Subject: Re: How to recover X display? > From: j...@actionline.com > To: plug-discuss@lists.plug.phoenix.az.us > > Now, I'm even more thoroughly confused. > > On 3/23/09, Lisa Kachold wrote: > > http://reformedmusings.wordpress.com/2008/12/11/installing-sun-virtualbox-6-guest-additions-in-linux-guests/ > > This is describing installing PCLinuxOS as a virtual machine inside a > working Ubuntu-VirtualBox setup ... which doesn't seem to have > anything to do with trying to get my installed PCLinuxOS system X > recovered. > > The article says: "Guest Additions installs from a CD iso file. > > I don't have any CD iso for this. > > The article then says: "So, we need to load the iso as a CD in our > virtual machine. > For this, the virtual machine must be shut down (powered off)." > > There is no way I can do this when my basic machine is not working. > --- > PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us > To subscribe, unsubscribe, or to change your mail settings: > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss _ Windows Live™ SkyDrive: Get 25 GB of free online storage. http://windowslive.com/online/skydrive?ocid=TXT_TAGLM_WL_skydrive_032009--- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: How to recover X display?
Now, I'm even more thoroughly confused. On 3/23/09, Lisa Kachold wrote: > http://reformedmusings.wordpress.com/2008/12/11/installing-sun-virtualbox-6-guest-additions-in-linux-guests/ This is describing installing PCLinuxOS as a virtual machine inside a working Ubuntu-VirtualBox setup ... which doesn't seem to have anything to do with trying to get my installed PCLinuxOS system X recovered. The article says: "Guest Additions installs from a CD iso file. I don't have any CD iso for this. The article then says: "So, we need to load the iso as a CD in our virtual machine. For this, the virtual machine must be shut down (powered off)." There is no way I can do this when my basic machine is not working. --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
RE: How to recover X display?
Virtualbox does a kernel recompile thing. See the other email related to quick repair via command line Guest Addtions: http://reformedmusings.wordpress.com/2008/12/11/installing-sun-virtualbox-6-guest-additions-in-linux-guests/ Obnosis | (503)754-4452 PLUG Linux Security Labs 2nd Saturday Each mo...@noon - 3PM > Date: Mon, 23 Mar 2009 12:58:39 -0700 > From: danceswithcr...@usa.net > To: plug-discuss@lists.plug.phoenix.az.us > Subject: Re: How to recover X display? > > From: Josef Lowder > >On 3/23/09, Matt Graham wrote: > >> USB drive, shirley? > > When I plug in a flash stick into a USB drive, it no longer gets > > mounted now, so I cannot copy files to it. > > Mount it manually, then. Plug drive in, dmesg | tail to see which > device node it got assigned to, mkdir /mnt/usb , mount /dev/sd?1 > /mnt/usb . (It's not that you can't copy files to the disk, it's > that you don't know how to do it.) > > >> This is an X problem IIRC. The module being referred to is the X > >> module, not a kernel module. Did X get upgraded at some point? > > As far as I can tell, "X" did not get upgraded or changed. > > No scare quotes around X are necessary. It's an abbreviation for > the X11 Window System, which drives graphics cards and input > devices on Linux/*BSD systems. You probably have an executable > called /usr/bin/X on your system. > > > Tried editing out the line referring to "v4l" and rebooted, but > > that did not bring back "X" > > No reboot was necessary. Just restarting X should've showed you > if it had worked. Did /var/log/Xorg.0.log change? It > would be a good idea to post that file too, since there are > probably some things in there that would be useful to see. The > whole file, not excerpts, even though 90% of the X log is usually > useless > > >> grep Driver /etc/X11/xorg.conf > >> lspci | grep VGA > > VGA compatible controller: ATI Technologies Inc Radeon Mobility > > Right, so the xorg.conf grep should've showed either radeon or fglrx. > Those are the Free and proprietary X modules that drive those cards. > > This is all very strange to me, since installing virtualbox shouldn't > have changed *anything* with the X config. > > -- > Matt G / Dances With Crows > The Crow202 Blog: http://crow202.org/wordpress/ > There is no Darkness in Eternity/But only Light too dim for us to see > > > --- > PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us > To subscribe, unsubscribe, or to change your mail settings: > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss _ Get quick access to your favorite MSN content with Internet Explorer 8. http://ie8.msn.com/microsoft/internet-explorer-8/en-us/ie8.aspx?ocid=B037MSN55C0701A--- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
RE: How to recover X display?
Sorry, I should have extracted the solution and made it big and bold (I forgot your system just got downgraded at an Installfest, and you are PTSD stuck!) This will fix her: Reinstall Virtualbox Guest Additions from the terminal: http://www.informit.com/articles/article.aspx?p=1271263&seqNum=3 Install VirtualBox as described Part 1 and Part 2 of "Sun VirtualBox (xVM): A Virtualization Environment for Linux" article. Of course, if you had Xterm you could just do: Next: Virtualbox Console > Devices > Install Guest Additions There is a script somewhere hereabouts: cd /media/VBOXADDITIONS_2.0.6_39755 [directory name will vary with the version] sudo sh ./VBoxLinuxAdditions-x86.run [or -x64 if running a 64-bit guest] Other stuff probably not related: http://www.virtualbox.org/wiki/User_FAQ Just FYI, the problem is that you upgraded to a new kernel, so you had to recompile or reinstall your graphic drivers . Obnosis | (503)754-4452 PLUG Linux Security Labs 2nd Saturday Each mo...@noon - 3PM From: lisakach...@obnosis.com To: plug-discuss@lists.plug.phoenix.az.us Subject: RE: How to recover X display? Date: Mon, 23 Mar 2009 02:23:26 + Updates between versions are sometimes a lottery! Let's look at how we must package a problem for the PLUG: We follow these steps (dumping into email): 1) What is it (versions, etc)? 2) What is she whining about (Linux like any good partner will tell you very clearly what is the issue)? [Ignore my installation references for Ubuntu's Virtualbox (they are just info); but possibly an update to the ABI module or v41 module were done during the installation?] Check the file creation date for your Grub at /here/boot/grub/menu.lst Check to verify what she is currently booting there - look for backup files and diff. Discussion: http://www.pclinuxos.com/index.php?option=com_smf&Itemid=26&topic=54523.0 We might logically research the exact Xorg errors for these, spoze? 3) Research our error for known solutions: module ABI major version (1) doesn't match server's version (2) failed to load module "v41" (module requirement mismatch,0) http://ubuntuforums.org/archive/index.php/t-313691.html PCLinuxOs virtualbox module issues http://www.neowin.net/forum/index.php?showtopic=611644 4) The Zen of Troubleshooting, "The error is the problem" Looks like you have a kernel module mismatch grasshopper. Obnosis | (503)754-4452 PLUG Linux Security Labs 2nd Saturday Each mo...@noon - 3PM > Date: Sun, 22 Mar 2009 12:04:29 -0700 > Subject: Re: How to recover X display? > From: j...@actionline.com > To: plug-discuss@lists.plug.phoenix.az.us > > Thanks very much Lisa. Following is what I've discovered so far: > > On 3/22/09, Lisa Kachold wrote: > > Quick Resurrection -- [drop info from these steps w reply to organize the > > issue] > > > > 1) Verify bootloader GRUB -- What does your grub.conf look like? > > Compare old and new, specifically looking at kernel boot options. > > What are you booting into? > > There is no grub.conf. In /boot/grub found menu.lst dated Apr 6, 2007 > (last date chgd) > It boots to /boot/vmlinuz VGA=788 (this is the one that locks up) > Also to /boot/vmlinuz without VGA-788 and this works, opens to # command line > Also to /boot vmlinuz "failsafe" > Also to win.xp which still works > All three /voot/vmlinuz boot to kernel.h-2.6.18.6 dated Feb 23, 2007 > > > 2) Verify X -- Boot to rescue mode and see what your /etc/X11/xorg.conf > > says. > > There would have been an old xorg.conf that was copied to backup. > > xorg.conf and xorg.conf.old are both dated Apr 6, 2007 > (Apparently no change from when everything was working.) > diff showed "old" had "DPMS" "false" and current "DPMS" (no false) > 'diff' also showed the following line identical in both old and new: > #DontZoom # disable (resolution switching) > > > Look at /var/log/Xorg.0.log for clues. > > Scrolling through the entire log file showed only two items flagged (EE): > module ABI major version (1) doesn't match server's version (2) > failed to load module "v41" (module requirement mismatch,0) > > > Run Xconfigurator after copying current xorg.conf to KNOWNBACKUP. > > Found no 'Xconfigurtor' nor 'xconfig' on the system. > > > Or just copy the current file to backup and move the old over. > > The current and 'old' are the same except as noted above. > > > You might want to add vboxdrv to the list of modules in /etc/modules to be > > loaded automatically at startup in. > > I did this and rebooted, but still get the message: > "cannot connect to X server" >
RE: How to recover X display?
No!!!
You failed to see the recommendation (for repairing these exact errors) at the
bottom of the on the last LINK.
These linked URL's are all part of the solution process, we don't just drop
them on for giggles.
Obnosis | (503)754-4452
PLUG Linux Security Labs 2nd Saturday Each mo...@noon - 3PM
> Date: Mon, 23 Mar 2009 09:23:50 -0700
> From: danceswithcr...@usa.net
> To: plug-discuss@lists.plug.phoenix.az.us
> Subject: Re: How to recover X display?
>
> From: Josef Lowder
> > Perhaps I'll just have to reinstall and risk losing my data as
> > I don't know a way to get it copied off.
>
> USB drive, shirley?
>
> [kernel modules and GRUB conf, not the problem]
> >> We might logically research the exact Xorg errors for these, spoze?
> >> 3) Research our error for known solutions:
> >> module ABI major version (1) doesn't match server's version (2)
> >> failed to load module "v41" (module requirement mismatch,0)
> > ("v41" above should have been "v4l"
>
> This is an X problem IIRC. The module being referred to is the X
> module, not a kernel module. Did X get upgraded at some point?
> The thing that's messed up is /usr/lib/xorg/modules/drivers/v4l_drv.*
> AFAICT. If you have any reference to v4l in your xorg.conf , then
> edit that file and comment that line out. Your webcam and/or TV
> tuner will stop being able to use XV, but you'll get X back. Also,
>
> grep Driver /etc/X11/xorg.conf
> lspci | grep VGA
>
> ...will tell you which X module you're using and which graphics
> card you have. In fact, you should take your xorg.conf and put
> it on your website somewhere, then follow up with a URL here.
>
> > The problem seems to pertain mainly if not exclusively to the X server.
> > I tried running '/usr/sbin/XFdrake' and it seems to show that everything
> > is set correctly.
>
> XFdrake... something Mandrake-specific? Gah, most of these tools are
> rather poorly debugged.
>
> > Should I try to remove all files on the system pertaining to virtualbox?
>
> This shouldn't have any effect on anything, but sure, try your distro's
> equivalent of "yum remove virtualbox". FWIW, I installed virtualbox
> on my Thinkpad T42p a while back, and never had any problems with it
> horking up suspend-to-RAM or doing anything weird to X. Then again,
> I'm using Gentoo, and YDistroMV. HTH anyway,
>
> --
> Matt G / Dances With Crows
> The Crow202 Blog: http://crow202.org/wordpress/
> There is no Darkness in Eternity/But only Light too dim for us to see
>
>
> ---
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
_
Internet Explorer 8 – Now Available. Faster, safer, easier.
http://clk.atdmt.com/MRT/go/141323790/direct/01/---
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: How to recover X display?
From: Josef Lowder >On 3/23/09, Matt Graham wrote: >> USB drive, shirley? > When I plug in a flash stick into a USB drive, it no longer gets > mounted now, so I cannot copy files to it. Mount it manually, then. Plug drive in, dmesg | tail to see which device node it got assigned to, mkdir /mnt/usb , mount /dev/sd?1 /mnt/usb . (It's not that you can't copy files to the disk, it's that you don't know how to do it.) >> This is an X problem IIRC. The module being referred to is the X >> module, not a kernel module. Did X get upgraded at some point? > As far as I can tell, "X" did not get upgraded or changed. No scare quotes around X are necessary. It's an abbreviation for the X11 Window System, which drives graphics cards and input devices on Linux/*BSD systems. You probably have an executable called /usr/bin/X on your system. > Tried editing out the line referring to "v4l" and rebooted, but > that did not bring back "X" No reboot was necessary. Just restarting X should've showed you if it had worked. Did /var/log/Xorg.0.log change? It would be a good idea to post that file too, since there are probably some things in there that would be useful to see. The whole file, not excerpts, even though 90% of the X log is usually useless >> grep Driver /etc/X11/xorg.conf >> lspci | grep VGA > VGA compatible controller: ATI Technologies Inc Radeon Mobility Right, so the xorg.conf grep should've showed either radeon or fglrx. Those are the Free and proprietary X modules that drive those cards. This is all very strange to me, since installing virtualbox shouldn't have changed *anything* with the X config. -- Matt G / Dances With Crows The Crow202 Blog: http://crow202.org/wordpress/ There is no Darkness in Eternity/But only Light too dim for us to see --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: How to recover X display?
On 3/23/09, Matt Graham wrote: > > USB drive, shirley? When I plug in a flash stick into a USB drive, it no longer gets mounted now, so I cannot copy files to it. It always did get mounted before this virtual box installation crashed "X" > This is an X problem IIRC. The module being referred to is the X > module, not a kernel module. Did X get upgraded at some point? As far as I can tell, "X" did not get upgraded or changed. > The thing that's messed up is /usr/lib/xorg/modules/drivers/v4l_drv.* > AFAICT. If you have any reference to v4l in your xorg.conf , then > edit that file and comment that line out. Your webcam and/or TV > tuner will stop being able to use XV, but you'll get X back. Also, Tried editing out the line referring to "v4l" and rebooted, but that did not bring back "X" > grep Driver /etc/X11/xorg.conf > lspci | grep VGA > > ...will tell you which X module you're using and which graphics > card you have. Doing that showed this: 01:00 VGA compatible controller: ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500] > In fact, you should take your xorg.conf and put > it on your website somewhere, then follow up with a URL here. I would do that, but I have to copy that file off of the broken system as I can't use a USB flash stick . --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: How to recover X display?
From: Josef Lowder
> Perhaps I'll just have to reinstall and risk losing my data as
> I don't know a way to get it copied off.
USB drive, shirley?
[kernel modules and GRUB conf, not the problem]
>> We might logically research the exact Xorg errors for these, spoze?
>> 3) Research our error for known solutions:
>> module ABI major version (1) doesn't match server's version (2)
>> failed to load module "v41" (module requirement mismatch,0)
> ("v41" above should have been "v4l"
This is an X problem IIRC. The module being referred to is the X
module, not a kernel module. Did X get upgraded at some point?
The thing that's messed up is /usr/lib/xorg/modules/drivers/v4l_drv.*
AFAICT. If you have any reference to v4l in your xorg.conf , then
edit that file and comment that line out. Your webcam and/or TV
tuner will stop being able to use XV, but you'll get X back. Also,
grep Driver /etc/X11/xorg.conf
lspci | grep VGA
...will tell you which X module you're using and which graphics
card you have. In fact, you should take your xorg.conf and put
it on your website somewhere, then follow up with a URL here.
> The problem seems to pertain mainly if not exclusively to the X server.
> I tried running '/usr/sbin/XFdrake' and it seems to show that everything
> is set correctly.
XFdrake... something Mandrake-specific? Gah, most of these tools are
rather poorly debugged.
> Should I try to remove all files on the system pertaining to virtualbox?
This shouldn't have any effect on anything, but sure, try your distro's
equivalent of "yum remove virtualbox". FWIW, I installed virtualbox
on my Thinkpad T42p a while back, and never had any problems with it
horking up suspend-to-RAM or doing anything weird to X. Then again,
I'm using Gentoo, and YDistroMV. HTH anyway,
--
Matt G / Dances With Crows
The Crow202 Blog: http://crow202.org/wordpress/
There is no Darkness in Eternity/But only Light too dim for us to see
---
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: How to recover X display?
Thanks for all your suggestions. I've tried to follow-up on every one,
but still haven't been able to solve the problem. Perhaps I'll just have
to reinstall and risk losing my data as I don't know a way to get it copied off.
On 3/22/09, Lisa Kachold wrote:
> Let's look at how we must package a problem for the PLUG:
> We follow these steps (dumping into email):
> 1) What is it (versions, etc)?
As previously reported, the Linux kernel booting is: kernel.h-2.6.18.6
dated Feb 23, 2007 and /boot/vmlinuz is dated Apr 6, 2007
None of this changed as a result of installing virtualbox.
> 2) What is she whining about (Linux will tell you what is the issue)
> Check the file creation date for your Grub at /here/boot/grub/menu.lst
> Check to verify what she is currently booting. look for backup files and diff.
As previously reported, there has been no change in the grub menu.lst.
It also is dated Apr 6, 2007. There are no backup or previous version
files for this, so nothing from which to 'diff' compare.
> We might logically research the exact Xorg errors for these, spoze?
As previously mentioned, I did this and found only two reported errors
as listed below.
> 3) Research our error for known solutions:
> module ABI major version (1) doesn't match server's version (2)
> failed to load module "v41" (module requirement mismatch,0)
I have searched the 'net for any info about how to resolve these two
reported errors, including the two links you provided, and have seen
a few corresponding references, but still haven't found any way to
correct these two errors. ("v41" above should have been "v4l" --
lower case letter "L" not the number one "1")
> 4) The Zen of Troubleshooting, "The error is the problem"
> Looks like you have a kernel module mismatch grasshopper.
You are no doubt correct, but how might one correct this problem?
Linux boots up fine, but without any "X" graphical access, just a
blank screen. I can switch to terminals 1 thru 6 and they all work,
but when I type 'startx' the response is: "Cannot access the X server."
The problem seems to pertain mainly if not exclusively to the X server.
I tried running '/usr/sbin/XFdrake' and it seems to show that everything
is set correctly.
Should I try to remove all files on the system pertaining to virtualbox?
---
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
RE: How to recover X display?
Updates between versions are sometimes a lottery! Let's look at how we must package a problem for the PLUG: We follow these steps (dumping into email): 1) What is it (versions, etc)? 2) What is she whining about (Linux like any good partner will tell you very clearly what is the issue)? [Ignore my installation references for Ubuntu's Virtualbox (they are just info); but possibly an update to the ABI module or v41 module were done during the installation?] Check the file creation date for your Grub at /here/boot/grub/menu.lst Check to verify what she is currently booting there - look for backup files and diff. Discussion: http://www.pclinuxos.com/index.php?option=com_smf&Itemid=26&topic=54523.0 We might logically research the exact Xorg errors for these, spoze? 3) Research our error for known solutions: module ABI major version (1) doesn't match server's version (2) failed to load module "v41" (module requirement mismatch,0) http://ubuntuforums.org/archive/index.php/t-313691.html PCLinuxOs virtualbox module issues http://www.neowin.net/forum/index.php?showtopic=611644 4) The Zen of Troubleshooting, "The error is the problem" Looks like you have a kernel module mismatch grasshopper. Obnosis | (503)754-4452 PLUG Linux Security Labs 2nd Saturday Each mo...@noon - 3PM > Date: Sun, 22 Mar 2009 12:04:29 -0700 > Subject: Re: How to recover X display? > From: j...@actionline.com > To: plug-discuss@lists.plug.phoenix.az.us > > Thanks very much Lisa. Following is what I've discovered so far: > > On 3/22/09, Lisa Kachold wrote: > > Quick Resurrection -- [drop info from these steps w reply to organize the > > issue] > > > > 1) Verify bootloader GRUB -- What does your grub.conf look like? > > Compare old and new, specifically looking at kernel boot options. > > What are you booting into? > > There is no grub.conf. In /boot/grub found menu.lst dated Apr 6, 2007 > (last date chgd) > It boots to /boot/vmlinuz VGA=788 (this is the one that locks up) > Also to /boot/vmlinuz without VGA-788 and this works, opens to # command line > Also to /boot vmlinuz "failsafe" > Also to win.xp which still works > All three /voot/vmlinuz boot to kernel.h-2.6.18.6 dated Feb 23, 2007 > > > 2) Verify X -- Boot to rescue mode and see what your /etc/X11/xorg.conf > > says. > > There would have been an old xorg.conf that was copied to backup. > > xorg.conf and xorg.conf.old are both dated Apr 6, 2007 > (Apparently no change from when everything was working.) > diff showed "old" had "DPMS" "false" and current "DPMS" (no false) > 'diff' also showed the following line identical in both old and new: > #DontZoom # disable (resolution switching) > > > Look at /var/log/Xorg.0.log for clues. > > Scrolling through the entire log file showed only two items flagged (EE): > module ABI major version (1) doesn't match server's version (2) > failed to load module "v41" (module requirement mismatch,0) > > > Run Xconfigurator after copying current xorg.conf to KNOWNBACKUP. > > Found no 'Xconfigurtor' nor 'xconfig' on the system. > > > Or just copy the current file to backup and move the old over. > > The current and 'old' are the same except as noted above. > > > You might want to add vboxdrv to the list of modules in /etc/modules to be > > loaded automatically at startup in. > > I did this and rebooted, but still get the message: > "cannot connect to X server" > > > Virtualbox > > apt-get install virtualbox-ose > > I don't have 'apt-get' so don't know where to go from here. :( > > > virtualbox-ose-modules-2.6.24-1-amd64 virtualbox-ose-source > > apt-get install module-assistant > > module-assistant prepare virtualbox-ose > > module-assistant auto-install virtualbox-ose > > modprove vboxdrv > > adduser myusername vboxusers > > We did add my user name to vbox users yesterday. > The system was working (after installing virtualbox) > until we rebooted, then the current problem began. > I can still boot the system into the non-fb (sp?) second > grub boot option and can switch among the terminals, > except F7 has a blank screen with solid cursor upper left. > --- > PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us > To subscribe, unsubscribe, or to change your mail settings: > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss _ Windows Live™ SkyDrive: Get 25 GB of free online storage. http://windowslive.com/online/skydrive?ocid=TXT_TAGLM_WL_skydrive_032009--- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
Re: How to recover X display?
Thanks very much Lisa. Following is what I've discovered so far: On 3/22/09, Lisa Kachold wrote: > Quick Resurrection -- [drop info from these steps w reply to organize the > issue] > > 1) Verify bootloader GRUB -- What does your grub.conf look like? > Compare old and new, specifically looking at kernel boot options. > What are you booting into? There is no grub.conf. In /boot/grub found menu.lst dated Apr 6, 2007 (last date chgd) It boots to /boot/vmlinuz VGA=788 (this is the one that locks up) Also to /boot/vmlinuz without VGA-788 and this works, opens to # command line Also to /boot vmlinuz "failsafe" Also to win.xp which still works All three /voot/vmlinuz boot to kernel.h-2.6.18.6 dated Feb 23, 2007 > 2) Verify X -- Boot to rescue mode and see what your /etc/X11/xorg.conf says. > There would have been an old xorg.conf that was copied to backup. xorg.conf and xorg.conf.old are both dated Apr 6, 2007 (Apparently no change from when everything was working.) diff showed "old" had "DPMS" "false" and current "DPMS" (no false) 'diff' also showed the following line identical in both old and new: #DontZoom # disable (resolution switching) > Look at /var/log/Xorg.0.log for clues. Scrolling through the entire log file showed only two items flagged (EE): module ABI major version (1) doesn't match server's version (2) failed to load module "v41" (module requirement mismatch,0) > Run Xconfigurator after copying current xorg.conf to KNOWNBACKUP. Found no 'Xconfigurtor' nor 'xconfig' on the system. > Or just copy the current file to backup and move the old over. The current and 'old' are the same except as noted above. > You might want to add vboxdrv to the list of modules in /etc/modules to be > loaded automatically at startup in. I did this and rebooted, but still get the message: "cannot connect to X server" > Virtualbox > apt-get install virtualbox-ose I don't have 'apt-get' so don't know where to go from here. :( > virtualbox-ose-modules-2.6.24-1-amd64 virtualbox-ose-source > apt-get install module-assistant > module-assistant prepare virtualbox-ose > module-assistant auto-install virtualbox-ose > modprove vboxdrv > adduser myusername vboxusers We did add my user name to vbox users yesterday. The system was working (after installing virtualbox) until we rebooted, then the current problem began. I can still boot the system into the non-fb (sp?) second grub boot option and can switch among the terminals, except F7 has a blank screen with solid cursor upper left. --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
RE: How to recover X display?
Hi Joe: There are known issues with virtualbox on a Thinkpad related to suspend/hibernate failures (see below). Quick Resurrection [drop info from these steps into this email with reply to organize the issue] 1) Verify bootloader GRUB What does your grub.conf look like? Compare the old and new version, specifically looking at the kernel boot options. What are you booting into? 2) Verify X Boot into rescue mode, and go see what your /etc/X11/xorg.conf says. Look at /var/log/Xorg.0.log for clues. There would have been an old xorg.conf that was copied to backup. Run Xconfigurator after copying current xorg.conf to KNOWNBACKUP. Or just copy the current file to backup and move the old over. Virtualbox apt-get install virtualbox-ose virtualbox-ose-modules-2.6.24-1-amd64 virtualbox-ose-sourceapt-get install module-assistantmodule-assistant prepare virtualbox-osemodule-assistant auto-install virtualbox-osemodprove vboxdrvadduser myusername vboxusers You might want to add vboxdrv to the list of modules in /etc/modules to be loaded automatically at startup in. Virtualbox fails Hibernate http://ubuntuforums.org/showpost.php?p=4582777&postcount=3 To circumvent this, put this in ~/bin/vbox_suspend: #!/bin/bash for x in `vboxmanage -nologo list runningvms` do vboxmanage -nologo controlvm $x savestate done and make it executable. you can test it by running ~/bin/vbox_suspend, which should save all your running virtual machines. put the following lines in /etc/pm/sleep.d/90virtualbox and make it executable as well: #!/bin/bash case $1 in hibernate) su YOURUSER -c /home/YOURUSER/bin/vbox_suspend ;; esac This is not very elegant (as the user is hard-coded), but it works. I have tried to make the machines resume on thaw, but it would place the vms on the wrong workspace even if it know which X server to use, which it doesn't. Known bug on Thinkpad with Suspend Drivers for ThinkPads: http://www.thinkwiki.org/wiki/ThinkWiki Obnosis | (503)754-4452 PLUG Linux Security Labs 2nd Saturday Each mo...@noon - 3PM > Date: Sun, 22 Mar 2009 08:21:03 -0700 > Subject: How to recover X display? > From: j...@actionline.com > To: plug-discuss@lists.plug.phoenix.az.us > > Yesterday at the ASU installfest, I sought help on how to install > VirtualBox on my HP Thinkpad running PCLinuxOS. After downloading and > installing VirtualBox, upon reboot, PCLinux goes through all the usual > startup steps, and when GRUB displays 4 options: Linux, Linux AFB, > Linux failsafe, and Windows (dual boot), it defaults into the first > Linux option, displays all the usual startup screens, and then the > screen goes blank with a small "-" in the upper left corner, but > nothing else. > > I can still boot into Windows, and Linux failsafe, but when I get to > the command line and type 'startx' the same result. No graphical > display? > > How can I get back to where I was before installing VirtualBox (which, > it seems apparent) caused this problem? > --- > PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us > To subscribe, unsubscribe, or to change your mail settings: > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss _ Windows Live™ SkyDrive: Get 25 GB of free online storage. http://windowslive.com/online/skydrive?ocid=TXT_TAGLM_WL_skydrive_032009--- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
