I second Stefan's response. I was so stubborn at first to try
This and then it helped me so much! So please try this or
Netconsole. I suspect your kernel could not mount the file
System you specified. If you try the above methods you should
See exactly what failed. I think...
FYI Netconsole link:
http://technocrat.net/article.pl?sid=04/08/14/0236245&mode=nested
-----Original Message-----
From: linuxbios-admin(a)clustermatic.org
[mailto:linuxbios-admin@clustermatic.org] On Behalf Of Stefan Reinauer
Sent: Tuesday, September 21, 2004 3:56 AM
To: Sagiv Yefet
Cc: linuxbios(a)clustermatic.org
Subject: Re: Boot problem
* Sagiv Yefet <sagivy(a)3vium.com> [040921 10:21]:
> I prepared a kernel elf file.
> The station is up and it loads the elf file.
> Then nothing happens.
> Just print something:
> Firmware: bios is Linuxbios
One note: It would be a lot easier to help you if you posted a bit of
context around your debug reports, like 2-3 lines of serial output
before the hang etc. Plus, just pasting the actual serial output is
easier to debug than writing error messages down from memory.
Detailed reports will give you higher quality and quicker answers.
> What can be the problem?
You did not specify to use serial console for your Linux kernel.
add something like "console=ttyS0,115200n8" to your command line.
Stefan
_______________________________________________
Linuxbios mailing list
Linuxbios(a)clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios
I prepared a kernel elf file.
The station is up and it loads the elf file.
Then nothing happens.
Just print something:
Firmware: bios is Linuxbios
What can be the problem?
Sagiv
It does. Etherboot can masquerade as PXE. Unless I'm missing something,
I'm not sure why you would want to do that since the DHCP server will send a
PXE image,
which then has to grab the kernel. Etherboot can just grab the whole thing
in one swoop.
David
Atlanta, GA
I'd look in src/arch/i386/lib/hardwaremain.c.
get_ramsize() in void hardwaremain() seems to be the culprit for RAM size. That's where I've been mucking about trying to do automatic memory sizing for the Epia M. I don't have any specs for the northbridge registers, so it's been slow going. I've been working from the spec sheets for an AMD 762 hoping to hit something. However, The 762 seems to conform better to standards. I also suspect an incorrect RAM size is causing the AGP GART setup code to crash the system both in LinuxBIOS and the AGP drivers in Linux. Good luck, and will somebody let me know when and where RAM sizing is working.
Hi,
I'm wondering if the epia-pd is already supported? From what I could
gather, it should not be different than the current epia-m board.
However, trying the epia-m code on the -pd results in a blank screen, no
serial, no beeps, no nothing. just a dead box.
So, either I missed something, or I did something wrong.
bye,
andreas
Hi,
I want to use the linuxbios on my epai-m board.
In the status page the support for this board is unstable.
Is it possible to reflash the board with the original software, if the
linuxbios doesn't work as aspected ?
I haven't got a flash programmer, so if the bios doesn't work, I can
throw the board out.
--
Gruß
Dieter
--
I do not get viruses because I do not use MS software.
If you use Outlook then please do not put my email address in your
address-book so that WHEN you get a virus it won't use my address in the
From field.
Hello,
I am trying to build the mkelfImage utility. I download the
mkelfImage-2.5.
configure and build. And I have the this error:
linux-i386/head.S: Assembler messages:
linux-i386/head.S:458: Error: junk at end of line, first unrecognized
character is `U'
where can I find a linux elf ?
thanks,
Sagiv
I get the message says:
The boot Image is not valid. (bzImage).
What it is expecting for ?
-----Original Message-----
From: YhLu [mailto:YhLu@tyan.com]
Sent: Wednesday, September 15, 2004 6:34 PM
To: Sagiv Yefet
Cc: Stefan Reinauer; linuxbios(a)clustermatic.org
Subject: RE: (fwd) RE: building romimage for tyan s2850 mainboard
[sagivy(a)3vium.com]
You can comment out dir /drivers/broadcom/tg3 too.
Current Etherboot has problem with NIC is S2850. I forget the chip
model.
So I use one add on card to do network booting. (intel eepro100)
Regards
YH
-----Original Message-----
From: Sagiv Yefet [mailto:sagivy@3vium.com]
Sent: Wednesday, September 15, 2004 4:53 AM
To: YhLu
Cc: Stefan Reinauer; linuxbios(a)clustermatic.org
Subject: RE: (fwd) RE: building romimage for tyan s2850 mainboard
[sagivy(a)3vium.com]
How can I had the broadcom NIC ?
When I comment out this in Config.lb (mainboard)?
dir /drivers/broadcom/tg3_ipmi
the buildtarget utility says it is not in the Sourcetree.
When I change this line to be:
dir /drivers/broadcom/tg3 (existing dir in the Sourcetree)
there is a make error.
I tried it with gcc-3.3.1 and gcc-3.3.2
I have binutils 2.15.
Did you ever succeed to build an image supporting broadcom NIC ?
Regards,
Sagiv
-----Original Message-----
From: YhLu [mailto:YhLu@tyan.com]
Sent: Tuesday, September 14, 2004 6:55 PM
To: Stefan Reinauer; linuxbios(a)clustermatic.org; Sagiv Yefet
Subject: RE: (fwd) RE: building romimage for tyan s2850 mainboard
[sagivy(a)3vium.com]
Sagiv,
I just sent you tar ball of my source code before I added S2895 and
S2735
support. Please check it out.
Regards
YH
-----Original Message-----
From: Stefan Reinauer [mailto:stepan@openbios.org]
Sent: Tuesday, September 14, 2004 7:29 AM
To: linuxbios(a)clustermatic.org; Sagiv Yefet
Subject: (fwd) RE: building romimage for tyan s2850 mainboard
[sagivy(a)3vium.com]
1) Please Cc the mailing list, there are many people who might help you
quicker/better than I do.
2) I don't understand your first question at all.
3) "invalid CMOS LB checksum" Means that the CMOS is not valid for
LinuxBIOS. Probably because you had a different firmware running
before LinuxBIOS in that machine. This error should go away
automatically after rebooting.
Stefan
----- Forwarded message from Sagiv Yefet <sagivy(a)3vium.com> -----
Date: Tue, 14 Sep 2004 16:41:46 +0200
From: "Sagiv Yefet" <sagivy(a)3vium.com>
To: "Stefan Reinauer" <stepan(a)openbios.org>
Subject: RE: building romimage for tyan s2850 mainboard
I comment out the:
#dir /drivers/ati/ragexl -- video
which pci line in the southbridge it relate to?
southbridge amd/amd8111 "amd8111" link 0
pci 0:0.0
pci 0:1.0 on
pci 0:1.1 on
pci 0:1.2 on
pci 0:1.3 on
pci 0:1.5 off
pci 0:1.6 off
pci 1:0.0 on
pci 1:0.1 on
pci 1:0.2 off
pci 1:1.0 off
end
what is this ERROR means ?
invalid CMOS LB checksum
Sagiv.
-----Original Message-----
From: Stefan Reinauer [mailto:stepan@openbios.org]
Sent: Tuesday, September 14, 2004 12:57 PM
To: Sagiv Yefet
Cc: linuxbios(a)clustermatic.org
Subject: Re: building romimage for tyan s2850 mainboard
* Sagiv Yefet <sagivy(a)3vium.com> [040914 12:43]:
> Thanks, it worked.
>
> There are 2 errors:
> 1. ERROR - could not find PCI 1:03.0, using defaults
This looks like an error in the mptable creation, but I am not
sure without the context here.
> 2. ERROR: PNP: 002e.b 70 not allocated
> in Config.lb: 002e.b = HW monitor
No idea. I always kind of guessed when fiddling with PnP configuration.
> what does it means?
Can anyone on the list give some details here?
Stefan
----- End forwarded message -----
_______________________________________________
Linuxbios mailing list
Linuxbios(a)clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios
I wanted to bring to attention Intel's Platform Innovation Framework for
Extensible Firmware Interface since its goals overlap with those LinuxBIOS a
little bit. After reading the article at
_http://www.linuxdevices.com/articles/AT3790951165.html_ (http://www.linuxdevices.com/articles/AT3790951165.html) ,
I had some
questions about the ability of LinuxBIOS to support next-generation
hardware. It looks like Intel wants to change the whole firmware landscape with
EFI. If such a framework will be truly open and support legacy systems, it'll
make LinuxBIOS redundant, wouldn't it? What about
newer architectures like those built around the Itanium? Will LinuxBIOS
be able to scale up as well as EFI? Those are questions that I wanted to
throw out there.
