DSM-G600, DNS-3xx and NSA-220 Hack Forum

jcard · 2010-09-23 01:07:03

What's new:

-kernel 2.6.35.4
-owners of A1 hardware boards should try this.
-no lzma squashfs backported patch, as it turns the kernel
unstable; as a result there are less 11MB of RAM available :-(
-sftp and ftps support
-ftp administering web page (AWP)
-wget proxy AWP (untested)
-disk wizard AWP
-disk maintenance AWP redesigned, more disk/raid operations supported
-disk partitioning AWP bugs fixed
-remote web administration AWP (untested)
-redesigned side menu and added drop-down menus on AWP
-SMART AWP
-Board revision level detection
-several other fixes and improvements.

Known Issues:

-Rev-A1 (try it an report) and rev-C1 hardware boards not yet supported

-network link auto-negotiation doesn't work. As result Alt-F
only works when the box is connected to Gbit switches/routers
or network cards. 100/10Mbps switch or routers won't work.

-ghostscrip/hplip can fail with an "Unable to get scanline 0/1" error,
and cups does not noticies it, sending the print job to the printer,
which prints a black page, wasting all your cartridge ink.
After configure the printer in cups, DISCONECT THE PRINTER and print
a test page. If in the State column of cups jobs web page, or using
"lpstat -p" you see a "Unable to get scanline 0/1" message,
CANCEL THE PRINT JOB AND DON'T USE THAT PRINT CONFIGURATION.

http://sites.google.com/site/altfirmware/
http://code.google.com/p/alt-f/
http://groups.google.com/group/alt-f

Enjoy

KRH · 2010-09-26 13:15:57

I have the same problem with the SATA Disk as with B1

jcard · 2010-09-27 05:16:49

KRH wrote:
I have the same problem with the SATA Disk as with B1

I though that according to this thread the A1 hardware issue was solved... damn

KRH · 2010-09-27 08:17:19

This post shows the same errors as i get.

http://groups.google.com/group/alt-f/po … 94%3F&

jcard · 2010-10-08 02:57:11

On another thread, mushanga said:

Hi Jcard,

good news!

Any chance that this "no CONFIG_MARVELL_PHY" Alt-f version could be reloaded (in ffp terms) on a C1 rev. to work on 100Mb?

Because if I've understood correctly the C1 and B1 have the same network hardware.

Could you share this Alt-f version please?

Sure: http://dl.dropbox.com/u/1555717/DNS-323 … index.html

To use it you must have ffp.
Download 0.1B4.tar to the box root directory, extract it, replace alt-f/zImage with the one you will find using the link above, then run whatever name you called to Alt-F fun_plug.

But be warned, rev-C1 has different pins assigned to leds and buttons, and a different fan controller -- you will have no fan and the leds might become crazy.

The safe way to test only the network is to edit Alt-F fun_plug, and replace the line that says

cmdline="console=ttyS0,115200"

with

cmdline="initdbg console=ttyS0,115200"

With this change "init" only launches inetd, and you can telnet the box, having a reduced environment.

linux-2.6.36 has support for rev-C1, and will be released within a couple of weeks.
I hope 0.1B5 to have support for rev-C1, I count on you :-)

Joao

jcard · 2010-10-08 03:03:22

KRH wrote:
This post shows the same errors as i get.

http://groups.google.com/group/alt-f/po … 94%3F&

Yes, I know.

It was Philster76 reports that convinced me that the problem was solved, but he gave-up and I never got a definitive answer.

If you want to takeover his "job", I will be glad to release experimental kernels for you (or anybody else with a rev-A1 board) to test. But it is a boring task...

KRH · 2010-10-08 08:09:25

jcard wrote:
If you want to takeover his "job", I will be glad to release experimental kernels for you (or anybody else with a rev-A1 board) to test. But it is a boring task...

Sure im ready

mushanga · 2010-10-10 13:08:21

jcard wrote:
Sure: http://dl.dropbox.com/u/1555717/DNS-323 … index.html

