On Mar 10, 2011, at 12:29 PM, Blake Hodder wrote: > Here is the out put of show on my net4521: > > ConSpeed = 19200 > ConLock = Enabled > ConMute = Disabled > BIOSentry = Enabled > PCIROMS = Enabled > PXEBoot = Enabled > FLASH = Primary > BootDelay = 1 > FastBoot = Enabled > BootPartition = Disabled > BootDrive = 80 81 F0 FF > ShowPCI = Enabled > Reset = Hard > > and I have confirmed that minicom is set to 19200: > > | A - Serial Device : /dev/ttyUSB0 | > | B - Lockfile Location : /var/lock | > | C - Callin Program > : | > | D - Callout Program : > | > | E - Bps/Par/Bits : 19200 8N1 | > | F - Hardware Flow Control : No | > | G - Software Flow Control : No
So much for that hope. I have a learning disability and will often see what I want to see (I can look at a ":" at then end of a line of Perl code all day and it looks like ";" to me until Perl tells me to check it). As a consequence I've learned to always double-check the obvious, so I wanted to double check the settings. Start that other thread I mentioned -- see if anyone has experience with this on a net4521 and if there are any differences in the serial port settings. Hal > > On 11-03-10 01:02 PM, Hal Vaughan wrote: >> On Mar 10, 2011, at 11:33 AM, Blake Hodder wrote: >> >>> I am in agreement here as I have just tried your tarball and still get >>> the same results. >> Then I'm baffled - I'd suggest starting a new thread and include the system >> (net4521) in the subject and ask about the serial port. >> >> But, just to be sure, post the output to "show" on the net4521 for >> verification and double-check the speed setting in minicom. (I may have >> mentioned I found some issues with the screen command, but those were gone >> in minicom.) >> >>> However; I am trying to use your image that you include on your wiki >>> page and it automatically is assuming "sdb" when my cf is "sdc". Is it >>> suppose to automatically assume where the device is? >> Do you mean the image tried to assume that once it was installed in your >> net4521 or the program did that? I had issues with the CF card I was using >> jumping from sdb to sdg, depending on which usb devices had a RAM drive or >> CF card in them on boot, so I made it to work with any location. I think it >> may have used sdb as a default, but it prompts for a device. I'll check on >> it, though. >> >> >> Hal >> >> >>> Blake >>> >>> On 11-03-09 11:33 PM, Hal Vaughan wrote: >>>> Okay, 2nd response to this, with additions. >>>> >>>> I've added a small section to the wiki page that includes this link: >>>> >>>> http://halblog.com/binaries/tftpboot.tgz >>>> >>>> That's my tftp boot setup with PXE Linux. I archived it and also >>>> triple-checked that this setup worked before (and after) archiving it in a >>>> .tgz file. >>>> >>>> Download that file and unpack it in a directory and temporarily point your >>>> tftp server to that directory (and verify the change is made, restarting >>>> any daemons that are effected, like xinetd). Then try it. >>>> >>>> If that doesn't give you a working setup to start with, I'm not at all >>>> sure what to do next, since that's my entire working tftp/pxe setup and >>>> there should be no issue with any other configuration issues outside of >>>> the files in the tarball. >>>> >>>> I am beginning to wonder, and would like to hear from someone who has been >>>> using a net4521 about if there's some hardware issue that might be causing >>>> this problem. >>>> >>>> >>>> >>>> Hal >>>> >>>> >>>> On Mar 9, 2011, at 11:44 AM, Blake Hodder wrote: >>>> >>>>> I appologize, I originally had it set up as the wiki guide described and >>>>> changed it a bit. Now I have just finished deleting everything I had and >>>>> followed the guide once again and still have the same issue. Once I hit >>>>> return to boot the install the kernel loads and the screen goes blank. >>>>> And this IS with my system setup according to the guide. I am using a >>>>> ubuntu distro using minicom. If there is other info needed please let me >>>>> know. >>>>> >>>>> Blake >>>>> >>>>> On 11-03-09 11:46 AM, Hal Vaughan wrote: >>>>>> On Mar 9, 2011, at 9:42 AM, Blake Hodder wrote: >>>>>> >>>>>>> Sorry, yes it is still going blank after loading initrd. My default >>>>>>> config file now looks like this: >>>>>>> >>>>>>> # D-I config version 1.0 >>>>>>> CONSOLE 0 >>>>>>> SERIAL 0 19200 0 >>>>>>> DISPLAY boot.txt >>>>>>> >>>>>>> DEFAULT squeeze_i386_install >>>>>>> >>>>>>> LABEL squeeze_i386_install >>>>>>> Kernel debian-installer/i386/linux >>>>>>> append initrd=debian-installer/i386/initrd.gz >>>>>>> console=ttyS0,19200,8n1 >>>>>>> IPAPPEND 1 >>>>>>> prompt 0 >>>>>>> timeout 0 >>>>>> I copied and pasted this file into my config file and it worked fine, so >>>>>> the problem isn't in the config file. >>>>>> >>>>>> Just to be sure, I used grep and searched that whole directory tree for >>>>>> my tftp boot setup and the only place 19200 is used is in >>>>>> /tftpserv/pxelinux.cfg, so it's not specified in other files anywhere, >>>>>> and, as Simon pointed out, it's the append line that makes it go blank >>>>>> after initrd loads, but that checked out. >>>>>> >>>>>> I don't want to cast blame, but I do need to make an important point, >>>>>> and this is after spending a few hours working on this and re-attaching >>>>>> my serial cable so I could check on a lot of this. You said, in your >>>>>> words, 'I did follow the wiki to a "t".' Yet I've spent time checking >>>>>> on issues that could be typos, interpretation problems in how the code >>>>>> parses the config files (for instance, the SYSLINUX wiki says keywords >>>>>> are case sensitive and is specific about this, so I did boot test with >>>>>> "Kernel" and "kernel" and played around with that) because you are >>>>>> working with your own configuration and setup. >>>>>> >>>>>> I'm sure, if you're using tftp booting for other systems, you have a >>>>>> setup that is working for all them, but at this point I would suggest >>>>>> setting up a separate configuration, just for this setup, then change >>>>>> the config files you're using to point to that setup, that's EXACTLY >>>>>> like he one in the wiki. That would include using the files specifically >>>>>> from those links, using the config files exactly as copied-and-pasted >>>>>> from there (or from the pages it links to), and matching it perfectly. >>>>>> >>>>>> It's quite possible the issue is something small, as a typo or misnamed >>>>>> directory, or two files with the same name so one ends up in the wrong >>>>>> directory. >>>>>> >>>>>> So, please, try a setup exactly as described and see what that does. >>>>>> >>>>>> Then, once it works, start adding stuff from your normal tftp boot >>>>>> server config and setup until it breaks. Then you'll find what's not >>>>>> working. >>>>>> >>>>>> >>>>>> >>>>>> Hal >>>>>> >>>>>> >>>>>>> Blake >>>>>>> >>>>>>> On 11-03-09 10:29 AM, Hal Vaughan wrote: >>>>>>>> On Mar 9, 2011, at 8:09 AM, Blake Hodder wrote: >>>>>>>> >>>>>>>>> Ok, So I have modified my default config to match that of the walk >>>>>>>>> through and the kernel loads to the point of ready and then still a >>>>>>>>> blank screen. This is with using 19200,8n1. I have made sure that all >>>>>>>>> the any where in the files are set to use a console speed of >>>>>>>>> 19200,8n1. >>>>>>>>> >>>>>>>>> If it is a console speed problem, what files would have the speed >>>>>>>>> setting in them that I would need to change? >>>>>>>> First, what do you mean by "loads to the point of ready"? Is it still >>>>>>>> going blank after loading initrd? If so, post the default config file >>>>>>>> you're using -- if you are still using include statements, include all >>>>>>>> the included files as well. >>>>>>>> >>>>>>>> I'll go back and double check on any other places the speed needs to >>>>>>>> be specified in case I left one out. >>>>>>>> >>>>>>>> >>>>>>>> Hal >>>>>>>> >>>>>>>>> Blake >>>>>>>>> >>>>>>>>> On 11-03-09 12:25 AM, Hal Vaughan wrote: >>>>>>>>>> On Mar 8, 2011, at 11:09 PM, Blake Hodder wrote: >>>>>>>>>> >>>>>>>>>>> Here are the contents of my default config: >>>>>>>>>>> >>>>>>>>>>> # D-I config version 1.0 >>>>>>>>>>> CONSOLE 0 >>>>>>>>>>> SERIAL 0 19200 0 >>>>>>>>>>> include debian-installer/i386/boot-screens/menu.cfg >>>>>>>>>>> default debian-installer/i386/boot-screens/vesamenu.c32 >>>>>>>>>>> prompt 0 >>>>>>>>>>> timeout 0 >>>>>>>>>>> >>>>>>>>>>> After I hit return on install I get the 2 lines: >>>>>>>>>>> >>>>>>>>>>> Loading debian/squeeze/i386/linux..... >>>>>>>>>>> Loading debian/squeeze/i386/initrd.gz.........ready. >>>>>>>>>>> >>>>>>>>>>> and then a blank screen. >>>>>>>>>> Okay, I don't know tftp that well or PXE Linux. Without looking >>>>>>>>>> through the file you include, I can't be sure what it does -- I'd >>>>>>>>>> suggest working with the default config file as close to the >>>>>>>>>> original posted to be sure. But, for now, post the menu.cfg file >>>>>>>>>> and let's see that. >>>>>>>>>> >>>>>>>>>> Also, one thing I did, and this means I'm no longer working with a >>>>>>>>>> stock install (and I forgot about this until just a moment ago when >>>>>>>>>> I was testing this), so I'm sorry I didn't mention this earlier. >>>>>>>>>> One "trick" I did to just make sure that<return> always gave >>>>>>>>>> the install I wanted is to remove or change the name of >>>>>>>>>> /tftpserv/boot.txt. (Actually, I stuffed it in my pxelinux.cfg >>>>>>>>>> directory since that's where the other config files are.) By >>>>>>>>>> removing it, you don't get a boot menu for PXE Linux and don't have >>>>>>>>>> problems with accidentally hitting arrow keys (even though I'm a >>>>>>>>>> competitive ballroom dancer, you'd be surprised at how clumsy I can >>>>>>>>>> be!). That'll force a default install. >>>>>>>>>> >>>>>>>>>> I'm not sure that your problem is related to boot.txt, but I thought >>>>>>>>>> I should mention it, just in case. >>>>>>>>>> >>>>>>>>>> Now, as to your blank screen -- I got that, many times, and was >>>>>>>>>> trying to work at 115200 instead of 19200. And what fixed it for me >>>>>>>>>> was finding out just how to get the parameters into the file >>>>>>>>>> "default." I suspect that's the issue here. Don't use the include >>>>>>>>>> directive for now. That's where you're varying from the >>>>>>>>>> instructions on the page I wrote up and from the two Debian >>>>>>>>>> reference pages I link to. And it's likely not coincidence that's >>>>>>>>>> where you did something different AND that's where console speed >>>>>>>>>> becomes an issue. >>>>>>>>>> >>>>>>>>>> Look at this version of "default": >>>>>>>>>> >>>>>>>>>> SERIAL 0 19200 >>>>>>>>>> CONSOLE 0 >>>>>>>>>> DISPLAY boot.txt >>>>>>>>>> >>>>>>>>>> DEFAULT squeeze_i386_install >>>>>>>>>> >>>>>>>>>> LABEL squeeze_i386_install >>>>>>>>>> kernel debian/squeeze/i386/linux >>>>>>>>>> append vga=normal console=ttyS0,19200,n8 >>>>>>>>>> initrd=debian/squeeze/i386/initrd.gz -- >>>>>>>>>> LABEL squeeze_i386_linux >>>>>>>>>> kernel debian/squeeze/i386/linux >>>>>>>>>> append vga=normal console=ttyS0,19200,n8 >>>>>>>>>> initrd=debian/squeeze/i386/initrd.gz -- >>>>>>>>>> LABEL squeeze_i386_expert >>>>>>>>>> kernel debian/squeeze/i386/linux >>>>>>>>>> append priority=low console=ttyS0,19200,n8 vga=normal >>>>>>>>>> initrd=debian/squeeze/i386/initrd.gz -- >>>>>>>>>> LABEL squeeze_i386_rescue >>>>>>>>>> kernel debian/squeeze/i386/linux >>>>>>>>>> append vga=normal console=ttyS0,19200,n8 >>>>>>>>>> initrd=debian/squeeze/i386/initrd.gz rescue/enable=true -- >>>>>>>>>> >>>>>>>>>> PROMPT 1 >>>>>>>>>> TIMEOUT 0 >>>>>>>>>> >>>>>>>>>> I know some of those lines wrapped (in Apple Mail, they don't), but >>>>>>>>>> use that format and don't include, for now, just cut and paste the >>>>>>>>>> text in to the file default. Also, be sure the parameters are on a >>>>>>>>>> separate line in each LABEL section. I've seen a friend forget that >>>>>>>>>> and append them (like the older GRUB, was it?) needed them done and >>>>>>>>>> it doesn't work that way. >>>>>>>>>> >>>>>>>>>> In my previous experience, I found that once initrd loaded and >>>>>>>>>> control is passed to it, unless the speed is specified correctly in >>>>>>>>>> the config file (either the default one or whichever one you're >>>>>>>>>> using), console communication stops. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Hal >>>>>>>>>> >>>>>>>>>>> Blake >>>>>>>>>>> On 11-03-08 11:52 PM, Hal Vaughan wrote: >>>>>>>>>>>> On Mar 8, 2011, at 10:10 PM, Blake Hodder wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hi there, >>>>>>>>>>>>> >>>>>>>>>>>>> My apologies, and when I get to the prompt instead of having a >>>>>>>>>>>>> "boot:" >>>>>>>>>>>>> prompt I have a text menu that I have to select install by using >>>>>>>>>>>>> my >>>>>>>>>>>>> arrows and enter. It is almost like is trying to do a graphical >>>>>>>>>>>>> install >>>>>>>>>>>>> but I am using the netboot files with the console modifications. >>>>>>>>>>>> Okay, I hooked up the serial cable and went through this again. I >>>>>>>>>>>> was trying to remember if there could be another menu later, or if >>>>>>>>>>>> there were more choices, but that I never saw them due to the 15 >>>>>>>>>>>> character width issue. When I booted to the NIC, I got this (it's >>>>>>>>>>>> edited to show in lines, instead of short 15 column lines): >>>>>>>>>>>> >>>>>>>>>>>> Intel UNDI, PXE-2.0 (build 082) >>>>>>>>>>>> Copyright (C) 1997,1998,1999 Intel Corporation >>>>>>>>>>>> VIA Rhine III Management Adapter v2.43 (2005/12/15) >>>>>>>>>>>> >>>>>>>>>>>> CLIENT MAC ADDR: 00 00 24 CD 92 34. >>>>>>>>>>>> DHCP.\\||//--\\||//--\\|| >>>>>>>>>>>> CLIENT IP: 172.16.7.205 MASK: 255.255.0.0 DHCP IP: 172.16.7.1 >>>>>>>>>>>> GATEWAY IP: 172.16.7.1 >>>>>>>>>>>> TFTP. >>>>>>>>>>>> TFTP.- >>>>>>>>>>>> PXELINUX 4.02 debian-20101014 Copyright (C) 1994-2010 H. Peter >>>>>>>>>>>> Anvin et al! >>>>>>>>>>>> PXE entry point found (we hope) at 9DEE:0106 via plan A >>>>>>>>>>>> UNDI code segment at 9DEE len 1966 >>>>>>>>>>>> UNDI data segment at 947D len 9710 >>>>>>>>>>>> Getting cached packet 01 02 03 >>>>>>>>>>>> My IP address seems to be AC1007CD 172.16.7.205 >>>>>>>>>>>> ip=172.16.7.205:172.16.7.12:172.16.7.1:255.255.0.0 >>>>>>>>>>>> BOOTIF=01-00-00-24-cd-92-34 >>>>>>>>>>>> TFTP prefix: >>>>>>>>>>>> Trying to load: pxelinux.cfg/01-00-00-24-cd-92-34 >>>>>>>>>>>> Trying to load: pxelinux.cfg/AC1007CD >>>>>>>>>>>> Trying to load: pxelinux.cfg/AC1007C >>>>>>>>>>>> Trying to load: pxelinux.cfg/AC1007 >>>>>>>>>>>> Trying to load: pxelinux.cfg/AC100 >>>>>>>>>>>> Trying to load: pxelinux.cfg/AC10 >>>>>>>>>>>> Trying to load: pxelinux.cfg/AC1 >>>>>>>>>>>> Trying to load: pxelinux.cfg/AC >>>>>>>>>>>> Trying to load: pxelinux.cfg/A >>>>>>>>>>>> Trying to load: pxelinux.cfg/default >>>>>>>>>>>> ok >>>>>>>>>>>> XELINUX 4.02 debian-20101014 Copyright (C) 1994-2010 H. Peter >>>>>>>>>>>> Anvin et al >>>>>>>>>>>> boot: >>>>>>>>>>>> Loading debian/squeeze/i386/linux..... >>>>>>>>>>>> Loading debian/squeeze/i386/initrd.gz.........ready. >>>>>>>>>>>> >>>>>>>>>>>> The "Trying to load:..." lines are the TFTP boot or PXE Linux >>>>>>>>>>>> searching for a config file, then settling on the default config. >>>>>>>>>>>> After that, the "boot:" is the only prompt I get. Once I >>>>>>>>>>>> hit<return>, I get the next two lines, followed by some LONG >>>>>>>>>>>> lines, then a chance to pick the language, which is the start of >>>>>>>>>>>> the installer. >>>>>>>>>>>> >>>>>>>>>>>> So what you're saying is that you don't get "boot:", you get a >>>>>>>>>>>> choice of which type of install to do instead? >>>>>>>>>>>> >>>>>>>>>>>> Could you post the contents of your /tftpserv/pxelinux.cfg/default >>>>>>>>>>>> file? >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Hal >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>> Blake >>>>>>>>>>>>> >>>>>>>>>>>>> On 11-03-08 10:06 PM, Hal Vaughan wrote: >>>>>>>>>>>>>> Okay -- remember, please, to respond to the list, since whatever >>>>>>>>>>>>>> goes wrong and whatever fixes it could help a lot of people. >>>>>>>>>>>>>> >>>>>>>>>>>>>> It also means I'm not the only one helping out, in case someone >>>>>>>>>>>>>> else finds something wrong that I miss. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Okay, then is the prompt where things go wrong the first prompt >>>>>>>>>>>>>> from PXE Linux, after it boots to Linux? The one where you get >>>>>>>>>>>>>> "boot:" and can just press<enter>? If so, when you get that >>>>>>>>>>>>>> prompt, what are you doing? >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Hal >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Mar 8, 2011, at 8:49 PM, Blake Hodder wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hi, >>>>>>>>>>>>>>> That is the wiki page that I did follow and I did set ConSpeed >>>>>>>>>>>>>>> to 19200 as well as my minicom console. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Blake >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On 11-03-08 09:22 PM, Hal Vaughan wrote: >>>>>>>>>>>>>>>> I don't know how it'll compare to installing on a Net5501, but >>>>>>>>>>>>>>>> I wrote that up in the Soekris wiki just a few weeks ago. >>>>>>>>>>>>>>>> Here's the page: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> http://wiki.soekris.info/Debian_Squeeze_On_Soekris >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> (I don't know if that's the page you're talking about or not.) >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I was careful to pay attention to the issue of baudrate, since >>>>>>>>>>>>>>>> it can really mess up your work. (I honestly feel if it had >>>>>>>>>>>>>>>> been better documented in previous pages on installing Debian, >>>>>>>>>>>>>>>> it would have saved me 5-10 hours of troubleshooting.) >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I'm not 100% clear, from what you're saying, if you mean you >>>>>>>>>>>>>>>> get to the "boot:" prompt and then are having trouble (which >>>>>>>>>>>>>>>> is where you could specify different options for booting), or >>>>>>>>>>>>>>>> if it's another point. However, it is important to remember >>>>>>>>>>>>>>>> you have to specify the bad rate in the >>>>>>>>>>>>>>>> /tftpserv/pxelinux.cfg/default file (where /tftpserv is your >>>>>>>>>>>>>>>> directory path to the tftp/pxe setup). You will also have to >>>>>>>>>>>>>>>> specify the baud rate at a few other points, as well. I >>>>>>>>>>>>>>>> mention that o the page I linked to above. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> If that's the page you're following, let us know and also >>>>>>>>>>>>>>>> please tell us exactly what the text for the last prompt you >>>>>>>>>>>>>>>> see before things go bad is. Also, is it at the section where >>>>>>>>>>>>>>>> (for some reason), the output is limited to only 15 characters >>>>>>>>>>>>>>>> wide? (That could also be a Net5501 thing, so I don't know if >>>>>>>>>>>>>>>> you'll see that on other systems.) >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Also, at the bottom of that wiki page, there's another page to >>>>>>>>>>>>>>>> my blog website, where I have an image I created on a Net5501. >>>>>>>>>>>>>>>> Off the top of my head, I don't know how similar the hardware >>>>>>>>>>>>>>>> is, but I have info on how you can copy that image and install >>>>>>>>>>>>>>>> it on another Net5501. It's possible that image may work on a >>>>>>>>>>>>>>>> Net4521, but I don't know. If so, it might save you some >>>>>>>>>>>>>>>> trouble and let you start with a basic Debian Squeeze image >>>>>>>>>>>>>>>> you can then modify to your heart's content. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Scott Newell pointed out the difference between baud and bps. >>>>>>>>>>>>>>>> Just for clarity, is 19200 what you set ConSpeed to? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Hal >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Mar 8, 2011, at 2:04 PM, Blake Hodder wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Hi, >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> I have a Soekris net4521 and I am trying to install Debian >>>>>>>>>>>>>>>>> Squeeze on it via tftp boot and serial console. However; I >>>>>>>>>>>>>>>>> get to where I can select install from a menu list and then >>>>>>>>>>>>>>>>> it sits at a blank screen. I am using the buadrate of 19200 >>>>>>>>>>>>>>>>> 8n1 no flow control. Does anyone know how to successfully >>>>>>>>>>>>>>>>> install squeeze. I have tried using the wiki guide. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Thanks in advanced, >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Blake >>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>> <RBI-Email-Signatures-BH.gif> >>>> _______________________________________________ >>>> Soekris-tech mailing list >>>> [email protected] >>>> http://lists.soekris.com/mailman/listinfo/soekris-tech >>> >>> -- >>> _______________________________________________ >>> Soekris-tech mailing list >>> [email protected] >>> http://lists.soekris.com/mailman/listinfo/soekris-tech >>> >> _______________________________________________ >> Soekris-tech mailing list >> [email protected] >> http://lists.soekris.com/mailman/listinfo/soekris-tech > > > -- > _______________________________________________ > Soekris-tech mailing list > [email protected] > http://lists.soekris.com/mailman/listinfo/soekris-tech > _______________________________________________ Soekris-tech mailing list [email protected] http://lists.soekris.com/mailman/listinfo/soekris-tech
