hi all
I am soon to buy a new motherboard and I have narrowed my choice down to 2. I am very interested in the LinuxBios project and am eager to "have a go". My question is whihc of these two motherbords would be better to use for LinuxBios:
MS-7327 K9AGM2-FIH http://global.msi.com.tw/index.php?func=proddesc&maincat_no=1&cat2_no=&cat3…
or the
Abit AN-M2HD http://www.abit.com.tw/page/uk/motherboard/motherboard_detail.php?pMODEL_NA…
as you can tell I need the HDMI feature.
…
[View More]
Other information:
On both I will use the AMD Athlon X2 3800+ AM2 CPU
MS-7327
uses AMI BIOS
AMD 690G Northbridge and SB600 Southbridge
integrated ATi Radeon X1250 videocard
Realtek High Definition Audio Driver
ATI System Drivers for RS480/RS482/RC410/SB600
AMD HDMI Audio Drivers
Realtek 10/100 LAN Drivers
ATI SB600 IDE RAID Driver
Realtek Gigabit Ethernet Drivers
from the photos it looks like this uses ??? its nt clear DIP BIOS???
Abit AN-M2HD
NVIDIA® GeForce®7050PV/nForce 630a
from the pictures i think this uses a PLCC: Plastic Leaded Chip Carrier
this is about all i have to go on. Any pointers would be great.
tia
mike
[View Less]
Hi,
Here's a one patch for IEI JUKI-511P and IEI ROCKY-512 half-size boards.
This boards are little difference, that's why it has one patch.
Linux with patchs from Juergen Beisert
(http://www.linuxbios.org/pipermail/linuxbios/2007-May/020932.html)
boots and work fine(ide, usb, ethernet, serial, keyboard and sound
work normally).
Problems:
Filo load bzImage only from ide0.
Video don't work, no any monitor output.
JUKI-511P – PCISA half–size board:
Specification:
CPU: Geode GX1 300Mhz
System …
[View More]Chipset: cs5530
SuperIO: Winbond w83977f-a
Ethernet: rtl8100B
Memory: one DIMM
AC97: AD1881
ROCKY-512 – ISA half–size board:
Specification:
CPU: Geode GX1 300Mhz
System Chipset: cs5530
SuperIO: Winbond w83977f-a
Ethernet: rtl8100B
Memory: 64MB on board and one DIMM
AC97: no sound chip
Here's also dmesg output.
--
Nikolay
[View Less]
Author: uwe
Date: 2007-06-03 01:55:17 +0200 (Sun, 03 Jun 2007)
New Revision: 2706
Modified:
trunk/LinuxBIOSv2/src/southbridge/amd/cs5536/cs5536.c
Log:
The UART disable code was causing a hang and was worked around with a
return that skipped the disable code. This patch removes the return and
fixes the UART disable code.
The problem was that the disable code was ORing bits into the Legacy_IO
MSR causing issues with the LPC SIOs init code that would manifest as a
hang because the IO would …
[View More]not be decoded correctly. ANDing to clear the
bits fixes the issue.
Signed-off-by: Marc Jones <marc.jones(a)amd.com>
Acked-by: Ronald G. Minnich <rminnich(a)gmail.com>
Acked-by: Uwe Hermann <uwe(a)hermann-uwe.de>
Modified: trunk/LinuxBIOSv2/src/southbridge/amd/cs5536/cs5536.c
===================================================================
--- trunk/LinuxBIOSv2/src/southbridge/amd/cs5536/cs5536.c 2007-05-29 19:26:37 UTC (rev 2705)
+++ trunk/LinuxBIOSv2/src/southbridge/amd/cs5536/cs5536.c 2007-06-02 23:55:17 UTC (rev 2706)
@@ -316,9 +316,6 @@
} else {
/* Reset and disable COM1 */
- printk_err("Not disabling COM1 due to a bug ...\n");
- /* for now, don't do this! */
- return;
msr = rdmsr(MDD_UART1_CONF);
msr.lo = 1; // reset
wrmsr(MDD_UART1_CONF, msr);
@@ -327,7 +324,7 @@
/* Disable the IRQ */
msr = rdmsr(MDD_LEG_IO);
- msr.lo |= ~(0xF << 16);
+ msr.lo &= ~(0xF << 16);
wrmsr(MDD_LEG_IO, msr);
}
@@ -391,7 +388,7 @@
/* Disable the IRQ */
msr = rdmsr(MDD_LEG_IO);
- msr.lo |= ~(0xF << 20);
+ msr.lo &= ~(0xF << 20);
wrmsr(MDD_LEG_IO, msr);
}
}
[View Less]
Hi,
here's a patch for v3 which reworks the payload selection in
'make menuconfig'. After the patch there are two simple options you
can use:
- Payload file
You specify a path and filename for the payload.
Default: payload.elf in the current directory.
_How_ you create this payload does not matter; manual building,
using a pre-built image from somewhere, using buildrom or lbdistro
to create one etc. etc.
- No payload
This will create an "empty" image without any …
[View More]payload. You can later
add a payload from the command line using the 'lar' utility.
Something like 'lar add payload.elf linuxbios.rom' will add it...
This is useful for multiple purposes:
- Other "payload-projects" such as GNUFI or Open Firmware etc. can
use LinuxBIOS as low-level bootstrap and incorporate LinuxBIOS
in their own build process. They use the "empty" LinuxBIOS image
as a base and use 'lar' to insert their own GNUFI / OFW / whatever
image.
- Linux distributions can ship 'linuxbios' packages which come with
/usr/bin/lar and "empty" pre-built images for all supported
mainboards somewhere in /usr/share, e.g.
/usr/share/linuxbios/images/lb_empty_asus_a8n_e.rom
/usr/share/linuxbios/images/lb_empty_tyan_s2882.rom
/usr/share/linuxbios/images/lb_empty_gigabyte_ga_6bxc_256k.rom
/usr/share/linuxbios/images/lb_empty_gigabyte_ga_6bxc_512k.rom
etc.
The user can then use those pre-built images and the 'lar' tool
to insert any desired payload into the "final" image before
flashing it.
Heck, the distributions could even ship default payloads in
/usr/share/linuxbios/payloads.
We definately need some more discussion on the payload handling, but I
think this patch is a good start. This system is flexible enough to
manage any use case you can imagine, IMO.
I documented the proposed procedure in the README in the patch, comments
welcome.
Uwe.
--
http://www.hermann-uwe.de | http://www.holsham-traders.dehttp://www.crazy-hacks.org | http://www.unmaintained-free-software.org
[View Less]