Using and installing other OS's (new threads)

Searching fuse.ko

Mon, 09 Nov 2009 22:36:51 +0000

Hi,
i am searching for a precompiled version of fuse.ko for 2.6.17.14 kernel. (debian lenny)
If somebody has it available please send me a download link. ;-)
Otherwise i have to go to install a toolchain etc.

Thank you very much.

cma123

serial access to white light

Tue, 20 Oct 2009 09:57:03 +0000

this is the boot log:
as you see, the kernel is loaded at 0x48500000

i don't know how to get my own compiled kernel at this address. maybe someone can help.

 Initialising disks No FIS received from device 1 No FIS received from device 1 Detecting SATA busses: Bus 0: Found first device OK Device 0: Model: WDC WD20EADS-00R6B0 Firm: 01.00A01 Ser#: WD-WCAVY0083223 Type: Hard Disk Supports 48-bit addressing Capacity: 1907729.0 MB = 1863.0 GB (-387938128 x 512) Device 1: not available Environment successfully read from disk 0 primary image U-Boot 1.1.2 (Oct 2 2008 - 12:51:43) U-Boot code: 48D00000 -> 48D1B228 BSS: -> 48D1F040 RAM Configuration: Bank #0: 48000000 128 MB SRAM Configuration: 128KB at 0x58000000 WARNING: flash_make_cmd: unsuppported LittleEndian mode WARNING: flash_make_cmd: unsuppported LittleEndian mode WARNING: flash_make_cmd: unsuppported LittleEndian mode WARNING: flash_make_cmd: unsuppported LittleEndian mode WARNING: flash_make_cmd: unsuppported LittleEndian mode WARNING: flash_make_cmd: unsuppported LittleEndian mode WARNING: flash_make_cmd: unsuppported LittleEndian mode WARNING: flash_make_cmd: unsuppported LittleEndian mode WARNING: flash_make_cmd: unsuppported LittleEndian mode WARNING: flash_make_cmd: unsuppported LittleEndian mode WARNING: flash_make_cmd: unsuppported LittleEndian mode WARNING: flash_make_cmd: unsuppported LittleEndian mode WARNING: flash_make_cmd: unsuppported LittleEndian mode ## Unknown FLASH on Bank 0 - Size = 0x00000000 = 0 MB Flash: 0 kB In: serial Out: serial Err: serial WD 1NC Board IDE read: device 0 block # 255, count 1 ... 1 blocks read: OK Controlled Power DOWN requested Hit any key to stop autoboot: 2 1 0 IDE device 0: Model: WDC WD20EADS-00R6B0 Firm: 01.00A01 Ser#: WD-WCAVY0083223 Type: Hard Disk Supports 48-bit addressing Capacity: 1907729.0 MB = 1863.0 GB (-387938128 x 512) ... is now current device IDE read: device 0 block # 300, count 5700 ... 5700 blocks read: OK ## Booting image at 48500000 ... Image Name: Linux-2.6.24.4 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1593324 Bytes = 1.5 MB Load Address: 48008000 Entry Point: 48008000 Verifying Checksum ... OK OK Starting kernel ... Uncompressing Linux.................................................................................................... done, booting the kernel. Linux version 2.6.24.4 (brian@dualla) (gcc version 4.2.4) #1 Tue Feb 10 11:00:22 GMT 2009 CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177 Machine: Oxsemi NAS Ignoring unrecognised tag 0x00000000 Memory policy: ECC disabled, Data cache writeback CPU0: D VIVT write-back cache CPU0: I cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets CPU0: D cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512 Kernel command line: root=/dev/md0 console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x90,0xA9,0x6D,0x8C,0x06 mem=128M wixmodel=WWLXN powermode=controlledpdown poweroutage=yes timeINC=949558681 PID hash table entries: 512 (order: 9, 2048 bytes) Console: colour dummy device 80x30 console [ttyS0] enabled Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 128MB = 128MB total Memory: 126592KB available (2892K code, 152K data, 108K init) Security Framework initialized Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok net_namespace: 64 bytes NET: Registered protocol family 16 Number of DMA channels = 5, version = 4 Allocating 891 SRAM generic DMA descriptors Chip Id: die-id 0x0752bd30e980 read back 0xbeefcafe SCSI subsystem initialized NET: Registered protocol family 2 IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP established hash table entries: 4096 (order: 3, 32768 bytes) TCP bind hash table entries: 4096 (order: 2, 16384 bytes) TCP: Hash tables configured (established 4096 bind 4096) TCP reno registered Hello, LED trigger fuse init (API version 7.9) SGI XFS with large block numbers, no debug enabled SGI XFS Quota Management subsystem io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled ÿserial8250: ttyS0 at MMIO 0x44300000 (irq = 24) is a 16550A RAMDISK driver initialized: 16 RAM disks of 10240K size 1024 blocksize loop: module loaded Driver 'sd' needs updating - please use bus_type methods ox810sata: OX810 sata core. scsi0 : oxnassata ata1: SATA max UDMA/133 irq 18 ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: HPA detected: current 3907029168, native 18446744073321613488 ata1.00: ATA-8: WDC WD20EADS-00R6B0, 01.00A01, max UDMA/133 ata1.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 0/32) ata1.00: configured for UDMA/133 scsi 0:0:0:0: Direct-Access WDC WDC WD20EADS-00R 01.0 PQ: 0 ANSI: 5 sd 0:0:0:0: [sda] 3907029168 512-byte hardware sectors (2000399 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 0:0:0:0: [sda] 3907029168 512-byte hardware sectors (2000399 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sda: sda1 sda2 sda3 sda4 sd 0:0:0:0: [sda] Attached SCSI disk ox810sata: OX810 sata core. scsi1 : oxnassata ata2: SATA max UDMA/133 irq 18 ata2: SATA link down (SStatus 0 SControl 300) mice: PS/2 mouse device common for all mice md: linear personality registered for level -1 md: raid0 personality registered for level 0 md: raid1 personality registered for level 1 device-mapper: ioctl: 4.12.0-ioctl (2007-10-02) initialised: dm-devel@redhat.com TCP cubic registered NET: Registered protocol family 1 NET: Registered protocol family 17 md: Autodetecting RAID arrays. md: Scanned 4 and added 4 devices. md: autorun ... md: considering sda4 ... md: adding sda4 ... md: sda3 has different UUID to sda4 md: sda2 has different UUID to sda4 md: sda1 has different UUID to sda4 md: created md2 md: bind md: running:  raid1: raid set md2 active with 1 out of 2 mirrors raid1 not hw raidable, needs two working disks. md: considering sda3 ... md: adding sda3 ... md: sda2 has different UUID to sda3 md: sda1 has different UUID to sda3 md: created md3 md: bind md: running:  raid1: raid set md3 active with 1 out of 2 mirrors raid1 not hw raidable, needs two working disks. md: considering sda2 ... md: adding sda2 ... md: sda1 has different UUID to sda2 md: created md1 md: bind md: running:  raid1: raid set md1 active with 1 out of 2 mirrors raid1 not hw raidable, needs two working disks. md: considering sda1 ... md: adding sda1 ... md: created md0 md: bind md: running:  raid1: raid set md0 active with 1 out of 2 mirrors raid1 not hw raidable, needs two working disks. md: ... autorun DONE. kjournald starting. Commit interval 5 seconds EXT3 FS on md0, internal journal EXT3-fs: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem). Freeing init memory: 108K Adding 256952k swap on /dev/md1. Priority:-1 extents:1 across:256952k Registered led device: oxnas-wd810-leds:switch Registered led device: oxnas-wd810-leds:state Registered led device: oxnas-wd810-leds:activity Registered led device: oxnas-wd810-leds:capacity /etc/init.d/S01auto_mountd /etc/init.d/S10portmap Stoping portmap: killall: portmap: no process killed OK /etc/init.d/S40network /etc/init.d/S50sshd Stopping sshd: killall: sshd: no process killed OK /etc/init.d/S55mini_httpd Stopping mini_httpd: killall: mini_httpd: no process killed OK /etc/init.d/S60inetd Stopping inetd... killall: inetd: no process killed OK /etc/init.d/S85ntpdated Shutting down NTP client: OK /etc/init.d/S90optware exportfs: /etc/exports [1]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/nfs/Public". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x exportfs: /etc/exports [2]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/nfs/Download". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x exportfs: Warning: /nfs/Download does not exist exportfs: Warning: /nfs/Public does not exist /etc/init.d/S90smbd Shutting down SMB services: FAIL Shutting down NMB services: FAIL /etc/init.d/S94fuse Fuse control filesystem not mounted. Fuse module not loaded. /etc/init.d/S95windbindd /etc/init.d/S96wixalarm Stopping the Wistron AlarmAPIs : FAIL /etc/init.d/S97twonkyserver PID file /var/run/twonky.pid not found, stopping server anyway... killall: twonkymedia: no process killed killall: twonkymusic: no process killed killall: twonkymediaserver: no process killed /etc/init.d/S98logrotate Stoping logrotate: FAIL /etc/init.d/S99sxminit Stopping syslogd......OK Stopping downloader.....OK /etc/init.d/S9M_mionet /etc/init.d/S9WiAutoConfig killall: WiAutoConfig: no process killed /etc/init.d/S9lltd $Shutting down lltd services: FAILED /etc/init.d/S9mDNSResponder $Shutting down mDNSResponder services: OK Stopping hotplug.....OK Umounting shares......Failed Umounting DataVolume......Failed Turn swap off......OK Stopping network.....rmmod: gmac: No such file or directory OK Umounting /proc.....OK Umounting /dev/pts.....OK Umounting /var.....Failed Umounting /sys/kernel/security.....OK Umounting /sys.....OK Umounting /.....OK Turning off LEDs.....OK Unload the Thermal & fan module.....OK The system is going down NOW !! Sending SIGTERM to all processes. Sending SIGKILL to all processes. md: md2 in immediate safe mode md: md3 in immediate safe mode md: md1 in immediate safe mode md: md0 in immediate safe mode The system is halted. md: stopping all md devices. md: md1 switched to read-only mode. md: md3 switched to read-only mode. md: md2 switched to read-only mode. md: md0 still in use. sd 0:0:0:0: [sda] Synchronizing SCSI cache sd 0:0:0:0: [sda] Stopping disk Power down. CoPro: Programming start address as 0x9801e000 (basic adr = 0x9801e000) Turning off disk 1 Turning off disk 2 Initialising disks No FIS received from device 1 No FIS received from device 1 Detecting SATA busses: Bus 0: Found first device OK Device 0: Model: WDC WD20EADS-00R6B0 Firm: 01.00A01 Ser#: WD-WCAVY0083223 Type: Hard Disk Supports 48-bit addressing Capacity: 1907729.0 MB = 1863.0 GB (-387938128 x 512) Device 1: not available Environment successfully read from disk 0 primary image U-Boot 1.1.2 (Oct 2 2008 - 12:51:43) U-Boot code: 48D00000 -> 48D1B228 BSS: -> 48D1F040 RAM Configuration: Bank #0: 48000000 128 MB SRAM Configuration: 128KB at 0x58000000 WARNING: flash_make_cmd: unsuppported LittleEndian mode WARNING: flash_make_cmd: unsuppported LittleEndian mode WARNING: flash_make_cmd: unsuppported LittleEndian mode WARNING: flash_make_cmd: unsuppported LittleEndian mode WARNING: flash_make_cmd: unsuppported LittleEndian mode WARNING: flash_make_cmd: unsuppported LittleEndian mode WARNING: flash_make_cmd: unsuppported LittleEndian mode WARNING: flash_make_cmd: unsuppported LittleEndian mode WARNING: flash_make_cmd: unsuppported LittleEndian mode WARNING: flash_make_cmd: unsuppported LittleEndian mode WARNING: flash_make_cmd: unsuppported LittleEndian mode WARNING: flash_make_cmd: unsuppported LittleEndian mode WARNING: flash_make_cmd: unsuppported LittleEndian mode ## Unknown FLASH on Bank 0 - Size = 0x00000000 = 0 MB Flash: 0 kB In: serial Out: serial Err: serial WD 1NC Board IDE read: device 0 block # 255, count 1 ... 1 blocks read: OK Controlled Power DOWN requested Hit any key to stop autoboot: 2 1 0 IDE device 0: Model: WDC WD20EADS-00R6B0 Firm: 01.00A01 Ser#: WD-WCAVY0083223 Type: Hard Disk Supports 48-bit addressing Capacity: 1907729.0 MB = 1863.0 GB (-387938128 x 512) ... is now current device IDE read: device 0 block # 300, count 5700 ... 5700 blocks read: OK ## Booting image at 48500000 ... Image Name: Linux-2.6.24.4 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1593324 Bytes = 1.5 MB Load Address: 48008000 Entry Point: 48008000 Verifying Checksum ... OK OK Starting kernel ... Uncompressing Linux.................................................................................................... done, booting the kernel. Linux version 2.6.24.4 (brian@dualla) (gcc version 4.2.4) #1 Tue Feb 10 11:00:22 GMT 2009 CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177 Machine: Oxsemi NAS Ignoring unrecognised tag 0x00000000 Memory policy: ECC disabled, Data cache writeback CPU0: D VIVT write-back cache CPU0: I cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets CPU0: D cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512 Kernel command line: root=/dev/md0 console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x90,0xA9,0x6D,0x26,0xC8 mem=128M wixmodel=WWLXN powermode=controlledpdown poweroutage=yes timeINC=949558681 PID hash table entries: 512 (order: 9, 2048 bytes) Console: colour dummy device 80x30 console [ttyS0] enabled Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 128MB = 128MB total Memory: 126592KB available (2892K code, 152K data, 108K init) Security Framework initialized Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok net_namespace: 64 bytes NET: Registered protocol family 16 Number of DMA channels = 5, version = 4 Allocating 891 SRAM generic DMA descriptors Chip Id: die-id 0x0752bd30e980 read back 0xbeefcafe SCSI subsystem initialized NET: Registered protocol family 2 IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP established hash table entries: 4096 (order: 3, 32768 bytes) TCP bind hash table entries: 4096 (order: 2, 16384 bytes) TCP: Hash tables configured (established 4096 bind 4096) TCP reno registered Hello, LED trigger fuse init (API version 7.9) SGI XFS with large block numbers, no debug enabled SGI XFS Quota Management subsystem io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled ÿserial8250: ttyS0 at MMIO 0x44300000 (irq = 24) is a 16550A RAMDISK driver initialized: 16 RAM disks of 10240K size 1024 blocksize loop: module loaded Driver 'sd' needs updating - please use bus_type methods ox810sata: OX810 sata core. scsi0 : oxnassata ata1: SATA max UDMA/133 irq 18 ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: HPA detected: current 3907029168, native 18446744073321613488 ata1.00: ATA-8: WDC WD20EADS-00R6B0, 01.00A01, max UDMA/133 ata1.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 0/32) ata1.00: configured for UDMA/133 scsi 0:0:0:0: Direct-Access WDC WDC WD20EADS-00R 01.0 PQ: 0 ANSI: 5 sd 0:0:0:0: [sda] 3907029168 512-byte hardware sectors (2000399 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 0:0:0:0: [sda] 3907029168 512-byte hardware sectors (2000399 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sda: sda1 sda2 sda3 sda4 sd 0:0:0:0: [sda] Attached SCSI disk ox810sata: OX810 sata core. scsi1 : oxnassata ata2: SATA max UDMA/133 irq 18 ata2: SATA link down (SStatus 0 SControl 300) mice: PS/2 mouse device common for all mice md: linear personality registered for level -1 md: raid0 personality registered for level 0 md: raid1 personality registered for level 1 device-mapper: ioctl: 4.12.0-ioctl (2007-10-02) initialised: dm-devel@redhat.com TCP cubic registered NET: Registered protocol family 1 NET: Registered protocol family 17 md: Autodetecting RAID arrays. md: invalid raid superblock magic on sda4 md: sda4 does not have a valid v0.90 superblock, not importing! md: Scanned 4 and added 3 devices. md: autorun ... md: considering sda3 ... md: adding sda3 ... md: sda2 has different UUID to sda3 md: sda1 has different UUID to sda3 md: created md3 md: bind md: running:  raid1: raid set md3 active with 1 out of 2 mirrors raid1 not hw raidable, needs two working disks. md: considering sda2 ... md: adding sda2 ... md: sda1 has different UUID to sda2 md: created md1 md: bind md: running:  raid1: raid set md1 active with 1 out of 2 mirrors raid1 not hw raidable, needs two working disks. md: considering sda1 ... md: adding sda1 ... md: created md0 md: bind md: running:  raid1: raid set md0 active with 1 out of 2 mirrors raid1 not hw raidable, needs two working disks. md: ... autorun DONE. kjournald starting. Commit interval 5 seconds EXT3 FS on md0, internal journal EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem). Freeing init memory: 108K Swap area shorter than signature indicates Registered led device: oxnas-wd810-leds:switch Registered led device: oxnas-wd810-leds:state Registered led device: oxnas-wd810-leds:activity Registered led device: oxnas-wd810-leds:capacity /etc/init.d/S01auto_mountd /etc/init.d/S10portmap Stoping portmap: killall: portmap: no process killed OK /etc/init.d/S40network /etc/init.d/S50sshd Stopping sshd: killall: sshd: no process killed OK /etc/init.d/S55mini_httpd Stopping mini_httpd: killall: mini_httpd: no process killed OK /etc/init.d/S60inetd Stopping inetd... killall: inetd: no process killed OK /etc/init.d/S85ntpdated Shutting down NTP client: OK /etc/init.d/S90smbd Shutting down SMB services: FAIL Shutting down NMB services: FAIL /etc/init.d/S94fuse Fuse control filesystem not mounted. Fuse module not loaded. /etc/init.d/S95windbindd /etc/init.d/S96wixalarm Stopping the Wistron AlarmAPIs : FAIL /etc/init.d/S97twonkyserver PID file /var/run/twonky.pid not found, stopping server anyway... killall: twonkymedia: no process killed killall: twonkymusic: no process killed killall: twonkymediaserver: no process killed /etc/init.d/S98logrotate Stoping logrotate: FAIL /etc/init.d/S99sxminit Stopping syslogd......OK Stopping downloader.....OK /etc/init.d/S9M_mionet /etc/init.d/S9WiAutoConfig killall: WiAutoConfig: no process killed /etc/init.d/S9iTune iTunes Server for Linux WiDMS v1.50 (0823.008) kill: No such process /etc/init.d/S9lltd $Shutting down lltd services: FAILED /etc/init.d/S9mDNSResponder $Shutting down mDNSResponder services: OK Stopping hotplug.....OK Umounting shares......Failed Umounting DataVolume......Failed Turn swap off......Failed Stopping network.....rmmod: gmac: No such file or directory OK Umounting /proc.....OK Umounting /dev/pts.....OK Umounting /var.....Failed Umounting /sys/kernel/security.....OK Umounting /sys.....OK Umounting /.....OK Turning off LEDs.....OK Unload the Thermal & fan module.....OK The system is going down NOW !! Sending SIGTERM to all processes. Sending SIGKILL to all processes. md: md3 in immediate safe mode md: md1 in immediate safe mode md: md0 in immediate safe mode The system is halted. md: stopping all md devices. md: md1 switched to read-only mode. md: md3 switched to read-only mode. md: md0 still in use. sd 0:0:0:0: [sda] Synchronizing SCSI cache sd 0:0:0:0: [sda] Stopping disk Power down. CoPro: Programming start address as 0x9801e000 (basic adr = 0x9801e000) Turning off disk 1 Turning off disk 2

