[SOLVED] UDEV Failed at boot

hey all,
I'm having an issue with udev at boot failing and although I can get to the login prompt and login a whole load of hardware is undetected including network graphics and sound. I am able the start udevd without any apparant issue once logged in but unfortunatley I'm not all that clued up on how to find and load driver short of loading modules I've been told to for reasons X,Y and Z.
I am having to use a live disc to get online and send this post and pull log data from my system.
things I've tried include re-installing udev, kmod and the kernel plus reading alot on udev and how it is ment to work (starting to get major eye strain now)
here is a paste of my boot log
http://pastebin.com/K5L3pbm1
my messages.log
http://pastebin.com/qzEziaxY
and finally my dmesg log
http://pastebin.com/F4aSdfKe
I'm not sure which of these logs will be useful but if any more information is need let me know...
and Thank You in advance.
Last edited by balasarius (2012-05-17 20:33:10)

And it helped me too....but leaves me curious as to why the initscripts are not updating ?
Medium length story: I had to upgrade to current using the official iso (current release) dated last fall.
I tried c couple of recent releng isos and they failed to mount my usb partition as the targets. This was
also the case for the latest archbang iso as well. i.e. To do an install to a usb stick I had to use the old core.
All of that, albeit time comsuming, was more or less something I could plod along with on my own. The failure
of the dep-chain to pick-up on installing the latest initscripts was surprising as it required that I find the information
in this email thread.

Similar Messages

[solved] udev fails to register anything on boot after kmod

Hello,
After yesterday's kmod upgrade, i can't seem to get udev to modprobe anything on boot. Udev throws about two dozen errors during boot complaining about "no such file or directory", but /sbin/modprobe exists, and seems to work fine with udev after the boot process is complete. i know this because i can remove and replace the USB cables to the computer, and udev picks up and modprobes the correct drivers. The same devices (keyboard, mouse) fail to load during boot.
I would throw in the errors, but dmesg doesn't seem to catch them. Most are of the form "udev: error: /sbin/modprobe "/sbin/modprobe [some "dash arguments"] usb:*huge alphanumeric string*" This is from memory, so excuse any probable inaccuracies.
Any ideas or starting points?
Thanks,
--Aaron
Last edited by usagi (2012-01-07 00:58:47)

falconindy wrote:
falconindy wrote:
usagi wrote:So, now my query becomes: is there a way to mount an arbitrary drive before boot commences?
Expect support for this (mounting /usr) in mkinitcpio "soon". If you want to help speed along the process, here's an untested patch. Zero assumptions are made about the partition -- you will need to include any modules necessary for creating the partition in MODULES= (if it differs at all from your / partition).
I should point out that it's actually a little more involved than just "apply the patch".
1) make sure you have util-linux>=2.20.1-2
2) add 'shutdown' and 'fsck' to your initramfs hooks in /etc/mkinitcpio.conf. shutdown only needs to be somewhere after base. 'fsck' should go after autodetect if your /usr is the same FS as root, before autodetect if its different.
3) apply said patch.
4) in /etc/fstab, set passno to 0 for your /usr partition (it'll be checked in the initramfs)
5) regenerate your initramfs.
Thanks to usagi for testing this and providing valuable feedback.
the patch worked for me. my /usr is ext4 on lvm.

[SOLVED]system fails to boot since adding udev rules for automounting

Hello
I have recently been trying to use udev rules to automount, and putting together stuff from the wiki, forums and general googling around have produced the following set of rules:
# automounts usb hdd and pendrives as usbhd-sdx; no messing around with
# volume labels or other confusing stuff
# matches all sdx devices except the internal hdd, sda
KERNEL=="sd[b-z]", NAME="%k", SYMLINK+="usbhd-%k", GROUP="users", OPTIONS="last_rule"
# imports filesystem information
ACTION=="add", IMPORT{program}="/sbin/blkid -o udev -p %N"
# creates mount points and sets up symlinks
ACTION=="add", KERNEL=="sd[b-z][0-9]", SYMLINK+="usbhd-%k", GROUP="users", NAME="%k"
ACTION=="add", KERNEL=="sd[b-z][0-9]", RUN+="/bin/mkdir -p /media/usbhd-%k"
ACTION=="add", KERNEL=="sd[b-z][0-9]", RUN+="/bin/ln -s /media/usbhd-%k /mnt/usbhd-%k"
# global mount options
ACTION=="add", ENV{mount_options}="relatime"
# filesystem-specific mount options (777/666 dir/file perms for ntfs/vfat)
ACTION=="add", ENV{ID_FS_TYPE}=="vfat|ntfs", ENV{mount_options}="$env{mount_options},gid=100,dmask=000,fmask=111,utf8"
# automount ntfs filesystem with ntfs-3g driver
ACTION=="add", KERNEL=="sd[b-z][0-9]", ENV{ID_FS_TYPE}=="ntfs", RUN+="/bin/mount -t ntfs-3g -o %E{mount_options} /dev/%k /media/usbhd-%k", OPTIONS="last_r$
# automount all other file systems
ACTION=="add", KERNEL=="sd[b-z][0-9]", ENV{ID_FS_TYPE}!="ntfs", RUN+="/bin/mount -t auto -o %E{mount_options} /dev/%k /media/usbhd-%k", OPTIONS="last_rule"
# unmounts and removes the mount points
ACTION=="remove", KERNEL=="sd[b-z][0-9]", RUN+="/bin/rm -f /mnt/usbhd-%k"
ACTION=="remove", KERNEL=="sd[b-z][0-9]", RUN+="/bin/umount -l /media/usbhd-%k"
ACTION=="remove", KERNEL=="sd[b-z][0-9]", RUN+="/bin/rmdir /media/usbhd-%k", OPTIONS="last_rule"
This seemed to be working very well unitl I tried to boot this morning and the boot process stopped at "processing UDev events" with the following message:
iTCO_wdt: Unexpected close, not stopping watchdog!
It pauses at this point for 10-15 seconds and then reboots.
Having searched a bit, I found the following similar post on the forums: http://bbs.archlinux.org/viewtopic.php?pid=459375
Which suggests that the problem might lie with this line:
ACTION=="add", IMPORT{program}="/sbin/blkid -o udev -p %N"
I have renamed the file so that it no longer has the udev .rules extension and now the system boots fine. Does anyone have any suggestions as to why the above rules might be causing this behaviour and how I might go about fixing it?
Thanks
Last edited by useradded (2010-07-02 22:58:14)

Hey falconindy
That was the final kick up the logical a$$ that I needed to get some kind of grip on udev rules. I now have a fully functional rule that applies only to /dev/sdxy and not to everything else as well, so no more boot trauma, THANK YOU.
I will mark this thread as solved and post my new rule for the benefit of anyone who might read this.
New rule (no boot problems):
# automounts usb hdd and pendrives as label or as usbhd-sdxy if no label present
# ensures the following is _only_ run for sdxy devices excluding internal hdd, sda
KERNEL!="sd[b-z][0-9]", GOTO="personal_usb_automount_settings_end"
# imports filesystem information
# provides access to following variables:
# ID_FS_UUID; ID_FS_UUID_ENC; ID_FS_VERSION; ID_FS_TYPE; ID_FS_VERSION; ID_FS_LABEL
# accessible via ENV{variable}; $env{variable}|%E{variable}
IMPORT{program}="/sbin/blkid -o udev -p %N"
# Get a label if present, otherwise name usbhd-%k
ENV{ID_FS_LABEL}!="", ENV{dir_name}="%E{ID_FS_LABEL}"
ENV{ID_FS_LABEL}=="", ENV{dir_name}="usbhd-%k"
# creates mount points and sets up symlinks
ACTION=="add", SYMLINK+="%E{dir_name}", GROUP="users", NAME="%k"
ACTION=="add", RUN+="/bin/mkdir -p /media/%E{dir_name}"
ACTION=="add", RUN+="/bin/ln -s /media/%E{dir_name} /mnt/%E{dir_name}"
# global mount options
ACTION=="add", ENV{mount_options}="relatime"
# filesystem-specific mount options (777/666 dir/file perms for ntfs/vfat)
ACTION=="add", ENV{ID_FS_TYPE}=="vfat|ntfs", ENV{mount_options}="$env{mount_options},gid=100,dmask=000,fmask=111,utf8"
# automount ntfs filesystem with ntfs-3g driver
ACTION=="add", ENV{ID_FS_TYPE}=="ntfs", RUN+="/bin/mount -t ntfs-3g -o %E{mount_options} /dev/%k /media/%E{dir_name}", OPTIONS="last_rule"
# automount all other file systems
ACTION=="add",ENV{ID_FS_TYPE}!="ntfs", RUN+="/bin/mount -t auto -o %E{mount_options} /dev/%k /media/%E{dir_name}", OPTIONS="last_rule"
# unmounts and removes the mount points
ACTION=="remove", RUN+="/bin/rm -f /mnt/%E{dir_name}"
ACTION=="remove", RUN+="/bin/umount -l /media/%E{dir_name}"
ACTION=="remove", RUN+="/bin/rmdir /media/%E{dir_name}", OPTIONS="last_rule"
# exit
LABEL=="personal_usb_automount_settings_end"
Last edited by useradded (2010-07-02 22:59:20)

[solved] lvm fails at boot time / lvm pv scan hangs (often)

Hi,
I switched from ubuntu to Archlinux two weeks ago and about half of my boot attempts fail because of some problems with my lvm-volumes
My setup
I have my root partition on /dev/sda2 and an lvm partition /dev/sda3 containing logical volumes for /var /home and /boot
If booting succeeds these volumes appear as
/dev/mapper/VolGroup01-varVol
/dev/mapper/VolGroup01-homeVol
/dev/mapper/VolGroup01-bootVol
If my booting fails, My screen shows
startin version 218
/dev/sda2: clean, blabla files, blabla blocks
A start job is running for LVM PV scan on devices 8:3
This last message (together with 3 start jobs for dev-disk-by-x2duuid-SOMENUMBERS) appears for 90 seconds and then emergency mode is started
After logging in for maintenance /dev/mapper only contains "control" but not my logical volumes
module dm_mod is loaded
dmesg does not seem to show anything related to lvm or sda3
and /var/log contains only empty files (btmp, lastlog, wtmp)
Where can I find informations about this problem?
Any suggestions how to solve this problem?
Last edited by DaAlx (2015-04-06 12:45:17)

