new build


 
No you shouldn't be losing your wifi settings or password if you've set it. There's definitely something weird going on if it keeps losing its configuration. You might want to look at Status -> System Log, or Status -> Kernel Log to see if there are errors on the SD card or something like the configuration being reset on every boot?
 
When I setup my HM WiFi connection I actually create a special interface for it rather than using WWAN... Looking at the WWAN Interface settings on my HM it seems to have DHCP enabled, looks like this is the interface that is used for the HM on first boot when it comes up in Access Point mode? Try creating an interface specifically for your WiFi client mode connection and use that instead of WWAN and see if you have better luck...
 
Bryan Mayland said:
No you shouldn't be losing your wifi settings or password if you've set it. There's definitely something weird going on if it keeps losing its configuration. You might want to look at Status -> System Log, or Status -> Kernel Log to see if there are errors on the SD card or something like the configuration being reset on every boot?
Click to expand...

Bryan, I haven't even been able to get the password set at all, it never seems to take it even after several minutes. I'm guessing that could be part of my problem. Should I just try to put a different SD card in and see what happens? I wouldn't need to write the image as HM will do that automagically right?
 
From the system log:
Jan 7 23:17:49 OpenWrt user.err lucid[399]: RRD last failed:short read while reading header rrd->stat_head
Jan 7 23:17:49 OpenWrt kern.crit kernel: [ 25.436007] EXT4-fs error (device mmcblk0p2): ext4_mb_generate_buddy:739: group 0, 3485 clusters in bitmap, 3562 in gd
Jan 7 23:17:49 OpenWrt kern.crit kernel: [ 25.440776] EXT4-fs (mmcblk0p2): Remounting filesystem read-only
Jan 7 23:17:49 OpenWrt kern.crit kernel: [ 25.443472] EXT4-fs (mmcblk0p2): ext4_da_writepages: jbd2_start: 1004 pages, ino 337; err -30
Jan 7 23:18:09 OpenWrt user.err lucid[582]: Error sending data to 10.0.0.103: 32
Jan 7 23:22:26 OpenWrt kern.notice kernel: [ 302.571730] EXT4-fs (mmcblk0p2): error count: 104
Jan 7 23:22:26 OpenWrt kern.notice kernel: [ 302.574132] EXT4-fs (mmcblk0p2): initial error at 1420424310: mb_free_blocks:1348: inode 337: block 3343
Jan 7 23:22:26 OpenWrt kern.notice kernel: [ 302.578742] EXT4-fs (mmcblk0p2): last error at 1420672669: ext4_mb_generate_buddy:739
Jan 7 23:23:44 OpenWrt user.err lucid[594]: Error sending data to 10.0.0.103: 32
 
