Hello,
I made a patch which make all bochs debug message can be seen from serial terminal. I think it might be useful if you want to apply ADLO to your own target.
you can apply this patch againt util/ADLO/bochs/bios/rombios.c by # patch -p0 < rombios-serial.patch
Regards,
to clarify. He's been working on getting ADLO running on EPIA-M.
He's been pretty succesfull so far.
Using serial console he's got both lilo and linux to boot using ADLO, so that you can use them pretty much "out of box" as long as you don't need video. However from what I heard you can get video once boot is done and you run some video program (TinyX Xvesa here).
As far as video goes, on cold-reboot he's getting :
Then, screen is blinkering with various color, but I can't see any text.
As far as video goes, on warm-reboot (after booting with original PC BIOS) he's getting :
If I first booted from original bios and reset with linuxbios + adlo, I can see text messages of original bios remained.
ideas on how to attack the issue?
Overall I would say that anyone who want to try get ADLO to work should start with serial console and leave VIDEO to the end given difficulty debugging binary-only module.
Another good idea is to try warm-boot from PC BIOS into ADLO at beginning of development/work on ADLO. It leaves you with somewhat functioning video-bios (or fully-functioning as it was for me).
On Sun, 20 Apr 2003 hcyun@etri.re.kr wrote:
Hello,
I made a patch which make all bochs debug message can be seen from serial terminal. I think it might be useful if you want to apply ADLO to your own target.
you can apply this patch againt util/ADLO/bochs/bios/rombios.c by # patch -p0 < rombios-serial.patch
Regards,
Hello from Gregg C Levine So I gathered from his earlier posts on this subject, and about that board specifically. But Adam, isn't ADLO board agnostic? By that I mean, that it does not need to know what motherboard it is being used on, unlike basic Linux BIOS. But, I am indeed watching this with interest. ------------------- Gregg C Levine hansolofalcon@worldnet.att.net ------------------------------------------------------------ "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 ) (This company dedicates this E-Mail to Master Yoda )
-----Original Message----- From: linuxbios-admin@clustermatic.org [mailto:linuxbios- admin@clustermatic.org] On Behalf Of Adam Sulmicki Sent: Saturday, April 19, 2003 11:32 AM To: hcyun@etri.re.kr Cc: linuxbios@clustermatic.org Subject: Re: serial debug patch for ADLO
to clarify. He's been working on getting ADLO running on EPIA-M.
He's been pretty succesfull so far.
Using serial console he's got both lilo and linux to boot using
ADLO, so
that you can use them pretty much "out of box" as long as you don't
need
video. However from what I heard you can get video once boot is done
and
you run some video program (TinyX Xvesa here).
As far as video goes, on cold-reboot he's getting :
Then, screen is blinkering with various color, but I can't see
any
text.
As far as video goes, on warm-reboot (after booting with original PC
BIOS)
he's getting :
If I first booted from original bios and reset with linuxbios
+
adlo, I can see text messages of original bios remained.
ideas on how to attack the issue?
Overall I would say that anyone who want to try get ADLO to work
should
start with serial console and leave VIDEO to the end given
difficulty
debugging binary-only module.
Another good idea is to try warm-boot from PC BIOS into ADLO at
beginning
of development/work on ADLO. It leaves you with somewhat functioning video-bios (or fully-functioning as it was for me).
On Sun, 20 Apr 2003 hcyun@etri.re.kr wrote:
Hello,
I made a patch which make all bochs debug message can be seen from
serial
terminal. I think it might be useful if you want to apply ADLO to your own
target.
you can apply this patch againt util/ADLO/bochs/bios/rombios.c by # patch -p0 < rombios-serial.patch
Regards,
-- Adam Sulmicki http://www.eax.com The Supreme Headquarters of the 32 bit
registers
Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
mostly yes, this is why he was able to get serial boot in just several hours of work.
the major quirks were that he needed to code up the patch for serial output for bochs to see what's going on. then reconfigure lilo for serial output. Then to the same with linux.
another issue was that while VIA EPIA-M has 128mb ram, upper 32 mb are revered for video. thus E820 map had to be modifed so that it shows 96mb of ram instead of 128mb to linux.
i think that's about it.
On Sat, 19 Apr 2003, Gregg C Levine wrote:
Hello from Gregg C Levine So I gathered from his earlier posts on this subject, and about that board specifically. But Adam, isn't ADLO board agnostic? By that I mean, that it does not need to know what motherboard it is being used on, unlike basic Linux BIOS. But, I am indeed watching this with interest.
Gregg C Levine hansolofalcon@worldnet.att.net
"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 ) (This company dedicates this E-Mail to Master Yoda )
-----Original Message----- From: linuxbios-admin@clustermatic.org [mailto:linuxbios- admin@clustermatic.org] On Behalf Of Adam Sulmicki Sent: Saturday, April 19, 2003 11:32 AM To: hcyun@etri.re.kr Cc: linuxbios@clustermatic.org Subject: Re: serial debug patch for ADLO
to clarify. He's been working on getting ADLO running on EPIA-M.
He's been pretty succesfull so far.
Using serial console he's got both lilo and linux to boot using
ADLO, so
that you can use them pretty much "out of box" as long as you don't
need
video. However from what I heard you can get video once boot is done
and
you run some video program (TinyX Xvesa here).
As far as video goes, on cold-reboot he's getting :
Then, screen is blinkering with various color, but I can't see
any
text.
As far as video goes, on warm-reboot (after booting with original PC
BIOS)
he's getting :
If I first booted from original bios and reset with linuxbios
adlo, I can see text messages of original bios remained.
ideas on how to attack the issue?
Overall I would say that anyone who want to try get ADLO to work
should
start with serial console and leave VIDEO to the end given
difficulty
debugging binary-only module.
Another good idea is to try warm-boot from PC BIOS into ADLO at
beginning
of development/work on ADLO. It leaves you with somewhat functioning video-bios (or fully-functioning as it was for me).
On Sun, 20 Apr 2003 hcyun@etri.re.kr wrote:
Hello,
I made a patch which make all bochs debug message can be seen from
serial
terminal. I think it might be useful if you want to apply ADLO to your own
target.
you can apply this patch againt util/ADLO/bochs/bios/rombios.c by # patch -p0 < rombios-serial.patch
Regards,
-- Adam Sulmicki http://www.eax.com The Supreme Headquarters of the 32 bit
registers
Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
hi,all. I have got the serial patch, and test it. but still have problem. my mainboard is k7sem ver3.0c here is some output message: --------------------------------------------------- Searching for server (DHCP)... ...Me: 192.168.0.40, Server: 192.168.0.38, Gateway 192.168.0.250 Loading 192.168.0.38:/var/tftpboot/kernel ...(ELF)... ............................................................................ ................done rombios.c,v 1.1 2002/11/25 02:07:53 rminnich Exp $ FATAL: Keyboard RESET error:31 FATAL: Keyboard RESET error:994 FATAL: Keyboard RESET error:995 FATAL: Keyboard RESET error:996 *** int 15h function AX=F401, BX=0005 not yet supported! Bochs BIOS, 1 cpu, $Revision: 1.1 $ $Date: 2002/11/25 02:07:53 $ [BOCHS BIOS VER:1.79] [COMPILE DATE:Apr 20 2003 TIME:15:00:19]
DEVICE:0 ata0 master: PCHS=16383/16/63 translation=lba LCHS=1024/255/63 ata0 master: IBM-DTLA-307030 ATA-5 Hard-Disk (29314 MBytes)
PCI BIOS function 0x01 --------------------------------------------------- and the screen can show some strange character, sometimes are part of original BIOS message. I think the bochs BIOS has run. any tips? thanks!
----- Original Message ----- From: "Adam Sulmicki" adam@cfar.umd.edu To: "Gregg C Levine" hansolofalcon@worldnet.att.net Cc: "Linuxbios" linuxbios@clustermatic.org Sent: Saturday, April 19, 2003 9:15 AM Subject: RE: serial debug patch for ADLO
mostly yes, this is why he was able to get serial boot in just several hours of work.
the major quirks were that he needed to code up the patch for serial output for bochs to see what's going on. then reconfigure lilo for serial output. Then to the same with linux.
another issue was that while VIA EPIA-M has 128mb ram, upper 32 mb are revered for video. thus E820 map had to be modifed so that it shows 96mb of ram instead of 128mb to linux.
i think that's about it.
On Sat, 19 Apr 2003, Gregg C Levine wrote:
Hello from Gregg C Levine So I gathered from his earlier posts on this subject, and about that board specifically. But Adam, isn't ADLO board agnostic? By that I mean, that it does not need to know what motherboard it is being used on, unlike basic Linux BIOS. But, I am indeed watching this with interest.
Gregg C Levine hansolofalcon@worldnet.att.net
"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 ) (This company dedicates this E-Mail to Master Yoda )
-----Original Message----- From: linuxbios-admin@clustermatic.org [mailto:linuxbios- admin@clustermatic.org] On Behalf Of Adam Sulmicki Sent: Saturday, April 19, 2003 11:32 AM To: hcyun@etri.re.kr Cc: linuxbios@clustermatic.org Subject: Re: serial debug patch for ADLO
to clarify. He's been working on getting ADLO running on EPIA-M.
He's been pretty succesfull so far.
Using serial console he's got both lilo and linux to boot using
ADLO, so
that you can use them pretty much "out of box" as long as you don't
need
video. However from what I heard you can get video once boot is done
and
you run some video program (TinyX Xvesa here).
As far as video goes, on cold-reboot he's getting :
Then, screen is blinkering with various color, but I can't see
any
text.
As far as video goes, on warm-reboot (after booting with original PC
BIOS)
he's getting :
If I first booted from original bios and reset with linuxbios
adlo, I can see text messages of original bios remained.
ideas on how to attack the issue?
Overall I would say that anyone who want to try get ADLO to work
should
start with serial console and leave VIDEO to the end given
difficulty
debugging binary-only module.
Another good idea is to try warm-boot from PC BIOS into ADLO at
beginning
of development/work on ADLO. It leaves you with somewhat functioning video-bios (or fully-functioning as it was for me).
On Sun, 20 Apr 2003 hcyun@etri.re.kr wrote:
Hello,
I made a patch which make all bochs debug message can be seen from
serial
terminal. I think it might be useful if you want to apply ADLO to your own
target.
you can apply this patch againt util/ADLO/bochs/bios/rombios.c by # patch -p0 < rombios-serial.patch
Regards,
-- Adam Sulmicki http://www.eax.com The Supreme Headquarters of the 32 bit
registers
Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
-- Adam Sulmicki http://www.eax.com The Supreme Headquarters of the 32 bit registers
Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
hmm that does not look right.
in general bochs bios should have tried to: - initalize vga module - try to boot from floppy (and fail) - try to load MBR from /dev/hda
I think it did init vga bios as it is probably the first thing it does (before the bochs banner which we can see below). Though u might want to double check on this.
I would expect to see the "floppy boot fail" (or similar) message instead of that "PCI BIOS function" which seems to be the last message here.
as far as vga bios goes, I would try doing warm boot from pc bios and see what happen.
as far as bochs bios itself goes, u will have to try enable some debugging information and see where exactly it stop. in particular I would try to enable interupt 13, since it might actually be reading MBR (that's the only place that I can think of hand that would probe for PCI bios).
On Sun, 20 Apr 2003, bendany wrote:
hi,all. I have got the serial patch, and test it. but still have problem. my mainboard is k7sem ver3.0c here is some output message:
Searching for server (DHCP)... ...Me: 192.168.0.40, Server: 192.168.0.38, Gateway 192.168.0.250 Loading 192.168.0.38:/var/tftpboot/kernel ...(ELF)... ............................................................................ ................done rombios.c,v 1.1 2002/11/25 02:07:53 rminnich Exp $ FATAL: Keyboard RESET error:31 FATAL: Keyboard RESET error:994 FATAL: Keyboard RESET error:995 FATAL: Keyboard RESET error:996 *** int 15h function AX=F401, BX=0005 not yet supported! Bochs BIOS, 1 cpu, $Revision: 1.1 $ $Date: 2002/11/25 02:07:53 $ [BOCHS BIOS VER:1.79] [COMPILE DATE:Apr 20 2003 TIME:15:00:19]
DEVICE:0 ata0 master: PCHS=16383/16/63 translation=lba LCHS=1024/255/63 ata0 master: IBM-DTLA-307030 ATA-5 Hard-Disk (29314 MBytes)
PCI BIOS function 0x01
and the screen can show some strange character, sometimes are part of original BIOS message. I think the bochs BIOS has run. any tips? thanks!
----- Original Message ----- From: "Adam Sulmicki" adam@cfar.umd.edu To: "Gregg C Levine" hansolofalcon@worldnet.att.net Cc: "Linuxbios" linuxbios@clustermatic.org Sent: Saturday, April 19, 2003 9:15 AM Subject: RE: serial debug patch for ADLO
mostly yes, this is why he was able to get serial boot in just several hours of work.
the major quirks were that he needed to code up the patch for serial output for bochs to see what's going on. then reconfigure lilo for serial output. Then to the same with linux.
another issue was that while VIA EPIA-M has 128mb ram, upper 32 mb are revered for video. thus E820 map had to be modifed so that it shows 96mb of ram instead of 128mb to linux.
i think that's about it.
On Sat, 19 Apr 2003, Gregg C Levine wrote:
Hello from Gregg C Levine So I gathered from his earlier posts on this subject, and about that board specifically. But Adam, isn't ADLO board agnostic? By that I mean, that it does not need to know what motherboard it is being used on, unlike basic Linux BIOS. But, I am indeed watching this with interest.
Gregg C Levine hansolofalcon@worldnet.att.net
"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 ) (This company dedicates this E-Mail to Master Yoda )
-----Original Message----- From: linuxbios-admin@clustermatic.org [mailto:linuxbios- admin@clustermatic.org] On Behalf Of Adam Sulmicki Sent: Saturday, April 19, 2003 11:32 AM To: hcyun@etri.re.kr Cc: linuxbios@clustermatic.org Subject: Re: serial debug patch for ADLO
to clarify. He's been working on getting ADLO running on EPIA-M.
He's been pretty succesfull so far.
Using serial console he's got both lilo and linux to boot using
ADLO, so
that you can use them pretty much "out of box" as long as you don't
need
video. However from what I heard you can get video once boot is done
and
you run some video program (TinyX Xvesa here).
As far as video goes, on cold-reboot he's getting :
Then, screen is blinkering with various color, but I can't see
any
text.
As far as video goes, on warm-reboot (after booting with original PC
BIOS)
he's getting :
If I first booted from original bios and reset with linuxbios
adlo, I can see text messages of original bios remained.
ideas on how to attack the issue?
Overall I would say that anyone who want to try get ADLO to work
should
start with serial console and leave VIDEO to the end given
difficulty
debugging binary-only module.
Another good idea is to try warm-boot from PC BIOS into ADLO at
beginning
of development/work on ADLO. It leaves you with somewhat functioning video-bios (or fully-functioning as it was for me).
On Sun, 20 Apr 2003 hcyun@etri.re.kr wrote:
Hello,
I made a patch which make all bochs debug message can be seen from
serial
terminal. I think it might be useful if you want to apply ADLO to your own
target.
you can apply this patch againt util/ADLO/bochs/bios/rombios.c by # patch -p0 < rombios-serial.patch
Regards,
-- Adam Sulmicki http://www.eax.com The Supreme Headquarters of the 32 bit
registers
Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
-- Adam Sulmicki http://www.eax.com The Supreme Headquarters of the 32 bit registers
Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Hi, It seems to have no responds in my serial port; I use etherboot to load the ADLO. Loading 192.168.1.1: payload ... (ELF)............................................................................... ................done No more information.
Some one gives me some suggestions?
Baud rate?
Best regards klos -----Original Message----- From: linuxbios-admin@clustermatic.org [mailto:linuxbios-admin@clustermatic.org] On Behalf Of hcyun@etri.re.kr Sent: 2003年4月19日 23:07 To: adam@cfar.umd.edu; linuxbios@clustermatic.org Subject: serial debug patch for ADLO
Hello, I made a patch which make all bochs debug message can be seen from serial terminal. I think it might be useful if you want to apply ADLO to your own target. you can apply this patch againt util/ADLO/bochs/bios/rombios.c by # patch -p0 < rombios-serial.patch Regards,