DaAlx wrote:
Hi,
I switched from ubuntu to Archlinux two weeks ago and about half of my boot attempts fail because of some problems with my lvm-volumes
My setup
I have my root partition on /dev/sda2 and an lvm partition /dev/sda3 containing logical volumes for /var /home and /boot
If booting succeeds these volumes appear as
/dev/mapper/VolGroup01-varVol
/dev/mapper/VolGroup01-homeVol
/dev/mapper/VolGroup01-bootVol
If my booting fails, My screen shows
startin version 218
/dev/sda2: clean, blabla files, blabla blocks
A start job is running for LVM PV scan on devices 8:3
This last message (together with 3 start jobs for dev-disk-by-x2duuid-SOMENUMBERS) appears for 90 seconds and then emergency mode is started
After logging in for maintenance /dev/mapper only contains "control" but not my logical volumes
module dm_mod is loaded
dmesg does not seem to show anything related to lvm or sda3
and /var/log contains only empty files (btmp, lastlog, wtmp)
Where can I find informations about this problem?
Any suggestions how to solve this problem?
Hello,
Disclaimer: Without any logs to see what is happening, this is just an educated guess because it sounds like what happened to me. Try getting the logs during the emergency shell process.
I've run into an issue myself with LVM. From what I understand, the pvscan processes get stuck waiting for a udev sync that no longer exists because udev is restarted while pvscan processes are running in the background. There hasn't been an official solution but I modified udev hook with this (can be found in /usr/lib/initcpio/hooks/udev):
while [ "$(pgrep -f pvscan)" ]; do
sleep 0.1
done
which forces udev to wait until the LVM processes finish before telling it to die. It is hacky and poor for a long term solution because we have lvm code in the udev hook is bad design but I haven't had that issue any more.
You can also try
In /etc/mkinitcpio.conf, you must change your HOOKS list:
HOOKS="base udev autodetect modconf block lvm2 filesystems keyboard fsck" is a hook list for script
HOOKS="base systemd autodetect modconf block sd-lvm2 filesystems keyboard fsck" is a hook list for systemd
but that stopped working for a few people on 3.19.
Here is the bug report to keep you up to date:
https://bugs.archlinux.org/task/41833#comment133971
Last edited by SirMyztiq (2015-04-06 00:36:46)

[SOLVED] System fails to boot after upgrade.

