Catégorie dans Informatique / Computers

Get the Dell HSPA 5530 WWAN working on any modern Dell Latitude laptop with Windows 7 x64bits.

Ok, after many (many) attempts and research, finally got the Dell HSPA 5530 WWAN Mini card working on a Dell Latitude laptop (in that case a 6420 XFR rugged) under Windows 7 x64Bits. The challenge is that you have to get the right combination of device drivers, and wireless manager version, as well force through the installation of the 5530 device, that check for a valid combination of laptop model / device and will reject the 5530 on this device.

Here is what you need :

  • A Dell Latitude laptop with a WWAN mini card slot, and the SIM Card slot (usually behind the battery), with pre-cabled antennas in the chassis. Fit the card into the chassis, shoud appear in Windows as an unknown device. Make sure BIOS setting is not interferring with disabled WWAN option.
  • The Windows 7 driver for the WWAN 5530 card, version A07, for Windows x64bits. You can find it here on Dell support web site Dell Wireless 5530 HSPA Mini-Card, v.Driver: v4.50.6.0 Co-installer: v1.0.12.1, A07. The name of the file is « DELL_WIRELESS-5530-HSPA-MINI_A07_R220899.exe ». This is a 10MBytes file.
  • The Dell Wireless Manager software, that comes inside a 10Mbytes file you can find on Dell Support at Dell Wireless 5530 HSPA Mini-Card, v.5.2.1045.60, A02
  • The Microsoft Orca MSI editor file, you can  find details and download link here
  • The approach used by Remko to force through the installation of the driver on the laptop (3x deactivating Authentication checks in MSI) documented on his blog here. 

Here are the steps :

  • Install the A02 applicatin 100Mbytes package first. This will get you the Wireless Manager on your Laptop. It won’t detect the device, because the WWAN card driver is not installed. That is OK.
  • Install the A07 driver of the card, this will fail with an error message that this card is not valid for this laptop. Use Remko’s approach, to NOT terminate the installer, but before closing it copy paste from the temp folder the whole temporary decompressed install folder, and then paste this somewhere in a place you have write access to. Terminate the installer that rejected the install, then edit the MSI file as documented by Remko by removing in 3 different places the authentication check. Re-run then the MSI package from there, that should install 3 new devices on your unit, that is a HSPA network card, a HSPA Modem, and a SIM Card slot.
  • Reboot, you are good to go. You shall now open the Wireless Manager application and see your card, turn the radio on, input your PIN code for the SIM and get connected. This will appear as a wired LAN connection to other programs when connected.

I tried other combination of Dell Control Point Connection Manager, or newer Wireless Manager, or not using Wireless Manager at all, or using different driver release, they all failed. The only one found working is A07 for the driver, and then A02 for the application call Wireless Manager.

 

 

 

 

Debian Live USB 9.4.0 with persistence

Ok, I spent some time to get the Live USB media of Debian Live 9.4.0 working. The documentation and experience is scattered around on Internet, so let’s get this here together so I can reproduce it later.

Scenario : deploy Debian Stretch 9.4.0 Live on USB stick with persistence, from Windows environment.

Source the right ISO : I got the amd 64bits edition with MATE environment, and non-free firmware. The non-free firmware was needed to get things working like in particular the Intel Wifi card.

User the right tool : Rufus was making the best installation, despite it does not provide persistence support, which need to be added after initial install.

Create the image, by using Rufus on your USB stick and selecting the ISO file you downloaded. That initial, primary, active, first permission has to be FAT32. It will take the whole space on the drive, that is OK.

Once the ISO file has been transferred/installed on the stick, time to get a tool like EPM (EaseUS Partition Manager) to resize down the primary FAT32 partition to something much smaller, like 3GB to cover your ISO image (mine was 2.2GB).

Create a new partition after this one (you can user the whole space remaining), and the under Linux Debian reformat it to « ext4 » and label it « persistence ». The persistence is NOT supported on FAT32 file, I figured that out by getting errors in kernel.log.

Then mount this newly created ext4 volume, and on the root of it, create a file named « persistence.conf » and add 2 lines (the second being an empty, blank line), the first just contains :

/ union

