From None Date: None From: Subject: [palinux-palo] bug#138: palo can't figure out 32/64 X-PA-RISC Linux-PR-Message: report 138 X-PA-RISC Linux-PR-Package: palo X-Loop: daniel_frazier@hp.com Received: via spool by bugs@bugs.parisc-linux.org id=B.99350381226568 (code B ref -1); Mon, 25 Jun 2001 21:18:01 GMT X-Mailer: exmh version 2.3.1 01/18/2001 (debian 2.3.1-1) with nmh-1.0.4+dev To: submit@bugs.parisc-linux.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 25 Jun 2001 15:19:38 -0600 From: Matt Taggart Message-Id: <20010625211938.00E8737D2C@carmen.fc.hp.com> Package: palo Version: 0.92 Severity: grave palo is trying to figure out 32/64 based on the kernel name. This breaks the default cross-compiling case of using "make palo" as the kernel is named vmlinux and you get the following on boot, Warning: kernel name doesn't end with 32 or 64... Guessing 32 Couldn't grok your kernel executable format failed to load kernel palo needs to figure this out a different way based on the kernel itself. According to Paul the work around for now is to change your kernel command line to be specific (add 32 or 64 to the end of the kernel name like 0/vmlinux64). -- Matt Taggart Linux Development Lab taggart@fc.hp.com HP Linux Systems Operation