|
schufti
|
 |
« on: September 27, 2008, 17:59:33 PM » |
|
a new version of my squasfs fw is in the repository.
It has BB 1.12.1, ntfs-3g (rw) and d'ld clients with fake IDs (to get more acceptance).
Don't use "devices information" with ntfs mounted as it will break functionality of USB-Unmount buttons. (a bad bug in AMIT GUI, most probably never to be fixed....)
It's working for me, so if it's not working for you -> try harder.
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 |
|
|
|
Yasen6275
|
|
« Reply #1 on: September 29, 2008, 09:10:12 AM » |
|
Is this fw is suitable for Conceptronic CHD2WLANU?
|
|
|
|
|
Logged
|
|
|
|
|
schufti
|
|
« Reply #2 on: September 29, 2008, 19:52:46 PM » |
|
Hi,
not without an GUI update (see wiki).
You could also search for the thread with the first "c3" upgrade software for details.
|
|
|
|
|
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 |
|
|
|
bpr
|
|
« Reply #3 on: September 30, 2008, 09:26:12 AM » |
|
This is really good, that there's people working on the MGB100... but is it a lot of work for you, to share the sources, too? It would be enough to have only the files you changed from the gpl code on the airlive home page. Or just a description of what you changed, so I can do the changes myself. The reason is this: I would like have sound and keyboard support, but when I compile the modules and try to insmod them, there seems to be basic functionality missing in the kernel. So I would like to be able to compile a kernel of my own and create a firmware with that kernel, that has all the features your firmware has. If you know any other solution to my problem that is less work for you, then go ahead  |
|
|
|
|
Logged
|
|
|
|
|
schufti
|
|
« Reply #4 on: September 30, 2008, 17:08:59 PM » |
|
sources are in the repository (ok, not the latest version, but quite recent)
my toolchain is also in the repository
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 |
|
|
|
bpr
|
|
« Reply #5 on: October 02, 2008, 14:56:05 PM » |
|
Is it possible to build a firmware image with that sources that runs with the new gui?
|
|
|
|
|
Logged
|
|
|
|
|
balans
|
|
« Reply #6 on: October 02, 2008, 15:11:18 PM » |
|
@schufti i placed the image (big fan) ,then let the harddisk be formated automatic it ended with 2 partitions hda1 133mb en the rest hda2 but it mounts hda1 as /mnt/C hda2 as /mnt/C so no swap. checking in telnet fdisk -l gives me that /hda1 is indeed created as swap # fdisk -l
Disk /dev/hda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 1 17 136521 82 Linux swap / Solaris
/dev/hda2 * 18 9729 78011640 83 Linux
# free
total used free shared buffers
Mem: 30020 17856 12164 0 284
Swap: 0 0 0
Total: 30020 17856 12164
# # mount
rootfs on / type rootfs (rw)
/dev/root on / type ext2 (rw)
none on /proc type proc (rw)
/dev/hda1 on /mnt/C type ext2 (rw,noatime)
/dev/hda2 on /mnt/D type ext2 (rw,noatime)
/dev/root on /var/share/USB type ext2 (rw)
/dev/hda1 on /var/share/C type ext2 (rw,noatime)
/dev/hda2 on /var/share/D type ext2 (rw,noatime)
# help  |
|
|
|
|
Logged
|
|
|
|
|
schufti
|
|
« Reply #7 on: October 02, 2008, 18:43:13 PM » |
|
Hi,
@balans:
interesting, I have to look into this problem, but can't give a timeframe.
When I started developing, I only had a 40MB HD. Then some kind soul donated a 12 GB Hitachi, unforunately it broke down recently (needs long time to finish any task, often can't format,....)
can you manualy enable swap (swapon /dev/hda1)?
I think I configured it to have hda4 as swap, so maybe I forgot to patch fdisk (does the automatic creation of swap)
@bpr:
ooops, when recreating the repository, I forgot to link the c3 source packet. now it is deletd from RS and I have to reupload, will take some time ...
schufti
|
|
|
|
« Last Edit: October 02, 2008, 18:45:14 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 |
|
|
|
balans
|
|
« Reply #8 on: October 02, 2008, 20:24:18 PM » |
|
# umount /dev/hda1
# mount
rootfs on / type rootfs (rw)
/dev/root on / type ext2 (rw)
none on /proc type proc (rw)
/dev/hda2 on /mnt/D type ext2 (rw,noatime)
/dev/root on /var/share/USB type ext2 (rw)
/dev/hda2 on /var/share/D type ext2 (rw,noatime)
# swapon /dev/hda1
swapon: /dev/hda1: Invalid argument
#
no problem ill wait patiencely  |
|
|
|
|
Logged
|
|
|
|
|
schufti
|
|
« Reply #9 on: October 08, 2008, 09:15:45 AM » |
|
Hi,
@balans: I checked with a blank hd and if I chose "basic" in the hd-menu, I get everything done as expected: /dev/hda4 is a 128MB swap, /dev/hda1 with the rest. Maybe you partitioned your hd with an older version of the fw?
@bpr: the sources are now in the repository. Copy both archives (source and toolchain) to your (compatible) linux system, decompress and compile with:
tar -xzf myMGBtc.tgz -C /opt
tar -xjf myMGBc3.tar.bz2 -C /usr/src
cd /usr/src/myMGB
make linuxall
after some time you should see
"Make F/W successfully! check the file : ./upgrade.img"
btw. it allways says that, even if the fw will brick your box!
I checked the result and it is working fw, so: if you break it, you fix it.
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 |
|
|
|
balans
|
|
« Reply #10 on: October 08, 2008, 12:33:56 PM » |
|
Ok i upgraded from an older version i`ll try later , and post the result
mvg,
Barry
|
|
|
|
|
Logged
|
|
|
|
|
balans
|
|
« Reply #11 on: October 08, 2008, 19:58:08 PM » |
|
got it working i was problably running with a wrong version i reflashed all and then this was the result BusyBox v1.11.2 (2008-09-26 13:08:09 CEST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
# free
total used free shared buffers
Mem: 30352 12340 18012 0 1708
Swap: 131504 0 131504
Total: 161856 12340 149516
# mount
rootfs on / type rootfs (rw)
/dev/root on / type squashfs (ro)
none on /proc type proc (rw)
tmpfs on /tmp type tmpfs (rw)
/dev/hda1 on /tmp/mnt/C type ext2 (rw,noatime)
/dev/hda1 on /tmp/share/C type ext2 (rw,noatime)
tmpfs on /tmp/share/USB type tmpfs (rw)
# fdisk -l
Disk /dev/hda: 80.0 GB, 80026361856 bytes
16 heads, 63 sectors/track, 155061 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 262 155061 78019200 83 Linux
/dev/hda4 1 261 131512+ 82 Linux swap / Solaris
Partition table entries are not in disk order
me happy , thx shufti nice work ... again |
|
|
|
|
Logged
|
|
|
|
|
bpr
|
|
« Reply #12 on: October 16, 2008, 11:12:41 AM » |
|
Hi Schufti, thank for the sources! That's really cool  Is there anything I check on a firmware file before flashing it? I know the only way to be sure is to flash it and see if it works. But maybe you know the common problems with failing firmwares (esp. when they trash the recovery boot loader, so one needs a JTAG to recover). I'm asking because I don't have a JTAG and I only want to get one if (and when) I need it. |
|
|
|
|
Logged
|
|
|
|
|
schufti
|
|
« Reply #13 on: October 17, 2008, 18:22:23 PM » |
|
hi,
if you didn't mess with the kernel config, chances are very good (>99,9%). you can compare the first 0d00h bytes wih my reference image (the address_header, kernel loader plus jump to rec-loader). Check kernel size, it shouldnt grow bigger than 1MB-16 bytes!
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 |
|
|
|
lotus01
|
 |
« Reply #14 on: October 20, 2008, 14:04:29 PM » |
|
Hi,
This is my first post and I would like to thank all you folks for your work and information. I would like some advice on how to proceed. I have read the WIKI several times and have based understanding of unix commands. A recently purchased a SMCWAPS-G and flashed it to the newest SMC firmware (SMCWAPS-G Firmware v.4.00c2_0130). I also have an external 500GB HD (NTFS formatted) attached to it. I would like to modify change my present FW to WMU-6000FS Firmware c3 and upgrade to MGB100_v4c3sq_080926 to take advantage of the BT Client and NTFS rw capabilities of this upgrade. Here is my understanding of what I need to do for this to work.
1. Downgrade my SMCWAPS-G from 4.00c2_0130 to SMC FW R400b5v4.
2. Rebrand my SMCWAPS-G to an Airlive WMU-6000FS by changing the header of the WMU-6000FS FW V.400b6 to the header of the SMC FW R400b5v4, then flash.
3. Flash from WMU-6000FS FW V.400b6 (modified header) to WMU-6000FS FW c3 (modified header).
4. Flash upgrade the WMU-6000FS FW c3 (modified header) to schufti’s MGB100_v4c3sq_080926.
Is this correct?
Can I use the web gui for flashing or do I have to use the recoveryloader?
Any suggestion would be appreciated
Thanks
Lotus
|
|
|
|
|
Logged
|
|
|
|
|
