Jump to content

Leon

Administrators
 View Profile  See their activity

  • Posts

    1235

  • Joined

  • Last visited

  • Days Won

    58

 Content Type 

Posts posted by Leon

    Fix Incorrect Clock Settings in Windows When Dual-Booting with OS X or Linux

    in Leon's blog

    Posted

    If you dual boot your Windows PC with OS X or Linux, you may have experienced a problem in which your clocks reset themselves incorrectly every time you boot into Windows. Here's a simple registry edit to fix that.

    Hi,

    So i guess this have been a issue for most of you dualbooting.

    Essentially, the incorrect clock setting happens because OS X and Linux use GMT time while Windows tries to synchronize with your local time zone, getting confused when you reboot between the two.


    Apple's own Boot Camp drivers for Windows are supposed to fix this problem, though some users have noticed that it still happens even with the drivers installed, and some Linux users are left out in the cold. Furthermore, if you have a Hackintosh, you can't install the Boot Camp drivers, so you'll need to find another way around the problem.

     

    To fix it, just hit Start and type regedit.exe in the search box. Hit [Enter] and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation.

    Right click anywhere in the right pane and hit New > DWORD (32-bit) Value. Name it RealTimeIsUniversal, then double click on it and give it a value of 1.

     

    Lastly, reboot into OS X, then reboot back into Windows. You should now notice that your clock actually displays the correct time.


    ... or import the attached reg file.
     
    Timefix: timefix.zip

     

    Apple (Broadcom) BCM4360CD & related 802.11 ac wifi and bluetooth combo card

    in Wireless and Bluetooth

    Posted

    Hi,

    In my constant hunt for better wifi my my Lenovo x201 I decided to give the BCM4360 a go - logically - the only to be found around is real apple cards (rumor has it that you can get some funky noname cards in china - but i have yet to test them)

    The card in question looks like this:

    bcm4360cd.png

     

    Screenshot 2022-01-09 at 19.53.08.png

    Now, logically.. this card wont fit just any machine - its made for a mac, so we are gonna need an adapter to fix that.

    For that we are gonna use an adapter called "Mini PCI-E Adapter for BCM94360CD/BCM94331CD" (search on ebay)

    $_57 (2).JPG

    ... and mounted...

    pic1.jpeg

    pic2.jpeg

    Since its native supported by Apple (doh!) its just to plug it in and start having fun - Same goes for Ubuntu/Debian - it does become a bit more tricky under Windows - however - it seems Asus have made a card with the same chipset - so i managed to track down the Windows driver for that - bluetooth under windows still remains to be fixed.

    Windows wifi driver: DR_PCE_AC66_6309519_Win8.zip

    Have fun!

    //Leon

     

    • Like 1

    Workaround for a Boot Camp x64 installation issue

    in Leon's blog

    Posted

    Yesterday I finally got around to dual-booting my MacBook, with a nice fresh copy of Windows 7. Everything was great, except for a laggy download of the Windows Support Software. So, earlier today, I got around to installing the drivers. It turns out, my old MacBook didn't support BootCampx64. I then did a quick search on how to fix this issue. 

    I came up with a number of answers, but this is an answer aimed at people who were in my situation which is:

    • I could not right click on the BootCampx64.msi file, because of the missing drivers.
    • Or if I could right click, then changing the properties of BootCampx64.msi resulted in not having the required elevated access privileges.

    My solution (done from within Windows, obviously):

    • Without the drivers installed, you can still right click on the BootCampx64.msi file by click it with 'Shift-F10' which apparently acts as an alternate right click.
    • If you have the first step down, try opening the properties of the file, and change the compatibility to earlier versions of Windows.
    • If that still doesn't work, then open the start menu. Then go to Programs » Accessories » CMD, and hover over CMD.
    • Press Shift-F10, or right click if you are able, on CMD (the Windows Command Prompt).
    • Select the option in the drop-down menu, 'Run as Administrator.'
    • Then open CMD and get a shell window.
    • Now, when you open CMD, you should be running it as C:Windowssystem32.
    • At the Command Prompt, type in cd /d C:
    • You should now have C: at the far left of the prompt.
    • Type in cd Users. Then type in dir.
    • Find your username, and then type in cd username, e.g. cd John Smith
    • Continue the dir, cd process until you come into the directory in which the BootCampx64.msi is. (You may have dragged the WindowsSupport folder onto the desktop, or someplace else).
    • After you have reached the directory, simply type in BootCampx64.msi.
    • The program should start.
    • All of the drivers should start installing. You probably won't be able to move your mouse if you have a trackpad, as I do, because the Apple Trackpad driver is one of the last to be installed.

    If it seems like the process is taking a while, be patient. 

    Sources: 

    This earlier hint, this Apple forum thread, and this very helpful article. 

    • Like 1

    Elementary OS Freya: Enable tweaks

    in Leon's blog

    Posted

    Hi,

    Lately i have been messing with Elementary OS, its a quite nice linux distro that unlike most others works and acts alot more like OSX.

    Anyway - tip of the day - howto enable Elementary Tweaks on the latest beta of Freya

    Original link: http://www.reddit.com/r/elementaryos/comments/2cv41d/installingelementarytweaksonfreya/

    Install Tweaks

    $ sudo add-apt-repository ppa:versable/elementary-tweaks-isis
    $ sudo apt-get update
    $ sudo apt-get install elementary-tweaks
     
    Open schema file in text editor:
    $ sudo scratch-text-editor /usr/share/glib-2.0/schemas/org.gnome.desktop.interface.gschema.xml

    Insert the following text BEFORE the closing tag at the end of the file:
    falseOverlay ScrollbarToggle the overlay scrollbar.$
     
    Install dconf-editor
    $ sudo apt-get install dconf-editor
     
    Go to org->gnome->desktop->interface on dconf-editor
    Find and enable ubuntu-overlay-scrollbars option
    It then says to reboot but I would think logging out then back in of the desktop would be enough. Hope this works for everyone. Sorry if I screw up the markdown... First $
    permalink

    Compile schemas
    sudo glib-compile-schemas /usr/share/glib-2.0/schemas/
     
    Now open Tweaks and all works
     

    Sierra Wireless 4G/LTE MC7710/MC7700

    in WWAN

    Posted

    Links:

     

    Following is my research notes on the mc7710

    First of all - i figured out that the card operates either in QMI or DIP (Direct IP) mode - To identify what mode your card is in check the ProductID under sysinfo.

    0x68A2 = QMI
    0x68a3 = DIP

    This seems to have alot of inpact on wether you can use it under osx/linux or not - under windows - logically... both work - mine is in QMI,

    There is a guide here for howto change it - but i havent had much luck with it yet: http://www.szelins.com/download/usermanual/H685_MC7710_from_DIP_to_QMI.pdf

    My progress on the different OS:

    OSX 10.9.4:

    • Patched Cellphonehelper.kext makes it show up in the topbar, but says "PIN LOCKED" when i click on it (the sim card is not locked)
    • Sierrawatcher: Card _MUST_ be in direct ip mode (DIP) or it wont work.. i'm pretty sure it will enable 4G/LTE also.
      Use this watcher software: Generic_Mac_Watcher_B3563.mpkg.zip

    Tried to patch the different plists and while card gets detected its unable to connect - dies with error "unable to comm. with modem"

    Linux:
    Not detected

    Windows:
    Works perfect using Sierrawatcher software

    Update:
    Switching modes from QMI to DIP worked by using another machine solves the problem and it now works as a DIP device in OSX using the watcher software.

     

    DirectIP vs. QMI

    DirectIP:
    - Independent control of user plane and data plane
    o Different USB interfaces for control vs data
    - Data sessions can be controlled by AT commands
    - Simple to setup a data session (one AT cmd to configure profile, one to trigger data session)
    o User can test manually from a terminal program
    - Currently supports multiple concurrent data sessions (PDP contexts) to host
    o Note: works in HSPA but not fully tested on LTE
    - No support for CDMA (therefore can’t be used with MC7750).
    - No SDK support on MC77xx platforms as we don’t officially support CNS on MC77xx
    - Windows and Linux driver support available

    QMI:
    - Control and data planes are multiplexed together
    o Share a single USB interface for control & data
    - Data sessions can only be controlled via QMI protocol
    - Compared to AT cmds, much more complicated to setup a data session as control services need to be initialized before any QMI commands can be sent
    o Need some sort of host program to do this (can’t be done manually)
    - Currently, does not support multiple concurrent data sessions to host
    o QCT has no plans to support but Sierra looking to add this support ourselves
    o May be more complicated than DirectIP due to fact that we will need to split control and data planes for subsequent data sessions (i.e. one control interface for multiple data paths)
    - Supports CDMA (currently only option for MC7750).
    - Supported via QMI SDK in Linux and Windows
    - Windows and Linux driver support available

    Sierra Wireless MC8700

    in WWAN

    Posted

    Hi,

    When i try to connect i get:
     

    Wed Jun 18 22:51:12 2014 : publish_entry SCDSet() failed: Success!

    Wed Jun 18 22:51:12 2014 : publish_entry SCDSet() failed: Success!

    Wed Jun 18 22:51:13 2014 : Initializing phone: ATE0V1&F&D2&C1S0=0

    Wed Jun 18 22:51:13 2014 : Initializing PDP context: AT+CGDCONT=1,"IP","internet.telenor.se"

    Wed Jun 18 22:51:13 2014 : Dialing: ATD*99***1#

    Wed Jun 18 22:51:13 2014 : Waiting for connection

    Wed Jun 18 22:51:13 2014 : No carrier.

    Wed Jun 18 22:51:13 2014 : CCLExit: -6021 (No carrier.)

    Wed Jun 18 22:51:13 2014 : Connect script failed

     

    Sierra Wireless MC8700

    in WWAN

    Posted

    BIOS i am not so worried about.. for the x201 we have a patched bios to whitelist that.. it will be quite slow to get past bios but the card will work.
    The x201s only comes with one antenna for WWAN, so i have wired in an antenna mine manually... adding one more shouldent be the biggest problem :-)

×
×
  • Create New...