Hello there, I’m trying to run Tumbleweed live on my usb drive sadly after 3-5 minutes of booting screen (after I choose if I want to open the os or recovery) it crashes, gives me the input:
3.013124] Coudn't get size: 0x8(a lot of 0's)e
3.013164] MODSIGN: Couldn't get UEFI db list
3.013124] Coudn't get size: 0x8(a lot of 0's)e
3.013124] Coudn't get size: 0x8(a lot of 0's)e
Then it tells things like there is a report text file and I should reboot my system, after that it just sends me to systemd terminal.
My Computer has gtx1070, i7 and 16gigs of ddr4 ram. And normally runs win10x64.
The tumbleweed live iso file I downloaded was for x86_x64 and had KDE, although I also tried with gnome, which gave me the same result.
The usb was formatted as FAT32.
Those messages are not important. If it is really crashing, then the crash happens after that, and is not related. You can safely ignore those messages.
Then it tells things like there is a report text file and I should reboot my system, after that it just sends me to systemd terminal.
That’s the part that might have more useful information about your problem. Can you provide a little detail about what it says?
My Computer has gtx1070, i7 and 16gigs of ddr4 ram. And normally runs win10x64.
Possibly that nvidia card is the problem. Can you add “nomodeset” to the kernel boot line? Perhaps that will get you booted.
When you get to the boot menu, hit ‘e’. That should give you an edit screen.
Scroll down until you find a line that starts “linux” or “linuxefi”.
Hit the END key to get to the end of that line. Enter “nomodeset” (perhaps with a preceding space to separate from other parameters).
(sorry for the dramatic, stock image site angle on that second photo)
Then the usual message.
Also how do we get the .txt file? i tried to copy using “cp (report files name).txt sdb1”
Since that didn’t do anything i tried to find where the file is located with “ls ~/” and learned that we can’t do that in this shell. As you see, i am quite new in this stuff.
The first image doesn’t have much that is useful. The “device not accepting address” might be a problem. All of the other lines can usually be ignored.
The second image suggests that you are actually in a dracut shell. So there is something about your hardware that the system does not like, and it did not complete booting.
Sorry, I don’t see any mention of a txt file – I guess if is off the edge of the image.
I don’t have any experience using the dracut shell. I’ll wait and see if someone else can add further help.
IMO all of what you posted are signs of a failed UEFI boot, specifically unable to boot to a USB drive.
Follow the instructions in the following article (written for booting into MINT, but the important and relevant steps are what you have to do in Windows to boot to first disable Fastboot, and then to reboot to a USB drive (Windows must allow mounting the USB drive).
That should take you down to the first part of “Step 03”
The latter part of “Step 03” appears to be attempts to boot using commands which normally boot to an MBR system.
In fact, rather than all the complications related to booting through UEFI,
It’s also possible to just switch to MBR in your Windows UEFI configuration (Yes, you will see warnings about possibly never again being able to boot to Windows again. You decide. I’ve never experienced a problem on several machines but the warning cannot be ingnored). And, then when you are finished experimenting with the LiveCDs, you should be able to switch back to re-enabling UEFI or just leave it booting to MBR. I know of only one quasi-theoretical exploit that attacks an MBR system, I haven’t heard of any more.
Ah the text file? yeah its called (something)sosreport.txt, it tells me to save that report file however i don’t know how to copy it to my disk.
IMO all of what you posted are signs of a failed UEFI boot, specifically unable to boot to a USB drive.
Follow the instructions in the following article (written for booting into MINT, but the important and relevant steps are what you have to do in Windows to boot to first disable Fastboot, and then to reboot to a USB drive (Windows must allow mounting the USB drive).
That should take you down to the first part of “Step 03”
The latter part of “Step 03” appears to be attempts to boot using commands which normally boot to an MBR system.
In fact, rather than all the complications related to booting through UEFI,
It’s also possible to just switch to MBR in your Windows UEFI configuration (Yes, you will see warnings about possibly never again being able to boot to Windows again. You decide. I’ve never experienced a problem on several machines but the warning cannot be ingnored). And, then when you are finished experimenting with the LiveCDs, you should be able to switch back to re-enabling UEFI or just leave it booting to MBR. I know of only one quasi-theoretical exploit that attacks an MBR system, I haven’t heard of any more.
HTH,
TSU
I did those on my bios actually, but i’ll re-check, thank you.
You say that the USB is FAT formatted. But it should not be after you have properly transferred the ISO. The iso is a boot ready image and should replace any FAT partitioning. You need to do an exact unmodified binary copy of the ISO to the USB device. NOT to a partition on the device.
Note that even if you make direct BIOS settings, you still can’t boot directly to your LiveCD, you have to follow instructions exactly when you reboot from Windows.
I’m not sure of the limitations of the dracut shell. But it probably supports “mount” and “cat”.
If possible, you would mount a partition at “/mnt” then see if you can copy the file to there. I don’t know anything about what is available on your system to mount. The USB that you are booting from should have two partitions. The smaller of those (partition 1) is the EFI partition. If you can’t think of anything else, you could probably copy to there (after mounting).
Another option would be to use “cat” to list the file content, and then use pencil and paper.
Exactly how did you create the USB. FAT should not have anything to do with live image.The image is boot ready binary image that should be copied to the device not a partition on the device. And certainly not a FAT partition. The only thing that is FAT related is a small FAT formatted partition used by EFI boot code in the image. By any chance did you use Rufus? If so you need to use the dd copy option to keep it from modifying the ISO.
Sadly that didn’t change anything. i did close fastboot but pressing shift on reboot does not show the use a device option for me, the rest is there. Im gonna try few things on bios for getting that option, it seems like its a bios related issue according to the internet.
Yes i used rufus but the dd copy option seems to be removed i couldn’t find anything about it, also tried unetbootin.
I first used the ordinary windows “format disk” thing, made it fat. then tried the formatting of xboot, then tried with rufus, then tried with unetbootin, then tried with imageusb. They all gave me the same result.
Note in the MSWindows reboot,
The first screen includes an option (IIRC may be the first option) that allows rebooting to, or at least mounting any USB connected devices.
