Re: Help with EPIA
Hi Josiah, Nice to see someone else trying to get the EPIA working again. 1st, what settings do you have in the Config.lb for enabling the IDE controllers - they should be in compatibility mode (I think). 2nd, I'm curious to know how stable your raminit appears to be, I've been having problems with it hanging reading the spd eprom on the dimm's. 3rd, I have a cleaned up version of the southbridge/via/vt8231/vt8231.c ready to commit after Ron checks it over, if you'd like to test it, I can email you the diff (plus a few changes to the Options.lb and Config.lb) Regards Mark Wilkinson. Quoting Josiah England <[EMAIL PROTECTED]>: Perhaps it'll help if I'm more specific. It appears some changes have been made to the via/epia tree and the southbridge doesn't seem to be working like it should (or used to). Using a filo payload (that works on a previous version of LinuxBIOS), I now get the following: LinuxBIOS-1.1.7.0Fallback Wed Mar 9 16:54:36 MST 2005 starting... 87 is the comm register SMBus controller enabled vt8601 init starting is the north 1106 0601 0120d4 is the computed timing NOP PRECHARGE DUMMY READS CBR MRS NORMAL set ref. rate enable multi-page open Slot 00 is SDRAM 1000 bytes 0100 is the chip size 000e is the MA type Slot 01 is empty Slot 02 is empty Slot 03 is empty vt8601 done Copying LinuxBIOS to ram. Jumping to LinuxBIOS. FILO version 0.4.2 ([EMAIL PROTECTED]) Tue Mar 8 15:01:09 MST 2005 collect_linuxbios_info: Searching for LinuxBIOS tables... find_lb_table: Found canidate at: 0500 find_lb_table: header checksum o.k. find_lb_table: table checksum o.k. find_lb_table: record count o.k. collect_linuxbios_info: Found LinuxBIOS table at: 0500 convert_memmap: 0x00 0x000b7c 16 convert_memmap: 0x000b7c 0x0ef484 1 convert_memmap: 0x0f 0x000400 16 convert_memmap: 0x0f0400 0x000ff0fc00 1 Press for default boot, or for boot prompt... timed out boot: hda1:/phase1.epia console=tty0 console=ttyS0,19200 find_ide_controller: found PCI IDE controller 1106:0571 prog_if=0x8f find_ide_controller: primary channel: native PCI mode find_ide_controller: cmd_base=0x0 ctrl_base=0x0 ide_software_reset: Waiting for ide0 to become ready for reset... ok IDE time out No drive detected on IDE channel 0 (Both primary and fallback payloads are the same) What could be going wrong? -Josiah England ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: new free software foundation crusade: http://www.fsf.org/campaigns/free-bios.html
Hi Andreas Quoting Andreas Thienemann <[EMAIL PROTECTED]>: Hi Mark, On Tue, 1 Mar 2005 [EMAIL PROTECTED] wrote: Andreas, which version of LB where you looking at ? People still seem to be getting on ok with V1 and the HOW-TO I wrote some time ago. I tried the Linuxbios 1 version together with the howto. Which version of the EPIA are you using, is it the original EPIA or one of the other version (ie EPIA-M, EPIA-MII etc) ? If it's the EPIA, I may be able to help. I tried the epia-pd. This could be the start of the problem, from what I remember, the versions of the EPIA after the initial one where each different enough to cause problems, such as a different north/south bridge requiring different configurations to get the ram, serial, etc up and running. The inital EPIA has a via VT8601 northbridge and a VT8231 southbridge. Looking at VIA's website, everything after the EPIA, upto but not including the new EPIA-SP have a CLE266 northbridge and a VT8235 southbridge. This would mean that the code for the EPIA-M in LinuxBIOS should work for these motherboards. The EPIA-SP is listed as having a CN400 northbridge and a VT8237 Southbrigde. Unfortunately, I think the EPIA-M code is not working at the present, I don't think it got updated after the major code changes a little while ago (Someone please correct me if I'm wrong) getting that code to compile would be your first step. According to the specs, the hardware itself is not that different from the M version. Seems not to be the case however. bye, andreas Regards Mark Wilkinson. ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
RE: new free software foundation crusade: http://www.fsf.org/campaigns/free-bios.html
Hi Ron, Andreas, Andreas, which version of LB where you looking at ? People still seem to be getting on ok with V1 and the HOW-TO I wrote some time ago. Which version of the EPIA are you using, is it the original EPIA or one of the other version (ie EPIA-M, EPIA-MII etc) ? If it's the EPIA, I may be able to help. Quoting "Ronald G. Minnich" : On Tue, 1 Mar 2005, Andreas Thienemann wrote: [new website] > volunteers? Well, I would volunteer to a) create the new webpage and b) set it up with some kind of CMS so that someone else can fill it with content. OK, guys, we've got a new web site for linuxbios, courtesy Stefan. Check it out: wiki.linuxbios.org Only problem: I have been trying to get linuxbios running on one of our epia boards and failed horribly. that's because somebody appears to have busted linuxbios/epia recently :-( Ron, Do you mean the EPIA, or the EPIA-M ? I didn't think anyone had updated the EPIA-M after the recent code changes. If it's the EPIA, I can't see what's broken against my checked out version, and nobody seems to be making any changes to the epia code that I can see. ron ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios Regards Mark Wilkinson. ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Anybody having success with EPIA 800? (was Re: EPIA halting after vt8601 init?)
Hi Al,
Quoting Al Hooton <[EMAIL PROTECTED]>:
On Thu, 2005-01-20 at 09:45 -0700, Ronald G. Minnich wrote:
I'm quite certain it is memory, this is always the scenario with this type
of output. I may still be wrong, but I doubt it. Certain problems occur
over and over again, and this looks to be one of them. Can you be sure
that your northbridge setup is duplicating fuctory bios?
Short form: is *anybody* currently taking a CVS download, and
successfully building/running for an EPIA 800 target? If so, please let
me know -- I'm beating my head against some kind of wierdness that I
have not yet grokked, and I'm wondering if something has broken since
the last know time this worked.
The short form answer is yes and no. I have a mostly current EPIA cvs
download,
that despite my best efforts at code tidying, continues to build and run every
now and again.
From reading the thread here, it looks like you are getting to the
bottom of the
code in northbridge/via/vt8601/raminit.c
i'd suggest trying this
just before the
print_err("vt8601 done.");
line, add
dumpnorth(north);
and compare the register settings against the lspci -xxx -s 0:0.0
You may need to tweek your logging level to get output from dumpnorth.
The important registers are 0x64->0x66, 0x68, 0x69
I had similer troubles (hanging at vt8601 done) until i did this. Turned out I
had PC133 memory and the config was setting up for PC100
Depending on the values from the factory bios, you may need to alter the
definitions of DIMM_PC133 and DIMM_CL2 at the top of raminit.c to get you
going.
Mark.
This message was sent using ISPMailNow.com
___
Linuxbios mailing list
Linuxbios@clustermatic.org
http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Small and fast systerm.
Quoting "Ronald G. Minnich" : for our tuturoials we found the EPIAs with linuxbios to boot 100% of the time, and this was several dozen of them. Hmmm, guess this means I have a problem here Was that V1 or V2 ? I don't remember having problems with V1 code. What version of gcc etc did you use/are you using ? ron ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios Mark. This message was sent using ISPMailNow.com ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Small and fast systerm.
Quoting ebiederman@lnxi.com: [EMAIL PROTECTED] writes: Hi Bari, I have the plain old VIA EPIA (800/5000) working a good 80 % of the time. Not sure if my problems are buggy northbridge setup or buggy motherboard - it generates some spurious serial at power on, and sometimes hangs reading the smbus to size the ram. The spurious serial at power on. (Assuming it is just a character) sounds like normal line noise. Unfortunately not, it's more like a couple of dozen characters, which if the reset button is pressed, come out as text from LB. I'm assuming that the spurious characters are because the serial UART is not setup the first time power is applied, but is still configured when the reset button get's pressed. As for smbus they seem to be the most common board problem I have seen. Last time I trace one down it really was a board design defect, and made using lmsensors on that board impossible. In any event it is not terribly hard to put in timeouts and board resets to get past smbus problems. Although if you are having problems 20% of the time that is much more often then I have seen problems on other boards. Usually I see problems closer to the 1% mark. Eric The 20% is just an estimate, it could well be more or less than this. I could have been miss lead as to the smbus as well, i'm basing this assumption on the fact it always seems to hang when reading the SDRAM config registers for the first memory bank. Mark. This message was sent using ISPMailNow.com ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Small and fast systerm.
Hi Bari, Quoting Bari Ari <[EMAIL PROTECTED]>: Frank wrote: Just FYI we're working on V2 for the CN400 (Epia-nano). -Bari The board looks very attractive for an application I'm thinking about. If I were to go out and buy an Epia board tomorrow, which one should I get if I want to use V2... Anyone know the status of all the Epia's working with V2? I have the plain old VIA EPIA (800/5000) working a good 80 % of the time. Not sure if my problems are buggy northbridge setup or buggy motherboard - it generates some spurious serial at power on, and sometimes hangs reading the smbus to size the ram. CVS is upto date with my current northbridge code, but not my clean up of the southbridge code. -Bari ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios Mark. This message was sent using ISPMailNow.com ___ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: epia problem/Epia status update
Hi Ron, Luc, Quoting "Ronald G. Minnich" <[EMAIL PROTECTED]>: On Sat, 4 Dec 2004, Luc Belliveau wrote: Here is the output from lspci on my board *00:00.0 Host bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia] (rev 05) 00:01.0 PCI bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia AGP] 00:11.0 ISA bridge: VIA Technologies, Inc. VT8231 [PCI-to-ISA Bridge] (rev 10) 00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) 00:11.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 1e) 00:11.3 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 1e) 00:11.4 Bridge: VIA Technologies, Inc. VT8235 ACPI (rev 10) 00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio Controller (rev 40) 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 51) 01:00.0 VGA compatible controller: Trident Microsystems CyberBlade/i1 (rev 6a) * What did you want me to double check about my IDE exactly? I haven't changed any of the defaults in LinuxBIOS with the exception of the CONFIG_CONSOLE_SERIAL8250 and the loglevels. I don't know how to set IDE back into non-native PCI and I'm not sure what Mark has done. FILO is finding the IDE controller just fine. We need to start looking at settings on the 8231 to make sure the IDE is in non-native mode. I'm on travel and can't help until next week but I hope Mark can. I've not touched the southbridge code that set's up the ide in CVS yet, so it should be as it was before the big code cleanup. I'm working on seperating it out in my private copy, so I'm not sure what's happening here. It sound's like the vt8231_init routine in vt8231.c is either not running, or that enable_native_ide is set to 1 somewhere, check the latter first. ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios Mark. This message was sent using ISPMailNow.com ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: epia problem/Epia status update
Ron, Consider me Pre-Pinged ! I've already e-mailed Luc and the list, I guess you haven't caught up with your e-mail yet :-) There is definately a need to add the following 2 lines to mainboard/via/epia/Options.lb use CONFIG_CONSOLE_SERIAL8250 default CONFIG_CONSOLE_SERIAL8250=1 Current status of my epia code is as follows :- It's booted ! All the way though LB, loaded a kernel via filo from the hard disk and let me login. There are issues with the speed, the boot sequence seemed painfully slow. This could be for any number of mis-configured settings at my end. I also seem to have some spurious output before getting to the following line LinuxBIOS-1.1.7.0Normal (date) starting... which seems to be part of the northbridge debug lines I haven't tracked down whats going on here yet. At present, I'm trying to clean up the southbridge code. Regards Mark. Quoting "Ronald G. Minnich" <[EMAIL PROTECTED]>: On Fri, 3 Dec 2004, Luc Belliveau wrote: I compiled from freebios2 from cvs, when I boot all I get back from the serial port is: LinuxBIOS-1.1.7.0Normal starting.. vt8601 init starting Slot 00 is SDRAM 0400 bytes x2 Slot 01 is empty Slot 02 is empty Slot 03 is empty vt8601 is done that's it. I tried changing the DEFAULT_CONSOLE_LOGLEVEL but when I do that the resulting rom stops at Slot 00 is SDRAM 0400 bytes x2. well we need to ping mark wilkinson, as he just committed a bunch of fixes ... Mark? ron ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios This message was sent using ISPMailNow.com ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: epia problem
Hi Luc, Can you check that you have the following lines in mainboard/via/epia/Options.lb use CONFIG_CONSOLE_SERIAL8250 default CONFIG_CONSOLE_SERIAL8250=1 I had a similar problem until I added these. You should see LB getting a little further. Regards Mark Wilkinson Quoting Luc Belliveau <[EMAIL PROTECTED]>: I compiled from freebios2 from cvs, when I boot all I get back from the serial port is: LinuxBIOS-1.1.7.0Normal starting.. vt8601 init starting Slot 00 is SDRAM 0400 bytes x2 Slot 01 is empty Slot 02 is empty Slot 03 is empty vt8601 is done that's it. I tried changing the DEFAULT_CONSOLE_LOGLEVEL but when I do that the resulting rom stops at Slot 00 is SDRAM 0400 bytes x2. I can't add uses DEFAULT_CONSOLE_LOGLEVEL or option DEFAULT_CONSOLE_LOGLEVEL in the Config.lb file either, the buildtarget scripts shuns it. I'm using FILO as the payload, with no vga bios yet. Could it be a FILO problem? I've never seen linuxBIOS before yesterday so I don't know what should be appearing on the terminal.. Any assistance would be appreciated :) Luc ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios This message was sent using ISPMailNow.com ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
devices/pci_devices.c
Hi Eric, Ron,
I noticed what might be a slight problem with some error messages in the
pci_level_irq routine. When it reports the new settings, it masks off the lower
nibble of intBits to compare against the byte read. If an interrupt line is set
in the upper nibble of the byte, then the error message will always be
displayed even if the setting was successful.
I've included a diff that should fix the masks.
Regards
Mark Wilkinson.
This message was sent using ISPMailNow.com
Index: freebios2/src/devices/pci_device.c
===
RCS file: /cvsroot/freebios/freebios2/src/devices/pci_device.c,v
retrieving revision 1.29
diff -u -r1.29 pci_device.c
--- freebios2/src/devices/pci_device.c 21 Oct 2004 10:43:55 - 1.29
+++ freebios2/src/devices/pci_device.c 2 Dec 2004 10:15:11 -
@@ -924,13 +924,13 @@
/* this seems like an error but is not ... */
#if 1
- if (inb(0x4d0) != (intBits & 0xf)) {
+ if (inb(0x4d0) != (intBits & 0xff)) {
printk_err("%s: lower order bits are wrong: want 0x%x, got 0x%x\n",
-__func__, intBits &0xf, inb(0x4d0));
+__func__, intBits &0xff, inb(0x4d0));
}
- if (inb(0x4d1) != ((intBits >> 8) & 0xf)) {
- printk_err("%s: lower order bits are wrong: want 0x%x, got 0x%x\n",
-__func__, (intBits>>8) &0xf, inb(0x4d1));
+ if (inb(0x4d1) != ((intBits >> 8) & 0xff)) {
+ printk_err("%s: high order bits are wrong: want 0x%x, got 0x%x\n",
+__func__, (intBits>>8) &0xff, inb(0x4d1));
}
#endif
}
CVS Commit
Hi All, I've just committed changes to the following files used by the VIA Epia northbridge/via/vt8601/raminit.c southbridge/via/vt8231/vt8231_early_smbus.c Changes are as follows :- re-written smbus_read_byte based on intel/i82801dbm after suggestion from ron, modifications to raminit to handle changes on re-written routine. Regards Mark Wilkinson. This message was sent using ISPMailNow.com ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Patch for V2 new config
Hi Greg,
On Wednesday 01 Oct 2003 16:25, Greg Watson wrote:
> If my understanding is correct, you want to have an option value that
> has a mainboard specific default value, but that can be overridden in
> the target configuration file?
Not quite, Ron (I assume it was Ron) already added a line like
default ROM_SIZE 256*1024
to the src/mainboard/via/epia/Config.lb file (there are similar lines for
solo and one other I think) in the CVS snapshot (20031001-1400)
What my patch does is make that line work so that the buildtarget command will
work out of the box (or cvs snapshot) in the targets diretory for
./buildtarget via/epia
The solo and other one (hdama) both have 'option ROM_SIZE ' lines in
their target Config.lb files
I think what was trying to be achived is that the mainboard config file has a
default rom size for the flash part supplied with that mainboard, and if you
want to override it (say you have a larger flash part) you can in the target
config file.
>
> If this is the case, then my preference would be to do something like
> the following in the mainboard file:
>
> if ~ ROM_IMAGE_SIZE
> option ROM_IMAGE_SIZE = 65536
> end
>
> where the '~' operator means "hasn't been set".
>
> It seems to me this would be clearer than changing a default value,
> possibly after the value has already been set.
>
> Greg
>
> At 3:44 PM +0100 1/10/03, Mark Wilkinson wrote:
> >Hi Ron,
> > I started looking at building the Via/Epia with the v2, and
> >noticed that your
> >last snapshot said that the mainboard Config.lb should set the ROM_SIZE to
> >265K.
> >
> >Here's a little patch that lets the config python use
> >'default OPTION value' tag in the Mainboard Config.lb overriding the value
> > set in config/Optins.lb (which has ROM_SIZE set to NONE)
> >
> >or should the command be 'default OPTION=' in which case, alter the
> >line for 'rule default<>: ...' to read
> > rule default<>: DEFAULT ID EQ value {{ if(C):
> > mbdefault(ID,value) }}
> >
> >Regards
> >Mark Wilkinson.
> >
> >PS. Hope to burn a V2 epia bios tomorrow morning and test !!
> >Attachment converted: Macintosh HD:config.patch (TEXT/ttxt) (002EE9D4)
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
Patch for V2 new config
Hi Ron,
I started looking at building the Via/Epia with the v2, and noticed that your
last snapshot said that the mainboard Config.lb should set the ROM_SIZE to
265K.
Here's a little patch that lets the config python use
'default OPTION value' tag in the Mainboard Config.lb overriding the value set
in config/Optins.lb (which has ROM_SIZE set to NONE)
or should the command be 'default OPTION=' in which case, alter the
line for 'rule default<>: ...' to read
rule default<>: DEFAULT ID EQ value {{ if(C): mbdefault(ID,value) }}
Regards
Mark Wilkinson.
PS. Hope to burn a V2 epia bios tomorrow morning and test !!diff -ur freebios2-1400/util/newconfig/config.g freebios2/util/newconfig/config.g
--- freebios2-1400/util/newconfig/config.g 2003-09-26 12:40:05.0 +0100
+++ freebios2/util/newconfig/config.g 2003-10-01 15:26:10.0 +0100
@@ -521,6 +521,15 @@
self.default = 1
self.loc = loc
+ def altdefault(self, value, loc):
+ global global_option_values
+ if (self.default):
+ warning("default value for %s already set" % self.name)
+ setdict(global_option_values, self.name, value)
+ self.defined = 1
+ self.default = 1
+ self.loc = loc
+
def setnodefault(self, loc):
self.default = 1
self.defined = 0
@@ -872,6 +881,16 @@
v = option_value(value)
o.setdefault(v, loc)
+def mbdefault(name, value):
+ global loc, global_options
+ o = getdict(global_options, name)
+ if (not o):
+ return
+ if (o.default):
+ print "setdefault: modifing default for %s" % name
+ v = option_value(value)
+ o.altdefault(v, loc)
+
def setnodefault(name):
global loc, global_options
o = getdict(global_options, name)
@@ -1488,7 +1507,7 @@
#mainboard config files are special, in that they can also have
# default values.
rule mainboard_cfgfile: (uses<<1>>)*
-(defstmts<<1>>)*
+(default<<1>>)*
(stmt<<1>>)*
EOF {{ return 1 }}
@@ -1550,6 +1569,9 @@
# ENTRY for parsing a delayed value
rule delexpr: "{" expr "}" EOF {{ return expr }}
+
+rule default<>: DEFAULT ID value {{ if(C): mbdefault(ID, value) }}
+
rule defstmts<>: {{ d = 0 }}
( DEFAULT
( value {{ setdefault(ID, value) }}
Re: UK supplier of Bios Saviour or SST39SF020A 70-4C-NH Flash Part
Hi James, You can get a BIOS Saviour from a company called SCAN in the UK (www.scan.co.uk) It's hidden away on the overclocking products page. Regards Mark. On Wednesday 06 Aug 2003 18:59, James Weir wrote: > Does anyone now of suppliers for either of the above ( see subject ) ? > > > > Thanks, James ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Do I need to make Makefile.conf for myself?
If you haven't build the mkelfImage yet, the first step it to run the configure program provided so that it can work out how to compile the mkelfImage program. in the directory you untar'd mkelfImage type the following ./configure it should then give a long output checking for various things once it's finished, make make install which should install the mkelfImage programs to /usr/local/bin Regards Mark. On Friday 25 Jul 2003 07:40, gimyung han wrote: > Thanks to your help, I could succeed in setup dhcp server and tftp > > And then, I tried to get over to next step, making elfboot image. > > At first time, I just typed whole command written in the HOWTO, but I > failed with "Error: no Makefile.conf " > > so I changed the original file, "Makefile.conf.in" to "Makefile.conf", then > I typed whole command again. > > After all, I failed and saw following message: > "bash: ./mkelfImage: @PERL@: bad Interpreter: No such file or directory > exist" > > Did I need to make my own Makefile.conf instead of changing > Makefile.conf.in? > If so, How can I make my own? > > thanks for your help > > _ > MSN Messenger를 통해 온라인상에 있는 친구와 대화를 나누세요. > http://messenger.msn.co.kr > > ___ > Linuxbios mailing list > [EMAIL PROTECTED] > http://www.clustermatic.org/mailman/listinfo/linuxbios ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: EPIA Howto Update
Hi Sone, Thanks for the comments, looks like an update to the update will be on it's way shortly ! On Friday 18 Jul 2003 05:56, SONE Takeshi wrote: > On Fri, Jul 18, 2003 at 01:29:48AM +0100, Mark Wilkinson wrote: > > Just a quick note to say that I've updated my EPIA howto to include a > > little section for the brave on enabling the onboard VGA. > > > > This is based on Sone Takeshi's work. > > > > Thanks to Andrew Ip for committing the update to CVS. > > Hi Mark, > Thank you for your work. > > Perhaps everyone already forgets about it, but I was asked by Ron > for a HOWTO on EPIA+VGA. > I started it, but it isn't finished. (I was fiddling with BOOT_IDE etc > to include in my documentation...) > Now that your HOWTO covers VGA, everything is OK. > > Some points... > > - Line 37-40: > NOTE: At present, the epia can be booted with a serial console. Power > management to turn off the power is not available, neither is the > video bios. Memeory is currenly hard coded to report 64M - you must > have at least this much memory. > > You can use video console once VGA is enabled (option VIDEO_CONSOLE=1). > It isn't very useful however, since VGA initialization is almost at the > end of LinuxBIOS execution. > Memory configuration is also fixed already. Oops, forgot all about the memory configuration being fixed, and I haven't had a chance to play with the VIDEO_CONSOLE=1 option yet (old story about not being enough hours in the day... :-) > > - Line 364-367: > 0 - Disable Framebuffer > 1 - 1 Mbyte > 2 - 2 Mbytes > 8 - 8 Mbytes > > This is incorrect. Valid values are 2, 4, and 8 (MB). > To disable framebuffer, remove the option HAVE_FRAMEBUFFER. Will correct that, although what I can remember from the northbridge docs is that a setting of 0 also disables the framebuffer - perhaps this option is really a 'have framebuffer, but don't share with it memory option' > > Also, now I use folowing lines in the config for the VGA BIOS image to be > patched in the romimage: > option ZKERNEL_START=0xfffc > option VGABIOS_START=0xfffe > addaction romimage dd if=/path/to/vgabios.bin of=romimage bs=65536 \ > seek=2 conv=sync conv=notrunc > This way you don't have to handcraft the vga+eb payload. so this copies the vgabios into the rom image after the payload (not the otherway around) doesn't copying 65536 bytes to 0xfffe000 overwrite the Linuxbios part of the rom image ? or is that done afterwards, in which case the LinuxBIOS would overwrite part of the vgabios image... althought, I think the VGA bios is only 48K in size isn't it ! I'll have to try this, just to get my head around what's happening ! Regards Mark. ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
EPIA Howto Update
Hello All, Just a quick note to say that I've updated my EPIA howto to include a little section for the brave on enabling the onboard VGA. This is based on Sone Takeshi's work. Thanks to Andrew Ip for committing the update to CVS. Regards Mark. ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Any EPIA etherboot success stories?
On Friday 11 Jul 2003 01:12, David Hendricks wrote: > EPIA howto? I must've overlooked it in my extensive Googling. It's in the HOWTO directory from CVS. > > I tried fff8 because when I run flash_rom, it finds my SST28SF040A at > that address. I did notice, however, that you and Sone used fffc for > the zkernel_start address. fff8 does not seem to work at all, so I > guess the Epia specifically looks for that address. Oh, you've got a 28SF040 the chip my EPIA came with is a 39SF020A, which is half the size (hence using 0xfffc) What you might need to do, is set the zkernel_start to 0xfff8, AND set the ROM_SIZE to 524288. why ? well, memory address is 0 to 0x which is a total of 0x1 bytes. the bios rom sits at the top of this and extends from 0x down. if your rom chip is 256K this will extend down my 0x4 bytes ( to start at 0xfffc) as you rom is 512K, this will extend down by 0x8 bytes (and start at the correctly used and found 0xfff8) There may be some magic in the Makefiles that works out the correct ZKERNEL_START from the rom size, but you will need to set the ROM_SIZE option to the size of your rom chip ! You may also have to increase the PAYLOAD_SIZE option by 256K As to the version of etherboot, i've not used 5.1 to boot from the network, only used it to boot from a CF disk regards Mark. > > My fault for not keeping the epia.config file exactly the same as it was > used in the minicom log. That's what I get for being a packrat and keeping > so many of them sitting around. The config I'm currently using is exactly > the same, but using fffc. > > As for my etherboot version, it was originally downloaded using CVS on > June 25. I'm using version etherboot-5.1. > > > On Thursday 10 Jul 2003 23:20, Mark Wilkinson wrote: > >> Hi David, > >>If you mean has anyone managed to boot a Via EPIA using etherboot as > >> the > >> payload, and loading the kernel via (no pun) tftp, then yes but then > >> I > >> wrote it all down in the EPIA howto :-) > > > > oops, hit the wrong key there... > > > > what seems to be the problem that you're having ? your epia.config, the > > zkernel_start address looks odd. My configs have this option commented > > out or > > set to 0xfffc000 > > > > what version of etherboot are you using ? > > > > > > Regards > > Mark. > > > >> Regards > >> Mark. > >> > >> On Thursday 10 Jul 2003 23:22, David Hendricks wrote: > >> > I see a lot of people here have gotten LinuxBIOS working with the Via > >> > EPIA using an IDE device, but has anyone managed to get it working > >> > >> using > >> > >> > etherboot to boot a kernel over a network? I'm a hopeless newbie and > >> > >> have > >> > >> > been struggling with this for some time. I have links to logs, my > >> > payload, and my config below (Trying to keep the list archives tidy). > >> > > >> > I had gotten etherboot working with the PCM-5823s earlier and compared > >> > the minicom log with that of my Epia. The only real obvious > >> > >> discrepency I > >> > >> > see is the entry point. The Geode entered at 0x00094000 (606,208), > >> > >> while > >> > >> > the Epia is trying to enter at 0x0002 (131,072). > >> > > >> > I'm using CVS versions of Etherboot and LinuxBios. However, I haven't > >> > been able to update in the past one or two weeks due to Sourceforge's > >> > problems so I might have missed an important patch. > >> > > >> > Links > >> > EPIA minicom log (High verbosity): > >> > http://www.flagen.com/~sc/linux/funstuff/epia-dave > >> > My Rhine payload: > >> > http://www.flagen.com/~sc/linux/funstuff/via-rhine-ebcvs.elf > >> > My config file: http://www.flagen.com/~sc/linux/funstuff/epia.config > >> > Geode (Elfboot part only): > >> > http://www.flagen.com/~sc/linux/funstuff/geode-elfboot-dave > >> > > >> > TIA > >> > --David > >> > ___ > >> > Linuxbios mailing list > >> > [EMAIL PROTECTED] > >> > http://www.clustermatic.org/mailman/listinfo/linuxbios > >> > >> ___ > >> Linuxbios mailing list > >> [EMAIL PROTECTED] > >> http://www.clustermatic.org/mailman/listinfo/linuxbios > > > > ___ > > Linuxbios mailing list > > [EMAIL PROTECTED] > > http://www.clustermatic.org/mailman/listinfo/linuxbios > > ___ > Linuxbios mailing list > [EMAIL PROTECTED] > http://www.clustermatic.org/mailman/listinfo/linuxbios ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Any EPIA etherboot success stories?
On Thursday 10 Jul 2003 23:20, Mark Wilkinson wrote: > Hi David, > If you mean has anyone managed to boot a Via EPIA using etherboot as the > payload, and loading the kernel via (no pun) tftp, then yes but then I > wrote it all down in the EPIA howto :-) > oops, hit the wrong key there... what seems to be the problem that you're having ? your epia.config, the zkernel_start address looks odd. My configs have this option commented out or set to 0xfffc000 what version of etherboot are you using ? Regards Mark. > > Regards > Mark. > > On Thursday 10 Jul 2003 23:22, David Hendricks wrote: > > I see a lot of people here have gotten LinuxBIOS working with the Via > > EPIA using an IDE device, but has anyone managed to get it working using > > etherboot to boot a kernel over a network? I'm a hopeless newbie and have > > been struggling with this for some time. I have links to logs, my > > payload, and my config below (Trying to keep the list archives tidy). > > > > I had gotten etherboot working with the PCM-5823s earlier and compared > > the minicom log with that of my Epia. The only real obvious discrepency I > > see is the entry point. The Geode entered at 0x00094000 (606,208), while > > the Epia is trying to enter at 0x0002 (131,072). > > > > I'm using CVS versions of Etherboot and LinuxBios. However, I haven't > > been able to update in the past one or two weeks due to Sourceforge's > > problems so I might have missed an important patch. > > > > Links > > EPIA minicom log (High verbosity): > > http://www.flagen.com/~sc/linux/funstuff/epia-dave > > My Rhine payload: > > http://www.flagen.com/~sc/linux/funstuff/via-rhine-ebcvs.elf > > My config file: http://www.flagen.com/~sc/linux/funstuff/epia.config > > Geode (Elfboot part only): > > http://www.flagen.com/~sc/linux/funstuff/geode-elfboot-dave > > > > TIA > > --David > > ___ > > Linuxbios mailing list > > [EMAIL PROTECTED] > > http://www.clustermatic.org/mailman/listinfo/linuxbios > > ___ > Linuxbios mailing list > [EMAIL PROTECTED] > http://www.clustermatic.org/mailman/listinfo/linuxbios ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: Any EPIA etherboot success stories?
Hi David, If you mean has anyone managed to boot a Via EPIA using etherboot as the payload, and loading the kernel via (no pun) tftp, then yes but then I wrote it all down in the EPIA howto :-) Regards Mark. On Thursday 10 Jul 2003 23:22, David Hendricks wrote: > I see a lot of people here have gotten LinuxBIOS working with the Via EPIA > using an IDE device, but has anyone managed to get it working using > etherboot to boot a kernel over a network? I'm a hopeless newbie and have > been struggling with this for some time. I have links to logs, my payload, > and my config below (Trying to keep the list archives tidy). > > I had gotten etherboot working with the PCM-5823s earlier and compared the > minicom log with that of my Epia. The only real obvious discrepency I see > is the entry point. The Geode entered at 0x00094000 (606,208), while the > Epia is trying to enter at 0x0002 (131,072). > > I'm using CVS versions of Etherboot and LinuxBios. However, I haven't been > able to update in the past one or two weeks due to Sourceforge's problems > so I might have missed an important patch. > > Links > EPIA minicom log (High verbosity): > http://www.flagen.com/~sc/linux/funstuff/epia-dave > My Rhine payload: > http://www.flagen.com/~sc/linux/funstuff/via-rhine-ebcvs.elf > My config file: http://www.flagen.com/~sc/linux/funstuff/epia.config > Geode (Elfboot part only): > http://www.flagen.com/~sc/linux/funstuff/geode-elfboot-dave > > TIA > --David > ___ > Linuxbios mailing list > [EMAIL PROTECTED] > http://www.clustermatic.org/mailman/listinfo/linuxbios ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: [epia] Unknown bootloader class
Hello HyungJong Thanks for the config information. I can only see one difference between your config and my own. That is the CFLAGS32+= -DASK_BOOT=3 -DANS_DEFAULT=ANS_NETWORK line, which I don't have enabled, but I can't see that being the cause of your problem. Just for Information, I'm using version 1.16 of mkelfImage As for you second question, I'm not sure about the values in raminit being optimised. I think they are configured to 'work' for 64Mbytes of memory - any more just get's ignored. For my 128Mb system, I've changed to the following 5a = 0x08 5b->5f,56,57 = 0x10 as these are what the original BIOS set for my memory module. Andrew Ip may be able to tell you more on this. The one document I've not seen is the BIOS porting guide. Just can't seem to find it freely available on the web. Regards Mark Wilkinson ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: [epia] Unknown bootloader class
Hello HyungJong, I'm beginning to wonder if the problem you are seeing lies with the configuration of etherboot you've used. My thinking is that etherboot thinks it's executing a different type of image (ie FreeBSD, Multiboot, etc) rather than an ELF image, and is thus passing some different information across. Can you forward the Config file that you used to build the etherboot payload ? Regards Mark Wilkinson. ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: [epia] Unknown bootloader class
Hello HyungJong Thanks for the configuration information. I'd first suggest using a more recent version of the kernel (2.4.18 or higher) as these have support for the Via C3 processor. Second, I'd also suggest configuring the kernel with the following options set/unset. If you go for a newer kernel, select C3 as the processor type. Disable SMP - it's a single processor ! Disable Power management - LinuxBIOS does not have any support at present. Set PCI access to DIRECT rather than ANY Disable the EtherExpress 1000 network card Enable the Via Rhine network card. Until you get the kernel working, I'd also disable sound support. I've also finally managed to track down the 'Unknown bootloader class' message to the mkelfimage utility (elf32-i386/convert_params.c). Perhaps Eric Biederman can comment more on the problem. Regards Mark Wilkinson. ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
Re: [epia] Unknown bootloader class
Title: Message Hello ! looking through the debug messages you've supplied, the problem seems to be with the image that you've loaded. The linuxbios + etherboot seems to have worked fine - Etherboot hands over to your image just after the 'rhine disable' message. Have you tried booting a stock kernel image ? Can you supply more information on the image you are loading ? What kernel version, configuration info etc. Regards Mark Wilkinson
Re: flash_rom.c
Hi Ron,
I've updated the patch slightly to add a routine to enable flash writes on
the epia mainboard with out the need for the seperate setpci command.
Mark
On Friday 28 Feb 2003 22:13, Ronald G. Minnich wrote:
> thanks for the patch!
>
> I'll try to get it in today or monday.
>
> ron
--- freebios/util/flash_and_burn/flash_rom.cFri Feb 28 17:21:37 2003
+++ mod-freebios/util/flash_and_burn/flash_rom.cSat Mar 1 15:37:40 2003
@@ -146,6 +146,30 @@
return 0;
}
+int
+enable_flash_epia(struct pci_dev *dev, char *name) {
+/* register 40.b gets bit 4 set to enable flash access
+ * information from README file for epia mainboard
+ *
+ * Should I put a check to make sure it only gets set on device 0:11.0 ?
+ *
+ */
+ unsigned char old, new;
+ int ok;
+
+ old = pci_read_byte(dev, 0x40);
+
+ new = old | 0x10;
+
+ ok = pci_write_byte(dev, 0x40, new);
+ if (!ok) {
+printf("Failed to set 0x%x to 0x%x on %s and got 0x%x (WARNING ONLY)\n",
+ old, new, name, ok);
+return -1;
+ }
+ return 0;
+}
+
struct flashchip * probe_flash(struct flashchip * flash)
{
int fd_mem;
@@ -260,6 +284,7 @@
{0x1, 0x1, "sis630 -- what's the ID?", enable_flash_sis630},
{0x8086, 0x2480, "E7500", enable_flash_e7500},
+ {0x1106, 0x8231, "Via EPIA", enable_flash_epia},
};
int
@@ -291,7 +316,8 @@
}
/* now do the deed. */
- enable->doit(dev, enable->name);
+ if ( enable )
+enable->doit(dev, enable->name);
return 0;
}
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
flash_rom.c
Hello I'm not sure who this should be addressed to, so appologies to the rest of the list. Briefly, I'm interested in running linuxBios on a via epia board, so I've gotten hold of a bios saviour ready to see how far I can get. After compiling up a rom image, and scanning the archives for how to burn the flash from linux, I compiled up the flash_rom program from the util directory. When running it with no image name (just so I could identify the flash chip of the bios saviour) I was greeted with a segmentation fault. To cut the story short, it seems that after scanning the pci bus in enable_flash_write() and not finding any of the devices in the enables (enable still set to 0) it still tries to call the 'doit' routine. I've included a patch that corrects the problem. Hope it's of use to someone. The second question I have (I think this is for Ron or Eric) is about the Config file under src/arch/i386/lib. I've notice that it has two copies of the 'object c_start.S' line. Is there a reason for this ? I've noticed that the NLBConfig.py script generates warnings about re-defining the object. Regards Mark Wilkinson --- orig/util/flash_and_burn/flash_rom.cFri Feb 28 17:21:37 2003 +++ freebios/util/flash_rom.c Fri Feb 28 20:56:55 2003 @@ -291,7 +291,8 @@ } /* now do the deed. */ - enable->doit(dev, enable->name); + if ( enable ) +enable->doit(dev, enable->name); return 0; } ___ Linuxbios mailing list [EMAIL PROTECTED] http://www.clustermatic.org/mailman/listinfo/linuxbios
