From: rough_wood <rou...@ya...> - 2012-05-05 18:25:25
|
This post says it doesn't show up on the mailing list and I am checking to see if this fixes it. -- View this message in context: http://gumstix.8.n6.nabble.com/Fails-to-boot-after-opkg-update-upgrade-tp4939860p4954868.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: rough_wood <rou...@ya...> - 2012-05-08 20:22:47
|
I recieved what seemed to be a working IronSTORM, and updated it exactly as asked by the Gumstix website; opkg update opkg upgrade After what seemed like an hour or more, it was finished. There were a couple little errors but I ignored them as I couldn't change it, and with what little experience I have with linux there are always font errors or something. Well I try to boot again, and I get this; [<c0008404>] (kernel_init+0x94/0x148) from [<c00f38c0>] (kernel_thread_exit+0x0/0x8) ---[ end trace 1b75b31a2719ed1c ]--- Found NAND on CS0 hw perfevents: enabled with ARMv7 Cortex-A8 PMU driver, 5 counters available Switched to new clocking rate (Crystal/Core/MPU): 26.0/500/332 MHz OMAP DMA hardware revision 5.0 bio: create slab <bio-0> at 0 SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb i2c_omap i2c_omap.1: bus 1 rev4.0 at 2600 kHz twl4030: PIH (irq 7) chaining IRQs 368..375 twl4030: power (irq 373) chaining IRQs 376..383 twl4030: gpio (irq 368) chaining IRQs 384..401 regulator: VUSB1V5: 1500 mV normal standby regulator: VUSB1V8: 1800 mV normal standby regulator: VUSB3V1: 3100 mV normal standby twl4030_usb twl4030_usb: Initialized TWL4030 USB module regulator: VMMC1: 1850 <--> 3150 mV at 3000 mV normal standby regulator: VDAC: 1800 mV normal standby regulator: VDVI: 1800 mV normal standby i2c_omap i2c_omap.3: bus 3 rev4.0 at 400 kHz Advanced Linux Sound Architecture Driver Version 1.0.22.1. Bluetooth: Core ver 2.15 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized cfg80211: Calling CRDA to update world regulatory domain Switching to clocksource 32k_counter musb_hdrc: version 6.0, musb-dma, host, debug=0 musb_hdrc musb_hdrc: MUSB HDRC host driver musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1 usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb1: Product: MUSB HDRC host driver usb usb1: Manufacturer: Linux 2.6.34 musb-hcd usb usb1: SerialNumber: musb_hdrc hub 1-0:1.0: USB hub found hub 1-0:1.0: 1 port detected musb_hdrc musb_hdrc: USB Host mode controller at fa0ab000 using DMA, IRQ 92 NET: Registered protocol family 2 IP route cache hash table entries: 4096 (order: 2, 16384 bytes) TCP established hash table entries: 16384 (order: 5, 131072 bytes) TCP bind hash table entries: 16384 (order: 4, 65536 bytes) TCP: Hash tables configured (established 16384 bind 16384) TCP reno registered UDP hash table entries: 256 (order: 0, 4096 bytes) UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) NET: Registered protocol family 1 RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. VFS: Disk quotas dquot_6.5.2 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc. msgmni has been set to 978 alg: No test for stdrng (krng) Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) OMAP DSS rev 2.0 OMAP DISPC rev 3.0 OMAP VENC rev 2 OMAP DSI rev 1.0 Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654 serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654 serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654 console [ttyS2] enabled brd: module loaded loop: module loaded omap2-nand driver initializing NAND device: Manufacturer ID: 0x2c, Chip ID: 0xbc (Micron NAND 512MiB 1,8V 16-bit) cmdlinepart partition parsing not available Creating 5 MTD partitions on "omap2-nand.0": 0x000000000000-0x000000080000 : "xloader" 0x000000080000-0x000000240000 : "uboot" 0x000000240000-0x000000280000 : "uboot environment" 0x000000280000-0x000000680000 : "linux" 0x000000680000-0x000020000000 : "rootfs" smsc911x: Driver version 2008-10-21. smsc911x-mdio: probed eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:01, irq=-1) net eth0: MAC Address: 00:15:c9:28:f1:2a smsc911x: Driver version 2008-10-21. usbcore: registered new interface driver asix usbcore: registered new interface driver cdc_ether ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver ehci-omap ehci-omap.0: OMAP-EHCI Host Controller ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 2 ehci-omap ehci-omap.0: irq 77, io mem 0x48064800 ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00 usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb2: Product: OMAP-EHCI Host Controller usb usb2: Manufacturer: Linux 2.6.34 ehci_hcd usb usb2: SerialNumber: ehci-omap.0 hub 2-0:1.0: USB hub found hub 2-0:1.0: 3 ports detected Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. udc: OMAP UDC driver, version: 4 October 2004 (iso) (dma) mice: PS/2 mouse device common for all mice twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0 twl_rtc twl_rtc: Power up reset detected. i2c /dev entries driver OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec twl4030_wdt twl4030_wdt: Failed to register misc device twl4030_wdt: probe of twl4030_wdt failed with error -16 Bluetooth: HCI UART driver ver 2.2 Bluetooth: HCI H4 protocol initialized Bluetooth: HCI BCSP protocol initialized Bluetooth: HCILL protocol initialized usbcore: registered new interface driver usbhid usbhid: USB HID core driver usbcore: registered new interface driver snd-usb-audio No device for DAI omap-mcbsp-dai-0 No device for DAI omap-mcbsp-dai-1 No device for DAI omap-mcbsp-dai-2 No device for DAI omap-mcbsp-dai-3 No device for DAI omap-mcbsp-dai-4 overo SoC init asoc: twl4030 <-> omap-mcbsp-dai-0 mapping ok ALSA device list: #0: overo (twl4030) oprofile: using arm/armv7 TCP cubic registered NET: Registered protocol family 17 NET: Registered protocol family 15 Bluetooth: L2CAP ver 2.14 Bluetooth: L2CAP socket layer initialized Bluetooth: SCO (Voice Link) ver 0.6 Bluetooth: SCO socket layer initialized Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM ver 1.11 Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Bluetooth: BNEP filters: protocol multicast Bluetooth: HIDP (Human Interface Emulation) ver 1.2 ThumbEE CPU extension supported. Power Management for TI OMAP3. VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3 fbcvt: 1024x768@60: CVT Name - .786M3-R Console: switching to colour frame buffer device 128x48 regulator_init_complete: incomplete constraints, leaving VDAC on twl_rtc twl_rtc: setting system clock to 2000-01-01 00:00:22 UTC (946684822) mmc1: new SDIO card at address 0001 Empty flash at 0x03c31794 ends at 0x03c31800 Empty flash at 0x162509fc ends at 0x16251000 JFFS2 notice: (1) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found. VFS: Mounted root (jffs2 filesystem) on device 31:4. devtmpfs: mounted Freeing init memory: 936K INIT: version 2.86 booting Please wait: booting... Starting udev Remounting root file system... Caching udev devnodes Populating dev cache logger: cannot connect: No such file or directory ALSA: Restoring mixer settings... Configuring network interfaces... done. Starting portmap daemon: portmap. net.ipv4.conf.default.rp_filter = 1 net.ipv4.conf.all.rp_filter = 1 JFFS2 notice: (722) check_node_data: wrong data CRC in data node at 0x03c30cf0: read 0x4ac2cfb8, calculated 0x3f36e8ae. Mon Apr 26 00:03:00 BST 2010 Turning echo off on /dev/ttyS1 INIT: Entering runlevel: 5 Starting system message bus: dbus. Starting Hardware abstraction layer hald Starting OpenBSD Secure Shell server: sshd modprobe: FATAL: Could not read '/lib/modules/2.6.34/kernel/net/ipv6/ipv6.ko': No such file or directory done. Starting advanced power management daemon: No APM support in kernel (failed.) modprobe: FATAL: Could not read '/lib/modules/2.6.34/kernel/net/ipv6/ipv6.ko': No such file or directory Starting ntpd: done Starting syslog-ng:modprobe: FATAL: Could not read '/lib/modules/2.6.34/kernel/net/ipv6/ipv6.ko': No such file or directory . * Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon [ ok ] Starting Bluetooth subsystem: Can't open serial port: No such file or directory Can't initialize device: No such file or directory Starting Network connection manager daemon: NetworkManager. No SGX hardware, not starting PVR Starting GPE display manager: gpe-dm net eth1: SMSC911x/921x identified at 0xe08c8000, IRQ: 336 JFFS2 notice: (982) check_node_data: wrong data CRC in data node at 0x06d53b80: read 0xbcdc7770, calculated 0xde94f2ea. ^C³tØ°b$U ÔH¨HU¯¬.HR·.]®][Y·ºs X-Loader 1.5.0 (Sep 16 2011 - 12:10:02) OMAP36XX/37XX-GP ES2.1 Board revision: 1 Loading u-boot.bin from nand U-Boot 2010.09 (Oct 20 2010 - 10:11:49) OMAP36XX/37XX-GP ES2.1, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz Gumstix Overo board + LPDDR/NAND I2C: ready DRAM: 512 MiB NAND: 512 MiB *** Warning - bad CRC or NAND, using default environment In: serial Out: serial Err: serial Board revision: 1 Tranceiver detected on mmc2 No EEPROM on expansion board Die ID #238e00229ff800000168300f0701b025 Net: smc911x-0 Hit any key to stop autoboot: 0 No MMC card found Booting from nand ... NAND read: device 0 offset 0x280000, size 0x400000 4194304 bytes read: OK ## Booting kernel from Legacy Image at 82000000 ... Image Name: Angstrom/2.6.34/overo Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3160068 Bytes = 3 MiB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. Linux version 2.6.34 (st...@ww...) (gcc version 4.3.3 (GCC) ) #1 Wed Oct 20 10:22:48 PDT 2010 CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache Machine: Gumstix Overo Memory policy: ECC disabled, Data cache writeback OMAP3630 ES1.0 (l2cache iva sgx neon isp 192mhz_clk ) SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x100000 Reserving 12582912 bytes SDRAM for VRAM Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048 Kernel command line: console=ttyS2,115200n8 mpurate=500 vram=12M omapfb.mode=dvi:1024x768MR-16@60 omapfb.debug=y omapdss.def_disp=dvi root=/dev/mtdblock4 rw rootfstype=jffs2 PID hash table entries: 2048 (order: 1, 8192 bytes) Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Memory: 256MB 256MB = 512MB total Memory: 500816k/500816k available, 23472k reserved, 0K highmem Virtual kernel memory layout: vector : 0xffff0000 - 0xffff1000 ( 4 kB) fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) DMA : 0xffc00000 - 0xffe00000 ( 2 MB) vmalloc : 0xe0800000 - 0xf8000000 ( 376 MB) lowmem : 0xc0000000 - 0xe0000000 ( 512 MB) modules : 0xbf000000 - 0xc0000000 ( 16 MB) .init : 0xc0008000 - 0xc00f2000 ( 936 kB) .text : 0xc00f2000 - 0xc05f6000 (5136 kB) .data : 0xc061a000 - 0xc0659400 ( 253 kB) Hierarchical RCU implementation. NR_IRQS:402 Clocking rate (Crystal/Core/MPU): 26.0/332/600 MHz (null): no physical address for uart#3, so skipping early_init... Reprogramming SDRC clock to 332000000 Hz GPMC revision 5.0 IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96 interrupts Total of 96 interrupts on 1 active controller OMAP GPIO hardware version 2.5 OMAP clockevent source: GPTIMER1 at 32768 Hz Console: colour dummy device 80x30 Calibrating delay loop... 597.64 BogoMIPS (lpj=2334720) Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok devtmpfs: initialized regulator: core version 0.5 NET: Registered protocol family 16 ------------[ cut here ]------------ WARNING: at arch/arm/mach-omap2/serial.c:727 omap_serial_init_port+0x60/0x480() (null): can't init uart3, no clocks available Modules linked in: [<c00f75c8>] (unwind_backtrace+0x0/0xec) from [<c0119b50>] (warn_slowpath_common+0x4c/0x80) [<c0119b50>] (warn_slowpath_common+0x4c/0x80) from [<c0119bc0>] (warn_slowpath_fmt+0x28/0x38) [<c0119bc0>] (warn_slowpath_fmt+0x28/0x38) from [<c000e98c>] (omap_serial_init_port+0x60/0x480) [<c000e98c>] (omap_serial_init_port+0x60/0x480) from [<c000edd8>] (omap_serial_init+0x2c/0x3c) [<c000edd8>] (omap_serial_init+0x2c/0x3c) from [<c0010680>] (overo_init+0x4c/0x4a0) [<c0010680>] (overo_init+0x4c/0x4a0) from [<c000b7e4>] (customize_machine+0x1c/0x2c) [<c000b7e4>] (customize_machine+0x1c/0x2c) from [<c00f234c>] (do_one_initcall+0x5c/0x1bc) [<c00f234c>] (do_one_initcall+0x5c/0x1bc) from [<c0008404>] (kernel_init+0x94/0x148) [<c0008404>] (kernel_init+0x94/0x148) from [<c00f38c0>] (kernel_thread_exit+0x0/0x8) ---[ end trace 1b75b31a2719ed1c ]--- Found NAND on CS0 hw perfevents: enabled with ARMv7 Cortex-A8 PMU driver, 5 counters available Switched to new clocking rate (Crystal/Core/MPU): 26.0/500/332 MHz OMAP DMA hardware revision 5.0 bio: create slab <bio-0> at 0 SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb i2c_omap i2c_omap.1: bus 1 rev4.0 at 2600 kHz twl4030: PIH (irq 7) chaining IRQs 368..375 twl4030: power (irq 373) chaining IRQs 376..383 twl4030: gpio (irq 368) chaining IRQs 384..401 regulator: VUSB1V5: 1500 mV normal standby regulator: VUSB1V8: 1800 mV normal standby regulator: VUSB3V1: 3100 mV normal standby twl4030_usb twl4030_usb: Initialized TWL4030 USB module regulator: VMMC1: 1850 <--> 3150 mV at 3000 mV normal standby regulator: VDAC: 1800 mV normal standby regulator: VDVI: 1800 mV normal standby i2c_omap i2c_omap.3: bus 3 rev4.0 at 400 kHz Advanced Linux Sound Architecture Driver Version 1.0.22.1. Bluetooth: Core ver 2.15 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized cfg80211: Calling CRDA to update world regulatory domain Switching to clocksource 32k_counter musb_hdrc: version 6.0, musb-dma, host, debug=0 musb_hdrc musb_hdrc: MUSB HDRC host driver musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1 usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb1: Product: MUSB HDRC host driver usb usb1: Manufacturer: Linux 2.6.34 musb-hcd usb usb1: SerialNumber: musb_hdrc hub 1-0:1.0: USB hub found hub 1-0:1.0: 1 port detected musb_hdrc musb_hdrc: USB Host mode controller at fa0ab000 using DMA, IRQ 92 NET: Registered protocol family 2 IP route cache hash table entries: 4096 (order: 2, 16384 bytes) TCP established hash table entries: 16384 (order: 5, 131072 bytes) TCP bind hash table entries: 16384 (order: 4, 65536 bytes) TCP: Hash tables configured (established 16384 bind 16384) TCP reno registered UDP hash table entries: 256 (order: 0, 4096 bytes) UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) NET: Registered protocol family 1 RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. VFS: Disk quotas dquot_6.5.2 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc. msgmni has been set to 978 alg: No test for stdrng (krng) Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) OMAP DSS rev 2.0 OMAP DISPC rev 3.0 OMAP VENC rev 2 OMAP DSI rev 1.0 Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654 serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654 serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654 console [ttyS2] enabled brd: module loaded loop: module loaded omap2-nand driver initializing NAND device: Manufacturer ID: 0x2c, Chip ID: 0xbc (Micron NAND 512MiB 1,8V 16-bit) cmdlinepart partition parsing not available Creating 5 MTD partitions on "omap2-nand.0": 0x000000000000-0x000000080000 : "xloader" 0x000000080000-0x000000240000 : "uboot" 0x000000240000-0x000000280000 : "uboot environment" 0x000000280000-0x000000680000 : "linux" 0x000000680000-0x000020000000 : "rootfs" smsc911x: Driver version 2008-10-21. smsc911x-mdio: probed eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:01, irq=-1) net eth0: MAC Address: 00:15:c9:28:f1:2a smsc911x: Driver version 2008-10-21. usbcore: registered new interface driver asix usbcore: registered new interface driver cdc_ether ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver ehci-omap ehci-omap.0: OMAP-EHCI Host Controller ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 2 ehci-omap ehci-omap.0: irq 77, io mem 0x48064800 ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00 usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb2: Product: OMAP-EHCI Host Controller usb usb2: Manufacturer: Linux 2.6.34 ehci_hcd usb usb2: SerialNumber: ehci-omap.0 hub 2-0:1.0: USB hub found hub 2-0:1.0: 3 ports detected Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. udc: OMAP UDC driver, version: 4 October 2004 (iso) (dma) mice: PS/2 mouse device common for all mice twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0 twl_rtc twl_rtc: Power up reset detected. i2c /dev entries driver OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec twl4030_wdt twl4030_wdt: Failed to register misc device twl4030_wdt: probe of twl4030_wdt failed with error -16 Bluetooth: HCI UART driver ver 2.2 Bluetooth: HCI H4 protocol initialized Bluetooth: HCI BCSP protocol initialized Bluetooth: HCILL protocol initialized usbcore: registered new interface driver usbhid usbhid: USB HID core driver usbcore: registered new interface driver snd-usb-audio No device for DAI omap-mcbsp-dai-0 No device for DAI omap-mcbsp-dai-1 No device for DAI omap-mcbsp-dai-2 No device for DAI omap-mcbsp-dai-3 No device for DAI omap-mcbsp-dai-4 overo SoC init asoc: twl4030 <-> omap-mcbsp-dai-0 mapping ok ALSA device list: #0: overo (twl4030) oprofile: using arm/armv7 TCP cubic registered NET: Registered protocol family 17 NET: Registered protocol family 15 Bluetooth: L2CAP ver 2.14 Bluetooth: L2CAP socket layer initialized Bluetooth: SCO (Voice Link) ver 0.6 Bluetooth: SCO socket layer initialized Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM ver 1.11 Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Bluetooth: BNEP filters: protocol multicast Bluetooth: HIDP (Human Interface Emulation) ver 1.2 ThumbEE CPU extension supported. Power Management for TI OMAP3. VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3 fbcvt: 1024x768@60: CVT Name - .786M3-R Console: switching to colour frame buffer device 128x48 regulator_init_complete: incomplete constraints, leaving VDAC on twl_rtc twl_rtc: setting system clock to 2000-01-01 00:00:22 UTC (946684822) mmc1: new SDIO card at address 0001 Empty flash at 0x03c31794 ends at 0x03c31800 Empty flash at 0x162509fc ends at 0x16251000 JFFS2 notice: (1) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found. VFS: Mounted root (jffs2 filesystem) on device 31:4. devtmpfs: mounted Freeing init memory: 936K INIT: version 2.86 booting Please wait: booting... Starting udev Remounting root file system... Caching udev devnodes Populating dev cache logger: cannot connect: No such file or directory ALSA: Restoring mixer settings... Configuring network interfaces... done. Starting portmap daemon: portmap. net.ipv4.conf.default.rp_filter = 1 net.ipv4.conf.all.rp_filter = 1 JFFS2 notice: (722) check_node_data: wrong data CRC in data node at 0x03c30cf0: read 0x4ac2cfb8, calculated 0x3f36e8ae. Mon Apr 26 00:03:00 BST 2010 Turning echo off on /dev/ttyS1 INIT: Entering runlevel: 5 Starting system message bus: dbus. Starting Hardware abstraction layer hald Starting OpenBSD Secure Shell server: sshd modprobe: FATAL: Could not read '/lib/modules/2.6.34/kernel/net/ipv6/ipv6.ko': No such file or directory done. Starting advanced power management daemon: No APM support in kernel (failed.) modprobe: FATAL: Could not read '/lib/modules/2.6.34/kernel/net/ipv6/ipv6.ko': No such file or directory Starting ntpd: done Starting syslog-ng:modprobe: FATAL: Could not read '/lib/modules/2.6.34/kernel/net/ipv6/ipv6.ko': No such file or directory . * Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon [ ok ] Starting Bluetooth subsystem: Can't open serial port: No such file or directory Can't initialize device: No such file or directory Starting Network connection manager daemon: NetworkManager. No SGX hardware, not starting PVR Starting GPE display manager: gpe-dm net eth1: SMSC911x/921x identified at 0xe08c8000, IRQ: 336 JFFS2 notice: (982) check_node_data: wrong data CRC in data node at 0x06d53b80: read 0xbcdc7770, calculated 0xde94f2ea. INIT: Id "S" respawning too fast: disabled for 5 minutes JFFS2 warning: (3811) jffs2_sum_write_data: Not enough space for summary, padsize = -556 JFFS2 warning: (6086) jffs2_sum_write_data: Not enough space for summary, padsize = -682 JFFS2 notice: (546) check_node_data: wrong data CRC in data node at 0x1624fd54: read 0x650742f8, calculated 0x67151345. jffs2_sum_write_data: Not enough space for summary, padsize = -628 INIT: Id "S" respawning too fast: disabled for 5 minutes When I wait it just continues to fail. I then tried every flash option I could get my hands on. For example when using tftp it stops after unzipping kernel. Everything has failed so far. It doesn't help having instructions that say to use a2000000 when what is aparently needed is 82000000. Hopefully I am just doing something wrong and this can be fixed. I tried http://www.sakoman.com/OMAP/preparing-a-bootable-sd-card.html using http://cumulus.gumstix.org/images/angstrom/factory/2011-08-30-1058/ making sure to use the updated mlo and renaming it MLO. When doing this I end up with the Kernel Panic. What do I do? I doubt I've exhausted all my options. My linux experience is poor. I am using Puppy Linux 528. I have a windows computer so I can use Putty etc. I tried tftp, and got it to send the files when I changed a2000000 to 82000000. Does Gumstix have an ip address we can tftpboot from? I doubt it but it would make my life alot easier. Please help! As a college student $300 was a big spend, and this thing would make a lowsy doorstop. It's too darn small :) -- View this message in context: http://gumstix.8.n6.nabble.com/Fails-to-boot-after-opkg-update-upgrade-tp4939860p4961346.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Steve S. <sa...@gm...> - 2012-05-08 21:10:10
|
On Tue, May 8, 2012 at 1:22 PM, rough_wood <rou...@ya...> wrote: > I tried http://www.sakoman.com/OMAP/preparing-a-bootable-sd-card.html using > http://cumulus.gumstix.org/images/angstrom/factory/2011-08-30-1058/ making > sure to use the updated mlo and renaming it MLO. When doing this I end up > with the Kernel Panic. > > What do I do? Try using the script here to make a bootable microSD card: http://www.sakoman.com/category/8-gnome-daily-builds-r13.html Steve |
From: Simon K. <sim...@pg...> - 2012-05-08 21:50:58
|
On 9/05/2012, at 8:22 AM, rough_wood wrote: > INIT: Id "S" respawning too fast: disabled for 5 minutes I'm not sure if this is relevant or not, but when I changed my kernel from 2.6.34 to 3.x I got a similar error message. IIRC it was to do with the console changing from ttyS2 to ttyO2. I think I had to edit the line "S:2345:respawn:/sbin/getty 115200 ttyS2" in /etc/inittab, though I don't remember exactly what changed -- probably just switching ttyS to ttyO. Then again, if you're running off NAND and can't boot I guess you won't actually be able to edit that file... Using Steve's script to get a bootable uSD should see you right. Simon. |
From: rough_wood <rou...@ya...> - 2012-05-08 23:30:35
|
When trying the Sakoman script: sh-4.1# ./mksdcard.sh ../mnt/sdb1 dd: opening `../mnt/sdb1': Is a directory DISK SIZE â bytes (standard_in) 1: syntax error CYLINDERS â ./mksdcard.sh: line 113: sfdisk: command not found Improper partitioning on ../mnt/sdb1 sh-4.1# ./mksdcard.sh ../mnt/sdb umount: can't umount ../mnt/sdb: No such file or directory 1024+0 records in 1024+0 records out 1048576 bytes (1.0 MB) copied, 0.00255174 s, 411 MB/s Disk ../mnt/sdb doesn't contain a valid partition table DISK SIZE â 0 bytes CYLINDERS â 0 ./mksdcard.sh: line 113: sfdisk: command not found Improper partitioning on ../mnt/sdb sh-4.1# ./mksdcard.sh /mnt/sdb umount: can't umount /mnt/sdb: Invalid argument 1024+0 records in 1024+0 records out 1048576 bytes (1.0 MB) copied, 0.00264082 s, 397 MB/s Disk /mnt/sdb doesn't contain a valid partition table DISK SIZE â 0 bytes CYLINDERS â 0 ./mksdcard.sh: line 113: sfdisk: command not found Improper partitioning on /mnt/sdb sh-4.1# ./mksdcard.sh /mnt/sdb1 umount: can't umount /mnt/sdb1: Invalid argument dd: opening `/mnt/sdb1': Is a directory DISK SIZE â bytes (standard_in) 1: syntax error CYLINDERS â ./mksdcard.sh: line 113: sfdisk: command not found Improper partitioning on /mnt/sdb1 sh-4.1# ./mksdcard.sh ../dec/sdb1 umount: can't umount ../dec/sdb1: No such file or directory dd: opening `../dec/sdb1': No such file or directory DISK SIZE â bytes (standard_in) 1: syntax error CYLINDERS â ./mksdcard.sh: line 113: sfdisk: command not found Improper partitioning on ../dec/sdb1 sh-4.1# ./mksdcard.sh ../dev/sdb1 umount: can't umount ../dev/sdb11: Invalid argument umount: can't umount ../dev/sdb12: Invalid argument 1024+0 records in 1024+0 records out 1048576 bytes (1.0 MB) copied, 1.29176 s, 812 kB/s Disk ../dev/sdb1 doesn't contain a valid partition table DISK SIZE â 7947157504 bytes CYLINDERS â 966 ./mksdcard.sh: line 113: sfdisk: command not found umount: can't umount ../dev/sdb11: Invalid argument mkfs.vfat 3.0.7 (24 Dec 2009) ../dev/sdb11: No such device or address umount: can't umount ../dev/sdb12: Invalid argument mke2fs 1.41.14 (22-Dec-2010) mke2fs: No such device or address while trying to determine filesystem size Backing up previously downloaded files (if any) mv: cannot stat `MLO': No such file or directory mv: cannot stat `u-boot.bin': No such file or directory mv: cannot stat `uImage': No such file or directory mv: cannot stat `sakoman-gnome-image.tar.bz2': No such file or directory Downloading files from http://feeds.sakoman.com/feeds/gnome-r12/images/overo/current --2012-05-07 22:27:03-- http://feeds.sakoman.com/feeds/gnome-r12/images/overo/current/MLO Resolving feeds.sakoman.com... 209.139.209.168 Connecting to feeds.sakoman.com|209.139.209.168|:80... connected. HTTP request sent, awaiting response... 302 Found Location: /feeds/gnome-r12/images/overo/current/MLO [following] --2012-05-07 22:27:05-- http://feeds.sakoman.com/feeds/gnome-r12/images/overo/current/MLO Connecting to feeds.sakoman.com|209.139.209.168|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 24288 (24K) [text/plain] Saving to: `MLO' 100%[======================================>] 24,288 91.3K/s in 0.3s 2012-05-07 22:27:05 (91.3 KB/s) - `MLO' saved [24288/24288] --2012-05-07 22:27:05-- http://feeds.sakoman.com/feeds/gnome-r12/images/overo/current/u-boot.bin Resolving feeds.sakoman.com... 209.139.209.168 Connecting to feeds.sakoman.com|209.139.209.168|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 235248 (230K) [application/octet-stream] Saving to: `u-boot.bin' 100%[======================================>] 235,248 176K/s in 1.3s 2012-05-07 22:27:07 (176 KB/s) - `u-boot.bin' saved [235248/235248] --2012-05-07 22:27:07-- http://feeds.sakoman.com/feeds/gnome-r12/images/omap3-multi/current/uImage Resolving feeds.sakoman.com... 209.139.209.168 Connecting to feeds.sakoman.com|209.139.209.168|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 2908444 (2.8M) [text/plain] Saving to: `uImage' 100%[======================================>] 2,908,444 56.9K/s in 37s 2012-05-07 22:27:44 (76.8 KB/s) - `uImage' saved [2908444/2908444] --2012-05-07 22:27:44-- http://feeds.sakoman.com/feeds/gnome-r12/images/omap3-multi/current/sakoman-gnome-image.tar.bz2 Resolving feeds.sakoman.com... 209.139.209.168 Connecting to feeds.sakoman.com|209.139.209.168|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 330954537 (316M) [application/x-bzip2] Saving to: `sakoman-gnome-image.tar.bz2' 100%[======================================>] 330,954,537 271K/s in 40m 21s 2012-05-07 23:08:05 (134 KB/s) - `sakoman-gnome-image.tar.bz2' saved [330954537/330954537] mkdir: cannot create directory `/media/sakoman-sd': No such file or directory Could not create mount point: /media/sakoman-sd SD card creation was not successful sh-4.1# You guys should be warned, I am a living testament to Murphy's Law. Strange glitches I noticed when using script (Maybe these are know, or my fault): It repeatedly wouldn't work untill I formatted the whole uSD to FAT32 Despite my drive being shown as ../mnt/sdc that would fail, so I did dev/sdc which finally worked. Actually it was sdb1 The first attempts it failed because it filled my personal storage file in Puppy Linux. I had to expand my personal save space. Thanks for the help so far! -- View this message in context: http://gumstix.8.n6.nabble.com/Fails-to-boot-after-opkg-update-upgrade-tp4939860p4961709.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Keane, B. (STRX) <ben...@ka...> - 2012-05-08 23:39:31
|
It looks like you are calling: ./mksdcard.sh ../mnt/sdb1 but you should be calling: sudo ./mksdcard.sh /dev/sdb (before you run this .. You should make sure this is the correct drive - otherwise ALL the data on the wrong drive will be destroyed!) * sudo is required because I believe the script needs root permissions. ../mnt/ is a directory were the automounter mounts devices .... Whereas /dev is a directory where all the 'devices' live. So make sure sdb is the correct device ... If you sd card already is partitioned you can run 'mount' to see that's the case. Also with that script, I don't believe you need the 1 on the end of the command, because that references the first partition, whereas this script wants to delete all partitions on there and create two or three new partitions. Good luck, Ben >-----Original Message----- >From: rough_wood [mailto:rou...@ya...] >Sent: Wednesday, 9 May 2012 9:30 AM >To: gum...@li... >Subject: Re: [Gumstix-users] Fails to boot after opkg update > upgrade > >When trying the Sakoman script: > >sh-4.1# ./mksdcard.sh ../mnt/sdb1 >dd: opening `../mnt/sdb1': Is a directory DISK SIZE â bytes >(standard_in) 1: syntax error >CYLINDERS â >./mksdcard.sh: line 113: sfdisk: command not found Improper >partitioning on ../mnt/sdb1 sh-4.1# ./mksdcard.sh ../mnt/sdb >umount: can't umount ../mnt/sdb: No such file or directory >1024+0 records in >1024+0 records out >1048576 bytes (1.0 MB) copied, 0.00255174 s, 411 MB/s Disk >../mnt/sdb doesn't contain a valid partition table DISK SIZE >â 0 bytes CYLINDERS â 0 >./mksdcard.sh: line 113: sfdisk: command not found Improper >partitioning on ../mnt/sdb sh-4.1# ./mksdcard.sh /mnt/sdb >umount: can't umount /mnt/sdb: Invalid argument >1024+0 records in >1024+0 records out >1048576 bytes (1.0 MB) copied, 0.00264082 s, 397 MB/s Disk >/mnt/sdb doesn't contain a valid partition table DISK SIZE â >0 bytes CYLINDERS â 0 >./mksdcard.sh: line 113: sfdisk: command not found Improper >partitioning on /mnt/sdb sh-4.1# ./mksdcard.sh /mnt/sdb1 >umount: can't umount /mnt/sdb1: Invalid argument >dd: opening `/mnt/sdb1': Is a directory >DISK SIZE â bytes >(standard_in) 1: syntax error >CYLINDERS â >./mksdcard.sh: line 113: sfdisk: command not found Improper >partitioning on /mnt/sdb1 sh-4.1# ./mksdcard.sh ../dec/sdb1 >umount: can't umount ../dec/sdb1: No such file or directory >dd: opening `../dec/sdb1': No such file or directory DISK SIZE >â bytes >(standard_in) 1: syntax error >CYLINDERS â >./mksdcard.sh: line 113: sfdisk: command not found Improper >partitioning on ../dec/sdb1 sh-4.1# ./mksdcard.sh ../dev/sdb1 >umount: can't umount ../dev/sdb11: Invalid argument >umount: can't umount ../dev/sdb12: Invalid argument >1024+0 records in >1024+0 records out >1048576 bytes (1.0 MB) copied, 1.29176 s, 812 kB/s Disk >../dev/sdb1 doesn't contain a valid partition table DISK SIZE >â 7947157504 bytes CYLINDERS â 966 >./mksdcard.sh: line 113: sfdisk: command not found >umount: can't umount ../dev/sdb11: Invalid argument mkfs.vfat >3.0.7 (24 Dec 2009) >../dev/sdb11: No such device or address >umount: can't umount ../dev/sdb12: Invalid argument mke2fs >1.41.14 (22-Dec-2010) >mke2fs: No such device or address while trying to determine >filesystem size Backing up previously downloaded files (if any) >mv: cannot stat `MLO': No such file or directory >mv: cannot stat `u-boot.bin': No such file or directory >mv: cannot stat `uImage': No such file or directory >mv: cannot stat `sakoman-gnome-image.tar.bz2': No such file or >directory Downloading files from >http://feeds.sakoman.com/feeds/gnome-r12/images/overo/current >--2012-05-07 22:27:03-- >http://feeds.sakoman.com/feeds/gnome-r12/images/overo/current/MLO >Resolving feeds.sakoman.com... 209.139.209.168 Connecting to >feeds.sakoman.com|209.139.209.168|:80... connected. >HTTP request sent, awaiting response... 302 Found >Location: /feeds/gnome-r12/images/overo/current/MLO [following] >--2012-05-07 22:27:05-- >http://feeds.sakoman.com/feeds/gnome-r12/images/overo/current/MLO >Connecting to feeds.sakoman.com|209.139.209.168|:80... connected. >HTTP request sent, awaiting response... 200 OK >Length: 24288 (24K) [text/plain] >Saving to: `MLO' > >100%[======================================>] 24,288 >91.3K/s in 0.3s > >2012-05-07 22:27:05 (91.3 KB/s) - `MLO' saved [24288/24288] > >--2012-05-07 22:27:05-- >http://feeds.sakoman.com/feeds/gnome-r12/images/overo/current/u >-boot.bin >Resolving feeds.sakoman.com... 209.139.209.168 Connecting to >feeds.sakoman.com|209.139.209.168|:80... connected. >HTTP request sent, awaiting response... 200 OK >Length: 235248 (230K) [application/octet-stream] Saving to: >`u-boot.bin' > >100%[======================================>] 235,248 >176K/s in 1.3s > >2012-05-07 22:27:07 (176 KB/s) - `u-boot.bin' saved [235248/235248] > >--2012-05-07 22:27:07-- >http://feeds.sakoman.com/feeds/gnome-r12/images/omap3-multi/cur >rent/uImage >Resolving feeds.sakoman.com... 209.139.209.168 Connecting to >feeds.sakoman.com|209.139.209.168|:80... connected. >HTTP request sent, awaiting response... 200 OK >Length: 2908444 (2.8M) [text/plain] >Saving to: `uImage' > >100%[======================================>] 2,908,444 >56.9K/s in 37s > >2012-05-07 22:27:44 (76.8 KB/s) - `uImage' saved [2908444/2908444] > >--2012-05-07 22:27:44-- >http://feeds.sakoman.com/feeds/gnome-r12/images/omap3-multi/cur >rent/sakoman-gnome-image.tar.bz2 >Resolving feeds.sakoman.com... 209.139.209.168 Connecting to >feeds.sakoman.com|209.139.209.168|:80... connected. >HTTP request sent, awaiting response... 200 OK >Length: 330954537 (316M) [application/x-bzip2] Saving to: >`sakoman-gnome-image.tar.bz2' > >100%[======================================>] 330,954,537 >271K/s in 40m >21s > >2012-05-07 23:08:05 (134 KB/s) - `sakoman-gnome-image.tar.bz2' >saved [330954537/330954537] > >mkdir: cannot create directory `/media/sakoman-sd': No such >file or directory Could not create mount point: >/media/sakoman-sd SD card creation was not successful sh-4.1# > >You guys should be warned, I am a living testament to Murphy's Law. > >Strange glitches I noticed when using script (Maybe these are >know, or my >fault): >It repeatedly wouldn't work untill I formatted the whole uSD >to FAT32 Despite my drive being shown as ../mnt/sdc that would >fail, so I did dev/sdc which finally worked. Actually it was >sdb1 The first attempts it failed because it filled my >personal storage file in Puppy Linux. I had to expand my >personal save space. > >Thanks for the help so far! > >-- >View this message in context: >http://gumstix.8.n6.nabble.com/Fails-to-boot-after-opkg-update- >upgrade-tp4939860p4961709.html >Sent from the Gumstix mailing list archive at Nabble.com. > >--------------------------------------------------------------- >--------------- >Live Security Virtual Conference >Exclusive live event will cover all the ways today's security >and threat landscape has changed and how IT managers can >respond. Discussions will include endpoint security, mobile >security and the latest in malware threats. >http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >_______________________________________________ >gumstix-users mailing list >gum...@li... >https://lists.sourceforge.net/lists/listinfo/gumstix-users > >______________________________________________________________________ >CAUTION: This message was sent via the Public Internet and its >authenticity cannot be guaranteed. > PROPRIETARY: This e-mail contains proprietary information some or all of which may be legally privileged. It is intended for the recipient only. If an addressing or transmission error has misdirected this e-mail, please notify the authority by replying to this e-mail. If you are not the intended recipient you must not use, disclose, distribute, copy, print, or rely on this e-mail. |
From: Keane, B. (STRX) <ben...@ka...> - 2012-05-09 04:48:55
|
Hi, Has anyone used the initcall_debug cmdline kernel parameter successfully? When I add it to my boot parameters it seems to cause no output on the console. Ben PROPRIETARY: This e-mail contains proprietary information some or all of which may be legally privileged. It is intended for the recipient only. If an addressing or transmission error has misdirected this e-mail, please notify the authority by replying to this e-mail. If you are not the intended recipient you must not use, disclose, distribute, copy, print, or rely on this e-mail. |
From: Keane, B. (STRX) <ben...@ka...> - 2012-05-09 06:26:33
|
Hi, Has anyone debugged the kernel via gdb on their overo system? If so, do you have some pointers about how to set that up? Thanks, Ben PROPRIETARY: This e-mail contains proprietary information some or all of which may be legally privileged. It is intended for the recipient only. If an addressing or transmission error has misdirected this e-mail, please notify the authority by replying to this e-mail. If you are not the intended recipient you must not use, disclose, distribute, copy, print, or rely on this e-mail. |
From: rough_wood <rou...@ya...> - 2012-05-15 02:14:37
|
I tried Sakoman's script again with what seems to be the correct command and it still fails. Is there some other way I should try this? Or another well proven method to reinstall the Overo's OS? I really need to get this thing working. Again, I am using Puppy Linux. Sudo command doesn't exist. I think it automatically logs me in as root or something. Can I just do something to the SD card? Such as add whatever directory it wanted etc? Cause I haven't touched that card after I ran the script. Thanks for the help so far. Console stuff attached below. sh-4.1# sudo sh: sudo: command not found sh-4.1# cd sh-4.1# ./mksdcard.sh /dev/sdb umount: can't umount /dev/sdb1: Invalid argument umount: can't umount /dev/sdb2: Invalid argument 1024+0 records in 1024+0 records out 1048576 bytes (1.0 MB) copied, 0.310382 s, 3.4 MB/s Disk /dev/sdb doesn't contain a valid partition table DISK SIZE â 7948206080 bytes CYLINDERS â 966 ./mksdcard.sh: line 113: sfdisk: command not found umount: can't umount /dev/sdb1: Invalid argument mkfs.vfat 3.0.7 (24 Dec 2009) umount: can't umount /dev/sdb2: Invalid argument mke2fs 1.41.14 (22-Dec-2010) mke2fs: No such device or address while trying to determine filesystem size Backing up previously downloaded files (if any) Downloading files from http://feeds.sakoman.com/feeds/gnome-r12/images/overo/current --2012-05-14 21:47:07-- http://feeds.sakoman.com/feeds/gnome-r12/images/overo/current/MLO Resolving feeds.sakoman.com... 209.139.209.168 Connecting to feeds.sakoman.com|209.139.209.168|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 24288 (24K) [text/plain] Saving to: `MLO' 100%[======================================>] 24,288 84.7K/s in 0.3s 2012-05-14 21:47:08 (84.7 KB/s) - `MLO' saved [24288/24288] --2012-05-14 21:47:08-- http://feeds.sakoman.com/feeds/gnome-r12/images/overo/current/u-boot.bin Resolving feeds.sakoman.com... 209.139.209.168 Connecting to feeds.sakoman.com|209.139.209.168|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 235248 (230K) [application/octet-stream] Saving to: `u-boot.bin' 100%[======================================>] 235,248 244K/s in 0.9s 2012-05-14 21:47:10 (244 KB/s) - `u-boot.bin' saved [235248/235248] --2012-05-14 21:47:10-- http://feeds.sakoman.com/feeds/gnome-r12/images/omap3-multi/current/uImage Resolving feeds.sakoman.com... 209.139.209.168 Connecting to feeds.sakoman.com|209.139.209.168|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 2908444 (2.8M) [text/plain] Saving to: `uImage' 100%[======================================>] 2,908,444 409K/s in 7.6s 2012-05-14 21:47:18 (375 KB/s) - `uImage' saved [2908444/2908444] --2012-05-14 21:47:18-- http://feeds.sakoman.com/feeds/gnome-r12/images/omap3-multi/current/sakoman-gnome-image.tar.bz2 Resolving feeds.sakoman.com... 209.139.209.168 Connecting to feeds.sakoman.com|209.139.209.168|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 330954537 (316M) [application/x-bzip2] Saving to: `sakoman-gnome-image.tar.bz2' 100%[======================================>] 330,954,537 525K/s in 13m 37s 2012-05-14 22:00:56 (395 KB/s) - `sakoman-gnome-image.tar.bz2' saved [330954537/330954537] mkdir: cannot create directory `/media/sakoman-sd': No such file or directory Could not create mount point: /media/sakoman-sd SD card creation was not successful sh-4.1# -- View this message in context: http://gumstix.8.n6.nabble.com/Fails-to-boot-after-opkg-update-upgrade-tp4939860p4964313.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Keane, B. (STRX) <ben...@ka...> - 2012-05-15 03:47:35
|
>From the log it looks like your linux distro - Puppy Linux doesn't have sfdisk ... Or you aren't logged in as root and therefore /sbin isn't in your PATH. Type 'whoami' to find out which user you are logged in as. If you aren't logged in as root, work out how to. If you are root, type 'echo $PATH' and check if /sbin is in the list. Also check if you have sfdisk somewhere on your machine with 'find / -name sfdisk' ... I would assume Puppy Linux has some sort of package management system .. Try and install sfdisk and then re-run the script as root. >-----Original Message----- >From: rough_wood [mailto:rou...@ya...] >Sent: Tuesday, 15 May 2012 12:15 PM >To: gum...@li... >Subject: Re: [Gumstix-users] Fails to boot after opkg update > upgrade > >I tried Sakoman's script again with what seems to be the >correct command and it still fails. > >Is there some other way I should try this? Or another well >proven method to reinstall the Overo's OS? I really need to >get this thing working. > >Again, I am using Puppy Linux. Sudo command doesn't exist. I >think it automatically logs me in as root or something. Can I >just do something to the SD card? Such as add whatever >directory it wanted etc? Cause I haven't touched that card >after I ran the script. Thanks for the help so far. >Console stuff attached below. > >sh-4.1# sudo >sh: sudo: command not found >sh-4.1# cd >sh-4.1# ./mksdcard.sh /dev/sdb >umount: can't umount /dev/sdb1: Invalid argument >umount: can't umount /dev/sdb2: Invalid argument >1024+0 records in >1024+0 records out >1048576 bytes (1.0 MB) copied, 0.310382 s, 3.4 MB/s Disk >/dev/sdb doesn't contain a valid partition table DISK SIZE â >7948206080 bytes CYLINDERS â 966 >./mksdcard.sh: line 113: sfdisk: command not found >umount: can't umount /dev/sdb1: Invalid argument mkfs.vfat >3.0.7 (24 Dec 2009) >umount: can't umount /dev/sdb2: Invalid argument mke2fs >1.41.14 (22-Dec-2010) >mke2fs: No such device or address while trying to determine >filesystem size Backing up previously downloaded files (if >any) Downloading files from >http://feeds.sakoman.com/feeds/gnome-r12/images/overo/current >--2012-05-14 21:47:07-- >http://feeds.sakoman.com/feeds/gnome-r12/images/overo/current/MLO >Resolving feeds.sakoman.com... 209.139.209.168 Connecting to >feeds.sakoman.com|209.139.209.168|:80... connected. >HTTP request sent, awaiting response... 200 OK >Length: 24288 (24K) [text/plain] >Saving to: `MLO' > >100%[======================================>] 24,288 >84.7K/s in 0.3s > >2012-05-14 21:47:08 (84.7 KB/s) - `MLO' saved [24288/24288] > >--2012-05-14 21:47:08-- >http://feeds.sakoman.com/feeds/gnome-r12/images/overo/current/u >-boot.bin >Resolving feeds.sakoman.com... 209.139.209.168 Connecting to >feeds.sakoman.com|209.139.209.168|:80... connected. >HTTP request sent, awaiting response... 200 OK >Length: 235248 (230K) [application/octet-stream] Saving to: >`u-boot.bin' > >100%[======================================>] 235,248 >244K/s in 0.9s > >2012-05-14 21:47:10 (244 KB/s) - `u-boot.bin' saved [235248/235248] > >--2012-05-14 21:47:10-- >http://feeds.sakoman.com/feeds/gnome-r12/images/omap3-multi/cur >rent/uImage >Resolving feeds.sakoman.com... 209.139.209.168 Connecting to >feeds.sakoman.com|209.139.209.168|:80... connected. >HTTP request sent, awaiting response... 200 OK >Length: 2908444 (2.8M) [text/plain] >Saving to: `uImage' > >100%[======================================>] 2,908,444 >409K/s in 7.6s > >2012-05-14 21:47:18 (375 KB/s) - `uImage' saved [2908444/2908444] > >--2012-05-14 21:47:18-- >http://feeds.sakoman.com/feeds/gnome-r12/images/omap3-multi/cur >rent/sakoman-gnome-image.tar.bz2 >Resolving feeds.sakoman.com... 209.139.209.168 Connecting to >feeds.sakoman.com|209.139.209.168|:80... connected. >HTTP request sent, awaiting response... 200 OK >Length: 330954537 (316M) [application/x-bzip2] Saving to: >`sakoman-gnome-image.tar.bz2' > >100%[======================================>] 330,954,537 >525K/s in 13m >37s > >2012-05-14 22:00:56 (395 KB/s) - `sakoman-gnome-image.tar.bz2' >saved [330954537/330954537] > >mkdir: cannot create directory `/media/sakoman-sd': No such >file or directory Could not create mount point: >/media/sakoman-sd SD card creation was not successful sh-4.1# > > >-- >View this message in context: >http://gumstix.8.n6.nabble.com/Fails-to-boot-after-opkg-update- >upgrade-tp4939860p4964313.html >Sent from the Gumstix mailing list archive at Nabble.com. > >--------------------------------------------------------------- >--------------- >Live Security Virtual Conference >Exclusive live event will cover all the ways today's security >and threat landscape has changed and how IT managers can >respond. Discussions will include endpoint security, mobile >security and the latest in malware threats. >http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >_______________________________________________ >gumstix-users mailing list >gum...@li... >https://lists.sourceforge.net/lists/listinfo/gumstix-users > >______________________________________________________________________ >CAUTION: This message was sent via the Public Internet and its >authenticity cannot be guaranteed. > PROPRIETARY: This e-mail contains proprietary information some or all of which may be legally privileged. It is intended for the recipient only. If an addressing or transmission error has misdirected this e-mail, please notify the authority by replying to this e-mail. If you are not the intended recipient you must not use, disclose, distribute, copy, print, or rely on this e-mail. |
From: rough_wood <rou...@ya...> - 2012-05-18 20:05:57
|
Installed sfdisk Also, despite already having files it downloaded them again,fyi. sh-4.1# ./mksdcard.sh /dev/sdb umount: can't umount /dev/sdb1: Invalid argument umount: can't umount /dev/sdb2: Invalid argument 1024+0 records in 1024+0 records out 1048576 bytes (1.0 MB) copied, 0.315459 s, 3.3 MB/s Disk /dev/sdb doesn't contain a valid partition table DISK SIZE â 7948206080 bytes CYLINDERS â 966 Checking that no-one is using this disk right now ... OK Warning: HDIO_GETGEO says that there are 245 heads Warning: HDIO_GETGEO says that there are 62 sectors Warning: BLKGETSIZE/HDIO_GETGEO says that there are 1021 cylinders Disk /dev/sdb: 966 cylinders, 255 heads, 63 sectors/track sfdisk: ERROR: sector 0 does not have an msdos signature /dev/sdb: unrecognized partition Old situation: No partitions found New situation: Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls #blocks Id System /dev/sdb1 * 0+ 8 9- 72261 c W95 FAT32 (LBA) /dev/sdb2 9 965 957 7687102+ 83 Linux /dev/sdb3 0 - 0 0 0 Empty /dev/sdb4 0 - 0 0 0 Empty Successfully wrote the new partition table Re-reading the partition table ... If you created or changed a DOS partition, /dev/foo7, say, then use dd(1) to zero the first 512 bytes: dd if=/dev/zero of=/dev/foo7 bs=512 count=1 (See fdisk(8).) umount: can't umount /dev/sdb1: Invalid argument mkfs.vfat 3.0.7 (24 Dec 2009) umount: can't umount /dev/sdb2: Invalid argument mke2fs 1.41.14 (22-Dec-2010) Filesystem label=rootfs OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) Stride=0 blocks, Stripe width=0 blocks 480496 inodes, 1921775 blocks 96088 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=1971322880 59 block groups 32768 blocks per group, 32768 fragments per group 8144 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632 Writing inode tables: done Creating journal (32768 blocks): done Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 32 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. Backing up previously downloaded files (if any) Downloading files from http://feeds.sakoman.com/feeds/gnome-r12/images/overo/current --2012-05-18 15:41:36-- http://feeds.sakoman.com/feeds/gnome-r12/images/overo/current/MLO Resolving feeds.sakoman.com... 209.139.209.168 Connecting to feeds.sakoman.com|209.139.209.168|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 24288 (24K) [text/plain] Saving to: `MLO' 100%[======================================>] 24,288 85.9K/s in 0.3s 2012-05-18 15:41:37 (85.9 KB/s) - `MLO' saved [24288/24288] --2012-05-18 15:41:37-- http://feeds.sakoman.com/feeds/gnome-r12/images/overo/current/u-boot.bin Resolving feeds.sakoman.com... 209.139.209.168 Connecting to feeds.sakoman.com|209.139.209.168|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 235248 (230K) [application/octet-stream] Saving to: `u-boot.bin' 100%[======================================>] 235,248 255K/s in 0.9s 2012-05-18 15:41:38 (255 KB/s) - `u-boot.bin' saved [235248/235248] --2012-05-18 15:41:38-- http://feeds.sakoman.com/feeds/gnome-r12/images/omap3-multi/current/uImage Resolving feeds.sakoman.com... 209.139.209.168 Connecting to feeds.sakoman.com|209.139.209.168|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 2908444 (2.8M) [text/plain] Saving to: `uImage' 100%[======================================>] 2,908,444 535K/s in 6.3s 2012-05-18 15:41:45 (453 KB/s) - `uImage' saved [2908444/2908444] --2012-05-18 15:41:45-- http://feeds.sakoman.com/feeds/gnome-r12/images/omap3-multi/current/sakoman-gnome-image.tar.bz2 Resolving feeds.sakoman.com... 209.139.209.168 Connecting to feeds.sakoman.com|209.139.209.168|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 330954537 (316M) [application/x-bzip2] Saving to: `sakoman-gnome-image.tar.bz2' 100%[======================================>] 330,954,537 483K/s in 9m 58s 2012-05-18 15:51:43 (541 KB/s) - `sakoman-gnome-image.tar.bz2' saved [330954537/330954537] mkdir: cannot create directory `/media/sakoman-sd': No such file or directory Could not create mount point: /media/sakoman-sd SD card creation was not successful sh-4.1# -- View this message in context: http://gumstix.8.n6.nabble.com/Fails-to-boot-after-opkg-update-upgrade-tp4939860p4964360.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: rough_wood <rou...@ya...> - 2012-05-26 15:29:33
|
After trying several more times, it is still failing. Is this a known problem with the Sakoman script? -- View this message in context: http://gumstix.8.n6.nabble.com/Fails-to-boot-after-opkg-update-upgrade-tp4939860p4964436.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: rough_wood <rou...@ya...> - 2012-05-29 02:58:09
|
I bought an extra hard drive for my laptop and installed Ubuntu 12.04 LTS on it. Running the script this time said it was successful. However, when putting the sd card into the Overo, it shows a random value such as @ and does nothing. The red light by the Ethernet flashes red, which in my experience so far indicates an error. What do I do to get the bootable sd to boot? I have tried powering on without it also, for example. Then I interrupt boot, and when attempting to boot from the SD it hands up when unzipping the kernel. I also have another question I am having trouble with. In Ubuntu 12.04 LTS, I am trying to get a Serial connection to the Overo, so I don't have to constantly power off and swap hard drives in my laptop. When plugging a USB cord from the console port of the Overo to my laptop, I don't seem to be finding new devices. I try to connect to /dev/ttyS0 and /dev/ttyUSB0 in putty, SSH, and Kermit and all fail. I run tty command and it says /dev/pts/0 More than likely I am doing something wrong with each method I've used to try to fix this darn thing. I am very inexperienced in Linux, and couple that with an Overo that won't even boot, instructions that use Buildroot and wrong addresses etc, and it is making for a very difficult time. Thanks for the help so far! -- View this message in context: http://gumstix.8.n6.nabble.com/Fails-to-boot-after-opkg-update-upgrade-tp4939860p4964457.html Sent from the Gumstix mailing list archive at Nabble.com. |