serial port speed was an issue months ago. dont know if that has been fixed.
try to lower the speed on the serial terminal (if you've configured 115200, try
57600)
niki
On 24-Mar-2004 Shawn Perkin wrote:
> Hello all,
>
>
>
> I'm currently in the process of trying to get Linuxbios to work on my
On 06-Jan-2004 Devi Priya wrote:
> Hi.
> Thanks.
> I want to have linuxbios, linux os and filesystem in my diskonchip
> millennium.
EXACTLY what i would like to have as well.
> Mine is sc1200.
ok. i have an epia-m board.
> If I use linuxbios to which physical address
> should the DOCM be mapp
i'd just like to confirm that the 2nd serial port on the epia-m
works if you do the modifications dave describes.
niki
On 09-Dec-2003 Dave Ashley wrote:
> In a previous email message
> http://www.clustermatic.org/pipermail/linuxbios/2003-November/005891.html
>
> I wrote
> In V1 the file to modify
i think we need a new thread for the ``intel dual netwokcard problem on epia-m'' topic.
facts (correct me if i am wrong!):
* intel dual eth nic is not working with linuxbios (2003-10-24).
* it can be plugged into the pci slot (00:14.0) of the epia-m.
* the dual nic has a pc
okay -- i got the dual card working -- somehow:
===
$ diff -u freebios-20031024.orig/src/mainboard/via/epia-m/mainboard.c
freebios-20031024/src/mainboard/via/epia-m/mainboard.c
--- freebios-20031024.orig/src/mainboard/via/epia-m/mainboard.c 2003-07-25
05:20:20.0 +0200
+++ freebios-2003102
the doc millennium "maps" the first 2 pages of the NAND flash into its high and low
address space.
it _can_ be used to boot/init memory/copy nand pages to ram/jmp to ram.
but -- you have to do all that within 512 bytes of code.
mem layout of the doc millennium (2001) is:
address
0x 512bytes b
this is maybe interesting as well:
===
# cat /proc/iomem
-0009 : System RAM
000a-000b : Video RAM area
000c-000c7fff : Video ROM
000f-000f : System ROM
0010-1dfe : System RAM
0010-00315318 : Kernel code
00315319-0043debf : Kernel data
1dff-1dff2f
i think i found the main problem:
award bios / dual ethernet nic:
===
# /sbin/lspci
00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 3123
00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP]
00:0d.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller
i have the same problem
===
PCI: No IRQ known for interrupt pin A of device :02:04.0. Please try using
pci=biosirq.
PCI: No IRQ known for interrupt pin A of device :02:05.0. Please try using
pci=biosirq.
===
with the linuxbios + the new generated irq_tables.c.
no matter if i use pci=bios
On 26-Nov-2003 ron minnich wrote:
>>
>> what is the reason for
>> ===
>> PCI: No IRQ known for interrupt pin A of device :02:04.0.
>> PCI: No IRQ known for interrupt pin A of device :02:05.0.
>> ===
>> if i use linuxbios?
>
> i have not done epia-m. this problem is due to bad irq_tables.
>> and i cannot bring the interface up.
>> (i've not tried yet with pci=biosirq...)
>
> tried with pci=biosirq kernel commandline -- same result...
> maybe it is the same result because my kernel supports
> DIRECT pci access only? i am going to try a pci ANY access
> kernel now...
unfort it is th
> and i cannot bring the interface up.
> (i've not tried yet with pci=biosirq...)
tried with pci=biosirq kernel commandline -- same result...
maybe it is the same result because my kernel supports
DIRECT pci access only? i am going to try a pci ANY access
kernel now...
if use the dual nic with the award bios on the epia-m i get:
===
Intel(R) PRO/100 Network Driver - version 2.3.30-k1
Copyright (c) 2003 Intel Corporation
e100: eth0: Intel(R) PRO/100 Network Connection
Hardware receive checksums enabled
cpu cycle saver enabled
e100: eth1: Intel(R) PRO/100 Netwo
seems to be almost the same as the epia-m + Onboard CardBus / CompactFlash...
http://www.viaembedded.com/product/epia_MII_spec.jsp?motherboardId=202
Processor
- VIA C3/ VIA Eden ESP processor
Chipset
- VIA CLE266 North Bridge
- VIA VT8235 South Bridge
System Memory
- 1 DDR266 DIMM socket
- U
i am using a epia-m 600 with success.
current cvs of freebios/linuxbios version1 works fine.
i used:
===
$ cat ../example.config | grep -v ^# | grep -v ^$
target /home/niki/packages/freebios-20031024-build
mainboard via/epia-m
option SERIAL_CONSOLE=1
option TTYS0_BAUD=115200
option DEFAULT_CONSOLE
def sure 57600 is (currently) the max on /dev/ttyS0.
(but my setup is 115200).
i dont care much, but of course it should be fixed.
/dev/ttyS0 was at 115200 when i changed from the regular
bios to linuxbios. a soft reset was ok -- still 115200.
but after pressing the power switch the port was at
57
perfect!!!
linux-2.6.0-test9-bk16 says:
===
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
===
thanks a lot!!!
niki
On 17-Nov-2003 Dave Ashley wrote:
>>setserial seems to be fine:
>
> In V
On 17-Nov-2003 Richard Smith wrote:
> Niki Waibel wrote:
>
>>
>> ~ # setserial /dev/tts/1 -a
>> /dev/tts/1, Line 1, UART: unknown, Port: 0x02f8, IRQ: 3
>> Baud_base: 115200, close_delay: 500, divisor: 0
>> closing_wait: 3
&g
On 17-Nov-2003 Dave Ashley wrote:
>>setserial seems to be fine:
>
> In V1 the file to modify is src/superio/via/vt1211/setup_serial.inc
> That code sets up ttyS0 which is the VT1211's logical device 2. You
> want to add some similiar code for logical device 3 to get ttyS1 working.
>
> Assuming y
>> any chance to get /dev/ttyS1 (/dev/tts/1) working with freebios
>> on the emia-m?
>>
>> (i need it for the smartcardreader ...)
>
> as soon as we get epia-m up under v2.
seems that that v2 will take some time.
i'd like to hack v1 to get it running.
is
src/lib/serial_subr.c:
vo
any chance to get /dev/ttyS1 (/dev/tts/1) working with freebios
on the emia-m?
(i need it for the smartcardreader ...)
niki
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
>> > > - LinuxBios tell that the RAM is 127Mbye (and i had 256Mbyte)
>> >
>> >That's the hard coded part.
>>
>> What is the file to edit to have 256Mbyte?
>
> Just as a reminder, this is the only hardware on linuxbios that you "patch
> a file" to get memory size, and we hope to fix this soon
what is the current dev status of epia-m in v2?
niki
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
> Yeah, but it's free. It's hard to complain too hard.
i always start my update like this:
$ while ! cvs update; do sleep 5; done
normally after about 5 retries you get a connection.
but i've had days in which 25 retries were done...
niki
___
Linu
hi ian,
> The first is that I think the comments in the code may be a bit misleading
> (apologies to the original author!)
>
> AIUI the registers at 0x56 and 0x57 (and 0x5E and 0x5F as well) should be
> set to the same value as 0x5D i.e. the DRAM ending address for your highest
> populated ban
On 25-Sep-2003 Ronald G. Minnich wrote:
> http://www.idot.com/TheStore/Desktop/777spec.asp?Product.id=777&Cate.id=14&Product.status=green
>
> $45.
>
> So we can get our EPIA with linuxbios from cwlinux.com, and then load
> them into this case. Might be a way to go.
>
> if only we could get 1
i use a 512MByte mem module in the epia-m 600mhz and linuxbios sayes:
===
totalram: 127M
===
i modified src/northbridge/via/vt8623/northbridge.c
===
diff -u -N -r freebios-20030924.old/src/northbridge/via/vt8623/northbridge.c
freebios-20030924/src/northbridge/via/vt8623/north
bridg
e.c
--- freebi
okay.
i found 2 reasons why linuxbios on my epia-m 600mhz was not booting.
it stopped after the following msgs on the serial console:
===
LinuxBIOS-1.0.0 Wed Sep 24 13:12:11 CEST 2003 starting...
Copying LinuxBIOS to ram.
i just got a romimage from ian smith (thanks a lot!).
see this!!!
===
LinuxBIOS-1.0.0 Tue Sep 23 21:19:35 BST 2003 starting...
Testing SDRAM : -0009
SDRAM fill:
0009
SDRAM verify:
0009
Done.
Copying LinuxBIOS to ram.
000f0fd4 4000
Jumping to LinuxBIOS.
On 23-Sep-2003 ron minnich wrote:
> On Tue, 23 Sep 2003, Niki Waibel wrote:
>
>> any idea why linuxbios is not starting on the epia-m 600?
>> i run memtest86 -- all tests (took about 24hours ;-) -> everyting ok.
>> (run memtest86 from lilo).
>> i also tri
> Based on some emails from Andrew I started poking around into the
> epia-m serial port problem. Here are my observations:
> The 9 pin internal serial port is part of the VT1211 chip, not
> the VT8235, or other chips with serial ports.
>
> Under linux all baud rates are 1/2 what they should be. S
any idea why linuxbios is not starting on the epia-m 600?
i run memtest86 -- all tests (took about 24hours ;-) -> everyting ok.
(run memtest86 from lilo).
i also tried the patch of Ian Smith <[EMAIL PROTECTED]>.
do you have an idea how i can find out which asm line the stop happens?
unfort i canno
> I find myself getting confused about all the EPIA boards and their
> configurations.
>
> Can someone help fill this in?
>
> name CPU Extension Speed RAM
> EPIA-M C3 3DNOW 800 Mhz SDRAM
EPIA-M C3 3DNOW 600 MHz
>> anyway -- running memtest86 with lilo right now and
>> it seems that everything is fine (test4 is running.
>> it will take some time to finnish). i dont think it
>> is a mem problem (but i might be wrong).
>>
>
> But the issue is, is linuxbios setting up ram correctly. I posted some
> time a
>> i've never used memtest86.
>
> make memtest86 the payload. be sure to build with serial console only.
no, no, that does not work.
the payload is never loaded/reached.
the trouble is caused earier!
right after crt0.s a jmp to the copied mem
is done. the copied mem is c_start.s at the beginning.
> I think you should get memtest86, set it up to run on serial console, and
> see if it works or not.
hmmm -- you mean with lilo?
i've never used memtest86.
will give it a try.
niki
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.o
linuxbios does not start ...
i can see:
===
LinuxBIOS-1.0.0 Mon Sep 22 02:17:36 CEST 2003 starting...
Copying LinuxBIOS to ram.
Jumping to LinuxBIOS.
===
that's it.
first i tought it is a mem problem (512MB Infineon CL2).
i changed 0x350 to 0x150 in src/northbridge/via/vt8623/raminit.inc
and i've a
he ecc stuff in the flash (nand_ecc) itself?
niki
> - Original Message -
> From: "Niki Waibel" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Wednesday, September 17, 2003 6:13 PM
> Subject: damaged DoC MD2808
my DoC MD2808-D08 responds fine to the control registers
(chipid and ecc toggle bit are ok i.e.).
but if it comes to the stage of sending nand commands and
reading memory it seems to do nothing.
if mem is read from the same IO reg (0x800) then
i always get the same value (0x55). also if the
nand
>> who knows how to init a ddr?
> It is already checked in. Checkout the memory init code under
> vt8623.
ok. this means that vt8623 == cle266?
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
>> what is so complex with ddr?
>> could you send me / point me to some more info about init a ddr?
>> or ask the guys at via?
> It is the hardware limitation since the ddr init code probably does
> not fit in ipl area of DOC which is only 512byte .
yes. i got the point. but to be sure we need to
>> More steps are required to init DDR. It might not fit
>> in 512 bytes.
>
> oops, I forgot the DDR nightmare. I think DoC is out for EPIA-M.
what is so complex with ddr?
could you send me / point me to some more info about init a ddr?
or ask the guys at via?
niki
_
hi,
i just had a funny idea...
what about haveing bios savior + DoC in a mb _and_
connecting the bios savior switch to an address pin...
that way it should be possible to have enough room
in the bios savior rom for doing everything. then
the DoC could be activated...
i think that booting should
>> i think that the CLE266 (epia-m) is quite different then the vt8601.
>> right now i've no idea about northbringes, but i hope that will change soon :)
>
> doubtful, I have found lots of reuse of cores in these norhtbridges. But
> I'm willing to be convinced :-)
>
>> where did the ppl (who hav
>> where can i get more info in how to init the mem on a
>> epia-m? do i have to rev eng the bios?
>
> src/northbridge/via/vt8601/ipl.S is code that worked for the vt8601 2
> years ago for DoC uses.
>
> Not guaranteed to work with all DRAM. The 8601 is very tricky.
[EMAIL PROTECTED] ~/freebios-
>> > where can i get more info in how to init the mem on a
>> > epia-m? do i have to rev eng the bios?
>> read the linuxbios source, of course!
> I think EPIA-M is even harder to fit into IPL.
why do you think so?
niki
___
Linuxbios mailing list
[EMAIL P
>> i am currently playing with this. my epia-m has no DIP32 socket. i
>> decided to use a DIP2PLCC adapter to use the MD2802-D08. so i can plug
>> it directly into the bios socket.
>
> please remember, getting to work in the socket is the easy part. Getting
> epia support for memory up and runnin
> does anybody have experience with DOC's on an Epia-M board? I read in a previous
> message (
> http://www.mail-archive.com/[EMAIL PROTECTED]/msg03307.html )
> that the DOC Millennium 8MB Module MD2802-D08 might work.
> Can anybody confirm
> this?
i am currently playing with this.
my epia-m has
okay -- here is the patch.
> hello,
>
> i cleaned up the util/flash_and_burn dir of linuxbios cvs 20030910.
> everyting compiles without warnings now.
>
> i am about to add support for the msystems doc device chips.
>
> who actually maintains the util/flash_and_burn tree?
> i could not find any
hello,
i cleaned up the util/flash_and_burn dir of linuxbios cvs 20030910.
everyting compiles without warnings now.
i am about to add support for the msystems doc device chips.
who actually maintains the util/flash_and_burn tree?
i could not find any email address in the files.
i am going to po
is it necessary to do some unlocking before reading/writing
to the bios area of the epia-m (vt8235)?
niki
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
okay -- it seems that things are working (a little bit).
on http://www.rootshell.be/~nwaibel/docprobe.txt you can
find the output of a modified version of docprobe.
you can see the plain mem map of the md2802-d08 there.
it is different to the md2800-d08!!!
0x: 512byte IPL -- is someone able
is there a written documentation about the DoC control registers?
(2000, millennium)
or do i have to find out from the linux kernel drivers?
niki
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
On 02-Sep-2003 ron minnich wrote:
> I think the 90 refers to speed, and I note that in my EPIA the part is a
> -70. This may be part of the problem.
that is not actually the problem.
it was never the plan to use bios savior in the production system.
i have no problem to remove bios savior and rep
On 03-Sep-2003 ron minnich wrote:
> via-rhine on 2.4.19 is working very poorly for us. We can plug a tulip
> board into the PCI slot and the board works quite well, but if we use the
> via-rhine we get errors and poor performance. Is the via-rhine driver any
> better on 2.4.19+1, 2, or more?
i
>>> is it possible that this does not work because the wires are
>>> too long (bios savior + dip2plcc adapter)?
>>
>> it is asynch. logic last time I checked.
>>
>> It could still be a timing issue however.
>>
>>> it is okay if i boot without dip2plcc converter and
>>> then plug it on top of th
>> is it possible that this does not work because the wires are
>> too long (bios savior + dip2plcc adapter)?
>
> it is asynch. logic last time I checked.
>
> It could still be a timing issue however.
>
>> it is okay if i boot without dip2plcc converter and
>> then plug it on top of the bios sa
>> but right now i have
>> epia-m + bios savior + dip2plcc adapter
>> (without doc millennium 8mbyte). bios savior is switched to its internal bios chip
>> (which works (burned the orig bios) if there is only epia-m + bios savior). but if
>> i plug the dip2plcc adapter (without touching the
i checked the dip2plcc adapter -- everything is fine.
all pins are connected properly.
is it possible that this does not work because the wires are
too long (bios savior + dip2plcc adapter)?
would it help to reduce the clockrate of the epia-m?
does someone know how that could be done?
it is okay
>> i am still trying to get this running:
>> epia-m + bios savior + dip2plcc adapter + doc millennium 8mbyte
>
> that won't work with the normal bios.
that's clear.
but right now i have
epia-m + bios savior + dip2plcc adapter
(without doc millennium 8mbyte). bios savior is switch
i am still trying to get this running:
epia-m + bios savior + dip2plcc adapter + doc millennium 8mbyte
it took quite long until all parts arrived.
anyway. the current problem is that if i plug the dip2plcc adapter
into the bios savior socket epia-m does not boot anymore...
(of course i've
On 12-Aug-2003 Michel Belleau wrote:
> Selon Niki Waibel <[EMAIL PROTECTED]>:
>> > Where could I find a DIP2PLCC adapter ?
>> http://www.epboard.com/
>
> That's what I did yesterday ;-)
>
>> i also ordered a MD-2802-D08-V3 and a MD-2202-D128-V3.
&
>> does that 2001 fit into a DIP socket?
>
> DIP32
on the m-systems website:
http://www.m-sys.com/Content/Products/DiskOnChip.asp
there is only the DiskOnChip 2000 which is in a
DIP socket.
are you really sure that that type would not work
in the bios?
is it the 8mbyte DoC millennium (not mille
> Where could I find a DIP2PLCC adapter ?
http://www.epboard.com/
i just ordered E32-0035 (still waiting).
E32-0030 seems to be too big (for my epia-m).
in addition i got the RD1 BIOS Savior from
http://www.ioss.com.tw/web/English/RD1BIOSSavior.html
the PL version works for my 600mhz epia-m.
i a
hi,
my plan is still to use a DoC 2000 on an EPIA-M mobo
with a DIP2PLCC adapter -- instead of the original
256kbyte (PLCC) bios chip.
can anyone tell me if this is theoretically possible?
niki
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.cl
quite new to all this...
just got 2 epia-m's and 2 bios saviors.
what tools do i need to flash the bios?
where do i get them?
(i'd like to flash the chips on the board...)
what do i need to activate in the kernel to
program a chip / use the flash tools?
what do i need to activate in the kernel t
>> quite new to all this...
>> just got 2 epia-m's and 2 bios saviors.
>> what tools do i need to flash the bios?
>> where do i get them?
>> (i'd like to flash the chips on the board...)
>> what do i need to activate in the kernel to
>> program a chip / use the flash tools?
>> what do i need to act
what are actually the differences between DoC 2000 and DoC Millennium?
are both versions working in linux?
which one is the newer product?
are they electrically (pins, voltage, etc) different?
are there any limitation in the size of these chips?
i mean -- could a 2GB chip be used on linux?
niki
___
does anyone know where i can order online a DoC 2000
in Austria or Europe?
--
niki w. waibel - system administrator @ newlogic technologies ag
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios
>> my plan is still to use a DoC 2000 on an EPIA-M mobo
>> with a DIP2PLCC adapter -- instead of the original
>> 256kbyte (PLCC) bios chip.
>
> that won't work, as the 2000 does not have an addressable boot block like
> the 2001.
what is the exact type i need for that?
does that 2001 fit into a
On 06-Aug-2003 [EMAIL PROTECTED] wrote:
> I am hoping someone on the list has an EPIA M-1 VIA C3 E-Series,
> could tell me which Bios Saviour kit they are using, if any
i just got the IOSS RD1-PL.
i put them into the epia-m (600mhz, because no fan)
and the orig bios works fine.
i try to
>> "custom made DIP-PLCC":
>> what did you customize?
>> there is also
>> http://www.epboard.com/eproducts/ezadapter.htm#DIP to PLCC Adapter
>> product number: E32-0030
>> name: DIP-32 to PLCC-32 eZ-Reconfigurable IC Adapter
>> which seems to be a pin reconfigurable adapter...
>> andrew, do you
>> Mine (Epia-M 1) only has 1 PLCC socket for 2/4MBit flash (no idea
>> whether more is possible)
> I think only EPIA has that socket. IIRC, Snapgear has got the driver
> for doc mil+, but I havn't seen anything yet. We have used a custom made
> DIP-PLCC adapter to connect DOC on EPIA, and L
>> hmmm - on http://www.epboard.com/ you can find a PLCC to DIP adapter.
>>
>> i'd like to know if it is possible to use E32-0041 (PLCC-32 to DIP-32
>> IC Adapter) on a epia-m board with a MD2802-D08 doc (m-systems).
>> it seems that these chips have capacities of 2, 4, 8, 12, 24, 40, 72 MByte!!!
On 07-Jul-2003 ollie lho wrote:
> On Sun, 2003-07-06 at 01:07, Niki Waibel wrote:
>> hmmm - on http://www.epboard.com/ you can find a PLCC to DIP adapter.
>>
>> i'd like to know if it is possible to use E32-0041 (PLCC-32 to DIP-32
>> IC Adapter) on a epia-m board
On 05-Jul-2003 Niki Waibel wrote:
> hi,
>
> it seems that more and more boards are using PLCC chips instead
> of DIP chips.
> (http://www.ioss.com.tw/web/English/RD1BIOSSavior/SelectionChart.html)
>
> if DIP is used you can replace the onboard bios chip (normally
> 2
hi,
it seems that more and more boards are using PLCC chips instead
of DIP chips.
(http://www.ioss.com.tw/web/English/RD1BIOSSavior/SelectionChart.html)
if DIP is used you can replace the onboard bios chip (normally
2mbit) by a 8mbyte (64mbit) (m-systems md-2800-d08 or md-2802-d08)
DIP chip. that
77 matches
Mail list logo
