Re: Cannot boot FreeBSD (8.0) from USB stick (Dell Inspiron 9400)
Fbsd1 schrieb: Christoph Kukulies wrote: I don't know why you shout. (?) Not shouting, just making my inserted comments visible within the old post as in different from bottom or top posting. Ok, writing in capitals is normally treated as shouting (see "netiquette") or only allowed when someone is disabled by eyes. Just write your comments inbetween. I and others will know how to read :) -- Christoph ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Cannot boot FreeBSD (8.0) from USB stick (Dell Inspiron 9400)
In freebsd-questions Digest, Vol 294, Issue 12, Message 1 On Fri, 22 Jan 2010 18:59:00 +0100 Christoph Kukulies wrote: > Here is some more info: > > The file I copied to the USB stick was > > ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/8.0/8.0-RELEASE-i386-memstick.img > > Actually, I don't remember how I got the image to the USB stick. I > believe I used a free tool from HP > from within Windows XP. This is likely your problem. As on the release page referring to this image (but substituting i386 for amd64) it should have been made using: # dd if=8.0-RELEASE-i386-memstick.img of=/dev/da0 bs=10240 conv=sync This works; I've no idea what a HP windows tool might do instead, though your fdisk below may offer clues; certainly the cylinders/heads/sectors arrangement seems wrong for a disk made from this image by dd as above. > kernel messages at the time usb stick is inserted: > ugen4.3: at usbus4 > umass0: on usbus4 > umass0: SCSI over Bulk-Only; quirks = 0x > umass0:1:0:-1: Attached to scbus1 > (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 > (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error > (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition > (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 > (probe0:umass-sim0:0:0:0): Not ready to ready change, medium may have > changed > (probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data) > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Removable Direct Access SCSI-0 device > da0: 40.000MB/s transfers > da0: 1921MB (3935000 512 byte sectors: 255H 63S/T 244C) > GEOM: da0: media size does not match label. While mine is only a 1GB stick, it shows an entirely different geometry, with 1MB per cylinder. da0: 967MB (1981440 512 byte sectors: 64H 32S/T 967C) > # fdisk /dev/da0 > *** Working on device /dev/da0 *** > parameters extracted from in-core disklabel are: > cylinders=244 heads=255 sectors/track=63 (16065 blks/cyl) Here instead fdisk /dev/da0 sees: cylinders=967 heads=64 sectors/track=32 (2048 blks/cyl) > # fdisk /dev/da0 > *** Working on device /dev/da0 *** > parameters extracted from in-core disklabel are: > cylinders=244 heads=255 sectors/track=63 (16065 blks/cyl) > > parameters to be used for BIOS calculations are: > cylinders=244 heads=255 sectors/track=63 (16065 blks/cyl) > > Media sector size is 512 > Warning: BIOS sector numbering starts with sector 1 > Information from DOS bootblock is: > The data for partition 1 is: > > The data for partition 2 is: > > The data for partition 3 is: > > The data for partition 4 is: > sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) > start 0, size 5 (24 Meg), flag 80 (active) > beg: cyl 0/ head 0/ sector 1; > end: cyl 1023/ head 254/ sector 63 The reason fdisk (bogusly) shows this as slice 4 is that this image is so-called 'dangerously dedicated' to FreeBSD, ie it is an unsliced disk, and needs to be mounted as /dev/da0a (not da0s1a or da0s4a). It contains a bsdlabel allocating 16 sectors for boot code (/boot/boot1 and /boot/boot2) with partition 'a' beginning at offset 16 (8KB). It boots just fine (though slowly as a 4x CDROM :) on my 2002 IBM Thinkpad T23 with only USB 1.0, after having promoted it in the BIOS boot order. I suggest remaking the image using dd exactly as above and trying that. cheers, Ian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Cannot boot FreeBSD (8.0) from USB stick (Dell Inspiron 9400)
Christoph Kukulies wrote: Here is some more info: The file I copied to the USB stick was ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/8.0/8.0-RELEASE-i386-memstick.img Actually, I don't remember how I got the image to the USB stick. I believe I used a free tool from HP from within Windows XP. I will try out your method below now. kernel messages at the time usb stick is inserted: ugen4.3: at usbus4 umass0: on usbus4 umass0: SCSI over Bulk-Only; quirks = 0x umass0:1:0:-1: Attached to scbus1 (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 (probe0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed (probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data) da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 1921MB (3935000 512 byte sectors: 255H 63S/T 244C) GEOM: da0: media size does not match label. # # # fdisk /dev/da0 *** Working on device /dev/da0 *** parameters extracted from in-core disklabel are: cylinders=244 heads=255 sectors/track=63 (16065 blks/cyl) /tmp/l12: unmodified, readonly: line 1 kernel messages at the time usb stick is inserted: ugen4.3: at usbus4 umass0: on usbus4 umass0: SCSI over Bulk-Only; quirks = 0x umass0:1:0:-1: Attached to scbus1 (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 (probe0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed (probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data) da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 1921MB (3935000 512 byte sectors: 255H 63S/T 244C) GEOM: da0: media size does not match label. # # # fdisk /dev/da0 *** Working on device /dev/da0 *** parameters extracted from in-core disklabel are: cylinders=244 heads=255 sectors/track=63 (16065 blks/cyl) parameters to be used for BIOS calculations are: cylinders=244 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 0, size 5 (24 Meg), flag 80 (active) beg: cyl 0/ head 0/ sector 1; end: cyl 1023/ head 254/ sector 63 # -- Christoph The dd command is what is used to copy the memstick.img to USB stick. The memstick.img is created with the dd command so no compression done. It has fixit included and is 3 times larger than the disc-1 iso file. Thats why I download the disc-1 iso and run the script to build the img on USB stick. So much faster this way. So I see that both usb sticks you are using are revision rev 2.00/1.10. But the stick that boots on your desktop will not boot on the laptop. And the stick that boots on the laptop will not boot on the desktop. Very strange indeed. This indicates that the pc bios are playing a big part in which USB stick it recognizes as bootable. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Cannot boot FreeBSD (8.0) from USB stick (Dell Inspiron 9400)
Christoph Kukulies wrote: I don't know why you shout. (?) Not shouting, just making my inserted comments visible within the old post as in different from bottom or top posting. Fbsd1 schrieb: Christoph Kukulies wrote: Fbsd1 schrieb: Christoph Kukulies wrote: I installed FreeBSD 8.0 on an USB-stick and was able to boot it on my Desktop PC and install 8.0 from it. DO YOU MEAN YOU INSTALLED THE 8.0 ISO ON A USB STICK. BOOTED FROM IT AS INSTALL SOURCE AND INSTALLED 8.0 ON A DESKTOP PC TO THE MOTHERBOARD CABLED HARD DRIVE??? OR DO YOU MEAN YOU INSTALLED 8.0 ON A DESKTOP PC TO ANOTHER USB STICK??? The former, I copied the 8.0 iso image to an USB stick, booted it and installed it to the desktop PCs hard drive. That was one story. The other point is, that I now wanted to plug this USB stick into my Dell inspiron and install FreeBSD in the same manner to a free partition on my notebooks hard drive. Now I plugged the same stick into my Dell Inspiron 9400 and the USB stick (2GB) is not even listed in the F12 Bios boot menu. YOU MEAN YOU PLUGGED THE STICK WITH THE ISO INSTALLED ON IT THAT THE DESKTOP BOOTED FROM??? Yes, that same stick booted the desktop but is not recognized in the F12 menu of my notebook. Any clues? -- Christoph Older pc's have bios which do not have option to boot from USB stick. I think that is so in your case. Check mfg website for bios update. If not you are SOL. (shit outof luck) I can boot USB sticks in general from that notebook/BIOS. That Dell 9400 isn't that old. Today I tried an another USB stick (16GB) an Ubuntu 9.04 boot image and it worked fine. I saw the boot device under F12 in the bootable device menu. It's definitely not the BIOS. Could be some partition problem (active partition?). > Why is it part #4 btw, that FreeBSD resides in and not part #1 ? LETS NOT GET CONFUSED WITH MSDOS /FREEBSD TERMS. IN FREEBSD A SLICE IS WHAT MSDOS CALLS A PARTITION. IN FREEBSD A PARTITION IS A FILE SYSTEM SUCH AS /, /USR, /VAR WITH IN THE SLICE. A SLICE IS MARKED AS ACTIVE MEANING ITS BOOTABLE. THE MBR The FreeBSD fdisk program names it "partition". (MASTER BOOT RECORD)PARTITION TABLE IS REALLY FREEBSD SLICE TABLE. FROM YOUR STATEMENT ABOVE YOU HAVE A MOTHERBOARD CABLED HARD DRIVE WITH 4 PARTITIONS/SLICES DEFINED IN THE MBR PARTITION TABLE. THE FIRST 3 PARTITIONS COULD BE HOLDING OTHER OPERATING SYSTEMS THAT YOU MAY WANT TO BOOT FROM. IS THIS CORRECT? Actually, I thought the USB stick had been blanked out before, but I'm nit sure and will look at it again. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Cannot boot FreeBSD (8.0) from USB stick (Dell Inspiron 9400)
Here is some more info: The file I copied to the USB stick was ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/8.0/8.0-RELEASE-i386-memstick.img Actually, I don't remember how I got the image to the USB stick. I believe I used a free tool from HP from within Windows XP. I will try out your method below now. kernel messages at the time usb stick is inserted: ugen4.3: at usbus4 umass0: on usbus4 umass0: SCSI over Bulk-Only; quirks = 0x umass0:1:0:-1: Attached to scbus1 (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 (probe0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed (probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data) da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 1921MB (3935000 512 byte sectors: 255H 63S/T 244C) GEOM: da0: media size does not match label. # # # fdisk /dev/da0 *** Working on device /dev/da0 *** parameters extracted from in-core disklabel are: cylinders=244 heads=255 sectors/track=63 (16065 blks/cyl) /tmp/l12: unmodified, readonly: line 1 kernel messages at the time usb stick is inserted: ugen4.3: at usbus4 umass0: on usbus4 umass0: SCSI over Bulk-Only; quirks = 0x umass0:1:0:-1: Attached to scbus1 (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 (probe0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed (probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data) da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 1921MB (3935000 512 byte sectors: 255H 63S/T 244C) GEOM: da0: media size does not match label. # # # fdisk /dev/da0 *** Working on device /dev/da0 *** parameters extracted from in-core disklabel are: cylinders=244 heads=255 sectors/track=63 (16065 blks/cyl) parameters to be used for BIOS calculations are: cylinders=244 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 0, size 5 (24 Meg), flag 80 (active) beg: cyl 0/ head 0/ sector 1; end: cyl 1023/ head 254/ sector 63 # -- Christoph ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Cannot boot FreeBSD (8.0) from USB stick (Dell Inspiron 9400)
I don't know why you shout. (?) Fbsd1 schrieb: Christoph Kukulies wrote: Fbsd1 schrieb: Christoph Kukulies wrote: I installed FreeBSD 8.0 on an USB-stick and was able to boot it on my Desktop PC and install 8.0 from it. DO YOU MEAN YOU INSTALLED THE 8.0 ISO ON A USB STICK. BOOTED FROM IT AS INSTALL SOURCE AND INSTALLED 8.0 ON A DESKTOP PC TO THE MOTHERBOARD CABLED HARD DRIVE??? OR DO YOU MEAN YOU INSTALLED 8.0 ON A DESKTOP PC TO ANOTHER USB STICK??? The former, I copied the 8.0 iso image to an USB stick, booted it and installed it to the desktop PCs hard drive. That was one story. The other point is, that I now wanted to plug this USB stick into my Dell inspiron and install FreeBSD in the same manner to a free partition on my notebooks hard drive. Now I plugged the same stick into my Dell Inspiron 9400 and the USB stick (2GB) is not even listed in the F12 Bios boot menu. YOU MEAN YOU PLUGGED THE STICK WITH THE ISO INSTALLED ON IT THAT THE DESKTOP BOOTED FROM??? Yes, that same stick booted the desktop but is not recognized in the F12 menu of my notebook. Any clues? -- Christoph Older pc's have bios which do not have option to boot from USB stick. I think that is so in your case. Check mfg website for bios update. If not you are SOL. (shit outof luck) I can boot USB sticks in general from that notebook/BIOS. That Dell 9400 isn't that old. Today I tried an another USB stick (16GB) an Ubuntu 9.04 boot image and it worked fine. I saw the boot device under F12 in the bootable device menu. It's definitely not the BIOS. Could be some partition problem (active partition?). > Why is it part #4 btw, that FreeBSD resides in and not part #1 ? LETS NOT GET CONFUSED WITH MSDOS /FREEBSD TERMS. IN FREEBSD A SLICE IS WHAT MSDOS CALLS A PARTITION. IN FREEBSD A PARTITION IS A FILE SYSTEM SUCH AS /, /USR, /VAR WITH IN THE SLICE. A SLICE IS MARKED AS ACTIVE MEANING ITS BOOTABLE. THE MBR The FreeBSD fdisk program names it "partition". (MASTER BOOT RECORD)PARTITION TABLE IS REALLY FREEBSD SLICE TABLE. FROM YOUR STATEMENT ABOVE YOU HAVE A MOTHERBOARD CABLED HARD DRIVE WITH 4 PARTITIONS/SLICES DEFINED IN THE MBR PARTITION TABLE. THE FIRST 3 PARTITIONS COULD BE HOLDING OTHER OPERATING SYSTEMS THAT YOU MAY WANT TO BOOT FROM. IS THIS CORRECT? Actually, I thought the USB stick had been blanked out before, but I'm nit sure and will look at it again. > I followed some FreeBSD howto, if I'm not wrong, to bring the ISO to the USB stick. Think it was a tool from HP to write it to the stick. -- Christoph I will come back with the results of the check below later. -- Christoph ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Cannot boot FreeBSD (8.0) from USB stick (Dell Inspiron 9400)
Christoph Kukulies wrote: Fbsd1 schrieb: Christoph Kukulies wrote: I installed FreeBSD 8.0 on an USB-stick and was able to boot it on my Desktop PC and install 8.0 from it. DO YOU MEAN YOU INSTALLED THE 8.0 ISO ON A USB STICK. BOOTED FROM IT AS INSTALL SOURCE AND INSTALLED 8.0 ON A DESKTOP PC TO THE MOTHERBOARD CABLED HARD DRIVE??? OR DO YOU MEAN YOU INSTALLED 8.0 ON A DESKTOP PC TO ANOTHER USB STICK??? Now I plugged the same stick into my Dell Inspiron 9400 and the USB stick (2GB) is not even listed in the F12 Bios boot menu. YOU MEAN YOU PLUGGED THE STICK WITH THE ISO INSTALLED ON IT THAT THE DESKTOP BOOTED FROM??? Any clues? -- Christoph Older pc's have bios which do not have option to boot from USB stick. I think that is so in your case. Check mfg website for bios update. If not you are SOL. (shit outof luck) I can boot USB sticks in general from that notebook/BIOS. That Dell 9400 isn't that old. Today I tried an another USB stick (16GB) an Ubuntu 9.04 boot image and it worked fine. I saw the boot device under F12 in the bootable device menu. It's definitely not the BIOS. Could be some partition problem (active partition?). > Why is it part #4 btw, that FreeBSD resides in and not part #1 ? LETS NOT GET CONFUSED WITH MSDOS /FREEBSD TERMS. IN FREEBSD A SLICE IS WHAT MSDOS CALLS A PARTITION. IN FREEBSD A PARTITION IS A FILE SYSTEM SUCH AS /, /USR, /VAR WITH IN THE SLICE. A SLICE IS MARKED AS ACTIVE MEANING ITS BOOTABLE. THE MBR (MASTER BOOT RECORD)PARTITION TABLE IS REALLY FREEBSD SLICE TABLE. FROM YOUR STATEMENT ABOVE YOU HAVE A MOTHERBOARD CABLED HARD DRIVE WITH 4 PARTITIONS/SLICES DEFINED IN THE MBR PARTITION TABLE. THE FIRST 3 PARTITIONS COULD BE HOLDING OTHER OPERATING SYSTEMS THAT YOU MAY WANT TO BOOT FROM. IS THIS CORRECT? > I followed some FreeBSD howto, if I'm not wrong, to bring the ISO to the USB stick. Think it was a tool from HP to write it to the stick. -- Christoph Here is some thing for you to check. When you plug your USB stick into a running freebsd system a bunch of messages are printed on the root console. One of those messages contain the Revision level of the 2.0 standard used by the micro code in the usb stick. I have found through testing different non-branded and branded sticks that the Revision level makes a very large difference in whether you can boot from the stick. Sticks that show Rev 2.00/0.00 or 2.00/1.00 will never boot. Only sticks that show Rev 2.00/2.00 are bootable. Now since only one of my 4 pc's is new enough to have bios option to boot from usb stick I do not know if these results are dependent on my particular Acer TravelMate 4220 pc bios. Please let me know what usb stick Revision levels you can boot from on both your desktop and laptop. I would think if the stick is bootable on desktop it should also boot on the laptop. Here is the script I use to put the disc-1 iso on usb stick so I can use the stick as source media to install from. When booting from usb stick as install source and installing onto another usb stack as the target you have to have both sticks plugged in before booting. When you are in sysinstall fdisk check the stick size to verify you have chosen the correct da stick as target. You can find yourself fdisking your source stick by mistake. If you don't get prompt to chose da0 or da1 before fdisk starts then you have to tell sysinstall to re-probe devices by using options rescan (*) off the main menu, move highlight bar by using arrow keys and hit space bar to rescan. Then you should get prompt containing both da devices before fdisk. I have used this command to to write zeros to the usb stick MBR dd if=/dev/zero of=/dev/da0 count=1 and this command to display the MBR dd if=/dev/da0 count=1 | od -c I also notice that fdisk does not allocate space on usb sticks as i would expect. It always allocates a free space before and after the full stick single slice. It also never get the size of the stick correct. A 2GB stick is shown as 1.7GB and 4GB stick is shown as 3.7GB. Do you see the same thing happening with your usb sticks? #!/bin/sh #Purpose = Use to transfer the FreeBSD install cd1 to # a bootable 1GB USB flash drive so it can be used to install from. # First fetch the FreeBSD 7.1-RELEASE-i386-disc1.iso to your # hard drive /usr. Then execute this script from the command line # fbsd2usb /usr/7.1-RELEASE-i386-disc1.iso /usr/7.1-RELEASE-i386-disc1.img # Change system bios to boot from USB-dd and away you go. # NOTE: This script has to be run from root and your 1GB USB flash drive # has to be plugged in before running this script. # On the command line enter fbsd2usb iso-path img-path # You can set some variables here. Edit them to fit your needs. # Set serial variable to 0 if you don't want serial console at all, # 1 if you want comconsole and 2 if you want comconsole and vidconsole serial=0 set -u if [ $# -lt 2 ]; then echo "U
Re: Cannot boot FreeBSD (8.0) from USB stick (Dell Inspiron 9400)
Fbsd1 schrieb: Christoph Kukulies wrote: I installed FreeBSD 8.0 on an USB-stick and was able to boot it on my Desktop PC and install 8.0 from it. Now I plugged the same stick into my Dell Inspiron 9400 and the USB stick (2GB) is not even listed in the F12 Bios boot menu. Any clues? -- Christoph ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" Older pc's have bios which do not have option to boot from USB stick. I think that is so in your case. Check mfg website for bios update. If not you are SOL. (shit outof luck) I can boot USB sticks in general from that notebook/BIOS. That Dell 9400 isn't that old. Today I tried an another USB stick (16GB) an Ubuntu 9.04 boot image and it worked fine. I saw the boot device under F12 in the bootable device menu. It's definitely not the BIOS. Could be some partition problem (active partition?). Why is it part #4 btw, that FreeBSD resides in and not part #1 ? I followed some FreeBSD howto, if I'm not wrong, to bring the ISO to the USB stick. Think it was a tool from HP to write it to the stick. -- Christoph ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Cannot boot FreeBSD (8.0) from USB stick (Dell Inspiron 9400)
Christoph Kukulies wrote: I installed FreeBSD 8.0 on an USB-stick and was able to boot it on my Desktop PC and install 8.0 from it. Now I plugged the same stick into my Dell Inspiron 9400 and the USB stick (2GB) is not even listed in the F12 Bios boot menu. Any clues? -- Christoph ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" Older pc's have bios which do not have option to boot from USB stick. I think that is so in your case. Check mfg website for bios update. If not you are SOL. (shit outof luck) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Cannot boot FreeBSD (8.0) from USB stick (Dell Inspiron 9400)
I installed FreeBSD 8.0 on an USB-stick and was able to boot it on my Desktop PC and install 8.0 from it. Now I plugged the same stick into my Dell Inspiron 9400 and the USB stick (2GB) is not even listed in the F12 Bios boot menu. Any clues? -- Christoph ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: cannot boot freebsd
ok, sorry... 2009/11/12 Jerry McAllister > On Thu, Nov 12, 2009 at 09:38:27AM -0600, Jesús Abidan wrote: > > First, please send all messages to the freebsd-questions list and not > just to me. That is proper list etiquette, plus you will be able to > get responses from more than just me. Others may know more. > In other words, always do a 'reply all' on list email. > > > > read this: > > > > "First, be aware that all the information necessary to boot FreeBSD must > be > > located within the first 1,024 cylinders of the hard disk. This is > necessary > > for the FreeBSD boot manager to work; it means that when you partition > the > > disk for FreeBSD using FIPS, either the root partition must be completely > > located within the first 1,024 cylinders or you can use a separate boot > > partition that is completely located in the first 1,024 cylinders. Use > the > > "Start" and "End" cylinder readouts in FIPS to determine where your > > partitions start and end. If you choose the latter option, the root > > partition does not have to be completely located in the first 1,024 > > cylinders. Note that "completely located" means that the partition has to > > both start and end below the 1,024th cylinder. Simply starting below the > > 1,024th cylinder is not good enough. > > This is obsolete information for most computers with BIOS and disks > created later than about 1998. That really means all computers > functioning today. It is also obsolete for FreeBSD systems which > do not use BIOS to talk to the disk. > > There are numerous web sites that explain this including some > documentation on the FreeBSD web site:http://www.freebsd.org/ > > jerry > > > > > > > http://www.informit.com/articles/article.aspx?p=32084&seqNum=4"; > > > > as i see, do i need to create a partition(located in the first > > 1024cylinders) to BOOT from? (sorry) > > > > 2009/11/12 Jesús Abidan > > > > > no, it's not vista, is XP > > > > > > 2009/11/12 Jerry McAllister > > > > > > On Wed, Nov 11, 2009 at 06:57:02PM -0600, Jesús Abidan wrote: > > >> > > >> > i did it like you say, but something is happening with my > installation, > > >> it > > >> > boots always the first OS, i don't have any ideas for having a dual > > >> > system... argh!! > > >> > > >> Perchance, is your other system MS-Vista? > > >> As I mentioned in a previous response, I have heard of people > > >> having problems with dual booting with Vista and having to > > >> follow some other procedure for that. But, I haven't used Vista > > >> (and do not intend to) so you will have to do some archive searching > > >> to find those pieces of information. > > >> > > >> jerry > > >> > > >> > > >> > > >> > > > >> > 2009/11/11 Jerry McAllister > > >> > > > >> > > On Wed, Nov 11, 2009 at 02:12:22PM -0600, Jesús Abidan wrote: > > >> > > > > >> > > > so, then i need to create 2 slices with gparted, install windows > on > > >> the > > >> > > > first one, and install freebsd on the second one and label this > > >> partition > > >> > > > automatically by the installer (ad0s1, ad0s2, etc) and install > the > > >> > > bootmgr? > > >> > > > > >> > > Yes, essentially except for those partition names. > > >> > > > > >> > > Create the two slices/primary partitions. > > >> > > Install the MS-Win in the first one. I think then MS will call it > > >> 'c:' > > >> > > Anyway, FreeBSD will think it is ad0s1. > > >> > > > > >> > > Then install FreeBSD in the second slice/primary partition. MS > will > > >> not > > >> > > even know it is there. FreeBSD will call it ad0s2. > > >> > > > > >> > > During the install, that ad0s2 slice will be subdivided according > to > > >> how > > >> > > you tell it into FreeBSD partitions with names like ad0s2a (for > root) > > >> > > and ad0s2b (for swap), ad0s2d for whatever - maybe /tmp, ad0s2e > for > > >> > > something else, such as /usr, etc. > > >> > > > > >> > > For my general purpose machines I usually subdivide in to > > >> > > the following partitions: > > >> > > amounts as / eg: mount /dev/ad0s2a / > > >> > > b swap > > >> > > cdescribes the slice and is not a real partition > > >> > > dmounts as /tmp eg: mount /dev/ad0s2d /tmp > > >> > > emounts as /usr etc > > >> > > fmounts as /var > > >> > > gmounts as /home or something similar > > >> > > > > >> > > > > >> > > For my systems that are single purpose central servers I tend to > do > > >> this: > > >> > > amounts as / everything but swap and afscache goes in > root. > > >> > > b swap > > >> > > cslice description > > >> > > d/afscache > > >> > > > > >> > > > > >> > > If I have a second drive for scratch or work space I tend to do: > > >> > > amounts as /work and uses up all the space except extra swap > > >> > > bused for additional swap > > >> > > cdescribes the slice > > >> > > > > >> > > The sizes of the various partition-subdivisions
Re: cannot boot freebsd
no, it is not the disk, i removed it and the same problem... 2009/11/12 Jesús Abidan > no idea... > > the machine had only one hard drive(PATA), then i plugged a new sata > HD(freebsd style), with information on it. The PATA drive is cofigured as > the primary disk, and the sata in bios it says is in PORT 0. > > I'll try removing the SATA disk and install freebsd, maybe is the jumper > configuration. > > 2009/11/12 Jerry McAllister > >> On Thu, Nov 12, 2009 at 10:04:29AM -0600, Jesús Abidan wrote: >> >> >> > i think i have the problem... >> > >> > i have two hard disks, IDE and SATA, i saw in my MS XP, my root label is >> F: >> > instead of C: maybe it is something related to jumpers or something like >> > that? >> >> That is a little surprise to me, but I am not up on the ins and outs >> of IDE/SATA labeling.Most of my machines - all of the servers - >> have SCSI or SAS disk which does it differently (and more easily). >> My only SATA machines have only a single disk. >> >> One thing to ask is: what does it have as c:, d: and e: ?? >> Maybe something is plugged in the wrong - or inconvenient - order >> on the controller. Or, I suppose there might be a jumper issue. >> >> jerry >> >> >> > >> > 2009/11/12 Jesús Abidan >> > >> > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: cannot boot freebsd
no idea... the machine had only one hard drive(PATA), then i plugged a new sata HD(freebsd style), with information on it. The PATA drive is cofigured as the primary disk, and the sata in bios it says is in PORT 0. I'll try removing the SATA disk and install freebsd, maybe is the jumper configuration. 2009/11/12 Jerry McAllister > On Thu, Nov 12, 2009 at 10:04:29AM -0600, Jesús Abidan wrote: > > > i think i have the problem... > > > > i have two hard disks, IDE and SATA, i saw in my MS XP, my root label is > F: > > instead of C: maybe it is something related to jumpers or something like > > that? > > That is a little surprise to me, but I am not up on the ins and outs > of IDE/SATA labeling.Most of my machines - all of the servers - > have SCSI or SAS disk which does it differently (and more easily). > My only SATA machines have only a single disk. > > One thing to ask is: what does it have as c:, d: and e: ?? > Maybe something is plugged in the wrong - or inconvenient - order > on the controller. Or, I suppose there might be a jumper issue. > > jerry > > > > > > 2009/11/12 Jesús Abidan > > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: cannot boot freebsd
On Thu, Nov 12, 2009 at 10:04:29AM -0600, Jesús Abidan wrote: > i think i have the problem... > > i have two hard disks, IDE and SATA, i saw in my MS XP, my root label is F: > instead of C: maybe it is something related to jumpers or something like > that? That is a little surprise to me, but I am not up on the ins and outs of IDE/SATA labeling.Most of my machines - all of the servers - have SCSI or SAS disk which does it differently (and more easily). My only SATA machines have only a single disk. One thing to ask is: what does it have as c:, d: and e: ?? Maybe something is plugged in the wrong - or inconvenient - order on the controller. Or, I suppose there might be a jumper issue. jerry > > 2009/11/12 Jesús Abidan > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: cannot boot freebsd
On Thu, Nov 12, 2009 at 09:38:27AM -0600, Jesús Abidan wrote: First, please send all messages to the freebsd-questions list and not just to me. That is proper list etiquette, plus you will be able to get responses from more than just me. Others may know more. In other words, always do a 'reply all' on list email. > read this: > > "First, be aware that all the information necessary to boot FreeBSD must be > located within the first 1,024 cylinders of the hard disk. This is necessary > for the FreeBSD boot manager to work; it means that when you partition the > disk for FreeBSD using FIPS, either the root partition must be completely > located within the first 1,024 cylinders or you can use a separate boot > partition that is completely located in the first 1,024 cylinders. Use the > "Start" and "End" cylinder readouts in FIPS to determine where your > partitions start and end. If you choose the latter option, the root > partition does not have to be completely located in the first 1,024 > cylinders. Note that "completely located" means that the partition has to > both start and end below the 1,024th cylinder. Simply starting below the > 1,024th cylinder is not good enough. This is obsolete information for most computers with BIOS and disks created later than about 1998. That really means all computers functioning today. It is also obsolete for FreeBSD systems which do not use BIOS to talk to the disk. There are numerous web sites that explain this including some documentation on the FreeBSD web site:http://www.freebsd.org/ jerry > > http://www.informit.com/articles/article.aspx?p=32084&seqNum=4"; > > as i see, do i need to create a partition(located in the first > 1024cylinders) to BOOT from? (sorry) > > 2009/11/12 Jesús Abidan > > > no, it's not vista, is XP > > > > 2009/11/12 Jerry McAllister > > > > On Wed, Nov 11, 2009 at 06:57:02PM -0600, Jesús Abidan wrote: > >> > >> > i did it like you say, but something is happening with my installation, > >> it > >> > boots always the first OS, i don't have any ideas for having a dual > >> > system... argh!! > >> > >> Perchance, is your other system MS-Vista? > >> As I mentioned in a previous response, I have heard of people > >> having problems with dual booting with Vista and having to > >> follow some other procedure for that. But, I haven't used Vista > >> (and do not intend to) so you will have to do some archive searching > >> to find those pieces of information. > >> > >> jerry > >> > >> > >> > >> > > >> > 2009/11/11 Jerry McAllister > >> > > >> > > On Wed, Nov 11, 2009 at 02:12:22PM -0600, Jesús Abidan wrote: > >> > > > >> > > > so, then i need to create 2 slices with gparted, install windows on > >> the > >> > > > first one, and install freebsd on the second one and label this > >> partition > >> > > > automatically by the installer (ad0s1, ad0s2, etc) and install the > >> > > bootmgr? > >> > > > >> > > Yes, essentially except for those partition names. > >> > > > >> > > Create the two slices/primary partitions. > >> > > Install the MS-Win in the first one. I think then MS will call it > >> 'c:' > >> > > Anyway, FreeBSD will think it is ad0s1. > >> > > > >> > > Then install FreeBSD in the second slice/primary partition. MS will > >> not > >> > > even know it is there. FreeBSD will call it ad0s2. > >> > > > >> > > During the install, that ad0s2 slice will be subdivided according to > >> how > >> > > you tell it into FreeBSD partitions with names like ad0s2a (for root) > >> > > and ad0s2b (for swap), ad0s2d for whatever - maybe /tmp, ad0s2e for > >> > > something else, such as /usr, etc. > >> > > > >> > > For my general purpose machines I usually subdivide in to > >> > > the following partitions: > >> > > amounts as / eg: mount /dev/ad0s2a / > >> > > b swap > >> > > cdescribes the slice and is not a real partition > >> > > dmounts as /tmp eg: mount /dev/ad0s2d /tmp > >> > > emounts as /usr etc > >> > > fmounts as /var > >> > > gmounts as /home or something similar > >> > > > >> > > > >> > > For my systems that are single purpose central servers I tend to do > >> this: > >> > > amounts as / everything but swap and afscache goes in root. > >> > > b swap > >> > > cslice description > >> > > d/afscache > >> > > > >> > > > >> > > If I have a second drive for scratch or work space I tend to do: > >> > > amounts as /work and uses up all the space except extra swap > >> > > bused for additional swap > >> > > cdescribes the slice > >> > > > >> > > The sizes of the various partition-subdivisions depends on the size > >> > > of the disk and the use being made of the machine and what I want > >> > > to install on it and how I want to handle backups. > >> > > > >> > > jerry > >> > > > >> > > > >> > > > > >> > > > 2009/11/11 Jerry McAllister > >> > > > > >> > > > > On Wed, Nov
Re: cannot boot freebsd
On Wed, Nov 11, 2009 at 06:57:02PM -0600, Jesús Abidan wrote: > i did it like you say, but something is happening with my installation, it > boots always the first OS, i don't have any ideas for having a dual > system... argh!! Perchance, is your other system MS-Vista? As I mentioned in a previous response, I have heard of people having problems with dual booting with Vista and having to follow some other procedure for that. But, I haven't used Vista (and do not intend to) so you will have to do some archive searching to find those pieces of information. jerry > > 2009/11/11 Jerry McAllister > > > On Wed, Nov 11, 2009 at 02:12:22PM -0600, Jesús Abidan wrote: > > > > > so, then i need to create 2 slices with gparted, install windows on the > > > first one, and install freebsd on the second one and label this partition > > > automatically by the installer (ad0s1, ad0s2, etc) and install the > > bootmgr? > > > > Yes, essentially except for those partition names. > > > > Create the two slices/primary partitions. > > Install the MS-Win in the first one. I think then MS will call it 'c:' > > Anyway, FreeBSD will think it is ad0s1. > > > > Then install FreeBSD in the second slice/primary partition. MS will not > > even know it is there. FreeBSD will call it ad0s2. > > > > During the install, that ad0s2 slice will be subdivided according to how > > you tell it into FreeBSD partitions with names like ad0s2a (for root) > > and ad0s2b (for swap), ad0s2d for whatever - maybe /tmp, ad0s2e for > > something else, such as /usr, etc. > > > > For my general purpose machines I usually subdivide in to > > the following partitions: > > amounts as / eg: mount /dev/ad0s2a / > > b swap > > cdescribes the slice and is not a real partition > > dmounts as /tmp eg: mount /dev/ad0s2d /tmp > > emounts as /usr etc > > fmounts as /var > > gmounts as /home or something similar > > > > > > For my systems that are single purpose central servers I tend to do this: > > amounts as / everything but swap and afscache goes in root. > > b swap > > cslice description > > d/afscache > > > > > > If I have a second drive for scratch or work space I tend to do: > > amounts as /work and uses up all the space except extra swap > > bused for additional swap > > cdescribes the slice > > > > The sizes of the various partition-subdivisions depends on the size > > of the disk and the use being made of the machine and what I want > > to install on it and how I want to handle backups. > > > > jerry > > > > > > > > > > 2009/11/11 Jerry McAllister > > > > > > > On Wed, Nov 11, 2009 at 01:22:58PM -0600, Jesús Abidan wrote: > > > > > > > > > ok. the slices in freebsd are little tricky, i will check my > > installation > > > > > and send some feedback later. > > > > > > > > > > > > ?? FreeBSD slices are pretty straight forward. They are just the > > > > name of the 4 primary divisions of a disk - limited to 4 by BIOS. > > > > MS just calls them primary partitions instead of slices. > > > > > > > > The major difference is how they might be subdivided. MS does what it > > > > calls logical partitions. FreeBSD subdivisions are just called > > partitions. > > > > > > > > The fdisk(8) utility creates slices (or primary partitions in MS, > > though > > > > the > > > > FreeBSD fdisk is not very conversant with some of the new MS types so > > you > > > > may be better off using something else to create primary > > partitions/slices > > > > if other OSen are being accomodated). Slices (or primary partitions) > > are > > > > identified by numbers 1..4. > > > > > > > > The bsdlabel(8) utility in FreeBSD is what subdivides a slice in to > > > > partitions. It used to be that it was limited to 7 real partitions > > > > identified with letters a..h with the letter 'c' reserved to describe > > > > the whole slice and not usable as a real partition. Partition 'a' is > > > > normally root mounted as '/' and partition 'b' is used as swap. These > > > > two (a & b) are conventions and not enforced, except that some software > > > > may make these assumptions.My understanding is that the newest > > > > versions of FreeBSD (8.0) modify or remove the limit and you can have > > > > letters above 'h' and thus more subdivisions in a slice, but I haven't > > > > tried that yet. > > > > > > > > In FreeBSD, to create a filesystem from a partition, you run newfs(8) > > on > > > > it. > > > > > > > > jerry > > > > > > > > > > > > > > Thanks a lot. > > > > > > > > > > 2009/11/11 Jerry McAllister > > > > > > > > > > > On Wed, Nov 11, 2009 at 12:27:13PM -0600, Jesús Abidan wrote: > > > > > > > > > > > > > i pressed f2 for freebsd and nothing happens... i pressed f1 for > > > > windows. > > > > > > > > > > > > > > I install freebsd on the first partition and now it occurs the > > > > viceversa, > > > > > > i > >
Re: cannot boot freebsd
On Wed, 11 Nov 2009, Jerry McAllister wrote: I have heard some complaints about MS-Vista and having to do some other monkeying around to get an MBR to handle it correctly, but I don't know details and I do not (lucky me) have any Vista machines to joust with. EasyBCD from neosmart.net is an easy and free way to do this. Install Vista, install FreeBSD in another slice/primary partition but leave the MBR alone, then install and use EasyBCD from Vista to set booting options. On boot, the machine shows a menu similar to but fancier than FreeBSD's boot0. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: cannot boot freebsd
2009/11/11 Jerry McAllister wrote: > That is because MS-Win doesn't play > very well if installed later and/or in a different slice. Windows behaves fine for me whatever slice it's installed in. What IS important is that it's installed first, as you said before. You can choose it to go wherever you like. By the way, please don't say win to refer to Windows; as RMS has said many times '[If] you call Windows a "win", you are praising it. If you don't want to praise Windows, it's better not to call it a "win".' [1] If you must abbreviate it, try w32, or leave off MS- and just write Windows [1] http://markmail.org/message/ncyme3djyujyre6u#query:stallman%20windows%20don%27t%20call%20win32+page:1+mid:ncyme3djyujyre6u+state:results -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in a mailing list? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: cannot boot freebsd
On Wed, Nov 11, 2009 at 01:22:58PM -0600, Jesús Abidan wrote: > ok. the slices in freebsd are little tricky, i will check my installation > and send some feedback later. ?? FreeBSD slices are pretty straight forward. They are just the name of the 4 primary divisions of a disk - limited to 4 by BIOS. MS just calls them primary partitions instead of slices. The major difference is how they might be subdivided. MS does what it calls logical partitions. FreeBSD subdivisions are just called partitions. The fdisk(8) utility creates slices (or primary partitions in MS, though the FreeBSD fdisk is not very conversant with some of the new MS types so you may be better off using something else to create primary partitions/slices if other OSen are being accomodated). Slices (or primary partitions) are identified by numbers 1..4. The bsdlabel(8) utility in FreeBSD is what subdivides a slice in to partitions. It used to be that it was limited to 7 real partitions identified with letters a..h with the letter 'c' reserved to describe the whole slice and not usable as a real partition. Partition 'a' is normally root mounted as '/' and partition 'b' is used as swap. These two (a & b) are conventions and not enforced, except that some software may make these assumptions.My understanding is that the newest versions of FreeBSD (8.0) modify or remove the limit and you can have letters above 'h' and thus more subdivisions in a slice, but I haven't tried that yet. In FreeBSD, to create a filesystem from a partition, you run newfs(8) on it. jerry > > Thanks a lot. > > 2009/11/11 Jerry McAllister > > > On Wed, Nov 11, 2009 at 12:27:13PM -0600, Jesús Abidan wrote: > > > > > i pressed f2 for freebsd and nothing happens... i pressed f1 for windows. > > > > > > I install freebsd on the first partition and now it occurs the viceversa, > > i > > > cannot boot windows, does it have to be something with the order of the > > > partitions? i mean primary, logical o something like this? > > > > MS-Win should optimally be installed on the first primary partition. > > This is called 'slice 1' by FreeBSD. Then FreeBSD should be installed > > on slice 2. > > > > If the slices are not to your liking, then you may need to use some > > utility such as Parition Magic 7 (I had trouble with PM-8) or gparted > > to define the primary partitions/slices before you do any of the installs. > > But, still, MS-Win should be installed first and go in the first slice > > and FreeBSD later in another slice. That is because MS-Win doesn't play > > very well if installed later and/or in a different slice. > > > > When you install FreeBSD (after the MS-Win install) select installing > > the FreeBSD MBR (not none or default minimum).It should be smart > > enough to find both. > > > > I have heard some complaints about MS-Vista and having to do some > > other monkeying around to get an MBR to handle it correctly, but I > > don't know details and I do not (lucky me) have any Vista machines > > to joust with. > > > > jerry > > > > > > > > > > 2009/11/11 Jerry McAllister > > > > > > > On Wed, Nov 11, 2009 at 11:02:35AM -0600, Jesús Abidan wrote: > > > > > > > > > Hi there, i have a problem here, i installed windows in mi box and i > > left > > > > a > > > > > partition for freebsd, i finished install of freebsd and installed > > the > > > > boot > > > > > mgr of freebsd but when i reboot only windows boots with f1 pressed? > > how > > > > can > > > > > I make the system boots both? > > > > > > > > Not sure all of what you see, but if you literally mean that when > > > > you press F1 it always boots MS-Win, that is probably correct. > > > > You will have to press F2 or maybe F3 (depending in which slice you > > > > installed FreeBSD) to boot FreeBSD. > > > > > > > > I suspect you mean something a little different, but if so, > > > > please elaborate. > > > > > > > > jerry > > > > > > > > > > > > > ___ > > > > > freebsd-questions@freebsd.org mailing list > > > > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > > > > To unsubscribe, send any mail to " > > > > freebsd-questions-unsubscr...@freebsd.org" > > > > > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: cannot boot freebsd
On Wed, Nov 11, 2009 at 12:27:13PM -0600, Jesús Abidan wrote: > i pressed f2 for freebsd and nothing happens... i pressed f1 for windows. > > I install freebsd on the first partition and now it occurs the viceversa, i > cannot boot windows, does it have to be something with the order of the > partitions? i mean primary, logical o something like this? MS-Win should optimally be installed on the first primary partition. This is called 'slice 1' by FreeBSD. Then FreeBSD should be installed on slice 2. If the slices are not to your liking, then you may need to use some utility such as Parition Magic 7 (I had trouble with PM-8) or gparted to define the primary partitions/slices before you do any of the installs. But, still, MS-Win should be installed first and go in the first slice and FreeBSD later in another slice. That is because MS-Win doesn't play very well if installed later and/or in a different slice. When you install FreeBSD (after the MS-Win install) select installing the FreeBSD MBR (not none or default minimum).It should be smart enough to find both. I have heard some complaints about MS-Vista and having to do some other monkeying around to get an MBR to handle it correctly, but I don't know details and I do not (lucky me) have any Vista machines to joust with. jerry > > 2009/11/11 Jerry McAllister > > > On Wed, Nov 11, 2009 at 11:02:35AM -0600, Jesús Abidan wrote: > > > > > Hi there, i have a problem here, i installed windows in mi box and i left > > a > > > partition for freebsd, i finished install of freebsd and installed the > > boot > > > mgr of freebsd but when i reboot only windows boots with f1 pressed? how > > can > > > I make the system boots both? > > > > Not sure all of what you see, but if you literally mean that when > > you press F1 it always boots MS-Win, that is probably correct. > > You will have to press F2 or maybe F3 (depending in which slice you > > installed FreeBSD) to boot FreeBSD. > > > > I suspect you mean something a little different, but if so, > > please elaborate. > > > > jerry > > > > > > > ___ > > > freebsd-questions@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > > To unsubscribe, send any mail to " > > freebsd-questions-unsubscr...@freebsd.org" > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: cannot boot freebsd
On Wed, Nov 11, 2009 at 11:02 AM, Jesús Abidan wrote: > Hi there, i have a problem here, i installed windows in mi box and i left a > partition for freebsd, i finished install of freebsd and installed the boot > mgr of freebsd but when i reboot only windows boots with f1 pressed? how can > I make the system boots both? What do you mean "make the system boot both?" At the same time? That's not going to happen. Isn't F1 the option for dos/windows? If so, consider your other options . . . one should be FreeBSD (assuming you did the install correctly) http://www.freebsd.org/doc/en/books/handbook/boot-blocks.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: cannot boot freebsd
On Wed, Nov 11, 2009 at 11:02:35AM -0600, Jesús Abidan wrote: > Hi there, i have a problem here, i installed windows in mi box and i left a > partition for freebsd, i finished install of freebsd and installed the boot > mgr of freebsd but when i reboot only windows boots with f1 pressed? how can > I make the system boots both? Not sure all of what you see, but if you literally mean that when you press F1 it always boots MS-Win, that is probably correct. You will have to press F2 or maybe F3 (depending in which slice you installed FreeBSD) to boot FreeBSD. I suspect you mean something a little different, but if so, please elaborate. jerry > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
cannot boot freebsd
Hi there, i have a problem here, i installed windows in mi box and i left a partition for freebsd, i finished install of freebsd and installed the boot mgr of freebsd but when i reboot only windows boots with f1 pressed? how can I make the system boots both? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Cannot boot FreeBSD kernel with etherboot
On Tue, Mar 04, 2003 at 02:38:29PM +0100, Heinrich Rebehn wrote: > Heinrich Rebehn wrote: > >Hi list, > > > >trying to boot a FreeBSD kernel with etherboot 5.0.6 results in: > > > >... > >Loading 134.102.176.16:/tftpboot/bsd-diskless ...(ELF)... segment does > >not fit in any memory region > > > >What does this mean? I'm not sure exactly what the message means, but I've had the same problem recently. It appears to be related to the network card - not the boot ROM. I have one diskless machine up and running - booting from a ROM on an Intel Pro100. I have another Intel Pro100 with a built-on ROM chip. Now, my known good machine will not boot with this second card. I get the same error as you about "segment...memory region". Both of the cards have the _exact_ same image loaded - by the way, neither of them have the -DIMAGE_FREEBSD option set. So apparently the -DIMAGE_FREEBSD option is not necessary, as I daily boot and use a machine from a ROM image that does not have this feature. Also, I have been getting my ROM images from http://rom-o-matic.org. I find it very convenient and altogether easier than using the ports version, not to mention that the version is newer. Anyway, my experiments seem to point to the fact that it has something to do with the card, not the image or the machine itself. I have two machines with which to test. Both machines boot fine with one card, and both machines fail with the second card, giving the same error you mention above. However, I could be way off base, and I'm definitely going to try loading an image with the -DIMAGE_FREEBSD option set onto the problem card and see what happens. > > > >The kernel is 2390599 bytes. Did i hit a size limitation? > >I am attaching the Etherboot Config file. > > I have found the solution myself, i forgot "-DIMAGE_FREEBSD", in fact i > thought i set it at my 2nd try, but on the 2nd try, i had the floppy write > protected, which i didn't notice.. :-( > > Now the kernel gets loaded, last output from etherboot is "done" > and then the system reboots.. :-( This is probably not a ROM issue, but instead a problem with the kernel you compiled. Make sure that you have set the machine type correctly your kernel config file. Also, and this one got me, make sure that you set the appropirate CPUTYPE in your /etc/make.conf file. For the longest time I had your exact problem - the kernel would load and then the machine would immediately reboot. I beat my head on the wall for quite some time before I realized that my make.conf file was set to build for CPUTYPE=i686, but I was trying to boot the kernel on i586. As soon as I specified the correct the CPUTYPE all was well. I hope this helps, and I'll let you know if setting -DIMAGE_FREEBSD works for my problem card. > Heinrich -- GPG Public Key ID: 0x4250A04C gpg --keyserver pgp.mit.edu --recv-keys 4250A04C http://63.105.21.156/gpg_nkinkade_4250A04C.asc pgp0.pgp Description: PGP signature
Re: Cannot boot FreeBSD kernel with etherboot
Heinrich Rebehn wrote: Hi list, trying to boot a FreeBSD kernel with etherboot 5.0.6 results in: ... Loading 134.102.176.16:/tftpboot/bsd-diskless ...(ELF)... segment does not fit in any memory region What does this mean? The kernel is 2390599 bytes. Did i hit a size limitation? I am attaching the Etherboot Config file. I have found the solution myself, i forgot "-DIMAGE_FREEBSD", in fact i thought i set it at my 2nd try, but on the 2nd try, i had the floppy write protected, which i didn't notice.. :-( Now the kernel gets loaded, last output from etherboot is "done" and then the system reboots.. :-( Heinrich Thanks for any hints Heinrich # # Config for Etherboot/32 # # Do not delete the tag OptionDescription and /OptionDescription # It is used to automatically generate the documentation. # # # User interaction options: # # -DASK_BOOT=n # Ask "Boot from Network or from Local? " at startup, # timeout after n seconds (0 = no timeout); this # can be done in a more generic way by using the # IMAGE_MENU, but it requires that the "bootp" # server is accessible, even when booting locally. # If unset, boot immediately using the default. # -DANS_DEFAULT=ANS_NETWORK # Assume Network to previous question # (alternative: ANS_LOCAL) on timeout or Return key # See etherboot.h for prompt and answer strings. # -DBAR_PROGRESS # Use rotating bar instead of sequential dots # to indicate an IP packet transmitted. # -DMOTD # Display message of the day; read vendortags.html # for further information. (Deprecated) # -DIMAGE_MENU # Allow to interactively chose between different # bootimages; read vendortags.html for further # information. (Deprecated) # -DPASSWD # Enable password protection for boot images; this # requires -DIMAGE_MENU. (Deprecated) # -DUSRPARMS # Allow the user to interactively edit parameters # that are passed to the booted kernel; you should # probably enable -DPASSWD as well; this feature # requires -DIMAGE_MENU. (Deprecated) # -DANSIESC # Evaluate a subset of common ANSI escape sequences # when displaying the message of the day; this # probably does not make sense unless you also # define -DMOTD or at least -DIMAGE_MENU. It is # possible to combine this option with -DCONSOLE_DUAL, # but you have to be aware that the boot menu will # no longer use ANSI escapes to be compatible with the # serial console. Also be careful with your banners, as # they may confuse your serial console. Generally you # lose most of the ANSIESC functionality. (Deprecated) # -DGFX # Support extensions to the ANSI escape sequences for # displaying graphics (icons or logos); this # requires -DANSIESC. It probably does not make sense # to use -DGFX if you have -DCONSOLE_DUAL, as the # serial console normally cannot handle the GFX stuff. # (Deprecated) # -DSHOW_NUMERIC # Display menu item labels as numbers. # -DDELIMITERLINES # Print a line of = characters at the start # and also just before starting an image. # -DSIZEINDICATOR # Update a running total of the amount of code # loaded so far, in kilobytes. # # Boot autoconfiguration protocol options: # # -DNO_DHCP_SUPPORT # Use BOOTP instead of DHCP. # -DRARP_NOT_BOOTP # Use RARP instead of BOOTP/DHCP. # -DREQUIRE_VCI_ETHERBOOT # Require an encapsulated Vendor Class Identifier # of "Etherboot" in the DHCP reply # Requires DHCP support. # -DALLOW_ONLY_ENCAPSULATED # Ignore Etherboot-specific options that are not within # the Etherboot encapsulated options field. This option # should be enabled unless you have a legacy DHCP server # configuration from the bad old days before the use of # encapsulated Etherboot options. # # Boot tuning parameter
Cannot boot FreeBSD kernel
Hi list, trying to boot a FreeBSD kernel with etherboot 5.0.6 results in: ... Loading 134.102.176.16:/tftpboot/bsd-diskless ...(ELF)... segment does not fit in any memory region What does this mean? The kernel is 2390599 bytes. Did i hit a size limitation? I am attaching the Etherboot Config file. Thanks for any hints Heinrich -- Heinrich Rebehn University of Bremen Physics / Electrical and Electronics Engineering - Department of Telecommunications - E-mail: mailto:[EMAIL PROTECTED] Phone : +49/421/218-4664 Fax :-3341 # # Config for Etherboot/32 # # Do not delete the tag OptionDescription and /OptionDescription # It is used to automatically generate the documentation. # # # User interaction options: # # -DASK_BOOT=n # Ask "Boot from Network or from Local? " at startup, # timeout after n seconds (0 = no timeout); this # can be done in a more generic way by using the # IMAGE_MENU, but it requires that the "bootp" # server is accessible, even when booting locally. # If unset, boot immediately using the default. # -DANS_DEFAULT=ANS_NETWORK # Assume Network to previous question # (alternative: ANS_LOCAL) on timeout or Return key # See etherboot.h for prompt and answer strings. # -DBAR_PROGRESS # Use rotating bar instead of sequential dots # to indicate an IP packet transmitted. # -DMOTD # Display message of the day; read vendortags.html # for further information. (Deprecated) # -DIMAGE_MENU # Allow to interactively chose between different # bootimages; read vendortags.html for further # information. (Deprecated) # -DPASSWD # Enable password protection for boot images; this # requires -DIMAGE_MENU. (Deprecated) # -DUSRPARMS # Allow the user to interactively edit parameters # that are passed to the booted kernel; you should # probably enable -DPASSWD as well; this feature # requires -DIMAGE_MENU. (Deprecated) # -DANSIESC # Evaluate a subset of common ANSI escape sequences # when displaying the message of the day; this # probably does not make sense unless you also # define -DMOTD or at least -DIMAGE_MENU. It is # possible to combine this option with -DCONSOLE_DUAL, # but you have to be aware that the boot menu will # no longer use ANSI escapes to be compatible with the # serial console. Also be careful with your banners, as # they may confuse your serial console. Generally you # lose most of the ANSIESC functionality. (Deprecated) # -DGFX # Support extensions to the ANSI escape sequences for # displaying graphics (icons or logos); this # requires -DANSIESC. It probably does not make sense # to use -DGFX if you have -DCONSOLE_DUAL, as the # serial console normally cannot handle the GFX stuff. # (Deprecated) # -DSHOW_NUMERIC # Display menu item labels as numbers. # -DDELIMITERLINES # Print a line of = characters at the start # and also just before starting an image. # -DSIZEINDICATOR # Update a running total of the amount of code # loaded so far, in kilobytes. # # Boot autoconfiguration protocol options: # # -DNO_DHCP_SUPPORT # Use BOOTP instead of DHCP. # -DRARP_NOT_BOOTP # Use RARP instead of BOOTP/DHCP. # -DREQUIRE_VCI_ETHERBOOT # Require an encapsulated Vendor Class Identifier # of "Etherboot" in the DHCP reply # Requires DHCP support. # -DALLOW_ONLY_ENCAPSULATED # Ignore Etherboot-specific options that are not within # the Etherboot encapsulated options field. This option # should be enabled unless you have a legacy DHCP server # configuration from the bad old days before the use of # encapsulated Etherboot options. # # Boot tuning parameters: # # -DCONGESTED # Turns on packet retransmission. Use it on a # congested network, where the normal operation # can't b
