Now and then I used to come in touch with a PC (a laptop) of a friend of mine. This PC used to display a rather strange behavior. This PC, running Windows 7, would not correctly mount any usb hard disk or pendrive, except for a few new USB 3.0 drives. This Asus laptop had a really convoluted installation history, as even specifying the precise model it is not very easy to uniquely determine the specific driver to install for a given device. It turns out that every re-installation is made is a sort of trial-and-error procedure and the final outcome is, as one can see, not very nice.
Today I decided to fix my front panel USB , that were since long gone due an unspecified issue on my Asustek mobo (WYGIWYP, what-you-get-is-what-you-paid). Since the usual remedies wouldn’t work (resetting CMOS, changing front panel, BIOS fiddling) I decided to tackle the problem the hard way, by bypassing the motherboard completely.Read More »
As previously metioned here, I had boot issues with my new Motherboard, and my external Western Digital USB hard disk. But it’s really a motherboard fault, or not? It turns out other cheap USB enclosures dont’ endanger my boot like the WD hard disk does.
A little google-fu revealed that it’s indeed Western Digital fault, and not AsRock.
See the original post here. The solution, as it turns out, is to simply modifying the USB legacy option disabling it. The article mentions a Sony Vaio but it worked also for me on an Asrock motherboard. It seems to me that Western digital has something to fix, instead of bouncing the problems to other brands…
No more failed boots, it worked flawlessly since.
This script (very dirty) was handful to me to discover some parameters (e.g KERNELS) to differentiate on udev/rules.d rules similar devices on a physical usb port basis.
It’s relased under the GNU General Public License and with no guaranties. Please read the Disclaimer.
It needs of course udevadm and less.
Syntax is: showdevicedetails.sh
# Copyright (C) Giuseppe Dia 06/May/2011
# showdevicedetails.sh this script is useful to peek into a device details.
# Syntax: showdevicedetails.sh
# This program is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License
version 3 oas published by
# the Free Software Foundation, .
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
# You should have received a copy of the GNU General Public License
# along with this program. If not, see http://www.gnu.org/licenses/gpl-3.0.txt
if [ “$1” == “” ]
echo Please specify device e.g $0 /dev/ttyACM0
# is a block device.
if [ -b “$1” ]|| [ -c “$1” ]
echo “$1 is a device.”
$UDEVADM_BIN info -a -p $($UDEVADM_BIN info -q path -n $1)|$LESS_BIN
echo “$1 is not a device, or it doesn’t exist, please specify a valid device exiting”
Tonight the sheevaplug died, sending napalmpiri.openssl.it down. Dead cold. I suspected at once a PSU issue, and that turned out to be too true.
Warning: twiddling with the PSU means dealing with electricity at dangerous voltages. It involves a dangerous hot soldering iron. If you are not skilled these things may conjure up and ruin your day. Or you may burn down the house. This is not a joke. If you don’t feel confident, just buy another plug.
Unfortunately Globalscale technologies gives only a 30 days warranty, so I was basically stuck.
I think that the sheevaplug, from the hardware point, is really flaky. It may be good as a developer tool, but it’s just too flaky even as a home server.Read More »