Bug#363331: installation-reports
On Sat, Apr 29, 2006 at 08:30:50PM +0200, Frans Pop wrote:
> On Saturday 29 April 2006 01:05, Digby Tarvin wrote:
> > 1. Mysterious '/etc/modules' content
>
> These are all wrong and should be either deleted or at least the ".load"
> should be removed. The best thing is probably to delete them completely
> (except maybe for the sbp2 module, no idea what that is really; the
> others were needed in the past for 2.4 and early 2.6 kernels).
>
> This has already been fixed in current daily builds.
Fine.
> Result of the above.
>
> > 2. Hardware detection seems to find a 'hw_random' device which either
> > doesn't exist or the driver doesn't recognise:
>
> Relatively harmless message. You can get rig of it by either blacklisting
> that module for discover or uninstalling discover.
> Discover is only really needed now to help detect your graphics card for
> Xorg and not anymore for loading modules during boot.
Any idea if it was mis-detection of non-existant hardware, or is there
really a hardware RNG that is being detected but not handled by the
driver module?
I can't see any mention of RNG in the datasheet for the device concerned..
> > 3. Hardware detect attempts to load modules that are already loaded,
> > producing the following warnings:
> >
> > Fri Apr 28 22:10:54 2006: ^[[33m*^[[39;49m Skipping already loaded
> > module yenta_socket. Fri Apr 28 22:10:54 2006: ^[[33m*^[[39;49m
> > Skipping already loaded module ohci1394. Fri Apr 28 22:10:54 2006:
> > ^[[33m*^[[39;49m Skipping already loaded module 8139too. Fri Apr 28
> > 22:10:54 2006: ^[[33m*^[[39;49m Skipping already loaded module ipw2200.
> > Fri Apr 28 22:10:54 2006: ^[[33m*^[[39;49m Skipping already loaded
> > module piix. Fri Apr 28 22:10:54 2006: ^[[33m*^[[39;49m Skipping
> > already loaded module ata_piix. Fri Apr 28 22:10:54 2006:
> > ^[[33m*^[[39;49m Skipping already loaded module snd_hda_intel. Fri Apr
> > 28 22:10:54 2006: ^[[33m*^[[39;49m Skipping already loaded module
> > uhci_hcd. Fri Apr 28 22:10:54 2006: ^[[33m*^[[39;49m Skipping already
> > loaded module ehci_hcd.
>
> All harmless. Caused by discover trying to do the same thing as already
> done by udev. Again, uninstalling discover will get rid of the messages.
Does this mean that it should have been used in the installer (to identify
the display hardware for X) but then not installed in the final system?
I have uninstalled it on the assumption that it overlaps with what
udev is doing beforehand.
This reminded me of another oddity which might be install related...
Whenever I add/remove packages with aptitude, it gives me a list
of about 80 packages which are being 'held back', and I know I have
not knowingly asked for any packages to be held back. Is that normal?
> Is it OK if we close your report? It seems to me that all issues have been
> sufficiently covered by now.
>
> With all the problems you've had (they do add up a bit), you may want to
> think about installing once more using a current daily build. As I've
> said, we've fixed a lot of errors that you encountered and your reports
> have really helped with that. It may help you get a "cleaner" system in
> the long run.
Sure. I have been keeping a list of everything I needed to do, so it
shouldn't be too hard to get back to where I am. And it will have
the advantage of letting me start a new install report if there
is anything else to bring up...
Thanks for all the advice.
Regards,
DigbyT
--
Digby R. S. Tarvin digbyt(at)digbyt.com
http://www.digbyt.com
Reply to: