[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: problem with pre-installed packages when using re-compiled kernel (solved)



Hi Jacob,

Thanks for your suggestion - it was big help!

Changing the config parameters (specifically
CONFIG_PACKET, CONFIG_FILTER) and re-compiling solved
the dhcp issue.

As for alsa, I just re-installed alsa-lib and
alsa-driver.

Thanks!
Deepa

--- Jacob S <stormspotter@6Texans.net> wrote:
> On Fri, 8 Apr 2005 11:58:47 -0700 (PDT)
> Deepa D <indebber@yahoo.com> wrote:
> 
> > Hi,
> > 
> > My name is Deepa. I am relatively new to linux,
> even
> > newer to Debian and the newest to this mailing
> list.
> 
> Welcome to the wonderful world of Debian! 
> 
> > I first installed Woody (2.4.18-bf2.4) and
> established
> > sound (alsa), network connectivity and so forth
> > successfully. I then compiled kernel-source-2.4.18
> > with tweaked kernel configs and added this booting
> > option in LILO. I am able to boot successfully
> with
> > either of these kernels.
> 
> Pretty good start for a newbie.
> 
> > I have noticed 2 problems though. 
> > 1. Alsa and kmix complain of a libasound.so.2 file
> > missing (no such file or directory). This file
> (upon
> > doing a find) is seen to reside deep in the /opt
> > directory and yet, is not being detected. This
> problem
> > is seen upon booting with either of the images. 
> 
> Did you get the alsa source via the alsa website? It
> sounds like you
> probably did not use Debian packages for it.
> "apt-get install
> libasound2" should install the Debian package that
> provides
> libasound.so.2 (it does on my Sarge box and I can't
> check a Woody box
> right now). 
> 
> Alternatively, there are ways to get Alsa and Kmix
> to see your
> libasound.so.2 file, but they are not recommended.
> Using the Debian
> package makes upgrades smoother, easier to install
> other packages that
> use Alsa, etc.
> 
> > 2. DHCP does not work in the newly compiled image.
> > dhclient complains of 'Protocol driver not
> attached'.
> 
> This sounds like you missed an option in your kernel
> config.
> Unfortunately, I am not expert enough with kernels
> and dhcp to remember
> which option that would be.
> 
> Did you happen to use the kernel config file from
> the 2.4.18-bf2.4 when
> compiling your new kernel? It's available in the
> /boot directory as
> config-2.4.18-bf2.4. This will help make sure that
> you have everything
> from the 2.4.18-bf2.4 kernel as a starting point for
> deciding which
> options to enable/disable in your new kernel.
> 
> > This has made me wonder if there is some work
> involved
> > in re-installing certain components. If so, what
> kind
> > of components and how can I have them work no
> matter
> > which debian image I'm running?
> 
> There are Debian recommended ways to do things, but
> once you learn them,
> I consider them to be *easier* than the 'manual'
> way. I've described a
> little bit of that, as it affects your current
> situation, above.
> 
> HTH,
> Jacob
>  
> 
> 
> -- 
> To UNSUBSCRIBE, email to
> debian-user-REQUEST@lists.debian.org 
> with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
> 
> 


		
__________________________________ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/



Reply to: