You are Here:
Linux Lite 4.4 Final has been released. See the Release Announcements section for more information.



BIOS problem

Author (Read 1637 times)

0 Members and 5 Guests are viewing this topic.

Re: BIOS problem
« Reply #15 on: June 04, 2019, 05:26:18 AM »
 

minesheep

  • New to Forums
  • *
  • 48
    Posts
  • Country: fi
  • Reputation: 6
  • Linux Lite Member

  • Linux Lite: 4.4 64bit

  • MEMORY: 4Gb
I was unable to use terminal effectively because the keyboard was garbled (e.g sudo blkid was showing as s4d6 fd5s2).
sudo's ascii is 115, 117, 100, 111 and in binary it is 01110011, 01110101, 01100100, 01101111
s4d6's ascii is 115, 52, 100, 54     and in binary it is 01110011, 00110100, 01100100, 00110110

Also pretty weird to note that "d" in sudo was registered as d but in blkid it was reqistered as "2"

d have ascii (in lower case) 100 and 2 have ascii 50
so d in binary         01100100
     2 in binary         00110010

looks like your keyboard cable is moving to wrong location inside your laptop. It probably have like 8 or 10 thin cables to move key presses to computer from keyboard and these cables may be shifting.
 


Re: BIOS problem
« Reply #16 on: June 04, 2019, 06:25:38 AM »
 

DeepThought

  • Forum Regular
  • ***
  • 150
    Posts
  • Country: wales
  • Reputation: 30
  • Linux Lite Member
    • WKDfm Radio | WKDfm Chat

  • Linux Lite: 4.2 64bit

  • CPU: AMD Turion(tm) 64 x 2 Mobile Technology TL-60

  • MEMORY: 4Gb

  • VIDEO CARD: ATI RS480
@pelouk  @minesheep   The garbled message is probably because Linux Lite has Numlock enabled as default in a live session.
You can disable Numlock using one of your keyboards Fn keys.

An ssd would be a good option.
Owner and DJ at WKDfm Radio ( www.wkdfm.co.uk )
 

Re: BIOS problem
« Reply #17 on: June 04, 2019, 07:09:48 AM »
 

minesheep

  • New to Forums
  • *
  • 48
    Posts
  • Country: fi
  • Reputation: 6
  • Linux Lite Member

  • Linux Lite: 4.4 64bit

  • MEMORY: 4Gb
@pelouk  @minesheep   The garbled message is probably because Linux Lite has Numlock enabled as default in a live session.
You can disable Numlock using one of your keyboards Fn keys.
No numlock won't turn letters into numbers

d in binary         01100100
2 in binary         00110010

All bits have moved to right it is (clear) contact issue.
 

Re: BIOS problem
« Reply #18 on: June 04, 2019, 11:31:55 AM »
 

pelouk

  • Occasional Poster
  • **
  • 62
    Posts
  • Reputation: 2
  • Linux Lite Member
Hi DeepThought and minesweep.  I managed to release the Num lock and got the keyboard going - I'm actually sending this using Firefox on the laptop. Re-trying the terminal instructions produces the following:-

inux@linux:~$ sudo blkid
/dev/sda1: LABEL="LINUX LITE" UUID="E613-A103" TYPE="vfat" PARTUUID="006d6afc-01"
/dev/loop0: TYPE="squashfs"
linux@linux:~$


linux@linux:~$ sudo fdisk -1
fdisk: invalid option -- '1'

Usage:
 fdisk [options] <disk>      change partition table
 fdisk [options] -l [<disk>] list partition table(s)

Display or manipulate a disk partition table.

Options:
 -b, --sector-size <size>      physical and logical sector size
 -B, --protect-boot            don't erase bootbits when create a new label
 -c, --compatibility[=<mode>]  mode is 'dos' or 'nondos' (default)
 -L, --color[=<when>]          colorize output (auto, always or never)
                                 colors are enabled by default
 -l, --list                    display partitions end exit
 -o, --output <list>           output columns
 -t, --type <type>             recognize specified partition table type only
 -u, --units[=<unit>]          display units: 'cylinders' or 'sectors' (default)
 -s, --getsz                   display device size in 512-byte sectors [DEPRECATED]
     --bytes                   print SIZE in bytes rather than in human readable format

 -C, --cylinders <number>      specify the number of cylinders
 -H, --heads <number>          specify the number of heads
 -S, --sectors <number>        specify the number of sectors per track

I can't, of course decipher that and still suspect the hard disk is knackered. What do you reckon?
 

Re: BIOS problem
« Reply #19 on: June 04, 2019, 12:10:39 PM »
 

DeepThought

  • Forum Regular
  • ***
  • 150
    Posts
  • Country: wales
  • Reputation: 30
  • Linux Lite Member
    • WKDfm Radio | WKDfm Chat

  • Linux Lite: 4.2 64bit

  • CPU: AMD Turion(tm) 64 x 2 Mobile Technology TL-60

  • MEMORY: 4Gb

  • VIDEO CARD: ATI RS480
@pelouk

Code: [Select]
inux@linux:~$ sudo blkid
/dev/sda1: LABEL="LINUX LITE" UUID="E613-A103" TYPE="vfat" PARTUUID="006d6afc-01"
/dev/loop0: TYPE="squashfs"
linux@linux:~$

That shows your usb drive with Linux Lite.
Your internal hdd is not showing so I would say it has failed.

The sudo fdisk -l command is actually a small L not 1, but using the command will probably give you the same result and not show your internal hdd.
Owner and DJ at WKDfm Radio ( www.wkdfm.co.uk )
 


Tags:
 


Linux Lite 4.4 Final has been released. See the Release Announcements section for more information.