CrunchBang Linux

You need the version from backports for package libusb-1.0-0-dev

See http://backports.debian.org/Instructions/ for instructions on how to do this.
Follow instructions for 'wheezy'.

In short:
1. edit /etc/apt/sources.list
2. run sudo apt-get update
3. run sudo apt-get -t wheezy-backports install libusb-1.0-0-dev
4. restart the 'make' command that gave you errors. It should run OK now.

One way to check if 'libusb-1.0-0-dev' is installed is:

apt-cache policy libusb-1.0-0-dev

Another way is

dpkg -L libusb-1.0-0-dev

The second one lists all files in the package. The file you seem to be missing is '/usr/include/libusb-1.0/libusb.h', which defines the libusb_log_level enumeration.

@overkill

1. How to slim down your initrd:

   Check initrd filesize in /boot ( ls -alh /boot )

   As root, edit /etc/initramfs-tools/initramfs.conf:

   replace

MODULES=most

by

MODULES=dep

   Save the file and rebuild initramfs:

sudo update-initramfs -u

   Check initrd file size in /boot. Compare with the original file size.

   Reboot to test if it works.

   Remarks:
   
   1. Your initrd is 26MB. On a default lubuntu install it is 19M. How come?
   2. This will shave off only a fraction of your total boot time.
   3. You have kernel version Linux version 3.13.0-29-generic running. Default is Linux version 3.13.0-24-generic. How come? Where did you get it from?

2. For the 5s your system needs to the HP screen, google for 'slow boot on BIOS' for suggestions to cure.

3. Mounting your root file system does NOT take excessively long.

Conclusion:

Your system boots in approx 22s according to the logs, including bringing up the wireless. I don't use upstart and I don't know it well enough to judge if that is reasonable or not. I guess systemd can do better?

So it takes 30s or more to set up your working environment up to the login prompt. Use suggestions from previous posts to reduce that time, or post more information ( start by posting output of 'ps -eF' after logging in,to show what you have running ).

Hi el_k,

Did not recognize you in that show. Must say you looked better with the beard and the sunglasses.

Best wishes to you and the #! crowd.

xaos

Or you could retain kms settings but specify your own resolution:
See this post

@OP - So the EDID info from your screen is correct.
Post output of

xrandr

to see which alternatives are available.

This is caused by 'Kernel Mode Setting' stepping in.
See the Debian wiki for more information.
What gfx card do you have? Post output of

lspci -knn | grep -EiA2 vga

Your gfx card may need a newer kernel.
See this thread for suggestions.

Did you do a normal install on the second system or somehow - rsync perhaps? - copied over the files?

Post output of

xrandr
cat /var/log/Xorg.0.log

from the malfunctioning system please.

ADHD Joe?

Are you mixing repos?
What repo are you tracking?
Post your /etc/apt/sources.list file please.

I installed gthumb myself now - on a Debian jessy system - and it works OK.
Of course it could be your data that is causing problems.

Never mind.

False alarm, caused by

this post
this bug report
and new package - libllvm3.2:amd64 (1:3.2repack-10) ... - being installed when you dist-upgrade jessy.

However,
I did the dist-upgrade and everything is still working OK for me.

Proviso:
I was already running kernel 3.9-1-amd64 #1 SMP Debian 3.9.8-1 - perhaps the problem occurs when upgrading from an older kernel?

Conclusion:
Thread with caution.