Hi LinuxBIOS list subscribers,
I've been struggling for a couple of days now trying to get LinuxBIOS
working on a DigitalLogic SmartCore-P5 166MHz PC/104 card.
I am using the v1 tree, since the v1 tree contained smartcore support,
but the v2 tree does not.
I had no problems building and flashing the LinuxBIOS, and it starts up
just fine and ends up in elfboot as expected. Elfboot reports to find
my payload, loads it, and attempts to start executing it. At that
point, nothing more happens. Due to the limited "debugability" at this
point, it's hard to say exactly what has happened, but a serial output
character I have put early in the FILO startup code is not showing up
so I guess the FILO code is never reached at all(?)
I have verified that the filo elf image I'm trying to load is OK by
loading it from GRUB (it worked OK).
I have searched both the archives and other parts of the Internet for
some hints about this, but the only interesting thing I was able to
find was a FAQ in the FILO tree saying there was a bug in some
linuxbios/elfboot checksum calculation routine that would cause FILO to
crash. According to that FAQ, using the latest linuxbios patches should
fix this problem. But I couldn't find any patches newer than the v1
stable tree, so I assumed this was old info(?)...
Does this sound familiar to anyone? Any suggestions would be highly
appreciated.
The v2 tree contains support for another DigitalLogic card that I'm not
familiar with. Would there be any chance that config would work on my
SmartCore-P5 card?
Cheers,
/Kjell
Just commit some lines to ondie Lan work now.
YH
> -----Original Message-----
> From: YhLu
> Sent: Wednesday, May 11, 2005 1:36 PM
> To: YhLu; Ronald G. Minnich; ebiederman(a)lnxi.com; Stefan
> Reinauer; Li-Ta Lo
> Cc: linuxbios(a)openbios.org
> Subject: RE: [LinuxBIOS] About Nvidia chipset support
>
> commited.
>
> > -----Original Message-----
> > From: YhLu
> > Sent: Wednesday, May 11, 2005 11:21 AM
> > To: Ronald G. Minnich; ebiederman(a)lnxi.com; Stefan
> Reinauer; Li-Ta Lo
> > Cc: linuxbios(a)openbios.org
> > Subject: [LinuxBIOS] About Nvidia chipset support
> >
> > All,
> >
> > Finally I get the approval for releasing Nvidia chipset support for
> > Ck804. I hope end user to press nvidia to release more info to make
> > sata and on die lan work.
> >
> > The problem my code is messed up dual core support etc. I need some
> > time to split them up.
> >
> > I will commit soon about
> > Nvidia CK804 support
> > smbus bus number support (to handle multi sumbus and mux)
> superio smsc
> > 47 support Tyan S2895/S2891/S2892 support flash_rom Ck804 support
> >
> > maybe two months later after AMD issue auth letter or put
> dual core on
> > public
> >
> > AMD D0/E0 Opteron new mem mapping support AMD E Opteron dual core
> > support AMD E Opteron mem hole support AMD K8 Four Ranks
> DIMM support
> >
> > Regards
> >
> > YH
> >
> > _______________________________________________
> > LinuxBIOS mailing list
> > LinuxBIOS(a)openbios.org
> > http://www.openbios.org/mailman/listinfo/linuxbios
> >
>
what is EEPROM in your BIOS socket?
How do you install your DIMM? 4x1G in CPU0?
What is your cpu version?
YH
_____
From: beneo [mailto:beneo@comcast.net]
Sent: Wednesday, May 11, 2005 6:57 PM
To: linuxbios(a)openbios.org
Subject: [LinuxBIOS] flash issue with AMD Ref board
I'm playing with the AMD seranede board. The flash_and_burn utility can not
program linuxBIOS to the flash. but I can read the linuxbios and save to a
file correctly.
If I boot from AMI BIOS, using same utility, I can program a linuxBIOS into
the flash. That made me believe some setting by linuxBIOS on the AMD Ref
board is not right. I just don't know what.
I used gdb to trace the code, Flash_and_burn utility enables flash by
program two AMD Southbridge 8111 registers, One for enable 4MB window to
flash (DevB, 0x43), one for enable write to the flash (DevB, 0x40). I
checked the AMD datasheet, it seems all it need. But if I boot with
LinuxBIOS, the flash erase command has no effect. with AMI BIOS, I can
sucessfully erase a sector.
could anybody give me some pointer on what to check?
I should add, the linuxBIOS only reports 2GB memory when I really have 4GB
in the system. I don't know if this have something to do with my issue.
Thanks
Beneo
Apparently it does not run.
I started modifying the commands in the makefile, and started compiling rombios.c
I am getting this error:
rombios.c:2662:1: pasting "(" and ""ata_cmd_data_in : read error\n"" does not give a valid preprocessing token
the source line is:
BX_DEBUG_ATA("ata_cmd_data_in : read error\n");
Do you think it is due to the environment?
MiKL
Stefan Reinauer <stepan(a)openbios.org> wrote:
* Toto Lebolo [050512 20:02]:
> I am trying to rebuild linux BIOS. I have installed the Windows version of the
> compilers.
> Does the makefile run in windows? or just in Linux?
Find out and tell us, please!
You'll also need python installed.
Stefan
---------------------------------
Yahoo! Mail Mobile
Take Yahoo! Mail with you! Check email on your mobile phone.
I am trying to rebuild linux BIOS. I have installed the Windows version of the compilers.
Does the makefile run in windows? or just in Linux?
toto
---------------------------------
Yahoo! Mail
Stay connected, organized, and protected. Take the tour
some GPIO need to be enabled. I guess.
You need to check the schematic in AMD NDA web site to find out which GPIO
control that.
YH
> -----Original Message-----
> From: beneo [mailto:beneo@comcast.net]
> Sent: Thursday, May 12, 2005 10:57 AM
> To: Ronald G. Minnich
> Cc: linuxbios(a)openbios.org; YhLu
> Subject: Re: [LinuxBIOS] flash issue with AMD Ref board
>
>
> Ron,
>
> I was also thinking if the AMD senanade board has some
> special hardware to protect eeprom write. but after I tried
> to boot with AMI BIOS into Linux and use same flash_and_burn
> utility to flash LinuxBIOS into the EEPROM sucessufully, I
> started to be convienced there are some setup issue within
> LinuxBIOS caused this.
>
> I spent sometime to check 8111 southbridge, but I couldn't
> find anything there.
>
> Is that possible some setting in the Opteron that prevent
> write access to the EEPROM address be passed down
> southbridge? I'm not farmilar with the Opteron NB and CPU,
> if you guys can give me some pointers, that would help me a lot.
>
> I don't have a scope now, I will see if I can get one.
>
> Thanks
>
> beneo
>
> ----- Original Message -----
> From: "Ronald G. Minnich" <rminnich(a)lanl.gov>
> To: "beneo" <beneo(a)comcast.net>
> Cc: <linuxbios(a)openbios.org>; "YhLu" <YhLu(a)tyan.com>
> Sent: Thursday, May 12, 2005 7:51 AM
> Subject: Re: [LinuxBIOS] flash issue with AMD Ref board
>
>
> > the flash problem: this sounds more to me like an enable
> line that has
> > been added for FLASHWR.
> >
> > Beneo, do you have a scope? it is often useful to put a
> scope on the WR
> > line and see if it is toggling.
> >
> > ron
> >
> >
> > _______________________________________________
> > LinuxBIOS mailing list
> > LinuxBIOS(a)openbios.org
> > http://www.openbios.org/mailman/listinfo/linuxbios
>
004 only can be use in intel platform. FW hub interface...
040 can be used in AMD platform. LPC interface...
PMC 004 support two interface...
YH
_____
From: beneo [mailto:beneo@comcast.net]
Sent: Thursday, May 12, 2005 10:46 AM
To: YhLu; linuxbios(a)openbios.org
Subject: Re: [LinuxBIOS] flash issue with AMD Ref board
It's SST 49LF004. It the replacement for SST49LF040. They use same argorithm
to flash. I looked the flash_and_burn utility. That's the case there too.
beneo.
----- Original Message -----
From: YhLu <mailto:YhLu@tyan.com>
To: beneo <mailto:beneo@comcast.net> ; linuxbios(a)openbios.org
<mailto:linuxbios@openbios.org>
Sent: Thursday, May 12, 2005 9:53 AM
Subject: RE: [LinuxBIOS] flash issue with AMD Ref board
SST49LF004 or SST49LF040 ?
YH
_____
From: beneo [mailto:beneo@comcast.net]
Sent: Wednesday, May 11, 2005 7:20 PM
To: beneo; YhLu; linuxbios(a)openbios.org <mailto:linuxbios@openbios.org>
Subject: Re: [LinuxBIOS] flash issue with AMD Ref board
YhLu,
EEPOM should be SST 49LF004, sorry.
I also get the CPU version, it's a print out from cat /proc/cpuinfo. Total
two CPU, I put the the second CPU here.
processor : 1
vendor_id : AuthenticAMD
cpu family : 15
model : 5
model name : 02/05
stepping : 8
cpu MHz : 1395.089
cache size : 1024 KB
physical id : 0
siblings : 1
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush mmx fxsr sse sse2 syscall mmxext l
m 3dnowext 3dnow
bogomips : 2785.28
Thanks
Beneo
----- Original Message -----
From: beneo <mailto:beneo@comcast.net>
To: YhLu <mailto:YhLu@tyan.com> ; linuxbios(a)openbios.org
<mailto:linuxbios@openbios.org>
Sent: Wednesday, May 11, 2005 7:14 PM
Subject: Re: [LinuxBIOS] flash issue with AMD Ref board
EEPROM is SST 48LF004.
I install 2GB to CPU0 and 2GB to CPU1. I use 512MB DIMM, 4 DIMM per CPU, so
total should be 4GB. But linux command cat /proc/meminfo report one 2 GB
when using LinuxBIOS.
I have two opteron CPU, I'm not sure the version though.
thanks
beneo
----- Original Message -----
From: YhLu <mailto:YhLu@tyan.com>
To: beneo <mailto:beneo@comcast.net> ; linuxbios(a)openbios.org
<mailto:linuxbios@openbios.org>
Sent: Wednesday, May 11, 2005 7:27 PM
Subject: RE: [LinuxBIOS] flash issue with AMD Ref board
what is EEPROM in your BIOS socket?
How do you install your DIMM? 4x1G in CPU0?
What is your cpu version?
YH
_____
From: beneo [mailto:beneo@comcast.net]
Sent: Wednesday, May 11, 2005 6:57 PM
To: linuxbios(a)openbios.org <mailto:linuxbios@openbios.org>
Subject: [LinuxBIOS] flash issue with AMD Ref board
I'm playing with the AMD seranede board. The flash_and_burn utility can not
program linuxBIOS to the flash. but I can read the linuxbios and save to a
file correctly.
If I boot from AMI BIOS, using same utility, I can program a linuxBIOS into
the flash. That made me believe some setting by linuxBIOS on the AMD Ref
board is not right. I just don't know what.
I used gdb to trace the code, Flash_and_burn utility enables flash by
program two AMD Southbridge 8111 registers, One for enable 4MB window to
flash (DevB, 0x43), one for enable write to the flash (DevB, 0x40). I
checked the AMD datasheet, it seems all it need. But if I boot with
LinuxBIOS, the flash erase command has no effect. with AMI BIOS, I can
sucessfully erase a sector.
could anybody give me some pointer on what to check?
I should add, the linuxBIOS only reports 2GB memory when I really have 4GB
in the system. I don't know if this have something to do with my issue.
Thanks
Beneo
_____
_______________________________________________
LinuxBIOS mailing list
LinuxBIOS(a)openbios.org
http://www.openbios.org/mailman/listinfo/linuxbios
_____
_______________________________________________
LinuxBIOS mailing list
LinuxBIOS(a)openbios.org
http://www.openbios.org/mailman/listinfo/linuxbios
_____
_______________________________________________
LinuxBIOS mailing list
LinuxBIOS(a)openbios.org
http://www.openbios.org/mailman/listinfo/linuxbios
SST49LF004 or SST49LF040 ?
YH
_____
From: beneo [mailto:beneo@comcast.net]
Sent: Wednesday, May 11, 2005 7:20 PM
To: beneo; YhLu; linuxbios(a)openbios.org
Subject: Re: [LinuxBIOS] flash issue with AMD Ref board
YhLu,
EEPOM should be SST 49LF004, sorry.
I also get the CPU version, it's a print out from cat /proc/cpuinfo. Total
two CPU, I put the the second CPU here.
processor : 1
vendor_id : AuthenticAMD
cpu family : 15
model : 5
model name : 02/05
stepping : 8
cpu MHz : 1395.089
cache size : 1024 KB
physical id : 0
siblings : 1
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush mmx fxsr sse sse2 syscall mmxext l
m 3dnowext 3dnow
bogomips : 2785.28
Thanks
Beneo
----- Original Message -----
From: beneo <mailto:beneo@comcast.net>
To: YhLu <mailto:YhLu@tyan.com> ; linuxbios(a)openbios.org
<mailto:linuxbios@openbios.org>
Sent: Wednesday, May 11, 2005 7:14 PM
Subject: Re: [LinuxBIOS] flash issue with AMD Ref board
EEPROM is SST 48LF004.
I install 2GB to CPU0 and 2GB to CPU1. I use 512MB DIMM, 4 DIMM per CPU, so
total should be 4GB. But linux command cat /proc/meminfo report one 2 GB
when using LinuxBIOS.
I have two opteron CPU, I'm not sure the version though.
thanks
beneo
----- Original Message -----
From: YhLu <mailto:YhLu@tyan.com>
To: beneo <mailto:beneo@comcast.net> ; linuxbios(a)openbios.org
<mailto:linuxbios@openbios.org>
Sent: Wednesday, May 11, 2005 7:27 PM
Subject: RE: [LinuxBIOS] flash issue with AMD Ref board
what is EEPROM in your BIOS socket?
How do you install your DIMM? 4x1G in CPU0?
What is your cpu version?
YH
_____
From: beneo [mailto:beneo@comcast.net]
Sent: Wednesday, May 11, 2005 6:57 PM
To: linuxbios(a)openbios.org <mailto:linuxbios@openbios.org>
Subject: [LinuxBIOS] flash issue with AMD Ref board
I'm playing with the AMD seranede board. The flash_and_burn utility can not
program linuxBIOS to the flash. but I can read the linuxbios and save to a
file correctly.
If I boot from AMI BIOS, using same utility, I can program a linuxBIOS into
the flash. That made me believe some setting by linuxBIOS on the AMD Ref
board is not right. I just don't know what.
I used gdb to trace the code, Flash_and_burn utility enables flash by
program two AMD Southbridge 8111 registers, One for enable 4MB window to
flash (DevB, 0x43), one for enable write to the flash (DevB, 0x40). I
checked the AMD datasheet, it seems all it need. But if I boot with
LinuxBIOS, the flash erase command has no effect. with AMI BIOS, I can
sucessfully erase a sector.
could anybody give me some pointer on what to check?
I should add, the linuxBIOS only reports 2GB memory when I really have 4GB
in the system. I don't know if this have something to do with my issue.
Thanks
Beneo
_____
_______________________________________________
LinuxBIOS mailing list
LinuxBIOS(a)openbios.org
http://www.openbios.org/mailman/listinfo/linuxbios
_____
_______________________________________________
LinuxBIOS mailing list
LinuxBIOS(a)openbios.org
http://www.openbios.org/mailman/listinfo/linuxbios
I'm playing with the AMD seranede board. The flash_and_burn utility can not program linuxBIOS to the flash. but I can read the linuxbios and save to a file correctly.
If I boot from AMI BIOS, using same utility, I can program a linuxBIOS into the flash. That made me believe some setting by linuxBIOS on the AMD Ref board is not right. I just don't know what.
I used gdb to trace the code, Flash_and_burn utility enables flash by program two AMD Southbridge 8111 registers, One for enable 4MB window to flash (DevB, 0x43), one for enable write to the flash (DevB, 0x40). I checked the AMD datasheet, it seems all it need. But if I boot with LinuxBIOS, the flash erase command has no effect. with AMI BIOS, I can sucessfully erase a sector.
could anybody give me some pointer on what to check?
I should add, the linuxBIOS only reports 2GB memory when I really have 4GB in the system. I don't know if this have something to do with my issue.
Thanks
Beneo
