[Fwd: Re: alsa problem]

[steef <steefvanduin@zonnet.nl>]

-------- Original Message --------
Subject: 	Re: alsa problem
Date: 	Thu, 26 May 2005 15:42:56 +0200
From: 	steef <steefvanduin@zonnet.nl>
Reply-To: 	steefvanduin@zonnet.nl
To: 	debian: gebruikerslijst <debian-user@lists.debian.org>
References: 	<[🔎] 20050525200707.9174.qmail@webmail28.rediffmail.com> 
<[🔎] 20050525202833.GI1108@pks.mpg.de> <[🔎] 42950B34.90200@hotmail.com> 
<[🔎] 429573DB.2030307@zonnet.nl> <[🔎] 20050526122605.GC6538@pks.mpg.de>



Ionut Georgescu wrote:

> We should wake up people, both of them ar wrong!!! :-)
>
> First, we are loading the kernel itself as an initrd image :-))
> Second, it cannot be append, because initrd is the boot loader's task.
>
> So:
>
> image=/boot/vmlinuz-2.4.27-2-686
>     label=Linux-2.4.27
>     initrd=/boot/initrd.img-2.4.27-2-686
>     read-only
>
> lilo
>
> On Thu, May 26, 2005 at 08:59:39AM +0200, steef wrote:
>  
>
> > Colin wrote:
> >
> >    
> >
> > > Ionut Georgescu wrote:
> > >
> > >
> > >      
> > >
> > > > default=Linux-2.4.27
> > > > image=/boot/vmlinuz-2.4.27-2-686
> > > >      label=Linux-2.4.27
> > > > 	append="initrd=image=/boot/vmlinuz-2.4.27-2-686"
> > > > 	read-only
> > > >  
> > > >
> > > >        
> > > I thought initrd can go on a line of its own like:
> > >
> > > image=/boot/vmlinuz-2.4.27-2-686
> > > 	label=Linux-2.4.27
> > > 	initrd=/boot/vmlinuz-2.4.27-2-686
> > > 	read-only
> > >
> > > Well, I use grub now so my memory could be fading. ;-)
> > >
> > >
> > >
> > >
> > >      
> > that last sentence is correct with woody. on one hard disk i still use 
> > woody. as backup for work.
> > if you do under woody a kernel upgrade you had better install 
> > initrd-tools before allthough not strictly necessary at that moment.
> >
> > steef
> >
> >
> > --
> > To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
> > with a subject of "unsubscribe". Trouble? Contact 
> > listmaster@lists.debian.org
> >
> >
> >
> >    
no!  if you do a kernel-upgrade under woody p.e. from 2.2 to 2.4, and 
you start with the kernel-headers you must after that of course install 
the corresponding kernel-image. in my experience the chap who put this 
2.4 or other image in kpackage put a thread in it. this thread asks you 
if: 'you have installed from scrap, uh?? and then 'debian/kpackage' asks 
you if you will be so kind to add a line in lilo: something like 
initrd=/initrd.img and asks again if it must make a symlinc from lilo to 
the kernelimage in /boot. at that point. if i remember well, 
initrd-tools-package is already installed.

kpackage proceeds asking if it will change lilo-make-up. i said allways 
'no' at that point.
further try out the procedure for yourself to fresh up your memory 
completely. last time i did this was i guess two months ago.

kind regards,

steef