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,6.0.0.18) 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.
but: then i wanted to install the nic wlan0 with hardware ndiswrapper.
?huh? there is none? so, now i still cannot install my wireless-interface, but one step more for me :-D
Roger
ah, yeah, if you have an ideahow to resolve my issue, fell free to tell it :-D - i would better say, i appreciate it ;-)
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,6.0.0.18) 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.
Dave
The only way I got my card to work was to add the SSID in the network-scripts config file for the site I wanted to connect to. Otherwise all I got was a "no link present " message when I tried to activate with /sbin/ifup. My card is a Linksys WPC54g v2 with a TI acx111 chipset using the same driver TNET1130 as your D-link card. You might try and get the acx100 projects stuff to work at http://acx100.erley.org/ Although some of it is GPL code you still need the firmware from D-link which is not GPL.
From: Dave Jones davej@redhat.com Reply-To: For testers of Fedora Core development releases fedora-test-list@redhat.com To: For testers of Fedora Core development releases fedora-test-list@redhat.com Subject: Re: ndiswrapper 1.5 Date: Wed, 30 Nov 2005 16:28:03 -0500
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,6.0.0.18) 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.
Dave-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
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,6.0.0.18) 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.
Dave
*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 up :-(
Roger
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,6.0.0.18) 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.
Dave*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 up :-(
Roger
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 - system-config-network didn't.
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.
Roger
On Thu, 2005-12-01 at 11:50 +0100, Roger Grosswiler wrote: [snip]
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 - system-config-network didn't.
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.
I think I read somewhere that FC4's network scripts have a bit of trouble handling wlan0. However, you can tell ndiswrapper to use a different device name. So it is possible to let ndiswrapper call the new device eth1 instead of wlan0. To make this happen stick this line in /etc/modprobe.conf:
options ndiswrapper if_name=eth1
Hope this helps.
Regards, Patrick
On 12/1/05, Patrick fedora@puzzled.xs4all.nl wrote:
On Thu, 2005-12-01 at 11:50 +0100, Roger Grosswiler wrote: [snip]
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 - system-config-network didn't.
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.
I think I read somewhere that FC4's network scripts have a bit of trouble handling wlan0. However, you can tell ndiswrapper to use a different device name. So it is possible to let ndiswrapper call the new device eth1 instead of wlan0. To make this happen stick this line in /etc/modprobe.conf:
options ndiswrapper if_name=eth1
No, no problem with the name wlan0 here. I can't remember how I got system-config-network to notice it -- possibly I manually modprobed ndiswrapper once.
MEF
-- __ Mary Ellen Foster __ http://homepages.inf.ed.ac.uk/mef/ __ "One of the main causes of the fall of the Roman Empire was that, lacking zero, they had no way to indicate successful termination of their C programs." (Robert Firth)
Am Donnerstag, den 01.12.2005, 13:58 +0000 schrieb Mary Ellen Foster:
On 12/1/05, Patrick fedora@puzzled.xs4all.nl wrote:
On Thu, 2005-12-01 at 11:50 +0100, Roger Grosswiler wrote: [snip]
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 - system-config-network didn't.
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.
I think I read somewhere that FC4's network scripts have a bit of trouble handling wlan0. However, you can tell ndiswrapper to use a different device name. So it is possible to let ndiswrapper call the new device eth1 instead of wlan0. To make this happen stick this line in /etc/modprobe.conf:
options ndiswrapper if_name=eth1
No, no problem with the name wlan0 here. I can't remember how I got system-config-network to notice it -- possibly I manually modprobed ndiswrapper once.
MEF
-- __ Mary Ellen Foster __ http://homepages.inf.ed.ac.uk/mef/ __ "One of the main causes of the fall of the Roman Empire was that, lacking zero, they had no way to indicate successful termination of their C programs." (Robert Firth)
i manually modprobed several times - perhaps the ndiswrapper -m was not a good choice....but now, it is working flawlessy
Rog
On Thu, 2005-12-01 at 15:15 +0100, Roger Grosswiler wrote:
Am Donnerstag, den 01.12.2005, 13:58 +0000 schrieb Mary Ellen Foster:
On 12/1/05, Patrick fedora@puzzled.xs4all.nl wrote:
On Thu, 2005-12-01 at 11:50 +0100, Roger Grosswiler wrote: [snip]
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 - system-config-network didn't.
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.
I think I read somewhere that FC4's network scripts have a bit of trouble handling wlan0. However, you can tell ndiswrapper to use a different device name. So it is possible to let ndiswrapper call the new device eth1 instead of wlan0. To make this happen stick this line in /etc/modprobe.conf:
options ndiswrapper if_name=eth1
No, no problem with the name wlan0 here. I can't remember how I got system-config-network to notice it -- possibly I manually modprobed ndiswrapper once.
MEF
-- __ Mary Ellen Foster __ http://homepages.inf.ed.ac.uk/mef/ __ "One of the main causes of the fall of the Roman Empire was that, lacking zero, they had no way to indicate successful termination of their C programs." (Robert Firth)
i manually modprobed several times - perhaps the ndiswrapper -m was not a good choice....but now, it is working flawlessy
Rog
After running yum update last night and installing the latest kernel it broke my ndiswrapper. No prob.. I would jump to my ndiswrapper source and make && make install.
.....Crud .... errors....
Went and downloaded ndiswrapper-1.6 and did the make && make install and all is well.
We have WEP encryption at our office and I had to modify the /etc/sysconfig/network-scripts/ifup-wireless script with the following
~~~~~~~~~~~~~~~snip~~~~~~~~~~~~~~~ if [ -n "$KEY" -o -n "$KEY1" -o -n "$KEY2" -o -n "$KEY3" -o -n "$KEY4" ] ; then [ -n "$KEY1" ] && iwconfig $DEVICE key [1] $KEY1 [ -n "$KEY2" ] && iwconfig $DEVICE key [2] $KEY2 [ -n "$KEY3" ] && iwconfig $DEVICE key [3] $KEY3 [ -n "$KEY4" ] && iwconfig $DEVICE key [4] $KEY4 [ -n "$DEFAULTKEY" ] && iwconfig $DEVICE key [${DEFAULTKEY}] [ -n "$KEY" ] && iwconfig $DEVICE key $KEY open else iwconfig $DEVICE key off ~~~~~~~~~~~~~~snip~~~~~~~~~~~~~~~ I had to add "open" to be able to use the network configuration gui.
-James
Am Donnerstag, den 01.12.2005, 08:37 -0600 schrieb James:
On Thu, 2005-12-01 at 15:15 +0100, Roger Grosswiler wrote:
Am Donnerstag, den 01.12.2005, 13:58 +0000 schrieb Mary Ellen Foster:
On 12/1/05, Patrick fedora@puzzled.xs4all.nl wrote:
On Thu, 2005-12-01 at 11:50 +0100, Roger Grosswiler wrote: [snip]
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 - system-config-network didn't.
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.
I think I read somewhere that FC4's network scripts have a bit of trouble handling wlan0. However, you can tell ndiswrapper to use a different device name. So it is possible to let ndiswrapper call the new device eth1 instead of wlan0. To make this happen stick this line in /etc/modprobe.conf:
options ndiswrapper if_name=eth1
No, no problem with the name wlan0 here. I can't remember how I got system-config-network to notice it -- possibly I manually modprobed ndiswrapper once.
MEF
-- __ Mary Ellen Foster __ http://homepages.inf.ed.ac.uk/mef/ __ "One of the main causes of the fall of the Roman Empire was that, lacking zero, they had no way to indicate successful termination of their C programs." (Robert Firth)
i manually modprobed several times - perhaps the ndiswrapper -m was not a good choice....but now, it is working flawlessy
Rog
After running yum update last night and installing the latest kernel it broke my ndiswrapper. No prob.. I would jump to my ndiswrapper source and make && make install.
.....Crud .... errors....
Went and downloaded ndiswrapper-1.6 and did the make && make install and all is well.
We have WEP encryption at our office and I had to modify the /etc/sysconfig/network-scripts/ifup-wireless script with the following
if [ -n "$KEY" -o -n "$KEY1" -o -n "$KEY2" -o -n "$KEY3" -o -n "$KEY4" ] ; then [ -n "$KEY1" ] && iwconfig $DEVICE key [1] $KEY1 [ -n "$KEY2" ] && iwconfig $DEVICE key [2] $KEY2 [ -n "$KEY3" ] && iwconfig $DEVICE key [3] $KEY3 [ -n "$KEY4" ] && iwconfig $DEVICE key [4] $KEY4 [ -n "$DEFAULTKEY" ] && iwconfig $DEVICE key [${DEFAULTKEY}] [ -n "$KEY" ] && iwconfig $DEVICE key $KEY open else iwconfig $DEVICE key off ~~~~~~~~~~~~~~snip~~~~~~~~~~~~~~~ I had to add "open" to be able to use the network configuration gui.
Interesting, when i was trying yesterday ndiswrapper 1.6 i got errors according to libusb (which is installed on my system) so i fell back to 1.5...
Rog
-
Dave Jones -
Don Springall -
James -
Mary Ellen Foster -
Patrick -
Roger Grosswiler