Ci sono novità:
- Un nuovo kernel
- Un nuovo root filesystem basato su Debian “lenny”
There are some good news:
- New kernel
- New root filesystem, based on Debian “lenny”
Le istruzioni sono cambiate, ma sempre qui, il nuovo kernel ed il filesystem di root sono prelevabili qui.
Il MyBook prende l’indirizzo di rete via DHCP, quindi serve un server DHCP attivo nella rete in cui viene connesso. Oppure modificare il file /etc/network/interfaces per assegnare un indirizzo statico.
Per accedere via SSH: utente “root”, password “mybook” (senza virgolette)
New instructions are here. A new root filesystem and a new kernel are here.
Now the MyBook get an IP address via DHCP, so you need a DHCP server in your network. Or you can modify the file /etc/network/interfaces to assigna a static IP address.
To logon through SSH: user “root”, password “mybook” (without quotes)
#1 da Gareth il 15 April 2008 - 09:01
Hi,
Enjoyed going through your MyBook detail, and tried natively compiling a kernel (to also build a few more device driver modules)… I’ve done the kernel build steps as you describe, and it all seems to build ok.
I took out the cross compile line in the Makefile, ran “make oxnas_wd2nc_defconfig”, then “make menuconfig” and removed the leon support. Ran “make uImage” and placed the new uImage in the root of sda1, “make modules” and copied the modules into /lib/modules.
But, no blue light on boot,
…is there something significant which would stop this working natively? Nothing shows in /var/log/* , and I have no serial access, so it’s a bit of a shot in the dark!
I don’t want to waste your time, but if you have any obvious ideas?
Thanks,
Gareth.
#2 da Mario Pascucci il 15 April 2008 - 09:12
@Gareth
Have you installed the new bootloader as explained in the document? Original bootloader is not able to load kernel from ext3 filesystem.
Double check the modules directory, it must be /lib/modules/[kernel-version]/.
Of course, you will have something in /var/log only when you successfully boot and when you have a syslog daemon running.
#3 da Gareth il 17 April 2008 - 15:53
Mario, I followed your instructions and set up a fresh disk. It boots fine – but I fancied compiling a new kernel on the unit itself with gcc-4.2, rather than the crosstool chain gcc-3.4. Your crosscompiled kernel & modules boot just fine, thanks.
Is there anything set in your boot loader to expect the gcc3.4 kernel only? Or perhaps some compatibility I have missed? I ran “make oxnas_wd2nc_defconfig” and then copied in your .config, ran “make menuconfig” and removed the leon support…
I may have to resort to a serial connection (a skill I do not really have). Since no logging daemons ever run to indicate what went wrong…
Do I need links from the /boot directory pointing to the uImage in the root? (and system map), since the boot loader looks in the root of sdb1, not /boot/uImage ?
Gareth.
#4 da Mario Pascucci il 17 April 2008 - 16:56
@Gareth
If I remember, gcc 4.x cannot cross compile for ARM, due a bug. Gcc 4.x create EABI binaries, and ARM cross compiling is broken in this way.
In one of my tries, I’ve attempted to use a virtual machine with Qemu (that emulates ARM platform) and Fedora for ARM, to build a kernel using native gcc 4.x, but I give up because lack of time.
You can try this way.
Or use gcc 3.x that cross compile fine with OABI (Old ABI).
#5 da Gareth il 17 April 2008 - 17:23
Mario,
I am not cross compiling. I am compiling it on the MyBook. So gcc4.2 should be fine, no?
Gareth.
#6 da Mario Pascucci il 18 April 2008 - 09:21
@Gareth
The bootloader works loading kernel from the root of first partition (see sect.6 “Second stage bootloader”). Symbolic links in /boot images are only for compatibility. I don’t know if some package search for kernel in /boot, so I put a link, to be sure.
I think you need a serial interface, at least to see what kernel says during boot process. Even bootloaders write characters to serial for debug purposes.
You can refer to links in document, or links in mybook wiki:
http://mybookworld.wikidot.com/
Section Hacks and tutorials.
#7 da Gareth il 18 April 2008 - 16:21
Is it possible for you to alter the u-boot image so that it writes debug output into a log file in the first partition ? My confidence in wiring a serial connection is not good!
#8 da Gareth il 21 April 2008 - 12:52
Ignore that last request… it was a quiet weekend, so I dug out an old DKU5 Nokia cable and put together a serial link. Now I have to work out what’s causing the stack trace as the kernel boots… Going to try a gcc3.4 build first…
#9 da Mario Pascucci il 24 April 2008 - 09:19
@Gareth
It is quite impossible, for me, to do a such massive changes to u-boot. I’m not so skilled. For what I see, modification to redirect output on a file are very extended, and involves a lot of work.
Surely to get a serial cable is less expensive
#10 da Gareth il 28 April 2008 - 11:00
Sure, as I posted on the 21st – I went with an old nokia cable to view the boot failures… Tried gcc3.4 instead – and it boots up ok.
Not sure why gcc4.x was a problem, even after patching over some inbuilt type clashes… never mind, works now, thanks.
Pingback: Hacking WD MyBook World Ed: Existing Info And Discussion
#11 da martin il 22 September 2009 - 00:10
buona sera arrivo a voi dopo aver navigato per il web alla ricerca di una risposta,
saro’ breve
non parte piu’ il mio WD mybook da 1 tera,
dopo averlo espulso dalla scrivania (mac osx 10.5.8)
spegnendosi ho provato a farlo partire ma la spia si accendeva solo quando il bottone era premuto, dopodiche ho provato ancora per 2-3 volte a schiacciare il bottone e ho sentito un piccolo scoppiettio, dopo quello non si e’ accesa neanche la luce,quindi penso si sia fuso qualcosa nell’accensione.
domanda:
secondo voi ho perso i dati che avevo nell’hard drive?
vi ringrazio per la pazienza
Martin