I have a new Toshiba C855D-S5900 with Windows 8 (present on the HD, but I have not accepted the EULA). When I try to use the install disks (tried both Net x86_64 and DVD x86_64) it only has 3 choices on the install screen - Installation, Rescue, and Check media. I have not been able to access any F-key commands or change the options of the 3 commands. When I clik any of the 3, it gets to:
Starting udev…
and halts with no messages.
With the KDE Live x86_64 it halts at approximately the same location, at: /usr/sbin/klogconsole
Do I need to accept the Microsoft EULA (Yecch …) and let it prep the disks before installing 13.1?
Problem is probably graphics and with a UEFI boot you don’t get the F keys. (Have no idea why not) But it is apperntly by design.
So what video do you have.
Note not sure this apply at the DVD boot or not
You may try editing the boot parameters/ press e at boot screen find the line that starts with linux press end key enter a space and nomodeset press F10 to boot
mount : using /dev/loop1
... ] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
... ] EDD information not available.
insmod: error inserting '/modules/edd.ko': -1 No such device
>>> openSUSE installation program v4.1.5 ...
Starting udev
The CPU/Video is: AMD E-Series Processor E-300/AMD Radeon™ HD 6310
Thanks, Do
If I understand you correctly, I don’t think that is correct. The F-keys during boot aren’t disabled, but the new PCs are so fast that the time window available for pressing F-keys to do anything is diminishing.
Also, several computers now come with so called multimedia keyboards. On laptops, that is implemented by “inverting” the F-keys functionality. That is, if you want to press an F-key, you need to press the <Fn>-key, then the <Fx>-key that you want. My Toshiba Satellite P50A is one of those. On my computer, to add to the confusion, pre UEFI loading, e.g. <Fn>+<F2> does not work. I have to press <F2> directly. Then, after UEFI has finished loading, I need to press <Fn>+<F2> in order to get the F2 functionality. The switch happens mid-boot. So how do you get to press the proper F-key within a time window smaller than the keyboard’s auto repeat rate? Not easy. Not easy at all.
Luckily, I can disable the multimedia keyboard by setting a BIOS parameter, thereby making F-keys available by direct press only. The multimedia functions are then available throgh <Fn>+<Fx> combination. Much better.
@DoitRight](https://forums.opensuse.org/members/doitright.html):
Maybe the multimedia keyboard is part of your problem. According to what I can see from the photos available from the link above, you have the same keyboard configuration - so maybe you can rectify it the same way as I can (see above).
Another thought: As a blind-test, try disabling your on-board 10/100Mbps LAN-adapter and try booting again. That may prove helpful, and too easy to execute before making further investigations to not to do it.
No the F keys in the Grub menu. They are not there for EFI installs which makes it hard to set noKMS to deal with problem video hardware on UEFI systems.
I had already reset the F-keys to the std usage (i.e. I need to push the Fn+F(x) button to access the extended usage such as dim the screen). Disabling the on-board lan adapter did not change anything. @gogalthor what other hw info do you need?
Thanks, Do
I think that’s a miscommunication. You are talking about F-keys, as supported by the hardware. But gogalthorp was talking about the boot loader support.
In a non-UEFI boot of install media, the boot loader is “syslinux” and the boot screen lists some F-keys. With a UEFI-boot, the boot-loader is grub2-efi, and there are fewer options on the boot screen.
With my Toshiba, at the installation DVD boot menu, if one presses ‘E’ one obtains the grub boot menu, which can be edited. Things like nomodeset can then be inserted.
Yes, I used nomodeset and it stopped at the same place. I didn’t explicitly state that I used it, just quoted your request and said it stopped at the same place.
It still stops at the Starting udev…
No one replied to the error I noted before the Starting udev (in #3). Is that a non-issue?
Thanks, Do
Not really but is why I thought maybe not a video problem but but then in again in might have been
Maybe possibly a mount problem. Can you see if the dvd will start on another machine. Don’t need to actually install just start the process to see if the DVD is ok.
On Mon 16 Dec 2013 10:26:02 PM CST, DoitRight wrote:
gogalthorp;2608993 Wrote:
> I suggested but not sure the op did it. But the errors reported really
> don’t look like video error. So ???
Yes, I used nomodeset and it stopped at the same place. I didn’t
explicitly state that I used it, just quoted your request and said it
stopped at the same place.
It still stops at the Starting udev…
No one replied to the error I noted before the Starting udev (in #3).
Is that a non-issue?
Thanks, Do
Hi
Have a look at pressing alt+F4 or F5 (can’t remember which one) to see
the boot log, I suspect it’s not finding usb devices or IRQ’s etc. Press
alt+F1 to get back. Is there a BIOS update available?
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
SLED 11 SP3 (x86_64) GNOME 2.28.0 Kernel 3.0.101-0.8-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
I successfully installed 13.1 from the DVD last week on a different Secure Boot/UEFI computer (Acer Aspire 1) from this DVD. [see: https://forums.opensuse.org/english/get-technical-help-here/install-boot-login/493062-installing-13-1-via-net-x86_64-cd.html]. I no longer have it to test because the owner took it back to the states. It took me awhile to find another 64-bit processor with a working DVD drive [problems of donated computers]. The DVD loaded up successfully, but the computer, while 64 bit, is well older than Secure Boot/UEFI issues.
Thanks, Do
You need to add “edd=off” to the kernel command line.
BIOS Enhanced Disk Drive Services causes problems with Linux in a variety of systems. It is an experimental disk controller option that is known to fail in some configurations, and in fact many disk controller BIOS vendors still don’t include this feature.
I’m going by an Ancient Memory Map, which never really did function flawlessly throughout the years, but I think I recall actually seeing an entry for it in the BIOS on one (or maybe more, who knows with MY memory holes ) of my current PCs where it could be disabled there. I could be mistaken, though. However, wouldn’t hurt for you to peek in your BIOS to see.
But, if not in the BIOS, that “edd=off” added to your kernel command line should get you up & running.
) of my current PCs where it could be disabled there. I could be mistaken, though. However, wouldn’t hurt for you to peek in your BIOS to see.