From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 96FE51381F3 for ; Fri, 9 Aug 2013 00:33:20 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3B54FE0BE3; Fri, 9 Aug 2013 00:32:55 +0000 (UTC) Received: from qmta06.westchester.pa.mail.comcast.net (qmta06.westchester.pa.mail.comcast.net [76.96.62.56]) by pigeon.gentoo.org (Postfix) with ESMTP id 7A083E0BDF for ; Fri, 9 Aug 2013 00:32:54 +0000 (UTC) Received: from omta09.westchester.pa.mail.comcast.net ([76.96.62.20]) by qmta06.westchester.pa.mail.comcast.net with comcast id AQAk1m0020SCNGk56QYueK; Fri, 09 Aug 2013 00:32:54 +0000 Received: from [192.168.1.3] ([50.139.201.59]) by omta09.westchester.pa.mail.comcast.net with comcast id AQYt1m0151HPovE3VQYt9Z; Fri, 09 Aug 2013 00:32:54 +0000 Subject: Re: [gentoo-amd64] early boot failure, not sure how to diagnose From: Drake Donahue To: gentoo-amd64@lists.gentoo.org In-Reply-To: References: <5204023D.5020705@googlemail.com> Content-Type: text/plain; charset="us-ascii" Date: Thu, 08 Aug 2013 20:32:51 -0400 Message-ID: <1376008371.22960.6.camel@fx8150.donahues.us.> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@lists.gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org Mime-Version: 1.0 X-Mailer: Evolution 2.32.3 Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1376008374; bh=PI7CIkqMOMJ8fHmr/UdtRbgbjPi5oGOTVXo5ikIJsFM=; h=Received:Received:Subject:From:To:Content-Type:Date:Message-ID: Mime-Version; b=SOZmt7aVkVOpJ8QmcCP/e31bRkqad7rWgP2b1yhPtx9wMk4rAuSt5kqHxJ+ChNuBD wTenwhLZv3N0PBKAEeGWpnodhvFhCFSZmNKgdKxUnUbmIfgGRGsVXIRjQs97qlOt+k CwOSChg6viUIVVBkmENDGFWTpBnI72c2quEfRimoG3ujBD90wzqRCe47JOlUicNKaR pJ+8lurHcfqUXZ8di3HgKExm4LvMTd94XK0zlmuaJrha3zauQdcrZJgVAJuNY+NEEb 1/pZc5N2n/t+3NSbyuT1djFGwMowidllECZVlnF/C6/7yW32YsSqsqLywLwl2ftlgh DnVDLIj1wRiuw== X-Archives-Salt: 361adda0-a350-44ef-9150-6471cdd4adbe X-Archives-Hash: 7c4bf40d841081e170e464719630a2fb On Fri, 2013-08-09 at 09:07 +1000, Daiajo Tibdixious wrote: > Logged in after failed boot. > /home & /boot are mounted, but nothing in them when I ls. > ls of / shows all the normal things there. > > While logged in, I'm still getting boot messages, where USB devices, > eg the mouse, disconnect and reconnect. > > There are a ridiculous number of sd devices in /dev. sda, sdb, sdc, > sdd all go to 15. sda is the hard drive, sdb/sdc for USB devices. > Never had sdd. > > Did see some errors, notably "cannot mount /run" bad superblock or > something like that. Its hard to scroll back with USB messages > constantly appearing, half a screenful each time. > > On Fri, Aug 9, 2013 at 6:40 AM, Volker Armin Hemmann > wrote: > > Am 08.08.2013 10:43, schrieb Daiajo Tibdixious: > >> I got new hardware for a home desktop a few days ago. > >> Downloaded install-amd64-minimal-20130801.iso and am still booting > >> from that cd as hard drive boot fails. > >> > >> I turned on logging in /etc/rc.conf, but no /var/log/rc.log is produced. > >> The disks are mounted but readonly. I guess from this the problem is > >> occurring before the root partition is mounted. > >> > >> I only have 4 partitions: boot, swap, root, and home. Since everything > >> important is on the root partition, I'm not using an initramfs. > >> > >> I have many times tried to catch the error by watching the screen, but > >> it scrolls past way to fast. > >> > >> The last part of the boot messages before things go crazy is > >> "Switching to clocksource TSC". > >> > >> I've been reading up on grub, but don't see anyway to get more info on > >> what is going wrong. > >> > >> If I boot from the cd and chroot to the disk, everything seems to work > >> fine. /boot is ext2 fs and this is my grug.conf: > >> default 0 > >> timeout 20 > >> splashimage=(hd0,0)/boot/grub/splash.xpm.gz > >> > >> title Gentoo Linux 3.8.13 > >> root (hd0,0) > >> kernel /boot/3.8/13-0/bzImage root=/dev/sda3 > >> > > > > > > and what is happening? > > > Does kernel config have: CONFIG_DEVTMPFS=y CONFIG_DEVTMPFS_MOUNT=y CONFIG_HOTPLUG=y CONFIG_FSNOTIFY=y CONFIG_DNOTIFY=y CONFIG_INOTIFY_USER=y CONFIG_NET=y CONFIG_PROC_FS=y CONFIG_SIGNALFD=y CONFIG_SYSFS=y CONFIG_SYSFS_DEPRECATED is not set CONFIG_UEVENT_HELPER_PATH="" CONFIG_BLK_DEV_BSG=y CONFIG_TMPFS=y CONFIG_TMPFS_POSIX_ACL=y CONFIG_TMPFS_XATTR=y also this problem frequently results from graphics support attempting to invoke kms support with: modules instead of builtins with frame buffers enabled with the radeon driver enabled without building in appropriate firmware