It seems that mkelfImage should get the com address from commandline.
For example: mkelfImage --command-line="ramdisk_size=65536 root=/dev/ram0 rw console=tty0 console=ttyS1,115200n8" --kernel=linuxkernel/bzImage_2. 6.9_k8.2 --ramdisk=rootfs/mydisk8_com2.gz --output=elf/ram0_2.5_2.6.9_k8.2_mydisk8_com2.elf
Then makeelfImage should use 0x2f8 instead of 0x3f8 in convert_params.c according to ttyS1.
Regards
YH
-----Original Message----- From: YhLu Sent: Monday, November 22, 2004 6:20 PM To: YhLu; ebiederman@lnxi.com Cc: linuxbios@clustermatic.org; etherboot-users@lists.sourceforge.net Subject: RE: [Etherboot-users] Direct message to com2
It's in mkelfImage 2.5 linux-i386/ convert_params.c
it is hardcode to 0x3f8.
YH
-----Original Message----- From: YhLu Sent: Monday, November 22, 2004 6:05 PM To: ebiederman@lnxi.com Cc: linuxbios@clustermatic.org; etherboot-users@lists.sourceforge.net Subject: RE: [Etherboot-users] Direct message to com2
Eric, I add second serial_x.c to support com2. then it works well.
The "Firmware type: LinuxBIOS" only comes out in COM1.
Which segement print " Firmware type: LinuxBIOS" ?, it seems hardcoded to use 0x3f8.
Regards
YH
-----Original Message----- From: YhLu Sent: Monday, November 22, 2004 3:04 PM To: linuxbios@clustermatic.org; ebiederman@lnxi.com; etherboot-users@lists.sourceforge.net Subject: [Etherboot-users] Direct message to com2
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 (root@tst288xsuse9) (gcc version 3.3.3 (SuSE Linux)) #15 SMP Mon Nov 22 14:53:36 PST 2004
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Etherboot-users mailing list Etherboot-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/etherboot-users
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Etherboot-users mailing list Etherboot-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/etherboot-users