| 1 |
On Mon, 2005-09-05 at 09:14 +0300, Rumen Yotov wrote: |
| 2 |
> Hi All, |
| 3 |
> The day before yesterday compiled/booted/worked with this 'new' kernel - |
| 4 |
> gentoo-sources-2.6.12-r10 (after -r9). |
| 5 |
> Changelog only says it's based on 2.6.12.6 and there are two fixed Bugs |
| 6 |
> for AMD-64 & a forcedeth problem (i'm on 32-bits& don't have forcedeth). |
| 7 |
> Went for it cause wanted to try 'vesafb-tng' (splashutils). Works OK. |
| 8 |
> Think the later problems came from the vesafb-tng thing, which replaced |
| 9 |
> my previous 'bootsplash' feature/theme. On first two/three runs it |
| 10 |
> boots/works OK (nice work with that splash-themes). |
| 11 |
> Yesterday the problems began, still while booting, errors appeared while |
| 12 |
> starting 'svscan' (part of daemontools - i run tinydns&qmail) with |
| 13 |
> messages about the filesystem being 'read-only' etc and as it retries to |
| 14 |
> start endlessly things are doomed. Had to use Live-CD to fix the errors. |
| 15 |
> Returned to -r9, disabled 'svscan' on boot - works w/o flaws, later even |
| 16 |
> could start 'svscan' manually. |
| 17 |
> This is just as info and eventually if somebodies have any experiences. |
| 18 |
> Will try -r10 w/o starting 'svscan' & look at the 2.6.12.6-Changelog, |
| 19 |
> but most probably will try out 2.6.13 (in testing or when it comes out). |
| 20 |
> Thank for your time. Rumen |
| 21 |
Hi, |
| 22 |
Found the culpit (or seems so), was "/etc/init.d/splash" started in |
| 23 |
'default level'. Could try starting it in boot-level but too much |
| 24 |
problems afterwards, so leave it turned off. |
| 25 |
Now w/o it my system is OK again - kernel-2.6.12-r10 with splash. |
| 26 |
Rumen |
Archives