On Sat, 20 Apr 2013 16:07:47 +0100 Ben Hutchings <ben@decadent.org.uk> wrote: > Control: tag -1 patch > > On Fri, 2013-04-19 at 22:07 -0700, Andres Salomon wrote: > > Package: fb-modules-3.2.0-4-486-di > > Version: 3.2.41-2 > > > > The OLPC XO-1.5 doesn't support VESA. It needs the viafb driver in > > order to get display output. Similar to #705780, please consider > > including viafb.ko in the fb-modules udeb. > > I just tried loading viafb on a VIA Epia board (Unichrome CLE266) > running squeeze, and the console is now broken. I can see the GRUB > boot messages (from weeks ago) and a mess of dots in various colours. > > The module also has a whole lot of parameters which suggest that it > may need board-specific configuration. So I don't think we can allow > it to be autoloaded on the whole range of device IDs it claims. > > What if we apply a patch (attached) to match the specific subsystem ID > on the XO 1.5? (I got this from the Openchrome source so hopefully > it's correct.) This still leaves us needing to update udev and then > worry about kernel vs udev versions, but it should cover the > installer. > The idea seems fine to me, though I think that VX855 is in other systems besides OLPC ones. Cc'ing Daniel, maybe he has some other ideas? Note that simply including the module in debian-installer doesn't cause the module to be loaded as far as I can tell (even with a PCI device id match). It still needs to be manually loaded, so it would seem safe for d-i.
Attachment:
signature.asc
Description: PGP signature