From: [email protected]

Package: kernel

I consistently experience lockups some 30s to 2 min after logging in
if the bttv module is loaded with the correct "card=100" parameter.
The cursor is blinking but the output of running programs is not
coming and neither mouse nor keyboard do anything. NUM-LOCK and
CAPS-LOCK lights are off and can't be turned on by pressing the
appropriate buttons. There is nothing in /var/log/messages.

I have a Hercules Smart TV Stereo, which is not autodetected by discover/hotplug as such (bttv0: using: *** UNKNOWN/GENERIC *** [card=0,autodetected]).

So I have added a file "bttv" in /etc/modprobe.d/ with the contents
"options bttv card=100" and discover/hotplug loads my card with the
correct parameter. I used this procedure before with the same card in
another system to get the Smart TV working.

If I move my /etc/modprobe.d/bttv out of the way and reboot the system
runs stable.

The system is not running X or anything. It's a fresh install and all
I did after installing so far is:

- Added "alias eth0 forcedeth" so the network would come up

- Ran pppoe-conf to set up ADSL

- Installed gpm

- Created by "bttv" file in /etc/modprobe.conf/ (<-- this is when the
lockups started even before doing the next step)

- Installed Alsa packages and copied contents of /usr/share/doc/alsa-base/alsa-base.discover to /etc/discover.conf


My system:
amd64 3200, Nforce3 chipset, Geforce 6800, Installed with
Debian-Installer rc1 using "unstable" as repository and 2.6.7 (as
coming with Debian Installer) as kernel


Please tell me if/how I can help to track down this bug.


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)