Feisty Hibernate/suspend issues

[manchicken]

On Tuesday 01 May 2007 12:01:53 Peter Niedzinski wrote:
> x86
>
> On 5/1/07, manchicken <manchicken at notsosoft.net> wrote:
> > On Tuesday 01 May 2007 11:00:26 Peter Niedzinski wrote:
> > > ndiswrapper
> > >
> > > On 5/1/07, manchicken <manchicken at notsosoft.net> wrote:
> > > > On Monday 30 April 2007 21:43:11 Peter Niedzinski wrote:
> > > > > Am running wireless, bcm 34xx or something like that.  Specifically
> > > >
> > > > Linksys
> > > >
> > > > > Wireless G PCMCIA card.  Have no SATA that I am aware of, and I
> >
> > can't
> >
> > > > > recall now what is ACPI.
> > > > >
> > > > > On 4/30/07, manchicken <manchicken at notsosoft.net> wrote:
> > > > > > On Monday 30 April 2007 19:00:12 Peter Niedzinski wrote:
> > > > > > > I am not sure what info you guys might need, but suspend only
> > > >
> > > > functions
> > > >
> > > > > > > when no programs are running and hibernate doesn't work under
> >
> > any
> >
> > > > > > > conditions. When a program is running, the computer freezes
> > > > > > > with
> > > >
> > > > both
> > > >
> > > > > > > options.  Any help would be great!
> > > > > > >
> > > > > > > Peter
> > > > > >
> > > > > > Here's a question... are you running any wireless cards?  If so,
> >
> > what
> >
> > > > > > interface are you using?  I'm noticing similar trouble since the
> >
> > move
> >
> > > > > > from 2.6.17 to 2.6.20, and I think it's related to my wireless
> >
> > over
> >
> > > > > > here.  Though
> > > > > > I've also heard of SATA drivers causing this problem, and then
> > > > > > there's the obvious ACPI possibility.
> > > > > >
> > > > > > --
> > > > > > ~ manchicken <><
> > > > > > (A)bort, (R)etry, (I)nfluence with large hammer.
> > > > > > The number of the beast - vi vi vi
> > > > > >
> > > > > > --
> > > > > > kubuntu-users mailing list
> > > > > > kubuntu-users at lists.ubuntu.com
> > > > > > Modify settings or unsubscribe at:
> > > > > > https://lists.ubuntu.com/mailman/listinfo/kubuntu-users
> > > >
> > > > Okay, for your broadcom card, are you running ndiswrapper or linuxant
> > > > driverloader?
> > > >
> > > > --
> > > > ~ manchicken <><
> > > > (A)bort, (R)etry, (I)nfluence with large hammer.
> > > > The number of the beast - vi vi vi
> > > >
> > > > --
> > > > kubuntu-users mailing list
> > > > kubuntu-users at lists.ubuntu.com
> > > > Modify settings or unsubscribe at:
> > > > https://lists.ubuntu.com/mailman/listinfo/kubuntu-users
> >
> > x86 or amd64?
> >
> > --
> > ~ manchicken <><
> > (A)bort, (R)etry, (I)nfluence with large hammer.
> > The number of the beast - vi vi vi
> >
> > --
> > kubuntu-users mailing list
> > kubuntu-users at lists.ubuntu.com
> > Modify settings or unsubscribe at:
> > https://lists.ubuntu.com/mailman/listinfo/kubuntu-users

We're very close, but not that close.  I'm running a bcm4318 on amd64 using 
driverloader.  I wonder if there's something in linux 2.6.20 that's breaking 
compatibility.

I've notified linuxant people and they're having their developers look into 
it.  They tried to imply that it may be kernel hackers' fault.  Had to remind 
them that kernel hackers aren't able to support driverloader stuff since it's 
proprietary.

-- 
~ manchicken <><
(A)bort, (R)etry, (I)nfluence with large hammer.
The number of the beast - vi vi vi