Not exactly sure what happened as the upgrade appeared to go smoothly. Now trying to start just causes an endless cycle of rebooting. I have been unable to even boot into single user mode. Any suggestions are greatly appreciated here.
Using the livecd I can mount all the filesystems, and I have run fsck on all of them so I know they are clean. Here are my grub entries:
# (0) Arch Linux
title Arch Linux
root (hd0,1)
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/569a7fe5-7452-4064-adc1-71b6b2b58b0b resume=/dev/sda7 ro vga=773 elevator=deadline
initrd /boot/kernel26.img
# (1) Arch Linux
title Arch Linux Fallback
root (hd0,1)
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/569a7fe5-7452-4064-adc1-71b6b2b58b0b ro vga=773
initrd /boot/kernel26-fallback.img
I have tried using a kernel line of just:
kernel /boot/vmlinuz26 root=/dev/sda2 ro
and get the same results, as soon as grub starts to load the kernel the system reboots and I can't see what's on screen long enough to know what's happening.
pacman.log:
[2009-07-19 16:02] synchronizing package lists
[2009-07-19 16:02] starting full system upgrade
[2009-07-20 14:52] synchronizing package lists
[2009-07-20 14:52] starting full system upgrade
[2009-07-20 14:54] starting full system upgrade
[2009-07-20 15:44] upgraded kernel-headers (2.6.29.3-1 -> 2.6.30.1-1)
[2009-07-20 15:44] Generating locales...
[2009-07-20 15:44] en_US.UTF-8... done
[2009-07-20 15:44] en_US.ISO-8859-1... done
[2009-07-20 15:44] Generation complete.
[2009-07-20 15:44] upgraded glibc (2.10.1-2 -> 2.10.1-3)
[2009-07-20 15:44] upgraded readline (5.2.013-2 -> 6.0.003-1)
[2009-07-20 15:44] upgraded abook (0.6.0pre2-1 -> 0.6.0pre2-2)
[2009-07-20 15:44] upgraded gcc-libs (4.4.0-3 -> 4.4.0-5)
[2009-07-20 15:44] upgraded libgcrypt (1.4.4-1 -> 1.4.4-2)
[2009-07-20 15:44] upgraded gnutls (2.8.0-1 -> 2.8.1-1)
[2009-07-20 15:44] upgraded bash (3.2.048-3 -> 4.0.024-1)
[2009-07-20 15:44] upgraded e2fsprogs (1.41.6-1 -> 1.41.8-1)
[2009-07-20 15:44] upgraded perl (5.10.0-4 -> 5.10.0-6)
[2009-07-20 15:44] warning: /etc/ssl/openssl.cnf installed as /etc/ssl/openssl.cnf.pacnew
[2009-07-20 15:44] upgraded openssl (0.9.8k-2 -> 0.9.8k-4)
[2009-07-20 15:44] upgraded sqlite3 (3.6.15-1 -> 3.6.15-2)
[2009-07-20 15:44] upgraded heimdal (1.2.1-3 -> 1.2.1-5)
[2009-07-20 15:44] upgraded libpng (1.2.37-1 -> 1.2.38-1)
[2009-07-20 15:44] upgraded libjpeg (6b-6 -> 7-1)
[2009-07-20 15:44] upgraded libtiff (3.8.2-4 -> 3.8.2-5)
[2009-07-20 15:44] upgraded libcups (1.3.10-2 -> 1.3.11-1)
[2009-07-20 15:44] upgraded cairo (1.8.6-1 -> 1.8.8-1)
[2009-07-20 15:44] upgraded libthai (0.1.11-1 -> 0.1.12-1)
[2009-07-20 15:44] upgraded pango (1.24.2-1 -> 1.24.4-2)
[2009-07-20 15:44] upgraded gtk2 (2.16.2-1 -> 2.16.5-1)
[2009-07-20 15:44] upgraded aiksaurus (1.2.1-1 -> 1.2.1-2)
[2009-07-20 15:45] upgraded python (2.6.2-2 -> 2.6.2-5)
[2009-07-20 15:45] upgraded boost (1.37.0-1 -> 1.39.0-1)
[2009-07-20 15:45] upgraded libmysqlclient (5.1.35-2 -> 5.1.36-1)
[2009-07-20 15:45] upgraded mysql-clients (5.1.35-1 -> 5.1.36-1)
[2009-07-20 15:45] upgraded mysql (5.1.35-1 -> 5.1.36-1)
[2009-07-20 15:45] upgraded libmng (1.0.10-1 -> 1.0.10-2)
[2009-07-20 15:45] upgraded dri2proto (2.0-1 -> 2.1-1)
[2009-07-20 15:45] upgraded libdrm (2.4.11-2 -> 2.4.12-1)
[2009-07-20 15:45] upgraded libxt (1.0.5-2 -> 1.0.6-1)
[2009-07-20 15:45] upgraded mesa (7.4.4-1 -> 7.5-1)
[2009-07-20 15:45]
[2009-07-20 15:45] > Qt 4.5.1
[2009-07-20 15:45]
[2009-07-20 15:45] Prefix: /usr
[2009-07-20 15:45]
[2009-07-20 15:45] > ATTENTION
[2009-07-20 15:45] Some components are split into separate packages:
[2009-07-20 15:45]
[2009-07-20 15:45] qtmod : Base libraries and tools
[2009-07-20 15:45] qtmod-doc : Documentation
[2009-07-20 15:45] qtmod-demos : Demos & Examples
[2009-07-20 15:45] qtmod-tools : Development Tools (Assistant, Designer, Linguist)
[2009-07-20 15:45]
[2009-07-20 15:45] upgraded qtmod (4.5.1-2 -> 4.5.1-4)
[2009-07-20 15:45] upgraded akonadi (1.1.2-1 -> 1.1.2-2)
[2009-07-20 15:45] upgraded apr (1.3.3-1 -> 1.3.5-1)
[2009-07-20 15:45] upgraded unixodbc (2.2.14-1 -> 2.2.14-2)
[2009-07-20 15:45] upgraded apr-util (1.3.4-1 -> 1.3.7-1)
[2009-07-20 15:45] upgraded apvlv (0.0.6.5-1 -> 0.0.6.7-1)
[2009-07-20 15:45] upgraded libsndfile (1.0.20-2 -> 1.0.20-3)
[2009-07-20 15:45] upgraded jack-audio-connection-kit (0.116.2-1 -> 0.116.2-2)
[2009-07-20 15:45] upgraded wxgtk (2.8.10.1-1 -> 2.8.10.1-4)
[2009-07-20 15:45] upgraded audacity (1.3.7-1 -> 1.3.8-1)
[2009-07-20 15:45] upgraded avifile (0.7.45-3 -> 0.7.45-4)
[2009-07-20 15:45] upgraded imlib2 (1.4.2-2 -> 1.4.2-3)
[2009-07-20 15:45] upgraded libxdg-basedir (1.0.0-2 -> 1.0.1-1)
[2009-07-20 15:45] upgraded lua (5.1.4-3 -> 5.1.4-4)
[2009-07-20 15:45]
[2009-07-20 15:45] ==> awesome installation notes:
[2009-07-20 15:45] ----------------------------------------
[2009-07-20 15:45] During some updates of awesome, the config file syntax changes heavily.
[2009-07-20 15:45] This means that your configuration file (~/.config/awesome/rc.lua) for
[2009-07-20 15:45] any other than this particular version of awesome may or may not work.
[2009-07-20 15:45]
[2009-07-20 15:45] upgraded awesome (3.3-2 -> 3.3.1-1)
[2009-07-20 15:45] upgraded bc (1.06-5 -> 1.06-6)
[2009-07-20 15:45] upgraded binutils (2.19.1-4 -> 2.19.1-5)
[2009-07-20 15:45] upgraded gstreamer0.10-base-plugins (0.10.23-1 -> 0.10.23-2)
[2009-07-20 15:45] upgraded brasero (2.26.2-1 -> 2.26.3-1)
[2009-07-20 15:45] upgraded run-parts (2.31-1 -> 3.1.3-1)
[2009-07-20 15:45] upgraded sed (4.2-1 -> 4.2.1-1)
[2009-07-20 15:45] Updating certificates in /etc/ssl/certs... 4 added, 0 removed; done.
[2009-07-20 15:45] Running hooks in /etc/ca-certificates/update.d....done.
[2009-07-20 15:45] upgraded ca-certificates (20080809-5 -> 20090709-1)
[2009-07-20 15:45] upgraded cairomm (1.8.0-1 -> 1.8.2-1)
[2009-07-20 15:45] upgraded calcurse (2.5-1 -> 2.6-1)
[2009-07-20 15:45] upgraded mjpegtools (1.9.0-1 -> 1.9.0-2)
[2009-07-20 15:45] upgraded cinelerra-cv (20090519-1 -> 20090715-1)
[2009-07-20 15:45] upgraded ctags (5.7-1 -> 5.8-1)
[2009-07-20 15:45] upgraded lcms (1.18-1 -> 1.18-2)
[2009-07-20 15:45]
[2009-07-20 15:45] NOTE for drcaw:
[2009-07-20 15:45] ----
[2009-07-20 15:45] ==> dcraw provides the simple commandline tools for raw conversion. If you
[2009-07-20 15:45] ==> are looking for a more sophisticated way consider gimp-ufraw, which
[2009-07-20 15:45] ==> provides a gimp-plugin and a standalone application that can even convert
[2009-07-20 15:45] ==> to 16-bit tiff files (which you can use in cinepaint eg.) So please do a
[2009-07-20 15:45] ==> 'pacman -S gimp-ufraw' to get it.
[2009-07-20 15:45]
[2009-07-20 15:45] upgraded dcraw (1.410-1 -> 1.425-1)
[2009-07-20 15:45] upgraded libtorrent-rasterbar (0.14.2-1 -> 0.14.4-2)
[2009-07-20 15:45]
[2009-07-20 15:45] >>> Deluge's daemon is running with the "deluge" user. The default download directory is /srv/deluge/
[2009-07-20 15:45]
[2009-07-20 15:45] upgraded deluge (1.1.9-1 -> 1.1.9-2)
[2009-07-20 15:45] upgraded device-mapper (1.02.32-1 -> 1.02.33-1)
[2009-07-20 15:45] upgraded jasper (1.900.1-2 -> 1.900.1-3)
[2009-07-20 15:45] upgraded devil (1.7.8-1 -> 1.7.8-2)
[2009-07-20 15:45] upgraded dhcpcd (5.0.4-1 -> 5.0.6-1)
[2009-07-20 15:45] > Rebuilding MIME database ... DONE
[2009-07-20 15:45] > Rebuilding xdg icon database ... DONE
[2009-07-20 15:45] upgraded kdemod-kdelibs (4.2.4-1 -> 4.2.4-3)
[2009-07-20 15:45] upgraded libtool (2.2.6a-1 -> 2.2.6a-2)
[2009-07-20 15:46] NOTE
[2009-07-20 15:46] ----
[2009-07-20 15:46] Add your user to group 'camera' to use camera devices.
[2009-07-20 15:46] upgraded libgphoto2 (2.4.6-1 -> 2.4.6-2)
[2009-07-20 15:46] NOTE
[2009-07-20 15:46] ----
[2009-07-20 15:46] Add your user to group 'scanner' to use scanner devices.
[2009-07-20 15:46] upgraded sane (1.0.20-2 -> 1.0.20-3)
[2009-07-20 15:46] > Rebuilding xdg icon database ... DONE
[2009-07-20 15:46] upgraded kdemod-kdegraphics-common (4.2.4-1 -> 4.2.4-3)
[2009-07-20 15:46] > Rebuilding xdg icon database ... DONE
[2009-07-20 15:46] upgraded kdemod-kdepimlibs (4.2.4-1 -> 4.2.4-3)
[2009-07-20 15:46] upgraded digikam (0.10.0-2 -> 0.10.0-3)
[2009-07-20 15:46] upgraded directfb (1.2.8-1 -> 1.4.1-1)
[2009-07-20 15:46] upgraded ghostscript (8.64-5 -> 8.64-6)
[2009-07-20 15:46] upgraded libwmf (0.2.8.4-4 -> 0.2.8.4-5)
[2009-07-20 15:46] upgraded libxml2 (2.7.3-1.1 -> 2.7.3-2)
[2009-07-20 15:46] upgraded imagemagick (6.5.3.2-1 -> 6.5.3.10-1)
[2009-07-20 15:46] upgraded dvdauthor (0.6.14-4 -> 0.6.14-5)
[2009-07-20 15:46] -- Edit config.h in PKGBUILD's directory (generally /var/abs/community/x11/dwm/)
[2009-07-20 15:46] -- and rebuild package if you want to change settings.
[2009-07-20 15:46] upgraded dwm (5.5-1 -> 5.6-1)
[2009-07-20 15:46] upgraded smbclient (3.3.6-1 -> 3.3.6-2)
[2009-07-20 15:46] upgraded mplayer (29318-1.1 -> 29411-3)
[2009-07-20 15:46] installed flam3 (2.7.18-3)
[2009-07-20 15:46] upgraded electricsheep (2.6.8-4 -> 2.7b12-1)
[2009-07-20 15:46] upgraded enblend-enfuse (3.2-2 -> 3.2-3)
[2009-07-20 15:46] upgraded gnome-keyring (2.26.1-1 -> 2.26.3-1)
[2009-07-20 15:46] upgraded libsoup (2.26.2-1 -> 2.26.3-1)
[2009-07-20 15:46] upgraded libgweather (2.26.1-2 -> 2.26.2.1-1)
[2009-07-20 15:46] upgraded evolution-data-server (2.26.2-1 -> 2.26.3-1)
[2009-07-20 15:46] upgraded gtkhtml (3.26.2-1 -> 3.26.3-1)
[2009-07-20 15:46] upgraded evolution (2.26.2-1 -> 2.26.3-1)
[2009-07-20 15:46] upgraded evolution-exchange (2.26.2-1 -> 2.26.3-1)
[2009-07-20 15:46] upgraded feh (1.3.4-4 -> 1.3.4-5)
[2009-07-20 15:46] upgraded ffmpegthumbnailer (1.5.0-1 -> 1.5.4-2)
[2009-07-20 15:46] upgraded filezilla (3.2.4.1-1 -> 3.2.6.1-1)
[2009-07-20 15:46] upgraded fltk (1.1.9-1 -> 1.1.9-2)
[2009-07-20 15:46] upgraded fluidsynth (1.0.8-1 -> 1.0.9-1)
[2009-07-20 15:46] upgraded fox (1.6.35-1 -> 1.6.36-1)
[2009-07-20 15:47] upgraded freeciv (2.1.9-1 -> 2.1.9-2)
[2009-07-20 15:47] upgraded gcc (4.4.0-3 -> 4.4.0-5)
[2009-07-20 15:47] upgraded gd (2.0.35-1 -> 2.0.35-2)
[2009-07-20 15:47] upgraded gedit (2.26.2-1 -> 2.26.3-1)
[2009-07-20 15:47] upgraded gegl (0.0.22-1 -> 0.0.22-2)
[2009-07-20 15:47] upgraded gimp (2.6.6-1 -> 2.6.6-2)
[2009-07-20 15:47] upgraded gimp-ufraw (0.15-2 -> 0.15-4)
[2009-07-20 15:47] upgraded glade (3.6.5-2 -> 3.6.7-1)
[2009-07-20 15:47] upgraded glib-perl (1.221-1 -> 1.222-1)
[2009-07-20 15:47] upgraded glibmm (2.20.0-1 -> 2.20.1-1)
[2009-07-20 15:47] upgraded gmerlin (0.4.0-4 -> 0.4.0-5)
[2009-07-20 15:47] upgraded gnome-desktop (2.26.2-1 -> 2.26.3-1)
[2009-07-20 15:47] upgraded gnome-menus (2.26.1-1 -> 2.26.2-1)
[2009-07-20 15:47] upgraded libwnck (2.26.1-1 -> 2.26.2-1)
[2009-07-20 15:47] upgraded gnome-panel (2.26.2-1 -> 2.26.3-1)
[2009-07-20 15:48] upgraded gnome-themes (2.26.2-1 -> 2.26.3.1-1)
[2009-07-20 15:48] upgraded gnupg (1.4.9-1 -> 1.4.9-4)
[2009-07-20 15:48] upgraded gnupg2 (2.0.11-1 -> 2.0.12-1)
[2009-07-20 15:48] upgraded libxaw (1.0.5-1 -> 1.0.6-1)
[2009-07-20 15:48] upgraded graphviz (2.22.2-1.1 -> 2.22.2-2)
[2009-07-20 15:48] upgraded grep (2.5.4-2 -> 2.5.4-3)
[2009-07-20 15:48] upgraded gstreamer0.10-good-plugins (0.10.15-1 -> 0.10.15-2)
[2009-07-20 15:48] upgraded gtk-recordmydesktop (0.3.8-1 -> 0.3.8-2)
[2009-07-20 15:48] upgraded gtk2-perl (1.220-1 -> 1.221-1)
[2009-07-20 15:48] upgraded guile (1.8.6-1 -> 1.8.7-1)
[2009-07-20 15:48] >>please run /usr/sbin/cups-genppdupdate
[2009-07-20 15:48] >>and restart cups deamon
[2009-07-20 15:48] upgraded gutenprint (5.2.3-1 -> 5.2.3-3)
[2009-07-20 15:48]
[2009-07-20 15:48] NOTE
[2009-07-20 15:48] ----
[2009-07-20 15:48] # If you want to use this driver with sane:
[2009-07-20 15:48] # echo "hpaio" >> /etc/sane.d/dll.conf
[2009-07-20 15:48]
[2009-07-20 15:48]
[2009-07-20 15:48] UPGRADING
[2009-07-20 15:48] ----
[2009-07-20 15:48] # This version no longer uses an init script. You should remove hplip
[2009-07-20 15:48] # from the /etc/rc.conf daemon list.
[2009-07-20 15:48]
[2009-07-20 15:48] upgraded hplip (3.9.4b-1 -> 3.9.4b-2)
[2009-07-20 15:48] upgraded htmldoc (1.8.27-1 -> 1.8.27-2)
[2009-07-20 15:48] upgraded libpano13 (2.9.12-1 -> 2.9.12-2)
[2009-07-20 15:48] upgraded hugin (0.7.0-4 -> 0.7.0-5)
[2009-07-20 15:48] upgraded hwdetect (2009.06-1 -> 2009.07-1)
[2009-07-20 15:48] upgraded icu (4.2-1 -> 4.2.1-1)
[2009-07-20 15:48] upgraded imlib (1.9.15-5 -> 1.9.15-6)
[2009-07-20 15:48] upgraded inkscape (0.46-11 -> 0.46-12)
[2009-07-20 15:48] upgraded iptables (1.4.3.2-1 -> 1.4.4-1)
[2009-07-20 15:48] upgraded iw (0.9.14-1 -> 0.9.15-1)
[2009-07-20 15:48] upgraded iwlwifi-4965-ucode (228.57.2.23-1 -> 228.61.2.24-1)
[2009-07-20 15:48] > Rebuilding xdg icon database ... DONE
[2009-07-20 15:48] upgraded kdemod-kdebase-runtime (4.2.4-1 -> 4.2.4-3)
[2009-07-20 15:48] > Rebuilding xdg icon database ... DONE
[2009-07-20 15:48] upgraded kdemod-kdebase (4.2.4-1 -> 4.2.4-3)
[2009-07-20 15:49] upgraded kdemod-kdebase-doc (4.2.4-1 -> 4.2.4-3)
[2009-07-20 15:49] > Rebuilding xdg icon database ... DONE
[2009-07-20 15:49] upgraded kdemod-kdebase-konsole (4.2.4-1 -> 4.2.4-3)
[2009-07-20 15:49] > Rebuilding xdg icon database ... DONE
[2009-07-20 15:49] upgraded kdemod-kdebase-kwrite (4.2.4-1 -> 4.2.4-3)
[2009-07-20 15:49] upgraded kdemod-kdebase-runtime-doc (4.2.4-1 -> 4.2.4-3)
[2009-07-20 15:49] > Rebuilding xdg icon database ... DONE
[2009-07-20 15:49] upgraded kdemod-kdebase-runtime-icons (4.2.4-1 -> 4.2.4-3)
[2009-07-20 15:49] > Rebuilding xdg icon database ... DONE
[2009-07-20 15:49] upgraded kdemod-kdebase-workspace (4.2.4-1 -> 4.2.4-3)
[2009-07-20 15:49] upgraded kdemod-kdebase-workspace-doc (4.2.4-1 -> 4.2.4-3)
[2009-07-20 15:49] upgraded kdemod-kdebase-workspace-wallpapers (4.2.4-1 -> 4.2.4-3)
[2009-07-20 15:49] upgraded kdemod-kdegraphics-doc (4.2.4-1 -> 4.2.4-3)
[2009-07-20 15:49] > Rebuilding xdg icon database ... DONE
[2009-07-20 15:49] upgraded kdemod-kdegraphics-gwenview (4.2.4-1 -> 4.2.4-3)
[2009-07-20 15:49] > Rebuilding xdg icon database ... DONE
[2009-07-20 15:49] upgraded kdemod-kdegraphics-kamera (4.2.4-1 -> 4.2.4-3)
[2009-07-20 15:49] > Rebuilding xdg icon database ... DONE
[2009-07-20 15:49] upgraded kdemod-kdegraphics-kcolorchooser (4.2.4-1 -> 4.2.4-3)
[2009-07-20 15:49] > Rebuilding xdg icon database ... DONE
[2009-07-20 15:49] upgraded kdemod-kdegraphics-kolourpaint (4.2.4-1 -> 4.2.4-3)
[2009-07-20 15:49] > Rebuilding xdg icon database ... DONE
[2009-07-20 15:49] upgraded kdemod-kdegraphics-kruler (4.2.4-1 -> 4.2.4-3)
[2009-07-20 15:49] > Rebuilding xdg icon database ... DONE
[2009-07-20 15:49] upgraded kdemod-kdegraphics-ksnapshot (4.2.4-1 -> 4.2.4-3)
[2009-07-20 15:49] upgraded libdjvu (3.5.22-1 -> 3.5.22-2)
[2009-07-20 15:49] > Rebuilding xdg icon database ... DONE
[2009-07-20 15:49] upgraded kdemod-kdegraphics-okular (4.2.4-1 -> 4.2.4-3)
[2009-07-20 15:49] > Rebuilding xdg icon database ... DONE
[2009-07-20 15:49] upgraded kdemod-kdenetwork-common (4.2.4-1 -> 4.2.4-2)
[2009-07-20 15:49] upgraded kdemod-kdenetwork-doc (4.2.4-1 -> 4.2.4-2)
[2009-07-20 15:49] > Rebuilding xdg icon database ... DONE
[2009-07-20 15:49] upgraded kdemod-kdenetwork-kget (4.2.4-1 -> 4.2.4-2)
[2009-07-20 15:49] > Rebuilding xdg icon database ... DONE
[2009-07-20 15:49] upgraded kdemod-kdenetwork-kopete (4.2.4-1 -> 4.2.4-2)
[2009-07-20 15:49] upgraded ppp (2.4.4-8 -> 2.4.4-9)
[2009-07-20 15:49] > Rebuilding xdg icon database ... DONE
[2009-07-20 15:49] upgraded kdemod-kdenetwork-kppp (4.2.4-1 -> 4.2.4-2)
[2009-07-20 15:49] upgraded libvncserver (0.9.7-1 -> 0.9.7-2)
[2009-07-20 15:49] > Rebuilding xdg icon database ... DONE
[2009-07-20 15:49] upgraded kdemod-kdenetwork-krdc (4.2.4-1 -> 4.2.4-2)
[2009-07-20 15:49] > Rebuilding xdg icon database ... DONE
[2009-07-20 15:49] upgraded kdemod-kdenetwork-krfb (4.2.4-1 -> 4.2.4-2)
[2009-07-20 15:50] >>> Updating module dependencies. Please wait ...
[2009-07-20 15:50] >>> MKINITCPIO SETUP
[2009-07-20 15:50] >>> ----------------
[2009-07-20 15:50] >>> If you use LVM2, Encrypted root or software RAID,
[2009-07-20 15:50] >>> Ensure you enable support in /etc/mkinitcpio.conf .
[2009-07-20 15:50] >>> More information about mkinitcpio setup can be found here:
[2009-07-20 15:50] >>> http://wiki.archlinux.org/index.php/Mkinitcpio
[2009-07-20 15:50]
[2009-07-20 15:50] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2009-07-20 15:50] ==> Building image "default"
[2009-07-20 15:50] ==> Running command: /sbin/mkinitcpio -k 2.6.30-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
[2009-07-20 15:50] :: Begin build
[2009-07-20 15:50] :: Parsing hook [base]
[2009-07-20 15:50] :: Parsing hook [udev]
[2009-07-20 15:50] :: Parsing hook [autodetect]
[2009-07-20 15:51] :: Parsing hook [pata]
[2009-07-20 15:51] :: Parsing hook [scsi]
[2009-07-20 15:51] :: Parsing hook [sata]
[2009-07-20 15:51] :: Parsing hook [filesystems]
[2009-07-20 15:51] :: Generating module dependencies
[2009-07-20 15:51] :: Generating image '/boot/kernel26.img'...SUCCESS
[2009-07-20 15:51] ==> SUCCESS
[2009-07-20 15:51] ==> Building image "fallback"
[2009-07-20 15:51] ==> Running command: /sbin/mkinitcpio -k 2.6.30-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26-fallback.img -S autodetect
[2009-07-20 15:51] :: Begin build
[2009-07-20 15:51] :: Parsing hook [base]
[2009-07-20 15:51] :: Parsing hook [udev]
[2009-07-20 15:51] :: Parsing hook [pata]
[2009-07-20 15:51] :: Parsing hook [scsi]
[2009-07-20 15:51] :: Parsing hook [sata]
[2009-07-20 15:51] :: Parsing hook [filesystems]
[2009-07-20 15:51] :: Generating module dependencies
[2009-07-20 15:51] :: Generating image '/boot/kernel26-fallback.img'...SUCCESS
[2009-07-20 15:51] ==> SUCCESS
[2009-07-20 15:51] upgraded kernel26 (2.6.30-5 -> 2.6.30.1-1)
[2009-07-20 15:51] upgraded kismet (2008_05_R1-4 -> 2008_05_R1-5)
[2009-07-20 15:51] upgraded lib32-cairo (1.8.6-1 -> 1.8.8-1)
[2009-07-20 15:51] upgraded lib32-glibc (2.10.1-2 -> 2.10.1-3)
[2009-07-20 15:51] upgraded lib32-e2fsprogs (1.41.6-1 -> 1.41.8-1)
[2009-07-20 15:51] upgraded lib32-gcc-libs (4.4.0-3 -> 4.4.0-5)
[2009-07-20 15:51] upgraded lib32-glib2 (2.20.3-1 -> 2.20.4-1)
[2009-07-20 15:51] upgraded lib32-readline (5.2.013-2 -> 6.0.003-1)
[2009-07-20 15:51] upgraded lib32-gnutls (2.8.0-1 -> 2.8.1-1)
[2009-07-20 15:51] upgraded lib32-openssl (0.9.8k-2 -> 0.9.8k-4)
[2009-07-20 15:51] upgraded lib32-heimdal (1.2.1-3 -> 1.2.1-5)
[2009-07-20 15:51] upgraded lib32-libjpeg (6b-6 -> 7-1)
[2009-07-20 15:51] upgraded lib32-libtiff (3.8.2-4 -> 3.8.2-5)
[2009-07-20 15:51] upgraded lib32-libcups (1.3.10-2 -> 1.3.11-1)
[2009-07-20 15:51] upgraded lib32-pango (1.24.2-1 -> 1.24.4-2)
[2009-07-20 15:51] upgraded lib32-gtk2 (2.16.2-1 -> 2.16.5-1)
[2009-07-20 15:51] upgraded lib32-libdrm (2.4.11-2 -> 2.4.12-1)
[2009-07-20 15:51] upgraded lib32-libgcrypt (1.4.4-1 -> 1.4.4-2)
[2009-07-20 15:51] upgraded lib32-libgl (7.4.2-2 -> 7.4.4-1)
[2009-07-20 15:51] upgraded lib32-libxml2 (2.7.3-1 -> 2.7.3-2)
[2009-07-20 15:51] upgraded lib32-libxt (1.0.5-2 -> 1.0.6-1)
[2009-07-20 15:51] upgraded lib32-mesa (7.4.2-1 -> 7.4.4-1)
[2009-07-20 15:51] upgraded lib32-sqlite3 (3.6.15-1 -> 3.6.15-2)
[2009-07-20 15:51] upgraded libcanberra (0.12-1 -> 0.14-1)
[2009-07-20 15:51] upgraded libevent (1.4.10-1 -> 1.4.11-1)
[2009-07-20 15:51] upgraded libgdiplus (2.4-1 -> 2.4.2-1)
[2009-07-20 15:51] upgraded libquicktime (1.1.1-3 -> 1.1.1-4)
[2009-07-20 15:52] upgraded libwebkit (1.1.10-1 -> 1.1.10-2)
[2009-07-20 15:52] upgraded links-g (2.2-1 -> 2.2-2)
[2009-07-20 15:52] upgraded lvm2 (2.02.47-1 -> 2.02.48-1)
[2009-07-20 15:52] upgraded mercurial (1.2.1-1 -> 1.3-3)
[2009-07-20 15:52] upgraded mtools (4.0.10-2 -> 4.0.10-3)
[2009-07-20 15:52] upgraded mutagen (1.15-1 -> 1.16-1)
[2009-07-20 15:52] upgraded namcap (2.2-2 -> 2.3-1)
[2009-07-20 15:52] upgraded nautilus-cd-burner (2.24.0-1 -> 2.24.0-2)
[2009-07-20 15:52] upgraded ncmpcpp (0.3.4-1 -> 0.3.5-1)
[2009-07-20 15:52] upgraded wpa_supplicant (0.6.9-1 -> 0.6.9-2)
[2009-07-20 15:52] upgraded netcfg (2.1.3-3 -> 2.2.1-1)
[2009-07-20 15:52] upgraded neverball (1.5.1-1 -> 1.5.1-2)
[2009-07-20 15:52] upgraded nmap (4.76-4 -> 5.00-1)
[2009-07-20 15:52] upgraded openmovieeditor (0.0.20090105-3 -> 0.0.20090105-4)
[2009-07-20 15:52] * relogin or source /etc/profile.d/openoffice.sh
[2009-07-20 15:52] * see http://wiki.archlinux.org/index.php/Openoffice
[2009-07-20 15:52] how to use extensions, e.g. for spell checking
[2009-07-20 15:52] see /opt/openoffice/share/extension/install what
[2009-07-20 15:52] is shipped with this package
[2009-07-20 15:52] upgraded openoffice-base (3.1.0-2 -> 3.1.0-5)
[2009-07-20 15:52] upgraded parted (1.8.8-2 -> 1.8.8-3)
[2009-07-20 15:52] upgraded pcmanfm (0.5.1-1 -> 0.5.1-2)
[2009-07-20 15:52] upgraded perl-html-parser (3.60-1 -> 3.61-1)
[2009-07-20 15:52] upgraded perl-uri (1.37-1 -> 1.38-1)
[2009-07-20 15:52] upgraded perl-libwww (5.825-1 -> 5.829-1)
[2009-07-20 15:52] upgraded postgresql-libs (8.3.7-1 -> 8.3.7-2)
[2009-07-20 15:52] upgraded pgadmin3 (1.10.0beta3-1 -> 1.10.0-1)
[2009-07-20 15:52] upgraded pil (1.1.6-5 -> 1.1.6-6)
[2009-07-20 15:52] upgraded pilot-link (0.12.3-4 -> 0.12.3-5)
[2009-07-20 15:52] upgraded poppler (0.10.7-1 -> 0.10.7-2)
[2009-07-20 15:52] upgraded postgresql (8.3.7-2 -> 8.3.7-3)
[2009-07-20 15:52] upgraded pycairo (1.8.4-1 -> 1.8.6-1)
[2009-07-20 15:52] upgraded qingy (0.9.9-1 -> 0.9.9-2)
[2009-07-20 15:52] upgraded qt3 (3.3.8-11 -> 3.3.8-12)
[2009-07-20 15:52] upgraded ruby (1.8.7_p173-1 -> 1.8.7_p174-1)
[2009-07-20 15:52] upgraded ruby-libart (0.18.1-1 -> 0.19.0-2)
[2009-07-20 15:52] upgraded samba (3.3.6-1 -> 3.3.6-2)
[2009-07-20 15:52] upgraded sdl_image (1.2.7-1 -> 1.2.7-2)
[2009-07-20 15:52] upgraded sauerbraten (2008_06_20_ctf_edition-1 -> 2009_05_04_trooper_edition-1)
[2009-07-20 15:52] upgraded sdl_perl (2.1.3-4 -> 2.1.3-5)
[2009-07-20 15:52] Fixing gshadow file ...
[2009-07-20 15:52] upgraded shadow (4.1.3.1-1 -> 4.1.4.1-1)
[2009-07-20 15:52] upgraded silly (0.1.0-2 -> 0.1.0-3)
[2009-07-20 15:52] upgraded smc (1.8-1 -> 1.8-2)
[2009-07-20 15:52] upgraded source-highlight (3.1-1 -> 3.1-2)
[2009-07-20 15:52] warning: extracting /etc/sudoers as /etc/sudoers.pacnew
[2009-07-20 15:52] upgraded sudo (1.7.1-2 -> 1.7.2-1)
[2009-07-20 15:52] upgraded sunbird (0.9-1 -> 0.9-2)
[2009-07-20 15:52] upgraded swftools (0.9.0-1 -> 0.9.0-2)
[2009-07-20 15:52] upgraded syslog-ng (3.0.1-6 -> 3.0.3-1)
[2009-07-20 15:52] upgraded texlive-bin (2008-4 -> 2008-5)
[2009-07-20 15:52] upgraded tftp-hpa (5.0-2 -> 5.0-3)
[2009-07-20 15:52] upgraded thunar (1.0.1-1 -> 1.0.1-4)
[2009-07-20 15:53] upgraded thunderbird (2.0.0.21-1 -> 2.0.0.22-1)
[2009-07-20 15:53] upgraded tightvnc (1.3.10-1 -> 1.3.10-2)
[2009-07-20 15:53] upgraded transcode (1.1.0-5 -> 1.1.3-1)
[2009-07-20 15:53] upgraded transmission-gtk (1.60-1 -> 1.72-1)
[2009-07-20 15:53] upgraded usbutils (0.82-1 -> 0.84-1)
[2009-07-20 15:53] installed libmtp (0.3.7-1)
[2009-07-20 15:53] installed enca (1.9-4)
[2009-07-20 15:53] installed libass (0.9.6-2)
[2009-07-20 15:53] upgraded vlc (0.9.9a-5 -> 1.0.0-5)
[2009-07-20 15:53] upgraded xfce4-clipman-plugin (1.0.1-1 -> 1.0.2-1)
[2009-07-20 15:53] upgraded xfce4-power-manager (0.8.0-1 -> 0.8.2-1)
[2009-07-20 15:53] upgraded xine-ui (0.99.5-4 -> 0.99.5-5)
[2009-07-20 15:53] upgraded xmlrpc-c (1.06.33-1 -> 1.06.35-1)
[2009-07-20 15:53] upgraded xorg-server (1.6.1.901-3 -> 1.6.2-1)
[2009-07-20 15:53] upgraded xz-utils (4.999.8beta-3 -> 4.999.8beta-4)
[2009-07-20 16:08] upgraded codecs (20071007-4 -> 20071007-6)
[2009-07-20 16:09] upgraded muttprint (0.72d-8 -> 0.72d-9)
[2009-07-20 16:11] upgraded openvpn-dev (2.1_rc15-2 -> 2.1_rc18-2)
[2009-07-20 16:11] upgraded perl-xyne-arch (0.66-1 -> 0.68-2)
[2009-07-20 16:11] installed rpmextract (1.0-3)
[2009-07-20 16:14] Before using picasa you must accept the license.
[2009-07-20 16:14] The license files are located in /usr/share/licences/picasa/
[2009-07-20 16:14]
[2009-07-20 16:14] NOTE:
[2009-07-20 16:14] If you're not running gnome/kde please look at the hook files
[2009-07-20 16:14] located in /opt/picasa/info.
[2009-07-20 16:14] Edit them for your default filemanager/browser/email/mime-handling,
[2009-07-20 16:14] and copy them to /opt/picasa/bin.
[2009-07-20 16:14] If you're a gnome/kde user you should not modify these files.
[2009-07-20 16:14] Picasa will use your default DE settings.
[2009-07-20 16:14]
[2009-07-20 16:14] upgraded picasa-beta (3.0_5744.02-1 -> 3.0_5744.02-3)
[2009-07-20 16:14] upgraded powerpill (16.0-11 -> 16.0-12)
[2009-07-20 16:24] synchronizing package lists
[2009-07-20 16:24] starting full system upgrade
[2009-07-20 16:25] upgraded lib32-libgl (7.4.4-1 -> 7.5-1)
[2009-07-20 16:25] upgraded lib32-libpng (1.2.37-1 -> 1.2.38-1)
[2009-07-20 16:25] upgraded lib32-mesa (7.4.4-1 -> 7.5-1)
[2009-07-20 16:25] synchronizing package lists
[2009-07-20 16:25] starting full system upgrade
[2009-07-20 16:28] update desktop mime database... done
[2009-07-20 16:28] update desktop applications database... done
[2009-07-20 16:28] upgraded xaralx (0.7r1785-3 -> 0.7r1785-5)
any suggestions on how to get more info?
thanks
Last edited by webframp (2009-07-21 18:32:58)

