From leo.cacciari at gmail.com Tue May 8 12:56:47 2012 From: leo.cacciari at gmail.com (Leo Cacciari) Date: Tue, 08 May 2012 12:56:47 +0200 Subject: [Udpcast] udpcast and android Message-ID: <4FA8FBEF.8060404@gmail.com> 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 From alain at knaff.lu Tue May 8 13:12:54 2012 From: alain at knaff.lu (Alain Knaff) Date: Tue, 08 May 2012 13:12:54 +0200 Subject: [Udpcast] udpcast and android In-Reply-To: <4FA8FBEF.8060404@gmail.com> References: <4FA8FBEF.8060404@gmail.com> Message-ID: <4FA8FFB6.1050509@knaff.lu> On 08/05/12 12:56, Leo Cacciari wrote: > 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 > Source can be downloaded from http://www.udpcast.linux.lu/download/udpcast-20120424.tar.gz When a new version comes, the link will be updated on http://www.udpcast.linux.lu/downloads.html Regards, Alain From leo.cacciari at gmail.com Tue May 8 13:26:51 2012 From: leo.cacciari at gmail.com (Leo Cacciari) Date: Tue, 08 May 2012 13:26:51 +0200 Subject: [Udpcast] udpcast and android In-Reply-To: <4FA8FFB6.1050509@knaff.lu> References: <4FA8FBEF.8060404@gmail.com> <4FA8FFB6.1050509@knaff.lu> Message-ID: <4FA902FB.5040500@gmail.com> Il 05/08/2012 01:12 PM, Alain Knaff ha scritto: > On 08/05/12 12:56, Leo Cacciari wrote: >> Hi, >> 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 >> > > Source can be downloaded from > http://www.udpcast.linux.lu/download/udpcast-20120424.tar.gz > > When a new version comes, the link will be updated on > http://www.udpcast.linux.lu/downloads.html > Hi, I already got this file and started working on it. It was how I found that the config.sub script (one of those installed by autotools) is very old (2006) and does not understand 'android' as system name. Thus I changed it, using a more recent version. I did this 'by hand', but this should be done by running the opportune autoconf command. This however, needs some files (such as configure.ac) that are not included in the distribution created by make dist (which is the file you refer to). What I was asking if it was possible to get a access (read-only obviously) to the project git/svn/cvs/whatever source repository. Thanks Leo -- Leo Cacciari Aliae nationes servitutem pati possunt populi romani est propria libertas From alain at knaff.lu Tue May 8 13:43:50 2012 From: alain at knaff.lu (Alain Knaff) Date: Tue, 08 May 2012 13:43:50 +0200 Subject: [Udpcast] udpcast and android In-Reply-To: <4FA902FB.5040500@gmail.com> References: <4FA8FBEF.8060404@gmail.com> <4FA8FFB6.1050509@knaff.lu> <4FA902FB.5040500@gmail.com> Message-ID: <4FA906F6.7030909@knaff.lu> On 08/05/12 13:26, Leo Cacciari wrote: > Il 05/08/2012 01:12 PM, Alain Knaff ha scritto: >> On 08/05/12 12:56, Leo Cacciari wrote: >>> Hi, >>> 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 >>> >> >> Source can be downloaded from >> http://www.udpcast.linux.lu/download/udpcast-20120424.tar.gz >> >> When a new version comes, the link will be updated on >> http://www.udpcast.linux.lu/downloads.html >> > Hi, > > I already got this file and started working on it. It was how I found > that the config.sub script (one of those installed by autotools) is very > old (2006) and does not understand 'android' as system name. Thus I > changed it, using a more recent version. I did this 'by hand', but this > should be done by running the opportune autoconf command. This however, > needs some files (such as configure.ac) that are not included in the > distribution created by make dist (which is the file you refer to). What > I was asking if it was possible to get a access (read-only obviously) > to the project git/svn/cvs/whatever source repository. > > Thanks > Leo > You can find config.sub and config.guess files from http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/config/config/ Yes, the string *checkout* is indeed part of the URL, and should be entered as such Regards, Alain From leo.cacciari at gmail.com Tue May 8 15:48:36 2012 From: leo.cacciari at gmail.com (Leo Cacciari) Date: Tue, 08 May 2012 15:48:36 +0200 Subject: [Udpcast] udpcast and android In-Reply-To: <4FA906F6.7030909@knaff.lu> References: <4FA8FBEF.8060404@gmail.com> <4FA8FFB6.1050509@knaff.lu> <4FA902FB.5040500@gmail.com> <4FA906F6.7030909@knaff.lu> Message-ID: <4FA92434.5050402@gmail.com> Il 05/08/2012 01:43 PM, Alain Knaff ha scritto: > You can find config.sub and config.guess files from http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/config/config/ > > Yes, the string *checkout* is indeed part of the URL, and should be > entered as such > > Regards, > > Alain Sorry but it seems that I'm unable to explain myself. Update those file is easy, and I'd already done it. Fact is, the basic problems are in the configure script itself, because it does not check for Android system peculiarities such as: - the fact that in_addr_t is not defined in netinet/in.h but in arpa/inet.h - the fact that android kernels do not contain ethtool (which in any case wouldn't be useful, as android devices uses wireless not ethernet) - Android thread model (still searching if pthreads could be used...) Thus what I'd need (if it is possible at all) is the configure.ac and Makefile.am used by autoconf/automake to produce the respective .in files. Thanks again for your help Leo -- Leo Cacciari Aliae nationes servitutem pati possunt populi romani est propria libertas From dteed at artistic.ca Fri May 25 16:15:08 2012 From: dteed at artistic.ca (D G Teed) Date: Fri, 25 May 2012 11:15:08 -0300 (ADT) Subject: [Udpcast] booting cdrom and serial console Message-ID: 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 From alain at knaff.lu Fri May 25 16:46:43 2012 From: alain at knaff.lu (Alain Knaff) Date: Fri, 25 May 2012 16:46:43 +0200 Subject: [Udpcast] booting cdrom and serial console In-Reply-To: References: Message-ID: <4FBF9B53.3010908@knaff.lu> Hi, Weird... normally, it's supposed to be the same kernel for PXE and CDROM. Only floppy is different (for size reasons). Does it work if you boot using PXE off a CDROM master? Regards, Alain On 25/05/12 16:15, D G Teed wrote: > 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 > > _______________________________________________ > Udpcast mailing list > Udpcast at udpcast.linux.lu > https://udpcast.linux.lu/cgi-bin/mailman/listinfo/udpcast From dteed at artistic.ca Fri May 25 17:38:33 2012 From: dteed at artistic.ca (D G Teed) Date: Fri, 25 May 2012 12:38:33 -0300 (ADT) Subject: [Udpcast] booting cdrom and serial console In-Reply-To: <4FBF9B53.3010908@knaff.lu> References: <4FBF9B53.3010908@knaff.lu> Message-ID: Hi, I am using the recent pxelinux.0 from syslinux 4.05 I made pxelinux.cfg a directory rather than a file from the CDROM and then copied the old ISOLINUX.CFG as a file called default under pxelinux.cfg Using PXE boot with this slightly modified CDROM boot master, it shows: PXELINUX 4.05 2011-12-09 Copyright (C) 1994-2011 H. Peter Anvin et al !PXE entry point found (we hope) at 95A3:00D6 via plan A UNDI code segment at 95A3 len 4C0C UNDI data segment at 90D9 len 4CA0 Getting cached packet 01 02 03 My IP address seems to be C0A8B11C 192.168.177.28 ip=192.168.177.28:192.168.177.2:192.168.177.2:255.255.255.0 BOOTIF=01-00-09-3d-11-20-70 SYSUUID=68d3be2e-6d5d-11d8-ba9a-0060b0b36963 TFTP prefix: cdrom/ Trying to load: pxelinux.cfg/default ok Loading linux... And that is all we get. The part I've never changed is using the linux kernel and initrd from the udpcast site, as this has the udpcast enrvironment we need. These were taken from within the ISO at http://www.udpcast.linux.lu/20120424/udpcd.iso If this is a 3.1 kernel, it is much newer than the one we've used from Debian to run the system: 2.6-32. I've seen situations before where newer kernel on older hardware doesn't get anywhere until some magic incantation is found. But it is silent, like the serial console is part of the issue. Regards, --Donald Teed On Fri, 25 May 2012, Alain Knaff wrote: > Hi, > > Weird... normally, it's supposed to be the same kernel for PXE and > CDROM. Only floppy is different (for size reasons). > > Does it work if you boot using PXE off a CDROM master? > > Regards, > > Alain > > > On 25/05/12 16:15, D G Teed wrote: >> 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 >> >> _______________________________________________ >> Udpcast mailing list >> Udpcast at udpcast.linux.lu >> https://udpcast.linux.lu/cgi-bin/mailman/listinfo/udpcast > > _______________________________________________ > Udpcast mailing list > Udpcast at udpcast.linux.lu > https://udpcast.linux.lu/cgi-bin/mailman/listinfo/udpcast > From dteed at artistic.ca Fri May 25 21:16:26 2012 From: dteed at artistic.ca (D G Teed) Date: Fri, 25 May 2012 16:16:26 -0300 (ADT) Subject: [Udpcast] booting cdrom and serial console In-Reply-To: <4FBF9B53.3010908@knaff.lu> References: <4FBF9B53.3010908@knaff.lu> Message-ID: Hi, I'm wondering if I'm struggling with a 3.1 Linux kernel issue on my older hardware. Where can I get an older udpcast ISO or a pair of linux/initrd for the CDROM boot which uses the 2.6 kernel? --Donald Teed On Fri, 25 May 2012, Alain Knaff wrote: > Hi, > > Weird... normally, it's supposed to be the same kernel for PXE and > CDROM. Only floppy is different (for size reasons). > > Does it work if you boot using PXE off a CDROM master? > > Regards, > > Alain > > > On 25/05/12 16:15, D G Teed wrote: >> 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 >> >> _______________________________________________ >> Udpcast mailing list >> Udpcast at udpcast.linux.lu >> https://udpcast.linux.lu/cgi-bin/mailman/listinfo/udpcast > > _______________________________________________ > Udpcast mailing list > Udpcast at udpcast.linux.lu > https://udpcast.linux.lu/cgi-bin/mailman/listinfo/udpcast > From alain at knaff.lu Sat May 26 10:52:02 2012 From: alain at knaff.lu (Alain Knaff) Date: Sat, 26 May 2012 10:52:02 +0200 Subject: [Udpcast] booting cdrom and serial console In-Reply-To: References: <4FBF9B53.3010908@knaff.lu> Message-ID: <4FC099B2.5060603@knaff.lu> On 2012-05-25 21:16, D G Teed wrote: > Hi, > > I'm wondering if I'm struggling with a 3.1 Linux kernel issue > on my older hardware. Where can I get an older udpcast ISO > or a pair of linux/initrd for the CDROM boot which uses > the 2.6 kernel? > > --Donald Teed You can find many previous versions in http://www.udpcast.linux.lu/download/ The kernels are named kernel-udpcast* , and you need udpcast-mkimage* for building the initrd Ready-made kernels and initrds may be found in the following directories: http://www.udpcast.linux.lu/20120103 http://www.udpcast.linux.lu/20110710 http://www.udpcast.linux.lu/20110423 http://www.udpcast.linux.lu/20110416 http://www.udpcast.linux.lu/20100131 http://www.udpcast.linux.lu/20100130 ... Regards, Alain From erwanaliasr1 at gmail.com Tue May 29 17:20:24 2012 From: erwanaliasr1 at gmail.com (Erwan Velu) Date: Tue, 29 May 2012 17:20:24 +0200 Subject: [Udpcast] Blocked udpcast on recent kernel Message-ID: <4FC4E938.8080405@gmail.com> 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, From dteed at artistic.ca Tue May 29 17:42:53 2012 From: dteed at artistic.ca (D G Teed) Date: Tue, 29 May 2012 12:42:53 -0300 (ADT) Subject: [Udpcast] udpcast for PXE coming up in VT 2 while using serial console Message-ID: 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 From dteed at artistic.ca Tue May 29 21:13:17 2012 From: dteed at artistic.ca (D G Teed) Date: Tue, 29 May 2012 16:13:17 -0300 (ADT) Subject: [Udpcast] Use of tg3 network and LSI SCSI device not proceeding In-Reply-To: References: Message-ID: Another problem I'm having with udpcast on these Sun V20z's is recognition the ethernet and scsi drives. It should be using tg3 for the ethernet and sd for the scsi hard drive. With the default initrd, it seems to probe tg3, prompts for module options but won't proceed. I am always shown the prompt to load modules repeatedly. I'm using the Linux 3.1 kernel and initrd. I have also tried with a castomatic initrd including all modules and auto probe for disk type and ethernet. With this configuration, I get a prompt for loading the disk device module, but nothing I've manually loaded (using existing Redhat module names loaded on another system as a guide) will cause it to find /dev/sda. Clonezilla 1.2.12 can auto-detect the hard drive and ethernet, so the hardware must be OK. Here is what lspci reports for SCSI type and Ethernet type while an identical machine runs Redhat Linux: 02:04.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 08) 02:02.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet (rev 03) lsmod with 2.6.18 kernel from Redhat shows these modules related to above: mptspi 54737 2 mptscsih 69569 1 mptspi mptbase 111461 2 mptspi,mptscsih scsi_transport_spi 59841 1 mptspi sd_mod 56257 3 scsi_mod 188665 10 iscsi_tcp,ib_iser,libiscsi,scsi_transport_iscsi,ib_srp,sg,mptspi,mptscsih,scsi_transport_spi,sd_mod tg3 145093 0 --Donald Teed