To eliminate misunderstandings, you must realize that xrandr only has an effect for graphical applications - for xserver clients.
xrandr has no effect on the virtual console(s).
It is possible that you have to re-enter the xrandr command after a wake-up from sleep or hibernation.
if you want everything in a lower resolution - virtual consoles and xserver clients, you could add the 'nomodeset' kernel parameter.
@DJ, concerning LFS:
Did you verify the system requirements before you started building LFS, especially the requirement that /bin/sh should be link to /bin/bash?
The build instructions assume that the Host System Requirements, including symbolic links, have been set properly:
bash is the shell in use.
sh is a symbolic link to bash.
/usr/bin/awk is a symbolic link to gawk.
/usr/bin/yacc is a symbolic link to bison or a small script that executes bison.
Just another guess at what could have made things poop out for you
How would i mount the volume group from the grml cd?
1. boot into live system from grml CD - enable lvm
2. create a mount point and mount the lvm, e.g.
sudo mount /dev/mapper/vg_debian-root /tmp/lvm1
How would I check the initramfs of the internal hd?
lsinitramfs <path-to-your-initramfs-fileon hd>
False alarm, caused by
I did the dist-upgrade and everything is still working OK for me.
I was already running kernel 3.9-1-amd64 #1 SMP Debian 3.9.8-1 - perhaps the problem occurs when upgrading from an older kernel?
Thread with caution.
Possibilities - off the top of my head:
- You did not remove package 'lvm2' by any chance?
Check /var/log/apt/history.log for packages removed
- can you mount the volume groups after having booted from live media?
- Does your initramfs contain the module lvm2?
- Check /boot/grub/grub.cfg:
- do you load the grub2 lvm module
- check the grub2 menu-itiem for the OS you want to load. Does the linux line contain the correct device path?
Can you boot into the old kernel?
Did you make a backup before upgrading your system?