So I did a good firmare upgrade, cleaned it all, installed prep_whitelight and now lsusb correctly displays my printer!

But…..reinstalled cups and my printer is not available and I cannot even select "USB" from the devices backend when adding a printer manually…..

Tried different times but with no luck….

Saw this today, and really want to give it a go (actually i started trying to), but i dont have that much linux experience. Can you give a step by step tutorial on how to set it up?

Cheers.
Stuart

this works well on mybook..

you need to install:

1. libglib2.0-0
2. libsysfs2
3. libwrap0-dev

download usbip for mybook here: http://alvnet.eu.org/usbip-0.1.7-arm-mybook.tar.gz
extract and place the files where you want them..

install usbip on the client
ubuntu: apt-get install usbip
windows: http://sourceforge.net/projects/usbip/

[Usage] (http://usbip.svn.sourceforge.net/viewvc/usbip/linux/trunk/src/README?view=markup)
35 server:# (Attach your USB device physically.)
36
37 server:# insmod usbip_common_mod.ko
38 server:# insmod usbip.ko
39 - It was formerly named as stub.ko.
40
41 server:# usbipd -D
42 - Start usbip daemon.
43
44 server:# usbip_bind_driver —list
45 - List driver assignments for usb devices.
46
47 server:# usbip_bind_driver —usbip 1-2
48 - Bind usbip.ko to the device of busid 1-2.
49 - A usb device 1-2 is now exportable to other hosts!
50 - Use 'usbip_bind_driver —other 1-2' when you want to shutdown exporting
51 and use the device locally.
52
53
54 client:# insmod usbip_common_mod.ko
55 client:# insmod vhci-hcd.ko
56 - It was formerly named as vhci.ko.
57
58 client:# usbip —list server
59 - List exportable usb devices on the server.
60
61 client:# usbip —attach server 1-2
62 - Connect the remote USB device.
63
64 client:# usbip —port
65 - Show virtual port status.
66
67 client:# usbip —detach 0
68 - Detach the usb device.

I had to manually mount USBFS by issuing, as root:

/bin/mount -n /proc/bus/usb/ /proc/bus/usb/ -t usbfs

Now lsusb correctly displays my printer.

Hope this helps for somebody else.

Ciao,

Fabio

Thanks,

Fabio

The best reference I got is:
compile sound support
which also refers to:
guide installing debian

When following those posts, consider also these points:
- You can do it in anylinux modern version, regardless the gcc compiler inside. No need to change the linux distro compiler (e.g., I did it with Ubuntu 8.04, gcc-4.3). The reason is that the buildroot will compile the specific gcc version with cross-compilation support.
- When configuring buildroot, set always soft emulated FP processor. Configure not to include any application, so it takes less time. The interesting thing is to compile basic tools and the applicable gcc compiler for arm cross compilation.
- If you compile applications, the easiest is to use all which comes in the WD source package. Just put all the buildroot archives inside buildroot/dl directory (so there is no download), and configure buildroot as in the original system, e.g. with FW 1.0.18 with gcc-3, and kernel 2.6.17.14. Important point is not to get the latest uClibc snapshot, but the version a specified version (leave empty and it takes default one, already indl, I think). If setting all correct, it compiles ok, except last steps of building the root, which is not necessary.
- Once you have the compiler, you can try to compile applications from source code, using the buildroot generated copiler and libraries. I have not done it, but maybe you need to touch makefiles to use correct elements. You can see how buildroot compiles applications to do the same.
- If you want to compile a kernel module, it is a bit more difficult, because you need to use arm gcc-4.1 compiler generated by build root. The main problem is that buildroot and uClibc evolve, and they do not support anymore old compilers gcc-4.1 and kernel. The following worked for me:
- Download the latest buildroot package and extract it. Maybe in the future it does not work, so instead of latest, take from buildroot site the one available as latest around nov-2009, which I used. The same for uClibc
- In the configuration, it is the same as for applications, except that you have to enable obsolete packages, and then select the gcc-4.1 version (in my case it was gcc-4.1.2). Take the latest snapshot of uClibc. Use the latest In the kernel headers, specify manually the version 2.6.18.1 (because kernel 17 does not have headers install kernel, so buildroot fails. It seems that using this version is ok.
- When you make, it takes quite a long time, because it downloads some packages and compiles big thing like gmp (I do not know why). At the end, it should compile until the erroor when creating root image, and hopefully the gcc-4.1.2 should be available.
- You can then go to the vendor/kernel sources provided by WD, set the path to the generated gcc-4.1.2 compiler and try. I could obtain my module doing this.

I hopt that with the original instructions and these tips someone with good knowledge of linux and compilation can get things to work…

Has anyone here tried to compile ipmitool for the MBWE. I looked through the Optware packages and didn't find any precompiled packages for ipmitool. I saw a tutorial about how to run an rc script by pressing the power button and thought it would be really useful if I could install ipmitool so that when I press the power button it could turn on one of my servers or something. If anyone has any experience in getting ipmitool on the MBWE let me know. I would greatly appreciate it.

Did you find a solution?

Hal

maybe somebody can help me, I'm trying to make my printer visible in cups with no luck, so I try to check with lsusb.

to sum up:

- the printer is connect and turned on
- user is root
- lsusb (installed with ipkg install usbutils) display nothing
- lsusb -t displays: cannot open /proc/bus/usb/devices
- dmesg | grep usb displays:

~ # dmesg | grep usb
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
usbcore: registered new interface driver usb-storage
usb usb1: configuration #1 chosen from 1 choice
usb 1-1: new full speed USB device using oxnas-ehci and address 2
usb 1-1: configuration #1 chosen from 1 choice

Any help?

Thanks,

D

/ # /opt/bin/ipkg install gcc
Nothing to be done
An error ocurred, return value: 4.
Collected errors:
Cannot find package gcc.
Check the spelling or perhaps run 'ipkg update'
/ #

I tryed to install with Optware, but I have this message:

 / # /opt/bin/ipkg install clutch Nothing to be done An error ocurred, return value: 4. Collected errors: Cannot find package clutch. Check the spelling or perhaps run 'ipkg update' / # 

Somebody can help me ? thanks

I am running for quite a long time now TwonkyVision on my ByBookWorld (with blue ledrings). I would like to install additional features like NZBget on to the MBW. The easiest this can be done via the feature pack and the automatic NZBget installation procedure. Will the installation of the feature pack have any influence on my Twonky-installation and settings?

THNX.

Thanks a lot for your help!

Banana_Split

I bought the WD World (2TB, white LED) a few days ago and I'm terribly disappointed of the Mionet service, so I tried to install the web server tutorial on my NAS. I'm quite a newbie in this kind of stuff, but I can follow instructions :-D.

Well, I activated SSH with the no-hack method. That worked out quite well. Afterwards I installed Teraterm on my PC and logged in with root/welc0me. This worked out too and I rebooted and tried to install the web server. That's the point where I got stuck. When I enter cd /shares/internal/public the box tells me that this folder doesn't exist or something. So i tried to install optware first. This was successful, too as far as I interpret that xD. I also tried to access my NAS via FTP. This didn't work at first, but worked out when I entered the main directory (/shares/internal/public). I saw the scructure and all the data on the NAS.

What do I have to do to make the web server work?

Thanks in advance

Banana_Split

P.S. I've done all the routing and so on with my father, so this is all fine. I can access my NAS via dyndns…