Sorry I misunderstood. I still recommend the same thing, only tell the Linux kernel to use the serial port as the console, console=ttyS0,115200
You don't want to try to capture the actual VGA probably. Good luck, Myles > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Friday, January 11, 2008 2:52 PM > To: [EMAIL PROTECTED] > Cc: 'LinuxBIOS' > Subject: Re: [LinuxBIOS] AMD SimNOW question > > No the serial port output looks ok. It is the "vga" ouput I need to > capture. The kernel as loader is crashing... > > /********************* > Marc Karasek > MTS > Sun Microsystems > mailto:[EMAIL PROTECTED] > ph:770.360.6415 > *********************/ > > > > Myles Watson wrote: > > There are a couple of ways, which you can find here: > > > > http://linuxbios.org/AMD_SimNow > > > > if you want it to go to a file, instead of > > > > cat /home/myles/.simnow/com1/simnow_out > > > > try > > > > cat /home/myles/.simnow/com1/simnow_out > myfile.log > > > > otherwise, if you're using snserial there is some option to do that as > well. > > > > Myles > > > > > >> -----Original Message----- > >> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > >> Sent: Friday, January 11, 2008 2:33 PM > >> To: Myles Watson; LinuxBIOS > >> Subject: Re: [LinuxBIOS] AMD SimNOW question > >> > >> Is there anyway under SimNow to send the console output to a log file. > >> > >> I have linuxbios up and running :-) but the Linux kernel I have as a > >> boot loader is crashing.. I have tried to stop it at the point when it > >> starts dmping the same message to the screen but it is nearly > impossible > >> to time it right. > >> > >> /********************* > >> Marc Karasek > >> MTS > >> Sun Microsystems > >> mailto:[EMAIL PROTECTED] > >> ph:770.360.6415 > >> *********************/ > >> > >> > >> > >> Myles Watson wrote: > >> > >>> Marc, > >>> > >>> I sent the wrong one for serengeti-cheetah last time. Sorry. > >>> > >>> Myles > >>> > >>> On Jan 11, 2008 11:49 AM, Marc Karasek <[EMAIL PROTECTED]> wrote: > >>> > >>> > >>>> I have managed to cobble together a build structure that tries to > >>>> > >> build. > >> > >>>> It gets to the point of building the linuxbios image and it chokes > >>>> because the image is to large for the romsize. > >>>> > >>>> Can someone shed some light on what Config.lb should be set to to get > >>>> this to compile. > >>>> > >>>> The payload buildrom is generating is 790,000+ bytes big. > >>>> > >>>> /********************* > >>>> Marc Karasek > >>>> MTS > >>>> Sun Microsystems > >>>> mailto:[EMAIL PROTECTED] > >>>> ph:770.360.6415 > >>>> *********************/ > >>>> > >>>> > >>>> > >>>> > >>>> ron minnich wrote: > >>>> > >>>> > >>>>> On Jan 8, 2008 2:38 PM, Marc Karasek <[EMAIL PROTECTED]> wrote: > >>>>> > >>>>> > >>>>> > >>>>>> I have found the main problem with svn. It looks like if you use > svn > >>>>>> > >> co > >> > >>>>>> http:// it will use the proxy settings under servers. If you do a > >>>>>> > >> svn > >> > >>>>>> co svn:// it tries to do a dns lookup, which fails behind a proxy > >>>>>> > >> server > >> > >>>>>> :-(. I have not been able to find any info on setting svn up to > use > >>>>>> > >> a > >> > >>>>>> proxy when doing svn:// type checkouts. > >>>>>> > >>>>>> > >>>>>> > >>>>> There is a way to do it, maybe: > >>>>> > >> http://subversion.tigris.org/faq.html#proxy > >> > >>>>> ron > >>>>> > >>>>> > >>>>> > > > > > > -- linuxbios mailing list linuxbios@linuxbios.org http://www.linuxbios.org/mailman/listinfo/linuxbios
