Search Engine Optimization Kit-2001 24123
Get Top 10 Positions With The Search Engine Optimization Kit-2001 No hype ... no gimmicks ... just the facts ... and only $59! Hello Friend, We created the Search Engine Optimization Kit-2001 to achieve high positions in search engines. This unique Kit includes: Detailed information about how search engines work, Step-by-step instructions to create, high-ranking,"search-engine-friendly" pages, All the tools and resources you need to create pages, submit to engines and track your placements, and Ongoing personal support by email and phone. Click to receive Free Information about Search Engines and the Kit, or call direct to 937-640-2762. We reply promptly to all inquires. Dr. Jerry R. Perrich, Director The Internet Marketing Institute, Inc. Helping You Be Successful Online 937-640-2762 PS - Please forward this email to any of your business associates or friends who may benefit from it. REMOVAL INSTRUCTIONS Per federal legislation, you can be removed from this mailing list at no cost to you by simply clicking here Remove Please. You will be promptly removed. Please note that interfering with this federally approved method of removal will deny others the opportunity to be removed. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PAE related crash
On Thu, 2 Oct 2003, Hendrik Scholz wrote: > Hi! > > I've just installed 5.1-RELEASE (updated to -current) on a > Dual Opteron 1.4 with 6GB memory installed (MSI K8D Master-F). > Without 'options PAE' the system works fine (beside the 'missing' 2GB). ... Does PAE even work on non-Intel CPUs? I thought it was Intel specific. The AMD recommended way of using 4+GB is to put the processor in 64bit mode. Can you try FreeBSD amd64 instead of FreeBSD i386? PAE is rather a crude kludge in comparison with 64bit native addressing, so if FreeBSD amd64 works for you, it is definitely the better solution. Tom ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Postfix locks 5.1-servers?
Usually if networking locks up like this, you should check the mbuf usage. It is possible for resource starvation to cause a situation where TCP connections are accepted, but can't be sent data. "netstat -m" If that doesn't work, I would recommend cvsup'ping one of the machines to -current. 5.1-p10 just has security fixes, not bug fixes. Tom On Wed, 29 Oct 2003, Niklas Saers Mailinglistaccount wrote: > Hi, > are anyone familiar with conditions where postfix may bring a 5.1-p10 > server to a halt, making the server accept incoming ports (such as 22) but > serve nothing, making getty(8) become non-respondent (pressing enter > doesn't give any feedback) and making the server ignore ctrl-alt-del etc? > > I've got two boxes running FreeBSD 5.1-p10 and Postfix 2.0.10,1 and > 2.0.13,1. They also have a java process (v1.3.1 and v1.4.1) running, but > that one is an extremely tiny process that can only be accessed from one > specific IP and when executing lives for a couple of milliseconds. > > Does this ring any bells with anyone? We've been at it for a while and not > being able to figure it out. The boxes are quite different hardwareish, so > I don't suspect that being the problem. > > Cheers > > Niklas Saers > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Postfix locks 5.1-servers?
All the time or sometimes? An unresponsive local console means that the entire machine is blocked though, not just networking. I'm using 5-current right now, and obviously I'm able to type this e-mail. Tom On Wed, 29 Oct 2003, Andy Hilker wrote: > > Hi, > > i am using current. Similar problems *without* postfix. Login via ssh > results in print motd, but nothing more. > Login on local console results in nothing after pressing enter on > username. > > Andy > > You (Tom) wrote: > > > > Usually if networking locks up like this, you should check the mbuf > > usage. It is possible for resource starvation to cause a situation where > > TCP connections are accepted, but can't be sent data. "netstat -m" > > > > If that doesn't work, I would recommend cvsup'ping one of the machines > > to -current. 5.1-p10 just has security fixes, not bug fixes. > > > > Tom > > > > On Wed, 29 Oct 2003, Niklas Saers Mailinglistaccount wrote: > > > > > Hi, > > > are anyone familiar with conditions where postfix may bring a 5.1-p10 > > > server to a halt, making the server accept incoming ports (such as 22) but > > > serve nothing, making getty(8) become non-respondent (pressing enter > > > doesn't give any feedback) and making the server ignore ctrl-alt-del etc? > > > > > > I've got two boxes running FreeBSD 5.1-p10 and Postfix 2.0.10,1 and > > > 2.0.13,1. They also have a java process (v1.3.1 and v1.4.1) running, but > > > that one is an extremely tiny process that can only be accessed from one > > > specific IP and when executing lives for a couple of milliseconds. > > > > > > Does this ring any bells with anyone? We've been at it for a while and not > > > being able to figure it out. The boxes are quite different hardwareish, so > > > I don't suspect that being the problem. > > > > > > Cheers > > > > > > Niklas Saers > > > ___ > > > [EMAIL PROTECTED] mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > > > > ___ > > [EMAIL PROTECTED] mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > -- > Andy Hilker-- mailto:[EMAIL PROTECTED] > http://www.cryptobank.de -- PGP Key: https://ca.crypta.net > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: jumbograms (& em) & nfs a no go
On Fri, 31 Oct 2003, Michal Mertl wrote: ... > > As I recall, when I used a crossover cable, I could not get the > > adapters to go to 1000, only 100. That might have been the cable, > > or not. > > I can confirm it works equally well with crossover as with straight cable. Depends usually. Some cards have auto-crossover detection now. And so do some switches (ex. Catalyst 3700 series). > -- > Michal Mertl Tom ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Intel I440GX+
On Thu, 6 Nov 2003, Scott Likens wrote: ... > Onboard SCSI, 1gig of ECC, dual P2-450's. Never had this problem > before. I hope you are using P3s, or Xeon CPUs not P2s, since P2s are not able to cache memory above 512MB, which means that things will be real slow. > Quite rare. > > Thanks > -- > Scott Likens <[EMAIL PROTECTED]> > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Compaq Proliant 2500 - freebsd 5.1 install problems
Sounds very similar to a problem that I have with FreeBSD 5.1. As soon as /stand/sysinstall is started, the display adaptor turns off! This is on a Dell Poweredge 6350 with 4xXeon 550s. I never did get FreeBSD 5.x working on any of the 6350s that I have, but 4.8 works perfectly. Tom On Thu, 6 Nov 2003, Christer Solskogen wrote: > I`m trying to get FreeBSD 5.1 installed, but sysinstall never shows. > The last info I get is "/stand/sysinstall running as init on vty0" and it > stops. It dont do anything more. > FreeBSD 4.8(and 4.9 i guess, havent tried yet) works. > > Any sollution? > Btw, I have set the OS to be 'Other' in BIOS. > > > -- > Med vennlig hilsen / Best regards > Christer Solskogen > http://dtz.cjb.net - http://carebears.mine.nu > > "Cheap, but not as cheap as your girlfriend!" > -Spider Jerusalem > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.2-RELEASE TODO
On Mon, 1 Dec 2003, Scott Long wrote: > On Tue, 2 Dec 2003, Greg 'groggy' Lehey wrote: > > On Monday, 1 December 2003 at 10:01:23 -0500, Robert Watson wrote: ... > > > > I'm currently investigating ACPI problems on a dual processor Intel > > motherboard (re@ knows about this). It looks as if the new code is > > much fussier than the old code about the quality of the motherboard > > BIOS: this machine runs fine on 5.1, but won't finish booting on > > 5.2-BETA. Yes, this is probably an ACPI bug, but users aren't going > > to see it that way: if we release a 5.2 which won't boot on a lot of > > machines, people are going to blame 5.2, not the machine. I think we > > should ensure that there's at least a fallback for machines with > > broken ACPI. > > This argument is exactly why I added the 'disable acpi' option in the boot > loader menu. Of course, we STILL need to get good debugging information > from you as to why you get a Trap 9 when ACPI is disabled. This is the > more important issue. Just to be complete, there are already a whole bunch of machines that will not boot 5.x, irregardless of the ACPI issues. I've never been able to boot 5.x with ACPI on or off, on any of the 5 Dell PowerEdge 6350 servers I have here, even though they run 4.9 perfectly. I have a PR open on it. So even without the ACPI issues on some hardware, there are still other reasons why 5.x is going to fail to boot. Tom ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.2-RELEASE TODO
On Tue, 2 Dec 2003, Eric Anderson wrote: > Tom wrote: > > > Just to be complete, there are already a whole bunch of machines that > >will not boot 5.x, irregardless of the ACPI issues. I've never been able > >to boot 5.x with ACPI on or off, on any of the 5 Dell PowerEdge 6350 > >servers I have here, even though they run 4.9 perfectly. I have a PR open > >on it. > > > > So even without the ACPI issues on some hardware, there are still other > >reasons why 5.x is going to fail to boot. > > > > > > Are you using a PERC in those boxes? I've seen issues with PERC > controllers on 5.1, but 4.8 worked fine. I received a patch, which > fixed it, but it's a bit hard to install the os, and then rebuild world > without rebooting the machine. :) Well, there are so many kinds of PERC cards. Some are just Mylex cards. Others are MegaRAID. I think they use some Adaptec now. Either way, I tried booting the install CD with all cards disconnected, just to see if I could get the installer up to the main menu. No go. The display switches off as soon as sysinstall starts probing devices. It appears to panic, but the display is dead. Once I was able to use scrolllock at the critical moment just before the kernel starts sysinstall, and prevent the display from switch off, but when I release the scroll lock, I was at the DDB prompt. Not good. > Eric > > -- > -- > Eric AndersonSystems Administrator Centaur Technology > All generalizations are false, including this one. > -- Tom ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.2-RELEASE TODO
On Wed, 3 Dec 2003, Eric Anderson wrote: ... > > Well, there are so many kinds of PERC cards. Some are just Mylex cards. > >Others are MegaRAID. I think they use some Adaptec now. > > > My troubles were with the MegaRAID variant, I'm not sure about the others.. > > > Either way, I tried booting the install CD with all cards disconnected, > >just to see if I could get the installer up to the main menu. No go. The > >display switches off as soon as sysinstall starts probing devices. It > >appears to panic, but the display is dead. Once I was able to use > >scrolllock at the critical moment just before the kernel starts > >sysinstall, and prevent the display from switch off, but when I release > >the scroll lock, I was at the DDB prompt. Not good. > > > > > First - I hope you mean the cards are physically OUT of the machine - it > seemed to me that if they had a logical disk configuration on the card, > it would hang. Although, it sounds like your problem is different. > Actually, it kind of sounds like it thinks you are doing the "-p" boot > thing to check for keyboard and roll over to the serial port. Other > than that, I'm out of ideas (doesn't take long for that to happen > though!).. :( Yes, the cards are physically out of the machine. "-p" seems unlikely, since the display is literally shutoff. The monitor goes into a power-save mode, so it appears that as soon as sysinstall touches whatever devices it touches, the onboard video stops generating output. I've also tried a serial console, which seems to fail the same way. There is simply no output to the serial console after sysinstall starts, and the machine appears to be hung. So, this was with 5.0 and 5.1. I will have to try 5.2 and see if it has the same problem. No one has contacted me about my PR, or even given me any suggestions about more debugging info that I can gather, so unless this gets fixed by chance, I suspect that 5.x is just going to orphan a significant number of machines. Which is a shame, since 5.x would be clearly superior on a quad Xeon machine than 4.9-RELEASE. > Eric Tom ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Kernel versions and kld modules [WAS: this of interest to anyone?]
>>>>> On Sat, 3 Jul 1999, Peter Wemm <[EMAIL PROTECTED]> writes: > A few key suggestions for people still along for the ride: > > 1: When you've got a good running kernel that you're happy with, do yourself > a big favour and copy it from /kernel to /kernel.ok or something like that. > So, when you manage to get a bad /kernel and /kernel.old, you've still got > a fallback that doesn't mean resorting to a fixit disk boot. This reminds me of something I wanted to ask about. A little while back I made the typical junior mistake of building/installing a new kernel without doing the make install of the related modules. In my case, the crash came from kernfs and it was easy to boot single-user and comment out a line in fstab. But my question is with the trend towards more module-ization of the kernel, does saving a /kernel.old make sense without saving a /modules.old? Should the config-generated Makefile for the kernel have a target to build and install the new modules as well (as opposed to installing them with make world)? Should we install modules into some path identified by a kernel version (whatever that means exactly)? The extreme end of this line of logic is the Linux module hashing mechanism, which I've never fully understood. My experience with it is that it can prevent you from using a binary-only module (AFS is the one I'm thinking of) even if the interfaces haven't really changed. It seems like a poor substitute for proper management and versioning of kernel interfaces. I suppose much of this becomes a non-issue outside of -current, and maybe that's why no one has seemed worried about it. Even in -stable, though, I suppose you could have incompatible kernel interfaces introduced that might break modules. It just seems to me that one should consider /kernel plus /modules/* to be more of unit. Thanks for any insights. Tom Pavel Stanford Linear Accelerator Center [EMAIL PROTECTED] http://www.slac.stanford.edu/~pavel/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: yet more TP 600E fun...
I see the same problem when trying to boot FreeBSD-3.0-RELEASE (or there abouts) and later cdroms on my TP770. I can boot FreeBSD-2.2.8 and earlier FreeBSD-3.0-SNAP cdroms just fine. I think it has something to do with the new boot loader that went in just before 3.0-RELEASE. Tom On Fri, 13 Aug 1999, David E. Cross wrote: > I attempt to boot a CD off of the TP600E and I get the following errors: > > "Can't work out which disk we are booting from." > "Guessed BIOS device 0x8b not found by probes, defaulting to disk0:" > > Then whenever it attmpts to access "disk0:" it goes to the floppy drive. > > Suggestions? > > -- > David Cross | email: [EMAIL PROTECTED] > Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd > Rensselaer Polytechnic Institute, | Ph: 518.276.2860 > Department of Computer Science| Fax: 518.276.4033 > I speak only for myself. | WinNT:Linux::Linux:FreeBSD > > > 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: yet more TP 600E fun...
I'd be more than happy to do the pestering if some one could write down a detailed description of exactly how the TP's BIOS is non-compliant. I don't know enough about the boot process and BIOS to write such a description. Tom On Fri, 13 Aug 1999, Mike Smith wrote: > > I attempt to boot a CD off of the TP600E and I get the following errors: > > > > "Can't work out which disk we are booting from." > > "Guessed BIOS device 0x8b not found by probes, defaulting to disk0:" > > > > Then whenever it attmpts to access "disk0:" it goes to the floppy drive. > > > > Suggestions? > > Known weirdness in the TP's BIOS not handled properly by the > bootloader. I don't have immediate plans to do anything about this; > you could try hacking the loader to accept the 0x8b value and see if > that actually works. Or you could pester IBM to DTRT. > > -- > \\ The mind's the standard \\ Mike Smith > \\ of the man. \\ [EMAIL PROTECTED] > \\-- Joseph Merrick \\ [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: Linuxulator: emulation? [was: Q: Extending the sysctl MIB...]
I absolutely agree with Jordan on this point. I'm having an increasingly hard time keeping our lab running FreeBSD over Linux due to pressure from higher-ups who aren't in the technical trenches with me and who don't understand the very good technical reasons I have for running FreeBSD here. One constant sticking point is the linux compatibility module. The higher-ups see the word "emulator" and all manner of warning messages go off in their uninformed heads. In a previous e-mail on this or a related thread I saw the term: "Linux image activator" or something close to this pass by. I think this term gave me a much closer feeling to what I imagine is really going on the the "linuxulator" than the term "emulator" and all its baggage. So we could name it the "Linux image activator" or "Lin-Axe" or some such... Tom On Mon, 16 Aug 1999, Jordan K. Hubbard wrote: > All of this would be true if your personal definition of "emulator" > were the prevailing one, but that is unfortunately just not the > case. :) > > When the average computing public thinks of an "emulator", they think > of something like MAME or the SNES emulator. Even the more > compute-minded folks tend to think of BOCHS or SIMOS when they hear > the word "emulator" and I need only point to the majority of entries > in /usr/ports/emulators in support of this. :-) In any case, my point > is simply that we need to be careful in our use of terminology if we > don't want to lend the majority the impression that our linux > "emulation" code goes through the same sorts of gyrations that MAME > does to run linux binaries. I do get questions at trade shows all the > time about this, and I can state without reservation that none of the > people asking about it share Marcel's definition of the term. :) > > - Jordan > > > 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: 4.0 code freeze scheduled for Jan 15th
On Thu, 6 Jan 2000, Josef Karthauser wrote: > On Fri, Jan 07, 2000 at 08:00:46AM +1100, Darren Reed wrote: > > > > btw, I completely agree with the need to have good pccard/pcmcia support. > > For the first time there was a real reason for me to ditch FreeBSD on an > > Intel platform box (my laptop) and go with NetBSD where my 3c589d works > > just fine. > > > > My 3c589d works just fine now, along with suspend/resume :) (under 4.0). > And these are also working perfectly for me as well under -current on a ThinkPad 770. Tom To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Additional option to ls -l for large files
>> kB and kiB are the proper abreviations, not KB and KiB. I don't know >> if miB or MiB is correct, likely MiB. > > I always thought it was "k/m/b = 1,000/1,000,000/1,000,000,000" >and "K/M/G = 2^10/2^20/2^30". Or was this just some convention I >learned somewhere that I mistakenly thought of as an actual accepted >rule? But, with the letter "M" for example, m = milli-, M = mega- Like Donn was saying, there's no reason not to do it every way. Have the different options selectable by either an environmental variable or a command line switch. I'd vote for default behavior as the traditional: K = 2^10 M = 2^20 G = 2^30 T = 2^40 P = 2^50 .. but also have options for showing the entire unclipped file length, "binary mode international abbreviation standard", and maybe even scientific or engineering notation (for kicks). Tom Embt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: why is my current so .... stable?
At 14:27 01/12/2000 +0100, Christian Carstensen wrote: >On Wed, 12 Jan 2000, Donn Miller wrote: > >> My guess is that once -current gets closer to the release date, it becomes >> more and more stable. I guess the period of greatest instability occurs >> somewhere about 1/4 to 1/2 through the -current life cycle. We could do a >> chart plotting stability vs. time for the life cycle of a given >> -current. That could help people decide whether or not they want to run >> -current. > >This would be great, but I wonder from what source we could take reliable >data about -current's stability. >But what I've meant was: I've had these ugly system freezes not perfactly >reproducable, but very often. From what I've read on current list, the >problems still exist, but not on my system. At least this system runs >stable for 1 day now. I'm wondering, why. > How 'bout some sort of client program that is run via the rc.d and rc.shutdown scripts? When run on bootup it checks dmesg for "WARNING: / was not properly dismounted", and tells a master server whether or not the last reboot was intentional. When run at shutdown it tells the master server the machine's uptime. Of course it would also help to send a 'uname -v' in both situations. This system would have statistical flaws, but it is still an interesting idea. Tom Embt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: why is my current so .... stable?
At 10:52 01/13/2000 +1030, Mark Newton wrote: >On Wed, Jan 12, 2000 at 08:29:44AM -0500, Tom Embt wrote: > > > >This would be great, but I wonder from what source we could take reliable > > >data about -current's stability. > > > > How 'bout some sort of client program that is run via the rc.d and > > rc.shutdown scripts? > >One of the more annoying aspects of IRIX in its default config is >that whenever you do a halt or reboot it'd pop up a menu to ask why. >That information, together with crash dump info and other data about >system failures, can be funnelled into a mail filter which records >historical reliability data; That data can (optionally) be sent back >to SGI too. > >We could provide something like this, but (a) if it's on by default >it'll suck rocks, and (b) if it's off by default nobody will bother >turning it on. Hey ho! > >- mark > Hmm, well the menu thing would surely suck, but we wouldn't really need that info anyway. Perhaps if the startup/shutdown info was just written to /var/log/ and people could optionally enable (as in off by default) something in /etc/rc.conf to actually send the info back to a master server on a regular basis. Even if the info isn't sent to the master it could be parsed locally if so desired. Again, just ideas.. Tom Embt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: My ATAPI CD not come ready
At 09:47 01/25/2000 +0100, Soren Schmidt wrote: >It seems Anders Andersson wrote: >> I have the same problem: >> >> [anders@enterprise:anders] $ dmesg | grep ata >> ata-pci0: port 0xffa0-0xffaf at device 7.1 >> on pci0 >> ata0 at 0x01f0 irq 14 on ata-pci0 >> ata-isa0: already registered as ata0 >> ata0-slave: ata_command: timeout waiting for intr >> ata0-slave: identify failed > >Could I please have a complete dmesg from that ?? > >-Søren > Don't mean to butt in here, I haven't really been following the thread - but I may have found a workaround/clue. I have a Sony CDU-55E (ooold 2x) on secondary master of the PIIX4 on my BP6. By going into the BIOS (the section of it where you would set CHS numbers, LBA, etc) and changing the secondary master device from "none" to "auto", I have gone from: SMP: AP CPU #1 Launched! ata1-master: ata_command: timeout waiting for intr ata1-master: identify failed ad0: 9671MB disk at ata0 as master mode UDMA33 Mounting root from ufs:/dev/ad0s1a to: SMP: AP CPU #1 Launched! ad0: 9671MB disk at ata0 as master mode UDMA33 acd0: CDROM at ata1 as master mode PIO0 Mounting root from ufs:/dev/ad0s1a I stumbled upon this quite by accident, but maybe it'll be of some help to somebody... BTW, this was on a kernel from around 20:00 GMT Jan 25 Tom Embt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: My ATAPI CD not come ready
At 22:01 01/25/2000 +0100, you wrote: >It seems Tom Embt wrote: >> Don't mean to butt in here, I haven't really been following the thread - >> but I may have found a workaround/clue. I have a Sony CDU-55E (ooold 2x) >> on secondary master of the PIIX4 on my BP6. By going into the BIOS (the >> section of it where you would set CHS numbers, LBA, etc) and changing the >> secondary master device from "none" to "auto", I have gone from: >> >> BTW, this was on a kernel from around 20:00 GMT Jan 25 > >Interesting... > >What version is you ata-all.c ?? its damn close to the commit I just >made, that should fix that problem... > >-Søren > That was with 1.43 I just updated all the files in /usr/src/sys/dev/ata (ata-all.c v1.44) and made a new kernel. While rebooting I set the BIOS back to "none" and watched FreeBSD boot. No error :) - then I rebooted to kernel.old (1.43) without touching the BIOS and the error came back. Looks like you got it. Tom Embt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Thinkpad won't boot ISO image
On Wed, 16 Feb 2000, Mike Smith wrote: > > > The problem with the Thinkpad BIOS is where it puts the emulated floppy > > > image's disk number - it's not in the 'normal' place, and I don't exactly > > > know how to deal with it cleanly. If someone were to lend me a thinkpad > > > or look at this it would be easy to fix. > > > > I'd like to help look at this. I have a ThinkPad 770 and it too exhibits > > this behavior. Unfortunately it's my only laptop so I can't loan it out > > but I certainly would like to help out if I can. I've got an > > up-to-date -current running. What code should I look at in sys/boot and > > how do I figure out where the Thinkpad BIOS puts the emulated floppy > > image's disk number? > > You'll need a CD burner and the time & patience to produce a small number > of coasters for this. O.K. I've got a burner and boat loads of cheap media so no problem there. One question though -- Once I've modified the sources as you've outlined below, how do I make the bootable floppy image that gets written to the CDR? > > In sys/boot/i386/loader/main.c:main() you will need to print the value of > initial_bootdev, sometime after the console is initialised. From what > I've seen, I get the impression that it will be something like 0x87. > This is the root of the problem; floppy disks are typically numbered 0,1 > and hard disks are numbered 0x80,0x81, etc. Normally all the unit > numbers are contiguous. Understood (I think) :-) On my Thinkpad I believe I've seen things like 0x8b or some such. This will be the first CD to burn... > > If this is the case, you will need to modify > sys/boot/i386/libi386/biosdisk.c:bd_init() to check whether it's scanned > the BIOS unit number from initial_bootdev, and if not (and it's legal) > scan it as well. Once we've 'probed' the BIOS unit, everything else > should work correctly. O.K. this makes a lot of sense and sounds easy. > > If you decide to take this on, please let me know how you go. Will do! > > Thanks! > And thank you too!!! Tom To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Thinkpad won't boot ISO image
On Wed, 16 Feb 2000, Mike Smith wrote: > > This is a problem with the thinkpad BIOS that I have not had the time to be > > able to track down. It would *appear* to be that the BIOS does not do > > int 13 handling on boot cdroms, and the boot/loader makes much use of that > > for loading the kernel and drivers. > > The problem with the Thinkpad BIOS is where it puts the emulated floppy > image's disk number - it's not in the 'normal' place, and I don't exactly > know how to deal with it cleanly. If someone were to lend me a thinkpad > or look at this it would be easy to fix. > I'd like to help look at this. I have a ThinkPad 770 and it too exhibits this behavior. Unfortunately it's my only laptop so I can't loan it out but I certainly would like to help out if I can. I've got an up-to-date -current running. What code should I look at in sys/boot and how do I figure out where the Thinkpad BIOS puts the emulated floppy image's disk number? Tom To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0R ?
At 19:05 03/13/2000 +, Ben Smithurst wrote: >Jim Bloom wrote: > >> The tag was laid down earlier today. Here is what my current kernel >> claims to be at the moment: > >I saw the RELENG_4 tag in my cvsup log, but I don't think that's the >same as the 4.0 release tag is it? That would be RELENG_4_0_0_RELEASE >surely. > I believe RELENG_4 would refer to the 4.x-STABLE branch (??maybe??), since it is different from 5.0-CURRENT but still not ready for it's first release. I'm no authority on the subject, though. Tom Embt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why not gzip iso images?
[...] > > Another issue is the size. Many factors determine how quickly one can > > obtain the ISO. It would be nice if it were broken into smaller > > volumes. About 10-20 MB each would be good. That way should something > > fail, there less time and bandwidth wasted should one need to start over. > >That would just make things more complicated, and there's no >reason for that. That's what the "reget" command is good for >-- no reason to start over at all. I would like to mention one case where it would have been helpful to have the .iso broken into smaller pieces. I have a 21,600bps net connection which my ISP will disconnect after 6 hours of uptime, and once had a friend (whom is not nearby, but I see on on occasion) download the 3.3-STABLE ISO image for me via his cable modem for me to burn to CD. As luck would have it the file's MD5 checksum did not match up, and I was forced to redownload the entire file over my sloow modem connection (took around 6 days). Had the file been split and a checksum computed for each piece, I could have grabbed only the affected portion of the ISO. This said, I still do not believe it is worthwhile to split the ISO into smaller files, as it only adds complexity to the situation. Concatenating the files back into an ISO would be OS-dependant and perhaps a bit too much for first time users to cope with. I just assume things stay the way they are. Also, should anyone care, I feel that gzipping these files is a waste of time, unless server bandwith is a serious concern. Tom Embt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Anyone running CompuPic?
Not sure which list this should go to, so if I'm in error feel free to point me in the right direction. I was wondering if anyone has had any luck running CompuPic (http://linux.compupic.com) under FreeBSD? It's an excellent image viewer that can do some basic file management as well. Along with Agent, it's one of the few good apps available for Windoze, and I was excited when I heard there was a free *NIX version available. Unfortunately, I haven't been able to get it to run. I'm not in FreeBSD right now so I'm working from memory, but I had some trouble with the install process (it is obviously not as portable as they'd have you believe). I seem to recall setting $UID and installing bash, but the script still bombed after it was installed. Then I had to brandelf it. I tried both "Linux" and "FreeBSD" branding and one was working better than the other though I don't recall which. End result: It starts to load, brings up a splash screen, and exits. I do recall it leaving messages on the console but forget which signal it was dying with. I can get more info if it's wanted but first I'm just asking if anyone else has either had better luck than I. Here's a quote from the website: "CompuPic is highly portable, and Photodex intends to support as many target platforms as possible over time. CompuPic for Linux (and UNIX) is available as a statically linked executable with no library dependencies whatsoever. You need only a Linux or UNIX kernel to run CompuPic. CompuPic has been tested with major Linux and BSD distributions and had no distribution specific issues. If you represent a hardware manufacturer or Linux/UNIX distribution publisher, you can contact Paul Schmidt to discuss Photodex's development plans for a specific platform. Paul Schmidt VP Technology Photodex Corporation 1106 Clayton Lane #200W Austin, TX 78723 (512) 406-3061 - voice (512) 452-6825 - fax [EMAIL PROTECTED]" They seem to make a point of saying "Linux/UNIX" and not referring to all of *NIX OS's as "Linux", even going so far as to mention BSD once. I was therefor a bit surprised when the binary wouldn't run on FreeBSD. I wonder if The Powers That Be would be interested in pursuing the last sentence there? FYI: My system is SMP 4.0-CURRENT from a day or two ago, XFree86 3.3.3.4 from packages, KDE-1.1 from packages, Linux emu running, etc. As far as my FreeBSD proficiency, lets just say I'm probably not the kind of person that ought to be running -CURRENT :) so I don't think I'd be much help in tracking down the problem (aside from being a guinea pig). of course there also exists the possibility that I forgot to insert tab A into slot B and CompuPic indeed runs perfectly in FBSD for everyone else.. and how did it get to be 3AM ? Ugh. well thanks to anyone who can clue me in, Tom Embt ICQ UIN: 11245398 [EMAIL PROTECTED] d:-)> -- "You're one of those condescending Unix computer users!" "Here's a nickel, kid. Get yourself a better computer" - Dilbert. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Anyone running CompuPic?
At 11:21 AM 9/10/99 -0400, you wrote: >On Fri, 10 Sep 1999, Mike Muir wrote: > >> I get the same problem, after brandelfing to linux and running it, the >> splash screen comes up and...disappears with: >> >> compupic: abnormal termination: (null) >> >> Brandelf -t FreeBSD segfaults it without even showing the splash screen. >> >> Nice helpful error message.. can anyone shed some light on that? > >If I were you, I would truss it: > > $ truss -o truss.out compupic > >and see what it's doing just before it dies. > >-- > Ben Rosengart > I just tried to run it again and both compupic and truss core dumped. Both cores as well as truss.out and dmesg available at http://www.embt.com/tom/compupic-crash.tar.gz . Tom Embt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Compupic - yes, it works.
At 09:51 AM 9/11/99 +1200, you wrote: >YOU DA MAN.. that works fine on -current also I'll second that, THANK YOU for this silly but effective solution! >"Gray, David W." wrote: > >> MOVE YOUR /usr/compat DIRECTORY aside - rename it temporarily. Run compupic >> once. You should now be able >> to move /usr/compat back into place (or /compat, if you left it there...) >> Why? I dunno. Found it by accident. > Now another question: Have you been able to get to /usr? When I try to bring it up I get /compat/linux/usr instead. At least /home works.. :) Tom Embt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86-3.3.5/kde-1.1.2/Current today.
At 12:11 AM 9/25/99 +, you wrote: >This morning I made world, updated XFree86 and kde, which didn´t seem to >be a problem until I started X and nowI get revers Icon's - silhouettes >on the kde background. I get no text but a block where the text is and >the mouse will often change to a block. I have never seen anything like >it. I have recompiled X-11 3 times and kde twice. I have erased the >.kde, .kderc, .klogin, Desktop each time. I have no idea where to >look. It was fine yesterday with XFree86-3.3.4 and kde-1.1.1. Also >tried twm and same problem so I can assume the it isn´t kde but .. . >Does the same at -bpp 8/16/24/32 and 640x, 800x y 1024x. > >The video card is a sis-6326 8MB and am running the SVGA server. > >Thanks in advance or any suggestions. > >ed > IIRC someone changed something in KDE recently to make icons work on big Endian machines, perhaps they botched it. If I'm not imagining this, you could probably find it on www.kde.org. Tom Embt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
MajorDomo Problems
I've been mysteriously unsubscribed from -questions sometime between Oct 7th and Oct 10th. My guess puts it at late morning/early afternoon EDT on the 7th. It would seem something is up... good thing somebody mentioned the 'which' command (I'd never heard of it), I was wondering why noone was responding to an earlier post ;) Tom Embt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Today's make world breakage
Ditto here. Tom On Wed, 15 Dec 1999, Forrest Aldrich wrote: > FYI just CVSup'd and got this: > > > > X-UIDL: 495287ccf607850cc65e4c59c7b49751 > > cd /usr/src/lib/librpcsvc; make beforeinstall > cd /usr/src/lib/libskey;make beforeinstall > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libskey/skey.h >/usr/obj/usr/src/i386/usr/include > cd /usr/src/lib/libstand; make beforeinstall > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 >/usr/src/lib/libstand/stand.h /usr/obj/usr/src/i386/usr/include > cd /usr/src/lib/libtacplus; make beforeinstall > sh /usr/src/tools/install.sh -c -o root -g wheel -m 444 >/usr/src/lib/libtacplus/taclib.h /usr/obj/usr/src/i386/usr/include > cd /usr/src/lib/libcom_err; make beforeinstall > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 >/usr/src/lib/libcom_err/../../contrib/com_err/com_err.h >/usr/src/lib/libcom_err/../../contrib/com_err/com_right.h >/usr/obj/usr/src/i386/usr/include > cd /usr/src/lib/libss; make -B hdrs beforeinstall > test -e ss_err.et || ln -s /usr/src/lib/libss/ss_err.et . > compile_et ss_err.et > test -h ss_err.et && rm -f ss_err.et > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libss/ss.h >ss_err.h /usr/obj/usr/src/i386/usr/include/ss > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 >/usr/src/lib/libss/copyright.h >/usr/obj/usr/src/i386/usr/include/ss/mit-sipb-copyright.h > cd /usr/src/lib/libutil;make beforeinstall > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 >/usr/src/lib/libutil/libutil.h /usr/obj/usr/src/i386/usr/include > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 >/usr/src/lib/libutil/login_cap.h /usr/obj/usr/src/i386/usr/include > cd /usr/src/lib/libvgl; make beforeinstall > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libvgl/vgl.h >/usr/obj/usr/src/i386/usr/include > cd /usr/src/lib/libwrap;make beforeinstall > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 >/usr/src/lib/libwrap/../../contrib/tcp_wrappers/tcpd.h >/usr/obj/usr/src/i386/usr/include > cd /usr/src/lib/libz; make beforeinstall > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libz/zconf.h >/usr/obj/usr/src/i386/usr/include > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libz/zlib.h >/usr/obj/usr/src/i386/usr/include > cd /usr/src/usr.bin/lex;make beforeinstall > sh /usr/src/tools/install.sh -C -o root -g wheel -m 644 >/usr/src/usr.bin/lex/FlexLexer.h /usr/obj/usr/src/i386/usr/include/g++ > > -- > >>> Building libraries > -- > cd /usr/src; >COMPILER_PATH=/usr/obj/usr/src/i386/usr/libexec:/usr/obj/usr/src/i386/usr/bin >LIBRARY_PATH=/usr/obj/usr/src/i386/usr/lib:/usr/obj/usr/src/i386/usr/lib >OBJFORMAT_PATH=/usr/obj/usr/src/i386/usr/libexec >PERL5LIB=/usr/obj/usr/src/i386/usr/libdata/perl/5.00503 MAKEOBJDIRPREFIX=/usr/obj >DESTDIR=/usr/obj/usr/src/i386 INSTALL="sh /usr/src/tools/install.sh" >PATH=/usr/obj/usr/src/i386/bin:/usr/obj/usr/src/i386/usr/bin:/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/ssl/bin:/usr/X11R6/bin:/usr/local/samba/bin:/usr/local/home/forrie/bin > make -f Makefile.inc1 -DNOINFO -DNOMAN libraries > cd /usr/src/lib/csu/i386-elf; make depend; make all; make install > rm -f .depend > mkdep -f .depend -a-I/usr/obj/usr/src/i386/usr/include >/usr/src/lib/csu/i386-elf/crti.S /usr/src/lib/csu/i386-elf/crtn.S > cpp: }: No such file or directory > cpp: }: No such file or directory > mkdep: compile failed > *** Error code 1 > > Stop in /usr/src/lib/csu/i386-elf. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > > > > > 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: sysinstall: is it really at the end of its lifecycle?
On Wed, 15 Dec 1999, Donn Miller wrote: > "Jordan K. Hubbard" wrote: > > > > > I was under the impression that Polar Bears are native to the > > > North Pole and penguins are from the South Pole. > > > > Really? What eats penguins then? Maybe walrus? > > Arctic Foxes. > > > - Donn I doubt it. No peguins in the arctic. But Sea Lions definitely do. Tom To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Serious server-side NFS problem
On Thu, 16 Dec 1999, Warner Losh wrote: > In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes: > : If people do a "settimeofday" we change the boot time since the > : amount of time we've been up *IS* known for sure, whereas the boottime > : is only an estimate. > > There is one problem with this. The amount of uptime isn't the same > as the amount of time since the machine booted. How can this happen? > When a laptop suspends, it doesn't update the update while it is > asleep, nor does it update the uptime by the amount of time that has > been slept. IS this a bug in the apm code? > > Warner > IIRC it does update uptime properly after a suspend in 2.2.8 but does not do so in 3.X and -current on my ThinkPad 770. Tom To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Serious server-side NFS problem
On Thu, 16 Dec 1999, Warner Losh wrote: > In message <[EMAIL PROTECTED]> Tom Bartol >writes: > : IIRC it does update uptime properly after a suspend in 2.2.8 but does not > : do so in 3.X and -current on my ThinkPad 770. > > define correctly. Eg, if I suspend for an hour it adds an hour? > > Warner > Yeah, that's what I meant by "correctly". I don't recall seeing a "thundering herd" effect afterwards. Hmmm... which reminds me, I believe this was not stock 2.2.8 but rather 2.2.8-PAO. I had thought that the lion's share of PAO code got merged into 3.0-current at some point. When I tried 3.0-current after this merge, suspend and resume worked fine on my 770 with the exception of uptime. Tom To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Serious server-side NFS problem
On Thu, 16 Dec 1999, Warner Losh wrote: > In message <[EMAIL PROTECTED]> Tom Bartol >writes: > : I tried 3.0-current after this merge, suspend and resume worked fine on my > : 770 with the exception of uptime. > > I can confirm that uptime, at least as reported by uptime(1), isn't > increased in the latest -current. > > Warner > I confirm this as well. Perhaps after suspend we need: Allow ntp to update time and adjust boottime as necessary. Then set uptime = time-boottime Tom To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Success with ATA drivers and UDMA66
[snip] >> What is the rating of your Power supply ? > >Not quite high enough :-( >It's a 300 Watt power supply. > Hehe - I'm running dual 540's (2.2V) on a BP6 (I'm guessing around 30 Watts per CPU), extra case fan, big CPU fans, CD, TNT and an IDE drive (I've had three hooked up once) - on a 235W power supply :) (Although it is probably a better-than-average PS, it's the one that comes with the AOpen HX45 case). One of these days I'm going to hook up a multimeter and see what it draws... Tom Embt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: BP6 (Was Re: Success with ATA drivers and UDMA66)
>[SNIP] > >> I would like to know how HOT other people's processors get. In the >> stationary situation I have a system core (= processor average) temperature >> of 46 and a case temperature of 50 degrees Celcius/Centigrade. > >What do you use for temp. watching ? (I fetched a little hack which is >called wmtempmon). My temps are somewhat lower : around 35/36 °C, as >I've installed "Alpha" coolers, bought from www.3dfx.com. One colleague >at work uses the same sink/fan combo, but with peltier and a monstrous >PSU to get to 572MHz. I've also loaded the latest BIOS from Abit. Perhaps you mean www.3dfxcool.com? Here's my story: I have two PHO fans from that place on my SL36C 366's (540's now). I had to do alot of tinkering to get them stable at that speed, in the end it all comes down to temperature and luck. One of my CPUs will do 550MHz (my goal) with a little TLC, but the other has to be prodded harshly to get it to 540Mhz. In the end I have done the following: - Realize that my heatsinks wouldn't fit over the angled levers on the ZIF sockets. Disassemble ZIF sockets and straighten metal levers in small vise; reassemble ZIF sockets. - Lapp the poorer CPU with successively finer grits of wet/dry sandpaper (it's mirror-like copper color now :) - Lapp the heatsink for this CPU - Turn around the fans on the heatsinks (quieter and works with well with next modification), using 3/16" standoffs made from vinyl hose and covering the side gap with electrical tape to create a ducted "sucking" effect. - Create a complicated cardboard air ducting system inside my case (I kid you not!!) which uses a case80HO (80mm case fan) to suck air in the side vents, blow it in between the CPUs and the AGP card, where the CPU fans suck it back up through the heatsinks, and it gets ducted back out the rear of the case. This dropped CPU temperature by something like 4-5 degrees Celsius IIRC, and is the key to this whole thing working reliably. I think the reason it helps so much is that it bathes the heatsinks in room-temperature air instead of internal case-temperature air, and does not allow "dead air" to recirculate around the heatsinks. On the downside it can reduce circulation for the rest of the components in the case, and should be done with caution. - Determine the "right" amount of heatsink goop to use, get it right and don't ever touch them again. Tip: apply this stuff with a clean single edged razor blade. - Play with CPU speeds and voltages doing ALOT of "make -j 12 buildworld" on a nice warm summer day to seperate the settings that _mostly_ worked from the ones that _really_ worked. Some would run for >30 minutes without a hitch only to sig11 at the last minute. Turns out 2.2V is the sweet spot for both CPUs. In the end I have a very stable dual 540MHz system who's CPUs NEVER exceed 45C and case temp NEVER exceeds 40C (BTW, no A/C here, ambient 65-80F). Was it worth it? It depends what you're time is worth and if you enjoy this sort of thing. It's not for most people, but I certainly had fun. Next project will be a water cooler (faster & quieter, yeah!), and after that I may put a pair of peltiers between the water plates and the CPUs. One must remember that a pair of fast CPUs is not always super useful. My compiling is still pretty much disk/memory bound, and what else uses the real horsepower of two fast Celerons? Games? hah - I've only an original TNT in this box, which is certainly the limiting factor in 3D stuff. One place I've found this system to really shine is running distributed.net clients. In RC5-64 I can get just over 3.0 Mkeys/sec, however right now I'm trying to win the CSC contest (I've personally done about 0.006% of the keyspace so far, out of ~57% total by all distributed.net members). Am I sick and twisted for being so concerned about busting keys? The BP6 is certainly a fun board to play with in FreeBSD, particularly now that the HPT366 is supported (Thanks Soren!), SMP is getting better every day, and there's always new sources to compile. PS - should this be moved to -hardware??? Man, I'm going to regret writing all that, now I've got replies to deal with ;) Tom Embt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Port of ext2fs fsck
OK for starters, a disclaimer: I have nearly zero experience with Linux. ..but I would guess that it is naming the disk much like BSD does, with hdb1...hdb4 being the four bios partitions (BSD slices) and hdb5 and up being the logical DOS-style partitions inside the other "DOS extended partition(s)". I believe Linux does make use of DOS "extended partitions" in this way. If this is true your RH /usr would be /dev/ad1s6, I think. The entry in /dev might not yet exist, though. At 12:26 12/23/1999 -0500, Donn Miller wrote: >Is there such a beast? This would be a big big help to those who >administer Linux boxes from FreeBSD machines. And, it would make >life easier for those of us who dual-boot with FreeBSD and >Linux. Basically, I'd like to see a port of e2fsck in the ports >collection. > >Also, I had this weird problem in the past. See, I've got >another IDE disk on my primary slave IDE controller (1.1 GB). I >installed RedHat Linux on there. Basically, that disk had 3 >Linux partitions: > >120M / /dev/hdb1 >120M swap/dev/hdb5 >~800MB /usr/dev/hdb6 > >Don't ask; the RedHat installer partitioned it this way. >Anyhow, when I do fdisk /dev/rad1, FBSD's fsck only sees 2 >partitions. Partition one is the 120M / partition, which I can >mount OK. But, fdisk claims the 2nd partition is a 920 MB >extended DOS partition. Hmmm... well, it may be that my second >disk needs low-level formatted or something. > >- Donn > > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-current" in the body of the message > > Tom Embt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Quickie question on UDMA/33
At 05:53 AM 4/12/00 -0400, Trevor Johnson wrote: >> Western Digital Caviar hard drives that should support UDMA/33, as should >> the Chipset. >> >> Both boot up, trying UDMA mode, throwing ICRC READ ERROR's then kick back >> down to PIO mode 4. > >> Bios's are set to do auto-chose pio/dma modes. > >There may be a BIOS option that will disable DMA entirely. > >> I've resolved to simply adding in the rc to reset them to pio mode, to get >> it over with (but I still get the errors at boot-up prior to the rc doing >> them). >> >> I simply use 'device ata' etc. forms in the knerel config. > >You might try commenting out this option (if you're using it): > >options ATA_ENABLE_ATAPI_DMA#Enable DMA on ATAPI devices That would apply only to the DVD, not the hard drives of course, but still there is no reason that reasonably modern equipment shouldn't work in UDMA/33 mode. Are the IDE cables new and in good shape? Using each end connector before attaching a device to the middle one... Tom Embt [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Strange rpc.statd and mount_nfs
I have the same problem with 4.0-STABLE, cvsup'ed June 2. I just turned rpc.statd off in /etc/rc.conf. Tom Schottle [EMAIL PROTECTED] Jonathan Hanna wrote: > > I am running a fairly recent current and noticed my swap seemed > a little overused. > > bash-2.02$ uname -a > FreeBSD roller.pangolin-systems.com 5.0-CURRENT FreeBSD 5.0-CURRENT #41: Sun May 14 >11:50:20 PDT 2000 [EMAIL PROTECTED] > stems.com:/home/src/sys/compile/ROLLER i386 > bash-2.02$ uptime > 11:27PM up 3 days, 5:15, 7 users, load averages: 0.21, 0.17, 0.14 > > ps shows: > > 0 212 1 29 2 0 2630360 select IWs ??0:00.00 rpc.statd To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NEWCARD and Xircom (RBEM56G-100)
Hi Tom, No, I have this same card running on a Toshiba Tecra 8100, and it does indeed use the dc driver, and the ethernet part of it does indeed work (I'm running Current, last updated yesterday). The dc driver needs the miibus device configured in the kernel in order to work correctly, and it appears as if you haven't configured your kernel with this device- your dmesg is showing: dc0: port 0x1000-0x107f mem 0x8400-0x84ff,0x84000100-0x8400017f irq 11 at device 0.0 on cardbus0 dc0: Ethernet address: 00:00:00:00:00:00 dc0: MII without any PHY! while you should in fact be seeing something like: dc0: port 0x1000-0x107f mem 0x84002000-0x840020ff,0x84002100-0x8400217f irq 11 at device 0.0 on cardbus0 dc0: Ethernet address: 2e:29:21:02:06:00 miibus0: on dc0 tdkphy0: on miibus0 tdkphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto I haven't been able to get the modem part of this to work since October. Warner had given us some hints on how to get this working early last year, and it actually did work up until the 'sio' code was broken out from isa and put under sys/dev/sio/. This hadn't really been a problem until yesterday, as I had been using an Alcatel usb ADSL modem with the pppoa port to connect to the internet, but yesterday's cvsup (or most likely earlier- before yesterday, I last upgraded on 11/20/01) broke that as well- now I have no way of connecting :-( Warner, do you have any clues on how to get the modem half of this card working again? best regards, tom [EMAIL PROTECTED] Tom Skoglund wrote: > I'll try contacting him as well if I cannot find a solution "soon". > Thanks, anyway! > > -Tom > > > "Greg Smith" <[EMAIL PROTECTED]> wrote: > > >>Tom, >> >>OK, but I am doubtful. >> >>My feeling was that dc is for some old Dec cards and related, not even >>available in pcmcia/cardbus; and that xe was for various Xircom cards >>and related. I think the same driver often supports 16 and 32 bit >>cards. You might want to ask [EMAIL PROTECTED] who seems to try >>single-handedly to keep the xe driver up to date. >> >>Best of luck. >> >>Greg >> >>-Original Message- >> >> >>>This encoded message has been converted to an attachment. >>> >>>Remember that this is a cardbus card, and AFAIK it should use the dc >>>driver. Think I actually tried the xe driver by mistake also, but I >>> >>have >> >>>not really played around with it. >>> >>>-Tom >>> >>>- Original Message - >>>From: "Greg Smith" <[EMAIL PROTECTED]> >>>To: "Tom Skoglund" <[EMAIL PROTECTED]> >>> >>> >>>>Tom, >>>> >>>>I'm a little surprised that card is using the dc driver instead of >>>> >>the >> >>>>xe driver. I thought all the Xircom ..em56 cards used xe. Is that >>>> >>how >> >>>>it was set up in pccard.conf? >>>> >>>>Greg >>>> >>>>-Original Message- >>>> >>>> >>>>>Hi, >>>>>I have been eager to get my Xircom pcmcia nic to work under >>>>> >>FreeBSD, >> >>>>and >>>> >>>>>have been reading up on the mailing list an so on. My system is a >>>>> >>>>Compaq >>>> >>>>>Armada E500 running 20020119-CURRENT. This weekend I gave it a try, >>>>> >>>>with >>>> >>>>>not >>>>>so good results I might add. I made a new kernel (I have tried many >>>>> >>>>this >>>> >>>>>weekend) built on NEWCARD. I have been fooling around with all the >>>>>different >>>>>config files and kernel parameters I can imagine. >>>>> >>>>>Basically I'm trying to get the dc driver working. I have attached >>>>> >>>>some >>>> >>>>>logs >>>>>(dmesg, kldstat, sysctl, pciconf) for you to look at. When the >>>>> >>driver >> >>>>>module >>>>>fails it also screws up my screen by dividing it in 3 and adding >>>>> >>som >> >>>>random >>>> >>>>>"graphics", so I have to reboot to see anything again. This >>>>> >>behaviour >> >>>>is >>>> >>>>>the >>>>>same if I boot with the card or try to insert it runtime. >>>>> >>>>>What I see in the logs makes me belive it doesn't read the >>>>> >>registers >> >>>>right. >>>> >>>>>So before I start hacking the cardbus/if_dc files can anyone see if >>>>> >>>>there >>>> >>>>>is >>>>>something else I might try? >>>>> >>>>> >>>>>-Tom >>>>> > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-mobile" in the body of the message > > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Promise/ATA-Raid making panic in -CURRENT?
Hi! I checked and compiled the recent -CURRENT tree, buildworld and buildkernel goes all fine. When booting it seems to crash on initialization of my Promise controller and get "bad ivar request (4)". I stripped all possible drivers out of the kernelconfig, except for the ata driver, and it still crashes. I then see a couple of pci0: (no driver attached), and when it should come to my Promise, BAM! Anyone can tell me how I can disable the ata-raid/Promise driver to test? Thx /tso __ Do You Yahoo!? Send FREE Valentine eCards with Yahoo! Greetings! http://greetings.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Promise/ATA-Raid making panic in -CURRENT?
> > I checked and compiled the recent -CURRENT tree, > > buildworld and buildkernel goes all fine. > > > > When booting it seems to crash on initialization > of my > > Promise controller and get "bad ivar request (4)". > I > > stripped all possible drivers out of the > kernelconfig, > > except for the ata driver, and it still crashes. I > > then see a couple of pci0: (no driver > > attached), and when it should come to my Promise, > BAM! > > The "bad ivar request (4)" message does *not* come > from the ATA driver, you must have something else > that is ruining your day... Does it boot if you > take out the promise board ? Gonna try this evening. I was first suspecting that it's the txp driver (I got a 3com 3CR990 NIC), but when I disabled most drivers incl txp, it didn't recognize all the cards, but still never managed to get over my Promise. /tso __ Do You Yahoo!? Send FREE Valentine eCards with Yahoo! Greetings! http://greetings.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Promise/ATA-Raid making panic in -CURRENT?
> The "bad ivar request (4)" message does *not* come > from the ATA driver, you must have something else > that is ruining your day... Does it boot if you > take out the promise board ? I was in a hurry yesterday and let the kernel compile w/o the ata driver while being under the shower. Without the ata driver it does boot. Just wanted to let you know. I'll take the Promise out when I got some more time (latest friday evening). /tso __ Do You Yahoo!? Send FREE Valentine eCards with Yahoo! Greetings! http://greetings.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Promise/ATA-Raid making panic in -CURRENT?
> > I was in a hurry yesterday and let the kernel > compile > > w/o the ata driver while being under the shower. > > Without the ata driver it does boot. Just wanted > to > > let you know. I'll take the Promise out when I got > > some more time (latest friday evening). > > Hmm, I need alot more info the, board chipset, what > exact > Promise controller etc etc, and of cause the usual > dmesg Here's the box: Asus CUV4X-D mainboard, VIA 694X, dual-capable 2x P3-933, 768MB PC133 RAM in 3 DIMM(s) Two IBM IC35L 60.1GB disks on first IDE Pioneer DVD-A05SZ on second IDE Two IBM IC35L 60.1GB on Promise Fasttrak TX2 (PDC20268/70) in RAID0 How do I dump the dmesg when it crashs into the debugger? /tso __ Do You Yahoo!? Send FREE Valentine eCards with Yahoo! Greetings! http://greetings.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Promise/ATA-Raid making panic in -CURRENT?
> > Here's the box: > > > > Asus CUV4X-D mainboard, VIA 694X, dual-capable > > 2x P3-933, 768MB PC133 RAM in 3 DIMM(s) > > Two IBM IC35L 60.1GB disks on first IDE > > Pioneer DVD-A05SZ on second IDE > > Two IBM IC35L 60.1GB on Promise Fasttrak TX2 > > (PDC20268/70) in RAID0 > > > > How do I dump the dmesg when it crashs into the > > debugger? > > With a current kernel from before you found it > failed ? No, first time I compiled a -CURRENT. I finally pulled the Promise out and it boots. Since I need it for some Windows apps on the same box I put it back in and commented some lines in ata driver regarding the detection of Promise Fasttrak controllers and it boots now w/o detecting it. The -CURRENT kernel runs fine so far. /tso __ Do You Yahoo!? Send FREE Valentine eCards with Yahoo! Greetings! http://greetings.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Promise/ATA-Raid making panic in -CURRENT?
> > I finally pulled the Promise out and it boots. > Since I > > need it for some Windows apps on the same box I > put it > > back in and commented some lines in ata driver > > regarding the detection of Promise Fasttrak > > controllers and it boots now w/o detecting it. > > This is strange, the error message you got is *not* > from the ATA driver, and putting a TX2 in a system > here work just fine, I'm out of ideas Well, maybe some other system/PCI code has been changed and doesn't work so well with the detection code in ata-raid.c? This would be my first guess, but I am no big programmer and I'm even less aware how it kernel internas work. To be exact, I commented stuff in ata-raid.c, ata-dma.c and ata-pci.c (everything related to device ID 0x4d68105a). And I made ar_probe to return 1 immediately. Like this I can leave the Promise in w/o getting that error. It happens on GENERIC and the configured kernel. PS booting verbose doesn't throw any usable info at all. PS2 my TX2 has BIOS 2.00 build 2 located in PCI slot 5. The mobo chipset is a VIA 694XDP. I hope this info helps. /tso __ Do You Yahoo!? Send FREE Valentine eCards with Yahoo! Greetings! http://greetings.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Promise/ATA-Raid making panic in -CURRENT?
Hi! I checked and compiled the recent -CURRENT tree, buildworld and buildkernel goes all fine. When booting it seems to crash on initialization of my Promise controller and get "bad ivar request (4)". I stripped all possible drivers out of the kernelconfig, except for the ata driver, and it still crashes. I then see a couple of pci0: (no driver attached), and when it should come to my Promise, BAM! Anyone can tell me how I can disable the ata-raid/Promise driver to test? Thx /tso __ Do You Yahoo!? Send FREE Valentine eCards with Yahoo! Greetings! http://greetings.yahoo.com 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: Promise/ATA-Raid making panic in -CURRENT?
> The "bad ivar request (4)" message does *not* come > from the ATA driver, you must have something else > that is ruining your day... Does it boot if you > take out the promise board ? I was in a hurry yesterday and let the kernel compile w/o the ata driver while being under the shower. Without the ata driver it does boot. Just wanted to let you know. I'll take the Promise out when I got some more time (latest friday evening). /tso __ Do You Yahoo!? Send FREE Valentine eCards with Yahoo! Greetings! http://greetings.yahoo.com 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: Promise/ATA-Raid making panic in -CURRENT?
> > I finally pulled the Promise out and it boots. > Since I > > need it for some Windows apps on the same box I > put it > > back in and commented some lines in ata driver > > regarding the detection of Promise Fasttrak > > controllers and it boots now w/o detecting it. > > This is strange, the error message you got is *not* > from the ATA driver, and putting a TX2 in a system > here work just fine, I'm out of ideas Well, maybe some other system/PCI code has been changed and doesn't work so well with the detection code in ata-raid.c? This would be my first guess, but I am no big programmer and I'm even less aware how it kernel internas work. To be exact, I commented stuff in ata-raid.c, ata-dma.c and ata-pci.c (everything related to device ID 0x4d68105a). And I made ar_probe to return 1 immediately. Like this I can leave the Promise in w/o getting that error. It happens on GENERIC and the configured kernel. PS booting verbose doesn't throw any usable info at all. PS2 my TX2 has BIOS 2.00 build 2 located in PCI slot 5. The mobo chipset is a VIA 694XDP. I hope this info helps. /tso __ Do You Yahoo!? Send FREE Valentine eCards with Yahoo! Greetings! http://greetings.yahoo.com 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: Promise/ATA-Raid making panic in -CURRENT?
> > Here's the box: > > > > Asus CUV4X-D mainboard, VIA 694X, dual-capable > > 2x P3-933, 768MB PC133 RAM in 3 DIMM(s) > > Two IBM IC35L 60.1GB disks on first IDE > > Pioneer DVD-A05SZ on second IDE > > Two IBM IC35L 60.1GB on Promise Fasttrak TX2 > > (PDC20268/70) in RAID0 > > > > How do I dump the dmesg when it crashs into the > > debugger? > > With a current kernel from before you found it > failed ? No, first time I compiled a -CURRENT. I finally pulled the Promise out and it boots. Since I need it for some Windows apps on the same box I put it back in and commented some lines in ata driver regarding the detection of Promise Fasttrak controllers and it boots now w/o detecting it. The -CURRENT kernel runs fine so far. /tso __ Do You Yahoo!? Send FREE Valentine eCards with Yahoo! Greetings! http://greetings.yahoo.com 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: more -current testers
Hello, These proposed articles can only help. I've been following this list for a few years, I'm ready to contribute in my own small way :-) tom [EMAIL PROTECTED] Michael Lucas wrote: > I understand that we're getting to that stage where we need more > -current testers. > > We all agree that the optimal thing would be to have hordes of very > sophisticated users who can debug problems on their own and submit > patches to fix all their issues. I would guess that we all also agree > that that's not going to happen. > > It seems that the best we can hope for is to educate some of the > braver users who are ready to take the next step and are willing to > donate some time to us. > > I'm considering doing a series of articles on testing FreeBSD-current, > including: setting up for kernel dumps, what to type at the debugger > prompt after a crash, filing a decent bug report, what to expect from > -current, and so on. I would also make it clear when to not bother > filing a bug report (i.e., "You crashed, but had no WITNESS? Sorry, > enable WITNESS & try again."). This would be (I suspect) three > articles, running about a month and a half. > > The last time I checked, I get 12-15 thousand readers for each > article. One half of one percent uptake would (hopefully) be quite a > few bug reports. > > My question to the community is: is it too early to do this? If I > start now, the articles would probably appear April-May. > > Thanks, > Michael > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
5.0-20010304-CURRENT panics during boot on Sony Vaio
all of the snapshots since the 24th have exhibited this same or very similar behavior. when booting from the kern & mfsroot floppies i get: . . . unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources pccard: card inserted, slot 0 kernel trap 9 with interrupts disabled Fatal trap 9: general protection fault while it kernel mode instruction pointer = 0x8:0xc02e3858 stack pointer = 0x10:0xc78c8f50 frame pointer = 0x10:0xc78c8f64 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= resume, IOPL = 0 current process = 19 (irq9: uhci0) trap number = 9 panic: general protection fault i only get this on my vaio (PCG-XG9); several other pc's i tried these boot floppies on boot and run sysinstall just fine. none of my other test boxes have USB though. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.0-20010304-CURRENT panics during boot on Sony Vaio
John Baldwin wrote: > > On 04-Mar-01 Tom Uffner wrote: > > all of the snapshots since the 24th have exhibited this same or > > very similar behavior. > > Does it happen for snapshots before the 24th? > no, it does not, at least not for the 5.0-20010210-CURRENT snap. it boots from the floppies and once installed, from the disk. oh well, so much for the idea that it would be easier to get past the libc change by installing a snapshot... Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-20010210-CURRENT #0: Sat Feb 10 16:04:54 GMT 2001 [EMAIL PROTECTED]:/usr/src/sys/compile/GENERIC Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 496311413 Hz CPU: Pentium III/Pentium III Xeon/Celeron (496.31-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x681 Stepping = 1 Features=0x383f9ff real memory = 134152192 (131008K bytes) avail memory = 125415424 (122476K bytes) Preloaded elf kernel "kernel" at 0xc0506000. Pentium Pro MTRR support enabled WARNING: Driver mistake: destroy_dev on 154/0 Using $PIR table, 8 entries at 0xc00fdf40 npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xfc90-0xfc9f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xfca0-0xfcbf irq 9 at dev ice 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: at 7.3 (no driver attached) pci0: at 8.0 (no driver attached) pcm0: port 0xfc8c-0xfc8f,0xfcc0-0xfcff mem 0xfedf8000-0x fedf irq 9 at device 9.0 on pci0 pci0: at 10.0 (no driver attached) pcic-pci0: at device 12.0 on pci0 pcic-pci1: at device 12.1 on pci0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 fdc0: 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 pcic0: at port 0x3e0 iomem 0xd on isa0 pcic0: Polling mode pccard0: on pcic0 pccard1: on pcic0 pmtimer0 on isa0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sn0: ioaddr is 0x300 sn0: test1 failed vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources pccard: card inserted, slot 0 ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed ad0: 17301MB [35152/16/63] at ata0-master UDMA33 acd0: DVD-ROM at ata1-master using PIO4 Mounting root from ufs:/dev/ad0s2a WARNING: / was not properly dismounted lp0: IPv6 not supported ed1 at port 0x300-0x31f irq 3 slot 0 on pccard0 ed1: address 00:e0:98:70:10:ee, type Linksys (16 bit) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.0-20010304-CURRENT panics during boot on Sony Vaio
John Baldwin wrote: > On 05-Mar-01 Tom Uffner wrote: > > John Baldwin wrote: > >> On 04-Mar-01 Tom Uffner wrote: > >> > all of the snapshots since the 24th have exhibited this same or > >> > very similar behavior. > >> Does it happen for snapshots before the 24th? > > no, it does not, at least not for the 5.0-20010210-CURRENT snap. > Can you try cvsupping the src/sys tree one day at a time to see what day > the kernel starts breaking for you? ok, now i'm really confused. i built GENERIC kernels for every day from the 2/10 to 2/25 and none of them panic. the snaps for the 24th and 25th both during boot (only on my Vaio, not my other test systems) could something outside the kernel have changed that made a difference? or could it from building with different options? my /etc/make.conf has "COPTFLAGS= -O -pipe -march=i686". i presume that the snaps were built without any optimization, could this make a difference? -- Tom Uffner [EMAIL PROTECTED] Give a man a fish and you feed him for a day; teach him to use the Net and he won't bother you for weeks. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Userbase of -current
Add a data point for me using -current on my laptop in order to take advantage of cardbus support (thanks Warner!). I update about once every two months, and so far my systems has been running flawlessly. All our other FreeBSD systems (~60) are running various incarnations of -stable... regards, tom [EMAIL PROTECTED] Warner Losh wrote: > > In message <[EMAIL PROTECTED]> Vincent Poy >writes: > : Somehow I always thought there were more than 50 people who are > : "really running" current. We do stress test it though and it had > : performed flawlessly over the past 8 years. Question though, does anyone > : happen to know what the largest maxusers variable is that one can define > : in the kernel config file? We have it at 512 but what's the highest > : number people have used reliably? Thanks. > > I've had at least 50 different people talk to me about NEWCARD, which > is only available in current... > > Warner > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message -- Thomas Fischer Sr Manager: Systems & Applications Support Paris &equant - Global Service Operations - Customer Operations Support Tour Mattei - 207, rue de Bercy - 75012 Paris France Tel: +33 1 53 44 08 03[EMAIL PROTECTED] Fax: +33 1 53 44 08 46[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
(no subject)
unsubscribe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Removing USB keyboard after filesystems synced causes panic with destroyed mutex twa(4)?
Hi FreeBSD-current, My name is Tom Couch, I am part of the 3ware driver team recently acquired by LSI. I believe Giovanni's patch, below, is the correct fix for this bug. I am available to maintain the twa driver, now that I am on this list. Let me know how I can help, Tom On Wed, Mar 10, 2010 at 1:56 PM, Giovanni Trematerra < giovanni.tremate...@gmail.com> wrote: > On Sun, Mar 7, 2010 at 11:24 AM, Garrett Cooper > wrote: > > On Sun, Mar 7, 2010 at 2:07 AM, Garrett Cooper > wrote: > >> Hi Alexander and Hans, > >>I recently did the following which generated a panic on a > >> 9-CURRENT kernel compiled on the 26th: > >> > >> 1. Executed reboot > >> 2. Removed keyboard. > >> 3. Some time after `All buffers synced\nUptime: ...' was displayed, > >> the keyboard was registered disconnected. > >> 4. The interrupt was delivered to my twa(4) enabled card and the > >> kernel panicked, like so: > >> > >> ugen2.2: at usbus2 (disconnected) > >> uhub8: at uhub2, port 1, addr 2 (disconnected) > >> ugen2.3: at usbus2 (disconnected) > >> ukbd0: at uhub8, port 3, addr 3 (disconnected) > >> uhid0: at uhub8, port 3, addr 3 (disconnected) > >> panic: mtx_lock_spin() of destroyed mutex @ > /usr/src/sys/dev/twa/tw_cl_intr.c:88 > >> > >> cpuid = 1 > >> KDB: enter: panic > >> [thread pid 12 tid 100025 ] > >> Stopped at kdb_enter+0x3d: movq $0,0x40289c(%rip) > >> db> > >> > >>I wish I could provide you with more details, but unfortunately I > >> the USB bus isn't registering the fact that I'm reattaching the > >> keyboard right now and the box won't reboot automatically :( (didn't > >> set the right sysctl beforehand to panic automatically). I'll try and > >> reproduce the issue again, but I was just wondering whether or not you > >> guys had seen this problem before. > > > >Phew... it's reproducible with that kernel. Here's what I did > > exactly (because my original directions were incorrect): > >1. Hit power button (for S5). > >2. Disconnect keyboard RIGHT as `Uptime: ...' is displayed. > >Kernel panicked on my system again. Now to figure out if it still > > exists with a kernel compiled today, and also how to debug it if it > > still does exist :/... > > Thanks, > > -Garrett > > Hi Garrett, > Could you please try the patch below and report back? > > Thank you > > diff -r cab6489de66d sys/dev/twa/tw_cl_intr.c > --- a/sys/dev/twa/tw_cl_intr.cWed Mar 03 04:51:13 2010 -0500 > +++ b/sys/dev/twa/tw_cl_intr.cWed Mar 10 06:29:05 2010 -0500 > @@ -75,9 +75,12 @@ tw_cl_interrupt(struct tw_cl_ctlr_handle > if (ctlr == NULL) > goto out; > > - /* If we get an interrupt while resetting, it is a shared > -one for another device, so just bail */ > - if (ctlr->state & TW_CLI_CTLR_STATE_RESET_IN_PROGRESS) > + /* > + * If we get an interrupt while resetting or shutting down, > + * it is a shared one for another device, so just bail > + */ > + if (ctlr->state & TW_CLI_CTLR_STATE_RESET_IN_PROGRESS || > + (ctrl->state & TW_CLI_CTLR_STATE_ACTIVE) == 0) > goto out; > > /* > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: HEADSUP: zlib updated [svn commit: r205471 - in head: . lib/libz lib/libz/contrib lib/libz/doc sys/sys]
Michael Butler wrote: This breaks most (if not all) of the QT4-dependent ports for the lack of a definition of "off64_t". it also breaks multimedia/mplayer, graphics/ImageMagick, and print/ghostscript8 & everything that depends on it. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: HEADSUP: zlib updated [svn commit: r205471 - in head: . lib/libz lib/libz/contrib lib/libz/doc sys/sys]
Xin LI wrote:
On Wed, Mar 31, 2010 at 6:56 PM, Tom Uffner wrote:
Michael Butler wrote:
This breaks most (if not all) of the QT4-dependent ports for the lack of
a definition of "off64_t".
it also breaks multimedia/mplayer, graphics/ImageMagick, and
print/ghostscript8 & everything that depends on it.
Just because they used to compile DOES NOT mean they were right. It's
NOT right to define _LARGEFILE64_SOURCE on FreeBSD, see:
http://www.delorie.com/gnu/docs/glibc/libc_13.html
i realize this. i was just adding to the list of ports that no longer
build after this change. ghostscript is kind of important for print
support.
i doubt this is "right" either, but it is a quick & dirty way to
make mplayer compile again:
--- configure.orig 2010-04-01 15:49:37.0 -0400
+++ configure 2010-04-01 15:50:50.0 -0400
@@ -5337,7 +5337,7 @@
#include
int main(void) { return 0; }
EOF
-cc_check -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE \
+cc_check -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 \
-ldvdread $_ld_dl && _dvdread=yes && _res_comment="external"
fi
fi
@@ -7412,8 +7412,6 @@
if test "$_largefiles" = yes || freebsd ; then
CFLAGS="$CFLAGS -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64"
if test "$_dvdread" = yes || test "$_libdvdcss_internal" = yes ; then
-# dvdread support requires this (for off64_t)
-CFLAGS="$CFLAGS -D_LARGEFILE64_SOURCE"
cygwin && CFLAGS="$CFLAGS -DSYS_CYGWIN"
fi
fi
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: When will we can use ZFS v24?
On Fri, Apr 9, 2010 at 6:44 PM, Dan Nelson wrote: > In the last episode (Apr 08), Garrett Cooper said: >> On Thu, Apr 8, 2010 at 2:30 PM, Chuck Swiger wrote: >> > On Apr 8, 2010, at 2:18 PM, krad wrote: >> > [ ... ] >> >>> is that even possible with CDDL? >> >> >> >> im not a lawyer but it wouldn't surprise me >> > >> > I'm not a lawyer either, but I was active in reviewing and suggesting >> > changes to CDDL submission for OSI approval back in 2004. >> > >> > A copyright owner always has the ability to relicense their code under >> > other terms, but existing code is guaranteed to be available, >> > redistributable to others, etc under the terms of the current version of >> > CDDL; in particular see: >> > >> > If Oracle chooses, they might make future changes to the ZFS source code >> > under different or more restrictive licensing terms, but what's >> > available now is always going to be available. >> >> The same of basic principle applies to BDB; originally it was BSD licensed >> in 1.x under FreeBSD, then GPLed in 2.x+ (IIRC), then left to pasture in >> 4.x after Oracle acquired Sleepycat DB. MySQL is GPLv2 today... who >> knows what it might be tomorrow... > > BDB was never GPL'ed; it was and still is BSD-licensed. > > http://www.oracle.com/technology/software/products/berkeley-db/htdocs/oslicense.html > IANAL, but that is not a BSD license. It is the Sleepycat license, which is compatible with GPL. The giveaway is in section 3: * 3. Redistributions in any form must be accompanied by information on *how to obtain complete source code for the DB software and any *accompanying software that uses the DB software. The '.. any accompanying software' clause makes it quite like the GPL. Cheers Tom ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ISO9660 4GB directory structures boundary limit and growisofs
On Mon, Apr 19, 2010 at 1:48 PM, Paul B Mahol wrote: > On 4/17/10, Paul B Mahol wrote: >> On Sat, Apr 17, 2010 at 4:31 PM, Tim Kientzle wrote: >>> Paul B Mahol wrote: >>>> >>>> It is apparently not possible to make use of -use-the-force-luke=4gms >>>> on FreeBSD when appending new session after 4GB. Mounted disk >>>> afterwards show nothing. >>>> >>>> Should we allow it like linux does? >>> >>> Are you claiming there is a problem when FreeBSD reads such >>> images or a problem with creating such images? What >>> programs are you using? >> >> I burn flac files in multiple sessions, each session have separate >> directory, on DVD+R DL MKM/003 >> After I used 4gms switch mounted fs shows nothing. (but there is >5GB of >> data) >> >> According to growisofs source BD (bluray) dont need this switch at all ... >> >>> This sounds like a pretty unsurprising 32-bit truncation >>> bug: the filesystem structures in ISO9660 are all sector >>> numbers so 8TB should be the natural limit (4G sectors >>> times 2k bytes/sector). >> >> I did not tested this on FreeBSD amd64 yet. > > Update: Linux shows all sessions and Windows 7 shows only first one. >From the source code of groisofs.c: * - DVD+R Double Layer support; * - -use-the-force-luke=4gms to allow ISO9660 directory structures * to cross 4GB boundary, the option is effective only with DVD+R DL * and for data to be accessible under Linux isofs a kernel patch is * required; So I'm guessing it does something non standard, particularly if windows also refuses to see the data. Cheers Tom ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: kern+world / ports make options
On Sat, Apr 24, 2010 at 5:42 PM, Pegasus Mc Cleaft wrote: > Hello Hackers & Current, > > I was wondering it if is possible, or if it can be done so a separate > set > of CC, CXX, etc can be specified for building the world and kernel > independently of a ports build? > > Right now, I use the base GCC to compile the world and kernel, and > GCC44 > for most of the other ports (when it complies cleanly). But I have to keep > editing the /etc/make.conf file to switch between the two. > > It may already be implemented, but it would be nice if there was > something defined while the kernel and/or world is being built to that a > nested block of ifdefs can select which env variables to be set. > > Peg man src.conf Cheers Tom ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: kmem_map too small: 3832475648 total allocated
On Thu, Apr 29, 2010 at 3:53 PM, Ollivier Robert wrote: > According to James R. Van Artsdalen: >> system is a Core i7 975 (3.33 GHz x 4 cores 3x threads per core) with 12 >> GB of RAM, a 2x2TB ZFS boot pool and a second (idle) pool of 16x2TB. > >> panic: kmem_malloc(131072): kmem_map too small: 3832475648 total allocated > > Apart from the fact that you must at least set vm.kmem_size to something like > 2x your RAM, one rule of thumb I've seen discussed for ZFS is that you will > need approximatively 1 GB of RAM per TB of data so you may be a bit short > here to get optimal perfs. > Citation needed? I have a file server running amd64 8-STABLE with 4GB of RAM, 6 x 1.5 TB drives in raidz, and have never had any problems with memory usage. Are you saying that after my next update, adding another 6 x 1.5 TB drives, it will start being flaky and/or panicing with kmem_map too small errors? Cheers Tom ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Make world dies on 3.0 STABLE
On Thu, Jan 21, 1999 at 07:41:20AM -0400, Victor Salaman wrote: > I just csvup'ed the sources...(I had the sources from January 12's > snapshot). While trying to do a "make world", eventually I get this message. > > c++ -pg -I/usr/obj/usr/src/tmp/usr/include/g++ -nostdinc -O -pipe > -I/usr/src/gnu [snipped] > Stop. > *** Error code 1 > > Stop. > > > > > and then dies! > What's your migration path? I went from 3.0-current to 3.0-release and then to 3.0-stable successfully. I have noticed that 'ppp -auto -alias demand' no longer works for me, however. Anybody else experiencing this gremlin? -- Tom To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
4GB of RAM?!
Hi all, Has anyone yet tried running -current on a Xeon with 4GB RAM installed? We're about to place an order for a Quad Xeon and would like to have 4GB of RAM installed if it is feasible and/or possible to make this work with -current. Thanks for the help, Tom To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: ports
I am attaching my description of a similar problem/solution as it directly addresses the problem and may be of interest to many people. See below... > (Send messages like this to -ports next time, please) > > * I've noticed that as I'm constantly syncing my /usr/ports directory and > * upgrading programs, the old packages stay there. If I pkg_delete them and > * there's an unchanged file that exists in both the update and the original > then > * tat gets deleted too. Any way of cleanly removing old packages? > Incidentally > > pkg_delete the old one before adding the new one? ;) > > * are the ports trees for all the FreeBSD releases the same one? I mean if > I'm > * running 2.2.x do I still get all the latest ports? > > ports-current (the tree you get if you cvsup ports now) only supports > 3.1-stable and 4.0-current. If you're running 2.2.x, you are on your > own. > > Satoshi Here it comes... > On Mon, 22 Feb 1999, Tom Torrance at home wrote: > > > This port fails when applying patches for FreeBSD. > > If you're monstrously annoyed at it merely being broken, then I guess I > can understand what you wrote ... but if you wanted help, you have to > give enough info, so that someone else can figure out why it broke for > you. > > How about including the actual error listing, the date on the perl5 > port's Makefile (so we can tell the age of it) the date on your > /usr/share/mk/bsd.port.mk file, and the FreeBSD version you're running. > At the time I was running a cvsup-15.4 client, as far as I remember (since updated to cvsup-16.0) under 2.2-stable. The system software was updated last as of Feb 13, 1999. The ports tree was as up-to-date as cvsup could make it. I got the info to fix it from John Polstra a year or two ago, in reference to a source tree problem I was having at that time, but had since forgotten about! (blush) The problem was old patch files that were not deleted by cvsup, which will not delete anything that it did not either write, or verify was there *and valid, expressly* on an update. It otherwise leaves trash lying around. The first thing one has to do with cvsup is verify/register the files one has by running it against the exact same release as the files one has before running a cvsup update to get the later files. Otherwise, as I understand it, any files deleted from the master tree between the time your version of the ports tree was created (usually when the cdrom distribution is created) and the first time you do a cvsup run to update it, will NEVER be detected and deleted by cvsup. An example, if you are running current or RELENG_3 and happen to have inserted the required files or symlinks to activate the softupdates code, cvsup will not delete them. Verification/registration is AFAIK not possible with ports, as there are not any separate cvs ports releases, as there is with the source tree. I got around the problem by: 1) deleting /usr/sup/ports* 2) deleting /usr/ports/* 3) cvsuping the entire ports tree. (ouch) This got rid of the invalid patch-aa file for perl5 as well as a number of other invalid files that were in my tree, which was quite old. All my ports are now running fine, and will continue to do so (hopefully). Anyone that wants to cvsup the ports tree on a system would be well advised to "rm /usr/ports/*" before the *first* time they run cvsup. This is particularly important if they have jost installed an old release. The first run will then automatically be a verification/registration run. Thanks for your reply. It is much appreciated - I really did not give any info, and I was frustrated. Forgive me. Cheers, Tom To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: fxp0 device timeout on 5.0-RELEASE
On Fri, 31 Jan 2003 12:14:29 +0300 "Sergey A. Osokin" <[EMAIL PROTECTED]> wrote: > On Fri, Jan 31, 2003 at 09:32:07AM +0100, Georg-W. Koltermann wrote: > > Am Do, 2003-01-30 um 12.41 schrieb Sergey A. Osokin: > > > > > > 3) Put hw.pci.allow_unsupported_io_range="1" into your > > > /boot/loader.conf.local > > > > Thanks, that did the trick. > > > > Could we, maybe, add a little note about this to the release notes > > or errata? Or better yet, how about a big fat warning message if > > the kernel probes a device at an unsupported address while > > hw.pci.allow_unsupported_io_range==0? > > Yes, I send list of questions/answers about this problem to doc@. > Still no answer from. Anyway list avaliable from my home page: > http://ozz.pp.ru/eag.txt > > -- > > Rgdz,/"\ ASCII RIBBON CAMPAIGN > Sergey Osokin aka oZZ, \ /AGAINST HTML MAIL > http://ozz.pp.ru/ X AND NEWS > / \ I was actually adding something when this email came into my mailbox. Sorry for not picking up on this before. -- Tom Rhodes To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ACPI thermal panics ThinkPad 600X
On Sat, 15 Feb 2003 04:49:39 +0200 Ruslan Ermilov <[EMAIL PROTECTED]> wrote: > ACPI thermal panics my ThinkPad 600X, is anyone > interested in a crash dump analysis? > > ACPI gives me hell on my IBM Thinkpad A31, also. Yet since it does not crash anything I just leave it be waiting for the day when the ACPI hackers have time to fix it :) -- Tom Rhodes To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/share/man/man4 Makefile
On Fri, 21 Feb 2003 14:01:32 +0200 Ruslan Ermilov <[EMAIL PROTECTED]> wrote: > > But my personal opinion on this change is that it is unnecessary. There is a right way, and a wrong way. To be honest, the `right' way here is alot of extra work, and I don't think that most users will really care about listing them. > The "if_*" convention on calling network interface modules is an > internal implementation detail, and only to allow ifconfig(8) to > automatically load driver modules. > > Any other opinions? See above :) -- Tom Rhodes To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/share/man/man4 Makefile
On Sat, 22 Feb 2003 17:24:48 -0700 (MST) "M. Warner Losh" <[EMAIL PROTECTED]> wrote: > In message: > <[EMAIL PROTECTED]> > "James E. Flemer" <[EMAIL PROTECTED]> writes: > : There are some non-if_* modules in there now that seem to > : be only documented in /usr/src, exca is a good example. > > exca is there just for the pleasure of cbb (and soon pcic)... No one > would load it on their own. > > Warner > And eventually that fact will be documented. -- Tom Rhodes To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Gnome2 terminal will not work right
People have been saying that 5.0-CURRENT problems belong here. I don't know if this is Gnome2 or Xfree86... I noticed tonight that the Gnome2 desktop terminal stopped working. When I open a terminal window, I do not get a command prompt. I have a flashing solid block cursor in the top left corner of the window. I tried various key combinations and nothing seems to get its attention. If I file/close or hit the "X" in the top right corner, I get kicked out to the command prompt, where I entered startx, or to the GDM2 signon screen. I'm reading this as an X server crash. I'm seeing some dumps for "Interfearance" but I do not think that is related. Nothing else appears to be broken at this point. The X logs are inconclusive. However, I'll include one that hints at a failure. "Fatal server error: xf86OpenConsole: VT_SETMODE VT_PROCESS failed" I've had this happen to root and to my non uid0 personal account. Any ideas folks? XFree86 Version 4.2.1 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 3 September 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: FreeBSD 5.0-CURRENT i386 [ELF] Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/XFree86.1.log", Time: Fri Mar 7 17:49:40 2003 (==) Using config file: "/etc/X11/XF86Config" (==) ServerLayout "XFree86 Configured" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "Monitor0" (**) | |-->Device "Card0" (**) |-->Input Device "Mouse0" (**) |-->Input Device "Keyboard0" (==) Keyboard: CustomKeycode disabled (**) FontPath set to "/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/" (**) RgbPath set to "/usr/X11R6/lib/X11/rgb" (**) ModulePath set to "/usr/X11R6/lib/modules" (--) Using syscons driver with X support (version 2.0) (++) using VT number 9 Fatal server error: xf86OpenConsole: VT_SETMODE VT_PROCESS failed When reporting a problem related to a server crash, please send the full server output, not just the last messages. This can be found in the log file "/var/log/XFree86.1.log". Please report problems to [EMAIL PROTECTED]
Re: Gnome2 terminal will not work right
Joe Marcus Clarke wrote: On Sat, 2003-03-08 at 00:15, Tom Parquette wrote: People have been saying that 5.0-CURRENT problems belong here. I don't know if this is Gnome2 or Xfree86... Both work fine for me in -CURRENT. I noticed tonight that the Gnome2 desktop terminal stopped working. What changed between the last known working date and tonight? Joe, Nothing that I know of. I did a make buildworld/buildkernel on this machine that was NFS mounted on another but I have not installed it on this machine yet. I was fighting with portupgrade to get the database consistant but I do not believe it went into Gnome-land. The problem simply appeared after I had left the Gnome2 session open overnight and picked it up sometime the next day. The X logs are inconclusive. However, I'll include one that hints at a failure. "Fatal server error: xf86OpenConsole: VT_SETMODE VT_PROCESS failed" I've had this happen to root and to my non uid0 personal account. Any ideas folks? What do you have in your ~/.xinitrc? Can you also send the output of pkg_info? Also, have you tried removing ~/.gnome2/session, and see if that helps? Joe There is no .xinitrc for this user id. I use GDM2 and that path brought up Gnome2. I noticed it but, I never questioned it beyond that. I have not tried removing .gnome2/session. I can try that. I'll attach pkg_info to the end of this reply. I do not know what the importance of this is but I keep seeing dumps for something called Interfearance. I do not know what it is or what it does. I also have not gotten around to researching what it is. I mention it here FWIW. __ XFree86 Version 4.2.1 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 3 September 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: FreeBSD 5.0-CURRENT i386 [ELF] Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/XFree86.1.log", Time: Fri Mar 7 17:49:40 2003 (==) Using config file: "/etc/X11/XF86Config" (==) ServerLayout "XFree86 Configured" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "Monitor0" (**) | |-->Device "Card0" (**) |-->Input Device "Mouse0" (**) |-->Input Device "Keyboard0" (==) Keyboard: CustomKeycode disabled (**) FontPath set to "/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/" (**) RgbPath set to "/usr/X11R6/lib/X11/rgb" (**) ModulePath set to "/usr/X11R6/lib/modules" (--) Using syscons driver with X support (version 2.0) (++) using VT number 9 Fatal server error: xf86OpenConsole: VT_SETMODE VT_PROCESS failed When reporting a problem related to a server crash, please send the full server output, not just the last messages. This can be found in the log file "/var/log/XFree86.1.log". Please report problems to [EMAIL PROTECTED] 44bsd-csh-20001106 The traditional 4.4BSD /bin/csh C-shell 9e-1.0 Explode Plan9 archives AbiWord2-1.1.3 An open-source, cross-platform WYSIWYG word processor Hermes-1.3.2Fast pixel formats conversion library ImageMagick-5.5.5 Image processing tools (interactive optional--misc/display Mesa-3.4.2_2A graphics library similar to SGI's OpenGL ORBit-0.5.17High-performance CORBA ORB with support for the C language ORBit2-2.6.0High-performance CORBA ORB with support for the C language OpenSSH-askpass-1.2.2.2001.02.24 Graphical password applet for entering SSH passphrase XFree86-4.2.0_1,1 X11/XFree86 core distribution (complete, using mini/meta-po XFree86-FontServer-4.2.0_1 XFree86-4 Font Server XFree86-Server-4.2.1_7 XFree86-4 X server and related programs XFree86-VirtualFramebufferServer-4.2.1_1 XFree86-4 Virtual Framebuffer Server XFree86-clients-4.2.1_3 XFree86-4 Client environments XFree86-documents-4.2.0 XFree86-4 Document Files XFree86-font100dpi-4.2.0 XFree86-4 bitmap 100 dpi fonts XFree86-font75dpi-4.2.0 XFree86-4 bitmap 75 dpi fonts XFree86-fontCyrillic-4.2.0_4 XFree86-4 Cyrillic Fonts XFree86-fontDefaultBitmaps-4.2.0 XFree86-4 default bitmap fonts XFree86-fontEncodings-4.2.0 XFree86-4 font encoding files XFree86-fontScalable-4.2.0 XFree86-4 Scalable font files XFree86-libraries-4.2.1_7 XFree86-4 include/(shared) library kit Xaw3d-1.5 A 3-D Athena Widget set that looks like Motif Xft-2.1_3 A client-sided font API for X applications aalib-1.4.r5
Re: AR9132 CPU and AR9100 wireless support
On 09/14/2010 04:08 PM, Outback Dingo wrote: Ive got some Ubiquiti mips devices id love to get FreeBSD on permanently and a Netgear WNDR370, if only we could boot FreeBSD out of redboot and flash it to them it would seriously ROCK, Booting FreeBSD out of redboot should be no problem. I have used the redboot loader on a Intel NAS to load a FreeBSD kernel and boot successfully, this was an arm core rather than mips however. If you have a working redboot you can also use the redboot shell to flash your kernel (with embedded MFS image) into the SPI part and then rewrite the load script to boot that. The debian-installer armel handbook had some useful docs in it for the platform I was working on, as well as the official redboot site. Tom On Tue, Sep 14, 2010 at 4:24 PM, Stefan Bethke wrote: Am 14.09.2010 um 11:35 schrieb Adrian Chadd: Hi everyone, I've just pushed the initial support for the AR9100 wireless MAC into my git repository. This is for the WMAC on the AR9132 SoC. I've tested it in 11bg hostap mode on an AP83 derived box - the TP-Link TL-WR1043ND. The source tree has support for the CPU, ethernet (but not the switch PHY; it's enough to get data across it!); flash and the AR9100 WMAC. I've only tested "open" hostap mode on 11bg on a fixed channel. The GIT repo is at: http://www.gitorious.org/~adrianchadd/freebsd/adrianchadd-freebsd ; it's the "work/atheros" branch. You'll need to open the unit up, solder on some pins to get to the serial port and acquire a TTL -> RS232 level converter. There's pictures and howto on the OpenWRT wiki: http://wiki.openwrt.org/toh/tp-link/tl-wr1043nd That sounds really nice! Is there some guide on how to prepare an image? I'm quite familiar with OpenWrt (patching and building) and have a number of routers (WRT-160N, WR941NL, 500gP) with serial adapters attached, but from the messages on the mips list, it felt the bootstrapping process might be a bit dauting... Stefan -- Stefan BethkeFon +49 151 14070811 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: buildworld + ccache trouble
On 09/15/2010 09:53 AM, Maxim Khitrov wrote: > On Wed, Sep 15, 2010 at 8:44 AM, Dmitry Krivenok > wrote: > >> Hello All! >> I recently updated to r212634 and tried to build CURRENT tree with ccache. >> >> However, I got build error: >> >> >> >> Stop in /usr/src/lib/csu/i386-elf. >> *** Error code 1 >> >> Is it a know issue? >> Any solutions? >> > If I remember correctly, this happens when you try to build 32-bit > library set on amd64 (you do not have WITHOUT_LIB32 set in > /etc/src.conf). > > My solution was to disable 32-bit support by setting that option. If > you're still using ccache version 2.4, try upgrading to 3.0.1, though > I'm not sure if this problem has been fix. The only other alternative > that I know of is to not use ccache to buildworld on amd64. > In the past I have used the solution outlined here: http://www.tomjudge.com/index.php/FreeBSD/Creating_a_%28i386/ia32%29_build_cluster_using_amd64_and_i386_hosts This used to (in the 6.2 days) allow us to build i386 objects on amd64 hosts. It may work for you. Tom -- TJU13-ARIN ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
USB 1.1 devs not working on ASUS K8VSE (x86) MB
I have a fairly recent Current system running on an ASUS K8V SE Deluxe MB. It was a dual boot amd64/x86 system (until a few days ago when the drive w/ the amd64 partitions unexpectedly failed after only a week of use) When running it as x86, USB 1.1 devices are not recognized by FreeBSD. They worked fine on the amd64 kernel built from the same code. both ohci and uhci are in the kernel even though they don't show up in dmesg. the devices in question (currently a 1.1 hub and a mouse) are both seen and activated by the BIOS but turned off once FreeBSD takes over. I had the same problem with GENERIC kernels from the 9.0-current-201011 snapshot, so it is not my kernel config. the mouse also works fine on either x86 or amd64 when plugged into a USB 2.0 hub or a PS2 adapter. and both these devices worked w/ the x86 kernel on the previous incarnation of this system with an ASUS A7N8X MB (NVIDIA chipset) so i suspect that the problem may be in the initialization code for the Via chipset. thanks in advance for any help, tom FreeBSD xiombarg.uffner.com 9.0-CURRENT FreeBSD 9.0-CURRENT #292: Wed Dec 8 13:10:15 EST 2010 root@:/usr/obj/usr/src/sys/XIOMBARG i386 Copyright (c) 1992-2010 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-CURRENT #292: Wed Dec 8 13:10:15 EST 2010 root@:/usr/obj/usr/src/sys/XIOMBARG i386 CPU: AMD Athlon(tm) 64 Processor 3200+ (2202.87-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0xfc0 Family = f Model = c Stepping = 0 Features=0x78bfbff AMD Features=0xe0500800 real memory = 2147483648 (2048 MB) avail memory = 2094309376 (1997 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: ioapic0: Changing APIC ID to 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 7fef (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: on hostb0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0xa000-0xa0ff mem 0xe000-0xefff,0xfce0-0xfce0 irq 16 at device 0.0 on pci1 vgapci1: mem 0xd000-0xdfff,0xfcc0-0xfcc0 at device 0.1 on pci1 atapci0: port 0xe800-0xe87f,0xe400-0xe4ff mem 0xfda0-0xfda00fff,0xfd90-0xfd91 irq 16 at device 9.0 on pci0 ata2: on atapci0 ata3: on atapci0 ata4: on atapci0 skc0: port 0xe000-0xe0ff mem 0xfdc0-0xfdc03fff irq 17 at device 10.0 on pci0 skc0: Marvell Yukon Lite Gigabit Ethernet rev. A3(0x7) sk0: on skc0 sk0: Ethernet address: 00:11:2f:38:7b:87 miibus0: on sk0 e1000phy0: PHY 0 on miibus0 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto re0: port 0xd800-0xd8ff mem 0xfd70-0xfd7000ff irq 17 at device 12.0 on pci0 re0: Chip rev. 0x1000 re0: MAC rev. 0x miibus1: on re0 rgephy0: PHY 1 on miibus1 rgephy0: 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow re0: Ethernet address: 00:14:d1:14:33:e6 pcm0: port 0xd400-0xd4ff irq 19 at device 14.0 on pci0 atapci1: port 0xd000-0xd007,0xc800-0xc803,0xc400-0xc407,0xc000-0xc003,0xb800-0xb80f,0xb400-0xb4ff irq 20 at device 15.0 on pci0 ata5: on atapci1 ata6: on atapci1 atapci2: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 15.1 on pci0 ata0: on atapci2 ata1: on atapci2 pci0: at device 16.0 (no driver attached) pci0: at device 16.1 (no driver attached) pci0: at device 16.2 (no driver attached) pci0: at device 16.3 (no driver attached) ehci0: mem 0xfd50-0xfd5000ff irq 21 at device 16.4 on pci0 usbus0: EHCI version 1.0 usbus0: on ehci0 isab0: at device 17.0 on pci0 isa0: on isab0 acpi_button0: on acpi0 acpi_button1: on acpi0 attimer0: port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: port 0x70-0x71 irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fd0: <1440-KB 3.5" drive> on fdc0 drive 0 uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 pmtimer0 on isa0 orm0: at iomem 0xc-0xc
Re: USB 1.1 devs not working on ASUS K8VSE (x86) MB
John Baldwin wrote: pci0: at device 16.0 (no driver attached) pci0: at device 16.1 (no driver attached) pci0: at device 16.2 (no driver attached) pci0: at device 16.3 (no driver attached) Can you get pciconf -lv output for these four devices? no...@pci0:0:16:0: class=0x0c0300 card=0x80ed1043 chip=0x30381106 rev=0x81 hdr=0x00 vendor = 'VIA Technologies, Inc.' device = 'VT82x UHCI USB 1.1 Controller (All VIA Chipsets)' class = serial bus subclass = USB no...@pci0:0:16:1: class=0x0c0300 card=0x80ed1043 chip=0x30381106 rev=0x81 hdr=0x00 vendor = 'VIA Technologies, Inc.' device = 'VT82x UHCI USB 1.1 Controller (All VIA Chipsets)' class = serial bus subclass = USB no...@pci0:0:16:2: class=0x0c0300 card=0x80ed1043 chip=0x30381106 rev=0x81 hdr=0x00 vendor = 'VIA Technologies, Inc.' device = 'VT82x UHCI USB 1.1 Controller (All VIA Chipsets)' class = serial bus subclass = USB no...@pci0:0:16:3: class=0x0c0300 card=0x80ed1043 chip=0x30381106 rev=0x81 hdr=0x00 vendor = 'VIA Technologies, Inc.' device = 'VT82x UHCI USB 1.1 Controller (All VIA Chipsets)' class = serial bus subclass = USB ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: USB 1.1 devs not working on ASUS K8VSE (x86) MB
John Baldwin wrote: On Friday, December 10, 2010 8:13:01 pm Tom Uffner wrote: no...@pci0:0:16:0: class=0x0c0300 card=0x80ed1043 chip=0x30381106 rev=0x81 hdr=0x00 vendor = 'VIA Technologies, Inc.' device = 'VT82x UHCI USB 1.1 Controller (All VIA Chipsets)' class = serial bus subclass = USB Ok, can you show the output of 'pciconf -rb pci0:0:16:0 0x9'? [xiombarg#:~:1] pciconf -rb pci0:0:16:0 0x9 00 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: USB 1.1 devs not working on ASUS K8VSE (x86) MB
according to kldstat -v, both "uhci/usbus" & "pci/uhci" were present in my kernel but one or both of them was silently failing. apparently something in my sources was corrupt because deleting all of the USB related code from my CVS root, re-csuping it, and building a fresh kernel solved the problem. thanks for the help. tom ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Freezing PC with start of X with ATI Rage
On Sunday 19 December 2010 09:49:21 Vladislav Movchan wrote: > On Sat, Dec 18, 2010 at 10:34 PM, Vladislav Movchan > > wrote: > > On Sat, Dec 18, 2010 at 11:14 AM, Christian Gusenbauer wrote: > >> Hi! > >> > >> With commit r216333 to pmap.c my PC (i386 32 bit) freezes within a few > >> seconds when X (with nvidia-driver 256.53) starts. I already recompiled > >> and reinstalled the nvidia driver, but this didn't change anything. I > >> also tried the latest nvidia-driver 260.19.29 but without luck, too > >> :-(. > >> > >> By chance I saw a panic message "vm_page_unwire: page 0x... wire count > >> is zero", but no crash dump was generated. > >> > >> Any clues? > >> > >> Thanks, > >> Christian. > >> ___ > >> freebsd-current@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-current > >> To unsubscribe, send any mail to > >> "freebsd-current-unsubscr...@freebsd.org" > > > > I can only add "me too" - I am experiencing the same problem with two > > i386 machines. Both PCs work fine on revision 216332 and hanging on > > revision 216333 or later. > > I've tried to use different nvidia-driver versions (195.36.24, 256.53 > > and 260.19.29), tried disabling glx/dri xorg extensions but nothing > > changed. Freeze happening before the moment when "nvidia logo" > > appears. > > Unfortunately I was never able to see panic message or obtain crash dump. > > > > If anybody have ideas I can help with testing. > > > > First machine: > > pciconf: > > vgap...@pci0:1:0:0: class=0x03 card=0x04421028 chip=0x0a2910de > > rev=0xa2 hdr=0x00 > >vendor = 'NVIDIA Corporation' > >class = display > >subclass = VGA > > > > Xorg log: > > (--) PCI:*(0:1:0:0) 10de:0a29:1028:0442 nVidia Corporation GT216 > > [GeForce GT 330M] rev 162, Mem @ 0xfa00/16777216, > > 0xc000/268435456, 0xd000/33554432, I/O @ 0xe000/128, BIOS > > @ 0x/65536 > > > > Second one: > > pciconf: > > vgap...@pci0:1:0:0: class=0x03 card=0x34681458 chip=0x061110de > > rev=0xa2 hdr=0x00 > >vendor = 'NVIDIA Corporation' > >device = 'NVIDIA GeForce 8800 GT (G92)' > >class = display > >subclass = VGA > > > > Xorg log: > > (--) PCI:*(0:1:0:0) 10de:0611:1458:3468 nVidia Corporation G92 > > [GeForce 8800 GT] rev 162, Mem @ 0xf600/16777216, > > 0xe000/268435456, 0xf400/33554432, I/O @ 0xb000/128, BIOS > > @ 0x/65536 > > > > -- > > Have a nice(1) day, > > Vladislav Movchan > > Update to r216555 fixed this problem for me. I have similar problems on my old Pentium-II with an ATI Rage, but the actual current still freezes. Stable is fine. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Mozilla V1.3.1 crashing on FreeBSD 5.1-C (older cvsup level)
Periodically, Mozilla V1.3.1 will appear to crash on some web sites. I finally got the following messages out of it. It's not much but I was hoping someone might have an idea. This was from an attempt to point at www.historychannel.com. TIA $ export DISPLAY=Stargate.Tom.Parquette.name:0 $ mozilla No running window found. /dev/dsp: No such file or directory open dsp: No such file or directory Gdk-ERROR **: BadAccess (attempt to access private resource denied) serial 26 error_code 10 request_code 147 minor_code 1 $ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bge & vlan stranges
On Sat, 2 Aug 2003, Terry Lambert wrote: ... > I suppose you want to do this because you are trunking a channel > that goes to a border device, and for some reason you have disabled > receipt of all ICMP, instead of only abusable ICMP, and thus you > have broken end-to-end path MTU discovery. > > It would be best if you were to simply fix your ICMP. Probably wouldn't be affective anyhow. L2 switches assume that they can encapsulate 1500 byte ethernet frames into 802.1q properly. It is part of the 802.1q standard. If the NIC can't understand the frame because it is now 1504 bytes, it will be a layer 2 discard. There will be no ICMP message sent in this case. You could argue that the switch should also be configured with a 1456 byte MTU to allow for the addition of the 802.1q encapsulation. But a L2 switch is not going to send a L3 message like a ICMP "unable to fragment" fragment. So MTU detection buys you nothing. The fact of the matter is, if you use 802.1q encapsulation, the total frame size can be 1504. That is the standard. > -- Terry Tom ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Mozilla V1.3.1 crashing on FreeBSD 5.1-C (older cvsup level)
I deinstalled and reinstalled gtk12. That appears to have fixed this problem. Joe Marcus Clarke wrote: (mozilla-bin:62160): Gtk-WARNING **: A floating object was finalized. This means that someone called g_object_unref() on an object that had only a floating reference; the initial floating reference is not owned by anyone and must be removed with gtk_object_sink() after a normal reference is obtained with g_object_ref(). $ Could be a problem with your gtk12 port. You might try rebuilding it. I removed flashplugin-mozilla and installed flashpluginwrapper. The screen painted but when I put the mouse pointer in the flash window, it indicates the movie was not loaded. However, I'm not getting error messages/crashes, per se. I would remove the flashplugin-mozilla-0.4.10_2 package, and install www/flashpluginwrapper instead. I've picked up a different problem... When I try to click on links off of the historychannel web site (either javascript or to another html page) I get the following: mozilla-bin in free(): error: page is already free I cannot identify any pattern to this message but once it is issued, I have to control-C out of mozilla-gtk2 in the window I started it from. I have not found any other way to get out of the problem. Put another way, when I get this error, Mozilla is dead but control-C will get rid of the hung application. Cheers... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Mozilla V1.3.1 crashing on FreeBSD 5.1-C (older cvsup level)
Joe, I cvsuped my ports tree and portupgraded mozilla and mozilla-gtk2 (I never noticed there were two flavors installed until now.) As a quick sidenote, the descriptions of the two ports are functionally identical. I noticed minor toolbar differences and some font differences and in the tests that I'm going to describe mozilla-gtk2 appears more resilient. Is one recommended over the other? Getting back to business... Using Mozilla-gtk2 (v1.4): A window appears with "Default Plugin" in the title bar. The exact text is: This page contains information of a type (application/x-shockwave-flash) that can only be viewed with the appropriate Plug-in. Click OK to download Plugin." When I close out of Mozilla-gtk2 the following appears in the terminal window: $ mozilla-gtk2 No running window found. /dev/dsp: No such file or directory (mozilla-bin:62160): Gtk-WARNING **: A floating object was finalized. This means that someone called g_object_unref() on an object that had only a floating reference; the initial floating reference is not owned by anyone and must be removed with gtk_object_sink() after a normal reference is obtained with g_object_ref(). $ I don't know if this is something I have to worry about. The plus side is, Mozilla-gtk2 (v1.4) does not crash. When I try Mozilla V1.4 I can very briefly see the page painting before mozilla crashes. The messages are a little different: $ mozilla No running window found. /dev/dsp: No such file or directory open dsp: No such file or directory Gdk-ERROR **: BadAccess (attempt to access private resource denied) serial 26 error_code 10 request_code 147 minor_code 1 $ echo $DISPLAY Stargate.Tom.Parquette.name:0 $ pkg_info indicates I have "flashplugin-mozilla-0.4.10_2 A GPL standalone Flash (TM) plugin for Mozilla web browser" installed. I have not checked to see if the plugin needs to be upgraded yet because I'm looking for a misconfigure for the plugins. Thanks for your help. Joe Marcus Clarke wrote: On Sat, 2003-08-02 at 16:20, Tom Parquette wrote: Try upgrading to Mozilla 1.4. There were numerous problems with 1.3.x. I am unable to reproduce this on 1.4 compiled with Xft and the GTK+-2 GUI. Joe ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
What is the actual status of Audigy2 support in 5.1-CURRENT?
Hi. I would like to get an Audigy2 Platnum card working on my AMD dual processor system. I'm 5.1-CURRENT but I tend to hang back a little. I have "device pcm" and "device sbc" in the kernel. When the system didn't figure out the card I added "device firewire" "device sbp" and "device fwe" to the kernel to see if the probes could figure out the firewire interface. The system appears to locate the firewire components of the card. It does not seem to understand the sound component. I get the following at boot time: pci2: at device 5.0 (no driver attached) I was following the discussion on the -current list about the Sound Blaster Audigy2 support. I do not know if the discussion continued off list but I suspect it might have. A dogpile search turned up a patch file emu10k2.txt. From the discussion thread in bsdforums I was unable to determine if this was the same patch file also mentioned in the -current mailing list threads. The first few lines of the patch file I have read: diff -u old-emu10k1/emu10k1.c new-emu10k2/emu10k1.c --- old-emu10k1/emu10k1.c Mon Feb 10 03:01:34 2003 +++ new-emu10k2/emu10k1.c Thu Feb 13 05:36:10 2003 @@ -1,4 +1,5 @@ /* + * Copyright (c) 2003 Orlando Bassotto <[EMAIL PROTECTED]> Whereis does not tell me the location of emu10k1.c. Can someone in the know clear this up for me? Thanks... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
5.1-CURRENT rebooting (multile systems) -- How to troubleshoot?
Hi. This is the third time I've tried to write this Email. Things keep failing out from under me. This did not happen before I cvsuped Oct 14 to get around the -pthread problem with ports. Either my server (I NFS mount /home from the server machine) or the desktop machine have failed unpredictably multiple times. Sometimes under load, sometimes it appears they fail overnight when only setiathome is running on them. They are dual processor Athlon machines. I have not seen any messages from any of these failures. I have seen one failure on the server that indiated a page fault in kernel mode. I didn't write all of the information down because I thought it would be logged in one of the logs. Wrong again idiot!! I do not have any doc on these and generic searches didn't turn up anything I can hang my hat on. My question is, if the system fails (I'm assuming these are panics) how do I get the machine to NOT automatically reboot so I can copy down the failure information? (Unless these are logged somewhere I have not found yet.) I'm frustrated because I cannot get any information on the failures to even begin to formulate a sane posting to the list. Sorry for the rambling posting. I'm venting a little. I'm used to fixing mainframe system software. I am still trying to learn the skills on my own for FreeBSD. TIA for any help. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /sys/boot, egcs vs. gcc, -Os
On Thu, 8 Apr 1999, John Polstra wrote: > > I am not saying the dependencies are broken. I'm just lamenting the > general problem that it's difficult to upgrade a port that depends on > a lot of things. It's a general structural problem, and I don't know > how to fix it. > > Say you've got a bunch of ports that all depend on the same shared > library -- maybe libjpeg or libXpm. You've had them installed for > a few months, and they all work fine. Now you decide to upgrade > one of them, the "foo" port. Oops, it requires a newer version of > libjpeg. You have to remove the old libjpeg so that the newer one > can be installed without a lot of complaints. Oops, a bunch of other > ports used the old libjpeg. Now you have to upgrade those ports too. > Oops, some of those ports depend on libXpm, and a new version of it is > needed now. Oops, now some other ports that used the old libXpm need > to be upgraded. > > At this point, you throw up your hands, pkg_delete -f everything, > and reinstall all your ports from scratch. And the next time you're > tempted to upgrade a port, you decide it would be easier to just buy > a new machine. :-) > > John I agree completely. I had just recently run into this problem in a big way over gnome. I am not familiar at all with the inner workings of the ports/package database system but it occurred to me that perhaps the database is currently only storing which packages a given package depends upon and is NOT storing which packages depend upon a given package -- i.e. the leaves know which branch they are on but the branches don't know which leaves they bear. If this is in fact the case then it seems to me that a first step in improving the behaviour of the port/package system is to make the database be a leaf-to-branch and branch-to-leaf linked relationship tree that can be traversed as needed. I'm not sure of the standard Computer Science jargon to describe such a tree. Tom To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: port dependencies (was Re: /sys/boot, egcs vs. gcc, -Os)
On Thu, 8 Apr 1999, Jacques Vidrine wrote: > On 8 April 1999 at 12:24, John Polstra wrote: > [snip] > > Say you've got a bunch of ports that all depend on the same shared > > library -- maybe libjpeg or libXpm. You've had them installed for > > a few months, and they all work fine. Now you decide to upgrade > > one of them, the "foo" port. Oops, it requires a newer version of > > libjpeg. You have to remove the old libjpeg so that the newer one > > can be installed without a lot of complaints. Oops, a bunch of other > > ports used the old libjpeg. Now you have to upgrade those ports too. > > Oops, some of those ports depend on libXpm, and a new version of it is > > needed now. Oops, now some other ports that used the old libXpm need > > to be upgraded. > > Now I understand what you are saying. The current ports structure > only goes one way through the dependency graph. Maybe when building a > particular port, not only should dependencies be checked, but anything > that depends on the port needs to be rebuilt. > > Jacques Vidrine / n...@nectar.com / nec...@freebsd.org Exactly correct. Tom To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: solid NFS patch #6 avail for -current - need testers files)
On Thu, 22 Apr 1999, Peter Wemm wrote: > Matthew Reimer wrote: > > Great work guys! It almost seems that -current is more stable than > > -stable! > > > > Matt > > Funny you should mention it. I've heard this from a number of people over > the last week.. One has even suggested using a particular known-good 4.0 > snapshot in preference to a 3.1-stable for a production system.. > > Cheers, > -Peter And on this note -- is it planned to merge or backport these patches to -stable? We make very heavy use of NFS (udp, 100mb fxp0 fullduplex). We're using FreeBSD-3.1-STABLE as NFS clients to a big Auspex NS7000 NFS file server. We're in production mode in our lab and can't risk running -current on many of our machines so we've decided to run -stable on ALL of them (except perhaps MY machine but don't tell anyone ;-) Tom To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
GrandCentralDispatch in FreeBSD?
Hi Robert I saw today that you've written a proof of concept MPM for apache in GCD [1] - are there any plans to port GCD to FreeBSD? Cheers Tom [1] http://lists.macosforge.org/pipermail/libdispatch-dev/2010-May/000352.html ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
Attilio Rao wrote: I have another problem where the bwn is fully recognized and wlan0 is created but the interface doesn't scan at all: # netstat -nil Name Mtu Network Address Ipkts Ierrs Idrop Opkts Oerrs Coll bwn0 2290 00:26:5e:64:be:750 0 0 0 0 0 # ifconfig wlan0 wlan0: flags=8843 metric 0 mtu 1500 ether 00:26:5e:64:be:75 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier ssid "" channel 1 (2412 MHz 11b) country US authmode OPEN privacy OFF txpower 30 bmiss 7 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 1 wme bintval 0 # kldstat Id Refs AddressSize Name 14 0x8010 90b9a8 kernel 21 0x80c22000 28a9abwn_v4_ucode.ko doing "ifconfig wlan0 list scan" ends up immediately without further output. The dmesg is here: http://www.freebsd.org/~attilio/dmesg-bwn0.diff I had a similar problem w/ a 4309. If you haven't solved this already, please check that the radio is actually enabled. some laptops have a button. some have a key sequence. many also have a BIOS setting. mine looked pretty much the same as yours to FreeBSD but just endlessly scanned the channels for a signal until i noticed that the radio was disabled in BIOS. tom ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
Weongyo Jeong wrote: OK. The patch is ready to test. Could you please test it with attached patch? your patch got rid of the "bwn0: unsupported rate 0" messages on my Dell Inspiron 1150. But it still gives me repeated: bwn0: RX decryption attempted (old 0 keyidx 0x1) and a few of the following: bwn0: need multicast update callback ts_to_ct(1274664456.824638117) = [2010-05-24 01:27:36] please let me know if there is anything you want me to test. Copyright (c) 1992-2010 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.0-STABLE #0: Sun May 16 00:05:17 EDT 2010 t...@zoe.uffner.com:/usr/obj/usr/src/sys/ZOE i386 Preloaded elf kernel "/boot/kernel/kernel" at 0xc0ab6000. Preloaded elf module "/boot/kernel/if_bwn.ko" at 0xc0ab6174. Preloaded elf module "/boot/kernel/siba_bwn.ko" at 0xc0ab6220. Preloaded elf module "/boot/modules/bwn_v4_ucode.ko" at 0xc0ab62d0. Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 2597803596 Hz CPU: Intel(R) Celeron(R) CPU 2.60GHz (2597.80-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Family = f Model = 2 Stepping = 9 Features=0xbfebf9ff Features2=0x4400 Instruction TLB: 4 KB, 2 MB or 4 MB pages, fully associative, 128 entries Data TLB: 4 KB or 4 MB pages, fully associative, 64 entries 1st-level data cache: 8 KB, 4-way set associative, sectored cache, 64 byte line size Trace cache: 12K-uops, 8-way set associative 2nd-level cache: 128 KB, 2-way set associative, sectored cache, 64 byte line size real memory = 1073741824 (1024 MB) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x0010 - 0x003f, 3145728 bytes (768 pages) 0x00c26000 - 0x3ec82fff, 1040568320 bytes (254045 pages) avail memory = 1040355328 (992 MB) bios32: Found BIOS32 Service Directory header at 0xc00ffe80 bios32: Entry = 0xffe90 (c00ffe90) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0xcfae pnpbios: Found PnP BIOS data at 0xc00fe2d0 pnpbios: Entry = f:e2f4 Rev = 1.0 pnpbios: Event flag at 4b4 Other BIOS signatures found: x86bios: IVT 0x00-0x0004ff at 0xc000 x86bios: SSEG 0x01-0x01 at 0xc3b74000 x86bios: EBDA 0x09f000-0x09 at 0xc009f000 x86bios: ROM 0x0a-0x0e at 0xc00a ULE: setup cpu 0 wlan: <802.11 Link Layer> snd_unit_init() u=0x00ff8000 [512] d=0x7c00 [32] c=0x03ff [1024] feeder_register: snd_unit=-1 snd_maxautovchans=16 latency=5 feeder_rate_min=1 feeder_rate_max=2016000 feeder_rate_round=25 firmware: 'bwn_v4_ucode' version 0: 0 bytes loaded at 0xc0a8b808 firmware: 'bwn_v4_ucode5' version 0: 22384 bytes loaded at 0xc0a8b808 firmware: 'bwn_v4_ucode11' version 0: 29864 bytes loaded at 0xc0a90f78 firmware: 'bwn_v4_ucode13' version 0: 32232 bytes loaded at 0xc0a98420 firmware: 'bwn_v4_ucode14' version 0: 31384 bytes loaded at 0xc0aa0208 firmware: 'bwn_v4_ucode15' version 0: 30488 bytes loaded at 0xc0aa7ca0 firmware: 'bwn_v4_pcm5' version 0: 1320 bytes loaded at 0xc0aaf3b8 firmware: 'bwn_v4_a0g1initvals5' version 0: 1840 bytes loaded at 0xc0aaf8e0 firmware: 'bwn_v4_a0g0initvals5' version 0: 1840 bytes loaded at 0xc0ab0010 firmware: 'bwn_v4_b0g0initvals5' version 0: 1840 bytes loaded at 0xc0ab0740 firmware: 'bwn_v4_b0g0initvals13' version 0: 2080 bytes loaded at 0xc0ab0e70 firmware: 'bwn_v4_a0g1bsinitvals5' version 0: 158 bytes loaded at 0xc0ab1690 firmware: 'bwn_v4_a0g0bsinitvals5' version 0: 158 bytes loaded at 0xc0ab172e firmware: 'bwn_v4_b0g0bsinitvals5' version 0: 158 bytes loaded at 0xc0ab17cc firmware: 'bwn_v4_lp0initvals13' version 0: 3618 bytes loaded at 0xc0ab186a firmware: 'bwn_v4_lp0initvals14' version 0: 2064 bytes loaded at 0xc0ab268c firmware: 'bwn_v4_lp0initvals15' version 0: 2052 bytes loaded at 0xc0ab2e9c firmware: 'bwn_v4_lp0bsinitvals13' version 0: 158 bytes loaded at 0xc0ab36a0 firmware: 'bwn_v4_lp0bsinitvals14' version 0: 158 bytes loaded at 0xc0ab373e firmware: 'bwn_v4_lp0bsinitvals15' version 0: 158 bytes loaded at 0xc0ab37dc firmware: 'bwn_v4_n0bsinitvals11' version 0: 158 bytes loaded at 0xc0ab387a kbd: new array size 4 kbd1 at kbdmux0 nfslock: pseudo-device mem: Pentium Pro MTRR support enabled null: io: random: ACPI: RSDP 0xfdf00 00014 (v0 DELL ) ACPI: RSDT 0x3fef 00028 (v1 DELLCPi R 27D50605 ASL 0061) ACPI: FACP 0x3fef0400 00074 (v1 DELLCPi R 27D50605 ASL 0061) ACPI: DSDT 0x3fef0c00 02594 (v1 INT430 SYSFexxx 1001 MSFT 010E) ACPI: FACS 0x3feff800 00040 npx0: INT 16 interface acpi0: on motherboard acpi0: [MPSAFE] acpi0: [ITHREAD] acpi0: wakeup code va 0xc3b73000 pa 0x1000 atpic: Programming IRQ9 as level/low pci_open(1):mode 1 addr port (0x0cf8) is 0x8050 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=80]
patch submission for multiple branches
I have updated the twa driver (src/sys/dev/twa) and generated patches against RELENG_7 and RELENG_8. I submitted the patches separately in PR 147694 (RELENG_7) and PR 147695 (RELENG_8). PR 147694 has been closed as a duplicate of PR 147695. What happens to the patch for RELENG_7 (PR 147694)? What is the proper way to submit patches for multiple branches? Tom Couch ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Ports doesnt respect fetch environment settings
My company recently enabled proxy authentication for outgoing connections, and this has stopped ports from working. >From fetch(5), I understand that I can place my proxy authentication in plain text in the environment*, and this will allow fetch to work correctly, and this does work: > # env | grep -i proxy ftp_proxy=http://proxy:3128/ HTTP_PROXY_AUTH=basic:*:tev...@domain.com:password HTTP_PROXY=http://proxy:3128/ > # fetch http://googlecl.googlecode.com/files/googlecl-0.9.5.tar.gz googlecl-0.9.5.tar.gz 100% of 36 kB 77 MBps However, the ports makefiles seem to do something funky to my environment which hides these environment variables, and so the ports infrastructure stops working: > # make fetch ===> Vulnerability check disabled, database not found ===> License check disabled, port has not defined LICENSE => googlecl-0.9.5.tar.gz doesn't seem to exist in /usr/ports/distfiles/. => Attempting to fetch from http://googlecl.googlecode.com/files/. fetch: http://googlecl.googlecode.com/files/googlecl-0.9.5.tar.gz: Proxy Authentication Required => Attempting to fetch from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/. fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/googlecl-0.9.5.tar.gz: Not Found => Couldn't fetch it - please try to retrieve this => port manually into /usr/ports/distfiles/ and try again. *** Error code 1 Stop in /usr/FreeBSD/CURRENT/ports/net/googlecl. This is on i386 7-STABLE, last updated in mid May, with current ports, last updated yesterday. Cheers Tom * Which, incidently, is completely rubbish. Why is there no option for HTTP like ~/.netrc for FTP? Exposing my passwords in plain text in my environment feels stupid. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Ports doesnt respect fetch environment settings
On Mon, Jun 21, 2010 at 11:10 AM, Erwin Lansing wrote:
> On Mon, Jun 21, 2010 at 11:04:16AM +0100, Tom Evans wrote:
>> My company recently enabled proxy authentication for outgoing
>> connections, and this has stopped ports from working.
>>
>> >From fetch(5), I understand that I can place my proxy authentication
>> in plain text in the environment*, and this will allow fetch to work
>> correctly, and this does work:
>>
>> > # env | grep -i proxy
>> ftp_proxy=http://proxy:3128/
>> HTTP_PROXY_AUTH=basic:*:tev...@domain.com:password
>> HTTP_PROXY=http://proxy:3128/
>> > # fetch http://googlecl.googlecode.com/files/googlecl-0.9.5.tar.gz
>> googlecl-0.9.5.tar.gz 100% of 36 kB 77 MBps
>>
>> However, the ports makefiles seem to do something funky to my
>> environment which hides these environment variables, and so the ports
>> infrastructure stops working:
>>
> You should use FETCH_ENV or FETCH_ARGS to pass information to fetch(1) from
> the
> ports infrastructure. It is documented in /usr/ports/Mk/bsd.port.mk,
> search for FETCH_BINARY. Hope that helps.
>
> -erwin
>
Er, ok that makes slight sense. In /usr/ports/Mk/bsd.port.mk it says:
# FETCH_ENV - Environment to pass to ${FETCH_CMD}.
# Default: none
So how is it picking up that it needs to go thru a proxy at all, given
that this is also only specified in the environment?
Also, am I supposed to literally repeat my same environment variables
in FETCH_ENV? Meaning I have to place my password in plain text again
in my environment? This is horrific...
Also, even after doing that, it still doesn't look at the environment
variables. I prepended "-v" to FETCH_ENV to show that it is setting
the right environment variables, but fetch in ports is still not
looking at them:
> # export FETCH_ENV="-v HTTP_PROXY=$HTTP_PROXY
> HTTP_PROXY_AUTH=$HTTP_PROXY_AUTH ftp_proxy=$ftp_proxy"
r...@strangepork '11:26:21' '/usr/ports/net/googlecl'
> # make fetch
===> Vulnerability check disabled, database not found
===> License check disabled, port has not defined LICENSE
=> googlecl-0.9.5.tar.gz doesn't seem to exist in /usr/ports/distfiles/.
=> Attempting to fetch from http://googlecl.googlecode.com/files/.
#env setenv:HTTP_PROXY=http://proxy:3128/
#env setenv:HTTP_PROXY_AUTH=basic:*:tev...@domain:pass
#env setenv:ftp_proxy=http://proxy:3128/
#env executing: /usr/bin/fetch
#envarg[0]= '/usr/bin/fetch'
#envarg[1]= '-ApRr'
#envarg[2]= '-S 37867'
#envarg[3]= 'http://googlecl.googlecode.com/files/googlecl-0.9.5.tar.gz'
fetch: http://googlecl.googlecode.com/files/googlecl-0.9.5.tar.gz:
Proxy Authentication Required
=> Attempting to fetch from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/.
#env setenv:HTTP_PROXY=http://proxy:3128/
#env setenv:HTTP_PROXY_AUTH=basic:*:tev...@domain:pass
#env setenv:ftp_proxy=http://proxy:3128/
#env executing: /usr/bin/fetch
#envarg[0]= '/usr/bin/fetch'
#envarg[1]= '-ApRr'
#envarg[2]= '-S 37867'
#envarg[3]=
'ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/googlecl-0.9.5.tar.gz'
fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/googlecl-0.9.5.tar.gz:
Not Found
=> Couldn't fetch it - please try to retrieve this
=> port manually into /usr/ports/distfiles/ and try again.
*** Error code 1
*.freebsd.org is whitelisted through the proxies, which is why the
second fetch gets a 404 and not a 407
Any thoughts?
Cheers
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Ports doesnt respect fetch environment settings
On Mon, Jun 21, 2010 at 12:07 PM, Gary Jennejohn
wrote:
> Yes. When you ran fetch by hand you didn't have the -ApRr on the CL.
> Could it be that the 'p' flag is causing problems?
>
> Try running fetch by hand again with those flags and see what happens.
> If it fails, try removing the 'p' flag.
>
> --
> Gary Jennejohn
>
Yes, I went through the same logic - its not the 'p' flag, its the 'A'
flag, which is supposed to prevent it following 302 redirects.
In this case, it refuses to retry the request when it receives a 407.
> # /usr/bin/fetch -ApRr -v -S 37867
> http://googlecl.googlecode.com/files/googlecl-0.9.5.tar.gz
looking up proxy
connecting to proxy:3128
requesting http://googlecl.googlecode.com/files/googlecl-0.9.5.tar.gz
proxy requires authorization
fetch: http://googlecl.googlecode.com/files/googlecl-0.9.5.tar.gz:
Proxy Authentication Required
r...@strangepork '12:13:28' '/usr/ports/net/googlecl'
> # /usr/bin/fetch -pRr -v -S 37867
> http://googlecl.googlecode.com/files/googlecl-0.9.5.tar.gz
looking up proxy
connecting to proxy:3128
requesting http://googlecl.googlecode.com/files/googlecl-0.9.5.tar.gz
proxy requires authorization
looking up proxy
connecting to proxy:3128
requesting http://googlecl.googlecode.com/files/googlecl-0.9.5.tar.gz
local size / mtime: 37867 / 1276839258
remote size / mtime: 37867 / 1276839258
That doesn't seem right!
Looking in lib/libfetch/http.c it tries to fetch the file in a loop.
libfetch first tries without proxy authentication, even if you specify
it in your environment.
If the request fails due to proxy authentication being required, it
sets a flag to add proxy auth details next time through the loop, and
continues.
If the '-A' flag is set however, it will only go through this loop one
time, and so does not attempt to use the supplied proxy
authentication.
Comments in the source code imply that this is a change in behaviour
introduced at the start of the year to support digest authentication;
prior to that it would have attempted proxy auth on the first request.
The flag for '-A' is documented as:
-A Do not automatically follow ‘‘temporary’’ (302) redirects.
Some broken Web sites will return a redirect instead of a
not‐found error when the requested object does not exist.
where as the behaviour is:
Do not attempt to download this file more than once, for any reason.
Having seen this, the bug is that we wish to go thru the loop one more
time to retry with proxy authentication added, but the loop may exit
on the next iteration. This diff allows it to go through the loop one
more time, and now fetches the file correctly.
Incidentally, having fixed fetch to work with '-A' thru a proxy that
requires proxy auth, I now dont require anything in FETCH_ENV or
FETCH_*_ARGS, it works correctly with the PROXY_* environment
variables.
Patch attached.
Cheers
Tom
Index: /usr/src/lib/libfetch/http.c
===
RCS file: /home/ncvs/src/lib/libfetch/http.c,v
retrieving revision 1.78.2.5
diff -u -r1.78.2.5 http.c
--- /usr/src/lib/libfetch/http.c27 Jan 2010 14:54:48 - 1.78.2.5
+++ /usr/src/lib/libfetch/http.c21 Jun 2010 11:30:32 -
@@ -1710,6 +1710,7 @@
goto ouch;
}
/* try again, but send the password this time */
+ ++n;
if (verbose)
fetch_info("proxy requires authorization");
break;
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Problem with buildworld with CLANG
On Wed, Jun 23, 2010 at 1:38 PM, Cristiano Deana wrote: > # uname -a > FreeBSD test 9.0-CURRENT FreeBSD 9.0-CURRENT #3: Tue Jun 22 16:04:38 > CEST 2010 r...@test:/usr/obj/usr/src/sys/GENERIC amd64 > > # cat /etc/src.conf > #NO_WERROR= > #WERROR= > CC= clang > CXX= clang++ > > sources from this morning, i got this error: > > clang -O2 -pipe -I/usr/src/lib/libc/include > -I/usr/src/lib/libc/../../include -I/usr/src/lib/libc/amd64 -DNLS > -D__DBINTERFACE_PRIVATE -I/usr/src/lib/libc/../../contrib/gdtoa > -DINET6 -I/usr/obj/usr/src/lib/libc -I/usr/src/lib/libc/resolv > -D_ACL_PRIVATE -DPOSIX_MISTAKE > -I/usr/src/lib/libc/../../contrib/tzcode/stdtime > -I/usr/src/lib/libc/stdtime -I/usr/src/lib/libc/locale -DBROKEN_DES > -DPORTMAP -DDES_BUILTIN -I/usr/src/lib/libc/rpc -DYP -DNS_CACHING > -DSYMBOL_VERSIONING -std=gnu99 -Wsystem-headers -Werror -Wall > -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c > /usr/src/lib/libc/sys/stack_protector.c > /usr/src/lib/libc/sys/stack_protector.c:88:19: error: format string is > not a string literal (potentially insecure) [-Wformat-security] > syslog(LOG_CRIT, msg); > ^~~ > 1 error generated. > *** Error code 1 > Top of the '[TESTING] Clang..' email: > hi, > > ClangBSD was updated to LLVM/clang revision 104832 which is what we aim to > import > into HEAD in roughly a week. We would like the initial import to be as > painless > as possible and therefore we ask you to test ClangBSD to assure that the > revision > we are importing does not have some really embarassing bugs. > > How to do it (on i386 and amd64): > > 0) install fresh devel/llvm-devel port > > 1) svn co http://svn.freebsd.org/base/projects/clangbsd src > > 2) echo NO_WERROR= >> /etc/src.conf ; echo WERROR= >> /etc/src.conf > > 3) cd src && make buildworld So uncomment your src.conf lines that are incompatible. Cheers Tom ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: using cupsd instead of base lpr [was Re: [HEADS UP] Kernel modules don't work properly in FreeBSD 8.1-RC1 (solved)]
On Thu, Jun 24, 2010 at 8:23 AM, Gary Jennejohn wrote: > On Wed, 23 Jun 2010 18:15:09 -0700 > Ted Faber wrote: > >> (/usr/local/bin/ preceeds /usr/bin in my path so I can use the lpr >> commands from cupsd, though it's evidently a bit of a dangerous idea.) >> > [trimmed Cc] > > I use cupsd and have these settings to get around using the base system > lp stuff: > > in /etc/src.conf - WITHOUT_LPR=yes > > and these symbolic links in /usr/bin > lrwxr-xr-x 1 root wheel 17 Mar 18 2009 /usr/bin/lp -> > /usr/local/bin/lp > lrwxr-xr-x 1 root wheel 24 Mar 18 2009 /usr/bin/lpoptions -> > /usr/local/bin/lpoptions > lrwxr-xr-x 1 root wheel 18 Mar 18 2009 /usr/bin/lpq -> > /usr/local/bin/lpq > lrwxr-xr-x 1 root wheel 18 Mar 18 2009 /usr/bin/lpr -> > /usr/local/bin/lpr > lrwxr-xr-x 1 root wheel 19 Mar 18 2009 /usr/bin/lprm -> > /usr/local/bin/lprm > lrwxr-xr-x 1 root wheel 21 Mar 18 2009 /usr/bin/lpstat -> > /usr/local/bin/lpstat > > and /usr/bin is _before_ /usr/local/bin in my PATH. > > --- > Gary Jennejohn I also have this in make.conf: CUPS_OVERWRITE_BASE=yes WITHOUT_LPR=yes which print/cups-base uses to do make any lpr related binaries in /usr/bin non-executable, so they are skipped over and the cups specific ones in /usr/loca/bin are used instead. WITHOUT_LPR just stops LPR being built by buildworld. Cheers Tom ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: zfs panic
On Wed, Jun 23, 2010 at 10:01 PM, ben wilber wrote: > On Wed, Jun 23, 2010 at 01:47:33PM -0700, Xin LI wrote: >> > >> > panic: _sx_xlock_hard: recursed on non-recursive sx >> > buf_hash_table.ht_locks[i].ht_lock @ >> > /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/c >> > ommon/fs/zfs/arc.c:1626 >> >> Any chance to obtain a backtrace for the panic? > > >From r209229: > > db:0:kdb.enter.default> bt > Tracing pid 3233 tid 100396 td 0xff013600f000 > kdb_enter() at kdb_enter+0x3d > panic() at panic+0x1c8 > _sx_xlock_hard() at _sx_xlock_hard+0x93 > _sx_xlock() at _sx_xlock+0xaa > arc_buf_remove_ref() at arc_buf_remove_ref+0x7b > dbuf_rele() at dbuf_rele+0x15d > zfs_freebsd_reclaim() at zfs_freebsd_reclaim+0xe1 > VOP_RECLAIM_APV() at VOP_RECLAIM_APV+0xe8 > vgonel() at vgonel+0x186 > vnlru_free() at vnlru_free+0x2f4 > vfs_lowmem() at vfs_lowmem+0x31 > kmem_malloc() at kmem_malloc+0x12c > page_alloc() at page_alloc+0x18 > keg_alloc_slab() at keg_alloc_slab+0xe6 > keg_fetch_slab() at keg_fetch_slab+0x18e > zone_fetch_slab() at zone_fetch_slab+0x4f > uma_zalloc_arg() at uma_zalloc_arg+0x56b > arc_get_data_buf() at arc_get_data_buf+0xaa > arc_read_nolock() at arc_read_nolock+0x1cb > arc_read() at arc_read+0x71 > dbuf_read() at dbuf_read+0x4ea > dmu_buf_hold_array_by_dnode() at dmu_buf_hold_array_by_dnode+0x119 > dmu_buf_hold_array() at dmu_buf_hold_array+0x57 > dmu_read_uio() at dmu_read_uio+0x3f > zfs_freebsd_read() at zfs_freebsd_read+0x558 > VOP_READ_APV() at VOP_READ_APV+0xe2 > vn_read() at vn_read+0x1d0 > dofileread() at dofileread+0x97 > kern_preadv() at kern_preadv+0x6a > pread() at pread+0x52 > syscallenter() at syscallenter+0x217 > syscall() at syscall+0x39 > Xfast_syscall() at Xfast_syscall+0xe1 > --- syscall (475, FreeBSD ELF64, pread), rip = 0x80100c14c, rsp = > 0x7fbfeb48, rbp = 0x2 --- > > Thanks. I notice the traceback is in the UMA zone allocaor. Did it used to be stable? ZFS recently changed to using the UMA allocator, and I found this made my system less reliable. Does disabling this help? Add this to /boot/loader.conf: vfs.zfs.zio.use_uma=0 Cheers Tom ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Problem with buildworld with CLANG
On Wed, Jun 23, 2010 at 4:52 PM, Cristiano Deana wrote: > On Wed, Jun 23, 2010 at 3:15 PM, Tom Evans wrote: > >> Top of the '[TESTING] Clang..' email: >> >>> hi, >>> >>> ClangBSD was updated to LLVM/clang revision 104832 which is what we aim to >>> import >>> into HEAD in roughly a week. We would like the initial import to be as >>> painless >>> as possible and therefore we ask you to test ClangBSD to assure that the >>> revision >>> we are importing does not have some really embarassing bugs. >>> >>> How to do it (on i386 and amd64): > >>> 1) svn co http://svn.freebsd.org/base/projects/clangbsd src > > i already did it and it worked, two weeks ago. > now i wanted to try with clan in system > >>> 2) echo NO_WERROR= >> /etc/src.conf ; echo WERROR= >> /etc/src.conf > >> So uncomment your src.conf lines that are incompatible. > > forgot to tell before. i tried with and without those lines. > The error in your first email was clearly a warning being promoted to an error, so either you had a different error on your build with NO_WERROR/WERROR, or your NO_WERROR/WERROR settings were not being respected. Please retry with NO_WERROR/WERROR set in /etc/src.conf, and show the resulting error. Cheers Tom ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: using cupsd instead of base lpr [was Re: [HEADS UP] Kernel modules don't work properly in FreeBSD 8.1-RC1 (solved)]
On Thu, Jun 24, 2010 at 10:21 AM, Andrew Reilly wrote: > On Thu, Jun 24, 2010 at 09:23:37AM +0200, Gary Jennejohn wrote: >> in /etc/src.conf - WITHOUT_LPR=yes >> >> and these symbolic links in /usr/bin >> lrwxr-xr-x 1 root wheel 17 Mar 18 2009 /usr/bin/lp -> >> /usr/local/bin/lp >> lrwxr-xr-x 1 root wheel 24 Mar 18 2009 /usr/bin/lpoptions -> >> /usr/local/bin/lpoptions >> lrwxr-xr-x 1 root wheel 18 Mar 18 2009 /usr/bin/lpq -> >> /usr/local/bin/lpq >> lrwxr-xr-x 1 root wheel 18 Mar 18 2009 /usr/bin/lpr -> >> /usr/local/bin/lpr >> lrwxr-xr-x 1 root wheel 19 Mar 18 2009 /usr/bin/lprm -> >> /usr/local/bin/lprm >> lrwxr-xr-x 1 root wheel 21 Mar 18 2009 /usr/bin/lpstat -> >> /usr/local/bin/lpstat >> >> and /usr/bin is _before_ /usr/local/bin in my PATH. > > Since you have /usr/local/bin in your path, why bother with > the symlinks at all? Your shell will find them in their new > locations just fine. You'll want to remove the old ones from > /usr/bin, but make delete-old will probably do that nicely > anyway. > > Cheers, > > -- > Andrew make delete-old removes old deprecated files, not files that weren't built because of src.conf options. It definitely will not remove the lpr binaries from /usr/bin if they exist there. There already is a proper solution for this: if you want to have LPR from CUPS, and don't want to use LPR from base, then you set these settings in make.conf: CUPS_OVERWRITE_BASE=yes WITHOUT_LPR=yes With these, lpr in base will not be built, and print/cups-base will deactivate any base system lpr binaries that are installed. It's documented in the FreeBSD CUPS article here: http://www.freebsd.org/doc/en/articles/cups/article.html#PRINTING-CUPS-PORTS-KNOBS Cheers Tom ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
