Re: i386/134986: make installworld fails (FreeBSD-7.2, tr not found)
As reported in the PR, the problem happens with a checkout of RELENG_7_2. http://www.freebsd.org/cgi/query-pr.cgi?pr=i386/134986 I have just tested a checkout of RELENG_7 (STABLE) and in this case make installworld succeeds. -- fernan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
update release schedule information?
Hi, the release schedule information available in http://www.freebsd.org/releases/7.1R/schedule.html is outdated. You probably already know about this ... and I also know 7.1-RELEASE is delayed, but the schedule page does not provide any useful information on what's going to happen next. BETA2 has already passed but it has not been mentioned in this document. The front page for the project (www.freebsd.org) links to ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/ISO-IMAGES/7.1/ with the text 'Upcoming Release 7.1 - BETA2' (but BETA2 is not mentioned in schedule.html) If you navigate to the FTP site using that link now, you'll find that the images for the RC1 are already available (Dec 7th). But the 'actual' dates for the RC1 builds are missing from schedule.html. I'm not familiar with the docproj procedures, but have tried to help by editing the release.ent and schedule.sgml files (patches attached), which looked as the obvious candidates to me. If someone can check them, complete the missing dates in schedule.sgml, and commit the changes, that would be great! Cheers, -- fernan 34c34 < --- > --- www/en/releases/7.1R/schedule.sgml.orig 2008-12-09 13:34:22.0 -0300 +++ www/en/releases/7.1R/schedule.sgml 2008-12-09 13:38:45.0 -0300 @@ -110,6 +110,13 @@ Begin BETA1 builds. + + BETA2 builds + -- + -- + Begin BETA2 builds. + + RELENG_7_1 branch @@ -122,7 +129,7 @@ RC1 builds 15 September 2008 - -- + 7 December 2008 Begin RC1 builds. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [FreeBSD] Fix for ServerWorks HT1000 in upcoming 7.1?
+[ To Kirk Strauser (29.Oct.2008 14:05): | | > On Tuesday 07 October 2008 17:10:49 Xin LI wrote: | > > Did anyone who can trigger the data corruption has tried John's patch | > > and let us know if it worked? | > > | > > Cheers, | > | > I can confirm that it works on my PowerEdge SC1435. With both controllers | > running in SATA150 mode, I have an uptime of 101 days with moderately heavy | > load. | > -- | > Kirk Strauser | | Same here. The ata_ht1000.patch referenced in this thread | works, in my case at least with 1 controller running in | SATA150 mode (I have only 1 disk). | | However, the recent 7.1-BETA2 does not work for me, contrary | to reports saying that this BETA contains the patch. Looking | at the sources, it seems evident that the patch applied is | not identical to the ata_ht1000.patch in this thread. | | This patch: | http://people.freebsd.org/~jhb/patches/ata_ht1000.patch | is the only requirement to turn a broken 7.1-BETA1 into a | working 7.1 for a Dell PowerEdge SC1435. | | The recent 7.1-BETA2, does not work! | | Fernan | +] Hi, I've been tracking the 7.1 release page but so far I haven't seen any update lately ... any news on when a new BETA/RC will be out for testing? Fernan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [EMAIL PROTECTED]: Re: [FreeBSD] Fix for ServerWorks HT1000 in upcoming 7.1?]
On Mon, Nov 10, 2008 at 10:01 AM, Fernan Aguero <[EMAIL PROTECTED]> wrote: > > Date: Wed, 29 Oct 2008 14:05:22 -0300 > From: Fernan Aguero <[EMAIL PROTECTED]> > To: Kirk Strauser <[EMAIL PROTECTED]> > Cc: freebsd-stable@freebsd.org, [EMAIL PROTECTED], >John Baldwin <[EMAIL PROTECTED]>, [EMAIL PROTECTED] > Subject: Re: [FreeBSD] Fix for ServerWorks HT1000 in upcoming 7.1? > >> On Tuesday 07 October 2008 17:10:49 Xin LI wrote: >> > Did anyone who can trigger the data corruption has tried John's patch >> > and let us know if it worked? >> > >> > Cheers, >> >> I can confirm that it works on my PowerEdge SC1435. With both controllers >> running in SATA150 mode, I have an uptime of 101 days with moderately heavy >> load. >> -- >> Kirk Strauser > > Same here. The ata_ht1000.patch referenced in this thread > works, in my case at least with 1 controller running in > SATA150 mode (I have only 1 disk). > > However, the recent 7.1-BETA2 does not work for me, contrary > to reports saying that this BETA contains the patch. Looking > at the sources, it seems evident that the patch applied is > not identical to the ata_ht1000.patch in this thread. > > This patch: > http://people.freebsd.org/~jhb/patches/ata_ht1000.patch > is the only requirement to turn a broken 7.1-BETA1 into a > working 7.1 for a Dell PowerEdge SC1435. > > The recent 7.1-BETA2, does not work! > > Fernan > Hi, can anyone confirm if 7.1-BETA2 works for this platform? It does not for me. Will there be another BETA/RC before 7.1 is rolled out? Thanks, -- fernan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [FreeBSD] Fix for ServerWorks HT1000 in upcoming 7.1?
> On Tuesday 07 October 2008 17:10:49 Xin LI wrote: > > Did anyone who can trigger the data corruption has tried John's patch > > and let us know if it worked? > > > > Cheers, > > I can confirm that it works on my PowerEdge SC1435. With both controllers > running in SATA150 mode, I have an uptime of 101 days with moderately heavy > load. > -- > Kirk Strauser Same here. The ata_ht1000.patch referenced in this thread works, in my case at least with 1 controller running in SATA150 mode (I have only 1 disk). However, the recent 7.1-BETA2 does not work for me, contrary to reports saying that this BETA contains the patch. Looking at the sources, it seems evident that the patch applied is not identical to the ata_ht1000.patch in this thread. This patch: http://people.freebsd.org/~jhb/patches/ata_ht1000.patch is the only requirement to turn a broken 7.1-BETA1 into a working 7.1 for a Dell PowerEdge SC1435. The recent 7.1-BETA2, does not work! Fernan dmesg (7.1-BETA2): Copyright (c) 1992-2008 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-BETA2 #0: Sun Oct 12 20:59:28 UTC 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Dual-Core AMD Opteron(tm) Processor 2210 (1795.51-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x40f13 Stepping = 3 Features=0x178bfbff Features2=0x2001 AMD Features=0xea500800 AMD Features2=0x1f Cores per package: 2 usable memory = 8575381504 (8178 MB) avail memory = 8295841792 (7911 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 ioapic0: Changing APIC ID to 4 ioapic1: Changing APIC ID to 5 ioapic2: Changing APIC ID to 6 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-15 on motherboard ioapic1 irqs 32-47 on motherboard ioapic2 irqs 64-79 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 acpi_hpet0: iomem 0xfed0-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci3: on pcib1 pcib2: at device 13.0 on pci3 pci4: on pcib2 atapci0: port 0xecb0-0xecb7,0xeca0-0xeca3,0xecb8-0xecbf,0xeca4-0xeca7,0xece0-0xecef mem 0xefdfe000-0xefdf irq 6 at device 14.0 on pci3 atapci0: [ITHREAD] ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: [ITHREAD] atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x8c0-0x8cf at device 2.1 on pci0 ata0: on atapci1 ata0: [ITHREAD] ata1: on atapci1 ata1: [ITHREAD] isab0: at device 2.2 on pci0 isa0: on isab0 ohci0: port 0xd000-0xd0ff mem 0xefbed000-0xefbedfff irq 11 at device 3.0 on pci0 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: <(0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0 uhub0: 2 ports with 2 removable, self powered ohci1: port 0xd400-0xd4ff mem 0xefbee000-0xefbeefff irq 11 at device 3.1 on pci0 ohci1: [GIANT-LOCKED] ohci1: [ITHREAD] usb1: OHCI version 1.0, legacy support usb1: on ohci1 usb1: USB revision 1.0 uhub1: <(0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1 uhub1: 2 ports with 2 removable, self powered ehci0: port 0xd800-0xd8ff mem 0xefbef000-0xefbe irq 11 at device 3.2 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb2: EHCI version 1.0 usb2: companion controllers, 2 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: <(0x1166) EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb2 uhub2: 4 ports with 4 removable, self powered uhub3: on uhub2 uhub3: multiple transaction translators uhub3: 2 ports with 2 removable, self powered ums0: on uhub3 ums0: 3 buttons and Z dir. ukbd0: on uhub3 kbd2 at ukbd0 uhid0: on uhub3 vgapci0: port 0xdc00-0xdcff mem 0xe000-0xe7ff,0xefbf-0xefbf irq 44 at device 4.0 on pci0 pcib3: irq 32 at device 7.0 on pci0 pci5: on pcib3 pcib4: irq 33 at device 8.0 on pci0 pci1: on pcib4 bge0: mem 0xefef-0xefef irq 33 at device 0.0 on pci1 miibus0: on bge0 brgphy0: PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto bge0: Ethernet address: 00:1a:a0:1e:3c:3b bge0: [ITHREAD] pcib5: irq 37 at device 9.0 on pci0 pci2: on pcib5 bge1: mem 0xefff-0xefff irq 37 at device 0.0 on pci2 miibus1: on bge1 brgphy1: PHY 1 on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100b
Re: [FreeBSD] Fix for ServerWorks HT1000 in upcoming 7.1?
> > On Friday 10 October 2008 01:11:17 pm Fernan Aguero wrote: > > > John, > > > > > > thanks for the tip. I have now successfully gone through > > > the process of making a new bootable CD using the ATA_HT1000 > > > patched kernel. [snipped] > So far everything seems to be working OK ... compiled and > installed a couple of ports (vim, screen, apache, > portupgrade), and everything looks fine. > > I can run more thourough tests if you want. Just let me know > what those are and guide me through them ... are we still on > time for including this patch in the upcoming 7.1? Will > there be a new beta or RC? > > Fernan I have already built world + kernel and installed some more ports. Again, everything works fine. Should I submit a PR asking for inclusion of this patch? This platform (ServerWorks HT1000, and the Dell PowerEdge SC1435) would not boot 7.0 nor 7.1-BETA. If the patch does not affect other chipsets, it would be good to include it in 7.1-RELEASE. Fernan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [FreeBSD] Fix for ServerWorks HT1000 in upcoming 7.1?
> On Friday 10 October 2008 01:11:17 pm Fernan Aguero wrote: > > John, > > > > thanks for the tip. I have now successfully gone through > > the process of making a new bootable CD using the ATA_HT1000 > > patched kernel. > > > > I have already done a minimal installation of > > FreeBSD-7.1-BETA onto the SC1435 PowerEdge box using this CD > > (BTW dmesg now shows the ad4 disk being recognized as > > SATA150 instead of giving a warning about a bad cable and > > recognizing it as an ATA drive). > > > > But I'm stuck at the last step ... > > > > > Just be sure that once you've installed the box, > > > you copy the updated kernel onto the box somehow before you > > > reboot from the > > > installer (you can use the fixit shell to help with this). > > > > I'm at the holographic emergency shell, and df(1) shows all > > the partitions in ad4s1 mounted under /mnt. So my idea is to > > cp boot/kernel/kernel /mnt/boot/kernel/ > > but when I do an ls(1) the /mnt directory appears to be empty ... > > > > However I'm unable to umount it! > > > > My recollection: > > $ df -h > > /dev/ad4s1a => /mnt > > /dev/ad4s1d => /mnt/tmp > > /dev/ad4s1e => /mnt/usr > > ... > > $ ls /mnt/boot > > boot: no such file or directory > > $ ls /mnt/ > > . .. > > $ umount /mnt > > device is busy > > > > I'm now downloading a 7.1-BETA-livefs ISO and I'll try next to boot > > the box with this CD to see if I can scp the kernel from > > another box ... but any other tip or suggestion is welcome. > > Hmmm, that is odd. I wonder if you are chroot'd into the drive somehow? > That > really shouldn't be though. > > -- > John Baldwin John Sorry for the delay in replying, I had no access to this box for the whole weekend. I finally managed to replace the stock kernel with the patched one before booting with the OS installed on disk. For some reason, the emergency shell launched from the install session had ad4s1 partitions mounted under /mnt and would not give up on them ... I just rebooted the box with the same patched CD, and using the livefs CD managed to bring up the bge0 interface, and replace the stock kernel with the patched one from an nfs-mounted partition. So far everything seems to be working OK ... compiled and installed a couple of ports (vim, screen, apache, portupgrade), and everything looks fine. I can run more thourough tests if you want. Just let me know what those are and guide me through them ... are we still on time for including this patch in the upcoming 7.1? Will there be a new beta or RC? Fernan PS: Output of dmesg (7.1-BETA w/ata_ht1000.patch) = Copyright (c) 1992-2008 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-BETA #0: Fri Oct 10 09:53:34 ART 2008 [EMAIL PROTECTED]:/usr/obj/raid10/freebsd/freebsd-7.1-beta/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Dual-Core AMD Opteron(tm) Processor 2210 (1795.51-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x40f13 Stepping = 3 Features=0x178bfbff Features2=0x2001 AMD Features=0xea500800 AMD Features2=0x1f Cores per package: 2 usable memory = 8575381504 (8178 MB) avail memory = 8295841792 (7911 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 ioapic0: Changing APIC ID to 4 ioapic1: Changing APIC ID to 5 ioapic2: Changing APIC ID to 6 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-15 on motherboard ioapic1 irqs 32-47 on motherboard ioapic2 irqs 64-79 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 acpi_hpet0: iomem 0xfed0-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci3: on pcib1 pcib2: at device 13.0 on pci3 pci4: on pcib2 atapci0: port 0xecb0-0xecb7,0xeca0-0xeca3,0xecb8-0xecbf,0xeca4-0xeca7,0xece0-0xecef mem 0xefdfe000-0xefdf irq 6 at device 14.0 on pci3 atapci0: [ITHREAD] ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: [ITHREAD] ata4: on a
Re: [FreeBSD] Fix for ServerWorks HT1000 in upcoming 7.1?
> On Wednesday 08 October 2008 04:33:25 pm Fernan Aguero wrote: > > > On Wednesday 08 October 2008 06:15:15 am Fernan Aguero wrote: > > > > > Did anyone who can trigger the data corruption has tried John's patch > > > > > and let us know if it worked? > > > > > > > > Not yet. My problem is that it's not that easy ... (at least > > > > for me, but maybe I'm missing something). > > > > > > > > The main issue for me is that I don't have a spare box > > > > running 7.x. All my FreeBSD boxes are running 6.x > > > > > > > > I've tried to make a new 7.1-BETA bootable ISO from the > > > > patched sources (make release), but failed ... this is the > > > > first time I've ever attempted this, and it seems that you > > > > cannot do that from a 6.x box (I have a full CVS mirror of > > > > FreeBSD, and a fresh checkout of RELENG_7). > > > > > You can just grab the existing iso, > > > > OK > > > > > untar it into a directory, > > > > OK > > > > > build your own GENERIC kernel and replace the > > > /boot/kernel/kernel in the iso tree, > > > > Will I be able to do this using a 7.x checkout on a 6.x box? > > You can use 'make kernel-toolchain' followed by 'make buildkernel' on a 6.x > box to build a 7.x kernel though. > -- > John Baldwin John, thanks for the tip. I have now successfully gone through the process of making a new bootable CD using the ATA_HT1000 patched kernel. I have already done a minimal installation of FreeBSD-7.1-BETA onto the SC1435 PowerEdge box using this CD (BTW dmesg now shows the ad4 disk being recognized as SATA150 instead of giving a warning about a bad cable and recognizing it as an ATA drive). But I'm stuck at the last step ... > Just be sure that once you've installed the box, > you copy the updated kernel onto the box somehow before you > reboot from the > installer (you can use the fixit shell to help with this). I'm at the holographic emergency shell, and df(1) shows all the partitions in ad4s1 mounted under /mnt. So my idea is to cp boot/kernel/kernel /mnt/boot/kernel/ but when I do an ls(1) the /mnt directory appears to be empty ... However I'm unable to umount it! My recollection: $ df -h /dev/ad4s1a => /mnt /dev/ad4s1d => /mnt/tmp /dev/ad4s1e => /mnt/usr ... $ ls /mnt/boot boot: no such file or directory $ ls /mnt/ . .. $ umount /mnt device is busy I'm now downloading a 7.1-BETA-livefs ISO and I'll try next to boot the box with this CD to see if I can scp the kernel from another box ... but any other tip or suggestion is welcome. Fernan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [FreeBSD] Fix for ServerWorks HT1000 in upcoming 7.1?
> On Wednesday 08 October 2008 06:15:15 am Fernan Aguero wrote: > > > Did anyone who can trigger the data corruption has tried John's patch > > > and let us know if it worked? > > > > Not yet. My problem is that it's not that easy ... (at least > > for me, but maybe I'm missing something). > > > > The main issue for me is that I don't have a spare box > > running 7.x. All my FreeBSD boxes are running 6.x > > > > I've tried to make a new 7.1-BETA bootable ISO from the > > patched sources (make release), but failed ... this is the > > first time I've ever attempted this, and it seems that you > > cannot do that from a 6.x box (I have a full CVS mirror of > > FreeBSD, and a fresh checkout of RELENG_7). > You can just grab the existing iso, OK > untar it into a directory, OK > build your own GENERIC kernel and replace the > /boot/kernel/kernel in the iso tree, Will I be able to do this using a 7.x checkout on a 6.x box? > then use mkisofs to build a new ISO. Just be sure that > once you've installed the box, you copy the updated kernel > onto the box somehow before you reboot from the installer > (you can use the fixit shell to help with this). Gotcha. > -- > John Baldwin Fernan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [FreeBSD] Fix for ServerWorks HT1000 in upcoming 7.1?
> Did anyone who can trigger the data corruption has tried John's patch > and let us know if it worked? Not yet. My problem is that it's not that easy ... (at least for me, but maybe I'm missing something). The main issue for me is that I don't have a spare box running 7.x. All my FreeBSD boxes are running 6.x I've tried to make a new 7.1-BETA bootable ISO from the patched sources (make release), but failed ... this is the first time I've ever attempted this, and it seems that you cannot do that from a 6.x box (I have a full CVS mirror of FreeBSD, and a fresh checkout of RELENG_7). The next thing to do (which I already tried once, and that was also not an painless path) is to boot the box with FreeBSD-6.1 (amd64, no data corruption here) and upgrade to 7.x patching the sources along the way. I need to find a free afternoon in my agenda to fit this ... I will get back with info as soon as I have done it. Fernan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [FreeBSD] Fix for ServerWorks HT1000 in upcoming 7.1?
> At 05:34 PM 9/30/2008, Fernan Aguero wrote: > >> I've been following the "HT1000 chipset errata saga" thread, and the >> commits by sos@ to CVS (around Jan 2008), but have not seen other more >> recent posts about this issue ... is it because it's already fixed and >> working fine for everyone? >> >> http://lists.freebsd.org/pipermail/freebsd-current/2008-March/084272.html > > Yes, we ran into this yesterday on a fresh install using the 7.1 beta CD as > it was set to PATA mode by accident. Also, on some earlier BIOS revs, we > had to turn off "enable USB legacy mode" as well as "EHCI handoff". By > default we set those to disabled as it seems to sometimes create a high > interrupt load on the USB bus if its enabled. Thanks for the tip. Unfortunately, the PowerEdge SC1435 BIOS does not allow much options here ... I can set the embedded SATA to 'ATA mode' (corruption hell, tested with 7.1 BETA) or just turn it 'OFF' in which case the FreeBSD installer sees no disk present. This is on BIOS v1.1.2. A newer v1.4.4 is available and I'm now researching how to update the BIOS to see if that helps. > If you forget to set the mode to SATA, the dmesg will look like > > Sep 30 13:37:08 dev2 kernel: ad4: DMA limited to UDMA33, device found > non-ATA66 cable > Sep 30 13:37:08 dev2 kernel: ad4: 152627MB at > ata2-master UDMA33 > > and you will indeed get corruption > > Turning onto normal SATA mode in the BIOS, you should see > > Sep 30 16:14:15 dev2 kernel: ad4: 152627MB at > ata2-master SATA150 > > ... And everything works great. > > Start with > ftp://ftp.freebsd.org//pub/FreeBSD/releases/i386/ISO-IMAGES/7.1/7.1-BETA-i386-disc1.iso I've used the amd64 version ... don't know if that makes any difference, though. Fernan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[FreeBSD] Fix for ServerWorks HT1000 in upcoming 7.1?
Hi, I have a server (Dell PowerEdge SC1435, ServerWorks HT1000) on which I'd like to try installing FreeBSD. I've already failed to make 7.0 work on this box and was wondering if you have information about the behavior of the upcoming 7.1 on this hardware. I've been following the "HT1000 chipset errata saga" thread, and the commits by sos@ to CVS (around Jan 2008), but have not seen other more recent posts about this issue ... is it because it's already fixed and working fine for everyone? http://lists.freebsd.org/pipermail/freebsd-current/2007-December/081429.html http://lists.freebsd.org/pipermail/freebsd-current/2008-March/084272.html Thanks in advance for any update on this, -- fernan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: buildworld error (texinfo)
+[ To Kent Stewart <[EMAIL PROTECTED]> (31.Mar.2006 21:42): | | | This looks like you were running with a -j? set and you aren't seeing | | the real error. It was hidden somewhere. | | Yes I was running with -j | | | I have only found setting -j to be of value on smp systems. You may have | | actually slowed your buildworld down. | | OK, I'm now running without -j ... let's see where it stops | now. | | Thanks for the suggestion, | +] Of course it was my fault, I had SENDMAIL_MC defined in /etc/make.conf and pointing to a non-existent file. As for using '-j' I just learned about it following an example from the handbook, and got used to it. Thanks again, Fernan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: buildworld error (texinfo)
+[ Kent Stewart <[EMAIL PROTECTED]> (31.Mar.2006 21:29): | | On Friday 31 March 2006 15:28, Fernan Aguero wrote: | > Hi! | > | > I've just cvsuped to the latest RELENG_6_0 (p6) and I can't | > get buildworld to finish ... this is the second time I got | > stopped at the same place: [snipped] | > gzip -cn texinfo.info > texinfo.info.gz | > 1 error | > *** Error code 2 | > 1 error | > *** Error code 2 | > 1 error | | This looks like you were running with a -j? set and you aren't seeing | the real error. It was hidden somewhere. Yes I was running with -j | I have only found setting -j to be of value on smp systems. You may have | actually slowed your buildworld down. OK, I'm now running without -j ... let's see where it stops now. Thanks for the suggestion, Fernan | | Kent | +] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
buildworld error (texinfo)
Hi! I've just cvsuped to the latest RELENG_6_0 (p6) and I can't get buildworld to finish ... this is the second time I got stopped at the same place: ===> gnu/usr.bin/texinfo/doc (all) makeinfo --no-split -I /usr/src/gnu/usr.bin/texinfo/doc -I /usr/src/gnu/usr.bin/texinfo/doc/../../../../contrib/texinfo/doc /usr/src/gnu/usr.bin/texinfo/doc/../../../../contrib/texinfo/doc/info.texi -o info.info makeinfo --no-split -I /usr/src/gnu/usr.bin/texinfo/doc -I /usr/src/gnu/usr.bin/texinfo/doc/../../../../contrib/texinfo/doc /usr/src/gnu/usr.bin/texinfo/doc/../../../../contrib/texinfo/doc/info-stnd.texi -o info-stnd.info ln -fs /usr/src/gnu/usr.bin/texinfo/doc/../../../../contrib/texinfo/doc/texinfo.txi texinfo.texi makeinfo --no-split -I /usr/src/gnu/usr.bin/texinfo/doc -I /usr/src/gnu/usr.bin/texinfo/doc/../../../../contrib/texinfo/doc texinfo.texi -o texinfo.info gzip -cn info.info > info.info.gz gzip -cn info-stnd.info > info-stnd.info.gz gzip -cn texinfo.info > texinfo.info.gz 1 error *** Error code 2 1 error *** Error code 2 1 error I don't know what is going on, but texinfo.info and texinfo.info.gz seem to be OK: [EMAIL PROTECTED] ls -l /usr/obj/usr/src/gnu/usr.bin/texinfo/doc/ total 1232 -rw-r--r-- 1 root wheel 124715 Mar 31 18:19 info-stnd.info -rw-r--r-- 1 root wheel 32549 Mar 31 18:19 info-stnd.info.gz -rw-r--r-- 1 root wheel 65264 Mar 31 18:19 info.info -rw-r--r-- 1 root wheel 20820 Mar 31 18:19 info.info.gz -rw-r--r-- 1 root wheel 769695 Mar 31 18:19 texinfo.info -rw-r--r-- 1 root wheel 206881 Mar 31 18:19 texinfo.info.gz lrwxr-xr-x 1 root wheel 76 Mar 31 18:19 texinfo.texi -> /usr/src/gnu/usr.bin/texinfo/doc/../../../../contrib/texinfo/doc/texinfo.txi [EMAIL PROTECTED] cd /usr/obj/usr/src/gnu/usr.bin/texinfo/doc/ [EMAIL PROTECTED] gzip -dc texinfo.info.gz > texinfo.info.2 [EMAIL PROTECTED] md5 texinfo.info* MD5 (texinfo.info) = f64fd991c84113a5d55dfa855196a970 MD5 (texinfo.info.2) = f64fd991c84113a5d55dfa855196a970 Just FYI, I did the following before beginning the build: cd /usr/src chflags -R noschg /usr/obj && rm -rf /usr/obj/* make clean && make -j4 buildworld Thanks for your help, Fernan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: make installworld fails on libperl.a
Sorry for the delay in replying. Thanks Jukka and Rudolph for pointing me to the problem. Both of you were right. I had built perl-5.6.1 from ports in the build host and my /etc/make.conf had some entries introduced by the use.perl script. I just copied the make.conf file to the install host and everything worked fine. Fernan +[ Jukka Simila <[EMAIL PROTECTED]> (14.Feb.2003 17:57): | | On Fri, 2003-02-14 at 20:59, Fernan Aguero wrote: | > I am using a FreeBSD-4.7-STABLE (Jan24) to build world and | > kernel for an older machine (Pentium1). | > | > buildworld and buildkernel proceed OK on the build host. | > | > In the install host I do: | > | > mount build:/usr/src /usr/src | > mount build:/usr/obj /usr/obj | > makeinstallworld | | maybe you have differing /etc/make.conf files on the two hosts? | | if the build host isn't building perl, | you definitely get errors on the install host.. | +] -- F e r n a n A g u e r o http://genoma.unsam.edu.ar/~fernan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
make installworld fails on libperl.a
I am using a FreeBSD-4.7-STABLE (Jan24) to build world and kernel for an older machine (Pentium1). buildworld and buildkernel proceed OK on the build host. In the install host I do: mount build:/usr/src /usr/src mount build:/usr/obj /usr/obj makeinstallworld and then I get an error about a missing perl library. This already occurred twice, in the last two days (I cvsup my sources daily). Has this been noticed already? Error messages below. Fernan Quoting the last lines of the output: ... ... ===> gnu/usr.bin/perl ===> gnu/usr.bin/perl/libperl install -C -o root -g wheel -m 444 libperl.a /usr/lib install: libperl.a: No such file or directory *** Error code 71 Stop in /usr/src/gnu/usr.bin/perl/libperl. *** Error code 1 Stop in /usr/src/gnu/usr.bin/perl. *** Error code 1 Stop in /usr/src/gnu/usr.bin. *** Error code 1 Stop in /usr/src/gnu. *** Error code 1 Stop in /usr/src. *** Error code 1 -- F e r n a n A g u e r o http://genoma.unsam.edu.ar/~fernan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: make buildworld fails on sdiff
+[ Ruslan Ermilov ([EMAIL PROTECTED]) dijo sobre "Re: make buildworld fails on sdiff": | | Re-cvsup, it's been fixed already. | +] Thanks. That did it. However i was suprised to hear David say that: | If this was with -jN (N numeric), the "real" error is likely to be | somewhat above the lines you quoted; please check -- or try to re-create | the problem without the -j flag -- if, in fact, you used such a flag. | | The reason I suspect this is that the error isn't readily apparent from | the lines you quoted. Of course I tried the buildworld with -j4. But that wasn't the problem (I did that many times before with success) Thanks again. Fernan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Vinum vs. hardware RAID (was: RAID5)
+[ Adrian Wontroba ([EMAIL PROTECTED]) dijo sobre "Re: Vinum vs. hardware RAID (was: +RAID5)": | | Disks are cheap, and capacities constantly expand. Correction: IDE disks are cheap. | Backup devices and media are expensive, wear out, and if they were big | enough when you bought them, soon are not, leaving you with the pain of | swapping media during backups. Tape stackers etc are expensive. | | If you decide that what you really want to protect yourself against is | disk failure, RAID becomes an attractive option. As always, YMMV, but if you also want to protect from other things, then having an external backup (tape, CD, removable hard disk) is something that can save you _lots_ of trouble. Just imagine your machine compromised and having to reinstall everything from scratch ... a mirroring RAID would be of no use. | -- | Adrian Wontroba | +] -- | F e r n a n A g u e r o | B i o i n f o r m a t i c s | | [EMAIL PROTECTED] | genoma.unsam.edu.ar | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
