On Sat, 2012-12-08 at 12:29 +0100, Gaudenz Steinlin wrote: > Hi > > Brian Potkin <claremont102@gmail.com> writes: > > > > +</para><para> > > + > > +The routines used to detect missing firmware can only be of help for > > +modules loaded after &d-i; has started. This is irrelevant; not all drivers are included in d-i (and in particular radeon is not). > This implies that the > > +capabilities of some devices, the graphics card, for example, are no > > +different at the end of the installation from what they were at the > > +beginning and may mean some of your hardware is not being used to its > > +full potential. If you suspect this is the case, or are just curious, it > > +is not a bad idea to check the output of the <command>dmesg</command> > > +command on the newly booted system and search for "firmware", "missing", > > +"unable" or "fail". > > + > > Shouldn't we improve the installer to do this search instead? To me this > seems to be mostly scriptable. This doesn't work. I think we should standardise the log messages from the kernel. Ben. -- Ben Hutchings Beware of programmers who carry screwdrivers. - Leonard Brandwein
Attachment:
signature.asc
Description: This is a digitally signed message part