Inline Monte breaks Elseed?

[bgreen]

In the quest for faster and faster extraction speeds I implemented the inline monte configuration as described by AlphaWolf here (http://www.dealdatabase.com/forum/showthread.php?p=216711#post216711). The results were positive and my extraction speeds went to 3.3-3.5MB/sec. That's the good news.

After implementation, Elseed's OSD functions seem to be broken. I'm using the Elseed that was posted here (http://www.dealdatabase.com/forum/showpost.php?p=215005&postcount=5). When Elseed loads, I get the following error right before it initializes the modem...

"Couldn't find or create shared front buffer"

Just wondering if anyone else has seen this error and know what I can attribute it to. I'm guessing it probably has something to do with running AW's 2.4.20 kernel rather than the killhdinitrd 2.4.20 kernel but I'm not sure. I think the faster downloads are great but the lack of CID is a deal breaker for the wife so I've backed out my changes for now. Can anyone help point me in the right direction?

[Jamie]

After implementation, Elseed's OSD functions seem to be broken. I'm using the Elseed that was posted here (http://www.dealdatabase.com/forum/showpost.php?p=215005&postcount=5). When Elseed loads, I get the following error right before it initializes the modem...

"Couldn't find or create shared front buffer"

Just wondering if anyone else has seen this error and know what I can attribute it to. ...relevant past history? (http://www.dealdatabase.com/forum/showthread.php?p=179493#post179493)

I believe you are using a kernel I built from the 7.1 kernel sources. I wonder if it is the kernel, or the monte that is the issue. We could try to substitute a 2.4.20 kernel from the 3.1.5 sources instead with the same config options I used with the 7.1 kernel.

[bgreen]

I believe you are using a kernel I built from the 7.1 kernel sources. I wonder if it is the kernel, or the monte that is the issue. We could try to substitute a 2.4.20 kernel from the 3.1.5 sources instead with the same config options I used with the 7.1 kernel.

I believe that's correct, the kernel I monte in to is loading as...

Linux version 2.4.20 (root@fedora.home.lan) (gcc version 3.0) #6 Wed Jan 26 17:52:06 MST 2005

...which I believe is the one you compiled. I think the kernel you are recommending (3.1.5 with the same options as you compiled in the 7.1 source) is what I'm looking for. At the very least this would provide a baseline to determine if it's the kernel or the monte config breaking elseed. I don't have a cross compiler set up let alone I've never compiled my own kernel. I'll start looking at your posts here (http://www.dealdatabase.com/forum/showpost.php?p=208377&postcount=70) and maybe attempt to start setting up an environement.

That is unless of course you'd like to take pitty on my and throw a kernel together for me. As I understand it, the only chnage you made was to disable CONFIG_NETFILTER?

Any Elseed experts out there care to comment?

[Jamie]

That is unless of course you'd like to take pitty on my and throw a kernel together for me. As I understand it, the only chnage you made was to disable CONFIG_NETFILTER?I'll do this and see if I can reproduce your OSD problems when I get time. I'm backlogged at the moment. I believe there are some other patches I made. I posted a summary somewhere, as I recall.

[Jamie]

It occurs to me that there is an easier way to test whether monte or the kernel is the issue.

Get a virgin 3.1.5 kernel and nueter it with replace_initrd. monte to that instead of the custom kernel. That way you'll be using the same kernel as if you didn't monte. Does the OSD problem still happen?

[bgreen]

Get a virgin 3.1.5 kernel and nueter it with replace_initrd. monte to that instead of the custom kernel. That way you'll be using the same kernel as if you didn't monte. Does the OSD problem still happen?

OK, that makes sense. Forgive me, if I'm asking a stupid question here... So I can just dd out the kernel from my unhacked backup drive to a vmlinux.px file? From there I can replace_initrd that kernel and then monte in to that?

On a sort of related note... I managed to create a cross compiling environment (whew!) and tested it with a "Hello world" application. I was attempting to compile the 7.1 kernel from the tivo.com/linux sources. I ran the menuconfig and saw where config_netfilter can be left out but it seems weird to me that there are A LOT of things not checked by default in the menu. The other option is to not run the menu and say "yes" to everything but that doesn't seem very efficient either. Seeing as you've compiled the kernel before for Tivo can you offer any insight on this. Did you say yes to all the modules "except" the config_netfilter when you compiled it?

[Jamie]

OK, that makes sense. Forgive me, if I'm asking a stupid question here... So I can just dd out the kernel from my unhacked backup drive to a vmlinux.px file? From there I can replace_initrd that kernel and then monte in to that?If you want to run exactly the same kernel you run without the monte, you'll want the 3.1.5 kernel. That way you're really just testing whether it is monte, or the custom 7.1 kernel that is causing you OSD grief.Your unhacked backup drive has a the kernel from 6.2, I assume.On a sort of related note... I managed to create a cross compiling environment (whew!) and tested it with a "Hello world" application. I was attempting to compile the 7.1 kernel from the tivo.com/linux sources. I ran the menuconfig and saw where config_netfilter can be left out but it seems weird to me that there are A LOT of things not checked by default in the menu. The other option is to not run the menu and say "yes" to everything but that doesn't seem very efficient either. Seeing as you've compiled the kernel before for Tivo can you offer any insight on this. Did you say yes to all the modules "except" the config_netfilter when you compiled it?It's been a while since I did this, but I believe I borrowed some of ADH's patches here (http://www.dealdatabase.com/forum/showthread.php?p=181536#post181536).

As I recall, the 'default' kernel config is the one that tivo uses when they built the production kernel. Only turn on/off the things you want to change. Turning off CONFIG_BLK_DEV_INITRD is a good idea to prevent initrd checks.