> 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 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
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/
In the MB Config.lb
The device apic_cluster 0 should be put before other pci devices
YH
________________________________
From: linuxbios-bounces(a)linuxbios.org
[mailto:linuxbios-bounces@linuxbios.org] On Behalf Of Vincente Tsou
Sent: Sunday, June 25, 2006 11:58 PM
To: yhlu
Cc: Stefan Reinauer; linuxbios(a)linuxbios.org
Subject: Re: [LinuxBIOS] New guy in LinuxBios
Hi,
Excuse me....
I don't know how to move the CPU init before other pci device init
call....
sorry.
I have tried to find it, but .... :(
2006/6/26, yhlu <yinghailu(a)gmail.com>:
the snow screen only happened when I was debugging the onboard VGA
support.
So i move the CPU init before other pci device init call. That is
something related to mtrr setting around [0xa0000-0xb0000) the font
buffer.
the halt_sys display is normal...it means the vga option rom is
executed successfully.
you can use filo in etherboot to boot from usb stick.
YH
On 6/25/06, Vincente Tsou <vincentetsou(a)nexcom.com.tw> wrote:
>
> Hi YH,
>
> Thanks again for your help.
>
> Now I can active all devices in my LinuxBios, it almost done except
VGA
> function.
>
> I appended a 36k VGA option rom to LinuxBios, and enable Options about
VGA.
>
> And I got the halt_sys message:
>
> PCI: 04:02.0 init
> rom address for PCI: 04: 02.0 = fff80000
> copying VGA ROM Image from 0xfff80000 to 0xc0000, 0x9000 bytes
> entering emulator
> halt_sys: file
>
/home/vincente/LinuxBIOS/LinuxBIOSv2/src/devices/emulator/x86emu/ops.c,
> line 4387
> PCI: 01:04.0 init
>
> then, I can see something output, but the output is like snow screen
and I
> can't read anything.
> I think it is working in the wrong mode.
>
> When I made a blind type 'root' and password, I can login the Linux,
and
> then the screen became clear. (work fine)
>
> I wonder how to fix the problem? is the halt_sys message normal ?
>
> I also got another question, could it possible boot to MS-DOS
floppy/USB
> disk.
> The MS-DOS needs a lot INT function in BIOS, does LinuxBios able to
support
> it?
>
>
>
> 2006/6/21, Vincente Tsou <vincentetsou(a)nexcom.com.tw >:
> >
> >
> > Dear YH,
> >
> > got it.
> >
> > Thanks for the information and your help.
> >
> >
> >
> > 2006/6/21, Lu, Yinghai < yinghai.lu(a)amd.com>:
> >
> > >
> > >
> > >
> > >
> > >
> > > Actually the irqtable entries is only for peer root pci bus scan
when
> mptable is used.
> > >
> > > So you need to make sure mptable is right, and put entries for
> hypertransport chain other than on bus0.
> > >
> > >
> > >
> > > YH
> > >
> > >
> > >
> > > ________________________________
>
> > >
> > > From: vincente.tsou(a)gmail.com [mailto:vincente.tsou@gmail.com] On
Behalf
> Of Vincente Tsou
> > > Sent: Tuesday, June 20, 2006 7:05 PM
> > > To: Lu, Yinghai
> > > Cc: Stefan Reinauer; linuxbios(a)linuxbios.org
> > >
> > > Subject: Re: [LinuxBIOS] New guy in LinuxBios
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Dear YH,
> > >
> > >
> > >
> > >
> > >
> > >
> > > excuse me, how about the irq_tables.c?
> > >
> > >
> > > should I modify it like tyan/s2882 did.
> > >
> > >
> > >
> > >
> > >
> > > printk_debug("setting Onboard Broadcom NIC\n");
> > > static const unsigned char slotIrqs_8131_1_9[4] = { 5, 9,
0, 0
> };
> > > pci_assign_irqs(bus_8131_1, 9, slotIrqs_8131_1_9);
> > > write_pirq_info(pirq_info, bus_8131_1,(9<<3)|0, 0x1,
0xdef8,
> 0x2, 0xdef8, 0, 0, 0, 0, 0, 0);
> > > pirq_info++; slot_num++;
> > >
> > >
> > >
> > >
> > >
> > > 2006/6/20, Lu, Yinghai < yinghai.lu(a)amd.com >:
> > >
> > >
> > >
> > >
> > > You need to update the entries at mptable.c for your slots or
onboard
> pci device.
> > >
> > >
> > >
> > > YH
> > >
> > >
> > >
> > >
> > >
> > >
> > > --
> > > Best Regards,
> > > Vincente Tsou
> > >
> > > Engineer
> > > R/D, S/W Dept.
> > > NEXCOM International Co.
> > > Tel: 886-2-82280606 Ext. 3205
> > > Fax: 886-2-82280506
> > > E-mail: vincentetsou(a)nexcom.com.tw
> > > Web: http://www.nexcom.com.tw/
> > >
> >
> >
> >
> >
> >
> > --
> > Best Regards,
> > Vincente Tsou
> >
> > Engineer
> > R/D, S/W Dept.
> > NEXCOM International Co.
> > Tel: 886-2-82280606 Ext. 3205
> > Fax: 886-2-82280506
> > E-mail: vincentetsou(a)nexcom.com.tw
> > Web: http://www.nexcom.com.tw/
>
>
>
>
> --
> Best Regards,
> Vincente Tsou
>
> Engineer
> R/D, S/W Dept.
> NEXCOM International Co.
> Tel: 886-2-82280606 Ext. 3205
> Fax: 886-2-82280506
> E-mail: vincentetsou(a)nexcom.com.tw
> Web: http://www.nexcom.com.tw/
> --
> linuxbios mailing list
> linuxbios(a)linuxbios.org
> http://www.openbios.org/mailman/listinfo/linuxbios
>
>
--
Best Regards,
Vincente Tsou
Engineer
R/D, S/W Dept.
NEXCOM International Co.
Tel: 886-2-82280606 Ext. 3205
Fax: 886-2-82280506
E-mail: vincentetsou(a)nexcom.com.tw
Web: http://www.nexcom.com.tw/
Right now, we use mkelfimage to set up parameter blocks for linux. There
is a lot of code to do this, and I am running out of room on OLPC. I
need to build tiny elf images with on executable code in them (other
than your kernel, of course).
I have modified mkelfimage so that it produces an elfimage with only 3
segments: command line, kernel, initrd. With this option, you can build
a very simple elfimage with just those three things.
There is the issue of setting up %esi for 386 linux. I am considering
the following convention:
architecture-independent part (src/boot/)
For the first PT_LOAD elf segment, assume it is the command line. Set a
variable, command_line, to the load address of this segment.
architecture-dependent, e.g. 386 (src/cpu/boot.c)
set %esi to command_line.
If you are using normal mkelfimage, this is a no-op: esi setting is
ignored. If you are using mkelfimage with my option (e.g. OLPC), this
address will be used as the command line pointer.
I can't see a problem, any comments?
thanks
ron
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
Hi,
I have just got my RD1, and installed it into my EPIA-PD10000 m/board (same chipset as the EPIA-M), all works fine :)
I ran the flashrom util fom the linuxbios source code, (downloaded via svn)
when i run the flashrom util i get the following :-
with bios savour switched in, but nothing written :-
:~/bios/LinuxBIOSv2/util/flashrom# ./flashrom
Calibrating delay loop... ok
No LinuxBIOS table found.
Enabling flash write on VT8235...OK
W49F002U found at physical address: 0xfffc0000
Flash part is W49F002U
OK, only ENABLING flash write, but NOT FLASHING.
with original bios switched in :-
~/bios/LinuxBIOSv2/util/flashrom# ./flashrom
Calibrating delay loop... ok
No LinuxBIOS table found.
Enabling flash write on VT8235...OK
No EEPROM/flash device found.
As you can see the RD1 bios chip is reconised fine but my original bios chip dosnt seem to be found :(
on inspection of the bios chip, i can see a chip number of :F492002UA
If ive understood the flashrom program, this isnt reconsied becasue there isnt a file of that name within the flashrom directory (each file represents its resective bios number????)
Has anyone come accross this bios chip before, and if so can they supply the config file for flashrom?
As i understand it, i should still be able to use the EPIA flash program, but as i dont have a working floppy drive in the house, and am not keen on using a cd for a 1.44Mb file, PLEASE could anyone recomend a way around this?
Also if i use the EPIA flash program it makes it harder to get the compiled rom into the bios, as i have to jump from linux to windows all the time :(
Is there a way to grab the entire bios using dd under linux? could this be sued to get a copy of the original bios, and then write this to the RD1?
Many thanks
Matt
I want to test if my linuxbios could boot from network . but have not done
that before ,could anyone please help me to check if my steps is right?
1.install an os on ide hdd on the test MB.
2.copy the installed image file to another Server MB.
3.make some configuration for DHCP.
4.remove test MB ide hdd ,and use linuxbios boot .
I have test windows boot from network before, its steps seems this . but
I've no idea whether linux is this too.
Thank you.
Carno
Actually the irqtable entries is only for peer root pci bus scan when
mptable is used.
So you need to make sure mptable is right, and put entries for
hypertransport chain other than on bus0.
YH
________________________________
From: vincente.tsou(a)gmail.com [mailto:vincente.tsou@gmail.com] On Behalf
Of Vincente Tsou
Sent: Tuesday, June 20, 2006 7:05 PM
To: Lu, Yinghai
Cc: Stefan Reinauer; linuxbios(a)linuxbios.org
Subject: Re: [LinuxBIOS] New guy in LinuxBios
Dear YH,
excuse me, how about the irq_tables.c?
should I modify it like tyan/s2882 did.
printk_debug("setting Onboard Broadcom NIC\n");
static const unsigned char slotIrqs_8131_1_9[4] = { 5, 9, 0, 0
};
pci_assign_irqs(bus_8131_1, 9, slotIrqs_8131_1_9);
write_pirq_info(pirq_info, bus_8131_1,(9<<3)|0, 0x1, 0xdef8,
0x2, 0xdef8, 0, 0, 0, 0, 0, 0);
pirq_info++; slot_num++;
2006/6/20, Lu, Yinghai <yinghai.lu(a)amd.com>:
You need to update the entries at mptable.c for your slots or onboard
pci device.
YH
--
Best Regards,
Vincente Tsou
Engineer
R/D, S/W Dept.
NEXCOM International Co.
Tel: 886-2-82280606 Ext. 3205
Fax: 886-2-82280506
E-mail: vincentetsou(a)nexcom.com.tw
Web: http://www.nexcom.com.tw/
First of all I'm sorry to cross-post this request. But I need urgent
reply to know if somebody wants to team up in a project making Debian
ready for the One Laptop per Child hardware. If there is somebody
interested applying for OLPC developer board to make things work,
please reply to debian-custom(a)lists.debian.org.
My project proposal:
After a tip from Walter Bender at MIT, I was subscribing to the
devel-boards list for the One Laptop per Child project. Walter is
president, software and content, of the One Laptop per Child
foundation.
My subscription was forwarded to the list moderator for approval. Then
i got a nice e-mail from Jim Gettys. He wrote that if my interest in
the list is to get a developer's board, then please follow the
following instructions (look at the bootom):
http://wiki.laptop.org/index.php/Developers_Program
This will result in a developer's board if the request is at all
reasonable, and you will be added to the mailing list (which is meant
to be low volume announcements for people with boards).
I wrote some suggestions for a plan to get the OLPC-machine up running
April 5th 2006:
http://lists.debian.org/debian-edu/2006/04/msg00016.html
So people, I could apply for boards to realize this plan. (The plan is
not at all finale, but a suggestion):
1. To make the Debian installer work with OLPC-machines
2. To make bare bone Debian run with network connectivety in a mesh
network (IPv6)
3. Make the power management work
4. To make X and a window manager with simplified debloated desktop
But with no developers interested doing the development, I see no
reason for applying for boards. So it depends on what the Debian Edu
and Debian contributers are interested in.
It's a considerable job tailoring the different subsystem in Debian to
OLPC hardware. The installer has to be tailored, the network mesh net
support has to work, simplified debloated desktop has to be configured,
and the power management has to work.
We have done interesting things with Custom Debian Distributions and
Debian Installer in the Skolelinux / Debian Edu environment before. It
seems to me that more people have joined the Skolelinux / Debian Edu
project. I believe the One Laptop per Child is important for Debian,
and we should do this development.
- What do you think about this suggestions?
- Who are interested to develop tailored Debian Edu for
OLPC-machines?
Regards
Knut Yrvin
Project manager Skolelinux Norway
