linux-kernel - Re: Specify devices manually in exotic environment

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <op.tesbw5xzepq0rv@localhost>
Date:	Thu, 24 Aug 2006 13:08:55 +0200
From:	Milan Hauth <milahu@...glemail.com>
To:	"Denis Vlasenko" <vda.linux@...glemail.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Specify devices manually in exotic environment

On Thu, 24 Aug 2006 11:08:52 +0200, Denis Vlasenko  
<vda.linux@...glemail.com> wrote:

> On Wednesday 23 August 2006 21:40, Milan Hauth wrote:
>> I have tried MTD's NAND module according this [1] document, but it also
>> did not work.
>>
>> As Richard B. Johnson <linux-os@...logic.com> already mentioned, a  
>> regular
>> IDE interface has to be emulated. Somehow. Anyhow.
>
> Yes, I never saw flash-based IDE devices, but they exist, that's true.
> However, it's not necessarily what you have.
> I think that IDE devices should be detected by kernel at boot-up.
> You say that they are not. That's why I'm inclined to think
> your flash memory is not IDEish.

What I also forgot to mention is, that it's a SmartMedia Flash Card I have  
here, which is told to always identify as a IDE device.


> lsusb? Or if you have no lsusb, then:
>
> # mount | grep usb
> none on /proc/bus/usb type usbfs (rw)

Ohh, that's why lsusb never worked.. but you won't like the current result:

Bus 001 Device 003: ID 046a:002b Cherry GmbH  -->  Keyboard
Bus 001 Device 002: ID 0451:2046 Texas Instruments, Inc. TUSB2046 Hub
Bus 001 Device 001: ID 0000:0000  -->  What the..?


But I'm afraid I broke my SMC, while playing around with my disassembled  
T20, since GRUB hangs with 'GRUB _' without having changed anything in the  
software. D'oh!

That's why I can't test with 'USB Mass Storage' support in the kernel at  
the moment, which would probably uncover the mysterious '0000:0000' USB  
device. Gonna try again next week with a new SMC.

Cheers, milahu
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/