Re: [Leaf-user] Wireless node on network
While I'm not completely useful in the area of the troubleshooting, I am curious how you configured the laptop to see the Wireless Card and get it configured. Did you use a stock howto or did you wing it? Would you be willing to write something possibly to demonstrate how to do it? --Pat On Thu, 28 Feb 2002, Da Haverford wrote: I have a home network behind a Dachstein v1.0.2 based floppy. It works flawlessly. I am trying to setup a dual homed laptop with one pcmcia card as a node on the network and the second pcmcia card - a wireless Lucent Orinonco. A second laptop with a similiar card is setup nearby. So far, I can ping the wireless client from the network attached laptop and visversa. However, I am not able to reach the Internet from the wireless client. My manipulations of ipchains has been unsuccessful. Any recommendations or references appreciated. ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] Bering and DOC2000
Since I see you are using MTD, would you be able to make your image available to others? If you need space to host it, I'll find someplace to put it. For some reason it seems like I'm pushing the envelope of Leaf by wanting to use PCMCIA Wireless Cards and a DOC2000 ;) Thanks! --Patrick On Fri, 8 Feb 2002, Bao C. Ha wrote: Hi guys, I have been able to bring the Jacques Nilo's Bering Leaf distribution up on a Disck-On-Chip (DOC2000) based system. I am using the Beta 2 since there seems to be problems with modify the Beta 3 floppy image. Following is the summary of changes to make it happens. (1) The DOC2000 has one partition. It is used as an ext3 filesystem. The content of the floppy image is put on the DOC's partition. (2) Grub. I am using grub to boot up from DOC. Following is the /boot/grub/menu.lst file. default 0 timeout 5 title=Linux with video card and keyboard kernel (dc0,0)/linux ramdisk_size=1536 init=/linuxrc \ root=/dev/ram0 boot=/dev/nftla1,ext3 LRP=root,etc,local,\ modules,pump,keyboard,shorwall,dnscache,weblet,dhcpd,ppp,\ pppoe,log,libz,sshd,sshkey,ssh,sftp initrd (dc0,0)/initrd.lrp Notes: - The kernel command is all on one line. - There is no PKGPATH. That will hang the DOC2000. Mtd devices can't be mounted at multiple points at the same time. (3) Loading required modules at boot time. The /boot/etc/modules is changed to load the following modules: (the order is very important to detect nftl on DOC2000) mtdcore docecc doc2000 docprobe nftl mtdchar mtdblock jbd ext3 There is probably no need to load mtdchar and mtdblock. Both the jbd and ext3 modules can be replaced by another fs module, like ext2, if ext2 file system is to be used for the DOC2000. These modules are also downloaded into the /boot/lib/modules directory (4) Add the following to the /var/lib/lrpkg/root.dev.mk file to create the /dev/nftla devices. #DOC nftl makedevs nftla b 93 0 0 8 s null 21 makedevs nftlb b 93 16 0 8 s null 21 That is all! Thanks. Bao ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] Bering and DOC2000
Are there any special procedures for me to boot off the DOC? rdev it and that's it? --Pat On Sat, 16 Feb 2002, Mike Noyes wrote: At 2002-02-16 08:21 -0500, Patrick Nixon wrote: Since I see you are using MTD, would you be able to make your image available to others? If you need space to host it, I'll find someplace to put it. Patrick, The LEAF Bering release has mtd modules. http://leaf.sourceforge.net/devel/jnilo/leaffw.html http://leaf.sourceforge.net/devel/jnilo/bering/latest/modules/drivers/mtd/ For some reason it seems like I'm pushing the envelope of Leaf by wanting to use PCMCIA Wireless Cards and a DOC2000 ;) Yes. We're working to make this easier. -- Mike Noyes [EMAIL PROTECTED] http://sourceforge.net/users/mhnoyes/ http://leaf.sourceforge.net/content.php?menu=1000page_id=4 ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] Bering and DOC2000
Pat, I don't know the exact procedure you need to follow. You may be the first person to try the mtd support in Bering. I'm just going to fire off some thoughts, perhaps not the correct answer :) I thought Charles laid it out pretty well in his hard disk howto and the cdrom howto boot instructions. Even though the directions refer to booting from a different device, the fundamental parts remain true, imo: 0) Need to be able to prove you can access the DOC device from a running LEAF system, thereby defining the modules that needed to be loaded to talk to it. Make note of IRQ's and addresses for comparison later. Using something I recall as Mullenstein (John Mullen did it I think), I have successfully booted and loaded using the M-Systems doc.o However, due to the license of M-systems driver, it can't be redistributed (or at least that's my understanding.) I've even compiled my own version of the kernel. Bering is based off 2.4.x which has MTD support directly in the kernel. Which shouldn't be too big of a problem to test except that my system with the DOC doesn't have a floppy so it's a rather time consuming process to try different sets of files. (I know, poor me ;) I'm relatively new at the whole development, unusual requirements thing, so while I am confident about compiling a kernel and whatnot, getting it t boot properly is shaky ground for me. 1) Need those modules that made the DOC work loaded for the kernel during the bootstraping initrd process (put them in /var/lib/modules?). So the idea is to take the working image from step (0) and burn a new diskette making sure that... 2) syslinux.cfg points to the boot device and the DOC modules get loaded during boot. Isn't that the big picture? If so, I'd like to hear about this fellow's configuration in level (0), and then move on. A big factor with these PC Cards and Compact Flash Cards is that they don't normally get an irq assignment by the PCI bios, or something like that, during POST, the way the other devices do. Johan and a few others are hashing through the details of what it takes to force a mass storage card to the correct IRQ and base address, or at least to reserve those settings for the device to take when it's driver loads. The issue is with the CardBus bridge and the CF bridge, which buffer data to the PCI bus and have to handle recognizing the different PC Cards during hot-swap operations. Maybe CF Cards with True IDE emulation would work easier. The LEAF Bering release has mtd modules. http://leaf.sourceforge.net/devel/jnilo/leaffw.html I don't know if JN is reading this thread, but it'd be nice if the above link would go a bit further in the What is Bering description. To say it is basically an enhanced Dachstein doesn't tell the new person what Bering is if they don't know what Dachstein is. I think the answer would want to include something like: Bering is a miniature Linux OS that lives entirely on a 1.68 MB diskette, and it's purpose is to act as a router/firewall that connects two networks, filtering the content to protect the internal network. Bering is based upon a tried and true router/firewall called Dachstein (version rc2), created by Charles St[ei][ie]nk[ue][eu]l[h]er, sigh. The Bering firewall uses iptables for the firewall rules and Linux kernel 2.4.x as the base OS. Running Bering on an old Pentium with 32 MB of RAM is like using one of those Linksys or DLink router-firewalls, except that Bering is much more powerful, capable, and extensible. If I don't hear from him, I'll suggest that in another thread. Good Luck, Matthew ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
RE: [Leaf-user] LRP and DOC
John, Let me be the first to congratulate you on a fine procedure and excellent work in doing this! I now have my websurfer proo running without a hard drive! Next project will be PCMCIA for wireless support, then USB ethernet plugged ( I know this works already). Suggestion: On your dos boot, create an autoexec.bat that contains simply '@echo off' so it doesn't ask you for the date/time each time you boot. I had to go about it a bit differnetly since I didn't have a floppy drive, but the same basic steps worked for me. --Pat On Sun, 27 Jan 2002, John Mullan wrote: Patrick (and all): I have created a page to help you on your quest. Please go to my web page at: http://mullan.dns2go.com/ Click on the 'Internet' link on the left panel. Keep in mind that I still consider myself quite a 'beginner' with Linux. However, if your system is similar to mine (IBM clone type with DiskOnChip2000) then I think following my page will result in a working system. I included all files I used to get a working flash based router. I have followed all the advice and included the DOC.O module separate in my distribution (ie; not compiled into the kernal). I look forward to all comments (good and bad) so I may improve my first psuedo-HOWTO. Cheers, John -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Patrick Nixon Sent: Saturday, January 26, 2002 1:51 PM To: John Mullan Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: FW: [Leaf-user] LRP and DOC John, Congrats on getting this working. I'm currently spending most of my weekend attempting to get it working and like charles mentioned, I'm running into a 'insufficent low memory error'. How did you get around that? When I attempted to syslinux the DOC using 1.66 it whined about exclusive access. Perhaps you can do a small write up on the steps you took to complete it? Thanks, Patrick On Sat, 26 Jan 2002, John Mullan wrote: Sorry, forgot to leave the link for the file... http://mullan.dns2go.com/files/MullanStein.zip -Original Message- From: John Mullan [mailto:[EMAIL PROTECTED]] Sent: Saturday, January 26, 2002 8:51 AM To: 'Charles Steinkuehler'; '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]' Subject: RE: [Leaf-user] LRP and DOC Charles FINALLY! It works. And it works great. I think the latest and greates SYSLINUX (version 1.66) did it for me. Once I re-did the boot loader with that, it worked. For informational purposes ONLY, if you or any list member would like to see what it took, I have made a ZIP of all files currently on my embedded board. Because of the licence thing about M-SYS (and the fact that I used your sample kernal with DOC in it), this is not a distribution. The board was purchased from ARISE computers, is a PIII 433mhz with DiskOnChip 2000 (80meg), 32meg RAM, Intel 82559 ethernet on board, and DE-538 in the only on-board PCI slot. Obviously this is over-kill for the job at hand, but since it was made available to me :) John PS: I like the WEBLET thing. First time for me and it's a nice feature. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Charles Steinkuehler Sent: Friday, January 25, 2002 2:59 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: [Leaf-user] LRP and DOC This results in an immediate 'boot fail' message. Note that I have tried minor:1 and minor:0 both with same result. Could there be a problem with the boot sector information? Does 'syslinux' work properly on D.O.C.? I don't know...I have yet to play with syslinux and DOC in an embedded environment. I did get a ZF Linux eval board with a DOC, but when I tried to run syslinux, I never got past the not enough low memory problem (but syslinux *was* running). I'm not sure how the other folks who have used DOC's boot their systems. I suppose you could always fall back to booting dos, and using ldlinux. I also think there are versions of lilo and grub that know how to boot from a DOC... Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
RE: [Leaf-user] LRP and DOC
John, Does your Kernel have IDE/CDRom support in it, or is it just a modified floppy kernel? --Pat On Mon, 28 Jan 2002, Patrick Nixon wrote: John, Let me be the first to congratulate you on a fine procedure and excellent work in doing this! I now have my websurfer proo running without a hard drive! Next project will be PCMCIA for wireless support, then USB ethernet plugged ( I know this works already). Suggestion: On your dos boot, create an autoexec.bat that contains simply '@echo off' so it doesn't ask you for the date/time each time you boot. I had to go about it a bit differnetly since I didn't have a floppy drive, but the same basic steps worked for me. --Pat On Sun, 27 Jan 2002, John Mullan wrote: Patrick (and all): I have created a page to help you on your quest. Please go to my web page at: http://mullan.dns2go.com/ Click on the 'Internet' link on the left panel. Keep in mind that I still consider myself quite a 'beginner' with Linux. However, if your system is similar to mine (IBM clone type with DiskOnChip2000) then I think following my page will result in a working system. I included all files I used to get a working flash based router. I have followed all the advice and included the DOC.O module separate in my distribution (ie; not compiled into the kernal). I look forward to all comments (good and bad) so I may improve my first psuedo-HOWTO. Cheers, John -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Patrick Nixon Sent: Saturday, January 26, 2002 1:51 PM To: John Mullan Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: FW: [Leaf-user] LRP and DOC John, Congrats on getting this working. I'm currently spending most of my weekend attempting to get it working and like charles mentioned, I'm running into a 'insufficent low memory error'. How did you get around that? When I attempted to syslinux the DOC using 1.66 it whined about exclusive access. Perhaps you can do a small write up on the steps you took to complete it? Thanks, Patrick On Sat, 26 Jan 2002, John Mullan wrote: Sorry, forgot to leave the link for the file... http://mullan.dns2go.com/files/MullanStein.zip -Original Message- From: John Mullan [mailto:[EMAIL PROTECTED]] Sent: Saturday, January 26, 2002 8:51 AM To: 'Charles Steinkuehler'; '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]' Subject: RE: [Leaf-user] LRP and DOC Charles FINALLY! It works. And it works great. I think the latest and greates SYSLINUX (version 1.66) did it for me. Once I re-did the boot loader with that, it worked. For informational purposes ONLY, if you or any list member would like to see what it took, I have made a ZIP of all files currently on my embedded board. Because of the licence thing about M-SYS (and the fact that I used your sample kernal with DOC in it), this is not a distribution. The board was purchased from ARISE computers, is a PIII 433mhz with DiskOnChip 2000 (80meg), 32meg RAM, Intel 82559 ethernet on board, and DE-538 in the only on-board PCI slot. Obviously this is over-kill for the job at hand, but since it was made available to me :) John PS: I like the WEBLET thing. First time for me and it's a nice feature. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Charles Steinkuehler Sent: Friday, January 25, 2002 2:59 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: [Leaf-user] LRP and DOC This results in an immediate 'boot fail' message. Note that I have tried minor:1 and minor:0 both with same result. Could there be a problem with the boot sector information? Does 'syslinux' work properly on D.O.C.? I don't know...I have yet to play with syslinux and DOC in an embedded environment. I did get a ZF Linux eval board with a DOC, but when I tried to run syslinux, I never got past the not enough low memory problem (but syslinux *was* running). I'm not sure how the other folks who have used DOC's boot their systems. I suppose you could always fall back to booting dos, and using ldlinux. I also think there are versions of lilo and grub that know how to boot from a DOC... Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: FW: [Leaf-user] LRP and DOC
John, Congrats on getting this working. I'm currently spending most of my weekend attempting to get it working and like charles mentioned, I'm running into a 'insufficent low memory error'. How did you get around that? When I attempted to syslinux the DOC using 1.66 it whined about exclusive access. Perhaps you can do a small write up on the steps you took to complete it? Thanks, Patrick On Sat, 26 Jan 2002, John Mullan wrote: Sorry, forgot to leave the link for the file... http://mullan.dns2go.com/files/MullanStein.zip -Original Message- From: John Mullan [mailto:[EMAIL PROTECTED]] Sent: Saturday, January 26, 2002 8:51 AM To: 'Charles Steinkuehler'; '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]' Subject: RE: [Leaf-user] LRP and DOC Charles FINALLY! It works. And it works great. I think the latest and greates SYSLINUX (version 1.66) did it for me. Once I re-did the boot loader with that, it worked. For informational purposes ONLY, if you or any list member would like to see what it took, I have made a ZIP of all files currently on my embedded board. Because of the licence thing about M-SYS (and the fact that I used your sample kernal with DOC in it), this is not a distribution. The board was purchased from ARISE computers, is a PIII 433mhz with DiskOnChip 2000 (80meg), 32meg RAM, Intel 82559 ethernet on board, and DE-538 in the only on-board PCI slot. Obviously this is over-kill for the job at hand, but since it was made available to me :) John PS: I like the WEBLET thing. First time for me and it's a nice feature. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Charles Steinkuehler Sent: Friday, January 25, 2002 2:59 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: [Leaf-user] LRP and DOC This results in an immediate 'boot fail' message. Note that I have tried minor:1 and minor:0 both with same result. Could there be a problem with the boot sector information? Does 'syslinux' work properly on D.O.C.? I don't know...I have yet to play with syslinux and DOC in an embedded environment. I did get a ZF Linux eval board with a DOC, but when I tried to run syslinux, I never got past the not enough low memory problem (but syslinux *was* running). I'm not sure how the other folks who have used DOC's boot their systems. I suppose you could always fall back to booting dos, and using ldlinux. I also think there are versions of lilo and grub that know how to boot from a DOC... Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] Kernel w/ DOC support
Just to clear on this issue. I would take my DOC, format it to dos, put syslinux on it Copy the DOC kernel and module to the DOC, along with the rest of the contents of the Dachstein floppy (going small first) and presto, it works? What did I miss? I know it's not that easy. --Pat On Mon, 7 Jan 2002, Charles Steinkuehler wrote: Would that 2.2 kernel be compatible with Dachstein? Do modules have to be re-configured? Yes, it's basically the 2.2.19 Dachstein kernel with the M-Systems DOC patches applied. Other gotchas? Since it's a binary-only module (no source available and not GPL'd) you can only distribute the kernel with DOC support compiled as a module...no compiling it into the kernel except for testing. This isn't too bad, as the Dachstein init scripts have support for loading boot-time device modules for HDD, CD-ROM, RAID, etc...you just have to make a custom root.lrp package. Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] Kernel w/ DOC support
Okay, that sort of makes sense! I can only try! Can you email these to mr or should I download them from someplace? --Pat On Tue, 8 Jan 2002, Charles Steinkuehler wrote: Just to clear on this issue. I would take my DOC, format it to dos, put syslinux on it Copy the DOC kernel and module to the DOC, along with the rest of the contents of the Dachstein floppy (going small first) and presto, it works? Or not... What did I miss? I know it's not that easy. The system you list would boot-up (BIOS POST), then syslinux would run and load the kernel and initial ramdisk image. At that point, the kernel would execute linuxrc, which would try to load your LRP pacakges. At this point, everything would die, since the kernel (and hence linuxrc) doesn't know how to read data from the DOC...only the BIOS (and through it, syslinux) know how to read the DOC until you load kernel modules to support it. Remember...linux doesn't talk to any hardware through the BIOS. NOTE: The kenel modules to talk to the DOC can be loaded at runtime from the ramdisk image...this is why the initrd support is in the kernel in the first place... Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] Kernel w/ DOC support
Would that 2.2 kernel be compatible with Dachstein? Do modules have to be re-configured? Other gotchas? --Pat On Mon, 7 Jan 2002, Charles Steinkuehler wrote: Well, this is currently not real high on my todo list, and when I get around to playing with MTD support, I'll probably be hacking to code to support a DOC2000 plugged into the ROM socket of a network interface...if you want a 2.4 kernel with MTD, you'll probably have to compile it yourself :( NOTE: I do have 2.2 kernels available with the msystems driver binary module, if you don't have to have a 2.4 kernel...they're not on the website to save space. Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) Charles Steinkueler (sp ? sorry charles) is/was working on this last time I checked. No update as of yet, maybe he'll be kind and give us his status. I'm waiting ever so patiently (okay, not really) for this support also! --Patrick On Fri, 4 Jan 2002, Bao C. Ha wrote: Is there a pre-compiled kernel 2.4.x with DOC2000 support via mtd? I have built a minimal Linux system that can boot up from Grub. I would like to redo it in LEAF. Thanks. Bao ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] Kernel w/ DOC support
Charles Steinkueler (sp ? sorry charles) is/was working on this last time I checked. No update as of yet, maybe he'll be kind and give us his status. I'm waiting ever so patiently (okay, not really) for this support also! --Patrick On Fri, 4 Jan 2002, Bao C. Ha wrote: Is there a pre-compiled kernel 2.4.x with DOC2000 support via mtd? I have built a minimal Linux system that can boot up from Grub. I would like to redo it in LEAF. Thanks. Bao ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
[Leaf-user] Network Card Problem
Hello All, I briefly mentioned a few weeks ago a problem I'm having with a specific network card, however, no one had any solid advice and I wasn't sure what the exact problem was so I'm reposting with a bit more information I hope. NIC: 3Com 3C920 Integrated network Card (lists as a 3c905C-TX in some systems) System: Dell Optiplex GX150 Problem: Despite a successful loading of the module 3c59x.o I am unable to receive any data over the network interface. from netstat -i I can see that it's transmitting, just not receiving properly. I have RedHat 7.2 with Kernel 2.4.3-7 running on an identical system, with a 'different' 3c59x.o module and that system is happyhappy. Ideas/suggestions/whathaveyous? --Pat ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re:[Leaf-user] loading PCMCIA modules
Hey, just to confirm what Brock already said, here's what I load upon boot ray_cs 18368 1 ds 6120 1 [ray_cs] i82365 21340 1 pcmcia_core48864 0 [ray_cs ds i82365] However, just to voice my experience, I can't get my wireless card to be anything but eth0 if I boot up with it in it, which required me to fix the configs to make eth1 my external interface. --Pat On Tue, 25 Dec 2001, Brock Nanson wrote: Pete, When I built my (Eiger) BreezeCOM box, I loaded, in this order: pcmcia_core i82365 ds I'm not real sure of what each does exactly but I *think*: pcmcia_core is the basic pcmcia functionality i82365 is the driver for the pcmcia chip (in my case an ISA - PCMCIA adapter board) ds is the actual card services to recognize a card has been inserted and load the appropriate driver. This only laces your skates - it doesn't win the hockey game. There is a directory /etc/pcmcia that has some config files for the card services. The actual wireless card driver is in /lib/modules/pcmcia. From what I can see (and someone can correct me if I'm wrong), the regular LRP modules file causes the listed modules to be loaded. In the order they appear. So the PCMCIA capability gets started, and probably a regular NIC if you have one. But the big catch is - the wireless card doesn't get loaded until the card services gets run! This is well after the modules file is read. In other words, wireless and other PCMCIA devices don't get loaded from the modules file. A side issue that comes from this is - there doesn't seem to be a simple way to cause your PCMCIA device to be eth0... it gets loaded after the NIC in modules, so by default becomes eth1. This means adjusting the remainder of the config files. Hopefully someone will jump in and correct my mistakes! As well, note that this is all based on Eiger - I have no idea what Dachstein does in this regard! Good luck, Brock Message: 7 Date: Tue, 25 Dec 2001 20:09:06 -0800 From: Pete Dubler [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: [Leaf-user] loading PCMCIA modules The saga continues... I refuse to ask a question until after I have spent a good 18 hours suffering and researching on my own... I am trying to get a wireless router going based on the Cisco Aironet 342 ISA card and the Dachstein release, combined with IDE and PCMCIA services, as posted by FABbnet (http://www.fabbnet.net/lrp.htm). (I promise to write a very explicit HOWTO about all this once I (with your help) get it working.) We are going to be building several of these for our neighborhood, so the days and days I have put into it will eventually pay so dividends in terms of public service... I must not be loading all of the necessary modules. Do you have any pointers?. I am loading: airo irq=5 io=0x340 airo_cs pcmcia_core What else, and if necesary, in what order, must I have them? I am getting the following messages at boottime: airo: Trying to configure ISA adapter at irq=5 io=0x340 airo: Rid ff15 has a length of -2 which is too short airo: bad MAC enable reason=85, rid=ff10, offset=16 airo: MAC could not be enabled ... airo_cs:... insmod: unresolved symbol register_pccard_driver insmod: unresolved symbol unregistered_pccard_driver insmod: unresolved symbol CardServices Looking forward to 11mbs before the new year Happy Holidays, Pete Dubler Fort Collins, CO ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] serial console
Like someone else already posted you need a serial terminal program. The one that leaps to my mind that most everyone has is HyperTerminal. Instead of putting a phone number into it, change the Connect Using from whatever it is listed to 'Direct to ComX' where X is your serial port number (ie: Com1, Com2). Also, make sure you match the settings you put in when you initialized the serial consoles or you'll see funny characters on the console. Hope this helps, Pat On Thu, 20 Dec 2001, guitarlynn wrote: This is likely a no-brainer for those that have done this, but after a couple of days of hunting and trying, I can't seem to get it. I've enabled a serial console following Charles' Serial HowTo on ttyS0 on Dachstein CD v1.0.2, everything there appears to be fine. I have Win95 on a laptop (haven't bothered to upgrade since it doesn't have a cd-rom) and have been trying to use a terminal emulator (Sterm in particular) to connect to the Dachstein box. All the emulator's I've tried want a port to connect to Dachstein with, I've tried ports 22, 23, 111, 512, 513, and 514 with no avail.. all return request turned down by server. It seems through hunting on the net that the emulation prog should just work, but no guidelines on how it supposed to be set to work. I've tried to even ssh in w/putty (that works on the LAN) but not on the serial. I am hoping to run Dachstein on a box reduced to a 1U half-slot. The serial terminal would be very nice if any problems resulted on LAN connection. Any advice or suggestions would be appreciated, ~Lynn Avants [EMAIL PROTECTED] ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
[Leaf-user] Network Card Issue
Hey All, I'm starting to play with the new Dachstein v1.0.2. For some reason the network module for the 3c59x isn't working 100% happy like for a 3c905C-TX onboard card. Whenever I try to get a dhcp address, I can see the request on the DHCP Server, and it reply with an address, however the Dachstein CD never sees it. Running a netstat -i shows 0 packets received. I've tried two identical computers and multiple network cables. ideas, suggestions, flames? --Pat ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
