You might be able to use the boot alternative: When the system boots (grub bootloader) press ESC (?not sure, haven't used it for a long time) to make the bootmenu (grub) visible. choose option 2 (a kind of "start in safe mode")
when you are in safe mode (and you are root) just type (or cut 'n paste from here):
echo "#these lines can be removed in the official hardy release" >>/etc/modprobe.d/blacklist
echo blacklist saa7134 >>/etc/modprobe.d/blacklist
echo blacklist saa7134_dvb >>/etc/modprobe.d/blacklist
now (in theory) you should be able to boot up normally. :-)
And yes, this is a well known bug and it is already solved, it just didn't make it in time to get into the Hardy-RC-Release.
Hi Kai,
You might be able to use the boot alternative: When the system boots (grub bootloader) press ESC (?not sure, haven't used it for a long time) to make the bootmenu (grub) visible. choose option 2 (a kind of "start in safe mode")
when you are in safe mode (and you are root) just type (or cut 'n paste from here):
echo "#these lines can be removed in the official hardy release" >>/etc/ modprobe. d/blacklist modprobe. d/blacklist modprobe. d/blacklist
echo blacklist saa7134 >>/etc/
echo blacklist saa7134_dvb >>/etc/
now (in theory) you should be able to boot up normally. :-)
And yes, this is a well known bug and it is already solved, it just didn't make it in time to get into the Hardy-RC-Release.