Siduction Forum
Siduction Forum => Installation - Support => Topic started by: eriefisher on 2020/05/02, 22:47:47
-
Following up on a wifi issue with the Xfce4 iso I decided to install it and upgrade the kernel to attempt to fix it.https://forum.siduction.org/index.php?topic=7966.0Well (https://forum.siduction.org/index.php?topic=7966.0Well) I never got that far. Install seems to go smoothly until 95%, installing boot loader, and then it locks up solid requiring a power button reset. I tried to install the boot loader manually in the live usb but with the same results. Full on Lock up. It looks like all the files are there. I did have some trouble with the installer, it wouldn't let set the esp flag to sda1. I used gparted to create the partitions and mark the flags and everything went ok until the boot loader lock up.
Am I doing something wrong here? I did have a similar issue when I originally installed MX-18 on this laptop(Acer Aspire ES 15) but was able to install the boot loader manually and carry on.
Any insight would greatly be welcomed.
-
Try the cli-installer
apt install cli-installer
As root (su) run cli-installer
-
I saw that and was just about to when I got the post notice. Thanks. I will report results.
-
We'll, I had to try again a few times. Both graphical and cli-installer and still won't boot. "No Bootable Disc". The last attempt with the cli-installer at least completed but no boot. I'm out of ideas here. Any suggestions? I came across dibl's bit of code to reinstall the boot loader, it completes but no boot.
Would be nice to get this sorted and not go back to where I was.
-
Some questions.
uefi?
secure boot?
installed grub to the mbr or partition?
dual boot?
-
Answers:
Yes UEFI.Secure boot disabled.cli-installer did not give me the option of where to install grub.Single OS not dual boot.
From a live session;System:
Host: siduction Kernel: 5.5.4-towo.1-siduction-amd64 x86_64 bits: 64
Desktop: Xfce 4.14.2
Distro: siduction 18.3.0 Patience - xfce - (202002161827)
Machine:
Type: Laptop System: Acer product: Aspire ES1-533 v: V1.08
serial: <root required>
Mobo: Acer model: Stego_AP v: V1.08 serial: <root required> UEFI: Insyde
v: 1.08 date: 01/20/2017
Battery:
ID-1: BAT1 charge: 33.7 Wh condition: 33.7/36.7 Wh (92%)
CPU:
Topology: Dual Core model: Intel Celeron N3350 bits: 64 type: MCP
L2 cache: 1024 KiB
Speed: 2087 MHz min/max: 800/2400 MHz Core speeds (MHz): 1: 2175 2: 2013
Graphics:
Device-1: Intel HD Graphics 500 driver: i915 v: kernel
Display: x11 server: X.Org 1.20.7 driver: modesetting unloaded: fbdev,vesa
resolution: 1366x768~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 500 (Broxton 2x6)
v: 4.6 Mesa 19.3.3
Audio:
Device-1: Intel Celeron N3350/Pentium N4200/Atom E3900 Series Audio Cluster driver: snd_hda_intel
Sound Server: ALSA v: k5.5.4-towo.1-siduction-amd64
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
driver: r8169
IF: enp1s0 state: up speed: 100 Mbps duplex: full mac: fc:45:96:e6:c1:88
Device-2: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi
Drives:
Local Storage: total: 480.72 GiB used: 90.5 MiB (0.0%)
ID-1: /dev/sda vendor: Western Digital model: WD5000LPCX-21VHAT0
size: 465.76 GiB
ID-2: /dev/sdb type: USB model: USB Flash Memory size: 14.96 GiB
Partition:
ID-1: / size: 3.30 GiB used: 90.5 MiB (2.7%) fs: overlay source: ERR-102
Sensors:
System Temperatures: cpu: 41.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 170 Uptime: 13m Memory: 3.67 GiB used: 892.0 MiB (23.7%)
Shell: bash inxi: 3.0.37
Partitions:root@siduction:~# parted -l
Model: ATA WDC WD5000LPCX-2 (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 538MB 537MB fat32 esp boot, esp
2 538MB 1075MB 537MB ext2 boot
5 1075MB 32.5GB 31.5GB ext4 root
6 32.5GB 105GB 72.6GB ext4 home
4 105GB 498GB 393GB ext4 data
3 498GB 500GB 2147MB linux-swap(v1) primary swap
-
hi,
looking at the sheer amount of partitions, i would recommend a trial install with a "simpler" setup, and see whether that works or not. how about only two partitions?
1. / (boot, root, home, etc...)
2. data
best
absolut
-
did you try
grub-install --no-uefi-secure-boot ......
?
-
Yes. That was going to be my next step. Remove everything. Back /data up of drive and start fresh with /esp /root and /home.
-
HendrikL, no I didn't. You need to chroot into the /root for that yes?
-
I do not have a modern uefi system, but I assume yes.
And there is no need for a separate /dev/home partition only for an extra /dev/data-grave for your personal stuff, my two cents. An extra home is only wasting hdd/ssd space ;) and useless.
If you ever install new, in 99% of cases you can't use the old settings and all important things like ~/.gnupg, .~/ssh and so on can be placed in the /data-grave and linked back to ~/.
-
OK, I'm 99% there. If I try and do a normal boot I get "NO BOOTABLE DISC". If I boot from the usb and select "detect efi boot loader" and select the correct one I can boot to the installed system. It seem to work normally. No boot error showed up that I saw.
Also, I installed the suggested kernel to get wifi working and now have a good, strong and stable wifi connection.uname -r
5.6.8-towo.2-siduction-amd64
Does anyone have a suggestion to move on from here to get this laptop to boot normally? Through all my attempts this is the closest I've been. Like I mentioned, whether the graphical or cli-installer I get a full system lock up at the boot loader installation. Even trying to install manually I got a lock up. There was a couple times it did complete but there was nothing there so it actually didn't complete.
side note: I was planning on wiping the whole drive to simplify the partition scheme but tried the install one more time and got here. So I still have the posted partitions.
-
I don't own a laptop, or a uefi motherboard
I would try and install again without a home partition, if that don't work , I would wipe.
My thing with home is it does more harm than good
I don’t use a separate /home, I have a partition > /my shit < that has all my stuff like > /my shit/movies < and > /my shit/music < etc....
/home has settings that can be os dependent/package version dependent. I have seen some messed up things with /home, especially mixing one from a different distro or using one spread out across the system using many distro's.
Just not worth it to me. The problem using /home from a "stable" version to a "rolling release" version is asking for trouble imho (.kde, apps, config, etc.) different version number of apps(stable, ubuntu would be much older), dependencies (stable, ubuntu would not be up to date, etc) installing a /home is like driving a ford pinto.
I and others here have seen many problems with home
my 2¢
-
Thanks for the input Piper. I agree with you. I still plan on wiping everything and start fresh like you mentioned. I just needed to see it I could get this to boot first.
By the way, i owned a pinto a little over thirty years ago.
-
Yeah, I did too, a wagon
I also owned a corvair spyder
-
Update: Since I got it to boot I thought I would test a D-U. There was an update for grub and a full lock up. WTF!
-
You did get the iso from
https://isobuilds.siduction.org/
right
siduction-patience-xfce-amd64-latest.iso 2020-02-16 19:36
That was a apt dist-upgrade and not a apt upgrade right
-
Yes. HendrikL pointed me there on my original thread when I questioned the age of the one I originally found.
https://isobuilds.siduction.org/ (https://isobuilds.siduction.org/)
-
Ok, just making suree, sorry I can't be of any more help
I can boot but I don't have a uefi board or laptop so that don't help you
-
Well I'm officially siducing. It finally booted into the hard drive with a little help from MX-19 Linux. I remembered when I first installed MX I had a similar issue. This was the first time with UEFI. Siduction my second. MX has a tool installed by default that did the trick. I couldn't find it or something similar in siduction so I loaded MX19 onto a usb and booted it up ran the tool, rebooted into siduction no problem. See "chroot-resue-scan"
https://forum.mxlinux.org/viewtopic.php?f=92&t=50884&hilit=eriefisher
When I installed MX the laptop froze up at about the same point during the boot loader install so I'm assuming there is something about the Acer UEFI that grub is having an issue with. I did notice that the boot loader was not being labelled with siduction. Unknown if this is related or not. Anyway I'm up and running and if I can help out in anyway let me know.
-
A better link for "chroot-rescue-scan"
https://mxlinux.org/wiki/system/chroot-rescue-scan/