Re: ATA atapi-all.c problems/fixes/cleanups
It seems Brian Fundakowski Feldman wrote:
I used a multiple of the blocksize, and it works fine, except for on
the very last bit of data. The very last bit of data is what causes
an underrun, and the code that's there for overrun/underrun is
wrong right now. For underrun, it ends up writing the underlying
blocksize length from the user buffer of _less_than_that_size_, then
it writes (blocksize - user buffer size) _more_ zeroed data! This
promptly locks up the IDE bus with my CD-R. That's what the patch was
about and you didn't say anything about; yes, I know that blocksizes
should be matched perfectly and padded perfectly to prevent the ATA
driver from having to handle the underrun/overrun cases, but the
current handling is/was still broken.
Try this patch instead, it should do the right thing..
Index: atapi-all.c
===
RCS file: /home/ncvs/src/sys/dev/ata/atapi-all.c,v
retrieving revision 1.29
diff -u -r1.29 atapi-all.c
--- atapi-all.c 2000/01/03 10:26:56 1.29
+++ atapi-all.c 2000/01/05 08:36:49
@@ -563,12 +563,15 @@
#endif
for (resid=request-bytecount; residlength; resid+=sizeof(int16_t))
inw(request-device-controller-ioaddr + ATA_DATA);
+ *buffer += request-bytecount;
+ request-bytecount = 0;
}
-else
+else {
insw(request-device-controller-ioaddr + ATA_DATA,
(void *)((uintptr_t)*buffer), length / sizeof(int16_t));
-request-bytecount -= length;
-*buffer += length;
+ *buffer += length;
+ request-bytecount -= length;
+}
}
static void
@@ -585,19 +588,22 @@
request-device-devname, length, request-bytecount);
#ifdef ATA_16BIT_ONLY
outsw(request-device-controller-ioaddr + ATA_DATA,
- (void *)((uintptr_t)*buffer), length / sizeof(int16_t));
+ (void *)((uintptr_t)*buffer), request-bytecount/sizeof(int16_t));
#else
outsl(request-device-controller-ioaddr + ATA_DATA,
- (void *)((uintptr_t)*buffer), length / sizeof(int32_t));
+ (void *)((uintptr_t)*buffer), request-bytecount/sizeof(int32_t));
#endif
for (resid=request-bytecount; residlength; resid+=sizeof(int16_t))
outw(request-device-controller-ioaddr + ATA_DATA, 0);
+*buffer += request-bytecount;
+ request-bytecount = 0;
}
-else
+else {
outsw(request-device-controller-ioaddr + ATA_DATA,
(void *)((uintptr_t)*buffer), length / sizeof(int16_t));
-request-bytecount -= length;
-*buffer += length;
+*buffer += length;
+ request-bytecount -= length;
+}
}
static void
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: ATA lost contact
It seems Kris Kennaway wrote: One of my Western Digital Caviars doesn't work under the new ATA driver: upon trying to access the disk (via swapon or mount during boot) it gives the famous "lost contact with disk" message and falls back to PIO mode. Interestingly, my two older WDCs work fine - although I notice that ad1 and ad2 are only detected as WDMA2, when it seems (from the udma=2) that they can handle UDMA - is this a cabling issue or something (I'm not familiar with IDE cabling requirements)? The disk probably has problems with DMA mode (lots of older WD disks has that). You only get WDMA2 mode since you controller is an older Intel PIIX that can't do UDMA... ata-pci0: Intel PIIX ATA controller at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ad0: piomode=4 dmamode=2 udmamode=-1 cblid=0 ad0: WDC AC31600H/21.15T21 ATA-0 disk at ata0 as master ad0: 1549MB (3173184 sectors), 3148 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, WDMA2 ad1: piomode=4 dmamode=2 udmamode=2 cblid=0 ad1: WDC AC22500L/32.41N37 ATA-3 disk at ata0 as slave ad1: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 1 depth queue, WDMA2 ad2: piomode=4 dmamode=2 udmamode=2 cblid=0 ad2: WDC AC26400R/15.01J55 ATA-4 disk at ata1 as master ad2: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S ad2: 16 secs/int, 1 depth queue, WDMA2 -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA lost contact
On Wed, 5 Jan 2000, Soren Schmidt wrote: The disk probably has problems with DMA mode (lots of older WD disks has that). You only get WDMA2 mode since you controller is an older Intel PIIX that can't do UDMA... Hmm..This disk was bought in about March 99..you're sure that's the reason? Kris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
newpcm problems
With yesterday's current I get bounce buffer panics in isa_dmastart doing cat foo.pcm /dev/dsp. The same thing happens with mss.c v1.42 modified to reduce MSS_BUFSIZE by 48k. The card is ESS1869 in this case: Jan 5 02:16:55 avalon /kernel: unknown0: ESS ES1869 Plug and Play AudioDrive at port 0x800-0x807 on isa0 Jan 5 02:16:55 avalon /kernel: sbc0: ESS ES1869 at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,0 on isa0 Jan 5 02:16:55 avalon /kernel: pcm0: SB DSP 3.01 (ESS mode) on sbc0 Jan 5 02:16:55 avalon /kernel: bus_dmamap_load: Too many segs! buf_len = 0xdf00 Jan 5 02:16:55 avalon /kernel: bus_dmamap_load: Too many segs! buf_len = 0xdf00 Jan 5 02:16:55 avalon /kernel: joy1: ESS0001 PnP Joystick at port 0x200 on isa0 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
portmap problems
Recently I've noticed that it takes a long time for portmap
to settle well enough so that mountd and nfsd can register.
Jan 5 02:16:56 avalon mountd[97]: can't register mount
Jan 5 02:16:56 avalon nfsd:[99]: can't register with udp portmap
Very strange. Strange enough so that perhaps it might
catch someone else's interest. Someone who might actually do
something about it, maybe even.
portmap was pid 92 this time. Killing and restarting mountd and nfsd
works:
% rpcinfo -p
program vers proto port
102 tcp111 portmapper
102 udp111 portmapper
153 udp 1011 mountd
153 tcp 1020 mountd
151 udp 1011 mountd
151 tcp 1020 mountd
132 udp 2049 nfs
133 udp 2049 nfs
Which suggests to me -- perhaps portmap and mountd
should be allowed to take a -u argument as well, to reduce
port consumption? If so, I imagine the patch would be something
like this:
diff -u sbin/mountd/mountd.c.orig sbin/mountd/mountd.c.new
--- sbin/mountd/mountd.c.orig Wed Jan 5 02:36:27 2000
+++ sbin/mountd/mountd.c.newWed Jan 5 02:38:22 2000
@@ -229,6 +229,8 @@
int debug = 0;
#endif
+int udponly = 0;
+
/*
* Mountd server for NFS mount protocol as described in:
* NFS: Network File System Protocol Specification, RFC1094, Appendix A
@@ -255,7 +257,7 @@
if (error)
errx(1, "NFS support is not available in the running kernel");
- while ((c = getopt(argc, argv, "2dlnr")) != -1)
+ while ((c = getopt(argc, argv, "2dlnru")) != -1)
switch (c) {
case '2':
force_v2 = 1;
@@ -272,6 +274,9 @@
case 'l':
log = 1;
break;
+ case 'u':
+ udponly = 1;
+ break;
default:
usage();
};
@@ -317,7 +322,7 @@
}
}
if ((udptransp = svcudp_create(RPC_ANYSOCK)) == NULL ||
- (tcptransp = svctcp_create(RPC_ANYSOCK, 0, 0)) == NULL) {
+ (!udponly (tcptransp = svctcp_create(RPC_ANYSOCK, 0, 0)) == NULL)) {
syslog(LOG_ERR, "can't create socket");
exit(1);
}
@@ -325,12 +330,12 @@
pmap_unset(RPCPROG_MNT, 3);
if (!force_v2)
if (!svc_register(udptransp, RPCPROG_MNT, 3, mntsrv, IPPROTO_UDP) ||
- !svc_register(tcptransp, RPCPROG_MNT, 3, mntsrv, IPPROTO_TCP)) {
+ (!udponly !svc_register(tcptransp, RPCPROG_MNT, 3, mntsrv,
+IPPROTO_TCP))) {
syslog(LOG_ERR, "can't register mount");
exit(1);
}
if (!svc_register(udptransp, RPCPROG_MNT, 1, mntsrv, IPPROTO_UDP) ||
- !svc_register(tcptransp, RPCPROG_MNT, 1, mntsrv, IPPROTO_TCP)) {
+ (!udponly !svc_register(tcptransp, RPCPROG_MNT, 1, mntsrv,
+IPPROTO_TCP))) {
syslog(LOG_ERR, "can't register mount");
exit(1);
}
diff -u usr.sbin/portmap/portmap.c.orig usr.sbin/portmap/portmap.c.new
--- usr.sbin/portmap/portmap.c.orig Wed Jan 5 02:33:53 2000
+++ usr.sbin/portmap/portmap.c.new Wed Jan 5 02:36:03 2000
@@ -109,6 +109,7 @@
struct pmaplist *pmaplist;
int debugging = 0;
+int udponly = 0;
int
main(argc, argv)
@@ -121,7 +122,7 @@
int len = sizeof(struct sockaddr_in);
register struct pmaplist *pml;
- while ((c = getopt(argc, argv, "dv")) != -1) {
+ while ((c = getopt(argc, argv, "duv")) != -1) {
switch (c) {
case 'd':
@@ -132,6 +133,10 @@
verboselog = 1;
break;
+ case 'u':
+ udponly = 1;
+ break;
+
default:
usage();
}
@@ -169,29 +174,32 @@
pml-pml_map.pm_port = PMAPPORT;
pmaplist = pml;
- if ((sock = socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)) 0) {
+ if (!udponly) {
+
+ if ((sock = socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)) 0) {
syslog(LOG_ERR, "cannot create tcp socket: %m");
exit(1);
- }
- if (bind(sock, (struct sockaddr *)addr, len) != 0) {
+ }
+ if (bind(sock, (struct sockaddr *)addr, len) != 0) {
syslog(LOG_ERR, "cannot bind tcp: %m");
exit(1);
- }
- if ((xprt = svctcp_create(sock, RPCSMALLMSGSIZE, RPCSMALLMSGSIZE))
- == (SVCXPRT *)NULL) {
+ }
+ if ((xprt = svctcp_create(sock, RPCSMALLMSGSIZE, RPCSMALLMSGSIZE))
+ == (SVCXPRT *)NULL) {
syslog(LOG_ERR, "couldn't do tcp_create");
exit(1);
+ }
+ /* make an entry for ourself */
+ pml = (struct
Re: ATA lost contact
It seems Kris Kennaway wrote: On Wed, 5 Jan 2000, Soren Schmidt wrote: The disk probably has problems with DMA mode (lots of older WD disks has that). You only get WDMA2 mode since you controller is an older Intel PIIX that can't do UDMA... Hmm..This disk was bought in about March 99..you're sure that's the reason? No, but I've had my share of bad experiences with WD disks in that regard, I'll have to look up the modelnumber to be sure... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: A couple questions regarding pcmcia cards....
The card is also available in a 16-bit version (it has a PC Card logo on the back, I don't know if the Cardbus one does or not). It's important to note that the 575 (not the 574) is CardBus. I used to have one, but semi-thankfully, it got blown up by lightning and the replacement was 16-bit and thus usuable with FreeBSD. If you actually have the 16-bit pccard version, then you need to patch your driver. I sent in patches that got committed to 4.0, but were basically replaced a month later by Matt Jacob's massive rework of the entire ep driver and not MFC'd. You can pull rev. 1.87 of if_ep.c out of the Attic from cvsweb: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/isa/Attic/if_ep.c And it will drop directly into your tree in /sys/i386/isa. Make sure you have 1.23.2.1 or later of if_epreg.h. The only major change of the patch is to hit the card with an offset command if the no-offset commands don't work. I have no idea what its significance is other than it's required to make my card work. I can't remember where I got the basic idea from, it was from PAO I think. -Original Message- From: Frank Mayhar [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 05, 2000 12:18 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: A couple questions regarding pcmcia cards William Woods wrote: I have two pcmcia cards here I am wondering if the work under either -stable or -current, they are: 3COM Megahertz 10/100 LAN PC Card model #3CCFE574BT This is a cardbus card (I have one, too) and won't work. Many of us are eagerly awaiting Warner's new cardbus code. The other card is cardbus, so I doubt it but I will ask anyway Adaptec SlimSCSI 1480A UltraSCSI If it's cardbus, it won't work. -- Frank Mayhar [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: options COMPAT_LINUX makes kernel fail to compile
Hello, Not that this is an actual fix to the problem, but: The COMPAT_LINUX kernel option isn't needed any more, per Marcel. (At least, when I wrote an article on this, it wasn't.) You can probably remove COMPAT_LINUX entirely. (If only the rest of the problems were this easy. :) ==ml Hi! With option COMPAT_LINUX (which present in LINT) make depend fails with: cc -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -fno-builtin -mpreferred-stack-boundary=2 -UKERNEL -o linux_genassym.o -c ../../i386/linux/linux_genassym.c genassym -o linux_assym.h linux_genassym.o genassym:No such file or directory *** Error code 1 Dmitry. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Opera Beta and FreeBSD
If memory serves me right, said on 2000-01-04 15:29 -0600: Has anyone gotten Opera beta working under linux emulation? Works fine, but you need the glibc-2.1 libraries (i.e. from RedHat 6.1), as it is linked against these. Keep in mind that this is no beta, but a 'technical preview', many functions are still missing. -- Lutz Albers, [EMAIL PROTECTED], pgp key available from http://www.pgp.net Do not take life too seriously, you will never get out of it alive. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Proposal: Removing doscmd from the source tree...
Thomas Zenker wrote: A possibility could be: 1. build it for i386 only, 2. build it via buildworld without X11, regardless if X11 exists. If I want to use it with X11, it is interactive and I can make it for X11 by hand - it will not break on compile runs at some hour at night. I'll commit a fix that will prevent including X when DESTDIR has been set. In practice this means that doscmd will never include X, unless you compile it by hand. This of course implies that you have to compile doscmd by hand every time you do an installworld, given that you want X. I still think doscmd should and can be a port, but I think it helps my argument if I have the port ready to be committed and downloadable for testing. It helps undermine the general objection that doscmd is very dependent on the kernel, which I doubt... If not, it will at least show me that I'm wrong :-) -- Marcel Moolenaarmailto:[EMAIL PROTECTED] SCC Internetworking Databases http://www.scc.nl/ The FreeBSD projectmailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Proposal: Removing doscmd from the source tree...
On Wed, 5 Jan 2000, Marcel Moolenaar wrote: Thomas Zenker wrote: A possibility could be: 1. build it for i386 only, 2. build it via buildworld without X11, regardless if X11 exists. If I want to use it with X11, it is interactive and I can make it for X11 by hand - it will not break on compile runs at some hour at night. I'll commit a fix that will prevent including X when DESTDIR has been set. In practice this means that doscmd will never include X, unless you compile it by hand. This of course implies that you have to compile doscmd by hand every time you do an installworld, given that you want X. Maybe knob in /etc/make.conf instead to force compiling with X? best regards, taavi --- Taavi Talvik| Internet: [EMAIL PROTECTED] Unineti Andmeside AS| phone: +372 6405150 Ravala pst. 10 | fax: +372 6405151 Tallinn 10143, Estonia | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Opera Beta and FreeBSD
On Wed, 5 Jan 2000, Lutz Albers wrote: Works fine, but you need the glibc-2.1 libraries (i.e. from RedHat 6.1), as it is linked against these. Keep in mind that this is no beta, but a 'technical preview', many functions are still missing. FWIW, the linux_base port in http://www.FreeBSD.org/~marcel/ works fine, and probably should be committed. I'm running Nutscrape on that port on several different machines and they're all just fine. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA atapi-all.c problems/fixes/cleanups
On Wed, 5 Jan 2000, Soren Schmidt wrote: Try this patch instead, it should do the right thing.. Since they're functionally the same, sure, I wouldn't mind either way :) -Søren -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / [EMAIL PROTECTED]`--' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: compiling libF77/libI77
On Tue, Jan 04, 2000 at 10:28:28PM +0100, Dave J. Boers wrote: It's funny how I tend to find things out only just _after_ I asked someone If you still need the shared libf2c.so.2 for older binaries, install the latest compat3x distribution. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Proposal: Removing doscmd from the source tree...
A possibility could be: 1. build it for i386 only, 2. build it via buildworld without X11, regardless if X11 exists. If I want to use it with X11, it is interactive and I can make it for X11 by hand - it will not break on compile runs at some hour at night. I'll commit a fix that will prevent including X when DESTDIR has been set. In practice this means that doscmd will never include X, unless you compile it by hand. This of course implies that you have to compile doscmd by hand every time you do an installworld, given that you want X. Maybe knob in /etc/make.conf instead to force compiling with X? best regards, taavi Actually, several ports give you the option of building with or without X support (i.e., SSH). It would be nice to have a USE_X11 option in /etc/make.conf for doscmd as well as these ports, so you don't have to specify it on the command line while building. Of course, I'd like a pony too. And a pink bike shed. ==ml To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Proposal: Removing doscmd from the source tree...
Taavi Talvik wrote: Maybe knob in /etc/make.conf instead to force compiling with X? Nah, we don't need to. doscmd doesn't have X support by default (now that I've committed the fix). Recompiling doscmd to get X (given X is installed on the machine of course) is broken but simple enough. If you don't want X, don't recompile doscmd or don't install X. Any other change only adds to the argument of making doscmd a port (or two), IMO. -- Marcel Moolenaarmailto:[EMAIL PROTECTED] SCC Internetworking Databases http://www.scc.nl/ The FreeBSD projectmailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
making release
Hi. I want to make a release of 4.0-CUR in 3.4-ST. Will it nice idea? Now I cvsuping sources of 4.0. Is there any troubles? And another one question: I don't cvsup "cvs-crypto". Will my release maked? Thanks. ..and sorry for my bad English. ;| P.S. pls reply to me, i'm not currently subscribed. Regards, Listopad Alexandr ([EMAIL PROTECTED]), LAA7-RIPE ZGIA, Zaporozhye, Ukraine. http://www.zgia.zp.ua. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ifq_maxlen in vx-driver
hello *! i am using the vx driver in for my two 3c397 boards. when booting i get the following message: vx0 XXX: driver didn't set ifq_maxlen obviosly the ifq_maxlen is not set in the eisa nor in the pci version in the driver. actually, to set this, would be one line in the driver, but unfrotunatly i am not that familiar with the hardware, and do not know, which value this parameter shoul have. maybe, someone knows ... cheers, oliver -- And remember: "Life sucks and then you die!" email: [EMAIL PROTECTED] [EMAIL PROTECTED] Hi! I'm a .signature virus! Copy me in your ~/.signature to help me spread! - Save this lifeform ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new man pages
On Wed, 5 Jan 2000, Bruce Evans wrote: On Wed, 5 Jan 2000, Ollivier Robert wrote: According to Rodney W. Grimes: xntpd was recently renamed ntpd, but the documentation and manual pages was not. You'll find the manual page for ntpd with a ``man xntpd''. Those are the old man pages. You're not running -current if you have them :-). As far as I can see only the command is removed, the xntpd man page is left alone. I still have it. This is current of December 31. [...] -- Marc Schneiders [EMAIL PROTECTED] [EMAIL PROTECTED] propro3:02pm up 5 days, 16:51, load average: 2.18 2.09 2.05 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: A couple questions regarding pcmcia cards....
Warner Losh wrote: In message [EMAIL PROTECTED] Frank Mayhar writes: : Wups, I thought I read 575BT. But no, the 574BT doesn't work either; there's : a bug somewhere in the driver. I have one of _those_, too, having read the : same thing you did. Last I heard, Matt Dodd had or was waiting for a 574BT and pccard enviornment to fix the driver. He's got both the card and the documentation, courtesy of Terry Murphy at 3Com and my efforts to that end. I have a 3CCFE575CT sitting here on my desk right now as a gentile reminder to work on pccard/cardbus stuff :-). Is that one that Matt sent you? If so, that's the result of the same effort. Else Matt has one, too. -- Frank Mayhar [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ifq_maxlen in vx-driver
On Wed, 5 Jan 2000, Oliver Schonefeld wrote: i am using the vx driver in for my two 3c397 boards. when booting i get the following message: vx0 XXX: driver didn't set ifq_maxlen obviosly the ifq_maxlen is not set in the eisa nor in the pci version in the driver. actually, to set this, would be one line in the driver, but unfrotunatly i am not that familiar with the hardware, and do not know, which value this parameter shoul have. maybe, someone knows ... This is just a warning message; it doesn't hurt anything. I'll deal with if_vx at some point; it will get fixed with if_ed and if_vx get collided at high speed. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: options COMPAT_LINUX makes kernel fail to compile
Well, just make sure that you load the linux compatibility kernel module though. = | Kenneth Culver | FreeBSD: The best OS around.| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Wed, 5 Jan 2000, Michael Lucas wrote: Hello, Not that this is an actual fix to the problem, but: The COMPAT_LINUX kernel option isn't needed any more, per Marcel. (At least, when I wrote an article on this, it wasn't.) You can probably remove COMPAT_LINUX entirely. (If only the rest of the problems were this easy. :) ==ml Hi! With option COMPAT_LINUX (which present in LINT) make depend fails with: cc -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -fno-builtin -mpreferred-stack-boundary=2 -UKERNEL -o linux_genassym.o -c ../../i386/linux/linux_genassym.c genassym -o linux_assym.h linux_genassym.o genassym:No such file or directory *** Error code 1 Dmitry. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: A couple questions regarding pcmcia cards....
On 05-Jan-00 William Woods wrote: ok, now...to get it working... ideas? I am currently using a 3Com 3CCFE574BT with 4.0-CURRENT here. Mind you, that is 4.0-CURRENT as of September 29, right before Matt Dodd's if_ep.c commit that moved towards newcard implementation. You will not be able to use it on any later version of 4.0-CURRENT as far as I know. And I know it does not work with 3.3-RELEASE. You may have better luck with 3.4-RELEASE, but I wouldn't know. /me waits for Matt to fix if_ep *patiently* ;-) I know it's coming soon. *twiddle thumbs* -- Will Andrews [EMAIL PROTECTED] GCS/E/S @d- s+:++:- a---+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP t++ 5 X++ R+ tv+ b++ DI+++ D+ G+ e- h! r--+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Proposal: Removing doscmd from the source tree...
Michael Lucas [EMAIL PROTECTED] wrote in list.freebsd-current: Actually, several ports give you the option of building with or without X support (i.e., SSH). It would be nice to have a USE_X11 option in /etc/make.conf for doscmd as well as these ports, so you don't have to specify it on the command line while building. Of course, I'd like a pony too. And a pink bike shed. Me too! :) I'm currently trying to fix the POV-Ray port. It could be built with and without X11 support, too, and it would be very useful to have a way to let the user choose. A USE_X11 knob in make.conf would be great. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:[EMAIL PROTECTED]) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
rlogin from 3.X to 4.0 problem...
With the 991229 shapshot, from a FreeBSD 3.3 or 3.4 machine: rlogin bsd4 assword:hey this is great! why is the initial 'P' missing, and the password echoed ? cheers luigi ---+- Luigi RIZZO, [EMAIL PROTECTED] . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) Mobile +39-347-0373137 ---+- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: A couple questions regarding pcmcia cards....
In message [EMAIL PROTECTED] "Matthew N. Dodd" writes: : Anyone know of a PCI Cardbus bridgeboard? I'd rather not have to get a : laptop just so I can play with cardbus. I've seen two, both of which seem to be unavailable. One is at a URL that I've lost and the other was made by compaq and was available for their desktop machines. CDW used to carry this, but it is unavailable now as well. I'll have to dig up the URL that I've lost (it is in my netscape history file, I'm sure) since they talked about availablities after the first of the year which is why I blew them off before (it was in October or so I was looking). I'll send you something if I can find it. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: rlogin from 3.X to 4.0 problem...
On Wed, Jan 05, 2000 at 18:33:40 +0100, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Luigi Rizzo writes: With the 991229 shapshot, from a FreeBSD 3.3 or 3.4 machine: rlogin bsd4 assword:hey this is great! why is the initial 'P' missing, and the password echoed ? Bug in /etc/pam.conf Fixed with pam.conf version 1.4. Regards --- Udo Schweigert || Voice : +49 89 636 42170 Siemens AG, Siemens CERT|| Fax: +49 89 636 41166 ZT IK 3 || email : [EMAIL PROTECTED] D-81730 Muenchen / Germany ||: [EMAIL PROTECTED] PGP fingerprint || 2A 53 F6 A6 30 59 64 02 6B C4 E0 73 B2 C9 6C E7 --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: options COMPAT_LINUX makes kernel fail to compile
David Scheidt wrote: On Wed, 5 Jan 2000, Michael Lucas wrote: Hello, Not that this is an actual fix to the problem, but: The COMPAT_LINUX kernel option isn't needed any more, per Marcel. (At least, when I wrote an article on this, it wasn't.) You can probably remove COMPAT_LINUX entirely. I use COMPAT_LINUX because I make kernels more frequently then I make world or modules. I get fewer panics that way. David Scheidt You should definately use a static kernel without modules if you are tracking -current and rebuilding regularly. It is too easy to shoot yourself in the foot by getting /modules and the kernel out of sync while the internal interfaces are still changing. Using kld's to develop drivers is different. Cheers, -Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: A couple questions regarding pcmcia cards....
Here is the pccard.conf entry: # 3Com Fast Etherlink 3C574TX card "3Com" "Megahertz 574B" config 0x1 "ep0" ? 0x1 insert echo 3Com Fast Etherlink 3C574B inserted insert /etc/pccard_ether ep0 remove echo 3Com Fast Etherlink This is on a 3.4 -stable system On 05-Jan-00 Warner Losh wrote: In message [EMAIL PROTECTED] will andrews writes: : I am currently using a 3Com 3CCFE574BT with 4.0-CURRENT here. Mind you, that : is What does your pccard.conf entry look like for it? Warner -- E-Mail: William Woods [EMAIL PROTECTED] Date: 05-Jan-00 Time: 10:23:02 FreeBSD 3.4 -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
4.0 code freeze scheduled for Jan 15th
And given that we've already slipped from December 15th, I think you can treat this as a pretty hard deadline, to be further slipped only grudgingly and in response to clear and dire need. 10 days, folks! Make 'em count.. :) The code freeze will last for 15 days, during which time the 4.0 snapshot server (current.freebsd.org) will be cranking out its daily snapshots (and, in the last half of the release cycle, ISO images as well). There will be an additional 10 days following 4.0-RELEASE before the final CD images are made, it being our goal to get the bugs worked out of the net release before the CDs are made in the future. This will result in some additional lag to CD customers, but they'll also get a product with the sharp edges filed off in return for the delay and I think it's worth-while since CDs are a lot harder to update than FTP sites. :-) If someone would care to volunteer an Alpha which has good network connectivity and enough "oomph" to create a full release every night, I'd also be happy to drag the Alpha architecture into this process of doing some actual release QA by porting my snapshot building scripts over and starting them up. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS-UP newppbus for beta-testing
Nicolas Souchu wrote: On Mon, Jan 03, 2000 at 09:24:52PM +0200, Maxim Sobolev wrote: Nicolas Souchu wrote: Hi there! FOR ANYBODY THAT USES ZIP/PRINTER/PLIP ON THE PARALLEL PORT UNDER -current A major ppbus(4) release is available for beta-testing. Good work! Now plip, which has been broken for ages, works perfectly - no more lockups, spontaneous reboots, panics, etc! To test it I even managed to get X and NFS working over plip line, things which was impossible with oldppbus. Nice! But, sure the 'net' interrupt level mask (at the ppc0 declaration) in you MACHINE config file would have done the job. Unfortunately it is not a solution because net,tty and bio keywords went away from config(8) long time ago... I've only received `syntax error' message. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: error messages while loading the kernel
"Robert C. Noland III" wrote: I have seen that as well... It seems to be caused by svr4_enable="YES" in rc.conf. or rather the specified module. I'd say any module : multi% kldstat Id Refs AddressSize Name 12 0xc010 1c4b58 kernel 41 0xc1155000 2000 blank_saver.ko multi% I don't use the svr4 emulation TfH robert. Thierry Herbelot writes: I've just remade the world and a new kernel with sources supped around 21h00 GMT today, and I've got error messages in the kernel loading phase (on an SMP machine : bi-celeron BP6) link_elf: symbol zfree undefined link_elf: symbol zfree undefined full dmesg available upon request, if necessary FreeBSD multi.herbelot.nom 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Wed Jan 5 23:15:23 CET 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/multi i386 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Mounting CD-ROM with ATA driver hangs system
I just discovered that my ATAPI CD-ROM is no longer usable - when I
try to mount it, my maching hangs (hard).
I'm running -current from cvs-cur 5961 (Monday about UTC).
The symptoms are:
Run "mount -r /dev/acd0c /cdrom"
The CD-ROM activity light flashes briefly and the CD-ROM spins up.
The activity light then goes hard on for something like 20 seconds.
The kernel then prints:
acd0: atapi_timeout: cmd=READ_BIG - resetting
ata0: resetting devices .. _
The cursor remains at the end of the line ("_" above). The CD-ROM
spins up and down. The HDD light stays hard on.
At this point, the system will not respond to the keyboard.
I didn't have any problems with the WD driver, so I don't think it's
hardware.
Any ideas?
Dmesg output:
Copyright (c) 1992-2000 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 4.0-CURRENT #15: Thu Jan 6 08:02:56 EST 2000
[EMAIL PROTECTED]:/3.0/cvs/src/sys/compile/gsmx
Timecounter "i8254" frequency 1193182 Hz
Timecounter "TSC" frequency 267310659 Hz
CPU: Pentium II (267.31-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x633 Stepping = 3
Features=0x80f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,MMX
real memory = 67108864 (65536K bytes)
avail memory = 61980672 (60528K bytes)
Preloaded elf kernel "kernel" at 0xc0301000.
VESA: v2.0, 4096k memory, flags:0x1, mode table:0xc02b1e22 (122)
VESA: Matrox Graphics Inc.
Pentium Pro MTRR support enabled
npx0: math processor on motherboard
npx0: INT 16 interface
pcib0: Intel 82443LX (440 LX) host to PCI bridge on motherboard
pci0: PCI bus on pcib0
pcib1: Intel 82443LX (440 LX) PCI-PCI (AGP) bridge at device 1.0 on pci0
pci1: PCI bus on pcib1
isab0: Intel 82371AB PCI to ISA bridge at device 7.0 on pci0
isa0: ISA bus on isab0
ata-pci0: Intel PIIX4 ATA controller at device 7.1 on pci0
ata-pci0: Busmastering DMA supported
ata0 at 0x01f0 irq 14 on ata-pci0
ata1 at 0x0170 irq 15 on ata-pci0
pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 7.2 irq 11
chip1: Intel 82371AB Power management controller at device 7.3 on pci0
vga-pci0: Matrox MGA 2164W graphics accelerator irq 10 at device 9.0 on pci0
tx0: SMC 83c170 irq 9 at device 10.0 on pci0
tx0: address 00:e0:29:24:34:1f, type SMC9432TX, Auto-Neg 100Mbps
ed0 at port 0x300-0x31f iomem 0xcc000-0xc irq 7 on isa0
ed0: address 00:00:c0:57:99:47, type WD8013EPC (16 bit)
atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa0
atkbd0: AT Keyboard irq 1 on atkbdc0
psm0: PS/2 Mouse irq 12 on atkbdc0
psm0: model Generic PS/2 mouse, device ID 0
vga0: Generic ISA VGA at port 0x3b0-0x3df iomem 0xa-0xb on isa0
sc0: System console on isa0
sc0: VGA 16 virtual consoles, flags=0x200
ata-isa0: already registered as ata0
ata-isa1: already registered as ata1
fdc0: NEC 72065B or clone at port 0x3f0-0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: 1440-KB 3.5" drive on fdc0 drive 0
fd1: not probed (disabled)
sio0 at port 0x3f8-0x3ff irq 4 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
pca0 at port 0x40 on isa0
pca0: PC speaker audio driver
isa_compat: didn't get irq for ppc
ppc0 at port 0x378-0x37f irq 7 on isa0
isa_compat: didn't get irq for ppc
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
plip0: PLIP network interface on ppbus 0
lpt0: generic printer on ppbus 0
lpt0: Interrupt-driven port
ppi0: generic parallel i/o on ppbus 0
pps0: Pulse per second Timing Interface on ppbus 0
sbc0: Creative ViBRA16X at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,3 on
isa0
sbc0: setting card to irq 5, drq 1, 3
pcm0: SB DSP 4.16 (ViBRA16X) on sbc0
joy0: Generic PnP Joystick at port 0x201 on isa0
ad0: FUJITSU MPB3064ATU E/4010 ATA-3 disk at ata0 as master
ad0: 6187MB (12672450 sectors), 13410 cyls, 15 heads, 63 S/T, 512 B/S
ad0: 16 secs/int, 1 depth queue, UDMA33
ad2: QUANTUM FIREBALL_TM1280A/A6B.2D00 ATA-0 disk at ata1 as master
ad2: 1222MB (2503872 sectors), 2484 cyls, 16 heads, 63 S/T, 512 B/S
ad2: 16 secs/int, 1 depth queue, DMA
acd0: CD-ROM CDU611/2.0a CDROM drive at ata0 as slave
acd0: read 1723KB/s (1723KB/s), 256KB buffer, DMA
acd0: Reads: CD-R, CD-RW, CD-DA stream
acd0: Audio: play, 16 volume levels
acd0: Mechanism: ejectable tray
acd0: Medium: CD-ROM 120mm data disc loaded, unlocked
Mounting root from ufs:/dev/ad0s2a
Peter
--
Peter Jeremy (VK2PJ)[EMAIL PROTECTED]
Alcatel Australia Limited
41 Mandible St Phone: +61 2 9690 5019
ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
problem building XFree86 (pre-3.3.6) on a recent Freebsd 4.0-current
I've just been doing a build test of the pre-3.3.6 version of XFree86 on a recent FreeBSD 4.0-current, and I've noticed that /usr/libexec/cpp doesn't predefine the symbol __FreeBSD__. imake uses /usr/libexec/cpp. Is it intentional that /usr/libexec/cpp not predefine any symbols like this? I've changed imake to use /usr/bin/cpp instead, and it seems to work on 3.4 and 4.0. Should this be OK on all FreeBSD versions? --- imakemdep.h 1999/07/29 09:22:27 3.24.2.14 +++ xc/config/imake/imakemdep.h 2000/01/06 04:39:59 @@ -265,8 +265,11 @@ #ifdef _CRAY #define DEFAULT_CPP "/lib/pcpp" #endif -#if defined(__386BSD__) || defined(__NetBSD__) || defined(__OpenBSD__) || defined(__FreeBSD__) +#if defined(__386BSD__) || defined(__NetBSD__) || defined(__OpenBSD__) #define DEFAULT_CPP "/usr/libexec/cpp" +#endif +#if defined(__FreeBSD__) +#define DEFAULT_CPP "/usr/bin/cpp" #endif #if defined(__sgi) defined(__ANSI_CPP__) #define USE_CC_E David -- David Dawes Email: [EMAIL PROTECTED] Co-founder/President, The XFree86 Project, Inc Phone: +1 570 775 9502 http://www.xfree86.org/ Fax: +61 2 9897 3755 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0 code freeze scheduled for Jan 15th
:This is a cryptographically signed message in MIME format. : :--ms7B55930FA2AAFE9EE4D45CA1 :Content-Type: text/plain; charset=us-ascii :Content-Transfer-Encoding: 7bit : : :Stupid question: will the latest PAO stuff be integrated with 4.0? : : :-dpg :--ms7B55930FA2AAFE9EE4D45CA1 :Content-Type: application/x-pkcs7-signature; name="smime.p7s" :Content-Transfer-Encoding: base64 :Content-Disposition: attachment; filename="smime.p7s" :Content-Description: S/MIME Cryptographic Signature : :MIIKLgYJKoZIhvcNAQcCoIIKHzCCChsCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC :B7owggSEMIID7aADAgECAhAV4oOYVg1pE0gVFzzXJ4WbMA0GCSqGSIb3DQEBBAUAMIHMMRcw :FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y :... :... lots of junk removed :... What is all ^^^ this junk? Can you post without adding all of this? -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: problem building XFree86 (pre-3.3.6) on a recent Freebsd 4.0-current
On Wed, Jan 05, 2000 at 09:15:07PM -0800, David O'Brien wrote: Correct. The change is due to philosophical changes by the GCC development team. GCC 2.95.2's cpp built from cccp.c is now a pure preprocessor and knows much less about the world than it previously did. In 2.95.2 there is now an additional cpp that is build using gcc.c and is a driver for the cccp.c cpp. I dare you to try saying that again with a mouth full of peanuts! - mark :-) -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
