At 21:47:12 on Saturday Saturday 10 October 2009, Aaron Kulkis
Stan Goodman wrote:
I FOUND IT!!
There was nothing wrong with the Ethernet card or the wireless card (aka Network card). The glitch was in the BIOS.
The BIOS, naturally, has a checkbox for "Enable Internal Wireless WLAN", and this was CHECKED, as it should be. It also has a checkbox for ""Enable Internal Bluetooth", which I had checked because, although I have no Bluetooth devices now, I had intended to acquire a headset. Since both are checked, and there is no indication whatever that they are mutually exclusive, I thought I might as well prepare for the future by enabling both.
They are, however, mutually exclusive, and this became clear after I unchecked Bluetooth on a hunch and spruced up the Network Devices window, I am able to communicate with the 'Net by hard connection to the router, but not by wireless. I can live with this for the time being.
The paradox is that disenabling Bluetooth in favor of the _wireless_card_ has permitted the Ethernet card to become visible, but has not affected the wireless card.
That is not the only bug in the BIOS: The BIOS behavior of the NUMLOCK key interacts with the behavior as set by Control Center > Peripherals > Keyboard in an unexpected way.
My gratitude to everyone who tried to help me solve the problem.
Which BIOS is this?
The startup screen says "Revision A00", which sounds like it hasn't been revised at all. This is a good opportunity to report that the great success described in my note above disappeared in the course of rebooting. The settings of Network Devises are all as I left them, and the Ethernet is reported as "not connected", which means that it is seen by the system. It seems that now now that software issues are resolved, I have a hardware problem. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org