Resize2fs fails; kvm-qemu; ext4; lvm2 [SOLVED]

the problem:
* a virtual machine (varch3) is created with kvm-qemu where /dev/sda on the guest is logical volume /dev/vg0/varch3 on the host with the following command:
$ sudo /usr/local/kvm/bin/qemu-system-x86_64 /dev/vg0/varch3 -m 1024 -smp 2 -net nic,macaddr=00:16:3e:73:86:97 -net tap -nographic
* here are the partitions on the guest (primary partitions):
$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 7.3G 1.4G 5.5G 21% /
none 501M 0 501M 0% /dev/shm
/dev/sda1 38M 9.7M 27M 27% /boot
/dev/sda4 2.4G 104M 2.2G 5% /home
* /home on varch3 is too small so /dev/vg0/varch3 is extended from 10G to 210G:
$ sudo lvextend -L +200G /dev/vg0/varch3 /dev/sdc2
$ sudo lvscan
ACTIVE '/dev/vg0/varch3' [210.00 GB] contiguous
* it is expected that the guest will see a /dev/sda that is now 210G instead of 10G
* after logging into the guest, i unmounted /dev/sda4 and attempted to increase the size of this primary partition with resize2fs:
$ sudo e2fsck /dev/sda4
e2fsck 1.41.5 (23-Apr-2009)
/dev/sda4: clean, 191/155648 files, 36355/622518 blocks
$ sudo resize2fs -f /dev/sda4 200G
resize2fs 1.41.5 (23-Apr-2009)
Resizing the filesystem on /dev/sda4 to 52428800 (4k) blocks.
resize2fs: Invalid argument while trying to resize /dev/sda4
* in an attempt to understand this cryptic result i ran cfdisk on /dev/sda4:
cfdisk (util-linux-ng 2.14.2)
Disk Drive: /dev/sda
Size: 225485783040 bytes, 225.4 GB
Heads: 255 Sectors per Track: 63 Cylinders: 27413
Name Flags Part Type FS Type [Label] Size (MB)
sda1 Boot, NC Primary Linux ext2 41.13
sda2 Primary Linux swap / Solaris 271.44
sda3 Primary Linux ext3 7871.60
sda4 Primary Linux ext3 2549.84
Unusable 214745.62
the questions:
* how is it possible that the space on /dev/sda4 is known AND unusable?
* what do i need to do to get a larger /home on varch3?
TIA
Last edited by poopship21 (2009-08-03 21:15:53)

for some reason, the MBR can hold up to four primary partitions and zero extended partitions or up to three primary partitions and an arbitrary number of extended partitions. i dont know exactly why this is the case but i can accept it and go on with my life. intuitively, the space which is not part of the existing primary partitions could be made into another partition since cfdisk must be able to see the beginning and ending blocks, and therefore every block in between in order to know the size of the unused space. i guess that the four-partition maximum is just a convention which reflects the limitations of legacy systems.
Last edited by poopship21 (2009-08-03 21:15:41)

Similar Messages

Arch thinks sound is working, but it's not (Guest in KVM / QEMU)

Hi chaps,
I have an Archlinux virtual machine running the very latest Arch-goodness.
It's running inside Kvm-Qemu on a Ubuntu system (don't hate me plz!! )
I have setup the sound to emulate an Intel AC97:
<sound model='ac97'/>
And when I load the Arch system and do a lsmod, it has loaded all the correct modules all by it's clever self:
The machine starts with every muted (possibly an indication that something is wrong?), but using
alsamixer
I turn everything up.
But when I try something like
aplay /usr/share/sounds/alsa/Front_Center.wav
I get no sound (and no errors).
I'm at a bit of a loss tbh; I have read and re-read the Alsa guide on your Wiki, but unfortunately it did not resolve the issue.
Would really appreciate some help please guys!
Thanks,
tommed

