Re: [leaf-user] tty errors on Bering 2.3 with WRAP box
Strange, you did disable the ttys in /etc/inittab so getty shouldn't try to open /dev/tty. Related to your other problem, did you edit the files on your router or did you use an other editor (CR/LF)? Instead of copying the old files please use the ones included in the image and comment out the ttys in /etc/inittab. Eric > I encounter some trouble updating my WRAP box to latest Bering 2.3. > > > - I use initrd_ide.lrp from the CD image as initrd.lrp for the WRAP box. > > > - I got the tty errors after crontab being installed > > > Starting periodic command scheduler: cron. > getty: /dev/tty1: cannot open as standard input: No such device > getty: /dev/tty2: cannot open as standard input: No such device > .. > > > I copied the old /etc/securetty and /etc/inittab as well as syslinux.cfg. > They are > > > /etc/inittab > - > #1:2345:respawn:/sbin/getty 38400 tty1 > #2:23:respawn:/sbin/getty 38400 tty2 > # for WRAP box > # > T1:2345:respawn:/sbin/getty -L ttyS0 38400 vt100 > > > /etc/securetty > > ttyS0 tty1 tty2 tty3 tty4 tty5 tty6 tty7 tty8 ttyS1 > > and syslinux.cfg: > serial 0 38400 display syslinux.dpy timeout 0 append console=ttyS0,38400 > default linux initrd=initrd.lrp init=/linuxrc rw root=/dev/ram0 > LEAFCFG=/dev/hda1:msdos > > > My current working version is 2.3beta4. Does something related to tty > change in between. I think somebody reported similar error on RC1, but I > am not sure he fixed it. > > Any suggestions? > > > > > > --- > This SF.Net email is sponsored by the JBoss Inc. > Get Certified Today * Register for a JBoss Training Course > Free Certification Exam for All Training Attendees Through End of 2005 > Visit http://www.jboss.com/services/certification for more information > > leaf-user mailing list: leaf-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/leaf-user > Support Request -- http://leaf-project.org/ > > --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information 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] madwifi drivers on Bering 2.3
Can you mail the exact contents of /etc/modules? Insmod is displaying its options because an "illegal" option is found. Did you try to insmod the modules by hand? Eric > I have them in /etc/modules as > > > wlan wlan_acl wlan_ccmp wlan_tkip wlan_wep wlan_xauth ath_hal ath_rate_sample > ath_pci > > but on loading wlan_ccmp as well as a couple of other modules, BusyBox > reported error: > > > wlan - Using /var/lib/lrpkg/mnt/modules/net//./wlan.o wlan: 0.8.6.0 > (EXPERIMENTAL) > wlan_acl - Using /var/lib/lrpkg/mnt/modules/net//./wlan_acl.o wlan: mac acl > policy registered wlan_ccmp - BusyBox v1.00 (2005.08.02-19:26+) > multi-call binary > > Usage: insmod [OPTION]... MODULE [symbol=value]... > ^^ > > > > wlan_tkip - BusyBox v1.00 (2005.08.02-19:26+) multi-call binary > > Usage: insmod [OPTION]... MODULE [symbol=value]... > > > wlan_wep - Using /var/lib/lrpkg/mnt/modules/net//./wlan_wep.o wlan_xauth - > BusyBox v1.00 (2005.08.02-19:26+) multi-call binary > > > Usage: insmod [OPTION]... MODULE [symbol=value]... > > > ath_hal - Using /var/lib/lrpkg/mnt/modules/net//./ath_hal.o Warning: > loading ath_hal will taint the kernel: non-GPL license ath_hal: 0.9.14.9 > (- Proprietary > AR5210 See http://www., AR5211tux.org/lkml/#ex, AR5212port-tainted for, > RF5111 information abo, RF5112ut tainted modul, Rs) > ath_rate_sample - BusyBox v1.00 (2005.08.02-19:26+) multi-call binary > > Usage: insmod [OPTION]... MODULE [symbol=value]... > > > ath_pci - Using /var/lib/lrpkg/mnt/modules/net//./ath_pci.o insmod: > unresolved symbol ath_rate_findrate insmod: unresolved symbol > ath_rate_newassoc insmod: unresolved symbol ath_rate_detach > insmod: unresolved symbol ath_rate_node_init > insmod: unresolved symbol ath_rate_setupxtxdesc > insmod: unresolved symbol ath_rate_dynamic_sysctl_register > insmod: unresolved symbol ath_rate_node_cleanup > insmod: unresolved symbol ath_rate_attach > insmod: unresolved symbol ath_rate_tx_complete > insmod: unresolved symbol ath_rate_newstate > > > -- > > > > Could anybody help? > > > Thank you. > > > > > > > > > --- > This SF.Net email is sponsored by the JBoss Inc. > Get Certified Today * Register for a JBoss Training Course > Free Certification Exam for All Training Attendees Through End of 2005 > Visit http://www.jboss.com/services/certification for more information > > leaf-user mailing list: leaf-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/leaf-user > Support Request -- http://leaf-project.org/ > > --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
[leaf-user] madwifi drivers on Bering 2.3
I have them in /etc/modules as wlan wlan_acl wlan_ccmp wlan_tkip wlan_wep wlan_xauth ath_hal ath_rate_sample ath_pci but on loading wlan_ccmp as well as a couple of other modules, BusyBox reported error: wlan - Using /var/lib/lrpkg/mnt/modules/net//./wlan.o wlan: 0.8.6.0 (EXPERIMENTAL) wlan_acl - Using /var/lib/lrpkg/mnt/modules/net//./wlan_acl.o wlan: mac acl policy registered wlan_ccmp - BusyBox v1.00 (2005.08.02-19:26+) multi-call binary Usage: insmod [OPTION]... MODULE [symbol=value]... ^^ wlan_tkip - BusyBox v1.00 (2005.08.02-19:26+) multi-call binary Usage: insmod [OPTION]... MODULE [symbol=value]... wlan_wep - Using /var/lib/lrpkg/mnt/modules/net//./wlan_wep.o wlan_xauth - BusyBox v1.00 (2005.08.02-19:26+) multi-call binary Usage: insmod [OPTION]... MODULE [symbol=value]... ath_hal - Using /var/lib/lrpkg/mnt/modules/net//./ath_hal.o Warning: loading ath_hal will taint the kernel: non-GPL license ath_hal: 0.9.14.9 (- Proprietary AR5210 See http://www., AR5211tux.org/lkml/#ex, AR5212port-tainted for, RF5111 information abo, RF5112ut tainted modul, Rs) ath_rate_sample - BusyBox v1.00 (2005.08.02-19:26+) multi-call binary Usage: insmod [OPTION]... MODULE [symbol=value]... ath_pci - Using /var/lib/lrpkg/mnt/modules/net//./ath_pci.o insmod: unresolved symbol ath_rate_findrate insmod: unresolved symbol ath_rate_newassoc insmod: unresolved symbol ath_rate_detach insmod: unresolved symbol ath_rate_node_init insmod: unresolved symbol ath_rate_setupxtxdesc insmod: unresolved symbol ath_rate_dynamic_sysctl_register insmod: unresolved symbol ath_rate_node_cleanup insmod: unresolved symbol ath_rate_attach insmod: unresolved symbol ath_rate_tx_complete insmod: unresolved symbol ath_rate_newstate -- Could anybody help? Thank you. --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
[leaf-user] tty errors on Bering 2.3 with WRAP box
I encounter some trouble updating my WRAP box to latest Bering 2.3. - I use initrd_ide.lrp from the CD image as initrd.lrp for the WRAP box. - I got the tty errors after crontab being installed Starting periodic command scheduler: cron. getty: /dev/tty1: cannot open as standard input: No such device getty: /dev/tty2: cannot open as standard input: No such device .. I copied the old /etc/securetty and /etc/inittab as well as syslinux.cfg. They are /etc/inittab - #1:2345:respawn:/sbin/getty 38400 tty1 #2:23:respawn:/sbin/getty 38400 tty2 # for WRAP box # T1:2345:respawn:/sbin/getty -L ttyS0 38400 vt100 /etc/securetty ttyS0 tty1 tty2 tty3 tty4 tty5 tty6 tty7 tty8 ttyS1 and syslinux.cfg: serial 0 38400 display syslinux.dpy timeout 0 append console=ttyS0,38400 default linux initrd=initrd.lrp init=/linuxrc rw root=/dev/ram0 LEAFCFG=/dev/hda1:msdos My current working version is 2.3beta4. Does something related to tty change in between. I think somebody reported similar error on RC1, but I am not sure he fixed it. Any suggestions? --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information 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] Bering-uClibc-2.3 files
Hi KP, Thank you for the explanation and also for the final release. M Lu - Original Message - From: "KP Kirchdoerfer" <[EMAIL PROTECTED]> To: Sent: Tuesday, October 25, 2005 7:35 AM Subject: Re: [leaf-user] Bering-uClibc-2.3 files Well, different view's of the same packages... The packages were build and committed to a cvs subdir a week before the packages has been committed to main cvs respository and the page you are referring to has been build by a script using the dates in cvs log. Should I get the ISO and then update with latest packages? Just use the ISO image. sorry for confusion. kp --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information 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] Bering-uClibc-2.3 files
Am Dienstag, 25. Oktober 2005 03:57 schrieb M Lu: > Is the final 2.3 released? On the download link > (http://sourceforge.net/project/showfiles.php?group_id=13751&package_id=675 >34) I see the images released on Oct 16 (when mounted ISO, the files inside > are Oct 15), whereas a lot of core packages are released Oct 23 > (http://leaf.sourceforge.net/bering-uclibc/index.php?module=pagemaster&PAGE >_user_op=view_page&PAGE_id=3&MMN_position=3:3#CHANGELOG) Well, different view's of the same packages... The packages were build and committed to a cvs subdir a week before the packages has been committed to main cvs respository and the page you are referring to has been build by a script using the dates in cvs log. > Should I get the ISO and then update with latest packages? Just use the ISO image. sorry for confusion. kp --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
