Re: Staroffice 5.0 under 4.0-current
Go to http://lt.tar.com/ and see? transcript? of a successful installation of StarOffice 5.0. It should help you. ad...@worldbank.org wrote: I'm running 4.0-current as of late last week, elf kernel.? Everything works great - no problems.? I understand that the Linux kernel threads stuff is now in my system by default, so I should be able to download and install StarOffice 5.0.? Others on the list have confirmed that it works. I, however, am unable to get it running.? The setup program continually complains about not finding the glibc2 libraries, even after I extracted them into /compat/linux/lib and reran /compat/linux/sbin/ldconfig. Any help would be greatly appreciated. FWIW - Linux Wp7, and several others work just fine Al To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Aladdin chipset SMBus support available!
On Tue, 16 Feb 1999, Warner Losh wrote: : Not to stop you in your tracks, but I would really love to see : somebody (more capable than the PAO people) work out a power : management architecture for us before we have too many more : hacks in this area... I'd have to agree that a unified power management architecture would be a good thing. There is also the new APCI to consider as well. Warner And hot-docking/undocking with PnP reprobing of new devices... Ouch, stop hitting me. -- Doug Rabson Mail: d...@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: RE: Problems in VM structure ?
:I'm seeing different responses depending on hardware. : :On regular Pentium 166 machines, I almost NEVER get :a panic. On brand-new Pentium II 350s, I get a panic :every 6-9 hours. This happens when both kernels are :configured the same for maxusers. It happens when :both machines are under the same load level -- the :P5 stays rock solid, the P6 flakes out. : :What's the chance that our kernel adaptations for PIIs :is partly at fault? : :-Troy Cobb : Circle Net, Inc. : http://www.circle.net With what config? Have you tried reducing maxusers to 128? -Matt To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Kernel option NFS_NOSERVER breaks current kernel
Hi folks, I have the following pertinent options in my kernel config: options FFS #Fast filesystem options FFS_ROOT#FFS usable as root device options MFS #Memory filesystem options NFS #Network filesystem options NFS_NOSERVER#Disable the NFS-server code. options SOFTUPDATES I'm using current sources pulled down about 10 hours before the time of this post. A ``config -r MYKERNEL ; cd ../../compile/MYKERNEL ; make depend'' works, but I get the following breakage during a ``make'': # make [...] cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK -include opt_global.h -elf ../../nfs/nfs_syscalls.c *** Error code 1 Stop. # ident ../../nfs/nfs_syscalls.c ../../nfs/nfs_syscalls.c: $Id: nfs_syscalls.c,v 1.46 1999/02/16 10:49:53 dfr Exp $ Is anyone else using the NFS_NOSERVER option successfully? Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Kernel option NFS_NOSERVER breaks current kernel
On Wed, 17 Feb 1999 11:48:15 +0200, Sheldon Hearn wrote: Is anyone else using the NFS_NOSERVER option successfully? Bleh, I should have mentioned that the kernel builds fine if I remove the NFS_NOSERVER option. Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: VM patch.. SMP and SO5.0
who's looked at this. Tor Egge, he has been very helpful during the development of the code. The pmap change was a result of discussions with him. It looks to me that this is serious stuff spliting the pmap out of the vmspace structure is a big change. caertainly a logical move but requires checking.. I guess it should be refered to the VM cabal. I presume that this is to be done in conjunction with the linuxthreads (and native threads) code already committed... What exactly is the reason for separating them? First, pmap is not split out of vmspace structure, it's just a trick to keep struct kinfo_proc constant size (i.e. independent of NCPU), vmspace_alloc() has been changed to allocate sizeof(struct vmspace)+sizeof(struct pmap) amount of space and pmap lives at the bottom half. julian -lq To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: SMP and SO5.0
I've gone through these patches and I can see that they are really needed for SMP where address spaces are shared. There are details I didn't get, such as where is the per-processor pde pointed, (i.e. where is the per processor KVM range) and is there a single page table for each processor that is always mapped into the processor specific slot for that process. I didn't change any of these (that's main reason I chose to have multiple page directories over a single page directory with a different slot for each processor and reference the per-processor data through a pointer in processor local storage, e.g. %fs, which is simply too complicated without compiler support. In fact I like the 2nd way better), so the process specific slot is still MPPTDI (KVM 0xff80-0xffbf?). another question that is raised I guess is how do we tell gdb to switch between processors when reading core-dumps :-). Tor has sent me a patch which implements a cpu command allowing you to switch among cpus. I've never actually used it, in most of the cases, you don't really care on which cpu the crash occurred. If you want to try it, I can send a copy of the gdb patch to you. -lq To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
RE: RE: Problems in VM structure ?
-Original Message- From: Matthew Dillon [mailto:dil...@apollo.backplane.com] :What's the chance that our kernel adaptations for PIIs :is partly at fault? : :-Troy Cobb : Circle Net, Inc. : http://www.circle.net With what config? Have you tried reducing maxusers to 128? -Matt I've had it at MAXUSERS=256 on both the P5 and the P6. The P5 stays stable, the P6 doesn't. If I reduce MAXUSERS to 128 then these heavily loaded boxen will fall over due to out of MBUFs errors, or so I believe. I'd love to find some real kernel-tuning documentation out there, one of my panics is a pipeinit: cannot allocate pipe -- out of kvm and I can't pull a crashdump due to a DSCHECK error because my SWAP is 2GB. -Troy Cobb Circle Net, Inc. http://www.circle.net To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: RE: RE: Problems in VM structure ?
Try reducing maxusers to 128. If you have mbuf problems, override NMBCLUSTERS ( making it 4096 or 8192 should be sufficient ). Sometimes network mbuf problems on heavily loaded machines are due to too-large default buffer sizes - if net.inet.tcp.sendspace or recvspace is greater then 16384, try reducing it to 16384. If your machine is not using that 2GB of swap, cap the swap at 1.9GB. -Matt Matthew Dillon dil...@backplane.com :I've had it at MAXUSERS=256 on both the P5 and the P6. The P5 stays :stable, the P6 doesn't. If I reduce MAXUSERS to 128 then these :heavily loaded boxen will fall over due to out of MBUFs errors, or :so I believe. : :I'd love to find some real kernel-tuning documentation out there, :one of my panics is a pipeinit: cannot allocate pipe -- out of kvm :and I can't pull a crashdump due to a DSCHECK error because my :SWAP is 2GB. : : :-Troy Cobb : Circle Net, Inc. : http://www.circle.net : : :To Unsubscribe: send mail to majord...@freebsd.org :with unsubscribe freebsd-current in the body of the message : To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Problems in VM structure ?
[ CC trimmed ] tc...@staff.circle.net wrote in message ID a0cfa284c004d211b7ee0060082f32a412e...@freya.circle.net: I've had it at MAXUSERS=256 on both the P5 and the P6. The P5 stays stable, the P6 doesn't. If I reduce MAXUSERS to 128 then these heavily loaded boxen will fall over due to out of MBUFs errors, or so I believe. If you are running out of MBUF clusters, play with option NMBCLUSTERS=x directly rather than indirectly through maxusers... 4096 or 8192 is probably a good starting value. If you look in /sys/compile/YOUR_KERNEL at the param.c, then you can get a better idea of what maxusers tweaks, and what you need to tweak manually. I know its not a `howto' guide :) Sorry Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /etc/defaults/rc.conf
On Wed, Feb 17, 1999 at 06:15:06PM +1030, Greg Lehey wrote: On Tuesday, 16 February 1999 at 9:24:31 -0800, Jordan K. Hubbard wrote: If I have a /etc/defaults/rc.conf, then my /etc/rc.conf won't be consulted. Wrong. You need to read just a bit FURTHER into that file before jumping to such conclusions. :-) Been there, done that. Next thing is to write a book about it. Can I hope that it won't change again this year? You can _hope_. Eivind, who has a number of things he would like to see be different in the rc system (including rc.conf) - see http://www.freebsd.org/~eivind/newrc.html for a set of requirements and a couple of thoughts. Missed requirements are welcome. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: how to play with pci128 sound card
Greetings, I also have a Creative Labs Sound Blaster PCI128 installed, and though I followed your instructions below I am not havine what I would call promising results. At 12:21 PM 1/10/99 +0100, Luigi Rizzo wrote: you need a -current system with the pcm device, then I am running 3.1-STABLE, but since your instructions were dated befoe the split, I assumed this would be OK. I have added the pnp0 controller and the pcm0 device to my kernel. /kernel: es1: AudioPCI ES1370 rev 0x00 int a irq 12 on pci0.10.0 /kernel: pcm1: using I/O space register mapping at 0xb800 cd /dev ./MAKEDEV snd1 I have done this. cat somefile /dev/audio When I cat'd a .au file I had on my system there was a pause before I got my prompt back, but complete silence from the speakers. Since I did not get any errors addressing the device, could this be a volume problem? If so, is there any way to adjust the volume. If not a volume problem, do you have any suggestions? Any help appreciated! -ck To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Buildworld fails on today 3.1-STABLE!
On Tue, 16 Feb 1999, Mikhail Teterin wrote: I usually keep -O to just '-O' - I had been upping it recently, but then it started breaking even some of my simple programs, so leasson learn't, it's staying at just '-O' from now on in... (safety first? :-) -O2 works fine too. -O3 does not. We'll probably see the newer version of compiler before this is fixed. -O2 does *not* work for the alpha build (at least with gcc 2.7.2.x). It might work with a newer compiler if and when that happens. -- Doug Rabson Mail: d...@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
axp kernel breakage
cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h -mno-fp-regs -Wa,-mev56 ../../nfs/nfs_syscalls.c ../../nfs/nfs_syscalls.c:924: `sysctl__vfs_nfs_children' undeclared here (not in a function) ../../nfs/nfs_syscalls.c:924: initializer element for `sysctl___vfs_nfs_defect.oid_parent' is not constant ../../nfs/nfs_syscalls.c:92: warning: `nfsrv_zapsock' declared `static' but never defined *** Error code 1 Not *quite* sure where its coming from. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: SMP and SO5.0
Julian Elischer said: On Tue, 16 Feb 1999, Luoqi Chen wrote: You may try my patch at http://www.freebsd.org/~luoqi, which would allow linux threads to run on SMP. I've gone through these patches and I can see that they are really needed for SMP where address spaces are shared. I agree -- a per-cpu page directory per multithreaded process is the way that I had implemented. Excellent!!! -- John | Never try to teach a pig to sing, dy...@iquest.net | it makes one look stupid jdy...@nc.com | and it irritates the pig. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: You Got To Love the New Kind of Spam 8)
On Wed, 17 Feb 1999, Kenneth D. Merry wrote: Amancio Hasty wrote... SGI is releasing GLX 8) http://biz.yahoo.com/prnews/990216/ca_silicon_2.html Have Fun, Amancio P.S.: If companies start dumping large packages is going to weight us down :( Heh. That's pretty cool. Although I wouldn't say that GLX itself is exactly huge. What they've released is basically the X server side connecting glue that allows connecting up OpenGL to an X server. Here's a snippet from the readme: = GLX is used to connect an X server and an OpenGL implementation. By itself, the GLX distribution is incomplete. XFree86 (or other code based on the X11R6 release) provides the X server. = They aren't releasing, however, their OpenGL implementation. Here's what they said about that: = Please do not deluge SGI with requests to make our SI available as open source. We are fully aware of the issues involved. = Apparantly Red Hat and some other company (Precision Insight) are working on getting Mesa to work with GLX. I have met one of the principals at Precision Insight and have corresponded with them about their GL work for XFree86. They do seem to be heading in the correct direction. When they get closer to an implementation, we will need to sort out a few kernel issues (they need some low-level kernel support for virtualising the 3D hardware and queuing DMA buffers for hardware where that is relavent). If this works out, I might actually be able to release the software I'm working on (a game and a game development system) on FreeBSD which would be cool :-). -- Doug Rabson Mail: d...@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Buildworld fails on today 3.1-STABLE!
At 8:05 pm -0800 16/2/99, Mike Smith wrote: [...] No, -O2 does not work fine; we've seen reports of it breaking things before. I've been using -O2 building -current for over a year with no problems. I haven't dared try it for the kernel though... -- Bob Bishop (0118) 977 4017 international code +44 118 r...@gid.co.ukfax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Problems in VM structure ?
On Tue, Feb 16, 1999 at 12:19:07AM -0800, Matthew Dillon wrote: :maxusers 256 Try reducing maxusers to 128. Another person reported similar behavior to me and after a bunch of work he tried going back to a basic distribution -- and everything started working again. To add some public informations. The host in case was using 512Meg RAM and I have tested it with 256Meg. I originaly installed a 3.0-CURRENT from mid December and updated to a recent version after getting panics. I used MAXUSERS of 512 and was able to trigger a panic during only a few minutes uptime after reducing it to 256 the host was more stable. Now it is running without any panics using MAXUSERS 128. It turned out that a maxusers value of 256 and 512 were causing his machine to go poof, but a maxusers value of 128 worked fine. I haven't tracked the problem down yet. Please try reducing your maxusers to 128 and email the results to current. -Matt To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message -- B.Walter To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Problems in VM structure ?
On Wed, Feb 17, 1999 at 08:46:49AM -0500, tc...@staff.circle.net wrote: -Original Message- From: Matthew Dillon [mailto:dil...@apollo.backplane.com] :What's the chance that our kernel adaptations for PIIs :is partly at fault? : :-Troy Cobb : Circle Net, Inc. : http://www.circle.net With what config? Have you tried reducing maxusers to 128? -Matt I've had it at MAXUSERS=256 on both the P5 and the P6. The P5 stays stable, the P6 doesn't. If I reduce MAXUSERS to 128 then these heavily loaded boxen will fall over due to out of MBUFs errors, or so I believe. I my case it was a P-II 400 I'd love to find some real kernel-tuning documentation out there, one of my panics is a pipeinit: cannot allocate pipe -- out of kvm and I can't pull a crashdump due to a DSCHECK error because my SWAP is 2GB. The pipeinit is one of the panics I got very often - but they were not reduced to -Troy Cobb Circle Net, Inc. http://www.circle.net To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message -- B.Walter To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Buildworld fails on today 3.1-STABLE!
Bob Bishop wrote: At 8:05 pm -0800 16/2/99, Mike Smith wrote: [...] No, -O2 does not work fine; we've seen reports of it breaking things before. I've been using -O2 building -current for over a year with no problems. I haven't dared try it for the kernel though... Lucky you. -O2 *does* break world for many people. Eventually, it might break your world too, and there is a great chance you'll first spam -current before changing -O2 to -O and trying again. Or there would, if we stopped hitting on this nail. :-) -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org Well, as a computer geek, I have to believe in the binary universe. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Buildworld fails on today 3.1-STABLE!
:At 8:05 pm -0800 16/2/99, Mike Smith wrote: :[...] :No, -O2 does not work fine; we've seen reports of it breaking things :before. : :I've been using -O2 building -current for over a year with no problems. I :haven't dared try it for the kernel though... : :-- :Bob Bishop (0118) 977 4017 international code +44 118 :r...@gid.co.ukfax (0118) 989 4254 between 0800 and 1800 UK I've been using -O2 kernels for over a year. Works fine as far as I can tell. makeoptions COPTFLAGS=-O2 -pipe -Matt Matthew Dillon dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Buildworld fails on today 3.1-STABLE!
On Thu, 18 Feb 1999, Daniel C. Sobral wrote: Lucky you. -O2 *does* break world for many people. Eventually, it might break your world too, and there is a great chance you'll first spam -current before changing -O2 to -O and trying again. Or there would, if we stopped hitting on this nail. :-) Odd..I've been running -O2 -mno-486 -pipe for at least a year now, without noticing any world problems (or weird behaviour from binaries) other than the commit-related breakage everyone else has seen due to legitimate bugs. What would cause some people to have problems with -O2 and others not? I also run my kernels -O3 because they work for me, but I understand the potential problems with this and drop it back if I ever have problems. This reminds me of something I need to benchmark a bit more: I was testing the optimization of egcs 1.1.1 and found that -O3 produced executables which were significantly slower than -O2, no matter what architecture settings I used. From memory, for -O2 binaries I was getting ~20% speed improvements on my simple test suite compiling with -mpentium -march=pentium compared to -mno-486 on GCC 2.7.2.3 Kris -- Daniel C. Sobral (8-DCS) d...@newsguy.com d...@freebsd.org Well, as a computer geek, I have to believe in the binary universe. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message - (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Buildworld fails on today 3.1-STABLE!
Matthew Dillon wrote: I've been using -O2 kernels for over a year. Works fine as far as I can tell. I've had a few failures with -O2 ages ago, though I can't guess how long ages was - I definitely remember tracing one problem down to '-O' vs. '-O2', I stick to '-0' now religiously... (at least it rules it out of the equation - I hope g) -Kp To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Compaq built-in ncr tl controllers with 4.0
Hello- I've been trying to get 3.1 or 4.0 to run on a Compaq Professional Workstation 6000 with dual PII-300s, using the built-in symbios 53c875 SCSI controller, and the built-in ThunderLan ethernet adapter. The machine works perfectly with 2.2.8, but we'd like to get it running 3.1 (or 4.0 if necessary) to take advantage of the second CPU. We have been able to complete a make upgrade with freshly cvsupped 3.1 source, to the point where the new kernel boots. While booting, the GENERIC kernel does not find the ncr or tl devices, and of course fails to mount root. I'd include dmesg from those boots, but it doesn't get far enough to write it anywhere. The new bootblocks seem to be working fine, and are able to boot the kernel, but it fails with a cannot mount root message and then panics. We then tried to boot with the 3.1 and the 4.0 boot floppies. Neither was able to find the SCSI controller or the ethernet device. Of course, we find it odd that 2.2.8 found the devices ok, but newer releases do not. As far as I can tell, the hardware is supported by CAM, etc. (I have a Tekram 390F 53c875-based card in another 4.0 machine that works great). The installs failed with the complaint that no disks could be found to install on. A search through the mailing list archives yielded little information that still seemed relevant (apparently, the tl0 driver wasn't around in 2.2.6 or earlier but that obviously changed before 2.2.8). I've included the 2.2.8 dmesg output below. I'm hoping that someone out there will see something in them that I cannot and will provide us with the magic incantation needed to get this thing running 3.1 or 4.0. Our suspicions are on the PCI bridge, since both the unfound devices are on pci bus 1, while the detected devices reside on bus 0, but we don't know what to do about that. By the way, the unidentified storage device that doesn't get a driver assigned on pci1:10 is a Jaz Jet card, apparently with an Advansys chipset, that 2.2.8 doesn't grok, but 3.1+ should find ok. It doesn't get detected by 3.1 or 4.0 kernels either. Thank you in advance, -Ben Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2.8-STABLE #0: Wed Feb 17 09:02:09 GMT 1999 bhle...@server2.mediumlook.com:/usr/src/sys/compile/CALVIN CPU: Pentium II (299.53-MHz 686-class CPU) Origin = GenuineIntel Id = 0x633 Stepping=3 Features=0x80fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMO V,MMX real memory = 536870912 (524288K bytes) avail memory = 524316672 (512028K bytes) Probing for devices on PCI bus 0: chip0 Ross (?) host to PCI bridge rev 1 on pci0:0:0 pci0:9:Compaq, device=0xa0f8, class=serial, subclass=0x03 int a irq 11 [no d river assigned] vga0 VGA-compatible display device rev 1 int a irq 11 on pci0:13:0 chip1 generic PCI bridge (vendor=0e11 device=a0f3 subclass=1) rev 12 on pci0:1 5:0 pci0:15:1: Compaq, device=0xae33, class=storage (ide) int a irq 15 [no driver as signed] chip2 Ross (?) host to PCI bridge rev 1 on pci0:17:0 Probing for devices on PCI bus 1: tl0 Compaq Netelligent 10/100 Proliant rev 16 int a irq 11 on pci1:7:0 tl0: Ethernet address: 00:80:5f:85:23:8b tl0: autoneg complete, link status good (half-duplex, 10Mbps) ncr0 ncr 53c875 fast20 wide scsi rev 4 int a irq 11 on pci1:9:0 ncr0 waiting for scsi devices to settle (ncr0:0:0): WIDE SCSI (16 bit) enabled(ncr0:0:0): 10.0 MB/s (200 ns, offset 15) (ncr0:0:0): COMPAQ WDE4360W 1.52 type 0 fixed SCSI 2 sd0(ncr0:0:0): Direct-Access sd0(ncr0:0:0): WIDE SCSI (16 bit) enabled sd0(ncr0:0:0): 40.0 MB/s (50 ns, offset 15) 4094MB (8386000 512 byte sectors) pci1:10:vendor=0x10cd, device=0x1300, class=storage (scsi) int a irq 11 [no driver assigned] Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color 16 virtual consoles, flags=0x0 sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface lpt1 not found at 0x mse0 not found at 0x23c psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (atapi): CD-ROM CDU571-Q/1.1a, removable, accel, dma, iordis wcd0: 1378KB/sec, 128KB cache, audio play, 256 volume levels, ejectable tray wcd0: door open, unlocked wdc1 not found at 0x170 uha0 not found at 0x330 aha0 not found at 0x330 aic0 not found at 0x340 nca0 not found at 0x1f88 nca1 not found at 0x350 sea0 not found wt0 not found at 0x300 mcd0 not found at 0x300 matcdc0 not found at 0x230 scd0 not found at 0x230 npx0 flags 0x1 on motherboard npx0: INT 16 interface -- Benjamin Lewis bhle...@gte.net -or- bhle...@purdue.edu To Unsubscribe: send mail to
4.0-current make release failure (sysctl)
Hi, Just fyi, current as of 2pm EST. Thanks, John cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK -include opt_global.h -elf ../../nfs/nfs_syscalls.c ../../nfs/nfs_syscalls.c:924: `sysctl__vfs_nfs_children' undeclared here (not in a function) ../../nfs/nfs_syscalls.c:924: initializer element for `sysctl___vfs_nfs_defect.oid_parent' is not constant ../../nfs/nfs_syscalls.c:92: warning: `nfsrv_zapsock' declared `static' but never defined *** Error code 1 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: 4.0-current make release failure (sysctl)
On Wed, 17 Feb 1999 19:12:59 EST, John W. DeBoskey wrote: Just fyi, current as of 2pm EST. ../../nfs/nfs_syscalls.c:92: warning: `nfsrv_zapsock' declared `static' but never defined *** Error code 1 I get this when I set ``option NFS_NOSERVER''. If I disable the option, my kernel builds. Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: 4.0-current make release failure (sysctl)
Hi, I don't control the options used to build the distribution kernels during a 'make release'. Jordan is responsible for that. I don't have any problems building my local kernel since the only nfs options I have are: options NFS #Network Filesystem options NFS_ROOT#NFS usable as root device, NFS req'ed Anyways, it looks like something needs to be done, whether it is to change 'make release', or fix the sysctl code.. Thanks! John On Wed, 17 Feb 1999 19:12:59 EST, John W. DeBoskey wrote: Just fyi, current as of 2pm EST. ../../nfs/nfs_syscalls.c:92: warning: `nfsrv_zapsock' declared `static' but never defined *** Error code 1 I get this when I set ``option NFS_NOSERVER''. If I disable the option, my kernel builds. Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Compaq built-in ncr tl controllers with 4.0
Hi, On Wed, 17 Feb 1999, Benjamin Lewis wrote: ... We then tried to boot with the 3.1 and the 4.0 boot floppies. Neither was able to find the SCSI controller or the ethernet device. Of course, we find it odd that 2.2.8 found the devices ok, but newer releases do not. As far as I can tell, the hardware is supported by CAM, etc. (I have a Tekram 390F 53c875-based card in another 4.0 machine that works great). The installs failed with the complaint that no disks could be found to install on. I have the same symptoms with an Compaq Proliant 1600. The cause seems to be that these machines have more than one PCI-Busses which lay behind on PCI-PCI-Bridges and only one gets probed/found under 3.*, 4.*. Furthermore under 2.2.7 the Busses seems to get probed but in an different order than the BIOS does because the ncr for the internal disks (which gets probed first by BIOS) is probed last by the Kernel and im my case the BIOS-drive C: gets da2. Verry annoying if Disks get added into the cabinet... :-( Do the symptoms trigger some Ideas by someone? Bye! Michael Reifenberger Plaut Software GmbH, R/3 Basis To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
panic mount root failed
Env: Yesterday I went to a friends house for installing a box from the freebsd 3.0-release cdrom (I have also the src and obj very current on another cd to do a quick make installword :-). He has : 1 hd master (A) + 1 cdrom slave on primary ch. 1 hd master (B) + 1 zip atapi slave on secundary ch. on (A) there is a primary win98 partition. on (B) there is a fat partition on wd2s1 and a freebsd installation on wd2s2a. The installation procedure was fine, but at the next reboot it can't mount the root fs because it tries to mount / on wd1s2a even if in /etc/fstab there is wd2s2a ! I think it is a problem related to the fact that the cdrom make confusion on the routine that have to find the hd slice number... everything was fine after adding a boot config with 1:wd(2,a)kernel Is it a known problem or I miss something ? Best Regards, Gianmarco Giovannelli , Unix expert since yesterday http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: panic mount root failed
:Env: : :Yesterday I went to a friends house for installing a box from the freebsd :3.0-release cdrom (I have also the src and obj very current on another cd :to do a quick make installword :-). : :He has : :1 hd master (A) + 1 cdrom slave on primary ch. :1 hd master (B) + 1 zip atapi slave on secundary ch. : :on (A) there is a primary win98 partition. on (B) there is a fat partition :on wd2s1 and a freebsd installation on wd2s2a. : :The installation procedure was fine, but at the next reboot it can't mount :the root fs because it tries to mount / on wd1s2a even if in /etc/fstab :there is wd2s2a ! I think it is a problem related to the fact that the :cdrom make confusion on the routine that have to find the hd slice number... : :everything was fine after adding a boot config with 1:wd(2,a)kernel : :Is it a known problem or I miss something ? : :Best Regards, :Gianmarco Giovannelli , Unix expert since yesterday :http://www.giovannelli.it/~gmarco :http://www2.masternet.it Look at the disklabel for wd2s2. If the 'disk:' field in the label says wd1 that may be your problem. -Matt Matthew Dillon dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: panic mount root failed
At 17.49 17/02/99 -0800, you wrote: :everything was fine after adding a boot config with 1:wd(2,a)kernel Look at the disklabel for wd2s2. If the 'disk:' field in the label says wd1 that may be your problem. I think is our installer that have some problems :-) Btw I'll check it, but also is to investigate if it's true why installer put it there :-) Thanks for your kind reply Best Regards, Gianmarco Giovannelli , Unix expert since yesterday http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: panic mount root failed
:Env: : :Yesterday I went to a friends house for installing a box from the freebsd :3.0-release cdrom (I have also the src and obj very current on another cd :to do a quick make installword :-). : :He has : :1 hd master (A) + 1 cdrom slave on primary ch. :1 hd master (B) + 1 zip atapi slave on secundary ch. : :on (A) there is a primary win98 partition. on (B) there is a fat partition :on wd2s1 and a freebsd installation on wd2s2a. : :The installation procedure was fine, but at the next reboot it can't mount :the root fs because it tries to mount / on wd1s2a even if in /etc/fstab :there is wd2s2a ! I think it is a problem related to the fact that the :cdrom make confusion on the routine that have to find the hd slice number... : :everything was fine after adding a boot config with 1:wd(2,a)kernel : :Is it a known problem or I miss something ? : Look at the disklabel for wd2s2. If the 'disk:' field in the label says wd1 that may be your problem. It's amazing how many folk remedies people come up with for this one, regardless of the number of times it's solved correctly. So, for everyone bothering to read this, here it is again: You have two IDE disks, wd0 and wd2. You have two BIOS disk devices, 0x80 and 0x81. FreeBSD can't tell that the disk you're booting from (0x81) is actually wd2 without some help. For 3.0 and earlier systems, you would use 1:wd(2,a)kernel at the boot: prompt. For 3.1 and later systems, use: set root_disk_unit=2 at the loader prompt. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ m...@smith.net.au \\ The race is long, and in the \\ msm...@freebsd.org \\ end it's only with yourself. \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: axp kernel breakage
cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h -mno-fp-regs -Wa,-mev56 ../../nfs/nfs_syscalls.c ../../nfs/nfs_syscalls.c:924: `sysctl__vfs_nfs_children' undeclared here (not in a function) ../../nfs/nfs_syscalls.c:924: initializer element for `sysctl___vfs_nfs_defect.oid_parent' is not constant ../../nfs/nfs_syscalls.c:92: warning: `nfsrv_zapsock' declared `static' but never defined *** Error code 1 Not *quite* sure where its coming from. The new SYSCTL_DECL() is in an ifdef tangle for NFS_NOSERVER, so it only works if NFS_NOSERVER is not defined. Bruce To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
