On Mon, 23 Aug 2004, Veli-Pekka Tatila wrote: > output: > ERROR: No Sound Modules found > You don't seem to be running a kernel with modular sound > enabled. (soundcore.o was not found in the module search path). > To use sndconfig, you must be running a kernel with modular > sound, such as the kernel images shipped with Debian Linux or > a 2.2 or greater kernel. > end of output > > What does this mean in more detail? this means that the tool youa re using can/t find the soundcore.o module which should be part of the kernel-package. I find this somehwat weird cause it should be there. modules are stored in /lib/modules/<kernel-version>/ and subdirs
> You are attempting to install an initrd kernel image (version 2.6.7-1-686) > This will not work unless you have configured your boot loader to use > initrd. (An initrd image is a kernel image that expects to use an INITial > Ram Disk to mount a minimal root file system into RAM and use that for > booting). > > As a reminder, in order to configure LILO, you need > to add an 'initrd=/initrd.img' to the image=/vmlinuz > stanza of your /etc/lilo.conf nweer debian kernels seam to use these small images to bootup. Dunno why though, but that's not the isssue hehre. It indeed simply needs the initrd=<imagenmae> line in the /etc/lilo.conf > I repeat, You need to configure your boot loader -- please read your > bootloader documentation for details on how to add initrd images. man lilo.conf I believe. > If you have already done so, and you wish to get rid of this message, > please put > `do_initrd = Yes' > in /etc/kernel-img.conf. Note that this is optional, but if you do not, > you'll continue to see this message whenever you install a kernel > image using initrd. meaning, it shows this message even if your lilo.conf indeed is correct (as far as I can tell thatis. > Do you want to stop now? [Y/n]y > Ok, Aborting > dpkg: error processing > /var/cache/apt/archives/kernel-image-2.6.7-1-686_2.6.7-2_ > i386.deb (--unpack): > subprocess pre-installation script returned error exit status 1 > Errors were encountered while processing: > /var/cache/apt/archives/kernel-image-2.6.7-1-686_2.6.7-2_i386.deb > E: Sub-process /usr/bin/dpkg returned an error code (1) > celeron:~# > end of output this is default dpkg-stuff, your install-process faield with statuscode nonzero, so the install fails with an error. > I have not even looked at any lilo config file yet but went with the default > setting during installation so to speak. I don't even know what's on the > lilo menu, I just know that if I type linux console=ttyS0 at bootup, it > seems to forward all text to the serial port. I've got 3 partitions: boot, > swap and root(?) only. My processor is a Celeron, by the way, as you > probably guessed judjing by the above output. I tend to name machines on a > LAN basesd on their type, I've got another named T-Bird here also, which is > my main music machine. well, one other thing is that you have to look if the -686 kernel is usabel for your cpu. Its pentinium-II at least. > I think I'm stil running the 2.2 kernel based on the output receied at > bootup. How do I check the kernel version? I suppose it should be easy. I've > tried apropos kernel as well as Googling for displaying linux kernel version > but with no luck so far. uname -r does the trick. But I'm sure you are still running the 2.2. kernenl, cause the install failed (look at your dpkg-output). > Finally, when I do get the kernel updated, do I have to do any manual > configuring to ensure that it keeps the serial console support? I would not > want to lose it at this point as accessing the machine through the serial > port seems to be the best option I've got currently running. There are no > screen readers yet and it is easier and faster to read the output with a > familiar Windows screen reader, namely Supernova, than it would be with > X-zoom. yes, well what you could do is add append="console=ttyS0" ot the relevent section in your lilo.conf or even out of a section to make it a global option. This ensures you don't have to type it on the commandlien anymore. For the most part the kernel-image should do everything else. Maybe you need to check if that initrd= line is indeed there. > Any help greatly appreciated. > well the kernel-howto won't help you here. And this is all I know cause I'm compiling/installling manually. -- Andor Demarteau E-mail: [EMAIL PROTECTED] student computer science www: http://www.students.cs.uu.nl/~ademarte/ UU based & VU guest-student jabber,icq,msn,voip: do ask ;) ----------- chairman Stichting Studiereizen STORM www: http://www.stistusto.nl vice-chairman USF Studentenbelangen executive committee 2002-2003
