Results 1 to 2 of 2

Thread: un-documented: error on development server

  1. #1
    rcherry Guest

    Default un-documented: error on development server

    I've built my development server and configured uboot to use it. The appliance is connecting to the server and loads the image but is unable to load Asterisk. I'm unable to find any information in the PADS user guide on how to troubleshoot this problem. Any help would be appreciated. From what I can tell I'm unable to write to flash on the appliance?

    U-Boot 1.3.0-65 (Feb 9 2009 - 15:51:21)

    Hit any key to stop autoboot: -1
    TFTP from server 192.168.1.83; our IP address is 192.168.1.75
    Filename 'cuImage.warp'.
    Load address: 0x200000
    Loading: ################################################## ###############
    #######################################


    <output omitted to conserve space>

    done
    Bytes transferred = 1526276 (174a04 hex)
    ## Booting image at 00200000 ...
    Image Name: Linux-2.6.26.5-pika
    Image Type: PowerPC Linux Kernel Image (gzip compressed)
    Data Size: 1526212 Bytes = 1.5 MB
    Load Address: 00400000
    Entry Point: 00400684
    Verifying Checksum ... OK
    Uncompressing Kernel Image ... OK


    <output omitted to conserve space>

    zImage starting: loaded at 0x00400000 (sp: 0x0fefe510)
    Allocating 0x321b24 bytes for kernel ...
    gunzipping (0x00000000 <- 0x0040e000:0x0072436c)...done 0x2ff468 bytes

    <output omitted to conserve space>

    Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65023
    Kernel command line: root=/dev/nfs rw nfsroot=192.168.1.83:/PADS/v_2.0.5.5/PADS_
    2.0.5.5/build_warp/root ip=192.168.1.75:192.168.1.83:192.168.1.2:255.255.2 55.0:w
    arp:eth0ff panic=1 console=ttyS0,115200
    UIC0 (32 IRQ sources) at DCR 0xc0
    UIC1 (32 IRQ sources) at DCR 0xd0
    PID hash table entries: 1024 (order: 10, 4096 bytes)
    clocksource: timebase mult[79364e] shift[22] registered
    Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
    Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
    Memory: 256384k/262140k available (2920k kernel code, 5492k reserved, 124k data,
    134k bss, 156k init)
    Mount-cache hash table entries: 512
    net_namespace: 480 bytes
    NET: Registered protocol family 16

    SCSI subsystem initialized

    <output omitted to conserve space>
    console handover: b
    oot [udbg0] -> real [ttyS0]
    brd: module loaded
    PPC 4xx OCP EMAC driver, version 3.54
    MAL v1 /plb/mcmal, 4 TX channels, 2 RX channels
    ZMII /plb/opb/emac-zmii@ef600d00 initialized
    /plb/opb/emac-zmii@ef600d00: bridge in RMII mode
    eth0: EMAC-0 /plb/opb/ethernet@ef600e00, MAC 00:1e:84:00:00:0e
    eth0: found Generic MII PHY (0x01)
    Driver 'sd' needs updating - please use bus_type methods
    ffc00000.nor_flash: Found 1 x16 devices at 0x0 in 16-bit bank
    Amd/Fujitsu Extended Query Table at 0x0040
    ffc00000.nor_flash: CFI does not contain boot bank location. Assuming top.
    number of CFI chips: 1
    cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
    cmdlinepart partition parsing not available
    RedBoot partition parsing not available
    Creating 3 MTD partitions on "ffc00000.nor_flash":
    0x00300000-0x00340000 : "fpga"
    0x00340000-0x00380000 : "env"
    0x00380000-0x00400000 : "u-boot"
    NDFC NAND Driver initialized. Chip-Rev: 0x00000109
    NAND device: Manufacturer ID: 0xec, Chip ID: 0xda (Samsung NAND 256MiB 3,3V 8-bi
    t)

    Scanning device for bad blocks
    Bad eraseblock 1721 at 0x0d720000

    Number of partitions 5
    Creating 5 MTD partitions on "NAND 256MiB 3,3V 8-bit":
    0x00000000-0x00200000 : "kernel"
    0x00200000-0x04000000 : "root"
    0x04000000-0x08000000 : "persistent"
    0x08000000-0x0c000000 : "persistent1"
    0x0c000000-0x10000000 : "persistent2"
    ndfc: Failed to register with procfs.
    usbmon: debugfs is not available
    ppc-of-ohci ef601000.usb: OF OHCI
    ppc-of-ohci ef601000.usb: new USB bus registered, assigned bus number 1
    ppc-of-ohci ef601000.usb: irq 22, io mem 0xef601000
    usb usb1: configuration #1 chosen from 1 choice
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 2 ports detected
    Initializing USB Mass Storage driver...


    <output omitted to conserve space>

    Warp POST OK
    PIKA DTM thread running.
    eth0: link is down
    eth0: link is up, 100 FDX
    mmc0: new SD card at address 950b
    mmcblk0: mmc0:950b SD02G 1985024KiB
    mmcblk0: p1
    IP-Config: Complete:
    device=eth0, addr=192.168.1.75, mask=255.255.255.0, gw=192.168.1.2,
    host=warp, domain=, nis-domain=(none),
    bootserver=192.168.1.83, rootserver=192.168.1.83, rootpath=
    Looking up port of RPC 100003/2 on 192.168.1.83
    Looking up port of RPC 100005/1 on 192.168.1.83
    VFS: Mounted root (nfs filesystem).
    Freeing unused kernel memory: 156k init
    init started: BusyBox v1.10.3 (2009-05-26 17:27:13 EDT)
    starting pid 26, tty '': '/sbin/syslogd'
    starting pid 28, tty '': '/sbin/klogd'
    starting pid 30, tty '': '/etc/rc.S'
    /etc/rc.S: line 7: cannot create /etc/mtab: Read-only file system
    ln: /etc/HOSTNAME: Read-only file system
    ln: /etc/asterisk: Read-only file system
    ln: /etc/devfsd.conf: Read-only file system
    ln: /etc/dnsd.conf: Read-only file system
    ln: /etc/dropbear: Read-only file system
    ln: /etc/fstab: Read-only file system
    ln: /etc/group: Read-only file system
    ln: /etc/hosts: Read-only file system
    ln: /etc/httpd.conf: Read-only file system
    ln: /etc/inetd.conf: Read-only file system
    ln: /etc/localenv: Read-only file system
    ln: /etc/networking.conf: Read-only file system
    ln: /etc/nsswitch.conf: Read-only file system
    ln: /etc/ntp: Read-only file system
    ln: /etc/ntp.conf: Read-only file system
    ln: /etc/passwd: File exists
    ln: /etc/pika: Read-only file system
    ln: /etc/profile: Read-only file system
    ln: /etc/protocols: Read-only file system
    ln: /etc/rc.0: Read-only file system
    ln: /etc/rc.local: Read-only file system
    ln: /etc/resolv.conf: Read-only file system
    ln: /etc/securetty: Read-only file system
    ln: /etc/services: Read-only file system
    ln: /etc/shells: Read-only file system
    ln: /etc/termcap: Read-only file system
    ln: /etc/terminfo: Read-only file system
    ln: /etc/udhcpd.conf: Read-only file system
    ln: /etc/zaptel.conf: Read-only file system
    cat: can't open '/etc/HOSTNAME': No such file or directory
    warp
    ln: /root: Read-only file system
    mount: cannot read /etc/fstab: No such file or directory
    ln: /var/tmp: Read-only file system
    fgrep: /etc/fstab: No such file or directory
    cat: can't open '/etc/resolv.conf': No such file or directory
    cat: can't open '/etc/resolv.conf': No such file or directory
    Copying file to asterisk/networking2.conf
    mkdir: cannot create directory '/etc/asterisk': Read-only file system
    /etc/rc.S: /persistent/autorun/S30networking: line 45: cannot create /etc/asteri
    sk/networking2.conf: nonexistent directory
    /etc/rc.S: /persistent/autorun/S30networking: line 46: cannot create /etc/asteri
    sk/networking2.conf: nonexistent directory
    Networking was configured from u-boot...
    Error : Servname not supported for ai_socktype
    1 Jan 00:00:03 ntpdate[93]: can't find host 0.pool.ntp.org

    1 Jan 00:00:03 ntpdate[93]: no servers can be used, exiting
    chmod: /dev/pika1: Read-only file system
    chmod: /dev/pika2: Read-only file system
    chmod: /dev/pika3: Read-only file system
    chmod: /dev/pika4: Read-only file system
    chmod: /dev/pikahsp: Read-only file system
    chmod: /dev/pikalcd: Read-only file system
    Starting the PIKA drivers
    pikahsp: module license 'PIKA Technologies Inc.' taints kernel.
    PIKA HSP Starting. HZ=1000.
    pikacore: registered 253.0
    taco: FPGA 00212026
    Modules A: FXO B: FXS
    pikacore: registered 253.1
    pikalcd: lcd_init_module
    pikacore: registered 253.60
    insmod: cannot insert '/lib/modules/2.6.26.5-pika/kernel/drivers/char/pikabrie.k
    o': No such device
    modprobe: failed to load module pikabrie
    Starting Zaptel
    Zapata Telephony Interface Registered on major 196
    Zaptel Version: 1.4.9.2
    Zaptel Echo Canceller: MG2
    /usr/sbin/aohscan: line 36: cannot create /tmp/aohscan.new: Read-only file syste
    m
    /usr/sbin/aohscan: line 37: cannot create /tmp/zapscan.conf: Read-only file syst
    em
    cp: cannot stat '/tmp/zapscan.conf': No such file or directory
    Checking for hardware changes...
    Hardware has changed, updating configuration...
    mv: cannot rename '/tmp/aohscan.new': No such file or directory
    mv: cannot rename '/tmp/zapscan.conf': No such file or directory
    Running 'pikacf'
    /tmp/.PIKAlock: Read-only file system
    sed: /etc/asterisk/pika.conf: No such file or directory
    sed: /etc/asterisk/pika.conf: No such file or directory
    sed: /etc/asterisk/pika.conf: No such file or directory
    pkdummy: init() finished
    mkdir: cannot create directory '/var/log/asterisk': Read-only file system
    Starting Astmanproxy
    ln: /var/www: Read-only file system
    Starting HTTPD
    httpd: chdir(/var/www/htdocs): No such file or directory
    chmod: /persistent/tftpboot: Read-only file system
    Starting tftpd...
    chmod: /mnt/sd: Read-only file system
    chmod: /mnt/usb: Read-only file system
    PIKA WDT started...
    starting pid 141, tty '': '/sbin/svscan /service'
    starting pid 142, tty '': '/sbin/getty -L ttyS0 115200 vt100'
    supervise: fatal: unable to acquire ntpd/supervise/lock: file does not exist
    supervise: fatal: unable to acquire autoflash-sd/supervise/lock: file does not e
    xist
    supervise: fatal: unable to acquire asterisk/supervise/lock: file does not exist

    supervise: fatal: unable to acquire autoflash-usb/supervise/lock: file does not
    exist
    supervise: fatal: unable to acquire dropbear/supervise/lock: file does not exist


    warp login:

  2. #2
    skar Guest

    Default check permissions on NFS directory

    Asterisk is unable to start because the service that starts it cannot create a file that it needs. Ensure that the nfs mount point on your development computer is witeable. Check in your /etc/exports file on the host has rw and not ro in its permissions for the nfs mount point you are using.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •