Re: What is SIOCSIFFLAGS, and when will he be back?
On Mon, 17 Jul 2000, Raymond L. Zarling wrote: Yes, I have booted linux both from a cold start and after running windows, with no difference. But I guess that indicates some kind of Plug and Play problem. I don't think that's what's going on in my case, since the dmesg output (recorded below) says to me that the kernal is talking to the card just fine. Does anyone, please, know how I could research this problem farther? Prove, for instance, whether it is or is not a Plug and Play problem? I have had a similar problem (though it DID fix with soft booting). I have browsed through the drivers source (I think it was kernel 2.2.15?). What I have found is that the card and the driver have poor media autosensing. The log shows you are trying to autosense. Also, on a 3com card (its driver's author is the same) I had some headaches, for the card seemed PnP, but it lied (you had to programme its parameters via 3c5x9setup). I suggest that you should look for a tool like 3c5x9 for your card and try programming its IRQ and I/O settings to those autodetected by the driver, also don't rely on the driver's autosensing. --Ray [EMAIL PROTECTED] ** dmesg ** Linux version 2.2.12 ([EMAIL PROTECTED]) (gcc version 2.7.2.3) #2 Thu Aug 26 11:46:26 PDT 1999 ... tulip.c:v0.91g 7/16/99 [EMAIL PROTECTED] eth0: Digital DS21143 Tulip rev 65 at 0x6100, 00:C0:F0:3B:F7:91, IRQ 0. eth0: EEPROM default media type Autosense. eth0: Index #0 - Media MII (#11) described by a 21142 MII PHY (3) block. eth0: MII transceiver #1 config 3000 status 7829 advertising 01e1. ** ifconfig -a ** eth0 Link encap:Ethernet HWaddr 00:C0:F0:3B:F7:91 inet addr:192.168.1.13 Bcast:192.168.1.255 Mask:255.255.255.0 BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Base address:0x6100 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:3924 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 ** lsmod ** Module Size Used by nls_cp437 3548 1 (autoclean) tulip 29060 0 (unused) serial 18412 1 parport 6600 0 (unused) vfat8972 1 umsdos 22768 0 (unused) Hopefully helpful, Pavel
Re: What is SIOCSIFFLAGS, and when will he be back?
I have a Linksys LNE100TX, also tulip driver, and get the same error if I reboot from Windows into Linux. Problem is fixed if I start Linux from a cold boot as opposed to restarting from windows. Have you tried this? - Colin McMillen On Sun, Jul 16, 2000 at 03:36:24PM -0700, Raymond L. Zarling wrote: Linux has stopped talking to my ethernet card (Kingston KNE100TX, tulip driver). The probem seems to be in ifconfig, which reports: SIOCSIFFLAGS: Resource temporarily unavailable I run a dual boot system, and it works fine from Windoze 98. It used to run, some weeks ago, in Linux too, but I neglected Linux for a few weeks, and when I tried it now again--this! I honestly don't remember changing anything in the interim; I certainly haven't opened the computer case. Since I don't know what SIOCSIFFLAGS are, I'm completely stumped about where to look next. Short of clearing the disk and reinstalling everything, but that's one of the things I was hoping Linux would save me from. As shown below, the tulip driver doesn't seem to be complaining, and ifconfig has all the right IP addresses and routes. Any ideas what's going on here? Thanks! --Ray [EMAIL PROTECTED] ** dmesg ** Linux version 2.2.12 ([EMAIL PROTECTED]) (gcc version 2.7.2.3) #2 Thu Aug 26 11:46:26 PDT 1999 ... tulip.c:v0.91g 7/16/99 [EMAIL PROTECTED] eth0: Digital DS21143 Tulip rev 65 at 0x6100, 00:C0:F0:3B:F7:91, IRQ 0. eth0: EEPROM default media type Autosense. eth0: Index #0 - Media MII (#11) described by a 21142 MII PHY (3) block. eth0: MII transceiver #1 config 3000 status 7829 advertising 01e1. ** ifconfig -a ** eth0 Link encap:Ethernet HWaddr 00:C0:F0:3B:F7:91 inet addr:192.168.1.13 Bcast:192.168.1.255 Mask:255.255.255.0 BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Base address:0x6100 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:3924 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 ** lsmod ** Module Size Used by nls_cp437 3548 1 (autoclean) tulip 29060 0 (unused) serial 18412 1 parport 6600 0 (unused) vfat8972 1 umsdos 22768 0 (unused) -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- 1. Start Also Sprach Zarathustra by Richard Strauss on your CD player. 2. At the climax of the Sunrise section -- just before the cymbal crash on the C-major chord -- try to ping the first machine by IP address. 3. If it works... congratulations! Your intranet is now up and running. - From _The Linux Network_, Fred Butzen Christopher Hilton
Re: What is SIOCSIFFLAGS, and when will he be back?
Yes, I have booted linux both from a cold start and after running windows, with no difference. But I guess that indicates some kind of Plug and Play problem. I don't think that's what's going on in my case, since the dmesg output (recorded below) says to me that the kernal is talking to the card just fine. Does anyone, please, know how I could research this problem farther? Prove, for instance, whether it is or is not a Plug and Play problem? --Ray On 16-Jul-00, you wrote: I have a Linksys LNE100TX, also tulip driver, and get the same error if I reboot from Windows into Linux. Problem is fixed if I start Linux from a cold boot as opposed to restarting from windows. Have you tried this? - Colin McMillen On Sun, Jul 16, 2000 at 03:36:24PM -0700, Raymond L. Zarling wrote: Linux has stopped talking to my ethernet card (Kingston KNE100TX, tulip driver). The probem seems to be in ifconfig, which reports: SIOCSIFFLAGS: Resource temporarily unavailable I run a dual boot system, and it works fine from Windoze 98. It used to run, some weeks ago, in Linux too, but I neglected Linux for a few weeks, and when I tried it now again--this! I honestly don't remember changing anything in the interim; I certainly haven't opened the computer case. Since I don't know what SIOCSIFFLAGS are, I'm completely stumped about where to look next. Short of clearing the disk and reinstalling everything, but that's one of the things I was hoping Linux would save me from. As shown below, the tulip driver doesn't seem to be complaining, and ifconfig has all the right IP addresses and routes. Any ideas what's going on here? Thanks! --Ray [EMAIL PROTECTED] ** dmesg ** Linux version 2.2.12 ([EMAIL PROTECTED]) (gcc version 2.7.2.3) #2 Thu Aug 26 11:46:26 PDT 1999 ... tulip.c:v0.91g 7/16/99 [EMAIL PROTECTED] eth0: Digital DS21143 Tulip rev 65 at 0x6100, 00:C0:F0:3B:F7:91, IRQ 0. eth0: EEPROM default media type Autosense. eth0: Index #0 - Media MII (#11) described by a 21142 MII PHY (3) block. eth0: MII transceiver #1 config 3000 status 7829 advertising 01e1. ** ifconfig -a ** eth0 Link encap:Ethernet HWaddr 00:C0:F0:3B:F7:91 inet addr:192.168.1.13 Bcast:192.168.1.255 Mask:255.255.255.0 BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Base address:0x6100 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:3924 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 ** lsmod ** Module Size Used by nls_cp437 3548 1 (autoclean) tulip 29060 0 (unused) serial 18412 1 parport 6600 0 (unused) vfat8972 1 umsdos 22768 0 (unused) -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
What is SIOCSIFFLAGS, and when will he be back?
Linux has stopped talking to my ethernet card (Kingston KNE100TX, tulip driver). The probem seems to be in ifconfig, which reports: SIOCSIFFLAGS: Resource temporarily unavailable I run a dual boot system, and it works fine from Windoze 98. It used to run, some weeks ago, in Linux too, but I neglected Linux for a few weeks, and when I tried it now again--this! I honestly don't remember changing anything in the interim; I certainly haven't opened the computer case. Since I don't know what SIOCSIFFLAGS are, I'm completely stumped about where to look next. Short of clearing the disk and reinstalling everything, but that's one of the things I was hoping Linux would save me from. As shown below, the tulip driver doesn't seem to be complaining, and ifconfig has all the right IP addresses and routes. Any ideas what's going on here? Thanks! --Ray [EMAIL PROTECTED] ** dmesg ** Linux version 2.2.12 ([EMAIL PROTECTED]) (gcc version 2.7.2.3) #2 Thu Aug 26 11:46:26 PDT 1999 ... tulip.c:v0.91g 7/16/99 [EMAIL PROTECTED] eth0: Digital DS21143 Tulip rev 65 at 0x6100, 00:C0:F0:3B:F7:91, IRQ 0. eth0: EEPROM default media type Autosense. eth0: Index #0 - Media MII (#11) described by a 21142 MII PHY (3) block. eth0: MII transceiver #1 config 3000 status 7829 advertising 01e1. ** ifconfig -a ** eth0 Link encap:Ethernet HWaddr 00:C0:F0:3B:F7:91 inet addr:192.168.1.13 Bcast:192.168.1.255 Mask:255.255.255.0 BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Base address:0x6100 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:3924 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 ** lsmod ** Module Size Used by nls_cp437 3548 1 (autoclean) tulip 29060 0 (unused) serial 18412 1 parport 6600 0 (unused) vfat8972 1 umsdos 22768 0 (unused)