To use it you must have ffp.
Download 0.1B4.tar to the box root directory, extract it, replace alt-f/zImage with the one you will find using the link above, then run whatever name you called to Alt-F fun_plug.

But be warned, rev-C1 has different pins assigned to leds and buttons, and a different fan controller -- you will have no fan and the leds might become crazy.

The safe way to test only the network is to edit Alt-F fun_plug, and replace the line that says

cmdline="console=ttyS0,115200"

with

cmdline="initdbg console=ttyS0,115200"

With this change "init" only launches inetd, and you can telnet the box, having a reduced environment.

linux-2.6.36 has support for rev-C1, and will be released within a couple of weeks.
I hope 0.1B5 to have support for rev-C1, I count on you :-)

Joao

GREAT! it works! 100Mb full Alt-f reloaded under ffp with firmare 1.09

Code:

# uname -a
Linux Tiromancino.workgroup 2.6.35.4 #1 Thu Oct 7 22:51:58 WEST 2010 armv5tel GNU/Linux
# ethtool eth0
Settings for eth0:
        Supported ports: [ TP AUI BNC MII FIBRE ]
        Supported link modes:   10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
                                1000baseT/Full 
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
                                1000baseT/Full 
        Advertised pause frame use: No
        Advertised auto-negotiation: Yes
        Speed: 100Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 8
        Transceiver: external
        Auto-negotiation: on
        Link detected: yes
#

2 "strange" things though:

1) your cmdline="initdbg console=ttyS0,115200" worked first time but I had to use cmdline="nodef console=ttyS0,115200" to start the "full" alt-f.
I did not tried to save setting yet, can I do so without breaking anything (i.e. the flashed 1.09 firm)?

2) My rev. C1 is identified as "B1" in /tmp/board and the whole hardware seems to be recognized and functional (fan, temp. sensor, leds, front button...)
Do I have a B1 in disguise (my serial # and sticker on the box both tell C1) or does the C1 is already fully supported in 2.6.35.4?

And last thing does this mean I can flash alt-f now? (reminder: I don't have serial connexion)

Thanks again, can't wait for B5

jcard · 2010-10-10 18:12:50

mushanga wrote:
jcard wrote:
Sure: http://dl.dropbox.com/u/1555717/DNS-323 … index.html

To use it you must have ffp.
Download 0.1B4.tar to the box root directory, extract it, replace alt-f/zImage with the one you will find using the link above, then run whatever name you called to Alt-F fun_plug.

But be warned, rev-C1 has different pins assigned to leds and buttons, and a different fan controller -- you will have no fan and the leds might become crazy.

The safe way to test only the network is to edit Alt-F fun_plug, and replace the line that says

cmdline="console=ttyS0,115200"

with

cmdline="initdbg console=ttyS0,115200"

With this change "init" only launches inetd, and you can telnet the box, having a reduced environment.

linux-2.6.36 has support for rev-C1, and will be released within a couple of weeks.
I hope 0.1B5 to have support for rev-C1, I count on you :-)

Joao
GREAT! it works! 100Mb full Alt-f reloaded under ffp with firmare 1.09

Excelent!

2 "strange" things though:

1) your cmdline="initdbg console=ttyS0,115200" worked first time but I had to use cmdline="nodef console=ttyS0,115200" to start the "full" alt-f.

The initdbg thing was intended to keep you in a restricted environment, only with telnet.
If Alt-F works in your box you can remove the initdbg and/or nodef from the kernel command line.

"nodef" only avoids Alt-F to load any flashed settings on boot -- as you have not yet saved none it makes no difference.

