Booting with a Mylex-DAC960PL Installed
I downloaded Jan 2nd Current, made the floppies, and tried to boot a box with a DAC-960PL installed. The system hung as soon as it started to read from floppy. Rebooted, turned off the BIOS on the Mylex, system booted OK. Installed directly to the Mylex, and it all came to a halt with "Tried to write beyond end of drive" errors, which I am assuming is a geometry issue. Any ideas, short of booting from a separate disk? PS - The BIOS on the Mylex is Current. Lawrence Farr EPC Direct T:01179666123 F:01179666111 M:07970780901 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Mylex Support
This message was sent from Geocrawler.com by "Lawrence Farr" <[EMAIL PROTECTED]> Be sure to reply to that address. Has the Mylex RAID support been fixed or dropped? I could'nt see any mention of it in the hardware.txt for the release candidate. Geocrawler.com - The Knowledge Archive To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Mylex Support
I have 4 different Mylex DAC960 controllers that I cannot install Current onto. (Tried from Late December to 2307). Sysinstall seems to get the geometry wrong, and even telling sysinstall the "correct" geometry, it gives a "tied to write beyond end of drive" error. Booting from a running -current and formatting does the same. They all have the latest BIOS, and they have been tried with various drive combinations. Has anyone else got this to work successfully or is it just me?. And if it is just me, anyone got any ideas? I have been pestering Mike Smith about this for ages, and have probably driven him mad! Lawrence Farr EPC Direct To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mylex Support
OK. How about if I put the controller in a spare PC, stick a -current on there, and give you telnet access? Hopefully it _is_ just something stupid I'm doing, but at least that will cure my problem. If it's not, it may be a problem for others as well. Lawrence To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Samba Performance
I have installed a couple of FreeBSD machines using 3.3-Release, which have Appletalk over IP and samba access to them. On a write to a shared disk, the Macs can write at about 9000kb/sec (Measured with Helios LAN test). From a P3-500 via samba over switched fast ethernet I get about 100Kb/sec. to the same disk. I have added the usual socket options, and upped the recieve buffer size. On a read from the same machine, it is comparable to the Mac. The same machine running Linux was about equal on both. I have also made samba from source, which made no difference. Any bright ideas? Lawrence Farr EPC Direct T:01179666123 F:01179666111 M:07970780901 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: FreeBSD 5.0 as SOHO firewall, gateway -- STABLE?
Im running a CURRENT gateway at home with an iSDN line and a wireless card in hostap mode. Hasn't missed a beat since I replaced the previous (4.7) with DP2. Lawrence Farr EPC Direct Limited > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On Behalf Of > Thomas T. Veldhouse > Sent: 11 February 2003 16:27 > To: [EMAIL PROTECTED] > Subject: FreeBSD 5.0 as SOHO firewall, gateway -- STABLE? > > > I have been watching this list and I have not seen much talk about the > stability of FreeBSD 5.0 (RELENG_5_0) or of its use as a > server? I did see > that some people have upgraded their 4.7 servers to 5.0. Can > anybody relate > their experience with the OS release? I am looking for cases > in particular > for SOHO firewall/gateway environments. I have been waiting > for Java and it > looks as if this release just might offer the features I need. > > Thanks in advance, > > Tom Veldhouse > > > 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
Wireless Problems
I have a hostap box that lives under my stairs with: wi0: mem 0xffbef000-0xffbe irq 11 at device 11.0 on pci0 wi0: 802.11 address: 00:05:5d:ee:23:57 wi0: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI) wi0: Intersil Firmware: Primary (1.0.7), Station (1.3.5) wi0: supported rates: 1Mbps 2Mbps 5.5Mbps 11Mbps ifpi0: port 0xff80-0xff9f mem 0xffbeec00-0xffbeec1f irq 10 at device 17.0 on pci0 And I've also tried: wi0: mem 0xffbef000-0xffbe irq 11 at device 11.0 on pci0 wi0: 802.11 address: 00:09:5b:11:fa:2d wi0: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI) wi0: Intersil Firmware: Primary (1.0.7), Station (1.3.6) wi0: supported rates: 1Mbps 2Mbps 5.5Mbps 11Mbps Initialising with the line: ifconfig_wi0="inet 192.168.10.254 netmask 255.255.255.0 media DS/11Mbps mediaopt hostap ssid gate channel 6" The problem I have is that the most I can get out of it is 502k/sec on a laptop, and 192k on a P4 2.4Ghz next to it. Messages is full of: Feb 12 22:38:03 gate kernel: wi0: tx failed, retry limit exceeded Feb 12 22:38:04 gate last message repeated 7 times It's fairly recent: FreeBSD gate.bka.epcdirect.co.uk 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Sat Feb 8 11:31:01 GMT 2003 Any ideas anyone? Or am I expecting too much at 192k/second from hostap? The server is less than 6 feet away from the PC's. Lawrence Farr EPC Direct Limited To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Adaptec AIC7902 Ultra320 Problems
I have a Supermicro SuperServer 6013P-8, with: ahd0: port 0x4000-0x40ff,0x4400-0x44ff mem 0xfc30-0xfc301fff irq 5 at device 2.0 on pci3 aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 101-133Mhz, 512 SCBs ahd1: port 0x4800-0x48ff,0x4c00-0x4cff mem 0xfc302000-0xfc303fff irq 5 at device 2.1 on pci3 aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X 101-133Mhz, 512 SCBs Trying to install 5.1-CURRENT-20030709-JPSNAP or 4.8-STABLE on the box gives a timeout error that will hang the disk in a state that resetting the machine does not clear, and only power cycling will clear. Ive replaced the disks with no change, but installed and ran Redhat 7.3 on the box with no timeouts or errors. The full dmesg is here: http://aticatac.epcdirect.co.uk/~l.farr/6013P8_dmesg.txt And timeout is here: http://aticatac.epcdirect.co.uk/~l.farr/AIC7902_timeout.txt Lawrence Farr EPC Direct Limited ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Adaptec AIC7902 Ultra320 Problems
OK, gave that a go, and still the same. Im assuming you meant to set it to 160 in the Adaptec bios? It shows up as 160Mb transfers in the dmesg now. Any other ideas I can try? Lawrence Farr EPC Direct Limited > -Original Message- > From: Sergey A. Osokin [mailto:[EMAIL PROTECTED] > Sent: 22 July 2003 13:43 > To: Lawrence Farr > Cc: [EMAIL PROTECTED] > Subject: Re: Adaptec AIC7902 Ultra320 Problems > > > On Tue, Jul 22, 2003 at 01:23:18PM +0100, Lawrence Farr wrote: > > I have a Supermicro SuperServer 6013P-8, with: > > > > ahd0: port > > 0x4000-0x40ff,0x4400-0x44ff mem 0xfc30-0xfc301fff irq 5 > at device 2.0 on > > pci3 > > aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X > 101-133Mhz, 512 SCBs > > ahd1: port > > 0x4800-0x48ff,0x4c00-0x4cff mem 0xfc302000-0xfc303fff irq 5 > at device 2.1 on > > pci3 > > aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X > 101-133Mhz, 512 SCBs > > > > Trying to install 5.1-CURRENT-20030709-JPSNAP or 4.8-STABLE on the > > box gives a timeout error that will hang the disk in a state that > > resetting the machine does not clear, and only power cycling will > > clear. Ive replaced the disks with no change, but installed and > > ran Redhat 7.3 on the box with no timeouts or errors. > > > > The full dmesg is here: > > http://aticatac.epcdirect.co.uk/~l.farr/6013P8_dmesg.txt > > > > And timeout is here: > > http://aticatac.epcdirect.co.uk/~l.farr/AIC7902_timeout.txt > > Try to switch your adapter from Ultra320 to Ultra160 mode, then > try to install again. > > -- > > Rgdz,/"\ ASCII RIBBON CAMPAIGN > Sergey Osokin aka oZZ, \ /AGAINST HTML MAIL > http://ozz.pp.ru/ X AND NEWS > / \ > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Adaptec AIC7902 Ultra320 Problems
It still does the same timeout and hangs the disc. Theres the option of "Installed OS" which you can set to Other, Win95, Win98, WinME or Win2000. (I've only tried "Other" and "Win2000" in all honesty). Lawrence Farr EPC Direct Limited > -Original Message- > From: Scott Long [mailto:[EMAIL PROTECTED] > Sent: 22 July 2003 16:12 > To: Lawrence Farr > Cc: [EMAIL PROTECTED] > Subject: Re: Adaptec AIC7902 Ultra320 Problems > > > Lawrence Farr wrote: > > I have a Supermicro SuperServer 6013P-8, with: > > > > ahd0: port > > 0x4000-0x40ff,0x4400-0x44ff mem 0xfc30-0xfc301fff irq 5 > at device 2.0 on > > pci3 > > aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X > 101-133Mhz, 512 SCBs > > ahd1: port > > 0x4800-0x48ff,0x4c00-0x4cff mem 0xfc302000-0xfc303fff irq 5 > at device 2.1 on > > pci3 > > aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X > 101-133Mhz, 512 SCBs > > > > Trying to install 5.1-CURRENT-20030709-JPSNAP or 4.8-STABLE on the > > box gives a timeout error that will hang the disk in a state that > > resetting the machine does not clear, and only power cycling will > > clear. Ive replaced the disks with no change, but installed and > > ran Redhat 7.3 on the box with no timeouts or errors. > > > > The full dmesg is here: > > http://aticatac.epcdirect.co.uk/~l.farr/6013P8_dmesg.txt > > > > And timeout is here: > > http://aticatac.epcdirect.co.uk/~l.farr/AIC7902_timeout.txt > > > > Lawrence Farr > > EPC Direct Limited > > Timeouts usually point to interrupt routing problems. Try > booting with > ACPI turned off. > > Scott > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Adaptec AIC7902 Ultra320 Problems
I've got another drive now to mess about with: da0: Fixed Direct Access SCSI-3 device And I get the same problems. Running non-packetized fixes it. Are you sure this is a firmware issue? Lawrence Farr EPC Direct Limited > -Original Message- > From: Justin T. Gibbs [mailto:[EMAIL PROTECTED] > Sent: 22 July 2003 17:46 > To: Lawrence Farr; [EMAIL PROTECTED] > Subject: Re: Adaptec AIC7902 Ultra320 Problems > > > > I have a Supermicro SuperServer 6013P-8, with: > > > > ahd0: port > > 0x4000-0x40ff,0x4400-0x44ff mem 0xfc30-0xfc301fff irq 5 > at device 2.0 on > > pci3 > > aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X > 101-133Mhz, 512 SCBs > > ahd1: port > > 0x4800-0x48ff,0x4c00-0x4cff mem 0xfc302000-0xfc303fff irq 5 > at device 2.1 on > > pci3 > > aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X > 101-133Mhz, 512 SCBs > > > > Trying to install 5.1-CURRENT-20030709-JPSNAP or 4.8-STABLE on the > > box gives a timeout error that will hang the disk in a state that > > resetting the machine does not clear, and only power cycling will > > clear. Ive replaced the disks with no change, but installed and > > ran Redhat 7.3 on the box with no timeouts or errors. > > The problem you are encountering looks to be a drive firmware issue > exposed when the drive is running at high queue depths. The linux > driver limites the tag depth to 32 by default. The FreeBSD driver > does not throttle in this way. It seems that we just overwhelm the > drive with commands and it just stops doing anything on the > bus. According > to the timeout trace, the target just stopped sending packets while > still sitting on the bus. > > I have not tested this particular drive, so I do not know if update > firmware is available for it. You might try running in non-packetized > mode by toggling this option via SCSI-Select. You previous test of > running at "160" just reduced the clock rate, but still > allowed the use > of the newer, faster, packetized format. > > -- > Justin > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
fxp floods network on panic
I have an up to date SMP machine with an Intel 10/100 card and fxp driver. The machine has started to panic during running make release, and when it does, the intel card floods the network and pretty much wipes it out. ie no machines on the same switch can even ping each other. The switch is lit up like a christmas tree, and rebooting the box immediately brings the network to life. The machine is hung solid, so even though I have serial access to it, I cant reboot it to clear the condition. I seem to remember that the Intel card can go into some sort of "test" mode on a panic. Is there any way of preventing this? Or did I just imagine that? Lawrence Farr EPC Direct Limited ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
4 -> 5 Problem
I build 5-CURRENT every night, and NFS export src and obj to my other CURRENT machines to update. I've been doing this quite happily this way for a while. When I try to do an installkernel on a stable machine, I get: [EMAIL PROTECTED]:/usr/src# make installkernel Bad system call (core dumped) *** Error code 140 Stop in /usr/src. I can no longer do this on any of the current boxes either: mkdir -p /boot/kernel install -p -m 555 -o root -g wheel kernel /boot/kernel *** Signal 12 Stop in /usr/obj/usr/src/sys/P6MPFW. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. I tried with -DALWAYS_CHECK_MAKE as well. Have I missed something in UPDATING? Anyone else doing this without issue? the Current target machine is from Thu Sep 25 14:32:19 GMT 2003, the stable one from Mon Mar 24 16:30:45 GMT 2003, and the src and obj are fresh from last night. Lawrence Farr EPC Direct Limited ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: 4 -> 5 Problem
Err yes I did. Im trying to install a kernel. Lawrence Farr EPC Direct Limited > -Original Message- > From: Clement Laforet [mailto:[EMAIL PROTECTED] > Sent: 25 November 2003 16:26 > To: Lawrence Farr > Cc: [EMAIL PROTECTED] > Subject: Re: 4 -> 5 Problem > > On Tue, 25 Nov 2003 16:18:26 - > "Lawrence Farr" <[EMAIL PROTECTED]> wrote: > > > > the Current target machine is from Thu Sep 25 14:32:19 GMT 2003, > > the stable one from Mon Mar 24 16:30:45 GMT 2003, and the > > src and obj are fresh from last night. > > did you read /usr/src/UPDATING ? > > 20031112: > The statfs structure has been updated with 64-bit fields to > allow accurate reporting of multi-terabyte filesystem > sizes. You should build world, then build and boot > the new kernel > BEFORE doing a `installworld' as the new kernel will > know about > binaries using the old statfs structure, but an old > kernel will > not know about the new system calls that support the > new statfs > structure. > > clem > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: 4 -> 5 Problem
I'm still getting this with fresh sources. Has anyone else done 4->5 in the last few days? Is it worth filing a PR? Lawrence Farr EPC Direct Limited > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Lawrence Farr > Sent: 25 November 2003 16:27 > To: 'Clement Laforet' > Cc: [EMAIL PROTECTED] > Subject: RE: 4 -> 5 Problem > > Err yes I did. Im trying to install a kernel. > > Lawrence Farr > EPC Direct Limited > > > -Original Message- > > From: Clement Laforet [mailto:[EMAIL PROTECTED] > > Sent: 25 November 2003 16:26 > > To: Lawrence Farr > > Cc: [EMAIL PROTECTED] > > Subject: Re: 4 -> 5 Problem > > > > On Tue, 25 Nov 2003 16:18:26 - > > "Lawrence Farr" <[EMAIL PROTECTED]> wrote: > > > > > > the Current target machine is from Thu Sep 25 14:32:19 GMT 2003, > > > the stable one from Mon Mar 24 16:30:45 GMT 2003, and the > > > src and obj are fresh from last night. > > > > did you read /usr/src/UPDATING ? > > > > 20031112: > > The statfs structure has been updated with 64-bit fields to > > allow accurate reporting of multi-terabyte filesystem > > sizes. You should build world, then build and boot > > the new kernel > > BEFORE doing a `installworld' as the new kernel will > > know about > > binaries using the old statfs structure, but an old > > kernel will > > not know about the new system calls that support the > > new statfs > > structure. > > > > clem > > > > ___ > [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: 4 -> 5 Problem
I've just tried this again, and noticed an error message that I'd missed: [EMAIL PROTECTED]:/usr/src# make installkernel make: no target to make. "/usr/src/Makefile.inc1", line 157: warning: "make -f /dev/null -m /usr/src/share/mk CPUTYPE=i686 -V CPUTYPE" returned non-zero status cd /usr/obj/usr/src/sys/P6MPFW; MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=i386 MACHINE=i386 CPUTYPE=i686 GROFF_BIN_PATH=/usr/obj/usr/src/i386/legacy/usr/bin GROFF_FONT_PATH=/usr/obj/usr/src/i386/legacy/usr/share/groff_font GROFF_TMAC_PATH=/usr/obj/usr/src/i386/legacy/usr/share/tmac PATH=/usr/obj/usr/src/i386/legacy/usr/sbin:/usr/obj/usr/src/i386/legacy/usr/ bin:/usr/obj/usr/src/i386/legacy/usr/games:/usr/obj/usr/src/i386/usr/sbin:/u sr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/ sbin:/usr/bin make KERNEL=kernel install thiskernel=`sysctl -n kern.bootfile` ; if [ "`dirname "$thiskernel"`" != /boot/kernel ] ; then chflags -R noschg /boot/kernel ; rm -rf /boot/kernel ; else if [ -d /boot/kernel.old ] ; then chflags -R noschg /boot/kernel.old ; rm -rf /boot/kernel.old ; fi ; mv /boot/kernel /boot/kernel.old ; sysctl kern.bootfile=/boot/kernel.old/"`basename "$thiskernel"`" ; fi mkdir -p /boot/kernel install -p -m 555 -o root -g wheel kernel /boot/kernel *** Signal 12 I also tried un-setting CPUTYPE, but got the same error. This gives you a zero sized kernel in /boot/kernel. Running install -p -m 555 -o root -g wheel kernel /boot/kernel from within the correct /obj directory works though. Lawrence Farr EPC Direct Limited > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Lawrence Farr > Sent: 26 November 2003 19:32 > To: [EMAIL PROTECTED] > Subject: RE: 4 -> 5 Problem > > I'm still getting this with fresh sources. Has anyone else done 4->5 > in the last few days? Is it worth filing a PR? > > Lawrence Farr > EPC Direct Limited > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of > Lawrence Farr > > Sent: 25 November 2003 16:27 > > To: 'Clement Laforet' > > Cc: [EMAIL PROTECTED] > > Subject: RE: 4 -> 5 Problem > > > > Err yes I did. Im trying to install a kernel. > > > > Lawrence Farr > > EPC Direct Limited > > > > > -Original Message- > > > From: Clement Laforet [mailto:[EMAIL PROTECTED] > > > Sent: 25 November 2003 16:26 > > > To: Lawrence Farr > > > Cc: [EMAIL PROTECTED] > > > Subject: Re: 4 -> 5 Problem > > > > > > On Tue, 25 Nov 2003 16:18:26 - > > > "Lawrence Farr" <[EMAIL PROTECTED]> wrote: > > > > > > > > the Current target machine is from Thu Sep 25 14:32:19 GMT 2003, > > > > the stable one from Mon Mar 24 16:30:45 GMT 2003, and the > > > > src and obj are fresh from last night. > > > > > > did you read /usr/src/UPDATING ? > > > > > > 20031112: > > > The statfs structure has been updated with 64-bit > fields to > > > allow accurate reporting of multi-terabyte filesystem > > > sizes. You should build world, then build and boot > > > the new kernel > > > BEFORE doing a `installworld' as the new kernel will > > > know about > > > binaries using the old statfs structure, but an old > > > kernel will > > > not know about the new system calls that support the > > > new statfs > > > structure. > > > > > > clem > > > > > > > ___ > > [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]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: 4 -> 5 Problem
I get this error when trying to install the kernel, the same kernel installs fine on the box that made it. [EMAIL PROTECTED]:/usr/src# make installkernel Lawrence Farr EPC Direct Limited > -Original Message- > From: M. Warner Losh [mailto:[EMAIL PROTECTED] > Sent: 02 December 2003 17:16 > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: 4 -> 5 Problem > > In message: <[EMAIL PROTECTED]> > Kris Kennaway <[EMAIL PROTECTED]> writes: > : On Tue, Dec 02, 2003 at 04:33:42PM -, Lawrence Farr wrote: > : > > : > I've just tried this again, and noticed an error message that I'd > : > missed: > : > : > install -p -m 555 -o root -g wheel kernel /boot/kernel > : > *** Signal 12 > : > : This usually means you've tried to update something out of > the correct > : order. > > Signal 12 means thaqt you didn't upgrade your kernel first. > > Warner > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: 4 -> 5 Problem
Does this need a note in UPDATING then? 4-> 5 over NFS, and Older 5-> Newer 5 over NFS no longer work as previous? Lawrence Farr EPC Direct Limited > -Original Message- > From: Barney Wolff [mailto:[EMAIL PROTECTED] > Sent: 02 December 2003 18:32 > To: Lawrence Farr > Cc: 'M. Warner Losh'; [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: 4 -> 5 Problem > > On Tue, Dec 02, 2003 at 05:27:12PM -, Lawrence Farr wrote: > > I get this error when trying to install the kernel, > > the same kernel installs fine on the box that made it. > > > > [EMAIL PROTECTED]:/usr/src# make installkernel > > > > > -Original Message- > > > From: M. Warner Losh [mailto:[EMAIL PROTECTED] > > > Sent: 02 December 2003 17:16 > > > : > > > : > install -p -m 555 -o root -g wheel kernel /boot/kernel > > > : > *** Signal 12 > > > : > > > : This usually means you've tried to update something out of > > > the correct > > > : order. > > > > > > Signal 12 means thaqt you didn't upgrade your kernel first. > > I've observed this when installing on a different system than the > build system. I got it after building/installing several times > on the build system before trying to installkernel on another system > with /usr/src and /usr/obj nfs-mounted. The problem appeared to be > that the stuff in the legacy directory under /usr/obj is built > assuming that what's on the build system will work under the prior > kernel - which is true on the build system but not necessarily on > the target system. > > My solution was to edit (temporarily) /usr/src/Makefile.inc1 to > put /usr/bin first in the PATH set up for the reinstallkernel > target. That allowed make installkernel to succeed on the target > system. Then I rebooted the target and backed out the change to > /usr/src/Makefile.inc1, and after that make installworld and > mergemaster went fine as usual. > > I didn't delve deeply enough to figure out what a cleaner fix would > be, but this should probably be a PR as otherwise the 5.2 upgrade > may be "difficult" for people who build and install on separate boxes. > > -- > Barney Wolff http://www.databus.com/bwresume.pdf > I'm available by contract or FT, in the NYC metro area or via > the 'Net. > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
PXE Boot with Beastie Menu
Has anyone got a working loader.rc for PXE booting Current with the Beastie menu etc. included? The one on freebsd.org is for 4.x machines, which works, but doesn't give you the ACPI options etc. Lawrence Farr EPC Direct Limited ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