That does appear to be my issue, I use jfs with no separate /boot
Edit:
The following steps fixed it:
Mount your / (and /boot partition into this mount) from your Ach system, ex:
sda2 (/) -> /mnt/arch
sda1 (/boot)(if you have a own /boot) -> /mnt/arch/boot
Do a chroot /mnt
and therein a:
pacman -U /var/cache/pacman/pkg/kernel26-2.6.30.1-1-x86_64.pkg.tar.gz (or i686)
further details at the link above.
Last edited by webframp (2009-07-21 18:32:14)

[Solved] Udev hangs on boot after update

I don't know exactly what was updated that caused the problem, but udev hanged my computer whenever I tried to start it up. My solution consists of
hwdetect --modules >> rc.conf
from the live disk, and setting MOD_AUTOLOAD="no". But it's only temporary, and some modules aren't loaded properly because now my joysticks and USB sticks don't work. How can I find the problematic module and blacklist it so I can let udev do its thing again?
Last edited by Dren (2011-03-05 18:07:08)

[2011-02-25 20:38] Running 'pacman -Syu'
[2011-02-25 20:38] synchronizing package lists
[2011-02-25 20:38] starting full system upgrade
[2011-02-25 20:42] Generating locales...
[2011-02-25 20:42] en_US.UTF-8... done
[2011-02-25 20:42] en_US.ISO-8859-1... done
[2011-02-25 20:42] Generation complete.
[2011-02-25 20:42] upgraded glibc (2.13-3 -> 2.13-4)
[2011-02-25 20:42] upgraded aalib (1.4rc5-7 -> 1.4rc5-8)
[2011-02-25 20:42] upgraded alsa-lib (1.0.23-2 -> 1.0.24.1-1)
[2011-02-25 20:42] upgraded alsa-utils (1.0.23-3 -> 1.0.24.2-1)
[2011-02-25 20:42] upgraded bluez (4.88-1 -> 4.89-1)
[2011-02-25 20:42] upgraded chromium (9.0.597.94-1 -> 9.0.597.94-2)
[2011-02-25 20:42] upgraded curl (7.21.3-1 -> 7.21.4-2)
[2011-02-25 20:42] upgraded librsvg (2.32.1-1 -> 2.32.1-2)
[2011-02-25 20:42] upgraded eina-svn (56713-1 -> 57312-1)
[2011-02-25 20:42] upgraded eet-svn (56702-1 -> 57246-1)
[2011-02-25 20:42] installed fribidi (0.19.2-1)
[2011-02-25 20:42] upgraded evas-svn (56688-1 -> 57308-1)
[2011-02-25 20:42] upgraded ecore-svn (56689-1 -> 57310-1)
[2011-02-25 20:42] upgraded efreet-svn (56699-1 -> 57257-1)
[2011-02-25 20:42] upgraded e_dbus-svn (56607-1 -> 57246-1)
[2011-02-25 20:42] upgraded embryo-svn (56690-1 -> 57246-1)
[2011-02-25 20:42] upgraded edje-svn (56672-1 -> 57299-1)
[2011-02-25 20:42] upgraded udev (165-1 -> 166-2)
[2011-02-25 20:42] installed eeze-svn (57232-1)
[2011-02-25 20:42] upgraded e-svn (56715-1 -> 57289-1)
[2011-02-25 20:42] upgraded emprint-svn (54305-1 -> 57150-1)
[2011-02-25 20:42] upgraded e-modules-extra-svn (56389-1 -> 57316-1)
[2011-02-25 20:42] upgraded gegl (0.1.4-1 -> 0.1.6-1)
[2011-02-25 20:42] upgraded vim-runtime (7.3.102-1 -> 7.3.125-1)
[2011-02-25 20:42] upgraded ruby (1.9.2_p136-2 -> 1.9.2_p180-1)
[2011-02-25 20:42] Updating desktop and mime database...done.
[2011-02-25 20:42] upgraded gvim (7.3.102-1 -> 7.3.125-1)
[2011-02-25 20:42] >>> Updating module dependencies. Please wait ...
[2011-02-25 20:42] >>> MKINITCPIO SETUP
[2011-02-25 20:42] >>> ----------------
[2011-02-25 20:42] >>> If you use LVM2, Encrypted root or software RAID,
[2011-02-25 20:42] >>> Ensure you enable support in /etc/mkinitcpio.conf .
[2011-02-25 20:42] >>> More information about mkinitcpio setup can be found here:
[2011-02-25 20:42] >>> http://wiki.archlinux.org/index.php/Mkinitcpio
[2011-02-25 20:42]
[2011-02-25 20:42] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2011-02-25 20:42] ==> Building image "default"
[2011-02-25 20:42] ==> Running command: /sbin/mkinitcpio -k 2.6.37-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
[2011-02-25 20:42] :: Begin build
[2011-02-25 20:42] :: Parsing hook [base]
[2011-02-25 20:42] :: Parsing hook [udev]
[2011-02-25 20:42] :: Parsing hook [autodetect]
[2011-02-25 20:42] :: Parsing hook [pata]
[2011-02-25 20:42] :: Parsing hook [scsi]
[2011-02-25 20:43] :: Parsing hook [sata]
[2011-02-25 20:43] :: Parsing hook [filesystems]
[2011-02-25 20:43] :: Parsing hook [resume]
[2011-02-25 20:43] :: Generating module dependencies
[2011-02-25 20:43] :: Generating image '/boot/kernel26.img'...SUCCESS
[2011-02-25 20:43] ==> SUCCESS
[2011-02-25 20:43] ==> Building image "fallback"
[2011-02-25 20:43] ==> Running command: /sbin/mkinitcpio -k 2.6.37-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26-fallback.img -S autodetect
[2011-02-25 20:43] :: Begin build
[2011-02-25 20:43] :: Parsing hook [base]
[2011-02-25 20:43] :: Parsing hook [udev]
[2011-02-25 20:43] :: Parsing hook [pata]
[2011-02-25 20:43] :: Parsing hook [scsi]
[2011-02-25 20:43] :: Parsing hook [sata]
[2011-02-25 20:43] :: Parsing hook [filesystems]
[2011-02-25 20:44] :: Parsing hook [resume]
[2011-02-25 20:44] :: Generating module dependencies
[2011-02-25 20:44] :: Generating image '/boot/kernel26-fallback.img'...SUCCESS
[2011-02-25 20:44] ==> SUCCESS
[2011-02-25 20:44] upgraded kernel26 (2.6.37-6 -> 2.6.37.1-1)
[2011-02-25 20:44] upgraded kernel26-headers (2.6.37-6 -> 2.6.37.1-1)
[2011-02-25 20:44] upgraded leafpad (0.8.18.1-1 -> 0.8.18.1-2)
[2011-02-25 20:44] upgraded libao (1.0.0-5 -> 1.1.0-1)
[2011-02-25 20:44] upgraded libfm (0.1.14-2 -> 0.1.14-4)
[2011-02-25 20:44] upgraded libldap (2.4.23-1 -> 2.4.24-1)
[2011-02-25 20:44] upgraded libwpd (0.9.0-1 -> 0.9.1-1)
[2011-02-25 20:44] upgraded lsof (4.84-1 -> 4.84-2)
[2011-02-25 20:44] upgraded mplayer (32792-1 -> 32792-2)
[2011-02-25 20:44] upgraded pcmanfm (0.9.8-2 -> 0.9.8-5)
[2011-02-25 20:44] upgraded ppp (2.4.5-1 -> 2.4.5-2)
[2011-02-25 20:44] upgraded python-imaging (1.1.7-2 -> 1.1.7-3)
[2011-02-25 20:44] upgraded redland (1.0.12-4 -> 1.0.12-5)
[2011-02-25 20:44] warning: /etc/sane.d/dll.conf installed as /etc/sane.d/dll.conf.pacnew
[2011-02-25 20:44] upgraded sane (1.0.21-4 -> 1.0.22-1)
[2011-02-25 20:44] upgraded totem-plparser (2.32.2-1 -> 2.32.3-1)
[2011-02-25 20:44] upgraded wget (1.12-3 -> 1.12-5)

