Page 1 of 2
Meteohub no longer responding after network change
Posted: Mon Sep 21, 2009 2:28 pm
by tchazzard
Hello All;
My Meteohub has been working flawlessly for over the past 13 months. I just moved from a cable modem connection to a DSL connection. The router and wireless access point remained the same. So only the actual modem was swapped out.
The Meteohub makes all the same familiar beeps when booting up and I can see it listed at the same IP address as in the past. This said, I cannot log into the Meteohub web interface and none of my weather data is making it up to Wunderground or the other sites I had it configured for.
Any thoughts on how to troubleshoot or what might be wrong?
Thank you.
Re:Meteohub no longer responding after network change
Posted: Mon Sep 21, 2009 7:19 pm
by admin
can you login via ssh? putty for example. user root, pw meteohub.
What does "dmesg" and "df" reply?
Re:Meteohub no longer responding after network change
Posted: Mon Sep 21, 2009 7:27 pm
by tchazzard
I will try this when I get home and post the output here.
Re:Meteohub no longer responding after network change
Posted: Mon Sep 21, 2009 11:48 pm
by tchazzard
Here you go:
root@meteohub:~$ dmesg
<5>Linux version 2.6.21.7 (slug@otto) (gcc version 4.1.2) #1 PREEMPT Mon Dec 24 23:12:24 UTC 2007
<4>CPU: XScale-IXP42x Family [690541f1] revision 1 (ARMv5TE), cr=000039ff
<4>Machine: Linksys NSLU2
<4>Memory policy: ECC disabled, Data cache writeback
<7>On node 0 totalpages: 8192
<7> DMA zone: 64 pages used for memmap
<7> DMA zone: 0 pages reserved
<7> DMA zone: 8128 pages, LIFO batch:0
<7> Normal zone: 0 pages used for memmap
<4>CPU0: D VIVT undefined 5 cache
<4>CPU0: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets
<4>CPU0: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets
<4>Built 1 zonelists. Total pages: 8128
<5>Kernel command line: rtc-x1205.probe=0,0x6f console=ttyS0,115200n8 root=/dev/mtdblock4 rootfstype=jffs2 rw init=/linuxrc noirqdebug
<6>IRQ lockup detection disabled
<4>PID hash table entries: 128 (order: 7, 512 bytes)
<4>Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
<4>Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
<6>Memory: 32MB = 32MB total
<5>Memory: 30292KB available (1912K code, 153K data, 84K init)
<7>Calibrating delay loop... 132.71 BogoMIPS (lpj=663552)
<4>Mount-cache hash table entries: 512
<6>CPU: Testing write buffer coherency: ok
<6>NET: Registered protocol family 16
<4>IXP4xx: Using 16MiB expansion bus window size
<4>PCI: IXP4xx is host
<4>PCI: IXP4xx Using direct access for memory space
<6>PCI: bus0: Fast back to back transfers disabled
<6>dmabounce: registered device 0000:00:01.0 on pci bus
<6>dmabounce: registered device 0000:00:01.1 on pci bus
<6>dmabounce: registered device 0000:00:01.2 on pci bus
<5>SCSI subsystem initialized
<6>usbcore: registered new interface driver usbfs
<6>usbcore: registered new interface driver hub
<6>usbcore: registered new device driver usb
<6>Time: OSTS clocksource has been installed.
<6>NET: Registered protocol family 2
<4>IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
<4>TCP established hash table entries: 1024 (order: 1, 8192 bytes)
<4>TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
<6>TCP: Hash tables configured (established 1024 bind 1024)
<6>TCP reno registered
<4>NetWinder Floating Point Emulator V0.97 (double precision)
<6>JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc.
<6>io scheduler noop registered
<6>io scheduler deadline registered (default)
<6>Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled
<6>serial8250.0: ttyS0 at MMIO 0xc8000000 (irq = 15) is a XScale
<6>serial8250.0: ttyS1 at MMIO 0xc8001000 (irq = 13) is a XScale
<4>RAMDISK driver initialized: 4 RAM disks of 10240K size 1024 blocksize
<6>IXP4XX NPE driver Version 0.3.0 initialized
<6>NFTL driver: nftlcore.c $Revision: 1.98 $, nftlmount.c $Revision: 1.41 $
<6>IXP4XX-Flash.0: Found 1 x16 devices at 0x0 in 16-bit bank
<7>IXP4XX-Flash.0: Found an alias at 0x800000 for the chip at 0x0
<4> Intel/Sharp Extended Query Table at 0x0031
<6>Using buffer write method
<5>cfi_cmdset_0001: Erase suspend on write enabled
<7>erase region 0: offset=0x0,size=0x20000,blocks=64
<5>Searching for RedBoot partition table in IXP4XX-Flash.0 at offset 0x7e0000
<5>6 RedBoot partitions found on MTD device IXP4XX-Flash.0
<5>Creating 6 MTD partitions on "IXP4XX-Flash.0":
<5>0x00000000-0x00040000 : "RedBoot"
<6>nslu2 mac: 00:0f:66:7e:fa:46
<5>0x00040000-0x00060000 : "SysConf"
<5>0x00060000-0x00080000 : "Loader"
<5>0x00080000-0x00180000 : "Kernel"
<5>0x00180000-0x007e0000 : "Flashdisk"
<5>0x007e0000-0x00800000 : "FIS directory"
<4>npe: searching for firmware...
<6>npe: found at 0x1c010, IXP425/NPE-B func: 00, rev: 2.1, size: 11964, id: 01000201
<6>Image loaded to NPE-B Func:0, Rel: 2:1, Status: 82c00000
<6>Initializing USB Mass Storage driver...
<6>usbcore: registered new interface driver usb-storage
<6>USB Mass Storage support registered.
<6>input: ixp4xx beeper as /class/input/input0
<6>i2c /dev entries driver
<6>x1205 0-006f: chip found, driver version 1.0.7
<6>x1205 0-006f: rtc core: registered x1205 as rtc0
<6>Registered led device: ready
<6>Registered led device: status
<6>Registered led device: disk-1
<6>Registered led device: disk-2
<6>TCP cubic registered
<6>NET: Registered protocol family 1
<6>NET: Registered protocol family 17
<6>XScale DSP coprocessor detected.
<6>x1205 0-006f: setting the system clock to 2009-09-21 08:17:00 (1253521020)
<4>VFS: Mounted root (jffs2 filesystem).
<6>Freeing init memory: 84K
<4>PCI: enabling device 0000:00:01.2 (0140 -> 0142)
<6>ehci_hcd 0000:00:01.2: EHCI Host Controller
<6>ehci_hcd 0000:00:01.2: new USB bus registered, assigned bus number 1
<6>ehci_hcd 0000:00:01.2: irq 26, io mem 0x48002000
<6>ehci_hcd 0000:00:01.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
<6>usb usb1: configuration #1 chosen from 1 choice
<6>hub 1-0:1.0: USB hub found
<6>hub 1-0:1.0: 5 ports detected
<7>ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
<4>PCI: enabling device 0000:00:01.0 (0140 -> 0142)
<6>ohci_hcd 0000:00:01.0: OHCI Host Controller
<6>ohci_hcd 0000:00:01.0: new USB bus registered, assigned bus number 2
<6>ohci_hcd 0000:00:01.0: irq 28, io mem 0x48000000
<6>usb usb2: configuration #1 chosen from 1 choice
<6>hub 2-0:1.0: USB hub found
<6>hub 2-0:1.0: 3 ports detected
<4>PCI: enabling device 0000:00:01.1 (0140 -> 0142)
<6>ohci_hcd 0000:00:01.1: OHCI Host Controller
<6>ohci_hcd 0000:00:01.1: new USB bus registered, assigned bus number 3
<6>ohci_hcd 0000:00:01.1: irq 27, io mem 0x48001000
<6>usb usb3: configuration #1 chosen from 1 choice
<6>hub 3-0:1.0: USB hub found
<6>hub 3-0:1.0: 2 ports detected
<6>usb 1-2: new high speed USB device using ehci_hcd and address 3
<6>usb 1-2: configuration #1 chosen from 1 choice
<6>scsi0 : SCSI emulation for USB Mass Storage devices
<7>usb-storage: device found at 3
<7>usb-storage: waiting for device to settle before scanning
<6>usb 2-1: new full speed USB device using ohci_hcd and address 2
<6>usb 2-1: configuration #1 chosen from 1 choice
<5>scsi 0:0:0:0: Direct-Access Kingmax USB2.0 FlashDisk 0.00 PQ: 0 ANSI: 2
<5>SCSI device sda: 3948543 512-byte hdwr sectors (2022 MB)
<5>sda: Write Protect is off
<7>sda: Mode Sense: 00 00 00 00
<3>sda: assuming drive cache: write through
<5>SCSI device sda: 3948543 512-byte hdwr sectors (2022 MB)
<5>sda: Write Protect is off
<7>sda: Mode Sense: 00 00 00 00
<3>sda: assuming drive cache: write through
<6> sda: sda1 sda2 sda3
<5>sd 0:0:0:0: Attached scsi removable disk sda
<7>usb-storage: device scan complete
<6>kjournald starting. Commit interval 5 seconds
<4>EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
<6>EXT3 FS on sda1, internal journal
<6>EXT3-fs: recovery complete.
<6>EXT3-fs: mounted filesystem with ordered data mode.
<6>IXP4XX Q Manager 0.2.1 initialized.
<6>ixp4xx_mac driver 0.3.1: eth0 on NPE-B with PHY[1] initialized
<6>usbcore: registered new interface driver usbserial
<6>drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
<6>usbcore: registered new interface driver usbserial_generic
<6>drivers/usb/serial/usb-serial.c: USB Serial Driver core
<6>drivers/usb/serial/usb-serial.c: USB Serial support registered for pl2303
<6>pl2303 2-1:1.0: pl2303 converter detected
<6>usb 2-1: pl2303 converter now attached to ttyUSB0
<6>usbcore: registered new interface driver pl2303
<6>drivers/usb/serial/pl2303.c: Prolific PL2303 USB to serial adaptor driver
<2>EXT3-fs error (device sda3): ext3_check_descriptors: Block bitmap for group 0 not in group (block 73845)!
<3>EXT3-fs: group descriptors corrupted!
<2>EXT3-fs error (device sda3): ext3_check_descriptors: Block bitmap for group 0 not in group (block 73845)!
<3>EXT3-fs: group descriptors corrupted!
<6>Adding 131064k swap on /dev/sda2. Priority:-1 extents:1 across:131064k
<2>EXT3-fs error (device sda3): ext3_check_descriptors: Block bitmap for group 0 not in group (block 73845)!
<3>EXT3-fs: group descriptors corrupted!
<6>eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
<7>Link of eth0 is full-duplex
<4>IXP4xx Watchdog Timer: heartbeat 60 sec
<6>drivers/usb/serial/usb-serial.c: USB Serial support registered for cp2101
<6>usbcore: registered new interface driver cp2101
<6>drivers/usb/serial/cp2101.c: Silicon Labs CP2101/CP2102 RS232 serial adaptor driver v0.07
<6>drivers/usb/serial/usb-serial.c: USB Serial support registered for FTDI USB Serial Device
<6>usbcore: registered new interface driver ftdi_sio
<6>drivers/usb/serial/ftdi_sio.c: v1.4.3:USB FTDI Serial Converters Driver
root@meteohub:~$ df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/sda1 412524 213379 177847 55% /
/dev/mtdblock4 6528 5536 992 85% /initrd
/dev/sda1 412524 213379 177847 55% /dev/.static/dev
tmpfs 2048 32 2016 2% /dev
tmpfs 15188 392 14796 3% /var/volatile
tmpfs 15188 0 15188 0% /dev/shm
Re:Meteohub no longer responding after network change
Posted: Tue Sep 22, 2009 12:06 am
by admin
Your USB stick is broken. Data partition "/dev/sda3" cannot be mounted during boot:
EXT3-fs error (device sda3): ext3_check_descriptors: Block bitmap for group 0 not in group (block 73845)!
EXT3-fs: group descriptors corrupted!
EXT3-fs error (device sda3): ext3_check_descriptors: Block bitmap for group 0 not in group (block 73845)!
EXT3-fs: group descriptors corrupted!
Adding 131064k swap on /dev/sda2. Priority:-1 extents:1 across:131064k
EXT3-fs error (device sda3): ext3_check_descriptors: Block bitmap for group 0 not in group (block 73845)!
EXT3-fs: group descriptors corrupted!
You will need to setup a new USB stick.
Re:Meteohub no longer responding after network change
Posted: Tue Sep 22, 2009 1:54 am
by tchazzard
I am not Linux hack. Are there easy instructions on how to build a new image on a USB stick (will any USB memory stick work)?
Thank you
Re:Meteohub no longer responding after network change
Posted: Tue Sep 22, 2009 7:11 pm
by admin
Re:Meteohub no longer responding after network change
Posted: Wed Sep 23, 2009 2:57 am
by tchazzard
OK. Built 2Gb image on 4Gb USB drive (4GB did not quite fit). Can log in via ssh, but still not accessible via web browser. I need to change IP to 192.168.2.x network. No setip found. Any thoughts?
Output dmesg:
dmesg
<5>Linux version 2.6.21.7 (slug@otto) (gcc version 4.1.2) #1 PREEMPT Mon Dec 24 23:12:24 UTC 2007
<4>CPU: XScale-IXP42x Family [690541f1] revision 1 (ARMv5TE), cr=000039ff
<4>Machine: Linksys NSLU2
<4>Memory policy: ECC disabled, Data cache writeback
<7>On node 0 totalpages: 8192
<7> DMA zone: 64 pages used for memmap
<7> DMA zone: 0 pages reserved
<7> DMA zone: 8128 pages, LIFO batch:0
<7> Normal zone: 0 pages used for memmap
<4>CPU0: D VIVT undefined 5 cache
<4>CPU0: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets
<4>CPU0: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets
<4>Built 1 zonelists. Total pages: 8128
<5>Kernel command line: rtc-x1205.probe=0,0x6f console=ttyS0,115200n8 root=/dev/mtdblock4 rootfstype=jffs2 rw init=/linuxrc noirqdebug
<6>IRQ lockup detection disabled
<4>PID hash table entries: 128 (order: 7, 512 bytes)
<4>Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
<4>Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
<6>Memory: 32MB = 32MB total
<5>Memory: 30292KB available (1912K code, 153K data, 84K init)
<7>Calibrating delay loop... 132.71 BogoMIPS (lpj=663552)
<4>Mount-cache hash table entries: 512
<6>CPU: Testing write buffer coherency: ok
<6>NET: Registered protocol family 16
<4>IXP4xx: Using 16MiB expansion bus window size
<4>PCI: IXP4xx is host
<4>PCI: IXP4xx Using direct access for memory space
<6>PCI: bus0: Fast back to back transfers disabled
<6>dmabounce: registered device 0000:00:01.0 on pci bus
<6>dmabounce: registered device 0000:00:01.1 on pci bus
<6>dmabounce: registered device 0000:00:01.2 on pci bus
<5>SCSI subsystem initialized
<6>usbcore: registered new interface driver usbfs
<6>usbcore: registered new interface driver hub
<6>usbcore: registered new device driver usb
<6>Time: OSTS clocksource has been installed.
<6>NET: Registered protocol family 2
<4>IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
<4>TCP established hash table entries: 1024 (order: 1, 8192 bytes)
<4>TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
<6>TCP: Hash tables configured (established 1024 bind 1024)
<6>TCP reno registered
<4>NetWinder Floating Point Emulator V0.97 (double precision)
<6>JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc.
<6>io scheduler noop registered
<6>io scheduler deadline registered (default)
<6>Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled
<6>serial8250.0: ttyS0 at MMIO 0xc8000000 (irq = 15) is a XScale
<6>serial8250.0: ttyS1 at MMIO 0xc8001000 (irq = 13) is a XScale
<4>RAMDISK driver initialized: 4 RAM disks of 10240K size 1024 blocksize
<6>IXP4XX NPE driver Version 0.3.0 initialized
<6>NFTL driver: nftlcore.c $Revision: 1.98 $, nftlmount.c $Revision: 1.41 $
<6>IXP4XX-Flash.0: Found 1 x16 devices at 0x0 in 16-bit bank
<7>IXP4XX-Flash.0: Found an alias at 0x800000 for the chip at 0x0
<4> Intel/Sharp Extended Query Table at 0x0031
<6>Using buffer write method
<5>cfi_cmdset_0001: Erase suspend on write enabled
<7>erase region 0: offset=0x0,size=0x20000,blocks=64
<5>Searching for RedBoot partition table in IXP4XX-Flash.0 at offset 0x7e0000
<5>6 RedBoot partitions found on MTD device IXP4XX-Flash.0
<5>Creating 6 MTD partitions on "IXP4XX-Flash.0":
<5>0x00000000-0x00040000 : "RedBoot"
<6>nslu2 mac: 00:0f:66:7e:fa:46
<5>0x00040000-0x00060000 : "SysConf"
<5>0x00060000-0x00080000 : "Loader"
<5>0x00080000-0x00180000 : "Kernel"
<5>0x00180000-0x007e0000 : "Flashdisk"
<5>0x007e0000-0x00800000 : "FIS directory"
<4>npe: searching for firmware...
<6>npe: found at 0x1c010, IXP425/NPE-B func: 00, rev: 2.1, size: 11964, id: 01000201
<6>Image loaded to NPE-B Func:0, Rel: 2:1, Status: 82c00000
<6>Initializing USB Mass Storage driver...
<6>usbcore: registered new interface driver usb-storage
<6>USB Mass Storage support registered.
<6>input: ixp4xx beeper as /class/input/input0
<6>i2c /dev entries driver
<6>x1205 0-006f: chip found, driver version 1.0.7
<6>x1205 0-006f: rtc core: registered x1205 as rtc0
<6>Registered led device: ready
<6>Registered led device: status
<6>Registered led device: disk-1
<6>Registered led device: disk-2
<6>TCP cubic registered
<6>NET: Registered protocol family 1
<6>NET: Registered protocol family 17
<6>XScale DSP coprocessor detected.
<6>x1205 0-006f: setting the system clock to 2009-09-22 20:45:04 (1253652304)
<4>VFS: Mounted root (jffs2 filesystem).
<6>Freeing init memory: 84K
<4>PCI: enabling device 0000:00:01.2 (0140 -> 0142)
<6>ehci_hcd 0000:00:01.2: EHCI Host Controller
<6>ehci_hcd 0000:00:01.2: new USB bus registered, assigned bus number 1
<6>ehci_hcd 0000:00:01.2: irq 26, io mem 0x48002000
<6>ehci_hcd 0000:00:01.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
<6>usb usb1: configuration #1 chosen from 1 choice
<6>hub 1-0:1.0: USB hub found
<6>hub 1-0:1.0: 5 ports detected
<7>ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
<4>PCI: enabling device 0000:00:01.0 (0140 -> 0142)
<6>ohci_hcd 0000:00:01.0: OHCI Host Controller
<6>ohci_hcd 0000:00:01.0: new USB bus registered, assigned bus number 2
<6>ohci_hcd 0000:00:01.0: irq 28, io mem 0x48000000
<6>usb usb2: configuration #1 chosen from 1 choice
<6>hub 2-0:1.0: USB hub found
<6>hub 2-0:1.0: 3 ports detected
<6>usb 1-2: new high speed USB device using ehci_hcd and address 2
<4>PCI: enabling device 0000:00:01.1 (0140 -> 0142)
<6>ohci_hcd 0000:00:01.1: OHCI Host Controller
<6>ohci_hcd 0000:00:01.1: new USB bus registered, assigned bus number 3
<6>ohci_hcd 0000:00:01.1: irq 27, io mem 0x48001000
<6>usb usb3: configuration #1 chosen from 1 choice
<6>hub 3-0:1.0: USB hub found
<6>hub 3-0:1.0: 2 ports detected
<6>usb 1-2: configuration #1 chosen from 1 choice
<6>scsi0 : SCSI emulation for USB Mass Storage devices
<7>usb-storage: device found at 2
<7>usb-storage: waiting for device to settle before scanning
<5>scsi 0:0:0:0: Direct-Access USBest USB2FlashStorage 0.00 PQ: 0 ANSI: 2
<5>sd 0:0:0:0: Attached scsi removable disk sda
<7>usb-storage: device scan complete
<6>IXP4XX Q Manager 0.2.1 initialized.
<6>ixp4xx_mac driver 0.3.1: eth0 on NPE-B with PHY[1] initialized
<6>eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
<7>Link of eth0 is full-duplex
Re:Meteohub no longer responding after network change
Posted: Wed Sep 23, 2009 7:28 am
by admin
as you can see from dmesg, there is no USB stick recognized or mounted. I guess that USB stick is not setup correctly. Did you use DiskImage in "physical disk" mode when making the stick?
Re:Meteohub no longer responding after network change
Posted: Wed Sep 23, 2009 3:31 pm
by tchazzard
Yes, I did use "physical disk" when making the stick. I received the message that the image was completed successfully. I hate the thought of picking up another unit, but this is getting really frustrating.
Re:Meteohub no longer responding after network change
Posted: Wed Sep 23, 2009 6:41 pm
by admin
What OS are you using? Vista is known to have trouble with this kind of low level writing.
Re:Meteohub no longer responding after network change
Posted: Wed Sep 23, 2009 6:56 pm
by tchazzard
I am using Windows XP.
Re:Meteohub no longer responding after network change
Posted: Wed Sep 23, 2009 7:32 pm
by admin
Hm, that is not making sense. Your dmesg log indicates that the USB stick is not correctly recognized during boot.
An explanation for that might be...
a) that you didn't scrolled down the device list when using diskimage to select the device in "physical disk" mode
b) or that you selected the wrong device (not your stick) with diskimage
c) or you forgot to unrar the image before feeding it to diskimage
Could you please give me the name and md5sum of the unrared diskimage, that you used.
Re:Meteohub no longer responding after network change
Posted: Wed Sep 23, 2009 8:01 pm
by tchazzard
meteohub-v4.5-2GB.dd
I will have to run the md5sum when I get home later.
Re:Meteohub no longer responding after network change
Posted: Thu Sep 24, 2009 5:07 pm
by tchazzard
The md5sum is:
93fc732edbf1d9d74c2b12c84f2cfc7a