$ qemu -soundhw ?
Valid sound card names (comma separated):
pcspk PC speaker
sb16 Creative Sound Blaster 16
ac97 Intel 82801AA AC97 Audio
es1370 ENSONIQ AudioPCI ES1370
Using KVM as the launcher (the
<sound .../>
snippet was in the KVM config file.
Thanks for the snippet about Arch starting with mute.. good to know!

[CLOSED] install windows 7 in kvm/qemu

Hey all,
running arch 64, and just installed kvm and qemu by following the wiki:
https://wiki.archlinux.org/index.php/Qe … ws_version
https://wiki.archlinux.org/index.php/Kvm
when I try to install windows 7 32bit:
qemu-system-x86_64 -hda win7-32 -m 3072 -cdrom win7cd.iso -boot d -vga std
The installer starts, and then right after I select my language, and click the "Install Now" button, windows appears to hang. I can move the mouse around the virtualized window, but it just sits there. I let it be for over and hour and nothing.
Has anyone installed windows 7 32bit in KVM/qemu?
Thanx in advance.
Last edited by nixIT (2012-02-24 19:37:51)

jelly wrote:It worked for me ~ 1 year ago with qemu-kvm. You could ask around in #kvm in freenode or try to use virtio disks ( you need to find the driver for it on the internet for windows) which will boost I/O performance. The default -hda is ide and terrible slow when installing windows..
Thanx, that's what I've been reading up on, but am a bit confused on how to set up the virtio disks. I have the driver pulled from the fedora forums. how can I set it up with virtio disks? I've seen a post, but it looks like it's talking about setting it up on an already installed windows client.

Kvm: qemu with option "-enable-kvm" or kvm-84 from AUR?

whats the difference between the two? Which one should be preferred?
thanks!

Yeah, my bad. The patches to qemu would come from upstream KVM, like they did before. Avi Kivity, not Tobias. My mistake there.
And yeah, I think some of those distinctions are us using different semantics. I'd call the qemu implementation that Avi maintains a fork -- but that is different to me than, as you worded it, kvm being a fork of qemu. When saying "kvm" and referring to a chunk of code, not what I'll call for this conversation's sake "the kvm project," has always referred to the kvm module -- the kernel code, again hence the name. Back when the userspace code was just a set of patches to qemu, this confusion was rarer. (Even after the kvm project started maintaining their own version of the code, they also maintained the qemu patch set to apply to the qemu project -- their version was just qemu, pre-patched. Avi discusses that philosophy of modifying the original code as little as possible in his most recent blog a few months ago.) The kvm userspace code is -- again, by Avi's own description -- qemu and libkvm. (http://www.linux-kvm.org/page/Code - "The kvm userspace code (libkvm and qemu) is available through a git tree.") kvm-the-project does maintain a prepatched qemu, but that doesn't make it kvm's code -- particularly when kvm's intent all along was to have their patches accepted by qemu, which they now have. So while you can say that kvm-the-project has within it a build of qemu -- and if you wanted, you could even call it a fork, though the maintainer declines to use the term -- qemu is not kvm.
I'd also add that though the gray area there exists, from a future-discussion perspective it does make things a lot clearer if we refer to kvm the module, the "pure" build of qemu, and kvm's qemu build (or qemu-kvm) as separate.
And by extension, no, kvm-userspace has not reached 10.0.0. There's a reason that the kvm userspace code just has build numbers. Its version number is 85. It would make a lot of sense to say that the kvm-maintained patches were modified and applied to qemu upstream to make qemu 10.0.0, but the post-10 stability patches for kvm were applied independently to qemu and qemu-kvm -- qemu-kvm basically getting just kvm-related stability patches, which are submitted upstream to qemu (and thus qemu-kvm moving up in build number), and qemu using the qemu-kvm patches as well as patches relating to other parts of the system.
Getting back to the meat of the question, it is important to note that the kvm we're getting from the arch package is NOT the kvm that you would get from building the download file. You called it clean, and you're absolutely right -- it's *too* clean. Download the KVM package from sourceforge, build, and do a make -n install; you get:
make -C kernel DESTDIR="" install
make -C libkvm DESTDIR="" install
make -C qemu DESTDIR="" install
Which makes sense if you read their docs -- the KVM build, as per KVM, come as a (independent of the kernel) set of modules and a QEMU build to go with those modules, just like it was before it was accepted by linux-kernel. (You could probably have noticed that kernel modules were being build when you run make, but there was so much stuff in there that I thought it easier to cut/paste the install phase for clarity.) The Arch PKGBUILD, however, just compiles qemu-kvm and its necessary libraries:
for dir in libkvm user qemu extboot; do
cd ${srcdir}/kvm-${pkgver}/${dir}
make || return 1
done
and then hand-installs those components without the kernel modules meant to go with it. Unless the package builder knows something the KVM developer doesn't, I wouldn't go around using that qemu build with whatever KVM module version from whatever different kernel version you may have willy-nilly.
If I had the hankering to run the KVM maintained userspace stuff, I'd do what they said and run their kernel stuff too. I think a proper KVM build should do that. But that's not my call, since I'm not the extra maintainer. As it stands, for me I'd rather use the in-kernel version, which I think will get the kernel-side patches that the KVM project's kernel code gets anyway since there is so much attention on the kernel, but also has the benefit of the qemu userspace code getting bug fixes from the qemu devs themselves. It sounded to me like that was the direction kvm itself was moving. But to each their own, of course. I'd just say better to stick all the way with one or all the way with the other method, and not just start making hybrids without a much deeper knowledge of the code than I think any of us have.
Last edited by slinkygn (2009-05-04 02:11:30)

NVRM: RmInitAdapter failed! (hardware problem?) [SOLVED]

Fairly recently, an older i686 box I have cannot load X but displays the bootup info, and non-graphical login prompt just fine. The video card is an nVidia 8400GS. After googling around for several of the dmesg errors, and not finding much of relevance, I am starting to wonder if the card itself is bad. Anyone with experience is welcomed to chime in with suggestions.
I have tried:
* Moving the card to another PCI slot.
* Both the linux/nvidia and linux-lts/nvidia-lts packages.
* Chapter 8 of the nvidia README recommends several kernel bootline mods, none of which work.
Links
Complete dmesg: http://pastebin.com/J0y8yKT6
Complete /var/log/Xorg.log: http://pastebin.com/iCkq9kM5
Relevant drivers:
% pacman -Qs nvidia
local/libvdpau 0.7-1
Nvidia VDPAU library
local/nvidia 325.15-8
NVIDIA drivers for linux
local/nvidia-libgl 325.15-1
NVIDIA drivers libraries symlinks
local/nvidia-utils 325.15-1
NVIDIA drivers utilities
Interestingly, I cannot read any info from the card itself which is in stark contrast to any of the other nvidia machines to which I have access:
% cat /proc/driver/nvidia/gpus/0/information
Model: GeForce 8400 GS
IRQ: 16
GPU UUID: GPU-????????-????-????-????-????????????
Video BIOS: ??.??.??.??.??
Bus Type: PCIe
DMA Size: 40 bits
DMA Mask: 0xffffffffff
Bus Location: 0000:02.00.0
Specific errors in dmesg:
[ 7.318404] nvidia: module license 'NVIDIA' taints kernel.
[ 7.318413] Disabling lock debugging due to kernel taint
[ 7.361296] vgaarb: device changed decodes: PCI:0000:02:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
[ 7.363264] [drm] Initialized nvidia-drm 0.0.0 20130102 for 0000:02:00.0 on minor 0
[ 7.363285] NVRM: loading NVIDIA UNIX x86 Kernel Module 325.15 Wed Jul 31 18:18:15 PDT 2013
[ 7.654888] input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input4
[ 8.503106] Adding 1023996k swap on /dev/sda3. Priority:-1 extents:1 across:1023996k FS
[ 9.440825] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
[ 9.779428] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
[ 10.444258] systemd-journald[93]: Received request to flush runtime journal from PID 1
[ 65.003814] nvidia 0000:02:00.0: irq 40 for MSI/MSI-X
[ 69.922053] NVRM: RmInitAdapter failed! (0x12:0x2b:1830)
[ 69.922070] NVRM: rm_init_adapter(0) failed
[ 76.328374] nvidia 0000:02:00.0: irq 40 for MSI/MSI-X
[ 80.706326] NVRM: RmInitAdapter failed! (0x12:0x2b:1830)
[ 80.706343] NVRM: rm_init_adapter(0) failed
[ 87.113316] nvidia 0000:02:00.0: irq 40 for MSI/MSI-X
[ 91.491315] NVRM: RmInitAdapter failed! (0x12:0x2b:1830)
[ 91.491332] NVRM: rm_init_adapter(0) failed
% grep EE Xorg.0.log
[ 346.147] Initializing built-in extension MIT-SCREEN-SAVER
[ 346.220] (EE) Failed to load module "nouveau" (module does not exist, 0)
[ 346.222] (EE) Failed to load module "nv" (module does not exist, 0)
[ 346.222] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 346.223] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 346.223] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 350.605] (EE) NVIDIA(0): The NVIDIA kernel module does not appear to be receiving
[ 350.605] (EE) NVIDIA(0): interrupts generated by the NVIDIA GPU at PCI:2:0:0.
[ 350.605] (EE) NVIDIA(0): Please see Chapter 8: Common Problems in the README for
[ 350.605] (EE) NVIDIA(0): additional information.
[ 350.605] (EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device!
[ 350.605] (EE) NVIDIA(0): Failing initialization of X screen 0
[ 350.606] (EE) Screen(s) found, but none have a usable configuration.
[ 350.606] (EE)
[ 350.606] (EE) no screens found(EE)
[ 350.606] (EE)
[ 350.606] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 350.606] (EE)
[ 351.125] (EE) Server terminated with error (1). Closing log file.
Last edited by graysky (2013-10-06 15:54:40)

