Re: Linksys WPC11 -- orinoco or prism2?
Hi Hugh, - Original message follows- Hugh Saunders >> Where do you have your WEP config settings stored? > > In /etc/wlan.conf I have SSID_wlan0="stokerec" > Then i store my wep settings in /etc/wlan/wlancfg-stokerec Hrm, which version of Debian are you running? (I've got a /etc/wlan/wlan.conf, but no /etc/wlan.conf). > note: i do not want comments about the stupidness of publishing wepkeys. > > [EMAIL PROTECTED]:/etc/wlan$ cat wlancfg-stokerec That helped a great deal -- thank you. But for some reason, I still can't get my NIC to come up. From what I've read and done, I've rebuilt my kernel (now 2.4.21) WITHOUT pcmcia support (General setup -> PCMCIA/CardBus support), and YES to "Network device support -> Wireless LAN (non-hamradio) -> Wireless LAN (non-hamradio), Hermes chipset 802.11b support (Orinoco/Prism2/Symbol)" and have built pcmcia-cs-3.2.4 and linux-wlan-ng-0.2.1-pre8 from their respective sources. Do you have anything in your /etc/modules about your 'wlan0' interface or any of the modules for that NIC? Also, what do you have for the *WPC* stanzas in your /etc/pcmcia/config? Mine has "bind "orinoco_cs"" on both so that driver gets loaded by default.And if you could include the output of an 'lsmod' and 'cardctl ident' on your box, I would really appreciate it. Thank you again for all of your help, -Charlie
Re: Linksys WPC11 -- orinoco or prism2?
On Sun, Jun 15, 2003 at 11:34:50PM -0700, [EMAIL PROTECTED] wrote: > Hrm, which version of Debian are you running? (I've got a > /etc/wlan/wlan.conf, but no /etc/wlan.conf). sorry typo. [thinko maybe?] if it helps, unstable :D > But for some reason, I still can't get my NIC to come up. From what I've > read and done, I've rebuilt my kernel (now 2.4.21) WITHOUT pcmcia support > (General setup -> PCMCIA/CardBus support), and YES to "Network device > support -> Wireless LAN (non-hamradio) -> Wireless LAN (non-hamradio), > Hermes chipset 802.11b support (Orinoco/Prism2/Symbol)" and have built > pcmcia-cs-3.2.4 and linux-wlan-ng-0.2.1-pre8 from their respective > sources. works for me with the kernel pcmica stuff. [2.4.21] But.. i have never got the wireless nic to come up automatically. Prob cause i havent bothered to learn how to put the wireless stuff in /etc/network/interfaces [path maybe wrong, from the top of my head ;-) ] That is one thing that sucks about the wlan-ng stuff, no wireless extensions :( i use a nasty script, bad way of doing things but works #!/bin/sh /etc/pcmcia/wlan-ng start wlan0 ifconfig wlan0 inet 192.168.0.10 up route del default route add default gw 192.168.0.1 > Do you have anything in your /etc/modules about your 'wlan0' interface or > any of the modules for that NIC? Also, what do you have for the *WPC* > stanzas in your /etc/pcmcia/config? card "Linksys WPC11 11Mbps 802.11b WLAN Card" version "Instant Wireless ", " Network PC CARD", "Version 01.02" bind "orinoco_cs" funny that, cause i dont use the orinoco drivers! [EMAIL PROTECTED]:/home/hugh$ lsmod Module Size Used byTainted: P lt_serial 17620 2 vfat 10796 1 (autoclean) fat31736 0 (autoclean) [vfat] cipher-rc6 10036 1 cryptoloop 1948 1 cryptoapi 4236 5 [cipher-rc6 cryptoloop] loop9656 3 [cryptoloop] lt_modem 472155 0 [lt_serial] smbfs 38928 1 smapi 3152 0 thinkpad2436 0 [smapi] i810_audio 24508 1 prism2_cs 66128 2 p80211 19168 0 [prism2_cs] > if you could include the output of an 'lsmod' done :) > and 'cardctl ident' on your box, I would really appreciate it. [EMAIL PROTECTED]:/home/hugh$ cardctl ident 0 Socket 0: product info: "The Linksys Group, Inc.", "Instant Wireless Network PC Card", "ISL37300P", "RevA" manfid: 0x0274, 0x1613 function: 6 (network) hope that helps, -- hugh
unsubscribe
beeps!!
today i boot up my computer (dell inspiron 8000), having successfully installed debian on it friday afternoon, and now it beeps at me, sporadically, and in three octaves! same note (D i think); different register. i can't isolate what's causing it -- i'm plugged in, so it shouldn't be a battery issue ... this has never happened to me before! what is it? thanks, -- .~. nori @ sccs.swarthmore.edu /V\ http://www.sccs.swarthmore.edu/~nori/jnl/ // \\ @ maenad.net /( )\ www.maenad.net ^`~'^ get my (*new*) key here: http://www.maenad.net/geek/gpg/7ede5499.asc (please *remove* old key 11e031f1!)
Re: IBM X30 hibernation problem
> "WW" == Wei Wang <[EMAIL PROTECTED]> writes: WW> Please note that hda4 is the partition I created for WW> hibernation. Strangely although it is physically right WW> after the first partition, it's ordered as hda4. And the WW> last physical parititon, the IBM recover hidden WW> partition, is ordered as hda2. Same here on my X22. WW> A file is created: C:\SAVE2DSK.BIN WW> But in Windows, I can see the file created resides in drive O(hda6). >From within linux, mount /dev/hda6 and /dev/hda2 and "mv" the file to the _primary_ FAT16 partition /dev/hda2 where you wanted it to be. (Is /dev/hda2 big enough it?) WW> So did I miss anything for the hibernation? I looked WW> into the BIOS and didn't find anything related. I think it must be on a primary partition. (In my case, I also moved the save2dsk.bin around by hand, because the IBM utility put in on a _large_ primary FAT partition instead of the small one that I created for it. With the large one, it simply took the BIOS too long a time to find and use it.) == Uwe ==
Re: beeps!!
On Mon, 2003-06-16 at 08:58, Nori Heikkinen wrote: > today i boot up my computer (dell inspiron 8000), having successfully > installed debian on it friday afternoon, and now it beeps at me, > sporadically, and in three octaves! same note (D i think); different > register. i can't isolate what's causing it -- i'm plugged in, so it > shouldn't be a battery issue ... this has never happened to me before! > what is it? Could you elaborate a bit on when the beeping happens? Also, assuming that it's a hardware issue, which version of the BIOS is on there? I've been running Debian on my i8k for a year and half with no problems. -- Alex Malinovich Support Free Software, delete your Windows partition TODAY! Encrypted mail preferred. You can get my public key from any of the pgp.net keyservers. Key ID: A6D24837 signature.asc Description: This is a digitally signed message part
can't bring up eth0 correctly
I just went through my woody install on Inspiron 8200. On the initial installation, it gets its ip via dhcp. All good. I did an apt-get for the 2.4-18 kernel, recompiled it with some changes, restart and no more. On ifconfig I see lo and eth0, but I don’t get anything. In /etc/interfaces I have auto eth0 commented out and eth0 set for dhcp. If I manually try to assign the numbers it seems like it takes it. But when I add route gateway, I get that there is no such device. Any suggestions? I didn’t see netenv helping much, so I removed it from startup as well. Thanks, Charles
Re: can't bring up eth0 correctly
charles yoo wrote: I just went through my woody install on Inspiron 8200. On the initial installation, it gets its ip via dhcp. All good. I did an apt-get for the 2.4-18 kernel, recompiled it with some changes, restart and no more. On ifconfig I see lo and eth0, but I don’t get anything. In /etc/interfaces I have auto eth0 commented out and eth0 set for dhcp. Shouldn't that be "/etc/network/interfaces"? I'm a little confused about what you are trying to do, and what exactly is failing. The line "auto eth0" that you commented out is the line that causes the interface to be configured on boot. It is quite common to not want the interface to be configured on boot for a laptop. However, if you remove the 'auto' entry, you need manually bring up the interface using 'ifup eth0'. Have you tried doing that? If I manually try to assign the numbers it seems like it takes it. But when I add route gateway, I get that there is no such device. Did you bring up the interface after setting the address? Presumably you are using ifconfig to set the address. Try "ifconfig eth0 up". Any suggestions? Your /etc/network/interfaces file should look something like this: #auto eth0 iface eth0 inet dhcp You should then bring up the interface by doing: ifup eth0 If the interface fails to come up, check your system logs for error messages. I think you might need to post a bit more information before anyone can be any more specific with an answer. What is the network chip? Is it pcmcia/pccard or internal? What are the contents of your /etc/network/interfaces What commands are you using to set the IP address? What error message are you getting when you try to set the default route? What related error messages are you seeing in your syslog? What dhcp client do you have installed? -- jason
RE: can't bring up eth0 correctly
I should have written /etc/network/interfaces. In reading a few things on the net, a lot of people suggested to have the autho eth0 commented out. This is for a laptop. I'm coming from redhat, and once dhcp is set, you can more or less leave it that way. All that I'm trying to do at the moment is get eth0 up and running. I get alerts saying that there is no such process or device. When I restart networking, I expect to see eth0 come up, but it doesn't. In /etc/network/interfaces, I have the following information I am basically looking to configure for dhcp only. I have removed netenv, because it did not seem to work too well for me. Maybe misconfigured. -Original Message- From: Jason Kraftcheck [mailto:[EMAIL PROTECTED] Sent: Monday, June 16, 2003 5:49 PM To: [EMAIL PROTECTED] Cc: debian-laptop@lists.debian.org Subject: Re: can't bring up eth0 correctly charles yoo wrote: > I just went through my woody install on Inspiron 8200. On the initial > installation, it gets its ip via dhcp. All good. I did an apt-get for > the 2.4-18 kernel, recompiled it with some changes, restart and no > more. On ifconfig I see lo and eth0, but I don't get anything. > > > > In /etc/interfaces I have auto eth0 commented out and eth0 set for dhcp. > > Shouldn't that be "/etc/network/interfaces"? I'm a little confused about what you are trying to do, and what exactly is failing. The line "auto eth0" that you commented out is the line that causes the interface to be configured on boot. It is quite common to not want the interface to be configured on boot for a laptop. However, if you remove the 'auto' entry, you need manually bring up the interface using 'ifup eth0'. Have you tried doing that? > > If I manually try to assign the numbers it seems like it takes it. But > when I add route gateway, I get that there is no such device. > Did you bring up the interface after setting the address? Presumably you are using ifconfig to set the address. Try "ifconfig eth0 up". > > > Any suggestions? > > Your /etc/network/interfaces file should look something like this: #auto eth0 iface eth0 inet dhcp You should then bring up the interface by doing: ifup eth0 If the interface fails to come up, check your system logs for error messages. I think you might need to post a bit more information before anyone can be any more specific with an answer. What is the network chip? Is it pcmcia/pccard or internal? What are the contents of your /etc/network/interfaces What commands are you using to set the IP address? What error message are you getting when you try to set the default route? What related error messages are you seeing in your syslog? What dhcp client do you have installed? -- jason
Re: can't bring up eth0 correctly
charles yoo wrote: I should have written /etc/network/interfaces. In reading a few things on the net, a lot of people suggested to have the autho eth0 commented out. This is for a laptop. I'm coming from redhat, and once dhcp is set, you can more or less leave it that way. All that I'm trying to do at the moment is get eth0 up and running. I get alerts saying that there is no such process or device. When I restart networking, I expect to see eth0 come up, but it doesn't. Please read more carefully what I wrote below. If you comment out the 'auto eth0' entry, eth0 will not come up when you restart networking. Try 'ifup eth0' to manually bring up the interface. In /etc/network/interfaces, I have the following information I am basically looking to configure for dhcp only. I have removed netenv, because it did not seem to work too well for me. Maybe misconfigured. Please consider including the additinion information I listed in my first message, as it will make it easier for others to help you. (And please include the actual contents of your /etc/network/interfaces rather than your summary of the contents.) -- jason
Re: can't bring up eth0 correctly
"charles" == charles yoo <[EMAIL PROTECTED]> writes: charles> I should have written /etc/network/interfaces. In charles> reading a few things on the net, a lot of people charles> suggested to have the autho eth0 commented out. This is charles> for a laptop. I'm coming from redhat, and once dhcp is charles> set, you can more or less leave it that way. And so it is on Debian, but you need some additinal packages for the laptop case where you plug/unplug cables frequently. charles> All that I'm trying to do at the moment is get eth0 up charles> and running. I get alerts saying that there is no such charles> process or device. Hmmyou are confusing issues here. Does 'ifup eth0' bring up your ethernet device with a valid dhcp address or not? If not, your problem is probably from recompiling your kernel and not including (a) the correct driver or (b) not setting the packet filter options (this is not redhat, so you use ISC DHCP unless you installed pump, by default). charles> When I restart networking, I expect to see eth0 come up, charles> but it doesn't. That is as it should, because you commented out the 'auto eth0' line. charles> In /etc/network/interfaces, I have the following charles> information charles> I am basically looking to configure for dhcp only. I charles> have removed netenv, because it did not seem to work too charles> well for me. Maybe misconfigured. Just add back the 'auto eth0' - removing it makes sense for PCMCIA ethernet cards - and install laptop-net to ensure that dhcp does not hang when you boot without a cable in the ethernet socket. Cheers! Shyamal charles> -Original Message- From: Jason Kraftcheck charles> [mailto:[EMAIL PROTECTED] Sent: Monday, June 16, charles> 2003 5:49 PM To: [EMAIL PROTECTED] Cc: charles> debian-laptop@lists.debian.org Subject: Re: can't bring charles> up eth0 correctly charles> charles yoo wrote: >> I just went through my woody install on Inspiron 8200. On the >> initial installation, it gets its ip via dhcp. All good. I >> did an apt-get for the 2.4-18 kernel, recompiled it with some >> changes, restart and no more. On ifconfig I see lo and eth0, >> but I don't get anything. >> >> >> >> In /etc/interfaces I have auto eth0 commented out and eth0 set >> for dhcp. >> >> charles> Shouldn't that be "/etc/network/interfaces"? charles> I'm a little confused about what you are trying to do, charles> and what exactly is failing. The line "auto eth0" that charles> you commented out is the line that causes the interface charles> to be configured on boot. It is quite common to not want charles> the interface to be configured on boot for a laptop. charles> However, if you remove the 'auto' entry, you need charles> manually bring up the interface using 'ifup eth0'. Have charles> you tried doing that? >> If I manually try to assign the numbers it seems like it takes >> it. But when I add route gateway, I get that there is no such >> device. >> charles> Did you bring up the interface after setting the address? charles> Presumably you are using ifconfig to set the address. charles> Try "ifconfig eth0 up". >> >> >> Any suggestions? >> >> charles> Your /etc/network/interfaces file should look something charles> like this: charles> #auto eth0 iface eth0 inet dhcp charles> You should then bring up the interface by doing: ifup charles> eth0 charles> If the interface fails to come up, check your system logs charles> for error messages. charles> I think you might need to post a bit more information charles> before anyone can be any more specific with an answer. charles> What is the network chip? Is it pcmcia/pccard or charles> internal? What are the contents of your charles> /etc/network/interfaces What commands are you using to charles> set the IP address? What error message are you getting charles> when you try to set the default route? What related charles> error messages are you seeing in your syslog? What dhcp charles> client do you have installed? charles> -- jason charles> -- To UNSUBSCRIBE, email to charles> [EMAIL PROTECTED] with a subject of charles> "unsubscribe". Trouble? Contact charles> [EMAIL PROTECTED]
Re: Linksys WPC11 -- orinoco or prism2?
On Sun, Jun 15, 2003 at 11:34:50PM -0700, [EMAIL PROTECTED] wrote: > Hrm, which version of Debian are you running? (I've got a > /etc/wlan/wlan.conf, but no /etc/wlan.conf). sorry typo. [thinko maybe?] if it helps, unstable :D > But for some reason, I still can't get my NIC to come up. From what I've > read and done, I've rebuilt my kernel (now 2.4.21) WITHOUT pcmcia support > (General setup -> PCMCIA/CardBus support), and YES to "Network device > support -> Wireless LAN (non-hamradio) -> Wireless LAN (non-hamradio), > Hermes chipset 802.11b support (Orinoco/Prism2/Symbol)" and have built > pcmcia-cs-3.2.4 and linux-wlan-ng-0.2.1-pre8 from their respective > sources. works for me with the kernel pcmica stuff. [2.4.21] But.. i have never got the wireless nic to come up automatically. Prob cause i havent bothered to learn how to put the wireless stuff in /etc/network/interfaces [path maybe wrong, from the top of my head ;-) ] That is one thing that sucks about the wlan-ng stuff, no wireless extensions :( i use a nasty script, bad way of doing things but works #!/bin/sh /etc/pcmcia/wlan-ng start wlan0 ifconfig wlan0 inet 192.168.0.10 up route del default route add default gw 192.168.0.1 > Do you have anything in your /etc/modules about your 'wlan0' interface or > any of the modules for that NIC? Also, what do you have for the *WPC* > stanzas in your /etc/pcmcia/config? card "Linksys WPC11 11Mbps 802.11b WLAN Card" version "Instant Wireless ", " Network PC CARD", "Version 01.02" bind "orinoco_cs" funny that, cause i dont use the orinoco drivers! [EMAIL PROTECTED]:/home/hugh$ lsmod Module Size Used byTainted: P lt_serial 17620 2 vfat 10796 1 (autoclean) fat31736 0 (autoclean) [vfat] cipher-rc6 10036 1 cryptoloop 1948 1 cryptoapi 4236 5 [cipher-rc6 cryptoloop] loop9656 3 [cryptoloop] lt_modem 472155 0 [lt_serial] smbfs 38928 1 smapi 3152 0 thinkpad2436 0 [smapi] i810_audio 24508 1 prism2_cs 66128 2 p80211 19168 0 [prism2_cs] > if you could include the output of an 'lsmod' done :) > and 'cardctl ident' on your box, I would really appreciate it. [EMAIL PROTECTED]:/home/hugh$ cardctl ident 0 Socket 0: product info: "The Linksys Group, Inc.", "Instant Wireless Network PC Card", "ISL37300P", "RevA" manfid: 0x0274, 0x1613 function: 6 (network) hope that helps, -- hugh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
unsubscribe
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
beeps!!
today i boot up my computer (dell inspiron 8000), having successfully installed debian on it friday afternoon, and now it beeps at me, sporadically, and in three octaves! same note (D i think); different register. i can't isolate what's causing it -- i'm plugged in, so it shouldn't be a battery issue ... this has never happened to me before! what is it? thanks, -- .~. nori @ sccs.swarthmore.edu /V\ http://www.sccs.swarthmore.edu/~nori/jnl/ // \\ @ maenad.net /( )\ www.maenad.net ^`~'^ get my (*new*) key here: http://www.maenad.net/geek/gpg/7ede5499.asc (please *remove* old key 11e031f1!) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: IBM X30 hibernation problem
> "WW" == Wei Wang <[EMAIL PROTECTED]> writes: WW> Please note that hda4 is the partition I created for WW> hibernation. Strangely although it is physically right WW> after the first partition, it's ordered as hda4. And the WW> last physical parititon, the IBM recover hidden WW> partition, is ordered as hda2. Same here on my X22. WW> A file is created: C:\SAVE2DSK.BIN WW> But in Windows, I can see the file created resides in drive O(hda6). >From within linux, mount /dev/hda6 and /dev/hda2 and "mv" the file to the _primary_ FAT16 partition /dev/hda2 where you wanted it to be. (Is /dev/hda2 big enough it?) WW> So did I miss anything for the hibernation? I looked WW> into the BIOS and didn't find anything related. I think it must be on a primary partition. (In my case, I also moved the save2dsk.bin around by hand, because the IBM utility put in on a _large_ primary FAT partition instead of the small one that I created for it. With the large one, it simply took the BIOS too long a time to find and use it.) == Uwe == -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: beeps!!
On Mon, 2003-06-16 at 08:58, Nori Heikkinen wrote: > today i boot up my computer (dell inspiron 8000), having successfully > installed debian on it friday afternoon, and now it beeps at me, > sporadically, and in three octaves! same note (D i think); different > register. i can't isolate what's causing it -- i'm plugged in, so it > shouldn't be a battery issue ... this has never happened to me before! > what is it? Could you elaborate a bit on when the beeping happens? Also, assuming that it's a hardware issue, which version of the BIOS is on there? I've been running Debian on my i8k for a year and half with no problems. -- Alex Malinovich Support Free Software, delete your Windows partition TODAY! Encrypted mail preferred. You can get my public key from any of the pgp.net keyservers. Key ID: A6D24837 signature.asc Description: This is a digitally signed message part
can't bring up eth0 correctly
I just went through my woody install on Inspiron 8200. On the initial installation, it gets its ip via dhcp. All good. I did an apt-get for the 2.4-18 kernel, recompiled it with some changes, restart and no more. On ifconfig I see lo and eth0, but I don’t get anything. In /etc/interfaces I have auto eth0 commented out and eth0 set for dhcp. If I manually try to assign the numbers it seems like it takes it. But when I add route gateway, I get that there is no such device. Any suggestions? I didn’t see netenv helping much, so I removed it from startup as well. Thanks, Charles
Re: can't bring up eth0 correctly
charles yoo wrote: I just went through my woody install on Inspiron 8200. On the initial installation, it gets its ip via dhcp. All good. I did an apt-get for the 2.4-18 kernel, recompiled it with some changes, restart and no more. On ifconfig I see lo and eth0, but I don’t get anything. In /etc/interfaces I have auto eth0 commented out and eth0 set for dhcp. Shouldn't that be "/etc/network/interfaces"? I'm a little confused about what you are trying to do, and what exactly is failing. The line "auto eth0" that you commented out is the line that causes the interface to be configured on boot. It is quite common to not want the interface to be configured on boot for a laptop. However, if you remove the 'auto' entry, you need manually bring up the interface using 'ifup eth0'. Have you tried doing that? If I manually try to assign the numbers it seems like it takes it. But when I add route gateway, I get that there is no such device. Did you bring up the interface after setting the address? Presumably you are using ifconfig to set the address. Try "ifconfig eth0 up". Any suggestions? Your /etc/network/interfaces file should look something like this: #auto eth0 iface eth0 inet dhcp You should then bring up the interface by doing: ifup eth0 If the interface fails to come up, check your system logs for error messages. I think you might need to post a bit more information before anyone can be any more specific with an answer. What is the network chip? Is it pcmcia/pccard or internal? What are the contents of your /etc/network/interfaces What commands are you using to set the IP address? What error message are you getting when you try to set the default route? What related error messages are you seeing in your syslog? What dhcp client do you have installed? -- jason -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: can't bring up eth0 correctly
I should have written /etc/network/interfaces. In reading a few things on the net, a lot of people suggested to have the autho eth0 commented out. This is for a laptop. I'm coming from redhat, and once dhcp is set, you can more or less leave it that way. All that I'm trying to do at the moment is get eth0 up and running. I get alerts saying that there is no such process or device. When I restart networking, I expect to see eth0 come up, but it doesn't. In /etc/network/interfaces, I have the following information I am basically looking to configure for dhcp only. I have removed netenv, because it did not seem to work too well for me. Maybe misconfigured. -Original Message- From: Jason Kraftcheck [mailto:[EMAIL PROTECTED] Sent: Monday, June 16, 2003 5:49 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: can't bring up eth0 correctly charles yoo wrote: > I just went through my woody install on Inspiron 8200. On the initial > installation, it gets its ip via dhcp. All good. I did an apt-get for > the 2.4-18 kernel, recompiled it with some changes, restart and no > more. On ifconfig I see lo and eth0, but I don't get anything. > > > > In /etc/interfaces I have auto eth0 commented out and eth0 set for dhcp. > > Shouldn't that be "/etc/network/interfaces"? I'm a little confused about what you are trying to do, and what exactly is failing. The line "auto eth0" that you commented out is the line that causes the interface to be configured on boot. It is quite common to not want the interface to be configured on boot for a laptop. However, if you remove the 'auto' entry, you need manually bring up the interface using 'ifup eth0'. Have you tried doing that? > > If I manually try to assign the numbers it seems like it takes it. But > when I add route gateway, I get that there is no such device. > Did you bring up the interface after setting the address? Presumably you are using ifconfig to set the address. Try "ifconfig eth0 up". > > > Any suggestions? > > Your /etc/network/interfaces file should look something like this: #auto eth0 iface eth0 inet dhcp You should then bring up the interface by doing: ifup eth0 If the interface fails to come up, check your system logs for error messages. I think you might need to post a bit more information before anyone can be any more specific with an answer. What is the network chip? Is it pcmcia/pccard or internal? What are the contents of your /etc/network/interfaces What commands are you using to set the IP address? What error message are you getting when you try to set the default route? What related error messages are you seeing in your syslog? What dhcp client do you have installed? -- jason -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: can't bring up eth0 correctly
charles yoo wrote: I should have written /etc/network/interfaces. In reading a few things on the net, a lot of people suggested to have the autho eth0 commented out. This is for a laptop. I'm coming from redhat, and once dhcp is set, you can more or less leave it that way. All that I'm trying to do at the moment is get eth0 up and running. I get alerts saying that there is no such process or device. When I restart networking, I expect to see eth0 come up, but it doesn't. Please read more carefully what I wrote below. If you comment out the 'auto eth0' entry, eth0 will not come up when you restart networking. Try 'ifup eth0' to manually bring up the interface. In /etc/network/interfaces, I have the following information I am basically looking to configure for dhcp only. I have removed netenv, because it did not seem to work too well for me. Maybe misconfigured. Please consider including the additinion information I listed in my first message, as it will make it easier for others to help you. (And please include the actual contents of your /etc/network/interfaces rather than your summary of the contents.) -- jason -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: can't bring up eth0 correctly
"charles" == charles yoo <[EMAIL PROTECTED]> writes: charles> I should have written /etc/network/interfaces. In charles> reading a few things on the net, a lot of people charles> suggested to have the autho eth0 commented out. This is charles> for a laptop. I'm coming from redhat, and once dhcp is charles> set, you can more or less leave it that way. And so it is on Debian, but you need some additinal packages for the laptop case where you plug/unplug cables frequently. charles> All that I'm trying to do at the moment is get eth0 up charles> and running. I get alerts saying that there is no such charles> process or device. Hmmyou are confusing issues here. Does 'ifup eth0' bring up your ethernet device with a valid dhcp address or not? If not, your problem is probably from recompiling your kernel and not including (a) the correct driver or (b) not setting the packet filter options (this is not redhat, so you use ISC DHCP unless you installed pump, by default). charles> When I restart networking, I expect to see eth0 come up, charles> but it doesn't. That is as it should, because you commented out the 'auto eth0' line. charles> In /etc/network/interfaces, I have the following charles> information charles> I am basically looking to configure for dhcp only. I charles> have removed netenv, because it did not seem to work too charles> well for me. Maybe misconfigured. Just add back the 'auto eth0' - removing it makes sense for PCMCIA ethernet cards - and install laptop-net to ensure that dhcp does not hang when you boot without a cable in the ethernet socket. Cheers! Shyamal charles> -Original Message- From: Jason Kraftcheck charles> [mailto:[EMAIL PROTECTED] Sent: Monday, June 16, charles> 2003 5:49 PM To: [EMAIL PROTECTED] Cc: charles> [EMAIL PROTECTED] Subject: Re: can't bring charles> up eth0 correctly charles> charles yoo wrote: >> I just went through my woody install on Inspiron 8200. On the >> initial installation, it gets its ip via dhcp. All good. I >> did an apt-get for the 2.4-18 kernel, recompiled it with some >> changes, restart and no more. On ifconfig I see lo and eth0, >> but I don't get anything. >> >> >> >> In /etc/interfaces I have auto eth0 commented out and eth0 set >> for dhcp. >> >> charles> Shouldn't that be "/etc/network/interfaces"? charles> I'm a little confused about what you are trying to do, charles> and what exactly is failing. The line "auto eth0" that charles> you commented out is the line that causes the interface charles> to be configured on boot. It is quite common to not want charles> the interface to be configured on boot for a laptop. charles> However, if you remove the 'auto' entry, you need charles> manually bring up the interface using 'ifup eth0'. Have charles> you tried doing that? >> If I manually try to assign the numbers it seems like it takes >> it. But when I add route gateway, I get that there is no such >> device. >> charles> Did you bring up the interface after setting the address? charles> Presumably you are using ifconfig to set the address. charles> Try "ifconfig eth0 up". >> >> >> Any suggestions? >> >> charles> Your /etc/network/interfaces file should look something charles> like this: charles> #auto eth0 iface eth0 inet dhcp charles> You should then bring up the interface by doing: ifup charles> eth0 charles> If the interface fails to come up, check your system logs charles> for error messages. charles> I think you might need to post a bit more information charles> before anyone can be any more specific with an answer. charles> What is the network chip? Is it pcmcia/pccard or charles> internal? What are the contents of your charles> /etc/network/interfaces What commands are you using to charles> set the IP address? What error message are you getting charles> when you try to set the default route? What related charles> error messages are you seeing in your syslog? What dhcp charles> client do you have installed? charles> -- jason charles> -- To UNSUBSCRIBE, email to charles> [EMAIL PROTECTED] with a subject of charles> "unsubscribe". Trouble? Contact charles> [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
