hello guys,

I have a Sony Vaio FS980, with an Intel Wireless (ipw2200).
the firmware is correctly installed
----------
/lib/firmware/LICENSE.ipw2200-fw
/lib/firmware/ipw2200-bss.fw
/lib/firmware/ipw2200-ibss.fw
/lib/firmware/ipw2200-sniffer.fw
----------

and the kernel already comes with the ipw module.

Now, about 50% of the time, when I boot the box, and I do an iwconfig, I come up with this:
----------
lo no wireless extensions.

peth0 no wireless extensions.

eth1 IEEE 802.11b ESSID:"crap"
Mode:Managed Frequency:2.437 GHz Access Point: 00:0F:3D:5B:F7:C2
Bit Rate:11 Mb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thrff Fragment thrff
Encryption key:AFAF-AFAF-AFAF-AFAF-AFAF-AFAF-A6 Security mode:restricted
Power Managementff
Link Quality=83/100 Signal level=-47 dBm Noise level=-86 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

sit0 no wireless extensions.

vif0.0 no wireless extensions.

eth0 no wireless extensions.

vif0.1 no wireless extensions.

veth1 no wireless extensions.

vif0.2 no wireless extensions.

veth2 no wireless extensions.

vif0.3 no wireless extensions.

veth3 no wireless extensions.

xenbr0 no wireless extensions.
-----------


Which is FINE, and works perfect.
however, the other 50% of the time, I don't get "eth1" as my wireless interface, but something called "peth0"

and there is "no chance in hell boiled over" that I can get peth0 to do ANYTHING with the network. everything works exactly as the eth1, regarding the wireless info, and iwconfig looks same, and the cell is recognized, and authenticated, all fine, and I can give it an IP, and I can add a default route

but ZILCH, no pings anywhere, no traffic anywhere.

the only thing I can do, is keep rebooting, till by chance I get "eth1" in the iwconfig.
then everything works.

I hope someone can shed some light into this, and/or help me get rid of "peth0" , which I cannot even find in any device.

I found only 3 references in elgoog about peth0, one of them is by some brainiac ( look for felipe alfaro blog ) that seems to know what he's doing, however, all what he talks about in his page is just academic nosh that has no resemblance, nor intuitive application in the real world.

I understand peth0 (which also appears when eth1 is present I note) is a virtual network interface - are you by any chance using Xen?

This is probably a red herring - you need to know why eth1 dosn't always show up.

# dmesg | grep ipw2200

when it does and dosn't show up.

My guess is the interface will show up in iwconfig after you modprobe the driver.

