**** BEGIN LOGGING AT Sun Jun 04 03:00:02 2017 Jun 04 09:15:57 Hi, I am having an issue with lunching "192.168.7.2" in google chrome. It worked great for the past 8 days but just stopped working today. I am able to log into my board in mac terminal through ssh and serial and I do have internet-over-USB working on my board. Jun 04 09:16:17 My drivers are installed. I even re-installed them. Jun 04 09:16:46 I'm wondering if anyone has recommendations on what else I can try? Jun 04 11:42:20 did anyone try to connect the QCA6234 chip to BeagleBoard-xM through SDIO.? Jun 04 14:52:44 hello Jun 04 17:42:38 Hi, my questions in the Google groups for the bbb are only getting a 2 views after days... I was wondering if I could get some more help here? Jun 04 17:52:05 well, I can at least predict that you won't get any help if you don't actually state your problem / ask your question :) Jun 04 17:52:46 Thanks, I didn't want to go full on without greeting firs ;). I've got BBB rev C with latest IOT debian image Jun 04 17:52:58 I put it in standby and pressing the power button wakes it up. Jun 04 17:53:22 I put it in suspend to ram with "echo mem > /sys/power/state" and power button won't wake it up Jun 04 17:54:26 I don't know which power state you get exactly in the latter case... when in deepsleep only a limited set of wakeup sources are available, and the power button is not one of them Jun 04 17:55:23 According the the reference manual, the power button is connected to the ext_wakeup of the CPU, are you sure is not a valid wake up source? Jun 04 17:56:05 I've also tried with a GPIO from the bank 0, but I couldn't wake it up either. Jun 04 17:56:14 the power button is not connected via ext_wakeup, the power button is connected to the power button input of the PMIC Jun 04 17:56:48 its irq is connected to the EXTINT input of the cpu, which is not a wakeup source in the lowest power states afaik Jun 04 17:57:22 gpio0 *should* allow wakeup, but I don't know if any configuration needs to be done for it Jun 04 17:58:16 OK, do you know if the GPIO setup (if any) would be a dto or I need to recompile the kernel? Jun 04 17:58:48 neither sounds plausible Jun 04 17:58:56 I would just expect some config via sysfs Jun 04 17:59:41 sysfs... that's new to me. I'll have to do some learning on that one Jun 04 18:00:39 sysfs (/sys/*) is a pseudo-filesystem which is basically just a representation of devices and other kernel object and various information/configuration variables they expose Jun 04 18:01:52 you've already met it since you've used "echo mem >/sys/power/state" Jun 04 18:01:53 :) Jun 04 18:03:17 Thanks zmatt. I'll see if I can find more info. The SRM only states that EXT_WAKEUP is used to wake up the processor when it's in sleep mode but doesn't say what sleep mode. I guess it's only valid in standby. Jun 04 18:04:31 that sounds really weird, since ext_wakeup isn't relevant at all to sleep states Jun 04 18:04:44 nor is it accessible Jun 04 18:05:35 yeah that description is wrong Jun 04 18:06:08 The power button wake up does work in standby though... Jun 04 18:06:36 standby is the lightest sleep mode, in which any irq can wake up the system (if enabled when entering standby) Jun 04 18:07:03 I see. It sounds like I should move my efforts to the GPIO wake up then Jun 04 18:08:21 wakeup from the deepest sleep modes is limited to uart0, gpio0, adctsc async pen touch, rtc, and probably a few more things I've missed Jun 04 18:09:31 in all cases requiring the kernel to specifically request the wakeup-m3 to enable those wakeup sources Jun 04 18:09:34 I've only seen RTC working with "rtcwake -m mem -s 5", I tried uart0 and gpio0 but I couldn't make them work Jun 04 18:10:05 I haven't done anything with sleep in a long while, but uart0 and gpio0 did work back when I tried it Jun 04 18:10:54 Do you remember if you were using a kernel > 3.13? Jun 04 18:11:18 I was almost certainly using 4.1 or 4.4 Jun 04 18:12:21 Good to know, thanks. I will dig in the kernel code for that wakeup-m3 and see if I can fix the GPIO wake up. Jun 04 18:13:19 Can I ask one last thing... I'm not sure about dto. Should I try to change the GPIO 0 with an overlay or load an specific dto? Jun 04 18:13:35 neither should be necessary Jun 04 18:14:37 I probably just exported some gpio and enabled interrupt on falling and/or rising edge (via sysfs) Jun 04 18:14:55 OK, that's been very helpful, thanks. I will take this information and try a few things. I'll might ahve to come back here in a wee while :) Jun 04 18:15:38 Thank you for your time zmatt Jun 04 18:15:50 np :) Jun 04 18:15:55 I'm afk too Jun 04 20:53:09 hey guys Jun 04 20:53:12 allah is doing Jun 04 20:53:17 sun is not doing allah is doing Jun 04 20:53:19 to accept Islam say that i bear witness that there is no deity worthy of worship except Allah and Muhammad peace be upon him is his slave and messenger Jun 04 20:53:34 !ops Jun 04 23:18:01 Hello, I'm having an issue with launching http://192.168.7.2 in google chrome on Mac. I have connected to this more than 10 times in the past few days. The BB start page shows step 1 and 2 hi-lighted green indicating that the mac drivers are installed. I'm able to connect to internet-over-USB when I ssh and use screen in mac terminal. I'm not sure what to do about connecting to the link in chrome. Jun 04 23:18:43 I looked through online blogs and people say un install and then re install drivers, so I tried it and still didn't work. Jun 04 23:18:54 uhh, if you can ssh in then evidently you can reach the bbb Jun 04 23:20:05 if you can't reach the same ip/hostname in a webbrowser, the only reason for that I can think of would be if the webserver isn't running Jun 04 23:23:30 Although I can connect through ssh in terminal I'm looking to use Cloud9 IDE as well Jun 04 23:24:28 I've never used it beyond one little toy a long while ago, and currently don't even have it installed on any bbb here, so I can't really help you with getting it to work Jun 04 23:28:45 Ah alright, thanks for your input **** ENDING LOGGING AT Mon Jun 05 03:00:01 2017