Hi Tom. Arrg, I see the same thing.
It mounts on the desktop just fine. Let me work on it. I kink with the new custom build system. Lonnie On Mar 11, 2012, at 1:40 PM, Tom Mazzotta wrote: > Lonnie, > > I seem to be having trouble with the build I ran this morning. When I attempt > to boot the image, I get the following error on the console: > > "This is not a bootable disk. Please insert a bootable floppy and > press any key to try again ..." > > This is the image I built: > Install CF Images for (svn|ast14,no-rhino): > http://build.astlinux.org/images/svn/5a5c306c54f155f9aa44cee4e24c974c/ast14-img > > I have downloaded it twice. I have tried using gnu gzip, diskpart, and > physdiskwrite under Win7 vs. using Ubuntu w/ gparted and dd... with the same > results. I have even burned the image to a different CF card, but it still > doesn't boot. Was there a problem with this build? > > -tm > > -----Original Message----- > From: Lonnie Abelbeck [mailto:li...@lonnie.abelbeck.com] > Sent: Friday, March 09, 2012 4:40 PM > To: AstLinux Users Mailing List > Cc: Tom Mazzotta > Subject: Re: [Astlinux-users] Crash after upgrade 0.7.10 -> 1.0.2 > > Hi Tom, > > We need to get to the bottom of your issues with your Sangoma card. > > May I suggest building a custom image with the new "AstLinux Custom Build > Engine" > > http://build.astlinux.org/ > > Click on the "Build AstLinux SVN" tab, enter your email and desired Asterisk > version, then: > > 1) Uncheck "SMP Kernel" since you have a net5501 > > 2) Check "Disable Rhino" this will then use the latest DAHDI 2.6.0 > > Finally click the "Build AstLinux Image" button. > > The rest should be self explanatory. > > These choices will generate an image with the latest 3.5.25 Wanpipe drivers > and latest DAHDI 2.6.0 > > We can test from there, feel free to contact me off-list if you wish. > > If someone else has a Sangoma A200/A400/B600/B700/B800 card working fine, > please comment. > > Lonnie > > > > On Mar 4, 2012, at 7:38 PM, Tom Mazzotta wrote: > >> Lonnie, >> >> Is there anyway to do this with the newly flashed CF (which is crashing) >> ...or do I need to reflash the CF and start all over? >> >> -tm >> >> -----Original Message----- >> From: Lonnie Abelbeck [mailto:li...@lonnie.abelbeck.com] >> Sent: Sunday, March 04, 2012 7:24 PM >> To: AstLinux Users Mailing List >> Subject: Re: [Astlinux-users] Crash after upgrade 0.7.10 -> 1.0.2 >> >> Tom, >> >> As a test, try disabling traffic shaping in the firewall, it seem to always >> crash at that point. >> >> Very weird... >> >> Lonnie >> >> >> On Mar 4, 2012, at 2:38 PM, Tom Mazzotta wrote: >> >>> Darrick, >>> >>> Using a "fresh" install of 1.0.2 on a new CF card, I ran the wancfg_dahdi >>> script that I found under /mnt/kd/wanpipe (I think it was in the >>> zaptel_conf folder, but not sure now). This generated the (3) config files. >>> I modified them in the /mnt/kd locations so that they were similar to what >>> I used with 0.7, but there were some extra configurations generated by the >>> script that I left in (perhaps they should have been in my original files >>> w/ 0.7 as well). Anyway, when I rebooted the system, it crashes with the >>> same error I received earlier today after the upgrade. After having the >>> problem w/ a fresh install, I don't think that your suggestion of wiping >>> out the original wanpipe folder prior to an upgrade would make much of a >>> difference. >>> >>> I am attaching the boot log of the fresh install and my 3 config files (the >>> original versions used with 0.7). In the mean time, I will swap my CF cards >>> to go back to 0.7. >>> >>> Thanks for all your help!! >>> >>> From: Darrick Hartman [mailto:dhart...@djhsolutions.com] >>> Sent: Sunday, March 04, 2012 2:57 PM >>> To: astlinux-users@lists.sourceforge.net >>> Subject: Re: [Astlinux-users] Crash after upgrade 0.7.10 -> 1.0.2 >>> >>> Try removing the /mnt/kd/wanpipe dir before upgrading. Make a backup first, >>> but something likely changed between versions of wanpipe. You can then copy >>> /stat/etc/wanpipe to that location, after a successful upgrade. >>> >>> Sent from my mobile device. Please excuse my brevity. >>> >>> -----Original Message----- >>> From: Tom Mazzotta [tmazzo...@titanmicro.com] >>> Received: Sunday, 04 Mar 2012, 1:04pm >>> To: AstLinux Users Mailing List >>> [astlinux-users@lists.sourceforge.net] >>> Subject: Re: [Astlinux-users] Crash after upgrade 0.7.10 -> 1.0.2 >>> >>> Lonnie, >>> >>> Your procedure to revert back to 0.7 worked perfectly. Thanks so much! >>> I suggest that this info be added to the wiki. >>> >>> To answer your question, NO, I did not run the wancfg_dahdi script. >>> Now that I have the 0.7 system back on line, I will examine the >>> Sangoma config files, and try running the script on 1.0.2. >>> >>> -tm >>> >>> On 3/4/12 1:37 PM, "Lonnie Abelbeck" <li...@lonnie.abelbeck.com> wrote: >>> >>>> Tom, >>>> >>>> My first suggestion was going to be for you to start fresh as you >>>> have done with a 1.0.2 CF image. I see some udev stuff in your logs >>>> that should not be there. Possibly a dirty unionfs partition. >>>> >>>> So, you are booting fine with a fresh AstLinux 1.0.2 and Sangoma >>>> card installed? >>>> >>>> Did you use the "wancfg_dahdi" script to reconfigure the card? >>>> >>>> I have limited knowledge with the Sangoma stuff, Michael Keuter has >>>> used both 1.0.1 and 1.0.2 with Sangoma BRI cards with DAHDI just >>>> fine. Though the latest wanpipe drivers have changed from what 0.7.10 >>>> uses. >>>> >>>> Lonnie >>>> >>>> >>>> On Mar 4, 2012, at 12:26 PM, Tom Mazzotta wrote: >>>> >>>>> Thanks for the quick reply! FYI, in the interim, I have been trying >>>>> to get a fresh install of 1.0.2 running on a different CF card. >>>>> After restoring a basic config b/u from 0.7, the problem I run into >>>>> is that the system is unable to create any dahdi channels. Any >>>>> suggestions here? >>>>> >>>>> -----Original Message----- >>>>> From: Lonnie Abelbeck [mailto:li...@lonnie.abelbeck.com] >>>>> Sent: Sunday, March 04, 2012 1:21 PM >>>>> To: AstLinux Users Mailing List >>>>> Subject: Re: [Astlinux-users] Crash after upgrade 0.7.10 -> 1.0.2 >>>>> >>>>> Hi Tom, >>>>> >>>>> First, to get your phones working again... >>>>> >>>>> Reboot and at the 'boot' prompt type "shell". >>>>> >>>>> runnix# cd /mnt/base/os >>>>> >>>>> runnix# ls *ver >>>>> >>>>> You should see 'Xver' and 'ver'. "cat Xver" should be >>>>> astlinux-0.7.10 >>>>> >>>>> You want to exchange these two files, so *exactly* type >>>>> >>>>> runnix# mv ver Tver >>>>> runnix# mv Xver ver >>>>> runnix# mv Tver Xver >>>>> >>>>> runnix# sync >>>>> runnix# exit >>>>> >>>>> Important, now at the boot prompt type "xrunnix" >>>>> >>>>> It should now boot with runnix-0.3.3 and astlinux-0.7.10 >>>>> >>>>> After it boots properly, from the CLI >>>>> >>>>> $ upgrade-RUNNIX-image revert >>>>> >>>>> This should make runnix-0.3.3 the default again, so a box reboot >>>>> should work without any problems. >>>>> >>>>> I suspect your issues are with your Sangoma card, let me look at >>>>> your logs some more. >>>>> >>>>> Lonnie >>>>> >>>>> >>>>> >>>>> >>>>> On Mar 4, 2012, at 9:59 AM, Tom Mazzotta wrote: >>>>> >>>>>> I just upgraded my system from 0.7.10 using the CLI. Screen >>>>>> capture from PuTTY below: >>>>>> >>>>>> pbx ~ # upgrade-run-image check >>>>>> http://mirror.astlinux.org/firmware-1.x >>>>>> Current version is: astlinux-0.7.10, Newest available version is: >>>>>> astlinux-1.0.2 pbx ~ # upgrade-run-image upgrade >>>>>> http://mirror.astlinux.org/firmware-1.x >>>>>> Successful upgrade to: astlinux-1.0.2 [after reboot] pbx ~ # >>>>>> upgrade-RUNNIX-image check http://mirror.astlinux.org/runnix4 >>>>>> Current version is: runnix-0.3.3, Newest available version is: >>>>>> runnix-0.4-5339 pbx ~ # upgrade-RUNNIX-image upgrade >>>>>> http://mirror.astlinux.org/runnix4 >>>>>> Successful upgrade to: runnix-0.4-5339 pbx ~ # reboot pbx ~ # >>>>>> >>>>>> All appeared OK, however, the system crashes during the boot process. >>>>>> Using my console cable connected to the Soekris, the last thing I see: >>>>>> >>>>>> BUG: unable to handle kernel NULL pointer dereference at 00000054 >>>>>> IP: [<c11fbb0c>] tc_fill_qdisc+0x7f/0x22d *pde = 00000000 >>>>>> Oops: 0000 [#1] PREEMPT >>>>>> last sysfs file: /sys/module/x_tables/initstate Modules linked in: >>>>>> sch_ingress sch_sfq sch_htb xt_dscp xt_CLASSIFY xt_length >>>>>> xt_recent xt_tcpudp ipt_MASQUERADE nf_nat_ftp iptable_nat nf_nat >>>>>> nf_conntrack_ipv4 nf_defrag_ipv4 xt_TCPMSS ipt_LOG ipt_REJECT >>>>>> iptable_mangle xt_multiport xt_state xt_limit xt_conntrack >>>>>> nf_conntrack_ftp nf_conntrack iptable_filter ip_tables x_tables >>>>>> pc87360 hwmon_vid hwmon bridge stp llc wanec af_wanpipe wanpipe >>>>>> wanrouter dahdi sdladrv geodewdt cs5535_mfgpt geode_rng geode_aes >>>>>> via_rhine mii rtc cs5535_gpio >>>>>> >>>>>> Pid: 1046, comm: tc Not tainted 2.6.35.13-astlinux #1 / >>>>>> EIP: 0060:[<c11fbb0c>] EFLAGS: 00010283 CPU: 0 EIP is at >>>>>> tc_fill_qdisc+0x7f/0x22d >>>>>> EAX: dfa30010 EBX: c13602b0 ECX: 00000000 EDX: 00000000 >>>>>> ESI: dec8b200 EDI: dfa30000 EBP: deccbbf8 ESP: deccbb9c >>>>>> DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 0068 Process tc (pid: >>>>>> 1046, >>>>>> ti=decca000 task=decd1ac0 task.ti=decca000) >>>>>> Stack: >>>>>> 00000000 df9bc760 dfa30000 fffffff1 00000001 00000000 deccbbb4 >>>>>> deccbbb4 <0> df9c3001 fffffff1 deccbc98 deccbc24 00000246 df99c4a4 >>>>>> 00000202 00000202 <0> dec8b200 000000d0 df809680 deccbc04 dec8b200 >>>>>> 00000416 df9c3000 deccbc20 Call Trace: >>>>>> [<c11fcba3>] ? T.765+0x5d/0xce >>>>>> [<c11fcc34>] ? T.764+0x20/0x35 >>>>>> [<c11fcd64>] ? qdisc_graft+0x11b/0x19d [<c11fd153>] ? >>>>>> tc_modify_qdisc+0x36d/0x3b9 [<c11fcde6>] ? >>>>>> tc_modify_qdisc+0x0/0x3b9 [<c11f682f>] ? rtnetlink_rcv_msg+0x17e/0x194 >>>>>> [<c11f66b1>] ? >>>>>> rtnetlink_rcv_msg+0x0/0x194 [<c12017e2>] ? >>>>>> netlink_rcv_skb+0x30/0x77 [<c11f66aa>] ? rtnetlink_rcv+0x1b/0x22 >>>>>> [<c1201586>] ? >>>>>> netlink_unicast+0x1ae/0x20e [<c1201c7b>] ? >>>>>> netlink_sendmsg+0x223/0x230 [<c11e0f27>] ? sock_sendmsg+0xa4/0xba >>>>>> [<c104d61b>] ? >>>>>> find_lock_page+0x13/0x46 [<c10564bd>] ? shmem_getpage+0x5d/0x6e8 >>>>>> [<c11e84c6>] ? verify_iovec+0x3e/0x78 [<c11e131a>] ? >>>>>> sys_sendmsg+0x149/0x196 [<c104d605>] ? unlock_page+0x3d/0x40 >>>>>> [<c105b5eb>] ? __do_fault+0x2e0/0x30c [<c105ca06>] ? >>>>>> handle_mm_fault+0x273/0x522 [<c1252858>] ? >>>>>> do_page_fault+0x37a/0x3a8 [<c11e2394>] ? sys_socketcall+0x146/0x18b >>>>>> [<c1250725>] ? >>>>>> syscall_call+0x7/0xb >>>>>> Code: 47 04 8b 4d a4 66 89 4f 06 8b 45 08 89 47 0c 8b 45 0c c6 47 >>>>>> 10 >>>>>> 00 89 47 08 8d 47 10 c6 40 01 00 66 c7 40 02 00 00 8b 53 40 8b 12 >>>>>> <8b> >>>>>> 52 54 89 50 04 8b 55 b0 89 50 0c 8b 53 20 89 50 08 8b 53 28 >>>>>> EIP: [<c11fbb0c>] tc_fill_qdisc+0x7f/0x22d SS:ESP 0068:deccbb9c >>>>>> CR2: 0000000000000054 >>>>>> ---[ end trace 9e93ac46ed9c5d12 ]--- Killed >>>>>> >>>>>> I'm attaching the complete bootup log to this email. I'd really >>>>>> appreciate it if someone could help me resolve this issue; all >>>>>> phones are dead at this time! >>>>>> >>>>>> THANKS!! >>>>>> <putty.log>------------------------------------------------------- > > > > ------------------------------------------------------------------------------ > Virtualization & Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > _______________________________________________ > Astlinux-users mailing list > Astlinux-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to > pay...@krisk.org. > > ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
