Hi, Xen-75 doesn''t seem to contain a driver for VT6102 [Rhine-II] (rev 7c) ethernet controller, not only in the dom0 version but even in the bare metal one. Do the drivers available here http://homepage2.nifty.com/mrym3/taiyodo/eng/ have a chance to work with the dom0 kernel? Thanks, Nico
On 27 Oct 2007, at 11:54am, Nico Sabbi wrote:> Xen-75 doesn''t seem to contain a driver for VT6102 [Rhine-II] (rev 7c) > ethernet controller, not only in the dom0 version but even in the > bare metal one. > Do the drivers available here > http://homepage2.nifty.com/mrym3/taiyodo/eng/ > have a chance to work with the dom0 kernel?They should work. I''ve used them on bare metal, but not with dom0. In general, if a device/driver combination works on metal it should work just fine with dom0. dme. -- David Edmondson, Solaris Engineering, http://dme.org
Il Monday 29 October 2007 11:45:05 David Edmondson ha scritto:> On 27 Oct 2007, at 11:54am, Nico Sabbi wrote: > > Xen-75 doesn''t seem to contain a driver for VT6102 [Rhine-II] > > (rev 7c) ethernet controller, not only in the dom0 version but > > even in the bare metal one. > > Do the drivers available here > > http://homepage2.nifty.com/mrym3/taiyodo/eng/ > > have a chance to work with the dom0 kernel? > > They should work. I''ve used them on bare metal, but not with dom0. > > In general, if a device/driver combination works on metal it should > work just fine with dom0. > > dme.I had a problem: the installation (make install ; ./add_drv.sh) proceeded apparently well, but at the next reboot the physical-network services failed because the vfe0 interface wasn''t present: the vfe module wasn''t loaded. How can I make the driver load automatically at startup? isn''t add_drv enough?
On 29 Oct 2007, at 10:49am, Nico Sabbi wrote:> I had a problem: the installation (make install ; ./add_drv.sh) > proceeded apparently well, but at the next reboot the > physical-network services failed because the vfe0 interface > wasn''t present: the vfe module wasn''t loaded. > > How can I make the driver load automatically at startup? > isn''t add_drv enough?Perhaps the driver was installed into a directory which means that it''s only loaded on a metal system. Where does the script put it? dme. -- David Edmondson, Solaris Engineering, http://dme.org
Il Monday 29 October 2007 14:16:26 David Edmondson ha scritto:> On 29 Oct 2007, at 10:49am, Nico Sabbi wrote: > > I had a problem: the installation (make install ; ./add_drv.sh) > > proceeded apparently well, but at the next reboot the > > physical-network services failed because the vfe0 interface > > wasn''t present: the vfe module wasn''t loaded. > > > > How can I make the driver load automatically at startup? > > isn''t add_drv enough? > > Perhaps the driver was installed into a directory which means that > it''s only loaded on a metal system. Where does the script put it? > > dme.in /kernel/drv/ and /kernel/drv/amd64/ I noticed that boot_archive was remade before reboot, thus the driver can''t be missing from the boot_archive file
On 29 Oct 2007, at 1:41pm, Nico Sabbi wrote:> in /kernel/drv/ and /kernel/drv/amd64/ > I noticed that boot_archive was remade before reboot, thus the driver > can''t be missing from the boot_archive fileThat seems okay. If you attempt to plumb the device ("ifconfig vfe0 plumb"), what happens? dme. -- David Edmondson, Solaris Engineering, http://dme.org
Il Monday 29 October 2007 15:52:13 David Edmondson ha scritto:> On 29 Oct 2007, at 1:41pm, Nico Sabbi wrote: > > in /kernel/drv/ and /kernel/drv/amd64/ > > I noticed that boot_archive was remade before reboot, thus the > > driver can''t be missing from the boot_archive file > > That seems okay. If you attempt to plumb the device ("ifconfig vfe0 > plumb"), what happens? > > dme.nothing if previously I don''t run devfsadm -i vfe