where is the kernel at the white light?

Tue, 20 Oct 2009 09:34:19 +0000

got serial access to white light 2TB edition single drive. i want to put debian armel squezze on it like i did with some buffalo devices. but where is the kernel? i guess at some non-filesystem space in the first sectors. does someone knows it?

Debian on WD MyBook "White Light" Possible?

Thu, 30 Jul 2009 15:13:06 +0000

Is there currently a way to install Debian on WD MyBook "White Light"?

"MyLenny" firmware

Tue, 16 Jun 2009 11:48:21 +0000

Here's a simple way to install Debian Lenny
http://mybookworld.wikidot.com/mylenny-firmware

I tested it on my 2TB two-disk box with both stock firmware and Debian Lenny installed.

Cheers,

Cheap Trick to Get Debian Lenny Working

Tue, 09 Jun 2009 10:23:39 +0000

After trying all kinds of methods without seeing Debian running on my 500G mbwe (blue light, single hard drive version). Since I don't have a serial cable, I can't see what comes up at boot time to debug. Angry and frustrated, I decided to try this dirty trick to see what kind of hybrid monster would boot (if it would boot at all). But it did boot up and works fine as Debian Lenny! Strange. Hopefully I'm not the only lucky one trying this trick.

This is what I did to have Debian Lenny working on my single hard drive 500G mbwe.

