Hello!

I'm back again, with my actual meds so I'm hoping how I process these new questions and retain them will exceed my previous questions. That aside here goes the question:

I am running:

So i had a Latop (Dell Latitude E6430)
However one of my friends had theirs stolen so I gifted it to them to help them with their schooling.
I took my HDD out and put it into my desktop which has the information you see at the top of this post.
(they had their own spare HDDS)

I am currently typing from the latops os so it boots just fine.

My question is this:

How do i figure out how to find all drivers that are not in use or incorrect so I can migrate this HDD to my main OS without having to format and start over?

I figured that say the video drivers would be incorrect so I sudo apt purged Nvidia* and then installed the drivers I knew that I needed. However I'm not sure where to even begin to track down any other useless or incompatible drivers and such floating around to purge them and install what is proper.

Any and al input is greatly appreciated!

A distro and hence generally the kernel has it's own set of drivers.

Sometimes you can add in drivers to make your hardware work or work better.

Anyways. "how to find all drivers that are not in use or incorrect" to be exact you put your distro in that hardware but you could find out every device in this new hardware I guess.

I'd think that most people would say slap it in and see what it does. If you know it needs broadcom wifi then add it in but many distro's can be run from command line boot options to get going for video. Guess you could blacklist a driver before you move it.

Can't hurt to take over a live dvd or live usb to test.

3 members found this post helpful.

Linux distros have long been evolving good capability to automatically determine and load appropriate drivers in most cases. Failures usually only occur with newest hardware, or with rare exotics, or if not removing inappropriate proprietary drivers (e.g. NVidia). So, as suggested by jefro, just try. If everything works apparently as expected, you're done. I do it often. Most often if there's any problem, it's either NVidia driver-related and fixable without inordinate trouble, or sound-related, so not an impediment to important functions.

So it boots fine, and I didn't know if making another thread on this would count as clutter or be good.
However when I startup I see messages flashing on the screen. I recorded them on my phone and slowed them down but how do I view start up messages in debian 10?

On the screen i saw a massive list of things including messages like:

"[Firmware Bug]: TSC_DEADLINE disabled due to Errata"

I need to figure out where these are so I can try to resolve them individually. The deeper i go the more I seem to learn slowly.

Do you happen to know where these boot messages are or could possibly be stored so I can go through the start up messages?

Some boot messages can be found using dmesg. Others can be found using journalctl. Some can be found in both. Some can be found in neither. Some can be found only by adding various boot options intended usually for debugging. Some can be seen by using a serial console with a scrollback (something I've never tried successfully). I'd start with journalctl, which automatically filters through a pager.

Some messages that look threatening amount to no more than annoying noise. If you find what appears to be an error or failure, it doesn't necessarily matter.

The data that journalctl uses may or may not be persistent, meaning that it survives rebooting, and can retain info dating back weeks, months or years ago. If /var/log/journal/ exists, then the journal is persistent.

https://askubuntu.com/questions/9849...i-do-about-thi

From that link it suggests to update firmware.

Thanks dude Appreciate yours and everyones input.