Ok, some people use amd64 and can fix the issue by renaming sis-agp.ko. Do they get the "bind" error before renaming?
Or do we have (at least) two different bugs here?
Sybille, you can try the workaround on a live cd by switching to a console (ctrl-alt-f1) and stopping X (sudo /etc/init.d/gdm stop) and unloading the module (sudo modprobe -r sis_agp) and delete it (locate sis_agp.ko, sudo rm ..., sudo depmod -a) and restart X (sudo /etc/init.d/gdm start).
Since you also have a amd64 board (according to the original report) I guess the bug is amd64-hardware only.
Ok, some people use amd64 and can fix the issue by renaming sis-agp.ko. Do they get the "bind" error before renaming?
Or do we have (at least) two different bugs here?
Sybille, you can try the workaround on a live cd by switching to a console (ctrl-alt-f1) and stopping X (sudo /etc/init.d/gdm stop) and unloading the module (sudo modprobe -r sis_agp) and delete it (locate sis_agp.ko, sudo rm ..., sudo depmod -a) and restart X (sudo /etc/init.d/gdm start).
Since you also have a amd64 board (according to the original report) I guess the bug is amd64-hardware only.