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
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
p 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
p 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
t). 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 Cho
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
rotected 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
;>
>> 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 c
t 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
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
>
> --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]"
d 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 al
HED_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 probabl
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
_
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
_
napshot 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
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 lis
). 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]"
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]"
ndergraduate, 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/n
g 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
___
>
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
od 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]"
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 unsub
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
... 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 e
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
gt;
> 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
rror
*** 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
rnel. 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 F
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 curren
o, 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 ins
86
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
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
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 C
= 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
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
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
r 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
> -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 :)
--
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
ek. 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 -cur
es).
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
ither 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
ounted 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
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
ill 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
de 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 Driv
e 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
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
50 matches
Mail list logo