Open the mbwe box and connect its hard drive with stock firmware to a Linux machine.

Connect a new hard drive to the Linux machine. This will be used as the hard drive with Debian Lenny for the mbwe box. You can try it on the stock hard drive if you don't mind the risk of losing data on it.

dd the first 10GB of data on the stock hard drive to the new hard drive.

Connect the new hard drive to the mbwe box and see if it boots. Ping it and log in to see if it works OK. If it does, that's good.

Take the new hard drive out and connect it to the Linux machine. Mount the first partition of the new hard drive. Back up the files in this partition to a safe location, then delete them all. Now the first partition will be empty.

Download these files (To Mario: Thanks mate!)
http://www.ismprofessional.net/pascucci/documenti/mybook/packages/mybook-rootfs-debian-20070826.tar.bz2
http://www.ismprofessional.net/pascucci/documenti/mybook/packages/kernel-2.6.17.14-20070817-mybook.tar.gz
and extract them to the first partition. Having done that, disconnect the hard drive and connect it to the mbwe box. Prepare to be excited (or utterly disappointed).

Moment of truth. Boot the mbwe box. No light will come on telling you it's ready. Just put your ear next to the hard drive and check if it's cranking. Also try to ping it, check your router to see if it has given the mbwe an IP address, use AngryIP to scan your whole subnet, or do whatever it takes to find the IP address of the mbwe (if it gets one). If it has an IP address that you can ping, you're in business! ssh that address with username root and password mybook will let you in.

