<div dir="ltr"><div><div><div><div><div><div><div>For lazy people (yes I know some are trying to hide themselves at the back near the window ;) <a href="http://www.linuxquestions.org/questions/linux-general-1/ctrl-alt-f1-%3D-black-blank-screen-385376/#post4593178">http://www.linuxquestions.org/questions/linux-general-1/ctrl-alt-f1-%3D-black-blank-screen-385376/#post4593178</a><br>
<br></div>If I read carefully enough this should come from grub configuration.<br><br></div>The main issue is Ubuntu is designed to be user friendly and would stupidly erase grub configuration at each kernel update. This Linux distribution has to be avoid in my own opinion... But, you have it, you won't change today : )<br>
<br></div>So the point will be to change your system configuration to avoid grub setup to erase your modification.<br><br></div>For me, the simplest way to proceed is to:<br></div>1) create a working grub.cfg (the one you are using right now)<br>
</div>2) change it for it give you access to your console<br></div>3) change it for it uses a link to your current kernel and initrd rather than using the kernel / initrd file name.<br><div><div><div><div>4) modify grub2 setup scripts for they are not working any more (removing the executable bit one them for they can't be run when apt* would upgrade your grub or your kernel<br>
</div><div>5) run grub-install or grub2-install specifying your harddrive name:<br></div><div>grub2-install /dev/sda<br></div><div><br></div><div>1) your system boots -> you have the grub.cfg working<br></div><div>2) according to the link in the beginning of this mail, change one of your grub entries (the one you use each is a good candidate, you could copy it, changing its name, to keep your working config and create a new one for testing) by modifying the "linux" line, then the initrd line:<br>
</div><div>3) this needs two actions:<br></div><div>a - cd /boot<br></div><div>ln -s kernel-version-you-want-to-use vmlinuz<br></div><div>ls -l /boot/vmlinuz<br></div><div>/boot/vmlinuz -> kernel-version-you-want-to-use<br>
</div><div>ln -s initrd.img-X.Y.Z-blablabla initrd.img<br></div><div><br></div><div><br></div><div>On my own system that gives me that:<br>ls -l /boot/vmlinuz<br>lrwxrwxrwx 1 root root 44 23 févr. 13:44 /boot/vmlinuz -> kernel-genkernel-x86_64-3.12.2-gentoo-virtio<br>
</div><div><br></div><div>b - back into /boot/grub/grub.cfg, still modifying the "linux" line, replace /boot/kernel-version by /boot/vmlinuz<br><br></div><div>One some of my Debian there, initially a grub entry is:<br>
<b>menuentry</b> 'Debian GNU/Linux, with Linux 3.2.0-4-amd64' --class debian --class gnu-linux --class gnu --class os {<br> load_video<br> insmod gzio<br> insmod part_msdos<br> insmod ext2<br>
set root='(hd0,msdos1)'<br> search --no-floppy --fs-uuid --set=root 52a22bfb-be26-48eb-8345-7d813b8424b8<br> echo 'Loading Linux 3.2.0-4-amd64 ...'<br> <b>linux</b> <b>/vmlinuz-3.2.0-4-amd64</b> root=/dev/mapper/rootvg-rootlv ro quiet<br>
echo 'Loading initial ramdisk ...'<br> <b>initrd /initrd.img-3.2.0-4-amd64</b><br>}<br><br></div><div>Would become:<br><b>menuentry</b> 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu --class os {<br>
load_video<br> insmod gzio<br> insmod part_msdos<br> insmod ext2<br> set root='(hd0,msdos1)'<br> search --no-floppy --fs-uuid --set=root 52a22bfb-be26-48eb-8345-7d813b8424b8<br>
echo 'Loading Linux 3.2.0-4-amd64 ...'<br> <b>linux</b> <b>/vmlinuz</b> root=/dev/mapper/rootvg-rootlv ro quiet<br> echo 'Loading initial ramdisk ...'<br> <b>initrd</b> <b>/initrd.img</b><br>
}<br><br></div><div>Notes:<br>- /vmlinuz is used rather than /boot/vmlinuz because I use separated /boot partition.<br></div><div>- I changed the menuentry name to remove kernel version, this entry as no more reason to be changed again.<br>
<br></div><div>4) removing auto updte of grub.cfg:<br></div><div>When grub-setup is launched it runs scripts in /etc/grub.d to create your new grub.cfg. It do that because the scripts inside that directory are executable. To avoid grub erasing your config, just do that:<br>
</div><div>chmod -x /etc/grub.d/* <br></div><div><br></div><div>So now you have:<br></div><div>created the two links in /boot<br></div><div>modified your /boot/grub/grub.cfg<br></div><div>removed the executable bit on all files in /etc/grub.d<br>
<br></div><div>you can launch "grub-install /dev/sda" if /dev/sda is really your disk : )<br></div><div><br></div></div></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-06-05 13:38 GMT+02:00 Mathias Dufresne <span dir="ltr"><<a href="mailto:mathias.dufresne@gmail.com" target="_blank">mathias.dufresne@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div>Hi,<br><br></div>You should look into Xorg's configuration rather than into Openbox's one. Openbox is, for me, responsible of window management into X but not to switch outside of X.<br>
<br></div>As for Ctrl + Alt + Backspace, which is configured into keyboard section of Xorg files.<br><br></div>Perhaps you should have a look there: <a href="http://ubuntuforums.org/showthread.php?t=1471825" target="_blank">http://ubuntuforums.org/showthread.php?t=1471825</a><br>
<br></div>The title of this thread is: "<span>no ctrl alt f1 ubuntu 10.04" and is tagged as resolved.<br><br></span></div><span>Cheers,</span><br><div><div><div><div><br></div><div>mathias<br></div><div><div><br>
</div></div></div></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-06-05 8:12 GMT+02:00 Mindaugas B <span dir="ltr"><<a href="mailto:minde.b@gmail.com" target="_blank">minde.b@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr"><div><div><div><div>It looks at the end that it is related to startx not with openbox related.<br>
<br><br>
video card :<br>00:02.0 VGA compatible controller: Intel Corporation Device 0be2 (rev 0b)<br><br>consoles running:<br>
<i> 805 tty4 Ss+ 0:00 /sbin/getty -8 38400 tty4<br> 809 tty5 Ss+ 0:00 /sbin/getty -8 38400 tty5<br>
814 tty2 Ss+ 0:00 /sbin/getty -8 38400 tty2<br> 816 tty3 Ss+ 0:00 /sbin/getty -8 38400 tty3<br> 818 tty6 Ss+ 0:00 /sbin/getty -8 38400 tty6<br> 1019 tty1 Ss+ 0:00 /sbin/getty -8 38400 tty1</i><br>
<br></div>no /etc/inittab file<br></div>but i have default runlevel <code>/etc/init/rc-sysinit.conf</code>:<br>..<br><font size="1"><i>env DEFAULT_RUNLEVEL=2</i></font><br>..<br><br>also i use config in these files, this launch startx on tty8:<br>
/etc/init/tty8.conf<br><br>contents of file tty8.conf:<br><i># tty8 - getty<br>#<br># This service maintains a getty on tty8 from the point the system is<br># started until it is shut down again.<br><br>start on stopped rc RUNLEVEL=[2345]<br>
stop on runlevel [!2345]<br><br>respawn<br>exec /bin/openvt -fwc8 -- /usr/bin/sudo -H -u user /usr/bin/startx</i><br><br><br></div>in user profile folder there is .Xsession witch launch openbox</div><br><i>#!/bin/sh<br># OPEN BOX STARTUP<br>
#<br># start idesk, icons on desktop<br>/usr/bin/idesk &<br><br>openbox</i><br><br><div><div><div><div><div><br><div class="gmail_extra"><br></div></div></div></div></div></div></div>
<br></div></div><div class="">_______________________________________________<br>
openbox mailing list<br>
<a href="mailto:openbox@icculus.org" target="_blank">openbox@icculus.org</a><br>
<a href="http://icculus.org/mailman/listinfo/openbox" target="_blank">http://icculus.org/mailman/listinfo/openbox</a><br>
<br></div></blockquote></div><br></div>
</blockquote></div><br></div>