I have a dumb terminal connecting with serial port 1.Now I can directly
login in through
the dumb terminal.But before login ,I can not see nothing in the terminal
and do not know what has happened in the system before login.The start
information only display in the color CRT.In real use,I can’t use CRT ,only
use dumb terminal.So What I want to know is that how to make the dumb
terminal display all start info before login in Qnx6.1.0 ?
“zhz_zhang” <zhz_zhang26@sina.com> wrote in message
news:appvnj$kvl$1@inn.qnx.com…
I have a dumb terminal connecting with serial port 1.Now I can directly
login in through
the dumb terminal.But before login ,I can not see nothing in the terminal
and do not know what has happened in the system before login.The start
information only display in the color CRT.In real use,I can’t use CRT
,only
use dumb terminal.So What I want to know is that how to make the dumb
terminal display all start info before login in Qnx6.1.0 ?
Did you have a look at:
http://www.qnx.com/developer/docs/momentics_nc_docs/neutrino/utilities/s/sta
rtup-bios.html
I believe you want to creat the debug channel through serial port instead of
console by default.
Eduard.
zhz_zhang <zhz_zhang26@sina.com> wrote:
I have a dumb terminal connecting with serial port 1.Now I can directly
login in through
the dumb terminal.But before login ,I can not see nothing in the terminal
and do not know what has happened in the system before login.The start
information only display in the color CRT.In real use,I can’t use CRT ,only
use dumb terminal.So What I want to know is that how to make the dumb
terminal display all start info before login in Qnx6.1.0 ?
With the standard QNX6 boot image, you probably can’t do it.
When building custom images, look at the command line options to
startup-bios, in partticular the startup-bios -D option for specifying
where debug output goes.
Also, in your +script section, rather than running devc-con and doing
a reopen /dev/con1, instead run devc-ser8250 and reopen /dev/ser1
-David
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.
“David Gibbs” <dagibbs@qnx.com> wrote in message
news:aprp6o$vf$1@nntp.qnx.com…
When building custom images, look at the command line options to
startup-bios, in partticular the startup-bios -D option for specifying
where debug output goes.Also, in your +script section, rather than running devc-con and doing
a reopen /dev/con1, instead run devc-ser8250 and reopen /dev/ser1I change the /boot/qnxbasedma.build file a little to add some info about
serial port.first it display right info,but it still has some garbage before
login.
After I login,there are two “devc-ser8250” in system.I think maybe the two
“devc-ser8250”
create the garbage.
Another phenomena:Some display message in /etc/rc.d/rc.local display info in
CRT(concole),
it should be display in /dev/ser1 ,why not?
How to avoid these happen.
*****************the serial display info is **************************
System page at phys:00014000 user:f511000 kern:ff512000
Starting next program at vff8330dc
Detected EIDE .Scanning for devices.
set 2 serial port
*** after that there is some garbage as those **
dfsdd dfsgg dffdfdfdfsfdf fd0fdf *
dfdafjklkl;jf ldfdasdff; login:
*****************the custom.build 's content is ************************
The build file for qnx RTP booting on a PC
[virtual=x86,bios +compress] boot = {
I changed here
Reserve 64k of video memory to handle multiple video cards
and display start info in ser1
startup-bios -s64k -D 8250.3f8^0.9600.1843200.16 -v
PATH is the safe path for executables (confstr(_CS_PATH…))
LD_LIBRARY_PATH is the safe path for libraries (confstr(_CS_LIBPATH))
i.e. This is the path searched for libs in setuid/setgid executables.
PATH=/proc/boot:/bin:/usr/bin
LD_LIBRARY_PATH=/proc/boot:/lib:/usr/lib:/lib/dll procnto
}
[+script] startup-script = {
To save memory make everyone use the libc in the boot image!
For speed (less symbolic lookups) we point to libc.so.2 instead of
libc.so
procmgr_symlink …/…/proc/boot/libc.so.2 /usr/lib/ldqnx.so.2
\
I changed here two
add serial port driver start info
display_msg “set 2 serial port”
devc-ser8250 -e -u1 3f8,4 -u2 2f8,3 &
waitfor /dev/ser1
reopen /dev/ser1
\
Default user programs to priorty 10, other scheduler (pri=10o)
Tell “diskboot” this is a hard disk boot (-b1)
Tell “diskboot” to use DMA on IDE drives (-D1)
Start 4 text consoles buy passing “-n4” to “devc-con” (-o)
By adding “-e” linux ext2 filesystem will be mounted as well.
[pri=10o] PATH=/proc/boot diskboot -b1 -D1 -odevc-con,-n4
}
Include the current “libc.so”. It will be created as a real file using
it’s internal “SONAME”, with “libc.so” being a symlink to it. The symlink
will point to the last “libc.so.*” so if an earlier libc is needed
(e.g. libc.so.1) add it before the this line.
libc.so
Include all tie files for the default filesystems
libcam.so
io-blk.so
cam-disk.so
fs-qnx4.so
fs-dos.so
fs-ext2.so
cam-cdrom.so
fs-cd.so
These programs only need to be run once from the boot image.
“data=uip” will waste less memory as the ram from the boot
image will be used directly without making a copy of the data
(i.e. as the default “data=cpy” does). When they have been
run once, they will be unlinked from /proc/boot.
[data=uip]
seedres
pci-bios
devb-eide
devb-amd
devb-aha2
devb-aha4
devb-aha7
devb-aha8
devb-ncr8
diskboot
slogger
fesh
devc-ser8250
These files will be unlinked after the system has started
to release the memory back to the system. They are only
needed during boot. If needed later on, they will be loaded
from the boot device.
unlink_list={
/proc/boot/devb-*
}