After exhausting various options in the BIOS (acting under the belief that something was interfering with the IRQ of the card), I thought I would try installing the nvidia-304-xx driver which ended up solving the problem. As of 06-Oct-2013, the Nvidia web site advises to use the 325.xx or 319.xx driver which is flat out wrong.
In short, using the legacy 304xx driver seems to be required for the 8400GS.
% cat /proc/driver/nvidia/gpus/0/information
Model: GeForce 8400 GS
IRQ: 16
GPU UUID: GPU-7f6a5800-9dce-8f7b-a3a8-9bc018f522ef
Video BIOS: 62.98.12.00.00
Bus Type: PCIe
DMA Size: 40 bits
DMA Mask: 0xffffffffff
Bus Location: 0000:02.00.0
% pacman -Qs nvidia
local/libvdpau 0.7-1
Nvidia VDPAU library
local/nvidia-304xx 304.108-7
NVIDIA drivers for linux, 304xx legacy branch
local/nvidia-304xx-utils 304.108-1
NVIDIA drivers utilities and libraries, 304xx legacy branch
Last edited by graysky (2013-10-20 09:57:18)

Media applications fail to output sound. [SOLVED]

The issue here seems to be that for some reason or another applications such as VLC, Nightingale, clementine and amarok fail to output sound while system sounds, flash media, and notification sounds from applications such as Skype and Thunderbird continue to work. With each of the music players respectfully there seems to be an error output that amounts to not being able to connect to the sound device. As nightingale is what I currently have installed, the error output is such when I attempt to play any sort of media.
Configured audiosink audiosink-bin is not working.
I am using E17 after formerly having used KDE however I had similar problems with the initial install that were fixed after setting the default device in alsamixer.
The output of aplay -l is as follows
**** List of PLAYBACK Hardware Devices ****
card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Generic_1 [HD-Audio Generic], device 0: ALC269VB Analog [ALC269VB Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
lsmod | grep '^snd' | column -t
snd_seq_dummy 1463 0
snd_seq_oss 28970 0
snd_seq_midi_event 5660 1 snd_seq_oss
snd_seq 49946 5 snd_seq_midi_event,snd_seq_oss,snd_seq_dummy
snd_seq_device 5180 3 snd_seq,snd_seq_oss,snd_seq_dummy
snd_hda_codec_realtek 30893 1
snd_hda_codec_hdmi 29298 1
snd_hda_intel 35816 0
snd_hda_codec 145920 3 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_intel
snd_hwdep 6364 1 snd_hda_codec
snd_pcm 76860 3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
snd_page_alloc 7330 2 snd_pcm,snd_hda_intel
snd_timer 18687 2 snd_pcm,snd_seq
snd 58893 10 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_hda_codec,snd_hda_intel,snd_seq_oss,snd_seq_device
Every thing seems to be loaded correctly and speakertest -c 2 seems to be working. The problem I had last time was with flash blocking sound output from other programs, but this problem subsided after having correctly set my default with alsamixer. I began to have the problem of flash blocking other applications from outputting sound when a browser was open a couple of days ago, but this has somehow progressed to any media application failing to output sound at anytime regardless if a browser has been opened or not. I uninstalled flashplugin and now rely on the plugin packaged within chrome but the problem persists. Any suggestions? I have read the wiki on alsa and on the flash plugin and have searched around but have found nothing that addresses my problem or that I have not already implemented or tried.
EDIT: It seems that I have gotten vlc to start working again. The issue here seems to be that /etc/alsa.conf had been marked by pacman as /etc/alsa.conf.pacorig and renaming it and setting vlc to output directly to the default device instead of having set to default has gotten sound working for it again. It seems the only problem that remains and I have gotten this error is other applications and it is probably the problem behind XBMC not playing audio but the audiosink-bin is not working error is most likely the source of the additional problems. I will look into it and see if I get any reply in the meantime.
EDIT: Due to something beyond my intelligence it seems that nightingale now plays sound and can even do so with chrome and a youtube video open. I am guessing the problem lied in the gstreamer plugins and when I removed all of my orphaned dependencies that may have been what had done it, something may have been in conflict or maybe just from the couple of reboots I have had since then. I did reinstall the plugins but there was a package that was removed called smpeg and another called sdlmixer those may have had something to do with it. So the moral of this story is to remove orphans on a regular basis, which I have been doing but just got around to today. If anyone has any input, which I doubt at this point. I will mark this as solved
Last edited by agahnim (2013-07-04 00:45:35)

I fixed it (for now, at least!)
I ran the below command:
$ cat /proc/asound/cards
0 [U0x46d0x804 ]: USB-Audio - USB Device 0x46d:0x804
USB Device 0x46d:0x804 at usb-0000:00:1a.0-1.2, high speed
1 [MID ]: HDA-Intel - HDA Intel MID
HDA Intel MID at 0xf9ff8000 irq 47
2 [NVidia ]: HDA-Intel - HDA NVidia
HDA NVidia at 0xfbd7c000 irq 17
Basically, my USB webcam, which also acts as a microphone, was being treated as my default sound card. I changed this by creating a file in /etc/modprobe.d with the following:
options snd-hda-intel index=0
Which set my real sound card as default:
$ cat /proc/asound/cards
0 [MID ]: HDA-Intel - HDA Intel MID
HDA Intel MID at 0xf9ff8000 irq 47
1 [NVidia ]: HDA-Intel - HDA NVidia
HDA NVidia at 0xfbd7c000 irq 17
2 [U0x46d0x804 ]: USB-Audio - USB Device 0x46d:0x804
USB Device 0x46d:0x804 at usb-0000:00:1a.0-1.2, high speed
The problem isn't ENTIRELY fixed. Skype's still being a bit buggy, but at least Chromium is now playing sound, including in Flash media. Strangely enough, after playing a Flash video (e.g. on YouTube), Skype's sound seems to fix itself if it's defunct.
Last edited by Archimaredes (2013-03-14 20:23:49)

RSYSLOG Dependency failed for System Logging Service [SOLVED]

when i do:
sudo systemctl start rsyslog
i get:
A dependency job for rsyslog.service failed. See 'journalctl -xn' for details.
so #journalctl -xn
jul 06 10:21:14 GA-990FXA-UD3 systemd[1]: Reloading.
jul 06 10:21:22 GA-990FXA-UD3 systemd[1]: Starting Syslog Socket.
-- Subject: Unit syslog.socket has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
-- Unit syslog.socket has begun starting up.
jul 06 10:21:22 GA-990FXA-UD3 systemd[1]: Socket service syslog.service not loaded, refusing.
jul 06 10:21:22 GA-990FXA-UD3 systemd[1]: Failed to listen on Syslog Socket.
-- Subject: Unit syslog.socket has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
-- Documentation: http://www.freedesktop.org/wiki/Softwar … e9d022f03d
-- Unit syslog.socket has failed.
-- The result is failed.
jul 06 10:21:22 GA-990FXA-UD3 systemd[1]: Dependency failed for System Logging Service.
-- Subject: Unit rsyslog.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li … temd-devel
-- Documentation: http://www.freedesktop.org/wiki/Softwar … e9d022f03d
-- Unit rsyslog.service has failed.
-- The result is dependency.
Tried official rsyslog and rsyslog-dev from aur. None of them works. I have checked with rsyslogd -d and stops at line "9430.793770992:7ff79a72d740: Checking pidfile '/var/run/rsyslogd.pid'". I also checked the config file with "rsyslog -f /etc/rsyslog.conf -n 1" and is ok.
Dunno what to do. Totally lost.
Last edited by polito (2013-07-06 23:00:16)

Thanks issue solved by this enabling rsyslog service..
# systemctl enable rsyslog.service
# journalctl -xn
-- The start-up result is done.
Mar 15 12:03:01 XXX CROND[42196]: (root) CMD (/bin/bash /usr/bin/XXX)
Mar 15 12:03:35 XXX systemd[1]: Started System Logging Service.
-- Subject: Unit rsyslog.service has finished start-up

Changed NTFS filesystem to ext4 accidentally [Solved]

OK, so due to enter happy finger and lack of sleep, I accidentally changed the filesystem of my windows partitions to ext4 and swap. >.< When I realized what I was doing, I hit the power off button pretty quick.
Is there a way to recover my data by re-writing the partition table or something? I hate to have lost all the work from a momentary lapse of judgment.
ETA: Heh, well, apparently I can mount it with ntfs-3g so I guess I hit the power off fast enough.
Last edited by canuckkat (2009-12-21 01:01:04)

The problem is indeed caused by bad blocks.
But it wasnt that easy to prove that, when ms chkdsk always fails to finish :-)
Ive used "hdd regenerator". I dont what did the program exactly do with the hdd, but after the "regeneration" ms chkdsk was finally able to check the disk and showed a lot a of bad blocks. :-(
So it seems this has nothing to do with arch linux. The timing was just a coincidence..
btw the hdd is a Samsung HD103SJ, 2 months old :S
thx for the responses ;-)

