Re: Fix for hanging of vr interface (Rhine Ethernet)
Thomas Nystrom wrote: I have found one other person who has run the test sucessfully but I would feel more comfortable if there were some more people that had run the patch. I have also got a reply from a person in Finland that are going to do exactly the same thing as you are. When you're testing the vr driver, is it possible to do it as a loadable module, where you could repeatedly compile/kldload/test/kldunload? Or do you have to compile-the-kernel/install/reboot/test? When I was fighting with vr on my mini-itx board, I was doing it the second way, which was a pain. Tried the first way once, but didn't work (don't recall the details at the moment) - wasn't sure if it wasn't possible or if I was just missing something. If there is a less disruptive way to test any proposed patches, I'd be willing to take a whack at them. Barry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: ipfw and rule 65535
James Pace wrote: (No reply in -questions, so trying here. Thanks.) Here is the end of the output from 'ipfw show': 04000 0 0 deny log ip from any to any 65535 91 8227 deny ip from any to any Can anyone explain why the last rule is getting hit? I was under the impression that the rules are traversed in order, so 4000 should catch anything that 65535 would. This is FreeBSD 4.7-STABLE: Sun Nov 10 10:42:32 PST 2002 There were packets arrived when rule 4000 did not exist yet. Eugene Grosbein To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: bootvinum and multiple pc-partitions
On Thursday, 19 December 2002 at 21:33:50 -0600, Hari Bhaskaran wrote: Hi, I am having a problem using the bootvinum script. It seems to consider only the first slice (PC-partition) of the root spindle. I have put all vinum related files here http://65.189.239.65/vinum_files/ I have two (1 when you consider vinum) 120G dsks that need to be split onto more than 12 fs's. I created two PC-partitions 60G each to get over the a to h partition limit. I must confess to being a bit baffled. You seem to be confused on a number of points. Certainly there's never any reason to put more than one Vinum volume on a physical disk. I've taken a look at http://65.189.239.65/vinum_files/bootvinum/ (what happened to your DNS?), and find: bootvinum I've never seen this before. I don't do perl, but it doesn't seem like it does anything useful. create.ThruBank drive ThruBank device /dev/ad1s2h It's not clear what use this is by itself. create.YouCrazy drive YouCrazy device /dev/ad0s1h volume fs3 plex name fs3.p0 org concat volume fs3 sd name fs3.p0.s0 drive YouCrazy plex fs3.p0 len 88066257s driveoffset 16777481s volume var plex name var.p0 org concat volume var sd name var.p0.s0 drive YouCrazy plex var.p0 len 6291456s driveoffset 265s volume var/tmp plex name var/tmp.p0 org concat volume var/tmp sd name var/tmp.p0.s0 drive YouCrazy plex var/tmp.p0 len 2097152s driveoffset 6291721s volume var/log plex name var/log.p0 org concat volume var/log sd name var/log.p0.s0 drive YouCrazy plex var/log.p0 len 2097152s driveoffset 8388873s volume tmp plex name tmp.p0 org concat volume tmp sd name tmp.p0.s0 drive YouCrazy plex tmp.p0 len 6291456s driveoffset 10486025s You shouldn't be specifying explicit drive offsets. It's also not a good idea to specify names for pleses or subdisks. In addition, you've detected a bug in the Vinum parser: you can't have / characters in object names. create.UpWindow drive UpWindow device /dev/ad1s1h plex name fs3.p1 org concat volume fs3 sd name fs3.p1.s0 drive UpWindow plex fs3.p1 len 88066257s driveoffset 16777481s plex name var.p1 org concat volume var sd name var.p1.s0 drive UpWindow plex var.p1 len 6291456s driveoffset 265s plex name var/tmp.p1 org concat volume var/tmp sd name var/tmp.p1.s0 drive UpWindow plex var/tmp.p1 len 2097152s driveoffset 6291721s plex name var/log.p1 org concat volume var/log sd name var/log.p1.s0 drive UpWindow plex var/log.p1 len 2097152s driveoffset 8388873s plex name tmp.p1 org concat volume tmp sd name tmp.p1.s0 drive UpWindow plex tmp.p1 len 6291456s driveoffset 10486025s You're creating a lot of unattached plexes here. Why? disklabel.ad0s1 disklabel.ad0s1.b4vinum disklabel.ad1s1 disklabel.ad1s1.b4vinum disklabel.ad1s2 disklabel.ad1s2.b4vinum These look like normal enough volume labels, though it's not clear why you have ad1s2. I also have a different kind of problem. I was trying to find out how to modify bootvinum script to skip certain partitions when it processes /etc/fstab to create /etc/fstab.vinum I have two disks, and I want certain critical partitions mirrored on both, but I want each disk to have its own partitions made out of remaining space in each. I realise this may a little too much for the bootvinum perl script, but I just wanted to find out before I modify anything or try the manual approach. I don't know why you're going to so much trouble when it's *much* easier to do it manually. I can't help you with bootvinum, beyond to suggest not to use it. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: bootvinum and multiple pc-partitions
On Fri, Dec 20, 2002 at 02:26:34PM +1030, Greg 'groggy' Lehey wrote: I must confess to being a bit baffled. You seem to be confused on a number of points. Certainly there's never any reason to put more than one Vinum volume on a physical disk. Are you asking where the second hard-drive is attached to the same cable? Yes, one is the master, other is slave. I guess this could be problem if the master is dead. But they are still two separate harddisks. I was following the article http://www.freebsd.org/doc/en_US.ISO8859-1/articles/vinum/index.html After a search, I found some other articles http://org.netbase.org/vinum-mirrored.html. May be I will try to follow this one. Here is a summary of what I was trying to do:- I began a normal FreeBSD install with a single 120G disk. I needed the following partitions / 1G swap 6G (may be a bit too much!) /var 3G /var/log 1G /var/tmp 1G /tmp 3G /usr 3G /usr/home 3G /fs1 2G /fs2 20G /fs3 40G /fs4 31G Since I don't seem to be able to create more than 7 or so FreeBSD fs partitions per PC-partition, I split the PC-partition into two. That's why I have ad0s1 ad0s2. Now I need the whole disk mirrored on the second 120G disk. I may not want to mirror /fs4, that's all. create.ThruBank create.YouCrazy There are default files (I didn't care to change the default names) generated by bootvinum. You shouldn't be specifying explicit drive offsets. It's also not a good idea to specify names for pleses or subdisks. In addition, you've detected a bug in the Vinum parser: you can't have / characters in object names. [snip] You're creating a lot of unattached plexes here. Why? I just ran the script. So please ignore these. I don't know why you're going to so much trouble when it's *much* easier to do it manually. I can't help you with bootvinum, beyond to suggest not to use it. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: bootvinum and multiple pc-partitions
On Thursday, 19 December 2002 at 22:34:57 -0600, Hari Bhaskaran wrote: On Fri, Dec 20, 2002 at 02:26:34PM +1030, Greg 'groggy' Lehey wrote: I must confess to being a bit baffled. You seem to be confused on a number of points. Certainly there's never any reason to put more than one Vinum volume on a physical disk. Are you asking where the second hard-drive is attached to the same cable? No. Yes, one is the master, other is slave. I guess this could be problem if the master is dead. But they are still two separate harddisks. /dev/ad1s1 and /dev/ad1s2 are both the same disk. I was following the article http://www.freebsd.org/doc/en_US.ISO8859-1/articles/vinum/index.html After a search, I found some other articles http://org.netbase.org/vinum-mirrored.html. May be I will try to follow this one. Here is a summary of what I was trying to do:- I began a normal FreeBSD install with a single 120G disk. I needed the following partitions / 1G swap6G (may be a bit too much!) /var3G /var/log 1G /var/tmp 1G /tmp3G /usr3G /usr/home 3G /fs12G /fs220G /fs340G /fs431G Since I don't seem to be able to create more than 7 or so FreeBSD fs partitions per PC-partition, I split the PC-partition into two. That's why I have ad0s1 ad0s2. You don't need more than one partition. Now I need the whole disk mirrored on the second 120G disk. I may not want to mirror /fs4, that's all. create.ThruBank create.YouCrazy There are default files (I didn't care to change the default names) generated by bootvinum. You shouldn't be specifying explicit drive offsets. It's also not a good idea to specify names for pleses or subdisks. In addition, you've detected a bug in the Vinum parser: you can't have / characters in object names. [snip] You're creating a lot of unattached plexes here. Why? I just ran the script. So please ignore these. I don't know why you're going to so much trouble when it's *much* easier to do it manually. I can't help you with bootvinum, beyond to suggest not to use it. I can only repeat that. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: question in residue in umass.c
:I recently got my TREK Thumb drive working with -current. I was hoping to
:make similar changes to -STABLE to get it working. However, in -current,
:one of the quirks that had to be set IGNORE_RESIDUE. There does not
:seem to be any corresponding option in -STABLE.
:
:If there is, could one of the USB Wizards get back to me on how to make
:the appropriate change? The -CURRENT settings are below, as a reference.
:
: -Brian
:
: { USB_VENDOR_TREK, USB_PRODUCT_TREK_THUMBDRIVE_8MB, RID_WILDCARD,
:UMASS_PROTO_ATAPI | UMASS_PROTO_BBB,
:IGNORE_RESIDUE
: },
MFCing the quirk support, or at least most of it, is not that
difficult and I will be doing it after my -current patches get
cleared up.
In the mean time you can use this patch for -stable. Just add a quirk
entry for your TREK on top of this patch and there is a good chance
it will work.
-Matt
Matthew Dillon
[EMAIL PROTECTED]
Index: cam/scsi/scsi_da.c
===
RCS file: /home/ncvs/src/sys/cam/scsi/scsi_da.c,v
retrieving revision 1.42.2.29
diff -u -r1.42.2.29 scsi_da.c
--- cam/scsi/scsi_da.c 23 Nov 2002 23:21:42 - 1.42.2.29
+++ cam/scsi/scsi_da.c 19 Dec 2002 18:01:19 -
@@ -250,6 +250,16 @@
},
{
/*
+* Sony Key-Storage media fails in terrible ways without
+* both quirks. The auto 6-10 code doesn't do the job.
+* (note: The Sony diskkey is actually the MSYSTEMS
+* disk-on-key device).
+*/
+ {T_DIRECT, SIP_MEDIA_REMOVABLE, Sony, Storage Media, *},
+ /*quirks*/ DA_Q_NO_6_BYTE|DA_Q_NO_SYNC_CACHE
+ },
+ {
+ /*
* Sony DSC cameras (DSC-S30, DSC-S50, DSC-S70)
*/
{T_DIRECT, SIP_MEDIA_REMOVABLE, Sony, Sony DSC, *},
Index: dev/usb/ohci.c
===
RCS file: /home/ncvs/src/sys/dev/usb/ohci.c,v
retrieving revision 1.39.2.7
diff -u -r1.39.2.7 ohci.c
--- dev/usb/ohci.c 6 Nov 2002 20:23:50 - 1.39.2.7
+++ dev/usb/ohci.c 20 Dec 2002 01:21:12 -
@@ -469,7 +469,7 @@
cur = std;
- dataphysend = DMAADDR(dma, len - 1);
+ dataphysend = OHCI_PAGE(DMAADDR(dma, len - 1));
tdflags =
(rd ? OHCI_TD_IN : OHCI_TD_OUT) |
OHCI_TD_NOCC | OHCI_TD_TOGGLE_CARRY |
@@ -484,8 +484,8 @@
/* The OHCI hardware can handle at most one page crossing. */
#if defined(__NetBSD__) || defined(__OpenBSD__)
- if (OHCI_PAGE(dataphys) == OHCI_PAGE(dataphysend) ||
- OHCI_PAGE(dataphys) + OHCI_PAGE_SIZE == OHCI_PAGE(dataphysend))
+ if (OHCI_PAGE(dataphys) == dataphysend ||
+ OHCI_PAGE(dataphys) + OHCI_PAGE_SIZE == dataphysend)
#elif defined(__FreeBSD__)
/* XXX This is pretty broken: Because we do not allocate
* a contiguous buffer (contiguous in physical pages) we
@@ -493,7 +493,7 @@
* So check whether the start and end of the buffer are on
* the same page.
*/
- if (OHCI_PAGE(dataphys) == OHCI_PAGE(dataphysend))
+ if (OHCI_PAGE(dataphys) == dataphysend)
#endif
{
/* we can handle it in this TD */
@@ -510,6 +510,8 @@
/* must use multiple TDs, fill as much as possible. */
curlen = 2 * OHCI_PAGE_SIZE -
OHCI_PAGE_MASK(dataphys);
+ if (curlen len) /* may have fit in one page */
+ curlen = len;
#elif defined(__FreeBSD__)
/* See comment above (XXX) */
curlen = OHCI_PAGE_SIZE -
Index: dev/usb/umass.c
===
RCS file: /home/ncvs/src/sys/dev/usb/umass.c,v
retrieving revision 1.11.2.13
diff -u -r1.11.2.13 umass.c
--- dev/usb/umass.c 21 Nov 2002 21:26:14 - 1.11.2.13
+++ dev/usb/umass.c 20 Dec 2002 01:21:43 -
@@ -1488,6 +1488,7 @@
panic(%s: transferred %d bytes instead of %d bytes\n,
USBDEVNAME(sc-sc_dev),
sc-transfer_actlen, sc-transfer_datalen);
+#if 0
} else if (sc-transfer_datalen - sc-transfer_actlen
!= UGETDW(sc-csw.dCSWDataResidue)) {
DPRINTF(UDMASS_BBB, (%s: actlen=%d != residue=%d\n,
@@ -1497,6 +1498,7 @@
umass_bbb_reset(sc, STATUS_WIRE_FAILED);
return;
+#endif
} else if (sc-csw.bCSWStatus ==
Re: FTP installation from the floppies through ADSL modem with PPPoEor PPTP protocol.
Andrew wrote: On Fri, 20 Dec 2002, Asker wrote: The modem can be configured to use PPPoE or PPTP protocol for making the connection with my Internet Servise Provider. Well if the modem does PPPoE itself (and preusmably NAT) then you need no speical support from the OS. From its poitn of view you are just conencted via ethernet. If you need the machine to do PPPoE, ppp supports PPPoE. For this to work, though, you need netgraph, which isn't in GENERIC. You will need to make a custom kernel and build your own set of custom floppies. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
