(1) RAM type sis630 IPL.S read is not 04
I debug sis630 IPL.S, I find the RAM type value that IPL read is 01 or 00 for different RAM but not 04. But my RAM is definitely SDRAM. The code is:
...........
movb $0x02, %al # Read the RAM Type (SPD byte 2)
CALL_SP(read_spd) # of the dram on current DIMM.
movb %bl, %al # %bl is 01 or 00 for different RAM,not 04
outb %al, $0x80
cmpb $0x04, %bl # If the RAM Type = SDRAM ??
jne no_sdram # no, exit
.......
Is there any bug in the codes reading spd bytes?
(2) for some Sis630 mainboard, docipl will hang. Linuxbios can't be executed. I think the RAM initialization procedure is as compatible as BIOS.
Thanks
zhu
---------------------------------
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
Dear sir,
I've got one mainboard named A6T. A6T uses the same VIA northbridge and southbridge as vt5426. I boot linux from the mainboard and insert doc2001 in the BIOS slot. Then run the following commands:
insmod docecc
insmod doc2001
insmod docprobe
these commands can detect doc2001 successfully in SIS630 mainboard. But in A6T they can't detect doc2001. ( I check /proc/mtd file, it is null ).
SIS630 need flash_on utility, does VT5426 need some utility? Who knows the cause?
thanks
zhu
---------------------------------
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
I need to know the value of spd byte from linux. Is there any linux utility to read spd bytes?
tks
zhu
---------------------------------
Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!
You compile the LinuxBIOS, filo, .... in Suse 9 for AMD 64 ?
-----Original Message-----
From: ron minnich [mailto:rminnich@lanl.gov]
Sent: Wednesday, July 14, 2004 3:55 PM
To: David Aubin
Cc: LinuxBIOS
Subject: Re: How to build vgabios
On Wed, 14 Jul 2004, David Aubin wrote:
> gcc -Wall -Ix86emu/include -O2 -g -m32 -march=i386 -c -o
> pci-userspace.o pci-userspace.c
> pci-userspace.c:2:21: pci/pci.h: No such file or directory
your problems start here.
do you have the pciutils installed? You need:
pciutils-devel-2.1.9-2
or later.
ron
_______________________________________________
Linuxbios mailing list
Linuxbios(a)clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios
Hello,
I am having difficulty building vgabios. Can someone please give me
a hand? I took the latest code off of the freebios2 branch (6 days old,
by Ollie)
I get the following Errors when I try to compile. It looks like I am
missing
files in the drop #include <pci/pci.h>
gcc -Wall -Ix86emu/include -O2 -g -m32 -march=i386 -c -o
pci-userspace.o pci-userspace.c
pci-userspace.c:2:21: pci/pci.h: No such file or directory
In file included from pci-userspace.c:4:
pci.h:1: error: parse error before "port"
pci-userspace.c: In function `pciInit':
pci-userspace.c:20: warning: implicit declaration of function
`pci_alloc'
pci-userspace.c:20: warning: assignment makes pointer from integer
without a cast
pci-userspace.c:22: warning: implicit declaration of function `pci_init'
pci-userspace.c:23: warning: implicit declaration of function
`pci_scan_bus'
pci-userspace.c:24: error: dereferencing pointer to incomplete type
pci-userspace.c:24: error: dereferencing pointer to incomplete type
pci-userspace.c:25: warning: implicit declaration of function
`pci_fill_info'
pci-userspace.c:25: error: `PCI_FILL_IDENT' undeclared (first use in
this function)
pci-userspace.c:25: error: (Each undeclared identifier is reported only
once
pci-userspace.c:25: error: for each function it appears in.)
pci-userspace.c:25: error: `PCI_FILL_BASES' undeclared (first use in
this function)
pci-userspace.c: In function `pciExit':
pci-userspace.c:32: warning: implicit declaration of function
`pci_cleanup'
pci-userspace.c: In function `findPci':
pci-userspace.c:44: error: dereferencing pointer to incomplete type
pci-userspace.c:45: error: dereferencing pointer to incomplete type
pci-userspace.c:46: error: dereferencing pointer to incomplete type
pci-userspace.c:48: warning: implicit declaration of function
`pci_get_dev'
pci-userspace.c: At top level:
pci-userspace.c:54: error: parse error before "pciSlotBX"
pci-userspace.c:55: warning: return type defaults to `int'
pci-userspace.c: In function `pciSlotBX':
pci-userspace.c:56: error: dereferencing pointer to incomplete type
pci-userspace.c:56: error: dereferencing pointer to incomplete type
pci-userspace.c:56: error: dereferencing pointer to incomplete type
pci-userspace.c: At top level:
pci-userspace.c:59: error: parse error before "pciReadByte"
pci-userspace.c:59: error: parse error before "u32"
pci-userspace.c:60: warning: return type defaults to `int'
pci-userspace.c: In function `pciReadByte':
pci-userspace.c:62: error: `tag' undeclared (first use in this function)
pci-userspace.c:62: warning: assignment makes pointer from integer
without a cast
pci-userspace.c:63: warning: implicit declaration of function
`pci_read_byte'
pci-userspace.c:63: error: `idx' undeclared (first use in this function)
pci-userspace.c: At top level:
pci-userspace.c:71: error: parse error before "pciReadWord"
pci-userspace.c:71: error: parse error before "u32"
pci-userspace.c:72: warning: return type defaults to `int'
pci-userspace.c: In function `pciReadWord':
pci-userspace.c:74: error: `tag' undeclared (first use in this function)
pci-userspace.c:74: warning: assignment makes pointer from integer
without a cast
pci-userspace.c:75: warning: implicit declaration of function
`pci_read_word'
pci-userspace.c:75: error: `idx' undeclared (first use in this function)
pci-userspace.c: At top level:
pci-userspace.c:83: error: parse error before "pciReadLong"
pci-userspace.c:83: error: parse error before "u32"
pci-userspace.c:84: warning: return type defaults to `int'
pci-userspace.c: In function `pciReadLong':
pci-userspace.c:86: error: `tag' undeclared (first use in this function)
pci-userspace.c:86: warning: assignment makes pointer from integer
without a cast
pci-userspace.c:87: warning: implicit declaration of function
`pci_read_long'
pci-userspace.c:87: error: `idx' undeclared (first use in this function)
pci-userspace.c: At top level:
pci-userspace.c:96: error: parse error before "u32"
pci-userspace.c: In function `pciWriteLong':
pci-userspace.c:99: error: `tag' undeclared (first use in this function)
pci-userspace.c:99: warning: assignment makes pointer from integer
without a cast
pci-userspace.c:100: warning: implicit declaration of function
`pci_write_long'
pci-userspace.c:100: error: `idx' undeclared (first use in this
function)
pci-userspace.c:100: error: `data' undeclared (first use in this
function)
pci-userspace.c: At top level:
pci-userspace.c:108: error: parse error before "u32"
pci-userspace.c: In function `pciWriteWord':
pci-userspace.c:111: error: `tag' undeclared (first use in this
function)
pci-userspace.c:111: warning: assignment makes pointer from integer
without a cast
pci-userspace.c:112: warning: implicit declaration of function
`pci_write_word'
pci-userspace.c:112: error: `idx' undeclared (first use in this
function)
pci-userspace.c:112: error: `data' undeclared (first use in this
function)
pci-userspace.c: At top level:
pci-userspace.c:121: error: parse error before "u32"
pci-userspace.c: In function `pciWriteByte':
pci-userspace.c:124: error: `tag' undeclared (first use in this
function)
pci-userspace.c:124: warning: assignment makes pointer from integer
without a cast
pci-userspace.c:125: error: `idx' undeclared (first use in this
function)
pci-userspace.c:125: error: `data' undeclared (first use in this
function)
/usr/include/bits/stdio.h: At top level:
pci-userspace.c:13: error: storage size of `ltag' isn't known
make: *** [pci-userspace.o] Error 1
Can someone please tell me where I can find the correct pci files? I
have a Suse 9.0 x64 distribution.
Thanks,
Dave
I've got QDIA6T mainboard see http://www.qdigrp.com. It use via 8601t and 686b. I try to boot it using vt5426 mainboard in freebios V1. After testing, ipl.S will loop forever in the following code(in src/northbridge/via/8601/ipl.S):
............
wait_for_flash_ready:
/* delay by reding NOP register before polling the FLASH READY bit,
this is inlined to save a call/ret pair */
movb $0xbb, %al
outb %al,$0x80
doc_delay:
movb %ds:0x04(%di),%ah
movw $0x04, %cx # this one is DANGEROUS but I am
# sure the upper 3 bytes == 0x00
0:
movb %ds:0x20(%di), %al # read DOC NOP retisger
loop 0b # four times
testb $0x80,%ah # is flash ready ?
jz wait_for_flash_ready
........
Anybody can explain me what the code work for?
thanks
zhu
---------------------------------
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
I mean if you build tg3filoide_disk.zelf, it will confuse the Etherboot. So
you can only build tg3filo.zelf or tg3ide_disk.zelf.
Do you have spare IDE disk? If So format the disk into ext3 or fat format
and copy the .elf file into it.
Then connect that to your MB do test.
hda1:/ram0_......elf
Regards
YH
_____
From: David Aubin [mailto:daubin@actuality-systems.com]
Sent: Monday, July 12, 2004 12:50 PM
To: YhLu
Cc: Hendricks David W.; ron minnich; LinuxBIOS
Subject: RE: Filo Error Help
Hi,
I am unable to get my kernel & initrd off of the usb stick. I was reading
through the documents and came across this line in README.etherboot_in_filo:
You can not use filo and ide_disk at the same time.
Can you tell me what this means? Do I need to rebuild filo without IDE
support to get USB support?
Just to recap: My kernel & initrd fails as the initrd execution
complaining of
a bad CRC when I use the elf as a payload to load with with filo. I then
try
uda1:/kernel initrd=/boot/initrd root=/dev/sda1 and I get those td errors.
I then
tried your ramfs.elf and I get the same behavior are my elf image with the
CRC
complaining when the initrd portion is executed. Note, I have confirmed my
elf
works with etherboot, just not filo yet....
The CRC error makes me think that the image did not get loaded correctly
by the elf boot. Can you confirm you used Eric's mkelfImage2-5? Here is
my dump of the readelf -a.
ELF Header:
Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00
Class: ELF32
Data: 2's complement, little endian
Version: 1 (current)
OS/ABI: UNIX - System V
ABI Version: 0
Type: EXEC (Executable file)
Machine: Intel 80386
Version: 0x1
Entry point address: 0x10000
Start of program headers: 52 (bytes into file)
Start of section headers: 0 (bytes into file)
Flags: 0x0
Size of this header: 52 (bytes)
Size of program headers: 32 (bytes)
Number of program headers: 5
Size of section headers: 0 (bytes)
Number of section headers: 0
Section header string table index: 0
There are no sections in this file.
Program Headers:
Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align
NOTE 0x0000d4 0x00000000 0x00000000 0x00088 0x00088 RWE 0
LOAD 0x00015c 0x00010000 0x00010000 0x0559c 0x1aa24 RWE 0
LOAD 0x0056f8 0x00091000 0x00091000 0x00000 0x00070 RWE 0
LOAD 0x0056f8 0x00100000 0x00100000 0x1a952a 0x700000 RWE 0
LOAD 0x1aec22 0x00800000 0x00800000 0x2769f5 0x2769f5 RWE 0
There is no dynamic segment in this file.
There are no relocations in this file.
There are no unwind sections in this file.
No version information found in this file.
Thanks,
Dave
On Fri, 2004-07-09 at 15:48, YhLu wrote:
I have got two cpus and four dimms for every CPU.
YH
_____
From:David Aubin [mailto:daubin@actuality-systems.com]
Sent: Friday, July 09, 2004 12:07 PM
To: YhLu
Cc: Hendricks David W.; ron minnich; LinuxBIOS
Subject: RE: Filo Error Help
Hi,
Yes, I did, but I don't have a DHCP environment so it kept searching at
the DHCP phase.
This problem is odd. I can boot my elf fine with etherboot, but not with
filo. I can boot
my kernel fine with filo, but not the initrd. I can even boot your kernel
of the ram.elf you
sent me, but when it hits the initrd it fails with the same error as mine.
I suspect either my filo is not configured like yours or that there is a
problem loading a
mulitpart elf (kernel & initrd in filo). I'm confused as to why filo didn't
just use the etherboot
portion of elf_load. It could be you were on the, "bleeding" edge? ;)
Can you tell me how much memory you have in your working system? I have
just
one cpu and 512meg memory. Curious if loading it high & it runs out of
memory or
something like that.
Thanks,
Dave
On Fri, 2004-07-09 at 13:05, YhLu wrote:
Did you try the tg3--filo.zelf I sent to you?
YH
FILO in TWO CPU version LinuxBIOS works well S2885 in LANL and my lab.
So I still suggest that you get another CPU to verify the whole process.
Regards
YH
_____
From: David Aubin [mailto:daubin@actuality-systems.com]
Sent: Tuesday, July 13, 2004 12:40 PM
To: ron minnich
Cc: Takeshi Sone; YhLu; Hendricks David W.; LinuxBIOS
Subject: Re: Filo Error Help
That's interesting. Too small? Uncompressed it is:
ls -la :
8192000 2004-07-13 15:37 initrd
I have my ram disk set to 65536. I made it bigger just to be sure.
Are you saying the initrd and the ramdisk_size must be equal?
If so then this would explain why Yhlu's and my elf's did not work.
I'll try an exact ramdisk_size and initrd.
Thanks,
Dave
On Tue, 2004-07-13 at 15:27, ron minnich wrote:
On Tue, 13 Jul 2004, David Aubin wrote:
> Thank yo for the image, but oddly it fails exactly the
> same way....
> Found initrd block 0
> crc error
the few times I've seen the crc error is the initrd is configured too
small. I still think you might have a config problem here.
Put some debug prints in the initrd code and try to zoom in better to
what's going on.
ron
Can you get two cpus for the S2885? I would send my rom image to you for
test.
Regards
YH
_____
From: David Aubin [mailto:daubin@actuality-systems.com]
Sent: Tuesday, July 13, 2004 9:09 AM
To: Peter Stuge
Cc: LinuxBIOS
Subject: Re: Filo Error Help
Hi,
No no no, the disk. The initrd is ext2.
Tried changing the disk to ext2 and still get the same results.
This did work, but is not what I need.
1. Etherboot the filo.elf (4.2) as a payload
2. Run the filo.elf
3. It is able to load my kernel & initrd.elf, only off of the hd, not the
usb stick.
Arg!
My setup uses etherboot as a primary to get the kernel & intird as an elf.
But if that connection dies I want it to use the kernel & initrd elf on my
usb stick. This first part works just fine. It is finding a way to get the
second
part that is taking me weeks! :(
On Tue, 2004-07-13 at 11:48, Peter Stuge wrote:
On Tue, Jul 13, 2004 at 11:35:01AM -0400, David Aubin wrote:
> Thank yo for the image, but oddly it fails exactly the
> same way....
> Found initrd block 0
> crc error
>
> I'm using reiserfs, I'll try ext2. I'm really running out
> of ideas.
For the initrd? I believe only ext2, minix, cramfs and perhaps one
other filesystem is actually supported for initrd:s.
//Peter
_______________________________________________
Linuxbios mailing list
Linuxbios(a)clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios
<http://www.clustermatic.org/mailman/listinfo/linuxbios>
dear sir,
I've got one mainboard. Its northbridge is vt8601t, southbridge is 82c686b. I checked freebios source , there exists mainboard vt5426 which is very near my configuration. the northbridge and southbridge of vt5426 are seperately vt8601 and 82c686. Who know the difference between them?
By the way , where can I get the manual of vt8601t and 82c686b? I have checked via website, there is no deep technical information about them.
tks
zhu
---------------------------------
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
