On Thu, 6 Jun 2002 10:54am -0700, Alan Messer wrote:
> - I've configured it to pivot_root from the ipaq's flash to a 256
> SanDisk CF card. However, I have seen a couple of problems. I
> frequently get log entries claiming invalidate problems. Any ideas
> on how to get rid of these?
>
> invalidate: busy buffer
> invalidate: dirty buffer
> invalidate: busy buffer
> invalidate: dirty buffer
Have you suspended/resumed the ipaq at any point? -- I find the CF cards
often fail to come back properly after that.
> - I've also been trying to get the ipaq to boot the CF card
> directly. I've used the instructions from the Wiki
> BootingLinuxFromCF, but no luck. It refuses to do anything after
> finding the kernel. Looking through the logs I notice that the
> pcmcia insert stage doesn't correctly display the name/revision of
> the card (despite retrieving them correctly from under Linux). So
> perhaps 256M cards (SanDisk) aren't supported under bootldr
> 2.18.39? I've included my boot log entries below. I'd really like
> to get this is going and forget pivoting, but I'm not having much
> luck.
I've seen the strange ident too, consistently. I'm assuming it's just some
kind of byte-swapping style issue in interpreting the info that comes from
the disk. I have been able to boot successfully.
> boot> set kernel_filename boot/zimage
> setting param <kernel_filename> to value <boot/zimage>
> boot> boot vfat
> + set linuxargs "initrd root=/dev/rd/0"
> setting param <linuxargs> to value <initrd root=/dev/rd/0>
> + set kernel_filename boot/zImage
> setting param <kernel_filename> to value <boot/zImage>
If you haven't set the console to ttySA0 on the kernel command line(and it
doesn't default to that in the kernel), than you probably won't see
anything after the kernel boots since the console is no longer going to
the serial port... Try setting it manually and see if that gets you any
further.
Hope this helps!
Received on Fri Jun 07 12:32:37 2002
This archive was generated by hypermail 2.1.8 : Tue May 04 2004 - 09:44:51 EDT