Menu
▾
▴
ebolinux-devel — Ebolinux Developers
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
(1) |
Mar
(3) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
|
From: Tomas <tom...@he...> - 2007-10-07 13:36:20
|
Sorry for crossposting, but it seems that the mailing list activity is better than the Forum activity. Below is my post from the forum. I am fairly experienced with C programming and embedded systems but not a shellscript hacker, so I appreciate your help. If changing Linux distribution or version is the trick, i will do that. ------------- Hi, I have recently got myself an e-box. I have downloaded the software, but gets problems trying to build: running cook (according to the readme instructions) fails with the following error message: tomas@tomas-desktop:~$ ebolinux/bin/cook eB103 standard AC ebolinux/bin/common: 39: shopt: not found ebolinux/bin/cook: 40: Syntax error: Bad for loop variable I run a bash shell in a newly installed Ubuntu Linux v7.4. Any ideas? Cheers, Tomas, Sweden (I plan to set up the e-box to monitor at least temperature and humidity via onewire sensors in a house) |
|
From: p96support <p96...@sp...> - 2007-03-04 20:11:31
|
Hi, Is it possible to change the serial port speed to 115200? I have tried with stty, but the command does not respond. Regards /Dick L=E4s det senaste om alla v=E5ra k=E4ndisar. Var de har varit, vad det ha= r gjort och med vem. P=E5 Spray Mingel har vi full uppsikt. http://www.sp= ray.se/livsstil/mingel |
|
From: Jon-Erling D. <jo...@ga...> - 2002-10-25 21:14:19
|
Hi, I have some problems upgrading my ebox with the CVS version of ebolinux. I have an eB103 R2A manufactured 00W47. The box works fine, and I can surf to it on http://172.24.85.154/forum/, but there are no configuration options there, only bundle control and SMS simulator. It seems that it might be a production version I got my hands on. That might explain why the serial port is not enabled. I've tried both using minicom and start_ews_serial, but none of that worked. Instead I tried the start_ews_eth which seem to work. After I reboot I can connect using minicom, and I get a lot of output (included last in the mail). The problem is that I don't get a prompt. Do I need to to type some magic key sequence in order to get a prompt? What am I doing wrong? Also, pressing Ctrl-D when booting, gives me the boot loader prompt, but no matter what I write I get 'Access denied'... Any help appreciated. thanks, joda Output from startup after start_ews_serial: ------------------------------------------------------- ... eth1: transmit timed out, IRQ conflict ?? eth1: transmit underrun eth1: transmit timed out, IRQ conflict ?? eth1: transmit underrun Operation failed. Running /etc/rc.d/S35setup_pump ... DONE OK Running /etc/rc.d/S40install_certificate ... Running /etc/rc.d/S40install_certificate ... DONE OK Running /etc/rc.d/S70setup_loop_driver ... Running /etc/rc.d/S70setup_loop_driver ... DONE OK Running /etc/rc.d/S70setup_nat ... eth0 : installing NAT support. eth0 : interface is UP. Running /etc/rc.d/S70setup_nat ... DONE OK Running /etc/rc.d/S90setup_swud ... swud[63]: Initializing swud swud[63]: lstat(/tmp/opt/swud/, &st) returned -1, errno: 2 swud[63]: lstat(/mnt/tmpram_src/, &st) returned -1, errno: 2 swud[63]: EBL boot_type variable not set! Assuming normal boot swud[63]: Initializing neatboot swud[63]: lstat(/tmp/opt/swud/installer/, &st) returned -1, errno: 2 swud[63]: lstat(/tmp/opt/swud/executor/, &st) returned -1, errno: 2 swud[63]: lstat(/tmp/opt/swud/executor/db/, &st) returned -1, errno: 2 swud[63]: Start check module uhttpd swud[63]: Starting module uhttpd swud[63]: Start check module osg_adp swud[63]: Starting module osg_adp swud[63]: Start check module mserv swud[63]: Starting module mserv swud[63]: Start check module login swud[63]: Starting module login swud[63]: Start check module fw_setup swud[63]: Starting module fw_setup swud[63]: Start check module faulthandler swud[63]: Starting module faulthandler Running /etc/rc.d/S90setup_swud ... DONE OK Running /etc/rc.d/S99boxready ... Running /etc/rc.d/S99boxready ... DONE OK |
|
From: <ho...@ly...> - 2002-04-05 21:33:35
|
Hi,
I've merged the old, heavly modified, driver from the 2.2.13 ebox
port into the current 2.2.20 ebolinux kernel. The standard 2.2.20
driver *almost* work, but that's as far as I've manage to go with
it. Well, now both the ethernet cards work.
The bridging code also work. So if you've got an ADSL connection,
and want some firewall protection but not all the hassle NAT
gives you, the ebox should make a perfect solution (I'll soon
be off to the marketing department.)
Regards,
Mattias
|
|
From: <ho...@ly...> - 2002-03-30 15:21:32
|
Hi, I've applied the STP bridging patches (1.0.2) to the kernel, and incorporated the user-space bridge tools into ebolinux. All the bridging stuff seems to work, but in the process of testing it I discovered that the eth1 interface doesn't work correctly. I haven't found out why yet. What we have now is a fully functional _one-port_ filtering ethernet switch. :-) //Mattias |
|
From: <ho...@ly...> - 2002-03-24 01:53:27
|
Hi,
now we've managed to get Linux 2.2.20 up running on the eB103. I've
tried to port only the modifications that were *really* needed,
to make a possible transition to 2.4 run smoother. I've removed
most of the dependencies to the special eB10x BIOS, removed
(means: not ported) some CPU- and network monitoring stuff
that cluttered up various files such as sched.c and others. I haven't
ported any of the drivers needed for some eB101-only hardware devices
(ISDN cards and probably other stuff I can't remember right now). If
you have a eB101, and want some special driver, please let me know.
The kernel seems to work, as far as I see. It hasn't been tested
very much, but the must basic stuff like booting up, detecting the
hardware, bringing up the network interfaces etc seems to work ok.
If you want to run the more well-tested (presumably) more stable
2.2.13 you can check out using the BEFORE_NEW_KERNEL CVS tag.
And thanks to the real guru, Ulf Eklund, for the debugging help.
Kind regards,
Mattias
|
|
From: Dick <di...@ho...> - 2002-03-06 13:54:13
|
Hi, The start_esw_serial script stops with 'Waiting for e-Box to start...' as output. So I tried to connect the eb103 to my PC via a null modem cable (http://ftp.sunet.se/hwb/ca_Nullmodem9to9.html) and I used minicom with 38400 8N1 as settings. No sign of activity during the first 10 minutes. Any tip how I shall get the connection right? Regards /Dick |
|
From: Martti K. <mar...@ik...> - 2002-02-07 15:21:13
|
Hi!
I have an old eB101 and I'd like to upgrade the software on it.
Right now the EEPROM is corructed as I get "Invalid EEPROM data"
so I can only use the low level command prompt.
ROOT dhcp118:~> tip ebox
connected
Invalid EEPROM data
eBox Debugger / Diagnostics Utility
EBL Vers 1.00 Dec 10 10:21 1998
Test Module Vers 1.00 Dec 10 10:25 1998
Executing below 640k starting from 95C1:0
Invalid EEPROM Data
>ver
EBL Vers 1.00 Dec 10 10:21 1998
Test Module Vers 1.00 Dec 10 10:25 1998
I tried to download an image from Windows Teraterm with this
sequence:
1) Connect to the eBox with serial cable
2) LPT (or LPE)
3) Select "Send file" from Teraterm menu
All I get is "connection timeout", the transfer isn't started.
Should this work?
As I don't have any manual for this box could someone please explain
what "Test Module", "EBL" and "FTL" are? I assume "EBL=Ebox Boot Loader"
is the first-stage loader and test module is the actual kernel?
And how can I save the serial port speed set by "BR 115.2"?
All info is welcome (in Finnish, Swedish or English). Step-by-step
instructions are really appreciated...
Martti
---
Martti Kuparinen <mar...@ik...> NetBSD - No media hype
http://www.iki.fi/~kuparine/ http://www.netbsd.org/
|
