On Tue, Oct 15, 2002 at 07:10:16AM -0500, Jamin W. Collins wrote:
>
> It may be that the system is trying to load the prism2_cs module to bring
> up the interface, which in turn trys to load the ds module, prior to
> pcmcia service being started. Do you have wlan0 in /etc/network/interfaces
> con
On Tue, 15 Oct 2002 07:39:28 -0400 James Hughes <[EMAIL PROTECTED]> wrote:
> As you can see, all the elements are there for things to work:
I'll accept that.
> # Aliases to tell insmod/modprobe which module to use when bringing up
> # the wlan0 interface.
> alias wlan0 prism2_cs
>
> So, why is
On Sun, Oct 13, 2002 at 10:38:28AM -0500, Jamin W. Collins wrote:
> On Sat, Oct 12, 2002 at 11:54:09PM -0400, James Hughes wrote:
>
> > I have PCIC=i82365, which, again, works. Can you explain why
> > yenta_socket is the better option?
>
> Based on your previously supplied output, it doesn't app
James Hughes wrote:
> On Sat, Oct 12, 2002 at 10:08:36PM -0500, Jamin W. Collins wrote:
> Sorry, should have noted in previous mail, but...
>
>>I'm no expert, but I believe this is because you don't have a socket
>>driver loaded. Based on the kernel listed in your output, you should
>>probably b
On Sat, Oct 12, 2002 at 11:54:09PM -0400, James Hughes wrote:
> I have PCIC=i82365, which, again, works. Can you explain why
> yenta_socket is the better option?
Based on your previously supplied output, it doesn't appear to be
working. I say this because the ds.o module fails to load claiming t
5 matches
Mail list logo