if I am using Xen , its not by choice, but by design, i.e. I installed FC6, and installed the ipw firmware, and have been updating to the latest versions of everything as it shows up in the package manager (uname -a: Linux yuko.servermasters.com 2.6.18-1.2849.fc6xen #1 SMP Fri Nov 10 13:56:52 EST 2006 i686 i686 i386 GNU/Linux )
(also I dunno why it chose to be SMP, as my box is not SMP)

but I didn't click on any menu that says "use xen". in fact, I have an idea what it is, (an abstraction layer to provide multiple virtual machines), but I don't really need it.


my dmesg fills up with wireless packet messages, etc, so nothing is shown atm of any value, but one thing I can do is "grep -i ipw /var/log/messages"

here is the last 4 boots. (the third boot was crapped (peth0 showing in iwconfig), thats why I rebooted again to get eth1 working) so I can come and post here.
----------------------
Dec 2 01:01:04 yuko kernel: ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.1.2kmprq
Dec 2 01:01:04 yuko kernel: ipw2200: Copyright(c) 2003-2006 Intel Corporation
Dec 2 01:01:04 yuko kernel: ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
Dec 2 01:01:04 yuko kernel: ipw2200: Detected geography ZZM (11 802.11bg channels, 0 802.11a channels)
Dec 2 01:10:18 yuko kernel: ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.1.2kmprq
Dec 2 01:10:18 yuko kernel: ipw2200: Copyright(c) 2003-2006 Intel Corporation
Dec 2 01:10:18 yuko kernel: ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
Dec 2 01:10:18 yuko kernel: ipw2200: Detected geography ZZM (11 802.11bg channels, 0 802.11a channels)
Dec 2 07:47:31 yuko kernel: ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.1.2kmprq
Dec 2 07:47:31 yuko kernel: ipw2200: Copyright(c) 2003-2006 Intel Corporation
Dec 2 07:47:31 yuko kernel: ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
Dec 2 07:47:31 yuko kernel: ipw2200: Detected geography ZZM (11 802.11bg channels, 0 802.11a channels)
Dec 2 09:12:12 yuko kernel: ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.1.2kmprq
Dec 2 09:12:12 yuko kernel: ipw2200: Copyright(c) 2003-2006 Intel Corporation
Dec 2 09:12:12 yuko kernel: ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
Dec 2 09:12:12 yuko kernel: ipw2200: Detected geography ZZM (11 802.11bg channels, 0 802.11a channels)
Dec 2 09:14:36 yuko kernel: ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.1.2kmprq
Dec 2 09:14:36 yuko kernel: ipw2200: Copyright(c) 2003-2006 Intel Corporation
Dec 2 09:14:36 yuko kernel: ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
Dec 2 09:14:36 yuko kernel: ipw2200: Detected geography ZZM (11 802.11bg channels, 0 802.11a channels)
--------------------

nothing there that shows me its bound to eth1.

Ergo, then "grep -i eth1 /var/log/messages"

---------------------------
Dec 2 01:01:04 yuko kernel: e100: eth1: e100_probe: addr 0xb0107000, irq 21, MAC addr 00:13:A9:30:55:97
Dec 2 01:11:11 yuko avahi-daemon[2264]: New relevant interface eth1.IPv4 for mDNS.
Dec 2 01:11:11 yuko avahi-daemon[2264]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.0.100.
Dec 2 01:11:11 yuko avahi-daemon[2264]: Registering new address record for 192.168.0.100 on eth1.
Dec 2 01:11:11 yuko kernel: eth1: NETDEV_TX_BUSY returned; driver should report queue full via ieee_device->is_queue_full.
Dec 2 01:11:12 yuko avahi-daemon[2264]: New relevant interface eth1.IPv6 for mDNS.
Dec 2 01:11:12 yuko avahi-daemon[2264]: Joining mDNS multicast group on interface eth1.IPv6 with address fe80::216:6fff:fe82:b9e7.
Dec 2 01:11:12 yuko avahi-daemon[2264]: Registering new address record for fe80::216:6fff:fe82:b9e7 on eth1.
Dec 2 03:08:08 yuko avahi-daemon[2264]: Leaving mDNS multicast group on interface eth1.IPv6 with address fe80::216:6fff:fe82:b9e7.
Dec 2 03:08:08 yuko avahi-daemon[2264]: Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.0.100.
Dec 2 07:53:01 yuko avahi-daemon[2229]: New relevant interface eth1.IPv4 for mDNS.
Dec 2 07:53:01 yuko avahi-daemon[2229]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.0.100.
Dec 2 07:53:01 yuko avahi-daemon[2229]: Registering new address record for 192.168.0.100 on eth1.
Dec 2 07:53:01 yuko kernel: eth1: NETDEV_TX_BUSY returned; driver should report queue full via ieee_device->is_queue_full.
Dec 2 07:53:02 yuko avahi-daemon[2229]: New relevant interface eth1.IPv6 for mDNS.
Dec 2 07:53:02 yuko avahi-daemon[2229]: Joining mDNS multicast group on interface eth1.IPv6 with address fe80::216:6fff:fe82:b9e7.
Dec 2 07:53:02 yuko avahi-daemon[2229]: Registering new address record for fe80::216:6fff:fe82:b9e7 on eth1.
Dec 2 09:12:13 yuko kernel: e100: eth1: e100_probe: addr 0xb0107000, irq 21, MAC addr 00:13:A9:30:55:97
Dec 2 09:15:20 yuko avahi-daemon[2229]: New relevant interface eth1.IPv4 for mDNS.
Dec 2 09:15:20 yuko avahi-daemon[2229]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.0.100.
Dec 2 09:15:20 yuko avahi-daemon[2229]: Registering new address record for 192.168.0.100 on eth1.
Dec 2 09:15:20 yuko kernel: eth1: NETDEV_TX_BUSY returned; driver should report queue full via ieee_device->is_queue_full.
Dec 2 09:15:22 yuko avahi-daemon[2229]: New relevant interface eth1.IPv6 for mDNS.
Dec 2 09:15:22 yuko avahi-daemon[2229]: Joining mDNS multicast group on interface eth1.IPv6 with address fe80::216:6fff:fe82:b9e7.
Dec 2 09:15:22 yuko avahi-daemon[2229]: Registering new address record for fe80::216:6fff:fe82:b9e7 on eth1.
------------------------

the : NETDEV_TX_BUSY message, I get that when I execute my iwconfig commands to set the address, etc, I have a small shell script as follows:
---------------------
[root@yuko ~]# cat home_net.sh
/sbin/iwconfig eth1 essid crap
/sbin/iwconfig eth1 channel 6
/sbin/iwconfig eth1 key restricted [1] AFAF-AFAF-AFAF-AFAF-AFAF-AFAF-A6
ifconfig eth1 192.168.0.100 netmask 255.255.255.0 up
#/sbin/iwconfig peth0 essid crap
#/sbin/iwconfig peth0 channel 6
#/sbin/iwconfig peth0 key restricted [1] AFAF-AFAF-AFAF-AFAF-AFAF-AFAF-A6
#ifconfig peth0 192.168.0.100 netmask 255.255.255.0 up
#__tmp1804289383
#/sbin/iwconfig __tmp1804289383 essid crap
#/sbin/iwconfig __tmp1804289383 channel 6
#/sbin/iwconfig __tmp1804289383 key restricted [1] AFAF-AFAF-AFAF-AFAF-AFAF-AFAF-A6
#ifconfig __tmp1804289383 192.168.0.100 netmask 255.255.255.0 up
route add default gw 192.168.0.1
----------------------

as you can see, I have also tried doing the same for peth0, but no luck.

when peth0 shows as "wireless enabled" in the iwconfig command output, then eth1 shows up as " no wireless extensions...." i.e. it looks exactly the same, but the wireless world switches to peth0, which is, Im sorry to say " a DUD "

HAHAH
cheers, thanks for the helpage.

EDIT: [root@yuko ~]# lsmod | grep ipw
ipw2200 112549 0
ieee80211 34825 1 ipw2200
this shows up exactly the same, no matter if it works with eth1, or peth0. i.e. the driver is always loaded at boot, just fine.

EDIT #2: here is a "grep peth0 /var/log/messages"
---------------------
Dec 2 01:01:15 yuko kernel: peth0: Setting MAC to fe:ff:ff:ff:ff:ff
Dec 2 01:01:15 yuko kernel: ADDRCONF(NETDEV_UP): peth0: link is not ready
Dec 2 01:01:25 yuko kernel: device peth0 entered promiscuous mode
Dec 2 01:01:25 yuko kernel: audit(1165017685.493:4): dev=peth0 prom=256 old_prom=0 auid=4294967295
Dec 2 01:01:26 yuko kernel: xenbr0: port 2(peth0) entering disabled state
Dec 2 01:10:29 yuko kernel: ADDRCONF(NETDEV_UP): peth0: link is not ready
Dec 2 01:10:39 yuko kernel: device peth0 entered promiscuous mode
Dec 2 01:10:39 yuko kernel: audit(1165018239.379:4): dev=peth0 prom=256 old_prom=0 auid=4294967295
Dec 2 01:10:40 yuko kernel: xenbr0: port 2(peth0) entering disabled state
Dec 2 07:47:42 yuko kernel: ADDRCONF(NETDEV_UP): peth0: link is not ready
Dec 2 07:47:52 yuko kernel: device peth0 entered promiscuous mode
Dec 2 07:47:52 yuko kernel: audit(1165042072.684:4): dev=peth0 prom=256 old_prom=0 auid=4294967295
Dec 2 07:47:53 yuko kernel: xenbr0: port 2(peth0) entering disabled state
Dec 2 09:12:21 yuko kernel: peth0: Setting MAC to fe:ff:ff:ff:ff:ff
Dec 2 09:12:22 yuko kernel: ADDRCONF(NETDEV_UP): peth0: link is not ready
Dec 2 09:12:32 yuko kernel: device peth0 entered promiscuous mode
Dec 2 09:12:32 yuko kernel: audit(1165047152.195:4): dev=peth0 prom=256 old_prom=0 auid=4294967295
Dec 2 09:12:33 yuko kernel: xenbr0: port 2(peth0) entering disabled state
Dec 2 09:14:47 yuko kernel: ADDRCONF(NETDEV_UP): peth0: link is not ready
Dec 2 09:14:57 yuko kernel: device peth0 entered promiscuous mode
Dec 2 09:14:57 yuko kernel: audit(1165047297.517:4): dev=peth0 prom=256 old_prom=0 auid=4294967295
Dec 2 09:14:58 yuko kernel: xenbr0: port 2(peth0) entering disabled state
------------------

funny thing, I notice that in all boots where peth0 is bound to the wireless, and nothing works,
this line appears in messages:
..... yuko kernel: peth0: Setting MAC to fe:ff:ff:ff:ff:ff
and when eth1 is bound to wireless, then that peth0 info line does not appear.

What is in /var/log/xen ?
http://fedora.redhat.com/docs/releas...sn-Kernel.html
You seem to have the virtualisation kernel installed instead of the native one. It may be that you are running an FC6 VM in XEN running in FC6 host. But this is not the default behavior - leading to questions about how you installed FC6.

Anyway:

What xen does is relabel the network interfaces so that the MAC address comes under peth0, peth1 etc and the rest of the information comes under veth0, veth1 etc.

veth1 is supposed to get renamed as eth1

As pointed out earlier, your peth0 shows up all the time ... presumably corresponding to the mac addr. of your on-board network card. peth1 will hold the mac address of your wireless card. Check if veth1 exists when eth1 dosn't.

Xen handles virtual-hardware network connections via a bridge-process (xenbr0) which is quite complex but allows multiple virtual machines to believe they have exculsive use of the hardware. Keeps 'em happy.

Wireless networking is tricky over the bridging method, and is better handled via routing instead. However, as I have not done this (nor am I contemplating doing this) I don't know how one would route a wireless connection from a virtual machine. However - this should be the direction of your research if you don't want to reinstall FC6.

http://fedora.redhat.com/docs/releas...alization.html
http://fedoraproject.org/wiki/FedoraXenQuickstartFC6

I'd check the grub menue to see if there is a non-xen boot option.
Failing that - possibly installing a plain i686 (say) kernel and/or uninstalling the kernel-xen package. (Or reinstall, making sure the native kernel is installed.)

The SMP part is a red herring - fedora is no longer issues a seperate kernel for smp and up systems. The installer detects which is needed and sets the appropriate bits.

But here's something I'd like to clarify - when eth1 is not present, do you see peth0 listed with your wireless card statistics?

this is the latest, since my boot up this morning, which was a successful eth1 ("yiipeee , I got net") boot
---------------
[2006-12-03 11:21:32 xend 2557] INFO (SrvDaemon:283) Xend Daemon started
[2006-12-03 11:21:32 xend 2557] INFO (SrvDaemon:287) Xend changeset: unavailable .
[2006-12-03 11:21:32 xend.XendDomainInfo 2557] DEBUG (XendDomainInfo:212) XendDomainInfo.recreate({'paused': 0, 'cpu_time': 17575441233L, 'ssidref': 0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'shutdown_reason': 0, 'dying': 0, 'dom': 0, 'mem_kb': 953848, 'maxmem_kb': -4, 'max_vcpu_id': 0, 'crashed': 0, 'running': 1, 'shutdown': 0, 'online_vcpus': 1, 'blocked': 0})
[2006-12-03 11:21:32 xend.XendDomainInfo 2557] INFO (XendDomainInfo:224) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000.
[2006-12-03 11:21:32 xend.XendDomainInfo 2557] WARNING (XendDomainInfo:246) No vm path in store for existing domain 0
[2006-12-03 11:21:32 xend.XendDomainInfo 2557] DEBUG (XendDomainInfo:712) Storing VM details: {'shadow_memory': '0', 'uuid': '00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart', 'on_poweroff': 'destroy', 'name': 'Domain-0', 'xend/restart_count': '0', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '932', 'on_crash': 'restart', 'maxmem': '932'}
[2006-12-03 11:21:32 xend.XendDomainInfo 2557] DEBUG (XendDomainInfo:747) Storing domain details: {'cpu/0/availability': 'online', 'memory/target': '954368', 'name': 'Domain-0', 'console/limit': '1048576', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0'}
[2006-12-03 11:21:32 xend 2557] DEBUG (XendDomain:153) number of vcpus to use is 0
[2006-12-03 11:21:32 xend 2557] INFO (SrvServer:116) unix path=/var/lib/xend/xend-socket
[2006-12-03 11:21:32 xend.XendDomainInfo 2557] DEBUG (XendDomainInfo:933) XendDomainInfo.handleShutdownWatch
[root@yuko xen]#
-----------------


they both behave exactly the same, but reversed.

i.e.:
- when my net does not work (and I execute my scripty uncommenting peth0), I have:
-----------------------------
[root@yuko xen]# iwconfig
lo no wireless extensions.

peth0 IEEE 802.11b ESSID:"crap"
Mode:Managed Frequency:2.437 GHz Access Point: 00:0F:3D:5B:F7:C2
Bit Rate:11 Mb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thrff Fragment thrff
Encryption key:AFAF-AFAF-AFAF-AFAF-AFAF-AFAF-A6 Security mode:restricted
Power Managementff
Link Quality=86/100 Signal level=-43 dBm Noise level=-88 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

eth1 no wireless extensions.

sit0 no wireless extensions.

vif0.0 no wireless extensions.

eth0 no wireless extensions.

vif0.1 no wireless extensions.

veth1 no wireless extensions.

vif0.2 no wireless extensions.

veth2 no wireless extensions.

vif0.3 no wireless extensions.

veth3 no wireless extensions.

xenbr0 no wireless extensions.
-----------------------


and when my network WORKS, I get:

-----------------------
[root@yuko xen]# iwconfig
lo no wireless extensions.

peth0 no wireless extensions.

eth1 IEEE 802.11b ESSID:"crap"
Mode:Managed Frequency:2.437 GHz Access Point: 00:0F:3D:5B:F7:C2
Bit Rate:11 Mb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thrff Fragment thrff
Encryption key:AFAF-AFAF-AFAF-AFAF-AFAF-AFAF-A6 Security mode:restricted
Power Managementff
Link Quality=86/100 Signal level=-43 dBm Noise level=-88 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

sit0 no wireless extensions.

vif0.0 no wireless extensions.

eth0 no wireless extensions.

vif0.1 no wireless extensions.

veth1 no wireless extensions.

vif0.2 no wireless extensions.

veth2 no wireless extensions.

vif0.3 no wireless extensions.

veth3 no wireless extensions.

xenbr0 no wireless extensions.
-----------------------


to tell you the truth, they seem to "alternate" mostly, one boot works, the next does not, then it works, then it does not, etc etc. but sometimes it gets stuck in non-working-mode, for at least 5 boots, and in other cases, like this morning, I had a successful boot from the getgo, which would indicate 2 successful boots in a row (last night session, and now's).

Have you tried explicitly shutting down eth1 (when it works) before shutting down?
It is possible that fedora's network service script is just toggling stuff.

just tried it:
[root@yuko ~]# ifdown eth1
usage: ifdown <device name>
[root@yuko ~]#

strange.

i go sleep now, and will post more in the morning. will do an ifconfig eth1 down before the init 0.
cheers.

OKay

so, I took my laptop to the office today, and I wanted to get the standard "eth0", plugged into my ethernet connection, and what do I see ? ZILCH.
I must have tried 10 reboots, ifups, ifdowns (which worked), used neat to unconfigure and reconfigure everything, and ZILCH. I could surely get an IP on the box, but absolutely no network traffic.

So, I started thinking about this xen issue, when I came across: /etc/xen/xend-config.sxp
and upon editing this file, I found this line:
(network-script network-bridge)

HMMMMMMM (suspect crap level 9 deep)

Ergo, I commented out the line, it now looks like this:
#(network-script network-bridge)


Then, I rebooted the box, and VOILLA, eth0 works perfect.

I am now dying to get home to try out the wireless. If it works, then that was it, [and a large
BONK in the head to the guys that decided to enable xen by default. When I am sure only 0.1% of the users will actually use it.]

OK guys,

well, "the DUD interface" peth0 is now not "binding" anylonger to the wireless.
Now the wireless is toggling still, between eth1, and "__tmp1804289383"
(iwconfig output

__tmp1804289383 IEEE 802.11b ESSID:"crap"
Mode:Managed Frequency:2.437 GHz Access Point: 00:0F:3D:5B:F7:C2
Bit Rate:11 Mb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thrff Fragment thrff
Encryption key:AFAF-AFAF-AFAF-AFAF-AFAF-AFAF-A6 Security mode:restricted
Power Managementff
Link Quality=92/100 Signal level=-36 dBm Noise level=-88 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

peth0 does not even show up.

But at least , both eth1, and __tmp.... now work, so I can always have a networked machine.
I guess I will have to add an alias in /etc/modprobe.conf or something, to get it finally fixed up on eth1, dunno, I will investigate this further.

For now I am happy, after commenting that line in xend config.

salud everyone, thanks Simon.

Well OK - but you're still just using xen.

Check the grub menue that you do not have the normal system kernel installed. If you do, then set this as your default. If you don't, then use yum to install the system kernel and edit grub.conf accordingly.

Then all this peth0 stuff will vanish.

Yup Simon Bridge is correct. You are booting into a xen kernel. The reason peth0 won't work is because xen by default looks for eth0. If it doesn't find it networking won't come up. When your machine boots check the menu closely. You should see a choice of Fedora Core (2.6.18-1.2849.fc6) and Fedora Core (2.6.18-1.2849.fc6xen) or something similar depending on your kernel version. Choose the one that does not have xen in it.

You can change the default by editing /boot/grub/menu.lst and changing the line default=<some number> The first line that starts with title would be 0, the 2nd line that starts with title would be 1 and so on in the <some number> part above. Be sure and take out the <> as well.

Regarding your ipw2200 if it still acts flakey try adding irqpoll to the end of the line that starts with kernel in the section that you choose for your default. If that doesn't work try adding pci=routeirq and removing the irqpoll entry. On mine I occassionaly have to remove the eth1 network and device entries after certain updates (not sure which ones trigger this-probably dbus)and reboot so that it reloads the driver.

hth