[SOLVED] alsactl FAIL in boot.

Hi, today when I started the laptop I don't have sound on my laptop and I rebooted. When the operative system was loading ALSA show the next error:
alsactl: load_state:1625: No soundcards found...
[FAIL]
Somebody can help me with the problem?
My sound card is a Intel integrated. I'm use Gnome 3 desktop environment. Since I installed Arch Linux I haven't had any problems with audio, only today.
Thanks and regards.
Last edited by surrealistic (2011-09-21 18:11:15)

I too have occassionally encountered alsactl issues upon booting after an upgrade. It seems on occassion the asound.state file gets corrupted during an update of some kind.
The solution is simple. Re-create your asound.state file.
# alsamixer
Re-set your default volume levels.
# alsactl -f /var/lib/alsa/asound.state store
Settings have now been saved.
# alsactl -f /var/lib/alsa/asound.state restore
Tests to ensure the file is valid and can be loaded.
Providing you do not get any errors here, all should now be well!
Cheers.

[SOLVED] - UDev errors on boot after XFCE4 and goodies installation

I'm getting errors at "Waiting for UDev events to be processed". things are being "terminated by signal 9". I have a feeling that I set something up incorrectly, but I have no idea where to start looking. I think of this mostly as a learning experience, so just point me in the right direction. If I get stuck again, I'll come back to the thread. I'll also post my progress here. I've also done a search on here looking for UDev errors associated with XFCE. I have yet to read all of the threads that turned up, but I'm working on it. Thanks for your help ahead of time.
Last edited by brainard52 (2012-04-18 23:08:07)

