Re: STAROFFICE Broke?
On Wednesday 20 June 2001 14:23, Larry Rosenman wrote: > Interestingly, a REINSTALL of SO 5.2 from ports seemed to fix it, > after I mv'd all the old stuff away. > > This is really wierd.. > > LER > I had that problem a long time ago (moving from 4.2R to 4-stable, IIRC). I re-ran the user-install, and it recovered everything just fine. I had exactly the same symptoms though, locked up at the spash screen and refused to do anything else. I *did* discover that running it under a different login than my main login worked, and that's what lead me to run the end-user install again. It ran, found itself, and asked if I wanted to "uninstall" or "repair" the installation. I chose "repair" and haven't had any trouble since (including upgrades to 4.3R and then tracking back into 4-S). My (current) best guess is that somehow upgrading (cvsup) on a virtual terminal while having SOffice running on a different terminal/login caused something to break--perhaps in the make world stage, while rebuilding linux emulation?--, since I usually do this from the console, and I may have been logged in to X on a different screen at the time. mike > * Larry Rosenman <[EMAIL PROTECTED]> [010614 15:29]: > > * Mike Meyer <[EMAIL PROTECTED]> [010614 10:19]: > > > Larry Rosenman <[EMAIL PROTECTED]> types: > > > > On Thu, Jun 14, 2001 at 09:56:52AM -0500, Mike Meyer wrote: > > > > > Larry Rosenman <[EMAIL PROTECTED]> types: > > > > > > On Fri, Jun 15, 2001 at 12:50:13AM +1000, Kal Torak wrote: > > > > > > > Strange it was working fine after I cvsup'd about ~1 week > > > > > > > ago... > > > > > > > > > > > > Ok, so somewhere between ~1 week ago and yesterday Hmm. > > > > > > I just checked, and my last BuildWorld was 4Jun2001... > > > > > > > > > > Seems to start for me on a 10Jun2001 build. I don't normally use > > > > > it, so I can't say much beyond "it starts". > > > > > > > > Does it actually display it's screen? I just get the splash > > > > screen... > > > > > > Yup, it opens it's big window, and displays the icons in it. > > > > I opened a PR about it... > > > > KERN/28152 > > > > LER > > > > >> > -- > > > Mike Meyer <[EMAIL PROTECTED]>http://www.mired.org/home/mwm/ > > > Independent WWW/Perforce/FreeBSD/Unix consultant, email for more > > > information. > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: problems building mod_ruby
Update your ports and see if the problem persists. A new version of mod_ruby came out earlier today. -sc > I can't seem to get mod_ruby to build, do to some problem with eruby. No > matter weither eruby is installed or not, it seems to attempt to build it as > a dependency every time. > > any help appreciated > > jason -- Sean Chittenden PGP signature
problems building mod_ruby
I can't seem to get mod_ruby to build, do to some problem with eruby. No matter weither eruby is installed or not, it seems to attempt to build it as a dependency every time. any help appreciated jason navi# pwd /usr/ports/www/mod_ruby navi# make ===> Extracting for mod_ruby-0.8.1 >> Checksum OK for ruby/mod_ruby-0.8.1.tar.gz. ===> mod_ruby-0.8.1 depends on file: /usr/local/sbin/apxs - found ===> mod_ruby-0.8.1 depends on file: /usr/local/bin/ruby - found ===> mod_ruby-0.8.1 depends on shared library: eruby.9 - not found ===>Verifying install for eruby.9 in /usr/ports/textproc/eruby ===> Extracting for eruby-0.9.5 >> Checksum OK for ruby/eruby-0.9.5.tar.gz. ===> eruby-0.9.5 depends on file: /usr/local/bin/ruby - found ===> eruby-0.9.5 depends on file: /usr/local/bin/rd2 - found ===> Patching for eruby-0.9.5 ===> Configuring for eruby-0.9.5 checking whether we are using gcc... yes checking Ruby version... 1.6.4 checking for default charset... ISO-8859-1 checking whether enable shared... yes creating config.h creating Makefile ===> Building for eruby-0.9.5 cc -O -pipe -fPIC -Wall -I. -I/usr/local/lib/ruby/1.6/i386-freebsd4.3 -c eruby_lib.c ar rcu liberuby.a eruby_lib.o cc -O -pipe -fPIC -Wall -I. -I/usr/local/lib/ruby/1.6/i386-freebsd4.3 -c eruby_logo.c cc -O -pipe -fPIC -Wall -I. -I/usr/local/lib/ruby/1.6/i386-freebsd4.3 -c eruby_main.c cc -shared -Wl,-soname,liberuby.so.09 eruby_lib.o -L/usr/local/lib -lruby -lcrypt -lm -o liberuby.so.09 cc -rdynamic eruby_logo.o eruby_main.o -L. -leruby -L/usr/local/lib -lruby -lcrypt -lm -o eruby cc -O -pipe -fPIC -Wall -I. -I/usr/local/lib/ruby/1.6/i386-freebsd4.3 -c eruby_ext.c cc -shared -Wl,-soname,eruby.so -o eruby.so eruby_ext.o -L. -leruby -L/usr/local/lib -lruby -lcrypt -lm cd /usr/ports/textproc/eruby/work/eruby-0.9.5; /usr/local/bin/rd2 eruby.rd > eruby.html ===> Installing for eruby-0.9.5 ===> eruby-0.9.5 depends on file: /usr/local/bin/ruby - found eruby -> /usr/local/bin/eruby chmod 0755 /usr/local/bin/eruby liberuby.so.09 -> /usr/local/lib/liberuby.so.09 chmod 0644 /usr/local/lib/liberuby.so.09 liberuby.a -> /usr/local/lib/liberuby.a chmod 0644 /usr/local/lib/liberuby.a ./eruby.h -> /usr/local/include/eruby.h chmod 0644 /usr/local/include/eruby.h ./eruby.1 -> /usr/local/man/man1/eruby.1 chmod 0644 /usr/local/man/man1/eruby.1 eruby.so -> /usr/local/lib/ruby/site_ruby/1.6/i386-freebsd4.3/eruby.so chmod 0555 /usr/local/lib/ruby/site_ruby/1.6/i386-freebsd4.3/eruby.so ===> Generating temporary packing list /bin/mkdir -p /usr/local/share/examples/ruby/eruby install -c -o root -g wheel -m 444 /usr/ports/textproc/eruby/work/eruby-0.9.5/examples/* /usr/local/share/examples/ruby/eruby/ /bin/mkdir -p /usr/local/share/doc/ruby/eruby/ja install -c -o root -g wheel -m 444 /usr/ports/textproc/eruby/work/eruby-0.9.5/COPYING /usr/local/share/doc/ruby/eruby/ install -c -o root -g wheel -m 444 /usr/ports/textproc/eruby/work/eruby-0.9.5/ChangeLog /usr/local/share/doc/ruby/eruby/install -c -o root -g wheel -m 444 /usr/ports/textproc/eruby/work/eruby-0.9.5/README.en /usr/local/share/doc/ruby/eruby/ install -c -o root -g wheel -m 444 /usr/ports/textproc/eruby/work/eruby-0.9.5/eruby.html /usr/local/share/doc/ruby/eruby/ install -c -o root -g wheel -m 444 /usr/ports/textproc/eruby/work/eruby-0.9.5/eruby.rd /usr/local/share/doc/ruby/eruby/ install -c -o root -g wheel -m 444 /usr/ports/textproc/eruby/work/eruby-0.9.5/README.ja /usr/local/share/doc/ruby/eruby/ja/ ===> Compressing manual pages for eruby-0.9.5 ===> Running ldconfig /sbin/ldconfig -m /usr/local/lib ===> Registering installation for eruby-0.9.5 ===> Returning to build of mod_ruby-0.8.1 Error: shared library "eruby.9" does not exist *** Error code 1 Stop in /usr/ports/www/mod_ruby. *** Error code 1 Stop in /usr/ports/www/mod_ruby. *** Error code 1 Stop in /usr/ports/www/mod_ruby. *** Error code 1 Stop in /usr/ports/www/mod_ruby. *** Error code 1 Stop in /usr/ports/www/mod_ruby. *** Error code 1 Stop in /usr/ports/www/mod_ruby. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Staying *really stable* in FreeBSD
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I have been follow the discussion about RELEASE, STABLE, CURRENT and security patches for a particular release. Resuming: RELEASE and STABLE are develoment branches. In the handbook related to STABLE: «but we do occasionally make mistakes», so the best whay to stay really STABLE is do something like: cvsup to the last release RELENG_4_3_0_RELEASE and then cvsup all the times to RELENG_4_3 to receive security and critical fixes only. Am I right? When the RELEASE 4.4(?) is out, then I should repeat the example above to: RELENG_4_4_0_RELEASE and then stay in RELENG_4_4 Am I right? For what I read in this mailing list related to the naming version, is that the name STABLE make confusion some times (like in this particular case). Thanks very much, - -- Nuno Teixeira Dir. Técnico pt-quorum.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (FreeBSD) Comment: Made with pgp4pine 1.76 iD8DBQE7MSVwjwdyCmOgT8cRAor9AJ9JEzgZnuPblqHWwzosDqEXsutecwCfQpPR thueRvwwFfGiJknxOcSTkck= =fo/O -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: SMP/fxp problem...
Here's my full dmesg output: > Hi, > > I've got about 11 systems with two Intel NIC's each, > with varying 'versions' of FreeBSD 4.3-STABLE > < Multiple lines deleted for sanity > > Eric Parusel > Systems Administrator > Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.3-STABLE #1: Wed Jun 6 12:42:45 PDT 2001 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CUSTOMSMP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (549.06-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x387fbff real memory = 805306368 (786432K bytes) config> di ppc0 config> di sn0 No such device: sn0 Invalid command or syntax. Type `?' for help. config> di lnc0 No such device: lnc0 Invalid command or syntax. Type `?' for help. config> di ie0 No such device: ie0 Invalid command or syntax. Type `?' for help. config> di fe0 No such device: fe0 Invalid command or syntax. Type `?' for help. config> di ed0 No such device: ed0 Invalid command or syntax. Type `?' for help. config> di cs0 No such device: cs0 Invalid command or syntax. Type `?' for help. config> di bt0 config> di aic0 config> di aha0 config> di adv0 config> q avail memory = 778588160 (760340K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Preloaded elf kernel "kernel" at 0xc03da000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc03da09c. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xfcd0-0xfcdf at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 pci0: at 4.2 Timecounter "PIIX" frequency 3579545 Hz chip1: port 0x2180-0x218f at device 4.3 on pci0 pcib1: at device 7.0 on pci0 pci1: on pcib1 fxp0: port 0xecc0-0xecff mem 0xfea0-0xfeaf,0xfebfe000-0xfebfefff irq 10 at device 4.0 on pci1 fxp0: Ethernet address 00:d0:b7:9d:e0:15 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto sym0: <895> port 0xe800-0xe8ff mem 0xfebfd000-0xfebfdfff,0xfebff800-0xfebff8ff irq 11 at device 7.0 on pci1 sym0: Symbios NVRAM, ID 7, Fast-40, LVD, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. amr0: mem 0xe000-0xe7ff irq 9 at device 7.1 on pci0 amr0: Firmware \^C\^CD , BIOS \^C\^BB , 16MB RAM pcib2: at device 8.0 on pci0 pci2: on pcib2 fxp1: port 0xdcc0-0xdcff mem 0xfe80-0xfe8f,0xefffe000-0xefffefff irq 12 at device 2.0 on pci2 fxp1: Ethernet address 00:d0:b7:e0:3d:64 inphy1: on miibus1 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci0: (vendor=0x103c, dev=0x10c1) at 11.0 pci0: at 13.0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: unable to allocate the IRQ resource (12). vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A APIC_IO: Testing 8254 interrupt delivery APIC_IO: Broken MP table detected: 8254 is not connected to IOAPIC #0 intpin 2 APIC_IO: routing 8254 via 8259 and IOAPIC #0 intpin 0 SMP: AP CPU #1 Launched! acd0: CDROM at ata0-master using PIO4 Waiting 15 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. amrd0: on amr0 amrd0: 70006MB (143372288 sectors) RAID 1 (optimal) no devsw (majdev=0 bootdev=0xa020) Mounting root from ufs:/dev/amrd0s1a To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: releng4 no longer -STABLE???
My mistake, I read the output too quickly - you're correct, sir. It is the release notes breaking! - Jordan From: Dima Dorfman <[EMAIL PROTECTED]> Subject: Re: releng4 no longer -STABLE??? Date: Wed, 20 Jun 2001 14:36:57 -0700 > Jordan Hubbard <[EMAIL PROTECTED]> writes: > > 10 days ago, Andrey broke the handbook builds in -stable [...] > > The *Handbook* build? Or did you mean the release notes? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
SMP/fxp problem...
Hi, I've got about 11 systems with two Intel NIC's each, with varying 'versions' of FreeBSD 4.3-STABLE I've got one SMP system, with two Intel NIC's, as shown at the bottom of this message in my dmesg.boot It's an HP LH3r, and I've got two other systems (non SMP kernel) with the exact same network config, same cabling, same everything in the same rack, that are having no problems whatsoever I've had the problem running 4.3-STABLE compiled about a month ago, and a 4.3-STABLE that I've compiled June 6 at approx 12:00... I can't remember if the system was showing this problem before the fxp driver was MFC'd (sorry)... My SMP system gets a "fxp0: device timeout"or a "fxp1: device timeout" error about once every two days, and my network monitoring system is showing that the NIC is unreachable for a few minutes... Any ideas?? Anything I can try? "grep fxp dmesg.boot": fxp0: port 0xecc0-0xecff mem 0xfea0-0xfeaf,0xfebfe000-0xfebfefff irq 10 at device 4.0 on pci1 fxp0: Ethernet address 00:d0:b7:9d:e0:15 fxp1: port 0xdcc0-0xdcff mem 0xfe80-0xfe8f,0xefffe000-0xefffefff irq 12 at device 2.0 on pci2 fxp1: Ethernet address 00:d0:b7:e0:3d:64 By the way, is there a better list to post this message to, other than freebsd-stable? Thanks, Eric Parusel Systems Administrator To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: releng4 no longer -STABLE???
Jordan Hubbard <[EMAIL PROTECTED]> writes: > 10 days ago, Andrey broke the handbook builds in -stable [...] The *Handbook* build? Or did you mean the release notes? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: running out of buffer space for sockets
Ah, Thank you that cleared up a lot of issues. I have a greater idea of what I am dealing with at least.It is interesting that on the 4.x machine my fstat output is about 10x what my output for sockstat is. This is not the case on my 3.x machines. I am not _exactly_ sure what that means, but now at least I have a way of looking into the problem. Thank you again. -Marius M. Rex On Tue, 19 Jun 2001, Mikko Tyolajarvi wrote: > Yo! > > In local.freebsd.stable you write: > > >*smile* > > > Given my sometimes hideous abuse of the English language, it does > >not surprise me that someone would think I made a typo. Actually, I meant > >what I said. I am using thttpd not httpd. It is a single instance, > >spawning no children. > > You have a point though, I will indeed scan the docs to see if > >there is anything on thttpd's side that can be done to quell the tide. > > The pecular part about this is that my 3.5-Stable servers don't have > >such problems. With the same augents to the kernel (maxusers at 128 > >and NMBCLUSTERS at 16384) my 4.2-Stable box had significantly fewer > >kernel resources then my 3.5-Stable boxen. It would freeze up and die > >(couldn't open more filehandles) after about a day of serving. I manually > > You could be hitting the "maxsockets" limit (16k in your case). > > Dunno if this will help, but here is what I would do: > > - Check that thttpd isn't leaking sockets (fds). fstat -p PID | wc -l >Correlate with "sockstat | wc -l". Try to figure out if all your >sockets are in use (I don't think you will see pending connections >with either of these commands, though). > > - If you conclude thttpd is leaking sockets, fix it :-) > > - Otherwise, it looks like "maxsockets" is a kernel tunable, so >echo kern.ipc.maxsockets='"65536"' >> /boot/loader.conf >and reboot. If the values below are correct, you are nowhere near >exhausting your mbufs. > >Also see comment in /sys/kern/uipc_domain.c:domaininit() > > $.02, > /Mikko > > [...] > > >>kern.ipc.maxsockets: 16384 <- Lower than your 64k maxfiles > > [...] > > >># netstat -m > >>7115/8624/65536 mbufs in use (current/peak/max): > >>5454 mbufs allocated to data > >>1661 mbufs allocated to packet headers > >>5056/5854/16384 mbuf clusters in use (current/peak/max) > >>13864 Kbytes allocated to network (28% of mb_map in use) > > Only about one third of buffers in use. > -- > Mikko Työläjä[EMAIL PROTECTED] > RSA Security > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Strange mouse bahviour in FBSD 4.3 and XFree86 4.1.0
On Wed, 20 Jun 2001, John Merryweather Cooper wrote: Sorry, forgot the dmesg output: Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.3-STABLE #81: Wed Jun 20 21:33:40 CEST 2001 [EMAIL PROTECTED]:/usr/local/obj/usr/src/sys/WETTER Timecounter "i8254" frequency 1193182 Hz CPU: AMD Athlon(tm) Processor (807.19-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x642 Stepping = 2 Features=0x183f9ff AMD Features=0xc044<,AMIE,DSP,3DNow!> real memory = 268353536 (262064K bytes) avail memory = 257400832 (251368K bytes) Preloaded elf kernel "kernel" at 0xc039b000. Preloaded elf module "agp.ko" at 0xc039b09c. Pentium Pro MTRR support enabled apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 agp0: mem 0xe400-0xe7ff at device 0.0 on pci0 pcib2: at device 1.0 on pci0 pci1: on pcib2 pci1: at 0.0 irq 11 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xd800-0xd80f at device 4.1 on pci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xd400-0xd41f irq 5 at device 4.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xd000-0xd01f irq 5 at device 4.3 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhub2: ALCOR Generic USB Hub, class 9/0, rev 1.10/1.00, addr 2 uhub2: 4 ports with 4 removable, self powered fxp0: port 0xa400-0xa43f mem 0xdf00-0xdf0f,0xdf80-0xdf800fff irq 10 at device 11.0 on pci0 fxp0: Ethernet address 00:02:b3:17:99:90 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto atapci1: port 0x8800-0x883f,0x9000-0x9003,0x9400-0x9407,0x9800-0x9803,0xa000-0xa007 mem 0xde80-0xde81 irq 10 at device 17.0 on pci0 ata2: at 0xa000 on atapci1 pcib1: on motherboard pci2: on pcib1 orm0: at iomem 0xc-0xc9fff,0xcc000-0xc,0xd-0xd1fff,0xd4000-0xd57ff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <8 virtual consoles, flags=0x300> fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 flags 0x10 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 drq 1 flags 0x8 on isa0 ppc0: SMC-like chipset (ECP-only) in ECP mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: IEEE1284 device found /NIBBLE/ECP Probing for PnP devices on ppbus0: ppbus0: PRINTER MLC,MFPDTF1,PCL,PJL lpt0: on ppbus0 lpt0: Interrupt-driven port DUMMYNET initialized (010124) IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to deny, unlimited logging IPsec: Initialized Security Association Processing. ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed ad4: 29314MB [59560/16/63] at ata2-master UDMA100 acd0: CDROM at ata1-master using PIO4 Mounting root from ufs:/dev/ad4s1a link_elf: symbol splash_register undefined :>On 2001.06.20 13:58 "Hartmann, O." wrote: :>> Dear Sirs. :>> :>> I posted here several postings about a problem with one of our :>> FBSD 4.3-STABLE boxes. This machine has been cvsupdated today, :>> XFRee864.1.0_4 has been installed several days ago (by a fresh :>> compilation). :>> :>> One of the earlier problems is the following: :>> :>> I can not shutdown this machine by being remotely loged in :>> using shutdown -r now. I always have to use shutdown -r -o now :>> to do the task. On all other maschines that works! :>> :>> The machine I speak about is a AMD K7 800 MHz based on ASUS A7V :>> PCB and IBM DTLA 307030. The videoadaptor is a ELSA Erazor III Pro. :>> See the following dmesg-output . :>> :>> The new problem is hard to describe. It seems one way like a hardware :>> fault, but another way the fault of some FBSD subsystems. :>> :>> Description: :>> :>> Using /dev/sysmouse and moused as the basic mouse system, we have a :>> Logitech optical USB port mouse attached to this machine. The USB :>> mouse is connected to a HUB located at a Iiyama 18 inch LCD screen :>> (bit that doesn't matter, I tried the USB port directly or a PS/2 :>> mouse with the same effect). :>> On the X11 screen, the mouse rushes uncontrollable over the screen, :>> jumping, shivers around, not reacting on pressed buttons. It looks :>> like having used the wrong protocol with earlier XFree types. But there :>> is no misconfiguration, this configuration worked since approximately I :>> switched over to XFree86 4.1.0 and/or did a
Re: Strange mouse bahviour in FBSD 4.3 and XFree86 4.1.0
On 2001.06.20 13:58 "Hartmann, O." wrote: > Dear Sirs. > > I posted here several postings about a problem with one of our > FBSD 4.3-STABLE boxes. This machine has been cvsupdated today, > XFRee864.1.0_4 has been installed several days ago (by a fresh > compilation). > > One of the earlier problems is the following: > > I can not shutdown this machine by being remotely loged in > using shutdown -r now. I always have to use shutdown -r -o now > to do the task. On all other maschines that works! > > The machine I speak about is a AMD K7 800 MHz based on ASUS A7V > PCB and IBM DTLA 307030. The videoadaptor is a ELSA Erazor III Pro. > See the following dmesg-output . > > The new problem is hard to describe. It seems one way like a hardware > fault, but another way the fault of some FBSD subsystems. > > Description: > > Using /dev/sysmouse and moused as the basic mouse system, we have a > Logitech optical USB port mouse attached to this machine. The USB > mouse is connected to a HUB located at a Iiyama 18 inch LCD screen > (bit that doesn't matter, I tried the USB port directly or a PS/2 > mouse with the same effect). > On the X11 screen, the mouse rushes uncontrollable over the screen, > jumping, shivers around, not reacting on pressed buttons. It looks > like having used the wrong protocol with earlier XFree types. But there > is no misconfiguration, this configuration worked since approximately I > switched over to XFree86 4.1.0 and/or did a cvsupdate. > When leaving the X-session, Xserver drops a core, reporting something > about an > illegal instruction after resetting the mouese! > When in terminal mode (no X), the mouse shivers and jumps also > uncontroleable > on the screen. I exchanged the mouese with a simple PS/2 mouse and > sometimes > I have a pointer, sometimes not (using sysmouse/moused). In X11 the > phenomenon > of a jumping and rushing mouse is not as obvious as with the USB type, > but it > is also faulty. The mouse disappears or is unuseable. The kernel reports > a mouse > at psm0, but in X (chooser) there is no access/movement of it. Sometimes, > while > having luck moving it around, it seems to drop spontanously "button > presses" > around. > > This machine is without graphical device or mouse accessible and works > perfect. > I can use it remotely without problems. It seems really to be related to > something > like sysmouse/moused/mouse/XFree86 or FreeBSD's driver for the mouse > system. > > Does anyone heared about such strange things due a bug of FreeBSD/XFree86 > 4.1.0? > If not, this really seems to be a massive hardware related problem. > > On the other hand: > > We have a lot of self-made X11 Terminals around here for our students, > based > on a DFI AK74EC main PCB, Duron 700, Gigabyte GA660+ video board, using > Logitech > 3 button PS/2 mice. They are cvsupdated 7 days ago, XFree86 4.1.0 has > been build > several days ago. These diskless booting terminals do not show any kind > of disruption > of mouse access or movement ... > -- > MfG > O. Hartmann > > [EMAIL PROTECTED] > > IT-Administration des Institut fuer Physik der Atmosphaere (IPA) > > Johannes Gutenberg Universitaet Mainz > Becherweg 21 > 55099 Mainz > > Tel: +496131/3924662 (Maschinensaal) > Tel: +496131/3924144 > FAX: +496131/3923532 > > I have had similar, but less severe, experiences recently with my mouse--a Logitech MouseMan+. I don't get the illegal instruction error as above (but this maybe because I use "startx" and OH uses "xdm"?) But the erratic mouse cursor and the dropping of random clicks makes XFree86-4 operation somewhat more painful than I'd like at the moment. My configuration: Adapter: Diamond Mutlimedia Viper 770 Ultra (nVidia TNT2 Ultra with 32 megs) Mouse: Logitech MouseMan+ connected to PS/2 port jmc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Strange mouse bahviour in FBSD 4.3 and XFree86 4.1.0
Dear Sirs. I posted here several postings about a problem with one of our FBSD 4.3-STABLE boxes. This machine has been cvsupdated today, XFRee864.1.0_4 has been installed several days ago (by a fresh compilation). One of the earlier problems is the following: I can not shutdown this machine by being remotely loged in using shutdown -r now. I always have to use shutdown -r -o now to do the task. On all other maschines that works! The machine I speak about is a AMD K7 800 MHz based on ASUS A7V PCB and IBM DTLA 307030. The videoadaptor is a ELSA Erazor III Pro. See the following dmesg-output . The new problem is hard to describe. It seems one way like a hardware fault, but another way the fault of some FBSD subsystems. Description: Using /dev/sysmouse and moused as the basic mouse system, we have a Logitech optical USB port mouse attached to this machine. The USB mouse is connected to a HUB located at a Iiyama 18 inch LCD screen (bit that doesn't matter, I tried the USB port directly or a PS/2 mouse with the same effect). On the X11 screen, the mouse rushes uncontrollable over the screen, jumping, shivers around, not reacting on pressed buttons. It looks like having used the wrong protocol with earlier XFree types. But there is no misconfiguration, this configuration worked since approximately I switched over to XFree86 4.1.0 and/or did a cvsupdate. When leaving the X-session, Xserver drops a core, reporting something about an illegal instruction after resetting the mouese! When in terminal mode (no X), the mouse shivers and jumps also uncontroleable on the screen. I exchanged the mouese with a simple PS/2 mouse and sometimes I have a pointer, sometimes not (using sysmouse/moused). In X11 the phenomenon of a jumping and rushing mouse is not as obvious as with the USB type, but it is also faulty. The mouse disappears or is unuseable. The kernel reports a mouse at psm0, but in X (chooser) there is no access/movement of it. Sometimes, while having luck moving it around, it seems to drop spontanously "button presses" around. This machine is without graphical device or mouse accessible and works perfect. I can use it remotely without problems. It seems really to be related to something like sysmouse/moused/mouse/XFree86 or FreeBSD's driver for the mouse system. Does anyone heared about such strange things due a bug of FreeBSD/XFree86 4.1.0? If not, this really seems to be a massive hardware related problem. On the other hand: We have a lot of self-made X11 Terminals around here for our students, based on a DFI AK74EC main PCB, Duron 700, Gigabyte GA660+ video board, using Logitech 3 button PS/2 mice. They are cvsupdated 7 days ago, XFree86 4.1.0 has been build several days ago. These diskless booting terminals do not show any kind of disruption of mouse access or movement ... -- MfG O. Hartmann [EMAIL PROTECTED] IT-Administration des Institut fuer Physik der Atmosphaere (IPA) Johannes Gutenberg Universitaet Mainz Becherweg 21 55099 Mainz Tel: +496131/3924662 (Maschinensaal) Tel: +496131/3924144 FAX: +496131/3923532 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Last cvsup: openssl broken?
Hello to all, I've cvsuped my system today. I make buildworld, make kernel, etc, with no problems. I noted that fetchmail gives a signal 11 (core dumped). When I change the .fetchmailrc to fetch mail without SSL then it work ok. I have the same problem with SSH. Maybe a OpenSSL problem or anything else that this too programs use? Thanks, -- Nuno Teixeira Dir. Técnico pt-quorum.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
