On 29/12/09 16:45, Bogdan Cristea wrote:

On Tuesday 29 December 2009 07:22:52 Basil Chupin wrote:

...

I just had a look at the instructions at

http://en.opensuse.org/VirtualBox_Installation

but they refer to earlier versions of openSUSE.

Are the instructions shown at this URL still relevant to 11.2 (and its kernel)?

I have a set of instructions produced by Alexei Eremenko back on 18-05-2007 - and the same question also applies to these: are they out-of-date or still current?

Glad to get any advice on this, thanks.

BC

http://vavai.net/2009/12/21/installing-virtualbox-3-1-2-on-opensuse-11-2/

Thank you for this. I have saved the instructions and will read them shortly. BC -- If you don't succeed you run the risk of failure. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 30/12/09 12:17, Masim "Vavai" Sugianto wrote:

Hi BC,

On Tue, Dec 29, 2009 at 5:53 PM, Basil Chupin wrote:

...

...

...

http://vavai.net/2009/12/21/installing-virtualbox-3-1-2-on-opensuse-11-2/

Thank you for this. I have saved the instructions and will read them shortly.

Have you try the above tutorial ? On the above tutorial I'm using VirtualBox 3.1.2 PUEL on openSUSE 11.2 32 bit and overall seems to works like a charm.

I had a quick read of it. I don't think it goes far enough - only deals with actually installing VB, but then it stops. BC -- If you don't succeed you run the risk of failure. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 30/12/09 15:39, Masim "Vavai" Sugianto wrote:

Hi BC, On Wed, Dec 30, 2009 at 11:33 AM, Basil Chupin wrote:

...

...

I had a quick read of it. I don't think it goes far enough - only deals with actually installing VB, but then it stops.

So, what do you want ? VirtualBox 3.1.2 will automatically compiling the kernel module so you do not need to run /etc/init.d/vboxdrv setup. 3.1.2 also automatically supporting bridging network and USB, so, what's any task should be added ? Do you need any feature that doesn't enable by default ?

Ah, I see - you are the author of that tutorial. It didn't "click" at the time. One installs VB for a reason, which is to be able to run another system within it. The most likely OS people would want to install is Windows. The tutorial stops short of explaining how to install another OS. But up to this point I consider the tutorial to be excellent. BC -- If you don't succeed you run the risk of failure. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 30/12/09 20:55, Clayton wrote:

...

I had a quick read of it. I don't think it goes far enough - only deals with actually installing VB, but then it stops.

That's what the very comprehensive Virtual Box documentation is for. Have you taken a look at the VBox manual? There's little sense in openSUSE people rewriting dic on how to instal guest OSes when VBox provides that info already.

C.

I did read it a couple of years ago, or so. I couldn't understand some of it if I recall correctly. Perhaps it is time to revisit it. BC -- If you don't succeed you run the risk of failure. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tue, Dec 29, 2009 at 06:58, Rajko M. wrote:

On Monday 28 December 2009 23:22:52 Basil Chupin wrote:

...

I just had a look at the instructions at

http://en.opensuse.org/VirtualBox_Installation

but they refer to earlier versions of openSUSE.

Are the instructions shown at this URL still relevant to 11.2 (and its kernel)?

It is all the same for 11.2 as it was for 10.3, but you are right, it needs update.

It is? I'd say that for at least the downloaded RPM it's not the same... I've installed it this way: 1. Download the VirtualBox RPM from the virtualbox.org website 2. zypper install <vbox RPM> 3. Add my user to the vboxusers group 4. Log out/log in That's it. USB works.. everything works. No messing with fstab C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 29 Dec 2009, at 11:45, Basil Chupin wrote:

...

...

...

It is? I'd say that for at least the downloaded RPM it's not the same...

I've installed it this way: 1. Download the VirtualBox RPM from the virtualbox.org website 2. zypper install <vbox RPM> 3. Add my user to the vboxusers group 4. Log out/log in

That's it. USB works.. everything works. No messing with fstab

C.

Aaah...the beauty of a democracy and the freedom of choice.... :-)

Several answers...all wonderful.

But.....using "zypper install <vbox RPM>" will only install the openSUSE version of VirtualBox and not the SUN version...

