Re: DragonFly installation experience / suggestions
Matthew Dillon wrote: That early in the boot there's probably no way to get a kernel core dump. I think Michael wrote that he can load it from loader without problems, but it panics when kldloading it. Debugging in that case might be easy. Just set a dumpdev and write out a dump which then can be analyzed with kgdb. A `bt' in kgdb is usually the first step. Apart from that, my guess is contiguous DMA memory. cheers simon -- Serve - BSD +++ RENT this banner advert +++ASCII Ribbon /\ Work - Mac +++ space for low €€€ NOW!1 +++ Campaign \ / Party Enjoy Relax | http://dragonflybsd.org Against HTML \ Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \
Re: DragonFly installation experience / suggestions
On 8/13/07, Simon 'corecode' Schubert [EMAIL PROTECTED] wrote: Matthew Dillon wrote: That early in the boot there's probably no way to get a kernel core dump. I think Michael wrote that he can load it from loader without problems, but it panics when kldloading it. Debugging in that case might be easy. Just set a dumpdev and write out a dump which then can be analyzed with kgdb. A `bt' in kgdb is usually the first step. Apart from that, my guess is contiguous DMA memory. I have received a backtrace and dmesg from Michael. It was caused by cbb re-probe-attach when ipw is loaded after booting: 1) cbb/ipw is on same pci bus (pci2) 2) cbb attach failed during boot, due to unable to alloc irq res. 3) load ipw module after booting caused all unattached devices (including cbb) under pci2 re-probe-attach, then cbb tried to attach again, but failed again. But this time the error cleaning up in cbb attach code caused problem: resource is busy when releasing. Didn't have time to take a closer look at it last night. Above is the conclusion I got before I went to sleep. Best Regards, sephe -- Live Free or Die
Re: DragonFly installation experience / suggestions
Sepherosa Ziehau wrote: On 8/10/07, Michael Neumann [EMAIL PROTECTED] wrote: Hey, Once again I changed from FreeBSD to DragonFly :) Here's a list of a few problems I encountered and what I think could be improved: * After installation, my laptop BIOS hung up. I had to manually intercept the installation process and issue fdisk -BIC. The -C option seems to be important here. This wasn't neccessary on NetBSD/FreeBSD. The -C option does not exist in FreeBSD's fdisk, maybe there do it more intelligently? * kldload if_ipw led to a kernel panic, whereas if_ipw_load=YES in Can you give me more information about this panic? Things like back trace... How can I do that easily? The panic switches into the kernel debugger. From there? Thanks. Regards, Michael
Re: DragonFly installation experience / suggestions
Joerg Sonnenberger wrote: On Fri, Aug 10, 2007 at 01:43:33PM +0200, Michael Neumann wrote: * In FreeBSD there is a /etc/rc.d/ipw script, that load the firmware into the driver (ipwcontrol -i ipw0 -f firmwarefile). IIRC, FreeBSD 7.0 will even include the firmware file and add a sysctl like kern.license.ipw, which you have to set to agree the Intel license. It's very annoying to install a system, if this firmware is not shipped with the base system, as you need to get connected with a cable to fetch this firmware! I'm not sure if anyone wants to fight with Intel long enough to get the rights for redistribution. I certainly don't want to. Me too :) * Would it be possible to preset the PKG_PATH to for example pkgsrc-box.org? This would make life much easier for beginners. I object such a change. Really, take the 5min to figure out which mirror is nearest / fastest for you and take that. Agreed. Should be provided in the installer (select pkgsrc mirror). * After having added a lot of binary packages, I tried to install another one from source. This required libxml-someversion, which seemed to be already installed (by a binary package). Despite, it stopped and told me that I either should remove the package (pkg_delete) or that I should issue bmake replace. Oh, I did bmake replace, and this first removed a few packages (my window manager and stuff like that!). *What* did it tell you? The biggest reason is typically that the binary package is outdated and a newer reason is required for whatever reason. I also question that it told you to run make replace, which does something quite different. Sorry, you're right! It was a different version. === Installing for libxslt-1.1.21 ERROR: libxslt-1.1.20 is already installed - perhaps an older version? ERROR: If so, you may use either of: ERROR: - pkg_delete libxslt-1.1.20 and /usr/pkg/bin/bmake reinstall ERROR: to upgrade properly ERROR: - /usr/pkg/bin/bmake update to rebuild the package and all ERROR: of its dependencies ERROR: - /usr/pkg/bin/bmake replace to replace only the package without ERROR: re-linking dependencies, risking various problems. * pkgsrc: If you install www/firefox from source, this will install firefox 2.x. If you do pkg_add firefox, this will install firefox-15. It shouldn't. You might have hit a temporary bug in pkg_install though. * What would be really cool, if pkgsrc could mix binary and packages from source. So if I do pkg_add thispackage, it tries to add all packages it can find as binary, the others it will build from source. The same if you do bmake, given an option, it would first try to add binaries for all the dependencies. DEPENDS_TARGET=bin-install Set BINPKG_SITES similiar to PKG_PATH first. I'll try that out. Thanks! * Installing ipw-firmware, a message says to modify ACCEPTABLE_LICENSES accordingly in /etc/mk.conf. I do it, but the same message occurs, until I realize that there is /usr/pkg/etc/mk.conf that I have to modify. Fixed. Thanks. Regards, Michael
Re: DragonFly installation experience / suggestions
On Sat, Aug 11, 2007 at 09:33:36PM +0200, Michael Neumann wrote: Sorry, you're right! It was a different version. === Installing for libxslt-1.1.21 ERROR: libxslt-1.1.20 is already installed - perhaps an older version? ERROR: If so, you may use either of: ERROR: - pkg_delete libxslt-1.1.20 and /usr/pkg/bin/bmake ... The only package I can find that explicitly requests 1.1.21 is py-libxslt. And that makes sense as they are quite right together. Joerg
Re: DragonFly installation experience / suggestions
Sepherosa Ziehau wrote: On 8/10/07, Michael Neumann [EMAIL PROTECTED] wrote: Hey, Once again I changed from FreeBSD to DragonFly :) Here's a list of a few problems I encountered and what I think could be improved: * After installation, my laptop BIOS hung up. I had to manually intercept the installation process and issue fdisk -BIC. The -C option seems to be important here. This wasn't neccessary on NetBSD/FreeBSD. The -C option does not exist in FreeBSD's fdisk, maybe there do it more intelligently? * kldload if_ipw led to a kernel panic, whereas if_ipw_load=YES in Can you give me more information about this panic? Things like back trace... #0 dumpsys () at thread.h:83 #1 0xc02ef8ab in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:371 #2 0xc02f0034 in panic (fmt=0xc05677c5 from debugger) at /usr/src/sys/kern/kern_shutdown.c:796 #3 0xc0166c6a in db_panic (addr=-1068458059, have_addr=0, count=-1, modif=0xd2bcd8cc ) at /usr/src/sys/ddb/db_command.c:447 #4 0xc0166bff in db_command (last_cmdp=0xc063a9b0, cmd_table=0x0, aux_cmd_tablep=0xc05c4194, aux_cmd_tablep_end=0xc05c41b0) at /usr/src/sys/ddb/db_command.c:343 #5 0xc0166cdf in db_command_loop () at /usr/src/sys/ddb/db_command.c:469 #6 0xc0169874 in db_trap (type=3, code=0) at /usr/src/sys/ddb/db_trap.c:71 #7 0xc0509c58 in kdb_trap (type=3, code=0, regs=0xd2bcd9f0) at /usr/src/sys/platform/pc32/i386/db_interface.c:148 #8 0xc051cad0 in trap (frame=0xd2bcd9f0) at /usr/src/sys/platform/pc32/i386/trap.c:804 #9 0xc050aca6 in calltrap () at /usr/src/sys/platform/pc32/i386/exception.s:783 #10 0xc0509fb5 in Debugger (msg=0x12 Address 0x12 out of bounds) at cpufunc.h:73 #11 0xc02f002c in panic (fmt=0xc05aa1c0 resource_list_release: resource entry is not busy) at /usr/src/sys/kern/kern_shutdown.c:794 #12 0xc03028c3 in resource_list_release (rl=0x12, bus=0xcb2cb9d0, child=0xcb2cbaf0, type=3, rid=16, res=0xcb28ce68) at /usr/src/sys/kern/subr_bus.c:1832 #13 0xc045e920 in pci_release_resource (dev=0x0, child=0xcb2cbaf0, type=0, rid=0, r=0x0) at /usr/src/sys/bus/pci/pci.c:1932 #14 0xc0303cb7 in bus_release_resource (dev=0x0, type=3, rid=16, r=0xcb28ce68) at bus_if.h:131 #15 0xc0172c3f in cbb_pci_attach (brdev=0xcb2cbaf0) at /usr/src/sys/dev/pccard/pccbb/pccbb_pci.c:438 #16 0xc03017df in device_doattach (dev=0xcb2cbaf0) at device_if.h:39 #17 0xc03016f3 in device_probe_and_attach (dev=0xcb2cbaf0) at /usr/src/sys/kern/subr_bus.c:1114 #18 0xc030306f in bus_generic_driver_added (dev=0xcb2cb9d0, driver=0xd2c2a1b8) at /usr/src/sys/kern/subr_bus.c:2095 #19 0xc0300561 in devclass_add_driver (dc=0xc1641038, driver=0xd2c2a1b8) at bus_if.h:71 #20 0xc0304556 in driver_module_handler (mod=0xcb28cbc8, what=-758996552, arg=0xd2c2a1d0) at /usr/src/sys/kern/subr_bus.c:2636 #21 0xc02d1e38 in module_register_init (arg=0xd2c2a1e4) at /usr/src/sys/kern/kern_module.c:110 #22 0xc02d24c4 in linker_file_sysinit (lf=0xd2ad3cd8) at /usr/src/sys/kern/kern_linker.c:157 #23 0xc02d2779 in linker_load_file (filename=0xcb2e4c00 if_ipw, result=0xd2bcdcac) at /usr/src/sys/kern/kern_linker.c:286 #24 0xc02d30b8 in sys_kldload (uap=0xd2bcdcf8) at /usr/src/sys/kern/kern_linker.c:744 #25 0xc051d430 in syscall2 (frame=0xd2bcdd40) at /usr/src/sys/platform/pc32/i386/trap.c:1340 #26 0xc050ad45 in Xint0x80_syscall () at /usr/src/sys/platform/pc32/i386/exception.s:872 #27 0x080487b8 in ?? () #28 0xbfbffb4c in ?? () #29 0x002f in ?? () #30 0x in ?? () #31 0x in ?? () #32 0x in ?? () #33 0x in ?? () #34 0x1a5cb000 in ?? () #35 0x000d in ?? () #36 0xc0652878 in intr_info_ary () #37 0xd2bcd8a0 in ?? () #38 0xd2bcd888 in ?? () #39 0xc8016e00 in ?? () #40 0xc02f7572 in lwkt_preempt (ntd=0xbfbffbd8, critpri=Cannot access memory at address 0xbfbffb9c ) at /usr/src/sys/kern/lwkt_thread.c:882 Previous frame inner to this frame (corrupt stack?) Do you need anything else? Regards, Michael
Re: DragonFly installation experience / suggestions
Michael Neumann wrote: * In FreeBSD there is a /etc/rc.d/ipw script, that load the firmware into the driver (ipwcontrol -i ipw0 -f firmwarefile). I'll look at the script later. Try putting it in /etc/start_if.iwi0 for now. Sascha -- http://yoyodyne.ath.cx
Re: DragonFly installation experience / suggestions
On 8/10/07, Michael Neumann [EMAIL PROTECTED] wrote: Hey, Once again I changed from FreeBSD to DragonFly :) Here's a list of a few problems I encountered and what I think could be improved: * After installation, my laptop BIOS hung up. I had to manually intercept the installation process and issue fdisk -BIC. The -C option seems to be important here. This wasn't neccessary on NetBSD/FreeBSD. The -C option does not exist in FreeBSD's fdisk, maybe there do it more intelligently? * kldload if_ipw led to a kernel panic, whereas if_ipw_load=YES in Can you give me more information about this panic? Things like back trace... /boot/loader.conf works. * In FreeBSD there is a /etc/rc.d/ipw script, that load the firmware into the driver (ipwcontrol -i ipw0 -f firmwarefile). IIRC, FreeBSD 7.0 will even include the firmware file and add a sysctl like kern.license.ipw, which you have to set to agree the Intel license. It's very annoying to install a system, if this firmware is not shipped with the base system, as you need to get connected with a cable to fetch this firmware! I don't know much in the license stuffs nor the agreement between intel and FreeBSD foundation, but I thought/think ipw/iwi's firmware can only be distributed in FreeBSD. Best Regards, sephe -- Live Free or Die
DragonFly installation experience / suggestions
Hey, Once again I changed from FreeBSD to DragonFly :) Here's a list of a few problems I encountered and what I think could be improved: * After installation, my laptop BIOS hung up. I had to manually intercept the installation process and issue fdisk -BIC. The -C option seems to be important here. This wasn't neccessary on NetBSD/FreeBSD. The -C option does not exist in FreeBSD's fdisk, maybe there do it more intelligently? * kldload if_ipw led to a kernel panic, whereas if_ipw_load=YES in /boot/loader.conf works. * In FreeBSD there is a /etc/rc.d/ipw script, that load the firmware into the driver (ipwcontrol -i ipw0 -f firmwarefile). IIRC, FreeBSD 7.0 will even include the firmware file and add a sysctl like kern.license.ipw, which you have to set to agree the Intel license. It's very annoying to install a system, if this firmware is not shipped with the base system, as you need to get connected with a cable to fetch this firmware! * Would it be possible to preset the PKG_PATH to for example pkgsrc-box.org? This would make life much easier for beginners. * moused: There's no easy way (at least I know of) to run with two mice. I've to do: moused -t auto -p /dev/ums0 moused -t auto -p /dev/psm0 But that's not possible with moused_enable/flags in /etc/rc.conf. * After having added a lot of binary packages, I tried to install another one from source. This required libxml-someversion, which seemed to be already installed (by a binary package). Despite, it stopped and told me that I either should remove the package (pkg_delete) or that I should issue bmake replace. Oh, I did bmake replace, and this first removed a few packages (my window manager and stuff like that!). I don't understand what's the problem, why pkgsrc want's to install that package even if it's already installed. * pkgsrc: If you install www/firefox from source, this will install firefox 2.x. If you do pkg_add firefox, this will install firefox-15. * What would be really cool, if pkgsrc could mix binary and packages from source. So if I do pkg_add thispackage, it tries to add all packages it can find as binary, the others it will build from source. The same if you do bmake, given an option, it would first try to add binaries for all the dependencies. * Installing ipw-firmware, a message says to modify ACCEPTABLE_LICENSES accordingly in /etc/mk.conf. I do it, but the same message occurs, until I realize that there is /usr/pkg/etc/mk.conf that I have to modify. * Uh, and if DragonFly would get pkgjam.org that would be great! I don't know what the general opinion of pkgsrc developers about pkgjam.org is... * What I'd like to see ported is trunk(4) from OpenBSD and lagg(4) from FreeBSD (7.0) for link aggregation / trunking. If I understand that correctly, it would allow me to seamlessly switch between wireless/wired networks at runtime. Other than that I'm really happy with DragonFly so far. Regards, Michael