Presenter 8 64bit failing to install (Full install) SOLVED

I am trying to install the ELS. All of the applications are installing correctly except for Presenter 8.
I am running Windows 7 64bit and Office 2010 Plus 64bit.
I have tried both the installation package and the trial package and I receiving the same error. Anyone else have this issue?
Tech support has been less than helpful.
Exit Code: 6
Please see specific errors and warnings below for troubleshooting. For example, ERROR: DW030, DW050 ... WARNING: DF035 ...
-------------------------------------- Summary --------------------------------------
- 0 fatal error(s), 7 error(s), 2 warning(s)
----------- Payload: {5B1373CD-AF0F-11E1-A68F-9274728544BD} MultiSCOPackager 6.0 6.0.0.0 -----------
WARNING: DF035: CreateAlias:Icon file does not exist at C:\Program Files (x86)\Common Files\Adobe\Adobe Multi SCO Packager 6.0\MultiscoPackager.ico for icon C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Adobe eLearning Suite 6\Adobe Multi SCO Packager 6.0.lnk with target C:\Program Files (x86)\Common Files\Adobe\Adobe Multi SCO Packager 6.0\multiscopackager.exe(Seq 4810)
----------- Payload: {8C625A48-C129-11E1-B356-B79AC803160B} Adobe Presenter Video Creator (64 Bit) 8.0.0.0 -----------
ERROR: Presenter 32 bit can only be installed with Powerpoint 32 bit. Office Powerpoint 32 bit cannot be found on your system.
ERROR: DW030: Custom Action for payload {8C625A48-C129-11E1-B356-B79AC803160B} Adobe Presenter Video Creator (64 Bit) 8.0.0.0 returned error. Failing this payload.
----------- Payload: {6AF2BEEC-AF0F-11E1-A68F-8B9C341B6CA9} MultiSCOPackager 6.0 x64 6.0.0.0 -----------
WARNING: DF035: CreateAlias:Icon file does not exist at C:\Program Files\Common Files\Adobe\Adobe Multi SCO Packager 6.0 x64\MultiscoPackager.ico for icon C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Adobe eLearning Suite 6\Adobe Multi SCO Packager 6.0 x64.lnk with target C:\Program Files\Common Files\Adobe\Adobe Multi SCO Packager 6.0 x64\multiscopackager.exe(Seq 4813)
----------- Payload: {B00674D5-C129-11E1-B356-EF8CA3116C83} Adobe Presenter 8 8.0.0.0 -----------
ERROR: Presenter 32 bit can only be installed with Powerpoint 32 bit. Office Powerpoint 32 bit cannot be found on your system.
ERROR: DW030: Custom Action for payload {B00674D5-C129-11E1-B356-EF8CA3116C83} Adobe Presenter 8 8.0.0.0 returned error. Failing this payload.
ERROR: DW050: The following payload errors were found during install:
ERROR: DW050: - Adobe Presenter Video Creator (64 Bit): Install failed
ERROR: DW050: - Adobe Presenter 8_AdobePresenter8en_USLanguagePack: Install failed
ERROR: DW050: - Adobe Presenter 8: Failed due to Language Pack installation failure

