Using and installing other OS's (new posts)

Searching fuse.ko: Re: Searching fuse.ko

Wed, 18 Nov 2009 20:54:03 +0000

ok ;-)

i think the problem is the vermagic stuff.
The kernel version i could adjust in the kernel config, but the gcc is 4.4 i cannot change it. ;-)

So, for me the solution is to add an entry in /etc/modules

—force fuse

then fuse will be loaded during startup. Ok, for me.
Maybe there is a better solution, but is seems to work.

Searching fuse.ko: Re: Searching fuse.ko

Wed, 18 Nov 2009 19:23:42 +0000

Ok, i used the snapshot versions of buildroot and busybox together with gcc 4.4.
everything compiled.
Ok.
Next problem ;-)

The compiled fuse.ko cannot be loaded by lenny…

Linux mybook2 2.6.17.14-20070817-mybook #9 PREEMPT Wed Aug 22 17:00:46 CEST 2007 armv5tejl
Last login: Wed Nov 18 13:24:36 2009 from 192.168.1.102
root@mybook2:~# modprobe fuse
FATAL: Error inserting fuse (/lib/modules/2.6.17.14-20070817-mybook/kernel/fs/fuse/fuse.ko): Invalid module format
root@mybook2:~#

modinfo shows, at least for me, nothing ;-)

oot@mybook2:~# modinfo fuse
filename: /lib/modules/2.6.17.14-20070817-mybook/kernel/fs/fuse/fuse.ko
alias: char-major-10-229
license: GPL
description: Filesystem in Userspace
author: Miklos Szeredi <uh.iderezs|solkim#uh.iderezs|solkim>
depends:
vermagic: 2.6.17.14 preempt mod_unload ARMv5 gcc-4.4
root@mybook2:~#

oot@mybook2:~# modinfo ntfs
filename: /lib/modules/2.6.17.14-20070817-mybook/kernel/fs/ntfs/ntfs.ko
license: GPL
version: 2.1.27
description: NTFS 1.2/3.x driver - Copyright (c) 2001-2006 Anton Altaparmakov
author: Anton Altaparmakov <ten.batnac|12aia#ten.batnac|12aia>
srcversion: 79FF905C6FD06F467ACDEDB
depends:
vermagic: 2.6.17.14-20070817-mybook preempt mod_unload ARMv5 gcc-3.4
root@mybook2:~#

ok, when i comare it with ntfs,ko i see only adiffrence in the gcc version and the kernel name.
Could this be the reason??

Thanks for any support.

Searching fuse.ko: Re: Searching fuse.ko

Tue, 17 Nov 2009 23:07:23 +0000

Ok, nobody seems to have a fuse module. ;-)

I tried to build a toolchain, but i failed..

I used the info from http://mybookworld.wikidot.com/adding-sound-support, but busybox failed to compile.

Does anybody has a working config for buildroot?

(my base sytem is ubuntu 9.05)

Thanks

Searching fuse.ko: 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

My fast and perfect setup of Debian Lenny into my 500GB World Book: Re: My fast and perfect setup of Debian Lenny into my 500GB World Book

Sun, 08 Nov 2009 13:18:40 +0000

Thanks sany_v,

this solves my problem. ;-)

"MyLenny" firmware: Re: "MyLenny" firmware

Fri, 23 Oct 2009 17:25:59 +0000

Hi,
I have problem with "su" or "sudo" commands.
If I try use them, i got "libc.so.6: aborted attempt to load sudo!".
Can anyone help me fix it?

Thanks

serial access to white light: Re: serial access to white light

Tue, 20 Oct 2009 14:22:37 +0000

update:

i got debian squeeze with the new arm eabi (armel) running. i chrooted with an armel box and debootstrapped, but the kernel is still the old. i should fix the kernel, so that the system runs quite well.
for now the network card is doing kernel crashes from time to time. i guess the fault is the gmac firmware.
maybe someone can help, too.

serial access to white light: 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?: 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?

My fast and perfect setup of Debian Lenny into my 500GB World Book: Re: My fast and perfect setup of Debian Lenny into my 500GB World Book

Sat, 17 Oct 2009 19:28:53 +0000

I found problem.

Problem was in file system atribute & feature , u-boot support only i-node size 128 not more , when you make fs check that you FS support same Feature like original on wd mybook:
Filesystem features: has_journal filetype sparse_super large_file
….
Inode size: 128
….
other case u-boot can't see rootfs & kernel (uImage)

My fast and perfect setup of Debian Lenny into my 500GB World Book: Re: My fast and perfect setup of Debian Lenny into my 500GB World Book

Sat, 17 Oct 2009 14:28:41 +0000

i have same problem with no booting linux, i make reinstal many times from different linux os.

After that i made serial cable and connet to my linux PC, and what i saw:
$ NASOx_0800
dom lug 22 19:36:28 CEST 2007

U-Boot 1.1.2 (Jul 23 2007 - 13:53:26)

U-Boot code: 48D00000 -> 48D17658 BSS: -> 48D1B2C8
RAM Configuration:
Bank #0: 48000000 32 MB
*** Warning - bad CRC, using default environment

