Garrett,

I was following a full build (gmake world && gmake live) from the Building
SmartOS on SmartOS.

The process you describe I'm well familiar with, and is what I've done,
except that I was tweaking SmartOS to include the zyd driver.  That's not
quite there yet, but instructions I was given were to copy the compiled
driver up to the global zone from the build tree.  Especially since it's a
USB device.

Your update_drv magic did it's work.  I can see my devices now.

Thanks!!!!

Ben






On Tue, Mar 11, 2014 at 12:28 PM, Garrett D'Amore <[email protected]>wrote:

> You cannot *just edit* /etc/driver_aliases!   These kernel files
> (minor_perm, name_to_major, driver_aliases, and path_to_inst) should never
> *ever* be hand-edited.
>
> You should instead use update_drv.  I do it like this:  update_drv -a -i
> 'newalias' driver
> For example, when I was testing my igb on new hardware:
>
> update_drv -a -i pciex8086,1f45 igb
>
> Btw, you should also not need to build zyd apart from illumos.   You can
> instead do the following for illumos:
>
> cd <workspace>
> cp usr/src/tools/env/illumos.sh  illumos.sh
> vi illumos.sh   # edit to taste... especially the GATE definition needs to
> be edited with your path
> bldenv  illumos.sh  # (or bldenv -d to get a debug build)
> cd usr/src/
> make sgs
> cd uts/intel/zyd
> make
>
> The "zyd" driver (binary) will be in either objs64 or debug64, depending
> on whether you built as debug or not.  This approach works well for most of
> the drivers.  It doesn't work for *all* kernel modules however, and you
> won't be able to lint your tree with pass 2 of lint unless you have done a
> full kernel lint in the same workspace previously.
>
> --
> Garrett D'Amore
> Sent with Airmail
>
> On March 11, 2014 at 9:05:49 AM, Ben Taylor ([email protected])
> wrote:
>
> I'm working on updating the zyd driver.  in the mean time, I'm just
> working on getting it to build out to the distribution.
>
> I've got the driver compiling and getting installed.  I'm copying the
> driver out of my build zone up to the global zone in /kernel/drv/amd64 so I
> don't have to reboot.
>
> Since the zyd driver already had entries in /etc/name_to_major and
> /etc/minor_perm in the global zone, I updated /etc/driver_aliases with the
> usb ids for the devices that worked previously when I was working on the
> driver in the 2007-2008 time frame.
>
> However, the driver is not attaching.
>
> Here's the messages
>
>  2014-03-11T12:02:51.036354+00:00 b8-97-5a-40-66-d3 usba: [ID 912658
> kern.info] USB 2.0 device (usbace,1215) operating at hi speed (USB 2.x)
> on USB 2.0 root hub: device@4, usb_mid2 at bus address 2
> 2014-03-11T12:02:51.036557+00:00 b8-97-5a-40-66-d3 usba: [ID 349649
> kern.info] #011ZyDAS USB2.0 WLAN
> 2014-03-11T12:02:51.036576+00:00 b8-97-5a-40-66-d3 genunix: [ID 936769
> kern.info] usb_mid2 is /pci@0,0/pci1565,3700@12,2/device@4
> 2014-03-11T12:02:51.036601+00:00 b8-97-5a-40-66-d3 genunix: [ID 408114
> kern.info] /pci@0,0/pci1565,3700@12,2/device@4 (usb_mid2) online
> 2014-03-11T12:02:51.036861+00:00 b8-97-5a-40-66-d3 usba: [ID 349649
> kern.info] usba:#011no driver found for interface 0 (nodename:
> 'interface') of ZyDAS USB2.0 WLAN
>
> 2014-03-11T12:03:30.756753+00:00 b8-97-5a-40-66-d3 usba: [ID 912658
> kern.info] USB 2.0 device (usb6891,a727) operating at hi speed (USB 2.x)
> on USB 2.0 root hub: device@4, usb_mid2 at bus address 2
> 2014-03-11T12:03:30.756848+00:00 b8-97-5a-40-66-d3 usba: [ID 349649
> kern.info] #0113COM RUSB10075
> 2014-03-11T12:03:30.756883+00:00 b8-97-5a-40-66-d3 genunix: [ID 936769
> kern.info] usb_mid2 is /pci@0,0/pci1565,3700@12,2/device@4
> 2014-03-11T12:03:30.756916+00:00 b8-97-5a-40-66-d3 genunix: [ID 408114
> kern.info] /pci@0,0/pci1565,3700@12,2/device@4 (usb_mid2) online
> 2014-03-11T12:03:30.757131+00:00 b8-97-5a-40-66-d3 usba: [ID 349649
> kern.info] usba:#011no driver found for interface 0 (nodename:
> 'interface') of 3COM RUSB10075
>
> 2014-03-11T12:05:51.891445+00:00 b8-97-5a-40-66-d3 usba: [ID 912658
> kern.info] USB 2.0 device (usb83a,4505) operating at hi speed (USB 2.x)
> on USB 2.0 root hub: device@4, usb_mid2 at bus address 2
> 2014-03-11T12:05:51.891529+00:00 b8-97-5a-40-66-d3 usba: [ID 349649
> kern.info] #011SMC USB2.0 WLAN
> 2014-03-11T12:05:51.891550+00:00 b8-97-5a-40-66-d3 genunix: [ID 936769
> kern.info] usb_mid2 is /pci@0,0/pci1565,3700@12,2/device@4
> 2014-03-11T12:05:51.891573+00:00 b8-97-5a-40-66-d3 genunix: [ID 408114
> kern.info] /pci@0,0/pci1565,3700@12,2/device@4 (usb_mid2) online
> 2014-03-11T12:05:51.891948+00:00 b8-97-5a-40-66-d3 usba: [ID 349649
> kern.info] usba:#011no driver found for interface 0 (nodename:
> 'interface') of SMC USB2.0 WLAN
>
>  Ideas?  I've verified the usb ids in /etc/driver_aliases and in the
> source.  The driver is loaded (modload -p drv/amd64/zyd), as are the
> net80211 and mac_wifi modules.
>
>
>
> Ben
>   *smartos-discuss* | 
> Archives<https://www.listbox.com/member/archive/184463/=now> 
> <https://www.listbox.com/member/archive/rss/184463/22103350-51080293>|
> Modify<https://www.listbox.com/member/?&;>Your Subscription
> <http://www.listbox.com>
>
>



-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Reply via email to