I emerged hal-0.4.5-r2 and ivman-0.5_pre2 (using instructions from http://gentoo-wiki.com/HOWTO_ivman). hald starts correctly: * Starting D-BUS system messagebus... [ ok ] * Starting Hardware Abstraction Layer daemon... [ ok ] but ivman (in debug mode) gives: Ikke's Volume Manager, http://ivman.sf.net 23986: arguments to dbus_message_new_method_call() were incorrect, assertion "pa th != NULL" failed in file dbus-message.c line 1723. This is normally a bug in some application using the D-BUS library. libhal.c 1856 : Couldn't allocate D-BUS message IvmConfigActions.c:42 (ivm_device_is_mountable) (null) can't be mounted because it is not a block device When I put hald and ivman to start after boot (using rc-update), system hangs after this message. Reproducible: Always Steps to Reproduce: 1. emerge hald ivman 2. /etc/init.d/hald start 3. ivman Actual Results: Error message appeared (after disabling fork and enabling debugging in /etc/ivman/IvmConfigBase.xml) Expected Results: Work correctly ... * dbus installed: dbus-0.23-r3 * CD entry in /etc/fstab: /dev/cdrom /mnt/cdrom auto noauto,users 0 0 * kernel: 2.6.11-love2, tried also old gentoo-sources 2.6.8 * emerge info: Portage 2.0.51.19 (default-linux/x86/2004.2, gcc-3.4.2, glibc-2.3.4.20050125-r0, 2.6.11-love2 i686) ================================================================= System uname: 2.6.11-love2 i686 AMD Athlon(TM) XP 2500+ Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.3-r1 [2.3.3 (#1, Jul 16 2004, 03:32:58)] ccache version 2.3 [enabled] dev-lang/python: 2.3.3-r1 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.5, 1.6.3, 1.8.5-r3, 1.7.9-r1, 1.4_p6, 1.9.4 sys-devel/binutils: 2.14.90.0.8-r1 sys-devel/libtool: 1.4.3-r4, 1.5.10-r4 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=athlon-xp -pipe -mmmx -m3dnow -msse -s -mfpmath=sse -frename-registers" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=athlon-xp -pipe -mmmx -m3dnow -msse -s -mfpmath=sse -frename-registers" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig candy ccache distlocks sandbox sfperms" GENTOO_MIRRORS="http://gentoo.prz.rzeszow.pl http://src.gentoo.pl http://www.mirror.ac.uk/sites/www.ibiblio.org/gentoo http://gentoo.zie.pg.gda.pl" LANG="pl_PL" LC_ALL="pl_PL" LDFLAGS="-Wl,-O1" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://65.19.163.230/gentoo-portage" USE="x86 3dnow X aalib alsa apm artworkextra avi bash-completion berkdb bitmap-fonts cdr crypt cups curl directfb dvd emboss encode esd fam flac font-server foomaticdb gdbm gif gimpprint gnome gpm gtk gtk2 guile icons_alt_cryst icons_crystal16 icons_crystal22 icons_gg3d icons_real_gg imagemagick imlib ipv6 jabber jpeg junit libg++ libwww mad mikmod mmx module_account_management module_alsa_sound module_ao_sound module_autoaway module_default_sms module_desktop_docking module_ext_info module_filedesc module_mail module_spellchecker module_spy module_tabs module_tcl_scripting module_weather module_x11_docking motif mp3 mpeg ncurses nls nptl nptlonly oggvorbis opengl oss pam pdflib perl pheaders png ppds python quicktime readline real sdl slang spell sse ssl svg svga tcpd tiff truetype truetype-fonts type1-fonts userbox_sort xine xml xml2 xosd xv xvid zlib video_cards_radeon linguas_pl" Unset: ASFLAGS, CBUILD, CTARGET
rohan: any idea?
Well... this might be a silly question, but... have you tried setting fork=true and just ignoring that message? Your system will _always_ hang on boot if you've told Ivman not to fork (system init scripts are executed sequentially, so if you've told Ivman not to fork, whatever is supposed to come next will never be executed). In any case, that DBUS message is more of a warning than an error; it comes from HAL, but in all cases I've seen it, it was able to recover. This message - "IvmConfigActions.c:42 (ivm_device_is_mountable) (null) can't be mounted because it is not a block device" - confirms that Ivman is receiving DBUS messages from HAL in any case... set fork=true and ignore that message, and then see if Ivman is running by 'ps aux'. If it is running but your CDs/DVDs aren't being mounted, there's probably some configuration error...
I set fork to true, but it still doesn't work: # /etc/init.d/hald start * Starting D-BUS system messagebus... [ ok ] * Starting Hardware Abstraction Layer daemon... [ ok ] # ivman Ikke's Volume Manager, http://ivman.sf.net daemonize.c:32 (daemonize) Daemonizing... (now as non-root user:) # ps aux|grep ivman root 6936 0.0 0.3 4148 1852 ? S 12:23 0:00 ivman I inserted cd, but ls /mnt/cdrom gives nothing :-( mount /mnt/cdrom works as usual, but ivman isn't working :-(
Is /dev/cdrom a symlink to your device? Have you tried putting /dev/hdc (or whatever the real device name is) in fstab instead? Also, do you see any messages from Ivman in the system log when you insert a disc?
I changed /dev/cdrom (which symlinks to /dev/cdroms/cdrom0) to /dev/hdc (hdc: ATAPI 52X DVD-ROM CD-R/RW drive) in my fstab, but it didn't help. From my /var/log/messages: * after starting hald: Apr 12 16:18:57 mati fstab-sync[6398]: removed all generated mount points and about 20 messages like this: Apr 12 16:18:57 mati udevinfo[6425]: tdb_open_ex: could not open file /dev/.udev.tdb: No such file or directory * after starting ivman: Apr 12 16:21:49 mati ivman: IVM started in root mode Apr 12 16:21:49 mati ivman: (null) can't be mounted because it is not a block device Nothing appears in the log after inserting a cd.
Sounds like you've got udev troubles. What does 'udevinfo -d' say about /dev/hdc? Does 'udevinfo' fail to run? If so, you should probably try reinstalling udev, and maybe unmerging devfsd if you've still got it installed.
I reinstalled udev. udevinfo -d /dev/hdc still gives only: "unable to open udev database". > try reinstalling udev, and maybe unmerging devfsd if you've still got it installed Is it safe and needed to unmerge devfsd? http://www.gentoo.org/doc/en/devfs-guide.xml says "Warning: Currently, Gentoo cannot live without the compatibility symlinks.". I googled for "unable to open udev database" and found that: http://lists.freedesktop.org/archives/hal/2004-June/000480.html I runned udevstart, but it didn't help :-( Should I remove devfsd? Wouldn't it break my system?
I unmerged devfsd a long time ago and nothing broke. That being said, doing so won't necessarily fix your udev problem; but if your /dev is still being mounted by devfs, it probably will. Also, I suggest udev-045...
Disabling devfs solved the problem :-) Although I didn't unmerge it, I checked how system would behave if I pass 'devfs=nomount' to kernel, then I recompiled kernel without devfs suppeort. That was it.
resolved.