From Kernel Log:
[ 0.000000] Normal zone: 121920 pages, LIFO batch:31
[ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[ 0.000000] pcpu-alloc: [0] 0
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 121920
[ 0.000000] Kernel command line: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708.boardrev=0xe bcm2708.serial=0xb1a766dd smsc95xx.macaddr=B8:27:EB:A7:66:DD sdhci-bcm2708.emmc_clock_freq=100000000 vc_mem.mem_base=0x1ec00000 vc_mem.mem_size=0x20000000 dwc_otg.lpm_enable=0 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait
[ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Memory: 480MB = 480MB total
[ 0.000000] Memory: 483780k/483780k available, 7740k reserved, 0K highmem
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
[ 0.000000] vmalloc : 0xde800000 - 0xff000000 ( 520 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xde000000 ( 480 MB)
[ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)
[ 0.000000] .text : 0xc0008000 - 0xc02d9888 (2887 kB)
[ 0.000000] .init : 0xc02da000 - 0xc02f3000 ( 100 kB)
[ 0.000000] .data : 0xc02f4000 - 0xc0316ae0 ( 139 kB)
[ 0.000000] .bss : 0xc0316b04 - 0xc035de90 ( 285 kB)
[ 0.000000] SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] NR_IRQS:330
[ 0.000000] sched_clock: 32 bits at 1000kHz, resolution 1000ns, wraps every 4294967ms
[ 0.000000] timer_set_mode: unhandled mode:1
[ 0.000000] timer_set_mode: unhandled mode:3
[ 0.000000] Console: colour dummy device 80x30
[ 0.000000] console [tty0] enabled
[ 0.000645] Calibrating delay loop... 697.95 BogoMIPS (lpj=3489792)
[ 0.060156] pid_max: default: 32768 minimum: 301
[ 0.060452] Mount-cache hash table entries: 512
[ 0.060939] CPU: Testing write buffer coherency: ok
[ 0.061206] Setting up static identity map for 0x25c790 - 0x25c7ec
[ 0.061958] devtmpfs: initialized
[ 0.072446] NET: Registered protocol family 16
[ 0.072964] bcm2708.uart_clock = 0
[ 0.074745] mailbox: Broadcom VideoCore Mailbox driver
[ 0.074860] bcm2708_vcio: mailbox at f200b880
[ 0.074949] bcm_power: Broadcom power driver
[ 0.074980] bcm_power_open() -> 0
[ 0.075001] bcm_power_request(0, 8)
[ 0.575674] bcm_mailbox_read -> 00000080, 0
[ 0.575706] bcm_power_request -> 0
[ 0.575725] Serial: AMBA PL011 UART driver
[ 0.575867] dev:f1: ttyAMA0 at MMIO 0x20201000 (irq = 83) is a PL011 rev3
[ 0.596685] bio: create slab <bio-0> at 0
[ 0.597542] SCSI subsystem initialized
[ 0.597770] usbcore: registered new interface driver usbfs
[ 0.597901] usbcore: registered new interface driver hub
[ 0.598097] usbcore: registered new device driver usb
[ 0.599022] Switching to clocksource stc
[ 0.613091] NET: Registered protocol family 2
[ 0.613393] IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.613776] TCP established hash table entries: 16384 (order: 5, 131072 bytes)
[ 0.614245] TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.614520] TCP: Hash tables configured (established 16384 bind 16384)
[ 0.614549] TCP reno registered
[ 0.614575] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 0.614619] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 0.614993] NET: Registered protocol family 1
[ 0.615224] bcm2708_dma: DMA manager at f2007000
[ 0.615370] bcm2708_gpio: bcm2708_gpio_probe c02f9de8
[ 0.615738] gpiochip_add: registered GPIOs 0 to 53 on device: bcm2708_gpio
[ 0.615834] vc-mem: phys_addr:0x00000000 mem_base=0x1ec00000 mem_size:0x20000000(512 MiB)
[ 0.626009] msgmni has been set to 944
[ 0.626113] io scheduler noop registered
[ 0.626140] io scheduler deadline registered
[ 0.626205] io scheduler cfq registered (default)
[ 0.638586] Console: switching to colour frame buffer device 82x26
[ 0.653394] brd: module loaded
[ 0.660266] loop: module loaded
[ 0.663042] vcos: [1]: vchiq_init_state: slot_zero = 0xffd80000, is_master = 0
[ 0.665284] vcos: [1]: vchiq_init_state: called
[ 0.667606] vcos: [1]: vchiq: initialised - version 2 (min 2), device 253.0
[ 0.670108] usbcore: registered new interface driver smsc95xx
[ 0.672184] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[ 0.879321] Core Release: 2.80a
[ 0.881274] Setting default values for core params
[ 0.883211] Finished setting default values for core params
[ 1.090194] Using Buffer DMA mode
[ 1.092121] Periodic Transfer Interrupt Enhancement - disabled
[ 1.094080] Multiprocessor Interrupt Enhancement - disabled
[ 1.096013] OTG VER PARAM: 0, OTG VER FLAG: 0
[ 1.097897] Dedicated Tx FIFOs mode
[ 1.099944] dwc_otg: Microframe scheduler enabled
[ 1.099983] dwc_otg bcm2708_usb: DWC OTG Controller
[ 1.101909] dwc_otg bcm2708_usb: new USB bus registered, assigned bus number 1
[ 1.103883] dwc_otg bcm2708_usb: irq 32, io mem 0x00000000
[ 1.105873] Init: Port Power? op_state=1
[ 1.107803] Init: Power Port (0)
[ 1.109800] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.111774] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.113758] usb usb1: Product: DWC OTG Controller
[ 1.115671] usb usb1: Manufacturer: Linux 3.3.8 dwc_otg_hcd
[ 1.117595] usb usb1: SerialNumber: bcm2708_usb
[ 1.120365] hub 1-0:1.0: USB hub found
[ 1.122283] hub 1-0:1.0: 1 port detected
[ 1.124758] dwc_otg: FIQ enabled
[ 1.124773] dwc_otg: NAK holdoff enabled
[ 1.124793] Module dwc_common_port init
[ 1.125031] usbcore: registered new interface driver uas
[ 1.126901] Initializing USB Mass Storage driver...
[ 1.128865] usbcore: registered new interface driver usb-storage
[ 1.130774] USB Mass Storage support registered.
[ 1.132750] usbcore: registered new interface driver libusual
[ 1.134932] mousedev: PS/2 mouse device common for all mice
[ 1.137507] bcm2708 watchdog, heartbeat=10 sec (nowayout=0)
[ 1.139690] bcm2835-cpufreq: min=700000 max=800000 cur=700000
[ 1.139967] bcm2835-cpufreq: switching to governor ondemand
[ 1.141848] bcm2835-cpufreq: switching to governor ondemand
[ 1.143824] sdhci: Secure Digital Host Controller Interface driver
[ 1.147238] sdhci: Copyright(c) Pierre Ossman
[ 1.149062] sdhci: Enable low-latency mode
[ 1.150903] bcm_power_open() -> 1
[ 1.153878] Registered led device: mmc0::
[ 1.155120] mmc0: SDHCI controller on BCM2708_Arasan [platform] using PIO
[ 1.156998] mmc0: BCM2708 SDHC host at 0x20300000 DMA 2 IRQ 77
[ 1.158839] sdhci-pltfm: SDHCI platform and OF driver helper
[ 1.160937] Registered led device: led0
[ 1.161266] TCP cubic registered
[ 1.163090] NET: Registered protocol family 17
[ 1.165041] 8021q: 802.1Q VLAN Support v1.8
[ 1.166924] VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5
[ 1.171876] Waiting for root device /dev/mmcblk0p2...
[ 1.268878] mmc0: new high speed SD card at address b368
[ 1.271398] mmcblk0: mmc0:b368 SD 952 MiB
[ 1.274858] mmcblk0: p1 p2 p4
[ 1.284497] EXT4-fs (mmcblk0p2): warning: mounting unchecked fs, running e2fsck is recommended
[ 1.404902] EXT4-fs (mmcblk0p2): mounted filesystem without journal. Opts: (null)
[ 1.409157] VFS: Mounted root (ext4 filesystem) on device 179:2.
[ 1.411689] Freeing init memory: 100K
[ 1.414050] Indeed it is in host mode hprt0 = 00021501
[ 1.589192] usb 1-1: new high-speed USB device number 2 using dwc_otg
[ 1.591690] Indeed it is in host mode hprt0 = 00001101
[ 1.789562] usb 1-1: New USB device found, idVendor=0424, idProduct=9514
[ 1.791944] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1.809951] hub 1-1:1.0: USB hub found
[ 1.812371] hub 1-1:1.0: 5 ports detected
[ 2.089381] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[ 2.199765] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
[ 2.202149] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 2.246739] smsc95xx v1.0.4
[ 2.324983] smsc95xx 1-1.1:1.0: eth0: register 'smsc95xx' at usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:a7:66:dd
[ 5.469134] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[ 5.986282] cfg80211: Calling CRDA to update world regulatory domain
[ 6.123382] usbcore: registered new interface driver rt2800usb
[ 6.201058] usbcore: registered new interface driver rtl8192cu
[ 6.243324] usbcore: registered new interface driver usbhid
[ 6.245459] usbhid: USB HID core driver
[ 9.514646] smsc95xx 1-1.1:1.0: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
[ 16.149664] EXT4-fs (mmcblk0p4): warning: mounting unchecked fs, running e2fsck is recommended
[ 16.265137] EXT4-fs (mmcblk0p4): mounted filesystem without journal. Opts: (null)
[ 25.436007] EXT4-fs error (device mmcblk0p2): ext4_mb_generate_buddy:739: group 0, 3485 clusters in bitmap, 3562 in gd
[ 25.440776] EXT4-fs (mmcblk0p2): Remounting filesystem read-only
[ 25.443472] EXT4-fs (mmcblk0p2): ext4_da_writepages: jbd2_start: 1004 pages, ino 337; err -30
[ 302.571730] EXT4-fs (mmcblk0p2): error count: 104
[ 302.574132] EXT4-fs (mmcblk0p2): initial error at 1420424310: mb_free_blocks:1348: inode 337: block 3343
[ 302.578742] EXT4-fs (mmcblk0p2): last error at 1420672669: ext4_mb_generate_buddy:739
 
