[Bug 34933] Re: won't build against current kernel
** Changed in: thinkpad (Ubuntu) Status: Unconfirmed => Confirmed -- won't build against current kernel https://launchpad.net/bugs/34933 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 34933] Re: won't build against current kernel
Let me attach my trivial patch -- won't build against current kernel https://launchpad.net/bugs/34933 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 34933] Re: won't build against current kernel
** Changed in: thinkpad (Ubuntu) Assignee: MOTU => MOTU Reviewers Team Status: Confirmed => Fix Committed -- won't build against current kernel https://launchpad.net/bugs/34933 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 44194] Re: wpasupplicant doesn't start when the network start
I see the same problem and both workarounds work for me. But there is another (related?) problem remaining: once connected (either without workaround and having networking restarted or with one of the workarounds) it is not possible to restart networking again. The connection cannot be reestablished. -- wpasupplicant doesn't start when the network start https://launchpad.net/bugs/44194 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61329] Re: [edgy] pppd does not correctly work with pptpconfig
I see the same error message: Cannot determine ethernet address for proxy ARP I am using PPTP in kvpnc on edgy. I am not sure if this is a bug or a feature (me doing a configuration bug). More browsing of FAQs is required. -- [edgy] pppd does not correctly work with pptpconfig https://launchpad.net/bugs/61329 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61329] Re: [edgy] pppd does not correctly work with pptpconfig
The result of some more investigation is: The message "Cannot determine ethernet address for proxy ARP" does not point to the problem, but causes the problem. In older Ubuntu releases (e.g. breezy) this message pops up as well, but the pptpconfig does not care. With edgy, it seems that pptpconfig suddenly get's confused by that. Probably because an error code is generated somewhere in the tool chain due to that message. Getting closer - further investigation is needed. -- [edgy] pppd does not correctly work with pptpconfig https://launchpad.net/bugs/61329 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 207446] Re: wpa_supplicant fails after upgrade to Hardy
wpa_supplicant does not seem to run against kernel 2.6.24. With 2.6.22 everything works fine. In my case the problem appears with madwifi. /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.ath0.pid -i ath0 -D madwifi -C /var/run/wpa_supplicant Log: ioctl[SIOCSIWPMKSA]: No such device ioctl[SIOCSIWMODE]: No such device ioctl[SIOCGIFFLAGS]: No such device ioctl[SIOCGIWRANGE]: No such device ioctl[IEEE80211_IOCTL_SETPARAM]: No such device ioctl[SIOCSIWAP]: No such device ioctl[SIOCGIFFLAGS]: No such device Initializing interface 'ath0' conf 'N/A' driver 'madwifi' ctrl_interface '/var/run/wpa_supplicant' bridge 'N/A' Initializing interface (2) 'ath0' EAPOL: SUPP_PAE entering state DISCONNECTED EAPOL: KEY_RX entering state NO_KEY_RECEIVE EAPOL: SUPP_BE entering state INITIALIZE EAP: EAP entering state DISABLED EAPOL: External notification - portEnabled=0 EAPOL: External notification - portValid=0 Could not configure driver to use managed mode Could not set interface 'ath0' UP WEXT: Operstate: linkmode=1, operstate=5 wpa_driver_madwifi_init: failed to set wpa_supplicant-based roaming WEXT: Operstate: linkmode=0, operstate=6 Failed to initialize driver interface Failed to add interface ath0 Cancelling scan request Cancelling authentication timeout ** Changed in: wpasupplicant (Ubuntu) Status: New => Confirmed -- wpa_supplicant fails after upgrade to Hardy https://bugs.launchpad.net/bugs/207446 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
[Bug 63450] Re: acpid install fails, upgrading from dapper to edgy beta.
Same for me when upgrading from Feisty to Gutsy. * Loading ACPI modules... [ OK ] * Starting ACPI services... invoke-rc.d: initscript acpid, action "start" failed. The workaround of stopping acpid manually before running 'dpkg --configure -a' worked for me. I think that the issue should be addressed, because it is a stumbling stone for people who are upgrading their Kubuntu installation. -- acpid install fails, upgrading from dapper to edgy beta. https://bugs.launchpad.net/bugs/63450 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 34933] Re: won't build against current kernel
A quick fix is to add the following include statement to thinkpadpm.c: Click the following link for more information: http://www.thinkwiki.org/wiki/Talk:Tpctl -- won't build against current kernel https://launchpad.net/bugs/34933 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