If the above sounds like a lot of words, I'll make it simple. All that needs to be done is to remove the original file system on the first partition and replace it with the Debian Lenny file system compiled by Mario.

The reason I made the instructions vague is because I don't know if it works for anyone other than me, so I want more experienced users to have a crack first. If the success rate is good, then more detailed instructions will follow.

Good luck. I hope it works because I'd to say I've given something back to the community.

Cheers.

How Do I create a serial port?

Mon, 04 May 2009 02:29:30 +0000

I've tried to install Debian via a USB to SATA adapter per the instructions at http://mybookworld.wikidot.com/forum/t-30649/my-fast-and-perfect-setup-of-debian-lenny-into-my-500gb-world-book, but my MBWE won't boot up.

My board looks like the one at Martin Hinner's site, http://martin.hinner.info/mybook/pictures.php, but I am looking for advice on how to turn those four holes into a serial port. I'm not experienced with building a computer, but could solder a connector in if I could find one. Does anyone know if there is a particular part I can order that can be soldered to the board? Can anyone recommend a cable to connect this to my laptop? Must it be a serial cable or can it be a USB phone cable?

Thanks in advance!

It´s possible to install Windows Media Center?

Tue, 28 Apr 2009 06:29:47 +0000

Hello.

I think that installa WMCE is impossible but I need to ask it :D

