Sponsored Content
Operating Systems Linux Ubuntu System loks up after upgrade from 14.04 to 16.04 Post 302979562 by gandolf989 on Tuesday 16th of August 2016 09:43:09 AM
Old 08-16-2016
Quote:
Originally Posted by MadeInGermany
2 GB RAM is certainly enough for stability (but maybe not for speed).
I rather suspect that one of the listed kernel modules is not part of the LTS distro, and should be updated for the new kernel.
I received a dual core PC with Windows 7 free from my work. It had 2GB of RAM and was terribly slow. I bought a 4GB video card and 4-4GB DDR3 DIMMS and it preforms OK. I may never use 16GB of RAM, but I know my PC will never have to swap. It never hurts to buy extra memory, since modern browsers can use gigabytes of RAM just to cache web pages. Whether you are running Windows or Linux, you will probably use a browser that will suck up as much memory as it can. ;-)

I should have mentioned that I am running Ubuntu 16.04 on an I3 HP laptop with 12GB of RAM. I needed to install the Chrome browser, Flash control and disable the embeded flash control that came with the OS. It seems to work well. I don't have any complaints other than streaming could have worked a little better from the base install.
 

4 More Discussions You Might Find Interesting

1. SCO

file system not getting mounted in read write mode after system power failure

After System power get failed File system is not getting mounted in read- write mode (1 Reply)
Discussion started by: gtkpmbpl
1 Replies

2. UNIX for Advanced & Expert Users

how to make a full system backup excluding data and restoring it to a new system

Hi, In order to have a sand box machine that I could use to test some system changes before going to production state, I'd like to duplicate a working system to a virtual one. Ideally, I'd like to manage to do it this way : - Make a full system backup excluding the user file system (this... (7 Replies)
Discussion started by: pagaille
7 Replies

3. AIX

How to upgrade firmware of a system that doesn't boot?

any ideas ??????? (2 Replies)
Discussion started by: livehho
2 Replies

4. AIX

Cloning a system via mksysb backup from one system and restore to new system

Hello All, I am trying to clone an entire AIX virtual machine to a new virtual machine including all partitions and OS.Can anyone help me on the procedure to follow? I am not really sure on how it can be done.Thanks in advance. Please use CODE tags for sample input, sample output, and for code... (4 Replies)
Discussion started by: gull05
4 Replies
RDEV(8) 						     Linux Programmer's Manual							   RDEV(8)

NAME
rdev - query/set image root device, RAM disk size, or video mode SYNOPSIS
rdev [ -rvh ] [ -o offset ] [ image [ value [ offset ] ] ] rdev [ -o offset ] [ image [ root_device [ offset ] ] ] ramsize [ -o offset ] [ image [ size [ offset ] ] ] vidmode [ -o offset ] [ image [ mode [ offset ] ] ] rootflags [ -o offset ] [ image [ flags [ offset ] ] ] DESCRIPTION
With no arguments, rdev outputs an /etc/mtab line for the current root file system. With no arguments, ramsize, vidmode, and rootflags print usage information. In a bootable image for the Linux kernel on i386, there are several pairs of bytes which specify the root device, the video mode, and the size of the RAM disk. These pairs of bytes, by default, begin at offset 504 (decimal) in the kernel image: 498 Root flags (500 and 502 Reserved) 504 RAM Disk Size 506 VGA Mode 508 Root Device (510 Boot Signature) rdev will change these values. Typical values for the image parameter, which is a bootable Linux kernel image, might be: /vmlinux /vmunix /boot/bzImage-2.4.0 /dev/fd0 /dev/fd1 When using the rdev command, the root_device parameter might be something like: /dev/hda1 /dev/hdf13 /dev/sda2 /dev/sdc4 /dev/ida/c0d0p1 One may also specify the device by a comma-separated pair of decimal integers major,minor. For the ramsize command, the size parameter specifies the size of the RAM disk in kilobytes. For the rootflags command, the flags parameter contains extra information used when mounting root. Currently the only effect of these flags is to force the kernel to mount the root filesystem in readonly mode if flags is non-zero. For the vidmode command, the mode parameter specifies the video mode: -3 = Prompt -2 = Extended VGA -1 = Normal VGA 0 = as if "0" was pressed at the prompt 1 = as if "1" was pressed at the prompt 2 = as if "2" was pressed at the prompt n = as if "n" was pressed at the prompt If the value is not specified, the image will be examined to determine the current settings. OPTIONS
-r Causes rdev to act like ramsize. -R Causes rdev to act like rootflags. -v Causes rdev to act like vidmode. -h Provides help. BUGS
The rdev utility, when used other than to find a name for the current root device, is an ancient hack that works by patching a kernel image at a magic offset with magic numbers. It does not work on architectures other than i386. Its use is strongly discouraged. Use a boot loader like SysLinux or LILO instead. HISTORY
At offset 502 there used to be the device number of the swap device (in Linux 0.12), and "rdev -s" or "swapdev" would set this. However, since Linux 0.95 this constant is not used any longer, and the swap device is specified using the swapon() system call. AUTHORS
Originally by Werner Almesberger (almesber@nessie.cs.id.ethz.ch) Modified by Peter MacDonald (pmacdona@sanjuan.UVic.CA) rootflags support added by Stephen Tweedie (sct@dcs.ed.ac.uk) Linux 0.99 20 November 1993 RDEV(8)
All times are GMT -4. The time now is 05:30 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy