[PlanetCCRMA] acpi kernel reboot errors

[Carr Wilkerson]

Thanks again.  Unfortunately, I installed pd, so I will have to go with 
the --nodeps route.  Will/how will this effect the apt-get update tracking 
process?

Carr





On Sun, 8 Sep 2002, Fernando Pablo Lopez-Lezcano wrote:

> > Executing RPM (-i)...
> > package kernel-up-2.4.19-2.ll.acpi (which is newer than 
> > kernel-up-2.4.19-1.ll) is already installed
> > Executing RPM (-U)...
> > error: failed dependencies:
> > 	kernel-up = 2.4.19-1.ll is needed by 
> > alsa-driver-2.4.19-1.ll-0.9.0-36
> > E: Sub-process /bin/rpm returned an error code (1)
> > E: Sub-process /bin/rpm returned an error code (1)
> 
> I see...
> 
> > What'd ya think?
> 
> Yuck, I hate computers :-)
> 
> So... we need to get rid of it, I think. We could always install the
> "previous kernel" through rpm so that you would not have to erase it,
> probably not worth it as it is not working anyway.
> 
> Let me see, I think this will get rid of the kernel and associated alsa 
> drivers (and leave the system without needed parts for a moment - that's 
> why I'm using the --nodeps flag, come to think of it you probably have 
> not yet installed anything that needs alsa so you may be able to do 
> without --nodeps which would be better):
> 
> rpm -e --nodeps kernel-up-2.4.19-2.ll.acpi alsa-driver-2.4.19-2.ll.acpi 
> alsa-lib alsa-utils alsa-tools
> 
> After that you should be able to do a:
> 
> apt-get -f install kernel-up#2.4.19-1.ll alsa-driver-2.4.19-1.ll 
> alsa-driver alsa-utils alsa-tools
> 
> (using the -f flag if you used --nodeps to erase the other rpms)
> 
> -- Fernando
> 
> 
> _______________________________________________
> PlanetCCRMA mailing list
> PlanetCCRMA at ccrma.stanford.edu
> http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma
> 

-- 
Carr L. Wilkerson, Jr.
Center for Computer Research in Music and Acoustics (CCRMA)
http://www-ccrma.stanford.edu/~carrlane