If I could install a WMCE in WD my XBOX360 could access to the WD through the embbed MC and see the files with a great interface.

Regards

[SOLVED] NFS write but not rewrite in MBWE with Debian Lenny

Fri, 03 Apr 2009 08:00:01 +0000

Hi everyone.

I installed Debian Lenny from scratch following the tutorial of Mario Pascucci.

I had to tune the system to compile propely both tools and binaries (i.e: using a specific version of GCC 3.4). Then when I compiled the kernel I configure it to include NFS support built-in (both server and client). After compile sucessfully I copied to MBWE and boot and logged in by SSH. I configured repositories and runned

 mybook# apt-get install nfs-kernel-server nfs-common

then I created a directory /shares

 mybook# mkdir /shares mybook# chown nobody.nogroup /shares mybook# chmod 775 /shares

then in /etc/exports I added this line

 /shares 192.168.0.0/255.255.255.0(rw,sync,no_subtree_check,all_squash,anonuid=65534,anongid=65534)

then run the exportfs command to reread the exports configuration

 mybook# exportfs -a

Finish in MBWE. Now in my laptop I mounted the shared resource:

 laptop$ sudo mount -t nfs -o defaults 192.168.0.100:/shares /mnt Password: laptop$ ls -l /mnt total 0 laptop$ ls / > /mnt/files #create 'files' into 'mnt' laptop$ ls -l /mnt total 3 -rw-rw-r-- 1 nobody nogroup 136 apr 3 09:40 files laptop$ ls / > /mnt/files #try to overwrite 'files' into 'mnt' -bash: /mnt/files: Permission denied laptop$ rm /mnt/files rm: remove write-protected regular file 'kk'? Y laptop$ ls -l /mnt total 0

