Re: [PLUG] new kernel bombs

[Kevin Brosius <kbrosius@kns.com>]

Hmm, that machine is down (well, in Windows) at the moment, so I can't
access it remote.  I can check tonight...  I think the kernel had Sony
APIC or power management support in it's options.  It was a SuSE kernel,
as I recall, so might have included part/all of the patches you
mention.  I'll take a look.

Kevin


"W. Chris Shank" wrote:
> 
> i'll have to check for .rej files tonight.
> 
> the patches were for R505DL, mine is R505TS, so there is some differences.
> But I thought the differences were mostly just cpu, hdd size, and onboard
> wireless.
> 
> do remember which kernel option locks up your vaio?
> 
> > Good there're no rejects.  Did you search through the log, or check for
> > .rej files to be sure?
> >
> > Also, some of the SONY support appears to only work on some Vaio's,
> > from what I've seen (at least one of the kernel options I tried locks a
> > vaio solid.)  It might be that kind of problem.  Does this patch list
> > which Vaio models it supports?
> >
> > Kev
> >
> > "W. Chris Shank" wrote:
> >>
> >> I'm using grub. i copied the grub entry from stock RH7.3, renamed it
> >> and modified it so that all references to 2.4.18-3 (initrd and
> >> vmlinuz) point to 2.4.18 instead. I left the original entry so that i
> >> can boot stock RH7.3 too.
> >>
> >> it starts to boot. it just dies partway through.
> >>
> >> no rejects in patching. it was a bulk patch that someone made for vaio
> >> laptop. so i need to decompose it in order to apply individually.
> >>
> >>
> >>
> >> > You busted it! :)
> >> >
> >> > Are you using lilo?  Did you run it at the end?
> >> >
> >> > Do you _really_need_ a init_rd?  If so, did you modify lilo to point
> >> > to both the new kernel and new init_rd image?  (If you have a
> >> > separate kernel modules tree, such as a different version, for your
> >> > previous kernel, then yes, you can put entries for both in the boot
> >> > loader and just boot the previous kernel when the new one fails.
> >> > Highly
> >> > recommended.)
> >> >
> >> > How about the patching process, did you have any rejects?
> >> >
> >> > Kevin
> >> >
> >> > "W. Chris Shank" wrote:
> >> >>
> >> >> just to make sure i'm doing this right - this is my kernel
> >> >> building/deploying procedure:
> >> >>
> >> >> make xconfig
> >> >> make dep; make clean; make bzIamge; make modules; make
> >> >> modules_install mv /usr/src/linux/arch/i386/boot/bzImage
> >> >> /boot/vmlinuz-2.4.18 mv /usr/src/linux/System.map
> >> >> /boot/System-map-2.4.18
> >> >> mv /usr/src/linux/vmlinux /boot/vmlinux-2.4.18
> >> >> mkinitrd /boot/initrd-2.4.18.img 2.4.18
> >> >> (currently /boot/System.map is a soft-link to System.map-2.4.18-3
> >> >> (redhat 7.3 stock and /boot/vmlinuz is a soft-link to
> >> >> vmlinuz-2.4.18-3 --> do i need to relink htese to my new ones? wha
> >> >> if it doesn't work, will i be able to boot my old kernel?)
> >> >> there is also /boot/module-info-2.4.18-3, i don't know how ot make
> >> >> an equivalent of this with my new kernel.
> >> >>
> >> >> thanks for your help
> >> >>
> >> >> Sean Finney wrote:
> >> >>
> >> >> >On Tue, Jul 16, 2002 at 12:21:22AM -0500, Sean Finney wrote:
> >> >> >
> >> >> >
> >> >> >>i'd suggest reconfiguring and re-compiling your kernel with
> >> >> >>kernel debugging cranked all the way up to see if you can find
> >> >> >>where the error is during the boot process.  alternatively, you
> >> >> >>could also try
> >> >> >>
> >> >> >>
> >> >> >
> >> >> >oh, i forgot--i think you can use your System.map file to map the
> >> >> >eip to where in the kernel you got that error as well.  if that's
> >> >> >the case you could probably figure out which patch was causing
> >> >> >the error if the culprit were a patch
> >> >> >
> >> >> >--sean
> >> >> >
> >> >
> >> >
> >

______________________________________________________________________
Philadelphia Linux Users Group       -      http://www.phillylinux.org
Announcements-http://lists.phillylinux.org/mail/listinfo/plug-announce
General Discussion  -  http://lists.phillylinux.org/mail/listinfo/plug