2) My rev. C1 is identified as "B1" in /tmp/board and the whole hardware seems to be recognized and functional (fan, temp. sensor, leds, front button...)
Do I have a B1 in disguise (my serial # and sticker on the box both tell C1) or does the C1 is already fully supported in 2.6.35.4?

According to Benjamin Herrenschmid, in ports.arm.kernel (search for "DNS323 rev C1 fan support"), the differences between a B1 and a C1 boards are the phy (C1 uses a marvel 1118) and the fan controller, there is a new one on rev C1.

To detect the board it is running on, Alt-F looks for the processor type, which distinguish between A1 and the others, and for the fan controller, wich distinguish between B1 and C1.

The only way to say for sure is for you to open the box and look at the printed circuit board, its should be clearly printed which version you have.

But if the fan is running fine...
Execute "logread | grep sysctrl" and you will find fan/temperature logs.

Also, in /tmp you will find, among other files, fan_speed and system_temp, which you can read to see the current fan speed and system temperature.

Also, try:

Code:

find /sys -name pwm1

if the command reports
/sys/devices/platform/mv64xxx_i2c.0/i2c-0/0-003e/pwm1

and if the command

Code:

find /sys/ -name g760a

reports /sys/bus/i2c/drivers/g760a

than you almost certainly have a B1 (or Benjamin Herrenschmid is wrong)

Then you can try the following:

Code:

echo 200 > /sys/devices/platform/mv64xxx_i2c.0/i2c-0/0-003e/pwm1 # high speed fan, you should ear it
cat /sys/devices/platform/mv64xxx_i2c.0/i2c-0/0-003e/fan1_input # reports current fan sped

wait a little,

Code:

echo 0 > /sys/devices/platform/mv64xxx_i2c.0/i2c-0/0-003e/pwm1 # stops fan
cat /sys/devices/platform/mv64xxx_i2c.0/i2c-0/0-003e/fan1_input # reports current fan sped

But the best is for you to post the "alt-f.log" file that you can find in the root of every filesystem.
Can you do that, please?
Or at least the "dmesg" output from the very beginning?
And also the output of "cat /proc/cpuinfo"?

I did not tried to save setting yet, can I do so without breaking anything (i.e. the flashed 1.09 firm)?

Yes you can save settings.
Alt-F and the vendor's default files can coexist. Just don't "clear settings" -- that erases the vendor's firmware settings file (nothing very dramatic, I think that pressing the back-button for more than 20 seconds when using the vendor's firmware has the same effect.

Saving settings is not the same as flashing the kernel or initramfs. They live in separate flash partitions. The vendor's firmware even duplicates the settings in two separate flash partitions.

And last thing does this mean I can flash alt-f now? (reminder: I don't have serial connexion)

I can't advise you on that, you have to "measure" the benefits and risks.

Last edited by jcard (2010-10-10 18:22:13)

jcard · 2010-10-10 19:57:20

KRH wrote:
jcard wrote:
If you want to takeover his "job", I will be glad to release experimental kernels for you (or anybody else with a rev-A1 board) to test. But it is a boring task...
Sure im ready

OK then.

I would like to first establish a reference point; after that we can start testing different kernels.

I apologize if the instructions bellow are too detailed, I don't know your level of expertise.
Being very detailed allows other less experienced persons to also try them.

You must have ffp.
Do you have a serial-port connection? I will assume you don't have one.

A)
1-Download Alt-F-0.1B4.tar to the box (*)
2-Download Alt-F fun_plug to the box (*) , saving it under the name alt-f.sh
3-Make the alt-f.sh file executable by using the command "chmod +x alt-f.sh"
4-Extract Alt-F-0.1B4.tar by executing the command "tar xvf Alt-F-0.1B4.tar"

A directory named alt-f/ will appear with the contents
alt-f/reloaded-2.6.12.6-arm1-fonz.ko
alt-f/rootfs.arm.cpio.lzma
alt-f/README.USE
alt-f/zImage
alt-f/reloaded-2.6.6-arm2.ko
alt-f/reloaded-2.6.12.6-arm1.ko
alt-f/README.INSTALL

5-edit alt-f.sh, replacing line 62 who says
cmdline="console=ttyS0,115200"
with
cmdline="initdbg console=ttyS0,115200"

6-execute alt-f.sh by running the command "./alt-f.sh"
7-you will be ckicked off, and after a minute or so, start pinging the box.
8-telnet the box and login as "root", no password is asked

If you can't telnet and login, please review the steps above.

If you can telnet, you will be in a restricted environment, Alt-F will not try to touch or mount any of your disks.

9-run the command "dmsg".
Does it shows lots of errors? Its expected, we are just making sure that you can telnet the box.
10-Power off the box by pulling the box power-cord.
The "reboot" or "poweroff" commands will not work.

Now lets start testing a new kernel. You will have to do this for every new kernel you want to test.
You don't have to repeat all the A) steps above, only the indicated:

(*) /mnt/HD_a2, isn't it? I don't use the stock firmware for a while

B)
1-repeat A-3 above (every time alt-f.sh runs it removes itself the capability of running again)
2-Download from http://dl.dropbox.com/u/1555717/DNS-323 … index.html
the zImage-A1-testing-3.1 file, and put it in the alt-f directory under the name zImage.
It should replace the original zImage file.
3-execute A-6, A-7, A-8 and A-9 steps. Does the same "dmesg" errors appear? execute A-10 and
please report and wait for me to post a new testing kernel.
4-No dmesg errors? Try mounting one partition, e.g.
mkdir -p /mnt/sda2
mount /dev/sda2 /mnt/sda2
ls /mnt/sda2
does your files appear in the listing? Good, execute
umount /mnt/sda2

