Another idea. I'm not busting my head over this anymore. Don't have any great ideas anyway. Sorry. Need input from others. But: Why don't you post the entire dmesg output listing, not the one you get after modprobe, but what you get when you first turn your computer on and the card doesn't load, as you say. There should be some funny message there, like where it tries to load and then doesn't, or something. The card is on a pci slot and whether the device is created by udev or not, there must be some kind of system acknowledgement of it's presence. Maybe there's a clue in the listing? On Apr 12, 2005 1:35 AM, kwhiskers <kwhiskers@xxxxxxxxx> wrote: > Dead Silence. Seems an omen. Looked at some other boards, and many > have made the same comment. There is only silence on this topic. > > Not one of the more knowledgeable ones here, but one who has gotten > 100% of his system problems solved the long and hard way. > > Have you tried putting the card on pci slot 5? There is some > indication on various boards that this card wants pci 5 and it doesn't > like to share an interrupt. > > Have you looked into the bios. Read somewhere that linux does not like > the plug'n'play operating system setting turned on. I have it off and > windows doesn't complain. > > Just some further ideas that popped into my head. > > Had a look at mythtv, but for some reason yum won't work with the > atrpms repo. Keep getting messages about not being able to read > repomd.xml. Added a number of mirrors to conf, but still same. Don't > need it now anyway. Will wait. > > On Apr 11, 2005 9:36 PM, John L. Pierce <bjjp@xxxxxxxxx> wrote: > > A question for the more informed of us. > > > > Concerning the loading of the bttv module, is there anything in the udev > > permissions or rules that would prevent the module from loading at boot? > > > > My modprobe.conf file looks exactly like ever other modprobe.conf file I > > have seen on the internet. > > > > << > > alias char-major-81 bttv > > >> > > > > >From every thing I have read on the internet and discussions groups, the > > above line should be the only thing necessary to load the module at > > boot! > > > > Is that correct? If so, since the module loads fine in manual > > modprobe bttv, could it possibly be udev and hotplug causing the > > problem. > > > > Maybe /dev is not being created early enough to allow the creation > > of /dev/video0. > > > > Thanks in advance! > > > > John > > -- > > > > -- > > fedora-list mailing list > > fedora-list@xxxxxxxxxx > > To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list > > >
