netio and g_files_storage.ko for ES 6300

[juusso]

Code: Select all

drivers/mstar/usb/core/inode.c: creating file '001'
dummy_hcd mod ld
hub 4-0:1.0: state 7 ports 1 chg 0000 evt 0000
g_file_storage gadget: no file given for LUN0

It fails because you insmod it incorectly, driver need arguments (check vusb.init file) or google

SpoilerShow

Code: Select all

mkfs.vfat -C /dtv/vusb 500
insmod $MOD_DIR/kernel/drivers/usb/gadget/g_file_storage.ko file=/dtv/vusb

Same for g_mass_storage. Both of them can generate virtual usb`s AFAIK.

[zoelechat]

I just blindly sent command as they are in vusb script (no 'args' are defined before that):

Code: Select all

mkfs.vfat -C /dtv/vusb 500
insmod $MOD_DIR/kernel/drivers/usb/gadget/dummy_hcd.ko
insmod $MOD_DIR/kernel/drivers/usb/gadget/g_file_storage.ko

I don't need it anyway, it was just to give some feedback

[zoelechat]

ah ok, so the arg is missing in vusb script
Now inserted without error. Should I see a vusb appearing then? I don't.
Trying g_mass...

[juusso]

what about

Code: Select all

mkfs.vfat -C /dtv/vusb 500
insmod $MOD_DIR/kernel/drivers/usb/gadget/dummy_hcd.ko
insmod $MOD_DIR/kernel/drivers/usb/gadget/g_file_storage.ko file=/dtv/vusb

you can`t see virtual usb until you don`t properly write /dtv/usblog info about virtual usb you just created.

p.s. but maybe here we see the mstar related problem about no block devices created.

Code: Select all

mount | grep "/dtv/usb"
cat /sys/block/sd?/device/model

[zoelechat]

Yep, exactly what I tried, no vusb. Exact same dmesg with g_mass and g_file:

Code: Select all

/mnt # mkfs.vfat -C /dtv/vusb 500
mkfs.vfat 2.11 (12 Mar 2005)
/mnt # insmod $MOD_DIR/kernel/drivers/usb/gadget/dummy_hcd.ko
/mnt # insmod $MOD_DIR/kernel/drivers/usb/gadget/g_file_storage.ko file=/dtv/vusb
/mnt # dmesg | tail
g_file_storage gadget-lun0: ro=0, file: /dtv/vusb
g_file_storage mod ld
hub 4-0:1.0: state 7 ports 1 chg 0000 evt 0002
hub 4-0:1.0: port 1, status 0101, change 0001, 12 Mb/s
hub 4-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101
==9==> hub_port_init 1
hub 4-0:1.0: unable to enumerate USB device on port 1
hub 4-0:1.0: state 7 ports 1 chg 0000 evt 0002
hub 4-0:1.0: reset change on port 1
hub 4-0:1.0: state 7 ports 1 chg 0000 evt 0002

[zoelechat]

Ok, seems to work then

Code: Select all

real storage device at: /sys/block/sda/device/model (sda)

edit: NO, it's my physical USB

[juusso]

Maybe google has the answer again, need to check solutions given there one by one https://www.google.com/search?q=hub+4-0 ... 8&oe=utf-8

some reports on not proper ehci_hcd driver (or maybe this is not related to vusb at all). no idea

[zoelechat]

No matter, I definitely prefer to mount on physical USB and I never planned to record over network (except using PVRtoTS which does the job perfectly...). Let's wait for reports of users who really need it.

[cmuc05]

@juuso: Thank you, now I am able to build the modules stuff.

I can confirm the results of zoelechat. With high probability it is the MSTAR Problem of not creating a block device. I ask myself, If there is a MStAR TV outside who is creating a block device with g_file_storage.ko.

In this thread viewtopic.php?f=63&t=8512 is written, that the 02_03_crypto_load.init is important and should be load before vusb.init.
The init file I have, but not the modules. Can the modules are created like the usb gadget stuff? I searched the menuconfig but i can't find adequate options.

[cmuc05]

Figured crypto out and built it for ES 6300.
I think too that the "hub 4-0:1.0: unable to enumerate USB device on port 1" can be the problem.
Perhaps someone can send a dmesg | tail after a block device was created (non MSTAR) to see the difference