Sorry for the delay responding to this thread. Whilst linux users'
computers are immune to viruses, our bodies are not. I spent Tuesday
evening through late Wednesday afternoon in bed with the flu, and I'm
still not 100%.
On Tue, Apr 18, 2006 at 10:51:44AM +0800, Fr?d?ric Grosshans wrote
Le
Le mercredi 19 avril 2006 à 10:41 +0800, David a écrit :
On Tue, Apr 18, 2006 at 10:59:00PM +0800, Fr?d?ric Grosshans wrote:
I'll try when I'm back home (in may)
If you are in Beijing,
it is easy to do the test using an external usb hub with it's own
power supply for free. Because Beijing
On Wed, Apr 19, 2006 at 09:56:51PM +0800, Fr?d?ric Grosshans wrote:
Le mercredi 19 avril 2006 ? 10:41 +0800, David a ?crit :
On Tue, Apr 18, 2006 at 10:59:00PM +0800, Fr?d?ric Grosshans wrote:
I'll try when I'm back home (in may)
If you are in Beijing,
it is easy to do the test using an
Le mardi 18 avril 2006 à 13:20 +0800, Frédéric Grosshans a écrit :
L
Which in turn come from the table in
/usr/src/linux/drivers/usb/storage/unusual_devs.h. Maybe you can try
adding an entry for your device to that table? Something like:
UNUSUAL_DEV( 0x1043, 0x8006, 0x0110, 0x0110,
On Tuesday 18 April 2006 05:04, Frédéric Grosshans wrote:
[*]
OK. I have
sanduleak ~ # find /dev/disk/ -iname '*usb*'
/dev/disk/by-path/usb-0x1043-0x8006:0:0:0
/dev/disk/by-id/usb-Generic_USB_Flash_Drive
[*]
Any other idea ?
Never give up.
Try hexdump on the
Le mardi 18 avril 2006 à 09:12 +0200, Petr Kocmid a écrit :
On Tuesday 18 April 2006 05:04, Frédéric Grosshans wrote:
Any other idea ?
Never give up.
That seems to be your moto :-)
Try hexdump on the device above:
hexdump -C /dev/disk/by-id/usb-Generic_USB_Flash_Drive
I'm currently
On Tue, 18 Apr 2006 15:37:54 +0800, Frédéric Grosshans wrote:
There is indeed an encryption feature on this key. I've never used it (I
haven't even downloaded the windows-only software allowing to use it).
Can it be related to this problem ?
Possibly. Some USB keys use two partitions for
Le mardi 18 avril 2006 à 15:37 +0800, Frédéric Grosshans a écrit :
So my next steps are :
1. Switching back to usb-storage
2. Trying to dd the disk
3. That doesn't work, trying to get access to another computer and see
if I can do something.
Of course, I meant *If* that
Le mardi 18 avril 2006 à 09:05 +0100, Neil Bothwick a écrit :
On Tue, 18 Apr 2006 15:37:54 +0800, Frédéric Grosshans wrote:
There is indeed an encryption feature on this key. I've never used it (I
haven't even downloaded the windows-only software allowing to use it).
Can it be related to
On Tuesday 18 April 2006 10:14, Frédéric Grosshans wrote:
Any idea left ?
So, you definitely have a hardware problem. Digging for the id of your device
1043 8006 reveals a linux kernel mailing list archive thread:
http://www.ussg.iu.edu/hypermail/linux/kernel/0410.0/0023.html
with the
Frédéric Grosshans wrote:
Le lundi 17 avril 2006 à 18:51 +0100, Konstantin V. Gavrilenko a écrit :
On the example of the SD card reader, when you insert the card, /dev/sdb
appears, but not the actual partition (/dev/sdb1)
So you have to do fdisk /dev/sdb, then quit, then the /dev/sdb1 is
On 4/18/06, Frédéric Grosshans
[EMAIL PROTECTED] wrote:
The first time I saw those 32 MB (a few days ago, when the key worked
and was almost empty), df -h told me there was 1006 MB left on the key.
Wait, it worked before under Linux? I don't think you mentioned that
previously. Was this on
Le mardi 18 avril 2006 à 06:25 -0700, Richard Fish a écrit :
On 4/18/06, Frédéric Grosshans
[EMAIL PROTECTED] wrote:
The first time I saw those 32 MB (a few days ago, when the key worked
and was almost empty), df -h told me there was 1006 MB left on the key.
Wait, it worked before under
Le mardi 18 avril 2006 à 11:47 +0200, Petr Kocmid a écrit :
On Tuesday 18 April 2006 10:14, Frédéric Grosshans wrote:
Any idea left ?
So, you definitely have a hardware problem. Digging for the id of your device
1043 8006 reveals a linux kernel mailing list archive thread:
On Tue, Apr 18, 2006 at 10:59:00PM +0800, Fr?d?ric Grosshans wrote:
Le mardi 18 avril 2006 ? 11:47 +0200, Petr Kocmid a ?crit :
On Tuesday 18 April 2006 10:14, Fr?d?ric Grosshans wrote:
Any idea left ?
So, you definitely have a hardware problem. Digging for the id of your
device
I've a problem with a recently bought usb disk:there is a /dev/sda node
but no /dev/sda1 . When I try to access /dev/sda, I've the following
errors :
sanduleak ~ # fdisk /dev/sda
Unable to open /dev/sda
sanduleak ~ # dd if=/dev/sda of=/dev/null
dd: opening
Hey Fred.
Is the USB key in question formatted with a FAT partition by chance? If
so, you may need to load the vfat module as root, or, build vfat
(Windows FAT32) filesystem support into your kernel, or perhaps, add an
entry for the USB key in your /etc/fstab if you already have vfat support.
On Monday 17 April 2006 16:24, Frédéric Grosshans wrote:
Bus 003 Device 006: ID 1043:8006 iCreate Technologies Corp.
Flash Disk 32 MB
This is a not an iCreate 32MB drive, but a Kingston DataTraveler Elite
1GB drive. I did some first tests with small files, and it worked OK. I
Hi Jeff
Le lundi 17 avril 2006 à 10:52 -0400, Jeff a écrit :
Is the USB key in question formatted with a FAT partition by chance?
I think, if it was a format problem, I would see a /dev/sda1 node, but
wouldn't be able to mount it. I don't even see that /dev/sda1 , and
fdisk has no access to
Le lundi 17 avril 2006 à 17:26 +0200, Petr Kocmid a écrit :
On Monday 17 April 2006 16:24, Frédéric Grosshans wrote:
This is a not an iCreate 32MB drive, but a Kingston DataTraveler Elite
1GB drive. I did some first tests with small files, and it worked OK. I
Suddenly, I have so called
On Monday 17 April 2006 17:49, Frédéric Grosshans wrote:
Le lundi 17 avril 2006 à 17:26 +0200, Petr Kocmid a écrit :
What fdisk -l /dev/sda says when you plug it in? You should get something
as:
[snip]
I don't get anything :-(
sanduleak ~ # fdisk -l /dev/sda
sanduleak ~ #
Le lundi 17 avril 2006 à 18:23 +0200, Petr Kocmid a écrit :
On Monday 17 April 2006 17:49, Frédéric Grosshans wrote:
Le lundi 17 avril 2006 à 17:26 +0200, Petr Kocmid a écrit :
This is (sadly) consistent with the lack of /dev/sda1 device.
So be it, let's suppose there is something wrong
I noticed similar behavior on the externally connected usb storage devices.
On the example of the SD card reader, when you insert the card, /dev/sdb
appears, but not the actual partition (/dev/sdb1)
So you have to do fdisk /dev/sdb, then quit, then the /dev/sdb1 is
magically available for
Good. According to processed events, there is a raw disk dedected properly but
no partition processed. If you still do not see /dev/sda, try to look for
your disk at folowing locations:
/dev/disk/by-id/usb-*something*
and
/dev/disk/by-id/usb-*something*-part1
or
Le lundi 17 avril 2006 à 18:51 +0100, Konstantin V. Gavrilenko a écrit :
On the example of the SD card reader, when you insert the card, /dev/sdb
appears, but not the actual partition (/dev/sdb1)
So you have to do fdisk /dev/sdb, then quit, then the /dev/sdb1 is
magically available for
Le lundi 17 avril 2006 à 20:22 +0200, Petr Kocmid a écrit :
Good. According to processed events, there is a raw disk dedected properly
but
no partition processed. If you still do not see /dev/sda, try to look for
your disk at folowing locations:
/dev/disk/by-id/usb-*something*
and
On 4/17/06, Frédéric Grosshans
[EMAIL PROTECTED] wrote:
When I plug it, tje following entries are added to dmesg :
usb 3-2: new full speed USB device using uhci_hcd and address 6
scsi2 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 6
Le lundi 17 avril 2006 à 22:24 +0800, Frédéric Grosshans a écrit :
I've a problem with a recently bought usb disk:there is a /dev/sda node
but no /dev/sda1 . When I try to access /dev/sda, I've the following
errors : [...]
Thanks for everyone who has helped. To have more information, I
Le lundi 17 avril 2006 à 20:44 -0700, Richard Fish a écrit :
On 4/17/06, Frédéric Grosshans
This doesn't really matter. It comes from the database at
http://www.linux-usb.org/usb.ids
OK. Thanks
However, I think the kernel doesn't fully recognize your device. Your
dmesg output seems to be
29 matches
Mail list logo