Re: creaing new 3.0.4 kernel in squeeze --kernel panic
poenik...@operamail.com wrote: > On Oct 30, 8:10 pm, Hugo Vanwoerkom wrote: > > I suspect that my configuration of the kernel is at fault, but where > should I start looking for problems? > > Problem solved by installing wheezy which comes with a 3.0.0 kernel. Thank you all for your time and patience. -- Sian -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/j91888$c88$3...@speranza.aioe.org
Re: creaing new 3.0.4 kernel in squeeze --kernel panic
Arnt Karlsen wrote: > On Mon, 31 Oct 2011 13:56:46 -0700 (PDT), poenik...@operamail.com wrote > in message > <6a9c6581-5fbb-4848-9d92-81bf0dbce...@j36g2000prh.googlegroups.com>: > >> On Oct 31, 7:20 pm, "poenik...@operamail.com" >> wrote: >> > On Oct 31, 12:40 am, Stephen Powell wrote: >> > > Also, I recommend that you read >> > >> > > http://users.wowway.com/~zlinuxman/Kernel.htm >> > >> > > for a fairly comprehensive tutorial on kernel building in Debian >> > > which documents many common "gotchas" in kernel building. For >> > > example, there is a patch to kernel-package which is needed in >> > > some circumstances when building a version 3 kernel with >> > > make-kpkg. The patch is documented on the above web page. And, >> > > depending on which boot loader you use, you may need to install >> > > some hook scripts when using a custom kernel with Squeeze and >> > > later releases. This is also documented on the above web page. >> > >> > > -- >> > > .''`. Stephen Powell >> > > : :' : >> > > `. `'` >> > >> > I followed the instructions given in Kernel.htm and built a kernel >> > from the source tree I had >> > downloaded fromwww.kernel.orgafter issuing make-kpkg debian. I also >> > patched kernel-package >> > using the patch file (linuxv3.diff) mentioned on the web page. >> > >> > I also used make localmodconfig to greatly reduce the number of >> > modules actually compiled. >> > Compiling the kernel took 34 mins on my 1.6GHz laptop. >> > >> > I installed the kernel using dpkg as root, checked that an initramfs >> > image had been created, closed down >> > and rebooted. >> > >> > The kernel loaded, entered runlevel 2, but commands that tried to >> > write to the fs failed because it was >> > still readonly. The kernel finally hung with nfsd. ctrl-alt-del >> > successfully rebooted. I shall recompile >> > the kernel without NFS support because I don't need it. >> >> I removed NFS stuff and recompiled the kernel. I also removed the >> packages nfs-kernel-server and >> nfs-common. >> >> After rebooting with the new kernel, it loaded, hung at points and >> eventually gave me a tty login >> prompt. I could login as sian as well as root, but the file system was >> still read-only. I suspect that >> GNOME has to be able to write to the fs so that is why I only got a >> tty prompt. >> >> Some messages emitted by the kernel when loading: >> - >> Can't open or create /var/run/syslogd.pid >> Unknown hardware ThinkPad EC >> touch: setting times of /var/lib/sudo: Read-only file system >> -- >> What do I do next? > > ..remount your disk read-write. > >> At least the kernel loads and gives me a prompt. I >> don't understand why the >> file system is still read-only. > > ..could be _anything_ from a bad disk to a kernel config bug. > My reading of your NFS "hang" is you should have patient enough > to give it time to time out, at least once. (5 or 15 minutes?) > > ..try set up a syslog host on your lan and point your > 3.0.4 box' syslog there, and post the url to it if you > find funny errors etc things that warrants further fun. > >> > > Problem solved by installing wheezy. -- Sian -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/j91811$c88$2...@speranza.aioe.org
Re: creaing new 3.0.4 kernel in squeeze --kernel panic
Stephen Powell wrote: > On Tue, 01 Nov 2011 21:02:56 -0400 (EDT), Sian Mountbatten wrote: >> >> Thank you all for your helpful advice and info. >> >> I am giving up on squeeze because I get so many problems with building >> a series 3 kernel. I tried to download a kernel image from wheezy, but >> got problems when I tried to install the Debian package. I tried >> downloading and installing the dependencies, but putting a wheezy >> kernel onto a squeeze system did not work. So I have now downloaded >> the first DVD iso for wheeze and I shall try to install a series >> 3 kernel for that release. >> >> Again, thank you all for your help. > > I hope you have better luck with Wheezy. I am running a custom-built > 3.0.0 kernel on Wheezy right now, and I am not having any problems. > There are often dependencies between the kernel releases and some > other packages closely related to the kernel, such as initramfs- tools, > libc*, udev, etc. I suspect you will do better with Wheezy. > I have now successfully installed wheezy on both my desktop and my laptop. I am more than satisfied with the KDE desktop and all the apps which are available. Thank you all for your time and interest. -- Sian -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/j917ug$c88$1...@speranza.aioe.org
Re: creaing new 3.0.4 kernel in squeeze --kernel panic
On Tue, 01 Nov 2011 21:02:56 -0400 (EDT), Sian Mountbatten wrote: > > Thank you all for your helpful advice and info. > > I am giving up on squeeze because I get so many problems with building > a series 3 kernel. I tried to download a kernel image from wheezy, but > got problems when I tried to install the Debian package. I tried > downloading and installing the dependencies, but putting a wheezy > kernel onto a squeeze system did not work. So I have now downloaded > the first DVD iso for wheeze and I shall try to install a series > 3 kernel for that release. > > Again, thank you all for your help. I hope you have better luck with Wheezy. I am running a custom-built 3.0.0 kernel on Wheezy right now, and I am not having any problems. There are often dependencies between the kernel releases and some other packages closely related to the kernel, such as initramfs-tools, libc*, udev, etc. I suspect you will do better with Wheezy. -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/332873274.481855.1320198967497.javamail.r...@md01.wow.synacor.com
Re: creaing new 3.0.4 kernel in squeeze --kernel panic
On Tue, 01 Nov 2011 20:43:12 -0400 (EDT), Walter Hurry wrote: > > But my (single internal) hard disk is always /dev/sda, and my two > external USB disks are always /dev/sdb and /dev/sdc. So what difference > does it make? You mean that *so far* your internal hard disk is always /dev/sda and *so far* your external USB disks are always /dev/sdb and /dev/sdc. There are no guarantees that it will always be so. On my system, I've noticed that my single internal hard disk is usually /dev/sda and my CD-ROM drive is usually /dev/sdb. But if I boot my system from a rescue CD, the CD-ROM drive is usually /dev/sda and the hard disk is usually /dev/sdb. But I cannot guarantee that the hard disk will always be /dev/sda even if I boot from the hard disk every time. It's all timing dependent. Devices are not necessarily discovered in any particular order anymore. It is safest to use UUIDs or LABELs. -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1532239075.481697.1320198540616.javamail.r...@md01.wow.synacor.com
Re: creaing new 3.0.4 kernel in squeeze --kernel panic
On Wed, 02 Nov 2011 01:10:02 +0100, Stephen Powell wrote: > On Tue, 01 Nov 2011 19:46:13 -0400 (EDT), Walter Hurry wrote: >> On Tue, 01 Nov 2011 19:43:20 -0400, Stephen Powell wrote: >>> >>> It is important that you *not* use traditional device nomenclature, >>> such as >>> >>> /dev/hda1 >>> /dev/sda1 >> >> Why? > > Two reasons. First, whether an IDE hard disk shows up as /dev/hda, > /dev/hdb, etc. or /dev/sda, /dev/sdb, etc. depends on which drivers are > being used. For example, the 2.6.32-3-686 kernel and earlier ones use > the traditional IDE drivers, with device names /dev/hda, /dev/hdb, etc. > The 2.6.32-5-686 and later kernels use the libata SCSI emulation > drivers, with device names /dev/sda, /dev/sdb, etc. > > Second, the devices are not necessarily discovered in the same order > every time with newer kernels. Let's say you have a system with one > hard disk and one CD-ROM drive. On one boot, your hard disk may be > assigned device name /dev/sda and the CD-ROM drive may be assigned the > device name /dev/sdb. But on the next boot, it is possible that the > CD-ROM drive may be assigned the device name /dev/sda and the hard disk > may be assigned the device name /dev/sdb. You can never be sure. By > using UUIDs or LABELs, you will always get the same physical partition > mounted as the root file system every time, regardless of what its > device name happens to be in the current boot. The same applies to > non-root file sytems in /etc/fstab (i.e. /boot, /home, etc.) > > -- > .''`. Stephen Powell > : :' : > `. `'` >`- Thank you all for your helpful advice and info. I am giving up on squeeze because I get so many problems with building a series 3 kernel. I tried to download a kernel image from wheezy, but got problems when I tried to install the Debian package. I tried downloading and installing the dependencies, but putting a wheezy kernel onto a squeeze system did not work. So I have now downloaded the first DVD iso for wheeze and I shall try to install a series 3 kernel for that release. Again, thank you all for your help. -- Sian Mountbatten -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/j8q4s0$m0k$1...@dont-email.me
Re: creaing new 3.0.4 kernel in squeeze --kernel panic
On Tue, 01 Nov 2011 20:00:54 -0400, Stephen Powell wrote: > On Tue, 01 Nov 2011 19:46:13 -0400 (EDT), Walter Hurry wrote: >> On Tue, 01 Nov 2011 19:43:20 -0400, Stephen Powell wrote: >>> >>> It is important that you *not* use traditional device nomenclature, >>> such as >>> >>> /dev/hda1 /dev/sda1 >> >> Why? > > Two reasons. First, whether an IDE hard disk shows up as /dev/hda, > /dev/hdb, etc. or /dev/sda, /dev/sdb, etc. depends on which drivers are > being used. For example, the 2.6.32-3-686 kernel and earlier ones use > the traditional IDE drivers, with device names /dev/hda, /dev/hdb, etc. > The 2.6.32-5-686 and later kernels use the libata SCSI emulation > drivers, with device names /dev/sda, /dev/sdb, etc. > > Second, the devices are not necessarily discovered in the same order > every time with newer kernels. Let's say you have a system with one > hard disk and one CD-ROM drive. On one boot, your hard disk may be > assigned device name /dev/sda and the CD-ROM drive may be assigned the > device name /dev/sdb. But on the next boot, it is possible that the > CD-ROM drive may be assigned the device name /dev/sda and the hard disk > may be assigned the device name /dev/sdb. You can never be sure. > By using UUIDs or LABELs, you will always get the same physical > partition mounted as the root file system every time, regardless of what > its device name happens to be in the current boot. The same applies to > non-root file sytems in /etc/fstab (i.e. /boot, /home, etc.) But my (single internal) hard disk is always /dev/sda, and my two external USB disks are always /dev/sdb and /dev/sdc. So what difference does it make? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/j8q3n0$eor$1...@dough.gmane.org
Re: creaing new 3.0.4 kernel in squeeze --kernel panic
On Tue, 01 Nov 2011 19:46:13 -0400 (EDT), Walter Hurry wrote: > On Tue, 01 Nov 2011 19:43:20 -0400, Stephen Powell wrote: >> >> It is important that you *not* use traditional device nomenclature, such >> as >> >> /dev/hda1 >> /dev/sda1 > > Why? Two reasons. First, whether an IDE hard disk shows up as /dev/hda, /dev/hdb, etc. or /dev/sda, /dev/sdb, etc. depends on which drivers are being used. For example, the 2.6.32-3-686 kernel and earlier ones use the traditional IDE drivers, with device names /dev/hda, /dev/hdb, etc. The 2.6.32-5-686 and later kernels use the libata SCSI emulation drivers, with device names /dev/sda, /dev/sdb, etc. Second, the devices are not necessarily discovered in the same order every time with newer kernels. Let's say you have a system with one hard disk and one CD-ROM drive. On one boot, your hard disk may be assigned device name /dev/sda and the CD-ROM drive may be assigned the device name /dev/sdb. But on the next boot, it is possible that the CD-ROM drive may be assigned the device name /dev/sda and the hard disk may be assigned the device name /dev/sdb. You can never be sure. By using UUIDs or LABELs, you will always get the same physical partition mounted as the root file system every time, regardless of what its device name happens to be in the current boot. The same applies to non-root file sytems in /etc/fstab (i.e. /boot, /home, etc.) -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/544765130.478134.1320192054767.javamail.r...@md01.wow.synacor.com
Re: creaing new 3.0.4 kernel in squeeze --kernel panic
On Tue, 01 Nov 2011 19:43:20 -0400, Stephen Powell wrote: > It is important that you *not* use traditional device nomenclature, such > as > >/dev/hda1 /dev/sda1 Why? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/j8q0c5$noi$1...@dough.gmane.org
Re: creaing new 3.0.4 kernel in squeeze --kernel panic
On Mon, 31 Oct 2011 14:54:37 -0400 (EDT), poenik...@operamail.com wrote: > > I followed the instructions given in Kernel.htm and built a kernel > from the source tree I had > downloaded from www.kernel.org after issuing make-kpkg debian. I also > patched kernel-package > using the patch file (linuxv3.diff) mentioned on the web page. > > I also used make localmodconfig to greatly reduce the number of > modules actually compiled. > Compiling the kernel took 34 mins on my 1.6GHz laptop. > > I installed the kernel using dpkg as root, checked that an initramfs > image had been created, closed down > and rebooted. > > The kernel loaded, entered runlevel 2, but commands that tried to > write to the fs failed because it was > still readonly. The kernel finally hung with nfsd. ctrl-alt-del > successfully rebooted. I shall recompile > the kernel without NFS support because I don't need it. In a typical Debian boot, there are three stages for the root file system. In stage 1, the initial RAM file system is mounted as the root (/) file system. The boot loader loads the (mostly) compressed kernel image and the compressed initial RAM file system image into memory, then passes control to the kernel. The boot loader tells the kernel where the compressed initial RAM file system image is by passing it's address to the kernel. The kernel decompresses itself, decompresses the initial RAM file system image, frees the memory associated with the compressed version of the initial RAM file system, then mounts the uncompressed version of the initial RAM file system as the root (/) file system. For LILO, the "image" and "initrd" boot loader configuration records specify the kernel image and initial RAM file system image to be used, respectively. In stage 2, once all modules needed to do I/O to the disk have been loaded, as well as all modules needed to interpret the file system, the permanent root file system is mounted. Typically, it is mounted read-only. The location of the permanent root file system is passed to the kernel via the kernel command line from parameters specified in the boot loader configuration file. For LILO, the "read-only" and "root" boot loader configuration records specify this information. The corresponding options passed on the kernel command line are "ro" and "root". Once the permanent root file system has been mounted read-only, the uncompressed initial RAM file system image is freed from memory. Additional kernel modules are loaded at this stage, including those specified in /etc/modules. They are loaded from the permanent root file system, still mounted read-only. In stage 3, the permanent root file system is mounted read-write. At this stage, the file system to use is specified by /etc/fstab. Obviously, you must make sure that your boot loader configuration file and /etc/fstab specify the same root file system. It is important that you *not* use traditional device nomenclature, such as /dev/hda1 /dev/sda1 etc. Generally, the newer the kernel, the less likely this is to work. You should specify the root file system, both in the boot loader configuration file and in /etc/fstab by using "UUID=xxx..." or "LABEL=xxx" specifications. Since you seem to be having trouble at stage 3, the first thing I would look at is /etc/fstab. If you don't find any errors there, please post your boot loader configuration file, /etc/fstab, and the kernel boot messages. -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1391569326.477490.1320191000468.javamail.r...@md01.wow.synacor.com
Re: creaing new 3.0.4 kernel in squeeze --kernel panic
On Mon, 31 Oct 2011 10:25:04 -0400 (EDT), Hugo Vanwoerkom wrote: > Stephen Powell wrote: >> I would recommend using something like "make localmodconfig" to strip >> out drivers your hardware doesn't need. There are many hidden >> dependencies, such as SCSI support, that are not obvious. >> ... > That will definitely give you a bootable kernel but with the stock > Debian config, which is huge and gives you way more than you really need. > IMO to get just the right kernel config is very tricky because it is an > trial and error thing. What would be handy is an IDE that records what > change you made and for what reason, so that it can be removed when your > hardware changes. Perhaps you're thinking of "make oldconfig" or some other configuration target. "make localmodconfig" will definitely strip out modules that are not in use by the current hardware. There may be a few things that are built-in to the kernel that could be eliminated, but most stuff that is hardware-related is in a module by default, and "make localmodconfig" will get you 99% of the way (or better) toward the minimal kernel configuration for the current hardware. -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1875441311.476634.1320189198947.javamail.r...@md01.wow.synacor.com
Re: creaing new 3.0.4 kernel in squeeze --kernel panic
On Mon, 31 Oct 2011 13:56:46 -0700 (PDT), poenik...@operamail.com wrote in message <6a9c6581-5fbb-4848-9d92-81bf0dbce...@j36g2000prh.googlegroups.com>: > On Oct 31, 7:20 pm, "poenik...@operamail.com" > wrote: > > On Oct 31, 12:40 am, Stephen Powell wrote: > > > Also, I recommend that you read > > > > > http://users.wowway.com/~zlinuxman/Kernel.htm > > > > > for a fairly comprehensive tutorial on kernel building in Debian > > > which documents many common "gotchas" in kernel building. For > > > example, there is a patch to kernel-package which is needed in > > > some circumstances when building a version 3 kernel with > > > make-kpkg. The patch is documented on the above web page. And, > > > depending on which boot loader you use, you may need to install > > > some hook scripts when using a custom kernel with Squeeze and > > > later releases. This is also documented on the above web page. > > > > > -- > > > .''`. Stephen Powell > > > : :' : > > > `. `'` > > > > I followed the instructions given in Kernel.htm and built a kernel > > from the source tree I had > > downloaded fromwww.kernel.orgafter issuing make-kpkg debian. I also > > patched kernel-package > > using the patch file (linuxv3.diff) mentioned on the web page. > > > > I also used make localmodconfig to greatly reduce the number of > > modules actually compiled. > > Compiling the kernel took 34 mins on my 1.6GHz laptop. > > > > I installed the kernel using dpkg as root, checked that an initramfs > > image had been created, closed down > > and rebooted. > > > > The kernel loaded, entered runlevel 2, but commands that tried to > > write to the fs failed because it was > > still readonly. The kernel finally hung with nfsd. ctrl-alt-del > > successfully rebooted. I shall recompile > > the kernel without NFS support because I don't need it. > > I removed NFS stuff and recompiled the kernel. I also removed the > packages nfs-kernel-server and > nfs-common. > > After rebooting with the new kernel, it loaded, hung at points and > eventually gave me a tty login > prompt. I could login as sian as well as root, but the file system was > still read-only. I suspect that > GNOME has to be able to write to the fs so that is why I only got a > tty prompt. > > Some messages emitted by the kernel when loading: > - > Can't open or create /var/run/syslogd.pid > Unknown hardware ThinkPad EC > touch: setting times of /var/lib/sudo: Read-only file system > -- > What do I do next? ..remount your disk read-write. > At least the kernel loads and gives me a prompt. I > don't understand why the > file system is still read-only. ..could be _anything_ from a bad disk to a kernel config bug. My reading of your NFS "hang" is you should have patient enough to give it time to time out, at least once. (5 or 15 minutes?) ..try set up a syslog host on your lan and point your 3.0.4 box' syslog there, and post the url to it if you find funny errors etc things that warrants further fun. > -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2001151717.1dc35...@nb6.lan
Re: creaing new 3.0.4 kernel in squeeze --kernel panic
On Oct 31, 7:20 pm, "poenik...@operamail.com" wrote: > On Oct 31, 12:40 am, Stephen Powell wrote: > > Also, I recommend that you read > > > http://users.wowway.com/~zlinuxman/Kernel.htm > > > for a fairly comprehensive tutorial on kernel building in Debian which > > documents many common "gotchas" in kernel building. For example, there > > is a patch to kernel-package which is needed in some circumstances > > when building a version 3 kernel with make-kpkg. The patch is documented > > on the above web page. And, depending on which boot loader you use, > > you may need to install some hook scripts when using a custom kernel > > with Squeeze and later releases. This is also documented on the > > above web page. > > > -- > > .''`. Stephen Powell > > : :' : > > `. `'` > > I followed the instructions given in Kernel.htm and built a kernel > from the source tree I had > downloaded fromwww.kernel.orgafter issuing make-kpkg debian. I also > patched kernel-package > using the patch file (linuxv3.diff) mentioned on the web page. > > I also used make localmodconfig to greatly reduce the number of > modules actually compiled. > Compiling the kernel took 34 mins on my 1.6GHz laptop. > > I installed the kernel using dpkg as root, checked that an initramfs > image had been created, closed down > and rebooted. > > The kernel loaded, entered runlevel 2, but commands that tried to > write to the fs failed because it was > still readonly. The kernel finally hung with nfsd. ctrl-alt-del > successfully rebooted. I shall recompile > the kernel without NFS support because I don't need it. I removed NFS stuff and recompiled the kernel. I also removed the packages nfs-kernel-server and nfs-common. After rebooting with the new kernel, it loaded, hung at points and eventually gave me a tty login prompt. I could login as sian as well as root, but the file system was still read-only. I suspect that GNOME has to be able to write to the fs so that is why I only got a tty prompt. Some messages emitted by the kernel when loading: - Can't open or create /var/run/syslogd.pid Unknown hardware ThinkPad EC touch: setting times of /var/lib/sudo: Read-only file system -- What do I do next? At least the kernel loads and gives me a prompt. I don't understand why the file system is still read-only. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/6a9c6581-5fbb-4848-9d92-81bf0dbce...@j36g2000prh.googlegroups.com
Re: creaing new 3.0.4 kernel in squeeze --kernel panic
On Oct 31, 12:40 am, Stephen Powell wrote: > On Sun, 30 Oct 2011 14:24:28 -0400 (EDT), poenik...@operamail.com wrote: > > > I downloaded the source for kernel version 3.0.4 fromwww.kernel.org. > > ... > > I then ploughed through all the options, removing modules where I was > > sure I did not have > > the relevant hardware. > > ... > > I closed down squeeze, rebooted and chose the new 3.0.4 kernel. It > > displayed an > > error message (kernel panic) to the effect that it could not load the > > root fs. > > > What have I done wrong? > > I would recommend using something like "make localmodconfig" to strip > out drivers your hardware doesn't need. There are many hidden > dependencies, such as SCSI support, that are not obvious. > Also, I recommend that you read > > http://users.wowway.com/~zlinuxman/Kernel.htm > > for a fairly comprehensive tutorial on kernel building in Debian which > documents many common "gotchas" in kernel building. For example, there > is a patch to kernel-package which is needed in some circumstances > when building a version 3 kernel with make-kpkg. The patch is documented > on the above web page. And, depending on which boot loader you use, > you may need to install some hook scripts when using a custom kernel > with Squeeze and later releases. This is also documented on the > above web page. > > -- > .''`. Stephen Powell > : :' : > `. `'` I followed the instructions given in Kernel.htm and built a kernel from the source tree I had downloaded from www.kernel.org after issuing make-kpkg debian. I also patched kernel-package using the patch file (linuxv3.diff) mentioned on the web page. I also used make localmodconfig to greatly reduce the number of modules actually compiled. Compiling the kernel took 34 mins on my 1.6GHz laptop. I installed the kernel using dpkg as root, checked that an initramfs image had been created, closed down and rebooted. The kernel loaded, entered runlevel 2, but commands that tried to write to the fs failed because it was still readonly. The kernel finally hung with nfsd. ctrl-alt-del successfully rebooted. I shall recompile the kernel without NFS support because I don't need it. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20a54e07-8ae8-4781-9d05-05ff49ec6...@q35g2000prh.googlegroups.com
Re: creaing new 3.0.4 kernel in squeeze --kernel panic
Stephen Powell wrote: On Sun, 30 Oct 2011 14:24:28 -0400 (EDT), poenik...@operamail.com wrote: I downloaded the source for kernel version 3.0.4 from www.kernel.org. ... I then ploughed through all the options, removing modules where I was sure I did not have the relevant hardware. ... I closed down squeeze, rebooted and chose the new 3.0.4 kernel. It displayed an error message (kernel panic) to the effect that it could not load the root fs. What have I done wrong? I would recommend using something like "make localmodconfig" to strip out drivers your hardware doesn't need. There are many hidden dependencies, such as SCSI support, that are not obvious. Also, I recommend that you read http://users.wowway.com/~zlinuxman/Kernel.htm That will definitely give you a bootable kernel but with the stock Debian config, which is huge and gives you way more than you really need. IMO to get just the right kernel config is very tricky because it is an trial and error thing. What would be handy is an IDE that records what change you made and for what reason, so that it can be removed when your hardware changes. Hugo -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/j8mb41$4jj$1...@dough.gmane.org
Re: creaing new 3.0.4 kernel in squeeze --kernel panic
On Mon, 2011-10-31 at 05:16 +0100, Ralf Mardorf wrote: > On Sun, 2011-10-30 at 12:40 -0700, poenik...@operamail.com wrote: > > Here is the screen output for the kernel panic:- > > > > Kernel panic - not syncing: VFS: Unable to mount root fs on unknown- > > block(0.0) > > Pid: 1. comm:swapper Not tainted 3.0.4 #1 > > Call trace: > > [] ? panic+0x4d/0x137 > > [] ? mount_block_root+0x1e6/0x1fa > > [] ? parse_early_options+0x18/0x18 > > [] ? mount_root+0x39/0x4d > > [] ? parse_early_options+0x18/0x18 > > [] ? prepare_namespace+0x105/0x135 > > [] ? kernel_init+0xe9/0xf2 > > [] ? kernel_thread_helper+0x6/0xd > > - > > The computer locked and only continually pressing the on/off button > > worked. > > > > Any help appreciated. I can upload the .config file, but obviously not > > to this user group > > because it is 70KB long! :-) > > > > Regards, Sian > > Perhaps no initrd was build? > Perhaps you didn't run apt-get build-dep linux when installing the > requirements to build a kernel? > > I did it in this order > > apt-get update > apt-get install fakeroot build-essential crash kexec-tools makedumpfile > kernel-package kernel-wedge > apt-get build-dep linux > apt-get install libncurses5 libncurses5-dev libelf-dev asciidoc > binutils-dev Sorry, seems to be nonsense, I suspect I was confusing it with an old issue for Ubuntu: "Intrepid (8.10), through to Karmic (9.10): sudo apt-get install fakeroot kernel-wedge build-essential makedumpfile kernel-package Note: The linux-kernel-devel package does not exist in Intrepid, Jaunty, or any newer release. To compile the kernel on Intrepid or newer, you'll also need to run: sudo apt-get build-dep linux This will install the compiler related packages and kernel packaging tools. It will also install the git-core package, which is the best way to interact with the Ubuntu kernel source." root@debian:/home/spinymouse# apt-get build-dep linux Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to find a source package for linux -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1320036384.2802.9.camel@debian
Re: creaing new 3.0.4 kernel in squeeze --kernel panic
On Sun, 2011-10-30 at 13:56 -0600, Hugo Vanwoerkom wrote: > I use: > make-kpkg --revision 1 --append-to-version -amd64 --initrd kernel_image I run make-kpkg --rootcmd fakeroot --initrd kernel-image kernel-headers -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1320034961.2802.6.camel@debian
Re: creaing new 3.0.4 kernel in squeeze --kernel panic
On Sun, 2011-10-30 at 12:40 -0700, poenik...@operamail.com wrote: > Here is the screen output for the kernel panic:- > > Kernel panic - not syncing: VFS: Unable to mount root fs on unknown- > block(0.0) > Pid: 1. comm:swapper Not tainted 3.0.4 #1 > Call trace: > [] ? panic+0x4d/0x137 > [] ? mount_block_root+0x1e6/0x1fa > [] ? parse_early_options+0x18/0x18 > [] ? mount_root+0x39/0x4d > [] ? parse_early_options+0x18/0x18 > [] ? prepare_namespace+0x105/0x135 > [] ? kernel_init+0xe9/0xf2 > [] ? kernel_thread_helper+0x6/0xd > - > The computer locked and only continually pressing the on/off button > worked. > > Any help appreciated. I can upload the .config file, but obviously not > to this user group > because it is 70KB long! :-) > > Regards, Sian Perhaps no initrd was build? Perhaps you didn't run apt-get build-dep linux when installing the requirements to build a kernel? I did it in this order apt-get update apt-get install fakeroot build-essential crash kexec-tools makedumpfile kernel-package kernel-wedge apt-get build-dep linux apt-get install libncurses5 libncurses5-dev libelf-dev asciidoc binutils-dev -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1320034589.2802.5.camel@debian
Re: creaing new 3.0.4 kernel in squeeze --kernel panic
On Sun, 30 Oct 2011 14:24:28 -0400 (EDT), poenik...@operamail.com wrote: > > I downloaded the source for kernel version 3.0.4 from www.kernel.org. > ... > I then ploughed through all the options, removing modules where I was > sure I did not have > the relevant hardware. > ... > I closed down squeeze, rebooted and chose the new 3.0.4 kernel. It > displayed an > error message (kernel panic) to the effect that it could not load the > root fs. > > What have I done wrong? I would recommend using something like "make localmodconfig" to strip out drivers your hardware doesn't need. There are many hidden dependencies, such as SCSI support, that are not obvious. Also, I recommend that you read http://users.wowway.com/~zlinuxman/Kernel.htm for a fairly comprehensive tutorial on kernel building in Debian which documents many common "gotchas" in kernel building. For example, there is a patch to kernel-package which is needed in some circumstances when building a version 3 kernel with make-kpkg. The patch is documented on the above web page. And, depending on which boot loader you use, you may need to install some hook scripts when using a custom kernel with Squeeze and later releases. This is also documented on the above web page. -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1462473744.43.1320021505717.javamail.r...@md01.wow.synacor.com
Re: creaing new 3.0.4 kernel in squeeze --kernel panic
On Oct 30, 8:10 pm, Hugo Vanwoerkom wrote: > poenik...@operamail.com wrote: > > I downloaded the source for kernel version 3.0.4 fromwww.kernel.org. > > I then booted to the > > Deiban squeeze partition and as superuser, unpacked the kernel source > > in one of my own > > directories. > > > I ran make targets to get what config commands were available. I > > installed qt4-dev files from > > the Debian squeeze DVD and did make xconfig which gave me a > > configuration screen for > > the new kernel source. > > > I then ploughed through all the options, removing modules where I was > > sure I did not have > > the relevant hardware. I eventually did make-kpkg clean, then make- > > kpkg debian and then > > make-kpkg --targets, chose > > binary and issued > > make-kpkg binary > > The kernel was compiled and after much activity, make-kpkg returned me > > to the command > > line. In the directory above the top of the source tree were a number > > of Debian packages > > which included linux-image-3.0.4_3.0.4-10.00.Custom_i386.deb which I > > installed using > > dpkg. grub was run which found the Linux kernels as well as Ubuntu > > 11.10. > > > I closed down squeeze, rebooted and chose the new 3.0.4 kernel. It > > displayed an > > error message (kernel panic) to the effect that it could not load the > > root fs. > > > What have I done wrong? > > > I remember not choosing the option for an initramfs. What would be put > > in it if I had > > chosen that option? > > I use: > make-kpkg --revision 1 --append-to-version -amd64 --initrd kernel_image > > which installs an initrd.img for an initramfs, but it will depend upon > the config that you ended up with. > > Hugo > I tried this and got a kernel image which installed ok, but when I rebooted into it, it gave the following: Loading, please wait... there then followed a definite pause followed by these messages: Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay - Check root (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/disk/by-uuid/long number string does not exist. I suspect that my configuration of the kernel is at fault, but where should I start looking for problems? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/9bcfad6f-88bd-4684-a593-32553ddaf...@t8g2000yql.googlegroups.com
Re: creaing new 3.0.4 kernel in squeeze --kernel panic
On 10/30/2011 1:24 PM, poenik...@operamail.com wrote: > What have I done wrong? > > I remember not choosing the option for an initramfs. What would be put > in it if I had > chosen that option? I'd guess you configured your root filesystem (EXT3/4?) as a module instead of building it directly into the kernel. When you then omitted initramfs the kernel had no way to load the filesystem code, hence the error: "Unable to mount root fs on unknown" "Unknown" in this context means the kernel can't identify the filesystem on the device where you are telling it the root filesystem resides. It can't because the FS driver isn't loaded. The solution is to build the filesystem driver directly into the kernel or to enable initramfs. Personally I always build my filesystem driver(s) directly into the kernel. Every machine must have a filesystem driver for the root filesystem, so there is no advantage to making it a module--put it in the kernel proper. -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4eadd00b.6000...@hardwarefreak.com
Re: creaing new 3.0.4 kernel in squeeze --kernel panic
On Oct 30, 6:50 pm, "poenik...@operamail.com" wrote: > I downloaded the source for kernel version 3.0.4 fromwww.kernel.org. > I then booted to the > Deiban squeeze partition and as superuser, unpacked the kernel source > in one of my own > directories. > > I ran make targets to get what config commands were available. I > installed qt4-dev files from > the Debian squeeze DVD and did make xconfig which gave me a > configuration screen for > the new kernel source. > > I then ploughed through all the options, removing modules where I was > sure I did not have > the relevant hardware. I eventually did make-kpkg clean, then make- > kpkg debian and then > make-kpkg --targets, chose > binary and issued > make-kpkg binary > The kernel was compiled and after much activity, make-kpkg returned me > to the command > line. In the directory above the top of the source tree were a number > of Debian packages > which included linux-image-3.0.4_3.0.4-10.00.Custom_i386.deb which I > installed using > dpkg. grub was run which found the Linux kernels as well as Ubuntu > 11.10. > > I closed down squeeze, rebooted and chose the new 3.0.4 kernel. It > displayed an > error message (kernel panic) to the effect that it could not load the > root fs. > > What have I done wrong? > > I remember not choosing the option for an initramfs. What would be put > in it if I had > chosen that option? > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: > http://lists.debian.org/50833057-0988-4022-9f24-28b06e0e6...@hj4g2000vbb.googlegroups.com Here is the screen output for the kernel panic:- Kernel panic - not syncing: VFS: Unable to mount root fs on unknown- block(0.0) Pid: 1. comm:swapper Not tainted 3.0.4 #1 Call trace: [] ? panic+0x4d/0x137 [] ? mount_block_root+0x1e6/0x1fa [] ? parse_early_options+0x18/0x18 [] ? mount_root+0x39/0x4d [] ? parse_early_options+0x18/0x18 [] ? prepare_namespace+0x105/0x135 [] ? kernel_init+0xe9/0xf2 [] ? kernel_thread_helper+0x6/0xd - The computer locked and only continually pressing the on/off button worked. Any help appreciated. I can upload the .config file, but obviously not to this user group because it is 70KB long! :-) Regards, Sian -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/86a460a6-05a2-483b-81ac-bd5c946f1...@a7g2000yqd.googlegroups.com
Re: creaing new 3.0.4 kernel in squeeze --kernel panic
poenik...@operamail.com wrote: I downloaded the source for kernel version 3.0.4 from www.kernel.org. I then booted to the Deiban squeeze partition and as superuser, unpacked the kernel source in one of my own directories. I ran make targets to get what config commands were available. I installed qt4-dev files from the Debian squeeze DVD and did make xconfig which gave me a configuration screen for the new kernel source. I then ploughed through all the options, removing modules where I was sure I did not have the relevant hardware. I eventually did make-kpkg clean, then make- kpkg debian and then make-kpkg --targets, chose binary and issued make-kpkg binary The kernel was compiled and after much activity, make-kpkg returned me to the command line. In the directory above the top of the source tree were a number of Debian packages which included linux-image-3.0.4_3.0.4-10.00.Custom_i386.deb which I installed using dpkg. grub was run which found the Linux kernels as well as Ubuntu 11.10. I closed down squeeze, rebooted and chose the new 3.0.4 kernel. It displayed an error message (kernel panic) to the effect that it could not load the root fs. What have I done wrong? I remember not choosing the option for an initramfs. What would be put in it if I had chosen that option? I use: make-kpkg --revision 1 --append-to-version -amd64 --initrd kernel_image which installs an initrd.img for an initramfs, but it will depend upon the config that you ended up with. Hugo -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/j8ka66$doe$1...@dough.gmane.org
creaing new 3.0.4 kernel in squeeze --kernel panic
I downloaded the source for kernel version 3.0.4 from www.kernel.org. I then booted to the Deiban squeeze partition and as superuser, unpacked the kernel source in one of my own directories. I ran make targets to get what config commands were available. I installed qt4-dev files from the Debian squeeze DVD and did make xconfig which gave me a configuration screen for the new kernel source. I then ploughed through all the options, removing modules where I was sure I did not have the relevant hardware. I eventually did make-kpkg clean, then make- kpkg debian and then make-kpkg --targets, chose binary and issued make-kpkg binary The kernel was compiled and after much activity, make-kpkg returned me to the command line. In the directory above the top of the source tree were a number of Debian packages which included linux-image-3.0.4_3.0.4-10.00.Custom_i386.deb which I installed using dpkg. grub was run which found the Linux kernels as well as Ubuntu 11.10. I closed down squeeze, rebooted and chose the new 3.0.4 kernel. It displayed an error message (kernel panic) to the effect that it could not load the root fs. What have I done wrong? I remember not choosing the option for an initramfs. What would be put in it if I had chosen that option? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50833057-0988-4022-9f24-28b06e0e6...@hj4g2000vbb.googlegroups.com
