Amax wrote:
On Tue, 25 Aug 2009 00:50:10 +0200, Bernard wrote:
<- snip -->
The initrd.img that I have on my working system, as well as those
initrd.img that 'mkinitrd' generates when requested, are not compressed
files. Filenames are : initrd.img-2.6.20-16-386 for instance. No .gz
b
On Tue, 25 Aug 2009 00:50:10 +0200, Bernard wrote:
<- snip -->
> The initrd.img that I have on my working system, as well as those
> initrd.img that 'mkinitrd' generates when requested, are not compressed
> files. Filenames are : initrd.img-2.6.20-16-386 for instance. No .gz
> behind. I s
Bernard wrote:
>>
>>You really could use the recent 2.6.30.4. There were different problems
>>with 2.6.20 to 2.6.30. I find 2.6.30.4 the best I've had since 2.6.20.
>>
>>
> I tried 2.6.30.4. Same result as with 2.6.26.2 : compiles without
> errors, but crashes on boot.
>
so you are missing som
Emanoil Kotsev wrote:
Bernard wrote:
Emanoil Kotsev wrote:
Bernard wrote:
Compiling md in the kernel is the right approach to boot from raided root
without initrd. You can try this just skipping (deleteing the line in grub
temporary)
I just tried that. Raid compiled int
Bernard wrote:
> Emanoil Kotsev wrote:
>
>>Bernard wrote:
>>
>>
>>
>>
>>Compiling md in the kernel is the right approach to boot from raided root
>>without initrd. You can try this just skipping (deleteing the line in grub
>>temporary)
>>
>>
> I just tried that. Raid compiled into the kernel
Emanoil Kotsev wrote:
Bernard wrote:
Compiling md in the kernel is the right approach to boot from raided root
without initrd. You can try this just skipping (deleteing the line in grub
temporary)
I just tried that. Raid compiled into the kernel instead of modules. No
initrd. Still cra
Bernard wrote:
>
> 2.6.30.4 does compile all right, so does 2.6.26, but 2.6.20 does not.
you find out why in the archives
> Problem is that I still can't boot those I compiled, i.e. 2.6.26. because
> the initrd.img is buggy. I did find something, still it is not enough to
> get the process to w
Emanoil Kotsev wrote:
Emanoil Kotsev wrote:
Sorry forgot to write
Yes there is problem compiling the 2.6.20 with recent gcc
The problem is the compiler. If you are compiling just grab the last
version from kernel.org.
2.6.30.4 seems to be working fine
Just to be objective the gnu
> From: news [mailto:n...@ger.gmane.org] On Behalf Of Emanoil Kotsev
> Sent: Friday, August 21, 2009 1:55 PM
>
> Bernard wrote:
>
> > Emanoil Kotsev wrote:
> >
> >>Bernard wrote:
> >>
> >>
> >>
> >
> >
> >>
> >>why not just compile it on your notebook (or copy a compiled kernel)
> ?!
> >>
> >>you
Bernard wrote:
> Emanoil Kotsev wrote:
>
>>Bernard wrote:
>>
>>
>>
>
>
>>
>>why not just compile it on your notebook (or copy a compiled kernel) ?!
>>
>>you also can just disable the loading of the sound modules to make it more
>>simple.
>>
>>
>
> Things would be easy if all sound support
Emanoil Kotsev wrote:
try compiling the necessary modules _in_ the kernel.
This is the way it has been done.
So, I re-tried compiling after de-activating raid0 in the config,
leaving only raid1... to the same end result.
In the config it should be [*] not [M] if booting fro
Emanoil Kotsev wrote:
do you have a not raid boot partition, where you can put the initrd image?
My boot partition is not raid, or, at least, even though it is mirrored,
it remains in ext2fs, while the rest is in LVM2. So, the initrd image
that I am trying is available at start,
Emanoil Kotsev wrote:
Bernard wrote:
why not just compile it on your notebook (or copy a compiled kernel) ?!
you also can just disable the loading of the sound modules to make it more
simple.
Things would be easy if all sound support were in modules. But some
functions are part
Emanoil Kotsev wrote:
> Sorry forgot to write
>
> Yes there is problem compiling the 2.6.20 with recent gcc
>
> The problem is the compiler. If you are compiling just grab the last
> version from kernel.org.
>
> 2.6.30.4 seems to be working fine
>
Just to be objective the gnu compiler people
Sorry forgot to write
Yes there is problem compiling the 2.6.20 with recent gcc
The problem is the compiler. If you are compiling just grab the last version
from kernel.org.
2.6.30.4 seems to be working fine
>>
>> So, upon my failures to recompile kernel 2.6.20-16-386, I tried
>> downloading 2
Bernard wrote:
> Hi to Everyone,
>
> I need to re-compile my kernel so that it does not include sound support
> inside. I am running Debian 3.1 (Sarge). My system is on RAID1. My /boot
> partition is from /dev/sda1 (mirror on /dev/sdb1) installed on /dev/md0
> (ext3), while my '/' partition is fr
On Fri, Dec 05, 2003 at 10:00:48AM -0600, Hugo Vanwoerkom wrote:
> >In the file included from ksym.c:50:
> >/usr/src/kernel-source-2.4.18/include/asm/checksum.h:72:30: missing
> >termintating " character
>
> If you are using gcc 3.3, which you are if you ran dist-upgrade, it
> *will* complain of
Thomas H. George wrote:
My system is testing fully up-to-date. I just ran apt-get update and
apt-get dist-upgrade which installed kernel-source-2.4.18..
My current kernel was built from kernel-source-2.4.22 but I have been
experiencing irratic behavior - specifically many
p80211/knetdev_hard-s
On Mon, 6 Jul 1998, Shaleh wrote:
> > gcc: Internal compiler error: program cc1 got fatal signal 11
>
> sig11 (signal 11) is often a sign of a hardware problem. Either you
> machine is over/under clocked, over heating, has a memory glitch or
> something. Sig 11 can also be one of the problems
*-Patrick Olson ( 6 Jul)
|
| I've been running Debian 1.3.1 with kernel 2.0.29
|
| I decided to upgrade to kernel 2.0.34 but it fails during make zImage with
| an error message. Can anyone help?
|
| Here's the error message and a few of the lines before it:
|
| gcc -D__KERNEL__ -I/usr/src/linu
On Mon, 6 Jul 1998, Shaleh wrote:
> > gcc: Internal compiler error: program cc1 got fatal signal 11
>
> sig11 (signal 11) is often a sign of a hardware problem. Either you
> machine is over/under clocked, over heating, has a memory glitch or
> something. Sig 11 can also be one of the problems t
> gcc: Internal compiler error: program cc1 got fatal signal 11
sig11 (signal 11) is often a sign of a hardware problem. Either you
machine is over/under clocked, over heating, has a memory glitch or
something. Sig 11 can also be one of the problems that appears and then
never re-appears.
--
On Sun, 14 Sep 1997, Oliver Elphick wrote:
> In message <[EMAIL PROTECTED]>, writes:
> >Has anyone had any luck with compiling a kernel on Debian? I can compile
> [snip]
>
> I suggest that you use `make xconfig' or `make menuconfig' to set up
> your kernel configuration. That should leave the
In message <[EMAIL PROTECTED]>, writes:
>Has anyone had any luck with compiling a kernel on Debian? I can compile
>fine just as long as I don't try to compile with sound. NOTE: I did
>use the "make-kpkg -revision custom.1.0 kernel_image" option. This is the
>error I get (The same thing happ
> #error You will need to configure the sound driver with
> CONFIG_AUDIO option.
I had to manually edit the option file in the kernel directory (Forgot
its real name and am at work right now). Everytime I tried to specifiy
an IRQ it told me I typed an invalid number -- even the default 7.
--
TO
Lawrence Chim <[EMAIL PROTECTED]> writes:
> I have problem to compile the Linux kernel 2.0.28 using make-kpkg,
> here is a part of the screen dump, it didn't happen when I compiled
> 2.0.26
>
> MIDI interface support (CONFIG_MIDI) [Y/n/?]
> FM synthesizer (YM3812/OPL-3) support (CONFIG_YM3812) [
> I have problem to compile the Linux kernel 2.0.28 using make-kpkg,
> here is a part of the screen dump, it didn't happen when I compiled
> 2.0.26
This is because the behaviour of GNU expr regexps in shellutils 1.14 has
changed to be more POSIX-like, AND 2.0.28 has started using a different
metho
27 matches
Mail list logo
