Who has met such problem? I changed the linuxbios to direct message to com2 via changing 1. SP1 to SP2 in auto.c 2. enable com2 in Config.lb 3. change 0x3f8 to 0x2f8 in Options.lb
Etherboot change 0x3f8 to 0x2f8. Then After Ethertboot get the elf image from tftp server, it will hang a while (30s) at "Firmware type: LinuxBIOS", and that message is not shown. I remember several months ago, when I make message comes to both ports (COM1 and COM2), it worked well.... Weird. Regards YH [tg3-5703X]Ethernet addr: 00:E0:81:27:2D:30 Tigon3 [partno(BCM95703A30) rev 1002 PHY(5703)] (PCIX:100MHz:64-bit) Link is up at 1000 Mbps, full duplex. TX RX flow control Searching for server (DHCP)... ..Me: 192.168.1.191, Server: 192.168.1.1, Gateway 192.168.1.1 Loading 192.168.1.1:ram0_2.5_2.6.9_k8.2_mydisk8_com2.elf ...(ELF)... ............................................................... ....................................................... ............................................................................ ...............................................done (Firmware type: LinuxBIOS) old bootloader convention, maybe loadlin? Bootdata ok (command line is root=/dev/ram0 rw console=ttyS0,115200n8 ) Linux version 2.6.9 ([EMAIL PROTECTED]) (gcc version 3.3.3 (SuSE Linux)) #15 SMP Mon Nov 22 14:53:36 PST 2004 _______________________________________________ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
