On Thursday 11 December 2008, Nikos Chantziaras wrote:
Clone that config:
make cloneconfig
How does this compare to make oldconfig?
--
Regards,
Mick
signature.asc
Description: This is a digitally signed message part.
Mick wrote:
On Thursday 11 December 2008, Nikos Chantziaras wrote:
Clone that config:
make cloneconfig
How does this compare to make oldconfig?
It doesn't, because it doesn't even exist. I meant oldconfig here :P
(openSUSE has a cloneconfig target and I got it mixed up here. Sorry.)
Nikos Chantziaras wrote:
Mick wrote:
On Thursday 11 December 2008, Nikos Chantziaras wrote:
Clone that config:
make cloneconfig
How does this compare to make oldconfig?
It doesn't, because it doesn't even exist. I meant oldconfig here :P
(openSUSE has a cloneconfig target and I got
Dale wrote:
Nikos Chantziaras wrote:
Mick wrote:
On Thursday 11 December 2008, Nikos Chantziaras wrote:
Clone that config:
make cloneconfig
How does this compare to make oldconfig?
It doesn't, because it doesn't even exist. I meant oldconfig here :P
(openSUSE has a cloneconfig target
Nikos Chantziaras wrote:
Dale wrote:
Nikos Chantziaras wrote:
Mick wrote:
On Thursday 11 December 2008, Nikos Chantziaras wrote:
Clone that config:
make cloneconfig
How does this compare to make oldconfig?
It doesn't, because it doesn't even exist. I meant oldconfig here :P
On Friday 12 December 2008 08:46:00 Heinrichs, Dirk (EXT-Capgemini -
DE/Dusseldorf) wrote:
Am Donnerstag, den 11.12.2008, 16:59 -0600 schrieb ext Harry Putnam:
These URLS seem to be loading kind of slow right now:
Hmm, unfortunately they don't load at all because of DNS failure. The
machine
On Thursday 11 December 2008 23:59:46 Harry Putnam wrote:
Could please post the kernels .config (or /proc/config) and lspci
output from the original, working setup?
Yes, sorry I made you work so hard for the info... you did ask for
more info but I got working on this thread and forgot.
Dirk Heinrichs dirk.heinri...@online.de writes:
[...]
OK, I'll give it a try. I see this in lspci
[...]
and this in dmesg
[...]
which then later detects the sdb partitions.
This means that you would need to compile the following into the kernel:
CONFIG_PCI
CONFIG_SCSI
On Saturday 13 December 2008 00:54:27 Harry Putnam wrote:
Thanks for your patience Dirk.
You're welcome.
Bye...
Dirk
Nikos Chantziaras rea...@arcor.de writes:
Harry Putnam wrote:
Nikos Chantziaras rea...@arcor.de writes:
Harry Putnam wrote:
Nikos Chantziaras rea...@arcor.de writes:
[...]
mptbase: ioc0: Initiating bringup
ioc0: LSI53C1030 B0: Capabilities={Initiator}
scsi4 : ioc0: LSI53C1030 B0,
Harry Putnam wrote:
[...]
I then tried copying as best I can from the working kernel config of
2.6.24-r8 by running menuconfig in that directory and
genkernel --menuconfig all in the new kernel directory.
I'd already tried the same thing but without genkernel... just calling
make after
Nikos Chantziaras wrote:
[...]
Just to make sure you're doing it right...
[...]
Forgot to mention that no initrd is needed and the grub.conf should not
have an inird line.
Dirk Heinrichs dirk.heinri...@online.de writes:
From that and the contents of the original initrd you posted in the
former thread and what others already found out:
This initrd has all all sorts of driver modules for SATA and SCSI
chipsets, so it's most likely that you forgot to compile in
Dirk Heinrichs dirk.heinri...@online.de writes:
Forgot this one: dmesg output from the working setup.
www.jtan.com/~reader/kdiag/dmesg.html
Nikos Chantziaras rea...@arcor.de writes:
Nikos Chantziaras wrote:
[...]
Just to make sure you're doing it right...
[...]
Forgot to mention that no initrd is needed and the grub.conf should
not have an inird line.
Ok Nikos... I'm going to do that right now but of course it will take
a
Am Donnerstag, den 11.12.2008, 16:59 -0600 schrieb ext Harry Putnam:
These URLS seem to be loading kind of slow right now:
Hmm, unfortunately they don't load at all because of DNS failure. The
machine name is unknown.
Just put the files into a gzipped tar archive and attach that.
Bye...
Harry Putnam wrote:
[...]
It worked just fine. But none of my attempts to bring the kernel up
to date have worked. All failing with a error message something like:
`/dev/sdb3 is not a valid device'.
According to your screenshot, you don't even have an sdb. All the
kernel sees is one hard
Nikos Chantziaras [EMAIL PROTECTED] writes:
Harry Putnam wrote:
[...]
It worked just fine. But none of my attempts to bring the kernel up
to date have worked. All failing with a error message something like:
`/dev/sdb3 is not a valid device'.
According to your screenshot, you don't even
Harry Putnam wrote:
Nikos Chantziaras [EMAIL PROTECTED] writes:
Harry Putnam wrote:
[...]
It worked just fine. But none of my attempts to bring the kernel up
to date have worked. All failing with a error message something like:
`/dev/sdb3 is not a valid device'.
According to your
Nikos Chantziaras [EMAIL PROTECTED] writes:
Harry Putnam wrote:
[...]
It worked just fine. But none of my attempts to bring the kernel up
to date have worked. All failing with a error message something like:
`/dev/sdb3 is not a valid device'.
According to your screenshot, you don't even
Harry Putnam wrote:
[...]
About sdb3. In the following dmesg output (when booting with a
working kernel-2.6.24-r8 I wondered if anyone can determine what
driver is involved there. I couldn't really tell much from it other
than the kernel sees it with no problem:
Nikos Chantziaras [EMAIL PROTECTED] writes:
[...]
mptbase: ioc0: Initiating bringup
ioc0: LSI53C1030 B0: Capabilities={Initiator}
scsi4 : ioc0: LSI53C1030 B0, FwRev=h, Ports=1, MaxQ=128, IRQ=16
That's an LSI Fusion-MPT controller. Enable:
Device Drivers-[*] Fusion MPT device
[EMAIL PROTECTED] writes:
My guess is tha while inside the initrd a kenrel module was loaded
and it was something that you needed to read the boot volume. Are
you statically or modulely including your sata drivers? Sent via
BlackBerry from T-Mobile
kyle, how can I discover what is in the
Harry Putnam wrote:
Nikos Chantziaras [EMAIL PROTECTED] writes:
[...]
mptbase: ioc0: Initiating bringup
ioc0: LSI53C1030 B0: Capabilities={Initiator}
scsi4 : ioc0: LSI53C1030 B0, FwRev=h, Ports=1, MaxQ=128, IRQ=16
That's an LSI Fusion-MPT controller. Enable:
Device Drivers-[*]
Nikos Chantziaras [EMAIL PROTECTED] writes:
Harry Putnam wrote:
Nikos Chantziaras [EMAIL PROTECTED] writes:
[...]
mptbase: ioc0: Initiating bringup
ioc0: LSI53C1030 B0: Capabilities={Initiator}
scsi4 : ioc0: LSI53C1030 B0, FwRev=h, Ports=1, MaxQ=128, IRQ=16
That's an LSI
Harry Putnam wrote:
Nikos Chantziaras [EMAIL PROTECTED] writes:
Harry Putnam wrote:
Nikos Chantziaras [EMAIL PROTECTED] writes:
[...]
mptbase: ioc0: Initiating bringup
ioc0: LSI53C1030 B0: Capabilities={Initiator}
scsi4 : ioc0: LSI53C1030 B0, FwRev=h, Ports=1, MaxQ=128, IRQ=16
[EMAIL PROTECTED]
Date: Thu, 11 Dec 2008 08:24:08
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Tragic kernel building for vmware gentoo guest on
WinXP
Harry Putnam wrote:
Nikos Chantziaras [EMAIL PROTECTED] writes:
Harry Putnam wrote:
Nikos Chantziaras [EMAIL PROTECTED] writes
27 matches
Mail list logo
