You need to set it up (PCMCIA) to hottplug. On Tuesday 01 July 2003 03:04, Per-Olof Litby (Reg'l Mgr Nordic/Baltic - Java Web Services - Sun Microsystems) wrote:
Never got any response to this, so here's a little bit more info. After manually starting the interface as per the below, it works fine for a while until it suddenly loses its IP address again.
The dhcp daemon is still running, so I then have to kill it and repeat the manual startup process for the device.
Any ideas?
/POL
On Fri, 2003-06-27 at 12:23, Per-Olof Litby (Reg'l Mgr - Nordic/Baltic -
Java Web Services - Sun Microsystems) wrote:
A follow up to my own post: I discovered that if I manually do:
ifconfig eth1 up dhcpcd eth1
the interface comes up with a DHCP address and everything works great. So right now there are only 2 questions remaining:
- Why does the device come up as "failed" during boot?
- Why is not the DHCP request done automatically - is it missing from some startup script or what?
Any ideas welcome.
Thanks, P O Litby
On Thu, 2003-06-26 at 12:53, Per-Olof Litby (Java Web Services Reg'l
Mgr - Nordic - Sun Microsystems) wrote:
Greetings,
I've just installed SuSE 8.2 on my Toshiba Tecra 9000 laptop - I've tried using both Mandrake and RedHat but ended up selecting SuSE for hardware compatibility and company reasons.
The installation went like a charm, but to my surprise the built-in wireless LAN interface, a Lucent/Orinoco based mini-PCI interface which worked perfectly using the orinoco_cs driver in RedHat 9 and Mandrake 9 (and of course) Windows XP, was not detected and will not work properly.
I manually added the interface as eth1 with the orinoco_cs module (the "alias eth1 orinoco_cs" in /etc/modules.conf is there). Here are the problem symptoms:
- During boot, eth1 reports as "failed" - KWiFi Manager shows my machine has contact with the access point, the signal strength is excellent, the ESS ID is correct but Local IP is missing. - iwconfig shows the same information. - Trying to ping something results in "Network is unavailable" message.
If I then go into the Control Center and open up the configuration tool for the network cards, it shows that the wireless card is in ad hoc mode. It should be set to "Auto". Now, if I change the setting to "Auto" and hit "Finish" something interesting happens: For a brief instant, after SuSEconfig has completed, KWiFi Manager shows a local IP address and then the connection disappears and everything goes blank.
Rebooting will restore the WLAN connection to the same state as before, and it will have returned to ad hoc mode.
I've tried all the different drivers which should work with this card - same problem. This has to be something SuSE specific because it worked with other distributions. I have 2 DHCP servers on the LAN and both are working fine.
Any help appreciated! thanks,
------------------------------------------------------- Per-Olof Litby Phone: +46 8 631-1463 Regional Mgr - Nordic/Baltic Fax: +46 8 631-1005 Java Web Services Email: politby@sun.com Sun Microsystems ------------------------------------------------------- Calendar URL below (Sun only) http://namefinder.germany/nfcal.cgi?-s+23213 ------------------------------------------------------- I've got this great ambition to die of exhaustion rather than boredom. -------------------------------------------------------
------------------------------------------------------- Per-Olof Litby Phone +46 8 631-1463 Regional Mgr - Nordic/Baltic Fax +46 8 631-1005 Java Web Services Email politby@sun.com Sun Microsystems ------------------------------------------------------- Calendar URL below (Sun only) http://namefinder.germany/nfcal.cgi?-s+23213 ------------------------------------------------------- I've got this great ambition to die of exhaustion rather than boredom. -------------------------------------------------------