Intenso Tab 814 Firmware Download
Osoulo Lejeune
You mean .config/hosts.conf ?
No, the Fritz Box is not there.
I should try what you said. The IP of the router instead of the name resolution, in the sources.xml and the passwords.xml.
Thanks.
I will get back with feedback.
Kodi SMB settings: min SMB2, max SMB3
Sources.xml and Passwords.xml files edited to add manually the sources paths with the IP of the router (instead of the Name) + username and the password that SMB2 requires (as browsing is not allowed). Library was cleared before I applied the new .xml files.
the mystery with the advancedsettings.xml file has not been solved. Eventually I had to delete it, for everything to work. Otherwise most of my video files were just not playable. The system would even hang some times with that file in place. I tried various versions of it without success. Still makes me wonder how come the .xml file did not cause problems with the current / older stable firmware of the router, but brings up huge issues with the new BETA firmwares (that will become official soon).
Hi there.
Whatever number I put in the buffermode tag, the same issue occurs.
Furthermore, I wanted the caching for the local (SMB lan) files, as I mostly watch local videos / movies.
My TV Box has a 100 lan card so I had some buffering in the past with some videos.
SOLUTION for me was to update the firmware on my ASRock mb as thatu pdate changed the EFI software (by American Megatrends) version from 2.00 to 2.31. However, other users are still experiencing the blue screen.
LONG VERSION
I made an USB installation media (product: Intenso Rainbow) by following this advice on the wiki.
I used the july release of Arch for that. First of, after installing the image to the USB stick I found that I needed to correct the label in the archiso-x86_64.conf file to ARCH_201307 (or was it the label of the usb stick, can't remember right now). (Pretty sure it was the same problem with "Linux Live USB Creator" which I used 3-4 months ago...)
After doing that, I rebooted and selected the entry
But just to make sure, I then did the check for UEFI mode according to this and only saw a folder acpi and ... something else I can't really remember, but it definitely was not efi. Thing is, I needwant to boot into UEFI mode as I have Win 7 already installed in UEFI mode.
Some info about my motherboard: it's from ASRock and is called H67M. The BIOS is dated to 2011-10-26 and is version 1.7.
The only reference I can find to that error message is in the source code to PreLoader.efi, the Linux Foundation's Secure Boot loader. It indicates that the program was unable to register itself as an extension to the firmware's built-in Secure Boot functions. This error is quite rare. As the developer of rEFInd, I'd be interested in knowing what firmware you've got (make and model of motherboard, as well as the publisher of the firmware and its version number). I also strongly recommend you e-mail Matthew Garrett and James Bottomley; they're the developers of shim and PreLoader, the two Linux Secure Boot solutions released to date. Both are likely to be interested in knowing about this failure, because it affects future directions for their Secure Boot solutions.
It's conceivable that a firmware upgrade would fix this problem, but I can't make any promises about that. If a firmware upgrade doesn't help, I recommend you disable Secure Boot in your firmware. Alternatively, you could try installing using shim rather than PreLoader; shim uses a different method to work around Secure Boot problems. Yet another option is to install your own keys in the firmware, but this procedure is quite tedious. Unless you really want to avoid using Microsoft's keys, this method is likely to be too much effort.
Just for the record: same happened with an USB stick created with Linux Live Creator (after adjusting the stick's label to 'ARCH_201307'). ... what I'm wondering is, what was different (in relation to the issue) with the Arch Linux image file from march?
Hm, can't I just install Linux in "normal" non-UEFI mode and then do something to make it work once I boot into UEFI again?
With an USB installation media created with Linux Live Creator and the 2013.06 Arch Linux version, it still does not work but after selecting
UEFI: Intenso Rainbow
it goes to a screen where 3 entries are shown, the first being Arch (x86_64) and then the two "UEFI shell" entries (v1, v2). After selecting the first entry, it just goes to a black screen.
Chances are you're running PreLoader.efi, since it's very unlikely that anything else would use the exact phrasing "Failed to install override security policy." It might not be stored on your boot media under that filename, though. It sounds like this message isn't causing any real harm, though, since from your description, you're getting to a regular gummiboot menu thereafter. Neither your original post nor your post on SuperUser mentioned an inability to boot beyond that point; but your post #5 in this thread says you're getting a black screen when you select the Arch option. That is the problem, not the PreLoader.efi message. You can remove the PreLoader.efi file, of course (although it's probably stored under another filename), but I doubt if that will do anything but remove that one error message. See my Web page on Secure Boot for more information on PreLoader generally.
As to Arch producing a black screen when booting, there have been similar reports on this forum and elsewhere. Sometimes adding a boot option, like "nomodeset" or "noefi", can fix the problem. (Note that "noefi" disables access to EFI features, though, which means that the efibootmgr utility won't work.) Details vary from one computer to another, though. It's also possible you're running into this problem, which unfortunately isn't really fixed. One workaround is to try another boot loader, though. GRUB usually works, although I've seen recent reports of GRUB problems.
Thanks for clearing up the black screen problem. Actually, I wouldn't mind sending off 2 mails to the devs about the PreLoader.efi problem but I honestly can't find their addresses (which certainly has a good reason).
Ok, after more research I get that there are some users who played around with boot options for USB sticks... sort of. I can't really pinpoint how to reproduce those steps by working with Win 7 and either win32diskimager or Linux Live USB Creator. I'll guess I give it another try with a Xubuntu usb stick to test things, maybe that'll lead to something. I am not going to use rEFInd as that most likely won't work, tried it out already and didn't get anywhere.
Ok, so booting Xubuntu 13.04 in UEFI mode from a USB stick worked flawlessly. It flashed a short message "Secure Boot not enabled" on a black screen and then just loaded up quickly. Although I do not have any possibility to enable Secure Boot (according the motherboard's manual), this reassurance is good.
Typically, you adjust kernel boot options using your boot manager or boot loader. In GRUB, you hit the "e" key to open an editor. In rEFInd, you hit F2 or Insert twice. I don't recall offhand what key does the job for gummiboot (which I'm pretty sure the Arch installer uses), but I'm certain it's got the feature.
That first one (for Garrett) may not be current, though; he switched jobs recently, from Red Hat to a startup called Nebula. I don't think posting the addresses here is a problem since the source code is readily available on the Web and therefore trawlable by spam-bots.
You are right. Thanks. I realized I had the gummiboot config right in front of me all the time. It's the file 'archiso-x86_64.conf' in \loader\entries (on Windows).
An addendum: I think the USB: Intenso Rainbow boot option takes me into a GRUB menu. Hitting 'e' in this "big" and fully designed menu didn't do anything IIRC. Hitting 'Tab' did the trick to get into editing the boot command line.
Hitting 'e' worked in the gummiboot menu though.
To be rather safe than sorry: I should mention that there are two grey-ish bars visible on the top and bottom of the screen after I try to boot the first entry, Arch Linux archiso x86_64 UEFI USB. Always has been with those two older Arch version (2013.05+2013.06). I also found another thread where one user talks about using the VGA port of the monitor, which I am currently not, I am using the DVI one, so that's worth a try too. EDIT It did not help either. What I did was setting the primary graphics adapter in the UEFI north bridge configuration menu to 'onboard' which worked immediately when rebooting (I hit the button labeled "Source" on my monitor and it showed it is using the "Analog" mode), but the problem just stayed the same. Adding aforementioned boot options or a combination thereof did not change anything.
I'm wondering if any of the previous ISOs have worked, as I'm sure someone has installed Arch on these motherboards before, but the only posts about this problem have been since the 2013.07.01 release.
The "solution" for me was to update the motherboard's firmware. As the firmware was updated from 1.70 to 2.10, the EFI version was updated from 2.00 to 2.31. The USB flash drive with 2013.07 now boots flawlessly in UEFI mode (did not try again with 2013.06). However I didn't really do any specific steps to solve any issue possibly directly related to the blue screen or Rod's notations about the PreLoader.efi file.
1) This device does not have sufficient resources (flash and/or RAM) to provide secure and reliable operation.
This means that even setting a password or changing simple network settings might not be possible any more, rendering the device effectively useless. See OpenWrt on 4/32 devices what you can do now.