Asus screenDUO

Asus screenDUO

[bob]

Hello.  I'm posting here because someone asked (a long time ago) for a 
driver or app that would drive a little usb gadget (mini vga display)
called the screenDUO that comes with Asus motherboards.  I recently put 
a bunch of work into it (multiline support, color text, pixel drawing, 
etc.)  And its quite useful (but no button support yet).
If you are interested in the app, search on github for screenduo4linux.  
I won't post the url because the spam filter would kill this whole message.
Thank you.

Re: ASUS ScreenDuo

[Wander Winkelhorst]

>  > This is pure wild guessing since I have no clue about SideShow or this
>  > device.  Anyway it would be hard to proceed without capturing a trace
>  > or managing to find some docs somewhere.
>
>  I certainly have no intention of installing vista on this host. I'll see
>  if I manage to borrow a windows laptop somewhere.

You could also open the device up, snap a few pictures of it and start
googleing for chip datasheets.
Who knows what kind of fun chips might be hiding in there, Could be an
ARM for instance.

Regards,
Wander.

Re: ASUS ScreenDuo

[Xavier Bestel]

On ven, 2008-04-04 at 11:22 -0400, Bob Copeland wrote:
> On Fri, Apr 4, 2008 at 10:55 AM, Xavier Bestel <xavier.bestel@free.fr> wrote:
> >  > If it is supposed to implement the MS SideShow API, then that would be
> >  > the .NET VM (i.e. C#).  My 10 second googling turned up some info about
> >  > that but I couldn't find a definition of how the hardware interface
> >  > for such devices is supposed to work.  There's some XML-laden software
> >  > API but it seemed to be transport agnostic.
> >
> >  Wouldn't there be at least 2 interfaces to the device ?
> 
> Who knows, they could have a almost-mass-storage protocol layer that
> recognizes proprietary stuff in the URBs.  It could be as simple as:
> 
>  - User clicks 'synchronize' in some windows app
>  - Device driver on host does some magic to make Asus device pretend like
>    removable media was inserted
>  - Vista sees the new device, mounts it
>  - App copies C# classes and XML files to special directories on the device
>  - App ejects device

Fair enough.

> Does the screen turn on or is that software controlled too?

There's a power-on button, which lits the screen and makes the device
connect to the usb host.

> This is pure wild guessing since I have no clue about SideShow or this
> device.  Anyway it would be hard to proceed without capturing a trace
> or managing to find some docs somewhere.

I certainly have no intention of installing vista on this host. I'll see
if I manage to borrow a windows laptop somewhere.

Thanks,
	Xav

Re: ASUS ScreenDuo

[Bob Copeland]

On Fri, Apr 4, 2008 at 10:55 AM, Xavier Bestel <xavier.bestel@free.fr> wrote:
>  > If it is supposed to implement the MS SideShow API, then that would be
>  > the .NET VM (i.e. C#).  My 10 second googling turned up some info about
>  > that but I couldn't find a definition of how the hardware interface
>  > for such devices is supposed to work.  There's some XML-laden software
>  > API but it seemed to be transport agnostic.
>
>  Wouldn't there be at least 2 interfaces to the device ?

Who knows, they could have a almost-mass-storage protocol layer that
recognizes proprietary stuff in the URBs.  It could be as simple as:

 - User clicks 'synchronize' in some windows app
 - Device driver on host does some magic to make Asus device pretend like
   removable media was inserted
 - Vista sees the new device, mounts it
 - App copies C# classes and XML files to special directories on the device
 - App ejects device

Does the screen turn on or is that software controlled too?

This is pure wild guessing since I have no clue about SideShow or this
device.  Anyway it would be hard to proceed without capturing a trace
or managing to find some docs somewhere.

-Bob

Re: ASUS ScreenDuo

[Xavier Bestel]

On Fri, 2008-04-04 at 10:37 -0400, Bob Copeland wrote:
> On Thu, Apr 3, 2008 at 5:24 PM, Lennart Sorensen
> <lsorense@csclub.uwaterloo.ca> wrote:
> >  Well apparently vista expects the device to support running programs
> >  written in .NET Micro Framework.  Maybe that is some JVM like thingy.
> 
> If it is supposed to implement the MS SideShow API, then that would be
> the .NET VM (i.e. C#).  My 10 second googling turned up some info about
> that but I couldn't find a definition of how the hardware interface
> for such devices is supposed to work.  There's some XML-laden software
> API but it seemed to be transport agnostic.

Wouldn't there be at least 2 interfaces to the device ?

	Xav

Re: ASUS ScreenDuo

[Bob Copeland]

On Thu, Apr 3, 2008 at 5:24 PM, Lennart Sorensen
<lsorense@csclub.uwaterloo.ca> wrote:
>  Well apparently vista expects the device to support running programs
>  written in .NET Micro Framework.  Maybe that is some JVM like thingy.

If it is supposed to implement the MS SideShow API, then that would be
the .NET VM (i.e. C#).  My 10 second googling turned up some info about
that but I couldn't find a definition of how the hardware interface
for such devices is supposed to work.  There's some XML-laden software
API but it seemed to be transport agnostic.

-Bob

Re: ASUS ScreenDuo

[Lennart Sorensen]

On Thu, Apr 03, 2008 at 04:58:03PM -0400, Bob Copeland wrote:
> If you have a friend with this device and windows, you might be able to
> capture the initialization sequence using usbsnoopy or something similar.
> Some devices just need a little proprietary poke before they become a normal
> USB device.

Well apparently vista expects the device to support running programs
written in .NET Micro Framework.  Maybe that is some JVM like thingy.  I
am not sure what Microsoft means by "Managed Code".  Since it seems to
be architecture independant I imagine it is similar to java byte code or
something similar.

Perhaps vista writes the firmware/OS to the mass storage device and they
talks to it after that.  Is there such a thing as a write only usb mass
storage device?

-- 
Len Sorensen

Re: ASUS ScreenDuo

[Bob Copeland]

>  Ah. Apparently it just waits for some driver from the Windows side (no
>  way to insert anything in there).
>  I guess it'll just be another useless piece of electronics at home.

If you have a friend with this device and windows, you might be able to
capture the initialization sequence using usbsnoopy or something similar.
Some devices just need a little proprietary poke before they become a normal
USB device.

-Bob

Re: ASUS ScreenDuo

[Alan Stern]

On Thu, 3 Apr 2008 david@lang.hm wrote:

> for future use, what was it that made everyone decide that this is going 
> to show up as a storage device?
> 
> with a screen and buttons I would have guessed a HID of some sort.

During enumeration it reports that it is a USB mass-storage-class 
device.  Look at Xavier's lsusb output in the original posting.

Alan Stern

Re: ASUS ScreenDuo

[david]

On Thu, 3 Apr 2008, Xavier Bestel wrote:

> On jeu, 2008-04-03 at 15:07 -0400, Alan Stern wrote:
>> On Thu, 3 Apr 2008, Xavier Bestel wrote:
>>
>>> On jeu, 2008-04-03 at 11:37 -0400, Alan Stern wrote:
>>>> On Thu, 3 Apr 2008, Xavier Bestel wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I have an ASUS motherboard with an USB gadget, the ASUS ScreenDUO. It's
>>>>> an independant little lcd screen with buttons, apparently it runs some
>>>>> kind of OS because it can access the net (e.g. to retrieve RSS) even
>>>>> when the computer is off - I guess they mean soft-off.
>>>>>
>>>>> Well, all that is theory because it's under Vista, which I don't have.
>>>>> Under Linux the ScreenDUO is kind-of recognized: it says it's a mass
>>>>> storage device, but I can't mount it (the kernel says it's bound to sdc,
>>>>> but sdc doesn't exist).
>>>>> I'd like to access it. Does anyone know how that thing works ?
>>>>
>>>> What does usbmon show when you modprobe usb-storage?  (The instructions
>>>> for usbmon are in the kernel source file Documentation/usb/usbmon.txt.)
>>
>> ...
>>
>> The ScreenDUO is reporting that no medium is present.  Maybe it needs
>> you to insert some sort of flash memory card before it will work as a
>> mass-storage device.
>
> Ah. Apparently it just waits for some driver from the Windows side (no
> way to insert anything in there).
> I guess it'll just be another useless piece of electronics at home.

for future use, what was it that made everyone decide that this is going 
to show up as a storage device?

with a screen and buttons I would have guessed a HID of some sort.

David Lang

Re: ASUS ScreenDuo

[Xavier Bestel]

On jeu, 2008-04-03 at 13:04 -0700, david@lang.hm wrote:
> On Thu, 3 Apr 2008, Xavier Bestel wrote:
> 
> > On jeu, 2008-04-03 at 15:07 -0400, Alan Stern wrote:
> >> On Thu, 3 Apr 2008, Xavier Bestel wrote:
> >>
> >>> On jeu, 2008-04-03 at 11:37 -0400, Alan Stern wrote:
> >>>> On Thu, 3 Apr 2008, Xavier Bestel wrote:
> >>>>
> >>>>> Hi,
> >>>>>
> >>>>> I have an ASUS motherboard with an USB gadget, the ASUS ScreenDUO. It's
> >>>>> an independant little lcd screen with buttons, apparently it runs some
> >>>>> kind of OS because it can access the net (e.g. to retrieve RSS) even
> >>>>> when the computer is off - I guess they mean soft-off.
> >>>>>
> >>>>> Well, all that is theory because it's under Vista, which I don't have.
> >>>>> Under Linux the ScreenDUO is kind-of recognized: it says it's a mass
> >>>>> storage device, but I can't mount it (the kernel says it's bound to sdc,
> >>>>> but sdc doesn't exist).
> >>>>> I'd like to access it. Does anyone know how that thing works ?
> >>>>
> >>>> What does usbmon show when you modprobe usb-storage?  (The instructions
> >>>> for usbmon are in the kernel source file Documentation/usb/usbmon.txt.)
> >>
> >> ...
> >>
> >> The ScreenDUO is reporting that no medium is present.  Maybe it needs
> >> you to insert some sort of flash memory card before it will work as a
> >> mass-storage device.
> >
> > Ah. Apparently it just waits for some driver from the Windows side (no
> > way to insert anything in there).
> > I guess it'll just be another useless piece of electronics at home.
> 
> for future use, what was it that made everyone decide that this is going 
> to show up as a storage device?
> 
> with a screen and buttons I would have guessed a HID of some sort.

Maybe it waits for a firmware or something first.

	Xav

Re: ASUS ScreenDuo

[Xavier Bestel]

On jeu, 2008-04-03 at 15:07 -0400, Alan Stern wrote:
> On Thu, 3 Apr 2008, Xavier Bestel wrote:
> 
> > On jeu, 2008-04-03 at 11:37 -0400, Alan Stern wrote:
> > > On Thu, 3 Apr 2008, Xavier Bestel wrote:
> > > 
> > > > Hi,
> > > > 
> > > > I have an ASUS motherboard with an USB gadget, the ASUS ScreenDUO. It's
> > > > an independant little lcd screen with buttons, apparently it runs some
> > > > kind of OS because it can access the net (e.g. to retrieve RSS) even
> > > > when the computer is off - I guess they mean soft-off.
> > > > 
> > > > Well, all that is theory because it's under Vista, which I don't have.
> > > > Under Linux the ScreenDUO is kind-of recognized: it says it's a mass
> > > > storage device, but I can't mount it (the kernel says it's bound to sdc,
> > > > but sdc doesn't exist).
> > > > I'd like to access it. Does anyone know how that thing works ?
> > > 
> > > What does usbmon show when you modprobe usb-storage?  (The instructions 
> > > for usbmon are in the kernel source file Documentation/usb/usbmon.txt.)
> 
> ...
> 
> The ScreenDUO is reporting that no medium is present.  Maybe it needs 
> you to insert some sort of flash memory card before it will work as a 
> mass-storage device.

Ah. Apparently it just waits for some driver from the Windows side (no
way to insert anything in there).
I guess it'll just be another useless piece of electronics at home.

Thanks,
	Xav

Re: ASUS ScreenDuo

[Alan Stern]

On Thu, 3 Apr 2008, Xavier Bestel wrote:

> On jeu, 2008-04-03 at 11:37 -0400, Alan Stern wrote:
> > On Thu, 3 Apr 2008, Xavier Bestel wrote:
> > 
> > > Hi,
> > > 
> > > I have an ASUS motherboard with an USB gadget, the ASUS ScreenDUO. It's
> > > an independant little lcd screen with buttons, apparently it runs some
> > > kind of OS because it can access the net (e.g. to retrieve RSS) even
> > > when the computer is off - I guess they mean soft-off.
> > > 
> > > Well, all that is theory because it's under Vista, which I don't have.
> > > Under Linux the ScreenDUO is kind-of recognized: it says it's a mass
> > > storage device, but I can't mount it (the kernel says it's bound to sdc,
> > > but sdc doesn't exist).
> > > I'd like to access it. Does anyone know how that thing works ?
> > 
> > What does usbmon show when you modprobe usb-storage?  (The instructions 
> > for usbmon are in the kernel source file Documentation/usb/usbmon.txt.)

...

The ScreenDUO is reporting that no medium is present.  Maybe it needs 
you to insert some sort of flash memory card before it will work as a 
mass-storage device.

Alan Stern

Re: ASUS ScreenDuo

[Xavier Bestel]

On jeu, 2008-04-03 at 11:37 -0400, Alan Stern wrote:
> On Thu, 3 Apr 2008, Xavier Bestel wrote:
> 
> > Hi,
> > 
> > I have an ASUS motherboard with an USB gadget, the ASUS ScreenDUO. It's
> > an independant little lcd screen with buttons, apparently it runs some
> > kind of OS because it can access the net (e.g. to retrieve RSS) even
> > when the computer is off - I guess they mean soft-off.
> > 
> > Well, all that is theory because it's under Vista, which I don't have.
> > Under Linux the ScreenDUO is kind-of recognized: it says it's a mass
> > storage device, but I can't mount it (the kernel says it's bound to sdc,
> > but sdc doesn't exist).
> > I'd like to access it. Does anyone know how that thing works ?
> 
> What does usbmon show when you modprobe usb-storage?  (The instructions 
> for usbmon are in the kernel source file Documentation/usb/usbmon.txt.)

dfb8d3c0 4163439081 C Ii:7:001:1 0:2048 1 = 10
dfb8d3c0 4163439091 S Ii:7:001:1 -115:2048 4 <
e5d7aa40 4163439171 S Ci:7:001:0 s a3 00 0000 0004 0004 4 <
e5d7aa40 4163439176 C Ci:7:001:0 0 4 = 01050100
e5d7aa40 4163439179 S Co:7:001:0 s 23 01 0010 0004 0000 0
e5d7aa40 4163439182 C Co:7:001:0 0 0
e5d7aa40 4163439184 S Ci:7:001:0 s a3 00 0000 0004 0004 4 <
e5d7aa40 4163439186 C Ci:7:001:0 0 4 = 01050000
e5d7aa40 4163470364 S Ci:7:001:0 s a3 00 0000 0004 0004 4 <
e5d7aa40 4163470368 C Ci:7:001:0 0 4 = 01050000
e5d7aa40 4163502356 S Ci:7:001:0 s a3 00 0000 0004 0004 4 <
e5d7aa40 4163502360 C Ci:7:001:0 0 4 = 01050000
e5d7aa40 4163534355 S Ci:7:001:0 s a3 00 0000 0004 0004 4 <
e5d7aa40 4163534358 C Ci:7:001:0 0 4 = 01050000
e5d7aa40 4163566364 S Ci:7:001:0 s a3 00 0000 0004 0004 4 <
e5d7aa40 4163566367 C Ci:7:001:0 0 4 = 01050000
e5d7aa40 4163566374 S Co:7:001:0 s 23 03 0004 0004 0000 0
e5d7aa40 4163566377 C Co:7:001:0 0 0
e5d7aa40 4163622353 S Ci:7:001:0 s a3 00 0000 0004 0004 4 <
e5d7aa40 4163622563 C Ci:7:001:0 0 4 = 03051000
e5d7aa40 4163678364 S Co:7:001:0 s 23 01 0014 0004 0000 0
e5d7aa40 4163678369 C Co:7:001:0 0 0
e5d7aa40 4163678392 S Ci:7:000:0 s 80 06 0100 0000 0040 64 <
e5d7aa40 4163678576 C Ci:7:000:0 0 18 = 12010002 00000040 43100031 01001020 6001
e5d7aa40 4163678602 S Co:7:001:0 s 23 03 0004 0004 0000 0
e5d7aa40 4163678607 C Co:7:001:0 0 0
e5d7aa40 4163734354 S Ci:7:001:0 s a3 00 0000 0004 0004 4 <
e5d7aa40 4163734568 C Ci:7:001:0 0 4 = 03051000
e5d7aa40 4163790363 S Co:7:001:0 s 23 01 0014 0004 0000 0
e5d7aa40 4163790370 C Co:7:001:0 0 0
e5d7aa40 4163790373 S Co:7:000:0 s 00 05 0005 0000 0000 0
e5d7aa40 4163790577 C Co:7:000:0 0 0
e5d7aa40 4163810360 S Ci:7:005:0 s 80 06 0100 0000 0012 18 <
e5d7aa40 4163810578 C Ci:7:005:0 0 18 = 12010002 00000040 43100031 01001020 6001
e5d7aa40 4163810603 S Ci:7:005:0 s 80 06 0200 0000 0009 9 <
e5d7aa40 4163810828 C Ci:7:005:0 0 9 = 09022300 010130c0 00
e5d7aa40 4163810847 S Ci:7:005:0 s 80 06 0200 0000 0023 35 <
e5d7aa40 4163811078 C Ci:7:005:0 0 35 = 09022300 010130c0 00090400 00020806 50400705 81020002 00070502 02000200
e5d7aa40 4163811103 S Ci:7:005:0 s 80 06 0300 0000 00ff 255 <
e5d7aa40 4163811328 C Ci:7:005:0 0 4 = 04030904
e5d7aa40 4163811346 S Ci:7:005:0 s 80 06 0320 0409 00ff 255 <
e5d7aa40 4163811578 C Ci:7:005:0 0 20 = 14035300 63007200 65006500 6e004400 55004f00
e5d7aa40 4163811598 S Ci:7:005:0 s 80 06 0310 0409 00ff 255 <
e5d7aa40 4163811828 C Ci:7:005:0 0 10 = 0a034100 53005500 5300
e5d7aa40 4163811846 S Ci:7:005:0 s 80 06 0360 0409 00ff 255 <
e5d7aa40 4163812078 C Ci:7:005:0 0 64 = 4d000000 0b8f8309 c0b002c0 99e92e00 f0a0e2e2 0f02400c e0f03050 09090509
e5d7aa40 4163812248 S Co:7:005:0 s 00 09 0001 0000 0000 0
e5d7aa40 4163812452 C Co:7:005:0 0 0
e5d7aa40 4163812462 S Ci:7:005:0 s 80 06 0330 0409 00ff 255 <
e5d7aa40 4163812702 C Ci:7:005:0 0 28 = 1c034300 4f004e00 46004900 47002000 53005400 52004900 4e004700
e5d7a540 4163812815 S Ci:7:005:0 s 80 06 0340 0409 00ff 255 <
e5d7a540 4163812953 C Ci:7:005:0 0 34 = 22034900 4e005400 45005200 46004100 43004500 20005300 54005200 49004e00
e5d7aa40 4168810367 S Ci:7:005:0 s a1 fe 0000 0000 0001 1 <
e5d7aa40 4168811518 C Ci:7:005:0 0 1 = 00
e5d7aa40 4168811605 S Bo:7:005:2 -115 31 = 55534243 01000000 24000000 80000612 00000024 00000000 00000000 000000
e5d7aa40 4168811642 C Bo:7:005:2 0 31 >
e5d7a540 4168811651 S Bi:7:005:1 -115 36 <
e5d7a540 4168811891 C Bi:7:005:1 0 36 = 00800202 21000000 41535553 20202020 53637265 656e4455 4f202020 20202020
e5d7aa40 4168811896 S Bi:7:005:1 -115 13 <
e5d7aa40 4168812017 C Bi:7:005:1 0 13 = 55534253 01000000 00000000 00
e5d7aa40 4168812294 S Bo:7:005:2 -115 31 = 55534243 02000000 00000000 00000600 00000000 00000000 00000000 000000
e5d7aa40 4168812391 C Bo:7:005:2 0 31 >
e5d7aa40 4168812394 S Bi:7:005:1 -115 13 <
e5d7aa40 4168812641 C Bi:7:005:1 0 13 = 55534253 02000000 00000000 01
e5d7aa40 4168812644 S Bo:7:005:2 -115 31 = 55534243 03000000 12000000 80000603 00000012 00000000 00000000 000000
e5d7aa40 4168812766 C Bo:7:005:2 0 31 >
f36a85c0 4168827343 S Bi:7:005:1 -115 18 <
f36a85c0 4168827391 C Bi:7:005:1 0 18 = 70000200 0000000a 00000000 3a000000 0000
e5d7aa40 4168827396 S Bi:7:005:1 -115 13 <
e5d7aa40 4168827516 C Bi:7:005:1 0 13 = 55534253 03000000 00000000 00
e5d7aa40 4262289563 S Bo:7:005:2 -115 31 = 55534243 04000000 00000000 00000600 00000000 00000000 00000000 000000
e5d7aa40 4262289679 C Bo:7:005:2 0 31 >
e5d7aa40 4262289683 S Bi:7:005:1 -115 13 <
e5d7aa40 4262289803 C Bi:7:005:1 0 13 = 55534253 04000000 00000000 01
e5d7aa40 4262289808 S Bo:7:005:2 -115 31 = 55534243 05000000 12000000 80000603 00000012 00000000 00000000 000000
e5d7aa40 4262290053 C Bo:7:005:2 0 31 >
f36a8240 4262290058 S Bi:7:005:1 -115 18 <
f36a8240 4262290178 C Bi:7:005:1 0 18 = 70000200 0000000a 00000000 3a000000 0000
e5d7aa40 4262290183 S Bi:7:005:1 -115 13 <
e5d7aa40 4262290303 C Bi:7:005:1 0 13 = 55534253 05000000 00000000 00
e5d7aa40 4262290327 S Bo:7:005:2 -115 31 = 55534243 06000000 00000000 00000600 00000000 00000000 00000000 000000
e5d7aa40 4262290429 C Bo:7:005:2 0 31 >
e5d7aa40 4262290432 S Bi:7:005:1 -115 13 <
e5d7aa40 4262290554 C Bi:7:005:1 0 13 = 55534253 06000000 00000000 01
e5d7aa40 4262290558 S Bo:7:005:2 -115 31 = 55534243 07000000 12000000 80000603 00000012 00000000 00000000 000000
e5d7aa40 4262290803 C Bo:7:005:2 0 31 >
f36a8240 4262290806 S Bi:7:005:1 -115 18 <
f36a8240 4262290929 C Bi:7:005:1 0 18 = 70000200 0000000a 00000000 3a000000 0000
e5d7aa40 4262290933 S Bi:7:005:1 -115 13 <
e5d7aa40 4262291053 C Bi:7:005:1 0 13 = 55534253 07000000 00000000 00
e5d7aa40 4262291077 S Bo:7:005:2 -115 31 = 55534243 08000000 00000000 00000600 00000000 00000000 00000000 000000
e5d7aa40 4262291179 C Bo:7:005:2 0 31 >
e5d7aa40 4262291183 S Bi:7:005:1 -115 13 <
e5d7aa40 4262291428 C Bi:7:005:1 0 13 = 55534253 08000000 00000000 01
e5d7aa40 4262291431 S Bo:7:005:2 -115 31 = 55534243 09000000 12000000 80000603 00000012 00000000 00000000 000000
e5d7aa40 4262291554 C Bo:7:005:2 0 31 >
f36a8240 4262291558 S Bi:7:005:1 -115 18 <
f36a8240 4262291803 C Bi:7:005:1 0 18 = 70000200 0000000a 00000000 3a000000 0000
e5d7aa40 4262291806 S Bi:7:005:1 -115 13 <
e5d7aa40 4262291928 C Bi:7:005:1 0 13 = 55534253 09000000 00000000 00
e5d7aa40 4262291946 S Bo:7:005:2 -115 31 = 55534243 0a000000 00000000 00000600 00000000 00000000 00000000 000000
e5d7aa40 4262292054 C Bo:7:005:2 0 31 >
e5d7aa40 4262292058 S Bi:7:005:1 -115 13 <
e5d7aa40 4262292303 C Bi:7:005:1 0 13 = 55534253 0a000000 00000000 01
e5d7aa40 4262292306 S Bo:7:005:2 -115 31 = 55534243 0b000000 12000000 80000603 00000012 00000000 00000000 000000
e5d7aa40 4262292429 C Bo:7:005:2 0 31 >
f36a8240 4262292433 S Bi:7:005:1 -115 18 <
f36a8240 4262292678 C Bi:7:005:1 0 18 = 70000200 0000000a 00000000 3a000000 0000
e5d7aa40 4262292681 S Bi:7:005:1 -115 13 <
e5d7aa40 4262292804 C Bi:7:005:1 0 13 = 55534253 0b000000 00000000 00

Re: ASUS ScreenDuo

[Matthew Dharm]

[-- Attachment #1: Type: text/plain, Size: 733 bytes --]

On Thu, Apr 03, 2008 at 04:07:08PM +0200, Xavier Bestel wrote:
> On Thu, 2008-04-03 at 09:57 -0400, Mark Lord wrote:
> > > [root@awak:~]$ fdisk /dev/sdc
> > > 
> > > Unable to open /dev/sdc
> > > 
> > ..
> > 
> > As root, try:   mknod /tmp/sdc b 8 32 ; fdisk /tmp/sdc
> > 
> > Any different? 
> 
> Nope. But /dev/sdc has already been created, and looks right (b 8 32
> too). Just there's nothing behind it.

Turn on CONFIG_USB_STORAGE_DEBUG and see what logs it generates when you
try to access the device.

Matt

-- 
Matthew Dharm                              Home: mdharm-usb@one-eyed-alien.net 
Maintainer, Linux USB Mass Storage Driver

NYET! The evil stops here!
					-- Pitr
User Friendly, 6/22/1998

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: ASUS ScreenDuo

[Alan Stern]

On Thu, 3 Apr 2008, Xavier Bestel wrote:

> Hi,
> 
> I have an ASUS motherboard with an USB gadget, the ASUS ScreenDUO. It's
> an independant little lcd screen with buttons, apparently it runs some
> kind of OS because it can access the net (e.g. to retrieve RSS) even
> when the computer is off - I guess they mean soft-off.
> 
> Well, all that is theory because it's under Vista, which I don't have.
> Under Linux the ScreenDUO is kind-of recognized: it says it's a mass
> storage device, but I can't mount it (the kernel says it's bound to sdc,
> but sdc doesn't exist).
> I'd like to access it. Does anyone know how that thing works ?

What does usbmon show when you modprobe usb-storage?  (The instructions 
for usbmon are in the kernel source file Documentation/usb/usbmon.txt.)

Alan Stern

Re: ASUS ScreenDuo

[Xavier Bestel]

On Thu, 2008-04-03 at 09:57 -0400, Mark Lord wrote:
> > [root@awak:~]$ fdisk /dev/sdc
> > 
> > Unable to open /dev/sdc
> > 
> ..
> 
> As root, try:   mknod /tmp/sdc b 8 32 ; fdisk /tmp/sdc
> 
> Any different? 

Nope. But /dev/sdc has already been created, and looks right (b 8 32
too). Just there's nothing behind it.

	Xav

Re: ASUS ScreenDuo

[Mark Lord]

Xavier Bestel wrote:
> Hi,
> 
> I have an ASUS motherboard with an USB gadget, the ASUS ScreenDUO. It's
> an independant little lcd screen with buttons, apparently it runs some
> kind of OS because it can access the net (e.g. to retrieve RSS) even
> when the computer is off - I guess they mean soft-off.
> 
> Well, all that is theory because it's under Vista, which I don't have.
> Under Linux the ScreenDUO is kind-of recognized: it says it's a mass
> storage device, but I can't mount it (the kernel says it's bound to sdc,
> but sdc doesn't exist).
> I'd like to access it. Does anyone know how that thing works ?
> 
> Thanks,
> 	Xav
> 
> PS: please Cc: me on anwers
> 
> interesting dmesg part:
> 
> usb 7-4: new high speed USB device using ehci_hcd and address 3
> usb 7-4: configuration #1 chosen from 1 choice
> scsi9 : SCSI emulation for USB Mass Storage devices
> usb-storage: device found at 3
> usb-storage: waiting for device to settle before scanning
> usb-storage: device scan complete
> scsi 9:0:0:0: Direct-Access     ASUS     ScreenDUO             PQ: 0 ANSI: 2
> sd 9:0:0:0: [sdc] Attached SCSI removable disk
> usb 7-4: USB disconnect, address 3
> usb 7-4: new high speed USB device using ehci_hcd and address 4
> usb 7-4: configuration #1 chosen from 1 choice
> scsi10 : SCSI emulation for USB Mass Storage devices
> usb-storage: device found at 4
> usb-storage: waiting for device to settle before scanning
> usb-storage: device scan complete
> scsi 10:0:0:0: Direct-Access     ASUS     ScreenDUO             PQ: 0 ANSI: 2
> sd 10:0:0:0: [sdc] Attached SCSI removable disk
> 
> 
> [root@awak:~]$ fdisk /dev/sdc
> 
> Unable to open /dev/sdc
> 
..

As root, try:   mknod /tmp/sdc b 8 32 ; fdisk /tmp/sdc

Any different?

ASUS ScreenDuo

[Xavier Bestel]

Hi,

I have an ASUS motherboard with an USB gadget, the ASUS ScreenDUO. It's
an independant little lcd screen with buttons, apparently it runs some
kind of OS because it can access the net (e.g. to retrieve RSS) even
when the computer is off - I guess they mean soft-off.

Well, all that is theory because it's under Vista, which I don't have.
Under Linux the ScreenDUO is kind-of recognized: it says it's a mass
storage device, but I can't mount it (the kernel says it's bound to sdc,
but sdc doesn't exist).
I'd like to access it. Does anyone know how that thing works ?

Thanks,
	Xav

PS: please Cc: me on anwers

interesting dmesg part:

usb 7-4: new high speed USB device using ehci_hcd and address 3
usb 7-4: configuration #1 chosen from 1 choice
scsi9 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
scsi 9:0:0:0: Direct-Access     ASUS     ScreenDUO             PQ: 0 ANSI: 2
sd 9:0:0:0: [sdc] Attached SCSI removable disk
usb 7-4: USB disconnect, address 3
usb 7-4: new high speed USB device using ehci_hcd and address 4
usb 7-4: configuration #1 chosen from 1 choice
scsi10 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
scsi 10:0:0:0: Direct-Access     ASUS     ScreenDUO             PQ: 0 ANSI: 2
sd 10:0:0:0: [sdc] Attached SCSI removable disk


[root@awak:~]$ fdisk /dev/sdc

Unable to open /dev/sdc



[root@awak:~]$ lsusb -v

Bus 007 Device 004: ID 1043:3100 iCreate Technologies Corp. 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x1043 iCreate Technologies Corp.
  idProduct          0x3100 
  bcdDevice            0.01
  iManufacturer          16 ASUS
  iProduct               32 ScreenDUO
  iSerial                96 
  bNumConfigurations      1
OTG Descriptor:
  bLength                 3
  bDescriptorType         9
  bmAttributes         0x03
    SRP (Session Request Protocol)
    HNP (Host Negotiation Protocol)
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           35
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration         48 CONFIG STRING
    bmAttributes         0xc0
      Self Powered
    MaxPower                0mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk (Zip)
      iInterface             64 INTERFACE STRING
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0001
  Self Powered

etc.