In the process of answering your question of what was in "messages", I found the following:
Aug 8 23:44:16 miark mdkkdm[1509]: IO Error in XOpenDisplay Aug 8 23:44:16 miark mdkkdm[1361]: Display :0 cannot be opened So that proved it was a graphics problem--although I wasn't sure what. Seeing "mdkkdm" I decided to try a different dm, so I installed gdm and configured it to run. When I booted to that, about the same thing happened except it _knew_ something was up, and gave me the option to re-configure the X server via a text-gui. I tried all the nVidia drivers, but nothing worked. I then remembered that when I last used nVidia's installer, I did it while in failsafe, and failsafe uses the standard kernel. But I don't use the standard kernel--I use the patched Win4Lin kernel. So of course the nVidia drivers weren't working--they were compiled for the wrong kernel! Fine, but how the hell do I boot to init 3 or 5 using the standard kernel to fix the problem? My guess was to use a generic driver, so I tried the VESA driver, and it worked! So I rebooted the box to the Win4Lin kernel into init 5. It worked fine, so as soon as I was logged in and dropped to init 3 and re-ran nVidia's installer. Then I edited XF86Config-4 to use nvidia instead of VESA, and rebooted. It worked! So now, everything is back to normal. fschk'ing problem has been eating me all day, but it sure feels good to have sorted it out. Thanks for poking my brain with the right question to get me back to good, Stephen. Miark On 10 Aug 2003 07:02:19 +1000, Stephen Kuhn <[EMAIL PROTECTED]> wrote: > Very strange. Can't rightly think of how to get this going - and I also > thought that saslauthd was for the mailer....hmmm...what kinda shits > showing up in your dmesg or /var/log/messages after that?
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