Well, now I feel silly. I guess it's here for future reference, though. I had a bad udev rule, so I deleted it and we're good now.

[SOLVED] Arch Linux Duke (2007) Fails to Boot

Folks, I have a unique and challenging problem that has exhausted my Arch Linux skills, and so I am now turning to you.
I have a vintage Pentium Pro 200 system (that’s 200 MHz folks! – 200 MHz 686 architecture – the original 686!), two CPUs, running a dual boot between Windows NT 4.0 and Arch Linux Duke (2007). It has 512 MB of RAM and a 120 GB hard drive, partitioned up between Windows NT and Linux. I built this system new in 2007, hence the dated version of Arch. It has run like a charm all these years, granted not getting that much use. After about a year of no use at all, I fired the system up last week to help with a little research for a blog post I was writing on networking Windows NT 4.0 and Mac OS 8.6. Windows NT 4.0 fired right up with no issue, and after I was done testing what needed to be tested I tried to boot over to Arch.
After a year of disuse, Arch unexpectedly and stubbornly refused to boot. The boot process started up just fine, but towards the end, it declared that it could not mount the root file system on the root device and took a kernel panic and stopped. My Arch skills have gotten a bit rusty in the last few years, but I dusted them off and went to work. My guess was a file system or superblock error. Arch wouldn’t boot, but I dragged out my trusty RIPLinux 2.9 Rescue Live CD and fired it up. It came right up and ran, and I was able to mount the Arch partition and view all the files… everything seemed to be there; it just wouldn’t boot. Windows NT 4.0 AND RIPLinux both boot and run on the machine, so the hardware is fine as well.
A little information on the disk layout. Windows NT 4.0 is in the first partition on the hard drive. The extended partition has a second Windows NT 4.0 partition (sort of a /home partition for Windows NT 4.0), followed by the main Arch partition (the one I am trying to boot), followed by a swap partition and then the largest partition, which I use to share data between Arch and Windows NT 4.0 (I have loaded an ext2/3 driver into Windows NT 4.0 and it happily accesses the Linux partitions on the box).
RIPLinux’s e2fsck did find some issues with the Arch partition and I had it repair them all. I checked again afterwards that all the files were still there, and they were. With the partition now known to be clean, and the superblock repaired from one of the backups, all should have been well. However, Arch still wouldn’t (and still won’t) boot.
RIPLinux has a kind of a chain loader function, so I had it attempt to start up Arch for me. However, this was flummoxed by the fact that Arch addresses all my hard drive partitions as /dev/sdax and RIPLinux addresses them as /dev/hdax. Hence, without a common language, it was hard to get the one to start the other. Still, using this function, I have been able to get a crippled version of Arch running on the machine again. No modules had been loaded, and so it couldn’t do almost anything, but there it was (and is), Arch Linux Duke, at the CLI level. From there, I can see all the files, I can move freely in and out of my user account and the root account, but I can’t make the thing actually boot properly.
If you have read this far, you are a trooper. Summarizing what I know, the hardware is good, the file system is clean, the superblock is good, I can mount it cleanly from a live CD and I can chain load a crippled version of Arch. Here is the boot process blow-by-blow. When I try to do a normal boot, the Windows NT 4.0 loader passes control to the Lilo boot sector I have placed on hda1 (sda1 in Duke’s parlance). Lilo takes over, present a menu and when I select Duke, takes off. Arch Linux Duke starts to boot. It gets a good long way along, all the way along to:
:: Loading udev events [Pass]
:: Mount root Read-only
:: Checking file systems
This is where it stops.
The next thing I see is:
/dev/sda6
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else) then the superblock is corrupt and you might try running e2fsck with an alternate superblock:
E2fsck –b 8193 <device>
I then get a sort of character based splash screen that says
**********FILE SYSTEM CHECK FAILED ****************************
* Please repair manually and reboot. Note that the root file system
* is currently mounted read-only. To remount it read-write, type:
* mount –n –o remount,rw /. When you exit the maintenance
* shell, the system will reboot automatically
Give root password for maintenance
At this point, I give the root password and enter the maintenance shell as root. I typed in “mount” and the first entry I got back is
/dev/sda6 on / type ext3 (rw)
This is exactly the root partition that the start up complains about. It is clearly there. I can see it, I can walk around it… it is clearly there. Why won’t it boot? Despite the message, the superblock is fine – it passes every test e2fsck can throw at it.
At this point, I did a “e2fsck /dev/hda6 (which is how RIPLinux would have passed it into Arch” and it says it is “clean”. I suspect that the Superblock message is because Arch sees root as sda6, while RIP passed it in as hda6...
Deciding to see what Arch would be seeing as it tried to set things up in the boot sequence, I tried the following next:
# mknod “/dev/root2” b 3 6
(“3” because RIPLinux refers to my hard drive as IDE, while Arch refers to it by major number “8”, which is SCSI. By the way, it IS an IDE drive – not sure why Arch insists on using the sdx nomenclature instead of hdx)
Then I entered “mount /dev/root2 /mnt/hda6” and “ls /mnt/hda6”
All was well. I can make the node, I can mount it, and I can see the contents. All is clearly well, but something is clearly wrong enough that Arch can’t boot.
I am totally out of ideas. I have tried every trick I know and am out of tricks. I would welcome any insights as to what I could try to get this venerable Arch installation back on its legs.
By the way, the key section of the /etc/lilo.conf file (lest anyone want to know) is:
image = /boot/vmlinuz26
root = /dev/sda6
label = ArchLinux-Duke
initrd = /boot/kernel26.img
read-only
I am stumped. Thanks in advance for any and all pointers you may be able to offer.
Last edited by mac57 (2014-06-02 17:42:21)

Folks, thanks for all your helpful comments, and I wanted to report back to you that I finally overcame the issue, and ArchLinux-Duke (2007) is once again executing flawlessly on my old Pentium Pro 200 system. I won't bother reporting here all the blind allies I went down as I tried to figure out what was wrong, but in the end, literally moments before I was about to give up and overwrite my Arch installation with a new Linux variant (antiX seemed well suited for such old and low power hardware), my attention was drawn to a note I had made in my files back in 2007 about a problem with similar symptoms. In that case, I had just deleted ZenWalk Linux from the hard drive (both Arch and Zen had been on the drive), and merged several partitions to make use of the newly free space. This had changed Arch's view of the drive lettering, and what had been its /dev/sddx root device was now /dev/sdcx. Arch failed to boot, throwing off the same errors I was seeing now. I wish I had recalled that note a month or so ago! It would have saved me a lot of work and a lot of frustration.
At any rate, as a last step, and testing the idea that maybe the drive lettering had changed for some reason, I repeatedly manually booted Arch, specifying root=/dev/sda6, then /dev/sdb6, then /dev/sdd6, and finally, /dev/sdc6. Eureka! Arch now considered itself to be on /dev/sdc6 whereas previously it had been on /dev/sda6. This got me part way there, but the boot failed at the filesystem check stage and threw me into root. I disabled the file system check in /etc/rc.sysinit and got farther. Then I cleaned up /etc/fstab to agree with the new sdc naming, and I was back on the air fully.
So, what had happened was that Arch had changed its view of the drive it was on from sda6 to sdc6. While I could not understand why this "sudden" change had occurred, at least I had a solution, and had Arch back up and running.
Trolling through the rest of my notes, I found the answer. In 2012, the Tekram SCSI card in the machine failed, and I ultimately replaced it with an Adaptec card. The Tekram card did not have a BIOS segment on it. The Adaptec card did. My guess is that this caused the two internal SCSI devices I have built into the system (Iomega ZIP and Jaz respectively) to be enumerated first, claiming the "sda" and "sdb". device names. That left "sdc" for the root device, and that is where Arch went next. This is my guess anyway.
I should have caught this issue back in 2012, at the time, but from my notes, I can see that I tested the new card thoroughly using the Windows NT 4.0 side of the machine, but never thought to bring up Arch as well. Hence, this problem lay dormant for two years, before I attempted to fire up Arch last month and blundered right into it.
It has not all been bad. I have learned more about the ext2 and ext3 file systems and superblocks in the intervening time than I will ever need to use. I have learned how to manually boot Linux on a machine whose BIOS is so old that it cannot address the disk cylinder that the kernel is on and I have completely refreshed the many general Linux skills that used to just flow from my finger tips. It has been a frustrating experience, but ultimately a successful and useful one.
Just wanted to let everyone know that this is now [SOLVED]. I would mark the post as such, but I don't see any obvious way to do that. Thanks again everyone.

[SOLVED] "Filesystem check failed" during boot process

I was using XFCE on my netbook recently and clicked "shutdown". It logged out to the command prompt and nothing happened. Assuming that I'd clicked "logout" by mistake, I typed "pacman -Syu" to run an update... And moments later it suddenly started the shutdown process.
Now, whenever I boot up, I see the message below. I tried booting from a GParted CD to check the filesystems for errors, but none were detected.
Can anyone suggest what I might need to do to fix the problem?
rootfs: clean, 11026/246512 files, 477083/984576 blocks
home: clean, 4386/527280 files, 237183/2105344 blocks
/dev/sdb2 is mounted. e2fsck: Cannot continue, aborting.
************* FILESYSTEM CHECK FAILED ************
* Please repair manually and reboot. Note that the root
* file system is currently mounted read-only. To remount
* it read-write type: mount -n -o remount,rw /
* when you exit the maintenance shell the system will
* reboot automatically.
Give root password for maintenance
(or type Control-D to continue):
Last edited by esuhl (2012-03-27 01:20:07)

Thank you all for your replies :-)
hadrons123 wrote:What happens when you do try the suggestion given by it?
I don't exactly know how I should "repair manually"... I thought a filesystem check in GParted would have been enough...
lijpbasin wrote:You can boot the system using a archlinux live cd, and run fsck manually on every linux partition in the old system with options.
DON'T mount any of the filesystems before running fsck, or your data will probably be lost. If you want to check the partition information first, run fdisk -l with root privileges.
Thanks. I tried booting from an ArchBang live CD last night and ran "e2fsck -pcv" on each partition. The check completed, but the problem persists... I just tried again using "fsck" as you suggested and got the following output (but the machine still fails to boot with the same error as before):
fsck from util-linux 2.20.1
e2fsck 1.41.14 (22-Dec-2010)
usr was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
usr: 115811/458752 files (1.7% non-contiguous), 783161/1834496 blocks
Gcool wrote:
/dev/sdb2 is mounted. e2fsck: Cannot continue, aborting.
As mentioned already, the reason it's failing is because the /dev/sdb2 partition is mounted before it can be fsck'd. What is this partition exactly (which filesystem, what's on it, mountpoint,...)?
I'm not overly familiar with the Linux boot process, but why would it suddenly be mounting this partition before fsck-ing it? Even if it was mounted when the netbook shutdown, surely the boot process starts with all partitions unmounted...? Anyway, the partition details from /etc/fstab are below.
<file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
/dev/sda1 / ext2 defaults,noatime 0 1
/dev/sdb1 /home ext2 defaults,noatime,user_xattr 0 1
/dev/sdb2 /usr ext2 defaults,noatime 0 1
I'm (now) aware that mounting /usr as a separate partition is a bad idea and (having read the "Error when booting with the new initscripts" thread), I have told pacman to ignore updates to the initscripts package (until I figure out how best to work round or fix that issue).
Shark wrote:Write umount /dev/sdb2 in konsole or unmount partition in gparted by right click on problematic partition and click unmount. Than proced.
If I type "umount /dev/sdb2" at the prompt, I get the following error:
umount: /usr: device is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
I tried "umount -l /dev/sdb2" to unmount when the device becomes free... but it never does.
I also booted into GParted, but there is no option to "unmount" /dev/sdb2. There is a "mount" option in the menu, but it is greyed out. If I open a terminal window from the GParted Live environment and type "sudo umount /dev/sdb2" I get the following message:
umount: /dev/sdb2: not mounted
DSpider wrote:Are you mounting the root drive with "ro" (read only) in fstab?
No (as shown above). I don't *think* I've messed anything up with fstab or any other config files -- everything was working perfectly till the netbook shutdown whilst pacman was running.

[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

[SOLVED] QEMU-KVM fails to boot if passed q35 machine type

As I understand it, qemu still uses the PII3X as the default machine type. I had been using -machine type=q35,accel=kvm for a few weeks to learn more about qemu and KVM. With this code I could boot a win7 VM and I confirmed the ICH9 chipset appeared in the device manager.
After a system update I am no longer able to pass that command. I am using the linux-0.2 image located here.
If I enter this code, the system boots normally:
qemu-system-x86_64 -enable-kvm -boot order=c linux-0.2.img
This however does not work and the bios complains that there is no bootable media found (after waiting for pxe):
qemu-system-x86_64 -enable-kvm -boot order=c -M q35 linux-0.2.img
qemu is 1.7.0-2 (built 02/19/14 but this is the only package in pacman's cache)
seabios is 1.7.3.1-2 (built 09/21/13)
I actually tried this on two different machines with the same result. What can I do next to troubleshoot? Thanks.
Last edited by gizzard (2014-04-13 15:55:25)

R00KIE wrote:
The iso should boot, yes. I did try using -M q35 with a WinXP image I have here and it started to boot (I get blue screens and automatic reboots since lots of things change with -M q35).
One different thing I have however is the specification of the interface type for disks. Try using "-drive file=/path/to/image,if=scsi" or "-drive file=/path/to/image,if=virtio", that seems to make it work for me, it still might make Win7 complain though.
I think I'm getting closer thanks to your help. Adding the if variable allows the debian image to boot using the q35 machine type. Here are results of some trials (command and result):
1. qemu-system-x86_64 -enable-kvm -cpu host -m 1024 debian-live-7.4-amd64-standard.iso
- boots fine
user@debian:~$ lspci | grep ACPI
00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
2. qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -machine type=q35,accel=kvm debian-live-7.4-amd64-standard.iso
- fails to boot
3. qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -machine type=q35,accel=kvm -drive file=debian-live-7.4-amd64-standard.iso,if=ide
- fails to boot
4. qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -machine type=q35,accel=kvm -drive file=debian-live-7.4-amd64-standard.iso,if=scsi
- boots fine
user@debian:~$ lspci | grep AHCI
00:1f.2 SATA controller: Intel Corporation 82901IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] (rev 02)
user@debian:~$ lspci | grep SCSI
00:03.0 SCSI storage controller: LSI Logic / Symbios Logic 53c895a
4. qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -machine type=q35,accel=kvm -drive file=debian-live-7.4-amd64-standard.iso,if=virtio
- boots fine
user@debian:~$ lspci | grep AHCI
00:1f.2 SATA controller: Intel Corporation 82901IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] (rev 02)
user@debian:~$ lspci | grep SCSI
00:03.0 SCSI storage controller: Red Hat, Inc Virtio block device
I will try these options with the win7 VM and report back. I may need to recreate it from scratch, so it might take a little while.

IBook G4 fails to boot with internal HD installed, works when removed

The short version: My iBook started failing to boot via any method (gray screen) and the boot menu (Option during startup) would freeze. Replaced HD, things were better. Six months into new HD, nearly the same symptoms appear again. Removed HD, now running off different HD via FireWire.
The long version–
Back in late 2008-12, my iBook started failing to boot up. Usually it would refuse to boot from any source. Booting the internal disk (10.4.11) would get to a gray screen without any logo and stay there. Holding down Option, the boot menu would come up, but it would usually freeze before it displayed any volumes. Booting from CD (AHT, or OS install disc) would fail in nearly the same way as booting from the internal drive. Target Disk Mode would start, but once the other machine tried to access the drive, the FireWire logo would stop moving and the drive would never show up on the other computer. Very rarely, the machine would get a bit further through one of the boot mechanisms, but it usually froze while booting or just after login.
This machine has gone through three logic boards in the past, so I suspected that was the problem again. I took it to a local Genius Bar and the Genius explained that it was probably the hard drive. He said that sometimes, depending on the way the drive fails, it can "take out" other parts of the system due to drawing too much current, etc.
I was a bit skeptical, but it was going to be much cheaper to replace the HD myself than it would be to send it in for a MLB replacement. So I ordered a new HD (80G) and a USB-to-ATA/SATA adapter. I hoped that I would be able to use the adapter to savlage a bit more data off the drive (it originally failed right before a backup!).
After extracting the HD (40G), I connected it to the USB adapter and was able to access the drive just fine. I used another machine to run another backup from the recently removed HD (40G) to one of my FireWire backup drives and proceeded to put the iBook back together with the new HD (80G).
Once it was all back together, the new HD worked fine. I was able to restore the recent backup from my FireWire drive to the internal, and it worked fine. The only oddity I noticed was that the new drive was apparently trying to sleep several times a minute. I used smartctl (installed via MacPorts) to adjust the power management setting on the drive, and that seemed to help. I also started running smartd (also via MacPorts) to better monitor the new drive.
Recently, a bit more than six months after the new HD was installed, the new HD started showing errors in the system.log. I never found any errors in the logs after the previous HD failed (even though I could look through the logs just fine with the drive attached through the ATA-USB adapter).
Jul 2 18:04:40 Blinky kernel\[0]: disk0s3: I/O error.
Jul 2 18:33:43 Blinky smartd\[217]: Device: disk0, ATA error count increased from 0 to 30\n
Jul 3 02:03:42 Blinky smartd\[217]: Device: disk0, ATA error count increased from 30 to 31\n
Jul 3 03:03:42 Blinky smartd\[217]: Device: disk0, ATA error count increased from 31 to 32\n
Jul 6 23:33:42 Blinky smartd\[217]: Device: disk0, ATA error count increased from 32 to 33\n
Jul 7 00:33:42 Blinky smartd\[217]: Device: disk0, ATA error count increased from 33 to 34\n
Jul 7 12:42:24 Blinky smartd\[217]: Device: disk0, ATA error count increased from 34 to 36\n
Jul 7 13:17:59 Blinky kernel\[0]: disk0s3: I/O error.
+same error message a bit faster than one every 3 seconds+
Jul 7 13:23:00 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 13:33:44 Blinky smartd\[217]: Device: disk0, ATA error count increased from 36 to 615\n
Jul 7 21:17:05 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:17:12 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:17:12 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:17:12 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:17:15 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:17:18 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:17:21 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:17:23 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:17:29 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:18:17 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:19:21 Blinky kernel\[0]: disk0s3: I/O error.
Jul 7 21:19:23 Blinky kernel\[0]: disk0s3: I/O error.
I did not notice the errors until the afternoon of the 7th when the problem became evident. The events around 13:00 happened when I was trying to run a backup. The first backup failed in an odd way (when I came back to check on it later that evening, SuperDuper! seemed to have quit running). So I restarted the backup and started looking around in the logs. That is when I noticed the kernel I/O error messages. When I asked smartctl to query the drive, it showed that many errors had been occurring and it displayed the drive's log of the last five or so errors (alas, I did not save this output). Meanwhile the re-run of SuperDuper! was having problems again. It seemed to have hung (no SDAgent or SDCopy processes were running, but the main UI was still there). Since the backup was not getting anywhere, I decided to shutdown for a while and try again later.
When I did try again later, I was back in the situation of six months ago. It would not boot at all (no internal, no FireWire, no CD/DVD, boot menu hangs, Target Disk Mode hangs). So, I opened up the system, removed the HD and put it back together without an internal HD. The machine is now able to boot and run from FireWire. Again, the (6 month old, 80G) HD "works fine" via the USB adapter. If SMART were available through the USB adapter, I could check to see if the drive is continuing to have problems. I used SuperDuper! to copy the HD to a volume on my FireWire drive which is how I an now running the system.
Has anyone had any similar problems? Any idea why my iBook seems to be killing/rejecting hard drives? (I say killing because, while the drive is connected internally, it certainly seems to be dying. I say rejecting because once the drive is out of the system, both the drive and the system seem to "recover".) I have read messages there where others report success having their iBook MLB resoldered ("reball"). Has anyone experienced substantially similar issues that were solved with a resolder repair?
Thanks!

I was able to test my “failing” ATA drives in a G4 Mac mini (I had to take the mini apart because its drive had finally failed). I was able to successfully boot the Mac mini with either of my iBook drives installed. Once booted, +Disk Utility+ said that each one's SMART Status was Verified. I used smartctl to pull the full SMART info while I had them installed in the Mac mini.
Since the drives were still “good”, I think this emphasizes that the problem is with the ATA interface on my iBook's logic board. Maybe it is broken, or maybe it just needs to be resoldered. For now I am happy just booting off an external Firewire drive.
BTW, I ended up installing the 6 month old 80G drive in the mini. It has been working OK for 10 days now. As long as it continues to operate normally in the mini, it will serve as evidence that my iBook's HD ATA controller is borked. I just hope the ATA controller is more capable of accepting its fallibility than was HAL.
There is a minor problem with the 80G in the mini in that I am unable to use hdapm to change the aggressive head unloading that the drive suffers. I was able to adjust it with hdapm while it was in my iBook. I am able to adjust it with hdparm under Linux on the mini. Luckily the change I made while booted in Linux "sticks" after rebooting back into Mac OS X (I hear it will be lost if the drive is completely powered off though).

Compaq Notebook CQ-45 137TX fails to boot

Hello,
I own a Compaq CQ-45 137TX (Intel Core 2 Duo P7350, 3 GB RAM, 320GB HDD, nVidia GeForce 9200M GS, Windows 7(upgraded from Vista)) with a broken LCD Screen. Since repairing the screen made no sense for such an old laptop, I started using it as a desktop by attaching an external monitor and input devices. The computer worked fine for the past few months.
Upon restarting the computer after a hiatus of a week or so, the computer failed to boot and display anything on the external monitor. I think it is failing POST.
The laptop gives out multiple beeps continually (not continuous, multiple beeps that don't end).
I thought that the RAM is faulty and tried to reboot the machine by trying one RAM stick at a time (since the laptop has two). It didn't work for either of the two sticks tried in both slots individually.
I think both the RAM sticks may be faulty, however, I am unable to borrow a RAM stick to test on it.
Before buying a new one, I would like someone to clarify or point out other hardware that may faulty in this laptop. I have had people tell me that my Graphic Card may have given up.
Thank you for your assistance.

Hello @root123 ,
Welcome to the HP Forums!
I understand you're unable to boot up your CQ-45 notebook.
It's unlikely to be RAM if neither card worked in either of the two DIMM slots. It is possible that both cards or slots have failed, but highly unlikely.
The beeping should tell you exactly what the error is. Try looking through this document which should help you identify the error: Computer Does Not Start and the LEDs Blink or the Computer Beeps.
You may also want to try this document as well: Troubleshooting Black Screen Displays with No Error Messages During Startup or Boot.
Let me know if you're able to identify the failure with the beep code and we'll go from there.
Please click the "Kudos, Thumbs Up" at the bottom of this post if you want to say "Thanks" for helping!
Please click "Accept as Solution" if you feel my post solved your issue, it will help others find the solution.
The Great Deku Tree
I work on behalf of HP.

Arch fails to boot after installation (BIOS mode)

I finished my Arch installation, following the Beginner's Guide, and once I unmounted the partitions and rebooted, GRUB failed to boot into Arch. I'm not exactly sure what the problem is though. Basically what happens is I power on the machine, the Dell splash screen comes up, GRUB loads, I choose
Arch Linux, with Linux core repo kernel
the kernel and ramdisk attempt to load, then some message about "recovering journal" appears, and then I return back to the Dell splash screen. The same thing happens even if I choose the second option
Arch Linux, with Linux core repo kernel (Fallback initramfs)
However, when I choose to boot Win XP everything boots just fine. My apologies for the quality of the videos and pictures.
Here's a video of what happens:
http://youtu.be/uC96kX6iTjI
I suspect this has to do with this error I got when I generated the "grub.cfg". Although I'm not entirely sure because my understanding is that this error would affect booting Win XP which in fact boots perfectly fine.
Error (and no I'm not using any lvm volumes)
http://imgur.com/qqxpoGG
I believe these are the portions of the "grub.cfg" that load Arch and Win XP. I got these by pressing "e" while on their menu entry in the GRUB bootloader.
Arch (I had to scroll down to see the rest, hence two pictures)
http://imgur.com/79dBw2C
http://imgur.com/qusEfL0
Win XP
http://imgur.com/oLnLlT0
Any idea how I can fix this? Any help is greatly appreciated and please be patient, I know, I'm a noob.
* I'm not sure if this is of any significance but I had a problem very similar to this when trying to get the Arch install to boot via usb (this computer doesn't have CD/DVD drive). I solved it by following this excerpt from the Beginner's Guide.
Troubleshooting boot problems
If you are using an Intel video chipset and the screen goes blank during the boot process, the problem is likely an issue with Kernel Mode Setting. A possible workaround may be achieved by rebooting and pressing
e
over the entry that you are trying to boot (i686 or x86_64). At the end of the string type
nomodeset
and press
Enter
Here's a video of what it looked like:
http://youtu.be/vXRcbU0zdto
The computer specs:
OS: Windows XP Professional 32 bit Version 2002 Service Pack 3
CPU: Intel Pentium 4 @ 3.00 GHz
RAM: 2 GB DDR2
HDD: 80 GB

Hi,
why did you not try adding nomodeset with the regular boot? During the net-install no video drivers will be installed;
you have to install them after reboot after installing xorg. The (video)problem you had with booting from usb is still
present.

[SOLVED] UDEV Failed at boot

Similar Messages

Maybe you are looking for