[EMAIL PROTECTED] wrote: > This should really be a follow-up to another message I posted, which hasn't arrived back yet. > > On Tue, Jul 04, 2006 at 10:21:37PM -0700, Willie Wonka wrote: > > > > [EMAIL PROTECTED] wrote: > > > On Mon, Jul 03, 2006 at 09:30:15PM -0400, [EMAIL PROTECTED] wrote: > > > > After upgrading my etch to xorg7.0 and making everything up-to-date > > > > yesterday, (except for a few package aptitude didn't want to > > > > update) things went fine for a reboot or two. But today when > > > > I was out of the room, the screen went black. When I pressed shift, > > > > though it remained black except for about ten or so characters of > > > > gibberish in the top left of the screen. Pressing ctl-alt-F* didn't > > > > help, didn't even get me to a text console. Remote login via ssh > > > > worked, so I used the ssh connexion to enter a reboot command. > > > > > > > > Rebooting worked fine until it was time to start gdm. Again the > > > > screen went black and everything becane unresponsive. > > > > > > > > Now I have a dual boot system, sarge or etch. Sarge works fine. > > > > So I figure I eliminated hardware problems. > > > > > > > > After a while I managed to get it into a state where I could use > > > > a text console after the crash, and examined some log files. (I used an > > > > old 2.6.11 kernel I had lying around to accomplish this -- but I > > > > suspect I was just lucky. Each reboot failed in a similar, but slightly > > > > different way, so random chance seems to be a factor) > > > > > > > > The following messages in xorg.1.log seem relevant: > > > > > > > > (II) RADEON(0): [drm] added 1 reserved context for kernel > > > > (WW) RADEON(0): [agp] AGP not available > > > > (EE) RADEON(0): [agp] AGP failed to initialize. Disabling the DRI. > > > > (II) RADEON(0): [agp] You may want to make sure the agpgart kernel module > > > > is loaded before the radeon kernel module. > > > > (**) RADEON(0): RADEONDRICloseScreen > > > > > > > > Very good. I imagine X *might* have trouble reaching the video card > > > > if the driver for the AGP slot is missing. Now how *do* I "make sure > > > > the agpgart kernel module is loaded before the radeon kernel module."? > > > > And why isn't it already happening? Or is the problem somewhere else? > > > > Where should I look? After the crash (i.e., now), lsmod tells me that > > > > agpgart *is* loaded. > > > >
I would seriously consider following up on this lead; try; ~$ dmesg | tail ~$ dmesg | grep -i agp (try some other keywords in place of 'agp' too) **** [ Remember I'm running Sarge/Xfree86, not Etch/Xorg, so YMMV ] **** View the many other log files in '/var/log'. Check if in your /home you have too many ~/.gdm or ~/.gnome entries -- I have in mine /.gnome, /.gnome2, /.gnome2_private and I don't use GDM, I use KDM...and that may be the rub... Check out the /etc/init.d/gdm file contents 'less /etc/init.d/gdm' --------------- Here's some of my *KDM* script contents [...] # To start kdm even if it is not the default display manager, change # HEED_DEFAULT_DISPLAY_MANAGER to "false." HEED_DEFAULT_DISPLAY_MANAGER=true DEFAULT_DISPLAY_MANAGER_FILE=/etc/X11/default-display-manager PATH=/bin:/usr/bin:/sbin:/usr/sbin DAEMON=/usr/bin/kdm PIDFILE=/var/run/kdm.pid UPGRADEFILE=/var/run/kdm.upgrade test -x $DAEMON || exit 0 [...] -------------- ---------------------------------- Compare that with my *GDM* contents # To start gdm even if it is not the default display manager, change # HEED_DEFAULT_DISPLAY_MANAGER to "false." HEED_DEFAULT_DISPLAY_MANAGER=true DEFAULT_DISPLAY_MANAGER_FILE=/etc/X11/default-display-manager PATH=/sbin:/bin:/usr/sbin:/usr/bin DAEMON=/usr/bin/gdm PIDFILE=/var/run/gdm.pid UPGRADEFILE=/var/run/gdm.upgrade ------------------------------------ They are basically the SAME...both HEED the default display. I bring this up because i suspect perhaps *sometimes* KDM may be trying to load?? I've run into issues like that in the past. When you do ctrl+alt+F1 do you see any errors about GDM or KDM ? When I had issues; I would see comments like this "GDM not starting, not the default display manager" Now, after using 'sudo rcconf' to reconfigure my Startup Services/apps, in which I unticked GDM altogether, that message is gone! All i see now is "Starting K Display Manager: kdm." as the last entry/service started. I had to d/l and install RCCONF Do this to find out more about it; $ apt-cache show rcconf > > > Well, managed to install and boot to a new kernel -- 2.6.15. > > > With the new kernel, have booted successfully to X and gdm twice in a row. > > > Might be fixed, or am I just lucky? The problem was intermittent, after all. > > > > > > -- hendrik > > > > > > > Have you seen; > > http://wiki.debian.org/Xorg69To7 > > > > Regards > > > > Actually, the fix they have for gdm not starting is applicable if the symlink /usr/X11R6/bin->../bin > hasn't been established by x11-common. Mine is there. I see... hmmmm **** [ Remember I'm running Sarge/Xfree86, not Etch/Xorg, so YMMV ] **** Here's the entirety of my /etc/X11/default-display-manager file ----------------- /usr/bin/kdm ----------------- Perhaps you have some (Xfree86) remnants leftover in any of the above mentioned DIRs ? Have you --purged whatever you don't use and 'removed' ?? Purging will get rid of the Orig Config files (too) for that '<packagename>'. Are you also using KDM ?? if not, use sudo rcconf to first stop the service during boot and then perhaps; ~$ sudo apt-get remove kdm ~$ sudo apt-get --purge kdm Obviously 'sudo' is only needed if you're not root who knows? you might be able to combine it into one command using; ~$ sudo apt-get remove kdm && --purge kdm but I'm not sure of that at all - and it doesn't take much more wqork to run both commands separately. Also note; On my KDM login screen, I have Sub-menus which allow choosing different WMs, and the choice "kdm" has *default* written next to it. Do you use Gnome Control Center ?? In K Control Center, I configured mine to my $Username to "Auto Login" (No passwd required)-- it boot's directly into KDE, so I hardly ever even see the kdm login screen. One has to enter the Root passwd to gain "Admin" privileges to alter these settings. Have you done that with yours? Regards __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