After look further I figured out how to get it installed.
Even though presenter supports Powerpoint 64-bit and Windows 7 64bit (and it is also 64-bit) it seems to only install with powerpoint 2010 32bit.
1. Uninstall Office 2010 64-bit
2. Reboot
3. Install Office 2010 32-bit (Only select Powerpoint, will shorten install)
4. Reboot
5. Install presenter
6. Uninstall Office 2010 32-bit
7. Reboot
8. Install Office 2010 64 bit
After you install the 64-bit you will be able to open powerpoint and see presenter.
Thanks to jitesh swaroop @ Adobe support for spending 1:45 on the phone with me, putting me on hold for 15 mins to research the issue (before I even tell you what I am calling about), moving my mouse around, trying to convince me it's installed (contrary to it showing a failure) and then telling me you have no idea that your supervisor will call me back. He never called. Stay ever helpful!

Daemon script fails -- no log entries. [SOLVED]

Greetings.
A daemon script I got for rTorrent I got from this page, fails to start
No entries show up in dmesg or any logs in /var. I've compared the script to a couple others, but see noe obvious differences that would indicate why the script should fail.
The user and app dir is correct.
What am I missing?
Thanks.
Last edited by zfsd (2010-01-15 20:46:10)

Ah.. bullocks - seems like I missed the part about dtach. Doh!

