OP
Brickwizard
Well-Known Member
yes it boots normally [just takes a little longer to get going]
I get the normal grub
Mint LMDE
Mint advanced [recovery]
Solved Latitude 5490, NVMe conversion
- Thread starter Brickwizard
- Start date
Solved issue
yes it boots normally [just takes a little longer to get going]
Mint LMDE
Mint advanced [recovery]
Sounds more like normal booting isn't detecting the correct boot device or something or something similar. In the bios/uefi what options for selecting primary boot devices do you have and any other boot settings available?
Is your system an efi or bios install now?
OP
Brickwizard
Well-Known Member
boot order is set first NVMe second USB, in the drives I have disabled all but the NVMe
looks like it too, but it's finding what is causing the problem
Did you try updating grub "update-grub" and manually try reinstalling Grub on the nvme drive? What does your grub config look like now, so the part under "GRUB_CMDLINE_LINUX=" and share the output of the following?
Code:
sudo blkidSolved?
OP
Brickwizard
Well-Known Member
UP and running, My thanks to all
@f33dm3bits I used nano to make the edit,
@f33dm3bits I used nano to make the edit,
What did you change in Grub?
OP
Brickwizard
Well-Known Member
pcie_aspm=off
I don't have any experience with nvme drives but as I follow this thread, I wonder if there's something about this particular drive or this particular computer or this particular combination that requires some driver.
These are just my thoughts and I don't mean to suggest that you haven't already though of most (or all) of them for yourself...
If understand correctly, you can boot an OS from another device and then can see the files on the nvme drive then that implies that the computer and the drive are both working.
At boot time, the computer does not see the nvme drive - or does it just "not see it as bootable"?
After booting into an OS (using some other device), the nvme drive is seen.
Is the partition marked as "bootable" (fdisk/gdisk)? If more than one partition, is the -correct- one marked as bootable?
Is there maybe some driver that's compiled into the kernel (or loaded as a module or whatever) of the OS that you're booting (from usb) that would enable the nvme drive to be visible after boot even though it's not visible before booting?
Any chance there's a BIOS update for the computer that would help? Back in the day, wasn't there some issue where one had to jump through some hoops to boot from SCSI drives - though, really, I thought we were past that sort of thing.
Do you have access to another computer on which you could try test booting the nvme drive?
There have been posts while I typed this, so sorry if I'm behind in the thread.
These are just my thoughts and I don't mean to suggest that you haven't already though of most (or all) of them for yourself...
If understand correctly, you can boot an OS from another device and then can see the files on the nvme drive then that implies that the computer and the drive are both working.
At boot time, the computer does not see the nvme drive - or does it just "not see it as bootable"?
After booting into an OS (using some other device), the nvme drive is seen.
Is the partition marked as "bootable" (fdisk/gdisk)? If more than one partition, is the -correct- one marked as bootable?
Is there maybe some driver that's compiled into the kernel (or loaded as a module or whatever) of the OS that you're booting (from usb) that would enable the nvme drive to be visible after boot even though it's not visible before booting?
Any chance there's a BIOS update for the computer that would help? Back in the day, wasn't there some issue where one had to jump through some hoops to boot from SCSI drives - though, really, I thought we were past that sort of thing.
Do you have access to another computer on which you could try test booting the nvme drive?
There have been posts while I typed this, so sorry if I'm behind in the thread.
OP
Brickwizard
Well-Known Member
Hi Mike
the problem seems peculiar to some Dells from what I have read and effects all distributions [including broken windows]
there is a bit in the Grub called ASPM which is not supported on some machines so i had to edit Grub to turn it off, this is what finally lead to the answer
$ journalctl -b | grep ASPM
Nov 04 07:21:09 the-answer-42 kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
this is the first time I can remember having to edit the Grub
Right then. I -was- a bit behind. Glad it's working.
Regarding "this is the first time I can remember having to edit the Grub"...
While I'm not familiar with that setting in grub (as I'm not using any modern DElls) I've always written grub.cfg in a text editor - I only recently realized there are a bunch of programs in addition to grub-install included with grub2. I don't do any major magic with it, but might be able to help if you find yourself going further down that road. (Though really, grub.cfg is a lot like shell script. To me, that's is one of its most endearing features.)
Regarding "this is the first time I can remember having to edit the Grub"...
While I'm not familiar with that setting in grub (as I'm not using any modern DElls) I've always written grub.cfg in a text editor - I only recently realized there are a bunch of programs in addition to grub-install included with grub2. I don't do any major magic with it, but might be able to help if you find yourself going further down that road. (Though really, grub.cfg is a lot like shell script. To me, that's is one of its most endearing features.)
OP
Brickwizard
Well-Known Member
Boot time reduced by 60% we are flying
@Brickwizard :-
Nice to hear you finally got it sorted. That sort of thing is frequently very, VERY frustrating, and can take ages to track down.
See, this is yet another thing I love about our Pup. The way she boots up, even on an old HDD it's pretty fast anyway. You switch to even an "ordinary" SSD, and it's magnitudes faster. My Pups on the E6430 are all at desktop between 10-15 seconds after hitting the power button....
That's plenty fast enough for me.
I followed the thread for a bit, but I got kinda lost after a while.....!!
Mike.
Nice to hear you finally got it sorted. That sort of thing is frequently very, VERY frustrating, and can take ages to track down.
See, this is yet another thing I love about our Pup. The way she boots up, even on an old HDD it's pretty fast anyway. You switch to even an "ordinary" SSD, and it's magnitudes faster. My Pups on the E6430 are all at desktop between 10-15 seconds after hitting the power button....
That's plenty fast enough for me.
Heh. Y'know, this reminds me of a few years back over at BleepingComputer. @wizardfromoz :- Chris, d'you remember that? A bunch of the guys in the Linux & Unix forum were having a kind of competition to see who could get their boot times down the fastest.....playing around with all kinds of settings in the BIOS/UEFI. modifying the kernel exec line, changing & altering everything they could think of to shave off a few fractions of a second more.
I followed the thread for a bit, but I got kinda lost after a while.....!!
Mike.
@Brickwizard Congrats on getting it sorted. Happy it worked out for you!
Happy it worked out for you!
Yeah, they were using systemd-analyze blame and critical-chain as a diagnostic.
@Brickwizard glad for the favourable outcome. I like the references to deep thought and answer 42.
Wiz
OP
Brickwizard
Well-Known Member
I bought this from the .Magratheans as salvaged stock from the building of the new super computer,
I like the crinkly bits that Slartibartfast did with the Scandinavian fjords.
Avagudweegend
Avagudweegend
OP
Brickwizard
Well-Known Member
Sorry David, but I didn't like it at all, to my mind they cut so much out what was left seemed to me totally disjointed