The issue is that I can create files, I cannot overwrite files and I can remove files. I tried compile kernel with other options, compare versions of NFS, mount the MBWE shares in serveral computers but the results is the same.

Anyone have any idea of why is NFS punishing me with this?

Thanks.

New, White Light My book World Edition Software

Mon, 23 Feb 2009 12:45:50 +0000

Does anyone know if it would be possible to copy the software from the New (White Light) Mybook world edition and install it on to the Blue ring 1TB version?
The new My book World Edition comes complete with Upnp support for PS3's and simpler file construction (according to the website). I have tried to follow the tutorial for installing twonkymedia and have had lots of problems. This would be a far easier solution as I have very limited skill's with Linux.

If it is possible, does anyone know the source/ tutorial for the software.

Many thanks in advance for your help,

regards,
Nik.

After reaching 2.445 GB stop !

Tue, 17 Feb 2009 23:16:58 +0000

While I am trying to upload file from my machine to MBWD though FTP just stop !
the file size is around 7 GB ((Backup file from Acronis True Image program) ).
I try SFTP even SCP didn’t work !
I try many ides but still does work >
It's stop when it's reach 2.445 GB exactly .
if it's mean anything why this number ! three times .
which is stranger! I use three kind of protocols in different time ! still stop when it’s reach 2.445 GB
maybe samba configurations !
Please advise me anything >
This thing make me crazy ! 

