linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Mark Glines <mark@glines.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: kurobox kernel
Date: Fri, 29 Dec 2006 09:58:56 -0800	[thread overview]
Message-ID: <45955760.6020306@glines.org> (raw)
In-Reply-To: <Pine.LNX.4.60.0612290127180.3942@poirot.grange>

Guennadi Liakhovetski wrote:
> My config is in the kernel - arch/powerpc/configs/linkstation_defconfig.
> And I don't use IDE, I use PATA, and it works good, I also had problems 
> with IDE, although, not as bad as you describe. Also, you, certainly, need 
> root=/dev/sda1, not hda1, change it in your U-boot environment. As for 
> interrupt numbers - they are correct, and they are (pretty) arbitrary, 
> allocated dynamically. I have:
> 
> lyakh@KURO-BOX:~$ cat /proc/interrupts
>            CPU0
>  16:          0   EPIC      Level     serial
>  17:        230   EPIC      Edge      serial
>  18:       1747   EPIC      Level     i2c-mpc
>  19:     142193   EPIC      Level     eth0
>  20:       1764   EPIC      Level     libata
>  21:    1309856   EPIC      Level     ehci_hcd:usb1, ohci_hcd:usb2, ohci_hcd:usb3
> BAD:         15
> 
> Thanks
> Guennadi
> ---
> Guennadi Liakhovetski

Thanks, disabling IDE worked.  It took a couple tries due to a Makefile 
issue (or misunderstanding on my part)... see below.  Now I get to 
figure out why my Gentoo userspace won't boot, which I think is beyond 
the scope of this list :)

NET: Registered protocol family 1
NET: Registered protocol family 17
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
linkstation: disarming the AVR watchdog:
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 140k init
Synchronizing SCSI cache for disk sda:
Restarting system.


One issue I ran into is that "make zImage" does not rebuild an existing 
image, but "make uImage" does... I think the Makefile is missing a 
dependency.  I'll send a patch if I debug this further.  I know the 
"zImage" rule is just there for convenience, but apparently zImage is a 
deeply ingrained habit for me.

paranoid@kuro-2 /usr/src/linux $ make zImage
   CHK     include/linux/version.h
   CHK     include/linux/compile.h
   UPD     include/linux/compile.h
   CHK     include/linux/utsrelease.h
   CC      init/main.o
   CC      init/version.o
   LD      init/built-in.o
   CC      fs/proc/proc_misc.o
   LD      fs/proc/proc.o
   LD      fs/proc/built-in.o
   LD      fs/built-in.o
   GEN     .version
   LD      .tmp_vmlinux1
   KSYM    .tmp_kallsyms1.S
   AS      .tmp_kallsyms1.o
   LD      .tmp_vmlinux2
   KSYM    .tmp_kallsyms2.S
   AS      .tmp_kallsyms2.o
   LD      vmlinux
   SYSMAP  System.map
   SYSMAP  .tmp_System.map
   MODPOST vmlinux
make[1]: `arch/powerpc/boot/zImage' is up to date.
paranoid@kuro-2 /usr/src/linux $ make uImage
   CHK     include/linux/version.h
   CHK     include/linux/compile.h
   UPD     include/linux/compile.h
   CHK     include/linux/utsrelease.h
   CC      init/main.o
   CC      init/version.o
   LD      init/built-in.o
   CC      fs/proc/proc_misc.o
   LD      fs/proc/proc.o
   LD      fs/proc/built-in.o
   LD      fs/built-in.o
   GEN     .version
   LD      .tmp_vmlinux1
   KSYM    .tmp_kallsyms1.S
   AS      .tmp_kallsyms1.o
   LD      .tmp_vmlinux2
   KSYM    .tmp_kallsyms2.S
   AS      .tmp_kallsyms2.o
   LD      vmlinux
   SYSMAP  System.map
   SYSMAP  .tmp_System.map
   MODPOST vmlinux
   WRAP    arch/powerpc/boot/uImage
Image Name:   Linux-2.6.20-rc2-kuroboxHG
Created:      Fri Dec 29 09:43:09 2006
Image Type:   PowerPC Linux Kernel Image (gzip compressed)
Data Size:    1624545 Bytes = 1586.47 kB = 1.55 MB
Load Address: 0x00000000
Entry Point:  0x00000000

Mark

  parent reply	other threads:[~2006-12-29 17:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.ne7N9dqjDz5qS4D/fowPKdPc4ZY@ifi.uio.no>
     [not found] ` <fa.pM17YEcICUlveSt/vbSKGv6sFWk@ifi.uio.no>
2006-12-25 19:45   ` Linux 2.6.20-rc2: forgot how to make a zImage on powerpc? Mark Glines
2006-12-25 20:31     ` Guennadi Liakhovetski
2006-12-25 21:47       ` [PATCH] powerpc: linkstation uses uimage style zImages Mark Glines
2006-12-25 22:54         ` Guennadi Liakhovetski
2006-12-25 23:07           ` Mark Glines
2006-12-25 23:23             ` Guennadi Liakhovetski
2006-12-26 20:14               ` kurobox kernel Mark Glines
2006-12-26 21:23                 ` Guennadi Liakhovetski
2006-12-28 20:53                   ` Mark Glines
2006-12-28 21:02                     ` Scott Wood
2006-12-28 21:07                       ` Xianghua Xiao
2006-12-28 21:11                     ` Guennadi Liakhovetski
2006-12-28 23:28                       ` Mark Glines
2006-12-29  0:31                         ` Guennadi Liakhovetski
2006-12-29  2:52                           ` Mark Glines
2006-12-29 17:58                           ` Mark Glines [this message]
2006-12-29 18:35                             ` Guennadi Liakhovetski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45955760.6020306@glines.org \
    --to=mark@glines.org \
    --cc=g.liakhovetski@gmx.de \
    --cc=linuxppc-dev@ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).