Close it all, reboot and select kernel option by pressing « tab » on the boot menu and adding « persistence » (without the quotes) to the boot.
The kernel should get it, and with that union on / level, you simply get full persistence of the environment.
You can happily create folders on Desktop, in your home, change your password as well install and upgrade packages, and find this back when you reboot.

 

Ecran noir sur Acer Aspire 5740G

Bon, comme c’est la deuxième fois que cela arrive, voilà comment procéder pour récupérer un Acer Aspire 5740G avec son écran noir / carte graphique ATI plantée.

  • Etape 1 : stopper les BSOD à répétition et récupérer la machine.
    • Brancher le laptop en HDMI sur un écran externe
    • Rebooter W10 en mode sans échec (après 3 reboot avec BSOD, le choix est proposé).
    • Dans gestionnaire de périphérique faire supprimer sur carte ATI. Supprimer le pilote.
    • Rebooter en mode normal, toujours avec l’écran extérieur en HDMI connecté
  • Etape 2 : flasher le BIOS
    • Télécharger le BIOS sur Acer Support, la version 1.09 a correctement fonctionné et s’est installée sous W10x64.
    • Rebooter Windows 10 en mode Command Prompt (faire Shift + Eteindre, et ensuite choisir le bon menu)
    • Flasher depuis Windows le BIOS, en mode Windows (pas DOS). Il faut prendre le bios en .EXE dans WinFlash64
    • Éteindre la machine, retirer le courant et l’écran externe.
    • Redémarrer, l’écran principal doit à nouveau fonctionner, mais en mode VGA basse résolution.
    • Le Bios doit à nouveau fonctionner, et l’on peut rentrer dedans avec F2 (et parfois F12 offre le choix des boots aussi).
  • Etape 3 : remise en service
    • Installer le driver official de AMD pour Radeon Mobile HD5470 (HD5000 family).
    • Rebooter, nettoyer, vérifier Windows de façon générale.

Changement carte mère, injection drivers SATA Windows 7

Passage d’un disque d’une machine à une autre :

Cloner le disque complet avec CloneZilla

Si possible le télécharger et l’installer sur une clef USB, depuis un PC Windows, avec l’outils TuxBoot

Faire le clone du disque. Il ne bootera probablement pas (écran bleu). On peut désactiver le redémarrage automatique pour voir le code erreur, très probablement un code 0xxxxxx7B. Manque le driver pour accéder au disque correctement.

Sur une autre machine, extraire les drivers en question. Par exemple les drivers Intel Chipset, il faut faire un setup -a pour extraire le tout dans un dossier, genre 94 drivers en 64bits.

Rebooter en mode « repair » (premier choix), puis entrer l’utilisateur / mot de passe, puis choisir l’option la ligne de commande. Confirmer le disque système cible (C: normalement) ainsi que la clef USB. 

Intégrer les drivers dans le système Windows existant non bootable avec :

dism /image:c:\ /add-driver /Driver:D:\drivers /recurse

Faire un exit / reboot, la machine devrait booter, puis rajouter les autres drivers manquants (vidéo, wifi, son, etc…)

HTTPs armoring

So Mozilla is offering a nifty HTTPs testing tool at https://observatory.mozilla.org/ 

After I tried that, had to fix a few things :). D- rating (ouch !)

HTTP Strict Transport Security

First enable the header module with command line :

a2enmod headers

Then edit the vhosts files into the /etc/apache2/sites-available by adding the header entry (right below the VirtualHost entry)

Header add Strict-Transport-Security: « max-age=31536000;includeSubdomains »

And restart Apache 2 with :

systemctl restart apache2

And then check if nothing is wrong in the startup by looking into the log file for the daemon at :

less /var/log/daemon.log

Implement HTTP Headers

Install the WordPress extension HTTP Headers from Dimitar Ivanov. In the security options, turn ON the following restrictions :

X-Frame-Options DENY
X-XSS-Protection 
X-Content-Type-Options nosniff

And rescan….

That is how you end up with a A+ Rating.

(Don’t celebrate too much, my website rolled down from A to D- in…. 11 months between November 2016 to November 2017… looks like a fight to keep up and have a recheck every 6 months !).