Re: loading kernel mode setting drivers
Julien Cristau wrote:
> On Mon, Jan 25, 2010 at 00:27:48 +, Ben Hutchings wrote:
>
> > What about my suggestion of removing the MODULE_DEVICE_TABLE
> > declarations from fb modules, so they do not appear in modules.pcimap
> > etc? Did you see any problem with that?
> >
> Dropping those and udev's blacklist would be fine as far as I'm
> concerned. Not sure what this means for people with custom kernel,
> since they'd lose the blacklist too, but I don't care much either way.
I suppose we don't really want this level of coupling between udev and
the kernel. So I'm happy to recommend your recipe to Marco, but with a
restriction to PCI drivers:
find /lib/modules/$(uname -r)/kernel/drivers/video -type f | {
while read mod; do
/sbin/modinfo $mod | grep -q '^alias: *pci' \
&& echo blacklist $(basename $mod .ko)
done
}
Ben.
--
Ben Hutchings
Any smoothly functioning technology is indistinguishable from a rigged demo.
signature.asc
Description: This is a digitally signed message part
Re: loading kernel mode setting drivers
On Mon, Jan 25, 2010 at 00:27:48 +, Ben Hutchings wrote: > What about my suggestion of removing the MODULE_DEVICE_TABLE > declarations from fb modules, so they do not appear in modules.pcimap > etc? Did you see any problem with that? > Dropping those and udev's blacklist would be fine as far as I'm concerned. Not sure what this means for people with custom kernel, since they'd lose the blacklist too, but I don't care much either way. Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: loading kernel mode setting drivers
On Mon, 2010-01-25 at 00:56 +0100, Julien Cristau wrote: > On Tue, Jan 12, 2010 at 01:34:45 +0100, Marco d'Itri wrote: > > > On Jan 12, Julien Cristau wrote: > > > > > Marco, what do you think of switching to this, or at least using its fb > > > part? > > I do not mind explicitly blacklisting each fb driver, but I would like > > to have a way to semi-automatically generate the list. Is there any? > > > I suppose something like > find /lib/modules/$(uname -r)/kernel/drivers/video -type f|while read > mod; do echo blacklist $(basename $mod .ko); done > could work (possibly excluding some generic and backlight drivers, if > those should be autoloaded?). What about my suggestion of removing the MODULE_DEVICE_TABLE declarations from fb modules, so they do not appear in modules.pcimap etc? Did you see any problem with that? Ben. -- Ben Hutchings Any smoothly functioning technology is indistinguishable from a rigged demo. signature.asc Description: This is a digitally signed message part
Re: loading kernel mode setting drivers
On Tue, Jan 12, 2010 at 01:34:45 +0100, Marco d'Itri wrote: > On Jan 12, Julien Cristau wrote: > > > Marco, what do you think of switching to this, or at least using its fb > > part? > I do not mind explicitly blacklisting each fb driver, but I would like > to have a way to semi-automatically generate the list. Is there any? > I suppose something like find /lib/modules/$(uname -r)/kernel/drivers/video -type f|while read mod; do echo blacklist $(basename $mod .ko); done could work (possibly excluding some generic and backlight drivers, if those should be autoloaded?). Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: loading kernel mode setting drivers
On Tue, 2010-01-12 at 00:43 +, Julien Cristau wrote: > On Tue, Jan 12, 2010 at 00:36:49 +, Julien Cristau wrote: > > > On Tue, Jan 12, 2010 at 00:31:53 +, Julien Cristau wrote: > > > > > I tried to look at how other distributions handle this, and this > > > /etc/modprobe.d/blacklist.conf file seems to be a Debianism. From what > > > I can tell (looking at the ubuntu archive and a fedora 10 box) other > > > distros have a /etc/modprobe.d/blacklist.conf provided by the hwdata > > > package, which explicitly blacklists fb drivers, avoiding the above > > > issue. > > > > > Looking again ubuntu's hwdata doesn't install that file, so they > > probably have something else. Something for another day… > > > Their blacklist is here: > http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/lucid/module-init-tools/lucid/files/head%3A/debian/modprobe.d/ > > So they also blacklist explicitly each fb driver. Except for the firewire stack, their entire blacklist looks nice (and well commented). Xav -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: loading kernel mode setting drivers
On Tue, Jan 12, 2010 at 01:34:45AM +0100, Marco d'Itri wrote: > I do not mind explicitly blacklisting each fb driver, but I would like > to have a way to semi-automatically generate the list. Is there any? Sure, the kernel build have all necessary informations. Bastian -- We Klingons believe as you do -- the sick should die. Only the strong should live. -- Kras, "Friday's Child", stardate 3497.2 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: loading kernel mode setting drivers
On Tue, Jan 12, 2010 at 00:36:49 +, Julien Cristau wrote: > On Tue, Jan 12, 2010 at 00:31:53 +, Julien Cristau wrote: > > > I tried to look at how other distributions handle this, and this > > /etc/modprobe.d/blacklist.conf file seems to be a Debianism. From what > > I can tell (looking at the ubuntu archive and a fedora 10 box) other > > distros have a /etc/modprobe.d/blacklist.conf provided by the hwdata > > package, which explicitly blacklists fb drivers, avoiding the above > > issue. > > > Looking again ubuntu's hwdata doesn't install that file, so they > probably have something else. Something for another day… > Their blacklist is here: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/lucid/module-init-tools/lucid/files/head%3A/debian/modprobe.d/ So they also blacklist explicitly each fb driver. Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: loading kernel mode setting drivers
On Tue, Jan 12, 2010 at 00:31:53 +, Julien Cristau wrote: > I tried to look at how other distributions handle this, and this > /etc/modprobe.d/blacklist.conf file seems to be a Debianism. From what > I can tell (looking at the ubuntu archive and a fedora 10 box) other > distros have a /etc/modprobe.d/blacklist.conf provided by the hwdata > package, which explicitly blacklists fb drivers, avoiding the above > issue. > Looking again ubuntu's hwdata doesn't install that file, so they probably have something else. Something for another day… Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: loading kernel mode setting drivers
On Jan 12, Julien Cristau wrote: > Marco, what do you think of switching to this, or at least using its fb > part? I do not mind explicitly blacklisting each fb driver, but I would like to have a way to semi-automatically generate the list. Is there any? BTW, I am not sure why the watchdog drivers are being blacklisted... What is the point? The watchdog will not be enabled anyway until the device is opened. -- ciao, Marco signature.asc Description: Digital signature
Re: loading kernel mode setting drivers
On Thu, Dec 31, 2009 at 18:24:56 +, Julien Cristau wrote: > One issue that showed up is that i915 isn't getting loaded by udev, > because /etc/modprobe.d/blacklist.conf contains: > > # This directive blacklists all devices which are members of the display > class. > # It has the main effect of preventing udev from autoloading the fb drivers. > # vendor, device, subsystem_vendor, subsystem_device, class, class, class > install pci:v*d*sv*sd*bc03sc*i* /bin/true > > So right now it gets loaded by the initramfs if video=i915 is in the > kernel command line, or by X when it starts otherwise. > I tried to look at how other distributions handle this, and this /etc/modprobe.d/blacklist.conf file seems to be a Debianism. From what I can tell (looking at the ubuntu archive and a fedora 10 box) other distros have a /etc/modprobe.d/blacklist.conf provided by the hwdata package, which explicitly blacklists fb drivers, avoiding the above issue. The current version of that blacklist is: # # Listing a module here prevents the hotplug scripts from loading it. # Usually that'd be so that some other driver will bind it instead, # no matter which driver happens to get probed first. Sometimes user # mode tools can also control driver binding. # # Syntax: driver name alone (without any spaces) on a line. Other # lines are ignored. # # watchdog drivers blacklist i8xx_tco # framebuffer drivers blacklist aty128fb blacklist atyfb blacklist radeonfb blacklist i810fb blacklist cirrusfb blacklist intelfb blacklist kyrofb blacklist i2c-matroxfb blacklist hgafb blacklist nvidiafb blacklist rivafb blacklist savagefb blacklist sstfb blacklist neofb blacklist tridentfb blacklist tdfxfb blacklist virgefb blacklist vga16fb # ISDN - see bugs 154799, 159068 blacklist hisax blacklist hisax_fcpcipnp # sound drivers blacklist snd-pcsp Marco, what do you think of switching to this, or at least using its fb part? Thanks, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: loading kernel mode setting drivers
On Thu, 2009-12-31 at 18:24 +, Julien Cristau wrote: [...] > One possible way to fix this, I guess, would be to replace this > blacklist entry with a list of blacklisted fb drivers, to allow i915 > (and later radeon and nouveau) being loaded automatically on boot. Is > this feasible? Are there other/better solutions? That sounds like it might be a problem to maintain. Would it be feasible for each X video driver to blacklist the conflicting fb driver(s), in the same way that KMS-capable X video drivers set module parameters to enable KMS? Ben. -- Ben Hutchings The generation of random numbers is too important to be left to chance. - Robert Coveyou signature.asc Description: This is a digitally signed message part
loading kernel mode setting drivers
On Tue, Dec 22, 2009 at 20:33:00 +0100, Julien Cristau wrote: > On Sun, Dec 20, 2009 at 16:50:22 +, Ben Hutchings wrote: > > > > > The X packages will be able to use modprobe > > > > config files to enable KMS at run time as required. > > > > This is not for the kernel team to do. > > > FWIW, this is done for intel in experimental, probably soon in unstable. > For radeon the decision whether to enable kernel mode setting by default > for squeeze is still to be made. > One issue that showed up is that i915 isn't getting loaded by udev, because /etc/modprobe.d/blacklist.conf contains: # This directive blacklists all devices which are members of the display class. # It has the main effect of preventing udev from autoloading the fb drivers. # vendor, device, subsystem_vendor, subsystem_device, class, class, class install pci:v*d*sv*sd*bc03sc*i* /bin/true So right now it gets loaded by the initramfs if video=i915 is in the kernel command line, or by X when it starts otherwise. One possible way to fix this, I guess, would be to replace this blacklist entry with a list of blacklisted fb drivers, to allow i915 (and later radeon and nouveau) being loaded automatically on boot. Is this feasible? Are there other/better solutions? Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
