Re: 9.0 bsdinstall usage
On 23/09/2011, at 11:39, Fbsd8 wrote: > I have installed 9.0 bata2 from cd and the net. In both cases after the > completion of the install and rebooting, the bsdinstall scripts still remain > on the new installed system. If I interpret the code logic correctly, > bsdinstall can ONLY be used for an original install. It's not intended by > design to be used any other time, unlike sysinstall. I think the "auto" > script should have code added to remove all traces of the bsdinstall > environment at the conclusion of the install. This way bsdinstall fulfills > the original design goals and guarantees no one can exec it by accident and > kill there running system. The binary is installed by default, but there it isn't run at startup. If it is being run then I would expect you are booting off your install media again by accident. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: 9.0 beta2 & the new bsdinstaller
On Wed, Sep 21, 2011 at 08:26:47AM + I heard the voice of Thomas Mueller, and lo! it spake thus: > > I don't think there is any particular advantage in aligning GPT > partitions on 1 MB boundaries. No, but it's bg, and rund! (http://dilbert.com/fast/1994-03-24/) It's a nice round number, and with even the by-modern-standards smallish drives I was using, it rounds to 0 "wasted" space. So I figured, what does it hurt? My mail was just to say IWBNI the hurt was more "Hey, this probably isn't going to work, are you sure?" rather than "Hahaha, you think you can boot?? Sucker!" -- Matthew Fuller (MF4839) | fulle...@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: 9.0 bsdinstall usage
On 23 September 2011 10:09, Fbsd8 wrote: > I have installed 9.0 bata2 from cd and the net. In both cases after the > completion of the install and rebooting, the bsdinstall scripts still remain > on the new installed system. If I interpret the code logic correctly, > bsdinstall can ONLY be used for an original install. It's not intended by > design to be used any other time, unlike sysinstall. I think the "auto" > script should have code added to remove all traces of the bsdinstall > environment at the conclusion of the install. This way bsdinstall fulfills > the original design goals and guarantees no one can exec it by accident and > kill there running system. Have you thought about filing PRs for your installer suggestions, just so they don't get lost? I've just filed a bsdinstaller PR for a wifi config bug; I'm likely going to file a few more PRs based on my interaction with the installer. Thanks, Adrian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ataidle + notebook hdd + 9.0-BETA2
On Sat, September 17, 2011 11:02, Tijl Coosemans wrote: > On Wednesday 14 September 2011 05:59:05 Nenhum_de_Nos wrote: >> I just installed BETA2 on WD notebook disk: >> >> ada0 at ata2 bus 0 scbus1 target 0 lun 0 >> ada0: ATA-8 SATA 2.x device >> ada0: 150.000MB/s transfers (SATA, UDMA5, PIO 8192bytes) >> ada0: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C) >> ada0: Previously was known as ad4 >> >> and tried as usual to make the disk last a little longer: >> >> rush# ataidle -P 243 /dev/ad4 >> ataidle: error: identify device /dev/ad4 >> >> rush# ataidle -P 243 /dev/ada0 >> (pass0:ata2:0:0:0): SETFEATURES. ACB: ef 05 00 00 00 40 00 00 00 00 f3 >> 00 >> (pass0:ata2:0:0:0): CAM status: CCB request completed with an error >> Failed to configure APM: No error: 0 >> >> so, is this still needed after ada took place ? How can I do it now if >> needed ? > > Until a more elegant solution is found you can set the APM value like > this: > > camcontrol cmd ada0 -a "EF 05 00 00 00 00 00 00 00 00 F3 00" > > EF is setfeature command > 05 enables APM feature > F3 is 243 > > To disable APM you can use: > > camcontrol cmd ada0 -a "EF 85 00 00 00 00 00 00 00 00 00 00" > > You can check the value with: > > camcontrol identify ada0 thanks, problem solved :) matheus -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
9.0 bsdinstall usage
I have installed 9.0 bata2 from cd and the net. In both cases after the completion of the install and rebooting, the bsdinstall scripts still remain on the new installed system. If I interpret the code logic correctly, bsdinstall can ONLY be used for an original install. It's not intended by design to be used any other time, unlike sysinstall. I think the "auto" script should have code added to remove all traces of the bsdinstall environment at the conclusion of the install. This way bsdinstall fulfills the original design goals and guarantees no one can exec it by accident and kill there running system. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Intel Atom Board + 9.0-BETA2
hail again, has anyone seen these: ACPI Error: Method parse/execution failed [\\_SB_.PCI0.LPC_.SMBR] (Node 0xfe00024af9c0), AE_AML_INFINITE_LOOP (20110527/psparse-560) ACPI Error: Method parse/execution failed [\\_SB_.PCI0.LPC_.INIT] (Node 0xfe00024afa00), AE_AML_INFINITE_LOOP (20110527/psparse-560) ACPI Error: Method parse/execution failed [\\_GPE._L00] (Node 0xfe000220f440), AE_AML_INFINITE_LOOP (20110527/psparse-560) ACPI Exception: AE_AML_INFINITE_LOOP, while evaluating GPE method [_L00] (20110527/evgpe-606) its 9.0-BETA2 amd64. I got it compiling smartmontools and it began, but the box is cold, and after compiled it didn't stop. matheus -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
[head tinderbox] failure on i386/i386
TB --- 2011-09-22 21:50:00 - tinderbox 2.7 running on freebsd-current.sentex.ca TB --- 2011-09-22 21:50:00 - starting HEAD tinderbox run for i386/i386 TB --- 2011-09-22 21:50:00 - cleaning the object tree TB --- 2011-09-22 21:50:47 - cvsupping the source tree TB --- 2011-09-22 21:50:47 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/i386/i386/supfile TB --- 2011-09-22 21:56:11 - building world TB --- 2011-09-22 21:56:11 - MAKEOBJDIRPREFIX=/obj TB --- 2011-09-22 21:56:11 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-09-22 21:56:11 - TARGET=i386 TB --- 2011-09-22 21:56:11 - TARGET_ARCH=i386 TB --- 2011-09-22 21:56:11 - TZ=UTC TB --- 2011-09-22 21:56:11 - __MAKE_CONF=/dev/null TB --- 2011-09-22 21:56:11 - cd /src TB --- 2011-09-22 21:56:11 - /usr/bin/make -B buildworld >>> World build started on Thu Sep 22 21:56:11 UTC 2011 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Thu Sep 22 23:59:38 UTC 2011 TB --- 2011-09-22 23:59:38 - generating LINT kernel config TB --- 2011-09-22 23:59:38 - cd /src/sys/i386/conf TB --- 2011-09-22 23:59:38 - /usr/bin/make -B LINT TB --- 2011-09-22 23:59:38 - building LINT kernel TB --- 2011-09-22 23:59:38 - MAKEOBJDIRPREFIX=/obj TB --- 2011-09-22 23:59:38 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-09-22 23:59:38 - TARGET=i386 TB --- 2011-09-22 23:59:38 - TARGET_ARCH=i386 TB --- 2011-09-22 23:59:38 - TZ=UTC TB --- 2011-09-22 23:59:38 - __MAKE_CONF=/dev/null TB --- 2011-09-22 23:59:38 - cd /src TB --- 2011-09-22 23:59:38 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu Sep 22 23:59:38 UTC 2011 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for LINT completed on Fri Sep 23 00:30:40 UTC 2011 TB --- 2011-09-23 00:30:40 - cd /src/sys/i386/conf TB --- 2011-09-23 00:30:40 - /usr/sbin/config -m GENERIC TB --- 2011-09-23 00:30:40 - building GENERIC kernel TB --- 2011-09-23 00:30:40 - MAKEOBJDIRPREFIX=/obj TB --- 2011-09-23 00:30:40 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-09-23 00:30:40 - TARGET=i386 TB --- 2011-09-23 00:30:40 - TARGET_ARCH=i386 TB --- 2011-09-23 00:30:40 - TZ=UTC TB --- 2011-09-23 00:30:40 - __MAKE_CONF=/dev/null TB --- 2011-09-23 00:30:40 - cd /src TB --- 2011-09-23 00:30:40 - /usr/bin/make -B buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Fri Sep 23 00:30:40 UTC 2011 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for GENERIC completed on Fri Sep 23 00:55:24 UTC 2011 TB --- 2011-09-23 00:55:24 - cd /src/sys/i386/conf TB --- 2011-09-23 00:55:24 - /usr/sbin/config -m PAE TB --- 2011-09-23 00:55:24 - building PAE kernel TB --- 2011-09-23 00:55:24 - MAKEOBJDIRPREFIX=/obj TB --- 2011-09-23 00:55:24 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-09-23 00:55:24 - TARGET=i386 TB --- 2011-09-23 00:55:24 - TARGET_ARCH=i386 TB --- 2011-09-23 00:55:24 - TZ=UTC TB --- 2011-09-23 00:55:24 - __MAKE_CONF=/dev/null TB --- 2011-09-23 00:55:24 - cd /src TB --- 2011-09-23 00:55:24 - /usr/bin/make -B buildkernel KERNCONF=PAE >>> Kernel build for PAE started on Fri Sep 23 00:55:25 UTC 2011 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for PAE completed on Fri Sep 23 01:01:39 UTC 2011 TB --- 2011-09-23 01:01:39 - cd /src/sys/i386/conf TB --- 2011-09-23 01:01:39 - /usr/sbin/config -m XBOX TB --- 2011-09-23 01:01:39 - building XBOX kernel TB --- 2011-09-23 01:01:39 - MAKEOBJDIRPREFIX=/obj TB --- 2011-09-23 01:01:39 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-09-23 01:01:39 - TARGET=i386 TB --- 2011-09-23 01:01:39 - TARGET_ARCH=i386 TB --- 2011-09-23 01:01:39 - TZ=UTC TB --- 2011-09-23 01:01:39 - __MAKE_CONF=/dev/null TB --- 2011-09-23 01:01:39 - cd /src TB --- 2011-09-23 01:01:39 - /usr/bin/make -B buildkernel KERNCONF=XBOX >>> Kernel build for XBOX started on Fri Sep 23 01:01:40 UTC 2011 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for XBOX completed on Fri Sep 23 01:05:27 UTC 2011 TB ---
Re: Recommended methods to upgrade firmware on HBAs
The current firmware(9) mechanism might work for you. The QLogic FC/SCSI cards in FreeBSD use that for loading firmware images to download to the cards, albeit to just load and reset, to update flash. "not to update flash" (locations in flash where to put firmware are not documented by Qlogic) ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Recommended methods to upgrade firmware on HBAs
The current firmware(9) mechanism might work for you. The QLogic FC/SCSI cards in FreeBSD use that for loading firmware images to download to the cards, albeit to just load and reset, to update flash. This allows the drivers themselves to request updates. Note that the root filesystem has to be mounted for this mechanism to work. Other mechanisms include ioctl mechanisms as per what the LSI cards do via the mpiutil and mfiutil programs. On Thu, 22 Sep 2011, David Somayajulu wrote: Hi All, 1. What is the current recommended method for upgrading firmware for HBAs? 2. Is there a mechanism wherein the firmware binary can be provided as a separate file, which is then made accessible to the corresponding device driver during device initialization? 3. Is there a restriction on the size of driver.ko file? If not, is it acceptable to provide the firmware as fw_file.c which is then compiled into the driver. Thanks david S. This message and any attached documents contain information from QLogic Corporation or its wholly-owned subsidiaries that may be confidential. If you are not the intended recipient, you may not read, copy, distribute, or use this information. If you have received this transmission in error, please notify the sender immediately by reply e-mail and then delete this message. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Choosing between DELAY(useconds) and pause()
if (cold) DELAY() else pause() On Sep 22, 2011, at 11:55 AM, David Somayajulu wrote: > It appears that the pause() function cannot be used in driver functions which > are invoked early in the boot process. Is there is a kernel api which a > device driver can use to determine whether to use pause() or DELAY(), for > delays which are say greater than 10hz - may be even 1 hz ? > > Cheers, > David S. > > > > This message and any attached documents contain information from QLogic > Corporation or its wholly-owned subsidiaries that may be confidential. If you > are not the intended recipient, you may not read, copy, distribute, or use > this information. If you have received this transmission in error, please > notify the sender immediately by reply e-mail and then delete this message. > ___ > freebsd-driv...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-drivers > To unsubscribe, send any mail to "freebsd-drivers-unsubscr...@freebsd.org" > > ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Choosing between DELAY(useconds) and pause()
On Thursday 22 September 2011 19:55:23 David Somayajulu wrote: > It appears that the pause() function cannot be used in driver functions > which are invoked early in the boot process. Is there is a kernel api > which a device driver can use to determine whether to use pause() or > DELAY(), for delays which are say greater than 10hz - may be even 1 hz ? Maybe you want to use something like this: if (cold) DELAY() else pause() In your code. --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Choosing between DELAY(useconds) and pause()
It appears that the pause() function cannot be used in driver functions which are invoked early in the boot process. Is there is a kernel api which a device driver can use to determine whether to use pause() or DELAY(), for delays which are say greater than 10hz - may be even 1 hz ? Cheers, David S. This message and any attached documents contain information from QLogic Corporation or its wholly-owned subsidiaries that may be confidential. If you are not the intended recipient, you may not read, copy, distribute, or use this information. If you have received this transmission in error, please notify the sender immediately by reply e-mail and then delete this message. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Recommended methods to upgrade firmware on HBAs
Hi All, 1. What is the current recommended method for upgrading firmware for HBAs? 2. Is there a mechanism wherein the firmware binary can be provided as a separate file, which is then made accessible to the corresponding device driver during device initialization? 3. Is there a restriction on the size of driver.ko file? If not, is it acceptable to provide the firmware as fw_file.c which is then compiled into the driver. Thanks david S. This message and any attached documents contain information from QLogic Corporation or its wholly-owned subsidiaries that may be confidential. If you are not the intended recipient, you may not read, copy, distribute, or use this information. If you have received this transmission in error, please notify the sender immediately by reply e-mail and then delete this message. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