Jan 7 23:17:49 OpenWrt kern.crit kernel: [ 25.440776] EXT4-fs (mmcblk0p2): Remounting filesystem read-only


Make sure you didn't slide over the write protect tab on your SD card...

EDC04014_01.gif


Sometimes moving the switch to locked and back to unlocked will get the card working again according to what I have read... MicroSD cards don't have a mechanical switch, and it seems some of them just decide to lock off for no apparent reason and never unlock again....
 
Last edited:
Just change the SD card. All is well now.

Thanks for dealing with my insanity over this. It was making me crazy.
 
Glad you got it up and running Jay. It seems after I replaced my sd card this morning and rebooting my cable modem seemed to fix my problem. Thank to everyone for there input in helping us get our Heatermeters going .
 
RalphTrimble said:
Jan 7 23:17:49 OpenWrt kern.crit kernel: [ 25.440776] EXT4-fs (mmcblk0p2): Remounting filesystem read-only


Make sure you didn't slide over the write protect tab on your SD card...

EDC04014_01.gif


Sometimes moving the switch to locked and back to unlocked will get the card working again according to what I have read... MicroSD cards don't have a mechanical switch, and it seems some of them just decide to lock off for no apparent reason and never unlock again....
Click to expand...

Ralph, thanks. Yes, I do know about the lock/unlock and I did have the card readable.

