Re: [Leaf-user] ATT transition woes
gc wrote: I've got a standard configuration: home network behind a cable modem. I've been running an old Eiger distribution for the past year without issue. Then I got caught up in the big ATT migration last week and it screwed things up. Rather than troubleshoot such an old distribution, I figured I'd start over with the Dachstein v1.0.2 distribution. That's what I did for a friend. We had Oxygen running on his @Home rigged as a static IP setup even though it's dhcp. Then when they choked and became attbi (they never should have merged with the white elephant Excite), their dhcp is so touchy that I couldn't rely on the static rig, and I went for dhcp. Oxygen locked up during boot, after enabling the correct nic modules and rebooting. Doing the same on Dachstein rc2 gave him a perfectly working system. It was pretty spectacular, I must say. I followed the basic setup instructions, but it didn't fix my problem. Specifically, I can only ping a couple of hosts. Describe exactly what you did and what you saw, if it's still happeing and the DNS advice you got doesn't fix it. If I hook my win2k box directly to the cable modem, everything works fine. Yea yea. And if I suck Bill's cock, he might let me drink from the river of wealth. The suspipcious thing is that my win2k box uses different IP and gateway addresses than the LEAF router (even though both use DHCP). So, I'm thinkin it's some sort of DHCP configuration problem. Just so you know, it's common to get a new IP address and whatnot when you switch systems (and thus mac addresses) and get a new lease. I didn't have to touch a single dhcp setting to get my friend's attbi.com system in Petaluma, CA to work. I messed around with the dhcpclient settings with no success. One thing I wondered was if I needed to update the domain name somewhere (since it changed from home.com to attbi.com), but I couldn't find anything that looked relevant. I thought I was going to have to labor through something like that, but instead it was butter. Good Luck, Matthew Any other former excite@home users go through this? Anybody else have any thoughts? Thanks in advance. ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
RE: [Leaf-user] ATT transition woes
I switched from ESB2 to Dachstein CD while the service (@home) was out. Left the machine on while I was at work. Came home, and it had connected when the service came back up, Like Magic, and I was all set to go! None of the BS configurator nonsense! Been running fine ever since! Sean -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Matt Schalit Sent: Friday, December 14, 2001 4:37 AM To: [EMAIL PROTECTED] Subject: Re: [Leaf-user] ATT transition woes gc wrote: I've got a standard configuration: home network behind a cable modem. I've been running an old Eiger distribution for the past year without issue. Then I got caught up in the big ATT migration last week and it screwed things up. Rather than troubleshoot such an old distribution, I figured I'd start over with the Dachstein v1.0.2 distribution. That's what I did for a friend. We had Oxygen running on his @Home rigged as a static IP setup even though it's dhcp. Then when they choked and became attbi (they never should have merged with the white elephant Excite), their dhcp is so touchy that I couldn't rely on the static rig, and I went for dhcp. Oxygen locked up during boot, after enabling the correct nic modules and rebooting. Doing the same on Dachstein rc2 gave him a perfectly working system. It was pretty spectacular, I must say. I followed the basic setup instructions, but it didn't fix my problem. Specifically, I can only ping a couple of hosts. Describe exactly what you did and what you saw, if it's still happeing and the DNS advice you got doesn't fix it. If I hook my win2k box directly to the cable modem, everything works fine. Yea yea. And if I suck Bill's cock, he might let me drink from the river of wealth. The suspipcious thing is that my win2k box uses different IP and gateway addresses than the LEAF router (even though both use DHCP). So, I'm thinkin it's some sort of DHCP configuration problem. Just so you know, it's common to get a new IP address and whatnot when you switch systems (and thus mac addresses) and get a new lease. I didn't have to touch a single dhcp setting to get my friend's attbi.com system in Petaluma, CA to work. I messed around with the dhcpclient settings with no success. One thing I wondered was if I needed to update the domain name somewhere (since it changed from home.com to attbi.com), but I couldn't find anything that looked relevant. I thought I was going to have to labor through something like that, but instead it was butter. Good Luck, Matthew Any other former excite@home users go through this? Anybody else have any thoughts? Thanks in advance. ___ 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] ATT transition woes
Matt Schalit wrote: That's what I did for a friend. We had Oxygen running on his @Home rigged as a static IP setup even though it's dhcp. Then when they choked and became attbi (they never should have merged with the white elephant Excite), their dhcp is so touchy that I couldn't rely on the static rig, and I went for dhcp. Oxygen locked up during boot, after enabling the correct nic modules and rebooting. It would be nice to know what happened. However, I've been using the current pre-release version of Oxygen with DHCP routinely - especially since I don't have to configure it :) It works just fine. ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] Newbie Q: 2 of 2
On Thu, 13 Dec 2001, Kenneth Downs wrote: Folks, The extensive documentation on Sourceforge is a delight, many thanks to those who have put time into it, it will provide much pleasant reading and education. I do have one question that I do not see covered, and I wonder if I just don't know the word I am looking for. Is it possible to have a LEAF box connected to two external lines with totally different IPs (DSL in this case) so as to provide automatic rollover if one of them goes down? Off to read the docs... TIA, - Kenneth Downs [EMAIL PROTECTED] http://www.monkeynoodle.org/lrp/LRP-Load-Balancing-HOWTO.html -- Jack Coates Monkeynoodle: A Scientific Venture... ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] ATT transition woes
--- Matt Schalit [EMAIL PROTECTED] wrote: gc wrote: Describe exactly what you did and what you saw, if it's still happeing and the DNS advice you got doesn't fix it. o Downloaded Dachstein 1.0.2 distribution o Loaded it onto a floppy o Selected appropriate modules for my NIC cards in /etc/modules (8390 and ne2k) o Commented out the masq_quake module o Tried to enable a serial port console in /etc/inittab (which didn't work, btw, but i'll figure that out some other day) o Backed up /etc o Added a send host-name line to dhclient.conf o Backed up dhclient o Rebooted o Observed the DHCP sequence go through successfully o Examined IP address and routing table. Nothing apparently out of the ordinary. o The 'ip route' command showed an entry that said something like this: 11.22.33.44/28 ... src 22.33.44.55 o I could not ping 11.22.33.44 (what I believe should be my next hop router, yes?) o I could ping 22.33.44.55 o I could not ping any other nodes (Sorry I don't have exact IP addresses. I'm at work at the moment. I can supply them tonight if it would be helpful) If I hook my win2k box directly to the cable modem, everything works fine. Yea yea. And if I suck Bill's cock, he might let me drink from the river of wealth. Now, now...that wasn't a jab...i was simply making the point that the problem appears to be on my end. Just so you know, it's common to get a new IP address an whatnot when you switch systems (and thus mac addresses) and get a new lease. I didn't have to touch a single dhcp setting to get my friend's attbi.com system in Petaluma, CA to work. That gives me an idea. I know someone who had a problem when they unplugged their old computer from the cable modem and plugged a new one in. Turned out the system 'remembered' their MAC address and would only give them one IP address (in that case, though, DHCP was failing). The technician told them to power down the modem for five minutes and that cleared it up. I don't fully understand why, but there it is. modem for five minutes. I'm not sure why that seemed __ Do You Yahoo!? Check out Yahoo! Shopping and Yahoo! Auctions for all of your unique holiday gifts! Buy at http://shopping.yahoo.com or bid at http://auctions.yahoo.com ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] ATT transition woes
Describe exactly what you did and what you saw, if it's still happeing and the DNS advice you got doesn't fix it. o Downloaded Dachstein 1.0.2 distribution o Loaded it onto a floppy o Selected appropriate modules for my NIC cards in /etc/modules (8390 and ne2k) o Commented out the masq_quake module o Tried to enable a serial port console in /etc/inittab (which didn't work, btw, but i'll figure that out some other day) To save space, the small kernel tree used on the floppy distributions is compiled w/o built-in serial support. Either switch to the normal kernel, or d/l and install the serial.o module to get serial support (if you use the module, you get run-time support for serial ports...if you use the kernel, you can have kernel boot messages appear on the serial terminal). 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] dachstein cd 1.0.2 modules
I´ve just burned dachstein-cd-v1.0.2.iso and made the boot floppy from the image included. When I went to /lib/modules there is no single file. Why? Do I need to load every ip_masq* and net support files from diskette?? Are this files in another .lrp file??? The modules are on the CD. There are now commands to mount a device, and load modules directly from it, rather than having to copy modules into /lib/modules and back them up on your configuration floppy (wasting valuable space). The default /etc/modules configuration file includes the required commands to mount the CD and load modules from it, as well as comments on the newly added ! (bang) commands. 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] Datchstein CD 1.0.2 and pppoe
Hi, Here are some info about my work with Dachstein cd and pppoe - It seems that ifconfig.lrp is needed by the adsl-* scripts ... Once I figured out I was able to connect quite easily ( great work charles) Now a little question about some variables in thenetwork.conf My setup: eth0 -- adsl model eth1 -- internal lan I can connect with IF_AUTO="eth1" IF_LIST="ppp0 eth1" EXTERN_IF="ppp0" EXTERN_DHCP=NO EXTERN_DYNADDR=YES ???is it correct EXTERN_IP=DYNAMIC Regards, Etienne
Re: [Leaf-user] Datchstein CD 1.0.2 and pppoe
I can connect with IF_AUTO=eth1 IF_LIST=ppp0 eth1 EXTERN_IF=ppp0 EXTERN_DHCP=NO EXTERN_DYNADDR=YES ???is it correct This should be: EXTERN_DYNADDR=NO Not exactly intuitive, but the EXTERN_DYNADDR is kind of a relic from the past... EXTERN_IP=DYNAMIC 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] More questions about Datchstein CD 1.0.2 and pppoe
- is it possible to change the root ramdisk size and still booting from the CD ?? Yes, but you have to burn a new CD, with a different boot-floppy image. NOTE: It *is* possible to change the size of the /var/log ramdisk, since that's created at runtime. You only need a new boot-floppy image if you have to change the size of the root ramdisk. - I think that the behaviour of the cut command as changed It has in previous versions of dachstein: ping -c 1 some.dns.name | grep PING | cut -d (): -f 3 returned only the ip address 1.2.3.4 in dachstein cd, the same command returns (1.2.3.4): Any idea ?? The previous cut command was massively broken, and the fact that the above usage worked was an artifact of cut's mis-behavior. Try the above on a 'normal' linux system and you'll get an error...the delimiter for cut must be a single character... Try using sed instead of cut: sed 's/).*//;s/.*(//' 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] More questions about Datchstein CD 1.0.2 and pppoe
Charles Steinkuehler wrote: - is it possible to change the root ramdisk size and still booting from the CD ?? Yes, but you have to burn a new CD, with a different boot-floppy image. I thought you COULD change it. Hold down the left shift, and at the boot: prompt type linux ramsize=X ...and that should do it (assuming the default kernel label is linux)... Of course, you DO have to type it in... in previous versions of dachstein: ping -c 1 some.dns.name | grep PING | cut -d (): -f 3 returned only the ip address 1.2.3.4 in dachstein cd, the same command returns (1.2.3.4): Any idea ?? The previous cut command was massively broken, and the fact that the above usage worked was an artifact of cut's mis-behavior. Try the above on a 'normal' linux system and you'll get an error...the delimiter for cut must be a single character... Try using sed instead of cut: sed 's/).*//;s/.*(//' How about this (for your entire command line): ping -c 1 some.dns.name | sed -n '/PING/s/.*(\(.*\)):.*/\1/p' ...one sed command, no cut and no grep. ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] Squid package??
Sergio Morilla wrote: Dave Thanks for the package and the dependecies info!! Just one more question, I would like to move the cache to an HD I have on the computer, is this a paremeter on squid.conf? IIRC it's CacheDirectory. The manual at http://www.squid-cache.org/ will tell you if I was right. Ewald Wasscher ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] More questions about Datchstein CD 1.0.2 and pppoe
So, could I change the ramsize this way to get LEAF to boot up on a very low memory machine? (ie. 4MB) I -Steve On Friday, December 14, 2001, at 11:25 AM, David Douthitt wrote: Charles Steinkuehler wrote: - is it possible to change the root ramdisk size and still booting from the CD ?? Yes, but you have to burn a new CD, with a different boot-floppy image. I thought you COULD change it. Hold down the left shift, and at the boot: prompt type linux ramsize=X ...and that should do it (assuming the default kernel label is linux)... Of course, you DO have to type it in... ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] More questions about Datchstein CD 1.0.2 and pppoe
thanks I 'm sure that if both of you ( Charles and David) are able to - change tyres of a car - build a house only using sed and sh ;-) Once again thanks for your help Etienne Charlier - Original Message - From: David Douthitt [EMAIL PROTECTED] To: LEAF Users List [EMAIL PROTECTED] Sent: Friday, December 14, 2001 6:25 PM Subject: Re: [Leaf-user] More questions about Datchstein CD 1.0.2 and pppoe Charles Steinkuehler wrote: - is it possible to change the root ramdisk size and still booting from the CD ?? Yes, but you have to burn a new CD, with a different boot-floppy image. I thought you COULD change it. Hold down the left shift, and at the boot: prompt type linux ramsize=X ...and that should do it (assuming the default kernel label is linux)... Of course, you DO have to type it in... in previous versions of dachstein: ping -c 1 some.dns.name | grep PING | cut -d (): -f 3 returned only the ip address 1.2.3.4 in dachstein cd, the same command returns (1.2.3.4): Any idea ?? The previous cut command was massively broken, and the fact that the above usage worked was an artifact of cut's mis-behavior. Try the above on a 'normal' linux system and you'll get an error...the delimiter for cut must be a single character... Try using sed instead of cut: sed 's/).*//;s/.*(//' How about this (for your entire command line): ping -c 1 some.dns.name | sed -n '/PING/s/.*(\(.*\)):.*/\1/p' ...one sed command, no cut and no grep. ___ 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] Squid package??
Ewald Wasscher wrote: Sergio Morilla wrote: Thanks for the package and the dependecies info!! Just one more question, I would like to move the cache to an HD I have on the computer, is this a paremeter on squid.conf? IIRC it's CacheDirectory. The manual at http://www.squid-cache.org/ will tell you if I was right. You don't have to do that, though, necessarily: Add a line something like this to /etc/fstab: /dev/hda1 /var/spool/cache ext2 defaults 1 2 ...and then: # mkdir /var/spool/cache # squid -z ...and you're all set. Then you just have to make sure that /etc/fstab is restored on boot. ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
RE: [Leaf-user] dachstein cd 1.0.2 modules
Found them. I modified /etc/modules adding 8390 and smc-ultra insmod seems to recognize the 8390.o module but with smc-ultra and all ip_masq modules it displays a message like somemodule - insmod: /lib/modules/2.2.19-3-LEAF-RAID: No such file or directory insmod: somemodule.o: no module by that name found I can´t see why it loads (lsmod shows it) 8390 and does not load the other modules. Any hint Thanks -Mensaje original- De: Charles Steinkuehler [mailto:[EMAIL PROTECTED]] Enviado el: Friday, December 14, 2001 12:56 Para: Sergio Morilla; Leaf-user@lists. sourceforge. net (E-mail) Asunto: Re: [Leaf-user] dachstein cd 1.0.2 modules I´ve just burned dachstein-cd-v1.0.2.iso and made the boot floppy from the image included. When I went to /lib/modules there is no single file. Why? Do I need to load every ip_masq* and net support files from diskette?? Are this files in another .lrp file??? The modules are on the CD. There are now commands to mount a device, and load modules directly from it, rather than having to copy modules into /lib/modules and back them up on your configuration floppy (wasting valuable space). The default /etc/modules configuration file includes the required commands to mount the CD and load modules from it, as well as comments on the newly added ! (bang) commands. 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] LEAF development box, 2.2.19 kernel cannot use old ide hdd ???
I am building a development box with slink. The system is up and functioning; but, now, I need to implement a 2.2.19 kernel. It builds successfully; but, has problems at bootup. The system: Pentium 150 64MB RAM /dev/sda1 - swap /dev/sda2 - / /dev/scd0 - cdrom /dev/hdb1 - /usr/local Under the original slink, *ALL* of this functions properly! My new (2.2.19) kernel properly recognizes everything *except* /dev/hdb1: ``Checking all file systems . . . Parallelizing fsck version 1.12 (9-Jul-98) fsck.ext2: Operation not supported by devices while trying to open /dev/hdb1 /dev/hdb1: The superblock could not be read or does not describe a correct ext2 filesystem ...'' When I do this: e2fsck -b 8193 /dev/hdb1 I get this: ``The superblock could not be read or does not describe a correct ext2 filesystem ...'' I've varied several variables in .config to no avail ; What do you think? -- Best Regards, mds mds resource 888.250.3987 Dare to fix things before they break . . . Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] LEAF development box, 2.2.19 kernel cannot use old ide hdd ???
Michael D. Schleif wrote: Charles Steinkuehler wrote: chopped Looks like everything but IDE is working properly...are you sure you've got the kernel configured properly for IDE support? It's an older ide hdd (quantum lps270), if that matters. Here are what I believe to be pertinent .config sections -- in lieu of the whole thing: # # Block devices # CONFIG_BLK_DEV_FD=y CONFIG_BLK_DEV_IDE=m CONFIG_BLK_DEV_HD_IDE=y CONFIG_BLK_DEV_IDEDISK=m CONFIG_BLK_DEV_IDECD=m CONFIG_BLK_DEV_IDEDISK should probably be y and not m if I recall right. chopped -- Mike Bell [EMAIL PROTECTED] ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] kernal appears to lack KLIPS??
I am running Dachstein with Seawall, and the 1.91 IPSEC with ipsec_masq uncommented. I also have the mawk and ifconfig modules. I keep getting this message when I boot the system.: kernel appears to lack KLIPS I would greatly appreciate it if anyone could give me any clues as to what this message means and how to make it go away. If you want to run FreeS/WAN IPSec on your firewall, you need a kernel with IPSec built-in. The default floppy-disk kernel does not include IPSec to save space, although the default CD kernel does. Get one of the kernels with -IPSec in the name from the Dachstein small, normal, or RAID kernel trees available from my site (or one of the mirrors): http://lrp.steinkuehler.net/files/kernels/ NOTE: The floppy disto uses the small kernel tree by default, so the appropriate kernel w/IPSec included would be: http://lrp.steinkuehler.net/files/kernels/Dachstein-small/linux-2.2.19-3-LEA F-small-IPSec.zImage.upx 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] Datchstein CD 1.0.2 and pppoe
Etienne List: I have similar setup (etho --adsl modem, eth1-internal lan), although booting from floppy (rc2 image) And exactly the same setup below (Except EXTERN_DYNADDR=NO). My internal interface is fine, pings work. I do not get a ppp0 iface generated at boot time. How do you start your pppoe? Where is start_adsl? Thx in advance. RWT Etienne Charlier wrote: 001101c184ba$37a2bc80$[EMAIL PROTECTED]"> Hi, Here are some info about my work with Dachstein cd and pppoe - It seems that ifconfig.lrp is needed by the adsl-* scripts ... Once I figured out I was able to connect quite easily ( great work charles) Now a little question about some variables in thenetwork.conf My setup: eth0 -- adsl model eth1 -- internal lan I can connect with IF_AUTO="eth1" IF_LIST="ppp0 eth1" EXTERN_IF="ppp0" EXTERN_DHCP=NO EXTERN_DYNADDR=YES ???is it correct EXTERN_IP=DYNAMIC Regards, Etienne
Re: [Leaf-user] LEAF development box, 2.2.19 kernel cannotuse old ide hdd ???
Ray Olszewski wrote: At 05:37 PM 12/14/01 -0600, Michael D. Schleif wrote: ... Interestingly, under the kernel that is functioning properly, there is *NO* /proc/ide !?!? ... So, how is this handling the IDE hdd? Is it using scsi to interpret ide? It would be easier to answer this if we know what kernel version was involved. An earlier message mentioned Under the original slink, *ALL* of this functions properly! So I dusted off my old Slink workstation and started it up. My version runs kernel 2.0.36; is that what we are talking about as original? 2.0.38 If so, I match your observation that there is no /proc/ide ... but the changes between kernel 2.0.x and 2.2.x were pretty far-reaching ... contrasted with a Potato workstation running 2.2.19, the /proc pseudo-directory differs in many ways, with many fewer file-style paths into kernel variables than the newer kernels have ... so I wouldn't worry much about this one difference. I'm sure it isn't using scci to interpret ide, since none of my systems include scsi drives or drivers. Nevertheless, the problem remains -- the system does *not* recognize /dev/hdb1. Any ideas how to correct this? -- Best Regards, mds mds resource 888.250.3987 Dare to fix things before they break . . . Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] LEAF development box, 2.2.19 kernel cannotuse old ide hdd ???
At 06:11 PM 12/14/01 -0600, Michael D. Schleif wrote: [...] [irrelevancies about 2.0.x kernels and ogriginal Slink deleted] Nevertheless, the problem remains -- the system does *not* recognize /dev/hdb1. Any ideas how to correct this? Based on what you've posted previously ... I'd second Mike Bell's suggestion, and extend it to recommending these two changes: CONFIG_BLK_DEV_IDE=y CONFIG_BLK_DEV_IDEDISK=y This should suffice to move IDE hard-drive support from modules to the kernel itself. If you don't want to go that route ... I'm used to compiling ide support in, not using modules for it, so I don't actually know what the modules setup looks like. Charles already suggested: Looks like you've got IDE support compiled as a module. Make sure you're loading all the right modules before trying to access the HDD. I didn't see any reply to this suggestion. To that end, you might report -- the output (or the ide-related subset) of lsmod -- the relevant part of /etc/modules -- whether the relevant modules are findable by insmod so someone used to using IDE as modules will be able to note anything that's missing. What is in directory /proc/ide/hdb/ (if it exists)? What is in pseudo-file /proc/ide/hdb/driver (if it exists)? -- Never tell me the odds!--- Ray Olszewski-- Han Solo Palo Alto, CA[EMAIL PROTECTED] ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
[Leaf-user] IP Address
How do you see what your IP addresses are? Ifconfig not on the floppy. Also how do you search Geocrawler? It seems to only be browseable. For example look at this URL http://www.geocrawler.com/lists/3/SourceForge/7325/0/ there is no search method. In the upper right hand corner there is a box that is searching something other than Geocrawler. Type Dachstein and nothing comes up.
RE: [Leaf-user] IP Address
From: Jack Coates How do you see what your IP addresses are? Ifconfig not on the floppy. ip addr pn] You wouldn't happen to know where they buried the equivalent command on a 2.4 (SuSE 7.1) kernel, would ya? --- Peter Nosko _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] ATT transition woes
Gary and Cindy Cote wrote: --- Matt Schalit [EMAIL PROTECTED] wrote: gc wrote: Describe exactly what you did and what you saw, if it's still happeing and the DNS advice you got doesn't fix it. o Downloaded Dachstein 1.0.2 distribution o Loaded it onto a floppy o Selected appropriate modules for my NIC cards in /etc/modules (8390 and ne2k) Do either of these need pci-scan? I'm not looking at the deps file right now, so I'm just curios. o Commented out the masq_quake module o Tried to enable a serial port console in /etc/inittab (which didn't work, btw, but i'll figure that out some other day) o Backed up /etc o Added a send host-name line to dhclient.conf I didn't have to do that. Why don't you leave it commented out for now. It may be sending an invalid string. o Backed up dhclient o Rebooted o Observed the DHCP sequence go through successfully o Examined IP address and routing table. Nothing apparently out of the ordinary. o The 'ip route' command showed an entry that said something like this: 11.22.33.44/28 ... src 22.33.44.55 o I could not ping 11.22.33.44 (what I believe should be my next hop router, yes?) o I could ping 22.33.44.55 o I could not ping any other nodes (Sorry I don't have exact IP addresses. I'm at work at the moment. I can supply them tonight if it would be helpful) Yes those will be necessary. We'll need to see the relevant portion of dmesg and the entire output of ip addr show ip route show If I hook my win2k box directly to the cable modem, everything works fine. Yea yea. And if I suck Bill's cock, he might let me drink from the river of wealth. Now, now...that wasn't a jab...i was simply making the point that the problem appears to be on my end. I can not believe I posted that. For the love of Pete! You didn't do anything wrong at all. Just so you know, it's common to get a new IP address an whatnot when you switch systems (and thus mac addresses) and get a new lease. I didn't have to touch a single dhcp setting to get my friend's attbi.com system in Petaluma, CA to work. That gives me an idea. I know someone who had a problem when they unplugged their old computer from the cable modem and plugged a new one in. Turned out the system 'remembered' their MAC address and would only give them one IP address (in that case, though, DHCP was failing). The technician told them to power down the modem for five minutes and that cleared it up. I don't fully understand why, but there it is. modem for five minutes. I'm not sure why that seemed You're post cut off there, but the computer nics and routers communicate by the hardware mac addresses burned into the card, and the ip addresses are just numbers we assign. When you release the lease, you clear out the mac addy to ip addy mapping. I was going to recommend that you use your windows box to release the lease, but then I remembered you had only Linux, so I erased it. I don't know how to release the lease on Linux. Good Luck, Matthew ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] ATT transition woes
David Douthitt wrote: [snip] It would be nice to know what happened. However, I've been using the current pre-release version of Oxygen with DHCP routinely - especially since I don't have to configure it :) It works just fine. We tried Oxygen-120801. It just froze during boot right after loading the dhcp program and attempting to get an ip address, which it said it got. He doesn't want to take down his router to test out 12/11, though, because he has work to do. Sorry. Matthew ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] LEAF development box, 2.2.19 kernel cannotuse old ide hdd ???
I'm fishing a bit at this point, Michael. The thing not indicated in your snips from the .config file for the *failing* sustem is IDE chipset support. For *example*, my (working) 2.2.x kernel includes these .config lines: CONFIG_BLK_DEV_CMD640=y # CONFIG_BLK_DEV_CMD640_ENHANCED is not set CONFIG_BLK_DEV_RZ1000=y These (there are many others too) are characterized in the menuconfig frontend as loading bugfix code for various IDE chipsets, and I think the specific two I list above come as =y out of the box with kernel source. I cannot tell from what you posted if your system uses either one of these problem chipsets or one of the other chipset possibilities shown in menuconfig (or, for that matter, if you have these lines in .config). But you might try exploring in this area. At 10:35 PM 12/14/01 -0600, Michael D. Schleif wrote: [a lot of detail omitted here] -- Never tell me the odds!--- Ray Olszewski-- Han Solo Palo Alto, CA[EMAIL PROTECTED] ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