Ummm no. I said download the version from virtualbox.org (aka the Sun version) and install THAT VERSION with zypper using zypper install <vbox RPM>. This will install the downloaded RPM not the OSE version (as long as you run zypper from the same directory as the downloaded RPM or point zypper at the RPM). Then add vboxuser group to your user (easy with YaST)... Log out and back in. That's all you have to do... Zypper will pull in the dependencies for the downloaded RPM and install them. Vbox just works then... Including USB. No messing about with fstab settings. It's that easy. There are no other steps than what I outlined. The hard way is for the OSE build and used to be necessary for the Sun version (but that's been fixed in the Sun version) C.

And before you can install the SUN version of VB you need to first install pam-devel :-) .

Fortunately I found a copy of a post by David Rankin, dated 8 Feb '08, which gave details on how to install VB. I am now half-way thru installing VB (have to now go and find the XP installation disc.. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

...

...

and install THAT VERSION with zypper using zypper install <vbox RPM>. This will install the downloaded RPM not the OSE version (as long as you run zypper from the same directory as the downloaded RPM or point zypper at the RPM).

Yep, tried to do this- both while in the directory where the SUN version was located and then also pointing to that directory. Regrettably this did not work for me. Must have been doing something terribly wrong :- ( .

Or it's me being a numpty.... I'm trying to remember the command while on a train somewhere in Germany. Try just zypper <vbxox RPM>. i.e. without install and zypper should install the local RPM.... I think.. Old age is creeping up on me about 50 years early. :-P C.

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Maybe it is a silly question, but... I did not mention it in the earlier thread about Virtualbox, that I also tried to install the SUN version by clicking on the file in Dolphin (or Konqueror). Yast came up to install the package. I thought it would install THAT rpm, and not the one (ose) in the repo. Is this right? Installation was not successful, because of missing pam-devel and also failed to compile some kernel module. By the way, gcc, gcc++ and make should already be also prent on the system. Oszkoa -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tue, 29 Dec 2009 19:08:03 Clayton wrote:

On Tue, Dec 29, 2009 at 06:58, Rajko M. wrote:

...

On Monday 28 December 2009 23:22:52 Basil Chupin wrote:

...

I just had a look at the instructions at

http://en.opensuse.org/VirtualBox_Installation

but they refer to earlier versions of openSUSE.

Are the instructions shown at this URL still relevant to 11.2 (and its kernel)?

It is all the same for 11.2 as it was for 10.3, but you are right, it needs update.

It is? I'd say that for at least the downloaded RPM it's not the same...

I've installed it this way: 1. Download the VirtualBox RPM from the virtualbox.org website 2. zypper install <vbox RPM> 3. Add my user to the vboxusers group 4. Log out/log in

That's it. USB works.. everything works. No messing with fstab

C.

I didn't use the RPM version - I downloaded the generic installer, ran the script (as root), it compiled the modules to suit my running (custom) kernel and worked without any further intervention. Every 7 days or so it checks for an update and if it finds one it prompts me to download and install it (which is done exactly the same way). OK, so zypper/Yast don't know about it but they also don't try to update it :-). If I update the kernel, I just have to re-run a script that is provided (can't remember the exact one, but the "failed to load module" message at boot tells me anyway) to recompile the kernel modules against the new kernel. All in all, I found that to be the most painless way to do it. -- =================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au =================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 30/12/09 03:48, Ken Schneider - openSUSE wrote:

On 12/29/2009 09:17 AM, Rodney Baker pecked at the keyboard and wrote:

...

On Tue, 29 Dec 2009 19:08:03 Clayton wrote:

...

On Tue, Dec 29, 2009 at 06:58, Rajko M. wrote:

...

On Monday 28 December 2009 23:22:52 Basil Chupin wrote:

...

I just had a look at the instructions at

http://en.opensuse.org/VirtualBox_Installation

but they refer to earlier versions of openSUSE.

Are the instructions shown at this URL still relevant to 11.2 (and its kernel)?

It is all the same for 11.2 as it was for 10.3, but you are right, it needs update.

It is? I'd say that for at least the downloaded RPM it's not the same...

