Siduction Forum
Siduction Forum => Installation - Support => Topic started by: jyp on 2016/12/10, 19:52:27
-
Hi everybody
Just bought a Thinkpad T460 and was very keen to install siduction on it.
I removed the original hdd with Windows and replaced it with a Samsung ssd; also upgraded the memory to 16G.
The machine boots fine from the usb drive with siduction on it.
The installation was always successful (I tried many times either with efi or legacy only). In the "BIOS" settings, I tried to get rid of anything related to Windows (secure boot ... etc).
The machine does not boot from the local ssd; I always get a silly screen asking to choose the boot device and choosing the Samsung ssd only brings back the same window over and over. I search the forum and found some advice but always the same result. I am at lost. Any idea?
Thank you.
Here are the details
siducer@siduction:~$ inxi -F
System: Host: siduction Kernel: 4.4.0-towo.1-siduction-amd64 x86_64 (64 bit) Desktop: KDE Plasma 5.4.3
Distro: siduction 15.1.0 Paint It Black - kde - (201601162135)
Machine: System: LENOVO product: 20FNCTO1WW v: ThinkPad T460
Mobo: LENOVO model: 20FNCTO1WW v: SDK0J40700 WIN Bios: LENOVO v: R06ET46W (1.20 ) date: 11/15/2016
CPU: Dual core Intel Core i5-6200U (-HT-MCP-) cache: 3072 KB
clock speeds: max: 2800 MHz 1: 499 MHz 2: 499 MHz 3: 499 MHz 4: 499 MHz
Graphics: Card: Intel Sky Lake Integrated Graphics
Display Server: X.Org 1.17.3 drivers: intel (unloaded: fbdev,vesa) Resolution: 1920x1080@60.02hz
GLX Renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2) GLX Version: 3.0 Mesa 11.1.1
Audio: Card Intel Device 9d70 driver: snd_hda_intel Sound: ALSA v: k4.4.0-towo.1-siduction-amd64
Network: Card-1: Intel Ethernet Connection I219-V driver: e1000e
IF: enp0s31f6 state: down mac: c8:5b:76:91:49:76
Card-2: Intel Wireless 8260 driver: iwlwifi
IF: wlp4s0 state: up mac: f0:d5:bf:1d:ad:8a
Drives: HDD Total Size: NA (-) ID-1: /dev/sda model: Samsung_SSD_850 size: 512.1GB
ID-2: USB /dev/sdb model: DataTraveler_3.0 size: 7.7GB
Partition: ID-1: / size: 14G used: 75M (1%) fs: overlay dev: N/A
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 28.0C mobo: N/A
Fan Speeds (in rpm): cpu: 0
Info: Processes: 191 Uptime: 12 min Memory: 643.7/15487.2MB Client: Shell (bash) inxi: 2.2.32
root@siduction:/home/siducer# fdisk -l
Disk /dev/sda: 477 GiB, 512110190592 bytes, 1000215216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: CA25ED4F-3002-4B60-9890-DDF603C8DEA0
Device Start End Sectors Size Type
/dev/sda1 2048 102402047 102400000 48.8G Linux filesystem
/dev/sda2 102402048 143362047 40960000 19.5G Linux swap
/dev/sda3 143362048 983042047 839680000 400.4G Linux filesystem
-
Did you try installing, say Ubuntu, for testing?
-
Hi devil
No, I have not tried Ubuntu because using siduction kind of spoils you ;-)
Asking to boot from hard drive does not work.
Choosing _hardware detection_ from the live usb and checking Disks, I get the following:
>Disk 2
Disk 0x81 (EDD30)
...
MBR: Grub 2
> Partition 1
...
type: indication that this is legacy MBR
boot flag: No
...
Using gparted, I flag the first partition with boot.
Thanks for the quick reply
-
Set the bootflag!
-
Using gparted, I put the boot_legacy flag on /dev/sda1
Did a new install.
Same result :-(
Tried using fdisk (x for expert mode, A for the boot flag) but no success. The ssd still does not boot.
The new version of fdisk does not offer the usual simple command (_a_ to toggle boot).
Maybe there is a better way that I am not aware of. I will keep trying but...
Thanks towo
-
The simplest way is using cfdisk.
-
Problem solved :-)
@devil: no need to test with ubuntu, siduction is more than good enough thank you!
@towo: setting the boot flag was the trick of course. Following your advice in another post, I went the legacy way.
Using fdisk I created a fresh partition table <o>; then the option <a> to put a boot flag became available and this solved the problem.
Thank you all.
-
that without been forced to re-install after fdisk usage ?
thanks
-
It was a fresh install on a thinkpad t460.
After, I did <apt-get dist-updgrade> (not yet used to apt) that went perfect (even with more than 1500 pkgs) except for the manpages (upgrade warnings today).