[EMAIL PROTECTED] wrote: > > Are you using a 2.4 kernel? I'm afraid the default kernel is a 2.2 kernel. > > Either install a newer one or enter "bf2.4" at the CD boot prompt... > > Yes, you were right - the default kernel ist still 2.2.20 with Debian GNU > Linux 3.0 (!). To be honest, I did not expect that any recent distribution > would not come with Kernel 2.4.x, so I didn't even check it. Shame on me ;-)
When woody froze for release the 2.4 kernel was that new, untested and somewhat flakey kernel of the future, not the old reliable trusted friend that we know it to be today. Look back two years from now and you will see that the current 2.4.20 kernel will be viewed as an old kernel and who would be using any such ancient thing. It is all relative. > I installed Kernel 2.4.18-k7, but this was not trivial since the > installation did not generate a valid modules.conf automatically (as > I would have expected), so I had to manually enter all the modules > for the machine hardware (like Ethernet, SCSI, sound etc.). Debian currently does not have any automatic hardware detection. You need to know what hardware you have installed and to configure that hardware in /etc/modules. The lack of any automatic hardware discovery is a well known and well thrashed issue with Debian. The new debian-installer project well under way today is addressing that issue specifically in addition to many others. Please be patient. It is only an install issue. It does not affect daily operation. I use the computer daily. But I installed the software only once. Also, the file you refer to is not the correct location for your modules. You should list those in /etc/modules instead of /etc/modules.conf. That was was probably your main problem. The /etc/modules.conf file is automatically generated from another set of files. You changes may be overwritten in the future. One would normally either edit /etc/modules and place their list there, or use the 'modconf' utility to help them do that. I recommend 'modconf' since it has some safety built it. > Hopefully this problem will also be fixed with Debian 3.1 ? I think > many Linux Newbies will find it difficult to manually figure out > their hardware configuration. Yes. > I also noticed that there is still KDE 2.2.2 included, I think I need to > generate an image with KDE 3.1 updates for our customers. This might be > a non-trivial task too. The same discussion above concerning versions of the kernel applies to versions of KDE as well. In this case it is as if the development lab (kde.org) has released the bits but manufacturing (debian.org) has not finished packaging, integrating and testing them and the other ten thousand packages currently in the distribution to the point of releasing them as the next official stable release. One must have patience for rock solid stability. With such a large distribution there is a lot going on. But the bleeding edge is always available. Install the stable release and then upgrade your bits to the "today's build" of 'unstable'. There you will find the very latest versions of most software packages. Software in 'unstable' is updated frequently by their maintainers. By testing and reporting any bugs or issues found in those latest packages you will be improving the stability of the next 'stable' release. For your needs you might wish to try the KNOPPIX image. It features both automatic hardware detection and the latest KDE bits. I highly recommend it. http://www.knopper.net/knoppix/index-en.html This list debian-cd is really not the right place to be discussing installation issues. That is well beyond the issues of the cd. A better place to discuss these other topics would be debian-user which is the user support discussion list for Debian. If you would be so kind as to ask your further questions not related to cd's in debian-user I believe you will find a large helpful user community there. Bob
pgpJT1mheJIqe.pgp
Description: PGP signature
