brolin_empey | Oksana: What is your point? This Qicent hub is the first and still only USB hub I have that does not automatically enable a newly connected device but this hub is also the first and still only USB 3 hub I have but I do not think this behaviour changed from USB 1.x and 2 to 3. Also, it should not matter but I use this USB 3 hub with a Renesas USB 3 host controller on a PCI Express add-in card instead of with a USB 3 host controller integrated on the | 01:15 |
---|---|---|
brolin_empey | motherboard of my office computer because my office computer (Dell OptiPlex 960 minitower) is Core 2 era, not Nehalem era nor later, so the USB connectivity integrated on the motherboard is only USB 2, not USB 3. | 01:15 |
sunshavi | bq27200.sh where is the up to date version? | 02:56 |
Oksana | brolin_empey: Point is, it's a fairly complicated process to debug. I am fairly sure that there are lots of students at this university who (I think) speak Chinese, and could potentially ask Qicent about the problem - just, I am not sure what Qicent would say. Would it be "Oh, we send you a refund" or "We send you another hub" or a technical talk about details of the problem? | 05:41 |
* Oksana is hoping that Linux kernel is 4.6 or higher - and wonders if reinstalling/upgrading firmware of Renesas PCIe card could help | 05:52 | |
DocScrutinizer05 | wireguard not ready for primetime is what they told me | 05:58 |
DocScrutinizer05 | ~bq27200 | 06:01 |
infobot | i guess bq27k-detail is http://maemo.cloud-7.de/maemo5/usr/local/sbin/bq27k-detail2, or ~bq27 | 06:01 |
DocScrutinizer05 | ~bq27 | 06:01 |
infobot | methinks bq27 is http://maemo.cloud-7.de/maemo5/usr/local/sbin/ bq27*, or http://maemo.cloud-7.de/maemo5/patches_n_tools/ | 06:01 |
DocScrutinizer05 | I doubt a 2% are BQ's fault. Prolly powerkernel, CSSU-thumb, whatever | 06:03 |
DocScrutinizer05 | Konversation drives me nuts!!! resizes userlist to "hidden" every so often, without me ever noticing why and when | 06:07 |
slobber | how do i know which firmware is right for my n900? i tried the US one, no cellular network available. Tried the global one, same thing | 06:10 |
slobber | reflashed with emmc | 06:10 |
DocScrutinizer05 | you generally use the global firmware. US is rarely known to be needed. You might need full reflash | 06:14 |
slobber | full reflash, huh? | 06:15 |
slobber | i did both emmc and the, uh, other one | 06:15 |
slobber | in that order | 06:15 |
DocScrutinizer05 | ~flashing | 06:15 |
infobot | i heard maemo-flashing is http://wiki.maemo.org/Updating_the_tablet_firmware, or - on linux PC - download&extract http://maemo.cloud-7.de/maemo5/patches_n_tools/maemo-my-private-workdir.tgz, cd into it, do sudo ./flash-it-all.sh; or see ~flashing-cmdline, or see ~lazyflashing | 06:15 |
slobber | i did use the global firmwares from cloud-7.de | 06:15 |
slobber | alright, maybe i'll try flashing it again using those | 06:15 |
DocScrutinizer05 | you should use the lazyflashing | 06:15 |
DocScrutinizer05 | script | 06:16 |
DocScrutinizer05 | might be necessary to remove SIM | 06:16 |
slobber | remove sim during flashing? | 06:16 |
DocScrutinizer05 | yes | 06:16 |
slobber | ok, time to try that | 06:17 |
DocScrutinizer05 | a few reports suggested SIM causing trouble when flashing modem | 06:17 |
DocScrutinizer05 | doesn't the script mention that? | 06:17 |
slobber | doesn't seem like it | 06:18 |
DocScrutinizer05 | anyway, use the script, exactly follow instructions | 06:18 |
DocScrutinizer05 | try to copy & paste the full diagnostic output of lazyflashing script to some pastebin | 06:19 |
DocScrutinizer05 | read the full flashing wikipage | 06:20 |
DocScrutinizer05 | oh, and make sure your battery is fully charged! | 06:23 |
slobber | yup, been charging it all day | 06:23 |
DocScrutinizer05 | even than some old worn batteries might simply be too weak for operating the modem | 06:23 |
DocScrutinizer05 | then* | 06:24 |
slobber | doesn't seem to drain too fast | 06:24 |
DocScrutinizer05 | it's about impedance | 06:24 |
DocScrutinizer05 | not capacity | 06:24 |
slobber | right | 06:24 |
DocScrutinizer05 | might run 7 days and yet drop to a less than 3V when modem draws >2A | 06:25 |
slobber | same error still, damn | 06:30 |
slobber | it doesn't show that sign of missing sim card though | 06:30 |
slobber | ah, yeah, in the settings it can't find a network when i make it manual | 06:34 |
slobber | oh no here we go it found it | 06:34 |
slobber | but 2g, and ATT doesn't do 2g so something is lying | 06:34 |
DocScrutinizer05 | well, the supported bands are not covering 100% of USA (concluding from 'ATT' and firmware choice) | 06:41 |
slobber | hmmm, that's right, ATT is shutting off some of its 3g bands | 06:41 |
slobber | this may be a huge waste of time | 06:41 |
DocScrutinizer05 | well, at least I think another device proven to technically being OK and in working condition | 06:43 |
DocScrutinizer05 | maybe get a TMO SIM? | 06:43 |
slobber | i have a huge grandfathered dicsount with ATT, so might as well keep it | 06:44 |
slobber | shame! | 06:44 |
DocScrutinizer05 | or whatever needed at your location | 06:44 |
slobber | i heard a lot of these are having failing modems - how does that usually present itself? | 06:45 |
DocScrutinizer05 | first asl a friend or in shop to try your N900 with their SIM | 06:45 |
DocScrutinizer05 | ask* | 06:45 |
slobber | that requires having friends | 06:45 |
slobber | i'll ask around | 06:45 |
DocScrutinizer05 | failing modem... has a number of symptoms. *#06# not working anymore (communication to modem broken or modem not coming up). Or no network found (antenna or the RF part of modem broken) | 06:49 |
brolin_empey | slobber: The N900 cellular modem cannot be used with two of the three major, established cellular providers in Canada. Maybe the situation in the USA is similar and the N900 cellular modem cannot be used with your cellular provider. I live in Canada but very close to the USA. | 06:57 |
brolin_empey | Oksana: The version of the Linux kernel on my home computer and office computer is NaN because I use GNU+Windows NT, currently Windows 10 Enterprise for x86-64, instead of GNU+Linux on my primary computers. | 07:03 |
brolin_empey | Or the version is undefined? | 07:03 |
DocScrutinizer05 | Not a Number? | 07:08 |
brolin_empey | Yes. | 07:17 |
slobber | brolin_empey: so you don't use your n900 as a phone, i presume? | 07:30 |
slobber | DocScrutinizer05: *#06# works. maybe it's the antenna? | 07:31 |
slobber | >My guess would be that there isn't any discussion here as it lacks the 3G frequencies used by at&t (850/1900 mhz). It will work on at&t, but only on GSM/GPRS(Edge). Smiley Sad | 07:32 |
slobber | your thoughts are confirmed though | 07:32 |
brolin_empey | slobber: I use the one major, established cellular provider in Canada with which the N900 cellular modem works but I stopped using an N900 in 2014 because my N900 user experience was too bad. | 07:33 |
slobber | ah, i see | 07:34 |
brolin_empey | Currently I use Android OS 8 on an LG G5. | 07:36 |
slobber | android is pretty sad, i'm over it | 07:36 |
Oksana | brolin_empey: I know Windows, I know Linux, I don't know what GNU could mean in context of OS/kernel ?.. | 07:37 |
brolin_empey | slobber: Maybe you can use BlackBerry 10 if you like minority, legacy platforms and difficult to access/remove batteries? | 07:38 |
slobber | brolin_empey: maybe | 17:45 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!