binary upgrade problems (8.1-RELEASE-p5 - 8.2-RELEASE-p3)
I'm having some problems after doing a: freebsd-update -r 8.2-RELEASE upgrade (I had also done an upgrade from 8.1-p5 to p6 without rebooting; not sure if that's part of the problem). I did the update, merged the config files, ran freebsd-update install, rebooted, and then ran freebsd-update install; despite /boot/kernel and /boot/kernel.old both having a recently updated kernel, one which has FreeBSD 8.2-RELEASE-p3 #0: Tue Sep 27 18:45:57 UTC 2011 if I run strings on it, uname and sysctl report 8.1-RELEASE-p5 FreeBSD 8.1-RELEASE-p5 #0: Tue Sep 27 16:49:00 UTC 2011 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 As you can see, I'm just running the generic kernel. The system boots and most services run, though ipfw isn't loading because of the kernel version mismatch. Trying to either rollback or re-upgrade using freebsd-update isn't working (the update list it builds is wrong -- specifically, the fetch_make_patchlist() function isn't working right and is missing the filenames, so it wants to delete all my files). Any thoughts on the simplest way to get everything synced up and happy again without doing a binary upgrade from sysinstall? kernel and kernel.old are currently the same thing; I did try doing a nextboot -k kernel.old, but that doesn't change anything. If it matters, my first reboot after the upgrade was to single user mode (to do a fsck) rather than standard - wondering if this prevented some automatic thing that happens on the first boot after the binary upgrade from running It has been rebooted normally several times since then, though. I've tried moving /var/db/freebsd-update out of the way and re-creating it, but that didn't help (I've since moved the old one back). w ___ 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: binary upgrade problems (8.1-RELEASE-p5 - 8.2-RELEASE-p3)
Sorry for the self-follow-up, but I did eventually fix it - I thought I had tried this already, but the machine seems to have been booting from the inactive component of a gmirror array; doing a gmirror forget gm0 and a reboot fixed the problem. w ___ 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
gmirror resync seems stalled
I had a drive which had some timeout problems, and got kicked out of a gmirror based RAID1 on my FreeBSD machine (now 8.2-RELEASE-p3). Normally, if the devices get out of sync, they rebuild relatively quickly, and I can watch the progress. This time, after running gmirror forget and inserting the device, it just seems to sit at '0%', despite the fact that it's supposedly synchronizing. I've tried removing and re-adding it a couple times, but the behavior is the same. Am I just being too impatient? Autosynchronization of stale components should have already been enabled (and the gmirror list output says 'synchronizing'), but I tried a gmirror configure -a gm0 just in case. Also, any opinions on how safe the '-F' option (Do not synchronize after a power failure or system crash) is? Following: # gmirror remove gm0 ad6 # gmirror forget gm0 ad6 # gmirror insert gm0 ad6 I see: # gmirror list Geom name: gm0 State: DEGRADED Components: 2 Balance: round-robin Slice: 4096 Flags: NONE GenID: 4 SyncID: 1 ID: 506994055 Providers: 1. Name: mirror/gm0 Mediasize: 1000204885504 (932G) Sectorsize: 512 Mode: r6w5e14 Consumers: 1. Name: ad10 Mediasize: 1000204886016 (932G) Sectorsize: 512 Mode: r1w1e1 State: ACTIVE Priority: 0 Flags: DIRTY GenID: 4 SyncID: 1 ID: 3348119132 2. Name: ad6 Mediasize: 1000204886016 (932G) Sectorsize: 512 Mode: r1w1e1 State: SYNCHRONIZING Priority: 0 Flags: DIRTY, SYNCHRONIZING GenID: 4 SyncID: 1 Synchronized: 0% ID: 3439333064 and the status seems to just stay at 0% relevant atacontrol output: ATA channel 3: Master: ad6 WDC WD10EVDS-63U8B0/01.00A01 SATA revision 2.x Slave: no device present ATA channel 5: Master: ad10 WDC WD10EVDS-63U8B0/01.00A01 SATA revision 2.x Slave: no device present ___ 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
Canon A70 w/ FreeBSD
Has anyone had luck using the Canon PowerShot A70 with FreeBSD stable (4.x)? I notice in the home page for the s10sh drivers (see links below) that this model may not be supported. The FreeBSD maintainer has made some changes, and according to the changelog at: http://www.reynoldsnet.org/s10sh/, the A60 is now supported. However, it's unclear whether it's supported in serial only mode, like the A50, and whether there are problems, as with the A50 (see http://www.kyuzz.org/antirez/s10sh.html) Would i be better off with the SD100 model? I'd rather use the A70 if possible. A70 site: http://www.powershot.com/powershot2/a70-60/specs.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Canon A70 w/ FreeBSD
JacobRhoden wrote: On Mon, 8 Dec 2003 09:27 am, Will Yardley wrote: Has anyone had luck using the Canon PowerShot A70 with FreeBSD stable (4.x)? I notice in the home page for the s10sh drivers (see links below) that this model may not be supported. Just buy yourself a compact-flash card reader. All you do is put your card in and plug it into the usb port, and your able to mount it like a hard disk. (: I find this method much simpler and more convenient. That might be a good option. Otherwise you might want to checkout the gphoto port. Yeah - I've checked that out (and installed it from ports), and it does look like it supports that model. Is the other driver still needed, or will this Just Work (TM), assuming that the usb and umass options are compiled into the kernel? I haven't ever used USB with FreeBSD, so I don't have a lot of experience with dealing with USB in general. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pkgdb / portupgrade segfault
Chris wrote: On Tuesday 11 November 2003 01:08 pm, Will Yardley wrote: I have portupgrade version 20030723, installed from ports. I'm having some problems with it. Running pkgdb -Fv gives a segfault. aura# pkgdb -Fv Try this: pkgdb -fuF That seems to work - thanks. Presumably a corrupt pkgdb or something? Would be nice if portupgrade gave nicer errors, though. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: onboard sound card problems
On Mon, Nov 10, 2003 at 04:28:22PM -0500, fbsd_user wrote: [ I wrote (TOFU reversed) ]: I have been having some problems since upgrading to 4.9 - earlier I had problems with the onboard sound card, so I switched to a PCI card which worked a lot better. Since the upgrade, FreeBSD makes the onboard card /dev/dsp0 and the PCI card /dev/dsp1. Disable the onboard sound in the pc bios setup config. Actually, it's already disabled (I just checked). It was disabled from the last time I had this problem. However, since the upgrade from 4.8 to 4.9, FreeBSD seems to recognize it anyway. I haven't changed any of the BIOS settings. The actual setting is something like: AC97 onboard sound controller: [Disabled] -- Since when is skepticism un-American? Dissent's not treason but they talk like it's the same... (Sleater-Kinney - Combat Rock) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
pkgdb / portupgrade segfault
I have portupgrade version 20030723, installed from ports. I'm having some problems with it. Running pkgdb -Fv gives a segfault. aura# pkgdb -Fv --- Checking the package registry database [Updating the pkgdb format:bdb1_btree in /var/db/pkg ... - 282 packages found (-22 +71) (...)/usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:469: [BUG] Segmentation fault ruby 1.6.8 (2003-10-15) [i386-freebsd4] zsh: abort (core dumped) pkgdb -Fv Stack backtrace: aura# gdb `which ruby` ruby.core This GDB was configured as i386-unknown-freebsd...(no debugging symbols found)... Core was generated by `ruby'. Program terminated with signal 6, Abort trap. Reading symbols from /usr/local/lib/libruby.so.16...(no debugging symbols found)...done. Reading symbols from /usr/lib/libcrypt.so.2...(no debugging symbols found)...done. Reading symbols from /usr/lib/libm.so.2...(no debugging symbols found)...done. Reading symbols from /usr/lib/libc.so.4...(no debugging symbols found)...done. Reading symbols from /usr/local/lib/ruby/site_ruby/1.6/i386-freebsd4/features/ruby18/file_ruby18.so... (no debugging symbols found)...done. Reading symbols from /usr/local/lib/ruby/site_ruby/1.6/i386-freebsd4/dl.so...(no debugging symbols found)...done. Reading symbols from /usr/local/lib/ruby/site_ruby/1.6/i386-freebsd4/bdb1.so...(no debugging symbols found)...done. Reading symbols from /usr/libexec/ld-elf.so.1...(no debugging symbols found)...done. #0 0x28177fc0 in kill () from /usr/lib/libc.so.4 (gdb) bt #0 0x28177fc0 in kill () from /usr/lib/libc.so.4 #1 0x281b9876 in abort () from /usr/lib/libc.so.4 #2 0x2807d42e in rb_bug () from /usr/local/lib/libruby.so.16 #3 0x280d7a76 in sigsegv () from /usr/local/lib/libruby.so.16 #4 0xbfbfffac in ?? () #5 0x281b0d6b in __bt_ret () from /usr/lib/libc.so.4 #6 0x281b041b in __bt_seq () from /usr/lib/libc.so.4 #7 0x281f3d48 in bdb1_each_common () from /usr/local/lib/ruby/site_ruby/1.6/i386-freebsd4/bdb1.so #8 0x281f3da8 in bdb1_each_pair () from /usr/local/lib/ruby/site_ruby/1.6/i386-freebsd4/bdb1.so #9 0x2808893d in call_cfunc () from /usr/local/lib/libruby.so.16 #10 0x28088ea1 in rb_call0 () from /usr/local/lib/libruby.so.16 #11 0x280896fe in rb_call () from /usr/local/lib/libruby.so.16 #12 0x28089969 in rb_funcall () from /usr/local/lib/libruby.so.16 #13 0x2807c7c9 in rb_each () from /usr/local/lib/libruby.so.16 #14 0x28087a33 in rb_iterate () from /usr/local/lib/libruby.so.16 #15 0x2807ca57 in enum_find_all () from /usr/local/lib/libruby.so.16 #16 0x2808893d in call_cfunc () from /usr/local/lib/libruby.so.16 #17 0x28088ea1 in rb_call0 () from /usr/local/lib/libruby.so.16 #18 0x280896fe in rb_call () from /usr/local/lib/libruby.so.16 #19 0x28083fd4 in rb_eval () from /usr/local/lib/libruby.so.16 #20 0x28082efe in rb_eval () from /usr/local/lib/libruby.so.16 #21 0x28083b15 in rb_eval () from /usr/local/lib/libruby.so.16 #22 0x28082efe in rb_eval () from /usr/local/lib/libruby.so.16 #23 0x2808249e in rb_eval () from /usr/local/lib/libruby.so.16 #24 0x2808249e in rb_eval () from /usr/local/lib/libruby.so.16 #25 0x28083414 in rb_eval () from /usr/local/lib/libruby.so.16 #26 0x28083682 in rb_eval () from /usr/local/lib/libruby.so.16 #27 0x280892d3 in rb_call0 () from /usr/local/lib/libruby.so.16 #28 0x280896fe in rb_call () from /usr/local/lib/libruby.so.16 #29 0x28083fd4 in rb_eval () from /usr/local/lib/libruby.so.16 #30 0x2808249e in rb_eval () from /usr/local/lib/libruby.so.16 #31 0x280892d3 in rb_call0 () from /usr/local/lib/libruby.so.16 #32 0x280896fe in rb_call () from /usr/local/lib/libruby.so.16 #33 0x28083fd4 in rb_eval () from /usr/local/lib/libruby.so.16 #34 0x2808249e in rb_eval () from /usr/local/lib/libruby.so.16 #35 0x280892d3 in rb_call0 () from /usr/local/lib/libruby.so.16 #36 0x280896fe in rb_call () from /usr/local/lib/libruby.so.16 #37 0x28083fd4 in rb_eval () from /usr/local/lib/libruby.so.16 #38 0x28084a62 in rb_eval () from /usr/local/lib/libruby.so.16 #39 0x2808249e in rb_eval () from /usr/local/lib/libruby.so.16 #40 0x280892d3 in rb_call0 () from /usr/local/lib/libruby.so.16 #41 0x280896fe in rb_call () from /usr/local/lib/libruby.so.16 #42 0x28083fd4 in rb_eval () from /usr/local/lib/libruby.so.16 #43 0x2808249e in rb_eval () from /usr/local/lib/libruby.so.16 #44 0x280892d3 in rb_call0 () from /usr/local/lib/libruby.so.16 #45 0x280896fe in rb_call () from /usr/local/lib/libruby.so.16 #46 0x28083fd4 in rb_eval () from /usr/local/lib/libruby.so.16 #47 0x2808249e in rb_eval () from /usr/local/lib/libruby.so.16 #48 0x28083414 in rb_eval () from /usr/local/lib/libruby.so.16 #49 0x28087007 in rb_yield_0 () from /usr/local/lib/libruby.so.16 #50 0x2808336e in rb_eval () from /usr/local/lib/libruby.so.16 #51 0x280892d3 in rb_call0 () from /usr/local/lib/libruby.so.16 #52 0x280896fe in rb_call () from /usr/local/lib/libruby.so.16 #53 0x280899f1 in rb_funcall2 () from /usr/local/lib/libruby.so.16 #54 0x2808bdb0 in rb_obj_call_init () from /usr/local/lib/libruby.so.16 #55
onboard sound card problems
Not sure if Mailing.freebsd.questions is still gatewayed here (it's really low traffic now, so I'm thinking not) if it still is, sorry for the repost. From: Will Yardley [EMAIL PROTECTED] Subject: Disabling onboard sound card I have been having some problems since upgrading to 4.9 - earlier I had problems with the onboard sound card, so I switched to a PCI card which worked a lot better. Since the upgrade, FreeBSD makes the onboard card /dev/dsp0 and the PCI card /dev/dsp1. Is there any way to reverse the two devices? Do I just need to specify the device / IRQ in the kernel configuration (and if so, what exactly should I put?) aura% dmesg| grep pcm pcm0: CMedia CMI8738 port 0xb800-0xb8ff irq 9 at device 3.0 on pci2 pcm1: Yamaha DS-1 (YMF724) mem 0xf100-0xf1007fff irq 9 at device 10.0 on pci2 pcm1: Asahi Kasei AK4540 AC97 Codec Is there a quick hack to disable the onboard sound or switch the two devices? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
problems with FreeBSD telnet client
I've asked this before (a long while back), but never got a response. When I telnet to a Cisco device from a FreeBSD machine, I get this error: jazz% telnet somerouterorswitch Password: Kerberos: No default realm defined for Kerberos! Assuming you don't use Kerberos, is there a way to make the telnet client not attempt to use it to authenticate? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problems with FreeBSD telnet client
On Mon, Nov 10, 2003 at 06:16:50PM -0800, Will Yardley wrote: [ Sorry for the lack of proper references / in-reply-to headers; I'm not subbed to the list, and I didn't get sent a copy ] When I telnet to a Cisco device from a FreeBSD machine, I get this error: jazz% telnet somerouterorswitch Password: Kerberos: No default realm defined for Kerberos! Assuming you don't use Kerberos, is there a way to make the telnet client not attempt to use it to authenticate? Sure, two possible solutions: * Set up your Cisco devices to use Kerberos * Check out the -K option in the telnet man page Any other possibilities? I guess I could alias telnet to telnet -K, but then it won't automatically use my username if I telnet to another machine. I took a quick look through the telnet source, but didn't see any obvious options to simply build it without kerberos support. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problems with FreeBSD telnet client
Matthew Emmerton wrote: When I telnet to a Cisco device from a FreeBSD machine, I get this error: jazz% telnet somerouterorswitch Password: Kerberos: No default realm defined for Kerberos! Assuming you don't use Kerberos, is there a way to make the telnet client not attempt to use it to authenticate? I have a feeling that this is coming from the telnet server (ie, the Cisco box), since no such text shows up in the FreeBSD telnet client sources our our Kerberos-[45] libraries. (4-STABLE, cvsup'd just a few minutes ago.) Perhaps the Cisco box has Kerberos support, and since it senses that the FreeBSD telnet client is Kerberos-aware, it spews out this warning to notify you of the server misconfiguration? Yeah - I was guessing that that was the problem. I was hoping there was a way to get the telnet client not to try to use Kerberos, but sounds like -K may be the closest thing to that. Checked out some of the options at: http://www.cisco.com/en/US/products/sw/iosswrel/ps1831/products_command_summary_chapter09186a00800880ac.html but don't see anything that will help. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
