I need your help! My SuSE linux box (formerly 7.1...) stops at booting message "Setting up dummy0 device". I made a test and created a initrd for my kernel 2.4.14 (compiled by myself), in order to test vga=791 boot. First, when loading kernel at the beginning, screen got blank; I tried a ssh from another host of my home lan, but network was not available. I reset the machine, and I booted the other kernel so it would be made some changes. Result, the same error. But, when I do Ctrl-Alt-Del (the so called typical configuration of M$ keyboards), kernel works and it tries to close, but stops again when it has to be closed dummy device. I made an update to SuSE 7.2 (only kernel and base packages), thinking that this overwriting would be the answer (just like other times before). Result, the same error. Then I made an update to SuSE 7.3 (complete update: kernel and all packages). Result, the same error. Then again, I booted the other SuSE 7.1 in my second hard drive. I mounted the "wrong" partition (/dev/hdc3), entered it, and I made some changes again to lilo.conf, even in rc.config (where dummydev=no, even) but of course without any possibility to run SuSEconfig afterwards; I copied the bzImage of kernel 2.4.14 again in its place (mounted as /data1/boot/). When I rebooted for "i-don't-know-how-many-times" my machine, the result... the same error. Every Control-C was useless, without any action. Well, this is my short story, and my desperation. How can I solve this? Is this any place in the disk where I can apply changes in so my until yesterday quite perfect SuSE 7.1? Is this a hardware error? Is there any kernel module I can delete or arrange? If SuSE boot process would be just like that of Mandrake (interactive boot which lets pass through any misconfiguration at boot time...) Many thanks in advance and I would thank any piece of advice from you. Alejandro. --