-
Notifications
You must be signed in to change notification settings - Fork 18
USB and DVD installer hangs BIOS POST screen #1515
Comments
Not sure about the DVD other than make sure in bios you have enabled the ability to boot off of the DVD drive. As for the USB installer, you are basically out of luck with that route. FreeBSD has some kind of code in their program that certain bios recognise as something else. So having that USB stick with any kind of FreeBSD install in your computer will freeze it. Only affects some computers, and unfortunately mine is one of them. My laptop works fine with the same USB stick. Linux works fine as well. |
Thanks @Hecktor83 Shame about the USB option not working. I wonder what FreeBSD is doing there that Linux is not. |
Yeah, it would be my guess that it is a bad burn if you can boot other DVD's. Just bad luck with FreeBSD. They just have some particular bytes that just happen to be the same as what some bioses use for other purposes. Fault of the bios in my view, no way it should have that effect. Like if I plugged my usb stick in while Windows 10 was in mid-boot it would hang the computer. |
@Hecktor83 I noticed that too, if I wait and plug the TrueOS installer in at a later part of the POST, it will hang there instead. |
Yeah, the code is basically the same on the DVD as the USB. However, the computer realizes the DVD is a DVD and treats it accordingly. So DVD should work for you. With the USB it tries to treat it as something different than a drive. Though for me the computer had zero issues if I disabled booting off of the USB. Though that is kind of useless. Though if for some reason you can't get the DVD working and you can disable the USB boot so that it can access the USB drive without crashing, you can try this program: I haven't tried to boot FreeBSD with it, but it definitely detected my FreeBSD installs and booted Linux pretty well. |
@Hecktor83 |
Hey @Hecktor83 I spoke to FreeBSDHelp on Twitter and they suggested compiling all of the relevant info, especially USB hardware info and posting on the FreeBSD mailing list. Can we talk to combine our hardware info so I can post it in 1 post on the list? |
What info did you need? I can provide stuff as long as it is pretty easy to get, my computer is about a decade old. But the USB stick is a Kingston DataTraveler. The image I tried was: But I think they will have to be more specific on what info about the computer and what tool used to gather it. There is a huge amount of info regarding motherboards and not sure what they would be looking for. |
I wouldn't look at this as a solution to your original problem though. Like it is nice if they can figure out what is happening. But that is not going to change anything for you getting the OS installed. If they do make changes so it doesn't happen that will be way down the road. But I'm happy to provide any information they would require. |
@Hecktor83 I think what we need is hardware info. So 'lshw' on Linux and extract the USB host info. Send that over and I'll get mine and then I'll post the mailing list. I am doing this more to help the FreeBSD project than to help myself. It would be nice if it solved our issue too. |
@DaveQB For some reason I had issues attaching the file, so I guess I'll just have to paste it. I didn't realize you could install files on a livedvd, a nice feature. I plugged the USB drive in I was having issues with(though it didn't have the FreeBSD image). localhost.localdomain |
Hi,
This might be a rare, hardware compatibility issue; it has been impossible to find anyone else with an issue like this.
USB INSTALLER
I find my desktop hangs at the POST screen just after it checks memory and then checks and lists hard disks. I have tried a few different USB drives and even the same drive but with another OS installer on it and they all work fine.
DVD INSTALLER
When the computer looks for the DVD to boot from, the disk spins and then the system continues with looking for other boot devices.
I am really keen to move to TrueOS as my main desktop OS.
Thank you.
TrueOS-2017-07-05-x64
The text was updated successfully, but these errors were encountered: