|
schufti
|
 |
« on: October 11, 2007, 21:58:44 PM » |
|
Hi, I have rolled a new FW (pls. make sure you have at least a b08 version, as the password for the GUI is handled different in older versions). some of the features: kernel 2.4.35 (inkl. ext3, iso9660, ntfs (r/w)) kernel_nfs (mnt/C autom exported) samba 3.0.14a BusyBox 1.7.2 cifs 1.20c mii-tool (like ethtool) improved Reboot/Halt (with sync, umount) via /sbin/init compatibel with paganoV4 (supporting KamiKaze autobootfs) BEWARE: has to be named autobootfs (long filename) on FAT devices too! (mounted as VFAT) Forgot: if using autobootfs, new kernel needs new module directory. so before using this upgrade, make 2.4.35 as softlink to 2.4.38 in autobootfs ln -s /lib/modules/2.4.28 /lib/modules/2.4.35 via autoexec (/mnt/C/autoexec oder /mnt/USB/USB_C/autoexec) /etc/exports /etc/init.d/rcS /etc/init.d/rc.shutdown /etc/init.d/rc.restart can be modified according your needs. a smb/cifs mount looks like: mount -v -t cifs //server/share /mnt -o user=root,pass=secret,unc=\\\\server\\sharea change to 10Mbit/half duplex needs: mii-tool -F 10baseT-HD eth1I tried to integrate MONO but failed miserably since I couldn't find any docs or UGs on the topic of what to do for getting a runtime only for uclibc based embedded systems. Maybe someone can help? schufti Edit: mke2fs and e2fsck are missing in this release AMIT make broken again ...... New FW with latest components in these threads: latest & last FW for old GUINew Years special for Pearl MGB100Source&Toolchain |
|
|
|
« Last Edit: January 03, 2008, 23:34:21 PM by schufti »
|
Logged
|
I won't answer posts or PMs about repair/recovery after bad flash until proven that the wiki was read and followed! find all my MGB100 files here, pass: mgb100 |
|
|
|
firetwister
|
 |
