[gentoo-user] digikam fails to install
hello gentoos, I recently updated to kde 3.4.3 and on the way a lost digikam, which simply doesn't install. ### larissa frelun # emerge digikam Calculating dependencies ...done! emerge (1 of 1) media-gfx/digikam-0.8.1-r1 to / md5 files ;-) digikam-0.7.4-r1.ebuild md5 files ;-) digikam-0.8.1-r1.ebuild md5 files ;-) digikam-0.7.4-r2.ebuild md5 files ;-) files/digest-digikam-0.7.4-r1 md5 files ;-) files/digest-digikam-0.7.4-r2 md5 files ;-) files/digest-digikam-0.8.1-r1 md5 src_uri ;-) digikam-0.8.1.tar.bz2 md5 src_uri ;-) digikam-doc-0.8.0.tar.bz2 * Scan for possible needed slot related rebuilds. * Please run emerge --oneshot =media-libs/libkipi-0.1.2 =media-libs/libkexif-0.2.2 before continuing. !!! ERROR: media-gfx/digikam-0.8.1-r1 failed. !!! Function pkg_setup, Line 38, Exitcode 0 !!! (no error message) !!! If you need support, post the topmost build error, NOT this status message. larissa frelun # ### This is the same with or without 'media-gfx/digikam ~x86' as keyword I attached the output from emerge --info as well Any help??? Best from Fredrik use Description: Binary data
Re: [gentoo-user] digikam fails to install
Sorry, I forgot of course I also run ### emerge --oneshot =media-libs/libkipi-0.1.2 =media-libs/libkexif-0.2.2 ### which worked as supposed but no luck with digikam after that either. Fredrik - Original Message - From: Fredrik Lundgren [EMAIL PROTECTED] To: gentoo-user@lists.gentoo.org Sent: Saturday, February 18, 2006 3:50 PM Subject: [gentoo-user] digikam fails to install hello gentoos, I recently updated to kde 3.4.3 and on the way a lost digikam, which simply doesn't install. ### larissa frelun # emerge digikam Calculating dependencies ...done! emerge (1 of 1) media-gfx/digikam-0.8.1-r1 to / md5 files ;-) digikam-0.7.4-r1.ebuild md5 files ;-) digikam-0.8.1-r1.ebuild md5 files ;-) digikam-0.7.4-r2.ebuild md5 files ;-) files/digest-digikam-0.7.4-r1 md5 files ;-) files/digest-digikam-0.7.4-r2 md5 files ;-) files/digest-digikam-0.8.1-r1 md5 src_uri ;-) digikam-0.8.1.tar.bz2 md5 src_uri ;-) digikam-doc-0.8.0.tar.bz2 * Scan for possible needed slot related rebuilds. * Please run emerge --oneshot =media-libs/libkipi-0.1.2 =media-libs/libkexif-0.2.2 before continuing. !!! ERROR: media-gfx/digikam-0.8.1-r1 failed. !!! Function pkg_setup, Line 38, Exitcode 0 !!! (no error message) !!! If you need support, post the topmost build error, NOT this status message. larissa frelun # ### This is the same with or without 'media-gfx/digikam ~x86' as keyword I attached the output from emerge --info as well Any help??? Best from Fredrik -- gentoo-user@gentoo.org mailing list
[gentoo-user] ...startup information on screen...
Dear Gentoos, Is the information that runs on the screen before and after X is started or closed saved in some place or can it be saved or retrieved somehow? Fredrik -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] ... fails to open device '/dev/hda2' after update
Well, a local Gentoo-guru fixed the problem with etc-update. So the failure to appears to have been there. As, a newbie I could use some subtantial advice where, when, and how ect-update should be used (there were 80 config files to take care of) - although when I failed I wasn't even aware of the problem. Fredrik - Original Message - From: Richard Fish [EMAIL PROTECTED] To: gentoo-user@lists.gentoo.org Sent: Monday, January 30, 2006 4:27 AM Subject: Re: [gentoo-user] ... fails to open device '/dev/hda2' after update On 1/28/06, Fredrik Lundgren [EMAIL PROTECTED] wrote: * checking root filesystem ... Failed to open the device '/dev/hda2': No such file or directory * Filesystem couldn't be fixed: (Give root password for maintenance (or Control D to continue):_ --- Either this wasn't the problem or I mixed up the correction somehow. It appears as if the bootprocess sets the filesystem to be inaccesible? Can you post some of the messages that appear before this point? -Richard -- gentoo-user@gentoo.org mailing list -- gentoo-user@gentoo.org mailing list
[gentoo-user] ... fails to open device '/dev/hda2' after update
Dear list, I haven't used my Gentoo for more than half a year or so (it was well updated then) so the other night I made an update emerge --update system and all appeared to go well (lots of updates) but when I rebooted i got * checking root filesystem ... Failed to open the device '/dev/hda2': No such file or directory * Filesystem couldn't be fixed: (Give root password for maintenance (or Control D to continue):_ --- Well I changed to root and tried --- df Filesystem1K-blockusedAvailableUse%Mount on 35152904 8113240 2703966424%/ --- and --- fsck -t resierfs /dev/hda2 (Confirmed with Yes) Failed to open the device '/dev/hda2': No such file or directory --- The file system is there as I can use nano and navigate in the directory hierarchy and visit files. I have, in Win XP, tested the partitions with 'Acronis Disk Director Suite' and they look OK and don't have any errors. Please, how should this be fixed? Best wishes from a somewhat desperate Fredrik -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] ... fails to open device '/dev/hda2' after update
Thanks for the advice, To the best of my knoledge Kernel 2.6.15.1 was downloaded and installed. I haven't made any change with respect to devfs or udev. How should i make the migration? And I haven't used etc-update. What should I start with? Again thanks from Fredrik - Original Message - From: Richard Fish [EMAIL PROTECTED] To: gentoo-user@lists.gentoo.org Sent: Saturday, January 28, 2006 2:50 PM Subject: Re: [gentoo-user] ... fails to open device '/dev/hda2' after update On 1/28/06, Fredrik Lundgren [EMAIL PROTECTED] wrote: and all appeared to go well (lots of updates) but when I rebooted i got * checking root filesystem ... Failed to open the device '/dev/hda2': No such file or directory * Filesystem couldn't be fixed: (Give root password for maintenance (or Control D to continue):_ Did you update the kernel version? Are you still using devfs? If so, devfs has been removed from current kernels and you need to migrate to udev. Also, be sure to run etc-update, and fixup your configuration files in /etc/conf.d. Lots of stuff moved from /etc/rc.conf to /etc/conf.d/ files in the last 6 months, so you may have some issue there. Particularly there were changes in baselayout that decide whether to startup devfs or udev. -Richard -- gentoo-user@gentoo.org mailing list -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] ... fails to open device '/dev/hda2' after update
Sorry for my misstake, --- uname -a Linux(none) 2.6.10-gentoo-r6 #8 Thu Feb 17 13:15:44 CET 2005 i686 Intel(R) Pentium(R) M processor 1.70 Ghz Centurion Intel GNU/Linux etc-update mkdir: cannot create directory '/var/tmp/1162': Read only file system --- That must be my old Kernel which worked OK before my update No I didn't run etc-update after my update when the system was up and working Any way to mend the file system? Fredrik - Original Message - From: Ernie Schroder [EMAIL PROTECTED] To: gentoo-user@lists.gentoo.org Sent: Saturday, January 28, 2006 3:34 PM Subject: Re: [gentoo-user] ... fails to open device '/dev/hda2' after update On Saturday 28 January 2006 09:15, a tiny voice compelled Fredrik Lundgren to write: Thanks for the advice, To the best of my knoledge Kernel 2.6.15.1 was downloaded and installed. I haven't made any change with respect to devfs or udev. How should i make the migration? And I haven't used etc-update. What should I start with? d'loading and emerging a new kernel version is not installing a new kernel. You would have had to compile the kernel with genkernel or # make menuconfig Find your running kernel version with: $ uname -a Did you run etc-update after your updates? Again thanks from Fredrik - Original Message - From: Richard Fish [EMAIL PROTECTED] To: gentoo-user@lists.gentoo.org Sent: Saturday, January 28, 2006 2:50 PM Subject: Re: [gentoo-user] ... fails to open device '/dev/hda2' after update On 1/28/06, Fredrik Lundgren [EMAIL PROTECTED] wrote: and all appeared to go well (lots of updates) but when I rebooted i got * checking root filesystem ... Failed to open the device '/dev/hda2': No such file or directory * Filesystem couldn't be fixed: (Give root password for maintenance (or Control D to continue):_ Did you update the kernel version? Are you still using devfs? If so, devfs has been removed from current kernels and you need to migrate to udev. Also, be sure to run etc-update, and fixup your configuration files in /etc/conf.d. Lots of stuff moved from /etc/rc.conf to /etc/conf.d/ files in the last 6 months, so you may have some issue there. Particularly there were changes in baselayout that decide whether to startup devfs or udev. -Richard -- gentoo-user@gentoo.org mailing list -- Regards, Ernie -- gentoo-user@gentoo.org mailing list -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] ... fails to open device '/dev/hda2' after update
Thanks again, --- mount / -o remount, noatime,rw --- gave no protests --- etc-update --- Worked this time and I updated all and moved to my home directory and were able to change a file there looked at /etc/conf.d/rc but made no chages rebooted and ended up at the same place as before * checking root filesystem ... Failed to open the device '/dev/hda2': No such file or directory * Filesystem couldn't be fixed: (Give root password for maintenance (or Control D to continue):_ --- Either this wasn't the problem or I mixed up the correction somehow. It appears as if the bootprocess sets the filesystem to be inaccesible? Fredrik --- - Original Message - From: Richard Fish [EMAIL PROTECTED] To: gentoo-user@lists.gentoo.org Sent: Saturday, January 28, 2006 4:27 PM Subject: Re: [gentoo-user] ... fails to open device '/dev/hda2' after update On 1/28/06, Fredrik Lundgren [EMAIL PROTECTED] wrote: Sorry for my misstake, --- uname -a Linux(none) 2.6.10-gentoo-r6 #8 Thu Feb 17 13:15:44 CET 2005 i686 Intel(R) Pentium(R) M processor 1.70 Ghz Centurion Intel GNU/Linux etc-update mkdir: cannot create directory '/var/tmp/1162': Read only file system Try (assuming you don't have a separate /var filesystem): mount / -o remount,noatime,rw etc-update Once you have worked through that, edit /etc/conf.d/rc, which contains many of the things that were once in /etc/rc.conf, including RC_DEVICES. Since you are still on 2.6.10, a udev migration is not /necessary/ to fix your system, but I would still recommend it when you have some time. The basic steps are going to be: emerge udev coldplug hotplug edit /etc/conf.d/rc to set RC_DEVICES=udev remove any udev/devfs options from the kernel command line in /boot/grub/grub.conf remove /dev/.devfs if it exists reboot You can find a lot more information on udev here: http://www.gentoo.org/doc/en/udev-guide.xml -- gentoo-user@gentoo.org mailing list -- gentoo-user@gentoo.org mailing list
