Re: apm strangeness
--- Charles Baker <rascharles@yahoo.com> wrote:
>
> --- Nick Hastings <hastings@physics.unimelb.edu.au>
> wrote:
> > Hi Charles,
>
> <<SNIP>>
>
> > > --- Sean 'Shaleh' Perry <shalehperry@attbi.com>
> > 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?
<<SNIP>>
Okay, I ran modconf and installed apm module in the
kernel. Before wasn't apm built into most debian
kernel images? I also did a ``cp -R
/lib/modules/kernel-pcmcia-2.4.18-686
/lib/modules/2.4.18-686/pcmcia'' and the pcmcia
modules showed up in modconf. I installed
yenta_socket, xirc2ps_cs and a couple of other things.
Rebooted into 2.4.17 and presto, apmd started at boot
time as well as my pcmcia nic. Started up WindowMaker,
and wmbattery started as well. Next I'll see if I
can't get 2.4.18 to behave.One last strange thing,
uname -a reports 2.4.18-686, but linuxlogo is
reporting 2.4.17-686. /proc/version shows 2.4.18-686
as well.
=====
rascharles@yahoo.com
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/
Reply to: