Hi

Am 15.03.2008 13:15, marksouth schrieb:
>
> The current Sid kernel was 2.6.23 last time I looked, you give that a
> try, it would only take a little apt-get incantation.

Good to know, but not an option for me. I'm trying to install a
machine which is as close as possible to a root server I own. I've
chosen the Debian version of their offer, which means Debian "stable".

> I am puzzled a little by your story though: why not build the kernel the
> Debian way? The manual way is asking for trouble compared to all the
> automation that Debian provides.

Simply because I'm used to doing that in all my machines. My
understandig is that Debian supports manually compiled kernels.

regards
Arun

On Sat, 15 Mar 2008 20:48:04 +0100, Arun Dev wrote:

> Hi
>
> Am 15.03.2008 13:15, marksouth schrieb:
>>
>> The current Sid kernel was 2.6.23 last time I looked, you give that a
>> try, it would only take a little apt-get incantation.
>
> Good to know, but not an option for me. I'm trying to install a machine
> which is as close as possible to a root server I own. I've chosen the
> Debian version of their offer, which means Debian "stable".

You misunderstand me. I mean that there are later kernels in easily
accessible Debian repositories. No need to track Sid just to snag a
kernel.

>> I am puzzled a little by your story though: why not build the kernel
>> the Debian way? The manual way is asking for trouble compared to all
>> the automation that Debian provides.
>
> Simply because I'm used to doing that in all my machines. My
> understandig is that Debian supports manually compiled kernels.

I don't think Debian has a prejudice about manually compiled kernels, but
the thing that sets Debian apart from other distros is its level of
automation.

If you want to do everything manually you should be using Slackware.

To a.o.l.d

Am 15.03.2008 00:15, Arun Dev schrieb:
>
> The new kernel starts booting an halts at "Waiting for root
> device".
> [...]
>
> What am I doing wrong?

Thanks for all your hints and suggestions! This is a very helpful
newsgroup I must say.

Unfortunately I don't have access to the machine over the weekend.
It will be Monday late afternoon till start again. Will report back.

Arun

I demand that Anton Ertl may or may not have written...

> Arun Dev <nospam@pleaz.xy> writes:
>> My understanding is that Debian supports manually compiled kernels.

> Yes. I'm running a manually compiled kernel.org 2.6.19 kernel with perfctr
> patch on my home machine. Lately I have switched to building kernels the
> Debian way because it's less work

Or at least more convenient. :-)

> (but it's also much less educational than configuring a kernel and reading
> lots of informative help texts).

I thought that it was possible to do that *and* use make-kpkg. Clearly I'm
doing something wrong. ;-)

[snip]
--
| Darren Salt | linux or ds at | nr. Ashington, | Toon
| RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army
| + Interception of this message for advertising purposes is not permitted.

How come all the buttons keep flying off my shirt?

On Mar 16, 4:48 pm, Arun Dev <nos...@pleaz.xy> wrote:

> Thanks for all your hints and suggestions! This is a very helpful
> newsgroup I must say.
>
> Unfortunately I don't have access to the machine over the weekend.
> It will be Monday late afternoon till start again. Will report back.
>
> Arun

Ok, here are some good sites (and pages) which I use a lot to find
more advanced, and not so advanced, stuff:
http://wiki.debian.org/
* http://wiki.debian.org/KernelPackage
* http://wiki.debian.org/HowToRebuildA...nKernelPackage
* http://wiki.debian.org/KernelPage
* http://wiki.debian.org/DebianKernelDebconf5Paper
* http://wiki.debian.org/DebianKernelCustomCompilation

http://www.debian-administration.org/

http://debaday.debian.net/

Good luck.

Darren Salt <news@youmustbejoking.demon.cu.invalid> writes:
>I demand that Anton Ertl may or may not have written...
>
>> Arun Dev <nospam@pleaz.xy> writes:
>>> My understanding is that Debian supports manually compiled kernels.
>
>> Yes. I'm running a manually compiled kernel.org 2.6.19 kernel with perfctr
>> patch on my home machine. Lately I have switched to building kernels the
>> Debian way because it's less work
>
>Or at least more convenient. :-)
>
>> (but it's also much less educational than configuring a kernel and reading
>> lots of informative help texts).
>
>I thought that it was possible to do that *and* use make-kpkg.

Sure it's possible, but then all the savings (in terms of time and
work) of using make-kpkg go away (at least for me), so there's no
reason for me to use make-kpkg then.

