how to blacklist some hardware

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bonjour,

On a Toshiba laptop, I have an integrated TV card which is strangely not
recognised by udev, but which install the correct kernel module
specified by lspci.

lspci gives:

02:09.0 0400: 14f1:5b7a
	Subsystem: 1179:0010
	Flags: bus master, medium devsel, latency 64, IRQ 19
	Memory at 48000000 (32-bit, non-prefetchable) [size=64M]
	Capabilities: [44] Vital Product Data
	Capabilities: [4c] Power Management version 2
	Kernel modules: cx18

But at the beginning of the boot sequence, I have an error message:

dmesg | grep cx18

cx18: Start initialization, version 1.1.0
cx18-0: Initializing card 0
cx18-0: Unknown card: vendor/device: [14f1:5b7a]
cx18-0: subsystem vendor/device: [1179:0111]
cx18-0: Defaulting to Hauppauge HVR-1600 card
cx18-0: Please mail the vendor/device and subsystem vendor/device IDs
and what kind of
cx18-0: card you have to the ivtv-devel mailinglist (www.ivtvdriver.org)
cx18-0: Prefix your subject line with [UNKNOWN CX18 CARD].
cx18 0000:08:09.0: enabling device (0000 -> 0002)
cx18 0000:08:09.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
cx18-0: cx23418 revision 01010000 (B)
cx18-0: Invalid EEPROM
cx18-0: Simultaneous Digital and Analog TV capture supported
IRQ 22/cx18-0: IRQF_DISABLED is not guaranteed on shared IRQs
cs5345 0-004c: chip found @ 0x98 (cx18 i2c driver #0-0)
cx18-0: Registered device video1 for encoder MPEG (64 x 32 kB)
DVB: registering new adapter (cx18)
cx18-0: frontend initialization failed
cx18-0: DVB failed to register
cx18-0: Registered device video33 for encoder YUV (16 x 128 kB)
cx18-0: Registered device vbi1 for encoder VBI (20 x 51984 bytes)
cx18-0: Registered device video25 for encoder PCM audio (256 x 4 kB)
cx18-0: Registered device radio1 for encoder radio
cx18-0: Error -1 registering devices
cx18-0: Error -1 on initialization
cx18: probe of 0000:08:09.0 failed with error -1
cx18: End initialization

And it takes ages before going at the next step.

In fact, I do not need to have this card working and I don't want to
make a lot of things described in some google searches to have it working.

Is there a way to tell udev to ignore this hardware and skip anything
regarding it.

Thanks for any answer.

- -- 
François Patte
UFR de mathématiques et informatique
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)1 4286 2145
http://www.math-info.univ-paris5.fr/~patte
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAk5EJbcACgkQdE6C2dhV2JVb2wCgptesSzCnzdTpswkd/r2kTJv+
kekAn1Dkg60RZiMtk0hQ+yzufK6E5C6O
=Fa4I
-----END PGP SIGNATURE-----
-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines


[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux