From owner-freebsd-embedded@FreeBSD.ORG Sun Aug 24 18:52:06 2008 Return-Path: Delivered-To: freebsd-embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 74A111065682 for ; Sun, 24 Aug 2008 18:52:06 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from plato.miralink.com (mail.miralink.com [70.103.185.20]) by mx1.freebsd.org (Postfix) with ESMTP id 506388FC13 for ; Sun, 24 Aug 2008 18:52:06 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from localhost (localhost.localdomain [127.0.0.1]) by plato.miralink.com (Postfix) with ESMTP id A162C1A90FC for ; Sun, 24 Aug 2008 11:43:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at X-Spam-Flag: NO X-Spam-Score: -4.399 X-Spam-Level: X-Spam-Status: No, score=-4.399 tagged_above=-10 required=6.6 tests=[ALL_TRUSTED=-1.8, BAYES_00=-2.599] Received: from plato.miralink.com ([127.0.0.1]) by localhost (plato.miralink.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b-AEd85hZsbv for ; Sun, 24 Aug 2008 11:43:22 -0700 (PDT) Received: from [10.47.1.6] (vpn.office.miralink.com [10.0.0.5]) by plato.miralink.com (Postfix) with ESMTP id 0E5BA1A90D4 for ; Sun, 24 Aug 2008 11:43:22 -0700 (PDT) Message-ID: <48B1ADD2.1080507@miralink.com> Date: Sun, 24 Aug 2008 11:52:02 -0700 From: Sean Bruno User-Agent: Thunderbird 2.0.0.16 (X11/20080723) MIME-Version: 1.0 To: freebsd-embedded@freebsd.org References: <48AC7FAF.1060400@miralink.com> <48ACAD2D.9090107@miralink.com> <48ADE8D6.1090906@miralink.com> In-Reply-To: <48ADE8D6.1090906@miralink.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: PAM errors with NANOBSD X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Aug 2008 18:52:06 -0000 Sean Bruno wrote: > Sean Bruno wrote: >> Sean Bruno wrote: >>> I seem to be stumped by my latest issue with NANOBSD. >>> I can't login to the console due to missing pam libs and such. Any >>> and all calls to sudo seem to be blowing up as well. I can only >>> assume that something from my build system is causing pam to be >>> configured. Even though I have explicitly set NO_PAM=YES in my >>> NANOConf, I seem to be jamming up on pam. If I remove the NO_PAM >>> entry, I get the same failure. So perhaps NO_PAM doesn't mean what >>> I think it means? >>> >>> Anyone have a clue what the heck is going on here? >>> >>> ------------------------------------------------------------------------ >>> >> Here's an example from my last build. The system seems to boot fine, >> but then is completely useless at startup: >> >> FreeBSD/i386 (Amnesiac) (ttyd0) >> >> login: root >> Aug 21 07:50:22 login: in openpam_load_module(): no pam_unix.so found >> Aug 21 07:50:22 login: pam_start(): system error >> >> FreeBSD/i386 (Amnesiac) (ttyd0) >> >> login: >> >> > adding or removing "NO_PAM=YES" from the NANOBSD configuration has no > impact on whether or not PAM get's built. So, I'm not sure what the > heck is going on now. > > I mounted the diskimage on my system and verified that > /usr/lib/pam_unix.so exists and is properly built. Any ideas as to > why my disk image is acting like this? > Ok, this is excruciating. I can only assume that I am doing something so completely wrong that it is befuddling the build system and it's not generating an error that would be meaningful. I am using a RELENG_6 build machine to build a RELENG_6 image and I can't seem to figure out what is generating this non-sense PAM error. I'm certain that the correct libs are in place and that everything is being built without errors. Is anyone else using RELENG_6 with NanoBSD right now? This worked pre-6.3 and I can't see anything that would be causing this type of absolute failure. -- Sean Bruno MiraLink Corporation 6015 NE 80th Ave, Ste 100 Portland, OR 97218 Cell 503-358-6832 Phone 503-621-5143 Fax 503-621-5199 MSN: sbruno@miralink.com Google: seanwbruno@gmail.com From owner-freebsd-embedded@FreeBSD.ORG Mon Aug 25 11:06:48 2008 Return-Path: Delivered-To: freebsd-embedded@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A374B1065696 for ; Mon, 25 Aug 2008 11:06:48 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 8B5288FC37 for ; Mon, 25 Aug 2008 11:06:48 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m7PB6ml1027711 for ; Mon, 25 Aug 2008 11:06:48 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m7PB6lHo027707 for freebsd-embedded@FreeBSD.org; Mon, 25 Aug 2008 11:06:47 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 25 Aug 2008 11:06:47 GMT Message-Id: <200808251106.m7PB6lHo027707@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-embedded@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-embedded@FreeBSD.org X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Aug 2008 11:06:48 -0000 Current FreeBSD problem reports Critical problems Serious problems Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o misc/15876 embedded [picobsd] PicoBSD message of the day problems o kern/42728 embedded [picobsd] many problems in src/usr.sbin/ppp/* after c o misc/52256 embedded [picobsd] picobsd build script does not read in user/s o kern/101228 embedded [nanobsd] [patch] Two more entries for FlashDevice.sub 4 problems total. From owner-freebsd-embedded@FreeBSD.ORG Tue Aug 26 23:31:58 2008 Return-Path: Delivered-To: freebsd-embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 39637106566B for ; Tue, 26 Aug 2008 23:31:58 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from plato.miralink.com (mail.miralink.com [70.103.185.20]) by mx1.freebsd.org (Postfix) with ESMTP id DEF058FC16 for ; Tue, 26 Aug 2008 23:31:57 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from localhost (localhost.localdomain [127.0.0.1]) by plato.miralink.com (Postfix) with ESMTP id 5353F1A9173 for ; Tue, 26 Aug 2008 16:22:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at X-Spam-Flag: NO X-Spam-Score: -4.399 X-Spam-Level: X-Spam-Status: No, score=-4.399 tagged_above=-10 required=6.6 tests=[ALL_TRUSTED=-1.8, BAYES_00=-2.599] Received: from plato.miralink.com ([127.0.0.1]) by localhost (plato.miralink.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9IxChEmGY4jV for ; Tue, 26 Aug 2008 16:22:47 -0700 (PDT) Received: from [10.0.0.40] (iago.office.miralink.com [10.0.0.40]) by plato.miralink.com (Postfix) with ESMTP id C77F91A87A3 for ; Tue, 26 Aug 2008 16:22:47 -0700 (PDT) Message-ID: <48B4926D.8070208@miralink.com> Date: Tue, 26 Aug 2008 16:31:57 -0700 From: Sean Bruno User-Agent: Thunderbird 2.0.0.16 (X11/20080723) MIME-Version: 1.0 To: freebsd-embedded@freebsd.org References: <48AC7FAF.1060400@miralink.com> <48ACAD2D.9090107@miralink.com> <48ADE8D6.1090906@miralink.com> <48B1ADD2.1080507@miralink.com> In-Reply-To: <48B1ADD2.1080507@miralink.com> Content-Type: multipart/mixed; boundary="------------090608040103050203010709" Subject: Re: PAM errors with NANOBSD X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Aug 2008 23:31:58 -0000 This is a multi-part message in MIME format. --------------090608040103050203010709 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sean Bruno wrote: > Sean Bruno wrote: >> Sean Bruno wrote: >>> Sean Bruno wrote: >>>> I seem to be stumped by my latest issue with NANOBSD. >>>> I can't login to the console due to missing pam libs and such. Any >>>> and all calls to sudo seem to be blowing up as well. I can only >>>> assume that something from my build system is causing pam to be >>>> configured. Even though I have explicitly set NO_PAM=YES in my >>>> NANOConf, I seem to be jamming up on pam. If I remove the NO_PAM >>>> entry, I get the same failure. So perhaps NO_PAM doesn't mean what >>>> I think it means? >>>> >>>> Anyone have a clue what the heck is going on here? >>>> >>>> ------------------------------------------------------------------------ >>>> >>> Here's an example from my last build. The system seems to boot >>> fine, but then is completely useless at startup: >>> >>> FreeBSD/i386 (Amnesiac) (ttyd0) >>> >>> login: root >>> Aug 21 07:50:22 login: in openpam_load_module(): no pam_unix.so found >>> Aug 21 07:50:22 login: pam_start(): system error >>> >>> FreeBSD/i386 (Amnesiac) (ttyd0) >>> >>> login: >>> >>> >> adding or removing "NO_PAM=YES" from the NANOBSD configuration has no >> impact on whether or not PAM get's built. So, I'm not sure what the >> heck is going on now. >> >> I mounted the diskimage on my system and verified that >> /usr/lib/pam_unix.so exists and is properly built. Any ideas as to >> why my disk image is acting like this? >> > Ok, this is excruciating. I can only assume that I am doing something > so completely wrong that it is befuddling the build system and it's > not generating an error that would be meaningful. > > I am using a RELENG_6 build machine to build a RELENG_6 image and I > can't seem to figure out what is generating this non-sense PAM error. > I'm certain that the correct libs are in place and that everything is > being built without errors. > > Is anyone else using RELENG_6 with NanoBSD right now? This worked > pre-6.3 and I can't see anything that would be causing this type of > absolute failure. > Well, after twiddling about I began removing "NO_" argument from my configuration file. When I had removed: NO_TOOLCHAIN=YES NO_ATM=YES NO_NIS=YES NO_SHARE=YES All started working as it should, i.e. I could login to the console again and the PAM errors had vanished. I have attached my configuration in the event anyone else wants to figure out how or why this problem manifested itself. -- Sean Bruno MiraLink Corporation 6015 NE 80th Ave, Ste 100 Portland, OR 97218 Phone 503-621-5143 Fax 503-621-5199 MSN: sbruno@miralink.com Google: seanwbruno@gmail.com Yahoo: sean_bruno@yahoo.com --------------090608040103050203010709 Content-Type: text/plain; name="NANOMIRALINK" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="NANOMIRALINK" NANO_NAME=miralink NANO_SRC=${PWD}/../../../ NANO_OBJ=${PWD}/build NANO_KERNEL=GENERIC NANO_IMAGES=2 NANO_DRIVE=ad0 CONF_BUILD=' NO_NETGRAPH=YES NO_PAM=YES ' CONF_INSTALL=' NO_BLUETOOTH=YES NO_CVS=YES NO_FORTRAN=YES NO_HTML=YES NO_LPR=YES NO_MAN=YES NO_SHAREDOCS=YES NO_EXAMPLES=YES NO_CALENDAR=YES NO_MISC=YES NO_SENDMAIL=YES NO_INFO=YES ' CONF_WORLD=' NO_BIND=YES NO_KERBEROS=YES NO_GAMES=YES NO_RESCUE=YES ' # This removes the standard BSD menu from system startup. cust_nobeastie() ( touch ${NANO_WORLDDIR}/boot/loader.conf echo "beastie_disable=\"YES\"" >> ${NANO_WORLDDIR}/boot/loader.conf ) PORT_PACKAGES="sudo-1.6.8.12_1 perl-5.8.8 net-snmp-5.2.3_3 smartmontools-5.36 lsof-4.77 openssl-0.9.8d p5-Net-SSLeay-1.30_1" install_ports() ( for package in $PORT_PACKAGES; do sudo pkg_create -b $package PACKAGE_FILE="$package".tbz cp $PACKAGE_FILE ${NANO_OBJ}/_.w chroot "$NANO_WORLDDIR" sh -c "pkg_add -vF $PACKAGE_FILE; rm -f $PACKAGE_FILE" done ) FlashDevice transcend dom512m # Serial console only customize_cmd cust_comconsole # Root may ssh in customize_cmd cust_allow_ssh_root # Install Nanobsd update files in /root customize_cmd cust_install_files # Remove the BSD Daemon Menu customize_cmd cust_nobeastie # Install PORT_PACKAGES customize_cmd install_ports --------------090608040103050203010709-- From owner-freebsd-embedded@FreeBSD.ORG Wed Aug 27 00:29:16 2008 Return-Path: Delivered-To: freebsd-embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E1EE6106564A for ; Wed, 27 Aug 2008 00:29:16 +0000 (UTC) (envelope-from marauder@pi.avalonnetworks.us) Received: from pi.avalonnetworks.us (pi.avalonnetworks.us [76.164.27.10]) by mx1.freebsd.org (Postfix) with ESMTP id A6AAD8FC08 for ; Wed, 27 Aug 2008 00:29:16 +0000 (UTC) (envelope-from marauder@pi.avalonnetworks.us) Received: from Project_Infinity-MTA by pi.avalonnetworks.us with Novell_GroupWise; Tue, 26 Aug 2008 18:08:35 -0600 Message-Id: <48B4461C.5689.0089.0@pi.avalonnetworks.us> X-Mailer: Novell GroupWise Internet Agent 7.0 Date: Tue, 26 Aug 2008 18:08:09 -0600 From: "Marauder" To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: DMA to ATA drive failure X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Aug 2008 00:29:17 -0000 Hi, I have a system that needs to directly access the local storage device in = are machine (In this case it is a ATA hard disk). To do that we are use = code similar to this storageFD =3D open("/dev/ad4", O_RDWR); if (write(storageFD, configBlock, 512) =3D=3D -1) { cout << "Error" << endl; } We currently make sure we are writing to the disk in full sector sizes = (512 in this case) and im sure we have the disk open for write. But for some reason on some machines that we do this on we get the = following error displayed from the kernel. "Aligned DMA transfer attempted.= ad4: Setting up DMA failed" We have tried adding "SET hw.ata.ata_dma=3D0" = in are loader.rc file with no luck. Any help would be greatly appreciated Thanx M From owner-freebsd-embedded@FreeBSD.ORG Thu Aug 28 14:39:39 2008 Return-Path: Delivered-To: freebsd-embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 32AD61065671 for ; Thu, 28 Aug 2008 14:39:39 +0000 (UTC) (envelope-from stas@ht-systems.ru) Received: from smtp.ht-systems.ru (mr0.ht-systems.ru [78.110.50.55]) by mx1.freebsd.org (Postfix) with ESMTP id DE1718FC19 for ; Thu, 28 Aug 2008 14:39:38 +0000 (UTC) (envelope-from stas@ht-systems.ru) Received: from [78.110.49.49] (helo=quasar.ht-systems.ru) by smtp.ht-systems.ru with esmtpa (Exim 4.62) (envelope-from ) id 1KYiL9-00075r-2Y; Thu, 28 Aug 2008 18:19:11 +0400 Received: by quasar.ht-systems.ru (Postfix, from userid 1024) id E21DF73C90; Thu, 28 Aug 2008 18:19:10 +0400 (MSD) Date: Thu, 28 Aug 2008 18:19:05 +0400 From: Stanislav Sedov To: "Marauder" Message-Id: <20080828181905.51458f1b.stas@FreeBSD.org> In-Reply-To: <48B4461C.5689.0089.0@pi.avalonnetworks.us> References: <48B4461C.5689.0089.0@pi.avalonnetworks.us> Organization: The FreeBSD Project X-XMPP: ssedov@jabber.ru X-Voice: +7 916 849 20 23 X-PGP-Fingerprint: F21E D6CC 5626 9609 6CE2 A385 2BF5 5993 EB26 9581 X-Mailer: carrier-pigeon Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA1"; boundary="Signature=_Thu__28_Aug_2008_18_19_05_+0400_YRxs78LrET=H//pi" Cc: freebsd-embedded@freebsd.org Subject: Re: DMA to ATA drive failure X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Aug 2008 14:39:39 -0000 --Signature=_Thu__28_Aug_2008_18_19_05_+0400_YRxs78LrET=H//pi Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, 26 Aug 2008 18:08:09 -0600 "Marauder" mentioned: > Hi, >=20 > I have a system that needs to directly access the local storage device in= are machine (In this case it is a ATA hard disk). To do that we are use co= de similar to this >=20 > storageFD =3D open("/dev/ad4", O_RDWR); > if (write(storageFD, configBlock, 512) =3D=3D -1) { > cout << "Error" << endl; > } >=20 > We currently make sure we are writing to the disk in full sector sizes (5= 12 in this case) and im sure we have the disk open for write. >=20 > But for some reason on some machines that we do this on we get the follow= ing error displayed from the kernel. "Aligned DMA transfer attempted. ad4: = Setting up DMA failed" We have tried adding "SET hw.ata.ata_dma=3D0" in are= loader.rc file with no luck. >=20 > Any help would be greatly appreciated > Thanx What does atacontrol displays for the disk attached? And what hardware do you use? --=20 Stanislav Sedov ST4096-RIPE --Signature=_Thu__28_Aug_2008_18_19_05_+0400_YRxs78LrET=H//pi Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAki2s94ACgkQK/VZk+smlYH6sQCeIG/FAJr/MViRPwl0GmJIlVd0 hOoAn3kMRys0s1DtO/2KiSt3UsrpNqmM =qZ9f -----END PGP SIGNATURE----- --Signature=_Thu__28_Aug_2008_18_19_05_+0400_YRxs78LrET=H//pi--