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 t
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 I
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
@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 Ubu
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 w
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, whi
