Talk:Custom bootloader: Difference between revisions
Jump to navigation
Jump to search
PeasthopeOld (talk | contribs) m (→An olpc.fth for DebXO: Switched to another server for the display image and deleted the spurious text from the olpc.fth.) |
PeasthopeOld (talk | contribs) m (Corrections and clarifications.) |
||
Line 1: | Line 1: | ||
== An olpc.fth for DebXO == |
== An olpc.fth for DebXO == |
||
I am interested to run DebXO on a 1.5 machine. According to [[DebXO]] the olpc.fth in the release works for the XO-1. On the 1.5 the text of the boot console does not fit the [http:// |
I am interested to run DebXO on a 1.5 machine. According to [[DebXO]] the olpc.fth in the release works for the XO-1. On the 1.5 the text of the boot console does not fit the [http://members.shaw.ca/peasthope/DebXObootConsole.jpg display] properly. Adjustments to the boot parameters in olpc.fth from the release follow. The viafb driver is specified. Given that the 1 and 1.5 models both have 1200x900 screens, misfitting of the console puzzles. If anyone can explain, that would be helpful. A suggestion to fix olpc.fth for the 1.5 would be even better. When a suitable olpc.fth is found, I can try to add the details such that the XO model is detected automatically. Regards, ... Peter E., [[User:Peasthope|Peasthope]] 17:03, 22 February 2013 (UTC) |
||
\ OLPC boot script |
|||
<br> |
|||
game-key-mask button-check and if " int:\boot\olpc.fth" $boot then |
|||
<br> |
|||
\ fetch the /chosen/bootpath property |
|||
" /chosen" find-package if ( phandle ) |
|||
" bootpath" rot get-package-property 0= if ( propval$ ) |
|||
get-encoded-string ( bootpath$ ) |
|||
[char] \ left-parse-string 2nip ( dn$ ) |
|||
<br> |
|||
\ store the first part of bootpath (up to the '\') in $DN |
|||
dn-buf place ( ) |
|||
then |
|||
then |
|||
<br> |
|||
\ " ro root=LABEL=DebXO video=viafb" to boot-file |
\ " ro root=LABEL=DebXO video=viafb" to boot-file |
||
" ro root=LABEL=DebXO video=viafb:1200x900 fbcon=font:SUN12x22" to boot-file |
" ro root=LABEL=DebXO video=viafb:1200x900 fbcon=font:SUN12x22" to boot-file |
||
game-key-mask h# 80 and if |
|||
\ boot from backup kernel |
|||
" ${DN}\vmlinuz.bak" expand$ to boot-device |
|||
" ${DN}\initrd.img.bak" expand$ to ramdisk |
|||
else |
|||
\ boot from regular kernel |
|||
" ${DN}\vmlinuz" expand$ to boot-device |
|||
" ${DN}\initrd.img" expand$ to ramdisk |
|||
then |
|||
dcon-unfreeze |
|||
boot |
|||
:You appear to have combined Xorg configuration text with your olpc.fth, and this is not valid, but is harmless. Nothing after ''boot'' is processed. Your photograph seems incomplete. The differences in XO-1 and XO-1.5 are expected, since different frame buffer drivers are used by the kernel. I suggest using the DebXO talk page for this, as it isn't really a custom bootloader problem. --[[User:Quozl|Quozl]] 22:59, 22 February 2013 (UTC) |
:You appear to have combined Xorg configuration text with your olpc.fth, and this is not valid, but is harmless. Nothing after ''boot'' is processed. Your photograph seems incomplete. The differences in XO-1 and XO-1.5 are expected, since different frame buffer drivers are used by the kernel. I suggest using the DebXO talk page for this, as it isn't really a custom bootloader problem. --[[User:Quozl|Quozl]] 22:59, 22 February 2013 (UTC) |
||
:: Xorg configuration text is gone. The best explanation I can offer is being too dull when posting and accidentally clicking in the xorg.conf window. The photo of the [http://carnot.yi.org/DebXObootConsole.jpg display] from another server appears correctly. |
|||
::Using the DebXO talk page implies, to me at least, that the fix should be in the DebXO kernel. For an ordinary PC, the boot process is customized by Grub. Here the equivalent is OFW. You suggest distinct kernels for 1 and for 1.5 or a kernel which specializes the boot console according to the hardware? Thanks, [[User:Peasthope|Peasthope]] 06:34, 27 February 2013 (UTC) |
Revision as of 06:34, 27 February 2013
An olpc.fth for DebXO
I am interested to run DebXO on a 1.5 machine. According to DebXO the olpc.fth in the release works for the XO-1. On the 1.5 the text of the boot console does not fit the display properly. Adjustments to the boot parameters in olpc.fth from the release follow. The viafb driver is specified. Given that the 1 and 1.5 models both have 1200x900 screens, misfitting of the console puzzles. If anyone can explain, that would be helpful. A suggestion to fix olpc.fth for the 1.5 would be even better. When a suitable olpc.fth is found, I can try to add the details such that the XO model is detected automatically. Regards, ... Peter E., Peasthope 17:03, 22 February 2013 (UTC)
\ " ro root=LABEL=DebXO video=viafb" to boot-file " ro root=LABEL=DebXO video=viafb:1200x900 fbcon=font:SUN12x22" to boot-file
- You appear to have combined Xorg configuration text with your olpc.fth, and this is not valid, but is harmless. Nothing after boot is processed. Your photograph seems incomplete. The differences in XO-1 and XO-1.5 are expected, since different frame buffer drivers are used by the kernel. I suggest using the DebXO talk page for this, as it isn't really a custom bootloader problem. --Quozl 22:59, 22 February 2013 (UTC)
- Xorg configuration text is gone. The best explanation I can offer is being too dull when posting and accidentally clicking in the xorg.conf window. The photo of the display from another server appears correctly.
- Using the DebXO talk page implies, to me at least, that the fix should be in the DebXO kernel. For an ordinary PC, the boot process is customized by Grub. Here the equivalent is OFW. You suggest distinct kernels for 1 and for 1.5 or a kernel which specializes the boot console according to the hardware? Thanks, Peasthope 06:34, 27 February 2013 (UTC)