by a4b96384 on Wed Sep 14, 2011 4:13 pm
I've got the same issue as the initial and other posts - login appears to get started but then black screen and back to the login screen again.
I downloaded and burned yesterday (using InfraRecorder in WinXP). I didn't see any mention of it being an RC version. Did the install to HD from the DVD. I'm running this on a 10 yr old Sony Vaio - sorry, can't give you too much detail about it because it's no longer functional. It's a PCG-R505JL, with I'm pretty sure 384 MB RAM. Mint had about 3.5 GB for root partition and about 1 GB for home on which to do the install. df reports 400+ MB free on / after install.
I flipped over to tty1 (Ctrl-Alt-F1) and was able to login there using the ID/PW I'd created. I then went back to tty8 and tried loggin in again on the gdm side. I then went back to tty1 to see if I could catch the login with w - there were two users for a brief period, then back to one, so it sounded like the login was successful but there's something troubling the gdm.
When I did that again, some output appeared on the screen that looked like partial error messages. I checked dmesg - the end of it had error messages including the stuff I'd seen on screen. I did this a few more times - each time I try to log in, the same string of messages is appended to dmesg (with the new time counts of course).
Here is the output from dmesg - I've replaced the time counts at the start of the lines with # for clarity and in case there's word wrap:
# [drm:drm_reclaim_locked_buffers] *ERROR* reclaim_buffers_locked() deadlock. Please rework this
# driver to use reclaim_buffers_idlelocked() instead.
# I will go on reclaiming the buffers anyway.
# [drm] DMA Cleanup
# mtrr: no MTRR for f8000000,3000000 found
# mtrr: base(0xf8000000) is not aligned on a size(0x12c000) boundary
# [drm] Using v1.4 init.
# mtrr: base(0xf8000000) is not aligned on a size(0x3000000) boundary
# [drm:drm_reclaim_locked_buffers] *ERROR* reclaim_buffers_locked() deadlock. Please rework this
# driver to use reclaim_buffers_idlelocked() instead.
# I will go on reclaiming the buffers anyway.
(PS - typed this because the machine is hooped - have checked for typos carefully - pretty sure it's precise).
These lines repeat every time a login attempt is made. Using sudo, I see a couple of the lines from the above also appear in /var/log/messages. In /var/log/auth.log there are gdm-session-worker sessions - the session open and close a second apart.
I saw the comments on MD5 sums and burning. It seems kind of unlikely to me. There are multiple users reporting the same problem. Burning problems or bad MD5 sums would give random imperfections in the DVD, wouldn't they? And didn't one check the sums and they were fine? I wouldn't have thought there'd be multiple reports of the same issue b/c of burning/MD5 problems - possible I guess, if there was a bad image on a mirror, say, but would't be the first thing I'd think of. (IMHO - just an observation - not a complaint).
Hope this helps . I need the machine working though, so am going to install a different distro - maybe one of the Unity Linux respins (the Unity distro, not Ubuntu's thing).