From: "Drew Parsons" <[EMAIL PROTECTED]>
> > I wondered why the module "i82365.o" is chosen as default config.
>
> Roughly speaking, i82365 is what you need to work with 16-bit PCMCIA cards
> only. To use the 32-bit PC Cards, you need yenta (as you've discovered
> empirically ;) ). I had thought
From: "Drew Parsons" <[EMAIL PROTECTED]>
> > I wondered why the module "i82365.o" is chosen as default config.
>
> Roughly speaking, i82365 is what you need to work with 16-bit PCMCIA cards
> only. To use the 32-bit PC Cards, you need yenta (as you've discovered
> empirically ;) ). I had thought
On Sat, Oct 26, 2002 at 03:02:53PM +0200, Yuhanes Tjandra wrote:
> This is how I got it works.
>
> It wasn't APM that caused the problem. It was pcmcia service that tried
> to load inapporiate module which was "i82365.o"
> The PC card (Linksys PCMLM56) wasn't working. Adding the module
> "yenta_
On Sat, Oct 26, 2002 at 03:02:53PM +0200, Yuhanes Tjandra wrote:
> This is how I got it works.
>
> It wasn't APM that caused the problem. It was pcmcia service that tried
> to load inapporiate module which was "i82365.o"
> The PC card (Linksys PCMLM56) wasn't working. Adding the module
> "yenta_
This is how I got it works.
It wasn't APM that caused the problem. It was pcmcia service that tried
to load inapporiate module which was "i82365.o"
The PC card (Linksys PCMLM56) wasn't working. Adding the module
"yenta_socket" made the card working, yet there were
always error messages at bootu
This is how I got it works.
It wasn't APM that caused the problem. It was pcmcia service that tried
to load inapporiate module which was "i82365.o"
The PC card (Linksys PCMLM56) wasn't working. Adding the module
"yenta_socket" made the card working, yet there were
always error messages at bootup
Yeah, I know...
As I posted before, I am gonna try to compile a custom kernel with
CONFIG_PM enabled and APIC.
I will post the updated news as soon as I try it.
Yuhanes
Anders E. Andersen schrieb:
Yuhanes Tjandra wrote:
Hi,
just wanna update the last status of problem. After buildin
Yeah, I know...
As I posted before, I am gonna try to compile a custom kernel with
CONFIG_PM enabled and APIC.
I will post the updated news as soon as I try it.
Yuhanes
Anders E. Andersen schrieb:
> Yuhanes Tjandra wrote:
>
>> Hi,
>>
>> just wanna update the last status of problem. After
Yuhanes Tjandra wrote:
Hi,
just wanna update the last status of problem. After building a custom
kernel with CONFIG_PM disabled somehow solves the problem. I can now
reboot to windows in a warm start.
Disabling power management altogether sounds a bit harsh.
Have you tried compiling with C
Yuhanes Tjandra wrote:
> Hi,
>
> just wanna update the last status of problem. After building a custom
> kernel with CONFIG_PM disabled somehow solves the problem. I can now
> reboot to windows in a warm start.
Disabling power management altogether sounds a bit harsh.
Have you tried compilin
Hi,
just wanna update the last status of problem. After building a custom
kernel with CONFIG_PM disabled somehow solves the problem. I can now
reboot to windows in a warm start.
I also recognize that Windows can also be booted into safe mode with
CONFIG_PM enabled .
I am suspecting that t
Hi,
just wanna update the last status of problem. After building a custom
kernel with CONFIG_PM disabled somehow solves the problem. I can now
reboot to windows in a warm start.
I also recognize that Windows can also be booted into safe mode with
CONFIG_PM enabled .
I am suspecting that th
apm certainly is a candidate that could be causing the problems. Try not
loading the module at all, unloading will be done on shutdown, too, and
apparently isn't enough. Does your windows installation use ACPI?
(See the hardware manager)
Ok, I have tried suggestions that you guys gave. I have r
>
>
>apm certainly is a candidate that could be causing the problems. Try not
>loading the module at all, unloading will be done on shutdown, too, and
>apparently isn't enough. Does your windows installation use ACPI?
>(See the hardware manager)
>
Ok, I have tried suggestions that you guys gave. I
> And how to boot into single user mode? Sorry, newbie here. Are you
> saying that I have to remove related daemons?
Single user is for repairing a seriously broken system and such.
See the docs how to start it (depends on wheter you use lilo or grub)
> I had a thought that it could be caused by
On Sun, Oct 13, 2002 at 01:32:31PM +0200, Erich Schubert wrote:
> > The problem is that Win98Se can't be booted direct after restarting from
> > Woody. It freezes and the only thing that I can do is to press the
> > power button off and on, then Win98Se can operate normally.
>
> Sounds like a h
> And how to boot into single user mode? Sorry, newbie here. Are you
> saying that I have to remove related daemons?
Single user is for repairing a seriously broken system and such.
See the docs how to start it (depends on wheter you use lilo or grub)
> I had a thought that it could be caused b
Does windows work on a cold start (that is directly after poweron)?
If you boot linux into single user mode (probably not loading pcmcia and
such stuff) and then reboot into windows, does it work then?
Yes, it works on a cold start.
And how to boot into single user mode? Sorry, newbie here.
On Sun, Oct 13, 2002 at 01:32:31PM +0200, Erich Schubert wrote:
> > The problem is that Win98Se can't be booted direct after restarting from
> > Woody. It freezes and the only thing that I can do is to press the
> > power button off and on, then Win98Se can operate normally.
>
> Sounds like a
Am Sonntag, 13. Oktober 2002 13:32 schrieb Erich Schubert:
> > The problem is that Win98Se can't be booted direct after restarting from
> > Woody. It freezes and the only thing that I can do is to press the
> > power button off and on, then Win98Se can operate normally.
>
> Sounds like a hardware
> The problem is that Win98Se can't be booted direct after restarting from
> Woody. It freezes and the only thing that I can do is to press the
> power button off and on, then Win98Se can operate normally.
Sounds like a hardware problem to me.
I had a machine i had no sound in windows when i ra
On Sun, Oct 13, 2002 at 12:56:50PM +0200, Yuhanes Tjandra wrote:
> The problem is that Win98Se can't be booted direct after restarting from
> Woody. It freezes and the only thing that I can do is to press the
> power button off and on, then Win98Se can operate normally.
>
> FYI, I used to have
Am Sonntag, 13. Oktober 2002 13:32 schrieb Erich Schubert:
> > The problem is that Win98Se can't be booted direct after restarting from
> > Woody. It freezes and the only thing that I can do is to press the
> > power button off and on, then Win98Se can operate normally.
>
> Sounds like a hardware
Does windows work on a cold start (that is directly after poweron)?
If you boot linux into single user mode (probably not loading pcmcia and
such stuff) and then reboot into windows, does it work then?
Yes, it works on a cold start.
And how to boot into single user mode? Sorry, newbie here. A
On Sun, Oct 13, 2002 at 12:56:50PM +0200, Yuhanes Tjandra wrote:
> The problem is that Win98Se can't be booted direct after restarting from
> Woody. It freezes and the only thing that I can do is to press the
> power button off and on, then Win98Se can operate normally.
>
> FYI, I used to have
> The problem is that Win98Se can't be booted direct after restarting from
> Woody. It freezes and the only thing that I can do is to press the
> power button off and on, then Win98Se can operate normally.
Sounds like a hardware problem to me.
I had a machine i had no sound in windows when i ra
26 matches
Mail list logo
