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]
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: 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
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