5-execute A-10

Hope that there are no typos...

Thanks,
Joao

mushanga · 2010-10-10 21:30:03

jcard wrote:
But the best is for you to post the "alt-f.log" file that you can find in the root of every filesystem.
Can you do that, please?
Or at least the "dmesg" output from the very beginning?
And also the output of "cat /proc/cpuinfo"?

Well... seems I'm an idiot.
I just check the sticker with the serial number and it says "B1"
Plus all the commands you told say the same thing:

Code:

# logread | grep sysctrl
Oct 10 09:45:04 Tiromancino daemon.info sysctrl: temp=41.3       fan=2445
Oct 10 11:55:28 Tiromancino daemon.info sysctrl: temp=41.7       fan=2386

# find /sys -name pwm1
/sys/devices/platform/mv64xxx_i2c.0/i2c-0/0-003e/pwm1

# find /sys/ -name g760a
/sys/bus/i2c/drivers/g760a

# cat /sys/devices/platform/mv64xxx_i2c.0/i2c-0/0-003e/fan1_input
2457

I attach the alt-f.log anyway, it will be one more for your archives

I did not tried to save setting yet, can I do so without breaking anything (i.e. the flashed 1.09 firm)?
Yes you can save settings.
Alt-F and the vendor's default files can coexist. Just don't "clear settings" -- that erases the vendor's firmware settings file (nothing very dramatic, I think that pressing the back-button for more than 20 seconds when using the vendor's firmware has the same effect.

Saving settings is not the same as flashing the kernel or initramfs. They live in separate flash partitions. The vendor's firmware even duplicates the settings in two separate flash partitions.

Thanks for the confirmation, I'll save my settings.