I've installed it this way: 1. Download the VirtualBox RPM from the virtualbox.org website 2. zypper install <vbox RPM> 3. Add my user to the vboxusers group 4. Log out/log in

That's it. USB works.. everything works. No messing with fstab

C.

I didn't use the RPM version - I downloaded the generic installer, ran the script (as root), it compiled the modules to suit my running (custom) kernel and worked without any further intervention.

Every 7 days or so it checks for an update and if it finds one it prompts me to download and install it (which is done exactly the same way).

OK, so zypper/Yast don't know about it but they also don't try to update it :-). If I update the kernel, I just have to re-run a script that is provided (can't remember the exact one, but the "failed to load module" message at boot tells me anyway) to recompile the kernel modules against the new kernel.

All in all, I found that to be the most painless way to do it.

Or you can add the SUN site repo, give a higher priority and install that way. Then when SUN releases a newer version you can install it but simply using zypper up

An excellent suggestion! One new entry in the repos coming up :-) BC -- If you don't succeed you run the risk of failure. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tuesday 29 December 2009 04:58:44 Basil Chupin wrote:

Yes.

But it is a pity in a way that instructions like this cannot be made "universal" in the sense that they would apply now as well as to any future versions of an application.

Conversely of course......... :-)

It is a wiki, so when you finish installation, you can write your experience in section for 11.2. I was always wondering what makes people diligent writers here, but there is no way to make them go over to the wiki and write digest of discussion that solved some problem? It would be really helpful to have clean copy of problem solutions, without quotes, derailed discussions and other noise that is always present on mail lists, but you can't expect that small wiki team can do everything, or that "someone" will some from his hideout and do that. -- Regards Rajko, openSUSE Wiki Team: http://en.opensuse.org/Wiki_Team People of openSUSE: http://en.opensuse.org/People_of_openSUSE/About -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 30/12/09 04:19, Michael Roberts wrote:

2009/12/29 Basil Chupin :

...

I just had a look at the instructions at

http://en.opensuse.org/VirtualBox_Installation

but they refer to earlier versions of openSUSE.

Are the instructions shown at this URL still relevant to 11.2 (and its kernel)?

I have a set of instructions produced by Alexei Eremenko back on 18-05-2007 - and the same question also applies to these: are they out-of-date or still current?

By coincidence I have just started reviewing the VirtualBox wiki pages as part of this review: http://en.opensuse.org/Transition_Guidelines#Step_1_:_Articles_review

and will take into account the replies to this thread.

At this point I'll take the opportunity to thank everyone for providing me with most useful advice on how to go about getting VB up and running. I am glad to read that you are reviewing the wiki pages re VB. May I suggest that you take into account Clayton's, Ken Schneider's comment about using *full* name of the VB RPM from SUN, and also the instructions given by David Rankin in his post in this ML dated 8 Feb 2008 titled, "A Quick Start - VirtualBox Howto". One of my personal peeves about VB and around which I cannot wrap my brain is the ability to access from oS the files sitting in any of the partitions created in the Windows virtual disc (.VirtualBox) by apps. installed in VB. If that could be made more understandable then this would be great. Right now, I have VB installed as well as XP. However, I still haven't got something correct because I am not able to have XP display in the full resolution (1920x1080) of my monitor - and which I was able to do, if I recall correctly, a few years ago. BC -- If you don't succeed you run the risk of failure. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 30/12/09 23:55, Ken Schneider - openSUSE wrote:

On 12/29/2009 11:52 PM, Basil Chupin pecked at the keyboard and wrote:

...

On 30/12/09 04:19, Michael Roberts wrote:

<snip>

...

At this point I'll take the opportunity to thank everyone for providing me with most useful advice on how to go about getting VB up and running.

I am glad to read that you are reviewing the wiki pages re VB. May I suggest that you take into account Clayton's, Ken Schneider's comment about using *full* name of the VB RPM from SUN, and also the instructions given by David Rankin in his post in this ML dated 8 Feb 2008 titled, "A Quick Start - VirtualBox Howto".

One of my personal peeves about VB and around which I cannot wrap my brain is the ability to access from oS the files sitting in any of the partitions created in the Windows virtual disc (.VirtualBox) by apps. installed in VB. If that could be made more understandable then this would be great.

