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= CITIZEN= 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= : > CITIZEN= : : What about us dual citizens? :-) OK

Re: PnP probing in -current

In message <[EMAIL PROTECTED]> Brian Somers writes: : 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 :-/ OK. I'll take a look at it and see what's up. I even found my 1542CP in the large mass of

Re: PNPBIOS + Dell PowerEdge = panic()

In message <[EMAIL PROTECTED]> Garrett Wollman writes: : < 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*

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 so

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.

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

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

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

Re: Problems with PCMCIA Cards

In message <[EMAIL PROTECTED]> "Matthew N. Dodd" writes: : The pcic driver should be smart enough to find a free IRQ; in addition : pccardd shouldn't have to specify a list of IRQs to use; thats info the : kernel knows about. Should be smart enough? How? There are a limited number of IRQs avai

Re: Problems with PCMCIA Cards

In message <[EMAIL PROTECTED]> "Matthew N. Dodd" writes: : pccardd shouldn't have to specify a list of IRQs to use; thats info the : kernel knows about. Oops. Missed this part. The problem again is that the kernel doesn't know about this. At least it knows it only to a point. It knows which

Re: Problems with PCMCIA Cards

In message <[EMAIL PROTECTED]> "Matthew N. Dodd" writes: : Otherwise your timeout solution seems good. Are the valid IRQs dependent : on the board integrator or on the chip used? Since we can identify the : chips (well, it looks like we can) couldn't we maintain a 'quirk' table? That I'm not s

Re: Problems with PCMCIA Cards

In message <[EMAIL PROTECTED]> "Matthew N. Dodd" writes: : Well, I wasn't really trying to flame you, or anyone. It is frusterating : to see how much time gets tied up in tracking down dodgy PCIC configs : though. Solving that would probably free you up of several emails a : week. If I start m

Re: Problems with PCMCIA Cards

In message <[EMAIL PROTECTED]> "Matthew N. Dodd" writes: : Ok, I'm obviously missing something here... You mean the IRQs specified : in /etc/pccard.conf are a complete crapshoot? Well, yes. The IRQs are supposed to be free AND ROUTABLE TO THE PCIC part. If they are, then it works great. If

Re: Problems with PCMCIA Cards

