Skip to main content

FrameBuffer in Backtrack

Recently I had BT5 R3 installed on a Dell Latitude laptop, and it was working fine.  Then I needed to clone the hard drive, so I used DiscCopy 2.3 to copy the drive--No issues. 

However, when I went to boot back into my BT install, the screen was all messed up immediately after it hit the splash screen.  I couldn't figure out how this happened, as I didn't mess with the OS at all (I copied the drives outside of the OS, booting to the DiscCopy CD).

Initially I was worried I had a hardware failure, so to test it I booted into the original Windows 7 Drive that came with the laptop (when I installed BT I set that drive aside, as I don't normally use Windows).   Windows 7 booted fine--no hardware failure.  

However, when I booted to a BT instance I had happened to have installed on that same Windows 7 hard drive, a drive that was cleanly working when I put it in storage, it had the same video problems!  

So my symptoms were that I had a video problem with BT only, that spanned across hard drives!  How the heck was that possible I wondered?  Turns out it was my FrameBuffer.   This is a hardware device that renders the graphics for the OS--thus it is hard drive independent, which explains why I had a problem that persisted across hard drives, and even with the BT bootable iso!  

So to fix this, I booted the BT bootable iso, but into "noDRM drivers" mode.  This allowed me to actually boot the previously unbootable BT iso, and mount the hard drive.   I then edited the /boot/grub/grub.conf file to say "vga=normal nomodeset"   The 'nomodeset' is key, as it told the OS not to load the framebuffer.   

I booted up, and Bob's your Uncle---BT is working again!  

Comments

Post a Comment

Popular posts from this blog

HP c6180 Printer and Vista

Hp c6180 driver issues with Vista Home Premium My wife has a Vista Home Premium laptop, and the HP C6180 Photosmart printer keeps disappearing from her available printers.  The only way I've found to fix the problem is to reinstall all the HP software. When I do this, I have to download the (large..507M software from HP, or reinstall the printer (ONLY the printer, not the scanner) with the installation disk, as the drivers are not discovered with a "Windows Update" setting.  My guess is that is because HP doesn't like people to install only the printer driver, which would be easy, but they want folks to install all their crapware as well, so they are withholding the drivers from the on-line Microsoft printer database.  So keep your installation CD!  I've also found that unless I install everything on the CD or in the Full Version download (HP Customer Participation Program, HP Imaging Device functions, HP OCR SW, HP All-In-one SW, HP Photosm...
27 comments
Read more

atftpd vs tftpd-hpa

Recently I was trying to tftp files from a Windows computer to a Kali box.   One version of Windows worked, but another didn't.    After much troubleshooting, here were my symptoms: I could tftp a file from-to any Kali box from-to another Kali box I could NOT tftp files to a specific Windows 7 box from any Kali box I could NOT tftp files to a Chrooted-Ubuntu-Chromebook box from a Kali box After MUCH troubleshooting, going through every setting in atftpd, it seemed like it literally was a client OS problem.  Different clients simply would not download files---unacceptable. Thus, I switched to tftpd-hpa.   To install: apt-get install tftpd-hpa files go to/come from /srv/tftp, but it needs to be a tftp user. Thus, I needed to: chroot -R /srv/tftp Also, if you want to be able to put files ON the tftp server (from a client), you need to modify /etc/default/tftpd-hpa: change "TFTP_OPTIONS="--secure"  to "TFTP_OPTIONS="--secure --create" ...
Post a Comment
Read more

Temper Temperature monitor on a Beaglebone Black

Beaglebone Black as a temperature monitor: Recently I wanted to monitor the temperature of my shed.  I thought I'd use a small computer such as a Raspberry Pi or a Beaglebone or Odroid. My Raspberry Pi boxes were all in use, so I grabbed my Beaglebone, which was doing nothing. I flashed it with the  Debian   9.3   2018-03-05   4GB SD   IoT   image, but that seemed like it was running lots of bloatware and the ethernet interface wouldn't take a static IP with /etc/network/interfaces. So I went with the  Debian   9.3   2018-01-28   4GB SD   LXQT   i  image instead.  I still had the same problem, that lots of junk was running, and I couldn't configure my interface by modifying /etc/network/interfaces So my first step was to get rid of all the bloatware.  If you're using a Raspberry Pi or something, you can skip this and just go to the second step below STEP 1--Remove Blotatware from Beaglebone Black...
6 comments
Read more