Eki Fa-Clang Shabazz wrote:
Start with this: http://linuxbios.org/Supported_Chipsets_and_Devices and
http://linuxbios.org/Supported_Motherboards. If you've still got
questions, respond with the output of lspci.
-Corey
Okay, I don't see mine. Sorry for the amount of stuff I'm sending, but:
Quoting [EMAIL PROTECTED]:
Hello,
I am working on the code for my northbridge (Intel 82830).
Particularly the raminit.c file. By looking at the sources from the
other northbridges and my datasheets, I am getting a little lost. My
datasheet (Intel) lists all the registers and their defaults
[EMAIL PROTECTED] wrote:
Quoting [EMAIL PROTECTED]:
Hello,
I am working on the code for my northbridge (Intel 82830).
Particularly the raminit.c file. By looking at the sources from the
other northbridges and my datasheets, I am getting a little lost. My
datasheet (Intel) lists all the
On Sat, Mar 03, 2007 at 03:45:18AM +0100, Peter Stuge wrote:
On Fri, Mar 02, 2007 at 04:05:08PM -0500, Ward Vandewege wrote:
For the record, the Biossavior RD1-PMC4 is not compatible with the
Gigabyte M57SLI-S4
Strange, it should work. Do you have any other LPC (not FWH) flash
chips to
On 19.03.2007 19:34, Ward Vandewege wrote:
On Thu, Mar 15, 2007 at 10:31:59AM -0700, Ed Swierk wrote:
Is there a patch with the remaining bits of Yinghai's MCP55 patch? I'm
bringing up an MCP55 board and this would be a good opportunity to try
to get the code working.
Same here - I'd like
On 3/19/07, Ward Vandewege [EMAIL PROTECTED] wrote:
Same here - I'd like to start working from the mainline tree. Uwe or Stefan,
any thoughts on what's still missing? I know it's the USB debug stuff, but
there
seem to be some other problems too - I just tried disabling the USB debug
Hi Ed,
Awesome - that works just fine for the M57SLI-S4. Still a lot of warnings,
but the code builds, and it boots the system just fine!
Thanks,
Ward.
On Mon, Mar 19, 2007 at 12:01:53PM -0700, Ed Swierk wrote:
Here's a patch with most of the remaining changes from the Yinghai
monster patch,
For MAC address:
1. make the flashrom util to take MAC address and GUUID as command
parameter.
2. use flashrom with excluding range to keep MAC address in the flash.
YH
--
linuxbios mailing list
linuxbios@linuxbios.org
http://www.linuxbios.org/mailman/listinfo/linuxbios
On 3/19/07, Ward Vandewege [EMAIL PROTECTED] wrote:
Awesome - that works just fine for the M57SLI-S4. Still a lot of warnings,
but the code builds, and it boots the system just fine!
That's good enough for me!
Signed-off-by: Ed Swierk [EMAIL PROTECTED]
--Ed
--
linuxbios mailing list
* Lu, Yinghai [EMAIL PROTECTED] [070319 21:04]:
For MAC address:
1. make the flashrom util to take MAC address and GUUID as command
parameter.
2. use flashrom with excluding range to keep MAC address in the flash.
where is it stored? Which area must stay untouched? I can add a .layout
file
Hi all,
My test machine has an Nvidia plugin card that I'm using with the free
software nv driver.
I've attached a diff between the Xorg.0.log file booted into the proprietary
BIOS, and into LinuxBIOS (Xorg.diff). These are the most interesting bits
(lines starting with + are LinuxBIOS):
I'm not sure on Legacy bios, ward could check that for you. But for LinuxBIOS,
I put them at last 16x3 bytes.
0xffd0
YH
-Original Message-
From: Stefan Reinauer [mailto:[EMAIL PROTECTED]
Sent: Monday, March 19, 2007 1:51 PM
To: Lu, Yinghai
Cc: Ward Vandewege; yhlu;
:00:01.3 0b40: 10de:036b (rev a2)
Is some IPMI processor, We could disable it but it doesn't hurt.
YH
--
linuxbios mailing list
linuxbios@linuxbios.org
http://www.linuxbios.org/mailman/listinfo/linuxbios
* Lu, Yinghai [EMAIL PROTECTED] [070319 21:57]:
I'm not sure on Legacy bios, ward could check that for you. But for
LinuxBIOS, I put them at last 16x3 bytes.
0xffd0
that would be 32 bytes, no? if it is 48 bytes, any changes to the reset
vector are not found. How big is the actual
16 bytes.
-Original Message-
From: Stefan Reinauer [mailto:[EMAIL PROTECTED]
Sent: Monday, March 19, 2007 2:08 PM
To: Lu, Yinghai
Cc: Ward Vandewege; yhlu; linuxbios@linuxbios.org
Subject: Re: [LinuxBIOS] trying to boot gigabyte m57sli-s4
* Lu, Yinghai [EMAIL PROTECTED] [070319 21:57]:
Hi everybody,
I'm new in the list !
I would like to know if I can install Linux Bios in my mother board ?
I take a look at: http://linuxbios.org/Supported_Motherboards
and my motherboard is not in.
My motherboard is P5T30-B4 TEKRAM: http://www.otasc.org/motherboard.log
So, here:
I've put up a build tutorial for the m57sli-s4 at
http://linuxbios.org/M57SLI-S4_Build_Tutorial
It's still based off of YH's big patch, but if Ed's patch from today gets
merged, I will update the tutorial to use the v2 tree.
Remaining issues are ACPI support, and the mac address changes (but
After successfully flashing the savior with the original bios using
awdflash, I got the same problem trying to flash the original chip with
flashrom.
Karl Erik
Peter Stuge wrote:
On Mon, Mar 19, 2007 at 10:50:02PM +0100, Karl Erik Asbjørnsen wrote:
Verifying flash address: 0x -
* Ward Vandewege [EMAIL PROTECTED] [070319 23:03]:
I've put up a build tutorial for the m57sli-s4 at
http://linuxbios.org/M57SLI-S4_Build_Tutorial
It's still based off of YH's big patch, but if Ed's patch from today gets
merged, I will update the tutorial to use the v2 tree.
Remaining
* Peter Stuge [EMAIL PROTECTED] [070319 23:32]:
On Mon, Mar 19, 2007 at 10:50:02PM +0100, Karl Erik Asbjørnsen wrote:
Verifying flash address: 0x - FAILED
Flashing the original bios to the bios savior did not work, so I
used awdflash instead. That worked fine.
awdflash could
On Mon, Mar 19, 2007 at 11:30:19PM +0100, Stefan Reinauer wrote:
* Peter Stuge [EMAIL PROTECTED] [070319 23:51]:
flashrom -w -s 0x3ffd0 -e 0x3ffdf image.rom
This is only for the case that a linuxbios image was previously
flashed.
Here image.rom is the factory BIOS, correct?
* Peter Stuge [EMAIL PROTECTED] [070319 23:59]:
it just ignores the 16 bytes at ffd0
Ok, sorry if I'm daft, but how does the MAC address end up in the
LinuxBIOS rom file?
Or, aha, did you mean This is only for the case that a factory image
was previously flashed. instead of the other
Let the flashrom take extra command parameter. MB should have MAC
address stick on the side.
YH
--
linuxbios mailing list
linuxbios@linuxbios.org
http://www.linuxbios.org/mailman/listinfo/linuxbios
On Mon, Mar 19, 2007 at 11:58:09PM +0100, Stefan Reinauer wrote:
* Determine that it's a transition from awardbios to linuxbios (safely)
* read the mac address (will it always be the same position for all
award bios updates in the future?)
Of course there is a bit more information that can
On Mon, Mar 19, 2007 at 04:02:19PM -0700, Lu, Yinghai wrote:
Let the flashrom take extra command parameter. MB should have MAC
address stick on the side.
Or it can be easily determined with ifconfig.
Yes, that's a great idea.
Thanks,
Ward.
--
Ward Vandewege [EMAIL PROTECTED]
Free Software
On Mon, Mar 19, 2007 at 04:02:19PM -0700, Lu, Yinghai wrote:
Let the flashrom take extra command parameter. MB should have MAC
address stick on the side.
Either that, or add a Config.lb option for the MAC since it will
always be the same for each board. Plus it only makes sense for
some
You will build rom for each MB if you have 10 or 100 same MB?
YH
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Peter Stuge
Sent: Monday, March 19, 2007 5:28 PM
To: linuxbios@linuxbios.org
Subject: Re: [LinuxBIOS] m57sli-s4 build tutorial
On Mon, Mar
Hi,
I noticed that there is a proposed Google Summer of Code project
(http://linuxbios.org/GSoC) to fork IDE drivers from the Linux kernel
and port them to Linux-independent boot managers like GRUB2. I dont
think this is a good design choice or a sustainable solution. There
are many different
On 3/18/07, Peter Stuge [EMAIL PROTECTED] wrote:
On Sun, Mar 18, 2007 at 08:54:29PM -0500, David H. Barr wrote:
[EMAIL PROTECTED]:~/msi_orig$ sudo flashrom -vV -c Pm49FL004 A7260NMS.300
Try -w
Well -MY- face is red; I forced the chip detection but failed explicitly to
invoke the write.
Does anyone know where (waht file) PCI_ADDR is defined?
Thanks - Joe
--
linuxbios mailing list
linuxbios@linuxbios.org
http://www.linuxbios.org/mailman/listinfo/linuxbios
Does anyone know where (waht file) PCI_ADDR is defined?
/src/arch/i386/include/arch/romcc_io.h
bxshi
--
linuxbios mailing list
linuxbios@linuxbios.org
http://www.linuxbios.org/mailman/listinfo/linuxbios
On Mon, Mar 19, 2007 at 02:10:25AM +0100, Peter Stuge wrote:
On Sun, Mar 18, 2007 at 06:25:30PM +0100, Stefan Reinauer wrote:
maybe it makes sense to port the openbios ide driver (ie clean
out the device tree hooks)?
Sounds good. Is the code structure a lot different?
Turns out it wasn't
On 3/19/07, Corey Osgood [EMAIL PROTECTED] wrote:
With pci_write_config32 (or pci_write_config16), do you send the value
to the first or the last register in the set? In other words, if it's a
range of 0x50-0x53, where should it be sent to? And if you were looking
to set it like this:
0x50 -
On 3/19/07, Vlad [EMAIL PROTECTED] wrote:
So, what do you guys think about a userspace boot manager stored in
the ROM?
I think it is inevitable. I think that the best boot loader is Linux.
We already showed how to do it on OLPC, but the size of the boot rom
(1 Mbyte) was too small. I think
ron minnich wrote:
On 3/19/07, Corey Osgood [EMAIL PROTECTED] wrote:
With pci_write_config32 (or pci_write_config16), do you send the value
to the first or the last register in the set? In other words, if it's a
range of 0x50-0x53, where should it be sent to? And if you were looking
to set it
35 matches
Mail list logo
