From niel.drummond at grumpytoad.org Sun Aug 3 14:39:36 2008 From: niel.drummond at grumpytoad.org (Niel Drummond) Date: Sun, 03 Aug 2008 16:39:36 +0200 Subject: [armedslack] loadlin woes In-Reply-To: References: <48803935.2070501@grumpytoad.org> <4880F004.1000808@grumpytoad.org> <4887A65E.9000601@grumpytoad.org> Message-ID: <4895C328.3060004@grumpytoad.org> Hi Stuart and list, Everything seems to work as described, except the critical loadlin bootup step :-| I've tried a number of loadlin parameters, but the result is nearly always an immediate black screen / hard crash. There is no disc access, and I need to pull the power to start up again. The --dry-run option gives me something more useful, but it does not look like a stack dump or error: === *dir armedslack *dir slackbt *!Linloader.!Run --dry-run zImage2422 lll_sys_name = Castle IYONIX lll_sys_id = 8 dram_layout_is_riscpc = 0 lll_rpc_vram_pages = 0 lll_pages = 65536 lll_memory_bank[] = {65536, 0, 0, 0, 0, 0, 0, 0} proc_id = 0x69052C32 mc_id = 0xFF Linloader 0.36 ? 1999 Timothy Baldwin Parts ? Russell King, Matthias Seifert and others System : Castle IYONIX === any help is much appreciated.. I'm going to try hunting down Timothy Baldwin's email address, as he may be able to interpret the above regards, - Niel From m-lists at biscuit.org.uk Tue Aug 5 11:55:01 2008 From: m-lists at biscuit.org.uk (Stuart Winter) Date: Tue, 5 Aug 2008 12:55:01 +0100 (BST) Subject: [armedslack] loadlin woes In-Reply-To: <4895C328.3060004@grumpytoad.org> References: <48803935.2070501@grumpytoad.org> <4880F004.1000808@grumpytoad.org> <4887A65E.9000601@grumpytoad.org> <4895C328.3060004@grumpytoad.org> Message-ID: > Everything seems to work as described, except the critical loadlin bootup step > :-| Tbh what I'd do is ask Peter Naulls directly. The version of Linloader I included with armedslack-11.0 was a slightly different version that worked for machines than had 1GB of RAM (although Linux only found 512). That *may* be the problem. I do not think that Peter was or is much of an upstream pusher, so his changes probably remained on his hard disk. > > any help is much appreciated.. I'm going to try hunting down Timothy Baldwin's > email address, as he may be able to interpret the above Tim is the author of the GRUB port to ARM which superceded Linloader. Last time I conversed with Tim (2 years ago) he did not have a Iyonix. Things may have changed though! From niel.drummond at grumpytoad.org Tue Aug 5 17:28:10 2008 From: niel.drummond at grumpytoad.org (Niel Drummond) Date: Tue, 05 Aug 2008 19:28:10 +0200 Subject: [armedslack] loadlin woes In-Reply-To: References: <48803935.2070501@grumpytoad.org> <4880F004.1000808@grumpytoad.org> <4887A65E.9000601@grumpytoad.org> <4895C328.3060004@grumpytoad.org> Message-ID: <48988DAA.90609@grumpytoad.org> Stuart Winter wrote: >> Everything seems to work as described, except the critical loadlin bootup step >> :-| >> > > Tbh what I'd do is ask Peter Naulls directly. > The version of Linloader I included with armedslack-11.0 was > a slightly different version that worked for machines than had > 1GB of RAM (although Linux only found 512). That *may* be > the problem. I do not think that Peter was or is much of > an upstream pusher, so his changes probably remained on his hard disk. > I have an answer from John Ballance @ castle - he says the 5200 graphics card shipped with the newer iyonix machines is the problem (they used to ship them with a geforce 2 card). That would explain the blank screen. Thanks for the tip though, I will email Peter Naulls. I had thought he might be a bit fed up with giving support, since many links on his site have been taken down. kind regards, - Niel > >> any help is much appreciated.. I'm going to try hunting down Timothy Baldwin's >> email address, as he may be able to interpret the above >> > > Tim is the author of the GRUB port to ARM which superceded > Linloader. Last time I conversed with Tim (2 years ago) he did > not have a Iyonix. Things may have changed though! > > >