public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rumen Yotov <rumen_yotov@dir.bg>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] strange boot problems with gentoo-sources-2.6.12-r10
Date: Mon, 05 Sep 2005 09:14:01 +0300	[thread overview]
Message-ID: <1125900841.11636.27.camel@mach.qrypto.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1177 bytes --]

Hi All,
The day before yesterday compiled/booted/worked with this 'new' kernel -
gentoo-sources-2.6.12-r10 (after -r9).
Changelog only says it's based on 2.6.12.6 and there are two fixed Bugs
for AMD-64 & a forcedeth problem (i'm on 32-bits& don't have forcedeth).
Went for it cause wanted to try 'vesafb-tng' (splashutils). Works OK.
Think the later problems came from the vesafb-tng thing, which replaced
my previous 'bootsplash' feature/theme. On first two/three runs it
boots/works OK (nice work with that splash-themes).
Yesterday the problems began, still while booting, errors appeared while
starting 'svscan' (part of daemontools - i run tinydns&qmail) with
messages about the filesystem being 'read-only' etc and as it retries to
start endlessly things are doomed. Had to use Live-CD to fix the errors.
Returned to -r9, disabled 'svscan' on boot - works w/o flaws, later even
could start 'svscan' manually.
This is just as info and eventually if somebodies have any experiences.
Will try -r10 w/o starting 'svscan' & look at the 2.6.12.6-Changelog,
but most probably will try out 2.6.13 (in testing or when it comes out).
Thank for your time. Rumen

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

             reply	other threads:[~2005-09-05  6:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-05  6:14 Rumen Yotov [this message]
2005-09-05 11:49 ` Solved[gentoo-user] strange boot problems with gentoo-sources-2.6.12-r10 Rumen Yotov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1125900841.11636.27.camel@mach.qrypto.org \
    --to=rumen_yotov@dir.bg \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox