Re: Some problems installing dragonFly BSD. Can anybody help?
Dear Justin On 07/05/2011 01:14, Justin Sherrill wrote: 5. I was expecting FVWM as the window manager: I thought the docs said that was the default. Presumably I can change the window manager. Should it have been FVWM? Is the fact that I got TWM instead a symptom that some config was wrong? If the original poster was running as a newly created user rather than root, that may be why. I don't think the default GUI config is added to new user profiles; just the root one present at install. That's exactly what was happening, thanks. Just now I logged in as root and started X, and got fvwm. Also, exiting X back to the console went smoothly. One thing that happened both times: on startx, the laptop screen filled with semi-random-looking blocks of colour for a split second before going into the wm. I think I've seen this before on some linux installs. Presumably X is configured to some default (vesa?) and not the particular graphics card, screen, etc., I have on my laptop. I'll go through comments as time allows, ironing out the glitches on my laptop, and write up once everything's working. As no-one has said anything like you have completely ballsed up your installation! I shan't reinstall (unless advised otherwise). Although installing DragonFly on a virtual machine (e.g., VirtualBox) is a good idea, many of my symptoms seem to be to do with the particular hardware of the laptop. so I'll continue with the real machine for now. Thanks again to everyone for help. Best wishes Ivan -- Ivan A. Uemlianin Speech Technology Research and Development i...@llaisdy.com www.llaisdy.com llaisdy.wordpress.com www.linkedin.com/in/ivanuemlianin Froh, froh! Wie seine Sonnen, seine Sonnen fliegen (Schiller, Beethoven)
Re: Some problems installing dragonFly BSD. Can anybody help?
On Montag, 9. Mai 2011 at 09:47, Ivan Uemlianin wrote: One thing that happened both times: on startx, the laptop screen filled with semi-random-looking blocks of colour for a split second before going into the wm. I think I've seen this before on some linux installs. Presumably X is configured to some default (vesa?) and not the particular graphics card, screen, etc., I have on my laptop. I don't think that's anything to worry about … I've once seen what I had on screen before the last reboot, so I guess this is just random contents of video RAM being displayed before anything is drawn over them. On Samstag, 7. Mai 2011 at 17:44, Justin Sherrill wrote: This is a new bug, then, cause I think the original ath(4) problem is fixed. I don't have the right laptop and wireless combo to test. In any case, you may want to file a report including the network encryption type. From what I can tell from [1] this has not been fixed. I can still file a report if that helps? Also note that I have control over the WLAN router (other than my flatmates kicking me when I kill their internet), so if I can provide any additional info / try anything out let me know. Re: IO APIC Disabling IO APIC didn't help with the SMP kernel, it complains about lapic initialization before dropping to the debugger (is there a LAPIC loader tunable? I can't find any documentation on this or hw.apic_io_enable). Are SMP kernels on UP machines *supposed* to work anyway? -matthiasr [1] http://gitweb.dragonflybsd.org/dragonfly.git/history/HEAD:/sys/dev/netif/ath
Re: Some problems installing dragonFly BSD. Can anybody help?
I agree on the random video RAM contents thing - that would have been my first guess. The wireless connection Matt and I both had trouble with, with ath(4), was using WPA2, though I don't know the device. If you want to try different setups and see what works and what doesn't, that would make a useful report. Maybe set sysctl kern.emergency_intr_enable=1? I don't remember if that's already been suggested, or if that would apply in this case. On Mon, May 9, 2011 at 4:49 AM, Matthias Rampke matthias.ram...@googlemail.com wrote: On Montag, 9. Mai 2011 at 09:47, Ivan Uemlianin wrote: One thing that happened both times: on startx, the laptop screen filled with semi-random-looking blocks of colour for a split second before going into the wm. I think I've seen this before on some linux installs. Presumably X is configured to some default (vesa?) and not the particular graphics card, screen, etc., I have on my laptop. I don't think that's anything to worry about … I've once seen what I had on screen before the last reboot, so I guess this is just random contents of video RAM being displayed before anything is drawn over them. On Samstag, 7. Mai 2011 at 17:44, Justin Sherrill wrote: This is a new bug, then, cause I think the original ath(4) problem is fixed. I don't have the right laptop and wireless combo to test. In any case, you may want to file a report including the network encryption type. From what I can tell from [1] this has not been fixed. I can still file a report if that helps? Also note that I have control over the WLAN router (other than my flatmates kicking me when I kill their internet), so if I can provide any additional info / try anything out let me know. Re: IO APIC Disabling IO APIC didn't help with the SMP kernel, it complains about lapic initialization before dropping to the debugger (is there a LAPIC loader tunable? I can't find any documentation on this or hw.apic_io_enable). Are SMP kernels on UP machines *supposed* to work anyway? -matthiasr [1] http://gitweb.dragonflybsd.org/dragonfly.git/history/HEAD:/sys/dev/netif/ath
Re: Some problems installing dragonFly BSD. Can anybody help?
On Fri, 6 May 2011, Justin Sherrill wrote: sysctl net.wlan.force_swcrypto=1 may help. http://leaf.dragonflybsd.org/mailarchive/commits/2010-11/msg00169.html Works for me. Thank you! -matthiasr
Re: Some problems installing dragonFly BSD. Can anybody help?
This is a new bug, then, cause I think the original ath(4) problem is fixed. I don't have the right laptop and wireless combo to test. In any case, you may want to file a report including the network encryption type. On May 7, 2011 4:16 AM, Matthias Rampke matth...@rampke.de wrote: On Fri, 6 May 2011, Justin Sherrill wrote: sysctl net.wlan.force_swcrypto=1 may help. http://leaf.dragonflybsd.org/mailarchive/commits/2010-11/msg00169.html Works for me. Thank you! -matthiasr
Some problems installing dragonFly BSD. Can anybody help?
Dear All I am installing DragonFly BSD onto a Thinkpad X60. Actually, I have installed it, but perhaps not correctly. Below are my symptoms. Please can anybody help with any of them? Some background: I am fairly familiar with Unix-like operating systems (long time fan of Debian GNU/Linux; currently using MacOS X), but I don't have a sysadmin background. One of my reasons for installing DragonFly BSD is to learn. I plan to blog as I go (e.g., I've just written a note on getting the image onto a USB stick: http://llaisdy.wordpress.com/2011/05/06/dragonfly-bsd-copying-the-image-onto-a-usb-stick-under-macos-x/). I installed dfly-i386-gui-2.10.1_REL.img from a USB stick. Symptoms: Major: 1. After the post-installation configuration step, I chose reboot. While rebooting, the system seemed to crash and I ended up inside a debugger. However, after a successful shutdown and reboot, the system seemed to run OK. 2. During configuration dhcp seemed to find the network (at least, a dialogue appeared, giving me some info ending with Status: Active), but after I'd rebooted into X and launched Firefox, Firefox could not find external urls. So, perhaps dhcp didn't work and I should configure the network manually. 3. The window manager is TWM. On exiting TWM, the screen froze and didn't return me to the console. I had to go to another console and kill X manually. Minor: 4. I don't think I set the correct keyboard map (and/or screen map?). Most of the keyboard works as it should, but shift-3 does not produce the expected £ --- it doesn't produce anything, so maybe the keyboard map is OK but the screen map is wrong? 5. I was expecting FVWM as the window manager: I thought the docs said that was the default. Presumably I can change the window manager. Should it have been FVWM? Is the fact that I got TWM instead a symptom that some config was wrong? All in all, it doesn't look very healthy. Can anybody indicate what might have gone wrong? Or, if I re-install, what signals I should be looking out for? With thanks and best wishes Ivan -- Ivan A. Uemlianin Speech Technology Research and Development i...@llaisdy.com www.llaisdy.com llaisdy.wordpress.com www.linkedin.com/in/ivanuemlianin Froh, froh! Wie seine Sonnen, seine Sonnen fliegen (Schiller, Beethoven)
Re: Some problems installing dragonFly BSD. Can anybody help?
At least output of dmesg, pciconf and probably pictures of those debugger output will be fine. On Fri, May 6, 2011 at 3:30 PM, Ivan Uemlianin i...@llaisdy.com wrote: Dear All I am installing DragonFly BSD onto a Thinkpad X60. Actually, I have installed it, but perhaps not correctly. Below are my symptoms. Please can anybody help with any of them? Some background: I am fairly familiar with Unix-like operating systems (long time fan of Debian GNU/Linux; currently using MacOS X), but I don't have a sysadmin background. One of my reasons for installing DragonFly BSD is to learn. I plan to blog as I go (e.g., I've just written a note on getting the image onto a USB stick: http://llaisdy.wordpress.com/2011/05/06/dragonfly-bsd-copying-the-image-onto-a-usb-stick-under-macos-x/). I installed dfly-i386-gui-2.10.1_REL.img from a USB stick. Symptoms: Major: 1. After the post-installation configuration step, I chose reboot. While rebooting, the system seemed to crash and I ended up inside a debugger. However, after a successful shutdown and reboot, the system seemed to run OK. 2. During configuration dhcp seemed to find the network (at least, a dialogue appeared, giving me some info ending with Status: Active), but after I'd rebooted into X and launched Firefox, Firefox could not find external urls. So, perhaps dhcp didn't work and I should configure the network manually. 3. The window manager is TWM. On exiting TWM, the screen froze and didn't return me to the console. I had to go to another console and kill X manually. Minor: 4. I don't think I set the correct keyboard map (and/or screen map?). Most of the keyboard works as it should, but shift-3 does not produce the expected £ --- it doesn't produce anything, so maybe the keyboard map is OK but the screen map is wrong? 5. I was expecting FVWM as the window manager: I thought the docs said that was the default. Presumably I can change the window manager. Should it have been FVWM? Is the fact that I got TWM instead a symptom that some config was wrong? All in all, it doesn't look very healthy. Can anybody indicate what might have gone wrong? Or, if I re-install, what signals I should be looking out for? With thanks and best wishes Ivan -- Ivan A. Uemlianin Speech Technology Research and Development i...@llaisdy.com www.llaisdy.com llaisdy.wordpress.com www.linkedin.com/in/ivanuemlianin Froh, froh! Wie seine Sonnen, seine Sonnen fliegen (Schiller, Beethoven)
Re: Some problems installing dragonFly BSD. Can anybody help?
On Freitag, 6. Mai 2011 at 15:30, Ivan Uemlianin wrote: Dear All I am installing DragonFly BSD onto a Thinkpad X60. I recently installed on a X40, so let's see. There is also a page on the Website about the T42[1] and the X61s[2], especially most of the latter should apply to your case as well. Symptoms: Major: 1. After the post-installation configuration step, I chose reboot. While rebooting, the system seemed to crash and I ended up inside a debugger. However, after a successful shutdown and reboot, the system seemed to run OK. From what I gather SMP Kernels with IO APIC enabled don't work. I just settled on using UP since I only have one core anyway. You may try setting hw.apic_io_enable=0 in /boot/loader.conf 2. During configuration dhcp seemed to find the network (at least, a dialogue appeared, giving me some info ending with Status: Active), but after I'd rebooted into X and launched Firefox, Firefox could not find external urls. So, perhaps dhcp didn't work and I should configure the network manually. Is this on the WLAN? Which card? I'm having massive trouble getting ath(4) to work with most WLAN routers, e.g. I don't receive the DHCPOFFERs from my home WLAN. My phone's WiFi hotspot (Motorola Milestone / CyanogenMod 6) works perfectly, though. I'm sorry I haven't gotten around to reporting this properly yet. 3. The window manager is TWM. On exiting TWM, the screen froze and didn't return me to the console. I had to go to another console and kill X manually. When it freezes, what does /var/log/Xorg.0.log say? Minor: 4. I don't think I set the correct keyboard map (and/or screen map?). Most of the keyboard works as it should, but shift-3 does not produce the expected £ --- it doesn't produce anything, so maybe the keyboard map is OK but the screen map is wrong? Which layout are you expecting to use, and what are the respective lines in /etc/rc.conf? 5. I was expecting FVWM as the window manager: I thought the docs said that was the default. Presumably I can change the window manager. Should it have been FVWM? Is the fact that I got TWM instead a symptom that some config was wrong? Probably ... (I'm not using the GUI image, so rather wild guessing here). You could a) check that FVWM2 is installed (just run fvwm2 from within twm) b) add exec fvwm2 as the last line of your $HOME/.xsession (and check that it is the *only* exec line, of course) All in all, it doesn't look very healthy. Can anybody indicate what might have gone wrong? Or, if I re-install, what signals I should be looking out for? It's not so bad :) Regards, matthiasr [1] http://www.dragonflybsd.org/docs/user/ThinkpadT42/ [2] http://www.dragonflybsd.org/docs/user/ThinkpadX61s/
Re: Some problems installing dragonFly BSD. Can anybody help?
Dear Tomas and Matthias Thanks for these leads. I'll investigate and report back. Best wishes Ivan -- Ivan A. Uemlianin Speech Technology Research and Development i...@llaisdy.com www.llaisdy.com llaisdy.wordpress.com www.linkedin.com/in/ivanuemlianin Froh, froh! Wie seine Sonnen, seine Sonnen fliegen (Schiller, Beethoven)
Re: Some problems installing dragonFly BSD. Can anybody help?
Maybe you should try no-gui DFBSD image, perhaps in VirtualBox (?) - it works fine on Mac OS X. That way, you can install configure all your needed stuff from the ground up (xorg, window manager, pkgsrc etc.) and copy most config files on your real DF system. Klanger Dnia 6-05-2011 o godz. 16:41 Ivan Uemlianin napisał(a): Dear Tomas and Matthias Thanks for these leads. I'll investigate and report back. Best wishes Ivan -- Ivan A. Uemlianin Speech Technology Research and Development i...@llaisdy.com www.llaisdy.com llaisdy.wordpress.com www.linkedin.com/in/ivanuemlianin Froh, froh! Wie seine Sonnen, seine Sonnen fliegen (Schiller, Beethoven)
Re: Some problems installing dragonFly BSD. Can anybody help?
That's a good idea (and I have vbox to hand). Many of the problems relate to the particular hardware (e.g., configuring the network), but I could at least iron out the other problems. Thanks Ivan On 06/05/2011 15:54, Krzysztof Langer wrote: Maybe you should try no-gui DFBSD image, perhaps in VirtualBox (?) - it works fine on Mac OS X. That way, you can install configure all your needed stuff from the ground up (xorg, window manager, pkgsrc etc.) and copy most config files on your real DF system. Klanger Dnia 6-05-2011 o godz. 16:41 Ivan Uemlianin napisał(a): Dear Tomas and Matthias Thanks for these leads. I'll investigate and report back. Best wishes Ivan -- Ivan A. Uemlianin Speech Technology Research and Development i...@llaisdy.com www.llaisdy.com llaisdy.wordpress.com www.linkedin.com/in/ivanuemlianin Froh, froh! Wie seine Sonnen, seine Sonnen fliegen (Schiller, Beethoven) -- Ivan A. Uemlianin Speech Technology Research and Development i...@llaisdy.com www.llaisdy.com llaisdy.wordpress.com www.linkedin.com/in/ivanuemlianin Froh, froh! Wie seine Sonnen, seine Sonnen fliegen (Schiller, Beethoven)
Re: Some problems installing dragonFly BSD. Can anybody help?
On Freitag, 6. Mai 2011 at 16:03, Matthias Rampke wrote: From what I gather SMP Kernels with IO APIC enabled don't work. I just settled on using UP since I only have one core anyway. You may try setting hw.apic_io_enable=0 in /boot/loader.conf Sorry, that wasn't worded well. I meant to say that SMP + IO APIC doesn't seem to work with x40/x60-ish ThinkPads, so this is very probably a ThinkPad specific issue, not a DragonFly issue. -matthiasr
Trouble installing DragonFly under qemu-kvm
Hi Folks, I'm trying to install DragonFly under qemu, using an ISO (this one's yesterday's snapshot, I think). It boots fine, I'm able to login as root and everything seems to work OK. When I try to login as installer, however, I get the following error message: = Starting installer. Reading /etc/pfi.conf ... Unsupported DFUI transport '' . = It then logs me out. Does anybody know of a workaround? This is how I'm invoking qemu: qemu -m 512 -smp 1 -enable-kvm -net nic -net user -cdrom LATEST-i386-master.iso -hda ./df.img -boot d Thanks, Karthik.
Re: Trouble installing DragonFly under qemu-kvm
Karthik Subramanian schrieb: Hi Folks, I'm trying to install DragonFly under qemu, using an ISO (this one's yesterday's snapshot, I think). It boots fine, I'm able to login as root and everything seems to work OK. When I try to login as installer, however, I get the following error message: = Starting installer. Reading /etc/pfi.conf ... Unsupported DFUI transport '' . = It then logs me out. Does anybody know of a workaround? This is how I'm invoking qemu: qemu -m 512 -smp 1 -enable-kvm -net nic -net user -cdrom LATEST-i386-master.iso -hda ./df.img -boot d Can you login as root instead and check if the /etc/defaults/pfi.conf file is there? There was an issue on recent ISOs which caused them to not have this file. But it was fixed on the 5th. Sascha -- http://yoyodyne.ath.cx
Re: Trouble installing DragonFly under qemu-kvm
On Sun, Nov 8, 2009 at 4:05 PM, Sascha Wildner s...@online.de wrote: Karthik Subramanian schrieb: Hi Folks, I'm trying to install DragonFly under qemu, using an ISO (this one's yesterday's snapshot, I think). It boots fine, I'm able to login as root and everything seems to work OK. When I try to login as installer, however, I get the following error message: = Starting installer. Reading /etc/pfi.conf ... Unsupported DFUI transport '' . = It then logs me out. Does anybody know of a workaround? This is how I'm invoking qemu: qemu -m 512 -smp 1 -enable-kvm -net nic -net user -cdrom LATEST-i386-master.iso -hda ./df.img -boot d Can you login as root instead and check if the /etc/defaults/pfi.conf file is there? There was an issue on recent ISOs which caused them to not have this file. But it was fixed on the 5th. Thanks, Sascha. It turns out that the ISO that I was using is earlier than yesterday's snapshot. So yes, it doesn't have /etc/defaults/pfi.conf. I'll download today's snapshot and use that instead. Karthik.
Re: Trouble installing DragonFly under qemu-kvm
On Sun, Nov 8, 2009 at 4:26 PM, Karthik Subramanian karthik301...@gmail.com wrote: On Sun, Nov 8, 2009 at 4:05 PM, Sascha Wildner s...@online.de wrote: Karthik Subramanian schrieb: Hi Folks, I'm trying to install DragonFly under qemu, using an ISO (this one's yesterday's snapshot, I think). It boots fine, I'm able to login as root and everything seems to work OK. When I try to login as installer, however, I get the following error message: = Starting installer. Reading /etc/pfi.conf ... Unsupported DFUI transport '' . = It then logs me out. Does anybody know of a workaround? This is how I'm invoking qemu: qemu -m 512 -smp 1 -enable-kvm -net nic -net user -cdrom LATEST-i386-master.iso -hda ./df.img -boot d Can you login as root instead and check if the /etc/defaults/pfi.conf file is there? There was an issue on recent ISOs which caused them to not have this file. But it was fixed on the 5th. Thanks, Sascha. It turns out that the ISO that I was using is earlier than yesterday's snapshot. So yes, it doesn't have /etc/defaults/pfi.conf. I'll download today's snapshot and use that instead. Karthik. Today's snapshot worked! Thanks. Sascha. Karthik.
Re: Installing DragonFly
I also tried saving the output from disklabel ad0s1 and just using the last part of that. But I get the same error messages. It looks like a bug in disklabel to me. 2009/4/20 Colin Adams colinpaulad...@googlemail.com: Thanks. I am having problems with the disklabel. I get: line 2: partition name out of range a-`: a and similar for lines 3 - 5 I tried reading the disklabel man page, but could not find anything that said where I was going wrong. P.S. I have a UK keyboard - this is not recognised. I work round it by typing SHIFT-3 (£) to produce a #, but I wonder if this might be relevant (though I can't think why it should be). 2009/4/19 Michael Neumann mneum...@ntecs.de: Am Sonntag, 19. April 2009 14:30:56 schrieben Sie: But I don't want to install on Hammer. I only have 160GB disk, and Matt has said you shouldn't consider Hammer on less than 500GB, if I remember rightly. You don't have to. The instructions are similar for UFS. Replace newfs_hammer with newfs for example and ignore all Hammer related stuff. Take a look at /usr/share/examples/rconfig/auto.sh . It should be available on the installer CD. It's an example how to install DragonFly without the installer using UFS. Of course you need to change fdisk -IB $disk into fdisk -IB -C $disk in this file. If you have any further questions, please ask. Regards, Michael 2009/4/19 Michael Neumann mneum...@ntecs.de: On Sat, 18 Apr 2009 09:00:21 +0100 Colin Adams colinpaulad...@googlemail.com wrote: 2009/4/18 Jordan Gordeev jgord...@dir.bg: Colin Adams wrote: I don't know if it is the same problem (it certainly sounds similar). This is not a laptop though. Nor is it an old machine (less than 3 years old). Anyway, I have booted DragonFly from the live CD and logged in as root. But what device name do I use (I only have one disk)? Everything I guessed at, it says device not configured. 2009/4/17 Michael Neumann mneum...@ntecs.de: Try ad0 or sd0. You should look at dmesg(8) output and see what devices the kernel has recognised (and what names they got). I had already tried ad0. dmesg revealed that the disk hadn't been seen at all. Perhaps I plugged it in too late. Re-booting and re-plugging really early did the trick (it was ad0, which was where the live DVD installed DragonFly yesterday). so fdisk -C ad0 says (slightly abbreviated): cylinders=310101 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 bytes. Warning: BIOS sector numbering starts with sector 1 Information form DOS bootblock is: The data for partition 1 is: ssysid 165,(DragonFly/FreeBSD/NetBSD/386BSD) start 63, size 312581745 (152627 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 255/ sector 63 partitions 2 3 and 4 UNUSED So where do I go from here? Basically, follow those instructions below, replacing ad4 with ad0, and fdisk -B -I ad4 with fdisk -B -I -C ad0. You simply have to by-pass the installer, because it doesn't use the -C option in fdisk, which is essential! http://www.ntecs.de/blog/articles/2008/07/30/dragonfly-on-hammer/ The instructions above are a bit outdated, but they should still work. You can stop the instructions after reboot. Regards, Michael -- Rubyist for over a decade
Re: Installing DragonFly
If I add an extra initial line: 4 partitions: Then I no longer get the error message. But it does say sector size 0, and just typing: disklabel ad0s1 shows the same information as before. 2009/4/20 Colin Adams colinpaulad...@googlemail.com: I also tried saving the output from disklabel ad0s1 and just using the last part of that. But I get the same error messages. It looks like a bug in disklabel to me. 2009/4/20 Colin Adams colinpaulad...@googlemail.com: Thanks. I am having problems with the disklabel. I get: line 2: partition name out of range a-`: a and similar for lines 3 - 5 I tried reading the disklabel man page, but could not find anything that said where I was going wrong. P.S. I have a UK keyboard - this is not recognised. I work round it by typing SHIFT-3 (£) to produce a #, but I wonder if this might be relevant (though I can't think why it should be). 2009/4/19 Michael Neumann mneum...@ntecs.de: Am Sonntag, 19. April 2009 14:30:56 schrieben Sie: But I don't want to install on Hammer. I only have 160GB disk, and Matt has said you shouldn't consider Hammer on less than 500GB, if I remember rightly. You don't have to. The instructions are similar for UFS. Replace newfs_hammer with newfs for example and ignore all Hammer related stuff. Take a look at /usr/share/examples/rconfig/auto.sh . It should be available on the installer CD. It's an example how to install DragonFly without the installer using UFS. Of course you need to change fdisk -IB $disk into fdisk -IB -C $disk in this file. If you have any further questions, please ask. Regards, Michael 2009/4/19 Michael Neumann mneum...@ntecs.de: On Sat, 18 Apr 2009 09:00:21 +0100 Colin Adams colinpaulad...@googlemail.com wrote: 2009/4/18 Jordan Gordeev jgord...@dir.bg: Colin Adams wrote: I don't know if it is the same problem (it certainly sounds similar). This is not a laptop though. Nor is it an old machine (less than 3 years old). Anyway, I have booted DragonFly from the live CD and logged in as root. But what device name do I use (I only have one disk)? Everything I guessed at, it says device not configured. 2009/4/17 Michael Neumann mneum...@ntecs.de: Try ad0 or sd0. You should look at dmesg(8) output and see what devices the kernel has recognised (and what names they got). I had already tried ad0. dmesg revealed that the disk hadn't been seen at all. Perhaps I plugged it in too late. Re-booting and re-plugging really early did the trick (it was ad0, which was where the live DVD installed DragonFly yesterday). so fdisk -C ad0 says (slightly abbreviated): cylinders=310101 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 bytes. Warning: BIOS sector numbering starts with sector 1 Information form DOS bootblock is: The data for partition 1 is: ssysid 165,(DragonFly/FreeBSD/NetBSD/386BSD) start 63, size 312581745 (152627 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 255/ sector 63 partitions 2 3 and 4 UNUSED So where do I go from here? Basically, follow those instructions below, replacing ad4 with ad0, and fdisk -B -I ad4 with fdisk -B -I -C ad0. You simply have to by-pass the installer, because it doesn't use the -C option in fdisk, which is essential! http://www.ntecs.de/blog/articles/2008/07/30/dragonfly-on-hammer/ The instructions above are a bit outdated, but they should still work. You can stop the instructions after reboot. Regards, Michael -- Rubyist for over a decade
Re: Installing DragonFly
Anyway, I ignored the possibility that it wasn't working, and proceeded with the instructions. And when I tried re-booting, from the disk drive, it worked! At least, it almost worked. I have a dragonfly system, but it's not quire right. (I think I edited /etc/fstab in the wrong place - I forgot to put /mnt in front of the path). Hopefully I can correct that on my own without further help. Thanks for all your help. 2009/4/20 Colin Adams colinpaulad...@googlemail.com: If I add an extra initial line: 4 partitions: Then I no longer get the error message. But it does say sector size 0, and just typing: disklabel ad0s1 shows the same information as before. 2009/4/20 Colin Adams colinpaulad...@googlemail.com: I also tried saving the output from disklabel ad0s1 and just using the last part of that. But I get the same error messages. It looks like a bug in disklabel to me. 2009/4/20 Colin Adams colinpaulad...@googlemail.com: Thanks. I am having problems with the disklabel. I get: line 2: partition name out of range a-`: a and similar for lines 3 - 5 I tried reading the disklabel man page, but could not find anything that said where I was going wrong. P.S. I have a UK keyboard - this is not recognised. I work round it by typing SHIFT-3 (£) to produce a #, but I wonder if this might be relevant (though I can't think why it should be). 2009/4/19 Michael Neumann mneum...@ntecs.de: Am Sonntag, 19. April 2009 14:30:56 schrieben Sie: But I don't want to install on Hammer. I only have 160GB disk, and Matt has said you shouldn't consider Hammer on less than 500GB, if I remember rightly. You don't have to. The instructions are similar for UFS. Replace newfs_hammer with newfs for example and ignore all Hammer related stuff. Take a look at /usr/share/examples/rconfig/auto.sh . It should be available on the installer CD. It's an example how to install DragonFly without the installer using UFS. Of course you need to change fdisk -IB $disk into fdisk -IB -C $disk in this file. If you have any further questions, please ask. Regards, Michael 2009/4/19 Michael Neumann mneum...@ntecs.de: On Sat, 18 Apr 2009 09:00:21 +0100 Colin Adams colinpaulad...@googlemail.com wrote: 2009/4/18 Jordan Gordeev jgord...@dir.bg: Colin Adams wrote: I don't know if it is the same problem (it certainly sounds similar). This is not a laptop though. Nor is it an old machine (less than 3 years old). Anyway, I have booted DragonFly from the live CD and logged in as root. But what device name do I use (I only have one disk)? Everything I guessed at, it says device not configured. 2009/4/17 Michael Neumann mneum...@ntecs.de: Try ad0 or sd0. You should look at dmesg(8) output and see what devices the kernel has recognised (and what names they got). I had already tried ad0. dmesg revealed that the disk hadn't been seen at all. Perhaps I plugged it in too late. Re-booting and re-plugging really early did the trick (it was ad0, which was where the live DVD installed DragonFly yesterday). so fdisk -C ad0 says (slightly abbreviated): cylinders=310101 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 bytes. Warning: BIOS sector numbering starts with sector 1 Information form DOS bootblock is: The data for partition 1 is: ssysid 165,(DragonFly/FreeBSD/NetBSD/386BSD) start 63, size 312581745 (152627 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 255/ sector 63 partitions 2 3 and 4 UNUSED So where do I go from here? Basically, follow those instructions below, replacing ad4 with ad0, and fdisk -B -I ad4 with fdisk -B -I -C ad0. You simply have to by-pass the installer, because it doesn't use the -C option in fdisk, which is essential! http://www.ntecs.de/blog/articles/2008/07/30/dragonfly-on-hammer/ The instructions above are a bit outdated, but they should still work. You can stop the instructions after reboot. Regards, Michael -- Rubyist for over a decade
Re: Installing DragonFly
On Sat, 18 Apr 2009 09:00:21 +0100 Colin Adams colinpaulad...@googlemail.com wrote: 2009/4/18 Jordan Gordeev jgord...@dir.bg: Colin Adams wrote: I don't know if it is the same problem (it certainly sounds similar). This is not a laptop though. Nor is it an old machine (less than 3 years old). Anyway, I have booted DragonFly from the live CD and logged in as root. But what device name do I use (I only have one disk)? Everything I guessed at, it says device not configured. 2009/4/17 Michael Neumann mneum...@ntecs.de: Try ad0 or sd0. You should look at dmesg(8) output and see what devices the kernel has recognised (and what names they got). I had already tried ad0. dmesg revealed that the disk hadn't been seen at all. Perhaps I plugged it in too late. Re-booting and re-plugging really early did the trick (it was ad0, which was where the live DVD installed DragonFly yesterday). so fdisk -C ad0 says (slightly abbreviated): cylinders=310101 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 bytes. Warning: BIOS sector numbering starts with sector 1 Information form DOS bootblock is: The data for partition 1 is: ssysid 165,(DragonFly/FreeBSD/NetBSD/386BSD) start 63, size 312581745 (152627 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 255/ sector 63 partitions 2 3 and 4 UNUSED So where do I go from here? Basically, follow those instructions below, replacing ad4 with ad0, and fdisk -B -I ad4 with fdisk -B -I -C ad0. You simply have to by-pass the installer, because it doesn't use the -C option in fdisk, which is essential! http://www.ntecs.de/blog/articles/2008/07/30/dragonfly-on-hammer/ The instructions above are a bit outdated, but they should still work. You can stop the instructions after reboot. Regards, Michael
Re: Installing DragonFly
Colin Adams wrote: I don't know if it is the same problem (it certainly sounds similar). This is not a laptop though. Nor is it an old machine (less than 3 years old). Anyway, I have booted DragonFly from the live CD and logged in as root. But what device name do I use (I only have one disk)? Everything I guessed at, it says device not configured. 2009/4/17 Michael Neumann mneum...@ntecs.de: Try ad0 or sd0. You should look at dmesg(8) output and see what devices the kernel has recognised (and what names they got).
Re: Installing DragonFly
2009/4/18 Jordan Gordeev jgord...@dir.bg: Colin Adams wrote: I don't know if it is the same problem (it certainly sounds similar). This is not a laptop though. Nor is it an old machine (less than 3 years old). Anyway, I have booted DragonFly from the live CD and logged in as root. But what device name do I use (I only have one disk)? Everything I guessed at, it says device not configured. 2009/4/17 Michael Neumann mneum...@ntecs.de: Try ad0 or sd0. You should look at dmesg(8) output and see what devices the kernel has recognised (and what names they got). I had already tried ad0. dmesg revealed that the disk hadn't been seen at all. Perhaps I plugged it in too late. Re-booting and re-plugging really early did the trick (it was ad0, which was where the live DVD installed DragonFly yesterday). so fdisk -C ad0 says (slightly abbreviated): cylinders=310101 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 bytes. Warning: BIOS sector numbering starts with sector 1 Information form DOS bootblock is: The data for partition 1 is: ssysid 165,(DragonFly/FreeBSD/NetBSD/386BSD) start 63, size 312581745 (152627 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 255/ sector 63 partitions 2 3 and 4 UNUSED So where do I go from here?
Re: Installing DragonFly
I was able to install DragonFly on the disk all-right, but the machine still won't boot if the drive is powered-on at boot time. I'll have to try the linux live-cd fdisk :-( 2009/4/17 Colin Adams colinpaulad...@googlemail.com: Now I'm back home, i've tried out everyone's suggestions. Bill's idea to remove the hard-disk from the boot-sequence made no difference (I'm surprised - I thought that was just something obvious that I had forgotten in my approaching senility). The suggestion to only plug the hard-disk in after booting from the CD works - and in fact I didn't bother to boot a linux live-CD - I just went ahead (after deleteting the ttysv1 entry) and let the DragonFly DVD format the hard disk - it seems to be working so far (it is currently installing files). 2009/4/15 Simon 'corecode' Schubert corec...@fs.ei.tum.de: I bet this is the set all bits to one on CHS overflow thing in fdisk. I'd really like to know how we are supposed to handle this (better). Colin, sorry for trashing your computer. I think we are well aware of this issue, but we simply don't know exactly how to deal with it. Could you maybe use window's fdisk to create a large partition on the drive and then report back how the partition table looks like? In this case we could adjust our fdisk so that this won't happen again. thanks simon Colin Adams wrote: What appears to have happened is that in some way it has trashed my disk-drive - I can still get the machine to boot from the live CD, but only if I physically disconnect the hard-disk first. 2009/4/8 Hasso Tepper ha...@estpak.ee: Colin Adams wrote: Well, if that is the case the ISO should not be available for download - there should be a fixed version. Well. It shouldn't be any way fatal, but in general I agree - we should release 2.2.1 ASAP, really. -- Hasso Tepper
Re: Installing DragonFly
So linux fdisk says the following things about the disk: /dev/sda1 Bootable Start 1 End 19382 Blocks 156290872+ Id a5 System FreeBSD (I selected UFS rather than HAMMER when I installed DragonFly on it). So everything looks fine, except I can't have it powered on at Computer boot-time. Perhaps I can install GRUB on a floppy, pointing it at /dev/sda1, and plug the disk in whilst GRUB is being loaded. (This begs of desperation - especially as I don't know what a GRUB definition for DragonFly should look like). 2009/4/15 Simon 'corecode' Schubert corec...@fs.ei.tum.de: I bet this is the set all bits to one on CHS overflow thing in fdisk. I'd really like to know how we are supposed to handle this (better). Colin, sorry for trashing your computer. I think we are well aware of this issue, but we simply don't know exactly how to deal with it. Could you maybe use window's fdisk to create a large partition on the drive and then report back how the partition table looks like? In this case we could adjust our fdisk so that this won't happen again. thanks simon Colin Adams wrote: What appears to have happened is that in some way it has trashed my disk-drive - I can still get the machine to boot from the live CD, but only if I physically disconnect the hard-disk first. 2009/4/8 Hasso Tepper ha...@estpak.ee: Colin Adams wrote: Well, if that is the case the ISO should not be available for download - there should be a fixed version. Well. It shouldn't be any way fatal, but in general I agree - we should release 2.2.1 ASAP, really. -- Hasso Tepper
Re: Installing DragonFly
Colin Adams wrote: I was able to install DragonFly on the disk all-right, but the machine still won't boot if the drive is powered-on at boot time. I remember that I had a similar problem about 2 years ago with my Bullman laptop. http://leaf.dragonflybsd.org/mailarchive/users/2007-02/msg00158.html If yours is the same problem (can you confirm?) then fdisk -C will solve it. But as the installer does not provide an option to set the -C flag, you'd have to install DragonFly without the installer. Regards, Michael
Re: Installing DragonFly
I don't know if it is the same problem (it certainly sounds similar). This is not a laptop though. Nor is it an old machine (less than 3 years old). Anyway, I have booted DragonFly from the live CD and logged in as root. But what device name do I use (I only have one disk)? Everything I guessed at, it says device not configured. 2009/4/17 Michael Neumann mneum...@ntecs.de: Colin Adams wrote: I was able to install DragonFly on the disk all-right, but the machine still won't boot if the drive is powered-on at boot time. I remember that I had a similar problem about 2 years ago with my Bullman laptop. http://leaf.dragonflybsd.org/mailarchive/users/2007-02/msg00158.html If yours is the same problem (can you confirm?) then fdisk -C will solve it. But as the installer does not provide an option to set the -C flag, you'd have to install DragonFly without the installer. Regards, Michael
Re: Installing DragonFly
I bet this is the set all bits to one on CHS overflow thing in fdisk. I'd really like to know how we are supposed to handle this (better). Colin, sorry for trashing your computer. I think we are well aware of this issue, but we simply don't know exactly how to deal with it. Could you maybe use window's fdisk to create a large partition on the drive and then report back how the partition table looks like? In this case we could adjust our fdisk so that this won't happen again. thanks simon Colin Adams wrote: What appears to have happened is that in some way it has trashed my disk-drive - I can still get the machine to boot from the live CD, but only if I physically disconnect the hard-disk first. 2009/4/8 Hasso Tepper ha...@estpak.ee: Colin Adams wrote: Well, if that is the case the ISO should not be available for download - there should be a fixed version. Well. It shouldn't be any way fatal, but in general I agree - we should release 2.2.1 ASAP, really. -- Hasso Tepper
Re: Installing DragonFly
I couldn't use Windows anything - that is banned from my house. Equally, I can't use a Linux fdisk (for instance), because I can't boot the computer at all if the disk is plugged in. If I remove uncable the disk, then I can boot from the DragonFly live DVD (or any other live CD/DVD presumably). But then I can't do anything to the disk because it isn't plugged in. 2009/4/15 Simon 'corecode' Schubert corec...@fs.ei.tum.de: I bet this is the set all bits to one on CHS overflow thing in fdisk. I'd really like to know how we are supposed to handle this (better). Colin, sorry for trashing your computer. I think we are well aware of this issue, but we simply don't know exactly how to deal with it. Could you maybe use window's fdisk to create a large partition on the drive and then report back how the partition table looks like? In this case we could adjust our fdisk so that this won't happen again. thanks simon Colin Adams wrote: What appears to have happened is that in some way it has trashed my disk-drive - I can still get the machine to boot from the live CD, but only if I physically disconnect the hard-disk first. 2009/4/8 Hasso Tepper ha...@estpak.ee: Colin Adams wrote: Well, if that is the case the ISO should not be available for download - there should be a fixed version. Well. It shouldn't be any way fatal, but in general I agree - we should release 2.2.1 ASAP, really. -- Hasso Tepper
Re: Installing DragonFly
You can try booting a linux live cd, then plugging in the hdd after the bios screen, but before the linux kernel starts running. cheers simon Colin Adams wrote: I couldn't use Windows anything - that is banned from my house. Equally, I can't use a Linux fdisk (for instance), because I can't boot the computer at all if the disk is plugged in. If I remove uncable the disk, then I can boot from the DragonFly live DVD (or any other live CD/DVD presumably). But then I can't do anything to the disk because it isn't plugged in. 2009/4/15 Simon 'corecode' Schubert corec...@fs.ei.tum.de: I bet this is the set all bits to one on CHS overflow thing in fdisk. I'd really like to know how we are supposed to handle this (better). Colin, sorry for trashing your computer. I think we are well aware of this issue, but we simply don't know exactly how to deal with it. Could you maybe use window's fdisk to create a large partition on the drive and then report back how the partition table looks like? In this case we could adjust our fdisk so that this won't happen again. thanks simon Colin Adams wrote: What appears to have happened is that in some way it has trashed my disk-drive - I can still get the machine to boot from the live CD, but only if I physically disconnect the hard-disk first. 2009/4/8 Hasso Tepper ha...@estpak.ee: Colin Adams wrote: Well, if that is the case the ISO should not be available for download - there should be a fixed version. Well. It shouldn't be any way fatal, but in general I agree - we should release 2.2.1 ASAP, really. -- Hasso Tepper
Re: Installing DragonFly
Colin Adams wrote: I couldn't use Windows anything - that is banned from my house. Good news, that. Should reduce your long-term rosk of stroke or hear attack. ;-) Equally, I can't use a Linux fdisk (for instance), because I can't boot the computer at all if the disk is plugged in. If I remove uncable the disk, then I can boot from the DragonFly live DVD (or any other live CD/DVD presumably). But then I can't do anything to the disk because it isn't plugged in. Suggestion (from 'bitter' experience) - get your hands on another HDD, (temporarily) make that one the 'primary' and set it up with (at least) one or more *BSD and a low-hassle Linux. My mix of choice is FreeBSD, NetBSD, DFLY Vector Linux 5.9 Std edition. (It often helps to see how, or IF 'the other guy' reads your MBR and disklabel) You should then be able to attach the problematic disk - before or after boot. (Suspicion - is your BIOS set ot boot form it? and if so, can that be changed?) Further - RAID quite aside, FreeBSD atacontrol, DFLY natacontrol have convenient utilities to list, attach/detach, re-scan, ATA chanels and devices et al w/o reboot. fdisk and disklabel / bsdlabel, then newfs should let you re-slice etc to clean up the problematic HDD. Presuming thet HDD is the newer/larger/faster or otherwise more desirable device, you should then be able to reverse the process and do further experimentation on the 'other' less-valuable HDD as a secondary. It can be helpful to have multiple versions of /etc/fstab on each that can be 'cp'ed into place rather than edited to either/both get desired dev ID's to fit detached/swapped situations, and/or do only partial mounting with the rest done manually or by script other-than-fstab. Thereafter, DFLY/FreeBSD boot manager should handle the rest painlessly. You *can* 'get there from here' with a Live CD - but a fully-functional HDD install give you a richer toolset and more flexibility for relatively low cost in time and hardware - especially if the 'other' HDD can be USB-attached. HTH, Bill Hacker 2009/4/15 Simon 'corecode' Schubert corec...@fs.ei.tum.de: I bet this is the set all bits to one on CHS overflow thing in fdisk. I'd really like to know how we are supposed to handle this (better). Colin, sorry for trashing your computer. I think we are well aware of this issue, but we simply don't know exactly how to deal with it. Could you maybe use window's fdisk to create a large partition on the drive and then report back how the partition table looks like? In this case we could adjust our fdisk so that this won't happen again. thanks simon Colin Adams wrote: What appears to have happened is that in some way it has trashed my disk-drive - I can still get the machine to boot from the live CD, but only if I physically disconnect the hard-disk first. 2009/4/8 Hasso Tepper ha...@estpak.ee: Colin Adams wrote: Well, if that is the case the ISO should not be available for download - there should be a fixed version. Well. It shouldn't be any way fatal, but in general I agree - we should release 2.2.1 ASAP, really. -- Hasso Tepper
Re: Installing DragonFly
What appears to have happened is that in some way it has trashed my disk-drive - I can still get the machine to boot from the live CD, but only if I physically disconnect the hard-disk first. 2009/4/8 Hasso Tepper ha...@estpak.ee: Colin Adams wrote: Well, if that is the case the ISO should not be available for download - there should be a fixed version. Well. It shouldn't be any way fatal, but in general I agree - we should release 2.2.1 ASAP, really. -- Hasso Tepper
Re: Installing DragonFly
Colin Adams schrieb: I'm trying to install from the DVD. When i get to the login prompt, I type installer. Now every screen I come to, I get, in addition to the formatted screens, I get: Login incorrect login: Password:/i386 (dfly-live) (ttyv1) login: It appears I need some kind of password to login as installer. I can't see this in the handbook. Yea it's a known bug which has been fixed some time ago. Do the following: 1) Boot the CD 2) Login as root 3) Edit /etc/ttys and remove the ttyv1 entry 4) kill -1 1 5) Logout and relogin as installer Generally I wouldn't recommend to take the release ISO. 2.2 snapshot is better as it has important bug fixes: http://chlamydia.fs.ei.tum.de/pub/DragonFly/snapshots/i386/LATEST-Release-2.2.iso.bz2 Sascha -- http://yoyodyne.ath.cx
Re: Installing DragonFly
Well, if that is the case the ISO should not be available for download - there should be a fixed version. Meanwhile my PC appears to have been broken - I'm not sure if it was caused by DragonFly or a coincidence. I get stuck at an initial display after power-up with an intel logo, And a message: Press TAB to show POST screen, DEL to enter SETUP, ESC to Enter Boot Menu. None of these keys produces any response, except sometimes TAB works. In which case I get a screen telling me the Phoenix AwardBIOS version, and the CPU and IDE channels, and the same options except for TAB. Nothing works (except CTRL_ALT_DEL). :-( :-( 2009/4/8 Sascha Wildner s...@online.de: Colin Adams schrieb: I'm trying to install from the DVD. When i get to the login prompt, I type installer. Now every screen I come to, I get, in addition to the formatted screens, I get: Login incorrect login: Password:/i386 (dfly-live) (ttyv1) login: It appears I need some kind of password to login as installer. I can't see this in the handbook. Yea it's a known bug which has been fixed some time ago. Do the following: 1) Boot the CD 2) Login as root 3) Edit /etc/ttys and remove the ttyv1 entry 4) kill -1 1 5) Logout and relogin as installer Generally I wouldn't recommend to take the release ISO. 2.2 snapshot is better as it has important bug fixes: http://chlamydia.fs.ei.tum.de/pub/DragonFly/snapshots/i386/LATEST-Release-2.2.iso.bz2 Sascha -- http://yoyodyne.ath.cx
Re: Installing DragonFly
Colin Adams wrote: Well, if that is the case the ISO should not be available for download - there should be a fixed version. Well. It shouldn't be any way fatal, but in general I agree - we should release 2.2.1 ASAP, really. -- Hasso Tepper
Re: Installing DragonFly
Sascha Wildner wrote: Colin Adams schrieb: I'm trying to install from the DVD. When i get to the login prompt, I type installer. Now every screen I come to, I get, in addition to the formatted screens, I get: Login incorrect login: Password:/i386 (dfly-live) (ttyv1) login: It appears I need some kind of password to login as installer. I can't see this in the handbook. Yea it's a known bug which has been fixed some time ago. Do the following: 1) Boot the CD 2) Login as root 3) Edit /etc/ttys and remove the ttyv1 entry 4) kill -1 1 5) Logout and relogin as installer Generally I wouldn't recommend to take the release ISO. 2.2 snapshot is better as it has important bug fixes: http://chlamydia.fs.ei.tum.de/pub/DragonFly/snapshots/i386/LATEST- Release-2.2.iso.bz2 It would be nice to build and distribute snapshots of the USB-stick version as well. IMHO this is the easiest and most economical way to try out a development version of DragonFly. Regards, Michael
Re: Installing DragonFly
: :Colin Adams wrote: : Well, if that is the case the ISO should not be available for download : - there should be a fixed version. : :Well. It shouldn't be any way fatal, but in general I agree - we should :release 2.2.1 ASAP, really. : : :-- :Hasso Tepper I'd love to but I'm so busy I haven't had time to cherry-pick the commits back into the 2.2 tree. If someone would like to do that bit we could roll out 2.2.1 more quickly. With the libc major rev change we can't just sync the entire main development branch to 2.2. -Matt Matthew Dillon dil...@backplane.com
Re: Installing DragonFly head on Hammer root ?
:Hi, : :* [EMAIL PROTECTED] wrote: : The script doesn't seem to work. Firstly I had to change ad6 to ad4, and : remove a line saying exit 1 after the 10 second warning. The partitions : get created but it seems that most of the important stuff doesn't get : cpduped over as for example the /boot partition ONLY has 1 file in it : (loader.conf) and the kernel and everything else is missing, theres whole : lot of other stuff missing too. I tried the process twice, with the same : results each time. : :Sorry, forget to mention that you have to remove the exit line. :Furthermore I had to add a cpdup line to copy /usr over. But with these :two modifications you should be fine. : :Regards : : Matthias I've noticed cpdup apparently not working properly when run from that script too. I'm not sure if it is cpdup itself or if it is the cd9660 ISO filesystem. Since I don't have problems using cpdup otherwise I am guessing that there's something in the cd9660 ISO filedsystem code that is causing incomplete copies to occur without generating errors or warnings. I have no had time to track down the problem myself. -Matt Matthew Dillon [EMAIL PROTECTED]
Installing DragonFly head on Hammer root ?
Is it yet possible or is it coming? 1) Does the installer support selection of file system. I need to install a DragonFly OS and i definately need at least /home and /usr on Hammer, but I want to do it during the install, not complicatedly after the install. Can someone show me how? 2) is /boot now on separate partition? Thanks, Petr
Installing DragonFly 2.0
Hi, First of all, congratulations for this new release of DragonFly! I've tried installing on my desktop PC but I encountered some errors while adding software packages (checked all) but suddenly it prompts for Packages were successfully installed!. Below are the errors I've encountered. /usr/pkg/bin/pkg_info: not found /usr/pkg/bin/pkg_info: not found /usr/pkg/bin/pkg_info: not found /usr/pkg/bin/pkg_info: not found /usr/pkg/bin/pkg_info: not found /usr/pkg/bin/pkg_info: not found ,- Executing `/usr/pkg/bin/pkg_create -b pkgdb.byfile.db /mnt/tmp/pkgdb.byfile.db.tgz' | /usr/pkg/bin/pkg_create: not found `- Exit status: 127 [pressing Skip button] ,- Executing `/usr/sbin/chroot /mnt/ /usr/pkg/bin/pkg_add /tmp/pkgdb.byfile. b.tgz' | chroot: /usr/pkg/bin/pkg_add: No such file or directory `- Exit status: 1 [pressing Skip button] ,- Executing `/bin/rm /mnt/tmp/pkgdb.byfile.db.tgz' | rm: /mnt/tmp/pkgdb.byfile.db.tgz: No such file or directory `- Exit status: 1 Packages were successfully installed! - I also have the dmesg of my desktop PC which is an AMD Sempron (32-bit) Copyright (c) 2003-2008 The DragonFly Project. Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. DragonFly 2.0.0-RELEASE #1: Sat Jul 19 14:34:49 PDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Calibrating clock(s) ... TSC clock: 1666710718 Hz, i8254 clock: 1197755 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: AMD Sempron(tm) 2400+ (1639.73-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x681 Stepping = 1 Features=0x380a97bFPU,VME,PSE,TSC,MSR,PAE,CX8,SEP,PGE,CMOV,MMX,FXSR,SSE AMD Features=0x40AMIE Data TLB: 32 entries, fully associative Instruction TLB: 16 entries, fully associative L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L2 internal cache: 256 kbytes, 64 bytes/line, 1 lines/tag, 16-way associative real memory = 134152192 (131008K bytes) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x007c8000 - 0x07fd, 125927424 bytes (30744 pages) avail memory = 11918 (116352K bytes) pnpbios: Found PnP BIOS data at 0xc00f3c30 pnpbios: Entry = f:43ca Rev = 1.0 Other BIOS signatures found: Preloaded elf kernel /kernel at 0xc079b000. Preloaded elf module /modules/acpi.ko at 0xc079b1e8. crypto: crypto core wlan: 802.11 Link Layer md0: Malloc disk Math emulator present pci_open(1):mode 1 addr port (0x0cf8) is 0x805c pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=71928086) pcibios: No call entry point pcibios: No call entry point ACPI: RSDP @ 0x0xf52c0/0x0014 (v 0 ACPIAM) ACPI: RSDT @ 0x0x7ff/0x002C (v 1 A M I OEMRSDT 0x08000314 MSFT 0x0097) ACPI: FACP @ 0x0x7ff0200/0x0081 (v 2 A M I OEMFACP 0x08000314 MSFT 0x0097) ACPI: DSDT @ 0x0x7ff0300/0x209B (v 1 AMIBI AMIBI002 0x0002 INTL 0x02002026) ACPI: FACS @ 0x0x7fff000/0x0040 ACPI: OEMB @ 0x0x7fff040/0x0053 (v 1 A M I OEMBIOS 0x08000314 MSFT 0x0097) npx0.nexus0.root0 npx0: math processor [tentative] on motherboard npx0: INT 16 interface Using MMX optimized bcopy/copyin/copyout npx0: math processor [attached!] on motherboard acpi0.nexus0.root0 acpi0: A M I OEMRSDT [tentative] on motherboard acpi0: Power Button (fixed) Warning: ACPI is disabling APM's device. You can't run both AcpiOsDerivePciId: bus 0 dev 7 func 0 ACPI timer looks BAD min = 29, max = 2495, width = 2466 ACPI timer looks BAD min = 29, max = 69088, width = 69059 ACPI timer looks BAD min = 29, max = 3476, width = 3447 ACPI timer looks BAD min = 29, max = 9118, width = 9089 ACPI timer looks BAD min = 29, max = 38724, width = 38695 ACPI timer looks BAD min = 29, max = 3777, width = 3748 ACPI timer looks BAD min = 28, max = 81415, width = 81387 ACPI timer looks BAD min = 29, max = 6447, width = 6418 ACPI timer looks BAD min = 29, max = 5416, width = 5387 ACPI timer looks BAD min = 28, max = 78864, width = 78836 acpi_timer0.acpi0.nexus0.root0 acpi_timer0: 24-bit timer at 3.579545MHz [tentative] port 0x408-0x40b on acpi0 acpi_timer0: 24-bit timer at 3.579545MHz [attached!] port 0x408-0x40b on acpi0 cpu0.acpi0.nexus0.root0 cpu0: ACPI CPU [tentative] on acpi0 cpu0: ACPI CPU [attached!] on acpi0 atkbdc0.acpi0.nexus0.root0 atkbdc0: Keyboard controller (i8042) [tentative] port 0x64,0x60 irq 1 on acpi0 atkbd0.atkbdc0.acpi0.nexus0.root0 atkbd0: AT Keyboard [tentative] flags 0x1 irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) kbd0 at atkbd0 kbd0: atkbd0, AT
Re: Installing DragonFly 2.0
Archimedes Gaviola schrieb: First of all, congratulations for this new release of DragonFly! I've tried installing on my desktop PC but I encountered some errors while adding software packages (checked all) but suddenly it prompts for Packages were successfully installed!. Below are the errors I've encountered. I don't think adding packages from the installer works (it probably still assumes that we're using FreeBSD ports). Try pkg_radd(1) instead (note the 'r'). Sascha -- http://yoyodyne.ath.cx
Re: Installing DragonFly 2.0
Sascha Wildner schrieb: I don't think adding packages from the installer works (it probably still assumes that we're using FreeBSD ports). I take that back. The path for the package tools was wrong. I've changed it in HEAD and the 2.0 branch. Although I'm not sure if there aren't other issues in the installer wrt installing packages. If you want you can try again using http://chlamydia.fs.ei.tum.de/pub/DragonFly/snapshots/i386/LATEST-Release-2.0.iso.bz2 in ~48h or so (once the new 2.0 snapshot has been built). Sascha -- http://yoyodyne.ath.cx
Re: Installing DragonFly 2.0
Okay Sascha thanks! I'm going to re-install my desktop once that build is available. Just let me know. On 7/22/08, Sascha Wildner [EMAIL PROTECTED] wrote: Sascha Wildner schrieb: I don't think adding packages from the installer works (it probably still assumes that we're using FreeBSD ports). I take that back. The path for the package tools was wrong. I've changed it in HEAD and the 2.0 branch. Although I'm not sure if there aren't other issues in the installer wrt installing packages. If you want you can try again using http://chlamydia.fs.ei.tum.de/pub/DragonFly/snapshots/i386/LATEST-Release-2.0.iso.bz2 in ~48h or so (once the new 2.0 snapshot has been built). Sascha -- http://yoyodyne.ath.cx
Re: Building/Installing DragonFly from within FreeBSD
Can anybody confirm that this still works? When I try to upgrade a FreeBSD 4.9 system to DragonFly 1.2 following the procedure outlined in this document, make buildworld fails in /usr/src/usr.bin/mklocale. What error do you get? === usr.bin/mklocale (bootstrap-tools) /usr/obj/usr/src/btools_i386/usr/src/usr.bin/mklocale created for /usr/src/usr.bin/mklocale yacc -d /usr/src/usr.bin/mklocale/yacc.y cp y.tab.c yacc.c lex -t /usr/src/usr.bin/mklocale/lex.l lex.c cp /usr/src/usr.bin/mklocale/../../include/runetype.h runetype.h grep '#define._CTYPE_' /usr/src/usr.bin/mklocale/../../include/ctype.h ctype.h rm -f .depend mkdep -f .depend -a-I. -I/usr/src/usr.bin/mklocale yacc.c lex.c In file included from /usr/src/usr.bin/mklocale/yacc.y:54: runetype.h:46: sys/stdint.h: No such file or directory In file included from /usr/src/usr.bin/mklocale/ldef.h:40, from /usr/src/usr.bin/mklocale/lex.l:46: runetype.h:46: sys/stdint.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/usr.bin/mklocale. *** Error code 1 Stop in /usr/src. *** Error code 1
Re: Building/Installing DragonFly from within FreeBSD
Matthew Dillon wrote: I really doubt that you can build the dragonfly kernel from inside FreeBSD any more, short of booting a DragonFly CD in a virtual machine and building it there. Hmm, but he's trying FreeBSD 4 - DragonFly 1.2, something which seems to have been working at some point. Strange.. Sascha -- http://yoyodyne.ath.cx
Re: Building/Installing DragonFly from within FreeBSD
:Hmm, but he's trying FreeBSD 4 - DragonFly 1.2, something which seems :to have been working at some point. : :Strange.. : :Sascha : :-- :http://yoyodyne.ath.cx It's possible that the CVS surgery we've done over the years has messed up 1.2 with regards to building from FreeBSD. Even more likely, changes in FreeBSD have probably made portions of the old 1.2 build incompatible. Some of the FreeBSD folks keep refering to DragonFly as something relative to FreeBSD-4 and that probably causes a lot of confusion. DragonFly was forked from FreeBSD-4 a long time ago, but holds very little in common with it these days. -Matt Matthew Dillon [EMAIL PROTECTED]
Re: Building/Installing DragonFly from within FreeBSD
:Can anybody confirm that this still works? When I try to upgrade a :FreeBSD 4.9 system to DragonFly 1.2 following the procedure outlined in :this document, make buildworld fails in /usr/src/usr.bin/mklocale. :I would like to go this route to migrate some production servers that :are currently running FBSD 4.11 to DragonFly, if possible. : :Thanks! : :Andre I really doubt that you can build the dragonfly kernel from inside FreeBSD any more, short of booting a DragonFly CD in a virtual machine and building it there. -Matt Matthew Dillon [EMAIL PROTECTED]
Re: Building/Installing DragonFly from within FreeBSD
Sascha Wildner wrote: I would like to go this route to migrate some production servers that are currently running FBSD 4.11 to DragonFly, if possible. Yeah, some kind of more or less convenient upgrade path for FreeBSD 4 users would be nice to have. Where is the big difference between doing a buildworld, buildkernel, installkernel, installworld or doing a binary update? Maybe we should encourage people to do this instead? I even thought the installer had an option. If not, just copying over /kernel /modules /usr /bin/sbin and updating /etc should do it as well, right? 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: Building/Installing DragonFly from within FreeBSD
On Sat, February 16, 2008 2:27 pm, Sascha Wildner wrote: Andre LeClaire wrote: I would like to go this route to migrate some production servers that are currently running FBSD 4.11 to DragonFly, if possible. Yeah, some kind of more or less convenient upgrade path for FreeBSD 4 users would be nice to have. This seems somewhat bizarre, but: would we be able to apply a Depenguinator style strategy? http://www.daemonology.net/blog/2008-01-29-depenguinator-2.0.html
Building/Installing DragonFly from within FreeBSD
Hi there, though it seems to be supported to build (some releases) of DragonFly on (some releases) of FreeBSD and cross-install them, I can't get it to work. I tried building 1.0, 1.2, 1.4, 1.6 and 1.10 on 4.11, 5.5, 6.0 and 8.0. They all quickly die in buildworld during bootstrap-tools phase. Even plastering over some obvious differences, this seems to be not possible with the given releases. Some background: I'm trying to debug SCSI/CAM/cd(4) on FreeBSD, where my external DVD drive will not read retail DVDs (yes, burned DVDs are fine, please don't ask). And since this worked with DFly 1.8 last time I tried, I'm now in the progress of doing a binary search between, well FreeBSD 4.x and DFly 1.8 to nail down the commit that made this possible in DFly. (right now, I'm blaming GEOM for this no longer working in FreeBSD). I'm trying to install this on a headless machine, using serial consoles only. So popping in an install CD and using monitor/keyboard to install is not that easy. Anyway, so I downloaded the 1.0A ISO and extracted it to ad2s1a, placed an /etc/rc.conf and /etc/fstab there, removed /boot/loader.conf and wanted to boot this. It loads /boot/loader, but when loading (decoding?) the kernel, it hangs solid. I tried without ACPI and safe mode, doesn't help. What am I missing? Is boot, loader, or kernel from the 1.0A ISO not able to boot a kernel from the hard disk. Or is the serial console fucking things up? This is how far I get (using grub) root (hd1,1,a) Filesystem type is ffs, partition type 0xa5 kernel /boot/loader -Dh [FreeBSD-a.out, loadaddr=0x20, text=0x1000, data=0x2d000, bss=0x0, entry =0x20] Console: serial port Console: null port BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS drive D: is disk2 BIOS 640kB/326644kB available memory DragonFly/i386 bootstrap loader, Revision 1.1 (root@, Wed Jul 1 17:17:37 GMT 2004) Loading /boot/defaults/loader.conf /kernel text=0x386a50 data=0x5c8b4+0x3626c syms=[0x4+0x4bf40+0x4+0x5b104] Loading /boot/defaults/loader.conf | menu /modules/acpi.ko text=0x477c0 data=0x2034+0xc98 syms=[0x4+0x6e60+0x4+0x8bfc] - And then it's dead Cheers, Ulrich Spoerlein -- It is better to remain silent and be thought a fool, than to speak, and remove all doubt.
Re: Building/Installing DragonFly from within FreeBSD
Ulrich Spoerlein wrote: /modules/acpi.ko text=0x477c0 data=0x2034+0xc98 syms=[0x4+0x6e60+0x4+0x8bfc] - And then it's dead Are you sure (sure sure) it is dead? I had the situation that it would simply not use the console, and at some point the Login: prompt would show up (maybe won't happen with a serial console). 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: Building/Installing DragonFly from within FreeBSD
On Thu, February 14, 2008 3:08 pm, Ulrich Spoerlein wrote: Hi there, though it seems to be supported to build (some releases) of DragonFly on (some releases) of FreeBSD and cross-install them, I can't get it to work. I tried building 1.0, 1.2, 1.4, 1.6 and 1.10 on 4.11, 5.5, 6.0 and 8.0. They all quickly die in buildworld during bootstrap-tools phase. Even plastering over some obvious differences, this seems to be not possible with the given releases. There's an existing guide: http://www.dragonflybsd.org/docs/upgrade-freebsd.shtml Though it sounds like you've done close to what it says already. The installer supports headless installs. You need to create a file called 'pfi.conf' (for Pre-Flight Installer) and put it on a USB thumb drive or floppy disk or something else that can be mounted and searched. There's an example file at: src/nrelease/installer/etc/defaults/pfi.conf I haven't tried this myself, but it should work.
Re: Building/Installing DragonFly from within FreeBSD
On Thu, 14.02.2008 at 22:16:38 +0100, Simon 'corecode' Schubert wrote: Ulrich Spoerlein wrote: /modules/acpi.ko text=0x477c0 data=0x2034+0xc98 syms=[0x4+0x6e60+0x4+0x8bfc] - And then it's dead Are you sure (sure sure) it is dead? I had the situation that it would simply not use the console, and at some point the Login: prompt would show up (maybe won't happen with a serial console). Guess I'll have to try with a real monitor then. But I switched on ttyd0 in /etc/ttys and nothing happened for like 5-8 minutes. Also no disk activity ... Perhaps I should try the 1.2 Release instead. Cheers, Ulrich Spoerlein -- It is better to remain silent and be thought a fool, than to speak, and remove all doubt.
Re: Installing Dragonfly 1.8 hangs BIOS completly
Rauf Kuliyev wrote: Hi, I bet it is IBM ThinkPad. You can find additional information here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/install.html#BOOT-ON-THINKPAD No it isn't a ThinkPad, it's a Bullman (noname), similar to an Acer. FreeBSD runs without change to the bootblock. NetBSD 3.1 runs as well, but during install I have to specify the disk geometry. This night I installed DragonFly 1.4.0-RELEASE (via dfly.iso) on it, and it works perfectly! Strange is that NetBSD seems to use a different disk geometry than DragonFly 1.4, and DragonFly 1.8 uses a different one as well! uname DragonFly 1.4.0-RELEASE fdisk in-core disklabel geometry cylinders=20672 heads=45 sectors/track=63 (2835 blks/cyl) BIOS geometry: same as above sysid 165 start 63, size 58605057 (28615 MB) beg: cyl 0 head 1 sector 1 end: cyl 191 head 44 sector 63 Strange, when I boot the DragonFly 1.8.0-RELEASE installer (after installation of 1.4 or modifying the harddisk) I get: uname DragonFly 1.8.0-RELEASE fdisk cylinders=58140 heads=16 sectors/track=63 (1008 blks/cyl) I don't know about the issues involved with different disk geometries, but as this is the only difference I see between DragonFly 1.4 and 1.8, maybe this might be a problem? Regards, Michael Regards, Rauf On 2/19/07, Michael Neumann [EMAIL PROTECTED] wrote: Hi, Just a few minutes ago, I installed Dragonfly 1.8 onto my laptop. Then I rebooted, and the BIOS hung up completely after showing that it detected the harddisk and cdrom. I powered down and tried again, but that didn't worked either. I couldn't even boot a CD or anything else or couldn't even enter the BIOS setup. The only thing that worked was to remove the harddisk physically and then pluging it in a few seconds after the BIOS crossed the detection of the devices. Using this method, I booted the Dragonfly installer cd and used the disk tools to wipe out the beginning of the harddisk. Then I rebooted again and voila, I could boot normally (without removing the harddisk). Puh! Now I tried a second time to install Dragonfly 1.8, but after I reboot the BIOS hangs again! I know that the BIOS should not hang up itself, but on the other hand that didn't happen with any other operating system I installed on my laptop (FreeBSD, NetBSD, DragonFly 1.6). So I think there is something wrong in the 1.8 version. Any hints? Regards, Michael
Re: Installing Dragonfly 1.8 hangs BIOS completly
Michael Neumann wrote: I don't know about the issues involved with different disk geometries, but as this is the only difference I see between DragonFly 1.4 and 1.8, maybe this might be a problem? Possibly not. Try using fdisk with -C. Your BIOS might stumble upon these values. 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 / \ signature.asc Description: OpenPGP digital signature
Re: Installing Dragonfly 1.8 hangs BIOS completly
Simon 'corecode' Schubert wrote: Michael Neumann wrote: I don't know about the issues involved with different disk geometries, but as this is the only difference I see between DragonFly 1.4 and 1.8, maybe this might be a problem? Possibly not. Try using fdisk with -C. Your BIOS might stumble upon these values. Thank you very much! That did the trick! I didn't knew how easy it is to install Dragonfly without the installer ;-) Regards, Michael
Installing Dragonfly 1.8 hangs BIOS completly
Hi, Just a few minutes ago, I installed Dragonfly 1.8 onto my laptop. Then I rebooted, and the BIOS hung up completely after showing that it detected the harddisk and cdrom. I powered down and tried again, but that didn't worked either. I couldn't even boot a CD or anything else or couldn't even enter the BIOS setup. The only thing that worked was to remove the harddisk physically and then pluging it in a few seconds after the BIOS crossed the detection of the devices. Using this method, I booted the Dragonfly installer cd and used the disk tools to wipe out the beginning of the harddisk. Then I rebooted again and voila, I could boot normally (without removing the harddisk). Puh! Now I tried a second time to install Dragonfly 1.8, but after I reboot the BIOS hangs again! I know that the BIOS should not hang up itself, but on the other hand that didn't happen with any other operating system I installed on my laptop (FreeBSD, NetBSD, DragonFly 1.6). So I think there is something wrong in the 1.8 version. Any hints? Regards, Michael
Re: Installing Dragonfly 1.8 hangs BIOS completly
Hi, I bet it is IBM ThinkPad. You can find additional information here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/install.html#BOOT-ON-THINKPAD Regards, Rauf On 2/19/07, Michael Neumann [EMAIL PROTECTED] wrote: Hi, Just a few minutes ago, I installed Dragonfly 1.8 onto my laptop. Then I rebooted, and the BIOS hung up completely after showing that it detected the harddisk and cdrom. I powered down and tried again, but that didn't worked either. I couldn't even boot a CD or anything else or couldn't even enter the BIOS setup. The only thing that worked was to remove the harddisk physically and then pluging it in a few seconds after the BIOS crossed the detection of the devices. Using this method, I booted the Dragonfly installer cd and used the disk tools to wipe out the beginning of the harddisk. Then I rebooted again and voila, I could boot normally (without removing the harddisk). Puh! Now I tried a second time to install Dragonfly 1.8, but after I reboot the BIOS hangs again! I know that the BIOS should not hang up itself, but on the other hand that didn't happen with any other operating system I installed on my laptop (FreeBSD, NetBSD, DragonFly 1.6). So I think there is something wrong in the 1.8 version. Any hints? Regards, Michael
Re: Installing Dragonfly 1.8 hangs BIOS completly
Michael Neumann wrote: Hi, Just a few minutes ago, I installed Dragonfly 1.8 onto my laptop. Then I rebooted, and the BIOS hung up completely after showing that it detected the harddisk and cdrom. I powered down and tried again, but that didn't worked either. I couldn't even boot a CD or anything else or couldn't even enter the BIOS setup. The only thing that worked was to remove the harddisk physically and then pluging it in a few seconds after the BIOS crossed the detection of the devices. Using this method, I booted the Dragonfly installer cd and used the disk tools to wipe out the beginning of the harddisk. Then I rebooted again and voila, I could boot normally (without removing the harddisk). Puh! Now I tried a second time to install Dragonfly 1.8, but after I reboot the BIOS hangs again! I know that the BIOS should not hang up itself, but on the other hand that didn't happen with any other operating system I installed on my laptop (FreeBSD, NetBSD, DragonFly 1.6). So I think there is something wrong in the 1.8 version. Any hints? Regards, Michael Welll... you have told us *which* laptop, (Make, model, age, CPU, whether you have APM, ACPI, enabled/not, if storage devices are autodetecting, swapped, set to boot out-of-order, etc. any and all of that info might help. .and nothing attached to a serial port while booting, please. Bill
Re: Warning about installing DragonFly and FreeBSD to same disk
Chris Pressey wrote: Because DragonFly and FreeBSD have the same partition id (165,) FreeBSD's installer will see the DragonFly partition as a FreeBSD slice. And, *even if you don't set up any BSD partitions on the DragonFly partition*, the installer will erase the DragonFly partition's disklabel. Could You tell, what was the version of FreeBSD, which caused such a problem, and if this problem occur rather often or always for that version? The fact is that I've installed FreeBSD 4.9 on a drive with DragonFly 1.2 and boot them with DragonFly bootloader with no extra manipulations.
Re: Warning about installing DragonFly and FreeBSD to same disk
On Fri, 26 Aug 2005 10:10:14 +0300 Eugene [EMAIL PROTECTED] wrote: Chris Pressey wrote: Because DragonFly and FreeBSD have the same partition id (165,) FreeBSD's installer will see the DragonFly partition as a FreeBSD slice. And, *even if you don't set up any BSD partitions on the DragonFly partition*, the installer will erase the DragonFly partition's disklabel. Could You tell, what was the version of FreeBSD, which caused such a problem, and if this problem occur rather often or always for that version? This was a FreeBSD 6.0-CURRENT snapshot from July. I've only tried it once, and it happened once, so you could say it happens 100% of the time :) I did try the workaround, successfully - I set the type of my DragonFly partition to 17 (chosen randomly) in FreeBSD's partition editor, before installing FreeBSD on the other partition, and FreeBSD didn't touch it. The fact is that I've installed FreeBSD 4.9 on a drive with DragonFly 1.2 and boot them with DragonFly bootloader with no extra manipulations. That's not too surprising, I don't think; 4.9 is similar enough to DragonFly that it probably recognizes and preserves the disklabel while installing. I really can't say why booting (which, I should be clear, is a *different* problem from what I was describing) fails to work smoothly. It fails to work smoothly for me, even just booting two DragonFly partitions - I have to manually enter ufs:ad2s1a or ufs:ad2s2a at the mountroot prompt. But I assumed that was because I'm using the NetBSD bootloader, which apparently doesn't communicate which partition we were booted from to the subsequent boot stages. -Chris
Warning about installing DragonFly and FreeBSD to same disk
Here's something I found out the hard way last night: If you already have DragonFly on a disk (say partition 1) and you want to install FreeBSD on that disk (say partition 2), you have to be very careful. Because DragonFly and FreeBSD have the same partition id (165,) FreeBSD's installer will see the DragonFly partition as a FreeBSD slice. And, *even if you don't set up any BSD partitions on the DragonFly partition*, the installer will erase the DragonFly partition's disklabel. I haven't tested any workarounds yet, but I suspect that marking the DragonFly partition with some other partition id (like MS-DOS) before installing, and marking it back after installing, would be enough to trick FreeBSD's installer into ignoring it. -Chris
Re: Warning about installing DragonFly and FreeBSD to same disk
On August 25, 2005 12:45 pm, Rob Andrews wrote: [25-Aug-2005 17:59.00 (BST) / Chris Pressey] I haven't tested any workarounds yet, but I suspect that marking the DragonFly partition with some other partition id (like MS-DOS) before installing, and marking it back after installing, would be enough to trick FreeBSD's installer into ignoring it. grub has an option parttype that can change the partition type before proceeding with the boot process. I used it to change freebsd's partition type back to 0 and dragonfly's to 165 before booting dragonfly, and vice versa for freebsd. Popping this into the menu file will do the grunt for you at boot time. If you install the loader to the FreeBSD and DragonFly partition boot sectors and skip the MBR loader installation you can install grub and have it chain load the boot loader from the boot sector. Be warned, grub may not support the ufs filesystem you choose to install it upon. If grub can't read the stage2 files from your filesystem, keep an ext2 or FAT filesystem somewhere. GRUB 0.9.5 and above supports UFS1 and UFS2. And you don't need to use chainloader to load the BSD loader. You just set the kernel option in GRUB to /boot/loader. I used GRUB 0.9.5 to tripleboot FreeBSD 4.8-4.11 and 5.2.1-6.0B2, and Windows XP (using chainloader and makeactive for XP) without issues. Haven't tried with DragonFlyBSD, but it should work. -- Freddie Cash, CCNT CCLPHelpdesk / Network Support Tech. School District 73 (250) 377-HELP [377-4357] [EMAIL PROTECTED]
Re: Warning about installing DragonFly and FreeBSD to same disk
fcash-ml wrote @ Thu, 25 Aug 2005 12:58:39 -0700: On August 25, 2005 12:45 pm, Rob Andrews wrote: [25-Aug-2005 17:59.00 (BST) / Chris Pressey] Be warned, grub may not support the ufs filesystem you choose to install it upon. If grub can't read the stage2 files from your filesystem, keep an ext2 or FAT filesystem somewhere. GRUB 0.9.5 and above supports UFS1 and UFS2. And you don't need to use chainloader to load the BSD loader. You just set the kernel option in GRUB to /boot/loader. I used GRUB 0.9.5 to tripleboot FreeBSD 4.8-4.11 and 5.2.1-6.0B2, and Windows XP (using chainloader and makeactive for XP) without issues. Haven't tried with DragonFlyBSD, but it should work. Works here. Andy
Re: Warning about installing DragonFly and FreeBSD to same disk
[25-Aug-2005 20:58.39 (BST) / Freddie Cash] GRUB 0.9.5 and above supports UFS1 and UFS2. And you don't need to use chainloader to load the BSD loader. You just set the kernel option in GRUB to /boot/loader. This is where my knowledge of grub booting FreeBSD DragonFly natively break doing - I was booting a ufs2 filesystem with an older non-ufs2 capable grub some time ago, so all I knew was that you'd have to use chainloader in the absence of being able to spawn /boot/loader natively. Good to see it's got ufs2 support.