Right now, I have VB installed as well as XP. However, I still haven't got something correct because I am not able to have XP display in the full resolution (1920x1080) of my monitor - and which I was able to do, if I recall correctly, a few years ago.

BC

You need to read the help provided by VB, it is excellent.

I will give you a hint: tools go through the pull downs of the running VM

I think the 'instructions' state to restart VB after installing Additions.iso but this did not give me the full screen. However, on booting up the system this morning I *did* have my 1920x1080 screen in VB which, I guess, means that restarting/rebooting oS is what needs to be done to have the new parameters kick-in. All seems to be well at this point in time -- but I am *not* looking forward to installing all the bits and pieces to give me additional desktops, hide the task bar, disc defragmenter, security s/ware..... :-( A question, Ken, if you know the answer which would save me finding out the hard way.... I have a Canon scanner which is not supported by Linux - but, of course, XP does. In the latest version of VB is the USB support still totally reliant on openSUSE or can this version now access USB devices if the driver is installed in XP under VB? BC -- If you don't succeed you run the risk of failure. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 31/12/09 16:27, Masim "Vavai" Sugianto wrote:

Hi BC, On Thu, Dec 31, 2009 at 11:40 AM, Basil Chupin wrote:

...

On 30/12/09 23:55, Ken Schneider - openSUSE wrote:

A question, Ken, if you know the answer which would save me finding out the hard way....

I have a Canon scanner which is not supported by Linux - but, of course, XP does.

In the latest version of VB is the USB support still totally reliant on openSUSE or can this version now access USB devices if the driver is installed in XP under VB?

Sorry, the question asked to Ken Schneider but just a sharing experience,

I haven't try guest XP with scanner on VB but I get the USB Epson printer works on XP guest without installing any driver in openSUSE. Just activating the USB support on VB, installing the XP driver and overall seems to works correctly.

Thanks for this, but the real question is: is your Epson printer recognised 'naturally' under openSUSE even without you having to deliberately install any drivers. For example, my HP printer and my Lexmark laser printer are recognised by openSUSE and I don't have to go out of my way to install any additional drivers simply because openSUSE already knows about them and installs the correct drivers. Canon stuff is different :-( . In earlier versions of VB the USB support/access was totally under the control of the host system. If the host could not handle the device (like my Canon scanner) then the guest (XP) could not have access to it. BC -- If you don't succeed you run the risk of failure. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 31/12/09 17:42, Masim "Vavai" Sugianto wrote:

On Thu, Dec 31, 2009 at 12:40 PM, Basil Chupin wrote:

...

Thanks for this, but the real question is: is your Epson printer recognised 'naturally' under openSUSE even without you having to deliberately install any drivers. For example, my HP printer and my Lexmark laser printer are recognised by openSUSE and I don't have to go out of my way to install any additional drivers simply because openSUSE already knows about them and installs the correct drivers.

Yes, I'm using the Epson LX-300 with USB port. openSUSE recognized it but I must add a driver to make it usable. Without installing new driver, I could not printing anyway.

Please, configure your mail client so that it does not send your response to both the mail list and also as a private message to me. I read this mail list and so do not need to also see the same message in my private mail. BC -- If you don't succeed you run the risk of failure. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 12/31/2009 12:08 AM, Masim "Vavai" Sugianto wrote:

Sorry, nothing wrong with my mail (I'm using Google Apps with Zimbra configure in my side). I just use reply all because I'm to lazy to move/manually put opensuse@opensuse.org at a to address. openSUSE list has a different setting than another list. openSUSE list put a personal email as a reply to address by default and I'm not really comfortable with it, because sometimes people doesn't like to get a personal email which should be sent to the list.

By the way, Thunderbird 3.0 now has a reply-to-list button. There are a lot of other improvements in this version of TB too. I particularly like the new "Smart-Folders" option, where it groups all the inboxes from multiple mailing lists into one super inbox. Yet it easily shows individual inboxes all grouped together. At the moment I've got seven different imap mail accounts and keeping tabs of them was a pain with the old TB. Now, it's a snap! Lightening still isn't ported last time I checked, but I can live without that for a while. Regards, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 12/30/2009 11:40 PM, Basil Chupin pecked at the keyboard and wrote:

On 30/12/09 23:55, Ken Schneider - openSUSE wrote:

...

On 12/29/2009 11:52 PM, Basil Chupin pecked at the keyboard and wrote:

...

On 30/12/09 04:19, Michael Roberts wrote:

<snip>

...

At this point I'll take the opportunity to thank everyone for providing me with most useful advice on how to go about getting VB up and running.

I am glad to read that you are reviewing the wiki pages re VB. May I suggest that you take into account Clayton's, Ken Schneider's comment about using *full* name of the VB RPM from SUN, and also the instructions given by David Rankin in his post in this ML dated 8 Feb 2008 titled, "A Quick Start - VirtualBox Howto".

One of my personal peeves about VB and around which I cannot wrap my brain is the ability to access from oS the files sitting in any of the partitions created in the Windows virtual disc (.VirtualBox) by apps. installed in VB. If that could be made more understandable then this would be great.

Right now, I have VB installed as well as XP. However, I still haven't got something correct because I am not able to have XP display in the full resolution (1920x1080) of my monitor - and which I was able to do, if I recall correctly, a few years ago.

BC

You need to read the help provided by VB, it is excellent.

I will give you a hint: tools go through the pull downs of the running VM

I think the 'instructions' state to restart VB after installing Additions.iso but this did not give me the full screen.

However, on booting up the system this morning I *did* have my 1920x1080 screen in VB which, I guess, means that restarting/rebooting oS is what needs to be done to have the new parameters kick-in.

All seems to be well at this point in time -- but I am *not* looking forward to installing all the bits and pieces to give me additional desktops, hide the task bar, disc defragmenter, security s/ware..... :-(

A question, Ken, if you know the answer which would save me finding out the hard way....

I have a Canon scanner which is not supported by Linux - but, of course, XP does.

In the latest version of VB is the USB support still totally reliant on openSUSE or can this version now access USB devices if the driver is installed in XP under VB?

BC

Sorry for the late reply, been away on a camping trip over the holiday weekend. I have not had any problem with any USB device as VB grabs the device from the host OS and passes it on to the guest OS. Best thing to do is just try it. Pass that I can't help much as I don't have any Canon devices here. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 01/04/2010 02:29 AM, Ken Schneider - openSUSE wrote:

.

...

I have a Canon scanner which is not supported by Linux - but, of course, XP does.

In the latest version of VB is the USB support still totally reliant on openSUSE or can this version now access USB devices if the driver is installed in XP under VB?

BC

Sorry for the late reply, been away on a camping trip over the holiday weekend.

I have not had any problem with any USB device as VB grabs the device from the host OS and passes it on to the guest OS. Best thing to do is just try it. Pass that I can't help much as I don't have any Canon devices here.

I have a usb HP scanner, also not supported in linux and it works without problems in XP as the guest OS on oS 11.0. I'm using the latest Sun version of VB. Gustav. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 01/04/2010 04:44 AM, Basil Chupin pecked at the keyboard and wrote:

On 04/01/10 19:16, Gustav Degreef wrote:

...

On 01/04/2010 02:29 AM, Ken Schneider - openSUSE wrote:

...

.

...

I have a Canon scanner which is not supported by Linux - but, of course, XP does.

In the latest version of VB is the USB support still totally reliant on openSUSE or can this version now access USB devices if the driver is installed in XP under VB?

BC

Sorry for the late reply, been away on a camping trip over the holiday weekend.

I have not had any problem with any USB device as VB grabs the device from the host OS and passes it on to the guest OS. Best thing to do is just try it. Pass that I can't help much as I don't have any Canon devices here.

I have a usb HP scanner, also not supported in linux and it works without problems in XP as the guest OS on oS 11.0. I'm using the latest Sun version of VB. Gustav.

Thank you. I shall now have to rethink things and see if my Canon scanner will work under XP as guest.

BC

One other thing, with the VM running, at the top there is a pulldown labeled Devices, look under the USB list and make sure it is checked otherwise the guest OS will not see it. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

"On 11:52:22 pm Basil Chupin said"

At this point I'll take the opportunity to thank everyone for providing me with most useful advice on how to go about getting VB up and running.

I am glad to read that you are reviewing the wiki pages re VB. May I suggest that you take into account Clayton's, Ken Schneider's comment about using *full* name of the VB RPM from SUN, and also the instructions given by David Rankin in his post in this ML dated 8 Feb 2008 titled, "A Quick Start - VirtualBox Howto".

One of my personal peeves about VB and around which I cannot wrap my brain is the ability to access from oS the files sitting in any of the partitions created in the Windows virtual disc (.VirtualBox) by apps. installed in VB. If that could be made more understandable then this would be great.

Right now, I have VB installed as well as XP. However, I still haven't got something correct because I am not able to have XP display in the full resolution (1920x1080) of my monitor - and which I was able to do, if I recall correctly, a few years ago.

BC

--

Ok, I have been following this thread for a bit and decided to try an install. It looks like it failed because it did not d/l the correct kernel headers or any at all and I am not sure why. Tnx, Mike Hopefully this info will help with a suggestion on how to procede. I am running opensuse 11.1 on amd 64. uname -a Linux MIKE-C521 2.6.27.39-0.2-default #1 SMP 2009-11-23 12:57:38 +0100 x86_64 x86_64 x86_64 GNU/Linux install info: The following NEW packages are going to be installed: VirtualBox-3.1-3.1.2_56127_openSUSE111-1.x86_64 (Plain RPM files cache, Sun Microsystems, Inc.) glibc-devel-2.9-2.12.1.x86_64 (openSUSE-11.1-Update, openSUSE) linux-kernel-headers-2.6.27-2.28.noarch (openSUSE 11.1-0, openSUSE) pam-devel-1.0.2-13.4.x86_64 (openSUSE 11.1-0, openSUSE) Overall download size: 44.7 M. After the operation, additional 125.1 M will be used. Continue? [YES/no]: yes committing Retrieving package linux-kernel-headers-2.6.27-2.28.noarch (1/4), 668.0 K (2.4 M unpacked) Installing: linux-kernel-headers-2.6.27-2.28 [done] Additional rpm output: post linux-kernel-headers-2.6.27-2.28 /var/tmp/rpm-tmp.97697 1 `usr/include/asm' -> `asm-x86' Retrieving package glibc-devel-2.9-2.12.1.x86_64 (2/4), 4.6 M (29.7 M unpacked) Retrieving: glibc-devel-2.9-2.12.1.x86_64.rpm [done (12.5 K/s)] Installing: glibc-devel-2.9-2.12.1 [done] Retrieving package pam-devel-1.0.2-13.4.x86_64 (3/4), 62.0 K (86.0 K unpacked) Installing: pam-devel-1.0.2-13.4 [done] Retrieving package VirtualBox-3.1-3.1.2_56127_openSUSE111-1.x86_64 (4/4), 39.4 M (92.9 M unpacked) Installing: VirtualBox-3.1-3.1.2_56127_openSUSE111-1 [done] Additional rpm output: warning: /var/tmp/TmpDir.II7o3y/VirtualBox-3.1-3.1.2_56127_openSUSE111-1.x86_64.rpm: Header V4 DSA signature: NOKEY, key ID 6dfbcbae Creating group 'vboxusers'. VM users must be member of that group! No precompiled module for this kernel found -- trying to build one. Messages emitted during module compilation will be logged to /var/log/vbox-install.log. Compilation of the kernel module FAILED! VirtualBox will not start until this problem is fixed. Please consult /var/log/vbox-install.log to find out why the kernel module does not compile. Most probably the kernel sources are not found. Install them and execute /etc/init.d/vboxdrv setup as root. committingCommitResult 4 (errors 0, remaining 0, srcremaining 0) MIKE-C521:/home/ka1ifq/Documents/FF_DL # more /var/log/vbox-install.log ** Compiling vboxdrv Makefile:179: *** Error: unable to find the include directory for your current Linux kernel. Specify KERN_INCL=<directory> and run Make a ain. Stop. -- 2.6.27.39-0.2-default GNU/Linux -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org