Regard's

Raed

nfs.ko and cifs.ko for Debian Lenny

Sat, 14 Feb 2009 16:07:46 +0000

Hello,

Install Debian Lenny on 500GB World Book is easy with tutorial "My fast and perfect setup of Debian Lenny into my 500GB World Book". Thanks for it.

Now im looking for nfs and cifs filesystem support. I don't like to work through the whole tutorial by Mario Pascucci just to compile two modules. Had someone compiled the kernel modules cifs.ko and nfs.ko or can do that and publish them?

Debian Lenny on MyBookWorld 500GB

Tue, 03 Feb 2009 23:19:23 +0000

Hello everybody!

I have a mybookworld 500gb edition and a want to install a fresh debian lenny on it. I have read some tutorials , doing all step of it(I took the files packages on the mybook repository like it was said), but after that , my mybook doesn't want to boot the new debian. no blue led. and i can't connect on ssh.

link of the tutorials : http://mybookworld.wikidot.com/forum/t-30649/my-fast-and-perfect-setup-of-debian-lenny-into-my-500gb-world-book
http://www.ismprofessional.net/pascucci/documenti/mybook/mybook-hacking-en.html#id2929663

Is it possible to make another tutorial or make the current more easier?
What is the way to boot the mybook?

Thanks for your help and your work!! and sorry for my english i'm a french student.

/dev/sdb: No such device or address

Tue, 13 Jan 2009 22:55:18 +0000

[root@MyStorage lighttpd]# /etc/init.d/lighttpd.sh stop
Stopping lighttpd
[root@MyStorage lighttpd]# /etc/init.d/lighttpd.sh start
Starting lighttpd
[root@MyStorage lighttpd]# /dev/sdb: No such device or address

Any ideas why? MyBook is working fine

Implications of changing the Kernel

Wed, 07 Jan 2009 17:26:16 +0000

I recently purchased a MyBookWorld, and after stumbling on this site decided to start modding it.

Problem:
I also own a Netgear SC101 which for those that dont know is a micro SAN device. My goal is to allow the MBWE to control the SC101. To use this drive from Linux it is required to compile sc101-nbd package. As the name suggest this package requires the nbd kernel module to be loaded.

