Am Sonntag 02 Oktober 2011, 22:34:25 schrieb J.Marcos Sitorus:
Hi Volker,
I just update VirtualBox from 4.0.8 to 4.1.2 today, and when emerge
finished I read the message that I need to manually put virtualbox
modules to /etc/conf.d/modules.
The module I said that I set to autoload on boot was
Am Freitag 30 September 2011, 18:34:48 schrieb J.Marcos Sitorus:
do you have any crashes when virtualbox was not started and no virtualbox
modules are loaded?
I was suffer another crash when I backup my data to the other partition on
LVM, when virtualbox not running
I set virtualbox modules
do you have any crashes when virtualbox was not started and no virtualbox
modules are loaded?
I was suffer another crash when I backup my data to the other partition on
LVM, when virtualbox not running
I set virtualbox modules to autoload on boot
btw the logs after a crash not after a clean boot
Am Donnerstag 29 September 2011, 09:11:09 schrieb J.Marcos Sitorus:
Hi Volker,
Thanks for the reply.
I have attach dmesg, xorg log, xsession-error, and kdm log.
So - get back to your last working versions - oh and those lvm volumes are
on
new disks?
Nope. Previously I have two separate
Am Mittwoch 28 September 2011, 09:25:56 schrieb J.Marcos Sitorus:
Hi list,
I have started using LVM about a week ago. I have created one volume group
name and two logical volume.
Both of the logical volume formatted with reiser4 file system, one volume as
my backup home and the other volume
On Wed, Sep 28, 2011 at 10:11 PM, J.Marcos Sitorus gkj...@gmail.com wrote:
You did not knock the ram loose while putting them in?
What do you mean by knock the ram loose?
Sorry, English is not my mother language.
He's asking if you may have bumped your RAM modules when connecting
new hard
6 matches
Mail list logo
