No, Steve is right. This is not one problem, but several problems that have the same apparent outcome, which is making this impossible to fix if it's treated as a single problem. Suppose your computer stopped booting into Ubuntu altogether. Could it be because your hard drive has physically failed? your hard drive's boot sector is overwritten? your hard drive's partition table is overwritten? your BIOS configuration settings are incorrect? your BIOS has become corrupt after a firmware update? Any of these will produce the same end result. But if you want to fix it, you have to focus on and address the cause of the problem at hand for your particular situation, instead of worrying about all the different things that could be causing it not to work.
Steve -- my issue relates to ndiswrapper, and Gene's relates to prism54. Both drivers seem to be fixed by changing the AP_SCAN value that is issued to wpa_supplicant by NetworkManager when those drivers are present. (Fixed, meaning that they will connect when the hidden AP information is entered manually, but they won't connect automatically at login.) I haven't tested it in Hardy yet, but I haven't seen anything in the changelog to suggest that this behavior has been modified at all from 0.6.5-0ubuntu16.7.10.0? -- can't connect to hidden network https://bugs.launchpad.net/bugs/50214 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
