hoofdpijn
Newbie
Posts: 15
|
 |
« Reply #15 on: June 21, 2009, 02:56:32 pm » |
|
It sounds like pfft and I have the same hardware then. It's good to not be alone.  As requested: ~ $ cat /proc/mtd dev: size erasesize name mtd0: 00080000 00020000 "NAND-boot" mtd1: 00040000 00020000 "bootloader" mtd2: 00020000 00020000 "u-env" mtd3: 00180000 00020000 "kernel" mtd4: 00d20000 00020000 "cramfs" mtd5: 00100000 00020000 "jffs2" mtd6: 06d80000 00020000 "yaffs" The dmesg output doesn't look very helpful in the context of storage. ~ $ dmesg | grep -i ide | head tl:413> IENCODE(KM): Video QueueAddr=0x03C4A000 Size=4194304. IOSD(KM): iosd_set_video_display: window:0, dimensions:720x240 IOSD(KM): set_video_position: win:0, left:0, top:0, right:719, bottom:239 iencode_ioctl:413> IENCODE(KM): Video QueueAddr=0x03C4A000 Size=4194304. IOSD(KM): iosd_set_video_display: window:0, dimensions:720x240 IOSD(KM): set_video_position: win:0, left:0, top:0, right:719, bottom:239 iencode_ioctl:413> IENCODE(KM): Video QueueAddr=0x03C4A000 Size=4194304. |
|
|
|
|
Logged
|
|
|
|
bigshew
Newbie
Posts: 23
|
|
« Reply #16 on: June 22, 2009, 12:35:31 am » |
|
BMC,
Yes, my OSD, which is running OSDng, has a CF slot and came with the CF card. I beleive it came with a note that said something like "for future expansion."
|
|
|
|
|
Logged
|
|
|
|
|
pfft2001
|
|
« Reply #17 on: June 22, 2009, 04:18:29 am » |
|
~ $ cat /proc/mtd
dev: size erasesize name
mtd0: 00080000 00020000 "NAND-boot"
mtd1: 00040000 00020000 "bootloader"
mtd2: 00020000 00020000 "u-env"
mtd3: 00180000 00020000 "kernel"
mtd4: 00d20000 00020000 "cramfs"
mtd5: 00100000 00020000 "jffs2"
mtd6: 06d80000 00020000 "yaffs"
~ $ dmesg | grep -i ide | head
IOSD(KM): iosd_set_video_display: window:0, dimensions:720x240
IOSD(KM): set_video_position: win:0, left:0, top:0, right:719, bottom:239
iencode_ioctl:413> IENCODE(KM): Video QueueAddr=0x03C4A000 Size=4194304.
IOSD(KM): iosd_set_video_display: window:0, dimensions:720x240
IOSD(KM): set_video_position: win:0, left:0, top:0, right:719, bottom:239
iencode_ioctl:413> IENCODE(KM): Video QueueAddr=0x03C4A000 Size=4194304.
~ $
|
|
|
|
|
Logged
|
|
|
|
|
greyback
|
|
« Reply #18 on: June 22, 2009, 10:47:52 am » |
|
I'm with Chad, I thought there are only two OSD models, the 1.0 with 16MB NOR flash and CF card slot, and the 1.15 model with 128MB NAND flash with no CF card slot.
pfft2001's machine confuses me!
-G
|
|
|
|
|
Logged
|
|
|
|
hoofdpijn
Newbie
Posts: 15
|
|
« Reply #19 on: June 22, 2009, 01:36:28 pm » |
|
Do we want to see a picture?
|
|
|
|
|
Logged
|
|
|
|
|
pfft2001
|
|
« Reply #20 on: June 23, 2009, 04:53:18 am » |
|
I'm with Chad, I thought there are only two OSD models, the 1.0 with 16MB NOR flash and CF card slot, and the 1.15 model with 128MB NAND flash with no CF card slot.
pfft2001's machine confuses me!
-G
Actually, now that I think about it, I may be confusing CF with SD (*). My machines have SD slots. Does that mean that the original model had both CF & SD slots (i.e., two slots)? -------------------------- (*) Or, more accurately, I assumed that people here were using "mushy terminology". Now, I am guessing that that is not the case. |
|
|
|
« Last Edit: June 23, 2009, 09:00:33 am by pfft2001 »
|
Logged
|
|
|
|
|
greyback
|
|
« Reply #21 on: June 23, 2009, 06:19:27 am » |
|
Hi pffft2001,
yes the original OSD had a slot for a SD card and a separate slot for a CF card.
In the newer models, the CF card slot disappeared, partly because it seemed to not be used so often, and partly I think so that additional memory could fit in the device.
Musht technology hasn't yet managed to bend spacial dimensions, but it's only a matter of time:)
-G
|
|
|
|
|
Logged
|
|
|
|
hoofdpijn
Newbie
Posts: 15
|
|
« Reply #22 on: June 23, 2009, 07:40:37 am » |
|
Ahhh...that explains it then. I was misinterpreting what I was looking at as well.
|
|
|
|
|
Logged
|
|
|
|
bmc
Newbie
Posts: 26
|
|
« Reply #23 on: June 23, 2009, 12:00:21 pm » |
|
Yes, looking at the output from their "dmesg" dump, there's no indication they have a CF/microdrive slot at all. So it looks like the OSDng update, at present, can't get applied to the 2nd rev hardware by the Neuros UPK updater. JoeBorn has said he'll be sending me one of those, and I'll see if I can reproduce hoof and pfft's upgrade problem. I'm back from vacation, but will be pretty busy at work in the near future. I'll try to find time to make sure 2nd rev OSD folks can use OSDng, so hoof and pfft and others can start playing and contributing too. I doubt hoof actually has a corrupt download of the upk (but for the record: "md5sum osdng-dev-2.52.upk" should produce "b98a8f8e7e066e4951ec2119ee71bf01"). Taking some blind guesses before I get hardware: More likely is that there's not enough space on the internal flash, and their upk updater chokes on that, maybe? (try running "df -h" - can you post that? Free up as much space as you can on "/dev/mtd6"). I don't really want to explore the other options (emergency upk updates, uboot mucking to force loading of OSDng even your old rootfs, tftp/nfs etc.) due to the high chance you'll soft-brick your OSD. If you guys can get a serial connection and a tftp/nfs boot working, you can probably figure out how to get OSDng running without going through the UPK update (update your nfs root with http://osd.oddren.com/files/cramfs/osdng-2.52.cramfs). If that's all greek to you, just wait until JoeBorn gets the rev2 hardware to me. |
|
|
|
|
Logged
|
|
|
|
hoofdpijn
Newbie
Posts: 15
|
|
« Reply #24 on: June 23, 2009, 06:30:13 pm » |
|
Well, root looks pretty full.  No wonder it's running sluggish. ~ $ df -h Filesystem Size Used Available Use% Mounted on /dev/mtd4 29.3M 29.3M 0 100% / tmpfs 256.0k 112.0k 144.0k 44% /mnt/tmpfs /dev/mtd5 1.0M 456.0k 568.0k 45% /mnt/OSD /dev/mtd6 109.5M 20.9M 88.6M 19% /mnt/tmpfs/mount_NAND /dev/sda1 1.9G 20.4M 1.8G 1% /mnt/tmpfs/mount_USB |
|
|
|
|
Logged
|
|
|
|
|
greyback
|
|
« Reply #25 on: June 23, 2009, 06:40:35 pm » |
|
Well, root looks pretty full. No wonder it's running sluggish. Root is a read-only partition of type cramfs, which always reports zero free space I think. @bmc I was of the impression that the only major difference between the OSDs was where /media/ext pointed to. On my older OSD, it points to the CF card, but newer OSD's I think it points to /mnt/tmpfs/mount_NAND. Aside from that, and some UPK flashing issues, the units aren't terribly dissimilar. But like you, I don't have a newer OSD. -G |
|
|
|
|
Logged
|
|
|
|
hoofdpijn
Newbie
Posts: 15
|
|
« Reply #26 on: June 23, 2009, 06:47:45 pm » |
|
Well, root looks pretty full. No wonder it's running sluggish. Root is a read-only partition of type cramfs, which always reports zero free space I think. @bmc I was of the impression that the only major difference between the OSDs was where /media/ext pointed to. On my older OSD, it points to the CF card, but newer OSD's I think it points to /mnt/tmpfs/mount_NAND. Aside from that, and some UPK flashing issues, the units aren't terribly dissimilar. But like you, I don't have a newer OSD. -G That looks right... / $ cd /media/ext /mnt/tmpfs/mount_NAND $ /mnt/tmpfs/mount_NAND $ ls -al drw-rw-rw- 1 root root 2048 Jan 1 1970 . drwxrwxrwt 7 root root 240 Jun 21 22:13 .. drwxr-xr-x 1 root root 2048 Jan 1 1970 .osd-extended drwxr-xr-x 1 root root 2048 Jan 1 1970 data drw-rw-rw- 1 root root 2048 Jan 1 1970 lost+found /mnt/tmpfs/mount_NAND $ /mnt/tmpfs/mount_NAND $ du -h . 2.0k ./data/shortcuts 27.0k ./data/xmms2 43.0k ./data 458.5k ./.osd-extended/programs/translations 877.0k ./.osd-extended/programs/Qt-4.4.0/lib/fonts 11.0M ./.osd-extended/programs/Qt-4.4.0/lib 49.5k ./.osd-extended/programs/Qt-4.4.0/plugins/iconengines 148.5k ./.osd-extended/programs/Qt-4.4.0/plugins/inputmethods 861.5k ./.osd-extended/programs/Qt-4.4.0/plugins/imageformats 47.0k ./.osd-extended/programs/Qt-4.4.0/plugins/gfxdrivers 61.0k ./.osd-extended/programs/Qt-4.4.0/plugins/ssaver 59.5k ./.osd-extended/programs/Qt-4.4.0/plugins/kbddrivers 34.5k ./.osd-extended/programs/Qt-4.4.0/plugins/styles 1.2M ./.osd-extended/programs/Qt-4.4.0/plugins 12.2M ./.osd-extended/programs/Qt-4.4.0 12.7M ./.osd-extended/programs 5.8M ./.osd-extended/scratch 18.5M ./.osd-extended 2.0k ./lost+found 18.5M . |
|
|
|
|
Logged
|
|
|
|
hoofdpijn
Newbie
Posts: 15
|
|
« Reply #27 on: June 23, 2009, 06:53:57 pm » |
|
One more for the sake of thoroughness
/mnt/tmpfs/mount_NAND $ mount
rootfs on / type rootfs (rw)
/dev/root on / type cramfs (ro)
devpts on /dev/pts type devpts (rw)
proc on /proc type proc (rw,nodiratime)
tmpfs on /mnt/tmpfs type tmpfs (rw)
sysfs on /sys type sysfs (rw)
/dev/mtd5 on /mnt/OSD type jffs2 (rw,noatime)
/dev/mtd6 on /mnt/tmpfs/mount_NAND type yaffs2 (rw)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
|
|
|
|
|
Logged
|
|
|
|
bmc
Newbie
Posts: 26
|
|
« Reply #28 on: June 26, 2009, 10:39:56 am » |
|
I just converted to OSDng and the process went smoothly. I noticed the keybounce fix rightaway. That has been something that's plagued OSD users for many, many months. Makes me scratch my head as to how Neuros couldn't get this fixed and you did it in a month. Youtube works again, but I viewed 2 vids and the OSD locked up after the 2nd one. Should we expect the same frequency of lockups with ng? A BIG THANK YOU for your efforts.  Bigshew: You're welcome! Glad it went smoothly for you and that the keybounce fix addressed one of your pet peeves. Caveat about youtube: I don't use the youtube player at all (fixing it was a favor to FC). The only fix I put in had to do with helping it find the URL of the youtube video to play (addressing "Youtube might have changed its video formats, try a firmware upgrade") As for locking up while playing youtube videos, nothing I did will make that better (or worse). Can you post youtube IDs (i.e. "v=AtyJbIOZjS8") of some videos that cause lockup? Does it always lockup on the same videos? Or will it sometimes play them fine, and only locks up after, say, playing X minutes of any videos? Any other patterns you can think of? |
|
|
|
|
Logged
|
|
|
|
bmc
Newbie
Posts: 26
|
|
« Reply #29 on: June 27, 2009, 05:58:03 am » |
|
hoof, pfft,
I have the second rev of firmware now (thanks JoeBorn), and OSDng loads up on it perfectly, without any changes.
Can you two give it a shot, and take careful notes about what goes wrong, when, and the exact error message?
The steps I observed:
* Put the 2.52 dev upk on an SD-card (not USB, incidentally)
* Play/Browse the upk file.
* I answer the "OK to install non-Neuros firmware" prompt.
* "pong screen" update briefly (I believe this is upk integrity check).
* Unit reboots
* pong screen update for a while (much faster than CF-units with NOR-flash, BTW) (this is update flash rootfs)
* "You Win" message, second reboot
* Final pong screen (updating extended area). Ends with "welcome to arizona". final reboot
I also did a flash using the "/newpackage/r3.upk" with "disable_upk_version_check" touchfile in the same directory, and that worked fine too.
Perhaps the "upk error" that one or both of you were experiencing was the result of flashing from a USB disk. I think one of the veterans on here had mentioned flashing from USB can be problematic under some conditions? Give it a shot from a SD-card, take careful notes, and let us know.
Thanks.
|
|
|
|
|
Logged
|
|
|
|
|
