Dear All, I have found a very easy solution of installing Astlinux on a net4826, the best way is to download the live cd from http://dl.metrix.net/support/livecd/, it has a wonderfull PXE boot environment for installing Astlinux over the network. Just plug and play.
Thanks for all of your support. Ahmad. On 7/20/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Send Soekris-tech mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.soekris.com/mailman/listinfo/soekris-tech > or, via email, send a message with subject or body 'help' to > [EMAIL PROTECTED] > > You can reach the person managing the list at > [EMAIL PROTECTED] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Soekris-tech digest..." > > > Today's Topics: > > 1. Re: Comm Port Help! (william estrada) > 2. Re: Comm Port Help! (RB) > 3. Re: Comm Port Help! (Mark) > 4. Re: Comm Port Help! (Mark) > 5. Re: Comm Port Help! (The Fungi) > 6. Re: ethernet problems w/ Fedora 7 on net4826 (Benjamin S. Scarlet) > 7. net4501 reboot/crash (Bastien Durel) > 8. how to install astlinux on net4826 using PXE (Eitesam Ahmad) > 9. Re: how to install astlinux on net4826 using PXE (Nils Vogels) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 19 Jul 2007 08:53:12 -0700 > From: william estrada <[EMAIL PROTECTED]> > Subject: Re: [Soekris] Comm Port Help! > To: "Mark" <[EMAIL PROTECTED]> > Cc: [email protected] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > > Mark, > > Not so crazy. > > Possible problem: > 1) Your BIOS may not support USB Serial ports. > 2) If I remember correctly, Grub does not support USB keyboards? > 3) Your OS should support this as a tty? > > Try it. > > -- > William Estrada > [EMAIL PROTECTED] > Mt-Umunhum-Wireless.net ( 64.124.13.3 ) > > > Message: 3 > > Date: Wed, 18 Jul 2007 09:28:11 -0400 > > From: "Mark" <[EMAIL PROTECTED]> > > Subject: Re: [Soekris] Comm Port Help! > > To: "'RB'" <[EMAIL PROTECTED]>, "'Bob Camp'" <[EMAIL PROTECTED]> > > Cc: [email protected] > > Message-ID: <[EMAIL PROTECTED]> > > Content-Type: text/plain; charset="UTF-8" > > > > We had a crazy idea--is it possible to redirect the console/kernel messages > > to the USB port as opposed to the Serial port? > > > > Thanks, > > > > Mark > > > > > ------------------------------ > > Message: 2 > Date: Thu, 19 Jul 2007 11:07:42 -0500 > From: RB <[EMAIL PROTECTED]> > Subject: Re: [Soekris] Comm Port Help! > To: [email protected] > Message-ID: > <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=UTF-8; format=flowed > > On 7/19/07, william estrada <[EMAIL PROTECTED]> wrote: > > 2) If I remember correctly, Grub does not support USB keyboards? > Incorrect - I've used USB almost exclusively for quite some time. > > > 3) Your OS should support this as a tty? > It does, through the usb-serial and related drivers. > > > ------------------------------ > > Message: 3 > Date: Thu, 19 Jul 2007 13:27:40 -0400 > From: "Mark" <[EMAIL PROTECTED]> > Subject: Re: [Soekris] Comm Port Help! > To: "'Soren Kristensen'" <[EMAIL PROTECTED]>, "'RB'" > <[EMAIL PROTECTED]> > Cc: [email protected] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="us-ascii" > > Thanks, Soren. > > --Mark > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Soren > Kristensen > Sent: Wednesday, July 18, 2007 4:38 PM > To: RB > Cc: [email protected] > Subject: Re: [Soekris] Comm Port Help! > > Hi, > > RB wrote: > > On 7/17/07, Bob Camp <[EMAIL PROTECTED]> wrote: > >> Yes, I would *think* that the bios and grub settings are not going to > >> impact what happens once the kernel is up. The problem is a kernel > >> resource conflict rather than a bios of boot loader problem. > > > > I concur. If you can at all, leave grub pointing at the console, > > since it will only use it at boot. That way you have a last-ditch > > window to recover a system without desoldering. > > Fyi, no matter what comBIOS settings or operating system you have you > can always get into the comBIOS using Ctrl-P during POST, and there boot > PXE and reinstall whatever software you have on the soldered on flash.... > > > Best Regards, > > > Soren Kristensen > > CEO & Chief Engineer > Soekris Engineering, Inc. > _______________________________________________ > Soekris-tech mailing list > [email protected] > http://lists.soekris.com/mailman/listinfo/soekris-tech > > > > ------------------------------ > > Message: 4 > Date: Thu, 19 Jul 2007 13:30:38 -0400 > From: "Mark" <[EMAIL PROTECTED]> > Subject: Re: [Soekris] Comm Port Help! > To: "'RB'" <[EMAIL PROTECTED]>, <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="us-ascii" > > Thanks for the help, I starting to feel better about our design... > > --Mark > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of RB > Sent: Thursday, July 19, 2007 12:08 PM > To: [email protected] > Subject: Re: [Soekris] Comm Port Help! > > On 7/19/07, william estrada <[EMAIL PROTECTED]> wrote: > > 2) If I remember correctly, Grub does not support USB keyboards? > Incorrect - I've used USB almost exclusively for quite some time. > > > 3) Your OS should support this as a tty? > It does, through the usb-serial and related drivers. > _______________________________________________ > Soekris-tech mailing list > [email protected] > http://lists.soekris.com/mailman/listinfo/soekris-tech > > > > ------------------------------ > > Message: 5 > Date: Thu, 19 Jul 2007 19:12:36 +0000 > From: The Fungi <[EMAIL PROTECTED]> > Subject: Re: [Soekris] Comm Port Help! > To: [email protected] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=us-ascii > > On Thu, Jul 19, 2007 at 11:07:42AM -0500, RB wrote: > > On 7/19/07, william estrada <[EMAIL PROTECTED]> wrote: > > > 2) If I remember correctly, Grub does not support USB keyboards? > > Incorrect - I've used USB almost exclusively for quite some time. > [...] > > Grub supports BIOS keyboards. When your BIOS supports USB keyboards, > they can be used with Grub. Grub does not *itself* know anything > about USB. To my knowledge, Soekris COMBIOS doesn't know what to do > with USB keyboards, so Grub will not see them on a Soekris. And > anyway, what good does a peecee keyboard do you if you don't have > support for a corresponding display device to be able to see what > you're typing? > > I would recommend keeping the first built-in serial interface for > the BIOS/bootloader/OS consoles. Either attach a second port to the > header for the second built-in serial interface on the Soekris board > (see the list archives for pertinent information) or use a USB > serial device supported by your OS to give your application access > to the external device you need to control. > > However, as stated by others in this thread, telling your kernel to > boot with no console at all (and configuring the OS not to present a > login on that interface as well) should be sufficient to free up the > first on-board serial for other uses... > -- > { IRL(Jeremy_Stanley); PGP(9E8DFF2E4F5995F8FEADDC5829ABF7441FB84657); > SMTP([EMAIL PROTECTED]); IRC([EMAIL PROTECTED]); ICQ(114362511); > AIM(dreadazathoth); YAHOO(crawlingchaoslabs); FINGER([EMAIL PROTECTED]); > MUD([EMAIL PROTECTED]:6669); WWW(http://fungi.yuggoth.org/); } > > > ------------------------------ > > Message: 6 > Date: Fri, 20 Jul 2007 01:41:50 -0400 > From: "Benjamin S. Scarlet" <[EMAIL PROTECTED]> > Subject: Re: [Soekris] ethernet problems w/ Fedora 7 on net4826 > To: Kannaiyan Natesan <[EMAIL PROTECTED]>, > [email protected] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain > > I've got an fstab which looks like this: > > 192.168.0.1:/raid/clients/diskless / nfs rsize=8192,wsize=8192 > 0 0 > tmpfs /dev/shm tmpfs defaults 0 0 > devpts /dev/pts devpts gid=5,mode=620 0 0 > sysfs /sys sysfs defaults 0 0 > proc /proc proc defaults 0 0 > > and then I run > mkinitrd -f --fstab=fstab --with=natsemi initrd.img 2.6.21-1.3228.fc7 > > on a fedora 7 machine with the i586 version of the kernel-2.6.21-1.3228 > rpm (from which I also take the kernel). > > For the vmware image, I replace natsemi with pcnet32, otherwise > everything else is the same. Since the image with pcnet32 works for the > vmware image, my first guess at whether I'd got the process right was > that I had. Granted, the net4826 version winds up picking up some extra > modules, because mkinitrd guesses they're necessary based on the > configuration of the machine it's running on (another vmware image, this > one with a disk, from which I copied the nfsroot directory, and with an > i586 kernel installed), but I wouldn't think the extra modules would > hurt anything, at least as a first guess. > > Given that the nfs server sees some packets and responds, but the actual > connection isn't working, I would have guessed some sort of driver > issue. > > -Ben Scarlet > > > On Wed, 2007-07-18 at 08:13 -0600, Kannaiyan Natesan wrote: > > May I know what parameters you have used for initrd to do the nfs boot > > ? Something might have missed out there. > > > > Kannaiyan > > > > On 7/18/07, Benjamin S. Scarlet <[EMAIL PROTECTED]> wrote: > > > Hello, > > > > > > I'm trying to get a net4826 running Fedora 7, using an NFS root > > > filesystem. When my boot process (dhcp, pxelinux, initrd, remount nfs as > > > root) gets to the point of mounting the nfs root, it has trouble > > > contacting the nfs server. > > > > > > For purposes of validation, I'm comparing to a VMware image, booting > > > with the same procedure. The only differences between the two are the > > > (perhaps virtual) hardware, the network cabling, and that the > > > initrd.img's differ in which network driver kernel module is included - > > > the VMware image gets an initrd with pcnet32, while the net4826 gets one > > > with natsemi. > > > > > > The vmware image boots fine. > > > > > > The net4826 pxeboots fine. Since the dhcp server and the tftp server are > > > on the same machine as the nfs server, I think the hardware and network > > > cabling are functional. > > > > > > The boot proceeds through the pxeboot to mount the initrd, load the > > > contained kernel modules including natsemi.ko, and re-acquire for linux > > > the ip which the pxe code got a few seconds before. (This is > > > interesting to me because that step presumably uses the ethernet through > > > the natsemi.ko, successfully). > > > > > > Then the initrd continues to boot, and tries to nfs mount the final > > > root. At this point all I get are a (very) slow progression of > > > > > > nfs: server 192.168.0.1 not responding, still trying > > > > > > messages, with an occasional > > > > > > nfs: server 192.168.0.1 OK > > > > > > thrown in. > > > > > > tcpdump on the nfs server does show some packets in both directions, but > > > I don't know what to look for beyond that. > > > > > > I've checked the code of the Fedora 7 natsemi kernel module, and it does > > > seem to include some form of the short cable patch, though a newer form > > > than the old one I found googling soekris-tech. > > > > > > Would anybody perhaps have any ideas what could be going wrong? I can > > > provide net4826 console logs and tcpdump logs and such if they'd help. > > > > > > Thanks, > > > Benjamin S. Scarlet > > > > > > > > > _______________________________________________ > > > Soekris-tech mailing list > > > [email protected] > > > http://lists.soekris.com/mailman/listinfo/soekris-tech > > > > > > > ------------------------------ > > Message: 7 > Date: Fri, 20 Jul 2007 08:04:56 +0200 > From: Bastien Durel <[EMAIL PROTECTED]> > Subject: [Soekris] net4501 reboot/crash > To: [email protected] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1 > > Hello, > > since monday, my net4501 is constantly rebooting. > > monday evening, it rebooted on networking initialization (it runs > OpenBSD), but now, the error led doesn't shut down, and I do not ever > see the memory test. It crashs during the POST ... > > I removed the CF, wifi card, and network cables, and now I have time to > see the bios before the reboot. > The error led do not shut down, thought. > > Ther are the only two lines I can see on the console before reboot : > > > POST: 0123456789bcefghipajklnopq,,,tvwxy > > > > comBIOS ver. 1.28 20050527 Copyright (C) 2000-2005 Soekris > > Is the card broken ? > > Thanks, > > -- > Bastien > Beaucoup trop pay? pour ce que je fais, > mais pas assez pour ce que je m'emmerde. > -+- Daniel Pennac -+- > > > ------------------------------ > > Message: 8 > Date: Fri, 20 Jul 2007 13:33:48 +0500 > From: "Eitesam Ahmad" <[EMAIL PROTECTED]> > Subject: [Soekris] how to install astlinux on net4826 using PXE > To: [email protected] > Message-ID: > <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="iso-8859-1" > > Dear All, > > I am having trouble installing AstLinux-0.4.6.1-net4801.img, on a net4826-50 > box, i have followed many documents for this but whenever the box loades the > vmlinuz and initrd, it just displayes Ready, and the screen goes away, > nothing displays ater this, can you please guide me how to do it ? or if > someone can refer some step by step guide to do this. > > Thanks and regards > > Ahmad > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.soekris.com/pipermail/soekris-tech/attachments/20070720/91379017/attachment-0001.html > > ------------------------------ > > Message: 9 > Date: Fri, 20 Jul 2007 13:25:38 +0200 > From: "Nils Vogels" <[EMAIL PROTECTED]> > Subject: Re: [Soekris] how to install astlinux on net4826 using PXE > To: [email protected] > Message-ID: > <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hi Eitesam, > > On 7/20/07, Eitesam Ahmad <[EMAIL PROTECTED]> wrote: > > Dear All, > > > > I am having trouble installing AstLinux-0.4.6.1-net4801.img, on a net4826-50 > > box, i have followed many documents for this but whenever the box loades the > > vmlinuz and initrd, it just displayes Ready, and the screen goes away, > > Since vmlinuz and initrd are loaded, the operating system has > effectively started up. I suspect this is something specific to > AstLinux. > > One thing that I've ran across on various OS's is that the COMport > speeds vary every once in a while. It could be that AstLinux switches > from 9600/8/N/1 to some other speed? > > Greetings, > > Nils > > > ------------------------------ > > _______________________________________________ > Soekris-tech mailing list > [email protected] > http://lists.soekris.com/mailman/listinfo/soekris-tech > > > End of Soekris-tech Digest, Vol 41, Issue 23 > ******************************************** > _______________________________________________ Soekris-tech mailing list [email protected] http://lists.soekris.com/mailman/listinfo/soekris-tech
