RE: questions on S-ATA and ICH5 (now owns hardware :)
> Yeah. My drive shows up as UDMA133 also. What I did notice is that > my WD Raptor was slightly outperformed a few times on UFS2 by > my actual > ATA-100 Western Digital drive. This seems somewhat bad as the Raptor > costs a hell of a lot more and one would hope that it would pound the > ATA-100 drive pretty thoroughly. > > Even the CPU overheads on both drives were about the same. Maybe its > that > 8MB caching :). I haven't found a good reason yet. Keep in mind that you are dealing with 36GB vs. 60 or 80GB platter density. The Raptor ought to be quicker but the older WD drive could be faster. Especially in long sequential reads. -Will ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: NVidia driver stability?
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 > -Original Message- > From: Munish Chopra [mailto:[EMAIL PROTECTED] > Sent: Saturday, July 12, 2003 5:57 PM > To: [EMAIL PROTECTED] > Subject: 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]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: NVidia driver stability?
I just installed these drivers on my machine, which uses a Geforce4 Ti4200. I had 10 glxgears processes running in the background and was running glxinfo over and over, and while the glxgears processes were not really spinning very fast nothing crashed or anything like that. Machine is running a June 27 -current with Xfree86 4.3.0. I compiled the nvidia-driver port with -DWITH_FREEBSD_AGP and -DWITH_NVIDIA_HACKS. -Will ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Heads up: checking in change to ata-card.c
> -Original Message- > From: Julian Elischer [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 26, 2003 7:26 PM > To: Will Saxon > Cc: David Xu; Soeren Schmidt; Bill Paul; [EMAIL PROTECTED]; > [EMAIL PROTECTED] > Subject: RE: Heads up: checking in change to ata-card.c > > > Nvidia (I previously didn't know they made full chipsets) > IDE interfaces got broken around FreeBSD 4.3 and at 4.8 they are still > not working.. There is however a workaround which is to > disable the use > of DMA on the devices (in the loader.conf file). if you don't > the system > hangs during boot. > > I have only sporadic access to one, but I don't have one myself which > makes it hard to > test more.. > I have not tested it on 5.x yet.. Well I am pretty sure this isn't an Nvidia chipset, actually I know it isn't: atapci0: port 0xb000-0xb00f at device 17.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ad0: 9797MB [19906/16/63] at ata0-master UDMA66 acd0: MODE_SENSE_BIG command timeout - resetting ata1: resetting devices .. done ..repeat 19 more times.. acd0: CDROM at ata1-master PIO4 Maybe there are some similarities though - Nvidia seemed to just pull a good chipset out of nowhere a couple of years ago, maybe they licensed some stuff from Via? I know they worked a lot on the Xbox but that is an Intel system - the nForce stuff is AMD-only. I have 4 operable machines, 3 of them working with this 694D board, the other (ironically) a 230T also (which is working fine with a 4.8-PRERELEASE kernel from 2/19). In a few weeks they will all be replaced by new P4 machines and I should have the ability to basically do whatever I want with them. So if this turns into a protracted issue that requires testing, I will be more than happy to test patches for 4.x and 5.x, single and dual processor. -Will > > > > On Thu, 26 Jun 2003, Will Saxon wrote: > > > > > > > > -Original Message- > > > From: David Xu [mailto:[EMAIL PROTECTED] > > > Sent: Thursday, June 26, 2003 6:30 PM > > > To: Soeren Schmidt; Bill Paul > > > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] > > > Subject: Re: Heads up: checking in change to ata-card.c > > > > > > > > > I have another problem different with Bill Paul's. > > > I have a Tyan Tiger 230T dual CPU MB. On second IDE, > > > there are MITSUBISHI 52X CDROM as master and a SONY > > > CD-RW CRX140E 8X/4X/32X as slave. FreeBSD never got > > > them to work, while MS Windows and Linux and NetBSD and > > > OpenBSD all work well with these devices. FreeBSD always > > > stuck at "MODE SENSE BIG", this sucks, I must disable > > > second IDE in BIOS before booting into FreeBSD and > > > reenable it before booting into another OS. I changed > > > configuration several times, both DMA and PIO mode don't > > > work, it works only when CR-RW is pulled. > > > > > > David Xu > > > > I started seeing this behavior also, but it started when I > swapped drives from a dead Via dual chipset board machine > (MSI 694D Pro, I think) into an athlon machine with an Asus > A7Vsomething. I can get correct model numbers, etc. if > helpful. This is a 4.8-RELEASE installation. I had to reboot > the first time with an old 4.4 GENERIC leftover from > installation, and I saw no errors, but after compiling a > uniprocessor kernel I started seeing the above behavior. > Although, I left it for awhile and eventually the machine > does boot after about 30 of the MODE_SENSE_BIG, resetting > devices lines. > > > > -Will > > ___ > > [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: Heads up: checking in change to ata-card.c
> -Original Message- > From: David Xu [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 26, 2003 6:30 PM > To: Soeren Schmidt; Bill Paul > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: Heads up: checking in change to ata-card.c > > > I have another problem different with Bill Paul's. > I have a Tyan Tiger 230T dual CPU MB. On second IDE, > there are MITSUBISHI 52X CDROM as master and a SONY > CD-RW CRX140E 8X/4X/32X as slave. FreeBSD never got > them to work, while MS Windows and Linux and NetBSD and > OpenBSD all work well with these devices. FreeBSD always > stuck at "MODE SENSE BIG", this sucks, I must disable > second IDE in BIOS before booting into FreeBSD and > reenable it before booting into another OS. I changed > configuration several times, both DMA and PIO mode don't > work, it works only when CR-RW is pulled. > > David Xu I started seeing this behavior also, but it started when I swapped drives from a dead Via dual chipset board machine (MSI 694D Pro, I think) into an athlon machine with an Asus A7Vsomething. I can get correct model numbers, etc. if helpful. This is a 4.8-RELEASE installation. I had to reboot the first time with an old 4.4 GENERIC leftover from installation, and I saw no errors, but after compiling a uniprocessor kernel I started seeing the above behavior. Although, I left it for awhile and eventually the machine does boot after about 30 of the MODE_SENSE_BIG, resetting devices lines. -Will ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: cardbus and xircom ethernet problem
> -Original Message- > From: Matt [mailto:[EMAIL PROTECTED] > Sent: Monday, June 23, 2003 2:22 PM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Re: cardbus and xircom ethernet problem > My kernel config currently has: > > nodevicecbb > nodevicepccard > nodevicecardbus > device card 2 > device pcic > device xe > > The OLDCARD file actually does not have a number after device card, > however I found when trying to compile this it errors with > Device "card" > requires a count. I am unsure of what the "count" means so just put a > random number in there. > > Anything else I can try? Do try loading if_dc.ko or compiling that in again. -Will ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Buildkernel broken
> -Original Message- > From: Krzysztof Parzyszek [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 27, 2003 11:50 AM > To: [EMAIL PROTECTED] > Subject: Buildkernel broken > > > Hello, > > I cvsupped the source this morning and I get: > > [...] > ===> firewire/firewire > cc -O -pipe -march=pentium2 -D_KERNEL -Wall > -Wredundant-decls -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > -fformat-extensions -std=c99 -DKLD_MODULE -nostdinc -I- -I. > -I@ -I@/dev -I@/../include -fno-common -g > -mno-align-long-strings -mpreferred-stack-boundary=2 > -ffreestanding -Wall -Wredundant-decls -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > -Winline -Wcast-qual -fformat-extensions -std=c99 -c > /usr/src/sys/dev/firewire/firewire.c > cc -O -pipe -march=pentium2 -D_KERNEL -Wall > -Wredundant-decls -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > -fformat-extensions -std=c99 -DKLD_MODULE -nostdinc -I- -I. > -I@ -I@/dev -I@/../include -fno-common -g > -mno-align-long-strings -mpreferred-stack-boundary=2 > -ffreestanding -Wall -Wredundant-decls -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > -Winline -Wcast-qual -fformat-extensions -std=c99 -c > /usr/src/sys/dev/firewire/fwohci.c > In file included from /usr/src/sys/dev/firewire/fwohci.c:72: > @/dev/firewire/fwdma.h:38: redefinition of `bus_dmasync_op_t' > machine/bus_dma.h:94: `bus_dmasync_op_t' previously declared here > *** Error code 1 > > [...] > I have the exact same problem. I think it has something to do with a commit from this morning. I commented out the offending #define in fwdma.h and the module compiles fine now. -Will ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
mouse question
Hello, Not certain what list this ought to go to, perhaps -questions so I apologize if this is not the right one. I was wondering if there could be a way to 'force' a type of ps/2 mouse. I have a logitech firstmouse+, with a wheel. It works fine if it is plugged directly into the back of this machine. However, I have it running through a KVM switch so that I can have one mouse for both of my machines. When in this configuration, the wheel action never works (although it works on the other machine, which runs windows), and the button action sometimes also doesn't work (this is rare). When plugged into the switch, I get this: psm0: failed to get data. psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 When plugged directly into the machine the third line comes up with MouseMan+. I have tried to manipulate moused to account for the wheel by mapping the wheel events as extra buttons, and I have tried to do the same in XF86Config. Neither work. Not terribly important, but it would be nice to know if there is something I can do about it. -Will To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA timeout errors
Well, while this isn't a problem that causes panics or makes people unable to use their machines, I think maybe the removal of the older wd driver ought to be held off until the ata driver provides all the features wdc does don't you think? I guess the philosophy here is that there shouldn't be driver redundancy in a -RELEASE or something? I will continue to use ata because my drives work (albeit in PIO mode apparently) and I don't play audio off the cdrom. Some people will probably hold off on upgrading to 4.0 because of this, and I don't know if anyone important cares about that but imho it kind of looks bad. Just a thought. Again, my box works, just not as advertised :). Could very well be user error, I just don't know. -will On Tue, 14 Mar 2000, Kris Kennaway wrote: > On Tue, 14 Mar 2000, Patrik Sundberg wrote: > > > I also get this when booting - think it started happening when I started > > using the new ata-driver. For me it happens when the root is supposed to be > > mounted (from dmesg): > > > As you can see I am using a seagate disk and I am having the same problem. > > I've always had this problem with the new ata drivers (on a Western > Digital, though). Looks like it's just something we have to Deal With :-( > Plus, my CDROM doesn't do audio any more. > > Kris > > > In God we Trust -- all others must submit an X.509 certificate. > -- Charles Forsythe <[EMAIL PROTECTED]> > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ATA timeout errors
Hello, I think this may have already been presented/answered but I am not certain. I have noticed recently that every so often I will get the following set of messages, generally right after the bootup sequence finishes: ad0: READ command timeout - resetting ata0: resetting devices .. done ad0: READ command timeout - resetting ata0: resetting devices .. done ad0: READ command timeout - resetting ata0: resetting devices .. done ad0: READ command timeout - resetting ata0-master: WARNING: WAIT_READY active=ATA_ACTIVE_ATA ad0: trying fallback to PIO mode ata0: resetting devices .. done This latest episode is on a 5.0-Current machine cvsupped yesterday, I got those messages while trying to log in after a reboot. I dont get any panics or anything, and after the reset to PIO everything seems to work fine. ad0 is an IBM Deskstar 22GXP. I recall something about Deskstars resetting their heads every week as a possible explanation for a similar problem, is that what this is too? I would of course prefer to be in DMA mode all the time rather than PIO. If there is something I can do to fix this I'm all ears. -Will To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Error: no such 386 instruction: `state' ???
I was having this problem a few weeks ago while trying to make world. I
had just gotten a new motherboard, that was letting me overclock my
processor (it offered new bus speeds). I reset the processor to run at its
default speed, and I have not seen this error since.
So, if you are overclocked at all I would suggest trying to clock it down
a little.
-Will
On Mon, 6 Mar 2000, Devin Butterfield wrote:
> Hi,
>
> I'm running a snap from 2/28:
>
> FreeBSD dbm.wireless.net 4.0-2228-CURRENT FreeBSD 4.0-2228-CURRENT #2:
> Fri Mar 3 22:19:33 PST 2000
>
> Often when compiling a port, the process will fail with messages like
> the following:
>
> [...]
> Compiling smbd/noquotas.c
> Compiling smbd/reply.c
> {standard input}: Assembler messages:
> {standard input}:4939: Error: no such 386 instruction: `state'
> *** Error code 1
>
> Stop in /usr/ports/net/samba/work/samba-2.0.6/source.
> *** Error code 1
>
> Stop in /usr/ports/net/samba.
> *** Error code 1
>
> Stop in /usr/ports/net/samba.
> *** Error code 1
>
> Stop in /usr/ports/net/samba.
> *** Error code 1
>
> Stop in /usr/ports/net/samba.
> [root@dbm /usr/ports/net/samba]#
>
> The strange thing is, if I just say "make" again, it will continue to compile
> where it left off without any problems.
>
> Anyone else see these errors? Any Ideas?
> --
> Regards, Devin.
>
> P.S. Never had this problem under 3.x.
>
>
>
> 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: XFree 3.3.6 authentication failed?
Actually I think this is a pam.conf issue. You probably built 3.3.6 with PAM support? This happened to me as soon as 3.3.6 came out. try copying pam.conf from whereveryoubuildworld/etc to /etc and see if that fixes it. I think mergemaster would take care of this too, I dunno last time I used it it did more harm than good. -Will On Tue, 22 Feb 2000, Will Andrews wrote: > On Wed, Feb 23, 2000 at 02:10:00AM -0300, [EMAIL PROTECTED] wrote: > > Dear guys, > > > > I am running monday's current, Mesa-glx for Riva, XFree 3.3.6 and > > KDE 1.1.2. All from monday's ports tree. > > Well, I think I can't say I am running this system, for I am getting > > the following message whenever I try startx: > > > > Authentication failed - cannot start X server. > > Perhaps you do not have console ownership? > > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > > _X11TransSocketUNIXConnect: Can't connect: errno = 2 > > giving up. > > xinit: No such file or directory (errno 2): unable to connect to X server > > xinit: No such process (errno 3): Server error. > > > > Damn, I know this must be my mistake. However, I can't seem to get > > X up. However, /stand/sysinstall -> Configure -> XFree86 -> XF86Setup > > works smooth. Before you mention it: yeah, yeah, I tried startx as root > > against my best judgement; and no, it did not work. :) > > UCONSOLE is enabled. > > My .xinitrc follows at the end of this file. > > What am I missing? A new authentication system? My guess. I went > > through the FAQ and most of the simple docs; I must be overlooking something. > > Any and all help appreciated. Please CC: to [EMAIL PROTECTED], for I > > am subscribed to neither freebsd-questions nor freebsd-current. > > I apologize in advance for the CC: accross mailing lists. > > > > Regards, > > Mario Ferreira > > > > ps: Please, don't flame me. /dev/null appreciates it. Thanks again. > > 1) Do you have "XSERVER" option in kernel? I'm not sure if it's > required, but it might be. > > 2) You should start KDE with "startkde" not "kde". > > -- > Will Andrews <[EMAIL PROTECTED]> > GCS/E/S @d- s+:+>+:- a--->+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- > ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++> DI+++ D+ > G++>+++ e-> h! r-->+++ y? > > > 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: Crashing netscape?
You arent the only one, I have tried nestcape 4.08 and 4.7 navigator and both exit on signal 10 and coredump quite often. It happens in the middle of page rendering and also everytime I try to close the application (rare since I hardly ever get the chance to do that myself). I dont know why it does that. I can't seem to tell that there is any definite pattern to it, or that anything in particular triggers it. I just deal with it, and lately I just do most of my browsing on a different machine with a different OS :/. Trying Mozilla M13 now, and it doesnt seem to be as bad although it still doesnt render pages correctly most of the time. -Will On Mon, 21 Feb 2000, Alex Le Heux wrote: > Hi, > > Am I the only one who's experiencing an amzing amount of crashes on > Netscape? > > It's been going on for quite some time now (months), upgrading Netscape or > switching from the Linux to the FreeBSD to the BSDI version doesn't help. > The most stable version seems to be the Linux version, but that even > crashes 5-10 times per day. It will *always* crash when a page uses java, > but I've not been able to find a non-java page that will always crash it. > > Is it just me? All the people I know who run various versions of FreeBSD > say it's not so bad. > > Alex > > -- > "What is this talk of 'release'? We do not make software >'releases'. Our software 'escapes', leaving a > bloody trail of designers and quality assurance people in its > wake." > > > 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: Broken FTP
I was experiencing the same thing with EPRT commands... I cvsupped, remade/installed ftp, and haven't seen that behavior since. Someone mentioned it was IPv6 related but I have no idea if that is the case. -Will On Wed, 16 Feb 2000, Andrey A. Chernov wrote: > Current ftp client tries to put this unknown command on each remote > request: > 500 'EPSV': command not understood. > It is just too bothering. > Could it silently try once at the beginning and remember status during the > session? > > -- > Andrey A. Chernov > <[EMAIL PROTECTED]> > http://nagual.pp.ru/~ache/ > > > 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
strange buildworld problem (not xinstal related)
Hello,
I am experiencing a (to me) strange error while trying to
buildworld. Sources are current as of about noon today, and this has been
happening for the past few days.
cc -O -pipe -I/usr/src/gnu/lib/libobjc/../../../contrib/gcc/objc
-I/usr/src/gnu/lib/libobjc/../../../contrib/gcc
-I/usr/obj/usr/src/i386/usr/include -Wno-import -pg -c
/usr/src/gnu/lib/libobjc/../../../contrib/gcc/objc/Object.m -o Object.po
{standard input}: Assembler messages:
{standard input}:808: Error: no such 386 instruction: `state'
{standard input}:1568: Fatal error: Symbol yydebug already defined.
*** Error code 1
Stop in /usr/src/gnu/lib/libobjc.
*** Error code 1
I have build and installed world before on this machine, both -stable and
-current branches. The only thing that has changed recently is I have a
new motherboard (shouldn't make a difference?). Machine is AMD K6-2 based.
I'm not sure what's going on, I haven't seen anyone else complain about
this so it's probably something wrong with my installation, but I thought
I would relay it anyway.
-Will
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
