Then you guys are doing something wrong, I have upgraded my kernel twice in 12.04 LTS and haven't had any issues of the sort, though admittedly I'm using compiled XBMC instead of PPA.
Also have fixed a few problems with script which bram77 hasn't yet used. Though they were problems with apparmor being removed incompletely and because rsyslog wouldnt start after that. I fixed both of those though I cant see how those issues would cause this.
uNi
(2013-01-13, 11:44)uNiversal Wrote: [ -> ]Then you guys are doing something wrong, I have upgraded my kernel twice in 12.04 LTS and haven't had any issues of the sort, though admittedly I'm using compiled XBMC instead of PPA.
Also have fixed a few problems with script which bram77 hasn't yet used. Though they were problems with apparmor being removed incompletely and because rsyslog wouldnt start after that. I fixed both of those though I cant see how those issues would cause this.
uNi
you are a) on 12.04 instead of 12.10 b) compiling from git and not using the ppa c) using an updated script. not to mention likely running different hardware and having no idea if the same options were picked while the script was installing things. given all of these variables for you to say that something was done incorrectly is narrow-minded. i grant you that it doesn't seem like there should be an issue but something somewhere is causing an instability. i'm not even saying it's definitely something with the script. it could be plymouth (which imo should be an option and not something that is installed with no say by the end user) or something that the script installs that i didn't when i did things by hand.
My kernel has been updated on my current installation too (possibly multiple times). No problems whatsoever. I'm not sure what's going wrong in your case, but it's not related to the way Ubuntu or XBMC has been installed by using this guide/script.
I would like to ask everybody to report issues (+solutions and detailed description) using the issue tracker on GitHub. It's difficult to backtrack all reported issues and filter duplicates using this topic.
Sorry for the lack of updates recently. I've been extremely busy with my company and the holidays/festivities didn't help either. I want to continue development this week and it would be very helpful if the existing issues and feature request would be reported in a workable manner using the GitHub issue tracker.
Thanks!
https://github.com/Bram77/xbmc-ubuntu-minimal/issues
Hi Bram77!
Just installed from this guide.http://forum.xbmc.org/showthread.php?tid=141369
works fine...thanks alot.
just one question....when booting up it askes what to start...Ubuntu as first choice ....and does run after a few seconds.
But can i skip that for a faster boot direct to xbmc without se that upstartsequence?
Best regards
D
It normally doesn't ask you what you want to start unless the previous boot was interrupted somehow. Do you have a dual boot configuration (is another OS installed on the same system)?
(2013-01-14, 16:35)Bram77 Wrote: [ -> ]It normally doesn't ask you what you want to start unless the previous boot was interrupted somehow.
Bram
Is there a way to disable that behaviour? At our place in Thailand we get a lot of power cuts and brown outs, and I don't want to have to connect up a keyboard to get past this prompt to select Ubuntu to continue, can it be disabled altogether? So it will just boot back in to XBMC no matter what has happened.
Thanks
Really good respone here.....thanks alot =)
Now when u say it....Ubuntu found some old vista bootloader during installation.but i choose ofcourse ubuntu to be system.
(but since another user cw-kid also have the same problem maybe its not just my install?)
And i did choose to use entire disk.
So now when booting it says
Ubuntu
Advanced options for ubuntu
Memory test (memtest86+)
Memory test (memtest86+ serial consol 115200)
anyway to skip this stage ?
best regards
D
It's Linux, almost everything can be adjusted
. But I don't think there is a solution that allows you skip the grub menu after a power failure. Not that I know of anyway.
If Grub has found another OS it will show the Grub menu by default. Google for "Grub 2" combined with "Ubuntu server" and I'm pretty sure you'll find an answer to your question.
Why "Ubuntu server"? Because it has no windows manager and it's widely used. So the procedures will be the same as is the case with your installation.
Showing the Grub boot menu is NOT the default behavior. If it's showing it by default on your machine then your machine is the exception. Please use google to find a solution. Almost everything has been done before and almost everything is documented somewhere. The trick is to find it
Thanks Bram
My installation only shows the Grub menu if I kill the power during boot up. Other wise it boots normally in to XBMC.
I just followed this post here:
http://ubuntuforums.org/showpost.php?p=1...stcount=13
I did a hard reset of the PC whilst XBMC was running. It powered off, I then powered it back on and this time it did not get stuck at the Grub menu and instead booted right in to XBMC!
I dont have an account at github so dont go counting on it.
uNi
You could register of course
. It's very simple to use and it would help a lot!