--- Nick Hastings <[EMAIL PROTECTED]>
wrote:
> Hi Charles,
<<SNIP>>
> > --- Sean 'Shaleh' Perry <[EMAIL PROTECTED]>
> wrote:
> > > Look in /proc. There should be an apm file
> there.
> > > If not, linux is NOT using
> > > apm.
> >
> > Okay, no /proc/apm but what could've killed it for
> > 2.4.17 ? It was working just fine before I
> installed 2.4.18 .
>
> What is in your /etc/lilo.conf now?
<<SNIP>>
lba32
boot=/dev/hda
root=/dev/hda3
install=/boot/boot.b
map=/boot/map
delay=20
vga=1
append="apm=on"
default=LinuxOld
image=/vmlinuz
initrd=/initrd.img
label=LinuxNew
read-only
image=/vmlinuz.old
initrd=/initrd.img.old
label=LinuxOld
read-only
image=/vmlinuz2.2
label=Linux22
read-only
optional
All other lines are comments from original install.
vmlinuz -> boot/vmlinuz-2.4.18-686
vmlinuz.old -> boot/vmlinuz-2.4.17-686
vmlinuz.2.2 -> boot/vmlinuz-2.2.18pre21
initrd.img -> boot/initrd.img-2.4.18-686
initrd.img.old -> boot/initrd.img-2.4.17-686
The weird thing w/ this is that 2.4.17 was using apm
before I installed and did the dist-upgrade ( which
btw did upgrade apmd ).
BTW, in my other post I mentioned a little pcmcia
strangeness. Saw no reply, but I did a ``modprobe
yenta_socket'' and then a ``modprobe xirc2ps_cs'' and
brought the pcmcia nic back up. I guess I need to use
modconf again to make this semi-permanent?
=====
[EMAIL PROTECTED]
Hacking is a "Good Thing!"
See http://www.tuxedo.org/~esr/faqs/hacker-howto.html
__________________________________________________
Do You Yahoo!?
Try FREE Yahoo! Mail - the world's greatest free email!
http://mail.yahoo.com/