`pacstrap -i /mnt base` fails because of linux 'leftovers' [SOLVED]

Hi,
In the process of trying to install Arch (on Acer Aspire V3, UEFI Bios, dual-boot with win 8.1) I accidentally skipped the step of manually creating a configuration file to add an entry for Arch Linux to the gummiboot manager. As a result I could not boot into arch and also failed chrooting into it. I then tried to wipe out the linux partitions (root and home) and reinstall the base system, but after wiping them out and loading again arch from the live USB and running
pacstrap -i /mnt base base-devel
I got the following error:
error: failed to commit transaction (conflicting files)
linux: mnt/boot/vmlinuz-linux exists in filesystem
I tried looking it up online but the only similar thing I could find was the Beginners guide entry saying I should run:
pacman-key --init && pacman-key --populate archlinux
I ran it but it didn't help me.
I also ran
efibootmgr -B -b <number>
to delete the linux entry but that did not help either (i.e. the linux entry is gone, but I still get that error message).
I'd like to wipe out any remaining 'leftovers' of the old linux installation and make a new one, without damaging my windows installation (which I assume should mean without wiping out the EFI partition).
How can I achieve that?
Last edited by rangel (2014-02-25 09:45:31)

I have root and home on two separate partitions. I wiped them by deleting the partitions and making new ones using cgdisk. According to this I mounted the EFI system (which is on a separate partition, which came with the win installation) on /mnt/boot using:
mkdir -p /mnt/boot
mount /dev/sdXY /mnt/boot
I assume (but not entirely sure) that I should delete whatever's left in the EFI partition, but I'd like to do it 'surgically' and not wipe it out (so as not to damage the win installation).