In message <[EMAIL PROTECTED]> Wes Peters writes: : Do you really want to cram a list of all known PCcard and USB devices : into your kernel? Ugh. Do you really want to cram a list of all known pci cards into the kernel? Same thing really. Warner To Unsubscribe: send mail to [EMAIL PROTECTED

Re: Problems with PCMCIA Cards

In message <[EMAIL PROTECTED]> Edwin Culp writes: : 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. That's an oversight on my part. Which I'm correcting right

Re: Wish list for PCCARD

In message <[EMAIL PROTECTED]> "Chris Silva" writes: : Would be nice if the pccard.conf.example had the D-Link DFE-650 in it! : For the hell of it, I tried the DE-660, no dice :( If you send me one, I'll add it to the list Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe

Re: Problems with PCMCIA Cards

In message <[EMAIL PROTECTED]> "Matthew N. Dodd" writes: : Too many drivers require knowledge of specific cards in order to properly : handle 'quirks'. This isn't going to change. While a recompile is : annoying we can be assured that a driver maintainer will only add IDs to a : driver after th

Re: Problems with PCMCIA Cards

In message <[EMAIL PROTECTED]> Mike Smith writes: : It can make a pretty good guess though; certainly good enough in most : cases. The problem with guesses is that they are guesses and often wrong. Consider a simple case. If I don't have a sound driver configured on my laptop, IRQ 5 could appe

Re: Error building current

In message <[EMAIL PROTECTED]> "David O'Brien" writes: : On Thu, Jan 20, 2000 at 11:01:10AM -0800, Tim Moore wrote: : > CVS'uped today: : ... : > gcc/version.c is "dead" in my CVS repository. Has my repository been : > corrupted somehow? : : Please try again. Did you change release tags or som

Re: 3C589 problems (was: 4.0 code freeze scheduled for Jan 15th)

In message <[EMAIL PROTECTED]> Will Andrews writes: : On Tue, Jan 18, 2000 at 02:48:25AM -0800, 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 a

Re: 3C589 problems (was: 4.0 code freeze scheduled for Jan 15th)

In message <[EMAIL PROTECTED]> Frank Mayhar writes: : Now I'm looking forward to the newcard cardbus support so I can finally use : the 575BT which came with the laptop. (Tapping fingers impatiently. :-) Hope you are tapping something soft :-) Wouldn't want you to hurt yourself, or have others

Re: Please help spread the CVSup mirror load more evenly

In message <[EMAIL PROTECTED]> John Polstra writes: : > Can you make cvsup accept multiple servers to try in it's configuration : > file? : : I'll add that to the to-do list. I have a very crude script that does its own (fixed) round robin of multiple servers. It tries three times fast (yes, I

Re: Please help spread the CVSup mirror load more evenly

In message <[EMAIL PROTECTED]> Chuck Robey writes: : I would think using a fixed order would be a really bad thing, causing : overload of the first server in line. Did I misunderstand you? How about : doing a script (say in perl, it has random numbers) that randomly picks : the server from a lis

Re: when is FreeBSD-4.0 up for release ?

In message <[EMAIL PROTECTED]> Mohit Aron writes: : wasn't the release date set for Jan 15 ? Anyone knows the new : tentative date ? Thanks, No. Jan 15 was a feature freeze. Likely first part of Feb for a release, but no date has been widely circulated. Warner To Unsubscribe: send mai

Re: Please help spread the CVSup mirror load more evenly

: > Does it matter? Who cvsup's regulary more than once or twice a day? : > Committers AFAIK do cvs directly. : I "cvs co" from my local copy of the repository, which is kept : up-to-date using cvsup. When I'm making lots of commits, I'll do 10-20 cvsups in a day, but usually it is more like 3-5

Re: Please help spread the CVSup mirror load more evenly

In message <[EMAIL PROTECTED]> "David O'Brien" writes: : "load" on the mirror. Where "load" is either one of the connection : slots, or actual kernel resource load if I have 20% packet loss and thus : cause a lot of retransmissions to occur. Hmmm. A thought just occurred to me. There's no need

Here's what I'm using

OK. I said I'd clean this up and send this out. Well, I didn't get as much ceanup done as I'd have liked. The order of hosts is arbitrary and works for me. I'm sure this could be improved, especially to make the order random. Warner #!/bin/sh if [ -z "$1" ]; then hosts=" \ cvs

Re: Please help spread the CVSup mirror load more evenly

In message <[EMAIL PROTECTED]> Brian Somers writes: : I like this idea, except that some sort of consistency is required - : ie, once I've started using cvsupX, I'd like to use it in preference : to slightly better machines unless it stays bad for some configurable : number of connections

Re: PCCARD support

In message <[EMAIL PROTECTED]> Forrest Aldrich writes: : Where are we with getting PCCARD support, such as the : 3COM MegaHertz (3CCFEM556 B) card in the mainstream : distribution? Should be there already. If it isn't, then contact me and we'll talk. Warner To Unsubscribe: send mail to [EMAI

Re: PCCARD support

In message <[EMAIL PROTECTED]> "Matthew N. Dodd" writes: : On Sun, 23 Jan 2000, Forrest Aldrich wrote: : > Where are we with getting PCCARD support, such as the 3COM MegaHertz : > (3CCFEM556 B) card in the mainstream distribution? : : Can you use the output of 'pccardc dumpcis' to construct an e

Re: Please help spread the CVSup mirror load more evenly

In message Brad Knowles writes: : Doesn't work. There might be a very low latency but : low-bandwidth connection between you and one of the servers, when you : (and everyone else) would be better off if you instead connected to a : server that show

Re: APM still ignoring DEVICE_SUSPEND errors

In message Nick Hibma writes: : The following patch fixes two things: First, DEVICE_SUSPEND errors are : no longer ignored. Since we have defaults for methods we should no : longer ignore these errors. Also, DEVICE_RESUME wasn't done when the : a

Re: Please help spread the CVSup mirror load more evenly

In message <[EMAIL PROTECTED]> Chuck Robey writes: : That's the precise reason I suggested a system that used no probing, had : feedback, and forced shared load in spite of user misconfiguration. Got : shouted down. One reason I think that you've been shouted down (and me too, since I had simila

Re: Please help spread the CVSup mirror load more evenly

In message <[EMAIL PROTECTED]> Chuck Robey writes: : Oh. If that's a problem, it would be a fatal problem (would be for me, : sometimes). It used to be a big problem. When cvsup was first getting mirrors, some seemed to update every 15 minutes, while others updated what seemed like every two da

Re: 3com 574-tx PCMCIA

In message <[EMAIL PROTECTED]> VINSON WAYNE HOWARD writes: : 1. I've had some people tell me that support for the 3com 574-tx PCMCIA : card was definitly in -current, and other people who weren't so sure. Is : it, and if so, under what driver? The ep driver claims to support this card. the pcca

Re: 3com 574-tx PCMCIA

In message <[EMAIL PROTECTED]> "Matthew N. Dodd" writes: : On Mon, 24 Jan 2000, Warner Losh wrote: : > The ep driver claims to support this card. the pccard.conf.sample : > file also claims to support this card. Matt Dodd claims to have fixed : > support for this card

Re: APM still ignoring DEVICE_SUSPEND errors

In message <[EMAIL PROTECTED]> Mitsuru IWASAKI writes: : > > Any reason to not shoot the apm_hook_{suspend,resume} in the head and : > > just use newbus suspend/resume everywhere? : > : > Are there any non-newbus devices which need suspend/resume? I think the : > i386 clock uses the apm hooks bu

BROKEN WORLD

Peter, I'd like to see your world log, and the output of cd src/share/mk ; cvs diff bsd.kmod.mk. I get the following error when I try to build world as of about 2 hours ago. I just did a cvsup and only things in lib and ports updated. ===> sys/modules/vpo @ -> /home/imp/FreeBSD/src/s

Re: BROKEN WORLD

Warner Losh writes: : I'd like to see your world log, and the output of : cd src/share/mk ; cvs diff bsd.kmod.mk. I get the following error : when I try to build world as of about 2 hours ago. I just did a cvsup : and only things in lib and ports updated. Ummm, I think cv

Re: ep0 incorrectly probed

In message <[EMAIL PROTECTED]> "Matthew N. Dodd" writes: : Using the boot configuration screen can you disable all devices that are : not installed? : : I suspect something is clobbering the board after it is identified. We've had *BAD* luck with the ex driver doing this... Warner To Unsubsc

Comments on this patch?

I've been running this for a while. I reversed the normal order to make it easier to do the math w/o having to shift columns and flip things over. BTW, I'm getting numbers that are 2x bigger than before :-(.I had makebuildworld down to around 1:20 at one point, but now it is 2:40. Comments

Re: Comments on this patch?

In message <[EMAIL PROTECTED]> "David O'Brien" writes: : > BTW, I'm getting numbers that are 2x bigger than before :-(.I had : > makebuildworld down to around 1:20 at one point, but now it is 2:40. : : Which compilers for both times? What ever was on -current as of 2.5 years ago. This is co

Re: Something strange with pccard/ed0 ?

In message <[EMAIL PROTECTED]> Eric Jacoboni writes: : that ed0 already exists ? Because there is an ed0 on isa already, even if it isn't attached. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: Problems installing FreeBSD 4.0 20000125-CURRENT

In message <[EMAIL PROTECTED]> Mike Smith writes: : It doesn't do anything to the keyboard, it just calls the BIOS to find : out whether keys have been pressed. I've been seeing the hit twice fast problem for months. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe fre

Re: Problems installing FreeBSD 4.0 20000125-CURRENT

In message <[EMAIL PROTECTED]> Mike Smith writes: : > In message <[EMAIL PROTECTED]> Mike Smith writes: : > : It doesn't do anything to the keyboard, it just calls the BIOS to find : > : out whether keys have been pressed. : > : > I've been seeing the hit twice fast problem for months. : : It'

Re: Comments on this patch?

In message <[EMAIL PROTECTED]> Bruce Evans writes: : I plan to put timestamps on most of the "<<<" lines and remove all : the ornation around the "<<" lines. Almost every large target could : begin by (optionally of course) printing the time. Sounds more general than mine... Warner To Unsubs

Re: Problems installing FreeBSD 4.0 20000125-CURRENT

In message Alex Zepeda writes: : in a row quickly occasionally screw up. Also sometimes I'll be able to : catch the screwed up booter when I notice that it doesn't respond to me : hitting enter (In 9 seconds... hit enter.. 8 seconds.. hit enter..

Re: Problems installing FreeBSD 4.0 20000125-CURRENT

In message <[EMAIL PROTECTED]> Garrett Wollman writes: : < said: : : > That's not correct; your DHCP configuration should reflect the hostname. : : No, it shouldn't. As I keep on trying to explain, the DHCP addresses : are: : : 1) Temporary. : 2) Meaningless. : 3) Temporary.

Re: Problems installing FreeBSD 4.0 20000125-CURRENT

In message <[EMAIL PROTECTED]> Mike Smith writes: : > That reminds me. sysinstall *SHOULD*NOT* hard code the IP address : > that it gets from dhcp into rc.conf. I've seen this in 3.2, but : > haven't tried since then to reproduce this. : : It doesn't do that anymore; it was a nasty hack to work

Makefile.inc1 change

The following has survived a make buildworld at least once. It optimizes buildworld a little by not building fortran as part of the build tools. This looks like a safe change to make, since we have no fortran in the tree that needs to get built. It doesn't disable building of fortran later in

Re: PAO

In message <[EMAIL PROTECTED]> VINSON WAYNE HOWARD writes: : I've been folowing 4.0, and I have a laptop I'd like to try it on... but I : can't figure out how to get support for a 3com 574-tx... normaly Pao would : handel that, but I didn't see a pao 4.0 cvs branch. Am I just SOL, or is : there

Re: Makefile.inc1 change

In message <[EMAIL PROTECTED]> "David O'Brien" writes: : I like it. If it passes a clean and -DNOCLEAN buildworld, commit that : baby! OK. It passes a clean buildworld + installworld. I'll crank up the -DNOCLEAN right now. Looks like the savings aren't huge. Like 3 minutes out of 140 on my f

Re: Makefile.inc1 change

In message <[EMAIL PROTECTED]> Jeroen Ruigrok/Asmodai writes: : All the bits help. =) : : And anyways, as you said, compiling it twice seems a bit unnecessary. : : Feel free to commit when you're sure. I'm sure. I did a make buildworld make installworld. I then did a make buildworld -DNOCLEA

Re: Makefile.inc1 change

In message <[EMAIL PROTECTED]> Bruce Evans writes: : This breaks bootetrapping of fortran. Fortran is not built as a build- : tool. Only a tool to build fortran is built. This tool is like the : internal tools for sh and libcurses, etc. It must be built in the host : environment, since the ve

Re: Makefile.inc1 change

In message <[EMAIL PROTECTED]> Bruce Evans writes: : > So I should back this out? I didn't do a 3.3 buildworld. : : Of course. OK. I'm doing a 3.3 buildworld right now on a virgin 3.3R system. I'll let you know what happens with that. If it is a problem at all, then I'll back it out (since o

Re: Makefile.inc1 change

In message <[EMAIL PROTECTED]> Bruce Evans writes: : > So I should back this out? I didn't do a 3.3 buildworld. : : Of course. OK. I've done the build on 3.3 and it works. It does break cross compilation. There is a tool (fini) that gets built on the host with the host libraries and run on

Re: Makefile.inc1 change

In message <[EMAIL PROTECTED]> Bruce Evans writes: : David committed Marcel's workaround for the problem with make depend in : f771 2 weeks ago. I don't know why you still have problems. No. I'm not having problems there. I was just making observations. : Deleting things is another workaroun

Re: Makefile.inc1 change

In message <[EMAIL PROTECTED]> John Polstra writes: : In article <[EMAIL PROTECTED]>, : Warner Losh <[EMAIL PROTECTED]> wrote: : : > I will back it out until after 4.0 so this change can be analized in :^^^

PAIN

What's the current wuildworld times for a 486DX2-66 + 12M RAM over NFS? I have a small box that I'd like to torture test before putting into service and thought this would make a good week long test. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in t

Re: PAIN

In message <[EMAIL PROTECTED]> Andy Farkas writes: : This was a 'buildworld' of 3.4-stable, on 486DX2-66 with 32MB RAM, and : both src and obj on the same local disk (softupdates enabled): I'm doing this over NFS and only have 12MB of RAM. : Scriptdone on Thu Jan 20 16:22:31 2000 : Script s

Re: PAIN

In message <[EMAIL PROTECTED]> Greg Lehey writes: : I did a make world on my PDP-11 yesterday. It took less than a day. : But that's 2.11BSD. Turns out that 12MB + 30MB of swap isn't enough to build world. I ran out of swap and the machine rebooted (at least that's what I think happened, since

Re: old style pcic attach messages - conversion to newbus

In message Nick Hibma writes: : pcic-pci0: irq 9 at device 19.0 on pci0 : pcic-pci0: driver is using old-style compatability shims : pcic-pci1: irq 9 at device 19.1 on pci0 : pcic-pci1: driver is using old-style compatability shims : : to : :

Re: UPDATING

In message <[EMAIL PROTECTED]> Max Khon writes: : actually xinstall cannot be built before make world or make buildworld : because of undefined symbols `setflags'. What's the right thing then? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body

Re: UPDATING

In message <[EMAIL PROTECTED]> Max Khon writes: : actually instructions are wrong. : you can't build xinstall before `make buildworld' now with old libc. I've seen multiple, conflicting reports on this. I've not personally hit this bug. What's the exact sequence one must do? Warner To Unsubs

Re: The Commit That Broke PCM

In message <[EMAIL PROTECTED]> Alex writes: : # pnpinfo : Checking for Plug-n-Play devices... : No Plug-n-Play devices were found Makes sense because this looks for PnP ISA addin cards. OK, taking the lead from http://members.hyperlink.net.au/~chart/pnpid.txt, lets have a crack at these things:

Re: AIC-7899 SCSI Driver?

In message <[EMAIL PROTECTED]> Osamu MIHARA writes: : Is anybody here working on driver for AIC-7899, Ataptec's Ultra160 : SCSI controller??? I thought that Justin just did commits for this. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of

Re: The Commit That Broke PCM

In message <[EMAIL PROTECTED]> Alex writes: : Many thanks for your explanation. The question is why PNPBIOS tries to : attach and assign resources to devices that have already been attached : (things like AT DMA controller, keyboard controller, math coprocessor, : printer port, etc.) Is it not

Re: ata (CDROM mount) and PCCARD problems (xe driver) with 4.0

In message <[EMAIL PROTECTED]> Andreas Klemm writes: : a) Xircom Card isn't detected : : Though I get a message during boot: : devclass_alloc_unit: xe0 already exists, using next available unit number : : Ejecting and reinserting doesn't cure the problem. Known problem. I'm working on a sol

Re: Problems make installworld

In message <[EMAIL PROTECTED]> "Dan Langille" writes: : OK. I'll cvsup to be sure I have the latest. And try the whole process : again. FWIW: I'm following the instructions mentioned by Jim Bloom in : the UPDATING thread (msg id = [EMAIL PROTECTED]). : : cheers : : cd /usr/src :

Re: 3.x to 4.0 upgrade problems

Thus spake Amancio Hasty ([EMAIL PROTECTED]): > Is it possible to checkin a file called something like "/usr/src/FLASH" to hold > temporary information on the current status of how to build the system? Are you volunteering to maintain it? I have enough trouble with keeping UPDATING current some

Re: Adaptec 1460 PCMCIA help

In message <[EMAIL PROTECTED]> Bruce Burden writes: :When pccardd runs, it reports "Driver allocation error". You are trying to allocate resources that conflict. : Do I need the cable inserted at both ends, with the SCSI :device powered up? (At this time, only the card is inserted)

Re: ATA and DMA

In message <[EMAIL PROTECTED]> Soren Schmidt writes: : Look at the ata.4 manpage, there is a sysctl knob that can change the : modes, if it gets too bad we can always make it boot in PIO mode, and : then the user can change to known safe DMA modes in rc.something... I know that I have one wdma dr

Re: from 3.x to 4.0, not the xinstall thing

In message <[EMAIL PROTECTED]> Kai=?iso-8859-1?q?_Gro=DFjohann?= writes: : Hm. Upon closer inspection, you're right. The following entry has : this: I had thought to put something like : / : | 19990929: : | The sigset_t datatype has been changed from an integral type : | t

Re: ftp 10.10

In message <[EMAIL PROTECTED]> Yoshinobu Inoue writes: : If standard documents would be updated to disallow it in the : future, then we need to think of changing getaddrinfo() : behaviour at that time. Agreed. I think in code freeze/feature freeze it is a bad time to change this, reguardless of

Re: Megahertz pccard

In message <[EMAIL PROTECTED]> Gerald Abshez writes: : FYI, Warner has stated that Cardbus isn't working, and there are known : problems with some of the ethernet cards (interrupts don't seem to be : working correctly). As far as I know, the interrupt problems were fixed by Matt Dodd a while ago.

Re: Megahertz pccard

In message <[EMAIL PROTECTED]> Forrest Aldrich writes: : I'm using the floppies from the 01/27 CURRENT (as that's all they provide : now, on current.freebsd.org)... and I can't get it to recognize the : cards. Period.When it goes to initialize, and time for installation, : nothing shows up

Re: Megahertz pccard

In message <[EMAIL PROTECTED]> Chris Webb writes: : FWIW, I'm still see the mysterious loss of interrupts after a suspend or : hibernate on my Vaio N505X with a 3com Megahertz card (now running : -current cvsuped and built this morning). Yes. That 's because we need acpi in order to properly s

Re: Megahertz pccard

In message <[EMAIL PROTECTED]> Gerald Abshez writes: : ep0: No irq?! You have an irq conflict. Make sure that pccard.conf.sample lists only those IRQs that are definitely free on your machine. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body

Re: ftp 10.10

In message <[EMAIL PROTECTED]> Peter Jeremy writes: : Since it's sort-of related: netstat(1) will drop trailing 0's from : the routes it prints out, ie 10.2.3.0/24 will print as 10.2.3/24 : (though route(8) won't accept 10.2.3/24 as an input). : : IMHO, having a 172.16 mean a network address of

Re: Slim SCSI log errors (PCMCIA)

In message <[EMAIL PROTECTED]> Bruce Burden writes: : aic0: at port 0x340-0x35f irq 8 slot 1 on pccard1 : aic0: aic6360, dma, disconnection, parity check : pcic0: Error 22 irq 8 I believe that irq 8 is specifically filtered at pcic interface. It is a bogus interrupt and generally cannot be rout

Re: Megahertz pccard

In message <[EMAIL PROTECTED]> "David O'Brien" writes: : On Tue, Feb 08, 2000 at 11:56:43AM -0800, Parag Patel wrote: : > Seems like the default IRQs used by pccard are being used by something : > else on your laptop. The default line in /etc/pccard.conf.sample is : > : > irq 3 5 10 11 1

Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader.

In message <[EMAIL PROTECTED]> Soren Schmidt writes: : Busspace is a joke, I'm perfectly fine with calling those macros : in[bwl]/out[bwl] like they should be :) You wouldn't say that if you've had to deal with all the oddities of a mips box. : Busdma, hmm, well I dont see that helping here eith

Re: annoying problem with ncurses, acs_chars and xterm

In message <[EMAIL PROTECTED]> "Jose M. Alcaide" writes: : Hummm... is there any way to force ncurses to use the old '-', '|' and : '+' characters for drawing lines and boxes (perhaps the "ac" termcap : capabilility)? I prefer lucidatypewriter over fixed font. On second thought: xterm-foo:as=:ae

Re: feedback on CD install of 4.0-RC2

In message <[EMAIL PROTECTED]> Anatoly Vorobey writes: : I'm actually scared by "novice" because it would be inflicting on me : defaults I would almost probably not want. I never run anything but : "custom", and I suspect many people do the same. I'm much too impatient to run anything but express

Re: openssl in -current

In message <[EMAIL PROTECTED]> "David O'Brien" writes: : Which OpenBSD has done -- so why was it so easy for them? They have the : *same* rules to live by that we have -- even though they are Canadian, : the rsaref libs came from USA, thus they cannot be exported from Canada. No. The RSA that t

Re: timed/adjtime() on -current

In message <[EMAIL PROTECTED]> Maxim Sobolev writes: : Why? As long as the timed is in the base system and serves the basic : need to syncronise time across several machines in the LAN I do not : see any objections to not use it. Its main advantage that it's : permit updating time via ntpdate (the

routed dumping core?

Before I go off and sink a huge amount of time into this, I was wondering if anybody else was noticing that routed in 4.0-rc2 was dumping core within a minute of the system starting. We have 4 different machines that this is hitting right now, but have not had the time to track it down any furth

Re: 4.0RC missing libXThrStub.so.6?

In message <[EMAIL PROTECTED]> "Louis A. Mamakos" writes: : With the 4.0-RC image, and sysinstall, I was now able to use a PCMCIA : ethernet to NFS mount the distribution media. It would have been nice : if the PCMCIA CDROM drive would have worked, but this was good enough. We're working on get

Re: PCI irq setting

In message <[EMAIL PROTECTED]> Remy Nonnenmacher writes: : After moving all Video cards (4 matrox), I noticed that, at boot, the : video cards monopolize a lot of usefull irqs: : : 9 : Matrox 1, integrated 82559 (Network), integrated aic7892 (SCSI), USB : 11: Matrox 2, Matrox 3 : 12: Matrox 4 :

Re: annoying problem with ncurses, acs_chars and xterm

In message <[EMAIL PROTECTED]> Alexander Leidinger writes: : Works here without problems (TERM = xterm & xterm-color). : : Wild guess: Does your shell support 8bit-chars? No. The line drawing characters aren't 8 bit characters on VT100 derived terminals. My guess is that you don't have a prope

Re: annoying problem with ncurses, acs_chars and xterm

In message <[EMAIL PROTECTED]> "Jose M. Alcaide" writes: : Hummm... is there any way to force ncurses to use the old '-', '|' and : '+' characters for drawing lines and boxes (perhaps the "ac" termcap : capabilility)? I prefer lucidatypewriter over fixed font. Yes. It's all a matter of the right

Re: ATA Drivers and Kernel Panic during INSTALL

In message <[EMAIL PROTECTED]> Thomas Veldhouse writes: : So, my question is, why NOT? If the old drivers can do it and the Linux : drivers can do it, I have to wonder why? This was a common interface to : say the least. Becaue they have data corruption bugs that can only partially be worked a

Re: pccardd and mapping memory descriptors

In message <[EMAIL PROTECTED]> [EMAIL PROTECTED] writes: : I believe setting MEM_ASSIGNED is the proper fix and attached is the : one line patch. This looks goo.d : PS: anybody know why cardaddr is set to 16k? No. I have no clue Maybe a kludge left over from an old card? Warner To Unsu

Re: feedback on CD install of 4.0-RC2

In message <[EMAIL PROTECTED]> Kai=?iso-8859-1?q?_Gro=DFjohann?= writes: : Does this mean that this option should be called `guided'? I know a : little bit about Unix but haven't installed FreeBSD more than five : times or so. And I always thought that the novice install meant that : I didn't g

Re: 4.0(current) on a 486SLC2 ?

In message <[EMAIL PROTECTED]> Kelvin Farmer writes: : I was wondering if its possible to run FreeBSD-4.0 on a 486 SLC2 66mhz. The village ran its dialin server on this machine using 2.2.5R (and later points on the 2.2.x stable branch) for years w/o problems. If there is a problem, it likely isn

Re: devices under 4.0

In message <[EMAIL PROTECTED]> R Joseph Wright writes: : I recently upgraded from 3.2 to 4.0. I use an ide hard disk, and would : like to know how to change over the devices. I created the new devices : by copying over /usr/src/etc/MAKEDEV to a new /dev directory and running : it, but it didn't

Re: openssl in -current

One thing to keep in mind is that on Sept 8, 2000 the patent for RSA expires and this whole mess goes away. Or at least devolves into the usual crypto export mess rather than the crypto export plus rsa patent law plus rsaref license jumping. Warner To Unsubscribe: send mail to [EMAIL PROTECTED

Re: openssl in -current

In message <[EMAIL PROTECTED]> "David O'Brien" writes: : On Sat, Feb 19, 2000 at 08:34:42PM -0800, Jordan K. Hubbard wrote: : > : > 1. They're in Canada : : What does that buy them? They have the same restrictions on rsaref since : it originated from the USA. They don't use rsaref. : > 2. Wha

Re: [PATCH]: Teach make.conf about FETCH_BEFORE_ARGS

I use the following: FETCH_CMD=runsocks ftp -p in my /etc/make.conf. Too bad ftp and fetch don't have compatible command lines. I sometimes have to add: FETCH_BEFORE_ARGS= FETCH_AFTER_ARGS= to the command line when ports are silly enough to assume too much about the fetch command. This lets

<    1   2   3   4   5   6   7   8   9   10   >