Greetings,
Often when I build systems with catalyst I encounter the following
kernel freeze after the boot loader has completed:
[ ... lots of kernel loading stuff which seems ok ... ]
Freeing unused kernel memory: 172k freed
request_module: runaway loop modprobe binfmt-
request_module:
On 08/01/08 15:46, Åsmund Grammeltvedt wrote:
On Tuesday 08 January 2008 15:34:09 lurker wrote:
Greetings,
Often when I build systems with catalyst I encounter the following
kernel freeze after the boot loader has completed:
[ ... lots of kernel loading stuff which seems ok ... ]
Freeing
On 08/01/08 15:46, Åsmund Grammeltvedt wrote:
On Tuesday 08 January 2008 15:34:09 lurker wrote:
Greetings,
Often when I build systems with catalyst I encounter the following
kernel freeze after the boot loader has completed:
[ ... lots of kernel loading stuff which seems ok ... ]
Freeing
On 12/01/08 17:49, Chris Gianelloni wrote:
On Sat, 2008-01-12 at 02:20 +0100, lurker wrote:
In my case, the only way I could get it to work consistently was to patch
genkernel to use symbolic links instead, when setting up the initramfs.
After upgrading to busybox-1.8.2 I've not experienced
Greetings again,
I've been searching for the catalyst reference manual the last couple of
days but cannot seem to find it. It used to reside in
http://www.gentoo.org/proj/en/releng/catalyst/2.x/reference.xml as
currently stated by
Greetings list,
Currently catalyst (2.0.5, 2.0.6pre4) doesn't seem to change what uname
outputs. uname -r, for example, prints the version of the kernel running
catalyst, not the kernel that's in the stage. Of course, that's how it
is, but isn't it possible to hack that somehow? It's a bit
On 14/02/08 04:01, Andrew Gaffney wrote:
lurker wrote:
Greetings list,
Currently catalyst (2.0.5, 2.0.6pre4) doesn't seem to change what uname
outputs. uname -r, for example, prints the version of the kernel running
catalyst, not the kernel that's in the stage. Of course, that's how
On 08/01/08 15:46, Åsmund Grammeltvedt wrote:
On Tuesday 08 January 2008 15:34:09 lurker wrote:
Greetings,
Often when I build systems with catalyst I encounter the following
kernel freeze after the boot loader has completed:
[ ... lots of kernel loading stuff which seems ok ... ]
Freeing
On 21/02/08 05:40, Chris Gianelloni wrote:
On Wed, 2008-02-20 at 21:38 +0100, lurker wrote:
genkernel fails to add busybox with cpio (this is with genkernel-3.4.9
and catalyst-2.0.6_pre6):
Please try catalyst-2.0.6_pre8, which is pretty new and should work just
fine for whatever you need
On 21/02/08 05:40, Chris Gianelloni wrote:
On Wed, 2008-02-20 at 21:38 +0100, lurker wrote:
genkernel fails to add busybox with cpio (this is with genkernel-3.4.9
and catalyst-2.0.6_pre6):
Please try catalyst-2.0.6_pre8, which is pretty new and should work just
fine for whatever you need
On 26/02/08 14:59, Pongracz Istvan wrote:
2008. 02. 26, kedd keltezéssel 07.33-kor Andrew Gaffney ezt írta:
Pongracz Istvan wrote:
Hi,
I use virtualbox/qemu to test the livecds.
I know, I will not really popular, but I expected that, if mkxf86 could
not detect the video card, it left empty
Hi list,
When I generate liveCDs using catalyst they always end up with a root
console being open on tty1 after boot. How can I disable this and have
it behave like a normal Gentoo install?
A somewhat related question: why is it only possible to login on tty1?
tty2 and up just give blank screens
On 10/02/09 21:17, Mike Frysinger wrote:
On Tuesday 10 February 2009 14:54:18 lurker wrote:
When I generate liveCDs using catalyst they always end up with a root
console being open on tty1 after boot. How can I disable this and have
it behave like a normal Gentoo install?
A somewhat related
On 10/02/09 23:27, Andrew Gaffney wrote:
lurker wrote:
On 10/02/09 22:28, Mike Frysinger wrote:
try grepping the init.d scripts. or look at the source scripts
from catalyst itself (iirc, there's a livecd support dir or
some such).
I've recursively grepped every file in /usr/lib/catalyst
14 matches
Mail list logo
