Am Donnerstag, den 01.12.2005, 10:41 +0100 schrieb Roger Grosswiler:
Am Mittwoch, den 30.11.2005, 16:28 -0500 schrieb Dave Jones:
> On Wed, Nov 30, 2005 at 10:06:29PM +0100, Roger Grosswiler wrote:
> > hey, hey...
> > after struggling, i got my card up - but still not online. Dmesg now
> > says:
> > ndiswrapper version 1.5 loaded (preempt=no,smp=no)
> > ndiswrapper: driver gplus (D-Link,04/09/2004,22.214.171.124) loaded
> > PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
> > ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [LNKD] -> GSI 11 (level,
> > low) -> IRQ 11
> > PCI: Setting latency timer of device 0000:02:00.0 to 64
> > ndiswrapper (IoCreateUnprotectedSymbolicLink:947): --UNIMPLEMENTED--
> > ndiswrapper: using irq 11
> > wlan0: vendor: 'TNET1130'
> > wlan0: ndiswrapper ethernet device 00:0f:3d:59:64:56 using driver gplus,
> > 104C:9066:1186:3B05.5.conf
> > wlan0: encryption modes supported: WEP; TKIP with WPA
> > iiiiiihaaaaaaaaaaaaaaa!!!!!!! it really was acpi messing it up! acpi=0
> > on boot resolved it.
> acpi=0 does nothing at all. It's not a valid option.
> You can see this by the fact you still have ACPI: lines in your dmesg.
*sigh* i was to early, thanks dave - in this case, the noapic option
must have done the trick - or i was even a lucky guy :-D
But, even if i have my card now - i don't get the device to set it
ok, got it now working. it is really a pig, like already said. ifconfig
-a told me later, that there exist a device called wlan0 -
so, as a first step, i called it manually with ifconfig wlan0 inet
[ipadress] netmask [netmask] up -> this worked fine.
afterwards, it was also known in system-config-network, so i could do
the rest there.