anyone have a 16-bit x86 early_printk?
I'm trying to get a box to boot and it appears to drop dead before start_kernel(). Would anyone happen to have an early_printk() analogue for 16-bit x86 code?
Thanks,
Bill
Quoted 3 lines · William Lee Irwin III
I'm trying to get a box to boot and it appears to drop dead before
start_kernel(). Would anyone happen to have anearly_printk()analogue for 16-bit x86 code?
It could be failing in the decompression routine if it was compiled for the wrong cpu (ie. using cmov instructions).
--
Brian Gerst
Quoted 3 lines · William Lee Irwin III
Quoted 3 lines
I'm trying to get a box to boot and it appears to drop dead before
start_kernel(). Would anyone happen to have anearly_printk()analogue for 16-bit x86 code?
Quoted 2 lines · Brian Gerst
It could be failing in the decompression routine if it was compiled for the wrong cpu (ie. using cmov instructions).
The cpu has cmov. It's Pentium-III. It suceeds in one configuration of the machine and fails in another.
Bill
Quoted 3 lines
I'm trying to get a box to boot and it appears to drop dead before
start_kernel(). Would anyone happen to have anearly_printk()analogue for 16-bit x86 code?
See arch/i386/boot/compressed/misc.c - there's a puts() routine in there that should work for most things OK.
M.
Quoted 7 lines · William Lee Irwin III
Quoted 4 lines · William Lee Irwin III
Quoted 3 lines
I'm trying to get a box to boot and it appears to drop dead before
start_kernel(). Would anyone happen to have anearly_printk()analogue for 16-bit x86 code?
Quoted 6 lines
Quoted 1 line · Brian Gerst
It could be failing in the decompression routine if it was compiled for the wrong cpu (ie. using cmov instructions).
The cpu has cmov. It's Pentium-III. It suceeds in one configuration of the machine and fails in another.
Does this mean succeeds with 32GB, but not with 48GB?
Signature · 2 lines
Dave Hansen [email protected]
Quoted 3 lines · At some point in the past, I wrote:
Quoted 3 lines
I'm trying to get a box to boot and it appears to drop dead before
start_kernel(). Would anyone happen to have anearly_printk()analogue for 16-bit x86 code?
Quoted 2 lines · Martin J. Bligh
See
arch/i386/boot/compressed/misc.c- there's aputs()routine in there that should work for most things OK.
Hmm, I wonder why that was never mentioned by some others...
At any rate, it suffices for me.
Bill
Quoted 3 lines · William Lee Irwin III
I'm trying to get a box to boot and it appears to drop dead before
start_kernel(). Would anyone happen to have anearly_printk()analogue for 16-bit x86 code?
Linux 8086 has a complete mini-linux for it, let alone printk. A bcc compileable printk is included
Quoted 3 lines · William Lee Irwin III
Quoted 3 lines
I'm trying to get a box to boot and it appears to drop dead before
start_kernel(). Would anyone happen to have anearly_printk()analogue for 16-bit x86 code?
Quoted 2 lines · Alan
Linux 8086 has a complete mini-linux for it, let alone printk. A bcc compileable printk is included
It actually turned out to be a bug in the early_printk I was using that killed it on the first call to it, but the availability of this will certainly broaden the scope of what I can feasibly debug.
Thanks,
Bill
Quoted 3 lines · William Lee Irwin III
It actually turned out to be a bug in the
early_printkI was using that killed it on the first call to it, but the availability of this will certainly broaden the scope of what I can feasibly debug.
Are you using the one that calls console_setup(), then initializes the serial driver directly? I was seeing some strange behavior with that yesterday, but I assumed that it was my patch crashing in early boot. What was the bug?
Signature · 2 lines
Dave Hansen [email protected]
Quoted 3 lines · William Lee Irwin III
Quoted 3 lines
It actually turned out to be a bug in the
early_printkI was using that killed it on the first call to it, but the availability of this will certainly broaden the scope of what I can feasibly debug.
Quoted 4 lines · Dave Hansen
Are you using the one that calls
console_setup(), then initializes the serial driver directly? I was seeing some strange behavior with that yesterday, but I assumed that it was my patch crashing in early boot. What was the bug?
I don't think that was the one, no. I didn't bother debugging it and just hand-coded the bitbanging directly in asm.
-- wli