Table of Contents
Sometimes your system may generate an error stating that kernel / boot / vmlinuz-linux root = / dev / sda1 ro nomodeset. This error can have various reasons.
Updated
To me this is like downloading the Linux kernel sources for a unix system from kernel.org or elsewhere, but also compiling them without you to use all the features of your distribution (e.g. packaging).
Most of the time this is possible, but in reality it is much more difficult than doing it in such a simple way.
Unfortunately the PPa repository for the Launchpad kernel in Ubuntu is no longer supported, I refer you to the answers at https://askubuntu.com/questions/47397/how-do-i-add -the -kernel -pp …
Updated
Are you tired of your computer running slow? Annoyed by frustrating error messages? ASR Pro is the solution for you! Our recommended tool will quickly diagnose and repair Windows issues while dramatically increasing system performance. So don't wait any longer, download ASR Pro today!
Instead, I refer you to http://ubuntuhandbook.org/index.php/2013/ 09 / kernel-3-11-1-released-install-upgrade-in-ubuntu-linux-mint / which contains instructions on how to download and create precompiled 3.11.1 kernel packages for Ubuntu. I’m using Debian, not Ubuntu, so I haven’t tested this myself, but the site page claims it will work for Ubuntu 12.04, 12.10 and 13.10 and the tutorials seem to be correct.
Please note that kernel-ppa on ubuntu.com is an unofficial or semi-official repository. Domain owned by Canonical, but unofficial kernel packages are not supported. There is no kernel compiled by me either.
ARCH = $ (dpkg --print-architecture)wget "http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.1-saucy/linux-headers-3.11.1-031101-generic_3.11.1-031101.201309141102_$ARCH.deb"wget "http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.1-saucy/linux-headers-3.11.1-031101_3.11.1-031101.201309141102_all.deb"wget "http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.1-saucy/linux-image-3.11.1-031101-generic_3.11.1-031101.201309141102_$ARCH.deb"sudo dpkg -iBE linux-headers-3.11.1 * .deb linux-image-3.11.1 * .deb
If your whole family prefers to download their own kernel over a pre-compiled package, I really recommend that you look into Ubuntu Forms Packages for 3.11.1, Unpacking the Source, dpkg-source Install Build Dependencies AssGather the required kernel configuration parameters and build them all with your own packages using dpkg-builpackage or similar.
As with software, another particular kernel compiled into packages can give you much less hassle and annoyance about what's not packaged ... it's almost always better to set yourself as make && make install , so even if you initially want to build from source, it is best to compile from commercially available source.
- bumby
- Member
- Registered: 29.01.2012
- Posts: 17
Subject: [RESOLVED] Grub Error
hard drive / dev / sda: 500.1 GB, 500107862016 bytes255 heads, 63 sectors / track, 60801 cylinders, about 976773168 sectorsUnits = sectors of 1 (spaces) 512 = bytes 512Sector size (logical / physical): 512 bytes / 512 bytesI / O size (minimum / optimal): 512 bytes / 512 bytesVolume ID: 0x82ca63ed Boot block identification system when the device is loaded/ dev / sda1 2048 976771071 488384512 some HPFS / NTFS / exFATDisk /dev / sdb: 1000.2 GB, 1000204886016 bytes255 heads, 63 sectors / track, 121,601 cylinders, total 1953,525,168 sectorsUnits = sectors of a specific * 512 = 512 bytesSector size (logical / physical): 512 bytes / 512 bytesI / O size (minimum / optimal): 512 bytes / 512 bytesData carrier identification: 0x4cd1e822 Boot block identification system when booting the device/ dev / sdb1 * sixty three 1953520064 976760001 7 HPFS / NTFS / exFATStorage medium / dev / sde: 1000.2 GB, 1000204886016 bytes255 heads, 63 sectors / caterpillar, 121 601 tanks, total 1953 525 168 sectorsUnits = Unique Sectors * 512 = 512 BytesFull sector size (logical / physical): 512 bytes / 512 bytesI / O Capacity (Minimum / Optimum): 512 Bytes / 512 BytesData carrier identification: 0x4cd1e824 Boot block identification system when the device is loaded/ dev / sde1 2048 209717247 104857600 83 Linux/ dev / sde2 209717248 234883071 12582912 eighty-two swaps Linux / Solaris/ dev / sde3 234883072 1953519615 859318272 8 HPFS / NTFS / exFATDisk / dev / sdc: 250.1 GB, 250059350016 bytes255 heads, 63 sectors / track, 30401 cylinders, 488397168 number of sectorsDisks = 16,512 sectors = 512 bytesSector size (logical / physical): 512byte for every 512 bytesI / O size (minimum / optimal): 512 bytes or 512 bytesData carrier identification: 0x04d186c1 Boot block identification system when the device is loaded/ dev / sdc1 * sixty three 488394431 244197184+ 3 HPFS / NTFS / exFATHDD / dev / sdf: 500.1 GB, 500107862016 heads, bytes255 63 sectors per track, 60 801 cylinders, all 976 773 168 sectorsDisks = 16,512 sectors = 512 bytesSector size (logical / physical): 512 bytes / 512 bytesI / O size (minimum / optimal): 512 bytes / 512 bytesVolume ID: 0x82ca63e8 Boot block identification system when the device is loaded/ dev / sdf1 * 2048 976771071 488384512 many HPFS / NTFS / exFATDisk / dev / sdd: 1000.2 GB, 1000204886016 bytes255 heads, 63 sectors / track, 121 601 cylinders, all 1953 525 168 sectorsDisks = 1 sectors 3,512 = 512 bytesSector size (logical / physical): 512 bytes / 512 bytesI / O size (minimum / optimal): 512 bytes / 512 bytesData carrier identification: 0x4cd1e823 Boot block identification system when the device is loaded/ dev / sdd1 * sixty three 1953520064 976760001 6 FAT16Disk / dev / sdg: 320.1 GB, 320072933376 bytes255 heads, 63 sectors / track, 38,913 tanks, total 625 142 448 sectorsUnits = Specific Sectors * 512 = 512 BytesSector degree (logical / physical): 512 bytes / 512 bytesI / O Count (Minimum / Optimum): 512 Bytes / 512 BytesData carrier identification: 0x1ec5d283 Boot block identification system when the device is loaded/ dev / sdg1 * sixty three 625137344 312568641 7 HPFS / NTFS / exFATDisk / dev / sdh: 1002 MB, 1002438656 bytes33 heads, 36 sectors per track, 1,854 cylinders, total 1,957,888 sectorsUnits = 1 * 512 transactions = 512 bytesSector type (logical / physical): 512 bytes / 512 bytesI / O period (minimum / optimal): 512 bytes / 512 bytesData carrier identification: 0x95c6168a Boot block identification system when the device is loaded/ dev / sdh1 5.96 1957887 978896 6 FAT16Storage medium / dev / sdi: 8000 MB, 8000110592 bytes160 heads, 29 sectors per track, 5,139 cylinders, total 15,625,216 sectorsUnits = vital 1 * 512 = 512 bytesSector length (logical / physical): 512 bytes / 512 bytesI / O diameter (minimum / optimal): 512 bytes / 512 bytesData carrier identification: 0x00000000 Loading block identification system when loading Your devices/ dev / sdi1 2.32 15625215 7812592b W95 FAT32Disk / dev / mapper / arch_root-image: 608 MB, 608174080 bytes255 heads, 63 sectors / track, 73 cylinders, total 1,187,840 sectorsDisks = 1 * 512 sectors = 512 bytesSector size (logical / physical): 512 bytes / 512 bytesI / O Weight (Minimum / Optimum): 512 Bytes / 512 BytesData carrier identification: 0x00000000Storage medium / dev / mapper / arch_lib-modules: 100 MB, 100663296 bytes255 GB, 63 sectors per track, 12 cylinders, 196,608 total sectorsUnits correspond to sectors of 1 * 512, which means 512 bytes.Sector size (logical / physical): 512 bytes and 512 bytesI / O size (minimum / optimal): 512 bytes 512 bytesData carrier identification: 0x00000000Storage medium / dev / mapper / arch_usr-share: 465 MB, 465 567 744 bytes255 heads, 63 sectors per track, 56 tanks, total 909312 sectorsUnits = sectors of a specific * 512 = 512 bytesSector size (logical / physical): 512 bytes / 512 bytesI / O Size (Minimum / Optimum): 512 Bytes / 512 BytesData carrier identification: 0x00000000
Speed up your computer today with this simple download.
Résoudre Le Problème Du Noyau / Boot / Vmlinuz-linux Root = / Dev / Sda1 Ro Nomodeset
Rozwiązanie Problemu Jądra / Boot / Vmlinuz-linux Root = / Dev / Sda1 Ro Nomodeset
Risolvere Il Problema Del Kernel / Boot / Vmlinuz-linux Root = / Dev / Sda1 Ro Nomodeset
커널 문제 해결 / Boot / Vmlinuz-linux Root = / Dev / Sda1 Ro Nomodeset
Решение проблемы с ядром / Boot / Vmlinuz-linux Root = / Dev / Sda1 Ro Nomodeset
Löser Kärnproblemet / Boot / Vmlinuz-linux Root = / Dev / Sda1 Ro Nomodeset
Lösung Des Kernelproblems / Boot / Vmlinuz-linux Root = / Dev / Sda1 Ro Nomodeset
Het Kernelprobleem Oplossen / Boot / Vmlinuz-linux Root = / Dev / Sda1 Ro Nomodeset
Resolviendo El Problema Del Kernel / Boot / Vmlinuz-linux Root = / Dev / Sda1 Ro Nomodeset
