(To those of you, including myself, who have seen the message already, I apologize. I am resending the message block, with more information, for why I need, or want, to do that, and something else with it.) Hello from Gregg C Levine actually with Jedi Knight Computers A question for those of you, who have gotten GRUB to work over, say a serial terminal hookup. Besides the obvious, that of specifying it, on the command line for the configuration script, can that same terminal output, provide debugging data? Or be configured to do so? I am in the process of designing an embedded device, it will operate headless, such that it gets started up via a serial hookup, or even a Ethernet port. And through that connection, it will supply the usual menu screen, or just boot directly to its embedded operating system. For now, it will display the menu screen, it will be booting a form of a DOS based product, which is all I can say, right now. ( Or an embeddable version of Linux! ) For more information please contact me off list. Now as to what I have done. I have downloaded the entire clutch of version 0.90 software, and glommed the current stuff in CVS. When I issue the command string to start the configuration script, I append "--enable serial". Then do the rest of it, and create my disk set the usual way. But when I boot the disk, I get this screen: GRUB Loading Stage2...................... GRUB Loading Stage2...................... GRUB Loading Stage2...................... GRUB Loading Stage2...................... GRUB And as all of you can see, it hangs there. But when I boot from a regular disk set, to which I have added the default menu.lst file from the /doc directory, it works. Should I have added to the configuration sequence a port number? Or does that sequence select it? I shall also study the info pages to see for myself. Oh, and once the correct one has been set, to what should I set my terminal emulator for baud rate? Or would that be the same from the boot loader's point of view? ------------------- Gregg C Levine mailto:[EMAIL PROTECTED] ------------------------------------------------------------ "The Force will be with you...Always." Obi-Wan Kenobi "Use the Force, Luke."� Obi-Wan Kenobi (This company dedicates this E-Mail to General Obi-Wan Kenobi (Perhaps one of the most powerful of all of the Jedi Knights)) (This company dedicates this E-Mail to Master Yoda���������������������� (Perhaps the other one of the most powerful of all of the Jedi Knights)) And the favorite line by Anonymous "May the Force be with you." > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of > Gregg C Levine > Sent: Friday, August 24, 2001 10:31 PM > To: Bug-Grub > Subject: Consoles and GRUB > > Hello from Gregg C Levine actually with Jedi Knight Computers > A question for those of you, who have gotten GRUB to work over, say a > serial terminal hookup. Besides the obvious, that of specifying it, on > the command line for the configuration script, can that same terminal > output, provide debugging data? Or be configured to do so? > ------------------- > Gregg C Levine mailto:[EMAIL PROTECTED] > ------------------------------------------------------------ > "The Force will be with you...Always." Obi-Wan Kenobi > "Use the Force, Luke."� Obi-Wan Kenobi > (This company dedicates this E-Mail to General Obi-Wan Kenobi (Perhaps > one of the most powerful of all of the Jedi Knights)) > (This company dedicates this E-Mail to Master Yoda > (Perhaps the other one of the most powerful of all of the Jedi Knights)) > And the favorite line by Anonymous "May the Force be with you." > > > > > _______________________________________________ > Bug-grub mailing list > [EMAIL PROTECTED] > http://mail.gnu.org/mailman/listinfo/bug-grub > _______________________________________________ Bug-grub mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-grub