Pacman -Syu fails due to mime.types[SOLVED]

Hi All,
pacman -Syu results in:
error: failed to commit transaction (conflicting files)
mime-types: /etc/mime.types exists in filesystem
Is it safe to mv mime.types and retry the system upgrade?
I have Gnome and KDE installed. I currently use KDE and this is "the" KED4.1 upgrade.
Thanks.
Last edited by whot (2008-08-19 01:03:49)

pacman -Qo /etc/mime.types, showed no owner for the file.
Performed:
pacman -Rn mime-types
pacman -S mime-types
pacman -Syu
System upgrade finished with no further problems. Machine booted to KDE4.1
I've noticed a few things with KDE4.1:
DUUUUDE, where's my data?!!? (calendar data, pim data, etc.)
It seems a bit slow to respond. I don't know if this is a kernel26 upgrade issue or it's the first time
applications are being used so "things" are being set-up/configured for the first time.
All in all, smooth upgrade to KDE4.1. Thank you, devs.
Thanks for your help, fwojciec.

2.6.33, alsa fails to load/no sound[SOLVED]

Ever since the move to the 2.6.33 kernel, I'm seeing following message during boot:
Unknown hardware: "ICH" "Realtek ALC100,100P rev 38" "AC97a:414c4326" "0x1019" "0x0a14"
Hardware is initialized using a guess method
/usr/sbin/alsactl: set_control:1256: failed to obtain info for control #5 (No such file or directory)
/usr/sbin/alsactl: set_control:1256: failed to obtain info for control #6 (No such file or directory)
Sound doesn't work anymore.
On a second machine, I get a similar message, the difference being the referenced soundchip(sblive card in that case), but sound still works...
Whats up?
Last edited by hungerfish (2010-04-21 18:22:29)