Herein lied my first difficulty as the nbd module was not included in the WD firmware. So after lengthly research managed to use the WD development toolkit's crosstool to build
the arm crosscompiler with uClibc and install locally. Using this crosscompiler I set about reconfiguring the kernel source included in WD development toolkit to build the nbd.ko (kernel module). (I would like to thank Mario Pascucci for his very informative guide about reviving a mybook) After a successful compile and many unsuccessful ones I then discovered the lack of depmod on MBWE and as far as I can tell from optware as well so had to compile this from source:(. Only one part left to the installation of nbd was to create the /dev/nbd0 special file as the MBWE does not use devfs. This was achieved with the mknod command, registering the device at major 43. After installing the nbd module and modprob'ing it successfully on the MBWE I thought that the hard part was over.

Next:
I managed to compile sc101-nbd-0.03 natively, only having to add an extra include to the source files for socket.h, I think. After loading the nbd module successfully and using the sc101-nbd package I managed to attach my sc101 to /dev/nbd0 and then mount this to /mnt/blah. I could browse the files stored on the sc101 from the mybookworld, cat also worked upto a point. Now comes the unexpected part, it appears that after some traffic has been received from the sc101 I start to get IO errors. A quick look in dmesg shows that nbd closed the socket and is now complaining that the socket is closed (control failed -32). After further looking about I think that there is some race condition that is happening as descried here but not entirely sure.

I am now thinking this is a bug with the specific kernel used which is exasperated by the MBWE architecture/scheduling algorithm, I attempted to pull nbd.c and nbd.h from a newer kernel (2.6.24) and place them into the correct places in the WD development toolkit linux-kernel source tree. Compilation failed as some data structures have changed and I am not experienced enough with C nor the linux kernel to start playing about at that level.

Conclusion:
An option could be to use the procedure shown here to install Debian Lenny but I have some reservations. I noticed while looking about in the MBWE kernel source a number of modifications to the source that deviate from a vanilla kernel, primarily with respect to the oxnas architecture. But also there are a number of other files such as raid0.c raid1.c that are modified. I cant remember a complete list of these changes. The guide implies that just because arm5el arch is supported by Lenny, all will work. Also a look at the OX800SE on the manufactures website suggests this. Some features such as Java byte code execution is directly supported by the ARM architecture. But other features from the OX800SE chip such as high speed 128bit-AES encryption are lost? Would this be a fair assumption?

So essentially if I choose the Lenny route, I will loose all the software that ships with MBWE and some functions from the OX800SE chip? Also does the power button stops doing funky things? Does any body know what is lost and what is gained? I have head that Lenny is much faster than the default firmware? Are there any problems setting up raid1? I assume that with the default firmware that raid is managed by hardware tho cant find enough literature about the chip.

Any comments are appreciated, did I do something wrong with the nbd compilation/installation, has any body managed to get nbd working? Is there a simple solution I have overlooked?

Thanks,
Karim Kanso

Need help using wd world edition II 2tb

Sat, 25 Oct 2008 18:53:51 +0000

I recently purchased wd mybook world editionII 2tb and i have no idea how to set it up and use it.. i purchased it thinkin that it would be a usb storage unit.. and i thought as i connect it to my computer it would show me the drives but it doesnt.. i have a d-link wireless router.. i tried everything but it doesnt show me the drives.. please can you help me out with this matter.. i have installed the software as well but it displays them as offline.. PLEASE HELP.. thanks,

and i cant access http://mybookworld also.. i had altered the network address on it after restarting it the page doesnt open anymore.. it says page not found.. PLEASE HELP!

Thanks

Is it possible to install freebsd on MBWE?

Wed, 17 Sep 2008 22:25:18 +0000

Suggestions?

HAs anyone looked or tried to install OPENFILER on a MBWE ?

Sun, 13 Apr 2008 10:10:26 +0000

I still find openfiler to be almost the "ultimate" NAS software (most features, good interface, etc…)
I would love to be able to install that on any of my 4 MBWE's

so .. has anyone tried this or looked at this?
from the expert hackers …. would it even be possible?

I even may be willing to "sponsor" someone who want's to try

Thanks

Linux gains new architecture support - applicable to MBWE?

Thu, 27 Mar 2008 20:35:21 +0000

Hi all. Is this relevant to the MBWE or is it for a completely different processor?
[http://linuxdevices.com/news/NS5637467946.html]

Possible OSs supporting ARM architecture

Sat, 15 Mar 2008 08:58:11 +0000

I am patiently waiting shipment of my new MBWE II, and I'm here soaking up all the information I can.

As we know, the MBWE is based on an ARM architecture. So, I am wondering if anyone's had success with installing some of the other ARM based distro's. I see that there has been some success with installing Debian Lenny. Taking a look at distrowatch, there are a few linux distros compiled for use on ARM. http://distrowatch.com/search.php?architecture=arm

The list at the moment is:
1. Debian
2. Gentoo
3. NetBSD
4. Rock

Rock looks interesting, but package support must be leaps better on a wider distro.

I haven't personally tried installing linux onto an ARM system. I understand that the MBWE runs ARM925 (ARM5) which resides on oxford semi's OXE800SE chip. I just wonder what type of extensions this implementation ARM chip may have. I tried getting my hands on the datasheets for the chip, but they seem to have things pretty tight. I suppose I could call and ask for them, I'm sure to be shut down but it may be worth a try.

http://www.oxsemi.com/products/storage/OxfordSemiconductorStoragecontrollersOXE800SE.html

Also you'll notice, that the OXE800 chips support 2 usb ports, so if we get our hands on the datasheets we can find the pinouts. (just a thought)

discussion anyone?