http://qa.mandrakesoft.com/show_bug.cgi?id=2511
------- Additional Comments From [EMAIL PROTECTED] 2003-03-07 16:00 ------- This still occurs with the Mar 06 cooker. ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: I installed this morning's cooker on my laptop, which has a Linksys wireless card whose description is not in the PCMCIA config files. The initial summary came up with network NOT CONFIGURED, so I clicked CONFIGURE and went through the wizard. It didn't detect any hardware, but did allow me to pick orinoco_cs from a list of drivers. It then gave me a choice of letting the driver autoprobe or not (I chose yes). Then it told me everything was fine, and ended the dialog. However, Summary still showed NOT CONFIGURED, and I didn't have a network. In particular, the wizard never got to the point of allowing me to choose dhcp/static or supply IP addresses. After booting, I corrected the PCMCIA config file, and tried drakconnect through MCC. Same deal. It was only after I rebooted and Cardmgr recognized the card during startup that drakconnect would allow me to set the IP address. There are several things wrong here. First, drakconnect is giving the user the impression that his choice of the correct driver (orinoco_cs) gave a successful result when it did not. Second, the dhcp/static and IP address, DNS, and Gateway IP address have nothing to do with the driver, and should be prompted for whether drakconnect can get the driver working or not. Third, drakconnect ought to be smarter when dealing with PCMCIA network cards. If the config database doesn't have an entry for the card, is there any point to prompting for a driver selection ? It's Cardmgr that has to load the driver once the card is recognized, not drakconnect. It would be useful for drakconnect to probe the card and get its particulars, so that it can tell the user that the card doesn't seem to be in the database, and would he like drakconnect to create an entry for it (using the driver name that the user picks) ? But if it's not going to do that, it ought to at least inform the user that Cardmgr doesn't seem to have recognized any ethernet cards, that drakconnect can't do anything about it, and tell the user what *he* can do about it.