Maybe those threads can help...
http://bbs.archlinux.org/viewtopic.php?id=74761
http://bbs.archlinux.org/viewtopic.php?id=89838
Last edited by dobedo (2010-04-21 11:34:12)

LibGL error: failed to load driver: i965 [Solved]

Executing some wine programs I get this messages:
libGL error: failed to load driver: i965
libGL error: Try again with LIBGL_DEBUG=verbose for more details.
Following the suggestion I get:
libGL: OpenDriver: trying /usr/lib32/xorg/modules/dri/tls/i965_dri.so
libGL: OpenDriver: trying /usr/lib32/xorg/modules/dri/i965_dri.so
libGL error: dlopen /usr/lib32/xorg/modules/dri/i965_dri.so failed (/usr/lib32/xorg/modules/dri/i965_dri.so: cannot open shared object file: No such file or directory)
libGL error: unable to load driver: i965_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: i965
libGL: OpenDriver: trying /usr/lib32/xorg/modules/dri/tls/swrast_dri.so
libGL: OpenDriver: trying /usr/lib32/xorg/modules/dri/swrast_dri.so
What is that lib32 xorg module file that appears missing?
Some informations that might be useful...
# lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
# glxinfo | grep 'dir\|^Open'
direct rendering: Yes
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Mobile
OpenGL version string: 3.0 Mesa 9.0.2
OpenGL shading language version string: 1.30
OpenGL extensions:
# uname -a
Linux macthearcher 3.7.4-1-ARCH #1 SMP PREEMPT Mon Jan 21 23:05:29 CET 2013 x86_64 GNU/Linux
Last edited by ezzetabi (2013-02-08 09:33:19)

According to wine#Graphics_Drivers it is lib32-intel-dri.

ATL development outlook plugin fails to load, how to solve

Such as the title, start the program displays COM add-ins COM add-ins loaded error, load failure
After manually loaded, plug-ins can run its normal but still Displays the above error, restart the program, plug in turn fail, we need to manually re-load

Try to add any logging mechanisms to the add-in (i.e. create a log file where you can record each step in the code). Thus, you can understand
what part of code fails to run.
Also make sure that you have all the required prerequisites installed on the problematic PC. Do you get an issue on the development PC?
Be aware, Microsoft Office applications can disable add-ins that behave unexpectedly. If an application does not load your add-in, the
application might have hard disabled or soft disabled your add-in.
Hard disabling can occur when an add-in causes the application to close unexpectedly. It might also occur on your development computer
if you stop the debugger while the Startup event
handler in your add-in is executing.
Soft disabling can occur when an add-in produces an error that does not cause the application to unexpectedly close. For example, an application
might soft disable an add-in if it throws an unhandled exception while the Startup event
handler is executing.
When you re-enable a soft-disabled add-in, the application immediately attempts to load the add-in. If the problem that initially caused
the application to soft disable the add-in has not been fixed, the application will soft disable the add-in again.
You can read more about that in the How
to: Re-enable an Add-in That Has Been Disabled article.

Resize2fs fails; kvm-qemu; ext4; lvm2 [SOLVED]

Similar Messages

Maybe you are looking for