Re: dates of ppc daily builds old? WAS: request clarification on sbp2 and tg3
On Mon, Apr 24, 2006 at 10:57:59AM -0400, Toni L. Harbaugh-Blackford [Contr] wrote:
> On Mon, 24 Apr 2006, Sven Luther wrote:
> > Try the daily netboot images from :
> > http://people.debian.org/~luther/d-i/images/daily/powerpc64/netboot64/
> > They include the needed yaboot stuff to netboot the images, so just move the
> > whole dir to a tftp server on your network, or use the mini.iso.
> > I am not sure what happened to the cd image built, as you may know, i was
> > replaced as d-i powerpc maintainer, and have thus not be following issues in
> > much detail.
> > Friendly,
> > Sven Luther
> I tried the mini.iso, but it hangs at 'Trying to im_free nonexistant area':
Try an older mini.iso, which still has the 2.6.15 kernel ?
> checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
> Freeing initrd memory: 4652k freed
> NET: Registered protocol family 16
> Linux ppc64
> #2 SMP Mon Apr 10 18:55:49 CEST 2006
> PCI: Probing PCI hardware
> mapping IO f0000000 -> d000080000400000, size: 800000
> mapping IO f4000000 -> d000080000000000, size: 400000
> PCI: Probing PCI hardware done
> nvram_init: Could not find nvram partition for nvram buffered error logging.
> audit: initializing netlink socket (disabled)
> audit(1145890159.990:1): initialized
> VFS: Disk quotas dquot_6.5.1
> Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
> Initializing Cryptographic API
> io scheduler noop registered
> io scheduler anticipatory registered (default)
> io scheduler deadline registered
> io scheduler cfq registered
> HVSI: registered 0 devices
> Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
> pmac_zilog: 0.6 (Benjamin Herrenschmidt <email@example.com>)
> pmac_zilog: Error registering serial device, disabling pmac_zilog.
> pmac_zilog: Did another serial driver already claim the minors?
> Trying to im_free nonexistent area (d0000800820d7000)
> With a previous version of the mini.iso, I was able to get to a shell
> to 'look around', but this time the boot did not get that far.
What version was it ? Can you capture the full log and file a bug report, and
also append your /proc/cpuinfo ?