Re: Botched X.org upgrade, need help
On Fri, Nov 09, 2007 at 03:26:15AM +, we recorded a bogon-computron collision of the <[EMAIL PROTECTED]> flavor, containing: > On Thursday 08 November 2007, Andrew Falanga said: > > On Nov 8, 2007 12:37 PM, Warren Block <[EMAIL PROTECTED]> wrote: > > > On Thu, 8 Nov 2007, Andrew Falanga wrote: > > > > Well, at last I think it's botched. I really was following the > > > directions [...] > > (WW) Warning, couldn't open module pcidata > > (II) UnloadModule: "pcidata" > > (EE) Failed to load module "pcidata" (module does not exist, 0) > > > > Fatal server error: > > Unable to load required base modules, Exiting... > I had a very similar experience, with the X server reporting missing modules immediately after I thought I'd followed the upgrade instructions to the letter (including the portupgrade -a, migrating all the /usr/X11R6 stuff with mergebase, and various nvidia-driver caveats). Turns out that in my case the xorg-drivers and xorg-fonts ports had not been added by the upgrade process, probably because I had a missing metaport in my previous install. That was the one block of caveats I apparently missed. In the end, I was able to just do a make install of the xorg metaport and it picked up the missing two, then I was back in business. Perhaps that's what's going on with you? Or perhaps not --- I see you also mentioned you hadn't updated ModulePath, and perhaps that was the only reason you are having problems? I didn't see a follow-up saying that was it. -- Tom RussoKM5VY SAR502 DM64ux http://www.swcp.com/~russo/ Tijeras, NM QRPL#1592 K2#398 SOC#236 AHTB#1 http://kevan.org/brain.cgi?DDTNM "And, isn't sanity really just a one-trick pony anyway? I mean all you get is one trick, rational thinking, but when you're good and crazy, oooh, oooh, oooh, the sky is the limit!" --- The Tick ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Botched X.org upgrade, need help
On Nov 9, 2007 7:00 AM, Adam J Richardson <[EMAIL PROTECTED]> wrote: > Andrew Falanga wrote: > Hi Andy, > > I botched my 6.9-7.2 upgrade too. It's easy to do even if you follow the > instructions. Can't remember what the problem was now, certainly it was > something no one else had, typical. :^) Ah well, all fixed now anyway. > > It's easy to botch even a simple install of X. Took me a while to learn > that you have to install 1) Xorg, 2) mesa-demos, 3) nVidia driver, in > that order (assuming you want mesa-demos, of course). > > Regards, > Adam J Richardson > Thanks. Unfortunately, I'm using amd64 and the nVidia driver isn't yet ported (there was a thread on the reason why quite some time ago, it's something to do with FreeBSD internally). Andy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Botched X.org upgrade, need help
Andrew Falanga wrote: Well, at last I think it's botched. I really was following the directions (I have the script file as UPDATING suggests to prove it :-), but the upgrade didn't work as the X server failed to start after I rebooted. I'm hoping some kind person here will know the answer before I e-mail the list mentioned in that section of UPDATING. Anyway, that's basically, what happened. I have kdm set to start on bootup and it complained that X failed to start. When I got to the point of "portupgrade -aP" in the UPDATING section for X.org 6.9 -> 7.2; I decided to go with that command instead of "portupgrade -a" thinking that by now, even for amd64, the packages would be available. Perhaps a bad assumption. Anyway, once that completed, the stats reported by portupgrade were disconcerting but I thought that it was ok and continued. portupgrade reported that only 2 packages were porcessed, most were ignored with 50 some skipped and 1 failed. I then proceeded to the mergebase.sh script, ran that and when I was satisfied that all was done as expected, I rebooted my machine. Well, that's when X failed to start. So, how would I go about correcting this problem? Andy Hi Andy, I botched my 6.9-7.2 upgrade too. It's easy to do even if you follow the instructions. Can't remember what the problem was now, certainly it was something no one else had, typical. :^) Ah well, all fixed now anyway. It's easy to botch even a simple install of X. Took me a while to learn that you have to install 1) Xorg, 2) mesa-demos, 3) nVidia driver, in that order (assuming you want mesa-demos, of course). Regards, Adam J Richardson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Botched X.org upgrade, need help
On Nov 8, 2007 8:03 PM, Beech Rintoul <[EMAIL PROTECTED]> wrote: > From UPDATING: > > "If you plan on keeping your current /etc/X11/xorg.conf, make sure you > change ModulePath to /usr/local/lib/xorg/modules prior to running X." > > Otherwise, just move /etc/X11/xorg.conf and restart X you can then add > in your video configs from the original. > > Beech > > Well, that's what I get for not reading down far enough in the Caveats section. Thanks for the tip. Andy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Botched X.org upgrade, need help
On Thursday 08 November 2007, Andrew Falanga said: > On Nov 8, 2007 12:37 PM, Warren Block <[EMAIL PROTECTED]> wrote: > > On Thu, 8 Nov 2007, Andrew Falanga wrote: > > > Well, at last I think it's botched. I really was following the > > > > directions > > > > > (I have the script file as UPDATING suggests to prove it :-), > > > but the upgrade didn't work as the X server failed to start > > > after I rebooted. > > > > I'm > > > > > hoping some kind person here will know the answer before I > > > e-mail the > > > > list > > > > > mentioned in that section of UPDATING. Anyway, that's > > > basically, what happened. I have kdm set to start on bootup > > > and it complained that X > > > > failed > > > > > to start. > > > > > > When I got to the point of "portupgrade -aP" in the UPDATING > > > section for X.org 6.9 -> 7.2; I decided to go with that command > > > instead of > > > > "portupgrade > > > > > -a" thinking that by now, even for amd64, the packages would be > > > > available. > > > > > Perhaps a bad assumption. Anyway, once that completed, the > > > stats > > > > reported > > > > > by portupgrade were disconcerting but I thought that it was ok > > > and continued. portupgrade reported that only 2 packages were > > > porcessed, > > > > most > > > > > were ignored with 50 some skipped and 1 failed. > > > > > > I then proceeded to the mergebase.sh script, ran that and when > > > I was satisfied that all was done as expected, I rebooted my > > > machine. Well, that's when X failed to start. So, how would I > > > go about correcting this problem? > > > > You'll at least have to do a portupgrade -a to get all the ports > > that still need to be built. > > > > -Warren Block * Rapid City, South Dakota USA > > I was wondering about that. Can I do that although I've completed > the instructions for the X.org update? That is, I've already run > that script they mention at the end and /usr/X11R6 is now a symlink > to /usr/local. Also, I did a pkg_info | grep xorg and it looks like > everything was upgraded to 7.3 ok. > > At any rate, here's what the log file said when X.org tried to > load. > > X.Org X Server 1.4.0 > Release Date: 5 September 2007 > X Protocol Version 11, Revision 0 > Build Operating System: FreeBSD 6.2-RELEASE-p7 amd64 > Current Operating System: FreeBSD sniper 6.2-RELEASE-p7 FreeBSD > 6.2-RELEASE-p7 #1: Sat Sep 8 13:37:08 MDT 2007 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC > amd64 > Build Date: 08 November 2007 01:09:22AM > > Before reporting problems, check http://wiki.x.org > to make sure that you have the latest version. > Module Loader present > Markers: (--) probed, (**) from config file, (==) default setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > (==) Log file: "/var/log/Xorg.0.log", Time: Thu Nov 8 19:28:38 > 2007 (==) Using config file: "/etc/X11/xorg.conf" > (==) ServerLayout "X.org Configured" > (**) |-->Screen "Screen0" (0) > (**) | |-->Monitor "Monitor0" > (**) | |-->Device "Card0" > (**) |-->Input Device "Mouse0" > (**) |-->Input Device "Keyboard0" > (==) Automatically adding devices > (==) Automatically enabling devices > (WW) The directory "/usr/X11R6/lib/X11/fonts/CID/" does not exist. > Entry deleted from font path. > (==) Including the default font path > /usr/local/lib/X11/fonts/misc/,/usr/local/lib/X11/fonts/TTF/,/usr/l >ocal/lib/X11/fonts/OTF,/usr/local/lib/X11/fonts/Type1/,/usr/local/li >b/X11/fonts/100dpi/,/usr/local/lib/X11/fonts/75dpi/. (**) FontPath > set to: > /usr/X11R6/lib/X11/fonts/misc/, > /usr/X11R6/lib/X11/fonts/TTF/, > /usr/X11R6/lib/X11/fonts/Type1/, > /usr/X11R6/lib/X11/fonts/75dpi/, > /usr/X11R6/lib/X11/fonts/100dpi/, > /usr/local/lib/X11/fonts/misc/, > /usr/local/lib/X11/fonts/TTF/, > /usr/local/lib/X11/fonts/OTF, > /usr/local/lib/X11/fonts/Type1/, > /usr/local/lib/X11/fonts/100dpi/, > /usr/local/lib/X11/fonts/75dpi/ > (**) RgbPath set to "/usr/X11R6/lib/X11/rgb" > (**) ModulePath set to "/usr/X11R6/lib/modules" > (II) Loader magic: 0x67eda0 > (II) Module ABI versions: > X.Org ANSI C Emulation: 0.3 > X.Org Video Driver: 2.0 > X.Org XInput driver : 2.0 > X.Org Server Extension : 0.3 > X.Org Font Renderer : 0.5 > (II) Loader running on freebsd > (II) LoadModule: "pcidata" > (WW) Warning, couldn't open module pcidata > (II) UnloadModule: "pcidata" > (EE) Failed to load module "pcidata" (module does not exist, 0) > > Fatal server error: > Unable to load required base modules, Exiting... From UPDATING: "If you plan on keeping your current /etc/X11/xorg.conf, make sure you change ModulePath to /usr/local/lib/xorg/modules prior to running X." Otherwise, just move /etc/X11/xorg.conf and restart X you can then add in your video configs from the original. Beech -- --- Beech Rintoul - Fre
Re: Botched X.org upgrade, need help
On Nov 8, 2007 12:37 PM, Warren Block <[EMAIL PROTECTED]> wrote: > On Thu, 8 Nov 2007, Andrew Falanga wrote: > > > Well, at last I think it's botched. I really was following the > directions > > (I have the script file as UPDATING suggests to prove it :-), but the > > upgrade didn't work as the X server failed to start after I rebooted. > I'm > > hoping some kind person here will know the answer before I e-mail the > list > > mentioned in that section of UPDATING. Anyway, that's basically, what > > happened. I have kdm set to start on bootup and it complained that X > failed > > to start. > > > > When I got to the point of "portupgrade -aP" in the UPDATING section for > > X.org 6.9 -> 7.2; I decided to go with that command instead of > "portupgrade > > -a" thinking that by now, even for amd64, the packages would be > available. > > Perhaps a bad assumption. Anyway, once that completed, the stats > reported > > by portupgrade were disconcerting but I thought that it was ok and > > continued. portupgrade reported that only 2 packages were porcessed, > most > > were ignored with 50 some skipped and 1 failed. > > > > I then proceeded to the mergebase.sh script, ran that and when I was > > satisfied that all was done as expected, I rebooted my machine. Well, > > that's when X failed to start. So, how would I go about correcting this > > problem? > > You'll at least have to do a portupgrade -a to get all the ports that > still need to be built. > > -Warren Block * Rapid City, South Dakota USA > I was wondering about that. Can I do that although I've completed the instructions for the X.org update? That is, I've already run that script they mention at the end and /usr/X11R6 is now a symlink to /usr/local. Also, I did a pkg_info | grep xorg and it looks like everything was upgraded to 7.3 ok. At any rate, here's what the log file said when X.org tried to load. X.Org X Server 1.4.0 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 6.2-RELEASE-p7 amd64 Current Operating System: FreeBSD sniper 6.2-RELEASE-p7 FreeBSD 6.2-RELEASE-p7 #1: Sat Sep 8 13:37:08 MDT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 Build Date: 08 November 2007 01:09:22AM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Thu Nov 8 19:28:38 2007 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "X.org Configured" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "Monitor0" (**) | |-->Device "Card0" (**) |-->Input Device "Mouse0" (**) |-->Input Device "Keyboard0" (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory "/usr/X11R6/lib/X11/fonts/CID/" does not exist. Entry deleted from font path. (==) Including the default font path /usr/local/lib/X11/fonts/misc/,/usr/local/lib/X11/fonts/TTF/,/usr/local/lib/X11/fonts/OTF,/usr/local/lib/X11/fonts/Type1/,/usr/local/lib/X11/fonts/100dpi/,/usr/local/lib/X11/fonts/75dpi/. (**) FontPath set to: /usr/X11R6/lib/X11/fonts/misc/, /usr/X11R6/lib/X11/fonts/TTF/, /usr/X11R6/lib/X11/fonts/Type1/, /usr/X11R6/lib/X11/fonts/75dpi/, /usr/X11R6/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/ (**) RgbPath set to "/usr/X11R6/lib/X11/rgb" (**) ModulePath set to "/usr/X11R6/lib/modules" (II) Loader magic: 0x67eda0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 2.0 X.Org XInput driver : 2.0 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on freebsd (II) LoadModule: "pcidata" (WW) Warning, couldn't open module pcidata (II) UnloadModule: "pcidata" (EE) Failed to load module "pcidata" (module does not exist, 0) Fatal server error: Unable to load required base modules, Exiting... Andy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Botched X.org upgrade, need help
On Thu, 8 Nov 2007, Andrew Falanga wrote: Well, at last I think it's botched. I really was following the directions (I have the script file as UPDATING suggests to prove it :-), but the upgrade didn't work as the X server failed to start after I rebooted. I'm hoping some kind person here will know the answer before I e-mail the list mentioned in that section of UPDATING. Anyway, that's basically, what happened. I have kdm set to start on bootup and it complained that X failed to start. When I got to the point of "portupgrade -aP" in the UPDATING section for X.org 6.9 -> 7.2; I decided to go with that command instead of "portupgrade -a" thinking that by now, even for amd64, the packages would be available. Perhaps a bad assumption. Anyway, once that completed, the stats reported by portupgrade were disconcerting but I thought that it was ok and continued. portupgrade reported that only 2 packages were porcessed, most were ignored with 50 some skipped and 1 failed. I then proceeded to the mergebase.sh script, ran that and when I was satisfied that all was done as expected, I rebooted my machine. Well, that's when X failed to start. So, how would I go about correcting this problem? You'll at least have to do a portupgrade -a to get all the ports that still need to be built. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Botched X.org upgrade, need help
On Thu, Nov 08, 2007 at 07:58:39AM -0700, Andrew Falanga wrote: > I then proceeded to the mergebase.sh script, ran that and when I was > satisfied that all was done as expected, I rebooted my machine. Well, > that's when X failed to start. So, how would I go about correcting this > problem? Look at /var/log/Xorg.0.log to see what exactly is the problem. While you're busy solving the problem, it is best to log into a shell instead of xdm. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpbX0Ni1sAUy.pgp Description: PGP signature
