similar to: Centos 5.4 with Rage

Hi all, Just found out that the Poweredge R300 cant even load the CentOS 5.2 64bit installer. Had to revert to Ubuntu. Seems its a driver problem. Pity, but does this kind of case apply to many other servers? --- OSCC MAMPU MyMeeting Version 2.0 Release http://knowledge.oscc.org.my/solution-areas/application/mymeeting

I have just installed Centos 6.5 on a Asus motherboard with an embedded ATI Rage XL controller (and with no room to install a more capable graphics card) and it is infuriatingly slow, running in VESA mode. Unfortunately this card is not supported "out-of-the-box" by centos 6.5 and after Googling I have not found that the kmod-fglrx-legacy driver from elrepo would work either according

I'm playing the newly released game Rage by id software on my Arch Linux 64 bit box and runs quite nicely. I was beginning to wonder if it would be possible to ply the game with controller/gamepad? What is possible/easiest to set up with wine? I have an ps3 controller could that do the job or would it be easier to get an xbox 360 controller or a completely different gamepad? Any suggestions

I have installed Centos 6.2 on: 1) Tyan S2892 with ATI on board Rage XL graphics ( Centos x86_64 version), 8GB memory, 3ware Raid array 2) Supermicro Dual Xeon Single core, old machine, with ATI onboard Rage XL graphics (Centos i386 version), 12GB memory, 3ware Raid array Both machines exhibit the same error. While trying to select a screen saver (clock or blank screen) the application seg

Hello, all I apologize for all these questions. But I have so many running through my head for this. What brand of server is a good one to use for running an asterisk box? I did an install the other day on a Compaq Proliant ML370 G2 / Debian Sarge and it is currently working great. But HP/Compaq costs bukooo bucks. I have heard Super Micro is what alot of you are using. Any problem running

I noticed in 4.92 there is no disabling selinux at install. It is now a firstboot option which then requires a reboot. Is there anyway to disable selinux at the boot install prompt so after the firstboot screens it wont reboot again? I presently install with "linux askmethod" so I can select NFS install. Thanks, Jerry

Hi, I'm running compiz on a r300, dual-screens setup. The r300 driver has a GL_MAX_TEXTURE_SIZE = 2048 limit, and it shows: the nautilus backdrop window doesn't cover both screens. Is there a mean to let compiz sort of "split" the nautilus window to stay within the 2048 limit on each screen ? Thanks, Xav PS: please Cc me, I'm not suscribed

anyone has installed Rage? the appdb entry doesn't work for me. Thanks

Currently we install a systemd service named firstboot.service and a SysV service named virt-sysprep-firstboot. On systems where systemd is the init system and runs with the SysV compatibility, the different names make systemd handle them as different services, and thus trying to run the firstboot script runner twice. Rename both the systemd service and the SysV one to guestfs-firstboot: the new

Currently firstboot would only work on redhat-based images. Handle redhat-based, suse-based and debian guests, error out in case of an unknown distro. Update firstboot.sh: - make sure scripts exists and can be executed - add LSB header to avoid insserv warnings later on - run script only if called with "start" Update functions, pass only required options. Signed-off-by: Olaf Hering

Currently we install a systemd service named firstboot.service and a SysV service named virt-sysprep-firstboot. On systems where systemd is the init system and runs with the SysV compatibility, the different names make systemd handle them as different services, and thus trying to run the firstboot script runner twice. Rename the systemd service to virt-sysprep-firstboot as well: other than being

On Thu, Nov 21, 2019 at 12:04:18PM +0100, Tomáš Golembiovský wrote: > Instead of running firstboot scripts during early boot schedule a task > delayed for 1-2 minute. > > During the first boot, after virt-v2v conversion, Windows installs the > drivers injected by virit-v2v. When this installation is finished > Windows enforces some kind of internal reboot. This unfortunately

Hi, We have a new 24-core Dell PowerEdge R905 server with 128GB's RAM. The 64 bits version of Fedora 12 lists the correct amount of 128GB, CentOS only finds 32GB (and so does Scientific Linux). I would much prefer to use CentOS (most of the software we use is specifically designed for CentOS). Does anyone know what is causing this/how to fix it? Many Thanks, Diederick -------------- next

When firstboot is used from virt-v2v the scripts, if not fast enough, can get killed by Windows. After windows installs virtio drivers injected by virt-v2v it performs some internall reboot, stopping all the running services and killing any running firstboot script. This is problem mostly for MSI installs (like qemu-ga that was added recently) that can take several seconds to finish. This change

If a script does not finish, hangs, etc, it would be executed again at the next boot, since the injected firstboot.sh helper removes it only after it finished. Since firstboot.sh only runs executable files, then remove the executable attributes before running it, so it will not run again. Also, remove any file found in the scripts subdirectory, be it just run or run in a previous boot. This

This patchset attempts to address a number of shortcomings in the firstboot infrastructure I came across while working with v2v conversion of various Windows VMs. Roman Kagan (4): firstboot: consolidate line ending conversion firstboot: enhance firstboot driver script for Windows firstboot: make script naming descriptive convert_windows: split firstboot into steps

If a script does not finish, hangs, etc, it would be executed again at the next boot, since the injected firstboot.sh helper removes it only after it finished. Before executing a script, move it to another internal subdirectory (scripts-done) and execute it from there, so it is not run again by firstboot.sh. The downside is that now scripts are executed only once at all, so if a script fails it

We are enforcing #!/bin/bash at the beginning of the scripts and bash is installed in every guest. Regards, Peter 2017. márc. 14. dátummal, 16:14 időpontban Richard W.M. Jones <rjones@redhat.com> írta: >> On Tue, Mar 14, 2017 at 03:45:34PM +0200, Keresztes Péter-Zoltán wrote: >> I am running libguestfs version 1.34.2 > > As far as I know, this version should contain

I am running the stock libguestfs on latest Ubuntu 16.04 (1:1.32.2-4ubuntu2). My guests are also Ubuntu 16.04. I am running virt-sysprep with --firstboot-command 'dpkg-reconfigure openssh-server'. This works 90% of the time, but occasionally when a new guest first starts it can't find the script: ~# cat virt-sysprep-firstboot.log /etc/init.d/virt-sysprep-firstboot start Scripts

On Wednesday, 3 August 2016 16:39:46 CEST Richard W.M. Jones wrote: > On Wed, Aug 03, 2016 at 05:35:14PM +0200, Pino Toscano wrote: > > Currently we install a systemd service named firstboot.service and a > > SysV service named virt-sysprep-firstboot. On systems where systemd is > > the init system and runs with the SysV compatibility, the different > > names make