You can try to get the information from the sysfs.
[rmtzcx@armtzcx01 ~]$ ls -l /sys/class/net/{eth0,wlan0}/device/driver
lrwxrwxrwx 1 root root 0 Feb 14 19:54
/sys/class/net/eth0/device/driver -> ../../../bus/pci/drivers/e1000e
lrwxrwxrwx 1 root root 0 Feb 14 19:02
/sys/class/net/wlan0/device/driver ->
../../../../bus/pci/drivers/iwlagn
--
Rodolfo
On Mon, Feb 14, 2011 at 6:25 PM, DaZZa <[email protected]> wrote:
>
> On Mon, Feb 14, 2011 at 7:40 PM, Tony Sceats <[email protected]> wrote:
> > I know you found the answer already but ethtool -i <interface> can also
> > work and is very simple
> >
> > Just thought I'd throw that in :)
>
> [root@dev-app01 ~]# ethtool -i seth0
> Cannot get driver information: Operation not supported
> [root@dev-app01 ~]#
>
> :-)
>
> DaZZa (stupid bloody Microsoft!)
> --
> SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
> Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
