From bugmaster at FreeBSD.org Mon Aug 4 11:06:53 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Aug 4 11:07:21 2008 Subject: Current problem reports assigned to freebsd-embedded@FreeBSD.org Message-ID: <200808041106.m74B6qHa082016@freefall.freebsd.org> 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 sbruno at miralink.com Wed Aug 6 04:35:47 2008 From: sbruno at miralink.com (Sean Bruno) Date: Wed Aug 6 04:35:53 2008 Subject: NANOBSD Build Failure Message-ID: <489925FC.7070404@miralink.com> I've recently started to get the following build failure from NanoBSD and I am not sure what to make of it. If I buildworld outside of nanobsd, I certainly don't see this error: ===> gnu/usr.bin/texinfo/texindex (all) cc -O2 -fno-strict-aliasing -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/var/tmp/nanobuild_1001/FreeBSD_RELENG6/gnu/usr.bin/texinfo/texindex/../../../../contrib/texinfo -I/var/tmp/nanobuild_1001/FreeBSD_RELENG6/gnu/usr.bin/texinfo/texindex/../../../../contrib/texinfo/lib -c /var/tmp/nanobuild_1001/FreeBSD_RELENG6/gnu/usr.bin/texinfo/texindex/../../../../contrib/texinfo/util/texindex.c gzip -cn /var/tmp/nanobuild_1001/FreeBSD_RELENG6/gnu/usr.bin/texinfo/texindex/../../../../contrib/texinfo/doc/texindex.1 > texindex.1.gz cc -O2 -fno-strict-aliasing -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/var/tmp/nanobuild_1001/FreeBSD_RELENG6/gnu/usr.bin/texinfo/texindex/../../../../contrib/texinfo -I/var/tmp/nanobuild_1001/FreeBSD_RELENG6/gnu/usr.bin/texinfo/texindex/../../../../contrib/texinfo/lib -o texindex texindex.o /var/tmp/nanobuild_1001/FreeBSD_RELENG6/tools/tools/nanobsd/build/var/tmp/nanobuild_1001/FreeBSD_RELENG6/gnu/usr.bin/texinfo/texindex/../libtxi/libtxi.a ===> gnu/usr.bin/texinfo/doc (all) 1 error *** Error code 2 1 error *** Error code 2 1 error Has something caused my NANO conf to become invalid recently: NANO_KERNEL=GENERIC NANO_IMAGES=2 NANO_DRIVE=ad0 CONF_BUILD=' NO_NETGRAPH=YES NO_PAM=YES ' CONF_INSTALL=' NO_BLUETOOTH=YES NO_DICT=YES NO_TOOLCHAIN=YES NO_ATM=YES NO_NIS=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_SHARE=YES ' CONF_WORLD=' NO_BIND=YES NO_KERBEROS=YES NO_GAMES=YES NO_RESCUE=YES NO_INFO=YES ' -- 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 davidn04 at gmail.com Wed Aug 6 05:18:53 2008 From: davidn04 at gmail.com (David N) Date: Wed Aug 6 05:19:00 2008 Subject: NANOBSD Build Failure In-Reply-To: <489925FC.7070404@miralink.com> References: <489925FC.7070404@miralink.com> Message-ID: <4d7dd86f0808052153uf7b9832s64793f1f643b5a48@mail.gmail.com> 2008/8/6 Sean Bruno : > I've recently started to get the following build failure from NanoBSD and I > am not sure what to make of it. If I buildworld outside of nanobsd, I > certainly don't see this error: > > ===> gnu/usr.bin/texinfo/texindex (all) > cc -O2 -fno-strict-aliasing -pipe -DHAVE_CONFIG_H > -DLOCALEDIR=\"/usr/share/locale\" > -I/var/tmp/nanobuild_1001/FreeBSD_RELENG6/gnu/usr.bin/texinfo/texindex/../../../../contrib/texinfo > -I/var/tmp/nanobuild_1001/FreeBSD_RELENG6/gnu/usr.bin/texinfo/texindex/../../../../contrib/texinfo/lib > -c > /var/tmp/nanobuild_1001/FreeBSD_RELENG6/gnu/usr.bin/texinfo/texindex/../../../../contrib/texinfo/util/texindex.c > gzip -cn > /var/tmp/nanobuild_1001/FreeBSD_RELENG6/gnu/usr.bin/texinfo/texindex/../../../../contrib/texinfo/doc/texindex.1 >> texindex.1.gz > cc -O2 -fno-strict-aliasing -pipe -DHAVE_CONFIG_H > -DLOCALEDIR=\"/usr/share/locale\" > -I/var/tmp/nanobuild_1001/FreeBSD_RELENG6/gnu/usr.bin/texinfo/texindex/../../../../contrib/texinfo > -I/var/tmp/nanobuild_1001/FreeBSD_RELENG6/gnu/usr.bin/texinfo/texindex/../../../../contrib/texinfo/lib > -o texindex texindex.o > /var/tmp/nanobuild_1001/FreeBSD_RELENG6/tools/tools/nanobsd/build/var/tmp/nanobuild_1001/FreeBSD_RELENG6/gnu/usr.bin/texinfo/texindex/../libtxi/libtxi.a > ===> gnu/usr.bin/texinfo/doc (all) > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > > > Has something caused my NANO conf to become invalid recently: > > NANO_KERNEL=GENERIC > NANO_IMAGES=2 > NANO_DRIVE=ad0 > > CONF_BUILD=' > NO_NETGRAPH=YES > NO_PAM=YES > ' > > CONF_INSTALL=' > NO_BLUETOOTH=YES > NO_DICT=YES > NO_TOOLCHAIN=YES > NO_ATM=YES > NO_NIS=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_SHARE=YES > ' > > CONF_WORLD=' > NO_BIND=YES > NO_KERBEROS=YES > NO_GAMES=YES > NO_RESCUE=YES > NO_INFO=YES > ' > > -- > 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 > > _______________________________________________ > freebsd-embedded@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-embedded > To unsubscribe, send any mail to "freebsd-embedded-unsubscribe@freebsd.org" > Hi, Take a look at this http://phk.freebsd.dk/misc/build_options/ Not sure how upto date it is. But it looks like the NO_INFO in conf_world is the problem. Regards David N From brix at FreeBSD.org Wed Aug 6 15:54:05 2008 From: brix at FreeBSD.org (Henrik Brix Andersen) Date: Wed Aug 6 15:54:12 2008 Subject: NANOBSD Build Failure In-Reply-To: <489925FC.7070404@miralink.com> References: <489925FC.7070404@miralink.com> Message-ID: <20080806153420.GB80548@tirith.brixandersen.dk> On Tue, Aug 05, 2008 at 09:18:04PM -0700, Sean Bruno wrote: > I've recently started to get the following build failure from NanoBSD > and I am not sure what to make of it. If I buildworld outside of > nanobsd, I certainly don't see this error: > > ===> gnu/usr.bin/texinfo/texindex (all) > cc -O2 -fno-strict-aliasing -pipe -DHAVE_CONFIG_H > -DLOCALEDIR=\"/usr/share/locale\" > -I/var/tmp/nanobuild_1001/FreeBSD_RELENG6/gnu/usr.bin/texinfo/texindex/../../../../contrib/texinfo > -I/var/tmp/nanobuild_1001/FreeBSD_RELENG6/gnu/usr.bin/texinfo/texindex/../../../../contrib/texinfo/lib > -c > /var/tmp/nanobuild_1001/FreeBSD_RELENG6/gnu/usr.bin/texinfo/texindex/../../../../contrib/texinfo/util/texindex.c > gzip -cn > /var/tmp/nanobuild_1001/FreeBSD_RELENG6/gnu/usr.bin/texinfo/texindex/../../../../contrib/texinfo/doc/texindex.1 > > texindex.1.gz > cc -O2 -fno-strict-aliasing -pipe -DHAVE_CONFIG_H > -DLOCALEDIR=\"/usr/share/locale\" > -I/var/tmp/nanobuild_1001/FreeBSD_RELENG6/gnu/usr.bin/texinfo/texindex/../../../../contrib/texinfo > -I/var/tmp/nanobuild_1001/FreeBSD_RELENG6/gnu/usr.bin/texinfo/texindex/../../../../contrib/texinfo/lib > -o texindex texindex.o > /var/tmp/nanobuild_1001/FreeBSD_RELENG6/tools/tools/nanobsd/build/var/tmp/nanobuild_1001/FreeBSD_RELENG6/gnu/usr.bin/texinfo/texindex/../libtxi/libtxi.a > ===> gnu/usr.bin/texinfo/doc (all) > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error Try setting NANO_PMAKE="make -j 1" - that should reveal what is failing. Brix -- Henrik Brix Andersen -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 217 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-embedded/attachments/20080806/82dc0f51/attachment.pgp From bugmaster at FreeBSD.org Mon Aug 11 11:06:55 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Aug 11 11:07:20 2008 Subject: Current problem reports assigned to freebsd-embedded@FreeBSD.org Message-ID: <200808111106.m7BB6s8a047143@freefall.freebsd.org> 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 bugmaster at FreeBSD.org Mon Aug 18 11:06:48 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Aug 18 11:07:20 2008 Subject: Current problem reports assigned to freebsd-embedded@FreeBSD.org Message-ID: <200808181106.m7IB6lIG079757@freefall.freebsd.org> 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 sbruno at miralink.com Mon Aug 18 23:23:31 2008 From: sbruno at miralink.com (Sean Bruno) Date: Mon Aug 18 23:23:38 2008 Subject: NANOBSD Build Failure In-Reply-To: <20080806153420.GB80548@tirith.brixandersen.dk> References: <489925FC.7070404@miralink.com> <20080806153420.GB80548@tirith.brixandersen.dk> Message-ID: <48AA00C7.5070500@miralink.com> Henrik Brix Andersen wrote: > On Tue, Aug 05, 2008 at 09:18:04PM -0700, Sean Bruno wrote: > >> I've recently started to get the following build failure from NanoBSD >> and I am not sure what to make of it. If I buildworld outside of >> nanobsd, I certainly don't see this error: >> >> ===> gnu/usr.bin/texinfo/texindex (all) >> cc -O2 -fno-strict-aliasing -pipe -DHAVE_CONFIG_H >> -DLOCALEDIR=\"/usr/share/locale\" >> -I/var/tmp/nanobuild_1001/FreeBSD_RELENG6/gnu/usr.bin/texinfo/texindex/../../../../contrib/texinfo >> -I/var/tmp/nanobuild_1001/FreeBSD_RELENG6/gnu/usr.bin/texinfo/texindex/../../../../contrib/texinfo/lib >> -c >> /var/tmp/nanobuild_1001/FreeBSD_RELENG6/gnu/usr.bin/texinfo/texindex/../../../../contrib/texinfo/util/texindex.c >> gzip -cn >> /var/tmp/nanobuild_1001/FreeBSD_RELENG6/gnu/usr.bin/texinfo/texindex/../../../../contrib/texinfo/doc/texindex.1 >> > texindex.1.gz >> cc -O2 -fno-strict-aliasing -pipe -DHAVE_CONFIG_H >> -DLOCALEDIR=\"/usr/share/locale\" >> -I/var/tmp/nanobuild_1001/FreeBSD_RELENG6/gnu/usr.bin/texinfo/texindex/../../../../contrib/texinfo >> -I/var/tmp/nanobuild_1001/FreeBSD_RELENG6/gnu/usr.bin/texinfo/texindex/../../../../contrib/texinfo/lib >> -o texindex texindex.o >> /var/tmp/nanobuild_1001/FreeBSD_RELENG6/tools/tools/nanobsd/build/var/tmp/nanobuild_1001/FreeBSD_RELENG6/gnu/usr.bin/texinfo/texindex/../libtxi/libtxi.a >> ===> gnu/usr.bin/texinfo/doc (all) >> 1 error >> *** Error code 2 >> 1 error >> *** Error code 2 >> 1 error >> > > Try setting NANO_PMAKE="make -j 1" - that should reveal what is > failing. > > Brix > Thanks for the help folks. My build failure was actually happening well before the reported error in some modifications to CAM that were made internally here. -- 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 From sbruno at miralink.com Wed Aug 20 20:33:53 2008 From: sbruno at miralink.com (Sean Bruno) Date: Wed Aug 20 20:34:01 2008 Subject: PAM errors with NANOBSD Message-ID: <48AC7FAF.1060400@miralink.com> 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? -- 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 -------------- next part -------------- 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_DICT=YES NO_TOOLCHAIN=YES NO_ATM=YES NO_NIS=YES NO_SHARE=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 ) # This installs sudo from ports. It is version dependant so it most likely will break. install_sudo() ( cd /usr/ports/security/sudo FORCE_PKG_REGISTER=1 make install package-recursive cp sudo-1.6.8.12_1.tbz ${NANO_OBJ}/_.w chroot "$NANO_WORLDDIR" sh -c "pkg_add -vF sudo-1.6.8.12_1.tbz" chroot "$NANO_WORLDDIR" sh -c "rm -f sudo-1.6.8.12_1.tbz" ) # This installs perl 5.8 from ports. It is version dependant so it most likely will break. install_perl() ( cd /usr/ports/lang/perl5.8 FORCE_PKG_REGISTER=1 make install package-recursive cp perl-5.8.8.tbz ${NANO_OBJ}/_.w chroot "$NANO_WORLDDIR" sh -c "pkg_add -vF perl-5.8.8.tbz" chroot "$NANO_WORLDDIR" sh -c "rm -f perl-5.8.8.tbz" ) # This installs net-snmp from ports. It is version dependant so it most likely will break. install_netsnmp() ( cd /usr/ports/net-mgmt/net-snmp FORCE_PKG_REGISTER=1 make install package-recursive cp net-snmp-5.2.3_3.tbz ${NANO_OBJ}/_.w chroot "$NANO_WORLDDIR" sh -c "pkg_add -vF net-snmp-5.2.3_3.tbz" chroot "$NANO_WORLDDIR" sh -c "rm -f net-snmp-5.2.3_3.tbz" ) # This installs smartmontools from ports. It is version dependant so it most likely will break. install_smartmontools() ( cd /usr/ports/sysutils/smartmontools FORCE_PKG_REGISTER=1 make install package-recursive cp smartmontools-5.36.tbz ${NANO_OBJ}/_.w chroot "$NANO_WORLDDIR" sh -c "pkg_add -vF smartmontools-5.36.tbz" chroot "$NANO_WORLDDIR" sh -c "rm -f smartmontools-5.36.tbz" ) # This installs lsof from ports. It is version dependant so it most likely will break. install_lsof() ( cd /usr/ports/sysutils/lsof FORCE_PKG_REGISTER=1 make install package-recursive cp lsof-4.77.tbz ${NANO_OBJ}/_.w chroot "$NANO_WORLDDIR" sh -c "pkg_add -vF lsof-4.77.tbz" chroot "$NANO_WORLDDIR" sh -c "rm -f lsof-4.77.tbz" ) install_openssl() ( cd /usr/ports/security/openssl FORCE_PKG_REGISTER=1 make install package-recursive cp openssl-0.9.8d.tbz ${NANO_OBJ}/_.w chroot "$NANO_WORLDDIR" sh -c "pkg_add -vF openssl-0.9.8d.tbz" chroot "$NANO_WORLDDIR" sh -c "rm -f openssl-0.9.8d.tbz" ) install_net_ssleay() ( cd /usr/ports/security/p5-Net-SSLeay/ FORCE_PKG_REGISTER=1 make install package-recursive cp p5-Net-SSLeay-1.30_1.tbz ${NANO_OBJ}/_.w chroot "$NANO_WORLDDIR" sh -c "pkg_add -vF p5-Net-SSLeay-1.30_1.tbz" chroot "$NANO_WORLDDIR" sh -c "rm -f p5-Net-SSLeay-1.30_1.tbz" ) 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 # customize_cmd cust_nobeastie customize_cmd install_sudo customize_cmd install_perl customize_cmd install_smartmontools customize_cmd install_lsof customize_cmd install_openssl customize_cmd install_net_ssleay customize_cmd install_netsnmp From sbruno at miralink.com Wed Aug 20 23:48:03 2008 From: sbruno at miralink.com (Sean Bruno) Date: Wed Aug 20 23:48:09 2008 Subject: PAM errors with NANOBSD In-Reply-To: <48AC7FAF.1060400@miralink.com> References: <48AC7FAF.1060400@miralink.com> Message-ID: <48ACAD2D.9090107@miralink.com> 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: -- 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 From sbruno at miralink.com Thu Aug 21 22:14:51 2008 From: sbruno at miralink.com (Sean Bruno) Date: Thu Aug 21 22:14:57 2008 Subject: PAM errors with NANOBSD In-Reply-To: <48ACAD2D.9090107@miralink.com> References: <48AC7FAF.1060400@miralink.com> <48ACAD2D.9090107@miralink.com> Message-ID: <48ADE8D6.1090906@miralink.com> 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? -- 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 From sbruno at miralink.com Sun Aug 24 18:52:06 2008 From: sbruno at miralink.com (Sean Bruno) Date: Sun Aug 24 18:52:13 2008 Subject: PAM errors with NANOBSD In-Reply-To: <48ADE8D6.1090906@miralink.com> References: <48AC7FAF.1060400@miralink.com> <48ACAD2D.9090107@miralink.com> <48ADE8D6.1090906@miralink.com> Message-ID: <48B1ADD2.1080507@miralink.com> 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 bugmaster at FreeBSD.org Mon Aug 25 11:06:48 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Aug 25 11:07:26 2008 Subject: Current problem reports assigned to freebsd-embedded@FreeBSD.org Message-ID: <200808251106.m7PB6lHo027707@freefall.freebsd.org> 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 sbruno at miralink.com Tue Aug 26 23:31:58 2008 From: sbruno at miralink.com (Sean Bruno) Date: Tue Aug 26 23:32:04 2008 Subject: PAM errors with NANOBSD In-Reply-To: <48B1ADD2.1080507@miralink.com> References: <48AC7FAF.1060400@miralink.com> <48ACAD2D.9090107@miralink.com> <48ADE8D6.1090906@miralink.com> <48B1ADD2.1080507@miralink.com> Message-ID: <48B4926D.8070208@miralink.com> 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 -------------- next part -------------- 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 From marauder at pi.avalonnetworks.us Wed Aug 27 00:29:17 2008 From: marauder at pi.avalonnetworks.us (Marauder) Date: Wed Aug 27 00:29:23 2008 Subject: DMA to ATA drive failure Message-ID: <48B4461C.5689.0089.0@pi.avalonnetworks.us> 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 = open("/dev/ad4", O_RDWR); if (write(storageFD, configBlock, 512) == -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=0" in are loader.rc file with no luck. Any help would be greatly appreciated Thanx M From stas at FreeBSD.org Thu Aug 28 14:39:39 2008 From: stas at FreeBSD.org (Stanislav Sedov) Date: Thu Aug 28 14:39:45 2008 Subject: DMA to ATA drive failure In-Reply-To: <48B4461C.5689.0089.0@pi.avalonnetworks.us> References: <48B4461C.5689.0089.0@pi.avalonnetworks.us> Message-ID: <20080828181905.51458f1b.stas@FreeBSD.org> On Tue, 26 Aug 2008 18:08:09 -0600 "Marauder" mentioned: > 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 = open("/dev/ad4", O_RDWR); > if (write(storageFD, configBlock, 512) == -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=0" in are loader.rc file with no luck. > > Any help would be greatly appreciated > Thanx What does atacontrol displays for the disk attached? And what hardware do you use? -- Stanislav Sedov ST4096-RIPE -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-embedded/attachments/20080828/41fae0e8/attachment.pgp