Re: Integrated Vibra16 in -current
Andy Sparrow wrote: [..] I've got a Micron W6-Li Lightning board with integrated Creative Vibra16X and Adaptec 7880, and I run a WinTV card as well. I also have the ISA Waveblaster daughter card that makes the sound setup effectively an AWE32. We probably need to find out what the PnP device ID is if it doesn't get found under pcm0/sbc0. Given the Plug'n'Pray changes in -current, I pretty much expected to lose AWE32 support (as I can no longer use the 'pnp' commands in 'userconfig' to probe the "magic" ports for the AWE32). However, I wasn't expecting to lose the ability to use VoxWare altogether. How about 'device pcm0' and 'device sbc0'? Without PNPBIOS, I got these messages (config file was the same one as used under -STABLE, just converted by the simple expedient of fixing the complaint s from 'config', mostly changing 'controller' to 'device' etc.): sb_reset_dsp failed sb_reset_dsp failed awe0 at port 0x620 on isa0 AWE32: not detected unknown0: WaveTable at port 0x621-0x624 on isa0 unknown1: Audio at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,3 o n isa0 unknown2: Game at port 0x201 on isa0 The output of 'pnpinfo' would be useful. I tried adding PNPBIOS to the kernel options, with little improvement: PNPBIOS gets extra info about devices including the motherboard resources. It is only useful for PnP-aware device drivers, such as pcm/sbc etc. Voxware is not a PnP-aware device driver so don't expect it to work on a PnP card. Switching 'PNP OS = YES' in the BIOS setup (it's a Phoenix BIOS) didn't seem to make any difference to anything. PNP OS = YES tells the motherboard to not bother configuring any hardware that isn't needed to boot. This means things like sound cards and other devices (pci and isa) are left in a totally unconfigured state. Worse, with PNPBIOS enabled, the WinTV card would not work either: bktr0: BrookTree 878 irq 17 at device 17.0 on pci0 bktr0: could not map memory device_probe_and_attach: bktr0 attach returned 6 pci0: unknown card (vendor=0x109e, dev=0x0878) at 17.1 irq 17 This is because the bt878 has not been assigned any memory addresses. We don't do PCIBIOS calls to reassign these yet, so if you use 'PNP OS = YES' you are asking for trouble. In fact, in -current, there's a few things that look odd. I always get this complaint from the BrookTree driver (which I've never seen on 3.x): pci0: unknown card (vendor=0x109e, dev=0x0878) at 17.1 irq 17 I get this even if PNPBIOS isn't an option, and the card actually works... This is a quirk of the bt878 device and drivers. There are actually two logical devices in the chip: bktr0@pci0:10:0: class=0x04 card=0x217d6606 chip=0x036e109e rev=0x02 none0@pci0:10:1: class=0x048000 card=0x217d6606 chip=0x0878109e rev=0x02 For whatever reason, the bktr driver is only interested in the first one and leaves the second one unconfigured. and I always see this too devclass_alloc_unit: npx0 already exists, using next available unit number This is because you have 'device npx0 at isa? ...' - see GENERIC, it's supposed to be 'at nexus?' or just 'device npx0'. Using the 'pcm0' and 'sbc0' driver (without any 'at isa?' etc. and without PNPBIOS so the WinTV card is usable) seems to work fine, but I'm a little confused as to why the VoxWare stuff can't work anymore. It's 'PNP OS = YES' that messes up the WinTV, not PNPBIOS. Ahh, pcm/sbc do work.. Use that then, the Voxware code's days are numbered. Last but not least, 'xmcd' doesn't work for me under -CURRENT (integrated AIC-7880 and Plextor PX-12TSi CD-ROM), it never recognises that a CD is inserted, and an attempt to eject the CD from 'xmcd' gives a 'Inappropriate IOCTL for device' message (sorry, I didn't make a note of the tag on the front). This is a different set of problems. make sure you are using an up-to-date port and that you have rerun MAKEDEV to create the required devices in /dev (in particular the xpt* and pass* devices.) Also, make sure you have 'device pass0' in your kernel config. Is this breakage of the built-in Vibra with VoxWare expected? Surprised the heck out of me... Pretty much, yes. :-/ Cheers, -Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Feature test for OpenSSL + RSA
On Jan 17 Kris Kennaway wrote:
On Tue, 18 Jan 2000, jack wrote:
On Jan 17 Kris Kennaway wrote:
+ rm -f /etc/ssl/openssl_hasrsa
Doh, I meant /bin/rm
No, you meant ${RM}
I couldn't find this defined in /usr/share/mk/* - it's only in
bsd.port.mk, AFAICT.
Ummm, yeah. Sorry, I had ports on the brain since that's where
I keep getting bit by all this lately.
--
Jack O'NeillSystems Administrator / Systems Analyst
[EMAIL PROTECTED] Crystal Wind Communications, Inc.
Finger [EMAIL PROTECTED] for my PGP key.
PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD
enriched, vcard, HTML messages /dev/null
--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: new nexus.c breaks kernel build
Manfred Antar wrote: The new version of nexus.c (1.23) breaks current kernel build : cc -c -O2 -Os -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../i386/i386/nexus.c ../../i386/i386/nexus.c: In function `nexus_deactivate_resource': ../../i386/i386/nexus.c:341: `rv' undeclared (first use in this function) ../../i386/i386/nexus.c:341: (Each undeclared identifier is reported only once ../../i386/i386/nexus.c:341: for each function it appears in.) ../../i386/i386/nexus.c:345: warning: passing arg 1 of `pmap_unmapdev' makes integer from pointer without a cast *** Error code 1 Same is here. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 3C589 problems (was: 4.0 code freeze scheduled for Jan 15th)
On Monday, 17 January 2000 at 8:24:20 -0800, Frank Mayhar wrote: Sorry for the delay on this reply; I was going over some old email and came across this only a week late. Jonathan Chen wrote: With what little pccard/ethernet programming experiences I've had, this problem seems to be caused by the interrupt for the card getting lost somewhere before getting processed by the handler. The reason you still get traffic is because of the watchdog. (Try uncommenting the commented out lines in sys/dev/ep/if_ep.c in the function ep_if_watchdog(), you should start seeing lots of kernel messages saying "ep: watchdog".) After looking briefly at the ep files, I saw something that doesn't seem right. In sys/dev/ep/if_ep_pccard.c around line 176, there's a comment that says "Fake IRQ must be 3". Now maybe the card requires it, or maybe the original author just didn't have anything on IRQ 3, I don't know. So, I'd suggest turning off com2 or whatever you have on irq3, -or- change the "fake irq" to something else you do have free on the next line (ie, 0x3000- 0xa000 if you have IRQ10 free). If this works, great... if not, I hope Warner gets some more free time. ;) According to the docs, this "Fake IRQ must be 3" is legitimate. The IRQ programmed into the resource config register in window 0 _must_ be 3: "any other value will disable the IRQ line drivers." (Quoted from the doc. As for the other problem with collisions, I did a search on the word collision on sys/dev/ep/if_ep.c, and found only one mention at around line 620. The comment says "TXS_MAX_COLLISION - we shouldn't get here". I suspect it does get there, so I suggest putting a printf there to find out. I also suspect that the card may require a reset or some other stuff if and when it "gets there". If that's the case, someone else with the specs on the 589 cards can look that up and do it. I can state pretty categorically that, at least in my case, we're _not_ getting here. As I said in an earlier email, I'm still having interrupt problems with the 589 (I have a 3C589D) and the 574BT. I haven't tracked it down yet, but I'm hunting. I do know, at least, that I'm not receiving _any_ interrupts from either card. So far I don't know why. The fact it's appearing with two different cards which work for other people tends to point away from the cards and towards some common factor, such as your laptop. Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86 3.9.17
(trimmed the long cc:-list) On Tue, Jan 18, 2000 at 07:51:22AM +0200, Vallo Kallaste wrote: The problem with 3.3.5 was something to do with refreshing, example after doing some ls -la in xterm the xterm screen got blank completely or showed some lines of text in the bottom but otherwise remained black. I noticed no such problems since running 3.3.5 in 1600x1200/bpp16. Am I just lucky? My board is a G400DH32. -Andreas -- The computer revolution is over. The computers won. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: installworld fails with setresuid.2.gz
On Tue, 18 Jan 2000 13:46:36 +0900, Munehiro Matsuda wrote: /usr/share/man/man2/setresgid.2.gz - /usr/share/man/man2/setresuid.2.gz ln: /usr/share/man/man2/setresuid.2.gz: No such file or directory *** Error code 1 My fault. It's fixed in rev 1.75 of src/lib/libc/sys/Makefile.inc . Sorry for the inconvenience. :-( Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Feature test for OpenSSL + RSA
On Mon, 17 Jan 2000 21:53:10 PST, Kris Kennaway wrote:
+.if defined(WITH_RSA) ${WITH_RSA} == YES
+ /usr/bin/touch /etc/ssl/openssl_hasrsa
Um, are you sure you want that hard path, /etc/ssl ? Shouldn't there be
a ${DESTDIR} in there? What do you need this for?
Ciao,
Sheldon.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Is texinfo needed for buildworld with -DNOINFO ?
Hi all,
It seems that texinfo is compiled as cross-tools for buildworld.
But, is it really needed when -DNOINFO has been specified?
Following patch seems to work for me.
--- Makefile.inc1.ctm Tue Jan 18 03:15:10 2000
+++ Makefile.inc1 Tue Jan 18 10:21:06 2000
@@ -527,11 +527,14 @@
.if ${TARGET_ARCH} == "i386" ${MACHINE} == "pc98"
_aout_tools= usr.bin/size usr.bin/strip gnu/usr.bin/as gnu/usr.bin/ld
.endif
+.if !defined(NOINFO)
+_info_tools= gnu/usr.bin/texinfo
+.endif
cross-tools:
.for _tool in ${_aout_tools} ${_btxld} ${_elf2exe} usr.bin/genassym \
usr.bin/gensetdefs gnu/usr.bin/binutils usr.bin/objformat gnu/usr.bin/cc \
-gnu/usr.bin/texinfo
+${_info_tools}
cd ${.CURDIR}/${_tool}; \
${MAKE} obj; \
${MAKE} depend; \
Thank you,
Haro
=--
_ _Munehiro (haro) Matsuda
-|- /_\ |_|_| Office of Business Planning Developement, Kubota Corp.
/|\ |_| |_|_| 1-3 Nihonbashi-Muromachi 3-Chome
Chuo-ku Tokyo 103, Japan
Tel: +81-3-3245-3318 Fax: +81-3-32454-3315
Email: [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Is texinfo needed for buildworld with -DNOINFO ?
On Tue, Jan 18, 2000 at 07:14:19PM +0900, Munehiro Matsuda wrote: Hi all, It seems that texinfo is compiled as cross-tools for buildworld. But, is it really needed when -DNOINFO has been specified? Yes, because we need an up-to-date makeinfo to be able to build newer info's (like those in texinfo itself and grep). Your patch does work only for the reason that you're not building texinfo plus info build for grep has been disabled till today. The world breakage has been fixed in src/Makefile.inc1,v 1.130 by moving gnu/usr.bin/texinfo before gnu/usr.bin/cc: http://www.freebsd.org/cgi/cvsweb.cgi/src/Makefile.inc1?r1=1.129r2=1.130 Cheers, -- Ruslan Ermilov Sysadmin and DBA of the [EMAIL PROTECTED]United Commercial Bank, [EMAIL PROTECTED] FreeBSD committer, +380.652.247.647Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Is texinfo needed for buildworld with -DNOINFO ?
On Tue, 18 Jan 2000 19:14:19 +0900, Munehiro Matsuda wrote: It seems that texinfo is compiled as cross-tools for buildworld. But, is it really needed when -DNOINFO has been specified? It's arguable, so I'd go with the status quo -- always build and install the texinfo program, even if info files are not to be installed. Following patch seems to work for me. Only because you have NOINFO defined. Try without it. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Feature test for OpenSSL + RSA
Sheldon Hearn wrote:
On Mon, 17 Jan 2000 21:53:10 PST, Kris Kennaway wrote:
+.if defined(WITH_RSA) ${WITH_RSA} == YES
+ /usr/bin/touch /etc/ssl/openssl_hasrsa
Um, are you sure you want that hard path, /etc/ssl ? Shouldn't there be
a ${DESTDIR} in there? What do you need this for?
Yes, This should most definately have ${DESTDIR} for this sort of thing, but
even then I'm not sure this is a good change.. We have got to find a better
way than this.
Cheers,
-Peter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: 3C589 problems (was: 4.0 code freeze scheduled for Jan 15th)
Greg Lehey wrote: The fact it's appearing with two different cards which work for other people tends to point away from the cards and towards some common factor, such as your laptop. True. Interestingly, I rebuilt world with the latest pccardd changes and, suddenly, the 589D started working perfectly. Unfortunately, the 574BT doesn't work at all now. It appears to configure properly, but it doesn't transmit or receive. -- Frank Mayhar [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Is texinfo needed for buildworld with -DNOINFO ?
On Tue, Jan 18, 2000 at 12:31:18PM +0200, Sheldon Hearn wrote:
On Tue, 18 Jan 2000 19:14:19 +0900, Munehiro Matsuda wrote:
It seems that texinfo is compiled as cross-tools for buildworld.
But, is it really needed when -DNOINFO has been specified?
It's arguable, so I'd go with the status quo -- always build and install
the texinfo program, even if info files are not to be installed.
The problem is that `{bootstrap,cross}-tools' are always built with
-DNOINFO, and thus there is no way to determine wherher the user
explicitly requested -DNOINFO or not.
--
Ruslan Ermilov Sysadmin and DBA of the
[EMAIL PROTECTED]United Commercial Bank,
[EMAIL PROTECTED] FreeBSD committer,
+380.652.247.647Simferopol, Ukraine
http://www.FreeBSD.org The Power To Serve
http://www.oracle.com Enabling The Information Age
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
mergemaster and new files
Does mergemaster automatically pick up on new files (if they have been added to the Makefile in src/etc that is)? I was wondering whether people have noticed and had usbd.conf installed by using mergemaster. Nick -- [EMAIL PROTECTED] [EMAIL PROTECTED] USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NEC ohci
Try running usbd -e and see if that makes your mouse show up. usbd -e does the explore once. The reason we need the daemon is that the kernel does not have kernel threads yet. Nick On Fri, 14 Jan 2000, Mike Smith wrote: You need usbd running; see /etc/rc.conf My friend has Toshiba's notebook which has NEC ohci USB controller. He installed FreeBSD-current but it cannot recognize USB device attach/detach signal. If USB mouse was plugged in at boot time, ohci found ums0 device and we can use it. But after booting without plugged mouse, we have no message after plugging USB mouse. Is there people who can use USB device with this chip? - ohci0: NEC uPD 9210 USB controller irq 11 at device 11.0 on pci0 usb0: OHCI version 1.0 usb0: NEC uPD 9210 USB controller on ohci0 usb0: USB revision 1.0 uhub0: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered - Jun Kuriyama // [EMAIL PROTECTED] // [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- [EMAIL PROTECTED] [EMAIL PROTECTED] USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: USB D-Link DSB-650 kue0: failed to load code
Both are specifications for USB Host controllers. The difference between them is internals of the chip and the interface exposed on the PCI bus. In brief: OHCI is made by M$ and emphasizes the fact that hardware should be smart to facilitate the software's task. UHCI is made by Intel and stupid, in order to facilitate a low gate count. Bottom line, OHCI has some brains and is actually able to transfer 8kb transfers in one go. UHCI needs to be told _every_sinle_thing_ about a transfer: transfer descriptors, size of transfers, but also the sequence in which iso, interrupt, bulk and control transfers need to be done. Also the number of interrupts is large, and when an interrupt happens you'll have to search for the transfer that created the interrupt. Overhead on the PCI bus should be lower for OHCI as the controller only has to fetch the description for the transfer once and then can transfer up to 1kb on the bus in one go. OHCI is being used in firewire as well I believe. UHCI will not be able to support those speeds (nor will it support USB2.0 without some change of the specification) Both host controllers will support all the USB devices and there should be no difference in using either of them. There will be some devices that are supported by one or the other, but those devices are probably old (some Genius mice come to mind) and newer devices should not have those problems. In FreeBSD the problem is that UHCI is slightly better supported than OHCI. isochronous transport does not work yet with OHCI. Also, I have been too lazy (busy?) to fix a few major issues with ohci and recognising devices. Apologies for that, but no one was willing to pay me for doing the open source FreeBSD USB stuff (until now) and time was limited due to some external factors. Hope this explains a bit. Nick On Mon, 17 Jan 2000, Alex Zepeda wrote: On Mon, 17 Jan 2000, Bill Paul wrote: I also noticed that performance with the OHCI controller is significantly better than with the UHCI controller. Just my rotten luck I'm stuck with a UHCI one in my laptop. Ok, with all this flurry of USB development, I keep seeing UHCI and OHCI. What's the difference? - alex who thought USB ethernet was bad until he had to buy an AAUI transciever .. builtin ethernet my ass To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- [EMAIL PROTECTED] [EMAIL PROTECTED] USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mandating USA_RESIDENT
* From: Kris Kennaway [EMAIL PROTECTED] * On Mon, 17 Jan 2000, David O'Brien wrote: * * Due to the concequence involved, you really do need to check for 'NO', * 'YES', and "other". Rather than combining 'YES' and "other". * * You're suggesting not building openssl at all if they don't have a boolean * value? Maybe it's better to make it an error to not specify it (yes, killing "make world" and stuff, that's what UPDATING is for). Won't people get into legal trouble (technically) if they build the wrong version? Satoshi To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mergemaster and new files
On Tue, Jan 18, 2000 at 10:43:06AM +, Nick Hibma wrote: Does mergemaster automatically pick up on new files (if they have been added to the Makefile in src/etc that is)? I was wondering whether people have noticed and had usbd.conf installed by using mergemaster. Yes .. i have noticed several occasions of mergemaster pointing out to me that a file from /usr/src/etc didn't exist in my own /etc tree yet. -- Pascal Hofstee - [EMAIL PROTECTED] -BEGIN GEEK CODE BLOCK- Version: 3.1 GCS 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+ --END GEEK CODE BLOCK-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newpcm
Hi ... URL:http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=245121+249137+/usr/local/www/db/text/1998/freebsd-multimedia/19980215.freebsd-multimedia I (and many others, I'm sure) would be very grateful if somebody would implement Luigi's first suggestion, to wit: I get the hint :) 1) complete the SETFRAGMENT (or whatever it is called) implementation (not hard, you just need to reduce the blocksize in the dma buffer descriptor and reset the dma channel; I had a look at the current pcm in -current ... there is code to change the second snd buffer size when it is requested ... but I'm not exactly sure what is the difference between the first and second buffer I stil have to find out how to "reset" the dma channel ... because I don't see that that is done anywhere Anyone with some help :) The ioctl in question is SNDCTL_DSP_SETFRAGMENT. Its semantics are described in the "Making audio complicated" section of the OSS Programmer's Guide: URL:http://www.opensound.com/pguide/audio2.html. I'm having a look at this too :) Reinier To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PnP probing in -current
In message [EMAIL PROTECTED] Brian Somers writes: : : Without saying it's ``at isa?'' I get only one aha failed line (I'm : I take that back. The card isn't seen now unless I say ``at isa?''. Please send me the dip switches on the aha1542CP. And the config lines that work and don't work, plus the config file that you are using. Where UP == OFF, from 1-8 I've got UP, UP, UP, UP, DOWN, UP, DOWN, DOWN Needless to say (you wanna see the state of this place), I can't seem to find the manual at the moment :-/ WRT my config, I've got device aha0 at isa? port ? irq ? Warner -- Brian [EMAIL PROTECTED][EMAIL PROTECTED] http://www.Awfulhak.org [EMAIL PROTECTED] Don't _EVER_ lose your sense of humour ! [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Is texinfo needed for buildworld with -DNOINFO ?
On Tue, 18 Jan 2000, Ruslan Ermilov wrote:
On Tue, Jan 18, 2000 at 12:31:18PM +0200, Sheldon Hearn wrote:
On Tue, 18 Jan 2000 19:14:19 +0900, Munehiro Matsuda wrote:
It seems that texinfo is compiled as cross-tools for buildworld.
But, is it really needed when -DNOINFO has been specified?
It's arguable, so I'd go with the status quo -- always build and install
the texinfo program, even if info files are not to be installed.
The patch is a (small) optimization. It happens to avoid the bug when
NOINFO is set for the whole world.
The problem is that `{bootstrap,cross}-tools' are always built with
-DNOINFO, and thus there is no way to determine wherher the user
explicitly requested -DNOINFO or not.
Not a problem. Only Makefile.1 needs to know whether the user set it.
Bruce
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Mandating USA_RESIDENT
On 18 Jan 2000 03:03:09 PST, Satoshi - Ports Wraith - Asami wrote: Maybe it's better to make it an error to not specify it (yes, killing "make world" and stuff, that's what UPDATING is for). There's no better time for doing so than prior to 4.0-RELEASE. :-) Does sysinstall set this one? If not, it should. Then we can stop worrying about it. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86 3.9.17
On Tue, Jan 18, 2000 at 07:51:22AM +0200, Vallo Kallaste [EMAIL PROTECTED] wrote: I can say that I tried building the 3.9.17 with both official compiler in -current and also with gcc-devel, both built fine but didn't install. Seems like my fault, nothing else. Time to try again. It seems there are newer version of 3.9.17 sources released in between my last build attempt. The src-[12] tarballs are both different from the ones in ftp.xfree86.org... -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Is texinfo needed for buildworld with -DNOINFO ?
On Tue, Jan 18, 2000 at 11:47:27PM +1100, Bruce Evans wrote:
On Tue, 18 Jan 2000, Ruslan Ermilov wrote:
On Tue, Jan 18, 2000 at 12:31:18PM +0200, Sheldon Hearn wrote:
On Tue, 18 Jan 2000 19:14:19 +0900, Munehiro Matsuda wrote:
It seems that texinfo is compiled as cross-tools for buildworld.
But, is it really needed when -DNOINFO has been specified?
It's arguable, so I'd go with the status quo -- always build and install
the texinfo program, even if info files are not to be installed.
The patch is a (small) optimization. It happens to avoid the bug when
NOINFO is set for the whole world.
The problem is that `{bootstrap,cross}-tools' are always built with
-DNOINFO, and thus there is no way to determine wherher the user
explicitly requested -DNOINFO or not.
Not a problem. Only Makefile.1 needs to know whether the user set it.
How's that not a problem? The current Makefile.inc1 is written so,
that bootstrap-tools are built with:
BMAKE=${BMAKEENV} ${MAKE} -f Makefile.inc1 -DNOMAN -DNOINFO -DNOHTML
So, how inside the Makefile.inc1's bootstrap-tools: target I could know
whether the user requested NOINFO, or Makefile.inc1 itself?
--
Ruslan Ermilov Sysadmin and DBA of the
[EMAIL PROTECTED]United Commercial Bank,
[EMAIL PROTECTED] FreeBSD committer,
+380.652.247.647Simferopol, Ukraine
http://www.FreeBSD.org The Power To Serve
http://www.oracle.com Enabling The Information Age
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
No Subject
Re: Is texinfo needed for buildworld with -DNOINFO ?
On Tue, 18 Jan 2000, Ruslan Ermilov wrote:
On Tue, Jan 18, 2000 at 11:47:27PM +1100, Bruce Evans wrote:
On Tue, 18 Jan 2000, Ruslan Ermilov wrote:
How's that not a problem? The current Makefile.inc1 is written so,
that bootstrap-tools are built with:
BMAKE=${BMAKEENV} ${MAKE} -f Makefile.inc1 -DNOMAN -DNOINFO -DNOHTML
So, how inside the Makefile.inc1's bootstrap-tools: target I could know
whether the user requested NOINFO, or Makefile.inc1 itself?
Oops. Makefile.inc1 always recurses to builds tools targets with
-DNOINFO, and the tools targets are (should be) internal, so the patch
is just an obfuscated way of removing texinfo from the list.
Bruce
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: mergemaster and new files
On 18/01 12:05, Pascal Hofstee wrote: Yes .. i have noticed several occasions of mergemaster pointing out to me that a file from /usr/src/etc didn't exist in my own /etc tree yet. And if you do a mergemaster -v it will tell you what exists in /etc, but not in /usr/src/etc. Very handy. :-) best; gjvc -- "Readers who only want to see algorithms that are already packaged in a plug-in way, using a trendy language, should buy other people's books." -- D. E. Knuth To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 3C589 problems (was: 4.0 code freeze scheduled for Jan 15th)
On Tue, 18 Jan 2000, Frank Mayhar wrote: Interestingly, I rebuilt world with the latest pccardd changes and, suddenly, the 589D started working perfectly. Unfortunately, the 574BT doesn't work at all now. It appears to configure properly, but it doesn't transmit or receive. Ok, I need the output of 'dmesg', 'ifconfig -a', your kernel config, and 'ident /sys/dev/ep/*'. I suspect you'll find that the 574BT may be in the 'OACTIVE' state as indicated in the flags section of ifconfig. Please try tcpdumping on ep0 and on another box (using the MAC address of the 574) and seeing if any traffic is visable. -- | 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: Is texinfo needed for buildworld with -DNOINFO ?
It seems that texinfo is compiled as cross-tools for buildworld. But, is it really needed when -DNOINFO has been specified? You stole my plan! :-) Once the dust settles and the current crop of `make world' problems are fixed, I want to commit a simular patch as I don't care for info files and don't want to waste time building them. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: grep 2.4a is now in the tree
On Tue, Jan 18, 2000 at 11:00:43AM -0500, Ben Rosengart wrote: On Tue, 18 Jan 2000, Ruslan Ermilov wrote: --binary-files='text' treats binary files as text (equivalent to -a or --text). So "-a" now does the opposite of what it used to do? Not exactly. A stock grep 2.0 did not distinguish between binary and text files. So we (FreeBSD) added -a option, which caused grep to skip binary files. A stock grep 2.3 intoduced a stock -a option. By default, grep 2.3 prints a one-line message "Binary file FOO matches" (if it really matches). Grep 2.4 introduces a --binary-files option, which could be used to either 1) print a one-line message, if files matches; 2) treat the binary files as text files; 3) skip binary files. The equivalent to the old -a option is --binary-files=without-match. If you want this by default, you can hardcode it in GREP_OPTIONS environment variable. For a full story, see src/gnu/usr.bin/grep/NEWS. Cheers, -- Ruslan Ermilov Sysadmin and DBA of the [EMAIL PROTECTED]United Commercial Bank, [EMAIL PROTECTED] FreeBSD committer, +380.652.247.647Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PNPBIOS + Dell PowerEdge = panic()
On Mon, 17 Jan 2000 17:12:14 -0800, Mike Smith [EMAIL PROTECTED] said: This is definitely a bad idea; IMHO we should only do this when the resource is actually activated (and obviously free it when deactivated). Absolutely! As I keep trying to explain to people, that's why there *is* a separate activate function (or one of the reasons, anyway). -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same [EMAIL PROTECTED] | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mandating USA_RESIDENT
Hi, If we are changing the meaning of "USA_RESIDENT", could we replace it by something else completely. I know that the USA are the center of the universe ;-), but... It seems to me that a things progress, the crypto regulation gets more complicated everyday. Why not have a "CRYPTO_COUNTRY" variable that could be set to "USA" "FRANCE" "CANADA" or "other" based where you live and weither special consideration must be taken relative to the crypto code ? Then as part of the build process, automatically create specific variables for RSA or other stuff as they show up: CRYPTO_RSA="RSAref" or CRYPTO_RSA="rsa" or CRYPTO_RSA="none". This can be done by a little bit of shell script easily. The other thing that could be set based on the CRYPTO_COUNTRY code is where to get the FreeBSD crypto related source from. Finally, the current "USA_RESIDENT" variable can then be generated automatically and with good confidence that it is set to a correct value (for the ports or source that still relies on that). OK, it may be overkill for what we need now. So if it looks too much like a bad idea, kill it now. Patrick. - Original Message - From: Sheldon Hearn [EMAIL PROTECTED] Newsgroups: list.freebsd.current Sent: Tuesday, January 18, 2000 8:02 AM Subject: Re: Mandating USA_RESIDENT On 18 Jan 2000 03:03:09 PST, Satoshi - Ports Wraith - Asami wrote: Maybe it's better to make it an error to not specify it (yes, killing "make world" and stuff, that's what UPDATING is for). There's no better time for doing so than prior to 4.0-RELEASE. :-) Does sysinstall set this one? If not, it should. Then we can stop worrying about it. :-) Ciao, Sheldon. 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
make world fail
Hi is any oone else having trouble doing a make world? Completed reomved /usr/obj and usr/src/ cvs'd twice and got the following error: (trimmed) /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/MKnames.awk:96: print "FIX(numcodes)""codeftr" awk: /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/MKnames.awk:96: ^ unexpected newline awk: /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/MKnames.awk:97: print "FIX(strcodes)""codeftr" awk: /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/MKnames.awk:97: ^ unexpected newline awk: /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/MKnames.awk:98: print "#endif /* BROKEN_LINKER */" "codeftr" awk: /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/MKnames.awk:98: ^ unexpected newline *** Error code 1 Stop in /usr/src/lib/libncurses. *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. JRS To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mandating USA_RESIDENT
On 18 Jan 2000 03:03:09 -0800, [EMAIL PROTECTED] (Satoshi - Ports Wraith - Asami) said: Won't people get into legal trouble (technically) if they build the wrong version? Depends on who they work for. Some people may work for organizations which have licensing agreements in place to permit them to use RSA. (This includes about 10,000 people who happen to work for the patent assignee.) -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same [EMAIL PROTECTED] | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RELNOTES.TXT
Hi, I checked the file RELNOTES.TXT for the latest snapshot (4.0-2118-CURRENT). The following network cards from Intel are listed: Intel EtherExpress 16 Intel EtherExpress Pro/10 Intel EtherExpress Pro/100B PCI Fast Ethernet Intel PRO/100+ Management Adapter FreeBSD also supports the "Intel InBusiness 10/100 PCI Network Adaptor", which has a different PCI device ID than the above listed cards. Can someone also add this to RELNOTES.TXT. - Mohit To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Feature test for OpenSSL + RSA
On Tue, 18 Jan 2000, Sheldon Hearn wrote:
On Mon, 17 Jan 2000 21:53:10 PST, Kris Kennaway wrote:
+.if defined(WITH_RSA) ${WITH_RSA} == YES
+ /usr/bin/touch /etc/ssl/openssl_hasrsa
Um, are you sure you want that hard path, /etc/ssl ? Shouldn't there be
a ${DESTDIR} in there? What do you need this for?
Yep, I realised this when I was falling asleep last night. Thanks :)
Kris
"How many roads must a man walk down, before you call him a man?"
"Eight!"
"That was a rhetorical question!"
"Oh..then, seven!" -- Homer Simpson
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Mandating USA_RESIDENT
On 18-Jan-00 Satoshi - Ports Wraith - Asami wrote: Won't people get into legal trouble (technically) if they build the wrong version? As far as I understand things specifying USA_RESIDENT=yes when it is not true is liable (technically) to get some US based ftp server operator in trouble (most likely Walnut Creek) by downloading export controlled material from a US ftp site (this seems insane to me but that is my understanding). It may also get the user into trouble depending on the legal status of crypto in their country. Setting USA_RESIDENT=no when it is not true is liable to get the user into trouble for patent violations. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mandating USA_RESIDENT
On Tue, 18 Jan 2000, Sheldon Hearn wrote: Does sysinstall set this one? If not, it should. Then we can stop worrying about it. :-) Not yet, but it should. If someone can help me out here it would be greatly appreciated. Kris "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Feature test for OpenSSL + RSA
On Tue, 18 Jan 2000, Peter Wemm wrote:
Yes, This should most definately have ${DESTDIR} for this sort of thing, but
even then I'm not sure this is a good change.. We have got to find a better
way than this.
I've said this a couple of times in private, but will repeat it again for
the list: we could do something like `nm /usr/lib/libcrypto.so | grep
RSA_free`, but this seemed ugly and non-obvious to me (e.g. if someone who
is not bsd.port.mk wanted to check whether their openssl port was
RSA-enabled). It also seems to get invoked about 20 times during the
course of making an openssl-using port (at least, that's how many times
my debugging echos get run :)
Kris
"How many roads must a man walk down, before you call him a man?"
"Eight!"
"That was a rhetorical question!"
"Oh..then, seven!" -- Homer Simpson
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Mandating USA_RESIDENT
On Tue, 18 Jan 2000, Patrick Bihan-Faou wrote: If we are changing the meaning of "USA_RESIDENT", could we replace it by We're not. It's just that until now it hasn't really mattered if it wasn't set (the cases where it did matter, like whether or not to fetch a crypto port from a US site, it was required it to be set there). Now it needs to be set to do a buildword. It seems to me that a things progress, the crypto regulation gets more complicated everyday. Why not have a "CRYPTO_COUNTRY" variable that could be set to "USA" "FRANCE" "CANADA" or "other" based where you live and weither special consideration must be taken relative to the crypto code ? I don't know much about the restrictions of other countries. If the current crypto policies were a legal problem for someone else we can surely change them to suit, but I'd rather not complicate things even more than they are already without a reason.. The other thing that could be set based on the CRYPTO_COUNTRY code is where to get the FreeBSD crypto related source from. Well, right now there is only one non-US crypto repository (AFAIK), so "closest" is a degenerate case :-) Kris "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
FIC SD-11 not happy with ata
I swapped out my motherboard and am seeing this now: ad0: UDMA CRC WRITE ERROR blk# 1140495 retrying ad0: UDMA CRC WRITE ERROR blk# 1140495 retrying ad0: UDMA CRC WRITE ERROR blk# 1140495 retrying ad0: UDMA CRC WRITE ERROR blk# 1140495WARNING: WAIT_READY active=ATA_ACTIVE_ATA falling back to PIO mode That doesn't sound good... This drive ran just fine with an ASUS P2B and seems to run fine on the FIC too. This is on a farm fresh -current. I've appended the dmesg. Cheers, Russell 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 #14: Tue Jan 18 10:44:46 MST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/CURRENT Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 499034055 Hz CPU: AMD-K7(tm) Processor (499.03-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x612 Stepping = 2 Features=0x81f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PA T,MMX AMD Features=0xc040AMIE,DSP,3DNow! real memory = 268369920 (262080K bytes) avail memory = 257212416 (251184K bytes) Preloaded elf kernel "kernel" at 0xc02f3000. Pentium Pro MTRR support enabled npx0: math processor on motherboard npx0: INT 16 interface pcib0: AMD-751 host to PCI bridge on motherboard pci0: PCI bus on pcib0 pcib1: AMD-751 PCI-PCI (AGP) bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 vga-pci0: ATI Mach64-GT graphics accelerator port 0xd800-0xd8ff mem 0xeefff000-0xeeff,0xef00-0xefff at device 3.0 on pci0 pci0: unknown card (vendor=0x12eb, dev=0x0001) at 6.0 irq 10 isab0: VIA 82C686 PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 ata-pci0: VIA 82C686 ATA-66 controller port 0xffa0-0xffaf 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 chip1: VIA 82C686 ACPI interface at device 7.4 on pci0 de0: Digital 21143 Fast Ethernet port 0xc800-0xc87f mem 0xeeffef80-0xeeffefff irq 11 at device 9.0 on pci0 de0: 21143 [10-100Mb/s] pass 3.0 de0: address 00:80:c8:63:47:84 fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 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 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: Parallel port at port 0x378-0x37f irq 5 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: IEEE1284 device found /NIBBLE Probing for PnP devices on ppbus0: ppbus0: Digital Equipment Corp LN09 PCL,PostScript lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ad0: IBM-DTTA-371440/T71OA73A ATA-4 disk at ata0 as master ad0: 13783MB (28229040 sectors), 28005 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 32 depth queue, UDMA33 ad1: IBM-DPTA-372050/P76OA30A ATA-4 disk at ata1 as master ad1: 19574MB (40088160 sectors), 39770 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 32 depth queue, UDMA66 Mounting root from ufs:/dev/ad0s1a de0: enabling 100baseTX port ad0: UDMA CRC WRITE ERROR blk# 1140495 retrying ad0: UDMA CRC WRITE ERROR blk# 1140495 retrying ad0: UDMA CRC WRITE ERROR blk# 1140495 retrying ad0: UDMA CRC WRITE ERROR blk# 1140495WARNING: WAIT_READY active=ATA_ACTIVE_ATA falling back to PIO mode To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mandating USA_RESIDENT
In message [EMAIL PROTECTED] Satoshi - Ports Wraith - Asami writes: : Won't people get into legal trouble (technically) if they build the : wrong version? RESIDENT=two-letter-iso-code CITIZEN=two-letter-iso-code Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mandating USA_RESIDENT
In message [EMAIL PROTECTED] Kris Kennaway
writes:
: In message [EMAIL PROTECTED] Satoshi - Ports Wraith -
:Asami writes:
: : Won't people get into legal trouble (technically) if they build the
: : wrong version?
:
: RESIDENT=two-letter-iso-code
: CITIZEN=two-letter-iso-code
:
: What about us dual citizens? :-)
OK, forget CITIZEN then. I forget that gets complicated in a hurry.
I've forgotten than many middle eastern countries offer this (Isreal
and Turkey come to mind) and it isn't as relevant as RESIDENT.
The idea for RESIDENT would be that it must be in
{us,ca}
to build RSA patented stuff via RSAREF.
If other patented or semi-patented stuff came along, then we could
test to see if it was jp, and not build the YoShiHaNya ONeCo data
compression modules for that country, but allow building them
elsewhere.
It would be much more flexible than the rigid and US Centric
USA_RESIDENT.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: buildworld failure in === makeinfo
On Mon, Jan 17, 2000 at 05:25:37PM -0500, Bush Doctor wrote: "make buildworld" fails with sources cvsup'd around 17:00 est ... whereintheworld.pl (thanxs Bill Fenner) shows ... What does this Perl script do? :-) --Will To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FIC SD-11 not happy with ata
It seems Russell L. Carter wrote: I swapped out my motherboard and am seeing this now: ad0: UDMA CRC WRITE ERROR blk# 1140495 retrying ad0: UDMA CRC WRITE ERROR blk# 1140495 retrying ad0: UDMA CRC WRITE ERROR blk# 1140495 retrying ad0: UDMA CRC WRITE ERROR blk# 1140495WARNING: WAIT_READY active=ATA_ACTIVE_ATA falling back to PIO mode This for the most part means cable and/or power problems, does this appear immediately or under moderate/high load ?? Remember the K7 is a power hog, how big is you PSU, especially how much power (amps) can it deliver on the 3.3V 5V and 12V rails ?? -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PNPBIOS + Dell PowerEdge = panic()
In message [EMAIL PROTECTED] Garrett Wollman writes: : On Mon, 17 Jan 2000 17:12:14 -0800, Mike Smith [EMAIL PROTECTED] said: : : This is definitely a bad idea; IMHO we should only do this when the : resource is actually activated (and obviously free it when deactivated). : : Absolutely! As I keep trying to explain to people, that's why there : *is* a separate activate function (or one of the reasons, anyway). Yes. There's lots of cool things that one can do with this. I know that the pccard code, both old and new, deferrs the actual programming of the bridge until a resource is activated (except for IRQ, which it further deferrs until the interrupt handler is setup). Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Problems with PCMCIA Cards
I am running current as of yesterday. I have neglegently not been rebooting after make world and making a new kernel. Yesterday I did reboot and found that something has changed and my D-Link 660 and my Viking Modem PCMCIA cards are no longer working. :Jan 17 23:33:58 local-27 pccardd[46]: driver allocation failed for D-Link(DE-66 0): Inappropriate ioctl for device Jan 17 23:07:31 local-27 pccardd[46]: driver allocation failed for Viking(V.90 K 56flex): Inappropriate ioctl for device My kernel configuration is: device card0 device pcic0 at isa? device pcic1 at isa? deviceed0 My pccard.conf is: card "D-Link" "DE-660" config 0x20 "ed0" 11 0x10 insert /etc/pccard_ether ed0 remove /sbin/ifconfig ed0 delete I could find no changes in LINT or in /etc . I even ran mergemaster, just incase. I am trying to build a new world but have been stopped at crypto -L/usr/local/lib -lrsaref speed.o: In function `speed_main': speed.o(.text+0x60a): undefined reference to `RSA_PKCS1_RSAref' /usr/local/lib/libcrypto.so: undefined reference to `ERR_load_RSAREF_strings' *** Error code 1 Stop in /usr/src/secure/usr.bin/openssl. *** Error code 1 Stop in /usr/src/secure/usr.bin. *** Error code 1 Any help will be appreciated. ed To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ata observation (bug?)
Hi, I don't know if you'd class this as a bug report or more as an observation. I have a machine with the following: ata-pci0: AcerLabs Aladdin ATA-33 controller port 0xf000-0xf00f at device 15.0 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 [.] ad0: FUJITSU M1623TAU/5245 ATA-0 disk at ata0 as master ad0: 1623MB (3324384 sectors), 3298 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, WDMA2 ad1: QUANTUM FIREBALL EL7.6A/A08.1100 ATA-4 disk at ata1 as master ad1: 7339MB (15032115 sectors), 15907 cyls, 15 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 1 depth queue, UDMA33 ad2: FUJITSU MPE3273AT/ED-82-25 ATA-4 disk at ata1 as slave ad2: 26063MB (53377152 sectors), 52953 cyls, 16 heads, 63 S/T, 512 B/S ad2: 16 secs/int, 1 depth queue, UDMA33 Note that ad0 is on a controller of its own, and ad[12] are on the second controller. If I put the second (7Gb) disk on the first controller as slave, I can't get the machine to boot. The wd driver works ok, but ad, although coming up in the ``?'' list in vfs_mountroot_ask(), won't boot... I get error 6 when I try ufs:/dev/rad0s1a at the prompt. This has stopped me going to the ata driver on this machine for a long time :-/ Moving the two UDMA disks to a controller of their own has solved the problem Comments ? -- Brian [EMAIL PROTECTED][EMAIL PROTECTED] http://www.Awfulhak.org [EMAIL PROTECTED] Don't _EVER_ lose your sense of humour ! [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata observation (bug?)
It seems Brian Somers wrote: Hi, I don't know if you'd class this as a bug report or more as an observation. I have a machine with the following: bug :) ata-pci0: AcerLabs Aladdin ATA-33 controller port 0xf000-0xf00f at device 15.0 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 [.] ad0: FUJITSU M1623TAU/5245 ATA-0 disk at ata0 as master ad0: 1623MB (3324384 sectors), 3298 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, WDMA2 ad1: QUANTUM FIREBALL EL7.6A/A08.1100 ATA-4 disk at ata1 as master ad1: 7339MB (15032115 sectors), 15907 cyls, 15 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 1 depth queue, UDMA33 ad2: FUJITSU MPE3273AT/ED-82-25 ATA-4 disk at ata1 as slave ad2: 26063MB (53377152 sectors), 52953 cyls, 16 heads, 63 S/T, 512 B/S ad2: 16 secs/int, 1 depth queue, UDMA33 Note that ad0 is on a controller of its own, and ad[12] are on the second controller. If I put the second (7Gb) disk on the first controller as slave, I can't get the machine to boot. The wd driver works ok, but ad, although coming up in the ``?'' list in vfs_mountroot_ask(), won't boot... I get error 6 when I try ufs:/dev/rad0s1a at the prompt. This has stopped me going to the ata driver on this machine for a long time :-/ Moving the two UDMA disks to a controller of their own has solved the problem Hmm, I'll investigate this, it sure adds more data to the equation.. Thanks for the report! -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mandating USA_RESIDENT
Not yet, but it should. If someone can help me out here it would be greatly appreciated. "Setting it in sysinstall" is easy. Deciding where and how to set it in response to questions at certain stages of the installations(s) is more the sticking point. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why not a default number of pings?
I think the -a parameter to ping would be useful to you. It makes the pc speaker emit a beep for every reply. If you have the speaker working and are not hearing impaired, you will NOT forget! :) On Tue, 18 Jan 2000, Leif Neland wrote: I've been hit by a "forgotten ping" again. I still do not see a reason for not having a default number of pings, instead of infinite. The only reason I've seen is "It's always been so". Even if a default of 4 pings is not acceptable, because windows does it that way, why not a large default then? If somebody _really_ want to ping forever, let them use -t0, and defend the rest of us from our blunders of forgetting a ping, keeping the line open infinitely. How about a MAX_PING=3600 in make.conf or so? I've supplied patches earlier, but they've been rejected. Leif 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: Why not a default number of pings?
If somebody _really_ want to ping forever, let them use -t0, and defend the rest of us from our blunders of forgetting a ping, keeping the line open infinitely. I use ping for precisely this purpose. Yes, I could change my setup, but so could you :-) I used SunOS (and later Solaris) for many years - with ping having a default count of 1. I hated it - I almost always used the -s option to get *my* desired ping behavior (standard BSD). And it wasn't a case of being used to something else - SunOS *was* my first contact with Unix. So please don't change the default behavior of ping. Steinar Haug, Nethelp consulting, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mandating USA_RESIDENT
On Tue, 18 Jan 2000, Warner Losh wrote: In message [EMAIL PROTECTED] Satoshi - Ports Wraith - Asami writes: : Won't people get into legal trouble (technically) if they build the : wrong version? RESIDENT=two-letter-iso-code CITIZEN=two-letter-iso-code What about us dual citizens? :-) Kris "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Make world break on openssl...
Hi, this is probably not news, but here is what I get. I tried with both USA_RESIDENT=YES and no USA_RESIDENT defined... The code has been CVSuped on tuesday Jan 18 2000 around 2am EST. cc -O -pipe -DMONOLITH -DNO_IDEA -I/usr/src-freebsd-4.x/secure/usr.bin/opens sl -DRSAref -I/usr/obj/usr/src-freebsd-4.x/i386/usr/include -o openssl apps.o asn1pars.o ca.o ciphers.o crl.o crl2p7.o dgst.o dh.o dsa.o dsaparam.o enc.o errstr.o gendh.o gendsa.o genrsa.o nseq.o openssl.o pkcs12.o pkcs7.o pkcs8.o req.o rsa.o s_cb.o s_client.o s_server.o s_socket.o s_time.o sess_id.o speed.o verify.o version.o x509.o -lssl -lcrypto -L/usr/local/lib -lrsaref speed.o: In function `speed_main': speed.o(.text+0x60a): undefined reference to `RSA_PKCS1_RSAref' /usr/local/lib/libcrypto.so: undefined reference to `ERR_load_RSAREF_strings' *** Error code 1 Stop in /usr/src-freebsd-4.x/secure/usr.bin/openssl. *** Error code 1 Stop in /usr/src-freebsd-4.x/secure/usr.bin. *** Error code 1 Stop in /usr/src-freebsd-4.x/secure. *** Error code 1 Stop in /usr/src-freebsd-4.x. *** Error code 1 Stop in /usr/src-freebsd-4.x. *** Error code 1 Stop in /usr/src-freebsd-4.x. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mandating USA_RESIDENT
At 9:58 AM -0800 2000/1/18, Kris Kennaway wrote: I don't know much about the restrictions of other countries. If the current crypto policies were a legal problem for someone else we can surely change them to suit, but I'd rather not complicate things even more than they are already without a reason.. Russia and France both are highly crypto-unfriendly, in that you are not allowed to use any crypto whatsoever unless it has been explicitly approved by the government. Since their lists of what's been "approved" (read: cracked) by the government may differ, we're starting to get into some issues here where I think a "CRYPTO_COUNTRY" variable would make a lot of sense, and then we could derive appropriate "RSA" and "USA_RESIDENT" variables from them. -- These are my opinions -- not to be taken as official Skynet policy |o| Brad Knowles, [EMAIL PROTECTED]Belgacom Skynet NV/SA |o| |o| Systems Architect, News FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with PCMCIA Cards
On Tue, Jan 18, 2000 at 11:31:17AM -0800, Edwin Culp wrote: I am running current as of yesterday. I have neglegently not been rebooting after make world and making a new kernel. Yesterday I did reboot and found that something has changed and my D-Link 660 and my Viking Modem PCMCIA cards are no longer working. :Jan 17 23:33:58 local-27 pccardd[46]: driver allocation failed for D-Link(DE-66 0): Inappropriate ioctl for device Jan 17 23:07:31 local-27 pccardd[46]: driver allocation failed for Viking(V.90 K 56flex): Inappropriate ioctl for device My kernel configuration is: device card0 device pcic0 at isa? device pcic1 at isa? deviceed0 My pccard.conf is: card "D-Link" "DE-660" config 0x20 "ed0" 11 0x10 insert /etc/pccard_ether ed0 remove /sbin/ifconfig ed0 delete I could find no changes in LINT or in /etc . I even ran mergemaster, just incase. I am trying to build a new world but have been stopped at crypto -L/usr/local/lib -lrsaref speed.o: In function `speed_main': speed.o(.text+0x60a): undefined reference to `RSA_PKCS1_RSAref' /usr/local/lib/libcrypto.so: undefined reference to `ERR_load_RSAREF_strings' *** Error code 1 Stop in /usr/src/secure/usr.bin/openssl. *** Error code 1 Stop in /usr/src/secure/usr.bin. *** Error code 1 I was having exactly the same problem with a current cvsuped today. I could fix it by changing the line device pcic0 at isa? irq 10 port 0x3e0 iomem 0xd to device pcic0 at isa? in the kernel config file... regards, -oscar -- pgp public key: finger [EMAIL PROTECTED] pgp fingerprint: 50 D4 B6 9B DB 7D D8 47 DF 3C ED 39 18 78 DA 8C To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
breakage
Sure would be nice if some folks would start testing before committing. I'm starting to wonder how long it'll be before it builds again. I understand screwups (god know I better!) but if you don't test before commit, that's taking things a step too far. Chuck Robey| Interests include C Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the| jaunt.mat.net : FreeBSD-current(Alpha)| dictionary.| To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mandating USA_RESIDENT
On Tue, 18 Jan 2000, Jordan K. Hubbard wrote: Not yet, but it should. If someone can help me out here it would be greatly appreciated. "Setting it in sysinstall" is easy. Deciding where and how to set it in response to questions at certain stages of the installations(s) is more the sticking point. Maybe we should extend meaning of USA_RESIDENT or introduce new variable indicating contry. After doing netfork install, subsecuent fetces for ports/packages/distfiles from nearest ftp.xx.freebsd.org/cvsup.xx.freebsd.org is really handy. Specially for newcomers, who do not yet have idea of editing /etc/make.conf 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: breakage
Sure would be nice if some folks would start testing before committing. I'm starting to wonder how long it'll be before it builds again. I had two problems building a kernel from 1/16/2000: I had to create the directories: /usr/share/examples/ses /usr/share/doc/bind before the "make installworld" would work. The "make buildworld" worked fine. The was on top of code downloaded and build 1/1/2000. So, if it is breakage, it happened in the last two days. Bruce -- --- Bruce Burden[EMAIL PROTECTED] Tandem Computers Inc. 512-432-8944Network Verification 14231 Tandem Blvd. Auto answer(4 rings) Austin, TX 78726 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Integrated Vibra16 in -current
-On [2118 04:02], Andy Sparrow ([EMAIL PROTECTED]) wrote: Given the Plug'n'Pray changes in -current, I pretty much expected to lose AWE32 support (as I can no longer use the 'pnp' commands in 'userconfig' to probe the "magic" ports for the AWE32). AWE32 here, PnPBIOS to off, and added device pcm0 and device sbc0 to my kernel config file. Works perfectly for me. Thanks Cameron! -- Jeroen Ruigrok vd W/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/B-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai I was searching through the Heavens and somehow I slipped... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: breakage
as of a cvsup from today, i just finished a buildworls and an installworld, so it seems the errors on my system have gone away Chuck Robey wrote: Sure would be nice if some folks would start testing before committing. I'm starting to wonder how long it'll be before it builds again. I understand screwups (god know I better!) but if you don't test before commit, that's taking things a step too far. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: apm suspend ??
On Mon, Jan 17, 2000 at 11:46:23PM +0100, Jesper Skriver wrote: On Mon, Jan 17, 2000 at 05:00:14PM -0500, Christopher Masto wrote: On Mon, Jan 17, 2000 at 09:20:38PM +0100, Jesper Skriver wrote: On Mon, Jan 17, 2000 at 11:18:02AM -0700, Warner Losh wrote: In message [EMAIL PROTECTED] Jesper Skriver writes: : Just upgraded my laptop from a Jan 5th -CURRENT to todays, and now : suspend doesn't work as expected. : : When I run 'apm -z' the laptop suspends as normal, but right after this : the harddisk led turns on, and it powers up again. That's very odd. apm hasn't changed since Dec 2 and even that was just deleting code that had been obsolete for a while now. I don't get it either - will try to revert to -CURRENT as of jan 5th, and see if it works again ... Sometimes the "enter" at the end of the command is sufficient to wake the machine back up. Have you tried "sleep 2; apm -z"? Yep, that's not it. I've just verified, by reverting to -CURRENT as of *default date=2000.01.05.12.00.00 Suspend works as expected, tomorrow I'll try at 2 days intervals, to try to narrow down the commit making the difference ... And it also works as of *default date=2000.01.13.23.00.00 But didn't on the cvsup on the 16th ... will try to narrow it down even further ... /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE# 5456 Work:Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek@ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: boot messages for pci devices...
On Wed, 19 Jan 2000, Poul-Henning Kamp wrote: fxp0: Intel EtherExpress Pro 10/100B Ethernet port 0xc400-0xc43f mem 0xefe0-0xefef,0xe000-0xefff irq 9 at device 14.0 on pci0 Is this level of verbosity really helping anybody ? Its consistant, but I need to unify all the resource printing stuff since theres about 5 different ways that are being used to print the stuff right now. I'll do this after 4.0R. I thought we printed out the port/mem stuff for ISA because it is usually jumpered by the admin, but for dynamic allocation busses/devices I think this should be "bootverbose" material. Humm... Thats possible. There was talk a while ago about making multiple levels of verbosity in the bootup messages. I'll explore this when I fix the line wrapping issues. It would really be nice if we could have busfs; this would make it much easier to allow access to this sort of information. -- | 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: boot messages for pci devices...
On Wed, Jan 19, 2000 at 12:28:09AM +0100, Poul-Henning Kamp wrote: fxp0: Intel EtherExpress Pro 10/100B Ethernet port 0xc400-0xc43f mem 0xefe0-0xefef,0xe000-0xefff irq 9 at device 14.0 on pci0 Is this level of verbosity really helping anybody ? I *thought* I noticed it was different. I actually find this pretty annoying because it wraps almost all of the lines and makes it difficult to read dmesg. -Chris -- [EMAIL PROTECTED] [EMAIL PROTECTED] Abbotsford, BC, Canada To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: boot messages for pci devices...
fxp0: Intel EtherExpress Pro 10/100B Ethernet port 0xc400-0xc43f mem 0xefe0-0xefef,0xe000-0xefff irq 9 at device 14.0 on pci0 Is this level of verbosity really helping anybody ? I thought we printed out the port/mem stuff for ISA because it is usually jumpered by the admin, but for dynamic allocation busses/devices I think this should be "bootverbose" material. Or maybe we should always make the resource allocations bootverbose stuff now ? I think that the pci info should be displayed onlly in verbose mode . Some of the pci devices specially the newer graphic cards have tons of memory map registers and it is of virtually no use to users. -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mandating USA_RESIDENT
On Tue, 18 Jan 2000, Taavi Talvik wrote: Maybe we should extend meaning of USA_RESIDENT or introduce new variable indicating contry. After doing netfork install, subsecuent fetces for ports/packages/distfiles from nearest ftp.xx.freebsd.org/cvsup.xx.freebsd.org is really handy. Specially for newcomers, who do not yet have idea of editing /etc/make.conf There seems to be broad support for this idea, but I'd prefer to leave it as is for now and get it working properly, then we can revisit it after 4.0-REL. Fetching packages due to network topology is another idea I've wanted to implement for a while, although I was thinking of doing it dynamically by testing the available bandwidth to each of the hosts (and storing it in a database) and using them in order of increasing bandwidth. Kris "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ppp, incoming mail keeping the line up.
From: "Jonathan M. Bresler" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Tuesday, January 18, 2000 3:07 AM Subject: Re: ppp, incoming mail keeping the line up. I run user-ppp, and I have a mx-record for my system, so incoming mail = goes directly to my system. this is asking for trouble. you should get yourself an MX that is online all the time and will store your mail for you. you can then pick it up whenever you want using APOP or POP thru SSHi peronsally use APOP thru SSH via fetchmail ;) I have a higher numbered MX online all the time, and used to pick up by ETRN. Now I pick up by uucp (just for the heck of it), but still have myself as lowest MX, to get mail fast while online. I don't like fetchmail to handle all my adresses and aliases. Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: shell problem
I like to use BASH shell in my user account. how can i do this ? please inform. Install bash (either from ports or a package). Use chsh to change the entry for Shell to /usr/local/bin/bash. and before you ask why you cannot ftp to your machine, do not forget to add the path above to /etc/shells. PS: This sort of question is better on -questions than -current. and one should take a look at the mailing list manifest! regards, mouss To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mandating USA_RESIDENT
On Tue, 18 Jan 2000, Kris Kennaway wrote: Fetching packages due to network topology is another idea I've wanted to implement for a while, although I was thinking of doing it dynamically by testing the available bandwidth to each of the hosts (and storing it in a database) and using them in order of increasing bandwidth. You also need to cater for those of us behind restrictive firewalls that keep our own copies of the packages distribution. Carl. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Make world break on openssl...
On Tue, 18 Jan 2000, Patrick Bihan-Faou wrote:
cc -O -pipe -DMONOLITH -DNO_IDEA -I/usr/src-freebsd-4.x/secure/usr.bin/opens
sl -DRSAref -I/usr/obj/usr/src-freebsd-4.x/i386/usr/include -o openssl
apps.o asn1pars.o ca.o ciphers.o crl.o crl2p7.o dgst.o dh.o dsa.o dsaparam.o
enc.o errstr.o gendh.o gendsa.o genrsa.o nseq.o openssl.o pkcs12.o pkcs7.o
pkcs8.o req.o rsa.o s_cb.o s_client.o s_server.o s_socket.o s_time.o
sess_id.o speed.o verify.o version.o
x509.o -lssl -lcrypto -L/usr/local/lib -lrsaref
speed.o: In function `speed_main':
speed.o(.text+0x60a): undefined reference to `RSA_PKCS1_RSAref'
/usr/local/lib/libcrypto.so: undefined reference to
`ERR_load_RSAREF_strings'
it's a known problem which I hope to fix tonight - pkg_delete or move
aside your openssl installation (e.g. /usr/local/lib/lib{crypto,ssl}.*).
Kris
"How many roads must a man walk down, before you call him a man?"
"Eight!"
"That was a rhetorical question!"
"Oh..then, seven!" -- Homer Simpson
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Security hole with new setresuid call
On Tue, Jan 18, 2000 at 02:12:02PM +0800, Peter Wemm wrote: .. and why is this a security hole? setresuid(geteuid(), geteuid(), geteuid()) is equivalent to setuid(geteuid()).. Umm, maybe not the hole exactly, but difference between same area syscalls implementation. We define POSIX_APPENDIX_B_4_2_2 by default for setuid(geteuid()), but I mean case when it is _not_ defined (BTW, why to have define which is always on?) And in case POSIX_APPENDIX_B_4_2_2 is not defined, ruid = euid; assignment was not allowed before you add new syscall. -- Andrey A. Chernov http://nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC+ D A a++ C G+ QH+(++) 666+++ Y To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Integrated Vibra16 in -current
On 18/01 23:09, Jeroen Ruigrok/Asmodai wrote: Given the Plug'n'Pray changes in -current, I pretty much expected to lose AWE32 support (as I can no longer use the 'pnp' commands in 'userconfig' to probe the "magic" ports for the AWE32). AWE32 here, PnPBIOS to off, and added device pcm0 and device sbc0 to my kernel config file. Works perfectly for me. Yeap, I've got a Creative AWE64 Gold ISA card working perfectly using the exact same settings. $ cat /dev/sndstat FreeBSD Audio Driver (newpcm) Jan 18 2000 20:59:19 Installed devices: pcm0: SB DSP 4.16 at io 0x220 irq 5 drq 1:5 (1p/1r channels duplex) Thanks Cameron! Yes absolutely. Well done, Sir! To think I was on the point of selling my AWE64 about 5 months ago because it didn't work under FreeBSD! gjvc -- "Readers who only want to see algorithms that are already packaged in a plug-in way, using a trendy language, should buy other people's books." -- D. E. Knuth To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mandating USA_RESIDENT
On 18/01 20:03, Brad Knowles wrote: Russia and France both are highly crypto-unfriendly, in that you are not allowed to use any crypto whatsoever unless it has been explicitly approved by the government. France changed their policy from zero-crypto to allowing 128-bits almost exactly a year ago today. http://slashdot.org/articles/99/01/19/1255234.shtml -- "Readers who only want to see algorithms that are already packaged in a plug-in way, using a trendy language, should buy other people's books." -- D. E. Knuth To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: boot messages for pci devices...
On Wed, Jan 19, 2000 at 12:28:09AM +0100, Poul-Henning Kamp wrote: fxp0: Intel EtherExpress Pro 10/100B Ethernet port 0xc400-0xc43f mem 0xefe0-0xefef,0xe000-0xefff irq 9 at device 14.0 on pci0 Agreed. For a PCI card all I want to know is what it is, and what IRQ it was assigned. A single line should be suffient. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PnP probing in -current
In message [EMAIL PROTECTED] Brian Somers writes: : Where UP == OFF, from 1-8 I've got : : UP, UP, UP, UP, DOWN, UP, DOWN, DOWN OK. I've found out what the problem is, at least with the bog standard GENERIC. I'll see about finding some time to fix aha. Short answer is that aha is caching softc pointers, which it shouldn't really be doing in the new world order. Thanks for spending the time - I'll look out for the fix and un-hak pnp.c :*O Warner -- Brian [EMAIL PROTECTED][EMAIL PROTECTED] http://www.Awfulhak.org [EMAIL PROTECTED] Don't _EVER_ lose your sense of humour ! [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mandating USA_RESIDENT
On Tue, Jan 18, 2000 at 10:26:12AM -0500, Patrick Bihan-Faou wrote: Then as part of the build process, automatically create specific variables for RSA or other stuff as they show up: CRYPTO_RSA="RSAref" or CRYPTO_RSA="rsa" or CRYPTO_RSA="none". This can be done by a little bit of shell script easily. I think this is the only way to properly handle it. As Garrett pointed out, some people in the USA actually do have a licence to use the "good" version of RSA. We could default if we wanted to: USA_RESIDENT=YES== CRYPTO_RSA=RSAref USA_RESIDENT=NO == CRYPTO_RSA=RSAintl if CRYPTO_RSA was unset. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: boot messages for pci devices...
On Wed, Jan 19, 2000 at 12:28:09AM +0100, Poul-Henning Kamp wrote: fxp0: Intel EtherExpress Pro 10/100B Ethernet port 0xc400-0xc43f mem 0xefe0-0xefef,0xe000-0xefff irq 9 at device 14.0 on pci0 Agreed. For a PCI card all I want to know is what it is, and what IRQ it was assigned. A single line should be suffient. Do you even need to know what IRQ it was assigned? It seems to me that IRQ, like IO-PORT, is only needed if you're either interested in such stuff or to catch conflicts (both are under bootverbose) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mandating USA_RESIDENT
On Tue, 18 Jan 2000, David O'Brien wrote: I think this is the only way to properly handle it. As Garrett pointed out, some people in the USA actually do have a licence to use the "good" version of RSA. Is this the same Garrett who persuaded me not to include the RSA code at all in the freefall repository so that people wouldn't get in trouble for simply posessing it? :) We could default if we wanted to: USA_RESIDENT=YES== CRYPTO_RSA=RSAref USA_RESIDENT=NO == CRYPTO_RSA=RSAintl if CRYPTO_RSA was unset. I have no problem with this, but it means either we have to have people who have an RSA license get their crypto from internat, or freefall has to have the RSA code (possbibly in another cvsup collection). Kris "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ata-all.c : undefined atapi_attach() in ata_attach()
It seems that we need #if...#endif here, maybe
something like that:
...
#if NATAPICD 0 || NATAPIFD 0 || NATAPIST 0
/* then the atapi devices */
for (ctlr=0; ctlrMAXATA; ctlr++) {
if (!atadevices[ctlr]) continue;
if (atadevices[ctlr]-devices
ATA_ATAPI_MASTER)
atapi_attach(atadevices[ctlr],
ATA_MASTER);
if (atadevices[ctlr]-devices
ATA_ATAPI_SLAVE)
atapi_attach(atadevices[ctlr], ATA_SLAVE);
}
#endif
...
Val
__
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: boot messages for pci devices...
On 19-Jan-00 Matthew Jacob wrote: Do you even need to know what IRQ it was assigned? It seems to me that IRQ, like IO-PORT, is only needed if you're either interested in such stuff or to catch conflicts (both are under bootverbose) What would be nice would be to have the normal version displayed and the verbose stuff go to a seperate buffer and logged seperatly.. ie so you don't clutter your boot screen with junk, but if you have a problem you can get at the verbose info :) .. and no I don't have any patches :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with PCMCIA Cards
Oscar, Thanks a lot, but my kernel.conf has device pcic0 isa? Already. Thanks, ed Oscar Bonilla wrote: On Tue, Jan 18, 2000 at 11:31:17AM -0800, Edwin Culp wrote: I am running current as of yesterday. I have neglegently not been rebooting after make world and making a new kernel. Yesterday I did reboot and found that something has changed and my D-Link 660 and my Viking Modem PCMCIA cards are no longer working. :Jan 17 23:33:58 local-27 pccardd[46]: driver allocation failed for D-Link(DE-66 0): Inappropriate ioctl for device Jan 17 23:07:31 local-27 pccardd[46]: driver allocation failed for Viking(V.90 K 56flex): Inappropriate ioctl for device My kernel configuration is: device card0 device pcic0 at isa? device pcic1 at isa? deviceed0 My pccard.conf is: card "D-Link" "DE-660" config 0x20 "ed0" 11 0x10 insert /etc/pccard_ether ed0 remove /sbin/ifconfig ed0 delete I could find no changes in LINT or in /etc . I even ran mergemaster, just incase. I am trying to build a new world but have been stopped at crypto -L/usr/local/lib -lrsaref speed.o: In function `speed_main': speed.o(.text+0x60a): undefined reference to `RSA_PKCS1_RSAref' /usr/local/lib/libcrypto.so: undefined reference to `ERR_load_RSAREF_strings' *** Error code 1 Stop in /usr/src/secure/usr.bin/openssl. *** Error code 1 Stop in /usr/src/secure/usr.bin. *** Error code 1 I was having exactly the same problem with a current cvsuped today. I could fix it by changing the line device pcic0 at isa? irq 10 port 0x3e0 iomem 0xd to device pcic0 at isa? in the kernel config file... regards, -oscar -- pgp public key: finger [EMAIL PROTECTED] pgp fingerprint: 50 D4 B6 9B DB 7D D8 47 DF 3C ED 39 18 78 DA 8C To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mandating USA_RESIDENT
On Tue, 18 Jan 2000 18:15:35 -0800 (PST), Kris Kennaway [EMAIL PROTECTED] said: Is this the same Garrett who persuaded me not to include the RSA code at all in the freefall repository so that people wouldn't get in trouble for simply posessing it? :) No, this is the same Garrett who persuaded you not to include the RSA code at all in the freefall repository so that I could continue to maintain a mirror without getting into trouble with the Technology Licensing Office. I can (at work) *use* RSA all I want, but can't distribute it without approval from TLO, who must be persuaded that the Institute would benefit. I think it took them something like six months to come to agreement (with the then RSADSI) over the distribution of free PGP. This gets even more complicated when I start to involve my own private activities -- such as participating in the FreeBSD Project as a developer -- which is (part of) why I don't use software containing RSA in the course of personal-time activities. (And hence why I can't log in to freefall, at least until markm and I get Kerberos inter-realm set up.) -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same [EMAIL PROTECTED] | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: boot messages for pci devices...
On Tue, Jan 18, 2000 at 06:10:00PM -0800, Matthew Jacob wrote: Agreed. For a PCI card all I want to know is what it is, and what IRQ it was assigned. A single line should be suffient. Do you even need to know what IRQ it was assigned? It seems to me that IRQ, With wacky PC hardware being what it is, I would say yes. Especially on laptops. Having to tell everyone to boot verbose besides posting /var/run/dmesg.boot would be yet one more thing to get over when pulling teeth [read details] from people. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: boot messages for pci devices...
What would be nice would be to have the normal version displayed and the verbose stuff go to a seperate buffer and logged seperatly.. ie so you don't clutter your boot screen with junk, but if you have a problem you can get at the verbose info :) .. and no I don't have any patches :) From tne cmn_err(9f) man page for solaris: The first character in format affects where the message will be written: !the message goes only to the system buffer. ^the message goes only to the console. ?If level is also CE_CONT, the message is always sent to the system buffer, but is only written to the console when the system has been booted in verbose mode. See kernel(1M). If neither condition is met, the '?' character has no effect and is simply ignored. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: boot messages for pci devices...
On Tue, 18 Jan 2000, David O'Brien wrote: On Tue, Jan 18, 2000 at 06:10:00PM -0800, Matthew Jacob wrote: Agreed. For a PCI card all I want to know is what it is, and what IRQ it was assigned. A single line should be suffient. Do you even need to know what IRQ it was assigned? It seems to me that IRQ, With wacky PC hardware being what it is, I would say yes. Especially on laptops. Having to tell everyone to boot verbose besides posting /var/run/dmesg.boot would be yet one more thing to get over when pulling teeth [read details] from people. Hmm? Haven't we argued over this before [ default grep output ]]? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mandating USA_RESIDENT
On Tue, 18 Jan 2000, Garrett Wollman wrote: No, this is the same Garrett who persuaded you not to include the RSA code at all in the freefall repository so that I could continue to maintain a mirror without getting into trouble with the Technology The upshot of all of which is that people who want RSA and have a license would have to get their crypto from internat, or from freefall with a special cvsup collection :-) Kris "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with PCMCIA Cards
From: Edwin Culp [EMAIL PROTECTED] Subject: Re: Problems with PCMCIA Cards Date: Tue, 18 Jan 2000 16:45:25 -0800 Message-ID: [EMAIL PROTECTED] eculp On Tue, Jan 18, 2000 at 11:31:17AM -0800, Edwin Culp wrote: eculp I am running current as of yesterday. I have neglegently not been eculp rebooting after make world and making a new kernel. Yesterday I did eculp reboot and found that something has changed and my D-Link 660 and my eculp Viking Modem PCMCIA cards are no longer working. eculp :Jan 17 23:33:58 local-27 pccardd[46]: driver allocation failed for eculp D-Link(DE-66 eculp 0): Inappropriate ioctl for device eculp Jan 17 23:07:31 local-27 pccardd[46]: driver allocation failed for eculp Viking(V.90 K eculp 56flex): Inappropriate ioctl for device I got this case, and fix it. :-) Probably, your kernel and pccardd is mismatch. To fix, cooy src/sys/pccard/cardinfo.h to /usr/incude/pccard/cardinfo.h, and make install pccard[cd] in src/usr.sbin/pccard. -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with PCMCIA Cards
[EMAIL PROTECTED] wrote: I am running current as of yesterday. I have neglegently not been rebooting after make world and making a new kernel. Yesterday I did reboot and found that something has changed and my D-Link 660 and my Viking Modem PCMCIA cards are no longer working. :Jan 17 23:33:58 local-27 pccardd[46]: driver allocation failed for D-Link(DE-660): Inappropriate ioctl for device ~ I also had same problem. I think you need to update /usr/sbin/pccardd. This problem is related to below commit. Date: Sat, 15 Jan 2000 22:44:48 -0800 (PST) To: [EMAIL PROTECTED], [EMAIL PROTECTED] hosokawa2000/01/15 22:44:48 PST Modified files: sys/pccard cardinfo.h pccard.c usr.sbin/pccard/pccardd cardd.c Log: This fixes a bug that /etc/pccard_ether did not work without DHCP. For example, when /etc/pccard.conf had ed0 in config line, but kernel refused this name and said - related file: /usr/sbin/pccardd /usr/include/pccard/cardinfo.h your kernel # Do we have to add this changes to UPDATING file? MIHIRA Yoshiro Yokohama, Japan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: no more parallel port zip drive
On Sun, Jan 16, 2000 at 03:21:16PM +0100, F. Heinrichmeyer wrote: My parallel port zip-drive stopped working this weekend with the new ppc code. There is no printer attached: Hmm, any chance to change parallel port bios setting on your MB? -- Fritz Heinrichmeyer mailto:[EMAIL PROTECTED] FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://www-es.fernuni-hagen.de/~jfh To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- [EMAIL PROTECTED] / [EMAIL PROTECTED] FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: grep 2.4a is now in the tree
hi, there! On Tue, 18 Jan 2000, Ruslan Ermilov wrote: The equivalent to the old -a option is --binary-files=without-match. If you want this by default, you can hardcode it in GREP_OPTIONS environment variable. I think there should be one-letter shorthand for this. /fjoe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with PCMCIA Cards
I copied the src/sys/pccard/cardinfo.h which was different from the one in include. I remade pccardc and pccardd. I haven't tested it yet because I am waiting for my "desperation" make world to finish in about 15 minutes, but I'm confident that is the problem. Thanks, I would not have found it for a while. I checked UPDATING and saw nothing, although my problem may have been because I haven't been able to finish a world since the commit. ed Masahide -mac- NODA wrote: From: Edwin Culp [EMAIL PROTECTED] Subject: Re: Problems with PCMCIA Cards Date: Tue, 18 Jan 2000 16:45:25 -0800 Message-ID: [EMAIL PROTECTED] eculp On Tue, Jan 18, 2000 at 11:31:17AM -0800, Edwin Culp wrote: eculp I am running current as of yesterday. I have neglegently not been eculp rebooting after make world and making a new kernel. Yesterday I did eculp reboot and found that something has changed and my D-Link 660 and my eculp Viking Modem PCMCIA cards are no longer working. eculp :Jan 17 23:33:58 local-27 pccardd[46]: driver allocation failed for eculp D-Link(DE-66 eculp 0): Inappropriate ioctl for device eculp Jan 17 23:07:31 local-27 pccardd[46]: driver allocation failed for eculp Viking(V.90 K eculp 56flex): Inappropriate ioctl for device I got this case, and fix it. :-) Probably, your kernel and pccardd is mismatch. To fix, cooy src/sys/pccard/cardinfo.h to /usr/incude/pccard/cardinfo.h, and make install pccard[cd] in src/usr.sbin/pccard. -- [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: Problems with PCMCIA Cards
Thank you very much. The include file was different and I copied it and rebuilt pccardc and pccardd and think that will solve the problem. Thanks, ed MIHIRA Yoshiro wrote: [EMAIL PROTECTED] wrote: I am running current as of yesterday. I have neglegently not been rebooting after make world and making a new kernel. Yesterday I did reboot and found that something has changed and my D-Link 660 and my Viking Modem PCMCIA cards are no longer working. :Jan 17 23:33:58 local-27 pccardd[46]: driver allocation failed for D-Link(DE-660): Inappropriate ioctl for device ~ I also had same problem. I think you need to update /usr/sbin/pccardd. This problem is related to below commit. Date: Sat, 15 Jan 2000 22:44:48 -0800 (PST) To: [EMAIL PROTECTED], [EMAIL PROTECTED] hosokawa2000/01/15 22:44:48 PST Modified files: sys/pccard cardinfo.h pccard.c usr.sbin/pccard/pccardd cardd.c Log: This fixes a bug that /etc/pccard_ether did not work without DHCP. For example, when /etc/pccard.conf had ed0 in config line, but kernel refused this name and said - related file: /usr/sbin/pccardd /usr/include/pccard/cardinfo.h your kernel # Do we have to add this changes to UPDATING file? MIHIRA Yoshiro Yokohama, Japan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FIC SD-11 not happy with ata
%It seems Russell L. Carter wrote: % %It seems Russell L. Carter wrote: % % % % I swapped out my motherboard and am seeing this now: % % % % ad0: UDMA CRC WRITE ERROR blk# 1140495 retrying % % ad0: UDMA CRC WRITE ERROR blk# 1140495 retrying % % ad0: UDMA CRC WRITE ERROR blk# 1140495 retrying % % ad0: UDMA CRC WRITE ERROR blk# 1140495WARNING: WAIT_READY active=ATA_ACTIVE_ATA % % falling back to PIO mode % % % %This for the most part means cable and/or power problems, does this % %appear immediately or under moderate/high load ?? % %Remember the K7 is a power hog, how big is you PSU, especially how % %much power (amps) can it deliver on the 3.3V 5V and 12V rails ?? % % All good points. Swapping the cable for an 80 pin ATA/66 % cable had no effect. The PSU claims it can deliver % 14A @ 3.3V, 25A @ 5V, and 10A @ 12V for this 250W unit. % %That should be enough... Hi Soren, I am beginning to believe that the FIC mb is the problem. My IBM-DPTA-372050 is only half as fast (500MB bonnie) as on the P2B (~10MB/s vs. ~19MB/s). A Jan 11 kernel doesn't downgrade to PIO on the IBM-DTTA-371440 as fast as this evenings -current with your latest bits does, but eventually it gets there. )(*$#%$# stupid magazine benchmarkers never actually test things like IO... gr Regards, Russell To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
YAWF: World failure- undefined reference to `RSA_PKCS1_RSAref'
cc -O -pipe -DMONOLITH -DNO_IDEA -I/usr/src/secure/usr.bin/openssl -DRSAref -I/usr/obj/usr/src/i386/usr/include -o openssl apps.o asn1pars.o ca.o ciphers.o crl.o crl2p7.o dgst.o dh.o dsa.o dsaparam.o enc.o errstr.o gendh.o gendsa.o genrsa.o nseq.o openssl.o pkcs12.o pkcs7.o pkcs8.o req.o rsa.o s_cb.o s_client.o s_server.o s_socket.o s_time.o sess_id.o speed.o verify.o version.o x509.o -lssl -lcrypto -L/usr/local/lib -lrsaref speed.o: In function `speed_main': speed.o(.text+0x60a): undefined reference to `RSA_PKCS1_RSAref' /usr/local/lib/libcrypto.so: undefined reference to `ERR_load_RSAREF_strings' *** Error code 1 Stop in /usr/src/secure/usr.bin/openssl. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with PCMCIA Cards
In message [EMAIL PROTECTED] Edwin Culp writes: : :Jan 17 23:33:58 local-27 pccardd[46]: driver allocation failed for : D-Link(DE-66 : 0): Inappropriate ioctl for device Make sure that your kernel and pccardd match. The binary api changes from time to time in -curent. This is a sure symptom. Also, you will likely need to add an IRQ to the pcic line in your kernel config. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: boot messages for pci devices...
In message [EMAIL PROTECTED] Chris Piazza writes: : I *thought* I noticed it was different. I actually find this pretty : annoying because it wraps almost all of the lines and makes it difficult : to read dmesg. I don't mind them, but wouldn't object to a generic wrapping mechanism. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: breakage
In message [EMAIL PROTECTED] Chuck Robey writes: : Sure would be nice if some folks would start testing before : committing. I'm starting to wonder how long it'll be before it builds : again. I understand screwups (god know I better!) but if you don't test : before commit, that's taking things a step too far. I did a make world Sunday and it worked. I did a makeworld today and it was busted. Turned out to be a cvsup problem that I owe jdp a message about. It was at least into what looked like the usr.sbin's when I left it to come home. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FIC SD-11 not happy with ata
%It seems Russell L. Carter wrote: % %It seems Russell L. Carter wrote: % % % % I swapped out my motherboard and am seeing this now: ... )(*$#%$# stupid magazine benchmarkers never actually test things like IO... gr We in the computer hardware business have a better name for ``FIC'', Fix It Continuously. They are not known for their quality, or should I say they are known for their lack of quality :-). -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: breakage
In article [EMAIL PROTECTED], Warner Losh [EMAIL PROTECTED] wrote: I did a make world Sunday and it worked. I did a makeworld today and it was busted. Turned out to be a cvsup problem that I owe jdp a message about. Details, please. If I had a nickel for every "CVSup problem" that turned out to be something else, I'd be a rich man today. John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: breakage
In message [EMAIL PROTECTED] John Polstra writes: : Details, please. If I had a nickel for every "CVSup problem" that : turned out to be something else, I'd be a rich man today. I was working on that It was either one of two things. My cvsup file at work didn't have a delete line like I had at home: *default delete I also had the following line in my file at work: *default umask 2 (notice missing = sign). What happened was that no revisions of the gcc (and others) tree were deleted with the latest checkins there. Also the default branch was still 1 rather than 1.1.1.x, it didn't switch. Once I added the delete line and umask=2 (added the =), everything updated. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
