I'm command line literate, but I'm not sure how to work around this one.

Here's my setup:

TOSHIBA Qosmio X505-Q894
Specs Link (Toshiba site PDF)
-6 GB RAM
-Loading Debian 8.0.2 i386 without desktop environment

Here's what I get at boot:

I think this is an ACPI issue. I'm not sure if I should look into disabling ACPI (not sure what the effects would be) or if I should be looking at some kind of patch/config fix.

Anyone come across anything like this before?

The rest below is more detailed stuff I've uncovered in this problem, but not necessary to read (as far as I can tell). I'm still posting it just in case it contains some important info pertaining to my boot problem that I missed.

Any ideas?

============================
======The long version =====
============================
============================
============================
============================
============================

How to eat an elephant? One bite at a time.

You have posted a lot. Although not impossible to help you solve your problems, I would suggest you post several small problems rather than one big post with a lot of problems.

I apologize. Usually people complain for not posting enough info and poorly giving the context.

That's why I put the "long version" in there underneath some separation. I wish there were more tags (like [compress][/compress]) so I could include seemingly relevant info but not make the post look huge.

I didn't want to give the impression that I was reaching out without having done any work to fix it myself.

I'll reformat the post to try and separate the important bits better.

If I may suggest, make a list of the problems, then prioritize them (text editor or pen and paper). Then post smaller questions, possibly one at a time.

Thanks for helping me to help you. Not that I can wave a magic wand, but the "fsck" error caught my eye because I recently had a similar question. It got solved. Actually, there really was no solving to do with that particular *announcement*, for lack of a better word. This fsck announcement, in my case, was simply a new Debian "thing" not to worry about or try to fix. I, like a lot of others as I learned, just let Debian do its bootup routine, and this is a part of it. Although, with the "KVM" note there may be something to fix.

Again I apologize. I didn't realize which was the most relevant, let alone which symptom would take priority.

Since my last post I've tried installing Ubuntu Server. Some package is included that solved the issue I was having, and I'm pretty sure it was an ACPI driver. The miracle package in question caused my laptop to go to sleep when the lid was closed, but at least that was the only issue, and it was easily fixed.

I think that package had something to do with "systemd". The config file was /etc/systemd/logind.conf

Any idea what package uses that config file? I'm gonna reinstall Debian, startup in recovery mode and start searching the repositories for "systemd". I found some entries on my Ubuntu installation that have "systemd" as a part of it, but haven't found anything that was just straight "systemd".

It would seem that priority 1 is to find all the right drivers (duh ... hardware 101).

Thanks for the kickstart. My train of thought finally got back on track, so I have a few more ideas to try.

If you have any more ideas or advice I'll certainly appreciate the consideration! I'll report back my findings.

Did a

and a

for the appropriate directory location of logind.conf,

and read that this file is a part of "systemd".

Did a

and I see, at first, what may be an interesting read.

Respectfully recommend you read up on

That's all I got for now...early morning calls.

I actually did try that and there were no results in the man pages on my system. Apart from reinstalling Debian maybe when I manually install systemd I will finally be able to see those man pages.

If you have internet access, maybe try

http://www.freedesktop.org/software/...n/systemd.html

It is an online man page for "systemd".

Ah hah! Thanks!! I can't believe that didn't cross my mind.

If you do a web search for "online man pages linux", there should be several to choose from. Whether Unix pages and Linux pages are exactly the same, I would doubt. So, you may not be able to settle on the first result (in my post), as accurate and applicable to your situation. You may have to search for yourself even further. But, they're out there on the Net. I'm glad you have capabilities to do a search yourself and pick a manual page that is most suited to your use.

Just wanted to finally report back a solution!

It turns out that for some reason, the KVM switch (attached via DVI + DVI>HDMI adapter) I was using was actually causing Debian to hang on boot. After doing a clean install of Debian without the KVM switch attached, everything worked fine.

EDIT: Also when I booted into recovery mode, everything worked fine as well with the KVM switch. I'm not inclined to troubleshoot any of that currently. Finally got the setup I was looking for.

The funny thing about this is that the last BIOS update I found for this laptop actually allowed the HDMI port to be used to view the boot screens. This WAS particularly helpful to me in that I use a KVM switch. Now however, I have nothing of the sort hooked up to this laptop anymore.

I finally learned how to configure SSH with public/private keys so there's no more need for actually seeing the screen anymore.

Can't believe it was so darn simple. Not sure what it was about that KVM switch I used, but it doesn't matter anymore!

I guess the "kvm: disabled by bios" bit was a bit more relevant than I thought. Never knew KVM switches were recognized at that level.

@theAdmiral
- Thanks for your patience. Sorry it took me so long to get back to participate in solving this one.

Glad you got it solved!