installworld error (ex: not found)
I've been having some trouble getting this -CURRENT system to do a proper installworld. I installed a JPSNAP (20011230) with only the /bin distribution, then cvsup'ed, made world and kernel, and went on to the installworld. I've done this thrice now (January 3,5,6), and each time I get the same error: [snip things going fine] ... install -c -o root -g wheel -m 444 xerox1730 /usr/share/tabset/xerox1730 install -c -o root -g wheel -m 444 xerox1730-lm /usr/share/tabset/xerox1730-lm install -c -o root -g wheel -m 444 zenith29 /usr/share/tabset/zenith29 ===> share/termcap install -c -o root -g wheel -m 444 /usr/src/share/termcap/map3270 /usr/share/misc/map3270 TERM=dumb ex - /usr/src/share/termcap/termcap.src < /usr/src/share/termcap/reorder ex: not found *** Error code 127 Stop in /usr/src/share/termcap. *** Error code 1 ...so wondering where ex is and what is wrong with it: [15:26 munish@rn-re116a13 ~] ll /usr/bin/ex -r-xr-xr-x 6 root wheel 279952 Dec 29 15:19 /usr/bin/ex ...it's there and fine. The PATH is set fine too. So I don't really know where to go from here...hints are welcome. Thanks. -- Munish Chopra To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
installworld error (ex: not found)
(re-posting this as the date on this box was stuck somewhere in December, which I figured would leave me with little response from anyone who sorts by date): I've been having some trouble getting this -CURRENT system to do a proper installworld. I installed a JPSNAP (20011230) with only the /bin distribution, then cvsup'ed, made world and kernel, and went on to the installworld. I've done this thrice now (January 3,5,6), and each time I get the same error: [snip things going fine] ... install -c -o root -g wheel -m 444 xerox1730 /usr/share/tabset/xerox1730 install -c -o root -g wheel -m 444 xerox1730-lm /usr/share/tabset/xerox1730-lm install -c -o root -g wheel -m 444 zenith29 /usr/share/tabset/zenith29 ===> share/termcap install -c -o root -g wheel -m 444 /usr/src/share/termcap/map3270 /usr/share/misc/map3270 TERM=dumb ex - /usr/src/share/termcap/termcap.src < /usr/src/share/termcap/reorder ex: not found *** Error code 127 Stop in /usr/src/share/termcap. *** Error code 1 ...so wondering where ex is and what is wrong with it: [15:26 munish@rn-re116a13 ~] ll /usr/bin/ex -r-xr-xr-x 6 root wheel 279952 Dec 29 15:19 /usr/bin/ex ...it's there and fine. The PATH is set fine too. So I don't really know where to go from here...hints are welcome. Thanks. -- Munish Chopra To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PAM Error
On Mon, Feb 11, 2002 at 12:04:53PM +, [EMAIL PROTECTED] wrote: > > Yesterday I tried to use SWAT for the first time since the PAM configs were > > moved from /etc/pam.conf and I'm getting the following error: > > > > Feb 6 22:54:05 galaxy swat: PAM _pam_init_handlers: could not open > > /etc/pam.conf > > > > What do I need to do to fix this? > > Recompile the app. I'm guessing it is linked statically, so is not > picking up the latest libpam. > Though that sounds logical to me too, I've had the same errors pop up using a self-compiled 'cups'. I haven't had time to try to chase what's going on. -- Munish Chopra The FreeBSD NVIDIA Driver Initiative http://nvidia.netexplorer.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PAM Error
On Mon, Feb 11, 2002 at 12:04:53PM +, [EMAIL PROTECTED] wrote: > > Yesterday I tried to use SWAT for the first time since the PAM configs were > > moved from /etc/pam.conf and I'm getting the following error: > > > > Feb 6 22:54:05 galaxy swat: PAM _pam_init_handlers: could not open > > /etc/pam.conf > > > > What do I need to do to fix this? > > Recompile the app. I'm guessing it is linked statically, so is not > picking up the latest libpam. > Though that sounds logical to me too, I've had the same errors pop up using a self-compiled 'cups'. I haven't had time to try to chase what's going on. -- Munish Chopra The FreeBSD NVIDIA Driver Initiative http://nvidia.netexplorer.org 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
On Tue, Feb 19, 2002 at 12:50:11PM -0500, Michael Lucas wrote: > > 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. > Very good idea. I probably qualify as a good representation of the type of users you are targetting. > 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. > That sounds good. I'm more of a no-BS-get-down-to-business kinda guy though. I like quick instructions and explanations of why. I should be able to figure out most of the stuff through whatever comes out of this thread though. And there's always the handbooks... > My question to the community is: is it too early to do this? If I > start now, the articles would probably appear April-May. I'm not going to pretend I'm an authority on this, but I think it'd be a good time to start now. All I am more or less comfortable with is typing 'trace' and looking at stuff I don't know anything about :) Give people some time to experiment with how the tools work and why they do what they do. After they've had to use them for a little while and the feedback isn't complete garbage to them anymore, the bug reports will be much better and more concise (I'd hope so at least). That would give then -CURRENT branch a boost at a time when I would guess it'll really need it. Basically, people who are new to -CURRENT like me need some time and advice to get comfortable with the tools. Then we'll be of much more help than stumbling around blindly. -- Munish Chopra The FreeBSD NVIDIA Driver Initiative http://nvidia.netexplorer.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
The FreeBSD NVIDIA Driver Initiative
If the following isn't an appropriate subject for discussion on this particular mailing list, please move ensuing discussion to one that is more appropriate (possibly -hackers or -hardware). We are a simply a few guys who at more or less the same time got tired of not having 3D-support for our NVIDIA cards in FreeBSD. So we decided to start 'The FreeBSD NVIDIA Driver Initiative'. As the name may say, we tried to figure out how we were going to get hardware accelerated 3D drivers for FreeBSD. After going through a bit of work and contacting NVIDIA, it's come to this: We are located at http://nvidia.netexplorer.org, from where we try to keep people updated on how the effort is going. We have taken over Michael Carlson's petition for drivers (some of you may remember it from when it was started back in January), and if you haven't signed it yet, please come on over and do. There IS currently a team working on the drivers (not NVIDIA itself, but some people who are getting a bit of help from NVIDIA at least). We will keep you updated on how things go. For those of you wondering about the legal issues, they DID come up, and have been successfully resolved. Please drop by the site to sign the petition and check on how things are going. Cheers, Munish Chopra The FreeBSD NVIDIA Driver Initiative _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: C conformance.
On 2003-02-09 19:13 +, Terry Lambert wrote: > Marcin Dalecki wrote: > > Trying to use a compiler different from GCC I have found the folowing error > > > > "/usr/include/sys/syslimits.h", line 42: Error: > >[ISO 6.8]: Unknown preprocessing directive, '#warning'. > > > > I think that somthing like to above should not appear in system > > headers. > > It is an ANSI compliant preprocessor directive. Please use an ANSI > compliant compiler. > > Have you actually looked at the line? It's protected by > "#if __GNUC__", so your compiler shouldn't be trying to interpret > any directives other than "#else", "#elif", or "#endif" (or the > premature end of the file). > This is a known problem with the overaggressive preprocessor. Things like this will get fixed as time permits, or new volunteers pop up :) -- Munish Chopra To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: C conformance.
Terry Lambert wrote: >Marcin Dalecki wrote: >> Trying to use a compiler different from GCC I have found the folowing >error >> >> "/usr/include/sys/syslimits.h", line 42: Error: >>[ISO 6.8]: Unknown preprocessing directive, '#warning'. >> >> I think that somthing like to above should not appear in system >> headers. > >It is an ANSI compliant preprocessor directive. Please use an ANSI >compliant compiler. I'd also be curious to know in which version of the ANSI standard you have found #warning. I certainly doesn't appear in mine. -- Munish Chopra To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Still problems with ULE
On 2003-02-10 20:36 +, Jeff Roberson wrote: > On Mon, 10 Feb 2003, Kris Kennaway wrote: > > > I gave ULE another try just now, following your recent commits, and > > I'm seeing even worse problems: > > > > At boot time when the X server is loading, disk activity occurs > > briefly about once every 2 seconds; the mouse is active briefly at the > > same time, and nothing much else happens for about a minute until the > > entire system deadlocks. > > Very weird. Is this on UP or SMP? I'm still working on a couple of > issues with ule. I think I am very happy with the dynamic priority > selection now but in the process the slice size selection got kinda dirty. > Its pretty much bug for bug compatible with the old scheduler's context > switching decisions but the errors there are more serious with this > design. I also think the max slice size is way too high now. I was > experimenting with that and I accidentally checked it in. > I'm seeing some of the same with sources from about 90 minutes ago. UP system, loading X is a pain. Interactivity is somewhat alright up until I start a compile, at which point the system goes down on it's knees. It hasn't completely deadlocked (yet?), but it's pretty much unusable if anything intensive is happening. -- Munish Chopra To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NVidia glx stuff dies in sysarch(I386_SET_LDT, ...)
On 2003-08-02 00:20 +0200, Thorsten Greiner wrote: > * Daniel Eischen <[EMAIL PROTECTED]> [2003-08-02 00:06]: > > I think the bug was in the old code allowing this to > > happen... > > Well, than someone should tell that to NVidia. Their driver is > closed source and comes without "user servicable parts". > > Regards > -Thorsten > That's going to be a lot easier to get through if someone can confirm whether 0-16 are reserved, or whether (like julian says), 6-15 are actually safe and something else is being clobbered. -- Munish Chopra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Specifying default alternate sound device?
On 2003-08-05 13:17 -0400, Mathew Kanner wrote: > On Aug 05, Adam wrote: > > Is there any easy way to specify a default alternate sound device (eg, > > /dev/dsp1). I have both onboard sound (/dev/dsp) and a SB Live card > > (/dev/dsp1), but I don't use the onboard sound. It's really frustrating > > to try to configure every single application (that uses sound) to use > > /dev/dsp1 instead. > > > > Is there some safe/easy trick to set a general rule that all/most apps > > will follow, so that they use /dev/dsp1 instead? > > With devfs, the default sound unit is tunable by a sysctl. > > tube# sysctl hw.snd.unit=0 ; ls -l dsp dsp0.0 dsp1.0 ; sysctl hw.snd.unit=1 ; ls -l > dsp dsp0.0 dsp1.0 > hw.snd.unit: 1 -> 0 > crw-rw-rw- 1 root wheel 30, 3 Aug 5 11:24 dsp > crw-rw-rw- 1 root wheel 30, 3 Aug 5 11:24 dsp0.0 > crw-rw-rw- 1 root wheel 30, 19 Aug 5 11:24 dsp1.0 > hw.snd.unit: 0 -> 1 > crw-rw-rw- 1 root wheel 30, 19 Aug 5 11:24 dsp > crw-rw-rw- 1 root wheel 30, 3 Aug 5 11:24 dsp0.0 > crw-rw-rw- 1 root wheel 30, 19 Aug 5 11:24 dsp1.0 > > --Mat > -- > sig machine broken. Besides this solution, you could just turn off onboard sound in the BIOS. -- Munish Chopra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Strange system responsiveness issues with 5.1-CURRENT
On 2003-09-23 09:58 -0700, Brooks Davis wrote: > On Tue, Sep 23, 2003 at 07:43:25PM +0300, Dan Naumov wrote: > > Starting applications (XFree, Evolution, Mozilla, OpenOffice, games) > > takes a noticably longer time than it used to, I'd say that Mozilla > > Firebird load times have increased by about 30-40%. I can also now see > > "jerkiness" in switching between applications. When Alt-Tabbing between > > Firebird, OpenOffice and Evolution, the windows appear half-drawn for a > > second or two. > > The debugging features mentioned in the first entry in /usr/src/UPDATING > were disabled in RELEASE, but not in CURRENT. This might account for > these differences. > I've been experiencing (especially) the lag in audio and/or video when seeking within media files. I kicked out all the debugging stuff, but it didn't make a difference. -- Munish Chopra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Status of SCHED_ULE?
On 2003-09-30 02:07 +0300, Aggelos Economopoulos wrote: > On Tuesday 30 September 2003 01:12, Jeff Roberson wrote: > > On Tue, 30 Sep 2003, Aggelos Economopoulos wrote: > > > On Monday 29 September 2003 08:05, Jeff Roberson wrote: > > > > On Sun, 28 Sep 2003, Arjan van Leeuwen wrote: > > > > > > [...] > > > > > > > > It happens when compiling stuff, when loading complicated pages in > > > > > Mozilla Firebird, and when logging out of GNOME 2.4 (the 'background > > > > > fade' animation brings my Athlon XP 2000+ to its knees when I use > > > > > SCHED_ULE). > > > > > > > > > > Arjan > > > > > > > > Gnome seems to be a common theme. Are you also using libkse? There > > > > could be some interaction there. > > > I'm having the same experience, no gnome involved. > > > I'm experiencing similar stuff with kde + libthr (kernel built with > > > sources from 18/9). > > > > > > Aggelos > > > > Are you running seti, rc4, etc? Any programs that sit in the background > > and consume 100% of the cpu? > > No. But interactive performance deteriorates instantly when compiling or > linking two or more programs (of course I expect it to deteriorate, but the > gui is _much_ more jerky with SCHED_ULE than with SCHED_4BSD). Let me know if > I can help with any more info. > I second that. I'm not running anything heavy, background or not. Windowmaker, a few desktops, a bunch of aterms -- that's more or less all. The most easily noticeable pessimization is probably Firebird (or Mozilla if you prefer). Compile anything, and try opening or closing a few tabs, or navigating. It's rather painful. This is on a Thunderbird 1200 sporting 512MB RAM. It's not exactly fast by today's standards, but operation is much smoother under SCHED_4BSD. -- Munish Chopra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ULE status; interactivity fixed? nice uninvestigated, HTT broken
On 2003-10-13 01:33 -0400, Wade Majors wrote: > Jeff Roberson wrote: > >I commited a fix that would have caused all of the jerky behaviors under > >some load. I was not able to reproduce this problem with kde running > >afterwards. > > It think it seems better (hard to be sure) but the issue is still there > for me. > > GNOME/Metacity > Single Processor Athlon Tbird > IDE Disk > USB Mouse (moused running) > AGP Radeon 9000 (using drm) > > -Wade > After updating to revision 1.58 of src/sys/kern/sched_ule.c and giving my system a good run for a few hours, things seem much better. There is still lag, but it is only occasional and rarely as severe as before. Windowmaker, TBird 1200, IDE disk, PS/2 mouse, NVIDIA driver. Probably not as taxing as Wade's GNOME setup. -- Munish Chopra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sound no longer works ... ?
On 2003-10-24 23:39 -0300, Marc G. Fournier wrote: > > Just noticed that sound isnt' working on my laptop since my last upgrade > (Oct 16), and one of our desktop's at the office is exhibiting the same > thing ... > > Just CVSup new sources, and see nothing sound related having changed since > my last one, so is this an isolated thing that nobody else is seeing? Sound's been working on all my builds, the latest one being from Oct 21. I've got a few SBxxx's, mainly Ensoniq chipsets. -- Munish Chopra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Best Way To Get to current -CURRENT
On 2003-11-04 19:51 -0800, Jeffrey Katcher wrote: > I have a new system (IBM ThinkPad T40 (gorgeous, too :)). In order to use > the WiFi card (ath) I need to install -current. What's the accepted best way? > 1) Install 5.1-RELEASE and cvsup from there. > 2) Install 5-1-CURRENT snapshot and cvsup to "real" current. > 3) Something else I haven't thought of. > Though there is no real best practice, I prefer to install a recent JPSNAP and take it from there. -- Munish Chopra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: acpi
On 2003-11-08 09:52 +0300, Konstantin Volevatch wrote: > Why acpi.ko module missed after latest CVS update? > Read UPDATING, or check the last few days worth of -current archives. -- Munish Chopra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS-UP new statfs structure
On 2003-11-14 21:50 +, Matt Smith wrote: > > The only thing I've found a problem with so far is postfix as I've > mentioned. > > Matt. > While attempting a portupgrade of postfix, I realized ruby core dumps after the statfs stuff too (even after I rebuilt it). I'm a bit puzzled, anyone else seeing this or is it a pilot error? -- Munish Chopra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RELENG_4 to RELENG_5_1
On 2003-06-04 10:15 +, Matthew Gardiner wrote: > >> > > Just a quick question, what version of GCC is going to appear in FreeBSD > 5.1? I heard that it maybe GCC 3.2.3 and that GCC 3.3 (depending on its > stability) will be used for 5.2. Could someone either confirm or correct me > on this assumption? > > Matthew Gardiner According to the 5.2 TODO list it's GCC 3.3. -- Munish Chopra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Interest in nvidia-driver debugging on 5-*
On 2003-06-12 11:51 +, Evan Dower wrote: > I am highly interested in getting nvidia-driver to work well for FBSD, and > in particular my own computer. I do not have the expertise to hack on > either it or the kernel (yet), but I am eager to provide debugging > information. nvidia-driver frequently crashes my machine, so I expect that > my input could be valuable. Is anybody interested in my assistance? Is > anybody actively working on/with/around the nvidia-driver, or does the > license make that infeasible? > Thanks a bundle, > Evan Dower > Undergraduate, Computer Science > University of Washington > NVIDIA is handling everything to do with the driver. Expect a new release "shortly" *cough*. Until then, perhaps some of the information in the FAQ will help you: http://www.soulwax.net/nvidia/faq.shtml Good luck. -- Munish Chopra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nvidia-driver database?
On 2003-07-11 20:48 +, Evan Dower wrote: > We've been posting our success stories and problems for a few days now. Has > anybody tried to compile these sorts of things into some sort of database? > Maybe something keeping track of hardware, configuration details, and > performance (success or symptoms)? If not, is anyone interested in creating > one? I would but am not well equipped (in other words I don't know how). Is > there interest in something like this? Are there willing victi... I mean... > volunteers? > E > I'm maintaining the FAQ at http://www.soulwax.net/nvidia/faq.shtml (warning: not MSIE friendly). I'm slightly short on time for now, but if someone is willing to help me out I have no problem extending it to include something like what you're describing. -- Munish Chopra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NVidia driver stability?
On 2003-07-12 14:46 +, Evan Dower wrote: > After following all the instructions at > http://www.soulwax.net/nvidia/faq.shtml _very_ carefully and compiling > nvidia-driver WITH_FREEBSD_AGP, WITH_NVIDIA_HACKS, and with FORCE_AGP_RATE, > my system was dramatically slower and substantially _less_ stable. (I had > to switch to another computer to write this email). Interestingly, whenever > I compile the kernel without optimizations, network activity becomes _very_ > slow. > E > aka Evan Dower > Undergraduate, Computer Science > University of Washington > Did you try using the NVIDIA AGP interface? The majority of mail I get indicates that the NVIDIA AGP stuff works better than the FreeBSD one. I'm not sure about your network problems, perhaps you should look at the driver for clues. -- Munish Chopra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NVidia driver stability?
On 2003-07-12 21:22 +, Will Saxon wrote: > Well I have to say that about 30min after I wrote in originally, I started having > problems. X locked up, but I could switch around to different vty's and also > ctrl-alt-bksp out of X. However, when I tried to restart X my machine locked up > entirely. > > I am wondering though if it is all the nvidia driver's fault - while my machine has > been stable through installation of the nvidia driver it is now being screwy even > after removal of the driver. It's basically locking hard after about 5-10 minutes > every time I use it, and sometimes I cannot even log in. I guess I don't know what > to think. > > -Will > If you have a kernel.good around boot that, and try fiddling around. There are a few sysctls you can play with (trying to use the NVIDIA AGP driver may be a good idea too). I have had a few really odd bug reports, but none that match this type of behaviour. -- Munish Chopra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NVidia driver stability?
On 2003-07-13 01:47 +, Evan Dower wrote: > That may have done it. Now that I recompiled nvidia-driver only > WITH_NVIDIA_HACKS, doing glxinfo several times no longer wreaks havoc. > Since something seems to be screwy with my network driver (rtl8139) when > the kernel is compiled without optimizations, I recompiled with them and so > far all is well. At the moment, I have my AGP rate knocked down from 4x to > 2x in BIOS. If all continues to go well, I'll bump it back up and report > what I find. > E > Bill Paul recently checked in some changes to the rtl8139 code, you might want to check the CVS logs for that. Bumping up the AGP rate should be safe in 99% of cases. Good luck. -- Munish Chopra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Kernel Panic and Automagic Reboots
On Tue, Jun 11, 2002 at 09:13:44AM -0700, Edwin Culp wrote: > > My laptop is rebooting with todays current/kernel in ifconfig. I just > got it up with an old kernel and am checking now. It will run with the > new kernel if I don't try to configure the network. I may have something > wrong though. > Same thing happens to me, reboot during the startup process when ifoncfig tries to get iself an IP from the dhcp server. I didn't have the time to write down the entire thing, but I'll try to get to it tonight. -- Munish Chopra The FreeBSD NVIDIA Driver Initiative http://nvidia.netexplorer.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Crash after world/kernel upgrade
On Tue, Jun 11, 2002 at 12:28:48PM -0500, Steve Ames wrote: > > You got way more info than I did. With this mornings -CURRENT (around 9AM EDT): > > Jun 11 09:22:10 : Doing initial network setup: > Jun 11 09:22:10 : host.conf > Jun 11 09:22:10 : hostname > Jun 11 09:22:10 : . > Jun 11 09:22:10 : > Jun 11 09:22:10 : > Jun 11 09:22:10 : Fatal trap 12: page fault while in kernel mode > Jun 11 09:22:10 : fault virtual address = 0x28 > Jun 11 09:22:10 : fault code = supervisor read, page not present > Jun 11 09:22:10 : instruction pointer = 0x8:0xc01851c1 > Jun 11 09:22:10 : stack pointer = 0x10:0xd7865bdc > Jun 11 09:22:10 : frame pointer = 0x10:0xd7865bec > Jun 11 09:22:10 : code segment= base 0x0, limit 0xf, type 0x1b > Jun 11 09:22:10 : = DPL 0, pres 1, def32 1, gran 1 > Jun 11 09:22:10 : processor eflags= interrupt enabled, resume, IOPL = 0 > Jun 11 09:22:10 : current process = 11 (swi1: net) > Jun 11 09:22:10 : trap number = 12 > Jun 11 09:22:10 : panic: page fault > Jun 11 09:22:10 : > Jun 11 09:22:10 : syncing disks... panic: bdwrite: buffer is not busy > Jun 11 09:22:10 : Uptime: 3s > Jun 11 09:22:10 : pfs_vncache_unload(): 1 entries remaining > Jun 11 09:22:10 : Terminate ACPI > Jun 11 09:22:10 : Automatic reboot in 15 seconds - press a key on the console to >abort > My bad, this is exactly what I was referring to in the other thread. -- Munish Chopra The FreeBSD NVIDIA Driver Initiative http://nvidia.netexplorer.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Total lockup
On Wed, Jun 12, 2002 at 06:14:24PM +0200, John Angelmo wrote: > Hello > > I updated world yesterday afternoon now everything bootsup just fine > But after I have done dhclient and my card (rl0 or wi0) got an IP an I > want to check it with ifconfig I get a total lockup this appens if I try > to use startx after I have aquierd an IP > > anyone got any idea? > > /John This is currently being covered in another thread on this list (unless someone picks it up here again that is). -- Munish Chopra The FreeBSD NVIDIA Driver Initiative http://nvidia.netexplorer.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: GCC upgrade ? on -current
On 2002-06-25 12:44 +, Sid Carter wrote: > Hi, > > Just a query. Is there anything stopping us from moving to the > latest gcc on current ? Just curious. Cause mozilla won't compile with > gcc from current and I have installed gcc from the ports just for that. > > Thanks > Regards > Sid Not exactly an answer to your question, but about a week ago or so a patch was posted that lets you compile mozilla with the system gcc. I tried it out and am now happily running mozilla 1.0. At least that's a short-term fix for you. -- Munish Chopra The FreeBSD NVIDIA Driver Initiative http://nvidia.netexplorer.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
error in /usr/src/gnu/usr.bin/binutils/doc/
Sources checked out today, 3AM EST. makeinfo --no-validate -I /usr/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/gas/doc -I /usr/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/ld -I /usr/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/bfd/doc -I /usr/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/binutils -I /usr/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb/gdb/doc -I /usr/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb/gdb/mi -I /usr/src/gnu/usr.bin/binutils/doc/../../../../contrib/libreadline/doc --no-split -I /usr/src/gnu/usr.bin/binutils/doc -I /usr/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils /usr/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/binutils/binutils.texi -o binutils.info ln -sf /usr/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb/gdb/doc/all-cfg.texi gdb-cfg.texi echo "@set GDBVN `sed q /usr/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb/gdb/version.in`" > GDBvn.texi cp /usr/src/gnu/usr.bin/binutils/doc/../../../../contrib/libreadline/doc/hsuser.texinfo inc-hist.texinfo patch -b .orig < /usr/src/gnu/usr.bin/binutils/doc/inc-hist.diff makeinfo: Removing output file `gdbint.info' due to errors; use --force to preserve. *** Error code 2 Hmm... Looks like a unified diff to me... The text leading up to this was: -- |$FreeBSD: src/gnu/usr.bin/binutils/doc/inc-hist.diff,v 1.4 2002/07/01 07:58:18 sheldonh Exp $ | |--- inc-hist.texinfo.orig Wed Apr 11 08:20:01 2001 |+++ inc-hist.texinfo Wed Apr 11 08:21:57 2001 -- Patching file inc-hist.texinfo using Plan A... Hunk #1 succeeded at 26. Hunk #2 succeeded at 39. done 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error Doing a simple 'make' in the directory is fine, so I guess the buildworld is pulling different stunts. I'd make the effort to track it, but I'm too tired, maybe someone else will catch it in the morning or so. -- Munish Chopra The FreeBSD NVIDIA Driver Initiative http://nvidia.netexplorer.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: KSE M-III status & junior hacker project.
On 2002-07-07 11:46 +, Josef Karthauser wrote: > > I've absolutely no idea what's causing it, but I'm still having random reboots > of current after some uptime with no dumps. I'll install a new kernel > today and report back if it still happens. Maybe someone can help me to > track it down. > Same happens to me, in addition the file systems aren't unmounted cleanly even if I manually shut down the machine. I built world with sources from around 11:30PM EST yesterday, and so far I've had only one random reboot (so I guess it's 'partly fixed'), as opposed to one every hour on average. I only caught something useful on one of the reboots as I was hanging around the console for a while: panic: lockmgr: draining against myself syncing disks... panic: bwrite: buffer is not busy ??? This was before my latest world/kernel. I'm about to build world again in the hope that something has fixed it. I'm assuming that my initial worries that KSE was causing this may be wrong and it's the vfs changes that have been going in lately (correct me if I'm way off here). -- Munish Chopra The FreeBSD NVIDIA Driver Initiative http://nvidia.netexplorer.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: "panic: lockmgr: locking against myself" with yesterday's -CURRENT
On 2002-07-07 06:01 +, David Wolfskill wrote: > I got the word about the changes to vfs_subr.c & vfs_bio.c fixing > the "hang" at shutdown for yesterday's -CURRENT fairly late in the > day yesterday, and since the problem didn't seem (as far as I could > tell) to affect normal operation, I figured I'd just pick up the > change at the following update (which would be this morning). > > However, once I started the "make -j8 buildworld" on this SMP machine > (this morning), I got a panic. Here's a cut-and-paste from the > serial console: > > Recovering vi editor sessions:. > Initial rc.i386 initialization:. > Configuring syscons: blanktime. > Additional ABI support:. > Local package initiCalization:reating DISK md10 > md10: invalid primary partition table: no magic > md10: invalid primary partition table: no magic > [1] 232 Floating point exception (core dumped) > Jul 7 05:41:21 freebeast kernel: pid 232 (newfs), uid 0: exited on signal 8 (core >dumped) > apache cvsupd > . > Additional TCP options:. > Starting background filesystem checks > > Sun Jul 7 05:41:23 PDT 2002 > > FreeBSD/i386 (freebeast.catwhisker.org) (cuaa0) > > login: panic: lockmgr: locking against myself This is exactly what's showing up for me (and possibly others) in the "KSE M-III status & junior hacker project." thread. I'm currently building world too (this is a UP machine btw.), I guess we'll see if the most recent commits change this. -- Munish Chopra The FreeBSD NVIDIA Driver Initiative http://nvidia.netexplorer.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
mergemaster failure
I first saw this a while ago (10 days?) but thought I'd screwed
something up myself. Didn't get a chance to clean the box up fully and
try again until this morning. After a successfull buildworld, trying to
do a mergemaster, this happens:
# mergemaster -i
mergemaster: not found
# /usr/sbin/mergemaster -i
*** The directory specified for the temporary root environment,
/var/tmp/temproot, exists. This can be a security risk if untrusted
users have access to the system.
Use 'd' to delete the old /var/tmp/temproot and continue
Use 't' to select a new temporary root directory
Use 'e' to exit mergemaster
Default is to use /var/tmp/temproot as is
How should I deal with this? [Use the existing /var/tmp/temproot]
*** Leaving /var/tmp/temproot intact
*** Creating the temporary root environment in /var/tmp/temproot
*** /var/tmp/temproot ready for use
*** Creating and populating directory structure in /var/tmp/temproot
set - `grep "^[a-zA-Z]" /usr/src/etc/locale.deprecated`; while [ $# -gt 0 ] ; do
for dir in /usr/share/locale /usr/share/nls /usr/local/share/nls; do test -d
/var/tmp/temproot/${dir} && cd /var/tmp/temproot/${dir}; test -L "$2" && rm -rf "$2";
test \! -L "$1" && test -d "$1" && mv "$1" "$2"; done; shift; shift; done
mtree -deU -f /usr/src/etc/mtree/BSD.root.dist -p /var/tmp/temproot/
mtree:No such file or directory
*** Error code 1
Stop in /usr/src/etc.
*** FATAL ERROR: Cannot 'cd' to /usr/src/etc and install files to
the temproot environment
/usr/src/etc exists, so does the temproot. I've tried nuking the
temproot too, nothing helps. Did I miss out on something or are other
people seeing this?
If it at all matters (can't see why), UP Thunderbird 1200.
uname -a:
FreeBSD CPE0030ab0ef2bb.cpe.net.cable.rogers.com 5.0-CURRENT FreeBSD 5.0-CURRENT #0:
Fri Jul 12 16:38:29 EDT 2002
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/ARCADIA i386
Any insights would be appreciated.
--
Munish Chopra The FreeBSD NVIDIA Driver Initiative
http://nvidia.netexplorer.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
panic: bdwrite: buffer is not busy
I've been having inexplicable crashes for a while and finally got around to getting a debug kernel and checking out what's going on, so here goes (apologies for the ^M's and all, I scripted a gdb session and that's what I got...): panic: bdwrite: buffer is not busy panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0xc1ca20f4 fault code = supervisor write, page not present instruction pointer = 0x8:0xc01d9b60 stack pointer = 0x10:0xd1e20a7c frame pointer = 0x10:0xd1e20a94 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 828 (smtpd) trap number = 12 panic: page fault syncing disks... panic: bdwrite: buffer is not busy Uptime: 43m45s Dumping 256 MB ata0: resetting devices .. done 16 32[CTRL-C to abort] 48[CTRL-C to abort] 64 80 96 112 128 144[CTRL-C to abort] 160[CTRL-C to abort] 176 192 208 224 240 --- #0 0x in ?? () (kgdb) hw where #0 0x in ?? () (kgdb) quit I've caught a few of these by hand while working in the console before, but thought they'd been resolved until now. FreeBSD CPE0030ab0ef2bb.cpe.net.cable.rogers.com 5.0-CURRENT FreeBSD 5.0-CURRENT #2: Sun Jul 14 20:26:50 EDT 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ARCADIA i386 The sources are from about 1800 EST, July 14. -- Munish Chopra The FreeBSD NVIDIA Driver Initiative http://nvidia.netexplorer.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: bdwrite: buffer is not busy
And another one comes along: GNU gdb 5.2.0 (FreeBSD) 20020627 Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-undermydesk-freebsd"... panic: bdwrite: buffer is not busy panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0xc2601cf4 fault code = supervisor write, page not present instruction pointer = 0x8:0xc01d9b60 stack pointer = 0x10:0xd1efba7c frame pointer = 0x10:0xd1efba94 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 53252 (smtpd) trap number = 12 panic: page fault syncing disks... panic: bdwrite: buffer is not busy Uptime: 18h49m23s Dumping 256 MB ata0: resetting devices .. done 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 --- #0 0x0000 in ?? () -- Munish Chopra The FreeBSD NVIDIA Driver Initiative http://nvidia.netexplorer.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: bdwrite: buffer is not busy
Third one: GNU gdb 5.2.0 (FreeBSD) 20020627 Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-undermydesk-freebsd"... panic: bdwrite: buffer is not busy panic messages: --- panic: bad pte syncing disks... panic: bdwrite: buffer is not busy Uptime: 3h37m11s Dumping 256 MB ata0: resetting devices .. done 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 --- #0 0x in ?? () Does anyone know what is going on or how I can get some more information out of this dump to track this down? I'd really like to resolve this... -- Munish Chopra The FreeBSD NVIDIA Driver Initiative http://nvidia.netexplorer.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: bdwrite: buffer is not busy
After rebuilding world/kernel/debug today I get some better info (I fear
my debug kernel was out of synch with my running kernel before, but
because of my inexperience with debugging I didn't figure that out right
away):
GNU gdb 5.2.0 (FreeBSD) 20020627
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-undermydesk-freebsd"...
panic: bdwrite: buffer is not busy
panic messages:
---
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xc227e6f4
fault code = supervisor write, page not present
instruction pointer = 0x8:0xc01db660
stack pointer = 0x10:0xd1f9ba7c
frame pointer = 0x10:0xd1f9ba94
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 55992 (smtpd)
trap number = 12
panic: page fault
syncing disks... panic: bdwrite: buffer is not busy
Uptime: 3h49m4s
Dumping 256 MB
ata0: resetting devices .. done
16 32 48 64 80 96 112 128 144 160 176 192 208 224 240
---
#0 doadump () at ../../../kern/kern_shutdown.c:213
213 dumping++;
(kgdb) where
#0 doadump () at ../../../kern/kern_shutdown.c:213
#1 0xc01bb513 in boot (howto=260) at ../../../kern/kern_shutdown.c:345
#2 0xc01bb71b in panic () at ../../../kern/kern_shutdown.c:491
#3 0xc01f8bdd in bdwrite (bp=0x104) at ../../../kern/vfs_bio.c:947
#4 0xc026b28d in ffs_update (vp=0xc1de5b58, waitfor=0) at
../../../ufs/ffs/ffs_inode.c:125
#5 0xc027df77 in ffs_fsync (ap=0xd1f9b8f4) at ../../../ufs/ffs/ffs_vnops.c:272
#6 0xc027c308 in ffs_sync (mp=0xc1c1ce00, waitfor=2, cred=0xc0ef6f00, td=0xc032e080)
at vnode_if.h:463
#7 0xc0209e43 in sync (td=0xc032e080, uap=0x0) at ../../../kern/vfs_syscalls.c:127
#8 0xc01bb19c in boot (howto=256) at ../../../kern/kern_shutdown.c:254
#9 0xc01bb71b in panic () at ../../../kern/kern_shutdown.c:491
#10 0xc02c596e in trap_fatal (frame=0x100, eva=0) at ../../../i386/i386/trap.c:845
#11 0xc02c565c in trap_pfault (frame=0xd1f9ba3c, usermode=0, eva=3257394932)
at ../../../i386/i386/trap.c:759
#12 0xc02c50b7 in trap (frame=
{tf_fs = 24, tf_es = 16, tf_ds = 16, tf_edi = 0, tf_esi = -1042227796, tf_ebp =
-772162924, tf_isp = -772162968, tf_ebx = -1037572416, tf_edx = 180, tf_ecx =
-1040183148, tf_eax = -1037572368, tf_trapno = 12, tf_err = 2, tf_eip = -1071794592,
tf_cs = 8, tf_eflags = 66118, tf_esp = -1070377308, tf_ss = -772162904})
at ../../../i386/i386/trap.c:445
#13 0xc02b73a8 in calltrap () at {standard input}:98
#14 0xc01f1269 in sowakeup (so=0xc1e0ddac, sb=0xc227e6c0) at
../../../kern/uipc_socket2.c:300
#15 0xc01f0e51 in soisconnected (so=0xc2096640) at ../../../kern/uipc_socket2.c:132
#16 0xc01f6c1d in unp_connect2 (so=0x0, so2=0xc1e0dd48) at
../../../kern/uipc_usrreq.c:769
#17 0xc01f6b7b in unp_connect (so=0xc24a6578, nam=0xc25bb300, td=0x0) at
../../../kern/uipc_usrreq.c:737
#18 0xc01f5c7e in uipc_connect (so=0x0, nam=0x0, td=0xc204d9c0) at
../../../kern/uipc_usrreq.c:161
#19 0xc01eee21 in soconnect (so=0xc2096640, nam=0x0, td=0x0) at
../../../kern/uipc_socket.c:429
#20 0xc01f2bcb in connect (td=0x0, uap=0xc1e0dd48) at ../../../kern/uipc_syscalls.c:441
#21 0xc02c5c70 in syscall (frame=
{tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 11, tf_esi = 0, tf_ebp =
-1077938120, tf_isp = -772162188, tf_ebx = 134704296, tf_edx = 2, tf_ecx = 0, tf_eax =
98, tf_trapno = 22, tf_err = 2, tf_eip = 671913163, tf_cs = 31, tf_eflags = 582,
tf_esp = -1077938276, tf_ss = 47}) at ../../../i386/i386/trap.c:1049
#22 0xc02b73dd in syscall_with_err_pushed () at {standard input}:128
---Can't read userspace from dump, or kernel process---
If there's anything else than this I can provide, pleas let me know.
--
Munish Chopra
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: make buildworld crashing
On 2002-07-29 20:15 +, karl agee wrote: > I just updated my source and running make buildworld crashes here: > > cd /usr/src/usr.bin/makewhatis; make DIRPRFX=usr.bin/makewhatis/ obj; > make DIRPRFX=usr.bin/makewhatis/ depend; make > DIRPRFX=usr.bin/makewhatis/ all; make DIRPRFX=usr.bin/makewhatis/ > DESTDIR=/usr/obj/usr/src/i386 install > /usr/obj/usr/src/i386/usr/src/usr.bin/makewhatis created for > /usr/src/usr.bin/makewhatis > make: don't know how to make bsd.README. Stop > *** Error code 2 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. cd /usr/src/share/mk && make install I believe (hope?) that fixes it. -- Munish Chopra To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: About 5.0 and Nvidia drivers
On 2002-08-03 12:14 +, Alp ATICI wrote: [snip] > > And what's the latest about the Nvidia drivers? It's mentioned that > Nvidia has plans to produce the drivers for FreeBSD. I'd be happy to know > what's going on in that issue too. > We know about as much as you do. Waiting for NVIDIA, once again. I'll fire off a mail to some of our contacts and ask, but I'm pretty sure it'll be more of the same we usually get. -- Munish Chopra To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Ports depending on forbidden compat3x?
On 2002-08-30 08:27 +, Craig Rodrigues wrote: > > [snip] > > The install failed because of the following: > >> Checksum OK for jre1.1.8i_ELF.V1999-11-9.tar.gz. > ===> jre-1.1.8 depends on shared library: c.3 - not found > ===>Verifying install for c.3 in /usr/ports/misc/compat3x > ===> compat3x-i386-5.0.20020219 is forbidden: FreeBSD-SA-02:28.resolv - buffer >overflow in resolver in libc. See also PR ports/42138. -- Munish Chopra To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Getting developer previews via cvsup?
On 2002-09-01 18:43 +, Andrew P. Lentvorski wrote: > I wanted to download via cvsup a snapshot of -current which I had a decent > chance of compiling (I need to look at some atacontrol RAID stuff). So I > tried to find a -current which had a recent tag, the comment was made that > DP2 just got a tag, but even a DP1 tag would do. > > What should that tag be? Even a date tag would be useful (-current was in > pretty good shape as of MM/DD/. Give it a try.), but I can't seem to > find *anything* even after Googling for about an hour. > > Thanks, > -a > IIRC, current was in good shape between August 12-15, 17, 18, 22-24. I'm probably a day or two off on a few but it's a decent guess. A cvsup from about an hour and a half ago is performing fine so far, with the new gcc imported. *Very* smooth transition, FWIW :) -- Munish Chopra To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: is src/UPDATING up to date
On 2002-10-25 07:28 +, Mathieu Arnold wrote: > Hi > > I was twiddling with my yesterday's current, I was trying to make release > to see how things were going, and I saw at the top of UPDATING that : > > In addition, IDE write caching is currently disabled by default > due to on-going concerns about disk write order and file system > integrity. Re-enabling write caching can substantially improve > performance. > This part of the performance disclaimer has been untrue for a while now. It is once again enabled by default. > I looked at ata(4), told me about hw.ata.wc, which was supposed to be > enabled by default, and it was, so, my question is, is the comment above > still true, and how do I enable write cache if it is, if it's not true any > more, maybe it should be removed. > As stated, it's untrue. You can check the status of write caching by using the sysctl(8) facility. You're looking for hw.ata.wc. It'd probably be a good idea for someone to nuke that paragraph... -- Munish Chopra To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: questions about the state of current
On 2002-10-29 11:40 +, Raymond Kohler wrote: > I'm now a stable user, and I'm considering moving to current to get a jump on >upgrading and help with the testing effort. I have some questions about its >performance: > > 1) How is the speed compared to stable? I remember it being just too slow some >months ago and was wondering how it was improving. > I haven't been on -STABLE for a long time now, but other comments seem to suggest that any performance hit being experienced is negligible. > 2) Are the random hangs in X fixed yet? I can put up with a few issues (it is >current, after all), but that's just too much to bear. > X has caused me zero trouble over the past ten months on -CURRENT, partly because I was lucky to have it compiled and working at the right time, partly 'just because'. I've had far more trouble with other things that just came from having built world at a time when things were unstable. > 3) Are there any Very Important Packages (mozilla, kde, &c) that won't build or >refuse to work right? > Mozilla builds fine, I build phoenix out of cvs a few times a week. I don't use KDE, but others seem to have it working fine. My -CURRENT box is my primary desktop, I have about 200 ports installed of various size and complexity. Besides noticing the odd breakage of a port and submitting a patch/PR, it hasn't been much trouble. Just remember to read the -current list frequently. -- Munish Chopra To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New NVidia drivers on -current
On 2002-11-18 01:29 +, Mikhail Teterin wrote: > Has anyone tried them yet? After removing the #error triggered by > __FreeBSD_version being over 50, I got the thing nvidia.ko to build, > but: > > 00:50:30 aldan shutdown: reboot by root: New world, kernel. Nvidia drivers > 00:56:12 aldan kernel: Preloaded elf module "/boot/kernel/nvidia.ko" at 0xc06470b0. > 00:56:12 aldan kernel: VESA: NVidia > 00:56:12 aldan kernel: VESA: NVidia Corporation NV15 Reference Board Chip Rev A0 > 00:56:14 aldan kernel: nvidia0: mem >0xf000-0xf7ff,0xe900-0xe9ff irq 11 at device 0.0 on pci1 > 00:56:14 aldan kernel: pcib1: device nvidia0 requested decoded memory range >0xe900-0xe9ff > 00:56:14 aldan kernel: pcib1: device nvidia0 requested unsupported memory range >0x0-0xe9ff (decoding 0xe900-0xe9ff, 0xf000-0xf7ff) > 00:56:14 aldan kernel: nvidia0: Unable to allocate NVIDIA memory resource. > 00:56:14 aldan kernel: device_probe_and_attach: nvidia0 attach returned 6 > > Any clues, or is, indeed, a major porting effort required to get it to > work on -current? Thanks! > > -mi > http://www.thirteenandtwo.org/nvidia/faq.html The box is currently down, since somone decided to upgrade it to -CURRENT and messed up, but Marc Fonvieille was nice enough to put it up here until tomorrow or so: http://people.freebsd.org/~blackend/nvidia/faq.html (missing style sheet, but oh well). Basically it works fine on -CURRENT, what you are seeing could be because you have something interfering (anything from ACPI to some old ISA device), but most likely you are missing SYSVSHM or don't have sufficiently new X binaries (you need 4.2.1 -Servers, -clients and -libraries). If none of the above works, mdodd@ can most likely give you a better answer. -- Munish Chopra To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New NVidia drivers on -current
On 2002-11-17 23:53 +, Kris Kennaway wrote: > > [...] > > Try putting this in your loader.conf: > > hw.pci.allow_unsupported_io_range=1 > > This allowed the device to probe for me, but the system locks up when > I try and start X. > Do you by any chance either have an SiS chipset or a regular TNT (or both)? -- Munish Chopra To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: OpenOffice and FreeBSD 5.0-Current
On 2002-11-24 23:33 +, Yann Berthier wrote: > On Sun, 24 Nov 2002, a wrote: > > > Hi > > > > I am running FreeBSD 5.0-CURRENT (22 Nov 22:52 CET) > > I did a download of a precompiled OpenOffice 1.0.1_4 package (it is for FreeBSD >Current) and installed that one with "pkg_add". > > Ok, that one went fine. > > But after that, i was not able to start OpenOffice. I get an Segmentation fault, >and thats it. > >Have you procfs mounted ? if not you should: this is mandatory to use >openoffice (/proc is not mounted by default in the -current land) > Yes, as the README says, procfs is necessary for now. Is there any update on when this dependency will be kicked out? Martin? -- Munish Chopra To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [Where] is OpenOffice 1.0.1_4 package available?
On 2002-11-25 06:09 +, Daniel Flickinger wrote: > package OpenOffice 1.0.1_4 is not available on > snapshot and there is no FreeBSD copy on > OpenOffice.org... > > where does it reside? http://projects.imp.ch/openoffice/ > > I would compile it, but I would need to reorganize > one of my disks and relabel for the 4 gig partition > stated as required to compile it. > > If mozilla-1.1_1,1 is currently installed, does it need > to be reinstalled with OpenOffice, or should I just go > ahead and upgrade to mozilla-1.1_2,1? Err, I think it'll be fine to just upgrade. Don't shoot me if I'm wrong though. -- Munish Chopra To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [Where] is OpenOffice 1.0.1_4 package available?
On 2002-11-25 08:30 +, [EMAIL PROTECTED] wrote: > > http://projects.imp.ch/openoffice/ > > But, i tried to install that package on my FreeBSD 5.0-CURRENT, well it > went fine, but when i try to run openoffice, i will get a "Segmentation > fault". > Hope you will have more luck. As it says in the README, you need procfs to run it. This dependency will supposedly be removed in the (near?) future. -- Munish Chopra To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
buildkernel broken
cvsup about three hours ago, buildkernel fails with: ===> uplcom cc -O -pipe -march=k6 -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/dev -I@/../include -fno-common -mpreferred-stack-boundary=2 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -c /usr/src/sys/modules/uplcom/../../dev/usb/uplcom.c /usr/src/sys/modules/uplcom/../../dev/usb/uplcom.c:206: `USB_PRODUCT_RATOC_REXUSB60' undeclared here (not in a function) /usr/src/sys/modules/uplcom/../../dev/usb/uplcom.c:206: initializer element is not constant /usr/src/sys/modules/uplcom/../../dev/usb/uplcom.c:206: (near initialization for `uplcom_products[5].product') *** Error code 1 Stop in /usr/src/sys/modules/uplcom. *** Error code 1 uname of current system: FreeBSD rn-re116a13.uwaterloo.ca 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Feb 28 18:44:28 EST 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ARCADIA i386 -- Munish Chopra The FreeBSD NVIDIA Driver Initiative http://nvidia.netexplorer.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pop3 email client
On Fri, Mar 29, 2002 at 03:07:18PM +0100, Bob Kersten wrote: > Hi, > > I was wondering if there's a pop3 e-mail client available that you > can recommend. I want it to run in textmode, thus not in Xfree86 or > anything, but the mail command is just not sufficient. I like it to > have graphical elements such as /stand/sysinstall uses. > > Bob. > This really belongs on -questions... A lot of people (such as me) prefer to use fetchmail to get our mail from POP3 servers (or other types of servers that fetchmail supports). To read mail, I personally use mutt. It's highly configurable, and deals nicely with mailing lists and such. Both fetchmail and mutt are in ports. -- Munish Chopra The FreeBSD NVIDIA Driver Initiative http://nvidia.netexplorer.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mouse in Xfree86 4.2.0
On Mon, Apr 15, 2002 at 10:02:33AM +0200, John Angelmo wrote: > Hello > > When I start XFree86 I get the error that /dev/mouse can't be found, OK > devfs seems to be installd so MAKEDEV dosn't exist anymore, is there > anyway to get /dev/mouse working as in FreeBSD 4? > > Thanks > > /John Set your mouse as being /dev/sysmouse in your XF86Config. -- Munish Chopra The FreeBSD NVIDIA Driver Initiative http://nvidia.netexplorer.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
