Bug#363331: Fwd: Re: Bug#363331: installation-reports
On Wed, Apr 19, 2006 at 02:20:06AM +0200, Frans Pop wrote:
> On Wednesday 19 April 2006 01:42, Digby Tarvin wrote:
> > But the modprobe.d method doesn't work on my system for installation or
> > post installation, and I think there is a good chance the two issues
> > are be related.
>
[snip]
> In other words: it creates a /etc/modprobe.conf and /etc/modules.conf.
> IIRC modules.conf is only for 2.4 kernels, so that leaves modprobe.conf.
>
> Hmm. Actually, I think I've read that modprobe.conf overrules anything
> that is in /etc/modprobe.d...
> Could you check if that is the case if you use the second method? Is there
> a file (maybe empty) /etc/modprobe.conf that could overrule what you've
> manually put in /etc/modprobe.d/libata?
> Could that also be the case on the installed system?
Bingo!! you got it!!
I tried booting from the Beta 2 install disk with 'install26 BOOT_DEBUG=3'
and per SataAtapiHowto, but then found that there was indeed a
a /etc/modprobe.conf file in existence, so used
echo "options libata atapi_enabled=1" >>/etc/modprobe.conf
instead of following the instructions about modprobe.d, and then
when it searches for the CD-Rom, it finds it!!
Unfortunately there was no /etc/modprobe.conf on the installed system,
so I guess it isn't the same problem after all. But at least we have
a workaround for the install problem.
I can also report that I have now succeeded in getting the wireless
interface to work (at least in the installed system), and you were
quite right about the firmware also. The procedure was:
Download appropriate firmware (in this case ipw2200-fw-2.4.tgz) from
http://ipw2200.sourceforge.net/firmware.php
unpack archive into /lib/firmware
Change '/etc/network/interfaces' replacing all instances
of eth0 (the UTP device) with eth2 (the Intel wireless..)
It might be nice if there were an instruction on how to add the firmware
files to the install CD, for anyone that only has the wireless i/f
available.
Regards,
DigbyT
--
Digby R. S. Tarvin digbyt(at)digbyt.com
http://www.digbyt.com
Reply to: