Re: Problem with Quantal and a KVM
Quoting Dale Amon (a...@vnl.com): Anyone know of a work around? A change in initrd? A change in /etc/default/grub? Warning: kinda ranty: This sounds like one of my major annoyances with Ubuntu (server): the framebuffered consoles splashscreens that are TERRIBLY incompatible with virtual monitors other than a physical connected VESA-VGA capable video display. Be it DRAC, ILOM, iRMC, KVM-switches alike, they all struggle with the framebuffered videomodes. Up until precise(?) it was possible to blacklist the framebuffered videomodule (fbcon, vga16) but these are now compiled in the kernel en therefore no longer blacklistable. :( What seemed to help for me was to force a specific videmode you *know* your monitor/application supports with the 'vga=xxx' kernelparameter (or gfxpayload GRUB option). However, things have been changing wildly the last couple of releases, none of my hacks to keep it working Try editing /etc/default/grub: * Comment out every line starting with 'GRUB_HIDDEN' This enables you to actually SEE the grub bootloader, without having to guess what key-combo is today's way to break in to the menu of GRUB. (It used to be ESC, then became one of the alt, ctrl or shift keys, today you might have to hold Escape-Meta-Alt-Control-Shift while double clicking your middle mouse button... who knows!) * Increase GRUB_TIMEOUT to 30 seconds This gives your monitor time to tune in and show you the GRUB menu AND allows you more time to change options / break the default process. * Change/Replace GRUB_CMDLINE_LINUX_DEFAULT with: vga=792 noplymouth nosplash verbose init_verbose=yes INIT=/sbin/init -v This line i composed in a fit of rage when i had a system not booting and not showing me ANYTHING usefull. It changes videomode, disables plymouth (as far as possible) switches off splashscreens, etc... * *UN*comment GRUB_TERMINAL=console Even GRUB has been switched to framebuffered video by default. :( HTH. -Sander. -- | The problem with dancing naked: not everything stalls when the music stops. | 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2 -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Problem with Quantal and a KVM
On Wed, Jan 02, 2013 at 09:11:06AM +0100, Sander Smeenk wrote: This sounds like one of my major annoyances with Ubuntu (server): the framebuffered consoles splashscreens that are TERRIBLY incompatible with virtual monitors other than a physical connected VESA-VGA capable video display. Be it DRAC, ILOM, iRMC, KVM-switches alike, they all struggle with the framebuffered videomodes. I agree, just did not want to say it. I get the feeling there are a lot of people working on Linux these days who have never set foot into a data centre. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Problem with Quantal and a KVM
For those who do not understand what I mean... if you have a release named 'server' and it is to work in a typical industrial rack, then you must assume: * your console is via a KVM that is probably 5-10 years old. * the rack has anywhere up to 10 other servers in it, some of which might be brand new, others may be 10 years old (If it ain't broke, you don't fix it). * The servers will be running various versions of Ubuntu, Windows, Debian, RedHat, Novell, and god knows what else. * There will rarely be a human being at the machine (going through all the security to get into the facility can be a pain); when there is it means there is either a scheduled maintenance or an emergency. * If it is an emergency, the sysadmin must get into the machine at command line as quickly as possible, find everything where 30 years of Unix experience says it should be, and have things fixed before someone higher up in the company demands your head. You have to develop to work in that environment. If you do not, you are just playing. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Problem with Quantal and a KVM
On Wed, Jan 02, 2013 at 03:31:47AM -0600, Jordon Bedwell wrote: Your statement is full of fail and horseshit. So you have worked in data centres on racks belonging to Fortune 500 companies and their contract service providers? Good to hear there are experienced people on board. Which also means there is no excuse. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Problem with Quantal and a KVM
Just fyi, this is the grub default set up I am using right now. I did try a number of different settings but they did not seem to make any difference. Perhaps this is because of the stuff being compiled that you noted. This is the grub default settings I typically use: GRUB_DEFAULT=0 #GRUB_HIDDEN_TIMEOUT=0 GRUB_TIMEOUT=15 GRUB_HIDDEN_TIMEOUT_QUIET=false GRUB_DISTRIBUTOR=`lsb_release -i -s 2 /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT= max_loop=64 panic=200 GRUB_CMDLINE_LINUX= # DMA20121217 Use these instead if I set up a serial console GRUB_CMDLINE_LINUX_DEFAULT=console=tty0 console=ttyS0,115200n8 max_loop=64 panic=200 GRUB_TERMINAL=serial console GRUB_SERIAL_COMMAND=serial --speed=115200 --unit=0 --word=8 --parity=no --stop=1 # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM=0x01234567,0xfefefefe,0x89abcdef,0xefefefef # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console # DMA20121218. This is new, suggested to me by Tom H on the ubuntudev list #GRUB_GFXPAYLOAD_LINUX=text # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' #GRUB_GFXMODE=640x480 # Uncomment if you don't want GRUB to pass root=UUID=xxx parameter to Linux #GRUB_DISABLE_LINUX_UUID=true # Uncomment to disable generation of recovery mode menu entries #GRUB_DISABLE_RECOVERY=true # Uncomment to get a beep at grub start #GRUB_INIT_TUNE=480 440 1 -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: redmine packaging
Would be cool if ChiliProject could be packaged too (a Redmine fork). https://www.chiliproject.org/ Well, that project seems to be much more active, so it _maybe_ could be a replacement for current redmine-core. As we're still at 1.4.4 base and now attempting to upgrade to 2.x, chiliproject might be an alternative candidate. Does anybody here has some experience in redmine-chilli migration ? cu -- Mit freundlichen Grüßen / Kind regards Enrico Weigelt VNC - Virtual Network Consult GmbH Head Of Development Pariser Platz 4a, D-10117 Berlin Tel.: +49 (30) 3464615-20 Mobile: +49 (151) 27565287 Fax: +49 (30) 3464615-59 enrico.weig...@vnc.biz; www.vnc.de -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