Boot reached stage -1
In: serial
Out: serial
Err: serial
Initialising disks
No FIS received from device 1
Detecting SATA busses:
Bus 0: Found first device OK
Device 0: Model: HTS721060G9SA00 Firm: MC3OC10H Ser#: MPCC11Y3G3HW0C
Type: Hard Disk
Supports 48-bit addressing
Capacity: 57231.5 MB = 55.8 GB (117210240 x 512)
Device 1: not available

IDE read: device 0 block # 63, count 1 … 1 blocks read: OK
Hit any key to stop autoboot: 0

0 bytes read
Boot reached stage 1
## Booting image at 48500000 …
Bad Magic Number
Boot reached stage -1

Any ideas, what do next?

"MyLenny" firmware: Re: "MyLenny" firmware

Fri, 28 Aug 2009 12:50:43 +0000

I have a couple of questions:
- Can I backup my /dev/root and /dev/md3 while running using dd?
- The power button which doesn't work, is it just the lights or can't I shut it down with the power button/restart it? Do I have to reboot via SSH or can i use the button?
- Can I install the firmware.sh through SSH?

Debian on WD MyBook "White Light" Possible?: Re: Debian on WD MyBook "White Light" Possible?

Fri, 21 Aug 2009 07:59:48 +0000

So does anyone had a success with it? I'm just trying to follow the instructions described here:
http://mybookworld.wikidot.com/forum/t-30649/my-fast-and-perfect-setup-of-debian-lenny-into-my-500gb-world-book
but it doesn't work for me (Im using mbwe 1Tb "white light") Also I've tryed to install an image, that works fine under the qemu emulation, using "dd if=image.raw of=/dev/sdb", I even disassembled mbwe and connected drive to the SATA II port om my desktop(Debian squeeze), but that didn't work too. So does anyone have any suggestions how to install Debian arm on a mbwe "white light"?

P.S. sorry for my bad english.

"MyLenny" firmware: Re: "MyLenny" firmware

Wed, 05 Aug 2009 01:16:19 +0000

Ok - went ahead.

All good. SAMBA in and up :o)

Only 2 things remain……

The hard disc never ever spins down.

Has anyone done any work on this with Debian on a Mybook?

Also, apt-get says that the latest udev conflicts with this particular kernel. Any thoughts on how to proceed anyone?

Dan

"MyLenny" firmware: Re: "MyLenny" firmware

Sun, 02 Aug 2009 09:12:10 +0000

Before doing this installation I have a couple of things to ask of those who have already installed Lenny on their units.

Does the hard drive spin down and stay down after a time of no use? (I have modded my current standard 2.00.18 firmware with scripts for this).

Does the usb port on the unit still function?

Do the blue leds operate as before - i.e spinning effect when disc is being accessed?

After installation does the data partition get mounted automatically?

I will also have to learn how to configure samba from the terminal….Not too hard I imagine.

That's it for now.

:o))

Debian on WD MyBook "White Light" Possible?: Re: Debian on WD MyBook "White Light" Possible?

Thu, 30 Jul 2009 20:42:32 +0000

take a look there is tons of guides http://mybookworld.wikidot.com/forum/t-161592/cheap-trick-to-get-debian-lenny-working
But at all there is always problems, sometimes it works sometimes not.

Debian on WD MyBook "White Light" Possible?: 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: Re: "MyLenny" firmware

Thu, 30 Jul 2009 05:04:29 +0000

Well, I was actually just coming by to drop off a hint on this very problem. In fact I was just deciding on where I should post my message, but I guess here is as good a place as any. :)
Anyways, I had the same problem and it turns out that in my case it's spinning someplace in /etc/rcS.d/S30checkfs.sh . In fact on my device I see it spawning two instances of 'sleep 1' at a time over and over again. Must be sourcing some other file, cause I don't see that behavior in the actual checkfs.sh script. I'll keep looking but in the meantime, in order to access your device you need to add yourself a backdoor of some type. I plugged one of the two drives from my MBWE II (blue lights) into my laptop, started up the RAID in degraded mode (mdadm —auto-detect), mounted the lenny part of the drive (mount /dev/md1 /mnt/md1), and created a new file:

vi /mnt/md1/etc/rcS.d/S11hack

#---CUT HERE-——
#!/bin/sh

/sbin/ifconfig eth0 192.168.1.2
/usr/sbin/sshd &
exit 0

#-END HERE--

Made that executable (chmod +x /mnt/md1/etc/rcS.d/S11hack), plugged the drive back into the device, fired it up and I'm back in and diagnosing it at least. I'd be curious to know if someone found a real cure for this, rather than an ugly hacl. ;)

Also, thanks to everyone for all on the great work on this so far! Always nice to see Debian running on more devices. It's really starting to earn that "universal operating system" name. :D

"MyLenny" firmware: Re: "MyLenny" firmware

Wed, 29 Jul 2009 19:32:00 +0000

Hi,

I want to install your firmware, but the mybook does not connect to the network now. So I cannot use this now.

- I installed the firmware.
- Change root password and reconfigure sshd.
- I upgrade my system with —fix-missing options.
- I installed "locales" and I reconfigure this, too. (I change the locale to hu_HU.UTF8).
- Reboot mybook and it does not connect to the network.

Can you help me? What's wrong?

Thanks!

New, White Light My book World Edition Software: Re: New, White Light My book World Edition Software

Sat, 25 Jul 2009 12:42:00 +0000

no i dont think so, as i know no one done it before.