> On Wed, Aug 03, 2005 at 11:59:20AM +0900, Jun OKAJIMA wrote:
> > Probably, most guys here use BIOS Saver.
> > And it works well?
> > In mine, RD1 for PLCC gets not being writable suddenly.
> > I mean, it seems writable but # flash_rom -v fails.
> > I solved this problem by a quick hack.
> >
> > How about yours? You can write RD1 or W49F002U well?
> > Any problem happen?
Johnathan McDowell wrote:
> Even after that it's sometimes a bit …
[View More]flakey and I have to erase, then
> write it. I've put the board's original BIOS in the RD1 and am writing
> to the SST 39SF020A instead, which works without problems.
I've read posts about the RD1 that suggest its integrated flash device
is low quality and it may take 10 or more flash attempts to get a good
flash update to the RD1 flash device.
As a result, many RD1 BIOS Savior users will flash the commercial
BIOS image (or other known good BIOS image) into the RD1 integrated
flash device as many times as needed to get an image that boots.
Then use the original BIOS device to flash test BIOS image (usually
LinuxBIOS images among this group), since the original BIOS device
usually flashes OK on the first attempt.
I've used the RD1 in the above fashion with great success on the
Tyan S2885 mainboard.
The same RD1 would not work on the nVidia CK8-04 CRB mainboard.
I think the CK8-04 CRB requires a flash device that the RD1 does
not support. However, the RD1 worked well as an "do nothing" adapter
which allowed swapping the BIOS flash device between my flash burner
and the mainboard without any wear to the mainboard's BIOS socket.
BTW, my flash burner is an older Enhanced Willem Universal Programmer.
I got mine for only $60 US over a year ago. I've seen it for less
than $40 on eBay a few weeks ago. The newest model is going for about
$50 US. It does a LinuxBIOS flash in about 5 minutes; not bad for a
$60 burner. However, it does require changing DIP switches to match
an image for each device it can program. Great for the amateur or
professional with a small budget.
> > BTW, a cable of your RD1 is not broken?
> > I needed soldering to fix it.
> Mine was fine out of the box.
Mine cable and switch worked fine out of the box as well.
Sincerely,
Ken Fuchs <kfuchs(a)winternet.com> ami-mac-sun
[View Less]
yhlu wrote:
> then how about the lines for 7z uncompress code?
>
> YH
Working on it. 7z decompressor is really small (8 kb compiled on
i386) and written in ISO C (1884 lines of code), but compressor is
big and written in C++.
Does it still make sense to try to use 7z?
How much RAM is the decompressor allowed to use?
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
I have inited the hw sensors in LinuxBIOS for s2881. So you could use
lmsensor to check the FAN speed. The config file is on Tyan web.
For the Fan control, there should more some reg setting...to reduce the
FAN speed winbond and adm1027...
YH
No. It seems there is one MB need to set..., I forget the model...
But amd chipset base MB should be ok to comment that out...
YH
-----Original Message-----
From: Stefan Reinauer [mailto:stepan@coresystems.de]
Sent: Thursday, May 11, 2006 10:01 AM
To: Lu, Yinghai
Cc: vincentetsou(a)nexcom.com.tw; linuxbios(a)linuxbios.org
Subject: Re: [LinuxBIOS] New guy in LinuxBios
* Lu, Yinghai <yinghai.lu(a)amd.com> [060511 18:32]:
> Comment out several lines about links in resourcemap.c.
Can …
[View More]we just comment this out? Or would we need to put the link number in
the registers before writing?
--
coresystems GmbH * Brahmsstr. 16 * D-79104 Freiburg i. Br.
Tel.: +49 761 7668825 * Fax: +49 761 7664613
Email: info(a)coresystems.de * http://www.coresystems.de/
[View Less]
The support code is done, and will be released to public tree after the
CPU is released to public.
YH
-----Original Message-----
From: linuxbios-bounces(a)linuxbios.org
[mailto:linuxbios-bounces@linuxbios.org] On Behalf Of Carl-Daniel
Hailfinger
Sent: Wednesday, April 19, 2006 4:35 PM
To: linuxbios(a)linuxbios.org
Subject: [LinuxBIOS] Support for AM2 processors?
Hi,
since the upcoming AM2 processors will have a new (DDR2)
memory controller, does that mean the RAM initialization
has to be …
[View More]rewritten completely? If so, is there any expected
time when LinuxBIOS support for these processors will be
available?
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
--
linuxbios mailing list
linuxbios(a)linuxbios.org
http://www.openbios.org/mailman/listinfo/linuxbios
[View Less]
I used the stock FC4 kernel with the same command line as you used. My
autoboot was just hdb1:/linux_2.6.16.elf (I have a CD-ROM as hda)
Good luck,
Myles
-----Original Message-----
From: linuxbios-bounces(a)linuxbios.org
[mailto:linuxbios-bounces@linuxbios.org] On Behalf Of Per Mellander
Sent: Wednesday, May 31, 2006 6:53 AM
To: myles(a)mouselemur.cs.byu.edu
Cc: linuxbios(a)linuxbios.org
Subject: Re: [LinuxBIOS] EPIA-MII 12000, almost there. ( newbie )
Now I get so far that the kernel is …
[View More]identified and loaded but then it breaks
:(
I created an elf with mkelfImage:
# mkelfImage --kernel=/vmlinuz-2.6.16-1.2111_FC5 --output=/vmlinuz.elf
--initrd=/initrd-2.6.16-1.2111_FC5.img --command-line="ro root=LABEL=/ rhgb
quiet
console=ttyS0 console=ttyS0,115200"
----8<-------------------------------------------------------------
Jumping to boot code at 0x109ad4
FILO version 0.5 (root(a)mm.int.mmtab.se) Wed May 31 13:44:15 CEST 2006
Press <Enter> for default boot, or <Esc> for boot prompt... timed out
boot: hda1:/vmlinuz.elf
find_ide_controller: found PCI IDE controller 1106:0571 prog_if=0x8a
find_ide_controller: primary channel: compatibility mode
find_ide_controller: cmd_base=0x1f0 ctrl_base=0x3f4
ide_software_reset: Waiting for ide0 to become ready for reset... ok
init_drive: Testing for hda
init_drive: Probing for hda
init_drive: LBA mode, sectors=268435455
init_drive: LBA48 mode, sectors=321672960
init_drive: Init device params... ok
hda: LBA48 164GB: HDS722516VLAT80
Mounted ext2fs
Loading Linux version 2.6.16-1.2111_FC5
(bhcompile(a)hs20-bc1-3.build.redhat.com) #1 Thu
May 4 21:16:58 EDT 2006...
Jumping to entry point...
0
LinuxBIOS-1.1.8.0Fallback Wed May 31 13:15:25 CEST 2006 starting...
Enabling mainboard devices
Enabling shadow ram
----8<-------------------------------------------------------------
I get the same result when I try,
AUTOBOOT_FILE = "hda1:/vmlinuz initrd=/initrd.img root=/dev/hda1
console=tty0
console=ttyS0,115200"
so the problem is not in the elf image.
Could you please send me a snippet from your AUTOBOOT or similar?
Btw. Do I have to make a 'special' kernel to make this work or should the
stock FC5 work?
/Per
On Tue, 30 May 2006 08:38:53 -0600, Myles Watson wrote
> Did you try using mkelfImage from ftp://ftp.lnxi.com/pub/mkelfImage ? It
> combines the vmlinuz & initrd files into one.
>
> To get my machine to boot I used the same kernel parameters as I found in
> grub, set up by Fedora.
>
--
linuxbios mailing list
linuxbios(a)linuxbios.org
http://www.openbios.org/mailman/listinfo/linuxbios
[View Less]
As you know, we've said we were going to have a developer's program. You
can find more information, including how to apply for boards at:
http://wiki.laptop.org/index.php/Developers_Program
Note that these are bare PC prototype boards, not packaged machines.
Jim Gettys
--
Jim Gettys
One Laptop Per Child
Hi list.
I've been trying to get LinuxBIOS going on my EPIA-MII 12000 system. I've read numerous
messages on the ML and Googling for answers. Still I can't get my system to boot properly.
Following the HOWTO I've managed to create a linuxbios.rom that actually boots, starts
the payload ( filo ) but then I don't get the kernel to load.
I'm using LinuxBIOS snapshot as of 24th of May and Filo 0.5. The VGA-rom is extracted with:
dd if=/dev/mem of=/video.bios.bin bs=65536 count=1 skip=12
My …
[View More]root is /dev/hdb1 and I've put my ( working ) kernel at /vmlinuz. ( It's a stock
Fedora 5 kernel, 2.6.16-1.2111_FC5. )
When I use USE_GRUB = 1 and put a copy of my menu.lst in /boot/filo/menu.lst, I only
get a grub prompt and when trying to manually load the kernel with:
kernel /vmlinuz
root=/dev/hdb1
boot
It complains about unknown filetype, IIRC.
I've also tried using:
AUTOBOOT_FILE = "hdb1:/vmlinuz root=/dev/hdb1 console=tty0 console=ttyS0,115200"
With this I get the LinuxBIOS to constantly restart.
My actual question is therefore If there is anyone with a working setup that could
please give me some help?
[View Less]
I'm experiencing problem with the flashrom utility. I have a BIOS SAVIOUR RD1-PL, and at
start it worked quite alright. I was able to flash the prom that's located on the RD1
and tried different settings in my LinuxBIOS. I was on the other hand not able to read
the contents out of the original BIOS because it was not detected properly. I have an
EPIA-MII 12000 with BIOS ver 1.35 ( bought it recently so it's quite new. ) The fact
that I couldn't read the original BIOS didn't on the other hand …
[View More]keep me from flashing
the part on the RD1.
The big problem now is that I'm not able to erase the flash anymore, making it quite
hard to continue developing my LinuxBIOS.
# flashrom -E'
Calibrating delay loop... ok
No LinuxBIOS table found.
Enabling flash write on VT8235...OK
W49F002U found at physical address: 0xfffc0000
Flash part is W49F002U
Erasing flash chip
but when I read it back it's not empty.
# flashrom -r test.bin
Calibrating delay loop... ok
No LinuxBIOS table found.
Enabling flash write on VT8235...OK
W49F002U found at physical address: 0xfffc0000
Flash part is W49F002U
Reading Flash...done
# hexdump test.bin | head -1
0000000 aa55 e970 7ffc 1b8b de34 83ca 0000 0000
# flashrom -E -V
Calibrating delay loop... Setting up microsecond timing loop
170M loops per second
ok
No LinuxBIOS table found.
Enabling flash write on VT8235...OK
Trying Am29F040B, 512 KB
probe_29f040b: id1 0xff, id2 0xff
Trying Am29F016D, 2048 KB
probe_29f040b: id1 0xff, id2 0xff
Trying At29C040A, 512 KB
probe_jedec: id1 0xff, id2 0xff
Trying Mx29f002, 256 KB
probe_29f002: id1 0xda, id2 0xb
Trying SST29EE020A, 256 KB
probe_jedec: id1 0xda, id2 0xb
Trying SST28SF040A, 512 KB
probe_28sf040: id1 0xff, id2 0xff
Trying SST39SF020A, 256 KB
probe_jedec: id1 0xda, id2 0xb
Trying SST39VF020, 256 KB
probe_jedec: id1 0xda, id2 0xb
Trying SST49LF040B, 512 KB
probe_jedec: id1 0xff, id2 0xff
Trying SST49LF040, 512 KB
probe_jedec: id1 0xff, id2 0xff
Trying SST49LF080A, 1024 KB
probe_jedec: id1 0xff, id2 0xff
Trying SST49LF002A/B, 256 KB
probe_jedec: id1 0xda, id2 0xb
Trying SST49LF003A/B, 384 KB
probe_jedec: id1 0xff, id2 0xff
Trying SST49LF004A/B, 512 KB
probe_jedec: id1 0xff, id2 0xff
Trying SST49LF008A, 1024 KB
probe_jedec: id1 0xff, id2 0xff
Trying Pm49FL004, 512 KB
probe_jedec: id1 0xff, id2 0xff
Trying W29C011, 128 KB
probe_jedec: id1 0xda, id2 0xb
Trying W29C020C, 256 KB
probe_jedec: id1 0x55, id2 0xaa
Trying W49F002U, 256 KB
probe_jedec: id1 0x55, id2 0xaa
Trying W39V040A, 512 KB
probe_jedec: id1 0xff, id2 0xff
Trying M29F040B, 512 KB
probe_29f040b: id1 0xff, id2 0xff
Trying M29F400BT, 512 KB
probe_m29f400bt: id1 0xff, id2 0xff
Trying 82802ab, 512 KB
probe_82802ab: id1 0xff, id2 0xff
Trying 82802ac, 1024 KB
probe_82802ab: id1 0xff, id2 0xff
Trying LHF00L04, 1024 KB
probe_lhf00l04: id1 0xff, id2 0xff
No EEPROM/flash device found.
which I find quite peculiar.
Why don't I get a success only because I've put on '-V'?
So I tried:
# flashrom -E -V -c W49F002U
Calibrating delay loop... Setting up microsecond timing loop
170M loops per second
ok
No LinuxBIOS table found.
Enabling flash write on VT8235...OK
Trying W49F002U, 256 KB
probe_jedec: id1 0x55, id2 0xaa
No EEPROM/flash device found.
Still the same problem!
Anyone that's have a hint why? I remember that when I started using the RD1-PL I noticed
that if I did a 'verify' after 'write' it said that it didn't match. On the other hand
was it the first time I flashed the device and if i read the flash I could see that it
had been flashed by doing a 'hexdump -C' and verify it by looking for the string section .
# hexdump -C test.bin | grep Linux | head -1
0001a800 00 4c 69 6e 75 78 42 49 4f 53 00 41 74 74 65 6d |.LinuxBIOS.Attem|
My hair turns grey...
[View Less]