From owner-freebsd-mobile Wed May 10 1:23:42 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 0EB5537B5F7 for ; Wed, 10 May 2000 01:23:38 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id BAA12904 for mobile@freebsd.org; Wed, 10 May 2000 01:13:59 +0100 (BST) (envelope-from nik) Date: Wed, 10 May 2000 01:13:57 +0100 From: Nik Clayton To: mobile@freebsd.org Subject: DFE650 unresponsive after reattaching balun Message-ID: <20000510011357.A11828@catkin.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Organization: FreeBSD Project Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi guys, Having just made the jump from 3.2-PAO to 4.0-stable on my Vaio F270, things are going fairly well. However. . . Most of the time my laptop's connected to a network, be at at home, or on a client's site. But when I'm travelling to and fro it's obviously disconnected. Under 3.2-PAO I could disconnect the balun (or 'dongle', if you prefer) from the network card, but leave the network card in the machine. I could then use the machine off the network as normal -- I'd get a few messages in syslog about the network not responding, but nothing that seemed to cause any problems. Then, when I plug the balun back in, and connect the laptop back up to a network, everything works fine -- the connectivity lights come on, the network is reachable, and all is well. It didn't matter what I'd done on the machine in the mean time -- I could suspend to memory or to disk with no problems, and the card would still come back. This was quite convenient, as it meant I didn't have to go through the hassle of ejecting the card, putting a 'spacer' card in to fill the gap, remembering to bring the card, and so on. I just tried it today with 4.0-stable and it doesn't work. I get the usual syslog messages about the network not being contactable. Then, when I plug the balun back in the link lights don't come on. "ifconfig -a" shows the ed1 interface as being "UP", and with an IP address. I tried removing and reinserting the card to see if I could force pccardd to redetect it, but no joy. I tried killing and restarting pccard, and then removing and reinserting the card -- again, no joy. In the end I rebooted, and the card came back to life. It's certainly not a serious problem. I just I'd mention it on the off chance there's an easy fix. N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message