Good idea.
-----Original Message-----
From: Takeshi Sone [mailto:ts1@tsn.or.jp]
Sent: Monday, July 12, 2004 6:56 PM
To: David Aubin
Cc: YhLu; Hendricks David W.; ron minnich; LinuxBIOS
Subject: Re: Filo Error Help
Can you try out my FILO? (http://te.to/~ts1/filo/)
If it works, it might help narrow the problem.
On Mon, Jul 12, 2004 at 05:14:39PM -0400, David Aubin wrote:
> Here are the results:
>
> I took my known working hard drive and stuck it in the device to test
> with filo.
> The results were the same! Meaning a known working kernel & intird on
> my hard drive failed at the initrd portion, again with the crc error.
>
> I'm now going to try a basic etherboot test without filo to see if I can
> read off of the
> hard drive, just as a baseline.
>
> Any other ideas would be appreciated.
>
> Thanks,
> Dave
>
> On Mon, 2004-07-12 at 16:01, YhLu wrote:
>
> > I mean if you build tg3?filo?ide_disk.zelf, it will confuse the
> > Etherboot. So you can only build tg3?filo.zelf or tg3?ide_disk.zelf.
> >
> >
> >
> > Do you have spare IDE disk? If So format the disk into ext3 or fat
> > format and copy the .elf file into it.
> >
> >
> >
> > Then connect that to your MB do test.
> >
> >
> >
> > hda1:/ram0_......elf
> >
> >
> >
> > Regards
> >
> >
> >
> > YH
> >
> >
> >
> >
> > ______________________________________________________________________
> >
> > From:David Aubin [mailto:daubin@actuality-systems.com]
> > Sent: Monday, July 12, 2004 12:50 PM
> > To: YhLu
> > Cc: Hendricks David W.; ron minnich; LinuxBIOS
> > Subject: RE: Filo Error Help
> >
> >
> >
> >
> > Hi,
> >
> > I am unable to get my kernel & initrd off of the usb stick. I was
> > reading
> > through the documents and came across this line in
> > README.etherboot_in_filo:
> > You can not use filo and ide_disk at the same time.
> >
> > Can you tell me what this means? Do I need to rebuild filo without
> > IDE
> > support to get USB support?
> >
> > Just to recap: My kernel & initrd fails as the initrd execution
> > complaining of
> > a bad CRC when I use the elf as a payload to load with with filo. I
> > then try
> > uda1:/kernel initrd=/boot/initrd root=/dev/sda1 and I get those td
> > errors. I then
> > tried your ramfs.elf and I get the same behavior are my elf image with
> > the CRC
> > complaining when the initrd portion is executed. Note, I have
> > confirmed my elf
> > works with etherboot, just not filo yet....
> >
> > The CRC error makes me think that the image did not get loaded
> > correctly
> > by the elf boot. Can you confirm you used Eric's mkelfImage2-5? Here
> > is
> > my dump of the readelf -a.
> >
> > ELF Header:
> > Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00
> > Class: ELF32
> > Data: 2's complement, little endian
> > Version: 1 (current)
> > OS/ABI: UNIX - System V
> > ABI Version: 0
> > Type: EXEC (Executable file)
> > Machine: Intel 80386
> > Version: 0x1
> > Entry point address: 0x10000
> > Start of program headers: 52 (bytes into file)
> > Start of section headers: 0 (bytes into file)
> > Flags: 0x0
> > Size of this header: 52 (bytes)
> > Size of program headers: 32 (bytes)
> > Number of program headers: 5
> > Size of section headers: 0 (bytes)
> > Number of section headers: 0
> > Section header string table index: 0
> >
> > There are no sections in this file.
> >
> > Program Headers:
> > Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg
> > Align
> > NOTE 0x0000d4 0x00000000 0x00000000 0x00088 0x00088 RWE 0
> > LOAD 0x00015c 0x00010000 0x00010000 0x0559c 0x1aa24 RWE 0
> > LOAD 0x0056f8 0x00091000 0x00091000 0x00000 0x00070 RWE 0
> > LOAD 0x0056f8 0x00100000 0x00100000 0x1a952a 0x700000 RWE
> > 0
> > LOAD 0x1aec22 0x00800000 0x00800000 0x2769f5 0x2769f5 RWE
> > 0
> >
> > There is no dynamic segment in this file.
> >
> > There are no relocations in this file.
> >
> > There are no unwind sections in this file.
> >
> > No version information found in this file.
> >
> >
> > Thanks,
> > Dave
> >
> > On Fri, 2004-07-09 at 15:48, YhLu wrote:
> >
> > I have got two cpus and four dimms for every CPU.
> >
> >
> >
> > YH
> >
> >
> >
> >
> > ______________________________________________________________________
> >
> >
> >
> > From:David Aubin [mailto:daubin@actuality-systems.com]
> > Sent: Friday, July 09, 2004 12:07 PM
> > To: YhLu
> > Cc: Hendricks David W.; ron minnich; LinuxBIOS
> > Subject: RE: Filo Error Help
> >
> >
> >
> >
> > Hi,
> >
> > Yes, I did, but I don't have a DHCP environment so it kept searching
> > at the DHCP phase.
> >
> > This problem is odd. I can boot my elf fine with etherboot, but not
> > with filo. I can boot
> > my kernel fine with filo, but not the initrd. I can even boot your
> > kernel of the ram.elf you
> > sent me, but when it hits the initrd it fails with the same error as
> > mine.
> >
> > I suspect either my filo is not configured like yours or that there
> > is a problem loading a
> > mulitpart elf (kernel & initrd in filo). I'm confused as to why filo
> > didn't just use the etherboot
> > portion of elf_load. It could be you were on the, "bleeding" edge?
> > ;)
> >
> > Can you tell me how much memory you have in your working system? I
> > have just
> > one cpu and 512meg memory. Curious if loading it high & it runs out
> > of memory or
> > something like that.
> >
> > Thanks,
> > Dave
> >
> >
> > On Fri, 2004-07-09 at 13:05, YhLu wrote:
> >
> >
> > Did you try the tg3--filo.zelf I sent to you?
> >
> > YH
--
Takeshi
I have got two cpus and four dimms for every CPU.
YH
_____
From: David Aubin [mailto:daubin@actuality-systems.com]
Sent: Friday, July 09, 2004 12:07 PM
To: YhLu
Cc: Hendricks David W.; ron minnich; LinuxBIOS
Subject: RE: Filo Error Help
Hi,
Yes, I did, but I don't have a DHCP environment so it kept searching at
the DHCP phase.
This problem is odd. I can boot my elf fine with etherboot, but not with
filo. I can boot
my kernel fine with filo, but not the initrd. I can even boot your kernel
of the ram.elf you
sent me, but when it hits the initrd it fails with the same error as mine.
I suspect either my filo is not configured like yours or that there is a
problem loading a
mulitpart elf (kernel & initrd in filo). I'm confused as to why filo didn't
just use the etherboot
portion of elf_load. It could be you were on the, "bleeding" edge? ;)
Can you tell me how much memory you have in your working system? I have
just
one cpu and 512meg memory. Curious if loading it high & it runs out of
memory or
something like that.
Thanks,
Dave
On Fri, 2004-07-09 at 13:05, YhLu wrote:
Did you try the tg3--filo.zelf I sent to you?
YH
Hi,
Thanks for everyone who helped me building the LinuxBIOS V2 on epia board.
I fixed two problems during trying to use FILO to boot a kernel in hard
disk.
1) One memory module is broken. I did not use memtest86. It takes too long
time. I just remove a very old memory module, the filo can reach the last
step.
2) hard disk should be set as MASTER. It has been set as slave. So I got
error message: no IDE dev at channel 0.
Right now the booting of kernel stopps at initialize AGP stuff, following
is the error message before the kernel crashes:
********************************************
Initializing Cryptographic API
Real Time Clock Driver v1.12
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected VIA Apollo MVP4 chipset
agpgart: Maximum main memory to use for agp memory: 96M
0
LinuxBIOS-1.1.6.0Fallback Fri Jul 9 14:06:03 PDT 2004 starting...
***********************************************
I have several questions:
1) DO i need to enable GP_APERTURE_SIZE?
And how to set the value? (i.e. by byte or M )
2) Does the kernel need patch? Right now, I am using 2.6.7 pure kernel.
Thanks a lot.
Simon Cheng
www.msica.com
I wonder if it is after gzip or before gzip.
-----Original Message-----
From: ron minnich [mailto:rminnich@lanl.gov]
Sent: Thursday, July 08, 2004 2:44 PM
To: David Aubin
Cc: YhLu; LinuxBIOS
Subject: RE: Filo Error Help
On Thu, 8 Jul 2004, David Aubin wrote:
> If so could it be a size issue? My initrd is 8Meg.
oh!
did you config the kernel for that? default is 4M.
ron
What is the current state of the EPIA port? I am interested in
running LinuxBIOS on a EPIA PD 10000 (as soon as I can find a supplier
in the States). Can X be run via the on-board VGA (as apposed to the
LVDS).
--adam
I could send you my elf, but it is about 6Mb.
YH
-----Original Message-----
From: ron minnich [mailto:rminnich@lanl.gov]
Sent: Thursday, July 08, 2004 2:42 PM
To: David Aubin
Cc: YhLu; LinuxBIOS
Subject: Re: Filo Error Help
On Thu, 8 Jul 2004, David Aubin wrote:
> RAMDISK: Compressed image found at block 0
well if found the image ...
> invalid compressed format (err=2)
this is odd. you've got linux up, and it found an image, but it seems
busted. Are you certain this initrd is ok? You could try booting the
kernel and initrd on a known-good system to make sure the initrd is right.
Do you have the right VFS for the initrd build into the kernel?
ron
1. which MB? Which USB stick
2. please try .elf at first. It would be
uda1:/ram0_2.5_2.6.5_k8.2_mydisk7.elf
format your usb disk with FAT or ext2, because it seems reiserfs
driver has some problem, and it will not work after abnormal shutdown.
3. I guess td is not be freed right after use.
Regards
YH
The hardwaremain become more tidy.
How about the progress about the romcc? I hope I can enable debug info while
include all ati support stuff.
Regards
YH
-----邮件原件-----
发件人: ebiederman(a)lnxi.com [mailto:ebiederman@lnxi.com]
发送时间: 2004年7月7日 21:03
收件人: LinuxBIOS
抄送: YhLu; ron minnich; Stefan Reinauer
主题: Re: CPU refactoring status....
ebiederman(a)lnxi.com (Eric W. Biederman) writes:
> The next big task is to get make the SMP cpu initialization methods
> normal device tree methods. I have everything ready to do that
> except I need a good way to get the information in the struct
> mem_range array by sizeram(). My gut feel is that I want to
> incorporate the sizeram functionality into the resource allocator,
Moving sizeram into read_resources/set_resources comes out fairly
clean, but it did require some grunt work.
That has allowed me to sort out the device tree and have a fairly
generic method of initializing cpus. Cpus don't fit into device
model methods as nicely as I would like (largely because their
methods have to run on the cpu in question). But it does work
well enough I can remove the special case from hardwaremain.
I still have a special case in the root_device methods but
that can be overridden, if necessary.
Because I have restructured where things fall in the device tree.
Because I have removed the sizeram call.
Because I have refactored x86 cpu handling.
Because I have removed the array initial_apic_id.
Every port in the tree is likely to break when I check this code in.
I have the arima/hdama working and I can with a little care
fix up the k8 based ports.
I can also likely fixup the recent e7501 forward port from the
freebios tree.
However beyond that I don't have testing resources to fix things up
so I am looking for some feedback before I break everything.
When in the next week or so is a good time?
Does any one have concerns about this set of changes?
I have attached my current version of hardwaremain below
to give a feel of what the changes look like.
Ok now I am off to bed. Before I commit anything I am going to let
the code sit a little.
Good Night,
Eric
/*
* C Bootstrap code for the LinuxBIOS
*/
#include <console/console.h>
#include <mem.h>
#include <version.h>
#include <boot/tables.h>
#include <device/device.h>
#include <device/pci.h>
#include <device/chip.h>
#include <delay.h>
#include <stdlib.h>
#include <part/hard_reset.h>
#include <boot/elf.h>
void hardwaremain(int boot_complete)
{
/* the order here is a bit tricky. We don't want to do much of
* anything that uses config registers until after
PciAllocateResources
* since that function also figures out what kind of config strategy
* to use (type 1 or type 2).
* so we turn on cache, then worry about PCI setup, then do other
* things, so that the other work can use the PciRead* and PciWrite*
* functions.
*/
struct lb_memory *lb_mem;
post_code(0x80);
CONFIGURE(CONF_PASS_PRE_CONSOLE);
/* displayinit MUST PRECEDE ALL PRINTK! */
console_init();
post_code(0x39);
printk_notice("LinuxBIOS-%s%s %s %s...\n",
linuxbios_version, linuxbios_extra_version, linuxbios_build,
(boot_complete)?"rebooting":"booting");
post_code(0x40);
/* If we have already booted attempt a hard reboot */
if (boot_complete) {
hard_reset();
}
init_timer(); /* needs to be moved into static configuration */
CONFIGURE(CONF_PASS_PRE_PCI);
/* pick how to scan the bus. This is first so we can get at memory
size. */
printk_info("Finding PCI configuration type.\n");
pci_set_method();
post_code(0x5f);
enumerate_static_devices();
dev_enumerate();
post_code(0x66);
/* Now do the real bus.
* We round the total ram up a lot for thing like the SISFB, which
* shares high memory with the CPU.
*/
dev_configure();
post_code(0x88);
dev_enable();
dev_initialize();
post_code(0x89);
CONFIGURE(CONF_PASS_POST_PCI);
/* Now that we have collected all of our information
* write our configuration tables.
*/
lb_mem = write_tables();
CONFIGURE(CONF_PASS_PRE_BOOT);
elfboot(lb_mem);
}
How about the size of the elf?
YH
-----Original Message-----
From: David Aubin [mailto:daubin@actuality-systems.com]
Sent: Thursday, July 08, 2004 2:27 PM
To: YhLu
Cc: LinuxBIOS
Subject: RE: Filo Error Help
Hi,
1. I'm using a S2885 chipset motherboard by Tyan;) I'm using a
Kingston 2.0 stick.
2. At the bottom of my original post I mention I did the elf as well.
Did your elf include an initrd?
If so could it be a size issue? My initrd is 8Meg.
3. Can you point me as to how to remedy this?
Thanks,
Dave
On Thu, 2004-07-08 at 17:25, David Aubin wrote:
> On Thu, 2004-07-08 at 17:11, YhLu wrote:
> > 1. which MB? Which USB stick
> > 2. please try .elf at first. It would be
> > uda1:/ram0_2.5_2.6.5_k8.2_mydisk7.elf
> > format your usb disk with FAT or ext2, because it seems reiserfs
> > driver has some problem, and it will not work after abnormal shutdown.
> > 3. I guess td is not be freed right after use.
> >
> > Regards
> >
> > YH
>
> Hi,
>
> 1. I'm using a S2885 chipset motherboard by Tyan;) I'm using a
> Kingston 2.0 stick.
> 2. At the bottom of my original post I mention I did the elf as
> well. Did your elf include an initrd?
> If so could it be a size issue? My initrd is 8Meg.
> 3. Can you point me as to how to remedy this?
>
> Thanks,
> Dave
>
