Messages in this thread | | | Date | Wed, 15 Sep 1999 14:27:41 +0200 | From | Christof Petig <> | Subject | Re: 2.3.18ac3 PCMCIA experiences (includes partial patch) |
| |
Jeff Garzik wrote:
> Christof Petig wrote: > > - vga16fb reported some problems registering vga memory. This might be a > > cause of recent resource management changes, this might be a cause of > > another clgenfb selected as a module (vga16 was compiled into the > > kernel)
> Can you provide some more details here? How does clgenfb figure into > the equation -- are you trying to load clgenfb as a module w/ vga16fb > compiled into the kernel?
See boot.msg attached, see .config file attached. I intended to boot with vga16fb to see the nice penguin and later try to load clgenfb since my Videochip (CL GD 7543) isn't supposed to work with it yet. However I deactivated clgenfb and the problem persisted.
> Does this problem go away if you do not enable CONFIG_PCMCIA?
I don't know since I need PCMCIA. If you want me to try exactly this, please tell me. (Constantly Rebooting my poor Terminal isn't a nice option at work) I suspect the enabled 'text mode console' disables vga16fb ... but that used to work some time ago ... (2.3.16 or so).
However (to Alan): - the pcmcia_core module doesn't know about versioning (it asks for __check_region), hmm that is not totally true, at the same time it asks for __release_region_Rd49501d4 and __release_region. CardServices_Re4eef0a4 is defined, CardServices is undefined. Looks like symbol versioning is screwed up.
- I experienced a full lockup while examining the output of /sbin/init.d/pcmcia start (missing symbols). Magic Key non functional. I have no clue. And that I unplugged the Laptop to heat tea-water (same plug) shouldn't have caused that - I do that several times a day (though with 2.2 and APM enabled).
Well, Lets see how it handles next release Christof
[unhandled content-type:application/x-gzip][unhandled content-type:application/x-gzip] | |