Remember to add your self to vboxusers - as su
groupmod --add-user <login_name> vboxusers
Hi Carl,
Thanks mate, it worked well.
Best,
David
God news indeed.
I cant operate VirtualBox today.
Here is terminal output
david@linux-zsof:~> VirtualBox
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (2.6.31.12-0.2-desktop) or it failed to
load. Please recompile the kernel module and install it by
sudo /etc/init.d/vboxdrv setup
You will not be able to start VMs until this problem is fixed.WARNING: The compilation of the vboxdrv.ko kernel module failed during the
installation for some reason. Starting a VM will not be possible.
Please consult the User Manual for build instructions.
/usr/bin/VirtualBox: line 72: /usr/lib/virtualbox/VirtualBox: Permission denied
/usr/bin/VirtualBox: line 72: exec: /usr/lib/virtualbox/VirtualBox: cannot execute: Permission denied
david@linux-zsof:~> sudo /etc/init.d/vboxdrv setup
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:
#1) Respect the privacy of others. #2) Think before you type. #3) With great power comes great responsibility.
root’s password:
Sorry, try again.
root’s password:
WARNING: All config files need .conf: /etc/modprobe.d/xen_pvdrivers, it will be ignored in a future release.
Stopping VirtualBox kernel module done
Recompiling VirtualBox kernel module failed
(Look at /var/log/vbox-install.log to find out what went wrong)
You have mail in /var/spool/mail/david
david@linux-zsof:~> virtualbox
If ‘virtualbox’ is not a typo you can use command-not-found to lookup the package that contains it, like this:
cnf virtualbox
david@linux-zsof:~> sudo /etc/init.d/vboxdrv setup
WARNING: All config files need .conf: /etc/modprobe.d/xen_pvdrivers, it will be ignored in a future release.
Stopping VirtualBox kernel module done
Recompiling VirtualBox kernel module failed
(Look at /var/log/vbox-install.log to find out what went wrong)
david@linux-zsof:~> /var/log/vbox-install.log
bash: /var/log/vbox-install.log: Permission denied
The error log is here -
/usr/share/virtualbox/src/vboxdrv/build_in_tmp: line 94: make: command not found
OKay, got it show up by installing GCC and Automake. Now it wants Kernel Driver. Working on it atm.
Not working after driver install
linux-zsof:/home/david # sudo /etc/init.d/vboxdrv setup
WARNING: All config files need .conf: /etc/modprobe.d/xen_pvdrivers, it will be ignored in a future release.
Stopping VirtualBox kernel module done
Recompiling VirtualBox kernel module failed
(Look at /var/log/vbox-install.log to find out what went wrong)
What does /var/log/vbox-install.log say? Did you do a kernel update/change. xen is mentioned. The xen kernel is not needed and may mess things up.
Now I get new error
Makefile:159: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop.
Please post result of
uname -a
rpm --query --all '*kernel*'
As su -
cat /boot/grub/menu.lst
The windows 7 Grub menu entry is gone. Should I start a seperate thread for it or we can continue that here.
david@linux-zsof:~> uname -a
Linux linux-zsof 2.6.31.12-0.2-default #1 SMP 2010-03-16 21:25:39 +0100 x86_64 x86_64 x86_64 GNU/Linux
david@linux-zsof:~> rpm --query --all ‘kernel’
kernel-xen-2.6.31.12-0.2.1.x86_64
linux-kernel-headers-2.6.31-3.4.noarch
kernel-default-2.6.31.12-0.2.1.x86_64
kernel-desktop-2.6.31.12-0.2.1.x86_64
linux-zsof:/home/david # cat /boot/grub/menu.lst
Modified by YaST2. Last modification on Sun Jul 4 19:42:56 SGT 2010
THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader
Configure custom boot parameters for updated kernels in /etc/sysconfig/bootloader
default 0
timeout 8
##YaST - generic_mbr
gfxmenu (hd0,5)/boot/message
##YaST - activate###Don’t change this comment - YaST2 identifier: Original name: linux###
title SUSE LINUX
root (hd0,5)
kernel /boot/vmlinuz root=/dev/disk/by-id/ata-ST3320418AS_9VMD0YPT-part6 repair=1 resume=/dev/disk/by-id/ata-ST3320418AS_9VMD0YPT-part5 splash=silent quiet showopts vga=0x317
initrd /boot/initrd###Don’t change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe – SUSE LINUX
root (hd0,5)
kernel /boot/vmlinuz root=/dev/disk/by-id/ata-ST3320418AS_9VMD0YPT-part6 showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 x11failsafe vga=0x317
initrd /boot/initrd
You can add an entry for windows manually.
If you post result of this I can advise
fdisk -l
I wonder if there is a menu.lst.old ? And if it contains the windows info? And perhaps the original boot code for openSUSE.
It seems you are booting to kernel-default
But you have 3 kernels installed: desktop, default, xen (WHY)??
Remove the other 2 and just use kernel-default (You’ll have fun doing that)
You have to play hard ball with Yast - probably using the Taboo/Do Not Install to force stuff away.
==================
Notice you boot code is generic: kernel /boot/vmlinuz
Mine is like this: kernel /boot/vmlinuz-2.6.34-12-desktop
How did you manage this?
Carl:
Here is fdisk output -
linux-zsof:/home/david # fdisk -l
Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0007d4a8
Device Boot Start End Blocks Id System
/dev/sda1 1 5222 41945683+ 7 HPFS/NTFS
/dev/sda2 5223 34997 239167687+ 7 HPFS/NTFS
/dev/sda3 * 34998 38913 31455270 f W95 Ext’d (LBA)
/dev/sda5 34998 35519 4192933+ 82 Linux swap / Solaris
/dev/sda6 35520 36823 10474348+ 83 Linux
/dev/sda7 36824 38913 16787893+ 83 Linux
sda1 is bootable with windows7 in it. sda2 is storage.
This time around I decided not to mess with YaST and take its suggested/recommended installs seriously. I have managed to keep software intact. This morning when I booted first it took me to a terminal prompt saying no displays available. I did ‘sudo halt’ and used ‘repair installed os’ option from install dvd, later it fixed all the stuff but it deleted windows7 entry. I can browse windows from filesystem. Well when I am done fixing this, I will just remove unwanted kernels from YaST.
YaST had a bad day yesterday.
It should look like this then
###Don't change this comment - YaST2 identifier: Original name: windows###
title Windows7
rootnoverify (hd0,0)
chainloader +1
What file to edit
When I do “vi /boot/grub/menu.lst”, but I cant edit, tried “gksudo gedit /boot/grub/menu.lst” but that doesnt show anything.
# Modified by YaST2. Last modification on Sun Jul 4 20:15:26 SGT 2010
# THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader
# Configure custom boot parameters for updated kernels in /etc/sysconfig/bootloader
default 0
timeout 8
##YaST - generic_mbr
gfxmenu (hd0,5)/boot/message
##YaST - activate
###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE LINUX
root (hd0,5)
kernel /boot/vmlinuz root=/dev/disk/by-id/ata-ST3320418AS_9VMD0YPT-part6 repair=1 resume=/dev/disk/by-id/ata-ST3320418AS_9VMD0YPT-part5 splash=silent quiet showopts vga=0x317
initrd /boot/initrd
###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- SUSE LINUX
root (hd0,5)
@
"/boot/grub/menu.lst" 21L, 960C 10,0-1 Top
OK, did it from “Yast - System - Bootloader”. Let me restart and see if it works.
In first reboot, i got kernel panic, had to use repair option from dvd and fix it. Let me now restart and get in windows to see how it works.
I cant see Grub at the time of start, the machine boots windows directly. tried repair tools but no luck.
Re-Install Grub Quickly with Parted Magic
That will work unless you totally borked the menu.lst
But you can edit the file at /boot/grub/menu.lst from Parted Magic with the text editor there and put back what you had:
# Modified by YaST2. Last modification on Sun Jul 4 19:42:56 SGT 2010
# THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader
# Configure custom boot parameters for updated kernels in /etc/sysconfig/bootloader
default 0
timeout 8
##YaST - generic_mbr
gfxmenu (hd0,5)/boot/message
##YaST - activate
###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE LINUX
root (hd0,5)
kernel /boot/vmlinuz root=/dev/disk/by-id/ata-ST3320418AS_9VMD0YPT-part6 repair=1 resume=/dev/disk/by-id/ata-ST3320418AS_9VMD0YPT-part5 splash=silent quiet showopts vga=0x317
initrd /boot/initrd
###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- SUSE LINUX
root (hd0,5)
kernel /boot/vmlinuz root=/dev/disk/by-id/ata-ST3320418AS_9VMD0YPT-part6 showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 x11failsafe vga=0x317
initrd /boot/initrd
###Don't change this comment - YaST2 identifier: Original name: windows###
title Windows7
rootnoverify (hd0,0)
chainloader +1
Guide to parted
Using Parted Magic an Introduction
Just mount the root partition to navigate to the menu.lst
check it
if it’s OK just re-install grub with the guide above
other wise edit the file and then re-install grub
unmount partitions before re-installing grub
Make sure the boot flag is on sda3
Carl,
I am in windows atm, cant boot suse at all. I will use repair option in dvd and try this out. I hope pm is there in repair kit. Imo, it has got to do with setting a boot flag, will have a look with Buntu live cd or systemrescue cd.