[SOLVED] Luks with /arch/setup installation , fails at boot

Hi all,
So I tried to install arch on virtualbox with encrypted partitions (root /, /home/ and swap), but it fails at boot.
/dev/sda1 is /boot
/dev/sda2 is swap
/dev/sda3 is /
/dev/sda4 is /home
The root partition seems to be loading fine because it asks for my password, then the boot sequence goes on, until the /home/ (apparently) :
:: Bringing up loopback interface
:: Unlocking encrypted volumes: chome..Usage: cryptsetup [-?vyrq] (...all the options...can't copy paste with virtualbox)
/sbin/cryptsetup: Unknown action
failed [FAIL]
/dev/mapper/croot: clean, 27576/457856 files, 166316/1830898 blocks
fsck.ext4: No such file or directory while trying to open /dev/mapper/chome
Possibly non-existent device?
/dev/sda1: clean,29/24096 files, 20790/96356 blocks
[FAIL]
It seems that it tries to open /dev/mapper/chome but it's not mounted yet
In my /etc/crypttab, I added the lines :
chome /dev/sda4 none luks
cswap /dev/sda2 none luks
/etc/fstab (I didn't change anything, /arch/setup configured it that way) :
/dev/mapper/chome /home ext4 defaults 0 1
/dev/mapper/croot / ext4 defaults 0 1
/dev/mapper/cswap swap swap defaults 0 0
/dev/sda1 /boot ext2 defaults 0 1
And grub :
title Arch Linux
root (hd0,0)
kernel /vmlinuz-linux root=/dev/mapper/croot cryptdevice=/dev/sda3:croot ro
initrd /initramfs-linux.img
What I wanted to do was to have swap,root and home encrypted partitions mounted at boot, but maybe it is not possible?
I tried a lot of configurations for /etc/fstab and /etc/crypttab according to what I could find on the net but nothing worked. I read the whole tutorial https://wiki.archlinux.org/index.php/Sy … _with_LUKS but there is no config for fstab or crypttab or grub when installing with /arch/setup
Thanks for any help !
Last edited by John0000 (2012-04-12 12:50:18)

Indeed you have a point, putting password in plaintext isn't very safe.
There is a good alternative though: https://wiki.archlinux.org/index.php/Sy … _a_Keyfile
the reason why you don't have a passphrase for root in a file somewhere is that you provide this passphrase during boot-time.
Somewhere during boot you get the option to unlock you root device by typing in a passphrase... right?
ro means that the volume is mounted read only http://linux.die.net/man/8/mount

Similar Messages

SDK Setup Installation failed

Hi Guys:
We created an SDK Setup as we do for every Add-On using a separated solution to include, Customer Library, Setup & SDK Setup.
We followed all the stesp we normally do, Change Add-On Name and Executable file, Include Customer Library Conpilation Output and files needed to run Add-On
The Add-On Registration Starts, Goes thru the Setup Wizard and after the Setup Wizard finishes it waits with the hourglass until times out and shows you that SDK Setup Installation failed.
So it does not finishes the Add-On Installation.
I have Created a new VS Solution and create everything from scratch and samething happened.
Does somebody has had the same problem, and found a solution for it.
Thanks
Edel

Please post it on the SDK forum:
SAP Business One SDK
Thanks,
Gordon

[SOLVED] error with mkinitcpio during installation

Hi there
I am looking to install Arch after I broke a previous installation
I put this basic set of commands after reading the Installation Guide and I run it from in the live /root.
#!/bin/bash
loadkeys uk
mkfs -t ext4 /dev/sda7
mkfs -t ext4 /dev/sda8
mkswap -f /dev/sda6
mkdir /mnt/root
mkdir /mnt/home
mount /dev/sda7 /mnt/root
mount /dev/sda8 /mnt/home
pacstrap /mnt/root base base-devel
genfstab -p /mnt >> /mnt/root/etc/fstab
arch-chroot /mnt
ln -s /usr/share/zoneinfo/Europe/London /etc/localtime
nano /etc/locale.conf
locale-gen
mkinitcpio -p linux
passwd root
If I run this script, there's some kind of problem with mkinitcpio and /boot is empty. It worked a month or so ago - maybe it's content in the new .iso? A misplaced /mnt or /mnt/root?
Any ideas? I've never failed to install distro properly and am a bit confused!
Thanks in advance
EDIT
I changed the script to this
loadkeys uk
cfdisk
mkfs -t ext4 /dev/sda7
mkfs -t ext4 /dev/sda8
mkswap -f /dev/sda6
mkdir /mnt/root
mkdir /mnt/home
mkdir /mnt/storage
mount /dev/sda7 /mnt/root
mount /dev/sda8 /mnt/home
mount /dev/sdb1 /mnt/storage
pacstrap /mnt/root base base-devel
genfstab -p /mnt/root >> /mnt/root/etc/fstab
arch-chroot /mnt/root
ln -s /usr/share/zoneinfo/Europe/London /etc/localtime
nano /etc/locale.conf
locale-gen
mkinitcpio -p linux
passwd root
exit
will see if that helps
Last edited by Bazzaah (2013-03-18 19:26:29)

Bazzaah wrote:
Great, thanks for your help, much appreciated.
I do indeed have a functional system (basic of course) but what concerns me is that I get a not found error after mkinitcpio - the system boots so the kernel and initrd must be there...still that error message worries me a bit.
About that error, you need to post it, if you want help!
Edit: If you are running those commands in a file, make it look like this:
loadkeys uk
cfdisk
mkfs.ext4 /dev/sda7
mkfs.ext4 /dev/sda8
mkswap -f /dev/sda6
mkdir /mnt/root
mkdir /mnt/root/home
mkdir /mnt/root/storage
mount /dev/sda7 /mnt/root
mount /dev/sda8 /mnt/root/home
mount /dev/sdb1 /mnt/root/storage
pacstrap /mnt/root base base-devel
genfstab -U -p /mnt/root > /mnt/root/etc/fstab
arch-chroot /mnt/root /bin/bash -c "ln -s /usr/share/zoneinfo/Europe/London /etc/localtime"
arch-chroot /mnt/root /bin/bash -c "nano /etc/locale.conf"
arch-chroot /mnt/root /bin/bash -c "locale-gen"
arch-chroot /mnt/root /bin/bash -c "mkinitcpio -p linux"
arch-chroot /mnt/root /bin/bash -c "passwd root"
The lines with "arch-chroot /mnt/root /bin/bash -c" are needed to run those inside the chroot environment, or else they will run in your live system, instead of making changes to your created system.
Last edited by s1ln7m4s7r (2013-03-18 17:46:26)

Repeated efforts to install Acrobat XI in OSX 10.9 fail with Message "The installation failed".

Have tried to install Acrobat XI at least 6-8 times. Always get the message "The installation failed. The installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance." This, combined with the incredibly high price, is why I get frustrated with Adobe products.
Any help to get this software installed and running ASAP is greatly appreciated.

if the uninstaller has been installed, run it. then run the cleaner, http://labs.adobe.com/downloads/acrobatcleaner.html.
then restart your computer and retry installing.
if that fails, attach a screenshot of the error message.

[SOLVED] nVidia 87.76 Drivers installer fails to build kernel module

Hey,
I have a nVidia GeForce2 Integrated graphics card on my Asus A7N266 motherboard. According to the nVidia site, http://www.nvidia.com/object/IO_32667.html, the most recent driver that supports this is the 96.xx series. Yet as shown here, http://www.nvnews.net/vbulletin/showthread.php?t=87332, many people have found that the 96.xx series drivers cause graphical corruption when using a GeForce2 IGP.
Before coming to Arch, I had used Xubuntu 7.04 and managed to compile the last known working drivers, version 87.76, following the instructions here: http://kmandla.wordpress.com/2007/03/25 … 20-12-386/
That all went well but now I'm using Arch. I tried using the nvidia-96.xx driver in the repos just for testing sake but I still got the same graphical corruption.
Thus I have been trying to install the 87.76 drivers on Arch, but it always fails at the kernel module building stage. I had first applied this patch here, http://www.nvnews.net/vbulletin/showthr … ost1086669, before compling as the plain driver wont compile against recent kernels.
Here is the output from the installer:
nvidia-installer log file '/var/log/nvidia-installer.log'
creation time: Sun Aug 5 11:57:53 2007
option status:
license pre-accepted : false
update : false
force update : false
expert : false
uninstall : false
driver info : false
precompiled interfaces : true
no ncurses color : false
query latest version : false
OpenGL header files : true
no questions : false
silent : false
no recursion : false
no backup : false
kernel module only : false
sanity : false
add this kernel : false
no runlevel check : false
no network : false
no ABI note : false
no RPMs : false
no kernel module : false
force SELinux : default
force tls : (not specified)
X install prefix : (not specified)
X library install path : (not specified)
X module install path : (not specified)
OpenGL install prefix : (not specified)
OpenGL install libdir : (not specified)
utility install prefix : (not specified)
utility install libdir : (not specified)
doc install prefix : (not specified)
kernel name : (not specified)
kernel include path : (not specified)
kernel source path : (not specified)
kernel output path : (not specified)
kernel install path : (not specified)
proc mount point : /proc
ui : (not specified)
tmpdir : /tmp
ftp mirror : ftp://download.nvidia.com
RPM file list : (not specified)
Using: nvidia-installer ncurses user interface
-> License accepted.
-> No precompiled kernel interface was found to match your kernel; would you li
ke the installer to attempt to download a kernel interface for your kernel f
rom the NVIDIA ftp site (ftp://download.nvidia.com)? (Answer: Yes)
-> No matching precompiled kernel interface was found on the NVIDIA ftp site;
this means that the installer will need to compile a kernel interface for
your kernel.
-> Performing CC sanity check with CC="cc".
-> Performing CC version check with CC="cc".
-> Kernel source path: '/lib/modules/2.6.22-ARCH/build'
-> Kernel output path: '/lib/modules/2.6.22-ARCH/build'
-> Performing rivafb check.
-> Performing nvidiafb check.
-> Cleaning kernel module build directory.
executing: 'cd ./usr/src/nv; make clean'...
rm -f -f nv.o nv-vm.o os-agp.o os-interface.o os-registry.o nv-i2c.o nv.o nv
-vm.o os-agp.o os-interface.o os-registry.o nv-i2c.o nvidia.mod.o
rm -f -f build-in.o nv-linux.o *.d .*.{cmd,flags}
rm -f -f nvidia.{o,ko,mod.{o,c}} nv_compiler.h *~
rm -f -f stprof stprof.o symtab.h
rm -f -rf .tmp_versions
-> Building kernel module:
executing: 'cd ./usr/src/nv; make module SYSSRC=/lib/modules/2.6.22-ARCH/bui
ld SYSOUT=/lib/modules/2.6.22-ARCH/build'...
NVIDIA: calling KBUILD...
make CC=cc KBUILD_VERBOSE=1 -C /lib/modules/2.6.22-ARCH/build SUBDIRS=/home
/kris/Source/nVidia GLX 87.76 Driver/NVIDIA-Linux-x86-1.0-8776-pkg1/usr/src/
nv modules
test -e include/linux/autoconf.h -a -e include/config/auto.conf || ( \
echo; \
echo " ERROR: Kernel configuration is invalid."; \
echo " include/linux/autoconf.h or include/config/auto.conf are mis
sing."; \
echo " Run 'make oldconfig && make prepare' on kernel src to fix it
echo; \
/bin/false)
make[2]: *** No rule to make target `GLX'. Stop.
NVIDIA: left KBUILD.
nvidia.ko failed to build!
make[1]: *** [mdl] Error 1
make: *** [module] Error 2
-> Error.
ERROR: Unable to build the NVIDIA kernel module.
ERROR: Installation has failed. Please see the file
'/var/log/nvidia-installer.log' for details. You may find suggestions
on fixing installation problems in the README available on the Linux
driver download page at www.nvidia.com.
Any ideas as to how I can get the kernel module to build?
I am using 'kernel26 2.6.22.1-4' with the 'kernel-headers 2.6.22.1-1' from the testing repo.
Last edited by Nameless One (2007-08-10 07:08:38)

make CC=cc KBUILD_VERBOSE=1 -C /lib/modules/2.6.22-ARCH/buildSUBDIRS=/home/kris/Source/nVidia GLX 87.76 Driver/NVIDIA-Linux-x86-1.0-8776-pkg1/usr/src/
The name of the directory you placed the driver in contains spaces. That is why you get the no rule to make target GLX error.
It would be better not to circumvent pacman. I am using the following PKGBUILDs for the 8776 driver:
nvidia-8776:
pkgname=nvidia-8776
pkgver=1.0.8776
_nver=1.0-8776
_kernver='2.6.22-ARCH'
pkgrel=1
pkgdesc="NVIDIA drivers for Arch kernel."
arch=(i686 x86_64)
[ "$CARCH" = "i686" ] && ARCH=x86
[ "$CARCH" = "x86_64" ] && ARCH=x86_64
url="http://www.nvidia.com/"
depends=(kernel26 nvidia-8776-utils)
conflicts=('nvidia' 'nvidia-96xx' 'nvidia-71xx' 'nvidia-legacy')
install=nvidia.install
source=(http://download.nvidia.com/XFree86/Linux-$ARCH/${_nver}/NVIDIA-Linux-$ARCH-${_nver}-pkg0.run NVIDIA_kernel-1.0-8776-20061203.diff.txt)
md5sums=('93ad45fe7b974a5a80348e1890f9b7c9' '70e669f06ee4881c2583261672de292a')
[ "$CARCH" = "x86_64" ] && md5sums=('f5340e4bbce811add994b1685cdea03b' '70e669f06ee4881c2583261672de292a')
build()
# Extract
cd $startdir/src/
sh NVIDIA-Linux-$ARCH-${_nver}-pkg0.run --extract-only
cd NVIDIA-Linux-$ARCH-${_nver}-pkg0
# Any extra patches are applied in here...
patch -p0 < $startdir/NVIDIA_kernel-1.0-8776-20061203.diff.txt ||return 1
cd usr/src/nv/
ln -s Makefile.kbuild Makefile
make SYSSRC=/lib/modules/$_kernver/build module || return 1
# install kernel module
mkdir -p $startdir/pkg/lib/modules/${_kernver}/kernel/drivers/video/
install -m644 nvidia.ko $startdir/pkg/lib/modules/${_kernver}/kernel/drivers/video/
sed -i -e "s/KERNEL_VERSION='.*'/KERNEL_VERSION='${_kernver}'/" $startdir/*.install
Place the patch (NVIDIA_kernel-1.0-8776-20061203.diff.txt) and nvidia.install in the same directory as the PKGBUILD.
nvidia-utils:
pkgname=nvidia-8776-utils
pkgver=1.0.8776
_nver=1.0-8776
pkgrel=1
pkgdesc="NVIDIA drivers utilities and libraries."
arch=(i686 x86_64)
[ "$CARCH" = "i686" ] && ARCH=x86
[ "$CARCH" = "x86_64" ] && ARCH=x86_64
url="http://www.nvidia.com/"
depends=(xorg-server)
conflicts=('libgl' 'libgl-dri' 'ati-fglrx-utils' 'nvidia-legacy-utils' 'nvidia-71xx-utils' 'nvidia-96xx-utils')
provides=('libgl' )
#install=nvidia.install
source=(http://download.nvidia.com/XFree86/Linux-$ARCH/${_nver}/NVIDIA-Linux-$ARCH-${_nver}-pkg0.run)
md5sums=('93ad45fe7b974a5a80348e1890f9b7c9')
[ "$CARCH" = "x86_64" ] && md5sums=('f5340e4bbce811add994b1685cdea03b')
build()
# override nvida install routine and do it the long way.
cd $startdir/src/
sh NVIDIA-Linux-${ARCH}-${_nver}-pkg0.run --extract-only
cd NVIDIA-Linux-${ARCH}-${_nver}-pkg0/usr/
mkdir -p $startdir/pkg/usr/{lib,bin,share/applications,share/pixmaps,man/man1}
mkdir -p $startdir/pkg/usr/lib/xorg/modules/{extensions,drivers}
mkdir -p $startdir/pkg/usr/share/licenses/nvidia/
install `find lib/ -iname \*.so\*` $startdir/pkg/usr/lib/
install lib/tls/* $startdir/pkg/usr/lib
install share/man/man1/* $startdir/pkg/usr/man/man1/
rm $startdir/pkg/usr/man/man1/nvidia-installer.1.gz
install X11R6/lib/libXv* $startdir/pkg/usr/lib/
install share/applications/nvidia-settings.desktop $startdir/pkg/usr/share/applications/
# fix nvidia .desktop file
sed -e 's:__UTILS_PATH__:/usr/bin:' -e 's:__PIXMAP_PATH__:/usr/share/pixmaps:' -i $startdir/pkg/usr/share/applications/nvidia-settings.desktop
install share/pixmaps/nvidia-settings.png $startdir/pkg/usr/share/pixmaps/
install X11R6/lib/modules/drivers/nvidia_drv.so $startdir/pkg/usr/lib/xorg/modules/drivers
install X11R6/lib/modules/extensions/libglx.so.$pkgver $startdir/pkg/usr/lib/xorg/modules/extensions
install -m755 bin/nvidia-{settings,xconfig,bug-report.sh} $startdir/pkg/usr/bin/
cd $startdir/pkg/usr/lib/;
ln -s /usr/lib/libGL.so.$pkgver libGL.so
ln -s /usr/lib/libGL.so.$pkgver libGL.so.1
ln -s /usr/lib/libGLcore.so.$pkgver libGLcore.so.1
ln -s /usr/lib/libnvidia-cfg.so.$pkgver libnvidia-cfg.so.1
ln -s /usr/lib/libnvidia-tls.so.$pkgver libnvidia-tls.so.1
cd $startdir/pkg/usr/lib/xorg/modules/extensions;
ln -s /usr/lib/xorg/modules/extensions/libglx.so.$pkgver libglx.so
install $startdir/src/NVIDIA-Linux-${ARCH}-${_nver}-pkg0/LICENSE $startdir/pkg/usr/share/licenses/nvidia/
find $startdir/pkg/usr -type d -exec chmod 755 {} \;
# phew :)
Last edited by kappa (2007-08-09 11:14:42)

Persistent USB Arch installation fails to boot after first shut down

Hey all,
I've recently installed Arch on a 32-GB USB flash drive (with the help of the wiki, of course). I have some experience installing arch on my computers, so the process went relatively smoothly. As some background info, I AM using UUIDs in both the bootloader and the fstab file, so that shouldn't be a problem.
Anyways, the problem itself: I have arch installed and ready to go, and it boots up fine (the first time). The thing is, after I shut down, if I try to boot the USB drive again, it simply hangs there-- no boot. What's weirder is not only does it not boot, but it also freezes the host computer at that point in the boot cycle. I mean, everything will be frozen up at the startup BIOS/splash whatever screen when the USB key is in, but once I take it out the computer will boot up regularly. It's really strange.
If I reinstall the bootloader on the USB drive then everything works again (that is, until I reboot).
Is the bootloader somehow getting corrupted while shutting down? I have tried using both GRUB and SYSLINUX (not at the same time of course) but they both behave the same.
Any help would be greatly appreciated.
Thank you for your time,
Ushahin

https://wiki.archlinux.org/index.php/Be … nvironment
Here you need to set the right hooks if the root is on a USB drive, if you use RAID, LVM, or if /usr is on a separate partition.
Did you remember to do this?
If not, mount the partition(s) starting with the root partition first, chroot into it, edit that file and re-generate the initramfs. Then reboot with the reboot command, don't forcefully shut it down using the power button or something like that.
It could also be a BIOS issue. Restore its defaults, set "Removable Dev." first, "CD-ROM" second (if you have an optical drive), "Internal Storage" third. Then select the USB stick as the first to boot in the boot priority screen.
Last edited by DSpider (2012-10-12 07:07:30)

TS1394 Can't re-install Leopard. Trying to reinstall the OS because computer locks up. It is a 2008 iMac that came with Leopard. Upgraded to Snow Leopard. Tried to archive and install from original DVD that came with iMac. Installation failed, so tri

Computer locks up, so I want to reinstall the OS. I had upgraded to Snow Leopard.
Tried to do an archive and install from the DVD that came with the computer, but that failed.
Tried to do an erase and install, but the install stops somewhere near the end, 13 minutes to go. Tried several times, same result.
Can't reboot from the install disk, it just ejects the disk and I get the flashing question mark.
Any suggestions will be appreciated.

I think my hard drive is toast. When I boot in single user mode, I get the following text:
CSRHID Transition Driver: start booting in single user... will wait for window server
Then the following text appears, repeating itself over and over, except that the numbers (indicated by "xxxxxxx")
SAM Multimedia: READ or WRITE failed, SENSE_KEY = 0x03, ASC = 0x02, ASCQ = 0x00
SAM Multimedia: READ or WRITE failed, SENSE_KEY = 0x03, ASC = 0x02, ASCQ = 0x00
disk1s3: I/O error.
0[level 3] [READUID 0] [Facility com.apple.system.fs] [ErrType IO] [Err No 51] [IDType READ] [PB1kNum xxxxxxxxx] [LB1kNum 0] [FSLogMsgID xxxxxxx] [FSLogMsgOrder First]
0[Level 3] [READUID 0] [Facility com.apple.system.fs] [FSLogMsgID xxxxxxxxxx] [FSLogMsgOrder Last]
These messages keep repeating with the numbers (xxxxxxxxx) changing with each iteration.
Does this indicate a bad hard drive?
Thanks.

UEFI installation fails to boot

Using the latest (2012.12.01) image, I can boot the CD in UEFI mode, `modprobe efivars` and `efibootmgr` work fine and I finished the installation.
However, upon trying to boot it, after a few seconds of init output, the screen turns black and nothing happens.
Motherboard is ASUS M5A97 Evo.

With nomodeset in the kernel parameters, I can boot and get to a command line, but when I try to start X, I get an error message stating that it can't set the mode, so there's less screens than it detected and therefore fails to start.
Without nomodeset, instead of the screen working, as soon as it gets to the part of booting up where it would change the resolution, the screen just violently flashes black and white.

[solved] netctl (/usr/lib/network/network) fails at boot, sometimes

Hi,
Since I reinstalled a new HD in my old laptop (8 years old) I have a problem with my netctl-profile: in about 1 in 4 boots the wireless does not connect. I appreciate it if someone could take a look at what happens, because I cannot seem to find the cause because the logs and errors do not give much information.
Some general info:
1) Wireless interface is wlan0; I turned off dynamic naming of systemd/udev. Network driver is RT2500pci.
2) I use an old kernel version, 3.3.8, because any newer version effectively hard blocks the radio signal without any possibility to change this (rfkill etc).
3) The power saving option of the network interface must be off. An udev rule does this effectively.
4) The ip link of the wireless interface must be off before netctl can start the network profile.
5) When the connection fails, I enter "ip link set wlan0 down" and then start the network profile by entering "netctl start Sorryvoordehobo". This *always* works.
The following logs and outputs perhaps give information about the issue. Particularly the last might be helpful, because it shows that some authentication indeed takes place, but there is no network.
netctl profile:
Description='Sorryvoordehobo'
Interface=wlan0
Connection=wireless
Security=wpa-configsection
IP=dhcp
TimeoutCarrier=60
TimeoutDHCP=90
WPAConfigSection=(
'ssid="sorry voor de hobo"'
'key_mgmt=WPA-PSK'
'proto=WPA'
'pairwise=CCMP'
'group=CCMP'
'psk=1234-etc'
ExecUpPost='/usr/bin/ntpd -q || true'
systemctl --failed:
UNIT LOAD ACTIVE SUB DESCRIPTION
[email protected] loaded failed failed Sorryvoordehobo
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
1 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
systemctl status -l [email protected]:
[email protected] - Sorryvoordehobo
Loaded: loaded (/etc/systemd/system/[email protected]; enabled)
Active: failed (Result: exit-code) since Tue 2013-12-17 21:19:04 CET; 3min 26
s ago
Docs: man:netctl.profile(5)
Process: 176 ExecStart=/usr/lib/network/network start %I (code=exited, status=
1/FAILURE)
Main PID: 176 (code=exited, status=1/FAILURE)
dmesg:
[ 2.879915] Adding 255996k swap on /dev/sda2. Priority:-1 extents:1 across:255996k SS
[ 3.001917] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: data=ordered
[ 3.037816] systemd-journald[90]: Received request to flush runtime journal from PID 1
[ 3.210237] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af: excluding 0x170-0x177 0x1f0-0x1f7 0x290-0x297 0x370-0x377
[ 3.212449] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff: excluding 0x3e0-0x3e7 0x3f0-0x3f7 0x400-0x40f 0x4d0-0x4d7
[ 3.213304] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff: excluding 0x820-0x87f
[ 3.213995] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7: clean.
[ 3.215231] pcmcia_socket pcmcia_socket0: cs: memory probe 0x0c0000-0x0fffff: excluding 0xc0000-0xc7fff 0xcc000-0xd3fff 0xe0000-0xfffff
[ 3.215280] pcmcia_socket pcmcia_socket0: cs: memory probe 0xa0000000-0xa0ffffff: clean.
[ 3.215324] pcmcia_socket pcmcia_socket0: cs: memory probe 0x60000000-0x60ffffff: clean.
[ 3.215367] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff: clean.
[ 3.400147] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 3.401565] Registered led device: rt2500pci-phy0::radio
[ 3.401645] Registered led device: rt2500pci-phy0::quality
[ 3.401959] snd_via82xx 0000:00:11.5: setting latency timer to 64
[ 3.586063] psmouse serio4: synaptics: Touchpad model: 1, fw: 5.1, id: 0x8f40
b1, caps: 0x80471b/0x0/0x0
[ 3.625577] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/seri
o4/input/input6
[ 9.541467] Installing knfsd (copyright (C) 1996 [email protected]).
[ 9.690039] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery d
irectory
[ 9.690680] NFSD: starting 90-second grace period
[ 10.513803] wlan0: authenticate with 00:1a:70:9e:3a:70 (try 1)
[ 10.515334] wlan0: authenticated
[ 10.527175] wlan0: associate with 00:1a:70:9e:3a:70 (try 1)
[ 10.529457] wlan0: RX AssocResp from 00:1a:70:9e:3a:70 (capab=0x411 status=0
aid=4)
[ 10.529464] wlan0: associated
[ 10.529472] wlan0: moving STA 00:1a:70:9e:3a:70 to state 1
[ 10.529476] wlan0: moving STA 00:1a:70:9e:3a:70 to state 2
[ 10.577870] Intel AES-NI instructions are not detected.
[ 11.367009] wlan0: moving STA 00:1a:70:9e:3a:70 to state 3
Any ideas as to what exactly fails here? Thanks!
Last edited by anadyr (2013-12-21 21:32:44)

I don't think there is anything wrong with the kernel. Note that with the previous HD everything started perfectly, with the same kernel version. The new HD is a lot faster as it is an SSD; maybe this has anything to do with the issue?
To continue: the connection always works when I manually enter "ip link set wlan0 down" and then start netctl. I figured that I should execute this command before netctl starts, but I cannot seem to get this to work. What I tried is to edit /etc/systemd/system/netctl.service, by entering this command with the options ExecStartPre and ExecStartPost (see the two commented lines):
[Unit]
Description=(Re)store the netctl profile state
Before=network.target
[Service]
Type=oneshot
RemainAfterExit=yes
#ExecStartPre=-/usr/bin/ip link set wlan0 down
ExecStart=-/usr/bin/netctl restore
#ExecStartPost=-/usr/bin/ip link set wlan0 down
ExecStop=/usr/bin/netctl store
KillMode=none
[Install]
WantedBy=multi-user.target
Nevertheless, with either of these lines uncommented I get boots without the netctl-profile starting.
In the original post I did not give the output of ip link. So here it is:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN mode DEFAULT
group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group
default qlen 1000
link/ether 00:40:45:25:dc:4b brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORM
ANT group default qlen 1000
link/ether 00:13:d3:6c:f3:78 brd ff:ff:ff:ff:ff:ff
To conclude: authentication succeeds (see the output of dmesg), but I do not seem to get an IP-address (see above). But I have no idea why, and the error messages are not very clear.
I am still figuring out what happens here, but maybe somebody knows what goes wrong here? Thanks!

SDK Installation Failed

Hi Guys:
We created an SDK Setup as we do for every Add-On using a separated solution to include, Customer Library, Setup & SDK Setup.
We followed all the stesp we normally do, Change Add-On Name and Executable file, Include Customer Library Conpilation Output and files needed to run Add-On
The Add-On Registration Starts, Goes thru the Setup Wizard and after the Setup Wizard finishes it waits with the hourglass until times out and shows you that SDK Setup Installation failed.
So it does not finishes the Add-On Installation.
I have Created a new VS Solution and create everything from scratch and samething happened.
Does somebody has had the same problem, and found a solution for it.
Thanks
Edel

Hello Edel,
Please make sure the following funcitons in AddOnInstallAPI.DLL have been called:
The installer must handle a command line parameter:
     "RecommendedPathForAddOn" | "PathForAddOnInstallAPI.dll"
You must use the AddOnInstallAPI.dll in your installer!
Mandatory:
EndInstallEx (String, Boolean)
     Call this function at the end of the installation process.
     The boolean parameter allows to indicate success (= True) or failure (= False).
     The function returns an integer value; 0 signals success.
EndUnInstall (String, Boolean)
     Call this function at the end of the uninstallation process.
     The boolean parameter allows to indicate success (= True) or failure (= False).
     The function returns an integer value; 0 signals success.
Actually there is a installer SDK sample and also AddOn Installer Wizard tool available in B1DE:
1.You can refer to SDK sample of AddOn Setup:
<<C:Program FilesSAPSAP Business One SDKSamplesCOM UIVB.NET14.AddOnInstaller>>
2.B1 Installer Wizard in B1DE, How to download.
=>SAP Business One Development Environment Tools
Please pay attention to download the right version for your B1 version and VS .Net
Please refer to help file of B1DE after installation
Start=>All Programs=>SAP Business One=>Development Tools=>Help file
=>Simple Installer
You may refer to the following relevant threads. Or search keyword "Installation" or "Installer" for more.
Regards, Yatsea

[SOLVED] Problem with external USB drive started yesterday

My system freezes for about 65 seconds at the login screen. After 65 seconds, I can login and everything is normal afterwards.
I discovered that I can eliminate the freeze by disconnecting the external USB drive from the PC. Here are the error messages from kernel.log when the drive is connected:
Oct 15 23:10:14 localhost kernel: [ 17.035091] usb 1-1.3: device descriptor read/64, error -110
Oct 15 23:10:29 localhost kernel: [ 32.155955] usb 1-1.3: device descriptor read/64, error -110
Oct 15 23:10:29 localhost kernel: [ 32.325394] usb 1-1.3: new high speed USB device number 4 using ehci_hcd
Oct 15 23:10:31 localhost kernel: [ 34.045126] MediaState is connected
There is supposed to be a kernel boot option (irqpoll) to prevent this from occurring. However, that option seems to no longer work for kernels after 2.6.39. If I try using it with Arch, the system will not boot, saying all the CPU's failed.
I also don't understand why this just started happening yesterday, as the USB drive has been connected to the PC longer than I've been using Arch. Also, my kernel has not been updated since I installed Arch on Oct 8.
Does anyone know another fix or workaround for this problem?
Thanks,
Tim
Last edited by ratcheer (2011-10-17 01:30:08)

Problem solved
I feel stupid, but I also feel better. I turned off the PC, disconnected the power from the USB drive for about 15 seconds, reconnected the power, rebooted, removed the irqpoll kernel option, and Ubuntu started, perfectly. I need to learn that the USB drive just goes freaky sometimes and remember to do this. But, this is only the second time I've had to do this in months of use.
Tim

Photoshop 13.1.2 for Creative Cloud Installation failed. Error Code: U44M1P7

Hello, I need some help. I am getting the following error just when updating my Photoshop CS6 app. U44M1P7

http://blogs.adobe.com/crawlspace/2012/07/photoshop-basic-troubleshooting-steps-to-fix-mos t-issues.html#TroubleshootUpda…
Re-install on top of CS6 had to do that myself when I had perpetual CS6 installed and tried to update to Subscription version. Perpetual CS 6 13.0.1.3 Windows 13.0.6 Mac are different then 13.1.2 subscription version
Explanations of error codes:
U = Updater.
44 = Install Update Error
M1 = Automatic
M2 = Standalone mode
P = Patcher
6 = Done With Errors
7 = Installation Failed
ISSUE: Installation failed. Error Code: U44M1P7, U44M2P7, U44M1P6
SOLUTION: Run the installer. Reinstall Photoshop CS6 to repair/replace the missing/modified file. Select Help>Updates… to run the updater again. http://helpx.adobe.com/creative-suite/kb/error-u44m1p7-installing-updates-ccm.html

CC 2014, the installation fails by the fatal error exit number: 7

Hey guys. Since 24 days Im trying to update my Cloud to the CC 2014 but when starting with PS, the installation fails by the fatal error exit number: 7. Whats to do?

Well John, first of all, thank you very much for helping me.
Yesterday I tried something, by deinstalling the Cloud App and PS, but still the same error remained.
What I also don't understand is the term: Reinstalling the product. Is it meant, to deinstall every app, just the Cloud app or only the app where the error occupies?
By Reinstalling I also understand: Uninstall the app and the install it again. Is this correct?
I am surprised anyway. Once everything is fine and then within one day, nothing runs anymore. I read about, using a disc clean app as Clean My Mac 2 can destroy the structure of adobe products some how... but hmmm... this sounds very strange.

FB 4.6 Installation fails. Information not found in Media_db

Hello everyone,
I have heard so much about the new features and performance updates in FB 4.6 that I decided to give it a try.
I removed my old FB 4.5 installation and run the FB 4.6 installer, but it does not complete... It aborts the installation with a simple installation failed message and no additonal info.
the log-file however offers the following information
----------------- CreatePayloadSession: machine is x64 ---------------
[ 1400] Tue Dec 13 18:44:38 2011 FATAL
Payload '{ED28819E-310F-4F17-925C-C69B0A1C1F7F} Suite Shared Configuration CS5.5 5.0.22.0' information not found in Media_db.
[ 1400] Tue Dec 13 18:44:38 2011 INFO
:: END TIMER :: [Total Timer] took 24685.1 milliseconds (24.6851 seconds) DTR = 10.8567 KBPS (0.0106023 MBPS)
-------------------------------------- Summary --------------------------------------
- 1 fatal error(s), 0 error(s), 0 warning(s)
FATAL: Payload '{ED28819E-310F-4F17-925C-C69B0A1C1F7F} Suite Shared Configuration CS5.5 5.0.22.0' information not found in Media_db.
Please search the above error/warning string(s) to find when the error occurred.
These errors resulted in installer Exit Code mentioned below.
Exit Code: 7 - Unable to complete Silent workflow.
I tried to install it in windows safe-mode (And yes I run the file as an admin), same result. I also got the tip to rename my Media_db file under ...Common Files/Adobe/caps still no changes.
I cannot figure out the Problem, the installation of 4.5 just went fine.
My system:
Windows 7 64bit.
AMD 1090T hexacore CPU
8GB Ram
44GB free disk space
CS 5 PP installed (but no sign of a conflict)

reinstalled FB 4.5 again
deinstalled FB 4.5 again
installed FB 4.6
finally completing without Error

"Installer Failed to Initialize" Error

I've just tried to install a very recently purchased CS6 upgrade for my CS5.1 but it immediately fails with the message "Installer Failed to Initialize". It suggests running the Adobe Support Advisor, which I've done but that cannot detect any issues. Where do I go from there?

Your next step would be to review the PDApp.log file. You can find directions on how to locate and review this file at Troubleshoot with install logs | CS5, CS5.5 - http://helpx.adobe.com/creative-suite/kb/troubleshoot-install-logs-cs5-cs5.html#main_Analy ze_the_Creative_Suite_5_PDapp_log.

[SOLVED] Luks with /arch/setup installation , fails at boot

Similar Messages

Maybe you are looking for