And last thing does this mean I can flash alt-f now? (reminder: I don't have serial connexion)
I can't advise you on that, you have to "measure" the benefits and risks.

Now I'm sure to have a B1, can I flash Alt-F or the risk is too hight anyway without serial connexion?

I will continue to be a proud an happy beta tester of yours

Attachments:

alt-f.log, Size: 26,651 bytes, Downloads: 577

jcard · 2010-10-11 03:06:19

mushanga wrote:
And last thing does this mean I can flash alt-f now? (reminder: I don't have serial connexion)
I can't advise you on that, you have to "measure" the benefits and risks.
Now I'm sure to have a B1, can I flash Alt-F or the risk is too hight anyway without serial connexion?

I don't think it to be more risky than upgrading the vendor's firmware. But I don't have a Q&A team behind me, here we live in the bleeding edge.

But you can't do it yet, as you don't have a 100mbps capable Alt-F firmware file.
Unless you want to do it "manually", look at /usr/www/cgi-bin/firmware2_proc.cgi if you dare, or if you want to create a firmware file by using the included dns323-fw:

Code:

# dns323-fw 
Split a vendor firmware file into its components:
        dns323-fw -s [-q (quiet)] [-k kernel_file] [-i initramfs_file]
        [-d defaults_file] firmware_file
Merge a kernel and initramfs into a firmware compatible vendor firmware file:
        dns323-fw -m [-q (quiet)] -k kernel_file -i initramfs_file 
        [-d defaults_file] [-p product_id]  [-c custom_id] [-l model_id ]
        [-u sub_id] [-v new_version] firmware_file

As an apart: I have setup two more kernels for A1 and C1 testing at the usual place:

http://dl.dropbox.com/u/1555717/DNS-323 … index.html

Anybody with a A1 or C1 board, please try them using the procedure outlined in a previous post, and please report back success or unsuccess.

Last edited by jcard (2010-10-11 03:24:16)

KRH · 2010-10-11 21:06:28

jcard wrote:
I would like to first establish a reference point; after that we can start testing different kernels.

You must have ffp.
Do you have a serial-port connection? I will assume you don't have one.

[snip]
ls /mnt/sda2
does your files appear in the listing? Good, execute
umount /mnt/sda2

5-execute A-10

Hope that there are no typos...

Thanks,
Joao

im quite technial as i where the first to compile programs on the dns-323

and yes i have seriel connection

and for all the steps it ended up whit mounting the sda2 so can you please make a image that i can flash whit

/dev/sda2 915.9G 874.5G 41.4G 95% /mnt/sda2

and i need more disk space

jcard · 2010-10-12 03:47:06

KRH wrote:
jcard wrote:
[snip]
ls /mnt/sda2
does your files appear in the listing? Good, execute
umount /mnt/sda2

5-execute A-10

Joao
im quite technial as i where the first to compile programs on the dns-323

and yes i have seriel connection

and for all the steps it ended up whit mounting the sda2 so can you please make a image that i can flash whit

Good. But not so fast

I have to still strip the kernel configuration a bit more, to know what exactly is causing the problem in the standard Alt-F kernel configuration.
You know, flash space is at a premium on the DNS323, one has to remove all unneeded bits to make space available for desirable features.

A new experimental kernel is available at the same place: zImage-A1-testing-4. Can you please test it also?

If you reach so far as to mount your disks, with any of the experimental kernels, you can try to give Alt-F a chance by removing "initdbg" from the command line. But do this only after you know that the disks are mountable!

Thanks

jcard · 2010-10-13 20:35:46

jcard wrote:
I have to still strip the kernel configuration a bit more, to know what exactly is causing the problem in the standard Alt-F kernel configuration.
You know, flash space is at a premium on the DNS323, one has to remove all unneeded bits to make space available for desirable features.
Thanks

I have also included in
http://dl.dropbox.com/u/1555717/DNS-323 … index.html
a README.txt and some further kernels, namely for testing C1 boards.

I would like to release 0.1B5 within a week, with at least partial support for A1 and C1 boards.
Testers needed

Last edited by jcard (2010-10-13 20:37:44)

KRH · 2010-10-13 20:53:01

i tested A1-4 and it works fine, i just gets out of memory when trying to run e2fsck (with ON initdbg)

KRH · 2010-10-13 21:20:48

when booting whitout initdbg this is the log
Orion ID: MV88F5181-Rev-B1. TCLK=166666667.
------------[ cut here ]------------
WARNING: at /home/jcard/tmp/linux-2.6.34/drivers/gpio/gpiolib.c:103 0xc0131294()
autorequest GPIO-4
Modules linked in:
Function entered at [<c002cc58>] from [<c0037b78>]
Function entered at [<c0037b78>] from [<c0037be8>]
Function entered at [<c0037be8>] from [<c0131294>]
Function entered at [<c0131294>] from [<c013138c>]
Function entered at [<c013138c>] from [<c000e8d4>]
Function entered at [<c000e8d4>] from [<c000aac0>]
Function entered at [<c000aac0>] from [<c002633c>]
Function entered at [<c002633c>] from [<c0008410>]
Function entered at [<c0008410>] from [<c0027e94>]
---[ end trace 1b75b31a2719ed1c ]---
DNS323: Found ethernet MAC address: 00:19:5b:72:a7:74.
jc: orion5x_pci_sys_setup: nr=0 orion5x_pci_disabled=0
Applying Orion-1/Orion-NAS PCIe config read transaction workaround
PCI: bus0: Fast back to back transfers disabled
jc: orion5x_pci_sys_setup: nr=1 orion5x_pci_disabled=0
PCI: bus1: Fast back to back transfers enabled
pci 0000:00:01.0: BAR 0: assigned [mem 0xe0000000-0xe00fffff 64bit]
pci 0000:00:01.0: BAR 0: set to [mem 0xe0000000-0xe00fffff 64bit] (PCI address [0xe0000000-0xe00fffff]
pci 0000:00:01.0: BAR 2: assigned [io 0x1000-0x10ff]
pci 0000:00:01.0: BAR 2: set to [io 0x1000-0x10ff] (PCI address [0x1000-0x10ff]
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Switching to clocksource orion_clocksource
Switched to NOHz mode on CPU #0
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
Unpacking initramfs...
Freeing initrd memory: 5600K
squashfs: version 4.0 (2009/01/31) Phillip Lougher
msgmni has been set to 120
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 3) is a 16550A
console [ttyS0] enabled
loop: module loaded
sata_mv 0000:00:01.0: version 1.28
sata_mv 0000:00:01.0: Gen-IIE 32 slots 4 ports SCSI mode IRQ via INTx
scsi0 : sata_mv
scsi1 : sata_mv
scsi2 : sata_mv
scsi3 : sata_mv
ata1: SATA max UDMA/133 mmio m1048576@0xe0000000 port 0xe0022000 irq 11
ata2: SATA max UDMA/133 mmio m1048576@0xe0000000 port 0xe0024000 irq 11
ata3: SATA max UDMA/133 mmio m1048576@0xe0000000 port 0xe0026000 irq 11
ata4: SATA max UDMA/133 mmio m1048576@0xe0000000 port 0xe0028000 irq 11
physmap platform flash device: 00800000 at f4000000
physmap-flash.0: Found 1 x16 devices at 0x0 in 8-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
number of CFI chips: 1
cmdlinepart partition parsing not available
RedBoot partition parsing not available
Using physmap partition information
Creating 5 MTD partitions on "physmap-flash.0":
0x000000000000-0x000000010000 : "MTD1"
0x000000010000-0x000000020000 : "MTD2"
0x000000020000-0x0000001a0000 : "Linux Kernel"
0x0000001a0000-0x0000007d0000 : "File System"
0x0000007d0000-0x000000800000 : "u-boot"
MV-643xx 10/100/1000 ethernet driver version 1.4
mv643xx_eth smi: probed
net eth0: port 0 with MAC address 00:19:5b:72:a7:74
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
orion-ehci orion-ehci.0: Marvell Orion EHCI
orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
orion-ehci orion-ehci.0: irq 17, io mem 0xf1050000
orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
input: gpio-keys as /class/input/input0
i2c /dev entries driver
rtc-m41t80 0-0068: chip found, driver version 0.05
rtc-m41t80 0-0068: rtc core: registered m41t80 as rtc0
lm75 0-0048: hwmon1: sensor 'lm75'
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
TCP cubic registered
NET: Registered protocol family 17
rtc-m41t80 0-0068: setting system clock to 2010-10-13 10:06:33 UTC (1286964393)
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: ATA-8: WDC WD10EACS-00D6B1, 01.01A01, max UDMA/133
ata1.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access ATA WDC WD10EACS-00D 01.0 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
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 sda4
sd 0:0:0:0: [sda] Attached SCSI disk
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: ATA-8: WDC WD10EACS-00D6B1, 01.01A01, max UDMA/133
ata2.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata2.00: configured for UDMA/133
scsi 1:0:0:0: Direct-Access ATA WDC WD10EACS-00D 01.0 PQ: 0 ANSI: 5
sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdb: sdb1 sdb2 sdb4
sd 1:0:0:0: [sdb] Attached SCSI disk
IP-Config: Complete:
device=eth0, addr=192.168.0.252, mask=255.255.255.0, gw=192.168.0.1,
host=NAS, domain=, nis-domain=workgroup,
bootserver=255.255.255.255, rootserver=255.255.255.255, rootpath=
ata3: SATA link down (SStatus 0 SControl 300)
ata4: SATA link down (SStatus 0 SControl 300)
Freeing init memory: 120K
pre-init started, pid=1
pre-init: noaufs
init started: BusyBox v1.15.3 (2010-09-14 15:01:48 WEST)
eth0: link up, 1000 Mb/s, full duplex, flow control disabled
Adding 530108k swap on /dev/sda1. Priority:1 extents:1 across:530108k

and then budt the console do not work and there are no telnet

jcard · 2010-10-14 00:09:20

KRH wrote:
i tested A1-4 and it works fine,

Good. A1-5 is at the usual place for testing.

i just gets out of memory when trying to run e2fsck (with ON initdbg)

In the initdbg environment swap is not activated, and fsck needs more memory in order to check big filesystems. Try:

swapon -p1 /dev/sda1

and if you have two disks also

swapon -p1 /dev/sdb1

Then try to run fsck and tell us if it worked. Run it with "-n" (do nothing, just verify), just to be in the safe side.

fsck -fnv /dev/sda2

For now I will disregard your report when running without initdbg, as the kernel has not all needed functionality. It was my fault to tell you to try it without initdbg.

Thanks

Last edited by jcard (2010-10-14 00:13:36)

DSM-G600, DNS-3xx and NSA-220 Hack Forum

Announcement

#1 2010-09-23 01:07:03

Alt-F-0.1B4 has been released

#2 2010-09-26 13:15:57

Re: Alt-F-0.1B4 has been released

#3 2010-09-27 05:16:49

Re: Alt-F-0.1B4 has been released

KRH wrote:

#4 2010-09-27 08:17:19

Re: Alt-F-0.1B4 has been released

#5 2010-10-08 02:57:11

Re: Alt-F-0.1B4 has been released

#6 2010-10-08 03:03:22

Re: Alt-F-0.1B4 has been released

KRH wrote:

#7 2010-10-08 08:09:25

Re: Alt-F-0.1B4 has been released

jcard wrote:

#8 2010-10-10 13:08:21

Re: Alt-F-0.1B4 has been released

jcard wrote:

Code:

#9 2010-10-10 18:12:50

Re: Alt-F-0.1B4 has been released

mushanga wrote:

jcard wrote:

Code:

Code:

Code:

Code:

#10 2010-10-10 19:57:20

Re: Alt-F-0.1B4 has been released

KRH wrote:

jcard wrote:

#11 2010-10-10 21:30:03

Re: Alt-F-0.1B4 has been released

jcard wrote:

Code:

#12 2010-10-11 03:06:19

Re: Alt-F-0.1B4 has been released

mushanga wrote:

Code:

#13 2010-10-11 21:06:28

Re: Alt-F-0.1B4 has been released

jcard wrote:

#14 2010-10-12 03:47:06

Re: Alt-F-0.1B4 has been released

KRH wrote:

jcard wrote:

#15 2010-10-13 20:35:46

Re: Alt-F-0.1B4 has been released

jcard wrote:

#16 2010-10-13 20:53:01

Re: Alt-F-0.1B4 has been released

#17 2010-10-13 21:20:48

Re: Alt-F-0.1B4 has been released

#18 2010-10-14 00:09:20

Re: Alt-F-0.1B4 has been released

KRH wrote:

Board footer