GPT boot blocks, booting and booteasy
Running FreeBSD 8-Stable of July 30 and I am trying to figure out a bit about how GPT works. I am unsure of what I can do with boot blocks. 0011223344556677 Here is what I've done so far. I have just created my first GPT structured FreeBSD system and it's all working fine, but I don't have any ability to select booting from another partition or drive. I boot the system and FreeBSD just boots with no option to boot from another disk. I have /boot/pmbr loaded into the PMBR and gptboot into the freebsd-boot partition. I'll admit that I did this by rote and don't understand how these two files interact with the UEFI BIOS to get the loader started. I'm not really certain that I even need both. Is it possible to build a "custom" booteasy boot system with boot0cfg or some other tool so I can select d ifferent bootable partition or my other disk which is sliced in the traditional fashion? Can anyone point me to any information on how the boot process works with GPT? Thanks! -- R. Kevin Oberman, Network Engineer - Retired E-mail: kob6...@gmail.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Fwd: Again, snd_hda headphones problem
Hi, Sorry about to post this on two freebsd- mailing lists. This problem makes me unable to use external headphones/speakers, which is a very serious problem. I pasted a full verbose boot log here: http://lists.freebsd.org/pipermail/freebsd-multimedia/2011-August/012389.html -- Forwarded message -- From: Zhihao Yuan Date: Wed, Aug 3, 2011 at 1:43 PM Subject: Again, snd_hda headphones problem To: freebsd-multime...@freebsd.org Hi, I posted this message on FreeBSD forum, but got no response. So I'm seeking some help here. I bought a laptop, HP Elitebook 8540w. ~> uname -a FreeBSD compaq.yuetime 8.2-STABLE FreeBSD 8.2-STABLE #4 r224501: Fri Jul 29 22:28:38 CDT 2011 lichray@compaq.yuetime:/usr/obj/home/lichray/devel/freebsd-stable/sys/HOUKAGO amd64 I have already set up the default_unit: ~> cat /dev/sndstat FreeBSD Audio Driver (newpcm: 64bit 2009061500/amd64) Installed devices: pcm0: (play) pcm1: (play) pcm2: (play) pcm3: (play) pcm4: (play/rec) default pcm5: (play) pindump: hdac1: Dumping AFG cad=0 nid=1 pins: hdac1: nid 10 0x2121101f as 1 seq 15 Headphones Jack jack 1 loc 33 color Black misc 0 hdac1: Caps: OUT HP Sense: 0x hdac1: nid 11 0x03a1102e as 2 seq 14 Mic Jack jack 1 loc 3 color Black misc 0 hdac1: Caps: IN VREF Sense: 0x hdac1: nid 12 0x90a70120 as 2 seq 0 Mic Fixed jack 7 loc 16 color Unknown misc 1 hdac1: Caps: IN VREF Sense: 0x hdac1: nid 13 0x90170110 as 1 seq 0 Speaker Fixed jack 7 loc 16 color Unknown misc 1 hdac1: Caps: OUT Sense: 0x hdac1: nid 14 0x21811040 as 4 seq 0 Line-in Jack jack 1 loc 33 color Black misc 0 [DISABLED] hdac1: Caps: IN VREF Sense: 0x hdac1: nid 15 0x03211030 as 3 seq 0 Headphones Jack jack 1 loc 3 color Black misc 0 hdac1: Caps: OUT Sense: 0x hdac1: nid 20 0x40f000f0 as 15 seq 0 Other None jack 0 loc 0 color Unknown misc 0 [DISABLED] hdac1: Caps: IN OUT hdac1: nid 24 0x40f000f0 as 15 seq 0 Other None jack 0 loc 0 color Unknown misc 0 [DISABLED] hdac1: Caps: IN hdac1: nid 25 0x40f000f0 as 15 seq 0 Other None jack 0 loc 0 color Unknown misc 0 [DISABLED] hdac1: Caps: IN hdac1: nid 30 0x40f000f0 as 15 seq 0 Other None jack 0 loc 0 color Unknown misc 0 [DISABLED] hdac1: Caps: OUT hdac1: nid 31 0x40f000f0 as 15 seq 0 Other None jack 0 loc 0 color Unknown misc 0 [DISABLED] hdac1: Caps: OUT EAPD hdac1: nid 32 0x40f000f0 as 15 seq 0 Other None jack 0 loc 0 color Unknown misc 0 [DISABLED] hdac1: Caps: OUT hdac1: NumGPIO=8 NumGPO=0 NumGPI=0 GPIWake=1 GPIUnsol=1 hdac1: GPIO: data=0x enable=0x direction=0x hdac1: wake=0x unsol=0x sticky=0x And the sound comes from the internal speaker, and the internal record works. But the sound does not work on the headphones. I read many posts and the snd_hda(4), and I know I need to bind the headphones and the internal speaker to the same as, and I need to do the same on output. But I don't know which device is which, and I just don't know how to deal with the seq. Please help me if you are pro on this. -- Zhihao Yuan, nickname lichray The best way to predict the future is to invent it. ___ 4BSD -- http://4bsd.biz/ -- Zhihao Yuan, nickname lichray The best way to predict the future is to invent it. ___ 4BSD -- http://4bsd.biz/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: "log_sysevent: type 19 is not implemented" messages during boot
On Fri, Jun 17, 2011 at 5:28 PM, Olivier Smedts wrote: > 2011/6/17 Rolf Nielsen : >> 2011-06-17 16:29, Artem Belevich skrev: >> <...> Are you sure that it's harmless? It appeared for me as an evidence of pool breakage. I had these messages when I ran any zpool command on broken pool. I do't havesingle one after pool is fixed. Here's my thread on freebsd-fs : http://lists.freebsd.org/pipermail/freebsd-fs/2011-June/011639.html >>> >>> Indeed. Same story here. Last week I've got my pool corrupted due to a >>> bad memory stick. Then I've got tons of thse "log_sysevent: type >>> 19..." messages. After re-importing the pool with -F the messages went >>> away. So, from where I stand, those messages do seem to correlate with >>> a problem and should not be hushed by default. > > On mine, it pops up at boot on the console if the cache device is > inaccessible (usb key). No real problem on the pool, but an > information with more meaning would be useful. On one of my test systems, I have a zpool consisting of 3 HDDs in external enclosures attached via eSATA ports. If the enclosures are not powered (i.e. the disks are off), and the system boots, then this message appears. Of course, the zpool isn't available then, not being available physically. OTOH, when the enclosures are on, and the system boots, this message doesn't show up, and the zpool is available and healthy alright. This message appeared since ZFSv28, and on this system and in this specific scenario, it is absolutely harmless. >> /Rolf > > Olivier Smedts _ -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 32GB limit per swap device?
On Tue, Aug 09, 2011 at 05:26:46PM +0300, Daniel Kalchev wrote: > I am trying to set up 64GB partitions for swap for a system that has > 64GB of RAM (with the idea to dump kernel core etc). But, on 8-stable as > of today I get: > > WARNING: reducing size to maximum of 67108864 blocks per swap unit > > Is there workaround for this limitation? While FreeBSD cannot address more than 32GB per swap space, it permits as many as 32 swap spaces to be active concurrently. (Sorry; I'm not finding the reference for this just now.) Peace, david -- David H. Wolfskill da...@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpww64jPfUn6.pgp Description: PGP signature
Re: 32GB limit per swap device?
On Aug 9, 2011, at 7:26 AM, Daniel Kalchev wrote: > I am trying to set up 64GB partitions for swap for a system that has 64GB of > RAM (with the idea to dump kernel core etc). But, on 8-stable as of today I > get: > > WARNING: reducing size to maximum of 67108864 blocks per swap unit > > Is there workaround for this limitation? Apparently, the 32GB swapspace limit is per swap area; you can add up to 4 swap areas so create two or three 32GB swap partitions. Regards, -- -Chuck PS: Older thread with some specific details: Begin forwarded message: > From: Matthew Dillon > Date: August 5, 2008 11:29:21 AM PDT > To: Max Laier > Cc: freebsd-stable@freebsd.org, Lin Jui-Nan Eric > Subject: Re: Max size of one swap slice > > :> Recently we found that we can only allocate 32GB for one swap slice. > :> Does there is any sysctl oid or any kernel option to increase it? Why > :> we have this restriction? > : > :this is a consequence of the data structure used to manage swap space. See > :sys/blist.h for details. It *seems* that you *might* be able to increase > the > :coverage by decreasing BLIST_META_RADIX, but that's from a quick glance and > :most certainly not a good idea. > : > :However, the blist is a abstract enough API so that you can likely replace > it > :with something that supports 64bit addresses (and thus 512*2^64 bytes of > swap > :space per device) ... but I don't see why you'd want to do something like > :this. Remember that you need memory to manage your swap space as well! > : > :-- > :/"\ Best regards, | mla...@freebsd.org > :\ / Max Laier | ICQ #67774661 > >The core structures can handle 2 billion swap pages == 2TB of swap, >but the blist code hits arithmatic overflows if a single blist has >more then (0x4000 / BLIST_META_RADIX) = 1G/16 = 64M swap blocks, >or 256GB. > >I think the VM/BIO system had additional overflow issues due to >conversions back and forth between PAGE_SIZE and DEV_BSIZE which >further restricted the limit to 32GB. Those restrictions may be gone >now that FreeBSD is using 64 bit block numbers, so you may be able to >pop it up to 256GB with virtually no effort (but you need to test it >significantly!). > >With some work on the blist code only (not its structures) the arithmatic >overflow issues could also be resolved, increasing the swap capability >to 2TB. > >I do not recommend changing any of the core blist structure, particularly >not BLIST_META_RADIX. Just don't try :-). You do NOT want to bump >the swap block number fields to 64 bits. > >Also note that significant memory is used to manage that much swap. It's >a factor of 1:16384 or so for the blist structures and probably about >the same amount for the vm_object tracking structures. 32G of swap needs >around 2-4MB of wired ram. > > -Matt > Matthew Dillon > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
32GB limit per swap device?
I am trying to set up 64GB partitions for swap for a system that has 64GB of RAM (with the idea to dump kernel core etc). But, on 8-stable as of today I get: WARNING: reducing size to maximum of 67108864 blocks per swap unit Is there workaround for this limitation? Daniel ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: zpool doesn't upgrade - Re: ZFS directory with a large number of files
On Tue, 09 Aug 2011 10:38:01 +0200, seanr...@gmail.com wrote: On Tue, Aug 2, 2011 at 8:59 PM, Ronald Klop wrote: On Tue, 02 Aug 2011 12:55:43 +0200, seanr...@gmail.com wrote: I think this zpool upgrade thing is weird. Can you try 'zpool upgrade -a'? Mine says: zpool get version zroot NAME PROPERTY VALUESOURCE zroot version 28 default Mind the SOURCE=default vs. SOURCE=local. Is it possible you did 'zpool set version=15 tank' in the past? You can check that with 'zpool history'. NB: if you upgrade the boot pool, don't forget to upgrade to boot loader. (See UPDATING) % sudo zpool upgrade -a Password: This system is currently running ZFS pool version 15. All pools are formatted using this version. I checked zpool history and I never set the version explicitly. My 'world' is from the 8th of March; it's possible my tree is sufficiently old (my kernel was built on the 12th of June; I'm fairly sure its from the same tree as the world, but it's also possible my kernel and userland have been out of sync for 2 months). I'll upgrade this machine sometime soon and see if that fixes the issue. Sean You can set the property to 28 and upgrade after that. zpool set version=28 zroot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS directory with a large number of files
On 8/2/11 9:39 AM, seanr...@gmail.com wrote: > Hi there, > > I Googled around and checked the PRs and wasn't successful in finding > any reports of what I'm seeing. I'm hoping someone here can help me > debug what's going on. > > On my FreeBSD 8.2-S machine (built circa 12th June), I created a > directory and populated it over the course of 3 weeks with about 2 > million individual files. As you might imagine, a 'ls' of this > directory took quite some time. > > The files were conveniently named with a timestamp in the filename > (still images from a security camera, once per second) so I've since > moved them all to timestamped directories (/MM/dd/hh/mm). What I > found though was the original directory the images were in is still > very slow to ls -- and it only has 1 file in it, another directory. > While not addressing your original question, which many people have already, I'll toss in the following: I do hope you've disabled access times on your ZFS dataset ? zfs set atime=off YOUR_DATASET/supercamera/captures ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: zpool doesn't upgrade - Re: ZFS directory with a large number of files
On Tue, Aug 2, 2011 at 8:59 PM, Ronald Klop wrote: > On Tue, 02 Aug 2011 12:55:43 +0200, seanr...@gmail.com > wrote: > I think this zpool upgrade thing is weird. Can you try 'zpool upgrade -a'? > > Mine says: > zpool get version zroot > NAME PROPERTY VALUE SOURCE > zroot version 28 default > > Mind the SOURCE=default vs. SOURCE=local. > Is it possible you did 'zpool set version=15 tank' in the past? You can > check that with 'zpool history'. > > NB: if you upgrade the boot pool, don't forget to upgrade to boot loader. > (See UPDATING) % sudo zpool upgrade -a Password: This system is currently running ZFS pool version 15. All pools are formatted using this version. I checked zpool history and I never set the version explicitly. My 'world' is from the 8th of March; it's possible my tree is sufficiently old (my kernel was built on the 12th of June; I'm fairly sure its from the same tree as the world, but it's also possible my kernel and userland have been out of sync for 2 months). I'll upgrade this machine sometime soon and see if that fixes the issue. Sean ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