« Reply #1 on: October 12, 2007, 13:32:39 PM » |
|
Hi Schufti,
nice to see a newer kernel. I'm really fed up of the old 2.4.28 with broken usbserial module (though it can be fixed with the usbserial.c from 2.4.22).
I'm currently backporting the "option" module which handles umts/gprs modems much faster and reliable than the usbserial module. For that it would be helpfull if you can post your kernel config.
Thanks in advance
Firetwister
|
|
|
|
|
Logged
|
|
|
|
|
mightyzen
|
|
« Reply #2 on: October 13, 2007, 08:20:07 AM » |
|
Excellent work!
I'm trying to connect a homebrew microchip 18f4450 USB device using the CDC (Communication Device Class) protocol. I ran into some problems with the current firmware, which may be related to broken usb-serial or acm support.
I want to try the new kernel, but I suppose the acm and probably the usb-serial are not compiled in.
Schufti, could you make available a set of kernel modules for this new kernel? Or could I compile these modules from a 2.4.35 kernel source tree myself?
Thanx
|
|
|
|
|
Logged
|
|
|
|
|
schufti
|
|
« Reply #3 on: October 13, 2007, 08:35:26 AM » |
|
Hi,
ofcourse you can use your own modules, provided you compile them for i486.
schufti
|
|
|
|
|
Logged
|
I won't answer posts or PMs about repair/recovery after bad flash until proven that the wiki was read and followed! find all my MGB100 files here, pass: mgb100 |
|
|
|
mightyzen
|
|
« Reply #4 on: October 13, 2007, 08:56:21 AM » |
|
Ok, I will try to compile them myself. I already have setup the original firmware compilation tree and got that to work on FC4.
So I just copy in the newest 2.4.35.3 kernel tree over the existing one, configure and compile?
Do I need to have the kernel configuration you have used, or can I make my own?
Thanx.
|
|
|
|
|
Logged
|
|
|
|
|
schufti
|
|
« Reply #5 on: October 13, 2007, 12:59:11 PM » |
|
Hi,
if you want to use only the modules, it's ok. If you want to use ther kernel later on, you better get the diffs from 2.4.28 upt o 2.4.35 and apply them accordingly. Lot of changes to interoperate with AMIT binaries. And most important: Emergency exit to recovery-loader.
no, you don't need my kernel .config
schufti
|
|
|
|
|
Logged
|
I won't answer posts or PMs about repair/recovery after bad flash until proven that the wiki was read and followed! find all my MGB100 files here, pass: mgb100 |
|
|
|
firetwister
|
|
« Reply #6 on: October 13, 2007, 20:58:07 PM » |
|
Hi Schufti,
would be great if you could make a patch against 2.4.35 vanilla.
This would avoid reinventing the wheel and having the same sources makes it easier to join efforts.
Firetwister
|
|
|
|
|
Logged
|
|
|
|
|
khe
|
|
« Reply #7 on: October 17, 2007, 18:09:45 PM » |
|
Hi, schufti,
I am current running the upgrade.img (v4). Can I upgrade to your "upgrade.img" (kernel 2.4.35) ?
What is the b8 version you mensioned in your post ?
Thanks,
|
|
|
|
|
Logged
|
|
|
|
|
Fox
|
|
« Reply #8 on: October 17, 2007, 19:20:37 PM » |
|
Uh looks like I did something wrong...
After upgrading to LevelOne b8 I flashed this one, i still had an autobootfs for v4 on the harddisk. However, it seems to be broken or something. Atleast the whole thing (LevelOne WAP-0007) doesnt boot correctly anymore with the harddisk installed. Without harddisk it seems to work.
The problem is that this is the only device accepting this HDD type i own so i wont have the chance to remove the file from it.
Is there any way of temp. disabling the autobootfs?
|
|
|
|
|
Logged
|
|
|
|
|
schufti
|
|
« Reply #9 on: October 17, 2007, 21:53:31 PM » |
|
@firetwister: I'm thinking of uploading the whole kerneltree
@khe: if you are not using usbfs or autobootfs YES, otherwise small changes are necessary
@Fox: can you supply bootlog? are you sure, it's not booting correct? Did you try via cable or only wireless? (in autobootfs you need to have a link from 2.4.35 to old (2.4.28) module directory for WLAN)
remedy: remove hd, reflash upgradev4.img, reinstall hd (make link, try again)
as the next version will have driver for rtc, keys and led I'll try to integrate something to override autobootfs
schufti
|
|
|
|
« Last Edit: October 17, 2007, 22:05:13 PM by schufti »
|
Logged
|
I won't answer posts or PMs about repair/recovery after bad flash until proven that the wiki was read and followed! find all my MGB100 files here, pass: mgb100 |
|
|
|
firetwister
|
|
« Reply #10 on: October 18, 2007, 10:14:06 AM » |
|
Hi Schufti, I revoked my plans to backport the option module, because new drivers aren't wellcome in 2.4 anymore. http://kerneltrap.org/Linux/Backporting_Drivers_to_the_2.4_KernelSo now I'm eager to bring 2.6 on my NAS. > as the next version will have driver for rtc, keys and led I would like to help you with the drivers. I think those busybox hacks should be in the kernel. I don't know how to implement those buttons in a nice way, but RTC and LED should be rather easy in 2.6. There is a driver for the pcf8563 and a gpio-i2c driver, so rtc is hopefully a insmod with the right params  The Led class includes a GPIO led driver, so it would be possible to use /sys/class/leds instead of the proprietary amit tool. What are your plans for 2.6 migration? Do you already have a partial working 2.6 firmware I can play with? I'm afraid of destroying my NAS, because I don't have a JTAG. Firetwister |
|
|
|
|
Logged
|
|
|
|
|
Fox
|
|
« Reply #11 on: October 18, 2007, 20:31:45 PM » |
|
schufti: yeh thats what I did in the end. (Remove HDD, reflash, replug, delete files, upgrade using your image) There wasnt any log made.
Luckily the whole thing is stable now and telnet is working. However either the autoexec is not working or my application is not compatible.
I only compiled my code using "gcc -o xxx xxx.c". It works fine under Fedora 7 - however i tried copying it to an usb device using both: samba and ftp and chmodded it 0777 and i wasnt able to start it via telnet or using autoexec. I can start autoexec using the telnet though, but it gives me an "xxx: not found". If i do "ls" i see autoexec and xxx.
|
|
|
|
|
Logged
|
|
|
|
|
schufti
|
|
« Reply #12 on: October 18, 2007, 21:47:43 PM » |
|
@firetwister: without jtag I wouldn't even fiddle with existing kernel in original source. Just now I managed to "optimize" my toolchain to get a kernel that flashed ok but didn't even send one char to console or go into recoveryloader.
One scenario could be loading RedBoot. Then you could load a kernel and some basic rootfs (initrd) and start it from RedBoot. At least, in this scenario the Bootloader is not depending on a working kernel. But one typo in a flash command and even your RedBoot is beyond repair (as is your MGB100).
@fox: hmmm, now I'm confused. Are you using autobootfs or autoexec? There is no use for autoexec in autobootfs as there should be regular initscripts where you can do "your thing".
pls be more specific about your existing/wanted configuration.
schufti
|
|
|
|
|
Logged
|
I won't answer posts or PMs about repair/recovery after bad flash until proven that the wiki was read and followed! find all my MGB100 files here, pass: mgb100 |
|
|
|
Fox
|
|
« Reply #13 on: October 19, 2007, 15:27:30 PM » |
|
Existing: No autobootfs at all (thats just been a leftover from last time which I removed as said in my last post allready).
Firmware Upgrade history:
1st. LevelOne b8
2nd. Firmware from your post
Wanted: Just have an application I compiled myself on the harddisk or an usb device which is started when the nas boots. (using autoexec I think).
Problem: Using telnet (logged in as root) I can't start the application: "not found" error (although "ls" tells me the file exists and it works fine on Fedora 7), manually starting autoexec using telnet results in "Error in Line 2: Not found" - line 1 is just "#!bin/sh". It doesnt work using autoexec on boot either
Chmod for both (Application / Autoexec) is 0777.
|
|
|
|
« Last Edit: October 19, 2007, 15:45:00 PM by Fox »
|
Logged
|
|
|
|
|
firetwister
|
|
« Reply #14 on: October 19, 2007, 15:44:31 PM » |
|
@Schufti
I'm not brave/curious enough to try my own kernels, not even unmodified ones. Redboot would be an option, but I need to solder a serial connector first. That's why I asked you if you have some partial working 2.6 firmware, so I can do some driver development with modules. Working Ethernet and USB or HD with autobootfs would be enough.
@Fox
File not found errors, which occur on execution usually result from the missing libc. So I assume you linked it against glibC, but only uclibc is on your NAS. Run the "file" or "ldd" utility on the executeable for more Information.
|
|
|
|
|
Logged
|
|
|
|
|
