Video Cards are completely plug n play now. If you swap cards, it will know. So if you upgrade your onboard nvidia 8200 for instance to a GT260, it will know, purge the old driver and install the appropriate one for you.

Hmm, this is causing me problems with a net install on 1004. The AVWizard pops up after each and every reboot. I complete it successfully and orbiter loads, etc, etc... on reboot the AVWizard returns every time. This may be fixed by issues you mentioned earlier and the newer 20120321 build, I'll check it tonight.

With an unknown video card the AVWizard was NOT creating an xorg.conf which was causing X to crash.

I have a patch, that I will submit tonight, that adds virtualbox video driver detection to your re-worded scripts so X (avwizard, orbiter, etc) will load in virtualbox.

Have you tested virtualbox against the new installer DVD??? What's your experience with running inside of virtualbox??? Positive? Negative? OK, but with issues?

Have you tried KVM at all.

Please do not take this the wrong way JaseP, I mean no disrespect, but I do not intend to hijack this thread for a discussion of these topics. In short: No, varied, depends, sometimes, definitely. You should search the forum, there have been numerous discussions of running lmce under virtual box and there is more knowledge there than I have about the topic. Wiki probably has topics too. I'd be happy to respond to a PM or discuss this in a new topic.

To be on topic: I find lmce works best on virtualbox with the vboxvideo driver enabled rather than the default vesa driver.

I recently ran an update on my core/hybrid.. its got an onboard ati rage xl card that usually uses the mach64 kernel module... however the new installer detects the board and is trying to install the fglrx module.. it crashes.. I cant even figure out how to get it to get past this so that it finishes booting to the UI1.

Ive tried disabling my onboard video and install a PCI nVidia card... but it seems to be having issues getting it working as well

Dell Latitude C400, ui2 with alpha is a little laggy, so went to ui2 w/o alpha... about 1/2" of what should have been the far right of the display was displaced on the left hand side. Will run through AVWizard again later.. output of 'lspci -v | grep "VGA"'

Hmm, this is causing me problems with a net install on 1004. The AVWizard pops up after each and every reboot. I complete it successfully and orbiter loads, etc, etc... on reboot the AVWizard returns every time. This may be fixed by issues you mentioned earlier and the newer 20120321 build, I'll check it tonight.

Same here, I have run apt-get upgrade on the MD and the Core is already updated, I have attached the Utils.sh and 0start_avwizard as text files.

My bad, adding the virtualbox driver I missed the test for detected driver equaling current driver which prevented the AVWizard override from being set. I've caught it now. Everything is working great! I spent last night updating my 1004 builder to current svn and I'll submit the code addition I'm using to detect the virtualbox video driver.

okay.. I was adding additional items to the video detection section of Utils.sh (added new item for ATI driver 'ati' and 'mach64') on bootup, the system identifies my display as requiring the 'ati' driver (identified in yellow text)... but continues to flicker... unable to launch AVWizard.. non-stop I might add

If i put a valid xorg.conf file in /etc/X11 on bootup there is the yellow text stating the 'ati' driver IS installed... but still cannot either run AVWizard or the orbiter... however I may sometimes get a 'cannot configure X' screen (or something along those lines).

For now, I have to kill all the AVWizard and X -config programs and then launch startx to get into myth setup (my dvb cards are in my core)

Any suggestions on how to get my orbiter working again or get the AVWizard to launch correctly?

ardirtbiker: There is also a radeon r128 driver out there. I am currently looking at how xserver-xorg-video-ati figures out and applies radeon/r128/mach64 driver based on the pci info. I should have a solution soon.

# Get the device number for the parent of the given device# Returns: number or empty stringGetDeviceParent(){ local PK_Device="$1" Q=" SELECT FK_Device_ControlledVia FROM Device WHERE PK_Device='$PK_Device' " local R=$(RunSQL "$Q")

if [[ "$R" == NULL ]]; then R="" fi echo "$R"}

# Delete a device and make its children top level# Does exactly the same thing as CMD_Delete_Device in General_Info_PluginDeleteDevice(){ local PK_Device="$1" local Q R

local -a Queries Queries=( "UPDATE Device SET FK_Device_ControlledVia=NULL WHERE FK_Device_ControlledVia=$PK_Device" "DELETE FROM Device WHERE PK_Device=$PK_Device" "DELETE FROM CommandGroup_Command WHERE FK_Device=$PK_Device" "DELETE FROM Device_Command WHERE FK_Device=$PK_Device" "DELETE FROM Device_CommandGroup WHERE FK_Device=$PK_Device" "DELETE FROM Device_DeviceData WHERE FK_Device=$PK_Device" "DELETE FROM Device_DeviceGroup WHERE FK_Device=$PK_Device" "DELETE FROM Device_Device_Related WHERE FK_Device=$PK_Device OR FK_Device_Related=$PK_Device" "DELETE FROM Device_EntertainArea WHERE FK_Device=$PK_Device" "DELETE FROM Device_HouseMode WHERE FK_Device=$PK_Device" "DELETE FROM Device_Orbiter WHERE FK_Device=$PK_Device" "DELETE FROM Device_StartupScript WHERE FK_Device=$PK_Device" "DELETE FROM Device_Users WHERE FK_Device=$PK_Device" "DELETE FROM Package_Device WHERE FK_Device=$PK_Device" "DELETE FROM PaidLicense WHERE FK_Device=$PK_Device" "DELETE FROM Device_Device_Pipe WHERE FK_Device_From=$PK_Device OR FK_Device_To=$PK_Device" "DELETE FROM PaidLicense WHERE FK_Device=$PK_Device" )

for Q in "${Queries[@]}"; do RunSQL "$Q" done}

XineConfSet(){ local Setting="$1" local Value="$2" local XineConf="${3:-/etc/pluto/xine.conf}"