I've been able to see more information while using
actual console, since I'm unable to funnel to virtual
terminals over serial (or at least, I don't know how this
can be done).
While using the recent linux and initrd with Linux 3.1 kernel,
I have this pxelinux.cfg/default :
serial 0
console 0
default linux
label linux
kernel linux
append load_ramdisk=1 initrd=initrd root=01:00 lang=US kbdmap=US console=ttyS0,9600n8
ipappend 3
I see the truncated session in the serial console,:
CLIENT MAC ADDR: 00 09 3D 10 C5 19 GUID: 00000000 0000 0000 0000 000000000000
CLIENT IP: 192.168.177.26 MASK: 255.255.255.0 DHCP IP: 192.168.177.2
GATEWAY IP: 192.168.177.2
PXELINUX 4.02 debian-20101014 C
If I check the actual console, I can use Ctrl+Alt+F2 and I
see the blue screen and a udpcast prompt for my network card.
What causes the udpcast session to fly to the VT2, or what can I try
to force it to use the VT1 display? Or is it a problem that
the serial setting isn't following a switch to the new VT console?
This wasn't a problem for the Debian installer over PXE so I think the
set up is capable of doing this.
--Donald Teed
Dear All,
I'm using udpcast for 1.5 year now and since I upgraded to a 3.2.x
kernel, I'm experiencing some weird issue on udpcast.
The setup didn't changed at all since the time it worked except the
kernel (same hw devices / network /..).
The behavior we saw is that after a while (~ 30Gb of data) some clients
looks like frozen.
We started to investigate on it and the can see the following:
- the multicast stream is still reaching the host (proc/net/igmp is ok,
tcpdump -pni show the traffic too)
- the udp-receiver seems block on a read() call
- udp-cast doesn't exist due to wrong data even if the timeout is
specified (the timeout worked by the past)
We are using 2011.07.10 version of updcast for a while now. It didn't
got changed since the time it worked.
Does anyone experienced that or does some have some ideas to understand
what's happening ?
Thanks,
Hi,
I've been away from udpcast for awhile. Now
I am using it for imaging on a cluster.
I'm having difficulty booting from CDROM
with working serial console. I can boot the system
with PXE and run the Debian installer over
serial console OK, and Debian booted from
hard drive will display and control OK over
serial.
With ISOLINUX, it shows a little progress over
the serial console, and then it is silent.
I started with the udpcd.iso (as of May 24, 2012 on the
udpcast website), mounted it, copied to an 'extracted'
directory and added my options for serial console.
Here is my ISOLIUX.CFG :
serial 0
default linux
label linux
kernel linux
append root=/dev/ram0 initrd=initrd console=ttyS0,9600
I run genisoimage within the "extracted" directory copy:
genisoimage -o ../serial-udpcd.iso -b ISOLINUX.BIN -c boot.catalog -no-emul-boot -boot-load-size 4 -boot-info-table .
It will get as far this:
ISOLINUX 3.63 Debian-2008-07-15 Copyright (C) 1994-2008 H. Peter Anvin
boot:
Loading linux................
Loading initrd..................................................................
...................................................ready.
I've tried current syslinux files for isolinux.bin and pxelinux.0
Same result:
ISOLINUX 4.05 2011-12-09 ETCD Copyright (C) 1994-2011 H. Peter Anvin et al
Loading linux...
Loading initrd..........ready.
I've tried CONSOLE 0 within ISOLINUX.CFG and it causes the ISOLINUX
banner to appear and that is all.
Here is the pxelinux.cfg/default which works OK with the Debian installer...
SERIAL 0 9600
CONSOLE 0
SAY debug
include debian-installer/amd64/boot-screens/menu.cfg
default debian-installer/amd64/boot-screens/vesamenu.c32
prompt 1
timeout 300
Then within one of the boot-screen menu files txt.cfg:
default install
label install
menu label ^Install
menu default
kernel debian-installer/amd64/linux
append vga=788 initrd=debian-installer/amd64/initrd.gz -- quiet noapic acpi=off console=ttyS0,9600 earlyprint=serial,ttyS0,9600
The kernel from udpcast doesn't like all of these options, so they were tried and
removed.
The systems are Sun V20z and they are connected with a serial hub.
I thought maybe I could save on some CDs by asking for some help. :-)
My thinking is to use CDROM for uploading master disk image,
and PXE for automated imaging. It should prevent mistakes.
--Donald Teed
Hi,
I'm working on a project requiring massive transfer of data between an
host and several android devices and I was thinking to use udpcast. This
requires compiling udpcast itself for Android.
Does anyone know of a porting to android? It would be nice if someone
had already done the job, thus sparing me to reinvent wheel... :)
On the other hand, if nobody already did, is silly to waste the effort
I'll have to do be keeping that for me. I already have the company
accord for sharing any work done on the porting with the community, but
for this access to the distribution is not enough: I need to access the
source itself (including clconfigure.ac and Makefile.am) as it is stored
in the source repository, at least to fetch it. Is this possible? And if
yes, how to obtain it?
Thanks
Leo
--
Leo Cacciari
Aliae nationes servitutem pati possunt populi romani est propria libertas
