Re: de0 strangenesses
Rene de Vries wrote: I think i've got a similar problem. This involves a DE500 (de0 driver) ethernet card and a 100 Mbit UTP. The problem was that somehow the driver didn't detect the 100Mbit and always switched to 10Mbit. The workaround that I use is a simple script "/etc/start_if.de0" with the following contents: # workaround 10/100Mbit start problem ifconfig de0 192.168.1.2 media 100baseTX ifconfig de0 down sleep 2 ifconfig de0 up Since I started using this script the machine always started with the 100baseTX interface active. Not always. Some boards resist that, and yet others will hang the hub (or the switch port) they are plugged into. Those need to see a 100MHz beat before they do something useful. I.e. Do NOT have them the first to turn on on a hub. Most switches are OK. I suspect some differences between revisions... Rene On a 3.0-current of October 1998 I'm having often trouble with de0. The machine often reboots over night (when either the locate db is built or some other big job - like mirror - is running). Anyway, after the reboot, often de0 is dead. This happend today again. When I came into the office I could not ping said machine. I sat at the console, logged in. The machine was perfectly alive, only the de0 interface didn't work at the BNC network. I did a ifconfig de0 down and exactly with doing that I got a kernel message from the driver: de0 BNC interface enabled (or something like that). Doing an ifconfig de0 up right after that the interface continued working at the BNC port. Can the driver writer(s) comment whether there have been changes to the driver WRT that behaviour so I can expect that with either 3.2 or -current the problem would be gone? -- Rene de Vrieshttp://www.tcja.nl/~rene; mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message -- Sincerely Yours, [EMAIL PROTECTED] 404.644.6401 Simon Shapiro Unwritten code has no bugs and executes at twice the speed of mouth S/MIME Cryptographic Signature
Re: de0 strangenesses
I think i've got a similar problem. This involves a DE500 (de0 driver) ethernet card and a 100 Mbit UTP. The problem was that somehow the driver didn't detect the 100Mbit and always switched to 10Mbit. The workaround that I use is a simple script /etc/start_if.de0 with the following contents: # workaround 10/100Mbit start problem ifconfig de0 192.168.1.2 media 100baseTX ifconfig de0 down sleep 2 ifconfig de0 up Since I started using this script the machine always started with the 100baseTX interface active. Rene On a 3.0-current of October 1998 I'm having often trouble with de0. The machine often reboots over night (when either the locate db is built or some other big job - like mirror - is running). Anyway, after the reboot, often de0 is dead. This happend today again. When I came into the office I could not ping said machine. I sat at the console, logged in. The machine was perfectly alive, only the de0 interface didn't work at the BNC network. I did a ifconfig de0 down and exactly with doing that I got a kernel message from the driver: de0 BNC interface enabled (or something like that). Doing an ifconfig de0 up right after that the interface continued working at the BNC port. Can the driver writer(s) comment whether there have been changes to the driver WRT that behaviour so I can expect that with either 3.2 or -current the problem would be gone? -- Rene de Vrieshttp://www.tcja.nl/~rene; mailto:r...@tcja.nl To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: de0 strangenesses
Christoph Kukulies writes: On a 3.0-current of October 1998 I'm having often trouble with de0. The machine often reboots over night (when either the locate db is built or some other big job - like mirror - is running). Anyway, after the reboot, often de0 is dead. This happend today again. When I came into the office I could not ping said machine. I sat at the console, logged in. The machine was perfectly alive, only the de0 interface didn't work at the BNC network. I did a ifconfig de0 down and exactly with doing that I got a kernel message from the driver: de0 BNC interface enabled (or something like that). Doing an ifconfig de0 up right after that the interface continued working at the BNC port. Can the driver writer(s) comment whether there have been changes to the driver WRT that behaviour so I can expect that with either 3.2 or -current the problem would be gone? this is old problem - I have it in 2.2.7-RELEASE too -- Chris Christoph P. U. Kukulies [EMAIL PROTECTED] -- @BABOLO http://links.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: de0 strangenesses
Christoph Kukulies writes: On a 3.0-current of October 1998 I'm having often trouble with de0. The machine often reboots over night (when either the locate db is built or some other big job - like mirror - is running). Anyway, after the reboot, often de0 is dead. This happend today again. When I came into the office I could not ping said machine. I sat at the console, logged in. The machine was perfectly alive, only the de0 interface didn't work at the BNC network. I did a ifconfig de0 down and exactly with doing that I got a kernel message from the driver: de0 BNC interface enabled (or something like that). Doing an ifconfig de0 up right after that the interface continued working at the BNC port. Can the driver writer(s) comment whether there have been changes to the driver WRT that behaviour so I can expect that with either 3.2 or -current the problem would be gone? this is old problem - I have it in 2.2.7-RELEASE too -- Chris Christoph P. U. Kukulies k...@gil.physik.rwth-aachen.de -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
