Hello John, thanks for the info. > Were any modules built with your kernel? I always install with > "make modules_install install". This will install kernel and modules > modules, and > build a new initrd.img file. This file should be referenced in the kernel > command > line defined in palo.conf. Actually I built the kernel with all the needed drivers already embedded. And,although the module support is enabled, I really didn't configure any module, because my aim is to make a module-less kernel for a initrd-less system. My C3750 is not likely to change its hardware in the future so I don't need the flexibility of the module/initrd system.
Clearly I either configured something that make conflict each other, or I forgot something else. The point is, what is the problem? > For example, I have the following in my > palo.conf: > > --commandline=2/vmlinux root=/dev/sda5 console=ttyS1 initrd=2/initrd.img > HOME=/ rootfstype=ext3 Now that I think about it, when I tried to boot the new kernel I didn't remove from the palo ipl command line the initrd of the former kernel. However, since the kernel version is different, it shouldn't load any module. I'll try again without the former initrd. > This switches over at just after the palo message. You will lose console > ouput if you select the > wrong console port. You should see something like the following: The console I have now is on ttyS0, and with the older kernel it works. I don't think the new kernel change the serial port numbering? Is there something else I can do to diagnose the problem? Thank you so much Paolo -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/caou17umrehdhprty19wlacuvl8cevcz-iwddmqgfxbmq--9...@mail.gmail.com
