{"id":1323,"date":"2009-08-16T00:44:22","date_gmt":"2009-08-16T05:44:22","guid":{"rendered":"http:\/\/www.microdevsys.com\/WordPress\/?p=1323"},"modified":"2012-12-01T01:30:41","modified_gmt":"2012-12-01T06:30:41","slug":"fedora-update-undefined-symbol-driopendrmmaster","status":"publish","type":"post","link":"https:\/\/microdevsys.com\/wp\/fedora-update-undefined-symbol-driopendrmmaster\/","title":{"rendered":"Fedora Update: undefined symbol: DRIOpenDRMMaster"},"content":{"rendered":"<p>\n\tFollowing a recent upgrade, <strong>Xorg<\/strong> was apparently also updated to version&nbsp;<strong>xorg-x11-server-Xorg-1.6.1.901-1.fc11.i586<\/strong> which unfortunately didn&#39;t play nicely with version <strong>xorg-x11-drv-ati-6.12.2-14.fc11.i586<\/strong> .&nbsp; After a brief investigation, the combination resulted in this error:\n<\/p>\n<p style=\"margin-left: 40px;\">\n\t<strong>&nbsp;\/usr\/lib\/xorg\/modules\/drivers\/\/radeon_drv.so: undefined symbol: DRIOpenDRMMaster<\/strong>\n<\/p>\n<p>\n\tUltimately, this had the following effect:\n<\/p>\n<ul>\n<li>\n\t\tNo GUI (System never got as far as showing any graphics let alone KDE, Gnome etc)\n\t<\/li>\n<li>\n\t\tNo Keyboard functionality:&nbsp;Couldn&#39;t open console window with <strong>CTRL-ALT-F1-9<\/strong> keys.\n\t<\/li>\n<li>\n\t\tNo mouse functionality.\n\t<\/li>\n<li>\n\t\tNo error message on the screen.&nbsp; Just an empty screen.\n\t<\/li>\n<\/ul>\n<p>\n\tNot good.&nbsp; The system was frozen and unresponsive and nothing I tried on the terminal did anything.&nbsp; Here&#39;s how to go a about solving this issue.\n<\/p>\n<p>\n\t&nbsp;<!--more-->\n<\/p>\n<p>\n\t<span style=\"font-size: medium;\"><strong>SOLUTION<\/strong><\/span>\n<\/p>\n<p>\n\tThe quick solution to this, as it turned out after a more extensive investigation, was to update the <strong>Xorg<\/strong> RPM&#39;s.&nbsp; Here&#39;s the procedure:\n<\/p>\n<ul>\n<li>\n\t\t<strong>wget <a href=\"ftp:\/\/rpmfind.net\/linux\/fedora\/updates\/testing\/11\/i386\/xorg-x11-server-Xorg-1.6.2-3.fc11.i586.rpm\" rel=\"external nofollow\">ftp:\/\/rpmfind.net\/linux\/fedora\/updates\/testing\/11\/i386\/xorg-x11-server-Xorg-1.6.2-3.fc11.i586.rpm<\/a><\/strong>\n\t<\/li>\n<li>\n\t\t<strong>wget <a href=\"ftp:\/\/rpmfind.net\/linux\/fedora\/updates\/testing\/11\/i386\/xorg-x11-server-common-1.6.2-3.fc11.i586.rpm\" rel=\"external nofollow\">ftp:\/\/rpmfind.net\/linux\/fedora\/updates\/testing\/11\/i386\/xorg-x11-server-common-1.6.2-3.fc11.i586.rpm<\/a><\/strong>\n\t<\/li>\n<li>\n\t\t<strong>rpm -Uvh xorg-x11-server-Xorg-1.6.2-3.fc11.i586.rpm xorg-x11-server-common-1.6.2-3.fc11.i586.rpm<\/strong>\n\t<\/li>\n<\/ul>\n<p>\n\tFollowing the above, you&#39;ll either need a restart or to simply run:\n<\/p>\n<ul>\n<li>\n\t\t<strong>init 3<\/strong>\n\t<\/li>\n<li>\n\t\tThen <strong>init 5<\/strong>\n\t<\/li>\n<\/ul>\n<p>\n\tFirst, this will bring you to level 3 or non GUI stage of the boot up process.&nbsp; <strong>init 5<\/strong> will bring you to the GUI stage where you can login to your favorite <strong>UI<\/strong> like <strong>KDE<\/strong>&nbsp;or <strong>GNOME<\/strong>.&nbsp; And that resolved the issue for me.\n<\/p>\n<p>\n\t&nbsp;\n<\/p>\n<p>\n\t<strong>Wait!&nbsp; How do I&nbsp;get into my system now if the keyboard, mouse and video aren&#39;t working?<\/strong>\n<\/p>\n<p>\n\tThere are really two ways I&nbsp;used.&nbsp; First option was to use another computer on my home network to get into the problematic PC so I can get things fixed up:\n<\/p>\n<ul>\n<li>\n\t\tIn a Windows PC, I&nbsp;installed PUTTY.&nbsp; You can get the application from <a href=\"http:\/\/www.chiark.greenend.org.uk\/~sgtatham\/putty\/\" rel=\"external nofollow\">here<\/a>.\n\t<\/li>\n<li>\n\t\tUsing PUTTY, SSH&nbsp;to your Workstation over your home network.&nbsp;\n\t<\/li>\n<li>\n\t\tYou should now be into your Workstations CLI.\n\t<\/li>\n<\/ul>\n<p>\n\tThe second way was to edit the boot grub startup options when the system starts up so you end up in <strong>init level 1<\/strong>.&nbsp; Here&#39;s how to do this:\n<\/p>\n<ul>\n<li>\n\t\tStart up your system.&nbsp; When the GRUB&nbsp;menu comes up, use the arrow keys to highlight the kernel you want to boot.\n\t<\/li>\n<li>\n\t\tInstead of clicking ENTER&nbsp;on the kernel, press the letter <strong>e<\/strong>.&nbsp; This will let you edit the boot parameters.\n\t<\/li>\n<li>\n\t\tYou may see a label that looks like this:&nbsp;<strong>kernel \/vmlinuz-2.6.29.6-217.2.3.fc11.i586 ro root=LABEL=\/<\/strong>\n\t<\/li>\n<li>\n\t\tAdd <strong> single<\/strong> to the end of it including a space in front to make it look like this:<br \/>\n\t\t<strong>kernel \/vmlinuz-2.6.29.6-217.2.3.fc11.i586 ro root=LABEL=\/ <\/strong><span style=\"color: rgb(0, 204, 0);\"><strong>single<\/strong><\/span>\n\t<\/li>\n<li>\n\t\tNow press enter to confirm the settings then press the <strong>b<\/strong> key to boot the above line.&nbsp; This will bring you to the command line <strong>init level 1<\/strong> of the system.&nbsp; (<strong>init 5<\/strong> is the <strong>GUI<\/strong>&nbsp;you can&#39;t start on account of above problem)\n\t<\/li>\n<\/ul>\n<p>\n\t&nbsp;\n<\/p>\n<p>\n\t<span style=\"font-size: medium;\"><strong>INVESTIGATION<\/strong><\/span>\n<\/p>\n<p>\n\tThe investigation for this one was a bit tricky and lengthy.&nbsp; For one, <strong>\/var\/log\/Xorg.0.log<\/strong> had no errors or warnings applicable to the above.&nbsp; There were basically no <strong>WW<\/strong> or <strong>EE<\/strong> marked items in the above file.&nbsp; The <strong>WW<\/strong> stands for <strong>warning<\/strong> and the <strong>EE<\/strong> stands for <strong>error<\/strong>.&nbsp; There was no messages on the screen either.&nbsp; Naturally since this appears video related, I&nbsp;look into <strong>\/etc\/X11\/xorg.conf<\/strong> but don&#39;t notice any changes there.&nbsp; First I try to copy this xorg.conf file out to <strong>old.xorg.conf<\/strong> and restart so the system regenerates it&#39;s own config file.&nbsp; That doesn&#39;t work either so I know my <strong>xorg.conf<\/strong> couldn&#39;t be at fault.&nbsp; Checking the main system log <strong>\/var\/log\/messages<\/strong> yielded many of these:\n<\/p>\n<blockquote>\n<p>\n\t\tAug&nbsp; 9 07:06:26 lhs gdm-binary[2930]: WARNING: GdmDisplay: display lasted 0.234230 seconds<br \/>\n\t\tAug&nbsp; 9 07:06:26 lhs gdm-binary[2930]: WARNING: GdmDisplay: display lasted 0.201843 seconds<br \/>\n\t\tAug&nbsp; 9 07:06:26 lhs gdm-binary[2930]: WARNING: GdmDisplay: display lasted 0.203118 seconds<br \/>\n\t\tAug&nbsp; 9 07:06:26 lhs gdm-binary[2930]: WARNING: GdmDisplay: display lasted 0.202416 seconds<br \/>\n\t\tAug&nbsp; 9 07:06:27 lhs gdm-binary[2930]: WARNING: GdmDisplay: display lasted 0.205379 seconds<br \/>\n\t\tAug&nbsp; 9 07:06:27 lhs gdm-binary[2930]: WARNING: GdmDisplay: display lasted 0.215556 seconds<br \/>\n\t\tAug&nbsp; 9 07:06:27 lhs <span style=\"color: rgb(255, 0, 0);\">gdm-binary<\/span>[2930]: WARNING: GdmLocalDisplayFactory: maximum number of X display failures reached: <span style=\"color: rgb(255, 153, 0);\">check X server log for errors<\/span><br \/>\n\t\tAug&nbsp; 9 07:06:27 lhs init: prefdm main process (2930) terminated with status 1<br \/>\n\t\tAug&nbsp; 9 07:06:27 lhs init: <span style=\"color: rgb(255, 0, 0);\">prefdm<\/span> main process ended, respawning\n\t<\/p>\n<\/blockquote>\n<p>\n\tNotice <strong>prefdm<\/strong> and <strong>gdm-binary<\/strong>.&nbsp; I&nbsp;really had no idea what these were but possibly these could just be scripts.&nbsp; So a quick search:\n<\/p>\n<p style=\"margin-left: 40px;\">\n\t<strong>$ locate prefdm<\/strong><br \/>\n\t\/etc\/X11\/prefdm<br \/>\n\t\/etc\/event.d\/prefdm<br \/>\n\t$\n<\/p>\n<p>\n\tQuickly checking the files it&#39;s clear they are both scripts and <strong>\/etc\/event.d\/prefdm<\/strong> calls <strong>\/etc\/X11\/prefdm<\/strong>.&nbsp; Editing <strong>\/etc\/X11\/prefdm<\/strong> it&#39;s clear it calls <strong>\/etc\/sysconfig\/desktop<\/strong> which has this setting on my system:\n<\/p>\n<p style=\"margin-left: 40px;\">\n\t<strong>$ cat \/etc\/sysconfig\/desktop<\/strong><br \/>\n\tDESKTOP=KDE<br \/>\n\tDISPLAYMANAGER=GNOME\n<\/p>\n<p>\n\t# DISPLAYMANAGER = GNOME<br \/>\n\t# DISPLAYMANAGER = KDE<br \/>\n\t# DISPLAYMANAGER = WDM<br \/>\n\t# DISPLAYMANAGER = XDM<br \/>\n\tYou have new mail in \/var\/spool\/mail\/root<br \/>\n\t$\n<\/p>\n<p>\n\tSo what does all of this mean for us?&nbsp; Unfortunately, not that much however it does tell us the sequence the startup is taking towards the error.&nbsp; At this point it could be anything and I&#39;m not much closer to what is really causing this problem for me.&nbsp; So the next thing I&nbsp;do is try to find other log files that could point me further in the right direction:\n<\/p>\n<ul>\n<li>\n\t\tcd \/var\/log\n\t<\/li>\n<li>\n\t\tls -al Xorg*\n\t<\/li>\n<\/ul>\n<p>\n\twhich results in a bunch of Xorg files one of which is <strong>\/var\/log\/Xorg.setup.log<\/strong>.&nbsp; Checking this file I see:\n<\/p>\n<blockquote>\n<p>\n\t\t<strong>$ cat Xorg.setup.log<\/strong>\n\t<\/p>\n<p>\n\t\tX.Org X Server 1.6.1.901 (1.6.2 RC 1)<br \/>\n\t\tRelease Date: 2009-5-8<br \/>\n\t\tX Protocol Version 11, Revision 0<br \/>\n\t\tBuild Operating System: Linux 2.6.18-128.1.6.el5 i686<br \/>\n\t\tCurrent Operating System: Linux lhs.localhostservers 2.6.29.6-217.2.3.fc11.i586 #1 SMP Wed Jul 29 15:46:46 EDT 2009 i686<br \/>\n\t\tKernel command line: ro root=LABEL=\/<br \/>\n\t\tBuild Date: 18 May 2009&nbsp; 02:47:59PM<br \/>\n\t\tBuild ID: xorg-x11-server 1.6.1.901-1.fc11<br \/>\n\t\t&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Before reporting problems, check http:\/\/wiki.x.org<br \/>\n\t\t&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to make sure that you have the latest version.<br \/>\n\t\tMarkers: (&#8211;) probed, (**) from config file, (==) default setting,<br \/>\n\t\t&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (++) from command line, (!!) notice, (II) informational,<br \/>\n\t\t&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (WW) warning, (EE) error, (NI) not implemented, (??) unknown.<br \/>\n\t\t(++) Log file: &quot;\/dev\/null&quot;, Time: Wed Aug 12 22:55:23 2009<br \/>\n\t\t(++) Using config file: &quot;\/tmp\/tmpYZhMwdxorg.config&quot;<br \/>\n\t\t<strong>\/usr\/bin\/Xorg: symbol lookup error: \/usr\/lib\/xorg\/modules\/drivers\/\/radeon_drv.so: undefined symbol: DRIOpenDRMMaster<\/strong><br \/>\n\t\t$\n\t<\/p>\n<\/blockquote>\n<p>\n\twhich seams to indicate the problem is with either <strong>\/usr\/bin\/Xorg<\/strong> or the <strong>\/usr\/lib\/xorg\/modules\/drivers\/radeon_drv.so<\/strong>.&nbsp; In fact, at the same time I notice a <strong>\/var\/log\/gdm<\/strong> folder and checking files there also shows the same errors.&nbsp; The radeon driver is the standard radeon driver supplied with Fedora from the <strong>Xorg<\/strong> project.&nbsp; There is an issue with the log file however, it&#39;s slightly old and doesn&#39;t match my last system restart so possibly it&#39;s not related.&nbsp; So to confirm, I run <strong>\/usr\/bin\/Xorg<\/strong> to see if it truly shows the same error and it does:\n<\/p>\n<blockquote>\n<p>\n\t\t$ \/usr\/bin\/Xorg<br \/>\n\t\tX.Org X Server 1.6.1.901 (1.6.2 RC 1)<br \/>\n\t\tRelease Date: 2009-5-8<br \/>\n\t\tX Protocol Version 11, Revision 0<br \/>\n\t\tBuild Operating System: Linux 2.6.18-128.1.6.el5 i686<br \/>\n\t\tCurrent Operating System: Linux lhs.localhostservers<br \/>\n\t\t2.6.29.6-217.2.3.fc11.i586<br \/>\n\t\t#1 SMP Wed Jul 29 15:46:46 EDT 2009 i686<br \/>\n\t\tKernel command line: ro root=LABEL=\/<br \/>\n\t\tBuild Date: 18 May 2009&nbsp; 02:47:59PM<br \/>\n\t\tBuild ID: xorg-x11-server 1.6.1.901-1.fc11<br \/>\n\t\t&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Before reporting problems, check http:\/\/wiki.x.org<br \/>\n\t\t&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to make sure that you have the latest version.<br \/>\n\t\tMarkers: (&#8211;) probed, (**) from config file, (==) default setting,<br \/>\n\t\t&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (++) from command line, (!!) notice, (II) informational,<br \/>\n\t\t&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (WW) warning, (EE) error, (NI) not implemented, (??) unknown.<br \/>\n\t\t(==) Log file: &quot;\/var\/log\/Xorg.0.log&quot;, Time: Wed Aug 12 22:55:46 2009<br \/>\n\t\t(==) Using config file: &quot;\/etc\/X11\/xorg.conf&quot;<br \/>\n\t\t<strong>\/usr\/bin\/Xorg: symbol lookup error: \/usr\/lib\/xorg\/modules\/drivers\/\/radeon_drv.so: undefined symbol: DRIOpenDRMMaster<\/strong><br \/>\n\t\t$\n\t<\/p>\n<\/blockquote>\n<p>\n\tNow I&nbsp;know the error is either with <strong>\/usr\/lib\/Xorg<\/strong> or with the radeon drivers which is astronomically better then what I initially started with.&nbsp; Naturally I decide to look into the driver and end up trying a few things that in the end don&#39;t work:\n<\/p>\n<ul>\n<li>\n\t\tGet an older copy of the radeon, extract <strong>radeon_drv.so<\/strong> then copy it over to the drivers folder above.\n\t<\/li>\n<li>\n\t\tDisable this driver in <strong>xorg.conf<\/strong>.\n\t<\/li>\n<li>\n\t\tTry to get and use the <a href=\"http:\/\/support.amd.com\/us\/gpudownload\/linux\/Legacy\/Pages\/radeon_linux.aspx?type=2.4.1&amp;product=2.4.1.3.24&amp;lang=English\" rel=\"external nofollow\">ATI drivers<\/a>.&nbsp; Unfortunately, ATI&nbsp;decides not to support my card in Kernels 2.6.29 (which is what I&nbsp;now have since F11) so I can&#39;t use those either.&nbsp; Neither does it appear there will be <a href=\"http:\/\/lists.rpmfusion.org\/pipermail\/rpmfusion-users\/2009-May\/000392.html\" rel=\"external nofollow\">any fglrx drivers<\/a> that support R500 or earlier releases of ATI cards!&nbsp; This is bad since my dependence will be solely on the Radeon drivers from x.org in future releases.\n\t<\/li>\n<\/ul>\n<p>\n\tEventually, I try to look into the <strong>\/usr\/bin\/Xorg<\/strong> file.&nbsp; I do notice the <strong>xorg-x11-drv-ati-6.12.2-14.fc11.i586<\/strong> was installed in a recent update I did on Aug 10th, which would suggest the issue is with the driver, however possibly the X server itself hasn&#39;t caught up yet and is calling <strong>DRIOpenDRMMaster<\/strong> incorrectly from the new <strong>ATI<\/strong> driver.&nbsp; A quick look into the <a href=\"http:\/\/x.org\" rel=\"external nofollow\">http:\/\/x.org<\/a> website quickly reveals some <a href=\"http:\/\/cgit.freedesktop.org\/xorg\/driver\/xf86-video-ati\/\" rel=\"external nofollow\">DRI changes<\/a> in the ATI&nbsp;video drivers, however not exactly in regards to the error I had.&nbsp; Since&nbsp;I already tried to get updated drivers and that didn&#39;t work, the other thing to do is to find out if there are updated <strong>Xorg<\/strong> RPM&#39;s available that could potentially work.&nbsp; Quickly checking which package holds the <strong>Xorg<\/strong> executable yields:\n<\/p>\n<blockquote>\n<p>\n\t\t<strong>$ rpm -qf \/usr\/bin\/Xorg<\/strong><br \/>\n\t\txorg-x11-server-Xorg-1.6.1.901-1.fc11.i586<br \/>\n\t\t$\n\t<\/p>\n<\/blockquote>\n<p>\n\tFollowing that I visit one of my favorite sites <a href=\"http:\/\/rpmfind.net\" rel=\"external nofollow\">rpmfind.net <\/a>and end up downloading and updating the above <strong>Xorg<\/strong> server file with the above mentioned testing RPM&#39;s in the solution, resolving the issue.\n<\/p>\n<p>\n\tCheers!<br \/>\n\tTom K.<\/p>\n\n    <div class=\"xs_social_share_widget xs_share_url after_content \t\tmain_content  wslu-style-1 wslu-share-box-shaped wslu-fill-colored wslu-none wslu-share-horizontal wslu-theme-font-no wslu-main_content\">\n\n\t\t\n        <ul>\n\t\t\t        <\/ul>\n    <\/div> \n","protected":false},"excerpt":{"rendered":"<p>Following a recent upgrade, Xorg was apparently also updated to version&nbsp;xorg-x11-server-Xorg-1.6.1.901-1.fc11.i586 which unfortunately didn&#39;t play nicely with version xorg-x11-drv-ati-6.12.2-14.fc11.i586 .&nbsp; After a brief investigation, the combination resulted in this error: &nbsp;\/usr\/lib\/xorg\/modules\/drivers\/\/radeon_drv.so: undefined symbol: DRIOpenDRMMaster Ultimately, this had the following effect: No GUI (System never got as far as showing any graphics let alone KDE, Gnome [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"footnotes":""},"categories":[3],"tags":[178,249,242,248,235,187,250,243,245,255,240,116,244,251,253,238,256,252,254,236,239,241,237,246,247,80],"class_list":["post-1323","post","type-post","status-publish","format-standard","hentry","category-unix-linux-admin-stuff","tag-ati","tag-catalyst","tag-desktop","tag-displaymanager","tag-driopendrmmaster","tag-drivers","tag-fglrx","tag-gdm","tag-gdm-binary","tag-gdmdisplay-display-lasted","tag-gnome","tag-kde","tag-kdm","tag-kernel-2629","tag-prefdm","tag-radeon","tag-seconds","tag-startx","tag-support","tag-undefined-symbol","tag-update","tag-x11","tag-xorg","tag-xorg0log","tag-xorgconf","tag-yum-update"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/microdevsys.com\/wp\/wp-json\/wp\/v2\/posts\/1323","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/microdevsys.com\/wp\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/microdevsys.com\/wp\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/microdevsys.com\/wp\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/microdevsys.com\/wp\/wp-json\/wp\/v2\/comments?post=1323"}],"version-history":[{"count":0,"href":"https:\/\/microdevsys.com\/wp\/wp-json\/wp\/v2\/posts\/1323\/revisions"}],"wp:attachment":[{"href":"https:\/\/microdevsys.com\/wp\/wp-json\/wp\/v2\/media?parent=1323"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/microdevsys.com\/wp\/wp-json\/wp\/v2\/categories?post=1323"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/microdevsys.com\/wp\/wp-json\/wp\/v2\/tags?post=1323"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}