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'.
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.
The sensible thing to do in this case is examine what has been installed after the initial install.
You can find that out in file /var/log/apt/history.log if you are using apt, or /var/log/aptitude if using aptitude.
Remove these packages one by one and check your boot time.
Do not autostart services that you do not need after every boot. I am looking at skype for instance. Start it manually if you really need to use it.
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.
Works for me too. (But I am on Debian sid.)
Looks like you are missing package 'libusb-1.0-0-dev'.
Restart from the beginning, especially watch for installation of mentioned package in the fist step (sudo apt-get install ...)
Copy/paste the whole line to prevent typo's.
Both cli and frontend work.
1. How to slim down your initrd:
Check initrd filesize in /boot ( ls -alh /boot )
As root, edit /etc/initramfs-tools/initramfs.conf:
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.
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.
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 ).
1. Unpacking initramfs takes 0.5s, not 5s. Your initramfs is BIG. I am sure it can be reduced in size by only including in it what you really need.
2. Mounting your root filesystem does take 5s, which is a lot. probably because the root partition is BIG.
Post output of
to show us the size and usage.
To eliminate misunderstandings, you must realize that xrandr only has an effect for graphical applications - for xserver clients.
xrandr has no effect on the virtual console(s).
It is possible that you have to re-enter the xrandr command after a wake-up from sleep or hibernation.
if you want everything in a lower resolution - virtual consoles and xserver clients, you could add the 'nomodeset' kernel parameter.
@DJ, concerning LFS:
Did you verify the system requirements before you started building LFS, especially the requirement that /bin/sh should be link to /bin/bash?
The build instructions assume that the Host System Requirements, including symbolic links, have been set properly:
bash is the shell in use.
sh is a symbolic link to bash.
/usr/bin/awk is a symbolic link to gawk.
/usr/bin/yacc is a symbolic link to bison or a small script that executes bison.
Just another guess at what could have made things poop out for you
How would i mount the volume group from the grml cd?
1. boot into live system from grml CD - enable lvm
2. create a mount point and mount the lvm, e.g.
sudo mount /dev/mapper/vg_debian-root /tmp/lvm1
How would I check the initramfs of the internal hd?
lsinitramfs <path-to-your-initramfs-fileon hd>
False alarm, caused by
I did the dist-upgrade and everything is still working OK for me.
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?
Thread with caution.