Hello, I am a first time Linux user (not counting steam deck) trying to install Solus after hearing windows 10 was going to stop receiving security updates next year. I have been following this guide https://help.getsol.us/docs/user/quick-start/installation/ and have already made (and remade a couple times now) the boot media. However, trying to boot it will bring up the selection menu (Solus, nomodeset version, return to firmware, etc) fine but after i select one it will go black for a few (probably just loading) before spitting out some variation of ( " XXX.XXXXXX dracut-initqueue[xxx]: timed out fo empty (it appears to be partially cut off for some reason at first, but after a few moments it will reprint the error with different numbers, the full error seeming to be "timed out for waiting the udev queue being empty"). I have tried both nomodeset which is what I saw reccomended, and someone on Reddit recommended using noapic and acpi=off, but I've still had no luck. The person on Reddit recommended I post here. Any ideas what's going on?

I currently run windows 10. My PC is a somewhat oldish Acer Predator G3-710 with an i7 and Nvidia GeForce GTX 1070. Any help would be appreciated.

    Is that the error when booting from the live version or is it from when the pc boots after installation?
    Assuming the error comes booting from the live version:- Check your boot media checksums as specified in the guide. If you are booting from a USB make sure that the correct settings have been chosen to boot from a BIOS or a UEFI prepared stick. If at all possible use a different USB as some just don't play nicely with booting PCs.
    At this stage my guess is that you are telling a PC which needs to boot from a BIOS setup to use a UEFI.
    Good luck.

      BuzzPCSOS I'm not exactly sure what you mean, but I'm assuming live loader, my computer still boots into windows just fine. I've tried two USB sticks now and redownloaded the iso a couple of times too, but I'll give the check sum thing a shot. My PC is ufei, I started out using ufei but now that I thinking about when I tried a different USB stick I also tried bios, I'll go back to making it with UFEI and see if that helps at all, will post back with results, thanks.

          I would assume the computer came with windows from the factory, probably fast boot and secure boot are enabled, try to disable them and try again.

          By the way

          superdecker64 I am a first time Linux user (not counting steam deck)

          I would recommend to try with a virtual machine and get familiar with the distro, as SteamOS works very different than Solus.

              superdecker64 that is a good plan. If you are making it to the first screen when booting from your USB then try using the selection for nomodeset which should allow use with NVIDIA graphics.
              It might be worth trying some other ISO loader program for your USB. Some good choices are Etcher, Ventoy or Rufus. They are all good and have different strengths but sometimes configuring one instead of another can make more sense and help you to understand what you are doing more.
              As a final try it would be worth using another Linux OS that has a Live environment (enters the OS direct from boot media without installing) just to prove it is a solus thing and not your configuration.

                nolan disabled secure boot, will double check and see if fast boot is enabled or not, thought it wasn't but could be wrong.

                Also appreciate the concern! Unfortunately I am a lazy bastard and if I don't force myself in balls deep first I'll never learn xD I did take a computer repair course in college and it went over Linux there (command line stuff) so I'm not going in completely blind at least

                    superdecker64 The thing that trips most folks up seems to be the UEFI/BIOS thing. Always worth a quick look at a tutorial here just to make sure you are on the right track.
                    If you are hoping to dual boot with Windows there are various hibernation variants that make any access to the hard drive more difficult. Always make sure you have shut down fully from windows. This should be adequately discussed elsewhere on this forum.

                        BuzzPCSOS I did look up how to check and my PC is definitely running on UFEI. Tried etcher and still no luck. I've checked a few tutorials but I don't think I've looked at one on this form specifically, mostly just the official guide, reddit, and some from YouTube.
                        Hmmmm, if I completely wipe my PC of windows and everything would that help at all? I'm not looking to dual boot for the moment, the only thing I think I'd outright need windows for is VR with oculus and I probably need to wait till I can build my own PC for that. I have a laptop I can use to make a new windows install media afterwards if it fails

                          BuzzPCSOS after a few more attempts, I think I'm gonna give Linux mint a shot for now and try Solus whenever I get around to building my own PC. Thanks for your help, and sorry for wasting your time

                            superdecker64 Hardware issue try noacpi in the live boot. (noapic is wrong no such thing)

                            Oh just saw your current post nobody wastes our time everybody is here to help and everybody
                            usually learns something in the process to.

                            good luck

                                Axios Hardware issue try noacpi in the live boot. (noapic is wrong no such thing)

                                I think I trust the Red Hat documentation more than you.

                                https://access.redhat.com/solutions/58790

                                According to that document there is in fact no such thing as noacpi, while noapic very much exists. What you mean would be acpi=off, as mentioned (and tried) by the OP.

                                    Staudey I stand corrected then and will always admit when wrong just dont make it personal.

                                      @superdecker64 I hope that you have an easier run with mint, feel free to come back and ask some more when you are ready. Solus is one of many great Linux operating systems and a very good choice for a newbie but also a great OS to stay with.

                                        BuzzPCSOS h

                                        BuzzPCSOS hello again, have an an update! I had the same issue when trying to install mint, I then tried Ubuntu and got a similar error. After getting frustrated I just started toggling a bunch of bios settings. Probably not a great idea but it ended up working! I think I disabled the onboard sata controller and also TPM (which I know I knew what that meant at some point but I sure do not remember anymore). Ubuntu installer seems to actually load now! Gonna give Solus installation another shot and see if it works now!

                                              Okay it's not recognizing the drive with windows now (probably the sata controller disabling did that which yeah probably should have seen that coming xD), gonna reenable sata controller and see if it still works and tpm was the issue or if it's some weird drive issue. I've run a couple disc checks and even downloaded a disk health manager and it all ran fine so not sure why it would be the drive, it's less than a year old. Only thing I could think of is when I installed the drive I was kinda of lazy and installed it into a new slot instead of removing the old broken one because whoever designed this case really did not want the original hard drives to be removed because wow the hard drive dock area is a mess of screws.

                                              Update: annnnd Windows is acting weird, says it lost my pin and to set it up again but everytime I try it just restarts and says the same thing, trying safe mode boot. If that doesn't work I think I'm gonna call an exorcist at this point. Don't need help quite yet, just documenting this in case someone else has this issue so they don't make the same mistakes I did

                                              Update 3: yeahhh I think the drive is just in the process of failing. Weird since every check passed and it's only a couple of months old. Think I'm gonna expedite trying to get hands on parts to build a new PC from scratch and salvage what I can from this cause I don't really trust it at this point

                                                I am guessing that your hard drive is an SSD, I have had an SSD in the past which gave good smart data but was failing badly all the same. If you have a spare hard drive that can be used to try instead then that would be a good thing to try.
                                                Edit: I have seen SSD drives on Windows with a proper installation go bad and couldn't find a reason for it. No virus, no torrenting, not a whole lot of anything except the registry was all over the place with crosslinks everywhere. Maybe an update failed at the wrong moment due to power outage or a forced restart. It could just be down to bathtub curve failure.
                                                Also it would be worthwhile to test the ram on your PC, there may be a pre boot option to do this in your UEFI/BIOS setup utility.

                                                superdecker64 After getting frustrated I just started toggling a bunch of bios settings. Probably not a great idea but it ended up working! I think ...

                                                Are you sure you have corrected what you did in BIOS. ? Then I would suggest go for a clean install of Solus.

                                                  [deleted]
                                                  Western Digital 1TB WD Blue PC Internal Hard Drive HDD - 7200 RPM, SATA 6 Gb/s, 64 MB Cache, 3.5" - WD10EZEX https://a.co/d/9UKsoKP
                                                  This is the drive
                                                  Disabling the sata controller makes the live launcher boot, yeah, altough there are two drives listed despite me only using one. I thought the one that was listed was my old broken drive I was too lazy to remove but I just opened up my PC and removed it today and it wasn't actually plugged in and now both drives are still listed in the bios. I didn't see any drive in there, googling the device name brings up an SSD but I didn't see one in there and looking at my PC model up it didn't come with one, and I didn't install one, so no idea what's going on there. Is there a way to disable SATA ports individually through like a command or something so I can test whether it's the phantom drive doing this or not?

                                                      If the SSD was unplugged it shouldn't have made a difference to Solus booting, it is still worth unplugging the WD drive and trying to boot again from your USB stick with no hard drive connected.
                                                      Usually the only place your previous drives will be listed is where the bios records the path to the boot image. This should not cause any problems with booting from a USB.