I have an IBM Netvista n2800, which is originally used as a network client. There is neither floppy driver nor cd-rom in it. Right now it runs Debian 3.1 very well. May I use LinuxBios in this machine?
He uses Interl430TX, PIIX4E, Pentunm266MMX, with a SII 64k bios flash. Thanks in advance!
#69: Fix mptable util so the output will compile
Reporter: Jon Dufresne <jon.dufresne(a)gmail.com> | Owner: somebody
Type: defect | Status: new
Priority: major | Milestone:
Component: code | Version: v2
Keywords: | Dependencies:
Patchstatus: patch needs review |
I'm guessing the mptable util is using deprecated functions which is why
the output it gave me did not compile in my environment. I used
tyan/s2735/mptable.c as a guide for what the correct functions and headers
Ticket URL: <http://tracker.linuxbios.org/trac/LinuxBIOS/ticket/69>
I am working on the southbridge portion of my board. Currently I can
boot to a bash prompt, but my southbridge peripherals do not work. I
am taking a guess that this is a misconfiguration in APIC or ACPI,
however this is only a guess.
I've looked through a lot of other southbridges and mainboard to get
an idea about how to program this however I am still a bit confused.
I'm wondering if someone with more knowledge on this subject than I
would be willing to give me some advice.
Does it seem likely that ACPI or APIC misconfiguration would cause my
southbridge peripherals to not function?
Any clues as to how to go about programming these sections and how to
Am I suppose to set the IRQs for my devices explicitly myself or is
this taken care of somewhere in the code for me? Right now I am
setting them explicitly in i82801db_lpc.c, but whenever I modprobe a
device linux says "Disabling IRQ #11".
Thanks for any help. I'll attach my LinuxBIOS output and my linux output.
I'm looking at working on via vt82c686b for tyan s2507, and I'm
wondering what the best way to handle the differences between 686a and
686b is. The only difference I can see is a single PCI ID for ACPI.
Would it be better to use some sort of runtime detection for this single
PCI ID to differentiate, or seperate the two entirely? Also, should I
use the whole name of the chipset, vt82c686b, or just shorten it to
vt686b (which is commonly used by via)? BTW, I'm putting off i815 again,
because I can't get the test rig out of its current use.
1. is there any wok being done for supporting LinuxBIOS on IBM T60p ?
2. Can we estimate that LinuxBIOS can reduce boot time to 3 sec on such machine (as claimed in the homepage for other platforms)?
3. Can anyone share with me real results experienced on Intel x86 platforms?
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
Has there been any effort in getting flashrom to work with the
SST49LF008C, SST49LF016C or SST49LF160C parts?
I'm no expert on flash programming, but the datasheets seem to
indicate that the programming mode currently used in sst_fwhub.c is
not supported on these chips (the SST49LF040B datasheet calls this
"parallel" mode). There appears to be a completely different protocol
for programming LPC flash chips, but I haven't figured out how to
access this from a C program.
From: Vlad C. [mailto:firstname.lastname@example.org]
Sent: Friday, December 15, 2006 9:27 AM
>Any chance you could port LinuxBIOS to a motherboard based on plain
>nForce 570 or nForce 590 without SLI?
570 == mcp55
590 == mcp55 + c51
So 590 would be more expensive than 570 SLI.
Dear LinuxBIOS readers!
This is the automated build check service of LinuxBIOS.
The developer "stepan" checked in revision 2529 to
the LinuxBIOS source repository and caused the following
(Patch 2, refs #14)
Signed-off-by: Ed Swierk <eswierk(a)arastra.com>
Acked-by: Stefan Reinauer <stepan(a)coresystems.de>
Configuration of via:epia-m has been fixed
If something broke during this checkin please be a pain
in stepan's neck until the issue is fixed.
If this issue is not fixed within 24h the revision will
be backed out.
LinuxBIOS automatic build system