[leaf-user] Errors on a compact flash
Hi,
I just installed Bering-uClibc 3.0.1 on a PC Engines WRAP box with a CF Card
but I'm getting these warnings at startup:
...
hda: HYPERSTONE FLASH DISK, CFA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: attached ide-disk driver.
hda: 253696 sectors (130 MB) w/0KiB Cache, CHS=991/8/32
Partition check:
hda: hda1
hda: hda1
hda: hda1
hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_no_data_intr: error=0x04 { DriveStatusError }
hda: Write Cache FAILED Flushing!
hda: hda1
hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_no_data_intr: error=0x04 { DriveStatusError }
hda: Write Cache FAILED Flushing!
LINUXRC: Mounting a 16M TMPFS filesystem...
hda: hda1
hda: hda1
...
Instead, booting from network with PXE, I get no error:
...
hda: HYPERSTONE FLASH DISK, CFA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: attached ide-disk driver.
hda: 253696 sectors (130 MB) w/0KiB Cache, CHS=991/8/32
Partition check:
hda: hda1
NET4: Linux TCP/IP 1.0 for NET4.0
...
Any suggestion?
Thanks
--
Domenico Viggiani
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
leaf-user mailing list: leaf-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/
Re: [leaf-user] Errors on a compact flash
Hi Domenico,
A bit of googling showed that
hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_no_data_intr: error=0x04 { DriveStatusError }
is just a warning and can be ignored. It has probably something todo with
the type of IDE controller you have.
There is even a config option in the kernel that supresses this warning:
CONFIG_IDEDISK_MULTIMODE
But because it may not be a good general option it's not enabled by default.
I'm not sure about the hda: Write Cache FAILED Flushing!
Eric
Op Wo, 7 februari, 2007 3:58 pm schreef Domenico Viggiani:
Hi,
I just installed Bering-uClibc 3.0.1 on a PC Engines WRAP box with a CF
Card
but I'm getting these warnings at startup: ...
hda: HYPERSTONE FLASH DISK, CFA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 hda: attached ide-disk driver.
hda: 253696 sectors (130 MB) w/0KiB Cache, CHS=991/8/32
Partition check:
hda: hda1
hda: hda1
hda: hda1
hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_no_data_intr: error=0x04 { DriveStatusError }
hda: Write Cache FAILED Flushing!
hda: hda1
hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_no_data_intr: error=0x04 { DriveStatusError }
hda: Write Cache FAILED Flushing!
LINUXRC: Mounting a 16M TMPFS filesystem...
hda: hda1
hda: hda1
...
Instead, booting from network with PXE, I get no error:
...
hda: HYPERSTONE FLASH DISK, CFA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 hda: attached ide-disk driver.
hda: 253696 sectors (130 MB) w/0KiB Cache, CHS=991/8/32
Partition check:
hda: hda1
NET4: Linux TCP/IP 1.0 for NET4.0
...
Any suggestion?
Thanks
--
Domenico Viggiani
-
Using Tomcat but need to do more? Need to support web services,
security? Get stuff done quickly with pre-integrated technology to make
your job easier. Download IBM WebSphere Application Server v.1.0.1 based
on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
leaf-user mailing list: leaf-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
leaf-user mailing list: leaf-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/
Re: [leaf-user] errors backing up ipsec (Bering-uClibc 2.2.2)
Troy, Am Freitag, 29. Oktober 2004 05:02 schrieb Troy Aden: First off thanks for the quick answers for the questions I have posted previously! I got the firewall up and it runs very nicely. However when I do a full backup I get the following errors: Creating ipsec.lrp Please wait: /tar: etc/pgpcert.pgp: No such file or directory tar: Error exit delayed from previous errors Back-up of ipsec complete I've seen this before, but it seems not to happen everywhere; will look into it again. This error is fixed in CVS now, it will show up in a few hours when viewcs is updated (http://cvs.sourceforge.net/viewcvs.py/leaf/bin/packages/uclibc- 0.9/20/). You must have CVS revision 1.7 or later. Creating lpthread.lrp Please wait: \tar: var/lib/lrpkg/libpthread.*: No such file or directory tar: Error exit delayed from previous errors Back-up of lpthread complete Yep, the var/lib/lrpkg/lpthread.list file has a wrong entry var/lib/lrpkg/libpthread.* should be var/lib/lrpkg/lpthread.* Will be fixed in future version. This one is also fixed in CVS (same directory as above), CVS revision 1.2 Just a footnote: I noticed that the version of IPSec that you have posted in the 2.2 Bering Uclibc does not include libm as a package dependency. I need to load the libm package for this version of IPSec to work so you may want to update your links. Here is a link: http://leaf.sourceforge.net/mod.php?mod=userpagemenu=91017page_id =51 ipsec.lrp Openswan IPSEC Homepage: http://www.openswan.org Requires: mawk.lrp lpthread.lrp LEAF Package by [EMAIL PROTECTED], 2004-09-23 Version: 1.0.7 Technically libm is not a dependency of ipsec but of mawk (and listed as a dependency for that package). This is a little confusing and we will think about a good solution. Eric Spakman --- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588alloc_id=12065op=click leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
Re: [leaf-user] errors backing up ipsec (Bering-uClibc 2.2.2)
Am Freitag, 29. Oktober 2004 05:02 schrieb Troy Aden: First off thanks for the quick answers for the questions I have posted previously! I got the firewall up and it runs very nicely. However when I do a full backup I get the following errors: Creating ipsec.lrp Please wait: /tar: etc/pgpcert.pgp: No such file or directory tar: Error exit delayed from previous errors Back-up of ipsec complete I've seen this before, but it seems not to happen everywhere; will look into it again. Creating lpthread.lrp Please wait: \tar: var/lib/lrpkg/libpthread.*: No such file or directory tar: Error exit delayed from previous errors Back-up of lpthread complete Yep, the var/lib/lrpkg/lpthread.list file has a wrong entry var/lib/lrpkg/libpthread.* should be var/lib/lrpkg/lpthread.* Will be fixed in future version. Can anyone please explain these to me? It looks like it is expecting some files that do not exist. Should I be concerned about this? Just a footnote: I noticed that the version of IPSec that you have posted in the 2.2 Bering Uclibc does not include libm as a package dependency. I need to load the libm package for this version of IPSec to work so you may want to update your links. Here is a link: http://leaf.sourceforge.net/mod.php?mod=userpagemenu=91017page_id =51 ipsec.lrp Openswan IPSEC Homepage: http://www.openswan.org Requires: mawk.lrp lpthread.lrp LEAF Package by [EMAIL PROTECTED], 2004-09-23 Version: 1.0.7 Thx for spotting. kp --- This Newsletter Sponsored by: Macrovision For reliable Linux application installations, use the industry's leading setup authoring tool, InstallShield X. Learn more and evaluate today. http://clk.atdmt.com/MSI/go/ins003001msi/direct/01/ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
Re: [leaf-user] errors backing up ipsec (Bering-uClibc 2.2.2)
K.-P. Kirchdörfer wrote: Am Freitag, 29. Oktober 2004 05:02 schrieb Troy Aden: First off thanks for the quick answers for the questions I have posted previously! I got the firewall up and it runs very nicely. However when I do a full backup I get the following errors: Creating ipsec.lrp Please wait: /tar: etc/pgpcert.pgp: No such file or directory tar: Error exit delayed from previous errors Back-up of ipsec complete I've seen this before, but it seems not to happen everywhere; will look into it again. The backup scripts will fail if anything listed in the package.list does not actually exist. Typically, the easiest way to handle this for packages that might or might not have some files (like certs for ipsec) is to put them in a sub-directory. That way, the sub-directory always exists, and any files that do exist are backed up, while those that don't exist won't cause errors. I personally use the /etc/ipsec directory for any files other than ipsec.conf and ipsec.secrets that relate to ipsec. -- Charles Steinkuehler [EMAIL PROTECTED] --- This Newsletter Sponsored by: Macrovision For reliable Linux application installations, use the industry's leading setup authoring tool, InstallShield X. Learn more and evaluate today. http://clk.atdmt.com/MSI/go/ins003001msi/direct/01/ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
[leaf-user] errors backing up ipsec (Bering-uClibc 2.2.2)
First off thanks for the quick answers for the questions I have posted previously! I got the firewall up and it runs very nicely. However when I do a full backup I get the following errors: Creating ipsec.lrp Please wait: /tar: etc/pgpcert.pgp: No such file or directory tar: Error exit delayed from previous errors Back-up of ipsec complete Creating lpthread.lrp Please wait: \tar: var/lib/lrpkg/libpthread.*: No such file or directory tar: Error exit delayed from previous errors Back-up of lpthread complete Can anyone please explain these to me? It looks like it is expecting some files that do not exist. Should I be concerned about this? Just a footnote: I noticed that the version of IPSec that you have posted in the 2.2 Bering Uclibc does not include libm as a package dependency. I need to load the libm package for this version of IPSec to work so you may want to update your links. Here is a link: http://leaf.sourceforge.net/mod.php?mod=userpagemenu=91017page_id=51 ipsec.lrp Openswan IPSEC Homepage: http://www.openswan.org Requires: mawk.lrp lpthread.lrp LEAF Package by [EMAIL PROTECTED], 2004-09-23 Version: 1.0.7 Again thanks for all the help so far. Troy --- This Newsletter Sponsored by: Macrovision For reliable Linux application installations, use the industry's leading setup authoring tool, InstallShield X. Learn more and evaluate today. http://clk.atdmt.com/MSI/go/ins003001msi/direct/01/ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
[leaf-user] Errors with lrcfg.back.script and Bash
I am encountering errors when I am attempting to back up packages after making configuration changes. I am currently using LEAF 2.0.1. The packages that are being loaded, in order, are: root,config,etc,local,modules,hdsupp,libm,mawk,tc,daemontl,iptables, shorwall,ulogd,dhcpcd,dnscache,dropbear,weblet,ntpdate,ipsec,ncurses,bash The errors seem to occur in the /usr/sbin/lrcfg.back.script backup script. ** When I backup modules.lrp, etc, root.lrp, dnscache.lrp, dhcpcd.lrp,ipsec.lrp,bash.lrp the error appears on line 122 ** When I backup shorwall.lrp, iptables.lrp, weblet.lrp the error is on line 123 ** It appears the error has something to with the ticker script because Terminated ticker (wd: ~) is at the end of every error message no matter what line number the error appears on. ticker is another script located in the /usr/sbin directory. ** These errors only appear when the bash.lrp environment is loaded. If I don't load Bash, and use just Ash instead, everything works as it was intended. I load every other package in the list above, except Bash, and then the backup scripts work fine. I noticed there was another error with the dnscache.lrp package when bash.lrp was loaded. Specifically, it had to do with the start-up script, /etc/init.d/dnscache. Within that script, it used a variable UID, and with bash that is a predefined variable so the script reported an error and stopped. To resolve, I changed UID to DNSUID and also exported DNSUID (the script had been exporting the UID variable previously). Once I made these changes, the dnscache.lrp package was working fine with bash.lrp loaded. Thought I'd share this fix just in case someone had run across this problem. Thank you for any assistance concerning the /usr/sbin/lrcfg.back.script and /usr/sbin/ticker script issues. Brad --- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149alloc_id=8166op=click leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
Re: [leaf-user] Errors with lrcfg.back.script and Bash
Please install latest bash.lrp from cvs or Bering-uClibc packages page. I have removed the the symlink from /bin/bash to /bin/sh three month ago to workaround all the errors you described. kp Am Samstag, 22. Mai 2004 23:43 schrieb Brad Klinghagen: I am encountering errors when I am attempting to back up packages after making configuration changes. I am currently using LEAF 2.0.1. The packages that are being loaded, in order, are: root,config,etc,local,modules,hdsupp,libm,mawk,tc,daemontl,iptables, shorwall,ulogd,dhcpcd,dnscache,dropbear,weblet,ntpdate,ipsec,ncurses,bash The errors seem to occur in the /usr/sbin/lrcfg.back.script backup script. ** When I backup modules.lrp, etc, root.lrp, dnscache.lrp, dhcpcd.lrp,ipsec.lrp,bash.lrp the error appears on line 122 ** When I backup shorwall.lrp, iptables.lrp, weblet.lrp the error is on line 123 ** It appears the error has something to with the ticker script because Terminated ticker (wd: ~) is at the end of every error message no matter what line number the error appears on. ticker is another script located in the /usr/sbin directory. ** These errors only appear when the bash.lrp environment is loaded. If I don't load Bash, and use just Ash instead, everything works as it was intended. I load every other package in the list above, except Bash, and then the backup scripts work fine. I noticed there was another error with the dnscache.lrp package when bash.lrp was loaded. Specifically, it had to do with the start-up script, /etc/init.d/dnscache. Within that script, it used a variable UID, and with bash that is a predefined variable so the script reported an error and stopped. To resolve, I changed UID to DNSUID and also exported DNSUID (the script had been exporting the UID variable previously). Once I made these changes, the dnscache.lrp package was working fine with bash.lrp loaded. Thought I'd share this fix just in case someone had run across this problem. Thank you for any assistance concerning the /usr/sbin/lrcfg.back.script and /usr/sbin/ticker script issues. Brad --- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149alloc_id=8166op=click leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html --- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149alloc_id=8166op=click leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
RE: [leaf-user] Errors--Route through eth0?
Richard: I'll be glad to share what I learn as I go, and I planned on sending lessons-learned back to the list / primary producers of LEAF. You pointed me in the right track, but it turned out the 3c589_cs CANNOT be called from within the /etc/modules. Instead, the 3c589 driver needs moved to the /lib/modules/pcmcia, then the pcmcia package backed up. Upon load, the OS automatically loads these modules, in module-dependent order. That got eth0 working, at least from the firewall's view. I'm still checking the eth0 service to make sure I understand what's available / works there. Best wishes, -Original Message- From: Richard Doyle [SMTP:[EMAIL PROTECTED] Sent: Monday, 09 June, 2003 21:03 To: '[EMAIL PROTECTED]' Subject:Re: [leaf-user] Errors--Route through eth0? On Mon, 2003-06-09 at 19:19, Greg Playle wrote: My thanks to Tom Eastep and Ray Olszewski, who pointed out some information that would help. I'm working on LEAF Bering 1.2, using a PPP serial modem (as ppp0) and a PCMCIA NIC as eth0 for the internal network. The host is a Toshiba Satellite Pro 460CDX laptop (recycled). The NIC is an older 3Com EtherLink III 3C589D based card (recycled). At boot, the firewall gives an error message of: Masquerade: Error: Unable to determine the routes through eth0 snip # /etc/modules: kernel modules to load at boot time. # ISA ethernet cards # PCI ethernet cards # should the 3c589_cs.o be declared here? - Yes. You can insert the module on a running system with insmod 3c589_cs I'm very interested in your progress on this project, as I'm about to try something rather similar in the next few weeks. Good luck! --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html --- This SF.NET email is sponsored by: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
[leaf-user] Errors--Route through eth0?
My thanks to Tom Eastep and Ray Olszewski, who pointed out some information that would help. I'm working on LEAF Bering 1.2, using a PPP serial modem (as ppp0) and a PCMCIA NIC as eth0 for the internal network. The host is a Toshiba Satellite Pro 460CDX laptop (recycled). The NIC is an older 3Com EtherLink III 3C589D based card (recycled). At boot, the firewall gives an error message of: Masquerade: Error: Unable to determine the routes through eth0 Tom suggested the interface isn't up before Shorewall starts, and that seems reasonable. Ray suggested there was a configuration error, and that seems highly likely, as I'm still learning. Pinging the firewall from the internal network, to the default IP of 192.168.1.254 Destination Host Unreachable. I think I've failed to declare something associated with the PCMCIA cards--I'm not sure where the declaration of the 3c589 driver goes--the documentation isn't clear. I've read the FAQ, but didn't find something that pointed in this direction. I searched the archive, and googled, but also didn't find much. I've pulled the information for troubleshooting, per http://leaf-project.org/pub/doc/docmanager/docid_1891.html. The document at http://leaf.sourceforge.net/pub/doc/guide/install-dachstein/ds-laptop.html there may be a PCI-to-PCMCIA bridge problem (these are older machines). But far more likely is that I've left something out, and I've annotated where my suspicions like, below, in the /etc/modules file. I appreciate the help you're providing, as I'm still learning. uname -a yields Linux firewall 2.4.20 #1 Sun May 11 18:53:34 CEST 2003 i586 unknown ip addr show 1: lo: LOOPBACK,UP mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 brd 127.255.255.255 scope host lo 2: dummy0: BROADCAST,NOARP mtu 1500 qdisc noop link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 3: ppp0: POINTOPOINT,MULTICAST,NOARP,UP mtu 1500 qdisc pfifo_fast qlen 3 link/ppp inet 10.64.64.64 peer 10.112.112.112/32 scope global ppp0 ip route show 10.112.112.112 dev ppp0 proto kernel scope link src 10.64.64.64 default via 10.112.112.112 dev ppp0 lsmod Module PagesUsed by ds 6796 2 i82365 27044 2 pcmcia_core41088 0 [ds i82365] ip_nat_irc 2176 0 (unused) ip_nat_ftp 2784 0 (unused) ip_conntrack_irc2880 1 ip_conntrack_ftp3648 1 ppp_async 6284 0 (unused) ppp_generic16152 1 [ppp_async] slhc4352 0 [ppp_generic] /sbin/shorewall status Shorewall-1.4.2 Status at firewall - Mon Jun 9 20:07:24 UTC 2003 Chain INPUT (policy DROP 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 0 0 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 state ESTABLISHED 0 0 ACCEPT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:53 0 0 DROP !icmp -- * * 0.0.0.0/0 0.0.0.0/0 state INVALID 0 0 ACCEPT all -- lo * 0.0.0.0/0 0.0.0.0/0 Chain FORWARD (policy DROP 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 0 0 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 state ESTABLISHED 0 0 ACCEPT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:53 0 0 DROP !icmp -- * * 0.0.0.0/0 0.0.0.0/0 state INVALID Chain OUTPUT (policy DROP 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 0 0 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 state ESTABLISHED 0 0 ACCEPT udp -- * * 0.0.0.0/00.0. 0.0/0 udp dpt:53 0 0 DROP !icmp -- * * 0.0.0.0/0 0.0.0.0/0 state INVALID 0 0 ACCEPT all -- * lo 0.0.0.0/0 0.0.0.0/0 Chain all2all (3 references) pkts bytes target prot opt in out source destination 0 0 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED 0 0 newnotsyn tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp flags:!0x16/0x02 0 0 common all -- * * 0.0.0.0/0 0.0.0.0/0 0 0 ULOG all -- * * 0.0.0.0/0 0.0.0.0/0 ULOG copy_range 0 nlgroup 1 prefix `Shorewall:all2all:REJECT:' queue_threshold 1 0 0 reject all -- * * 0.0.0.0/0 0.0.0.0/0 Chain common (2 references) pkts bytes target prot opt in out source dest ination 0 0 icmpdeficmp -- *
Re: [leaf-user] Errors--Route through eth0?
On Mon, 2003-06-09 at 19:19, Greg Playle wrote: My thanks to Tom Eastep and Ray Olszewski, who pointed out some information that would help. I'm working on LEAF Bering 1.2, using a PPP serial modem (as ppp0) and a PCMCIA NIC as eth0 for the internal network. The host is a Toshiba Satellite Pro 460CDX laptop (recycled). The NIC is an older 3Com EtherLink III 3C589D based card (recycled). At boot, the firewall gives an error message of: Masquerade: Error: Unable to determine the routes through eth0 snip # /etc/modules: kernel modules to load at boot time. # ISA ethernet cards # PCI ethernet cards # should the 3c589_cs.o be declared here? - Yes. You can insert the module on a running system with insmod 3c589_cs I'm very interested in your progress on this project, as I'm about to try something rather similar in the next few weeks. Good luck! --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
RE: [leaf-user] Errors--Route through eth0?
Please reply to the list. On Mon, 2003-06-09 at 20:49, Greg Playle wrote: I guess I'm a bit puzzled at this. The messages at boot appear to indicate that insmod is throwing unresolved symbol errors when it tries to load 3c589_cs. The things it's trying to refer to appear to be the modules loaded by the pcmcia modules. Later, the load messages show the pcmcia modules loading, but of course, 3c589 isn't working. Should the pcmcia call in syslinux.cfg precede the call to modules.lrp? Well, I haven't used pcmcia with LEAF yet, but yes, the pcmcia drivers (ds and pcmcia_core) must be loaded before the 3c589 driver, as shown by modules.dep: /lib/modules/2.4.20/pcmcia/3c589_cs.o: /lib/modules/2.4.20/pcmcia/ds.o \ /lib/modules/2.4.20/pcmcia/pcmcia_core.o /lib/modules/2.4.20/pcmcia/ds.o:/lib/modules/2.4.20/pcmcia/pcmcia_core.o /lib/modules/2.4.20/pcmcia/pcmcia_core.o: -Richard --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
Re: [leaf-user] Errors--Route through eth0?
This is all a bit muddled in my mind, Greg, and the message from Richard Doyle -- which appears to be in reply to something you wrote that I have not seen yet -- confuses me a bit more. What I *think* is going on is simply that the eth0 interface is not being created because you are not loading the module(s) needed to detect and initialize the NIC. At the least, this is the 3c589_cs.o; it includes anything that module depends on. It has (they have) to be in /etc/modules, and if there is more than one, they have to be in the right order. Based on the details in this message of yours and the one Richard posted, I **think** you need to edit /etc/modules to read something like this (my edits are not indented): # /etc/modules: kernel modules to load at boot time. # ISA ethernet cards # PCI ethernet cards # should the 3c589_cs.o be declared here? - pcmcia_core ds. 3c589_cs # Modules needed for PPP connection slhc ppp_generic ppp_async # The three following modules are not always needed #zlib_inflate #zlib_deflate #ppp_deflate # Masquerading 'helper' modules # Other modules available in bering/modules/net/ipv4/netfilter ip_conntrack_ftp ip_conntrack_irc ip_nat_ftp ip_nat_irc insmod'ing the modules in this order should cause the card to be detected and the eth0 interface created ... although in saying this I rely on your identifying this module as the right one for the card and on the depmod info in Richard's message being correct. All your other symptoms are secondary, caused by the eth0 interface not existing. Once it exists, other problems may turn up with your setup ... but until the interface exists, neither we nor you can even begin to evaluate that part of your configuration. BTW, the order of packages in syslinux.cfg has nothing to do with this problem. The order of modules ... and the completeness of the list ... in /etc/modules has everything to do with it. Digression into background: full-strength Linux systems almost universally use modprobe to install modules. modprobe takes care of module dependencies for you, loading what is needed for the named modules. Small distros like LEAF typically use the smaller program insmod, which does not do dependency checking for you. So someone coming to LEAF from Red Hat or Debian needs to adjust his or her thinking a bit to get this stuff rght. Hope this helps. Good luck. At 08:19 PM 6/9/2003 -0600, Greg Playle wrote: My thanks to Tom Eastep and Ray Olszewski, who pointed out some information that would help. I'm working on LEAF Bering 1.2, using a PPP serial modem (as ppp0) and a PCMCIA NIC as eth0 for the internal network. The host is a Toshiba Satellite Pro 460CDX laptop (recycled). The NIC is an older 3Com EtherLink III 3C589D based card (recycled). At boot, the firewall gives an error message of: Masquerade: Error: Unable to determine the routes through eth0 Tom suggested the interface isn't up before Shorewall starts, and that seems reasonable. Ray suggested there was a configuration error, and that seems highly likely, as I'm still learning. Pinging the firewall from the internal network, to the default IP of 192.168.1.254 Destination Host Unreachable. I think I've failed to declare something associated with the PCMCIA cards--I'm not sure where the declaration of the 3c589 driver goes--the documentation isn't clear. [details deleted] --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
[leaf-user] Errors--Route through eth0?
I'm working a simple, serial-modem / single network (ppp0 eth0) setup. At boot, one of the last messages before login is: Masquerade: Error: Unable to determine the routes through eth0 I've checked the zones defined, the interfaces defined, and the masquerade definitions, and all appear to agree with the PPP setup instructions in the LEAF User documentation. I've tried pinging the IP and the hostname; without a DNS, it's hard to get this to work. I've checked the archives, and googled, but find nothing that sheds light on this. Could someone point me at something to check, or tests to run, to determine the problem? Thank you --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
Re: [leaf-user] Errors--Route through eth0?
On Sun, 08 Jun 2003 15:51:36 -0700, Ray Olszewski [EMAIL PROTECTED] wrote: At 04:12 PM 6/8/2003 -0600, Greg Playle wrote: I'm working a simple, serial-modem / single network (ppp0 eth0) setup. Which LEAF variant? It's impossible even to begin giving any sort of detailed advice without knowing if it's Dachstein, Bering, or what. At boot, one of the last messages before login is: Masquerade: Error: Unable to determine the routes through eth0 Since you have a ppp setup, eth0 is presumably your LAN interface. Without context, this message is hard to interpret, but it make me suspect that you missed some setting and the system thinks that eth0 is the external interface. This is only a guess, though. This message usually means that the internal interface isn't up when Shorewall starts. Shorewall examines the routing table to understand what addresses need to be masqueraded. -Tom -- Tom Eastep\ Shorewall - iptables made easy Shoreline, \ http://www.shorewall.net Washington USA \ [EMAIL PROTECTED] --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
[leaf-user] Errors with LEAF
I could use some directions to more information. I am learning a bit about LEAF, the Bering distribution, v1.2. I've pulled the package, followed the directions, and I think I've got an approach working. I'm working a simple, serial-modem / single network (ppp0 eth0) setup. I wanted to install ssh as I went about it. I've followed the directions, changed the installation to use two floppies, and added the libz, sshd, and sshkey modules to syslinux.cfg and the modules disk. When I boot, I get an error message on the libz load that says Invalid gzip magic. I did a google, but could find only one dead link to a sourceforge archive. I've obviously set something up incorrectly, but don't know what it is. Would this be an erroneous version number, or am I not providing something? Possibly a corrupt file? Additionally, I'm seeing sshkey returning a format violated error message when that modules is loaded. Would this be a corrupt file? Finally, I'm getting an error message as the firewall loads its rules that says: Masquerade: Error: unable to determine the routes through eth0 I've checked the zones defined, the interfaces defined, and the masquerade definitions, and all appear to agree with the PPP setup instructions in the LEAF User documentation. If you could point me to something that might help, I'd greatly appreciate it. Thank you --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
[leaf-user] Errors with LEAF
I could use some directions to more information. I am learning a bit about LEAF, the Bering distribution, v1.2. I've pulled the package, followed the directions, and I think I've got an approach working. I'm working a simple, serial-modem / single network (ppp0 eth0) setup. I wanted to install ssh as I went about it. I've followed the directions, changed the installation to use two floppies, and added the libz, sshd, and sshkey modules to syslinux.cfg and the modules disk. When I boot, I get an error message on the libz load that says Invalid gzip magic. I did a google, but could find only one dead link to a sourceforge archive. I've obviously set something up incorrectly, but don't know what it is. Would this be an erroneous version number, or am I not providing something? Possibly a corrupt file? Additionally, I'm seeing sshkey returning a format violated error message when that modules is loaded. Would this be a corrupt file? Finally, I'm getting an error message as the firewall loads its rules that says: Masquerade: Error: unable to determine the routes through eth0 I've checked the zones defined, the interfaces defined, and the masquerade definitions, and all appear to agree with the PPP setup instructions in the LEAF User documentation. If you could point me to something that might help, I'd greatly appreciate it. Thank you --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
[Leaf-user] errors
Hi I'm using Dachstein RC2 with success at several sites but one of them is giving me an error message then stopping traffic. It works fine for a while (18 hours)and then stops. Rebooting fixes the problem. I've swapped hardware to no effect The message is eth1:too much work during an interrupt the Restarted Rx TIA Bill Hults ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