- anton
--
M. Anton Ertl Some things have to be seen to be believed
anton@mips.complang.tuwien.ac.at Most things have to be believed to be seen
http://www.complang.tuwien.ac.at/anton/home.html

Hi all

Am 17.03.2008 17:15, AJackson schrieb:
> On Mar 16, 4:48 pm, Arun Dev <nos...@pleaz.xy> wrote:
>
>> Thanks for all your hints and suggestions! This is a very helpful
>> newsgroup I must say.
>>
>> Unfortunately I don't have access to the machine over the weekend.
>> It will be Monday late afternoon till start again. Will report back.

Well, I have the vanilla kernel 2.6.19 (unpatched) compiled the Linus-
way (cp /boot/config-xxxx $SRC; cd $SRC; make oldconfig; make
menuconfig; make bzImage; cp arch/x86/boot/bzImage /boot/vmlinux-xxx;
vi menu.lst).

The problem was that I _need_ a different initrd.

"yaird --output=/boot/initrd-xxxx 2.6.19" made me one, provided
a) I've copied the .config as /boot/config-2.6.19 and
b) did "make modules ; make modules_install"

Now the former condition I understand but not the latter. Why do I
need to compile modules and install them if I don't need any? This
is a server, with "make menuconfig" I've told the drivers for the
filesystem and the network to be compiled into the kernel.

I've reasons not to compile modules:
a) compiling the modules takes _hours_
b) more software you have more things to look after!

I have dozens of computers running without compiling modules, but
not this one. Can somebody explain me why?

Anyway it is good to know that Debian hasn't burned the bridges
unlike *ubuntu.

Cheers
Arun

P.S. Ajackson, thanks for the literature, very useful!

Arun Dev <nospam@pleaz.xy> writes:
>Well, I have the vanilla kernel 2.6.19 (unpatched) compiled the Linus-
>way (cp /boot/config-xxxx $SRC; cd $SRC; make oldconfig; make
>menuconfig; make bzImage; cp arch/x86/boot/bzImage /boot/vmlinux-xxx;
>vi menu.lst).
>
>The problem was that I _need_ a different initrd.
....
>Now the former condition I understand but not the latter. Why do I
>need to compile modules and install them if I don't need any? This
>is a server, with "make menuconfig" I've told the drivers for the
>filesystem and the network to be compiled into the kernel.

If you don't need modules, you don't need an initrd. E.g., on my home
machine I use a manually built kernel without an initrd. In that case
just leave the initrd line away in the menu.lst.

- anton
--
M. Anton Ertl Some things have to be seen to be believed
anton@mips.complang.tuwien.ac.at Most things have to be believed to be seen
http://www.complang.tuwien.ac.at/anton/home.html

Hi anton

Am 20.03.2008 19:51, Anton Ertl schrieb:
> Arun Dev <nospam@pleaz.xy> writes:
>>
>> The problem was that I _need_ a different initrd.
> ...
>
> If you don't need modules, you don't need an initrd. E.g., on my home
> machine I use a manually built kernel without an initrd. In that case
> just leave the initrd line away in the menu.lst.

That's what I thought too. I did not have a initrd line in Grub and
getting "Waiting for root file system". Only then I compiled and
installed the module, made this initrd and added to Grup, it came up!

I'm still looking for an explanation.

Arun

Arun Dev <nospam@pleaz.xy>:
> Hi anton
>
> Am 20.03.2008 19:51, Anton Ertl schrieb:
> > Arun Dev <nospam@pleaz.xy> writes:
> >>
> >> The problem was that I _need_ a different initrd.
> > ...
> >
> > If you don't need modules, you don't need an initrd. E.g., on my home
> > machine I use a manually built kernel without an initrd. In that case
> > just leave the initrd line away in the menu.lst.
>
> That's what I thought too. I did not have a initrd line in Grub and
> getting "Waiting for root file system". Only then I compiled and
> installed the module, made this initrd and added to Grup, it came up!

What did you tell make menuconfig to do about your root file system
support? If it was compiled into the kernel, then modules and initrd
are unnecessary.


--
Any technology distinguishable from magic is insufficiently advanced.
(*) http://blinkynet.net/comp/uip5.html Linux Counter #80292
- - http://www.faqs.org/rfcs/rfc1855.html Please, don't Cc: me.