Here's what I think was going on with it. I know that when we first rooted some the original Nook Color tablets years ago that the SD card made all the difference in the success/failure of how well the OS would run on the SD card. It had to do with "small block random writes" and some cards were better than others. The best cards at the time were the cheaper Sandisk cards and I'm guessing that the HM project is seeing similar needs. Here is the thread that discusses the issue in detail:

http://forum.xda-developers.com/showthread.php?t=1005633

It may or may not have something to do with the SD issue that apparently some folks have had but it sure feels the same to me.

Thanks again for all the help guys. Ramiro, glad you're working too. I had mine up all night and everything is looking good!
 
The write protect pins on the SD card reader on the RaspberryPi are not connected to anything, so the lock position switch on an SD card shouldn't matter.
 
That doesn't make any sense to me, cause I had an SD card that got write protected and the rPi wouldn't work with it properly.
 
It was write protected via software modifying the bits on the SD card, it had nothing to do with a slider switch.
 
Oh, I see what you are saying.... the physical switch on the full size SD card goes to those two pins are on the edge of the card, which connect to nothing on the rPi, so do nothing. I am just assuming you are right on that 'cause I haven't researched it. On the other hand, the MICROSD card write protect is an internal software thing, not a mechanical switch. That makes sense to me... but this problem with SD and MicroSD cards going into write protect on their own without intervention from their user (or flipping the switch), which seems to be a common issue if you search it, could cause this issue on the rPI on either standard or MicroSD cards...

If one of you guys that experienced this issue on a full size SD card could put it into a reader on a computer and try to format the card to see if you get the write protect message that would be good info.....
 
Ralph, are you suggesting that the problem with my initial SD card is that something write protected it on a software level when I was setting up my HM/rPi? I'll certainly put it in the computer and see if I can format it and report back.

