if_ep compile error
Hi,
Looks like someone missed a file when updating the 'ep' driver. Simple
diff follows:
RCS file: /home/ncvs/src/sys/dev/ep/if_ep_eisa.c,v
retrieving revision 1.25
diff -u -r1.25 if_ep_eisa.c
--- if_ep_eisa.c24 Aug 2003 17:46:05 - 1.25
+++ if_ep_eisa.c18 Oct 2003 19:29:38 -
@@ -215,7 +215,7 @@
irq = 2;
GO_WINDOW(0);
- SET_IRQ(BASE, irq);
+ SET_IRQ(sc, irq);
if ((error = ep_attach(sc))) {
device_printf(dev, ep_attach() failed! (%d)\n, error);
Regards,
Stuart
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
atapicam related panic
Hi, I have an easily reproducable panic when using atapicam. Vague trace follows: panic was caused by this: KASSERT(bp-b_flags B_PHYS, (vmapbuf)); trace: vmapbuf cam_periph xptioctl spec_ioctl spec_vnoperate vn_ioctl ioctl syscall Let me know if you need any further information, this panic is easily reproducable for me(cdrecord --scanbus is enough). Regards, Stuart ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [Build Error]:: pccard
In message: [EMAIL PROTECTED] Sebastian Yepes F. [ESN] [EMAIL PROTECTED] writes: : i have just looked at it and don't see any info related to the pccard dev. : what are the instructions building both pcic and pccard in your kernel config? If so, don't do that. It is broken. pcic cannot possibly work, even if I fix the trivial compile problem. I have some changes in my p4 tree, but they aren't cooked yet. Your best bet is to simply remove pcic from your kernel config file. That's good to know. My laptop seems to vaguely work with pcic(it has a intel compatibility mode). Will pcic support cardbus at all? Stuart ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Atmel AT76C503 USB 802.11b device driver
On Wed Oct 08, 05:27P +0200, Bernd Walter wrote: On Wed, Oct 08, 2003 at 03:59:40AM +0100, Stuart Walsh wrote: Aww crap, my apologies for the duplicate email.. sendmail appears to be on steroids or something. The messages are sumited twice by your mailclient - it's not the MTAs fault. See that there are several minutes between them and that they have different message-ids. They were, yes. But once when the sendmail daemon wasn't running. I checked the mail queue before i sent it again and it wasn't there. Perhaps sendmail stores failed mail somewhere I'm not familiar with. EUSERERROR would seem to apply.. Anyway, I finally got around to installing exim and everyone is happy. Anyway.. just an update to the installation instructions. Warner kindly committed the usbdevs portion of the driver, so if you have a cvsup from yesterday or newer, you don't need to apply atwi.diff. Sounds interesting. Is this just to configure a WLAN-Ethernet bridge, or can you transmit network data over USB? It's treated like any other network device. Raw network data is sent and received over the USB transfer pipes and dealt with using mbufs in the normal way. The main difference is that you can only submit one packet at a time, so there is effectively no hardware queue/ring. The wireless part seems to be a cross between 'ath' devices and 'wi' devices. WEP is done in hardware, as is scanning. Scan results are processed in software. Stuart ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Atmel AT76C503 USB 802.11b device driver
On Wed, 8 Oct 2003 16:49:34 +0100 Stuart Walsh [EMAIL PROTECTED] wrote: They were, yes. But once when the sendmail daemon wasn't running. I checked the mail queue before i sent it again and it wasn't there. Perhaps sendmail stores failed mail somewhere I'm not familiar with. EUSERERROR would seem to apply.. mailq or mailq -Ac? I think we've established I was at fault, but thanks :) It really was just an off the cuff remark, I didn't intend to start an MTA war or a sendmail usage lecture. Can we restrict all further posts in this thread to feedback on my driver? :) Regards, Stuart ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Atmel AT76C503 USB 802.11b device driver
Hi folks, I've come up with a driver for the above mentioned devices. This particular chip is found in a whole load of 802.11b USB devices. My particular device is an SMC2662W-AR, but it should work for any device containing the above chip. Just fill in the product/vendor ids and let me know your results and i'll update my local copy accordingly. The driver is at http://stu.bash.sh/atwi-20031007.tar.gz. Extract the files from within /usr/src/sys and apply atwi.diff with patch -p0 atwi.diff. Only 5-CURRENT is supported at this time, so you will need a fairly recent cvsup. If you are going to report problems, set sysctl hw.atwi.debug=2 first and include all output. Both infrastructure and adhoc modes should work, but infrastructure mode hasnt been tested this last week as I had to return the AP I had on loan. You are strongly advised to use this driver as a module as the usb code has issues with the device if you unplug and replug it while the module is loaded. I'm working on fixing this. Other than that it should work fine. Please do report any successes or failures. Enjoy! Regards, Stuart ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Atmel AT76C503 USB 802.11b device driver
Hi folks, I've come up with a driver for the above mentioned devices. This particular chip is found in a whole load of 802.11b USB devices. My particular device is an SMC2662W-AR, but it should work for any device containing the above chip. Just fill in the product/vendor ids and let me know your results and i'll update my local copy accordingly. The driver is at http://stu.bash.sh/atwi-20031007.tar.gz. Extract the files from within /usr/src/sys and apply atwi.diff with patch -p0 atwi.diff. Only 5-CURRENT is supported at this time, so you will need a fairly recent cvsup. If you are going to report problems, set sysctl hw.atwi.debug=2 first and include all output. Both infrastructure and adhoc modes should work, but infrastructure mode hasnt been tested this last week as I had to return the AP I had on loan. You are strongly advised to use this driver as a module as the usb code has issues with the device if you unplug and replug it while the module is loaded. I'm working on fixing this. Other than that it should work fine. Please do report any successes or failures. Enjoy! Regards, Stuart ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Atmel AT76C503 USB 802.11b device driver
On Tue Oct 07, 02:36P +0100, Stuart Walsh wrote: Hi folks, I've come up with a driver for the above mentioned devices. This particular chip is found in a whole load of 802.11b USB devices. My particular device is an SMC2662W-AR, but it should work for any device containing the above chip. Just fill in the product/vendor ids and let me know your results and i'll update my local copy accordingly. The driver is at http://stu.bash.sh/atwi-20031007.tar.gz. Extract the files from within /usr/src/sys and apply atwi.diff with patch -p0 atwi.diff. Only 5-CURRENT is supported at this time, so you will need a fairly recent cvsup. If you are going to report problems, set sysctl hw.atwi.debug=2 first and include all output. Both infrastructure and adhoc modes should work, but infrastructure mode hasnt been tested this last week as I had to return the AP I had on loan. You are strongly advised to use this driver as a module as the usb code has issues with the device if you unplug and replug it while the module is loaded. I'm working on fixing this. Other than that it should work fine. Please do report any successes or failures. Enjoy! Aww crap, my apologies for the duplicate email.. sendmail appears to be on steroids or something. Anyway.. just an update to the installation instructions. Warner kindly committed the usbdevs portion of the driver, so if you have a cvsup from yesterday or newer, you don't need to apply atwi.diff. Stuart ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: if_sk build fails
On Sat, 20 Sep 2003 16:14:22 +0200 Pawel Worach [EMAIL PROTECTED] wrote: Hi! Last if_sk update broke buildkernel === sk rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include /usr/src/sys/modules/sk/../../pci/if_sk.c /usr/src/sys/pci/if_sk.c:129:26: pci/yukonreg.h: No such file or directory mkdep: compile failed missed to cvs add yukonreg.h? - Pawel This was fixed sometime yesterday with a commit of yukonreg.h. Regards, Stuart ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CIS is too long
- Original Message - From: M. Warner Losh [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Sunday, September 21, 2003 5:50 PM Subject: Re: CIS is too long In message: [EMAIL PROTECTED] Kenichi Niioka [EMAIL PROTECTED] writes: : I'm getting the following errors when I insert my pccard. : : CIS is too long -- truncating : pccard0: Card has no functions! : cbb0: PC Card card activation failed There's a small set of cards that aren't being read in correctly. You have one of the cards. It looks like I'm programming the bridges exactly the same between oldcard and newcard. I do not know why it isn't working, maybe a bad delay? maybe some bit I've overlooked? I'm not sure. I see it in maybe 3 of the hundred odd cards that I have. These cards read '0's. I have one other one that reads just freaky random junk. I have a wireless card that I get random junk for too, yet netbsd reads the CIS just fine.. unfortuneatly my laptop is somewhat out of commission at the moment so I can't really dig in to it :/ It's a shame, because I'd like to be able to port a driver for it. Regards, Stuart ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Fri, Sep 12, 2003 at 09:55:54PM -0400, Jung-uk Kim wrote: I have my own *working* driver, which is for 4-STABLE. It works with SK-9521 V2.0 (for me, at least) and it should work with 3C940. Note: This driver is ported from Nathan L. Binkert's OpenBSD driver. Note: This is completely independent from Stuart Walsh's work. ;-) Note: You must recompile MII driver and dependent network drivers. It's worth noting my patch was a port of Natan's patch also(which is actually Bill's driver technically speaking ;), so I'd be interested to see where i went wrong. But if it works then great, I'll get on with something else :) It's somewhat difficult to fine tune a driver when you dont actually own the hardware in question. Regards, Stuart ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Mon Aug 25, 11:11P -0500, Glenn Johnson wrote: Hi again chaps, I've been working on other things lately, including getting ready to move house and looking after my 3 month old daughter :) but recently I've took up trying to get this driver working again. If anyone is interested in helping out, could they give http://stu.bash.sh/if_sk.c and http://stu.bash.sh/if_skreg.h a try and let me know what output you get. I'm only really interested in what happens after the MAC gets printed so don't go to too much trouble to get the exact info. Just plonk the files in /usr/src/sys/pci over the top of the old ones. Thanks to anyone who helps out. Regards, Stuart ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Sun Aug 24, 10:42P -0500, Glenn Johnson wrote: On Sun, Aug 24, 2003 at 01:22:39PM +0200, Wilko Bulte wrote: On Sat, Aug 23, 2003 at 04:45:30PM +0100, Stuart Walsh wrote: Hi, I ported the openbsd additions to the sk driver to support the 3c940 gigabit network card which is commonly found in the above asus motherboard. Testers/comments/commits welcome, but please don't blame me if it burns your house down or something :) Hi Stuart, I tried this patch instead of the earlier ones you pointed me to on IRC. Unfortunately my Asus P4P800 still locks up solid (reset button required) after printing the 3c940's ethernet address. I'm interested to know if other P4P800 owners have the same issue. I have an Abit IS7 with a 3c940. I also get a lockup at boot time. I tried loading the module after bootup as well. I tried that two times; it loaded one time and locked the machine up the other time. Does it lock up after printing the ethernet address as in Wilko's case? Does the card work properly if the module does manage to load? Also could you mail your dmesg. Regards, Stuart ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Sun Aug 24, 01:22P +0200, Wilko Bulte wrote: On Sat, Aug 23, 2003 at 04:45:30PM +0100, Stuart Walsh wrote: Hi, I ported the openbsd additions to the sk driver to support the 3c940 gigabit network card which is commonly found in the above asus motherboard. Testers/comments/commits welcome, but please don't blame me if it burns your house down or something :) Hi Stuart, I tried this patch instead of the earlier ones you pointed me to on IRC. Unfortunately my Asus P4P800 still locks up solid (reset button required) after printing the 3c940's ethernet address. I'm interested to know if other P4P800 owners have the same issue. Wilko Hi Wilko, Sorry to hear you are still having trouble. Thus far I have only been able to find one other person to test the driver and for him it works perfectly(also a P4P800). Are you running up do date -current, or is there anything strange about your setup at all? Regards, Stuart ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
3C940 / Asus P4P800 gigabit LAN driver
Hi,
I ported the openbsd additions to the sk driver to support the 3c940
gigabit network card which is commonly found in the above asus
motherboard. Testers/comments/commits welcome, but please don't blame
me if it burns your house down or something :)
Apply the diff in /usr/src/sys. It will have to be a fairly recent
-current because of the recent pci header reloactions.
Please be aware that I have had reports of panics on kldunloading the sk
module. I don't posess the hardware myself and this could be present in
the sk driver in general, so more information on this would be greatly
received.
Regards,
Stuart Walsh
Index: dev/mii/e1000phy.c
===
RCS file: /home/ncvs/src/sys/dev/mii/e1000phy.c,v
retrieving revision 1.8
diff -u -r1.8 e1000phy.c
--- dev/mii/e1000phy.c 19 Jan 2003 02:59:32 - 1.8
+++ dev/mii/e1000phy.c 23 Aug 2003 15:17:42 -
@@ -87,7 +86,8 @@
ma = device_get_ivars(dev);
id = ((ma-mii_id1 16) | ma-mii_id2) E1000_ID_MASK;
- if (id != E1000_ID_88E1000 id != E1000_ID_88E1000S) {
+ if (id != E1000_ID_88E1000 id != E1000_ID_88E1000S
+id != E1011_ID) {
return ENXIO;
}
@@ -101,6 +101,9 @@
struct mii_softc *sc;
struct mii_attach_args *ma;
struct mii_data *mii;
+#if 0
+u_int32_t id;
+#endif
getenv_int(e1000phy_debug, e1000phy_debug);
@@ -117,6 +120,14 @@
sc-mii_flags |= MIIF_NOISOLATE;
mii-mii_instance++;
+
+#if 0
+id = ((ma-mii_id1 16) | ma-mii_id2) E1000_ID_MASK;
+
+if ((id == E1011_ID) (PHY_READ(sc, E1000_ESSR) E1000_ESSR_FIBER_LINK))
+sc-mii_flags |= MIIF_HAVEFIBER;
+#endif
+
e1000phy_reset(sc);
device_printf(dev, );
@@ -126,27 +137,37 @@
ADD(IFM_MAKEWORD(IFM_ETHER, IFM_NONE, 0, sc-mii_inst),
E1000_CR_ISOLATE);
*/
- ADD(IFM_MAKEWORD(IFM_ETHER, IFM_10_T, 0, sc-mii_inst),
- E1000_CR_SPEED_10);
- printf(10baseT, );
- ADD(IFM_MAKEWORD(IFM_ETHER, IFM_10_T, IFM_FDX, sc-mii_inst),
- E1000_CR_SPEED_10 | E1000_CR_FULL_DUPLEX);
- printf(10baseT-FDX, );
- ADD(IFM_MAKEWORD(IFM_ETHER, IFM_100_TX, 0, sc-mii_inst),
- E1000_CR_SPEED_100);
- printf(100baseTX, );
- ADD(IFM_MAKEWORD(IFM_ETHER, IFM_100_TX, IFM_FDX, sc-mii_inst),
- E1000_CR_SPEED_100 | E1000_CR_FULL_DUPLEX);
- printf(100baseTX-FDX, );
- /*
-* 1000BT-simplex not supported; driver must ignore this entry,
-* but it must be present in order to manually set full-duplex.
-*/
- ADD(IFM_MAKEWORD(IFM_ETHER, IFM_1000_T, 0, sc-mii_inst),
- E1000_CR_SPEED_1000);
- ADD(IFM_MAKEWORD(IFM_ETHER, IFM_1000_T, IFM_FDX, sc-mii_inst),
- E1000_CR_SPEED_1000 | E1000_CR_FULL_DUPLEX);
- printf(1000baseTX-FDX, );
+#if 0
+if ((sc-mii_flags MIIF_HAVEFIBER) == 0) {
+#endif
+ ADD(IFM_MAKEWORD(IFM_ETHER, IFM_10_T, 0, sc-mii_inst),
+ E1000_CR_SPEED_10);
+ printf(10baseT, );
+ ADD(IFM_MAKEWORD(IFM_ETHER, IFM_10_T, IFM_FDX, sc-mii_inst),
+ E1000_CR_SPEED_10 | E1000_CR_FULL_DUPLEX);
+ printf(10baseT-FDX, );
+ ADD(IFM_MAKEWORD(IFM_ETHER, IFM_100_TX, 0, sc-mii_inst),
+ E1000_CR_SPEED_100);
+ printf(100baseTX, );
+ ADD(IFM_MAKEWORD(IFM_ETHER, IFM_100_TX, IFM_FDX, sc-mii_inst),
+ E1000_CR_SPEED_100 | E1000_CR_FULL_DUPLEX);
+ printf(100baseTX-FDX, );
+ /*
+* 1000BT-simplex not supported; driver must ignore this entry,
+* but it must be present in order to manually set full-duplex.
+*/
+ ADD(IFM_MAKEWORD(IFM_ETHER, IFM_1000_T, 0, sc-mii_inst),
+ E1000_CR_SPEED_1000);
+ ADD(IFM_MAKEWORD(IFM_ETHER, IFM_1000_T, IFM_FDX, sc-mii_inst),
+ E1000_CR_SPEED_1000 | E1000_CR_FULL_DUPLEX);
+ printf(1000baseTX-FDX, );
+#if 0
+} else {
+ADD(IFM_MAKEWORD(IFM_ETHER, IFM_1000_SX, IFM_FDX,sc-mii_inst),
+E1000_CR_SPEED_1000 | E1000_CR_FULL_DUPLEX);
+}
+#endif
+
ADD(IFM_MAKEWORD(IFM_ETHER, IFM_AUTO, 0, sc-mii_inst), 0);
printf(auto\n);
#undef ADD
@@ -233,6 +254,13 @@
(void)e1000phy_mii_phy_auto(sc);
break;
+case IFM_1000_SX:
+e1000phy_reset(sc);
+
+PHY_WRITE(sc, E1000_CR, E1000_CR_FULL_DUPLEX | E1000_CR_SPEED_1000);
+PHY_WRITE(sc, E1000_AR, E1000_FA_1000X_FD);
+break;
+
case IFM_1000_T:
e1000phy_reset(sc);
@@ -351,40 +379,64 @@
return;
}
- if (ssr E1000_SSR_1000MBS)
- mii-mii_media_active |= IFM_1000_T;
- else if (ssr E1000_SSR_100MBS)
- mii-mii_media_active |= IFM_100_TX;
- else
- mii-mii_media_active
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Sat Aug 23, 04:45P +0100, Stuart Walsh wrote: Hi, I ported the openbsd additions to the sk driver to support the 3c940 gigabit network card which is commonly found in the above asus motherboard. Testers/comments/commits welcome, but please don't blame me if it burns your house down or something :) Apply the diff in /usr/src/sys. It will have to be a fairly recent -current because of the recent pci header reloactions. Please be aware that I have had reports of panics on kldunloading the sk module. I don't posess the hardware myself and this could be present in the sk driver in general, so more information on this would be greatly received. I should have mentioned that there is code in the PHY driver which has #if 0 around it because it deals with fibre links and I have been unable to test that configuration. If you can, please feel free to enable the code. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3C940 / Asus P4P800 gigabit LAN driver
On Sat Aug 23, 04:45P +0100, Stuart Walsh wrote: Hi, I ported the openbsd additions to the sk driver to support the 3c940 gigabit network card which is commonly found in the above asus motherboard. Testers/comments/commits welcome, but please don't blame me if it burns your house down or something :) Apply the diff in /usr/src/sys. It will have to be a fairly recent -current because of the recent pci header reloactions. Please be aware that I have had reports of panics on kldunloading the sk module. I don't posess the hardware myself and this could be present in the sk driver in general, so more information on this would be greatly received. Regards, Stuart Walsh Also, I forgot to mention that the code in the PHY driver to deal with fibre links is untested and as such #if 0'd out. If you can test this configuration, feel free to enable the code. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
panic when unplugging a mounted usb camera
Hi, A somewhat annoying occurance in -current; I get a panic if I leave the camera device mounted when I unplug it and subsequently try to unmount the device or reboot the system. I did some digging and it seems the dacleanup() function isnt being called because periph-refcount is 1. I spoke to another person who uses the da driver for their camera and their's cleans up fine when mounted. Aug 23 21:15:29 icecold kernel: umass0: Fuji Photo Film USB Mass Storage, rev 1.10/10.00, addr 2 Aug 23 21:15:29 icecold kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Aug 23 21:15:29 icecold kernel: da0: FUJIFILM USB-DRIVEUNIT 1.00 Removable Direct Access SCSI-0 device Aug 23 21:15:29 icecold kernel: da0: 1.000MB/s transfers Aug 23 21:15:29 icecold kernel: da0: 31MB (64000 512 byte sectors: 64H 32S/T 31C) Thats the camera, for reference. Aug 23 21:15:31 icecold kernel: umass0: at uhub1 port 2 (addr 2) disconnected Aug 23 21:15:31 icecold kernel: invalidate called... Aug 23 21:15:31 icecold kernel: (da0:umass-sim0:0:0:0): lost device Aug 23 21:15:31 icecold kernel: returned from inval Aug 23 21:15:31 icecold kernel: refcount is 0, freeing Aug 23 21:15:31 icecold kernel: periph not null, calling..0xc0159bd0 Aug 23 21:15:31 icecold kernel: we got to dacleanup.. Aug 23 21:15:31 icecold kernel: (da0:umass-sim0:0:0:0): removing device entr Thats what I get when I remove the device and it is unmounted(with my debugging additions). Aug 23 21:16:12 icecold kernel: umass0: at uhub1 port 2 (addr 2) disconnected Aug 23 21:16:12 icecold kernel: invalidate called... Aug 23 21:16:12 icecold kernel: (da0:umass-sim0:0:0:0): lost device Aug 23 21:16:12 icecold kernel: returned from inval Aug 23 21:16:12 icecold kernel: refcount is 1 Thats what I get when I remove the device and it is mounted. Please do let me know if I can provide any further information. Regards, Stuart Walsh ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
