Re: mpt problem on a Supermicro motherboard (FreeBSD 9.2 amd64)
Victor Sudakov wrote: > > I have several Supermicro-based servers with the mpt RAID adapter: > > # mptutil show adapter > mpt0 Adapter: >Board Name: UNUSED >Board Assembly: > Chip Name: C1068E > Chip Revision: UNUSED > RAID Levels: none > # > > The problem is, I cannot configure any RAIDs (please see output > below) from FreeBSD. If I configure volumes from BIOS setup, FreeBSD > still sees them as separate physical discs. What am I doing wrong? > > I cannot use gmirror with these servers because a) if no MPT RAID is > configured in BIOS setup, it cannot boot from HDD and b) if an MPT > RAID *is* configured in BIOS setup, it occupies the last sector and > prevents GEOM from working with these drives. > > Any help please? (or redirect me to a more appropriate maillist). After many unsuccessful trials and googling, we had to reconfigure the adapter from RAID mode to IT mode. It required flashing the adapter's BIOS from a Supermicro-supplied image and changing a jumper setting on the motherboard. Now as the adapter is in IT mode, it is a plain HBA the BIOS can boot from, and I have set up a gmirror on the SAS disks. After flashing the adapter BIOS, don't forget to enter its setup (Ctrl-C) and enable hotplugging of disks (called "Removable Media Support" in the menu, off by default). People come across similar problems and solutions on other OSes, like http://ubuntuforums.org/archive/index.php/t-973912.html -- Victor Sudakov Tomsk, Russia Russian Barefoot FAQ at http://www.barefooters.ru/barefoot.txt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Where is pkg repository for 9.2-RELEASE (amd64)?
Yeah!!! 96.47.72.120 works! Thanks! > Depends. Where are your other installed packages from? I'd probably > re-install all of them from the pkg-test repository just to be safe. I installed 9.1 on new node and compiled from ports. It took a long time, which I want to avoid right now. Here is what I consider as steps for 9.2: freebsd-update upgrade -r 9.2-RELEASE freebsd-update install nextboot -k GENERIC freebsd-update install portsnap fetch portsnap extract do all pkg steps freebsd-update install kernel rebuild reboot I might be making some misunderstandings in order of this? Best regards Zoran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Where is pkg repository for 9.2-RELEASE (amd64)?
On Tue, Oct 8, 2013, at 10:58, Zoran Kolic wrote: > > Use PACKAGESITE=http://pkg-test.freebsd.org/pkg-test-${ABI}/latest > > > > That's the kit that will form the official FreeBSD package repository; > > it just lacks the crypto bits for signing the packages, which is why > > it's calling itself 'pkg-test' > > > > Oh -- there isn't an A record in the DNS for pkg-test.freebsd.org -- > > look up a SRV record for _http._tcp.pkg-test.freebsd.org instead. > > Well, I still have no idea what the address of the server is. > Could someone post it (i.e. 123.456.789.123 or alike)? # dig _http._tcp.pkg-test.freebsd.org SRV ; <<>> DiG 9.9.3-P2 <<>> _http._tcp.pkg-test.freebsd.org SRV ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8634 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 3 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4000 ;; QUESTION SECTION: ;_http._tcp.pkg-test.freebsd.org. INSRV ;; ANSWER SECTION: _http._tcp.pkg-test.freebsd.org. 120 IN SRV 10 10 80 pkg1.nyi.freebsd.org. ;; ADDITIONAL SECTION: pkg1.nyi.freebsd.org. 3600IN A 96.47.72.120 pkg1.nyi.freebsd.org. 3600IN 2610:1c1:1:6300::16:78 ;; Query time: 374 msec ;; SERVER: 192.168.93.251#53(192.168.93.251) ;; WHEN: Tue Oct 08 11:24:41 CDT 2013 ;; MSG SIZE rcvd: 144 > After having it set as PACKAGESITE, I assume running pkg, pkg2ng, > pkg update, pkg upgrade -fy enough? > Best regards all > Depends. Where are your other installed packages from? I'd probably re-install all of them from the pkg-test repository just to be safe. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Where is pkg repository for 9.2-RELEASE (amd64)?
> Use PACKAGESITE=http://pkg-test.freebsd.org/pkg-test-${ABI}/latest > > That's the kit that will form the official FreeBSD package repository; > it just lacks the crypto bits for signing the packages, which is why > it's calling itself 'pkg-test' > > Oh -- there isn't an A record in the DNS for pkg-test.freebsd.org -- > look up a SRV record for _http._tcp.pkg-test.freebsd.org instead. Well, I still have no idea what the address of the server is. Could someone post it (i.e. 123.456.789.123 or alike)? After having it set as PACKAGESITE, I assume running pkg, pkg2ng, pkg update, pkg upgrade -fy enough? Best regards all Zoran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
mpt problem on a Supermicro motherboard (FreeBSD 9.2 amd64)
Colleagues, I have several Supermicro-based servers with the mpt RAID adapter: # mptutil show adapter mpt0 Adapter: Board Name: UNUSED Board Assembly: Chip Name: C1068E Chip Revision: UNUSED RAID Levels: none # The problem is, I cannot configure any RAIDs (please see output below) from FreeBSD. If I configure volumes from BIOS setup, FreeBSD still sees them as separate physical discs. What am I doing wrong? I cannot use gmirror with these servers because a) if no MPT RAID is configured in BIOS setup, it cannot boot from HDD and b) if an MPT RAID *is* configured in BIOS setup, it occupies the last sector and prevents GEOM from working with these drives. Any help please? (or redirect me to a more appropriate maillist). # mptutil clear Are you sure you wish to clear the configuration on mpt0? [y/N] y mpt0: Configuration cleared # mptutil show volumes mpt0 Volumes: Id SizeLevel Stripe State Write-Cache Name # mptutil show drives mpt0 Physical Drives: da0 ( 558G) ONLINE SCSI-6 bus 0 id 0 da1 ( 558G) ONLINE SCSI-6 bus 0 id 1 da2 ( 558G) ONLINE SCSI-6 bus 0 id 2 da3 ( 558G) ONLINE SCSI-6 bus 0 id 3 # # mptutil create raid1 -v da2,da3 mptutil: Reading config page header failed: Invalid configuration page Added drive da2 with PhysDiskNum 0 mptutil: Reading config page header failed: Invalid configuration page # # mptutil show volumes mpt0 Volumes: Id SizeLevel Stripe State Write-Cache Name # -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Where is pkg repository for 9.2-RELEASE (amd64)?
On 02/10/2013 21:07, Winston wrote: > Summary: > > Where is the (U.S.) pkg(ng) repository for amd64 9.2-RELEASE (i.e., > what's the right URI for PACKAGESITE in pkg.conf)? > > > Things I tried that didn't work: > > * pkg_add -r pkg didn't create /usr/local/etc/pkg.conf > > * pkg.conf.sample suggests "http://pkg.freebsd.org/${ABI}/latest";, > but the host name pkg.freebsd.org does not DNS resolve for me. > > * URLs using pkgbeta.FreeBSD.org didn't work, and > http://pkgbeta.FreeBSD.org/ itself says > "Currently this site only contains pkg bootstrap files!" Yeah -- and the bootstrap pkg on pkgbeta is severely out of date and has some problems with the up to date DB schema. Use PACKAGESITE=http://pkg-test.freebsd.org/pkg-test-${ABI}/latest That's the kit that will form the official FreeBSD package repository; it just lacks the crypto bits for signing the packages, which is why it's calling itself 'pkg-test' Oh -- there isn't an A record in the DNS for pkg-test.freebsd.org -- look up a SRV record for _http._tcp.pkg-test.freebsd.org instead. (Yes, this is counter to RFC 2616. https://github.com/freebsd/pkg/issues/550 There are moves afoot to change to a new set of URL schemes: pkg+http://, pkg+https://, pkg+ssh:// etc. but these are still under development) Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Where is pkg repository for 9.2-RELEASE (amd64)?
Summary: Where is the (U.S.) pkg(ng) repository for amd64 9.2-RELEASE (i.e., what's the right URI for PACKAGESITE in pkg.conf)? Things I tried that didn't work: * pkg_add -r pkg didn't create /usr/local/etc/pkg.conf * pkg.conf.sample suggests "http://pkg.freebsd.org/${ABI}/latest";, but the host name pkg.freebsd.org does not DNS resolve for me. * URLs using pkgbeta.FreeBSD.org didn't work, and http://pkgbeta.FreeBSD.org/ itself says "Currently this site only contains pkg bootstrap files!" Thanks! -WBE ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Wildly different numbers of portsnap updates between i386 and amd64?
The update is a delta from what is already on your system. When you updated the older box, you pulled in lots of changes to get it current. The newer box needed fewer updates to get current. Or something is wrong. You can always delete the contents of /ports and the database in /var/db/portsnap. Then just portsnap fetch && portsnap extract. You will get a fresh ports tree. On Sat, Sep 21, 2013 at 2:20 PM, Christian Campbell wrote: > Hi. I run 9.1-RELEASE on two boxes: one i386 and the other amd64. I've run > the latter for a bit over a week. When I portsnap update, the 32-bit > machine typically gets several to dozens or hundreds of updates, while the > 64-bit machine typically gets none, or maybe a couple. What might be the > explanation for this behaviour? > > Thank you, > Christian > > _ > 3425 SW 2nd Ave, #239 cell (352) 514-7411 > Gainesville, FL 32607-2813 > dc...@alumni.ufl.edu<https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=dc...@alumni.ufl.edu> > > On this perfect day / Nothing's standing in my way...-Hoku > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Wildly different numbers of portsnap updates between i386 and amd64?
Hi. I run 9.1-RELEASE on two boxes: one i386 and the other amd64. I've run the latter for a bit over a week. When I portsnap update, the 32-bit machine typically gets several to dozens or hundreds of updates, while the 64-bit machine typically gets none, or maybe a couple. What might be the explanation for this behaviour? Thank you, Christian _ 3425 SW 2nd Ave, #239 cell (352) 514-7411 Gainesville, FL 32607-2813 dc...@alumni.ufl.edu<https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=dc...@alumni.ufl.edu> On this perfect day / Nothing's standing in my way...-Hoku ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Installworld on amd64 fails on libc.a on r255342
On 09/13/2013 02:46 PM, Eir Nym wrote: > I get this error for a while, and don't know what to do with. > > I build the world, then try to install it into DESTDIR. And at this point I > always get error that libc.a can't be found. > > To eliminate any mistakes in commits I've run snapshot r255342 from FTP in > VM and build sources it contains. > > my building and installing world with following commands: > > # make toolchain buildworld __MAKE_CONF=/dev/null SRCCONF=src.conf > # make hierarchy distrib-dirs distribution installworld Ensure all the variables you define on the make command line are the same for all invocations of make, unless you're absolutely certain they don't apply: make -C /usr/src __MAKE_CONF=/dev/null SRCCONF=/my/src.conf buildworld make -C /usr/src __MAKE_CONF=/dev/null SRCCONF=/my/src.conf DESTDIR=/path distrib-dirs distribution installworld Setting some knobs for buildworld but not for installworld will, at best, compile things that won't be installed; and, at worst, attempt to install things that haven't been compiled. -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net Furry Peace! - http://www.fur.com/peace/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Installworld on amd64 fails on libc.a on r255342
I get this error for a while, and don't know what to do with. I build the world, then try to install it into DESTDIR. And at this point I always get error that libc.a can't be found. To eliminate any mistakes in commits I've run snapshot r255342 from FTP in VM and build sources it contains. my building and installing world with following commands: # make toolchain buildworld __MAKE_CONF=/dev/null SRCCONF=src.conf # make hierarchy distrib-dirs distribution installworld some notes: * Targets like hierarchy, disturb-dirs and distribution are described in FreeBSD Handbook in this order * Target distribution doesn't install anything, but configuration files. SRCCONF has following contents: WITHOUT_AMD="YES" WITHOUT_ASSERT_DEBUG="YES" WITHOUT_BIND="YES" WITH_BMAKE="YES" WITH_BSD_GREP="YES" WITH_CLANG="YES" WITH_CLANG_EXTRAS="YES" WITH_CLANG_FULL="YES" WITH_CLANG_IS_CC="YES" WITH_CTF="YES" WITHOUT_CTM="YES" WITHOUT_DYNAMICROOT="YES" WITHOUT_FLOPPY="YES" WITH_ICONV="YES" WITHOUT_HTML="YES" WITHOUT_IPFILTER="YES" WITHOUT_IPFW="YES" WITHOUT_IPX="YES" WITHOUT_IPX_SUPPORT="YES" WITH_LDNS_UTILS="YES" WITH_LIBCPLUSPLUS="YES" WITH_LIBICONV_COMPAT="YES" WITHOUT_NCP="YES" WITHOUT_NIS="YES" WITHOUT_NLS="YES" WITHOUT_NLS_CATALOGS="YES" WITH_OPENSSH_NONE_CIPHER="YES" WITHOUT_PC_SYSINSTALL="YES" WITHOUT_RCMDS="YES" WITHOUT_SYSINSTALL="YES" WITHOUT_TCSH="YES" WITH_USB_GADGET_EXAMPLES="YES" -- Eir Nym ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Should I move to amd64 ?
Hi-- On May 30, 2013, at 10:19 AM, Michael Gass wrote: > I am currently using a 9.1-RELEASE with an i386 install. > The hardware is a core 2 duo with 2 GB of RAM. My video card > is an ati radeon hd 2400 xt. Things work fine. > > Would I gain anything by starting over and doing an AMD64 install > or would that be a bad idea? Would my system perform better, worse, > or the same after the change? I may eventually bring the memory up > to 4GB, but not anytime soon. For machines with less than 4GB of RAM, running 32-bit version is probably wise; 32-bit processes use memory more efficiently compared with 64-bit mode. For some math-intensive workloads like SSL/crypto, audio/video transcoding, and such, there is likely to be significant improvement in 64-bit mode compared with running in 32-bit mode. For most other workloads, you're not likely to notice a difference. > I understand some ports my not work - like WINE - but I do not use > WINE. Would there be other problems? Nope, or at least not in general; AMD64 is very stable nowadays. Regards, -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Should I move to amd64 ?
Given your description, no you should not move. On Thu, May 30, 2013 at 1:04 PM, Michael Gass wrote: > > I am currently using a 9.1-RELEASE with an i386 install. > The hardware is a core 2 duo with 2 GB of RAM. My video card > is an ati radeon hd 2400 xt. Things work fine. > > Would I gain anything by starting over and doing an AMD64 install > or would that be a bad idea? Would my system perform better, worse, > or the same after the change? I may eventually bring the memory up > to 4GB, but not anytime soon. > > I understand some ports my not work - like WINE - but I do not use > WINE. Would there be other problems? > > -- > Michael Gass > mg...@csbsju.edu > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Should I move to amd64 ?
I am currently using a 9.1-RELEASE with an i386 install. The hardware is a core 2 duo with 2 GB of RAM. My video card is an ati radeon hd 2400 xt. Things work fine. Would I gain anything by starting over and doing an AMD64 install or would that be a bad idea? Would my system perform better, worse, or the same after the change? I may eventually bring the memory up to 4GB, but not anytime soon. I understand some ports my not work - like WINE - but I do not use WINE. Would there be other problems? -- Michael Gass mg...@csbsju.edu ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Should I move to amd64 ?
I am currently using a 9.1-RELEASE with an i386 install. The hardware is a core 2 duo with 2 GB of RAM. My video card is an ati radeon hd 2400 xt. Things work fine. Would I gain anything by starting over and doing an AMD64 install or would that be a bad idea? Would my system perform better, worse, or the same after the change? I may eventually bring the memory up to 4GB, but not anytime soon. I understand some ports my not work - like WINE - but I do not use WINE. Would there be other problems? -- Michael Gass mg...@csbsju.edu ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Thunderbird 17.0.6 build failure FreeBSD 9.1-p3 amd64
Hello list, Portaudit said thunderbird had a vulnerability so I went to upgrade it with portupgrade but it coredumps and it does this a good while into the compilation process. Can anyone advise please how to overcome this? Here is my system and output: system - FreeBSD 9.1-RELEASE-p3 #0 r250634: Tue May 14 16:13:46 BST 2013 ports - r318881 # clang -v FreeBSD clang version 3.1 (branches/release_31 156863) 20120523 Target: x86_64-unknown-freebsd9.0 Thread model: posix # cat /etc/make.conf CC=clang CXX=clang++ CPP=clang-cpp DIALOG="/usr/ports/Tools/scripts/dialogwrapper.sh" # added by use.perl 2013-03-11 18:36:08 PERL_VERSION=5.14.2 # portupgrade thunderbird ---> Upgrading 'thunderbird-17.0.5' to 'thunderbird-17.0.6' (mail/thunderbird) ---> Building '/usr/ports/mail/thunderbird' ===> Cleaning for thunderbird-17.0.6 ===> Found saved configuration for thunderbird-17.0.6 ===> Fetching all distfiles required by thunderbird-17.0.6 for building ===> Extracting for thunderbird-17.0.6 => SHA256 Checksum OK for thunderbird-17.0.6esr.source.tar.bz2. => SHA256 Checksum OK for enigmail-1.5.1.tar.gz. ===> thunderbird-17.0.6 depends on file: /usr/local/bin/perl5.14.2 - found [...] nsAutoSyncManager.cpp:27:1: warning: delete called on 'nsDefaultAutoSyncMsgStrategy' that has virtual functions but non-virtual destructor [-Wdelete-non-virtual-dtor] NS_IMPL_ISUPPORTS1(nsDefaultAutoSyncMsgStrategy, nsIAutoSyncMsgStrategy) ^ ../../../mozilla/dist/include/nsISupportsImpl.h:1201:3: note: expanded from macro 'NS_IMPL_ISUPPORTS1' NS_IMPL_RELEASE(_class) \ ^ ../../../mozilla/dist/include/nsISupportsImpl.h:495:40: note: expanded from macro 'NS_IMPL_RELEASE' NS_IMPL_RELEASE_WITH_DESTROY(_class, delete (this)) ^ ../../../mozilla/dist/include/nsISupportsImpl.h:475:5: note: expanded from macro 'NS_IMPL_RELEASE_WITH_DESTROY' _destroy; \ ^ nsAutoSyncManager.cpp:114:1: warning: delete called on 'nsDefaultAutoSyncFolderStrategy' that has virtual functions but non-virtual destructor [-Wdelete-non-virtual-dtor] NS_IMPL_ISUPPORTS1(nsDefaultAutoSyncFolderStrategy, nsIAutoSyncFolderStrategy) ^ ../../../mozilla/dist/include/nsISupportsImpl.h:1201:3: note: expanded from macro 'NS_IMPL_ISUPPORTS1' NS_IMPL_RELEASE(_class) \ ^ ../../../mozilla/dist/include/nsISupportsImpl.h:495:40: note: expanded from macro 'NS_IMPL_RELEASE' NS_IMPL_RELEASE_WITH_DESTROY(_class, delete (this)) ^ ../../../mozilla/dist/include/nsISupportsImpl.h:475:5: note: expanded from macro 'NS_IMPL_RELEASE_WITH_DESTROY' _destroy; \ ^ nsSyncRunnableHelpers.cpp:12:1: warning: delete called on 'StreamListenerProxy' that has virtual functions but non-virtual destructor [-Wdelete-non-virtual-dtor] NS_IMPL_THREADSAFE_ISUPPORTS1(StreamListenerProxy, nsIStreamListener) ^ ../../../mozilla/dist/include/nsISupportsImpl.h:1386:3: note: expanded from macro 'NS_IMPL_THREADSAFE_ISUPPORTS1' NS_IMPL_THREADSAFE_RELEASE(_class) \ ^ ../../../mozilla/dist/include/nsISupportsImpl.h:1363:5: note: expanded from macro 'NS_IMPL_THREADSAFE_RELEASE' delete (this); \ ^ nsSyncRunnableHelpers.cpp:13:1: warning: delete called on 'ImapMailFolderSinkProxy' that has virtual functions but non-virtual destructor [-Wdelete-non-virtual-dtor] NS_IMPL_THREADSAFE_ISUPPORTS1(ImapMailFolderSinkProxy, nsIImapMailFolderSink) ^ ../../../mozilla/dist/include/nsISupportsImpl.h:1386:3: note: expanded from macro 'NS_IMPL_THREADSAFE_ISUPPORTS1' NS_IMPL_THREADSAFE_RELEASE(_class) \ ^ ../../../mozilla/dist/include/nsISupportsImpl.h:1363:5: note: expanded from macro 'NS_IMPL_THREADSAFE_RELEASE' delete (this); \ ^ nsSyncRunnableHelpers.cpp:14:1: warning: delete called on 'ImapServerSinkProxy' that has virtual functions but non-virtual destructor [-Wdelete-non-virtual-dtor] NS_IMPL_THREADSAFE_ISUPPORTS1(ImapServerSinkProxy, nsIImapServerSink) ^ ../../../mozilla/dist/include/nsISupportsImpl.h:1386:3: note: expanded from macro 'NS_IMPL_THREADSAFE_ISUPPORTS1' NS_IMPL_THREADSAFE_RELEASE(_class) \ ^ ../../../mozilla/dist/include/nsISupportsImpl.h:1363:5: note: expanded from macro 'NS_IMPL_THREADSAFE_RELEASE' delete (this); \ ^ nsSyncRunnableHelpers.cpp:15:1: warning: delete called on 'ImapMessageSinkProxy' that has virtual functions but non-virtual destructor [-Wdelete-non-virtual-dtor] NS_IMPL_THREADSAFE_ISUPPORTS1(ImapMessageSinkProxy, ^ ../../../mozilla/dist/include/nsISupportsImpl.h:1386:3: note: expanded from macro 'NS_IMPL_THREADSAFE_ISUPPORTS1' NS_IMPL_THREADSAFE_RELEASE(_class) \ ^ ../../../mozilla/dist/include/nsISupportsImpl.h:1363:5: note: expanded from macro 'NS_IMPL_THREADSAFE_RELEASE' delete (this); \ ^ nsSyncRunnableHelpers.cpp:17:1: warning: delete called on 'ImapProtocolSinkProxy' that has virtual functions but non-virtual destructor [-Wdelete-non-vi
FreeBSD 9.1 amd64 : hwpstate0 : set freq failed , err 6
Dears All , The following message "hwpstate0 : set freq failed , err 6" is displayed frequently on the following computer : Main board : ASUS M5A97 R2.0 Processor : AMD FX X8 8350 Graphics Card : PowerColor HD 4830 Memory : 32GB FreeBSD 9.1 amd64 2013-04-20 Snapshot What may be the reason ? How can it be corrected ? Thank you very much . Mehmet Erol Sanliturk ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
amd64 and COMPAT_AOUT
I'm migrating a lot of services to a new server running 9.1 amd64. I have a VMWare FreeBSD 3.3 server I want to decommission, which is running a client's website with a shopping cart system in an a.out binary (source code lost long ago). I have just tried to build a new kernel on the 9.1/amd64 machine with COMPAT_AOUT added to /usr/src/sys/amd64/conf/NEWKERNEL but ... root@corella:/usr/src/sys/amd64/conf # config NEWKERNEL NEWKERNEL: unknown option "COMPAT_AOUT" COMPAT_AOUT is recognised in i386/conf The funny thing is that in amd64/conf/NOTES is device gzip#Exec gzipped a.out's. REQUIRES COMPAT_AOUT! Is it possible to get 9.1/amd64 to run i386 a.out binaries? What might I be missing? Thanks, Danny ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: IPMI SOL setup on FreeBSD 9.1 amd64 supermicro X9SCM-F/X9CL-F
At 09:07 AM 1/23/2013, Anton Yuzhaninov wrote: On Mon, 21 Jan 2013 22:52:17, Derek Ragona wrote: DR> I have a couple servers that are built using the supermicro X9SCM-F/X9CL-F DR> motherboards, and I can't quite get IPMI SOL working right. DR> DR> These motherboards have 3 NIC's. One NIC is for a dedicated IPMI interface. DR> DR> I have both servers configured to use the dedicated IPMI NIC and these DR> NIC's are plugged into a separate unmanaged switch. DR> DR> Both systems boards are set to redirect com1. I changed /etc/ttys to run a DR> getty on /dev/ttyu0. I have com1 configured to 115,200 baud, 8, n, 1, no DR> flowcontrol in the BIOS. I in have /etc/ttys: DR> ttyu0 "/usr/libexec/getty std.115200" vt100 on secure /etc/ttys: ttyu1 "/usr/libexec/getty std.115200" vt100 on secure /boot/loader.conf: hint.uart.0.flags="0" hint.uart.1.flags="0x10" boot_serial="YES" boot_multicons="YES" comconsole_speed="115200" console="comconsole vidconsole" Anton, Thanks for answering. I thought: /etc/ttys: ttyu1 "/usr/libexec/getty std.115200" vt100 on secure is for com2? I also thought: hint.uart.1.flags="0x10" Is for com2? you said: hint.uart.1.flags="0x10" Is that for for a serial only console? I read in some posts, to use: hint.uart.1.flags="0x30" for both a local console with a serial console. I could not find much documentation on the uart or sio flags. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: IPMI SOL setup on FreeBSD 9.1 amd64 supermicro X9SCM-F/X9CL-F
On Mon, 21 Jan 2013 22:52:17, Derek Ragona wrote: DR> I have a couple servers that are built using the supermicro X9SCM-F/X9CL-F DR> motherboards, and I can't quite get IPMI SOL working right. DR> DR> These motherboards have 3 NIC's. One NIC is for a dedicated IPMI interface. DR> DR> I have both servers configured to use the dedicated IPMI NIC and these DR> NIC's are plugged into a separate unmanaged switch. DR> DR> Both systems boards are set to redirect com1. I changed /etc/ttys to run a DR> getty on /dev/ttyu0. I have com1 configured to 115,200 baud, 8, n, 1, no DR> flowcontrol in the BIOS. I in have /etc/ttys: DR> ttyu0 "/usr/libexec/getty std.115200" vt100 on secure /etc/ttys: ttyu1 "/usr/libexec/getty std.115200" vt100 on secure /boot/loader.conf: hint.uart.0.flags="0" hint.uart.1.flags="0x10" boot_serial="YES" boot_multicons="YES" comconsole_speed="115200" console="comconsole vidconsole" -- Anton Yuzhaninov ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
IPMI SOL setup on FreeBSD 9.1 amd64 supermicro X9SCM-F/X9CL-F
I have a couple servers that are built using the supermicro X9SCM-F/X9CL-F motherboards, and I can't quite get IPMI SOL working right. These motherboards have 3 NIC's. One NIC is for a dedicated IPMI interface. I have both servers configured to use the dedicated IPMI NIC and these NIC's are plugged into a separate unmanaged switch. Both systems boards are set to redirect com1. I changed /etc/ttys to run a getty on /dev/ttyu0. I have com1 configured to 115,200 baud, 8, n, 1, no flowcontrol in the BIOS. I in have /etc/ttys: ttyu0 "/usr/libexec/getty std.115200" vt100 on secure Using one server, I start an IPMI SOL session to the other server. But all I get is the IPMI SOL output, no login prompt. If I reboot the server I am SOL connected to, I do see the BIOS boot messages, and even the initial FreeBSD boot prompt. I can even make boot prompt changes from the SOL session. Once boot starts the SOL gets no more output. I looked at both servers and the one I am using to initiate the SOL has /dev/ipmi0 and ipmitool working fine. On the server I am trying to connect to has /dev/ipmi1 and ipmitool errors: Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory These are identical motherboards. I suspect that because the one system creates /dev/ipmi1 instead of /dev/ipmi0 may be why the SOL output stops right after the boot starts. If I do: ln -s /dev/ipmi1 /dev/ipmi0 ipmitool works fine, until the next reboot. How can I get the one system to make /dev/ipmi0 instead of /dev/ipmi1? In FreeBSD 9.1 do I use hint.uart instead of hint.sio in /boot/loader.conf? Any help would be appreciated. -Derek derek at computinginnovations.com -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 关于在Freebsd9.0-amd64安装VirtualBox虚拟机的问题
On 10-01-2013 05:56, *;sτóΡ〆~*~ξ wrote: >��请�导 > >���骤� > ># portsnap fetch update ># cd /usr/ports/emulators/virtualbox-ose ># make install clean > >�路��认���OK� >� > >pass -build programs >pass -Libraries >pass -DLLs >pass -Programs >Pass - install >kmk:*** NoRULE to make target '/usr/src/sys/kern/bus_if.m',needed by >'/usr/ports/emulators/virtualbox-ose/work/virtualbox-4.0.14_OSE/out/fre >ebsd.amd64/release/obj/freebsdgeneratedkernelheaders/bus_if.h. Stop >*** error code 2 >Stop in /usr/ports/emulators/virtualbox-ose. >*** Error code 1 >Stop in /usr/ports/emulators/virtualbox-ose. >��# > >请�� �请��谢� > >�人�对���太��谢谢� It needs the FreeBSD source code in /usr/src. signature.asc Description: OpenPGP digital signature
关于在Freebsd9.0-amd64安装VirtualBox虚拟机的问题
���请�导 ��骤�� # portsnap fetch update # cd /usr/ports/emulators/virtualbox-ose # make install clean ��路���认�OK�� ��� pass -build programs pass -Libraries pass -DLLs pass -Programs Pass - install kmk:*** NoRULE to make target '/usr/src/sys/kern/bus_if.m',needed by '/usr/ports/emulators/virtualbox-ose/work/virtualbox-4.0.14_OSE/out/fre ebsd.amd64/release/obj/freebsdgeneratedkernelheaders/bus_if.h. Stop *** error code 2 Stop in /usr/ports/emulators/virtualbox-ose. *** Error code 1 Stop in /usr/ports/emulators/virtualbox-ose. ���# 请�� ��请�谢�� ��人对�太���谢谢�� ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: powerd(8), cpufreq(4) only available on amd64/i386?
On 01/07/13 01:23, Anton Shterenlikht wrote: > I recently installed 9.1-release on a sparc64 box. > One of the options in bsdinstall was to use the > cpu power control. I chose to use it. So I've got > > # grep power /etc/rc.conf > powerd_enable="YES" > # > > which doesn't seem to work: > > root: /etc/rc: WARNING: failed to start powerd > > Is the following dmesg line relevant? > > # dmesg|grep "power management" > jbusppm0: mem > 0x4000f00-0x4000f07,0x4000f410050-0x4000f41005f on nexus0 > # > > Anyway, I wonder if powerd is only for amd64/i386 > and is not supposed to work on sparc64. > cpufreq(4) is not listed in sparc64 GENERIC kernel. > > If that's the case, then maybe it's best to > remove powerd option from bsdinstall? > It does work at least on powerpc[64], but I don't think we have any sparc systems with dynamic frequency control. It's very hard for bsdinstall to know whether it will work or not in advance, since it supports installing to disk images, but I can add a note (if supported by hardware) or something. -Nathan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
powerd(8), cpufreq(4) only available on amd64/i386?
I recently installed 9.1-release on a sparc64 box. One of the options in bsdinstall was to use the cpu power control. I chose to use it. So I've got # grep power /etc/rc.conf powerd_enable="YES" # which doesn't seem to work: root: /etc/rc: WARNING: failed to start powerd Is the following dmesg line relevant? # dmesg|grep "power management" jbusppm0: mem 0x4000f00-0x4000f07,0x4000f410050-0x4000f41005f on nexus0 # Anyway, I wonder if powerd is only for amd64/i386 and is not supposed to work on sparc64. cpufreq(4) is not listed in sparc64 GENERIC kernel. If that's the case, then maybe it's best to remove powerd option from bsdinstall? Anton ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading FreeBSD 8.3 amd64
Hi, I've done the upgrade yesterday. It was a clean 8.3 install, I only set up PPPoE and then run the following commands. # cd /usr/ports/misc/mc && make install clean # uname -r 8.3-RELEASE # freebsd-update -r 9.1-RELEASE upgrade # freebsd-update install # shutdown -r now # freebsd-update install # cd /usr/ports/ports-mgmt/portupgrade && make install clean # /usr/local/sbin/portupgrade -f ruby # rm /var/db/pkg/pkgdb.db # /usr/local/sbin/portupgrade -f ruby18-bdb # rm /var/db/pkg/pkgdb.db /usr/ports/INDEX-*.db # /usr/local/sbin/portupgrade -af # freebsd-update install # shutdown -r now # freebsd-update IDS >> outfile.ids This is the content of outfile.ids: Looking up update.FreeBSD.org mirrors... 3 mirrors found. Fetching metadata signature for 9.1-RELEASE from update5.FreeBSD.org... done. Fetching metadata index... done. Fetching 1 metadata patches. done. Applying metadata patches... done. Fetching 1 metadata files... done. Inspecting system... done. /boot/kernel/linker.hints has SHA256 hash ebf78144f48f13af88e5e3752735a709b084d7e6aaee10b05e57f2a117cbc366, but should have SHA256 hash 07b927068b34c4671a323e6a8aaa80ad22dc5fc4b3741b8a4060da1764510350. /etc/group has SHA256 hash 108de8653d4a6d451cc3f018780277d2fe2d770df7a7d984f5160dc753e06678, but should have SHA256 hash d788718c25a04a14cc1818ac2afa8b76a3fd899583691972d0d5127947e3504f. /etc/hosts has SHA256 hash 9684014402be7ecd32b9047181f595d124df6cf6a79dd323b0bd5685dccc2a81, but should have SHA256 hash f795387981b68599c3df984f2ce4ac4a32bf420d57faf1fb55f249b885414d64. /etc/master.passwd has SHA256 hash cd9046284ac3e571eb9f0273f9bfc118e7094e0b9312fd1789f6385e43a26cd3, but should have SHA256 hash 6f1da238cc0a55ed360a215039bc6cb5ce5369d20b8fbceb8a1941c5124e6a4e. /etc/motd has SHA256 hash fa311ce1a08aea0c818d57b904c979941dabb726d1fb2ddaa368102bd6f2fb95, but should have SHA256 hash 98f082efc89da5e887e72bc4dcfa3e5fc8bada9d19db4bdbba9a32692a7c82a7. /etc/passwd has SHA256 hash e4bcb10c66a0440efb58591daadaeec894e75e5392da9e00f3881822d0647a11, but should have SHA256 hash 3135de169a0ff94c0c97aeb525a07ea10e5ed81c9b825e219f7eea8deb97c444. /etc/ppp/ppp.conf has 0755 permissions, but should have 0600 permissions. /etc/ppp/ppp.conf has SHA256 hash 623683de09ab97394221c64ccdec3569aa240854d907a4811f91c9ed92253dd4, but should have SHA256 hash f3dd3d0da252bd47681a261a1f0d46a8fc6ae84ff3cbd34b81b586bc87e49655. /etc/pwd.db has SHA256 hash 62eb1eafbfa8fe718e68bf784e542d09ccdc09012ef43d254ae48e9846a1df4d, but should have SHA256 hash bf86739ee052821992412b61a6673811588c382fa63ab38cc47c1a59305376eb. /etc/shells has SHA256 hash 4c25fb7c79fe5057217a70cfa1c27f41959bb7daa703a94774ec5ac9d29a9266, but should have SHA256 hash beab7e474ee12b051b98889f368bbd490340a908f6f2287f9238e818b830a1fd. /etc/spwd.db has SHA256 hash b25126503c347feb67b76a5f27f44c318a675ddc82f4984b5ec0d2fc5a45fd30, but should have SHA256 hash 1cbfbea78d316e4e8d29f53f0770b8ff1f3a731e993c3ae717f36304715d7a5b. When I run "ppp -ddial alice" now, I get warnings "Bad label in /etc/ppp/ppp.conf (line x) - missing colon", but PPPoE still works. Why are the checksums bad? FWIW "snd_hdspe" now is available. Regards, Ralf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading FreeBSD 8.3 amd64
On Fri, 2012-12-21 at 07:35 +0100, Ralf Mardorf wrote: > On Thu, 2012-12-20 at 10:57 -0500, Paul Kraus wrote: > > On Dec 20, 2012, at 10:51 AM, Ralf Mardorf wrote: > > > > > On Thu, 2012-12-20 at 05:29 +0100, Polytropon wrote: > > >> I'd say: Use the source Luke. :-) > > > > > > :) > > > > > > Strange question: Is the FreeBSD handbook available as iBook? > > > > You can get it as a PDF at > > ftp://ftp.freebsd.org/pub/FreeBSD/doc/en_US.ISO8859-1/books/handbook/ > > and you can then view that on your iPad. Look for the Bookshelf or > > some such, I use an iPod Touch and while similar, they are not > > identical to the iPad. > > ftp://ftp.freebsd.org/pub/FreeBSD/doc/de/books/handbook/book.pdf.bz2 > ftp://ftp.freebsd.org/pub/FreeBSD/doc/en_US.ISO8859-1/books/handbook/book.pdf.bz2 > > iBookshelf Lite 2.12.4 has got a file sharing option, so I added the > above extracted archives by renamed PDFs (FreeBSD Handbook de.pdf, > FreeBSD Handbook en.pdf), but after sync they still are not available. > > I renamed the files (bsdde.pdf, bsden.pdf), added them and synced again, > but they are still not available. > > The PDFs can be opened by Linux. VBox, resp. iTunes has got access to > the files and sync between VBox and the iPad does work for other data. > > However, it's OT for this list. > > Anyway, thank you :) > Ralf PS: I installed two other gratis apps. Offline Reader ! 2.0 and PDF Reader Lite 1.2.3, the first app seems to be useless and when I downloaded it, I was asked if I'm >= 17 years old :D, but the second app does receive and display the handbooks named bsdde.pdf, bsden.pdf :) Regards, Ralf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading FreeBSD 8.3 amd64
On Thu, 2012-12-20 at 10:57 -0500, Paul Kraus wrote: > On Dec 20, 2012, at 10:51 AM, Ralf Mardorf wrote: > > > On Thu, 2012-12-20 at 05:29 +0100, Polytropon wrote: > >> I'd say: Use the source Luke. :-) > > > > :) > > > > Strange question: Is the FreeBSD handbook available as iBook? > > You can get it as a PDF at > ftp://ftp.freebsd.org/pub/FreeBSD/doc/en_US.ISO8859-1/books/handbook/ > and you can then view that on your iPad. Look for the Bookshelf or > some such, I use an iPod Touch and while similar, they are not > identical to the iPad. ftp://ftp.freebsd.org/pub/FreeBSD/doc/de/books/handbook/book.pdf.bz2 ftp://ftp.freebsd.org/pub/FreeBSD/doc/en_US.ISO8859-1/books/handbook/book.pdf.bz2 iBookshelf Lite 2.12.4 has got a file sharing option, so I added the above extracted archives by renamed PDFs (FreeBSD Handbook de.pdf, FreeBSD Handbook en.pdf), but after sync they still are not available. I renamed the files (bsdde.pdf, bsden.pdf), added them and synced again, but they are still not available. The PDFs can be opened by Linux. VBox, resp. iTunes has got access to the files and sync between VBox and the iPad does work for other data. However, it's OT for this list. Anyway, thank you :) Ralf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading FreeBSD 8.3 amd64
On Thu, 2012-12-20 at 15:52 +0700, Erich Dollansky wrote: > > The author of the snd_hdspe driver for FreeBSD seems to need testers. > > I never have heard of this driver. It's a new driver for FreeBSD for some cards of the vendor RME, AFAIK they only sell really professional audio cards, used for broadcasting and by professional audio studios. I never heard of professional audio studios using FreeBSD, so it's very likely that FreeBSD users seldom spend that much money for cards, that ship with all kinds of audio interfaces, that aren't needed for averaged audio usage. I was a professional audio and video engineer, but for my home studio I only bought a relatively cheap RME card, the HDSPe AIO. http://www.rme-audio.de/en_products_hdspe_aio.php It comes with stereo AD/DA converters only, every elCheapo on-board audio device has got more AD/DA IOs. Costs around 500,- EUR / 650,- USD. Other RME gear is much more expensive. Regards, Ralf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading FreeBSD 8.3 amd64
On Dec 20, 2012, at 10:51 AM, Ralf Mardorf wrote: > On Thu, 2012-12-20 at 05:29 +0100, Polytropon wrote: >> I'd say: Use the source Luke. :-) > > :) > > Strange question: Is the FreeBSD handbook available as iBook? You can get it as a PDF at ftp://ftp.freebsd.org/pub/FreeBSD/doc/en_US.ISO8859-1/books/handbook/ and you can then view that on your iPad. Look for the Bookshelf or some such, I use an iPod Touch and while similar, they are not identical to the iPad. -- Paul Kraus Deputy Technical Director, LoneStarCon 3 Sound Coordinator, Schenectady Light Opera Company ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading FreeBSD 8.3 amd64
On Thu, 2012-12-20 at 05:29 +0100, Polytropon wrote: > I'd say: Use the source Luke. :-) :) Strange question: Is the FreeBSD handbook available as iBook? At the moment I've got plenty of time, unfortunately not in front of my desktop computer. Some time ago I won an iPad2, it's a dust catcher, nice hardware, but odd software. I wonder if its possible to use it as a reader. The problem is, that I can't connect the iPad to the Internet and using iTunes (a disgusting application) in a virtual machine until now I'm only able to use iBooks, but I don't know how to transmit plain txt, pdf, html or what ever from the PC to the iPad. If somebody should know how I can get the FreeBSD handbook on my iPad that would be a help, so I could spend more time in reading how to handle FreeBSD. On VirtualBox (it doesn't work with wine) I run Win XP + iTunes and I connect the PC and iPad by USB. No jailbreake, but if it would help I would jailbraeke it. I tried to set up Linux to do ad-hoc by an USB WiFi stick, but it never worked. It would be nice to run Linux or FreeBSD on the iPad ;). Regards, Ralf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading FreeBSD 8.3 amd64
Hi, On Thu, 20 Dec 2012 05:13:39 +0100 Ralf Mardorf wrote: > ok, so "FreeBSD release" is the version of the kernel and not a > labelling for the collection of all the software. yes. It is even so that the ports work on all 'current' FreeBSD versions but not the packages. With other words, you will download always the same source files for 7.4, 8.3, 9.0, 9.1 and 10.0 but compile it then for your version. > > For Linux major distros there usually is a labelling for the > collection of the software, independent of the kernel version. > > On Linux I usually install binaries for the base system and desktop > environment, but for important software, in my case it's audio, > compiling from source is very important. > This does not really matter here. It is only that you might do not have the options compiled in you will need when using the binary. > The author of the snd_hdspe driver for FreeBSD seems to need testers. I never have heard of this driver. > It seems to be that nobody ever tested if ADAT is working and I'll > test it. OTOH I suspect bug fixes for the driver have to be added by > recompiling the kernel or at least the driver for the kernel, so I > still could use binaries for the applications. Using sources for the kernel is then the way to go. Binaries could work if the required options are compiled in. You can mix binaries and source within the applications. I do this all the while. I install very often the binary and compile later from sources. > > Since audio on FreeBSD seems to be a niche, I wonder if it's more > promising, to go the source or to go the binary rout. Source is the more promissing route here as niches are not supported by default. There are some rare cases in which options exclude each other. So, if you have strange hardware, source is the only route. > > I suspect if it's impossible or at least less good to mix binaries and > from source build software for FreeBSD, I should chose to build from > source. You can mix. If it works, it works. If not, it is most likely an option not compiled in you would need. Erich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading FreeBSD 8.3 amd64
On Thu, 20 Dec 2012 05:13:39 +0100, Ralf Mardorf wrote: > Thank you Erich :) > > ok, so "FreeBSD release" is the version of the kernel and not a > labelling for the collection of all the software. No. The version specification refers to the version of the kernel _and_ the operating system (which form a unit maintained by the FreeBSD team). Those typically have to be in sync. Depending on what branch you follow, this can be: a) a static release number, e. g. 8.2-RELEASE b) a release, enriched by security updates, e. g. 8.2-RELEASE-p2 c) a stable version, e. g. 8-STABLE of a specific date (this is "work in progress" that has been considered working) d) a development version, e. g. 10-CURRENT (this may or _may not_ even compile, it's experimental) Depending on what branch you follow, updating techniques may differ: freebsd-update (the binary way) can be used for a) and b); for c) and d) you update from source. > For Linux major distros there usually is a labelling for the collection > of the software, independent of the kernel version. Linux doesn't know the differentiation between "the operating system" (consisting of the OS kernel and the OS programs, the "world" in FreeBSD terminology) and "everything else" (third party contributed applications, in FreeBSD provided by the ports collection). > On Linux I usually install binaries for the base system and desktop > environment, but for important software, in my case it's audio, > compiling from source is very important. The ports collection allows both binary installation and by source. There are tools that help managing them. Note that unlike Linux, FreeBSD draws a line between "the OS" and "installed applications" - you need to install and update them separately. This is a big benefit as a failed program installation can never harm your OS. > The author of the snd_hdspe driver for FreeBSD seems to need testers. It > seems to be that nobody ever tested if ADAT is working and I'll test it. > OTOH I suspect bug fixes for the driver have to be added by recompiling > the kernel or at least the driver for the kernel, so I still could use > binaries for the applications. Of course. The separation I've mentioned explicitely allows this method to function. What you need to do is to update your sources in /usr/src and then recompile the kernel and, if required, the world, as explained in /usr/src/Makefile's comment header. > Since audio on FreeBSD seems to be a niche, I wonder if it's more > promising, to go the source or to go the binary rout. I'd say: Use the source Luke. :-) Experimental changes and "bleeding edge updates" are typically a domain of source installations. With svn you can track smallest changes very quickly, apply them to your system and have a test run. Doesn't work? Undo the change, or wait for a new version. > I suspect if it's impossible or at least less good to mix binaries and > from source build software for FreeBSD, I should chose to build from > source. Basically there is no problem. One thing you have to pay attention to is dependency versions, but that's what port management tools like portmaster can do for you. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading FreeBSD 8.3 amd64
Thank you Erich :) ok, so "FreeBSD release" is the version of the kernel and not a labelling for the collection of all the software. For Linux major distros there usually is a labelling for the collection of the software, independent of the kernel version. On Linux I usually install binaries for the base system and desktop environment, but for important software, in my case it's audio, compiling from source is very important. The author of the snd_hdspe driver for FreeBSD seems to need testers. It seems to be that nobody ever tested if ADAT is working and I'll test it. OTOH I suspect bug fixes for the driver have to be added by recompiling the kernel or at least the driver for the kernel, so I still could use binaries for the applications. Since audio on FreeBSD seems to be a niche, I wonder if it's more promising, to go the source or to go the binary rout. I suspect if it's impossible or at least less good to mix binaries and from source build software for FreeBSD, I should chose to build from source. Regards, Ralf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading FreeBSD 8.3 amd64
Hi, On Wed, 19 Dec 2012 18:09:16 +0100 Ralf Mardorf wrote: > On Wed, 2012-12-19 at 10:14 -0600, Antonio Olivares wrote: > > You may also use at your discretion the portmaster tool? It works > > very well and a nice example is given by W. Block: > > > > http://www.wonkity.com/~wblock/docs/html/portupgrade.html > > Thank you Antonio :) > > because I can't install FreeBSD by the 9.0 DVD, for what reason ever > this doesn't work, I installed it by the 8.3 DVD and will now make a > release upgrade. IIUC a release upgrade will rebuild everything, hence one way was already shown to you. The other route would lead you via the sources. I prefer the sources over the binary upgrade. If the new kernel will not boot, you can boot the old kernel which will then be under kernel.old. > there should be no dependency issues. My FreeBSD 8.3 is a fresh Dependencies come in when it comes to ports. I would like to suggest the you first make a decision whether you want the ports as binaries or via source. Both routes work. Only the sources allow you to specify options. I would also recommend to download first the sources or the binaries and start the upgrade only after all files are downloaded. As you already know, portupgrade is the tool of choice here. If you have problems with 9.1, you might consider a move to 10. I have done this too for the same reason when I got a new machine which has had problems with 9.0. 10.0 is not recommended for production. Me and many other still do this. You might will run occassionally into problems. So, think twice before doing this. > install, I only set up PPPoE, anything else is default. > IIUC I need to take care about it to keep dependencies up to date, > when I don't upgrade the complete release, but just upgrade some > software. > > So, can I upgrade from 8.3 to 9.0, without taking care about > dependencies and take care about the link, when 9.0 is installed, > instead of doing it right now? > FreeBSD and the ports have 'nothing' to do with each other. You have to upgrade FreeBSD first and then upgrade the ports. Most likely, all applications will continue to work without upgrade. If I remember right, even after an upgrade from 8.3 to 10.0 on one of my machines, all applications continued to work. I still upgraded them as fast as possible. > My apologize for the terrible English, I'm in a hurry, but wanted to > rely immediately and this makes broken English not better ;). Do not worry about this here. I think, while you have been pretty clear on the rest, the last line does not make real sense to me. Erich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading FreeBSD 8.3 amd64
Ralf, On Wed, Dec 19, 2012 at 11:09 AM, Ralf Mardorf wrote: > On Wed, 2012-12-19 at 10:14 -0600, Antonio Olivares wrote: >> You may also use at your discretion the portmaster tool? It works >> very well and a nice example is given by W. Block: >> >> http://www.wonkity.com/~wblock/docs/html/portupgrade.html > > Thank you Antonio :) > > because I can't install FreeBSD by the 9.0 DVD, for what reason ever > this doesn't work, I installed it by the 8.3 DVD and will now make a > release upgrade. IIUC a release upgrade will rebuild everything, hence > there should be no dependency issues. My FreeBSD 8.3 is a fresh install, > I only set up PPPoE, anything else is default. > IIUC I need to take care about it to keep dependencies up to date, when > I don't upgrade the complete release, but just upgrade some software. > > So, can I upgrade from 8.3 to 9.0, without taking care about > dependencies and take care about the link, when 9.0 is installed, > instead of doing it right now? Yes, you can do it. You can update to 9.0 with freebsd-update tool and then install/reinstall the ports. # freebsd-update -r 9.1-RELEASE or # freebsd-update -r 9.0-RELEASE in case that 9.1 is not there yet*? then run # freebsd-update fetch # freebsd-update install to get security updates as is documented : http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html This should work well to get newer RELEASE, but some ports may be needed to be rebuilt/reinstalled. Hope this helps, Antonio > > My apologize for the terrible English, I'm in a hurry, but wanted to > rely immediately and this makes broken English not better ;). > > Regards, > Ralf > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading FreeBSD 8.3 amd64
On Wed, 2012-12-19 at 10:14 -0600, Antonio Olivares wrote: > You may also use at your discretion the portmaster tool? It works > very well and a nice example is given by W. Block: > > http://www.wonkity.com/~wblock/docs/html/portupgrade.html Thank you Antonio :) because I can't install FreeBSD by the 9.0 DVD, for what reason ever this doesn't work, I installed it by the 8.3 DVD and will now make a release upgrade. IIUC a release upgrade will rebuild everything, hence there should be no dependency issues. My FreeBSD 8.3 is a fresh install, I only set up PPPoE, anything else is default. IIUC I need to take care about it to keep dependencies up to date, when I don't upgrade the complete release, but just upgrade some software. So, can I upgrade from 8.3 to 9.0, without taking care about dependencies and take care about the link, when 9.0 is installed, instead of doing it right now? My apologize for the terrible English, I'm in a hurry, but wanted to rely immediately and this makes broken English not better ;). Regards, Ralf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading FreeBSD 8.3 amd64
Ralf, On Wed, Dec 19, 2012 at 10:04 AM, Ralf Mardorf wrote: > Hi :) > > this isn't a request, just a note about the handbook, from the point of > view a newbie has got. > >> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html > > "We also assume that you have already obtained the sources to a newer > system. If the sources available on the particular system are old too, > see Section 25.6 for detailed help about synchronizing them to a newer > version." > > I know svn from Linux, but I don't know what I should update using > svn ;). Yes, the ports, but to get knowledge were the ports are, I have > to google ;). This howto is more confusing for a newbie and seems to > need more reboots, so I started with > >> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html > > but it's not described how to do the following: > "Note that setting the BATCH environment variable to yes will answer yes > to any prompts during this process, removing the need for manual > intervention during the build process." > > regarding to google it's "env BATCH=yes", I'll test it next time I'll > reboot into FreeBSD. > > Another issue is, that the portupgrade command isn't found. Check in /usr/ports/ports-mgmt/ directory: Become super user, $ su - passwd: then as super user: # cd /usr/ports/ports-mgmt/portupgrade then from that directory # make install clean and you should have the portugrade command :) You may also use at your discretion the portmaster tool? It works very well and a nice example is given by W. Block: http://www.wonkity.com/~wblock/docs/html/portupgrade.html Best Regards, Antonio > > However, pppoe does work, but using vi never is fun for me :). > > I guess I'll read how to install software, IOW how to install > portupgrade and continue with the portupgrade method ASAP, later today, > or tomorrow. > > Regards, > Ralf > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading FreeBSD 8.3 amd64
Hi :) this isn't a request, just a note about the handbook, from the point of view a newbie has got. > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html "We also assume that you have already obtained the sources to a newer system. If the sources available on the particular system are old too, see Section 25.6 for detailed help about synchronizing them to a newer version." I know svn from Linux, but I don't know what I should update using svn ;). Yes, the ports, but to get knowledge were the ports are, I have to google ;). This howto is more confusing for a newbie and seems to need more reboots, so I started with > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html but it's not described how to do the following: "Note that setting the BATCH environment variable to yes will answer yes to any prompts during this process, removing the need for manual intervention during the build process." regarding to google it's "env BATCH=yes", I'll test it next time I'll reboot into FreeBSD. Another issue is, that the portupgrade command isn't found. However, pppoe does work, but using vi never is fun for me :). I guess I'll read how to install software, IOW how to install portupgrade and continue with the portupgrade method ASAP, later today, or tomorrow. Regards, Ralf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading FreeBSD 8.3 amd64
On Tue, 18 Dec 2012 18:54:29 +0100, Ralf Mardorf wrote: > On Tue, 2012-12-18 at 18:42 +0100, Ralf Mardorf wrote: > > I want to test snd_hdspe. How can I upgrade from 8.2 to a version > ^^^8.3 > > including the driver or something similar to get the driver? > > Btw. I didn't test, if the driver is part of 8.3 until now :D, but if > > IIUC I need >= 9.0. > > I'll read > http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html > can I assume that because I didn't install or updated and configured > anything until now, there won't be issues for a version upgrade, if I > only configure PPPoE, followed by a release upgrade and after that I'll > install software and set up FreeBSD completely? Sounds like a valid approach. I've been doing this many times, i. e. first install base system from installation media without additional packages, setup networking (PPPoE in former times, DHCP today), then update the system to the desired version or branch (e. g. -STABLE via source), and then start installing the applications from ports (also updated). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading FreeBSD 8.3 amd64
On Tue, 2012-12-18 at 18:57 +0100, Polytropon wrote: > On Tue, 18 Dec 2012 18:42:41 +0100, Ralf Mardorf wrote: > > I want to test snd_hdspe. How can I upgrade from 8.2 to a version > > including the driver or something similar to get the driver? > > Btw. I didn't test, if the driver is part of 8.3 until now :D, but if > > IIUC I need >= 9.0. > > It would probably be the easiest way to update your source tree > (using svn as this is the default method today) and re-install > from that. I'm not sure freebsd-update can cross the "major > version border" without trouble (never tried). > > See 25.7 for details: > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html > > But also note that freebsd-update supports a -r option > as explained in 25.2.3: > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html > > But as I said, I've never personally tried that. > > This approach keeps all your partition settings and doesn't require > any other work to be done on that level. Thank you :) I'll read and test it later. Regards, Ralf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading FreeBSD 8.3 amd64
On Tue, 18 Dec 2012 18:42:41 +0100, Ralf Mardorf wrote: > I want to test snd_hdspe. How can I upgrade from 8.2 to a version > including the driver or something similar to get the driver? > Btw. I didn't test, if the driver is part of 8.3 until now :D, but if > IIUC I need >= 9.0. It would probably be the easiest way to update your source tree (using svn as this is the default method today) and re-install from that. I'm not sure freebsd-update can cross the "major version border" without trouble (never tried). See 25.7 for details: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html But also note that freebsd-update supports a -r option as explained in 25.2.3: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html But as I said, I've never personally tried that. This approach keeps all your partition settings and doesn't require any other work to be done on that level. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Upgrading FreeBSD 8.3 amd64
On Tue, 2012-12-18 at 18:42 +0100, Ralf Mardorf wrote: > I want to test snd_hdspe. How can I upgrade from 8.2 to a version ^^^8.3 > including the driver or something similar to get the driver? > Btw. I didn't test, if the driver is part of 8.3 until now :D, but if > IIUC I need >= 9.0. I'll read http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html can I assume that because I didn't install or updated and configured anything until now, there won't be issues for a version upgrade, if I only configure PPPoE, followed by a release upgrade and after that I'll install software and set up FreeBSD completely? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Upgrading FreeBSD 8.3 amd64
Hi :) first I tried to install FreeBSD 9.0 64bit by the default installer, but it didn't work, then I installed PC-BSD 8.2 and it worked, after that I tried 9.0 again, but I choose sysinstall, it also failed. Now I've got FreeBSD 8.3 64bit installed, installing it worked without issues. I later today need to set up FreeBSD. The self-doubts that I'm an idiot are gone ;), I did the same as I tried to do for 9.0. The 9.0 media's checksum and the burners verifying after burning were ok. I want to test snd_hdspe. How can I upgrade from 8.2 to a version including the driver or something similar to get the driver? Btw. I didn't test, if the driver is part of 8.3 until now :D, but if IIUC I need >= 9.0. Regards, Ralf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: i386 vs. amd64
On 12/18/12 00:13, Erich Dollansky wrote: Hi, wasn't the same question here a few days ago? On Tue, 18 Dec 2012 00:16:36 -0500 Aryeh Friedman wrote: Ever since 8.X (my system is now 9.1-RC3 [done via csup]) been using i386 with the following main ports: Let me chime in where Erich couldn't answer as I recently made the switch to amd64 myself. x11-wm/xfce4 yes. www/firefox Yes. www/linux-f10-flashplugin11 Yes editors/libreoffice Yes. www/tomcat-7 www/apace22 Typo? Apache 2.2 runs. devel/aegis (I am the maintainer) devel/fhist devel/cook java/openjdk6 Yes So I have the following questions: 1. Will all the above ports (and their dependencies) work on amd64? I gave you the answer if I knew one. I general, I do not have problems which are linked to 32 or 64 bits. I've had no problems either, and I am in the middle of a devel/pcre rebuilding (over 200 ports). 2. Is there any way to do a in place switch to amd64 or do I need to rebuild the system from the ground up? To my knowledge, it is still a fresh installation. Just download an image and start from there. I think the handbook gives directions for an in-place switch, but it (and many, many others) suggest a fresh install, which is what I went with (I had other reasons as well). 3. In general is amd64 now as capable of handling ports and such as well as i386 does? I saw that some ports I used to use on i386 went 100% smooth on amd64. I believe that this has improved even further. Just make the jump. I agree, I've had no problems related to the arch since I switched and would 100% recommend it for anyone considering it. -- Yours in Christ, Joseph A Nagy Jr "Whoever loves instruction loves knowledge, But he who hates correction is stupid." -- Proverbs 12:1 Emails are not formal business letters, whatever businesses may want. Original content CopyFree (F) under the OWL http://owl.apotheon.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: i386 vs. amd64
Hi, wasn't the same question here a few days ago? On Tue, 18 Dec 2012 00:16:36 -0500 Aryeh Friedman wrote: > Ever since 8.X (my system is now 9.1-RC3 [done via csup]) been using > i386 with the following main ports: > > x11-wm/xfce4 yes. > www/firefox Yes. > www/linux-f10-flashplugin11 > editors/libreoffice Yes. > www/tomcat-7 > www/apace22 Typo? Apache 2.2 runs. > devel/aegis (I am the maintainer) > devel/fhist > devel/cook > java/openjdk6 > emulation/virtualbox-ose (and additions) > print/cups Yes. The ones I did not answer, I do not have installed. > > I have avoided amd64 in the past due to some or not all them working, > but want to switch if possible because PAE seems to be broken now on > i386. It was a big jump forward when I switched during 8.0 or 8.1. > > So I have the following questions: > > 1. Will all the above ports (and their dependencies) work on amd64? I gave you the answer if I knew one. I general, I do not have problems which are linked to 32 or 64 bits. > 2. Is there any way to do a in place switch to amd64 or do I need to > rebuild the system from the ground up? To my knowledge, it is still a fresh installation. Just download an image and start from there. > 3. In general is amd64 now as capable of handling ports and such as > well as i386 does? I saw that some ports I used to use on i386 went 100% smooth on amd64. I believe that this has improved even further. Just make the jump. Erich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
i386 vs. amd64
Ever since 8.X (my system is now 9.1-RC3 [done via csup]) been using i386 with the following main ports: x11-wm/xfce4 www/firefox www/linux-f10-flashplugin11 editors/libreoffice www/tomcat-7 www/apace22 devel/aegis (I am the maintainer) devel/fhist devel/cook java/openjdk6 emulation/virtualbox-ose (and additions) print/cups I have avoided amd64 in the past due to some or not all them working, but want to switch if possible because PAE seems to be broken now on i386. So I have the following questions: 1. Will all the above ports (and their dependencies) work on amd64? 2. Is there any way to do a in place switch to amd64 or do I need to rebuild the system from the ground up? 3. In general is amd64 now as capable of handling ports and such as well as i386 does? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: switching from i386 to amd64
On Sun, 16 Dec 2012 06:00:51 -0500 Aryeh Friedman wrote: > I have been using i386 (-STABLE) for years now and was wondering if > switching to amd64 ... nvidia-kmod are the minimal ones I need]) the > main reason for asking is PAE seems to be broken now The last I heard the nvidia driver wasn't compatible with PAE ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: switching from i386 to amd64
On Sun, 16 Dec 2012 12:13:36 -0700, Gary Aitken wrote: > On 12/16/12 07:08, Polytropon wrote: > > > And if you're using Firefox, there are plugins available that > > allow you to download video content instead of dealing with the > > "Flash" player the site wants you to use. > > and the recommended one is? No idea, I can't use Firefox as it freezes my computer (due to a faulty GPU). I prefer using youtube-dl and get-flash-video scripts which do not rely on a browser, but work for 99% of the cases I've tried them. But as suggested, there are Firefox extensions that allow a similar functionality, but integrated with the web browser. Until later, I'm using Opera, it doesn't freeze my computer. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: switching from i386 to amd64
On 12/16/12 04:00, Aryeh Friedman wrote: > I have been using i386 (-STABLE) for years now and was wondering if > switching to amd64 finally makes sense (i.e. are enough ports working > on it now [xfrce4, firefox, libreoffice, openjdk-6, tomcat, mysql, > apache22, flash, cups, devel/aegis, devel/cook, devel/fhist, > virtualbox-ose, nvidia-kmod are the minimal ones I need]) the main > reason for asking is PAE seems to be broken now and virtualbox-ose > refuses to let me install 64 bit OS's like Win 8. I've been using 9.0 release for about six months. xfce, firefox, thunderbird, openoffice 3.4.1, jdk (most was done prior to moving to fbsd 9.0, will be doing more) mysql, nvidia driver. had trouble using html5 from youtube -- caused weird transparent rendering issues, had to disable it. minor problems with oo which are probably generic. (Infinite loop when page had 20-40 images to run text around; not repeatable, but happens fairly frequently; scrolling causes refresh which temporarily fixes the problem). On 12/16/12 07:08, Polytropon wrote: > And if you're using Firefox, there are plugins available that > allow you to download video content instead of dealing with the > "Flash" player the site wants you to use. and the recommended one is? > Sometimes I wish it wouldn't work anymore. > It makes the web much more readable. :-) amen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: switching from i386 to amd64
On 12/16/12 11:00, Aryeh Friedman wrote: I have been using i386 (-STABLE) for years now and was wondering if switching to amd64 finally makes sense (i.e. are enough ports working on it now [xfrce4, firefox, libreoffice, openjdk-6, tomcat, mysql, apache22, flash, cups, devel/aegis, devel/cook, devel/fhist, virtualbox-ose, nvidia-kmod are the minimal ones I need]) the main reason for asking is PAE seems to be broken now and virtualbox-ose refuses to let me install 64 bit OS's like Win 8. I've been using amd64 since I built my current box in April 2008 (starting with 7.0-RELEASE) and have never had a problem. However, I avoid Flash like the plague it is. I recently installed an nVidia card and have no problems with the driver - the latest release dealt with the screen flash problem I had been having. As far as I understand, PAE usage has always had the caveat that certain device drivers may not work with it, and I suspect PAE support is suffering bit rot. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: switching from i386 to amd64
On Sun, 16 Dec 2012 12:48:40 +0100 Ralf Mardorf wrote: > Specific requirements _could_ be wine and nVidia's proprietary GPU > driver, as far as I know." - Polytropon (Btw. thank you Polytropon :) I'm using amd64 on an Atom/ION box here, the Nvidia binary drivers work fine for both openGL and the vdpau stuff. Virtualbox worked fine too, but this Atom doesn't have hardware virtualisation support so it's a bit sluggish. I've not tried (or wanted) Wine in years. -- Steve O'Hara-Smith ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: switching from i386 to amd64
On Sun, 16 Dec 2012, Ralf Mardorf wrote: On Sun, 2012-12-16 at 05:35 -0600, Joseph A. Nagy, Jr wrote: I'm running amd64 and it seems rock-solid and well supported. I had a similar question. I wanted to know if there are issues for audio, when using 64 bit and got this reply: "If you do not have a _specific_ requirement for 32 bit, use 64 bit, of course if you have a 64 bit CPU. :-) Specific requirements _could_ be wine and nVidia's proprietary GPU driver, as far as I know." - Polytropon (Btw. thank you Polytropon :) I guess in the web I read something about issues with VBox, but perhaps I'm confusing VBox with wine. I chose 64 bit and will stay with it, even if I should install another version of FreeBSD today. VirtualBox works well with both i386 and amd64 hosts and guests. Of course, with an amd64 host there can be more RAM to share between host and VMs. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: switching from i386 to amd64
On Sun, 16 Dec 2012 13:05:47 +0100, Ralf Mardorf wrote: > On Sun, 2012-12-16 at 18:45 +0700, Erich Dollansky wrote: > > flash > > For Linux there are no issues with the proprietary 64 bit flash, but > there will be no new versions of Flash any more for Linux. If FreeBSD > should use the Linux version, than Flash in the near future either way > won't work any more. That shouldn't be _that_ complicated, as "Flash" is going to be extinct soon (primarily to the lack of it on mobile devices with their growing "market share"). HTML5 will take over the world instead. :-) > IIRC Flash only is needed by some browsers and only > for videos that e.g. start with an advertising and special tasks like > that. Oh, if it would be that simple... :-( Sadly, for some developers, "Flash" has gotten a replacement for HTML. They design their whole pages _inside_ "Flash", so if you don't have it installed, you get an empty page. Their excuse is "interactivity". Still more and more online games (those you can play in the web browser) migrate to HTML 5 technology which offers good support on many platforms (and not only on the latest "Windows"). And if you're using Firefox, there are plugins available that allow you to download video content instead of dealing with the "Flash" player the site wants you to use. This also encourages the idea of wathcing such content offline with your favourite player, which is mplayer. :-) > I'm not sure, but AFAIR HTML 5 can replace Flash, assumed a video > doesn't start with an advertising and things like that. It already does this in more and more locations. Regarding video, there's still the problem created by patent lawyers and other strange guys: the coded. HTML 5 can support many formats for video content, even free formats (that do not require anyone to pay royalties in order to use it), but in how far those are already distributed among browsers and systems, that's a totally different question. However, the "out of the box experience" gets better. Soon the functionality of "Flash" will be integrated per default in modern web browsers. Just imagine how stupid it would be if I created a web page that requires you to download a proprietary plugin (with lots of security holes!) in order to see a PNG image, to see text in green color, or to render text centered. Sounds idiotic? It is! And it's mostly what applies to "Flash". :-) > For Linux Adobe will continue providing security upgrades for 11.2 in > the future, but that won't help, when websites expect newer versions. Correct, so this is another good reason for finally dropping "Flash" and move on to better alternatives. Side note: I've been experiencing working "Flash" for many years now without any trouble on FreeBSD. Sometimes I wish it wouldn't work anymore. It makes the web much more readable. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: switching from i386 to amd64
On Sun, 2012-12-16 at 18:45 +0700, Erich Dollansky wrote: > flash For Linux there are no issues with the proprietary 64 bit flash, but there will be no new versions of Flash any more for Linux. If FreeBSD should use the Linux version, than Flash in the near future either way won't work any more. IIRC Flash only is needed by some browsers and only for videos that e.g. start with an advertising and special tasks like that. I'm not sure, but AFAIR HTML 5 can replace Flash, assumed a video doesn't start with an advertising and things like that. For Linux Adobe will continue providing security upgrades for 11.2 in the future, but that won't help, when websites expect newer versions. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: switching from i386 to amd64
On Sun, 2012-12-16 at 05:35 -0600, Joseph A. Nagy, Jr wrote: > I'm running amd64 and it seems rock-solid and well supported. I had a similar question. I wanted to know if there are issues for audio, when using 64 bit and got this reply: "If you do not have a _specific_ requirement for 32 bit, use 64 bit, of course if you have a 64 bit CPU. :-) Specific requirements _could_ be wine and nVidia's proprietary GPU driver, as far as I know." - Polytropon (Btw. thank you Polytropon :) I guess in the web I read something about issues with VBox, but perhaps I'm confusing VBox with wine. I chose 64 bit and will stay with it, even if I should install another version of FreeBSD today. Regards, Ralf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: switching from i386 to amd64
Hi, On Sun, 16 Dec 2012 06:00:51 -0500 Aryeh Friedman wrote: > I have been using i386 (-STABLE) for years now and was wondering if > switching to amd64 finally makes sense (i.e. are enough ports working > on it now [xfrce4, firefox, libreoffice, openjdk-6, tomcat, mysql, > apache22, flash, cups, devel/aegis, devel/cook, devel/fhist, > virtualbox-ose, nvidia-kmod are the minimal ones I need]) the main > reason for asking is PAE seems to be broken now and virtualbox-ose > refuses to let me install 64 bit OS's like Win 8. I did the switch 2010 and missed nothing but wine. Ok, flash is not realy working for me but I also do not miss it. Erich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: switching from i386 to amd64
On 12/16/12 05:00, Aryeh Friedman wrote: I have been using i386 (-STABLE) for years now and was wondering if switching to amd64 finally makes sense (i.e. are enough ports working on it now [xfrce4, firefox, libreoffice, openjdk-6, tomcat, mysql, apache22, flash, cups, devel/aegis, devel/cook, devel/fhist, virtualbox-ose, nvidia-kmod are the minimal ones I need]) the main reason for asking is PAE seems to be broken now and virtualbox-ose refuses to let me install 64 bit OS's like Win 8. I'm running amd64 and it seems rock-solid and well supported. -- Yours in Christ, Joseph A Nagy Jr "Whoever loves instruction loves knowledge, But he who hates correction is stupid." -- Proverbs 12:1 Emails are not formal business letters, whatever businesses may want. Original content CopyFree (F) under the OWL http://owl.apotheon.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
switching from i386 to amd64
I have been using i386 (-STABLE) for years now and was wondering if switching to amd64 finally makes sense (i.e. are enough ports working on it now [xfrce4, firefox, libreoffice, openjdk-6, tomcat, mysql, apache22, flash, cups, devel/aegis, devel/cook, devel/fhist, virtualbox-ose, nvidia-kmod are the minimal ones I need]) the main reason for asking is PAE seems to be broken now and virtualbox-ose refuses to let me install 64 bit OS's like Win 8. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: i386 vs amd64
On 11/30/12 15:40, Thomas Mueller wrote: On Thu, Nov 29, 2012 at 2:57 PM, Bill Tillman wrote: i386 will not see anything above 4 GB Actually you *can* give access to >4Gb RAM for your system: PAE allows you to use 36 bits instead of 32 to address your memory (and supported till Pentium Pro) but that is only for OS (32bit apps would see 4Gb only). Anyway, I have not seen any troubles with 64bit installations. Ilya. How does the system know what is OS and what is 32-bit apps? I think this question is badly written. A kernel supporting PAE can see and use more than 4GB. However, since apps runs unmodified, a single process cannot break that barrier. So, if you are running a single program that requires that lot of memory, PAE is not an option and you will need amd64. OTOH, if you run several programs which don't singularly require more than 3GB of RAM, PAE might be a viable alternative to reinstalling. Where would GCC fit in this regard, or Clang for that matter? I don't really know, but I don't think it could make any difference. bye av. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: i386 vs amd64
> How does the system know what is OS and what is 32-bit apps? > "OS" works in kernel space while application is not. PAE affects paging system allowing software to address 2^36 bytes of memory. You can access it in kernel space, but user space applications are limited to 2^32 bytes of virtual memory (even less than 2^32 because of mappings). http://en.wikipedia.org/wiki/Physical_Address_Extension If you are interested in memory management in IA-32 (and IA-32e) here are good links: 1) official guide: http://www.intel.com/content/www/us/en/processors/architectures-software-developer-manuals.html 2) nice (human-readable) book: http://mindshare.com/shop/?c=b§ion=0A6B17101710 > Where would GCC fit in this regard, or Clang for that matter? > If you write app for user-space (not kernel module) you should not care about PAE. You simply compile it as you would do it for system with out of PAE. Ilya. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: i386 vs amd64
> On Thu, Nov 29, 2012 at 2:57 PM, Bill Tillman wrote: > > i386 will not see anything above 4 GB > Actually you *can* give access to >4Gb RAM for your system: PAE allows you > to use 36 bits instead of 32 to address your memory (and supported till > Pentium Pro) but that is only for OS (32bit apps would see 4Gb only). > Anyway, I have not seen any troubles with 64bit installations. > Ilya. How does the system know what is OS and what is 32-bit apps? Where would GCC fit in this regard, or Clang for that matter? Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: i386 vs amd64
Even that I was aware of that, I've just lost track of it. Thanks for simple solution. -- View this message in context: http://freebsd.1045724.n5.nabble.com/i386-vs-amd64-tp5765012p5765489.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: i386 vs amd64
The problem is, it gets recreated upon updating from source. -- View this message in context: http://freebsd.1045724.n5.nabble.com/i386-vs-amd64-tp5765012p5765488.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: i386 vs amd64
On 29/11/2012 22:00, Jakub Lach wrote: If it was from me, my system is without 32bit compat whatsoever, and this is not default setting on amd64. Maybe on def. amd64 there are no problems, I don't know, nobody replied to my thread. I have been running 9.0 amd64 for nearly 12 months, I think it was about february that I compiled my system with clang and no 32 bit libs. With the default install there is a small catch that the lib32 folder still gets created even though it is empty. Ports only check the existence of the folder to try to build 32 bit libs and therefore fail. valgrind is an example of that. Simply deleting the lib32 folder solves that. (pr/165175) I vaguely recall being surprised that one of the emulators was only 32bit (may be fixed by now) I haven't had any other issues since deleting the lib32 folder. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: i386 vs amd64
Hello, On Thu, Nov 29, 2012 at 2:57 PM, Bill Tillman wrote: > i386 will not see anything above 4 GB Actually you *can* give access to >4Gb RAM for your system: PAE allows you to use 36 bits instead of 32 to address your memory (and supported till Pentium Pro) but that is only for OS (32bit apps would see 4Gb only). Anyway, I have not seen any troubles with 64bit installations. Ilya. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: i386 vs amd64
If it was from me, my system is without 32bit compat whatsoever, and this is not default setting on amd64. Maybe on def. amd64 there are no problems, I don't know, nobody replied to my thread. -- View this message in context: http://freebsd.1045724.n5.nabble.com/i386-vs-amd64-tp5765012p5765188.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: i386 vs amd64
From: Fleuriot Damien To: birdf...@yahoo.com Cc: freebsd-questions@freebsd.org Sent: Wednesday, November 28, 2012 12:40 PM Subject: Re: i386 vs amd64 On Nov 28, 2012, at 6:36 PM, mike miskulin wrote: > About to build a replacement system for an older i386 setup. A few > years ago I had tried the amd64 port on it and found it was frustrating > as things that just worked on i386 did not on amd64. IIRC ports were > large annoyance too. > > Now I have a new system with 8GB, etc,etc and wonder if I am best off to > stick with i386 and PAE or is the amd64 version finally on a par or > close enough that I would not likely have many issues like in the past? > > Thanks for your thoughts/(recent) experiences. What port was that ? I've never had a *single* problem due to using amd64 over i386. >From a professional point of view, we're using over 60 amd64 fbsd 8.0 8.1 8.2 >and 8.3 boxes at work and they work just fine. I for one can recommend the 64 bits version. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" I have been using amd64 for at least 5 years now on mulitple systems and I don't know of any troubles like you're defining. And if you're using 8 GB of RAM then why waste 4 GB. i386 will not see anything above 4 GB. I'd say at least give it a try before you relent. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: i386 vs amd64
On Wed, 28 Nov 2012 19:25:59 +0100 Polytropon wrote: > On Wed, 28 Nov 2012 12:53:26 -0500, mike miskulin wrote: > > But I guess the basic question remains - are there any > > considerations in regards ports, linux emulation, etc that would > > sway me to remain i386? > > The only problem might be if you want to use wine. As it has > been said, there are binary packages (wine_amd64, if I remember > correctly), but the rest of the system should run good on > amd64 as it did on i386. > > Sidenote: I switched back from 8.2/amd64 to 8.2/i386 because > of three reasons (in fact, two reasons and one justification): > I had problems with wine, problems with nVidia's driver (plus > a faulty GPU), and I only have 2 GB RAM. Anywhere else, I have > not experienced problems with amd64. > > The nvidia driver works fine now. Linux emulation is only 32 bit though. -- Just because it can been done, does not mean it should be done. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: i386 vs amd64
On 11/28/12 18:49, Warren Block wrote: On Wed, 28 Nov 2012, mike miskulin wrote: About to build a replacement system for an older i386 setup. A few years ago I had tried the amd64 port on it and found it was frustrating as things that just worked on i386 did not on amd64. IIRC ports were large annoyance too. Now I have a new system with 8GB, etc,etc and wonder if I am best off to stick with i386 and PAE or is the amd64 version finally on a par or close enough that I would not likely have many issues like in the past? Thanks for your thoughts/(recent) experiences. Do you use emulators/wine? If not, switch to amd64. In fact, even if you do, switch to amd64 to use that 8G of memory. Building 32-bit Wine on amd64 is a hassle, but packages are available and I think there is a 64-bit port on the way. I heard valgrind is another... in case you are a developer. bye av. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: i386 vs amd64
On Wed, 28 Nov 2012 12:53:26 -0500, mike miskulin wrote: > But I guess the basic question remains - are there any considerations in > regards ports, linux emulation, etc that would sway me to remain i386? The only problem might be if you want to use wine. As it has been said, there are binary packages (wine_amd64, if I remember correctly), but the rest of the system should run good on amd64 as it did on i386. Sidenote: I switched back from 8.2/amd64 to 8.2/i386 because of three reasons (in fact, two reasons and one justification): I had problems with wine, problems with nVidia's driver (plus a faulty GPU), and I only have 2 GB RAM. Anywhere else, I have not experienced problems with amd64. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: i386 vs amd64
> What port was that ? > > I've never had a *single* problem due to using amd64 over i386. Well I have to apologize, I've reached senility! My past bad experience was with netbsd amd64 afterwhich I bailed and went to FreeBSD i386 (thanks google). But I guess the basic question remains - are there any considerations in regards ports, linux emulation, etc that would sway me to remain i386? Sorry about that! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: i386 vs amd64
On Wed, 28 Nov 2012, mike miskulin wrote: About to build a replacement system for an older i386 setup. A few years ago I had tried the amd64 port on it and found it was frustrating as things that just worked on i386 did not on amd64. IIRC ports were large annoyance too. Now I have a new system with 8GB, etc,etc and wonder if I am best off to stick with i386 and PAE or is the amd64 version finally on a par or close enough that I would not likely have many issues like in the past? Thanks for your thoughts/(recent) experiences. Do you use emulators/wine? If not, switch to amd64. In fact, even if you do, switch to amd64 to use that 8G of memory. Building 32-bit Wine on amd64 is a hassle, but packages are available and I think there is a 64-bit port on the way. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: i386 vs amd64
On Nov 28, 2012, at 6:36 PM, mike miskulin wrote: > About to build a replacement system for an older i386 setup. A few > years ago I had tried the amd64 port on it and found it was frustrating > as things that just worked on i386 did not on amd64. IIRC ports were > large annoyance too. > > Now I have a new system with 8GB, etc,etc and wonder if I am best off to > stick with i386 and PAE or is the amd64 version finally on a par or > close enough that I would not likely have many issues like in the past? > > Thanks for your thoughts/(recent) experiences. What port was that ? I've never had a *single* problem due to using amd64 over i386. >From a professional point of view, we're using over 60 amd64 fbsd 8.0 8.1 8.2 >and 8.3 boxes at work and they work just fine. I for one can recommend the 64 bits version. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
i386 vs amd64
About to build a replacement system for an older i386 setup. A few years ago I had tried the amd64 port on it and found it was frustrating as things that just worked on i386 did not on amd64. IIRC ports were large annoyance too. Now I have a new system with 8GB, etc,etc and wonder if I am best off to stick with i386 and PAE or is the amd64 version finally on a par or close enough that I would not likely have many issues like in the past? Thanks for your thoughts/(recent) experiences. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: do I need agp(4) on my amd64 laptop
On 25 November 2012 06:11, Anton Shterenlikht wrote: > From ill...@gmail.com Sat Nov 24 16:09:29 2012 > > On 22 November 2012 06:19, Anton Shterenlikht > wrote: > >> It is not clear for me from the agp(4) man page, > >> whether I need this device in the kernel or not. ... > >> hostb4@pci0:0:24:3: class=0x06 card=0x > chip=0x11031022 rev=0x00 hdr=0x00 > >> vendor = 'Advanced Micro Devices [AMD]' > >> device = 'K8 [Athlon64/Opteron] Miscellaneous Control' > >> class = bridge > >> subclass = HOST-PCI > >> vgapci0@pci0:1:5:0: class=0x03 card=0x30c2103c > chip=0x791f1002 rev=0x00 hdr=0x00 > >> vendor = 'Advanced Micro Devices [AMD] nee ATI' > >> device = 'RS690M [Radeon X1200 Series]' > >> class = display > >> subclass = VGA > >> bge0@pci0:16:0:0: class=0x02 card=0x30c2103c > chip=0x171314e4 rev=0x02 hdr=0x00 > >> vendor = 'Broadcom Corporation' > >> device = 'NetLink BCM5906M Fast Ethernet PCI Express' > >> class = network > >> subclass = ethernet > >> siba_bwn0@pci0:48:0:0: class=0x028000 card=0x1371103c > chip=0x431214e4 rev=0x02 hdr=0x00 > >> vendor = 'Broadcom Corporation' > >> device = 'BCM4311 802.11a/b/g' > >> class = network > >> cbb0@pci0:2:4:0:class=0x060700 card=0x30c2103c > chip=0x04761180 rev=0xb6 hdr=0x02 > >> vendor = 'Ricoh Co Ltd' > >> device = 'RL5c476 II' > >> class = bridge > >> subclass = PCI-CardBus > > > > You bring up a good point. Your laptop is almost the same as mine, > > & the graphics chip is connected via PCI Express. > > I should see if it builds & runs without agp. > > > > Looks like drm requires agp for the kernel to link correctly. > Oh well. > > ... > drm_agpsupport.o: In function `drm_agp_free_memory': > /home/svn/9.1/src/sys/dev/drm/drm_agpsupport.c:(.text+0xcba): > undefined reference to `agp_fi > nd_device' > /home/svn/9.1/src/sys/dev/drm/drm_agpsupport.c:(.text+0xcd4): > undefined reference to `agp_fr > ee_memory' > drm_agpsupport.o: In function `drm_agp_init': > /home/svn/9.1/src/sys/dev/drm/drm_agpsupport.c:(.text+0xdb8): > undefined reference to `agp_fi > nd_device' > /home/svn/9.1/src/sys/dev/drm/drm_agpsupport.c:(.text+0xe2f): > undefined reference to `agp_ge > t_info' > *** [kernel] Error code 1 > ... > > ok, I get it. I think I built drm and agp > together, hence I haven't encountered this > error. > > Do you use radeon video driver? > Do you use radeondrm device in kernel? > This only place I see this is in > src/sys/amd64/conf/NOTES. > My understanding is that to get drm > working with the radeon driver, I need > to add radeondrm to the kernel, but again, > I'm not sure. Yes, I use the radeon driver in xorg, & I have radeondrm in kernel. I don't think you need to build it in, as loading the module should work, I just got in the habit a while back & can't seem to quit now. -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: do I need agp(4) on my amd64 laptop
002 rev=0x00 hdr=0x00 >> vendor = 'Advanced Micro Devices [AMD] nee ATI' >> device = 'SB600 IDE' >> class = mass storage >> subclass = ATA >> hdac0@pci0:0:20:2: class=0x040300 card=0x30c2103c chip=0x43831002 rev=0x00 hdr=0x00 >> vendor = 'Advanced Micro Devices [AMD] nee ATI' >> device = 'SBx00 Azalia (Intel HDA)' >> class = multimedia >> subclass = HDA >> isab0@pci0:0:20:3: class=0x060100 card=0x30c2103c chip=0x438d1002 rev=0x00 hdr=0x00 >> vendor = 'Advanced Micro Devices [AMD] nee ATI' >> device = 'SB600 PCI to LPC Bridge' >> class = bridge >> subclass = PCI-ISA >> pcib5@pci0:0:20:4: class=0x060401 card=0x chip=0x43841002 rev=0x00 hdr=0x01 >> vendor = 'Advanced Micro Devices [AMD] nee ATI' >> device = 'SBx00 PCI to PCI Bridge' >> class = bridge >> subclass = PCI-PCI >> hostb1@pci0:0:24:0: class=0x06 card=0x chip=0x11001022 rev=0x00 hdr=0x00 >> vendor = 'Advanced Micro Devices [AMD]' >> device = 'K8 [Athlon64/Opteron] HyperTransport Technology Configuration' >> class = bridge >> subclass = HOST-PCI >> hostb2@pci0:0:24:1: class=0x06 card=0x chip=0x11011022 rev=0x00 hdr=0x00 >> vendor = 'Advanced Micro Devices [AMD]' >> device = 'K8 [Athlon64/Opteron] Address Map' >> class = bridge >> subclass = HOST-PCI >> hostb3@pci0:0:24:2: class=0x06 card=0x chip=0x11021022 rev=0x00 hdr=0x00 >> vendor = 'Advanced Micro Devices [AMD]' >> device = 'K8 [Athlon64/Opteron] DRAM Controller' >> class = bridge >> subclass = HOST-PCI >> hostb4@pci0:0:24:3: class=0x06 card=0x chip=0x11031022 rev=0x00 hdr=0x00 >> vendor = 'Advanced Micro Devices [AMD]' >> device = 'K8 [Athlon64/Opteron] Miscellaneous Control' >> class = bridge >> subclass = HOST-PCI >> vgapci0@pci0:1:5:0: class=0x03 card=0x30c2103c chip=0x791f1002 rev=0x00 hdr=0x00 >> vendor = 'Advanced Micro Devices [AMD] nee ATI' >> device = 'RS690M [Radeon X1200 Series]' >> class = display >> subclass = VGA >> bge0@pci0:16:0:0: class=0x02 card=0x30c2103c chip=0x171314e4 rev=0x02 hdr=0x00 >> vendor = 'Broadcom Corporation' >> device = 'NetLink BCM5906M Fast Ethernet PCI Express' >> class = network >> subclass = ethernet >> siba_bwn0@pci0:48:0:0: class=0x028000 card=0x1371103c chip=0x431214e4 rev=0x02 hdr=0x00 >> vendor = 'Broadcom Corporation' >> device = 'BCM4311 802.11a/b/g' >> class = network >> cbb0@pci0:2:4:0:class=0x060700 card=0x30c2103c chip=0x04761180 rev=0xb6 hdr=0x02 >> vendor = 'Ricoh Co Ltd' >> device = 'RL5c476 II' >> class = bridge >> subclass = PCI-CardBus > > You bring up a good point. Your laptop is almost the same as mine, > & the graphics chip is connected via PCI Express. > I should see if it builds & runs without agp. > Looks like drm requires agp for the kernel to link correctly. Oh well. ... drm_agpsupport.o: In function `drm_agp_free_memory': /home/svn/9.1/src/sys/dev/drm/drm_agpsupport.c:(.text+0xcba): undefined reference to `agp_fi nd_device' /home/svn/9.1/src/sys/dev/drm/drm_agpsupport.c:(.text+0xcd4): undefined reference to `agp_fr ee_memory' drm_agpsupport.o: In function `drm_agp_init': /home/svn/9.1/src/sys/dev/drm/drm_agpsupport.c:(.text+0xdb8): undefined reference to `agp_fi nd_device' /home/svn/9.1/src/sys/dev/drm/drm_agpsupport.c:(.text+0xe2f): undefined reference to `agp_ge t_info' *** [kernel] Error code 1 ... ok, I get it. I think I built drm and agp together, hence I haven't encountered this error. Do you use radeon video driver? Do you use radeondrm device in kernel? This only place I see this is in src/sys/amd64/conf/NOTES. My understanding is that to get drm working with the radeon driver, I need to add radeondrm to the kernel, but again, I'm not sure. Anton ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: do I need agp(4) on my amd64 laptop
From ill...@gmail.com Sat Nov 24 16:09:29 2012 On 22 November 2012 06:19, Anton Shterenlikht wrote: > It is not clear for me from the agp(4) man page, > whether I need this device in the kernel or not. > The pciconf -lv output is below. Or do I need to > show dmesg? > > Please advise > > Thanks > Anton > > > hostb0@pci0:0:0:0: class=0x06 card=0x30c2103c chip=0x79101002 rev=0x00 hdr=0x00 > vendor = 'Advanced Micro Devices [AMD] nee ATI' > device = 'RS690 Host Bridge' > class = bridge > subclass = HOST-PCI > pcib1@pci0:0:1:0: class=0x060400 card=0x30c2103c chip=0x79121002 rev=0x00 hdr=0x01 > vendor = 'Advanced Micro Devices [AMD] nee ATI' > device = 'RS690 PCI to PCI Bridge (Internal gfx)' > class = bridge > subclass = PCI-PCI > pcib2@pci0:0:4:0: class=0x060400 card=0x30c2103c chip=0x79141002 rev=0x00 hdr=0x01 > vendor = 'Advanced Micro Devices [AMD] nee ATI' > class = bridge > subclass = PCI-PCI > pcib3@pci0:0:5:0: class=0x060400 card=0x30c2103c chip=0x79151002 rev=0x00 hdr=0x01 > vendor = 'Advanced Micro Devices [AMD] nee ATI' > device = 'RS690 PCI to PCI Bridge (PCI Express Port 1)' > class = bridge > subclass = PCI-PCI > pcib4@pci0:0:6:0: class=0x060400 card=0x30c2103c chip=0x79161002 rev=0x00 hdr=0x01 > vendor = 'Advanced Micro Devices [AMD] nee ATI' > device = 'RS690 PCI to PCI Bridge (PCI Express Port 2)' > class = bridge > subclass = PCI-PCI > ahci0@pci0:0:18:0: class=0x01018f card=0x43801002 chip=0x43801002 rev=0x00 hdr=0x00 > vendor = 'Advanced Micro Devices [AMD] nee ATI' > device = 'SB600 Non-Raid-5 SATA' > class = mass storage > subclass = ATA > ohci0@pci0:0:19:0: class=0x0c0310 card=0x30c2103c chip=0x43871002 rev=0x00 hdr=0x00 > vendor = 'Advanced Micro Devices [AMD] nee ATI' > device = 'SB600 USB (OHCI0)' > class = serial bus > subclass = USB > ohci1@pci0:0:19:1: class=0x0c0310 card=0x30c2103c chip=0x43881002 rev=0x00 hdr=0x00 > vendor = 'Advanced Micro Devices [AMD] nee ATI' > device = 'SB600 USB (OHCI1)' > class = serial bus > subclass = USB > ohci2@pci0:0:19:2: class=0x0c0310 card=0x30c2103c chip=0x43891002 rev=0x00 hdr=0x00 > vendor = 'Advanced Micro Devices [AMD] nee ATI' > device = 'SB600 USB (OHCI2)' > class = serial bus > subclass = USB > ohci3@pci0:0:19:3: class=0x0c0310 card=0x30c2103c chip=0x438a1002 rev=0x00 hdr=0x00 > vendor = 'Advanced Micro Devices [AMD] nee ATI' > device = 'SB600 USB (OHCI3)' > class = serial bus > subclass = USB > ohci4@pci0:0:19:4: class=0x0c0310 card=0x30c2103c chip=0x438b1002 rev=0x00 hdr=0x00 > vendor = 'Advanced Micro Devices [AMD] nee ATI' > device = 'SB600 USB (OHCI4)' > class = serial bus > subclass = USB > ehci0@pci0:0:19:5: class=0x0c0320 card=0x30c2103c chip=0x43861002 rev=0x00 hdr=0x00 > vendor = 'Advanced Micro Devices [AMD] nee ATI' > device = 'SB600 USB Controller (EHCI)' > class = serial bus > subclass = USB > none0@pci0:0:20:0: class=0x0c0500 card=0x30c2103c chip=0x43851002 rev=0x14 hdr=0x00 > vendor = 'Advanced Micro Devices [AMD] nee ATI' > device = 'SBx00 SMBus Controller' > class = serial bus > subclass = SMBus > atapci0@pci0:0:20:1:class=0x010182 card=0x30c2103c chip=0x438c1002 rev=0x00 hdr=0x00 > vendor = 'Advanced Micro Devices [AMD] nee ATI' > device = 'SB600 IDE' > class = mass storage > subclass = ATA > hdac0@pci0:0:20:2: class=0x040300 card=0x30c2103c chip=0x43831002 rev=0x00 hdr=0x00 > vendor = 'Advanced Micro Devices [AMD] nee ATI' > device = 'SBx00 Azalia (Intel HDA)' > class = multimedia > subclass = HDA > isab0@pci0:0:20:3: class=0x060100 card=0x30c2103c chip=0x438d1002 rev=0x00 hdr=0x00 > vendor = 'Advanced Micro Devices [AMD] nee ATI' > device = 'SB600 PCI to LPC Bridge' > class = bridge > subclass = PCI-ISA > pci
Re: do I need agp(4) on my amd64 laptop
On 24 November 2012 10:14, ill...@gmail.com wrote: > On 22 November 2012 06:19, Anton Shterenlikht wrote: >> It is not clear for me from the agp(4) man page, >> whether I need this device in the kernel or not. >> The pciconf -lv output is below. Or do I need to >> show dmesg? >> >> Please advise >> >> Thanks >> Anton >> >> >> hostb0@pci0:0:0:0: class=0x06 card=0x30c2103c chip=0x79101002 >> rev=0x00 hdr=0x00 >> vendor = 'Advanced Micro Devices [AMD] nee ATI' >> device = 'RS690 Host Bridge' >> class = bridge >> subclass = HOST-PCI >> pcib1@pci0:0:1:0: class=0x060400 card=0x30c2103c chip=0x79121002 >> rev=0x00 hdr=0x01 >> vendor = 'Advanced Micro Devices [AMD] nee ATI' >> device = 'RS690 PCI to PCI Bridge (Internal gfx)' >> class = bridge >> subclass = PCI-PCI >> pcib2@pci0:0:4:0: class=0x060400 card=0x30c2103c chip=0x79141002 >> rev=0x00 hdr=0x01 >> vendor = 'Advanced Micro Devices [AMD] nee ATI' >> class = bridge >> subclass = PCI-PCI >> pcib3@pci0:0:5:0: class=0x060400 card=0x30c2103c chip=0x79151002 >> rev=0x00 hdr=0x01 >> vendor = 'Advanced Micro Devices [AMD] nee ATI' >> device = 'RS690 PCI to PCI Bridge (PCI Express Port 1)' >> class = bridge >> subclass = PCI-PCI >> pcib4@pci0:0:6:0: class=0x060400 card=0x30c2103c chip=0x79161002 >> rev=0x00 hdr=0x01 >> vendor = 'Advanced Micro Devices [AMD] nee ATI' >> device = 'RS690 PCI to PCI Bridge (PCI Express Port 2)' >> class = bridge >> subclass = PCI-PCI >> ahci0@pci0:0:18:0: class=0x01018f card=0x43801002 chip=0x43801002 >> rev=0x00 hdr=0x00 >> vendor = 'Advanced Micro Devices [AMD] nee ATI' >> device = 'SB600 Non-Raid-5 SATA' >> class = mass storage >> subclass = ATA >> ohci0@pci0:0:19:0: class=0x0c0310 card=0x30c2103c chip=0x43871002 >> rev=0x00 hdr=0x00 >> vendor = 'Advanced Micro Devices [AMD] nee ATI' >> device = 'SB600 USB (OHCI0)' >> class = serial bus >> subclass = USB >> ohci1@pci0:0:19:1: class=0x0c0310 card=0x30c2103c chip=0x43881002 >> rev=0x00 hdr=0x00 >> vendor = 'Advanced Micro Devices [AMD] nee ATI' >> device = 'SB600 USB (OHCI1)' >> class = serial bus >> subclass = USB >> ohci2@pci0:0:19:2: class=0x0c0310 card=0x30c2103c chip=0x43891002 >> rev=0x00 hdr=0x00 >> vendor = 'Advanced Micro Devices [AMD] nee ATI' >> device = 'SB600 USB (OHCI2)' >> class = serial bus >> subclass = USB >> ohci3@pci0:0:19:3: class=0x0c0310 card=0x30c2103c chip=0x438a1002 >> rev=0x00 hdr=0x00 >> vendor = 'Advanced Micro Devices [AMD] nee ATI' >> device = 'SB600 USB (OHCI3)' >> class = serial bus >> subclass = USB >> ohci4@pci0:0:19:4: class=0x0c0310 card=0x30c2103c chip=0x438b1002 >> rev=0x00 hdr=0x00 >> vendor = 'Advanced Micro Devices [AMD] nee ATI' >> device = 'SB600 USB (OHCI4)' >> class = serial bus >> subclass = USB >> ehci0@pci0:0:19:5: class=0x0c0320 card=0x30c2103c chip=0x43861002 >> rev=0x00 hdr=0x00 >> vendor = 'Advanced Micro Devices [AMD] nee ATI' >> device = 'SB600 USB Controller (EHCI)' >> class = serial bus >> subclass = USB >> none0@pci0:0:20:0: class=0x0c0500 card=0x30c2103c chip=0x43851002 >> rev=0x14 hdr=0x00 >> vendor = 'Advanced Micro Devices [AMD] nee ATI' >> device = 'SBx00 SMBus Controller' >> class = serial bus >> subclass = SMBus >> atapci0@pci0:0:20:1:class=0x010182 card=0x30c2103c chip=0x438c1002 >> rev=0x00 hdr=0x00 >> vendor = 'Advanced Micro Devices [AMD] nee ATI' >> device = 'SB600 IDE' >> class = mass storage >> subclass = ATA >> hdac0@pci0:0:20:2: class=0x040300 card=0x30c2103c chip=0x43831002 >> rev=0x00 hdr=0x00 >> vendor = 'Advanced Micro Devices [AMD] nee ATI' >> device = 'SBx00 Azalia (Intel HDA)' >> class = multimedia >> subclass = HDA >> isab0@pci0:0:20:3: class=0x060100 card=0x30c2103c chip=0x438d1002 >> rev=0x00 hdr=0x00 >> vendor = 'Advanced Micro Devices [AMD] nee ATI' >> device = 'SB600 PCI to LPC Bridge' >> class = bridge >> subclass = PCI-ISA >> pcib5@pci0:0:20:4: class=0x060401 card=0x chip=0x43841002 >> rev=0x00 hdr=0x01 >> vendor = 'Advanced Micro Devices [AMD] nee ATI' >> device = 'SBx00 PCI to PCI Bridge' >> class = bridge >> subclass = PCI-PCI >> hostb1@pci0:0:24:0: class=0x06 card=0x chip=0x11001022 >> rev=0x00 hdr=0x00 >> vendor = 'Advanced Micro Devices [AMD]' >> device = 'K8 [Athlon64/Opteron] HyperTransport Technology >> Configuration' >> class = bridge >> subclass = HOST-PCI >> hostb2@pci0:0:24:1: class=0x06 card=0x c
Re: do I need agp(4) on my amd64 laptop
On 22 November 2012 06:19, Anton Shterenlikht wrote: > It is not clear for me from the agp(4) man page, > whether I need this device in the kernel or not. > The pciconf -lv output is below. Or do I need to > show dmesg? > > Please advise > > Thanks > Anton > > > hostb0@pci0:0:0:0: class=0x06 card=0x30c2103c chip=0x79101002 > rev=0x00 hdr=0x00 > vendor = 'Advanced Micro Devices [AMD] nee ATI' > device = 'RS690 Host Bridge' > class = bridge > subclass = HOST-PCI > pcib1@pci0:0:1:0: class=0x060400 card=0x30c2103c chip=0x79121002 > rev=0x00 hdr=0x01 > vendor = 'Advanced Micro Devices [AMD] nee ATI' > device = 'RS690 PCI to PCI Bridge (Internal gfx)' > class = bridge > subclass = PCI-PCI > pcib2@pci0:0:4:0: class=0x060400 card=0x30c2103c chip=0x79141002 > rev=0x00 hdr=0x01 > vendor = 'Advanced Micro Devices [AMD] nee ATI' > class = bridge > subclass = PCI-PCI > pcib3@pci0:0:5:0: class=0x060400 card=0x30c2103c chip=0x79151002 > rev=0x00 hdr=0x01 > vendor = 'Advanced Micro Devices [AMD] nee ATI' > device = 'RS690 PCI to PCI Bridge (PCI Express Port 1)' > class = bridge > subclass = PCI-PCI > pcib4@pci0:0:6:0: class=0x060400 card=0x30c2103c chip=0x79161002 > rev=0x00 hdr=0x01 > vendor = 'Advanced Micro Devices [AMD] nee ATI' > device = 'RS690 PCI to PCI Bridge (PCI Express Port 2)' > class = bridge > subclass = PCI-PCI > ahci0@pci0:0:18:0: class=0x01018f card=0x43801002 chip=0x43801002 > rev=0x00 hdr=0x00 > vendor = 'Advanced Micro Devices [AMD] nee ATI' > device = 'SB600 Non-Raid-5 SATA' > class = mass storage > subclass = ATA > ohci0@pci0:0:19:0: class=0x0c0310 card=0x30c2103c chip=0x43871002 > rev=0x00 hdr=0x00 > vendor = 'Advanced Micro Devices [AMD] nee ATI' > device = 'SB600 USB (OHCI0)' > class = serial bus > subclass = USB > ohci1@pci0:0:19:1: class=0x0c0310 card=0x30c2103c chip=0x43881002 > rev=0x00 hdr=0x00 > vendor = 'Advanced Micro Devices [AMD] nee ATI' > device = 'SB600 USB (OHCI1)' > class = serial bus > subclass = USB > ohci2@pci0:0:19:2: class=0x0c0310 card=0x30c2103c chip=0x43891002 > rev=0x00 hdr=0x00 > vendor = 'Advanced Micro Devices [AMD] nee ATI' > device = 'SB600 USB (OHCI2)' > class = serial bus > subclass = USB > ohci3@pci0:0:19:3: class=0x0c0310 card=0x30c2103c chip=0x438a1002 > rev=0x00 hdr=0x00 > vendor = 'Advanced Micro Devices [AMD] nee ATI' > device = 'SB600 USB (OHCI3)' > class = serial bus > subclass = USB > ohci4@pci0:0:19:4: class=0x0c0310 card=0x30c2103c chip=0x438b1002 > rev=0x00 hdr=0x00 > vendor = 'Advanced Micro Devices [AMD] nee ATI' > device = 'SB600 USB (OHCI4)' > class = serial bus > subclass = USB > ehci0@pci0:0:19:5: class=0x0c0320 card=0x30c2103c chip=0x43861002 > rev=0x00 hdr=0x00 > vendor = 'Advanced Micro Devices [AMD] nee ATI' > device = 'SB600 USB Controller (EHCI)' > class = serial bus > subclass = USB > none0@pci0:0:20:0: class=0x0c0500 card=0x30c2103c chip=0x43851002 > rev=0x14 hdr=0x00 > vendor = 'Advanced Micro Devices [AMD] nee ATI' > device = 'SBx00 SMBus Controller' > class = serial bus > subclass = SMBus > atapci0@pci0:0:20:1:class=0x010182 card=0x30c2103c chip=0x438c1002 > rev=0x00 hdr=0x00 > vendor = 'Advanced Micro Devices [AMD] nee ATI' > device = 'SB600 IDE' > class = mass storage > subclass = ATA > hdac0@pci0:0:20:2: class=0x040300 card=0x30c2103c chip=0x43831002 > rev=0x00 hdr=0x00 > vendor = 'Advanced Micro Devices [AMD] nee ATI' > device = 'SBx00 Azalia (Intel HDA)' > class = multimedia > subclass = HDA > isab0@pci0:0:20:3: class=0x060100 card=0x30c2103c chip=0x438d1002 > rev=0x00 hdr=0x00 > vendor = 'Advanced Micro Devices [AMD] nee ATI' > device = 'SB600 PCI to LPC Bridge' > class = bridge > subclass = PCI-ISA > pcib5@pci0:0:20:4: class=0x060401 card=0x chip=0x43841002 > rev=0x00 hdr=0x01 > vendor = 'Advanced Micro Devices [AMD] nee ATI' > device = 'SBx00 PCI to PCI Bridge' > class = bridge > subclass = PCI-PCI > hostb1@pci0:0:24:0: class=0x06 card=0x chip=0x11001022 > rev=0x00 hdr=0x00 > vendor = 'Advanced Micro Devices [AMD]' > device = 'K8 [Athlon64/Opteron] HyperTransport Technology > Configuration' > class = bridge > subclass = HOST-PCI > hostb2@pci0:0:24:1: class=0x06 card=0x chip=0x11011022 > rev=0x00 hdr=0x00 > vendor = 'Advanced Micro Devices [AMD]' > device = 'K8 [Athlon64/Opteron] Address Map' > class = bridge > s
do I need agp(4) on my amd64 laptop
It is not clear for me from the agp(4) man page, whether I need this device in the kernel or not. The pciconf -lv output is below. Or do I need to show dmesg? Please advise Thanks Anton hostb0@pci0:0:0:0: class=0x06 card=0x30c2103c chip=0x79101002 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'RS690 Host Bridge' class = bridge subclass = HOST-PCI pcib1@pci0:0:1:0: class=0x060400 card=0x30c2103c chip=0x79121002 rev=0x00 hdr=0x01 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'RS690 PCI to PCI Bridge (Internal gfx)' class = bridge subclass = PCI-PCI pcib2@pci0:0:4:0: class=0x060400 card=0x30c2103c chip=0x79141002 rev=0x00 hdr=0x01 vendor = 'Advanced Micro Devices [AMD] nee ATI' class = bridge subclass = PCI-PCI pcib3@pci0:0:5:0: class=0x060400 card=0x30c2103c chip=0x79151002 rev=0x00 hdr=0x01 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'RS690 PCI to PCI Bridge (PCI Express Port 1)' class = bridge subclass = PCI-PCI pcib4@pci0:0:6:0: class=0x060400 card=0x30c2103c chip=0x79161002 rev=0x00 hdr=0x01 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'RS690 PCI to PCI Bridge (PCI Express Port 2)' class = bridge subclass = PCI-PCI ahci0@pci0:0:18:0: class=0x01018f card=0x43801002 chip=0x43801002 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'SB600 Non-Raid-5 SATA' class = mass storage subclass = ATA ohci0@pci0:0:19:0: class=0x0c0310 card=0x30c2103c chip=0x43871002 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'SB600 USB (OHCI0)' class = serial bus subclass = USB ohci1@pci0:0:19:1: class=0x0c0310 card=0x30c2103c chip=0x43881002 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'SB600 USB (OHCI1)' class = serial bus subclass = USB ohci2@pci0:0:19:2: class=0x0c0310 card=0x30c2103c chip=0x43891002 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'SB600 USB (OHCI2)' class = serial bus subclass = USB ohci3@pci0:0:19:3: class=0x0c0310 card=0x30c2103c chip=0x438a1002 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'SB600 USB (OHCI3)' class = serial bus subclass = USB ohci4@pci0:0:19:4: class=0x0c0310 card=0x30c2103c chip=0x438b1002 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'SB600 USB (OHCI4)' class = serial bus subclass = USB ehci0@pci0:0:19:5: class=0x0c0320 card=0x30c2103c chip=0x43861002 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'SB600 USB Controller (EHCI)' class = serial bus subclass = USB none0@pci0:0:20:0: class=0x0c0500 card=0x30c2103c chip=0x43851002 rev=0x14 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'SBx00 SMBus Controller' class = serial bus subclass = SMBus atapci0@pci0:0:20:1:class=0x010182 card=0x30c2103c chip=0x438c1002 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'SB600 IDE' class = mass storage subclass = ATA hdac0@pci0:0:20:2: class=0x040300 card=0x30c2103c chip=0x43831002 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'SBx00 Azalia (Intel HDA)' class = multimedia subclass = HDA isab0@pci0:0:20:3: class=0x060100 card=0x30c2103c chip=0x438d1002 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'SB600 PCI to LPC Bridge' class = bridge subclass = PCI-ISA pcib5@pci0:0:20:4: class=0x060401 card=0x chip=0x43841002 rev=0x00 hdr=0x01 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'SBx00 PCI to PCI Bridge' class = bridge subclass = PCI-PCI hostb1@pci0:0:24:0: class=0x06 card=0x chip=0x11001022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD]' device = 'K8 [Athlon64/Opteron] HyperTransport Technology Configuration' class = bridge subclass = HOST-PCI hostb2@pci0:0:24:1: class=0x06 card=0x chip=0x11011022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD]' device = 'K8 [Athlon64/Opteron] Address Map' class = bridge subclass = HOST-PCI hostb3@pci0:0:24:2: class=0x06 card=0x chip=0x11021022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD]' device = 'K8 [Athlon64/Opteron] DRAM Controller' class = bridge subclass = HOST-PCI hostb4@pci0:0:24:3: class=0x060
valgrind on pure amd64 (64 bit system _only_)
What's state of valgrind port on pure amd64 system? Here, it core dumps upon linking both with clang and gcc47, with complaint that looks suspicious (expected i386 not X86_64 or something to that effect). -- View this message in context: http://freebsd.1045724.n5.nabble.com/valgrind-on-pure-amd64-64-bit-system-only-tp5762993.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: nvidia driver on amd64 (for asus nvidia gt 610)
On 10/27/12 07:50, Gary Aitken wrote: > running 9.0 release > > Being frustrated with my radeon hd-5550 video card which occasionally > (once a week or so) goes into some kind of reset loop, filling up > Xorg.0.log and crashing the system because /var is full... > > I picked up an asus nvidia gt 610. > Downloaded the nvidia driver and tried to build it. > > make ominously reports: >ld: Relocatable linking with relocations from format elf32-i386-freebsd >(nv-kernel.o) to format elf64-x86-64-freebsd (nvidia.ko) is not > supported. > > Where is the elf32-i386-freebsd stuff coming from? > I just unpacked the driver in a tmp directory and did a make install there. > > I found the following which implied it is a make problem in 9.0: > > http://lists.freebsd.org/pipermail/freebsd-toolchain/2011-August/000265.html > > I'm guessing it can be made to work but I need to define appropriate make > architecture variables, and I'm not sure how to do dat. > Hints? > > BTW, can anyone explain why Xorg.*.log doesn't get closed and a new file > opened when it gets rather large and then rotate the way syslogs normally do? > It seems to rotate only when the server is restarted, or at least that's all > I've observed. My apologies for the original double posting; saw a temporary reject in my maillog and thought it would turn into a real one due to a past problem. I found the following patch and applied it, http://www.mail-archive.com/freebsd-toolchain@freebsd.org/msg00256.html Also discovered I had downloaded the x86 version instead of the 64bit version. "make CC=clang CXX=clang++ install" seemed to work; now on to testing it. Sorry for the mixup. Gary ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
nvidia driver on amd64 (for asus nvidia gt 610)
running 9.0 release Being frustrated with my radeon hd-5550 video card which occasionally (once a week or so) goes into some kind of reset loop, filling up Xorg.0.log and crashing the system because /var is full... I picked up an asus nvidia gt 610. Downloaded the nvidia driver and tried to build it. make ominously reports: ld: Relocatable linking with relocations from format elf32-i386-freebsd (nv-kernel.o) to format elf64-x86-64-freebsd (nvidia.ko) is not supported. Where is the elf32-i386-freebsd stuff coming from? I just unpacked the driver in a tmp directory and did a make install there. I found the following which implied it is a make problem in 9.0: http://lists.freebsd.org/pipermail/freebsd-toolchain/2011-August/000265.html I'm guessing it can be made to work but I need to define appropriate make architecture variables, and I'm not sure how to do dat. Hints? BTW, can anyone explain why Xorg.*.log doesn't get closed and a new file opened when it gets rather large and then rotate the way syslogs normally do? It seems to rotate only when the server is restarted, or at least that's all I've observed. Thanks, Gary ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
nvidia driver on amd64 (for asus nvidia gt 610)
running 9.0 release Being frustrated with my radeon hd-5550 video card which occasionally (once a week or so) goes into some kind of reset loop, filling up Xorg.0.log and crashing the system because /var is full... I picked up an asus nvidia gt 610. Downloaded the nvidia driver and tried to build it. make ominously reports: ld: Relocatable linking with relocations from format elf32-i386-freebsd (nv-kernel.o) to format elf64-x86-64-freebsd (nvidia.ko) is not supported. Where is the elf32-i386-freebsd stuff coming from? I unpacked the driver in a tmp directory and did a make install there. I found the following which implied it is a make problem in 9.0: http://lists.freebsd.org/pipermail/freebsd-toolchain/2011-August/000265.html I'm guessing it can be made to work but I need to define appropriate make architecture variables, and I'm not sure how to do dat. Hints? BTW, can anyone explain why Xorg.*.log doesn't get closed and a new file opened when it gets rather large and then rotate the way syslogs normally do? It seems to rotate only when the server is restarted, or at least that's all I've observed. Thanks, Gary ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 'svn up' problem on amd64
On 21/10/2012 07:35, Darrel wrote: > Advice? I have not seen this before: > > (685) @ 2:22:16> cd /usr/src > (686) @ 2:22:18> svn up > Updating '.': > Skipped 'sys' -- Node remains in conflict > At revision 241794. > Summary of conflicts: > Skipped paths: 1 > (687) @ 2:22:43> For some reason svn thinks your local copy of sys conflicts with the copy from the repo. That could happen if you have local patches or similar, but svn would usually prompt you to merge any such. Also this seems to have affected people completely innocent of any such changes. Assuming you've checked out the stable/9 branch then I think this (untested) command should resolve the problems: # cd /usr/src # svn merge --accept theirs-full ^/stable/9 Use 'svn info' to see what the URL setting for your repo is -- you can just paste that in as is instead of '^/stable/9', or you can use the shorthand '^' which stands for the text from the 'Repository Root' setting plus the rest of the URL string. Note that the 'theirs-full' method of resolving conflicts will tend to wipe out any local changes you may have. If that is a concern, then you could try using the 'edit' method instead. (As the name suggests, this puts you in an editor showing the conflicting merge results, and requires you to edit things into what the result of the mmerge should have been.) Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
'svn up' problem on amd64
Hello, Advice? I have not seen this before: (685) @ 2:22:16> cd /usr/src (686) @ 2:22:18> svn up Updating '.': Skipped 'sys' -- Node remains in conflict At revision 241794. Summary of conflicts: Skipped paths: 1 (687) @ 2:22:43> - more background information: ZFS Subsystem ReportSun Oct 21 02:32:36 2012 System Information: Kernel Version: 901000 (osreldate) Hardware Platform: amd64 Processor Architecture: amd64 ZFS Storage pool Version: 28 ZFS Filesystem Version: 5 FreeBSD 9.1-RC2 #0 r241106: Mon Oct 1 18:26:44 UTC 2012 root 2:32AM up 4 days, 18:32, 7 users, load averages: 0.14, 0.10, 0.08 Darrel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 8.3 stable or 9.0 stable amd64 iso with mfi driver changes of May 18, 2012
Kevin, Thank you for your response. It is great to get confirmation and I will try with 9.1-RC1 I DO have on board Broadcom 5720 NIC. Nice to know what my next problem is likely to be. Hopefully that will be easy to solve if I install another NIC card. Thanks! Jean Jean Christofferson je...@relevantpower.com Relevant Power, Inc. www.relevanttools.com On Sep 14, 2012, at 6:14 PM, kpn...@pobox.com wrote: On Fri, Sep 14, 2012 at 04:45:49PM -0700, Jean Christofferson wrote: I am trying to install FreeBSD stable - either 8.3 or 9.0 - on a Dell 420 with Perc H310 LSI PCI Express SAS Raid controllers. Although the physical disks are present and recognized by the BIOS the sysinstall does not see the disks. I think the issue is mfi driver and was added to the stable release May 18, 2012. Yup, the 12G machines came out when the paint was drying on 8.3. So there isn't a -stable release with the updated driver. The new mfi driver is in 9.1-RC1 if you are OK with a pre-release. I hope you don't have the Broadcom 5720 NIC like the R620. The FreeBSD driver (bge) isn't finished yet. At least, I don't remember seeing it go into the tree. It's known to _not_ work on the R620 and I believe R720. -- Kevin P. Nealhttp://www.pobox.com/ ~kpn/ "Nonbelievers found it difficult to defend their position in \ the presense of a working computer." -- a DEC Jensen paper ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
8.3 stable or 9.0 stable amd64 iso with mfi driver changes of May 18, 2012
I am trying to install FreeBSD stable - either 8.3 or 9.0 - on a Dell 420 with Perc H310 LSI PCI Express SAS Rain controllers. Although the physical disks are present and recognized by the BIOS the sysinstall does not see the disks. I think the issue is mfi driver and was added to the stable release May 18, 2012. http://www.FreeBSD.org/cgi/man.cgi?query=mfi&sektion=4&manpath=FreeBSD+8.3-RELEASE I do not have an environment to download the source and make my own installation disk. The 8.3 image on the ftp site is dated April 9, 2012 and the 9.0 is Jan 2012. Is there some place I can download an amd63 iso that was includes the mfi driver update done on May 18, 2012? Or perhaps that is not really the issue at all - any help that anyone can provide will be welcome! Thanks, Jean Jean Christofferson je...@relevantpower.com Relevant Power, Inc. www.relevanttools.com 415-472-8400 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Firefox 14.0.1 won't build under 8.3 on amd64
== John Levine wrote on Mon 13.Aug'12 at 5:41:52 - == > Oops, it's 14.0.1 I'm trying to build. 13.0.0.1 is what I have installed now. > > In article <20120813053621.24629.qm...@joyce.lan> you write: did you select the option to use optimised CFLAGS when you run make config in the port directory? I remember I had this problem on 8.2 earlier this year/last year and deselecting that option made it build. I don't know if that has been fixed/changed since I built that port and it was for an earlier version of firefox. I recall the same was true for Thunderbird at that time. You try that first? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Firefox 14.0.1 won't build under 8.3 on amd64
Oops, it's 14.0.1 I'm trying to build. 13.0.0.1 is what I have installed now. In article <20120813053621.24629.qm...@joyce.lan> you write: >I'm reasonably sure I have the png and sqlite3 libraries built as >needed, but the build still barfs when compiling the SSL function >nsNSSErrors.cpp. The end of the build log is copied below. > >I don't have the logs handy, but Thunderbird fails the same way. Any >suggestions? > >R's, >John > > >c++ -o nsNSSErrors.o -c -I../../../../dist/stl_wrappers >-I../../../../dist/system_wrappers >-include ../../../.././../config/gcc_hidden.h -DNSS_ENABLE_ECC >-DDLL_PREFIX=\"lib\" >-DDLL_SUFFIX=\".so\" -DMOZ_GLUE_IN_PROGRAM >-DXPCOM_TRANSLATE_NSGM_ENTRY_POINT=1 >-DMOZILLA_INTERNAL_API -D_IMPL_NS_COM -DEXPORT_XPT_API -DEXPORT_XPTC_API >-D_IMPL_NS_GFX >-D_IMPL_NS_WIDGET -DIMPL_XREAPI -DIMPL_NS_NET -DIMPL_THEBES >-DSTATIC_EXPORTABLE_JS_API >-DOSTYPE=\"FreeBSD8\" -DOSARCH=FreeBSD -I/usr/local/include/nss -I.. >+ /../../.././../security/manager/ssl/src -I. -I../../../../dist/include >-I../../../../dist/include/nsprpub -I/usr/local/include >-I/usr/local/include/nspr >-I/usr/local/include/nss -I/usr/local/include -I/usr/local/include-fPIC >-I/usr/local/include/nss -I/usr/local/include/nss/nss >-I/usr/local/include -fno-rtti -Wall >-Wpointer-arith -Woverloaded-virtual -Werror=return-type -Wno-ctor-dtor-privacy >-Wno-overlength-strings -Wno-invalid-offsetof -Wno-variadic-macros >-Wcast-align -O2 > -pipe -f > no-strict-aliasing -fno-exceptions -fno-strict-aliasing -fshort-wchar > -ffunction-sections >-fdata-sections -pipe -DNDEBUG -DTRIMMED -O2 -fomit-frame-pointer >-I/usr/local/include/nss >-I/usr/local/include/nss/nss -I/usr/local/include -DMOZILLA_CLIENT >-include >../../../../mozilla-config.h >/usr/ports/www/firefox/work/mozilla-release/security/manager/ssl/src/nsNSSErrors.cpp >/usr/ports/www/firefox/work/mozilla-release/security/manager/ssl/src/nsNSSComponent.cpp: > In >member function 'virtual nsresult nsCryptoHash::Finish(bool, >nsACString_internal&)': >/usr/ports/www/firefox/work/mozilla-release/security/manager/ssl/src/nsNSSComponent.cpp:2879: >error: 'BTOA_DataToAscii' was not declared in this scope >/usr/ports/www/firefox/work/mozilla-release/security/manager/ssl/src/nsNSSComponent.cpp: > In >member function 'virtual nsresult nsCryptoHMAC::Finish(bool, >nsACString_internal&)': >/usr/ports/www/firefox/work/mozilla-release/security/manager/ssl/src/nsNSSComponent.cpp:3070: >error: 'BTOA_DataToAscii' was not declared in this scope >gmake[5]: *** [nsNSSComponent.o] Error 1 >gmake[5]: *** Waiting for unfinished jobs >gmake[5]: Leaving directory >`/usr/ports/www/firefox/work/mozilla-release/obj-x86_64-portbld-freebsd8.3/security/manager/ssl/src' >gmake[4]: *** [libs] Error 2 >gmake[4]: Leaving directory >`/usr/ports/www/firefox/work/mozilla-release/obj-x86_64-portbld-freebsd8.3/security/manager/ssl' >gmake[3]: *** [libs] Error 2 >gmake[3]: Leaving directory >`/usr/ports/www/firefox/work/mozilla-release/obj-x86_64-portbld-freebsd8.3/security/manager' >gmake[2]: *** [libs_tier_platform] Error 2 >gmake[2]: Leaving directory >`/usr/ports/www/firefox/work/mozilla-release/obj-x86_64-portbld-freebsd8.3' >gmake[1]: *** [tier_platform] Error 2 >gmake[1]: Leaving directory >`/usr/ports/www/firefox/work/mozilla-release/obj-x86_64-portbld-freebsd8.3' >gmake: *** [default] Error 2 >*** Error code 1 > > > >___ >freebsd-questions@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-questions >To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Firefox 13.0.1.1 won't build under 8.3 on amd64
I'm reasonably sure I have the png and sqlite3 libraries built as needed, but the build still barfs when compiling the SSL function nsNSSErrors.cpp. The end of the build log is copied below. I don't have the logs handy, but Thunderbird fails the same way. Any suggestions? R's, John c++ -o nsNSSErrors.o -c -I../../../../dist/stl_wrappers -I../../../../dist/system_wrappers -include ../../../.././../config/gcc_hidden.h -DNSS_ENABLE_ECC -DDLL_PREFIX=\"lib\" -DDLL_SUFFIX=\".so\" -DMOZ_GLUE_IN_PROGRAM -DXPCOM_TRANSLATE_NSGM_ENTRY_POINT=1 -DMOZILLA_INTERNAL_API -D_IMPL_NS_COM -DEXPORT_XPT_API -DEXPORT_XPTC_API -D_IMPL_NS_GFX -D_IMPL_NS_WIDGET -DIMPL_XREAPI -DIMPL_NS_NET -DIMPL_THEBES -DSTATIC_EXPORTABLE_JS_API -DOSTYPE=\"FreeBSD8\" -DOSARCH=FreeBSD -I/usr/local/include/nss -I../../../.././../security/manager/ssl/src -I. -I../../../../dist/include -I../../../../dist/include/nsprpub -I/usr/local/include -I/usr/local/include/nspr -I/usr/local/include/nss -I/usr/local/include -I/usr/local/include-fPIC -I/usr/local/include/nss -I/usr/local/include/nss/nss -I/usr/local/include -fno-rtti -Wall -Wpointer-arith -Woverloaded-virtual -Werror=return-type -Wno-ctor-dtor-privacy -Wno-overlength-strings -Wno-invalid-offsetof -Wno-variadic-macros -Wcast-align -O2 -pipe -f no-strict-aliasing -fno-exceptions -fno-strict-aliasing -fshort-wchar -ffunction-sections -fdata-sections -pipe -DNDEBUG -DTRIMMED -O2 -fomit-frame-pointer -I/usr/local/include/nss -I/usr/local/include/nss/nss -I/usr/local/include -DMOZILLA_CLIENT -include ../../../../mozilla-config.h /usr/ports/www/firefox/work/mozilla-release/security/manager/ssl/src/nsNSSErrors.cpp /usr/ports/www/firefox/work/mozilla-release/security/manager/ssl/src/nsNSSComponent.cpp: In member function 'virtual nsresult nsCryptoHash::Finish(bool, nsACString_internal&)': /usr/ports/www/firefox/work/mozilla-release/security/manager/ssl/src/nsNSSComponent.cpp:2879: error: 'BTOA_DataToAscii' was not declared in this scope /usr/ports/www/firefox/work/mozilla-release/security/manager/ssl/src/nsNSSComponent.cpp: In member function 'virtual nsresult nsCryptoHMAC::Finish(bool, nsACString_internal&)': /usr/ports/www/firefox/work/mozilla-release/security/manager/ssl/src/nsNSSComponent.cpp:3070: error: 'BTOA_DataToAscii' was not declared in this scope gmake[5]: *** [nsNSSComponent.o] Error 1 gmake[5]: *** Waiting for unfinished jobs gmake[5]: Leaving directory `/usr/ports/www/firefox/work/mozilla-release/obj-x86_64-portbld-freebsd8.3/security/manager/ssl/src' gmake[4]: *** [libs] Error 2 gmake[4]: Leaving directory `/usr/ports/www/firefox/work/mozilla-release/obj-x86_64-portbld-freebsd8.3/security/manager/ssl' gmake[3]: *** [libs] Error 2 gmake[3]: Leaving directory `/usr/ports/www/firefox/work/mozilla-release/obj-x86_64-portbld-freebsd8.3/security/manager' gmake[2]: *** [libs_tier_platform] Error 2 gmake[2]: Leaving directory `/usr/ports/www/firefox/work/mozilla-release/obj-x86_64-portbld-freebsd8.3' gmake[1]: *** [tier_platform] Error 2 gmake[1]: Leaving directory `/usr/ports/www/firefox/work/mozilla-release/obj-x86_64-portbld-freebsd8.3' gmake: *** [default] Error 2 *** Error code 1 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: bsdinstall to jail aborted (9.0-RELEASE-p3, amd64)
Hi Darren, On Sun, 29 Jul 2012 04:57:43 +0400 Darren Baginski wrote: > No, feel free to open if you feel it needed. > I would say it's more a feature request, but without it, bsdinstall not > usable on non release environments. thanks, I submitted the PR here: http://www.freebsd.org/cgi/query-pr.cgi?pr=170264 Kind regards, Matthias -- Matthias Petermann ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: bsdinstall to jail aborted (9.0-RELEASE-p3, amd64)
29.07.2012, 00:29, "Matthias Petermann" : > Hi Darren, > > thanks for diving into the issue. I looked through the mentioned places in > the bsdinstall code and understand it now. > > On Sat, 28 Jul 2012 17:24:48 +0400 > Darren Baginski wrote: > >> I thing release/arch selection has to be a part of the installer, either >> directly or via environment variables. > > Yes, I think so too. I guess there usually no FTP directories created for > patch level releases like 9.0-RELEASE-p3? Your proposal to introduce a new > environment variable like TARGET makes sense. This could work like an > override - when it is not set it can fall back to the default (using uname -r > which makes sense for the installation media). > > Should I file a PR or did you already? No, feel free to open if you feel it needed. I would say it's more a feature request, but without it, bsdinstall not usable on non release environments. > > Thanks, > Matthias > > -- > Matthias Petermann ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: bsdinstall to jail aborted (9.0-RELEASE-p3, amd64)
Hi Darren, thanks for diving into the issue. I looked through the mentioned places in the bsdinstall code and understand it now. On Sat, 28 Jul 2012 17:24:48 +0400 Darren Baginski wrote: > I thing release/arch selection has to be a part of the installer, either > directly or via environment variables. Yes, I think so too. I guess there usually no FTP directories created for patch level releases like 9.0-RELEASE-p3? Your proposal to introduce a new environment variable like TARGET makes sense. This could work like an override - when it is not set it can fall back to the default (using uname -r which makes sense for the installation media). Should I file a PR or did you already? Thanks, Matthias -- Matthias Petermann ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: bsdinstall to jail aborted (9.0-RELEASE-p3, amd64)
28.07.2012, 17:13, "Darren Baginski" : > 28.07.2012, 13:46, "Matthias Petermann" : > >> Hello, >> >> currently I experienced an unexpected behavior of the FreeBSD bsdinstall >> installer. Some weeks ago I could use it sucessfully to create a jail >> environment with >> >> # bsdinstall jail /jails/myjail >> >> Today I tried to repeat this on another system(2) and it fails after the >> selection of the to-be-used mirror. Also re-trying it on the original >> system(1) leads to an error but a different one. Since then I upgraded from >> 9.0-RELEASE to 9.0-RELEASE-p3 using freebsd-update. >> >> Here are the symptoms: >> >> (2) FreeBSD 9.0-RELEASE-p3 amd64: After typing "bsdinstall..." it brings me >> directly to the mirror selection list, but after selecting a mirror it >> aborts with an error message "An installation step has beeen aborted. Would >> you like to restart the installer or exit the installer?" >> >> (1) FreeBSD 9.0-RELEASE-p3 i386: After typing "bsdinstall..." it brings me >> to the distribution select dialog. After selection of the distribution set, >> it shows the mirror selection dialog. After selecting a mirror it aborts >> with a fetch error "Error while fetching /base.txz: Invalid URL scheme" >> >> I tried different mirrors, too. And they all seem to be basically online - >> pointing an FTP client to them showed no errors. >> >> So what am I doing wrong? Does bsdinstall maintain some hidden >> configuration file which may influence its behavior? The environment >> variables mentioned in bsdinstall(8) are not set on both systems. Or is >> there a known issue with 9.0-RELEASE-p3 which appears different on amd64 and >> i386 systems? >> >> It would be great if anyone could validate this. > > I did a quick test on 9.1-PRERELEASE, ant bsdinstall trying to fetch > 9.1-PRERELEASE files, which it surely can't find. > There must be an option like 'TARGET' to specify exact version to fetch like > it's the case for Debian debootsrap. > What I did next is: #diff -u mirrorselect.orig mirrorselect --- mirrorselect.orig 2012-07-28 12:55:33.0 + +++ mirrorselect2012-07-28 12:58:49.0 + @@ -192,7 +192,7 @@ MIRROR_BUTTON=$? exec 3>&- -BSDINSTALL_DISTSITE="$MIRROR/pub/FreeBSD/releases/`uname -m`/`uname -p`/`uname -r`" +BSDINSTALL_DISTSITE="$MIRROR/pub/FreeBSD/releases/`uname -m`/`uname -p`/$TARGET" case $MIRROR_BUTTON in $DIALOG_CANCEL) and then: #export TARGET=9.0-RELEASE and again #bsdinstall jail /tmp/tstenv Got a working environment after that. I thing release/arch selection has to be a part of the installer, either directly or via environment variables. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: bsdinstall to jail aborted (9.0-RELEASE-p3, amd64)
28.07.2012, 13:46, "Matthias Petermann" : > Hello, > > currently I experienced an unexpected behavior of the FreeBSD bsdinstall > installer. Some weeks ago I could use it sucessfully to create a jail > environment with > > # bsdinstall jail /jails/myjail > > Today I tried to repeat this on another system(2) and it fails after the > selection of the to-be-used mirror. Also re-trying it on the original > system(1) leads to an error but a different one. Since then I upgraded from > 9.0-RELEASE to 9.0-RELEASE-p3 using freebsd-update. > > Here are the symptoms: > > (2) FreeBSD 9.0-RELEASE-p3 amd64: After typing "bsdinstall..." it brings me > directly to the mirror selection list, but after selecting a mirror it aborts > with an error message "An installation step has beeen aborted. Would you like > to restart the installer or exit the installer?" > > (1) FreeBSD 9.0-RELEASE-p3 i386: After typing "bsdinstall..." it brings me to > the distribution select dialog. After selection of the distribution set, it > shows the mirror selection dialog. After selecting a mirror it aborts with a > fetch error "Error while fetching /base.txz: Invalid URL scheme" > > I tried different mirrors, too. And they all seem to be basically online - > pointing an FTP client to them showed no errors. > > So what am I doing wrong? Does bsdinstall maintain some hidden configuration > file which may influence its behavior? The environment variables mentioned in > bsdinstall(8) are not set on both systems. Or is there a known issue with > 9.0-RELEASE-p3 which appears different on amd64 and i386 systems? > > It would be great if anyone could validate this. I did a quick test on 9.1-PRERELEASE, ant bsdinstall trying to fetch 9.1-PRERELEASE files, which it surely can't find. There must be an option like 'TARGET' to specify exact version to fetch like it's the case for Debian debootsrap. > > Kind regards, > Matthias > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
bsdinstall to jail aborted (9.0-RELEASE-p3, amd64)
Hello, currently I experienced an unexpected behavior of the FreeBSD bsdinstall installer. Some weeks ago I could use it sucessfully to create a jail environment with # bsdinstall jail /jails/myjail Today I tried to repeat this on another system(2) and it fails after the selection of the to-be-used mirror. Also re-trying it on the original system(1) leads to an error but a different one. Since then I upgraded from 9.0-RELEASE to 9.0-RELEASE-p3 using freebsd-update. Here are the symptoms: (2) FreeBSD 9.0-RELEASE-p3 amd64: After typing "bsdinstall..." it brings me directly to the mirror selection list, but after selecting a mirror it aborts with an error message "An installation step has beeen aborted. Would you like to restart the installer or exit the installer?" (1) FreeBSD 9.0-RELEASE-p3 i386: After typing "bsdinstall..." it brings me to the distribution select dialog. After selection of the distribution set, it shows the mirror selection dialog. After selecting a mirror it aborts with a fetch error "Error while fetching /base.txz: Invalid URL scheme" I tried different mirrors, too. And they all seem to be basically online - pointing an FTP client to them showed no errors. So what am I doing wrong? Does bsdinstall maintain some hidden configuration file which may influence its behavior? The environment variables mentioned in bsdinstall(8) are not set on both systems. Or is there a known issue with 9.0-RELEASE-p3 which appears different on amd64 and i386 systems? It would be great if anyone could validate this. Kind regards, Matthias -- Matthias Petermann ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: amd64, 57600 serial install help
On 21/07/2012 22:06, Ihsan Junaidi Ibrahim wrote: I assume you have compiled the bootblocks as per the instruction in the handbook. Second, do you have more than one serial port on the box because FreeBSD can only work its serial console magic on only one port at a time. If you redirect your IPMI serial console or just a normal serial console, take note it's interrupt number in the BIOS. You'll need to append the 0x10 flags to your UART device in device.hints file if the you plug in the cable at a non-default port. i have submitted a PR re this as a serial install on 8.3 works fine. Paul. -- - Paul Macdonald IFDNRG Ltd Web and video hosting - t: 0131 5548070 m: 07970339546 e: p...@ifdnrg.com w: http://www.ifdnrg.com - IFDNRG 40 Maritime Street Edinburgh EH6 6SA - ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: amd64, 57600 serial install help
I assume you have compiled the bootblocks as per the instruction in the handbook. Second, do you have more than one serial port on the box because FreeBSD can only work its serial console magic on only one port at a time. If you redirect your IPMI serial console or just a normal serial console, take note it's interrupt number in the BIOS. You'll need to append the 0x10 flags to your UART device in device.hints file if the you plug in the cable at a non-default port. ihsan On Jul 22, 2012, at 1:47 AM, Paul Macdonald wrote: > > what am i doing wrong here? > > From rebuilding the install iso and from the handbook instructions here: > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install-advanced.html > which suggests that in /boot/loader.conf only > > console="comconsole" > > is required, > > i have tried this and also explicity setting speed in boot/loader.conf > > console="comconsole" > comconsole_speed="57600" > > i have also tried having the settings i use to access via serial post install > ie: > > /etc/ttys:ttyu0 "/usr/libexec/getty std.57600" vt100 on secure > and /boot/config: -D > > but same result, install stops ( or goes elsewhere at point below) > > It does boot stage 1 and stage 2 then i get nothing? > > test serial output: > - > CD Loader 1.2 > r Configuration Menu ... > Building the boot loader arguments > Looking up /BOOT/LOADER... Found > Relocating the loader and the BTX > Starting the BTX loader > > BTX loader 1.00 BTX version is 1.02 > Consoles: internal video/keyboard > BIOS CD is cd0 in 5 sec.. > BIOS drive A: is disk0 > BIOS drive C: is disk1 > BIOS 640kB/3668736kB available memory > > FreeBSD/x86 bootstrap loader, Revision 1.1 > (r...@farrell.cse.buffalo.edu, Tue Jan 3 06:51:49 UTC 2012) > > > > (nothing after this point) > > > -- > > - > Paul Macdonald > IFDNRG Ltd > Web and video hosting > - > t: 0131 5548070 > m: 07970339546 > e: p...@ifdnrg.com > w: http://www.ifdnrg.com > - > IFDNRG > 40 Maritime Street > Edinburgh > EH6 6SA > - > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"