[Bug 105251] Re: NetworkManager wrongly releases DHCP IP
Marius: no, the reason for that is, that dhclient-script is not started. Just uncomment the dhclient-scprit entry and set it to the right path does fix that issue and you get the debugging output. But then it does not return to nm. wich is the real issue. -- NetworkManager wrongly releases DHCP IP https://bugs.launchpad.net/bugs/105251 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 105251] Re: NetworkManager wrongly releases DHCP IP
When I understand this right, following stuff appeared from Hardy to Intrepid: a) (minor issue) dhclient-script is not started per default. So the path to dhclient-script should be set right (to /sbin/dhclient-script) in /etc/dhclient.conf b) up to hardy, at the end in the dhclient-exit-hooks.d there is a should be some script telling the NetworkManager (via dbus?) that dhclient has done it's job. In hardy, this was done by _dhcdbd but dhcbd is not there any more in intrepid. And this seems to be the issue: there is nothing in dhclients exit hooks which tells the nm, that the job is done. If I'd understood, what is now the regular way to tell nm that, I could write a hook in exit... Or am I completely wrong? -- NetworkManager wrongly releases DHCP IP https://bugs.launchpad.net/bugs/105251 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 105251] Re: NetworkManager wrongly releases DHCP IP
Marius: no, the reason for that is, that dhclient-script is not started. Just uncomment the dhclient-scprit entry and set it to the right path does fix that issue and you get the debugging output. But then it does not return to nm. wich is the real issue. -- NetworkManager wrongly releases DHCP IP https://bugs.launchpad.net/bugs/105251 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 121653] Re: [gutsy] fglrx breaks over suspend/resume
On Mon, Feb 25, 2008 at 9:37 AM, Ben Collins [EMAIL PROTECTED] wrote: There's not much we can do here. We aren't reverting SLUB, and we can't fix the fglrx driver. Congratulations. But at last for my records: could you give us a pointer for the decision not to revert SLUB? Regards Steve -- [gutsy] fglrx breaks over suspend/resume https://bugs.launchpad.net/bugs/121653 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 121653] Re: [gutsy] fglrx breaks over suspend/resume
If this is the case, is there any reason not to convert to SLAB in Gutsy? Are there any usage numbers of ubuntu on ATI driven Laptops? -- [gutsy] fglrx breaks over suspend/resume https://bugs.launchpad.net/bugs/121653 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 121653] Re: [gutsy] fglrx breaks over suspend/resume
AFAIK everything has been said since a long time. Either the kernel configuration has to be changed or the fglrx (closed source) driver from ATI/AMD has to be changed. I am still wondering why the kernel configuration is not changed as I guess there are really many ATI gfx chipset users out there with laptops. Is there a reason for that? Meanwhile you could fix the standby issue it by a) Changing from SLUB to SLAB in the kernel konfiguration and rebuild the kernel (and of course all the restricted modules). For me a good starting point was http://www.thinkwiki.org/wiki/Installing_Ubuntu_(Gutsy_Gibbon)_7.10_on_a_ThinkPad_R60 (with the additional change from SLUB to SLAB) but you should understand what you are doing before you start on it... b) use the radeonhd driver (which I was not able to manage, but it sound not too promising right now) c) use unaccelerated drivers (which is really a pain) So, I went out for a) and everything works fine since then. Of course I have to pin now all kernel related stuff until the issue is solved in gutsy or hoary or whatever... Oh and before someone starts to complain about giving non bug related support in this list here: yes, I know :-) -- [gutsy] fglrx breaks over suspend/resume https://bugs.launchpad.net/bugs/121653 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 121653] Re: [gutsy] fglrx breaks over suspend/resume
@John I am even to dumb to get the radeonhd driver running. Is this the one included in gutsy? Could you place your xorg. conf for that somewhere? -- [gutsy] fglrx breaks over suspend/resume https://bugs.launchpad.net/bugs/121653 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
