Sjoerd Hiemstra([EMAIL PROTECTED]) is reported to have said: > Wayne Topa wrote: > > Sjoerd Hiemstra([EMAIL PROTECTED]) is reported to have said: > > > On Mon, 10 Sep 2007 Chris Brotherton wrote: <--<snip>--> originsg description > > > > You don't give enough information to really help troubleshooting these > > problems. ie Gome or KDE or standard wireless setup. Any useful > > answer depends, at least, on knowing which you are using to connect to > > your AP. > > When I purchased the T30, it came with Windows XP pre-installed. Before > I wiped that, I took a look at the way its wireless connections work. > My router is set to WPA-PSK encryption by default, and after entering > the WPA-PSK key the connection was OK. Then again, the laptop had a > label saying 'Designed for Windows XP'. I wonder if the manufacturer > violated standards while adapting to XP.
OK, I understand. Now we need even more info. Did you use the orinoco card to do the install or was it eth1? I suspect eth1 might be an IBM internal Wireless interface. > The Lenny installer only knows WEP encryption, as far as I could see. > So I configured the router to WEP, the installer detected the > connection automatically, and installation from the internet went well. > > The installer saw three connection systems in the laptop: > - wireless connection with interface wifi0 > - wireless connection with interface eth0 > - ethernet connection with interface eth1. > Odd enough, only eth0 worked, not wifi0 as one would expect. At a console prompt do lspci -v Be sure the orinoco in plugged in when you run that. That will tell us what the Network interfaces are. They work in windows so we have to find out what they are. We need the lines like these from my T40. 0000:02:02.0 Network controller: Intel Corp. PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04) 0000:02:08.0 Ethernet controller: Intel Corp. 82801BD PRO/100 VE (MOB) Ethernet Controller (rev 81) 0000:07:00.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01) > > After booting the first time, the connection was lost. > Wireless is new to me, and I understand from your words that I'd better > make a study of standard wireless setup, and possibly try to get the > wired connection working in order to do an 'aptitude install kde' and > explore the possibilities that KDE offers. > Until now, I've only used Gnome's tools to try to re-establish the > connection. Most (all) IBM interfaces will work in Linux so you need to know what modules have to be loaded before bringing the interfaces up. As I said, I don't use Gnome or KDE, so I can't help you there. If we can get the network working without them, _they_ should just fall into line. I hope. Install the debian-reference package. Chapter 10 is the section you need to read through. Another thing to check. Make sure you have the dhcp3-client package installed in both the etch and testing installs. > > As I only use /etc/network/interfaces and dhclient to connect to an > > AP, all I can offer is, let us see what that file look like. > > Contents of /etc/network/interfaces: > > | # The loopback network interface > | auto lo > | iface lo inet loopback > | > | # The primary network interface > | allow-hotplug wifi0 > | iface wifi0 inet dhcp > | network 81.207.239.0 > | broadcast 81.207.239.255 > | # wireless-* options are implemented by the wireless-tools package > | wireless-mode managed > | wireless-essid SX551559148 > | wireless-key1 s:1234567890abccba0987654321 > | # dns-* options are mplemented by the resolvconf package, if > installed > | dns-nameservers 195.121.1.34 195.121.1.66 > | dns-search sh > | wireless-key s:1234567890abccba0987654321 > | > | iface eth0 inet dhcp > | wireless-essid SX551559148 > | wireless-key dde1fefdtc007b83e6ada40098 > | > | auto wifi0 Wayne -- A hacker does for love what others would not do for money. _______________________________________________________ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