I was wondering if the title of this thread should be WiFi problems or something along those lines instead of new build. I know that I would have tried a different SD card much earlier had I known that could be the issue with my WiFi not working.

BTW, I smoked a burger for lunch today just to test the HM out and was getting texts on my phone as things happened--temperature got a little hot and when the meat was cooked. Is there a way to get texts periodically, say every 15 minutes with status on what all the temperature probes are prior to going into an alarm state? The HM project is totally awesome. I was very pleased with the result of my cook. I'm doing a pork butt this weekend for sure.
 
On the monitoring, or update texting... You could use the smartphone apps to look in any time you want, and there is a lite page built into the HM that just shows the temps (page made very small to load on low end "smart" phones"). Or I think you could prob make your own custom script to do this for you, but as far as I know this type of function is not "built-in" to the HM.

On the SD Card, yah, I am suggesting, or asking if these cards that are not working properly are showing up as write protected? Reason being, I just had a MicroSD card crap out on me and that is the issue, so I've been searching around for info and read a lot of stuff about SD cards getting locked down for no apparent reason, and also about rPi running into issues with write protect (even though the write protect switch on the rPi reader is not connected to anything as Steve_M pointed out). What pointed me in that direction here was the line in the log you posted:
Jan 7 23:17:49 OpenWrt kern.crit kernel: [ 25.440776] EXT4-fs (mmcblk0p2): Remounting filesystem read-only

I noticed the same thing when I was having the problem and that is what led me to discover the (MicroSD) card was write protected for some unknown reason. At least partially, because I do seem to be able to blank it and write it again with Disk Imager, but if I try to format it with Windows it tells me it is write protected, and the rPi is seeing it as write protected. Since you guys were making changes to your WiFi config and they weren't being saved, and your boot log says "remounting filesystem read-only" it makes me wonder if this is not a write protect issue as well. Either bad card or rPi somehow making the write protect happen. I have read some threads about ways to "minimize" the chance that raspian will lock down your card, some stuff about not having it save logs, so I guess it's a thing.....
 
Last edited:
Gotcha. Yes, I will see what I can do with the card (if anything). It was clearly working before I started all of this as I took almost a full gig of pictures off the card and moved them to my computer before imaging the card for HM. Now, I had that funky 3.3v problem at first so maybe that could have corrupted the card--who knows for sure. I'll see if I can format it.

I do have the smartphone app and that's great for when I'm at home. The idea of a frequent update is for if I'm out and about and want to know what's going on without having to be connected to the WiFi at home. So say I want to head to HD for something but I have a cook going and I'm getting toward the end. If I'm watching internal temp every 10 or 15 minutes, I have an idea when I really need to get home or if I can hang out and explore stuff for a project or make another stop while I'm out. I'm sure there's a way to script that but I don't know how to do that I suppose. Maybe I'll dig around and see if I can figure out how to do something like that.
 
I've mentioned it before that solid state media can get pretty unhappy when the power is removed from it. You might be able to do it 100 times and have no trouble, or it might cause problems the very first time.
 
The smartphone app and HM lite page works over the internet from anywhere in the world.....

Funny you mention that your card worked well in your camera.... The card I am having a problem with had been in my phone first, I had bought a 8G card for the HM but for some reason that card was acting crazy like yours (even though it was a virgin card when I put the HM OS on it), it would boot, wifi worked but it wouldn't allow me to create and save a password. So I went for this 4G card that was in an old phone. It worked fine at first, saved fine, worked for a week or two, then just died with this write protected business...
After the 4G card died I went back to the 8G, located the newest version of Disk Imager and used that to load the HM image, this time I can save a password and everything seems to be working properly with the 8G MicroSD card, for now....
 
I've had a couple of card go belly up on me, i always use 4 or 8 gb cards and mostly branded but they could easily be counterfeit from ebay. I found for me the easiest way is to get the config the way i want and use the disk imager to make a copy plus i save the config to my desktop. I would like to see a 'shutdown' feature in the software just to give it an elegant way of turning off. Either way i expect to lose the occasional SD card, it's the cost of doing business :-)
 
You must log in or register to reply here.

 

Back
Top