Big Big probs with leap anyone help...

English Install/Boot/Login
1

Having tried to install leap for the last 7 hours I have given up, shame
really.

Here in no particular order is the problem, first my setup though:

Toshiba 4 core Intel laptop 8gigs ram 1Tbyte drive sda with 13.2 on only
using uefi. external usb keyboard that is internally lit and usb mouse.

External 2 Tbytes USB3 drive sdb that has been running Tweed for quite a
while like it a lot, I booted by changing the order in bios and from uefi to
standard. install was longish in the hardware detection but not bad.

All hunky dorey there, all hardware recognised superb performance, no
complaints.

Yep here it comes…

Thought I would wipe and try 42.1.

D/L`d this morning imaged onto 8gig stick all checked fine.

booted from stick, three dots stopped and no further action, now I had seen
about the long time so flipped console and saw that iwas getting there BUT
for over an hour!!! I mean WTF is a first time person sat there watching
nothing going to do Ctrl+Alt+DEL.

Anyway it eventually deigned to go through the install, I let it do it all
except I had to change the partitioning from sda drive to sdb no biggy I
knew I would have to. I told it to format the root partition which was ext4
and keep it ext4 ( I have had bad times with btrfs )

came to boot and the sda uefi menu gave me the option of booting both
systems, here we go I thought very smooth, unfortunately it could not find
the drive because there were no usb modules loaded yet.

Thought I would give it another go at installing and change to normal boot
in bios with usb as top booter, not a sausage the same thing but different
version so that was 4 hours, d/loaded a fresh image ( just in case ) and
there is no way I can get this thing to boot as it is an infinite loop, need
usb module but usb module is on usb drive… so now I have just got back
into 13.2 had a look at the external drive and it was even formatted, there
are still files there from weeks ago alongside the new ones. Oh I could not
even get the rescue disk to see the drive to fix it and install a normal grub
on there.

Am I pi55ed you bet, that was 6 hours wasted, at least I will have Tweed on
there in the next hour.

If anyone can shed some light while I put the installer on a stick please
do.

Thanks, no that is not a smile that is a grimace :slight_smile:

Cheers.

–
Mark
Nullus in verba
Caveat emptor
Nil illigitimi carborundum

2

On Tue, 28 Jul 2015 16:43:06 +0000, Baskitcaise wrote:

> Having tried to install leap for the last 7 hours I have given up, shame
> really.

Hey, Mark -

Remember that this is still very early days for Leap - these are
milestone releases, so anything you run into like this really should have
a bug logged for it so it can be tracked and resolved.

Jim

–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

3

Jim Henderson donned his tin foil hat and penned:

> On Tue, 28 Jul 2015 16:43:06 +0000, Baskitcaise wrote:
>
>> Having tried to install leap for the last 7 hours I have given up, shame
>> really.
>
> Hey, Mark -
>
> Remember that this is still very early days for Leap - these are
> milestone releases, so anything you run into like this really should have
> a bug logged for it so it can be tracked and resolved.
>
> Jim
>
>
>

Hi Jim,

I have tried again to install and got the same results so took a walk, bit
of fresh air helped.

I remember having the same problem with 13.2 or 3 I think even though this
is all different hardware and I filed a bug report then.

However Gurgle does not remember and it has a better memory than this old`un
here does :slight_smile:

If I remember right I had to edit something in grub or a kernel param, but
the situation is slightly different now as I cannot get to the o/s on the
lappy unless I let grub start and quickly choose the laptop version because
now if I try without the external plugged in there is no boot just a drop to
a grub prompt.

I managed to get the journal log which just loses the drive half way through
the kernel load, I am sure one of the lads here told me to add a kernel
param but first I will have to get my uefi boot working on sda ( at the moment
it will be a bit awkward carrying all this lot around :slight_smile: just to pick up
mail. That is no problem I hope.

Anyway a good cup of java and maybe some of your nice chillies might get the
grey cells going.

I am just annoyed with myself for not remembering how I did it last time.

Cheers matey, catch ya later it looks like it might be a long night.

–
Mark
Nullus in verba
Caveat emptor
Nil illigitimi carborundum

4

Baskitcaise donned his tin foil hat and penned:

> I am just annoyed with myself for not remembering how I did it last time.
>
> Cheers matey, catch ya later it looks like it might be a long night.
>

Star date 03:30 am next day here in Wales :slight_smile:

Things went from bad to worse after I posted that last and this is for
anyone who might get in the same situation.

I tried one last ime and still no joy so pulled the external out of the loop
went back to 13.2 on internal and nothing, zip, nada.

Not even a boot screen, just a gnu message and a bash prompt gently flashing
I immediately thought there might be something hardware wise on all this
lovely new hardware.

Booted with my trusty live usb stick and all seemed fine ran mem checks and
every thingso plugged the external in and tried to boot, when it came to the
boot screen for 42 on a whim I chose 13.2 instead and it booted fine.

So now with the external out it would not boot but with it in it would, I
tried re-installing the bootloader using yast which went alright and re-
booted and nothing but a prompt plug the external in and it would boot 13.2
off the internal.

I have been round the interwebs, read reams of docs about uefi and posts but
could not seem to get anywhere at all, the file structure on sda3 (my / ) was
OK everything in boot was as far as I could see OK the EFI fat partition had
all the right files in all the right places I even tried to manually edit
individual parts of the disk as I thought it could be rooted, I could not
see how because I had not had 13.2 running for weeks, had not thrown it
across the room in temper because 42 was not playing for me or anything like
that but it would only boot it if the external was in and I used its loader.

I had even thought about rootkits.

Now here is the reason for the long post and it is praise for one of you lot
from way back in 2012 “caf” had helped a few people with a similar but not
the same problem, his fix did not help me but one of the posts mentioned
something about “GRUB” not playing nice with uefi and BINGO! I thought I had
better check and lo and behold it had got onto my 13.2 install, I do
remember that when I had gone first back to 13.2 when 42 would not work that
there was a load of updates waiting and it must have got on there and I took
no notice, I just did not know about the problems and when I was looking in
/boot and the EFI partition saw “GRUB” just assumed it was supposed to be
there, just uninstalled it and everything is fine again, I can boot 13.2 with
or without the external.

So thank you caf.

42 still will not boot but that can wait I wonder if I try and install again
it might :slight_smile:

So I may be old and slow like the proverbial tortoise but I got there in the
end and have learned a lot about bootloaders I did not know before.

Cheers lads and ladies. Good night or morning should I say.

–
Mark
Nullus in verba
Caveat emptor
Nil illigitimi carborundum