Re: (SOLVED) Re: Backported Kernel - install question
On Saturday 14 December 2013 12:06 PM, Kailash Kalyani wrote: On Friday 13 December 2013 02:32 AM, Reco wrote: Hi. On Thu, 12 Dec 2013 21:33:45 +0100 Ralf Mardorf ralf.mard...@alice-dsl.net wrote: On Thu, 2013-12-12 at 21:32 +0100, Ralf Mardorf wrote: I experienced that synaptic for *buntu Saucy is broken, perhaps it's for Debian broken too. Sometimes nothing is inconsistent, but Synaptic claims that a dependency should be broken. After closing and opening Synaptic everything is ok. If apt-get does work, than a not buggy Synaptic must work too ;). apt, aptitude and synaptic handle package install conflicts differently. These tools do the same in trivial situations like installing or removing package from the main archive. But, put a number of packages with the same name and different versions (add versioned dependencies to the picture) - and these 3 tools start behaving differently. Add the fact that any package in backports archive has special version that is _lower_ that any version in main archive - and sometimes these tools may produce funny results. Basically, apt provides you with the most dumb solution possible (works most of the time) - install what you want, upgrade dependencies. Aptitude gives you multiple ways of installing package (and one has to choose carefully) - install what you want, upgrade/downgrade dependencies (and may remove something just for fun :). Synaptic assumes that you are not lazy, and will use Ctrl+E (IIRC, may be wrong) to force particular versions for needed packages. So, it's possible to use Synaptic for the task, it just will violate the great IBM principle - 'People should think, machine should work'. Reco Hi, Apt-get gave me the following error: The following packages have unmet dependencies: linux-image-3.11-0.bpo.2-686-pae : Breaks: initramfs-tools ( 0.110~) but 0.109.1 is to be installed E: Unable to correct problems, you have held broken packages. And so I installed initramfs-tools from wheezy-backports first and then the linux-image-3.11-0.bpo.2-686-pae However, was apt-get correct in not attempting to upgrade initramfs-tools as well? Thanks, Kailash FYI only. My new install of the kernel caused VirtualBox to stop functioning: I followed the following steps: 1. Installed the wheezy-backports version of VirtualBox (no change- the kernel modules failed to start) 2. Tried to check versions of dkms - have the latest stable (no updates in backports) 3. After looking through VirtualBox installation page (http://www.virtualbox.org/manual/ch02.html#install-linux-host) I figured I was missing the headers for the new kernel. 4. sudo apt-get install linux-headers-3.11-0.bpo.2-686-pae followed by sudo apt-get install virtualbox/wheezy-backports --reinstall fixed the issue. Hope this helps. K. -- 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/52ac1505.9040...@gmail.com
Re: (SOLVED) Re: Backported Kernel - install question
Hi. On Sat, 14 Dec 2013 12:06:15 +0530 Kailash Kalyani listskail...@gmail.com wrote: Apt-get gave me the following error: The following packages have unmet dependencies: linux-image-3.11-0.bpo.2-686-pae : Breaks: initramfs-tools ( 0.110~) but 0.109.1 is to be installed E: Unable to correct problems, you have held broken packages. And so I installed initramfs-tools from wheezy-backports first and then the linux-image-3.11-0.bpo.2-686-pae However, was apt-get correct in not attempting to upgrade initramfs-tools as well? Yes, it was. Compare this: # apt-get install linux-image-3.11-0.bpo.2-amd64 The following information may help to resolve the situation: The following packages have unmet dependencies: linux-image-3.11-0.bpo.2-amd64 : Breaks: initramfs-tools ( 0.110~) but 0.109.1 is to be installed E: Unable to correct problems, you have held broken packages To this: apt-get install -t wheezy-backports linux-image-3.11-0.bpo.2-amd64 The following extra packages will be installed: initramfs-tools Suggested packages: linux-doc-3.11 debian-kernel-handbook The following NEW packages will be installed: linux-image-3.11-0.bpo.2-amd64 The following packages will be upgraded: initramfs-tools Unless you allow apt to search dependencies outside of preferred release (wheezy) - it will try to install from backports only the package you've told it to install (i.e. linux-image). Reco -- 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/20131214125254.1cfd76cc50fd9cdf2c4fb...@gmail.com
Re: (SOLVED) Re: Backported Kernel - install question
On Saturday 14 December 2013 02:22 PM, Reco wrote: Hi. On Sat, 14 Dec 2013 12:06:15 +0530 Kailash Kalyani listskail...@gmail.com wrote: Apt-get gave me the following error: The following packages have unmet dependencies: linux-image-3.11-0.bpo.2-686-pae : Breaks: initramfs-tools ( 0.110~) but 0.109.1 is to be installed E: Unable to correct problems, you have held broken packages. And so I installed initramfs-tools from wheezy-backports first and then the linux-image-3.11-0.bpo.2-686-pae However, was apt-get correct in not attempting to upgrade initramfs-tools as well? Yes, it was. Compare this: # apt-get install linux-image-3.11-0.bpo.2-amd64 The following information may help to resolve the situation: The following packages have unmet dependencies: linux-image-3.11-0.bpo.2-amd64 : Breaks: initramfs-tools ( 0.110~) but 0.109.1 is to be installed E: Unable to correct problems, you have held broken packages To this: apt-get install -t wheezy-backports linux-image-3.11-0.bpo.2-amd64 The following extra packages will be installed: initramfs-tools Suggested packages: linux-doc-3.11 debian-kernel-handbook The following NEW packages will be installed: linux-image-3.11-0.bpo.2-amd64 The following packages will be upgraded: initramfs-tools Unless you allow apt to search dependencies outside of preferred release (wheezy) - it will try to install from backports only the package you've told it to install (i.e. linux-image). Reco Thanks for the clarification! Much appreciated! K -- 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/52ac28ea.6070...@gmail.com
(SOLVED) Re: Backported Kernel - install question
On Friday 13 December 2013 02:32 AM, Reco wrote: Hi. On Thu, 12 Dec 2013 21:33:45 +0100 Ralf Mardorf ralf.mard...@alice-dsl.net wrote: On Thu, 2013-12-12 at 21:32 +0100, Ralf Mardorf wrote: I experienced that synaptic for *buntu Saucy is broken, perhaps it's for Debian broken too. Sometimes nothing is inconsistent, but Synaptic claims that a dependency should be broken. After closing and opening Synaptic everything is ok. If apt-get does work, than a not buggy Synaptic must work too ;). apt, aptitude and synaptic handle package install conflicts differently. These tools do the same in trivial situations like installing or removing package from the main archive. But, put a number of packages with the same name and different versions (add versioned dependencies to the picture) - and these 3 tools start behaving differently. Add the fact that any package in backports archive has special version that is _lower_ that any version in main archive - and sometimes these tools may produce funny results. Basically, apt provides you with the most dumb solution possible (works most of the time) - install what you want, upgrade dependencies. Aptitude gives you multiple ways of installing package (and one has to choose carefully) - install what you want, upgrade/downgrade dependencies (and may remove something just for fun :). Synaptic assumes that you are not lazy, and will use Ctrl+E (IIRC, may be wrong) to force particular versions for needed packages. So, it's possible to use Synaptic for the task, it just will violate the great IBM principle - 'People should think, machine should work'. Reco Hi, Apt-get gave me the following error: The following packages have unmet dependencies: linux-image-3.11-0.bpo.2-686-pae : Breaks: initramfs-tools ( 0.110~) but 0.109.1 is to be installed E: Unable to correct problems, you have held broken packages. And so I installed initramfs-tools from wheezy-backports first and then the linux-image-3.11-0.bpo.2-686-pae However, was apt-get correct in not attempting to upgrade initramfs-tools as well? Thanks, Kailash -- 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/52abfc5f.1010...@gmail.com
Re: Backported Kernel - install question
Hi. On Fri, 13 Dec 2013 00:17:02 +0530 Kailash Kalyani listskail...@gmail.com wrote: My understanding is that it should be possible to install backports without breaking a stable install. What am I missing? Sure, it is possible. You're just using wrong tool for the task. Try: apt-get install -t wheezy-backports linux-image-3.11-0.bpo.2-686-pae Reco -- 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/20131212230317.0c983c58b8cc0e7d2eb38...@gmail.com
Re: Backported Kernel - install question
On Thu, 2013-12-12 at 23:03 +0400, Reco wrote: Hi. On Fri, 13 Dec 2013 00:17:02 +0530 Kailash Kalyani listskail...@gmail.com wrote: My understanding is that it should be possible to install backports without breaking a stable install. What am I missing? Sure, it is possible. You're just using wrong tool for the task. Try: apt-get install -t wheezy-backports linux-image-3.11-0.bpo.2-686-pae Reco I experienced that synaptic for *buntu Saucy is broken, perhaps it's for Debian broken too. Sometimes nothing is inconsistent, but Synaptic claims that a dependency should be broken. After closing and opening Synaptic everything is ok. -- 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/1386880328.688.2.camel@archlinux
Re: Backported Kernel - install question
On Thu, 2013-12-12 at 21:32 +0100, Ralf Mardorf wrote: On Thu, 2013-12-12 at 23:03 +0400, Reco wrote: Hi. On Fri, 13 Dec 2013 00:17:02 +0530 Kailash Kalyani listskail...@gmail.com wrote: My understanding is that it should be possible to install backports without breaking a stable install. What am I missing? Sure, it is possible. You're just using wrong tool for the task. Try: apt-get install -t wheezy-backports linux-image-3.11-0.bpo.2-686-pae Reco I experienced that synaptic for *buntu Saucy is broken, perhaps it's for Debian broken too. Sometimes nothing is inconsistent, but Synaptic claims that a dependency should be broken. After closing and opening Synaptic everything is ok. If apt-get does work, than a not buggy Synaptic must work too ;). -- 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/1386880425.688.3.camel@archlinux
Re: Backported Kernel - install question
Hi. On Thu, 12 Dec 2013 21:33:45 +0100 Ralf Mardorf ralf.mard...@alice-dsl.net wrote: On Thu, 2013-12-12 at 21:32 +0100, Ralf Mardorf wrote: I experienced that synaptic for *buntu Saucy is broken, perhaps it's for Debian broken too. Sometimes nothing is inconsistent, but Synaptic claims that a dependency should be broken. After closing and opening Synaptic everything is ok. If apt-get does work, than a not buggy Synaptic must work too ;). apt, aptitude and synaptic handle package install conflicts differently. These tools do the same in trivial situations like installing or removing package from the main archive. But, put a number of packages with the same name and different versions (add versioned dependencies to the picture) - and these 3 tools start behaving differently. Add the fact that any package in backports archive has special version that is _lower_ that any version in main archive - and sometimes these tools may produce funny results. Basically, apt provides you with the most dumb solution possible (works most of the time) - install what you want, upgrade dependencies. Aptitude gives you multiple ways of installing package (and one has to choose carefully) - install what you want, upgrade/downgrade dependencies (and may remove something just for fun :). Synaptic assumes that you are not lazy, and will use Ctrl+E (IIRC, may be wrong) to force particular versions for needed packages. So, it's possible to use Synaptic for the task, it just will violate the great IBM principle - 'People should think, machine should work'. Reco -- 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/20131213010245.46f9feb53fc50bafd5390...@gmail.com
Re: LILO not run after kernel install/update
Matus UHLAR - fantomas uh...@fantomas.sk writes: Well, re-sending since nobody replied... P.S. no, I won't use grub. Hmmm. Maybe the two sentences are related. Even me, kicking and screaming, finally am using grub (grub2). Let's see. Apparently I just use $ tail /etc/default/grub GRUB_TERMINAL=console case $(hostname) in *1) GRUB_TIMEOUT=45;; *) GRUB_TIMEOUT=11;; esac #jidanni # Local Variables: # compile-command: update-grub grub-install /dev/hda #in emacs # End: -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
LILO not run after kernel install/update
Well, re-sending since nobody replied... On 02.06.09 18:52, Matus UHLAR - fantomas wrote: I noticed that in lenny, installing new linux image doesn't cause lilo to be run, therefore the system might get unbootable. I don't see any info about lilo (or any boot loader) being called Is there any docs about this and is there any way to cause lilo run after kernel image install? I have /etc/kernel-img.conf with do_bootloader = Yes for a long time, even tried loader = lilo (after reading the postinst) but is did not help. P.S. no, I won't use grub. -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Posli tento mail 100 svojim znamim - nech vidia aky si idiot Send this email to 100 your friends - let them see what an idiot you are -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: incomplete kernel install, etch-backports
Mark Copper mcop...@titaninterface.com: I'm trying to update an older system to Etch. I'm following Release Notes for Debian GNU/Linux 4.0. For hardware reasons, I ran the command aptitude -t etch-backports install linux-image-2.6-686 Output for the command aptitude show linux-image-2.6-686 includes State: installed However, even after running lilo, /vmlinuz is still symlinked to the old kernel. Is this related to the message I received during the installation, that the boot loader needed to be configured to use an initrd? And if so, where do I find out how to do this? Is boot support for your system enabled in that kernel (root fs etc)? Please describe your system (lvm/RAID, where's /, hardware, ...). -- Any technology distinguishable from magic is insufficiently advanced. (*)http://www.xs4all.nl/~js/gnksa/ Linux Counter #80292 - -http://www.faqs.org/rfcs/rfc1855.htmlPlease, don't Cc: me. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
incomplete kernel install, etch-backports
Hi, I'm trying to update an older system to Etch. I'm following Release Notes for Debian GNU/Linux 4.0. For hardware reasons, I ran the command aptitude -t etch-backports install linux-image-2.6-686 Output for the command aptitude show linux-image-2.6-686 includes State: installed However, even after running lilo, /vmlinuz is still symlinked to the old kernel. Is this related to the message I received during the installation, that the boot loader needed to be configured to use an initrd? And if so, where do I find out how to do this? Thank you. Mark -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Kernel install problem
Bob McGowan wrote: Roberto C. Sanchez wrote: On Thu, Mar 01, 2007 at 12:09:49PM -0500, Kevin Mark wrote: why do you use /boot/boot/grub/ and not the default /boot/grub/? what is in /boot/grub/menu.lst vs /boot/boot/grub/menu.lst ? Using /boot/boot/grub is necessary when /boot is its own filesystem. Regards, -Roberto Not so. My setup is: $ uname -r 2.6.18-3-686 $ mount|grep boot /dev/sda1 on /boot type ext3 (rw) $ ls /boot/*2.6.18-3-686* /boot/System.map-2.6.18-3-686 /boot/initrd.img-2.6.18-3-686 /boot/config-2.6.18-3-686 /boot/vmlinuz-2.6.18-3-686 $grep boot /etc/fstab /dev/sda1 /bootext3defaults 0 2 My /boot/grub/menu.lst for the default boot: title Debian GNU/Linux, kernel 2.6.18-3-686 root(hd0,0) kernel /vmlinuz-2.6.18-3-686 root=LABEL=/root ro initrd /initrd.img-2.6.18-3-686 === NOTE that the path names for the kernel and initrd image DO NOT have a leading '/boot', this is because, for the filesystem on /dev/sda1, these files are 'connected' to the filesystem's 'root', which ONLY becomes /boot/... when the system is up and running, with filesystems from the fstab file mounted. The above was set up automatically, during the install, by the Debian installer. I explicitly selected to have '/boot' be a separate file system. I suspect the OP's problem is, in fact, because of the differences between what the actual setup is and what the dpkg scripts expect. I further conjecture that the original install was with /boot on the root filesystem, and that a later decision was made to change it, with the boot files on a separate filesystem. To fix this, as root: # cd /boot/boot # mv * .. # no hidden files to worry about. # cd .. # rmdir boot # edit /etc/fstab - add/modify line to mount the boot partition, see above example # edit grub/menu.lst - to fix any kernel/initrd paths, removing /boot, see above example # reboot ... # apt-get update Of course, you should make backups of everything, just in case. And, rather than just removing the extra 'boot' directory, you might also want to do 'ln -s . boot', so if there are any residual dependencies on /boot/boot/..., they will automatically resolve to the right place. Bob Thanks for the help. I've have indeed got /boot on it's own partition. I apt installed grub an age ago and it created /boot/boot itself - I thought it a little odd at the time. Perhaps the install scripts weren't very clever way back when it was installed. The machine has been running Debian for a long time - it started out on late 2.2 kernels - and up until now grub has updated fine when a new kernel is installed even with the /boot/boot oddness. I'm wondering if something has changed with the way new kernels are installed. I was actually thinking about retiring the machine any way as it's getting a bit long in the tooth. As it's a server and currently providing some vital network services I can't realistically afford large amounts of down time on it so I think I'll hold off making the changes you suggest. Many thanks though. Graham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Kernel install problem
I tried to do an update this morning and ran into the problem below when it came to installing the kernel. I've looked in /boot/boot/grub/menu.lst and the new kernel 2.6.18-4 hasn't been added (I'm running 2.6.18-3 and that is the top kernel in the list). Any ideas what's gone wrong? dpkg: dependency problems prevent configuration of linux-image-2.6-486: linux-image-2.6-486 depends on linux-image-2.6.18-4-486; however: Package linux-image-2.6.18-4-486 is not configured yet. dpkg: error processing linux-image-2.6-486 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-2.6.18-4-486 linux-image-2.6-486 E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up linux-image-2.6.18-4-486 (2.6.18.dfsg.1-11) ... Running depmod. Finding valid ramdisk creators. Using mkinitramfs-kpkg to build the ramdisk. Running postinst hook script /usr/sbin/update-grub. Searching for GRUB installation directory ... found: /boot/boot/grub Searching for default file ... Generating /boot/boot/grub/default file and setting the default boot entry to 0 No GRUB directory found under / User postinst hook script [/usr/sbin/update-grub] exited with value 1 dpkg: error processing linux-image-2.6.18-4-486 (--configure): subprocess post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of linux-image-2.6-486: linux-image-2.6-486 depends on linux-image-2.6.18-4-486; however: Package linux-image-2.6.18-4-486 is not configured yet. dpkg: error processing linux-image-2.6-486 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-2.6.18-4-486 linux-image-2.6-486 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel install problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Mar 01, 2007 at 09:54:14AM +, Graham Smith wrote: I tried to do an update this morning and ran into the problem below when it came to installing the kernel. I've looked in /boot/boot/grub/menu.lst and the new kernel 2.6.18-4 hasn't been added (I'm running 2.6.18-3 and that is the top kernel in the list). Any ideas what's gone wrong? dpkg: dependency problems prevent configuration of linux-image-2.6-486: linux-image-2.6-486 depends on linux-image-2.6.18-4-486; however: Package linux-image-2.6.18-4-486 is not configured yet. dpkg: error processing linux-image-2.6-486 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-2.6.18-4-486 linux-image-2.6-486 E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up linux-image-2.6.18-4-486 (2.6.18.dfsg.1-11) ... Running depmod. Finding valid ramdisk creators. Using mkinitramfs-kpkg to build the ramdisk. Running postinst hook script /usr/sbin/update-grub. Searching for GRUB installation directory ... found: /boot/boot/grub Searching for default file ... Generating /boot/boot/grub/default file and setting the default boot entry to 0 No GRUB directory found under / User postinst hook script [/usr/sbin/update-grub] exited with value 1 dpkg: error processing linux-image-2.6.18-4-486 (--configure): subprocess post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of linux-image-2.6-486: linux-image-2.6-486 depends on linux-image-2.6.18-4-486; however: Package linux-image-2.6.18-4-486 is not configured yet. dpkg: error processing linux-image-2.6-486 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-2.6.18-4-486 linux-image-2.6-486 why do you use /boot/boot/grub/ and not the default /boot/grub/? what is in /boot/grub/menu.lst vs /boot/boot/grub/menu.lst ? - -- | .''`. == Debian GNU/Linux == | my web site: | | : :' : The Universal |mysite.verizon.net/kevin.mark/| | `. `' Operating System| go to counter.li.org and | | `-http://www.debian.org/ |be counted! #238656 | | my keyserver: subkeys.pgp.net | my NPO: cfsg.org | -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFF5wjdv8UcC1qRZVMRAqZtAJ9NyXfjAeKlKtKGQySnq0YGYXoUSwCffyrP hn2ZnuT3QAKUejka8g3VgVM= =uqLY -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel install problem
On Thu, Mar 01, 2007 at 12:09:49PM -0500, Kevin Mark wrote: why do you use /boot/boot/grub/ and not the default /boot/grub/? what is in /boot/grub/menu.lst vs /boot/boot/grub/menu.lst ? Using /boot/boot/grub is necessary when /boot is its own filesystem. Regards, -Roberto -- Roberto C. Sanchez http://people.connexer.com/~roberto http://www.connexer.com signature.asc Description: Digital signature
Re: Kernel install problem
Roberto C. Sanchez wrote: On Thu, Mar 01, 2007 at 12:09:49PM -0500, Kevin Mark wrote: why do you use /boot/boot/grub/ and not the default /boot/grub/? what is in /boot/grub/menu.lst vs /boot/boot/grub/menu.lst ? Using /boot/boot/grub is necessary when /boot is its own filesystem. I'd think most people with that setup have /boot/boot symlinked to /boot ? -- Håkon Alstadheimtlf: 74 82 60 27 mob: 47 35 39 38 7510 Skatval http://alstadheim.priv.no/hakon/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel install problem
On Thu, Mar 01, 2007 at 06:36:38PM +0100, Håkon Alstadheim wrote: Roberto C. Sanchez wrote: On Thu, Mar 01, 2007 at 12:09:49PM -0500, Kevin Mark wrote: why do you use /boot/boot/grub/ and not the default /boot/grub/? what is in /boot/grub/menu.lst vs /boot/boot/grub/menu.lst ? Using /boot/boot/grub is necessary when /boot is its own filesystem. I'd think most people with that setup have /boot/boot symlinked to /boot ? You can't do that becasue the first thing grub looks for is the boot/ directory on the root filesystem. If /boot is a separate partition, it is the first thing that grub sees, and so it looks for boot/ under it. When we mount it on /boot, it ends up looking to us (but not to grub) as /boot/boot. Regards, -Roberto -- Roberto C. Sanchez http://people.connexer.com/~roberto http://www.connexer.com signature.asc Description: Digital signature
Re: Kernel install problem
Roberto C. Sanchez wrote: On Thu, Mar 01, 2007 at 12:09:49PM -0500, Kevin Mark wrote: why do you use /boot/boot/grub/ and not the default /boot/grub/? what is in /boot/grub/menu.lst vs /boot/boot/grub/menu.lst ? Using /boot/boot/grub is necessary when /boot is its own filesystem. Regards, -Roberto Not so. My setup is: $ uname -r 2.6.18-3-686 $ mount|grep boot /dev/sda1 on /boot type ext3 (rw) $ ls /boot/*2.6.18-3-686* /boot/System.map-2.6.18-3-686 /boot/initrd.img-2.6.18-3-686 /boot/config-2.6.18-3-686 /boot/vmlinuz-2.6.18-3-686 $grep boot /etc/fstab /dev/sda1 /bootext3defaults 0 2 My /boot/grub/menu.lst for the default boot: title Debian GNU/Linux, kernel 2.6.18-3-686 root(hd0,0) kernel /vmlinuz-2.6.18-3-686 root=LABEL=/root ro initrd /initrd.img-2.6.18-3-686 === NOTE that the path names for the kernel and initrd image DO NOT have a leading '/boot', this is because, for the filesystem on /dev/sda1, these files are 'connected' to the filesystem's 'root', which ONLY becomes /boot/... when the system is up and running, with filesystems from the fstab file mounted. The above was set up automatically, during the install, by the Debian installer. I explicitly selected to have '/boot' be a separate file system. I suspect the OP's problem is, in fact, because of the differences between what the actual setup is and what the dpkg scripts expect. I further conjecture that the original install was with /boot on the root filesystem, and that a later decision was made to change it, with the boot files on a separate filesystem. To fix this, as root: # cd /boot/boot # mv * .. # no hidden files to worry about. # cd .. # rmdir boot # edit /etc/fstab - add/modify line to mount the boot partition, see above example # edit grub/menu.lst - to fix any kernel/initrd paths, removing /boot, see above example # reboot ... # apt-get update Of course, you should make backups of everything, just in case. And, rather than just removing the extra 'boot' directory, you might also want to do 'ln -s . boot', so if there are any residual dependencies on /boot/boot/..., they will automatically resolve to the right place. Bob smime.p7s Description: S/MIME Cryptographic Signature
Re: Kernel install problem
On Thu, Mar 01, 2007 at 10:08:25AM -0800, Bob McGowan wrote: Roberto C. Sanchez wrote: On Thu, Mar 01, 2007 at 12:09:49PM -0500, Kevin Mark wrote: why do you use /boot/boot/grub/ and not the default /boot/grub/? what is in /boot/grub/menu.lst vs /boot/boot/grub/menu.lst ? Using /boot/boot/grub is necessary when /boot is its own filesystem. Regards, -Roberto Not so. My setup is: $ uname -r 2.6.18-3-686 $ mount|grep boot /dev/sda1 on /boot type ext3 (rw) $ ls /boot/*2.6.18-3-686* /boot/System.map-2.6.18-3-686 /boot/initrd.img-2.6.18-3-686 /boot/config-2.6.18-3-686 /boot/vmlinuz-2.6.18-3-686 $grep boot /etc/fstab /dev/sda1 /bootext3defaults 0 2 My /boot/grub/menu.lst for the default boot: title Debian GNU/Linux, kernel 2.6.18-3-686 root(hd0,0) kernel /vmlinuz-2.6.18-3-686 root=LABEL=/root ro initrd /initrd.img-2.6.18-3-686 Hmmm. My system started out on Woody a long time ago and I gave messed with the partition scheme several times, so that might be why I have mine like that. Regards, -Roberto -- Roberto C. Sanchez http://people.connexer.com/~roberto http://www.connexer.com signature.asc Description: Digital signature
Re: Kernel install problem
On Thu, Mar 01, 2007 at 01:03:07PM -0500, Roberto C. Sanchez wrote: On Thu, Mar 01, 2007 at 06:36:38PM +0100, Håkon Alstadheim wrote: Roberto C. Sanchez wrote: On Thu, Mar 01, 2007 at 12:09:49PM -0500, Kevin Mark wrote: why do you use /boot/boot/grub/ and not the default /boot/grub/? what is in /boot/grub/menu.lst vs /boot/boot/grub/menu.lst ? Using /boot/boot/grub is necessary when /boot is its own filesystem. I'd think most people with that setup have /boot/boot symlinked to /boot ? You can't do that becasue the first thing grub looks for is the boot/ directory on the root filesystem. If /boot is a separate partition, it is the first thing that grub sees, and so it looks for boot/ under it. When we mount it on /boot, it ends up looking to us (but not to grub) as /boot/boot. I thought the /boot/boot thing came from installing grub incorrectly. When I have been too smart for my own good and applied a --root-directory switch to grub-install, its ended up in /boot/boot. If I just let it work on its own it end sup in /boot. This is with /boot on a seperate partition. At elast once, I've messed up and had it in /boot/boot and just mv'ed it up one level and all works well. A signature.asc Description: Digital signature
Re: Dell inspiron 4100... custom kernel install
On 10/6/05, James Gibbon [EMAIL PROTECTED] wrote: On 10/5/05, Felipe Törnvall N. [EMAIL PROTECTED] wrote: En español haber si entiendo bien tu problema es en el momento de la instalacion de debian ??? lo haces con la imagen que viene por defecto ??? Apesadumbrado, mi español es muy malo Mi problema no es la instalación. Mi problema está con el Kernel. Necesito un nuevo kernel para el proceso de la instalación James Apesadumbrado, Debo haber dicho que necesito un kernel en la ISO debian. mi sistema es inestable demasiado trabajar encendido Translated to english: My kernel issues have nothing to do with a bad installation. I need to create a custom kernel and stick it onto a Debian iso for re-installation of the base system. The kernel has made my laptop too unstable to recompile a kernel without crashing. James
Re: Dell inspiron 4100... custom kernel install
On 10/6/05, James Gibbon [EMAIL PROTECTED] wrote: On 10/6/05, James Gibbon [EMAIL PROTECTED] wrote: On 10/5/05, Felipe Törnvall N. [EMAIL PROTECTED] wrote: En español haber si entiendo bien tu problema es en el momento de la instalacion de debian ??? lo haces con la imagen que viene por defecto ??? Apesadumbrado, mi español es muy malo Mi problema no es la instalación. Mi problema está con el Kernel. Necesito un nuevo kernel para el proceso de la instalación James Apesadumbrado, Debo haber dicho que necesito un kernel en la ISO debian. mi sistema es inestable demasiado trabajar encendido Translated to english: My kernel issues have nothing to do with a bad installation. I need to create a custom kernel and stick it onto a Debian iso for re-installation of the base system. The kernel has made my laptop too unstable to recompile a kernel without crashing. James Nevermind. I got it figured out on my own. Thanks anyways James
Dell inspiron 4100... custom kernel install
I'm having a bit of trouble installing Debian on my inspiron 4100. I've identified the problem. The solution is in a kernel rebuild. I can't get the kernel to rebuild because the system freezes before the laptop can rebuild the kernel. It doesn't usually stay alive for more than two or three minutes before it freezes up. how can I reinstall the whole system using a custom kernel? If anyone could give me a link that would be great. I'm not even sure of what to google, so that would be good too. I don't need my hand held, just let me know what I'm looking for. James Gibbon
Kernel, install manually or through apt?
Hi everybody, I'm experimenting with the linux kernels, and have so far tried to kernels available through apt-get, namely 2.4.27-1-386 (standard with the installation in sarge) and 2.6.8-2-686 (running today). Is there an easy to understand howto on manually installing a kernel from kernel.org etc. for a newbie? Are there more kernels available with apt, by adding lines to sources.list? Besides that, if anyone have som hints or experinences to share with me, I am all ears! Thanks in advance, Vegard
Re: Kernel, install manually or through apt?
On Mon, May 30, 2005 at 11:26:00PM +0200, Vegard|drageV wrote: Hi everybody, I'm experimenting with the linux kernels, and have so far tried to kernels available through apt-get, namely 2.4.27-1-386 (standard with the installation in sarge) and 2.6.8-2-686 (running today). Is there an easy to understand howto on manually installing a kernel from kernel.org etc. for a newbie? Are there more kernels available with apt, by adding lines to sources.list? Besides that, if anyone have som hints or experinences to share with me, I am all ears! Thanks in advance, Vegard This will give you all the information you need about custom kernel building for Debian: http://newbiedoc.sourceforge.net/system/kernel-pkg.html -Roberto -- Roberto C. Sanchez http://familiasanchez.net/~sanchezr pgp5h3aWmevGp.pgp Description: PGP signature
kernel install on a Cobalt Raq4
Hi, Anyone succeeded in installing a Debian Woody distribution on a Cobalt Raq (4)? Pleasy help me out. Perhaps this is a more generic question, how to install a Debian kernel on an empty machine (only with debootstrap initialized), which is temporarly booted from the net with NFS. I followed the fine instructions on http://cobalt.iceblink.org/debian/debian- cobalt-howto.txt and succeeded for most steps. When I got at step 9, to download a debian kernel, me as newbie, don't know where start from here. I tried to downloaded the kernel-image-2.4.18-k6 package and all its dependencies from the debian site and installed them on the system (dpkg). The installation of some packages gave some errors which i did not know how to resolve. I was chrooted to the new and mounted filesystem root. The dpkg with sysvinit gave some timeout errors: init: timeout opening/writing control channel /dev/initctl And dpkg with the kernel image gave: Failed to create initrd image. dpkg: error processing kernel-image-2.4.18-k6 (--install): subprocess post-installation script returned error exit status 29 Errors were encountered while processing: kernel-image-2.4.18-k6 I bzip2'ed the vmlinuz-2.4.18-k6 to /boot/vmlinux.bz2 (according the install instructions) but the bootup failed with various error messages. Anyone can help me with this? Following are the bootup messages: Sun Cobalt - Smaller, Bluer, Better, and Free Firmware version 2.10.3-ext3 Current date: Jun 24 14:41:22 UTC 2004 ROM build info: Thu Mar 11 08:51:36 MST 2004 . System serial number: invalid csum! System type: 3000 series system, Version 1 board Silicon serial number: 7807d7f59c01 Monitor: 153536 bytes Memory: 256 MB CPU: 1 processor(s) detected CPU 0: AuthenticAMD 448MHz (4.5 x 100MHz host bus) [BSP] Initializing flash: done Flash Bank 0: AMD AM29F080B 1024KB (01:d5) Flash Bank 1: not installed. Mounting ROM fs: done Initializing PCI: done Initializing ethernet: 2 controller(s) found Initializing IDE: found ALI M5229 at 00:78 scanning ide0: master scanning ide1: master IDE: stabilizing spinup: 100% Checking Memory: done Press spacebar to enter ROM mode Booting default method - From disk First stage kernel (Linux): Decompressing - done ERROR: cannot relocate with filesize 0 Second stage kernel: Decompressing -Error bunzip2ing kernel. Trying gunzip. - done Linux version 2.2.16C28_III ([EMAIL PROTECTED]) (gcc version egcs-2.91.66 1999 0314/Linux (egcs-1.1.2 release)) #1 Mon Jul 30 22:07:58 PDT 2001 Ignoring bogus EBDA pointer 3FF000 Detected 448220 kHz processor. Pending 0x00 Calibrating delay loop... 894.57 BogoMIPS Memory: 257572k/262144k available (1244k kernel code, 416k reserved, 2848k data, 64k init) Dentry hash table entries: 32768 (order 6, 256k) Buffer cache hash table entries: 262144 (order 8, 1024k) Page cache hash table entries: 65536 (order 6, 256k) VFS: Diskquotas version dquot_6.4.0 initialized CPU: L1 I Cache: 32K L1 D Cache: 32K CPU: L2 Cache: 128K CPU: AMD AMD-K6(tm)-III Processor stepping 04 Checking 386/387 coupling... OK, FPU using exception 16 error reporting. Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX PCI: Using configuration type 1 PCI: Probing PCI hardware Linux NET4.0 for Linux 2.2 Based upon Swansea University Computer Society NET3.039 NET4: Unix domain sockets 1.0 for Linux NET4.0. NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP TCP: Hash tables configured (ehash 262144 bhash 65536) Initializing RT netlink socket Starting kswapd v 1.5 Cobalt watchdog v1.4 enabled Cobalt I2C bus initialized Cobalt temperature sensor v1.3 enabled Serial driver version 4.27 with4keyboard: Timeout - AT keyboard not present? keyboard: Timeout - AT keyboard not present? no serial options enabled ttyS00 at 0x03f8 (irq = 4) is a 16550A ttyS01 at 0x02f8 (irq = 3) is a 16550A pty: 256 Unix98 ptys configured Real Time Clock Driver v1.09 lcd: Cobalt LCD Driver v3.12 serialnumber: Version 1.9 initialized. Serial number=7807d7f59c01. Copyright (c)1994-2000 Axent Technologies, Inc. Uniform Multi-Platform E-IDE driver Revision: 6.30 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx ALI15X3: IDE controller on PCI bus 00 dev 78 ALI15X3: chipset revision 193 ALI15X3: 100% native mode on irq 14 ide0: BM-DMA at 0xfdd0-0xfdd7, BIOS settings: hda:DMA, hdb:DMA ide1: BM-DMA at 0xfdd8-0xfddf, BIOS settings: hdc:DMA, hdd:DMA hda: ST320410A, ATA DISK drive ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx hdc: ST320410A, ATA DISK drive ide0 at 0xfdf8-0xfdff,0xfdf6 on irq 14 ide1 at 0xfde8-0xfdef,0xfde6 on irq 15 hda: ST320410A, 19092MB w/2048kB Cache, CHS=38792/16/63, UDMA(33) hdc: ST320410A, 19092MB w/2048kB Cache, CHS=38792/16/63, UDMA(33) md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12 translucent personality
kernel install on a Cobalt Raq4
Hi, Anyone succeeded in installing a Debian Woody distribution on a Cobalt Raq(4)? Pleasy help me out. Perhaps this is a more generic question, how to install a Debian kernel on an empty machine (only with debootstrap initialized), which is temporarly booted from the net with NFS. I followed the fine instructions on http://cobalt.iceblink.org/debian/debian- cobalt-howto.txt and succeeded for most steps. When I got at step 9, to download a debian kernel, me as newbie, don't know where start from here. I tried to downloaded the kernel-image-2.4.18-k6 package and all its dependencies from the debian site and installed them on the system (dpkg). The installation of some packages gave some errors which i did not know how to resolve. I was chrooted to the new and mounted filesystem root. The dpkg with sysvinit gave some timeout errors: init: timeout opening/writing control channel /dev/initctl And dpkg with the kernel image gave: Failed to create initrd image. dpkg: error processing kernel-image-2.4.18-k6 (--install): subprocess post-installation script returned error exit status 29 Errors were encountered while processing: kernel-image-2.4.18-k6 I bzip2'ed the vmlinuz-2.4.18-k6 to /boot/vmlinux.bz2 (according the install instructions) but the bootup failed with various error messages. Anyone can help me with this? Following are the bootup messages: Sun Cobalt - Smaller, Bluer, Better, and Free Firmware version 2.10.3-ext3 Current date: Jun 24 14:41:22 UTC 2004 ROM build info: Thu Mar 11 08:51:36 MST 2004 . System serial number: invalid csum! System type: 3000 series system, Version 1 board Silicon serial number: 7807d7f59c01 Monitor: 153536 bytes Memory: 256 MB CPU: 1 processor(s) detected CPU 0: AuthenticAMD 448MHz (4.5 x 100MHz host bus) [BSP] Initializing flash: done Flash Bank 0: AMD AM29F080B 1024KB (01:d5) Flash Bank 1: not installed. Mounting ROM fs: done Initializing PCI: done Initializing ethernet: 2 controller(s) found Initializing IDE: found ALI M5229 at 00:78 scanning ide0: master scanning ide1: master IDE: stabilizing spinup: 100% Checking Memory: done Press spacebar to enter ROM mode Booting default method - From disk First stage kernel (Linux): Decompressing - done ERROR: cannot relocate with filesize 0 Second stage kernel: Decompressing -Error bunzip2ing kernel. Trying gunzip. - done Linux version 2.2.16C28_III ([EMAIL PROTECTED]) (gcc version egcs-2.91.66 1999 0314/Linux (egcs-1.1.2 release)) #1 Mon Jul 30 22:07:58 PDT 2001 Ignoring bogus EBDA pointer 3FF000 Detected 448220 kHz processor. Pending 0x00 Calibrating delay loop... 894.57 BogoMIPS Memory: 257572k/262144k available (1244k kernel code, 416k reserved, 2848k data, 64k init) Dentry hash table entries: 32768 (order 6, 256k) Buffer cache hash table entries: 262144 (order 8, 1024k) Page cache hash table entries: 65536 (order 6, 256k) VFS: Diskquotas version dquot_6.4.0 initialized CPU: L1 I Cache: 32K L1 D Cache: 32K CPU: L2 Cache: 128K CPU: AMD AMD-K6(tm)-III Processor stepping 04 Checking 386/387 coupling... OK, FPU using exception 16 error reporting. Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX PCI: Using configuration type 1 PCI: Probing PCI hardware Linux NET4.0 for Linux 2.2 Based upon Swansea University Computer Society NET3.039 NET4: Unix domain sockets 1.0 for Linux NET4.0. NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP TCP: Hash tables configured (ehash 262144 bhash 65536) Initializing RT netlink socket Starting kswapd v 1.5 Cobalt watchdog v1.4 enabled Cobalt I2C bus initialized Cobalt temperature sensor v1.3 enabled Serial driver version 4.27 with4keyboard: Timeout - AT keyboard not present? keyboard: Timeout - AT keyboard not present? no serial options enabled ttyS00 at 0x03f8 (irq = 4) is a 16550A ttyS01 at 0x02f8 (irq = 3) is a 16550A pty: 256 Unix98 ptys configured Real Time Clock Driver v1.09 lcd: Cobalt LCD Driver v3.12 serialnumber: Version 1.9 initialized. Serial number=7807d7f59c01. Copyright (c)1994-2000 Axent Technologies, Inc. Uniform Multi-Platform E-IDE driver Revision: 6.30 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx ALI15X3: IDE controller on PCI bus 00 dev 78 ALI15X3: chipset revision 193 ALI15X3: 100% native mode on irq 14 ide0: BM-DMA at 0xfdd0-0xfdd7, BIOS settings: hda:DMA, hdb:DMA ide1: BM-DMA at 0xfdd8-0xfddf, BIOS settings: hdc:DMA, hdd:DMA hda: ST320410A, ATA DISK drive ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx hdc: ST320410A, ATA DISK drive ide0 at 0xfdf8-0xfdff,0xfdf6 on irq 14 ide1 at 0xfde8-0xfdef,0xfde6 on irq 15 hda: ST320410A, 19092MB w/2048kB Cache, CHS=38792/16/63, UDMA(33) hdc: ST320410A, 19092MB w/2048kB Cache, CHS=38792/16/63, UDMA(33) md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12 translucent personality registered linear personality registered raid0 personality registered raid1
Re: networking problem with 2.6.4 kernel [was: Re: 2.6.4 kernel install wants to remove current kernel]
on Mon, 12 Apr 2004 09:53:38PM -0400, Derrick 'dman' Hudson insinuated: On Mon, Apr 12, 2004 at 06:26:33PM -0400, Nori Heikkinen wrote: | on Mon, 12 Apr 2004 03:08:28PM -0400, Derrick 'dman' Hudson insinuated: | What version of the dhcp-client package do you have installed? | | 2.0pl5-11 That's the one from woody. If you don't mind running a newer system, not at all -- not only do i regularly grab more packages than i plan to from unstable, but i'm upgrading to the 2.6 stock kernel from debian -- certainly gonna run into some dependency issues there, i suppose. then I'd try the version from sarge that did it. yay! is it a bug in the kernel package that it doesn't tell me to upgrade to the newer dhcp-client package, too? or the 'dhcp3-client' package. I don't remember exactly, but I think I upgraded to dhcp3-client before I upgraded to kernel 2.6. It is conceivable that dhclient is somewhat tied to the kernel version. then it should be upgraded when i use apt/aptitude to grab a new kernel version, yes? thanks, dman. just confirming previous knowledge that you rock. /nori -- .~. nori @ sccs.swarthmore.edu /V\ http://www.sccs.swarthmore.edu/~nori/jnl/ // \\ @ maenad.net /( )\ www.maenad.net ^`~'^ pgp0.pgp Description: PGP signature
networking problem with 2.6.4 kernel [was: Re: 2.6.4 kernel install wants to remove current kernel]
on Fri, 09 Apr 2004 03:42:06PM -0400, Derrick 'dman' Hudson insinuated: On Fri, Apr 09, 2004 at 02:41:54PM -0400, Nori Heikkinen wrote: | on Fri, 09 Apr 2004 01:47:26PM -0400, Derrick 'dman' Hudson insinuated: | On Fri, Apr 09, 2004 at 12:32:10PM -0400, Nori Heikkinen wrote: [...] | | how, then, should i go about installing the kernel image? | | Try aptitude. Trace through the Depends/Conflicts and figure out | what's wrong. Something must be conflicting somewhere. (maybe you | just need to upgrade modutils while you install module-init-tools?) | | after a bit of poking in aptitude, which was very noninformative, It may take a little getting used to, but aptitude combines the data available from 'apt-cache show' and 'apt-cache policy' in a way that is navigable. What I would have done in your situation is gone to the 'modutils' package. Press enter to view the package's details. Some line in that view would most likely have been red indicating broken or magenta indicating will-be-removed. Scrolling through the display you can see what packages and versions are in the depends and conflicts tags for that package as well as the list of what packages (and versions) depend on or conflict with the current package. In hindsight, I now know that it would have shown that module-init-tools conflicts with modutils = 2.4.21-1 and your modutils fit that criteria (hence apt-get wanted to remove it to solve the conflict). cool. i feel like i did this and didn't find anything useful, but maybe i just didn't spend long enough poking. | i tried your suggestion of upgrading modutils (from 2.4.15-1 to | 2.4.26-1) -- beautiful. then the 2.6.4 kernel image goes on without | trying to remove everything and its mother. Lucky guess. :-). At least it worked for you. yeah, thanks :) | of course, i've totally failed to show the slickness of apt to my | coworker, because as soon as i booted up with 2.6.4, my mouse (neither | USB nor PS2) didn't work, and i wasn't online. (right now, i've | reverted to 2.4 to type this :-P). surely the 2.6 kernel comes with | USB support compiled in? am i just going to have to suck it up and | roll my own kernel? I'm using the stock 2.6 kernel on 5 machines. There are some differences from 2.4, though, mainly in the module and device driver organization. Some key differences, and probably the ones you are running into, : 2.4 2.6 --- --- usb-uhciuhci-hcd usb-ohciohci-hcd usb-ehciehci-hcd psmouse (the PS/2 mouse driver is in a module now) okay, excellent. thanks for pointong this out -- now i have a functional mouse under 2.6. I haven't noticed any changes in networking, but that might be dependent on the hardware and what modules I already had configured to be loaded. the network error i get when i try to reconfigure my network interfaces is below: Reconfiguring network interfaces: cat: /var/run/dhclient.pid: No such file or directory Unrecognized kernel version done. i can tell that _something's_ not recognizing my kernel version, but what is it? i probably just need to grab a newer package of something, but what? thanks again! /nori -- .~. nori @ sccs.swarthmore.edu /V\ http://www.sccs.swarthmore.edu/~nori/jnl/ // \\ @ maenad.net /( )\ www.maenad.net ^`~'^ pgp0.pgp Description: PGP signature
Re: networking problem with 2.6.4 kernel [was: Re: 2.6.4 kernel install wants to remove current kernel]
[back on-list] on Mon, 12 Apr 2004 02:02:06PM -0400, J F insinuated: I don't have a specific answer to your problem, but using aptitude seems to ease upgrade problems. Also, having testing, unstable, and stable all in /etc/apt/sources.list seems to get aptitude to converge on a working solution. yeah, i do have all of them in there. i'm relatively new to aptitude, and have never been a convert, specifically because every time i try to install any one thing with it, it wants to upgrade the rest of my system and install at least 50 new packages. i probably don't have it synched with something or other -- probably related to the error i see whenever i start it up: Apt errors W: Can't open Aptitude extended status file but these problems with aptitude make me shy away from it. am i using it wrong, or something? /nori -- .~. nori @ sccs.swarthmore.edu /V\ http://www.sccs.swarthmore.edu/~nori/jnl/ // \\ @ maenad.net /( )\ www.maenad.net ^`~'^ pgp0.pgp Description: PGP signature
Re: networking problem with 2.6.4 kernel [was: Re: 2.6.4 kernel install wants to remove current kernel]
On Mon, Apr 12, 2004 at 12:19:06PM -0400, Nori Heikkinen wrote: | on Fri, 09 Apr 2004 03:42:06PM -0400, Derrick 'dman' Hudson insinuated: [...] | I haven't noticed any changes in networking, but that might be | dependent on the hardware and what modules I already had configured | to be loaded. | | the network error i get when i try to reconfigure my network | interfaces is below: | | Reconfiguring network interfaces: | cat: /var/run/dhclient.pid: No such file or directory This message results from trying to stop dhclient while it isn't running. No harm done. | Unrecognized kernel version This I've never seen before. | done. | | i can tell that _something's_ not recognizing my kernel version, but | what is it? i probably just need to grab a newer package of | something, but what? What is your network card? What driver did you use with the 2.4 kernel? What does 'ifconfig -a' report? (is eth0 listed there?) What version of the dhcp-client package do you have installed? -D -- If you hold to [Jesus'] teaching, you are really [Jesus'] disciples. Then you will know the truth, and the truth will set you free. John 8:31-32 www: http://dman13.dyndns.org/~dman/jabber: [EMAIL PROTECTED] signature.asc Description: Digital signature
using apt/aptitude (was: Re: networking problem with 2.6.4 kernel [was: Re: 2.6.4 kernel install wants to remove current kernel])
On Mon, Apr 12, 2004 at 02:11:24PM -0400, Nori Heikkinen wrote: | [back on-list] | | on Mon, 12 Apr 2004 02:02:06PM -0400, J F insinuated: | I don't have a specific answer to your problem, | but using aptitude seems to ease upgrade problems. | Also, having testing, unstable, and stable all in | /etc/apt/sources.list seems to get aptitude | to converge on a working solution. | | yeah, i do have all of them in there. i'm relatively new to aptitude, | and have never been a convert, specifically because every time i try | to install any one thing with it, it wants to upgrade the rest of my | system and install at least 50 new packages. Big picture : apt normally prefers the version of a package with the biggest number aptitude in woody defaults to 'Aptitude::Auto-Upgrade true' As a result, when you have woody installed, have sarge (and/or sid) in apt's sources list, and you run aptitude, then aptitude wants to upgrade your system to sarge (and/or sid). I assume, from your comments, that you don't want that. There are several factors at play here and you can choose what specific semantics you want. I'll explain by telling about my system. I generally follow sarge, but not infrequently install packages from sid. I like to see what version is in what release with 'apt-cache policy'. Sometimes I don't want to upgrade all upgradeable packages when I run aptitude in gui mode. As a result I have the following setup : 1) woody, sarge, sid all listed in apt's source list 2) sarge preferred, followed by the installed version, followed by woody, and never prefer sid specified in /etc/apt/prefereces. 3) aptitude version from sarge, with 'Aptitude::Auto-Upgrade false' (default in that version) I recommend using the aptitude in sarge over the one in woody because it works correctly (usefully/conveniently) with Auto-Upgrade set to false. (the woody version changes the 'auto' flag to 'manual' when choosing to upgrade a package unless Auto-Upgrade chose to upgrade it) Also take a look at documentation regarding apt's preferences files. | i probably don't have it | synched with something or other -- probably related to the error i see | whenever i start it up: | | Apt errors | W: Can't open Aptitude extended status file I've never seen this message (that I recall). My first guess, though, is that you ran aptitude as a non-root user and as a result didn't have permission to create /var/lib/aptitude/pkgstates. HTH, -D -- GUIs normally make it simple to accomplish simple actions and impossible to accomplish complex actions. --Doug Gwyn (22/Jun/91 in comp.unix.wizards) www: http://dman13.dyndns.org/~dman/jabber: [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: networking problem with 2.6.4 kernel [was: Re: 2.6.4 kernel install wants to remove current kernel]
on Mon, 12 Apr 2004 03:08:28PM -0400, Derrick 'dman' Hudson insinuated: On Mon, Apr 12, 2004 at 12:19:06PM -0400, Nori Heikkinen wrote: | on Fri, 09 Apr 2004 03:42:06PM -0400, Derrick 'dman' Hudson insinuated: [...] | I haven't noticed any changes in networking, but that might be | dependent on the hardware and what modules I already had configured | to be loaded. | | the network error i get when i try to reconfigure my network | interfaces is below: | | Reconfiguring network interfaces: | cat: /var/run/dhclient.pid: No such file or directory This message results from trying to stop dhclient while it isn't running. No harm done. yeah, looked pretty innocuous ... | Unrecognized kernel version This I've never seen before. :-P | done. | | i can tell that _something's_ not recognizing my kernel version, but | what is it? i probably just need to grab a newer package of | something, but what? What is your network card? 02:0c.0 Ethernet controller: 3Com Corporation 3c905C-TX [Fast Etherlink] (rev 78) What driver did you use with the 2.4 kernel? i put in the 3c59x module for it. the same one exists with the 2.6 kernel ... is this what you mean? never been good with hardware configuration. What does 'ifconfig -a' report? (is eth0 listed there?) with the 2.4 kernel, yes (clearly -- i'm writing from that :). with the 2.6, also yes, but not configured: eth0 Link encap:Ethernet HWaddr 00:06:5B:5F:A0:30 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:18 Base address:0xdc80 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:12 errors:0 dropped:0 overruns:0 frame:0 TX packets:12 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:840 (840.0 b) TX bytes:840 (840.0 b) What version of the dhcp-client package do you have installed? 2.0pl5-11 a friend of mine heard i was installing the 2.6 kernel, and he said bad idea. i asked why, and he mentioned bad driver support -- maybe he means my ethernet card :-P thanks again! /nori -- .~. nori @ sccs.swarthmore.edu /V\ http://www.sccs.swarthmore.edu/~nori/jnl/ // \\ @ maenad.net /( )\ www.maenad.net ^`~'^ pgp0.pgp Description: PGP signature
Re: networking problem with 2.6.4 kernel [was: Re: 2.6.4 kernel install wants to remove current kernel]
Derrick 'dman' Hudson wrote: On Mon, Apr 12, 2004 at 02:11:24PM -0400, Nori Heikkinen wrote: | on Mon, 12 Apr 2004 02:02:06PM -0400, J F insinuated: | I don't have a specific answer to your problem, | but using aptitude seems to ease upgrade problems. | Also, having testing, unstable, and stable all in | /etc/apt/sources.list seems to get aptitude | to converge on a working solution. | | yeah, i do have all of them in there. i'm relatively new to aptitude, | and have never been a convert, specifically because every time i try | to install any one thing with it, it wants to upgrade the rest of my | system and install at least 50 new packages. Big picture : apt normally prefers the version of a package with the biggest number aptitude in woody defaults to 'Aptitude::Auto-Upgrade true' As a result, when you have woody installed, have sarge (and/or sid) in apt's sources list, and you run aptitude, then aptitude wants to upgrade your system to sarge (and/or sid). I assume, from your comments, that you don't want that. There are several factors at play here and you can choose what specific semantics you want. I'll explain by telling about my system. I generally follow sarge, but not infrequently install packages from sid. I like to see what version is in what release with 'apt-cache policy'. Sometimes I don't want to upgrade all upgradeable packages when I run aptitude in gui mode. As a result I have the following setup : 1) woody, sarge, sid all listed in apt's source list 2) sarge preferred, followed by the installed version, followed by woody, and never prefer sid specified in /etc/apt/prefereces. 3) aptitude version from sarge, with 'Aptitude::Auto-Upgrade false' (default in that version) I recommend using the aptitude in sarge over the one in woody because it works correctly (usefully/conveniently) with Auto-Upgrade set to false. (the woody version changes the 'auto' flag to 'manual' when choosing to upgrade a package unless Auto-Upgrade chose to upgrade it) Also take a look at documentation regarding apt's preferences files. | i probably don't have it | synched with something or other -- probably related to the error i see | whenever i start it up: | | Apt errors | W: Can't open Aptitude extended status file I've never seen this message (that I recall). My first guess, though, is that you ran aptitude as a non-root user and as a result didn't have permission to create /var/lib/aptitude/pkgstates. HTH, -D Also, you can press F10 to bring up the menu and press right cursor move (-) twice to highlight OPtions and then down cursor move key to highlight Miscellaneous and press spacebar on to remove [X] before phrase: Automatically upgrade install Packages . You can then search for the broken package by typing: /konqueror which would find the konqueror package. Type carriage return to see the things that it depends on or conflicts with. Type ? for help. Type + to upgrade or '= to hold at the current version of a package. ___ Join Excite! - http://www.excite.com The most personalized portal on the Web! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: networking problem with 2.6.4 kernel [was: Re: 2.6.4 kernel install wants to remove current kernel]
On Mon, Apr 12, 2004 at 06:26:33PM -0400, Nori Heikkinen wrote: | on Mon, 12 Apr 2004 03:08:28PM -0400, Derrick 'dman' Hudson insinuated: | On Mon, Apr 12, 2004 at 12:19:06PM -0400, Nori Heikkinen wrote: | | on Fri, 09 Apr 2004 03:42:06PM -0400, Derrick 'dman' Hudson insinuated: | [...] | | I haven't noticed any changes in networking, but that might be | | dependent on the hardware and what modules I already had configured | | to be loaded. | | | | the network error i get when i try to reconfigure my network | | interfaces is below: | | | | Reconfiguring network interfaces: | | | cat: /var/run/dhclient.pid: No such file or directory | | This message results from trying to stop dhclient while it isn't | running. No harm done. | | yeah, looked pretty innocuous ... | | | Unrecognized kernel version | | This I've never seen before. | | :-P | | | done. | | | | i can tell that _something's_ not recognizing my kernel version, but | | what is it? i probably just need to grab a newer package of | | something, but what? | | What is your network card? | | 02:0c.0 Ethernet controller: 3Com Corporation 3c905C-TX [Fast | Etherlink] (rev 78) Pretty normal. | What driver did you use with the 2.4 kernel? | | i put in the 3c59x module for it. the same one exists with the 2.6 | kernel ... is this what you mean? never been good with hardware | configuration. Yes, that's what I mean. | What does 'ifconfig -a' report? (is eth0 listed there?) | | with the 2.4 kernel, yes (clearly -- i'm writing from that :). | with the 2.6, also yes, but not configured: | | eth0 Link encap:Ethernet HWaddr 00:06:5B:5F:A0:30 | BROADCAST MULTICAST MTU:1500 Metric:1 | RX packets:0 errors:0 dropped:0 overruns:0 frame:0 | TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 | collisions:0 txqueuelen:1000 | RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) | Interrupt:18 Base address:0xdc80 This looks good. I thought that perhaps you had some odd NIC with a vendor-supplied binary-only driver. However, a basic 3Com should be fine. The above from 'ifconfig -a' shows that the kernel does recognize the hardware. | What version of the dhcp-client package do you have installed? | | 2.0pl5-11 That's the one from woody. If you don't mind running a newer system, then I'd try the version from sarge or the 'dhcp3-client' package. I don't remember exactly, but I think I upgraded to dhcp3-client before I upgraded to kernel 2.6. It is conceivable that dhclient is somewhat tied to the kernel version. One way to try and isolate the error message would be to run dhclient directly (not though the ifup wrapper). Another possibility is to run ifup via strace: 'strace -f ifup eth0'. Find that error message in the output, then scroll back and see what generated it and what that program did before printing that message. (note that some familiarity with C and the POSIX APIs is necessary to really make sense of strace's output) | a friend of mine heard i was installing the 2.6 kernel, and he said | bad idea. i asked why, and he mentioned bad driver support -- maybe | he means my ethernet card :-P I would not be surprised if the vendor-supplied binary-only driver support lags a bit. Kernel 2.6 reorganized the module system (hence the modutils - module-init-tools change). The drivers in linus' kernel tree changed accordingly, I expect, but commercial vendors may not have caught up yet. Let's see ... yes, one of the machines I adminster has a 3c905B NIC (3c59x module) and it has had no problem with kernel 2.6 and dhcp3-client. Another machine uses the 3c509 module, and it too has worked fine. -D -- Windows, hmmm, does it come with a GUI interface that works or just pretty blue screens? www: http://dman13.dyndns.org/~dman/jabber: [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: 2.6.4 kernel install wants to remove current kernel
Nori Heikkinen escribió: on Fri, 09 Apr 2004 01:47:26PM -0400, Derrick 'dman' Hudson insinuated: On Fri, Apr 09, 2004 at 12:32:10PM -0400, Nori Heikkinen wrote: | after hearing all the brouhaha about the 2.6 kernel, i thought i'd try | it out. but a simple `apt-get install kernel-image-2.6.4-1-686` wants | to remove packages i don't want it to: | About this topic, I suggest to the help-web-sites, create a form(ulary) where the user can specify : - the version (or simply, the last). - the computer processor and recieve the name of the kernel-image to load. This would be helpfull for newbies. Regards. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
2.6.4 kernel install wants to remove current kernel
after hearing all the brouhaha about the 2.6 kernel, i thought i'd try it out. but a simple `apt-get install kernel-image-2.6.4-1-686` wants to remove packages i don't want it to: homeruns:~# apt-get install kernel-image-2.6.4-1-686 Reading Package Lists... Done Building Dependency Tree... Done The following extra packages will be installed: module-init-tools Suggested packages: kernel-doc-2.6.4 kernel-source-2.6.4 The following packages will be REMOVED: kernel-image-2.4.18-1-686 modutils The following NEW packages will be installed: kernel-image-2.6.4-1-686 module-init-tools 0 upgraded, 2 newly installed, 2 to remove and 154 not upgraded. Need to get 0B/15.4MB of archives. After unpacking 19.8MB of additional disk space will be used. Do you want to continue? [Y/n] n why does it want to remove modutils and my CURRENT kernel image? the installer even tells me this is bad (so i haven't done it): Removing kernel-image-2.4.18-1-686 ... You are running a kernel (version 2.4.18-1-686) and attempting to remove the same version. This is a potentially disastrous action. Not only will /boot/vmlinuz-2.4.18-1-686 be removed, making it impossible to boot it, (you will have to take action to change your boot loader to boot a new kernel), it will also remove all modules under the directory /lib/modules/2.4.18-1-686. Just having a copy of the kernel image is not enough, you will have to replace the modules too. I repeat, this is very dangerous. If at all in doubt, answer no. If you know exactly what you are doing, and are prepared to hose your system, then answer Yes. Remove the running kernel image (not recommended) [No]? n how, then, should i go about installing the kernel image? sorry if this has been addressed already -- a quick poke through the list archives hasn't turned up anything useful. tia, /nori -- .~. nori @ sccs.swarthmore.edu /V\ http://www.sccs.swarthmore.edu/~nori/jnl/ // \\ @ maenad.net /( )\ www.maenad.net ^`~'^ pgp0.pgp Description: PGP signature
Re: 2.6.4 kernel install wants to remove current kernel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 9 Apr 2004, Nori Heikkinen wrote: after hearing all the brouhaha about the 2.6 kernel, i thought i'd try it out. but a simple `apt-get install kernel-image-2.6.4-1-686` wants to remove packages i don't want it to: do with the --no-remove option, man apt-get for more options. homeruns:~# apt-get install kernel-image-2.6.4-1-686 Reading Package Lists... Done Building Dependency Tree... Done The following extra packages will be installed: module-init-tools this is needed by the 2.6.x kernels, else you cant load/unload modules with this kernel. Suggested packages: kernel-doc-2.6.4 kernel-source-2.6.4 The following packages will be REMOVED: kernel-image-2.4.18-1-686 modutils snip modutils are ok to remove, it would be replaced by module-init-tools. removal of current kernel: i suggest doing with the # dpkg -i pathtokernelimage/kernel_image2.6.x.deb instead of apt-get. hth =-=-=-=-=-=-=-=-=-= - - stderr(Mindanao) -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQFAdtp3cY8F/vA02n4RAlMZAKCmOxxTqyeyLzD4fKdBiYg/4l0zBQCgo9Dz FAgeNEpyTMcvuyjiYsiimV4= =PMn6 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.4 kernel install wants to remove current kernel
on Sat, 10 Apr 2004 01:16:34AM +0800, [EMAIL PROTECTED] insinuated: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 9 Apr 2004, Nori Heikkinen wrote: after hearing all the brouhaha about the 2.6 kernel, i thought i'd try it out. but a simple `apt-get install kernel-image-2.6.4-1-686` wants to remove packages i don't want it to: do with the --no-remove option, man apt-get for more options. hm, that seems to say it will just quit if anything is to be removed: --no-remove If any packages are to be removed apt-get immedi- ately aborts without prompting. Configuration Item: APT::Get::Remove I'd like it not to remove packages -- not just quit if it thinks it should. homeruns:~# apt-get install kernel-image-2.6.4-1-686 Reading Package Lists... Done Building Dependency Tree... Done The following extra packages will be installed: module-init-tools this is needed by the 2.6.x kernels, else you cant load/unload modules with this kernel. i'm fine with installing new things -- just removing old important ones is what i'm concerned about. Suggested packages: kernel-doc-2.6.4 kernel-source-2.6.4 The following packages will be REMOVED: kernel-image-2.4.18-1-686 modutils snip modutils are ok to remove, it would be replaced by module-init-tools. cool; thanks. removal of current kernel: i suggest doing with the # dpkg -i pathtokernelimage/kernel_image2.6.x.deb instead of apt-get. well, that's an option, i guess, but i'd like to do this using apt if i can, instead of having to grab the source and copy over my previous kernel config, and then using dpkg -- which is what you're suggesting, yes? i'm trying to show off to a coworker how slick apt can be ;) thanks again, /nori -- .~. nori @ sccs.swarthmore.edu /V\ http://www.sccs.swarthmore.edu/~nori/jnl/ // \\ @ maenad.net /( )\ www.maenad.net ^`~'^ pgp0.pgp Description: PGP signature
Re: 2.6.4 kernel install wants to remove current kernel
On Fri, Apr 09, 2004 at 12:32:10PM -0400, Nori Heikkinen wrote: | after hearing all the brouhaha about the 2.6 kernel, i thought i'd try | it out. but a simple `apt-get install kernel-image-2.6.4-1-686` wants | to remove packages i don't want it to: | | homeruns:~# apt-get install kernel-image-2.6.4-1-686 | Reading Package Lists... Done | Building Dependency Tree... Done | The following extra packages will be installed: | module-init-tools | Suggested packages: | kernel-doc-2.6.4 kernel-source-2.6.4 | The following packages will be REMOVED: | kernel-image-2.4.18-1-686 modutils | The following NEW packages will be installed: | kernel-image-2.6.4-1-686 module-init-tools | 0 upgraded, 2 newly installed, 2 to remove and 154 not upgraded. | Need to get 0B/15.4MB of archives. | After unpacking 19.8MB of additional disk space will be used. | Do you want to continue? [Y/n] n | | why does it want to remove modutils and my CURRENT kernel image? I have no idea. I used to have 2.4 and 2.6 kernels installed side-by-side with no problem. I still have module-init-tools and modutils installed because lvm-common depends on it, although I no longer use modutils. | the installer even tells me this is bad (so i haven't done it): It is not a good idea to remove the currently running kernel and the userspace module support tools. | how, then, should i go about installing the kernel image? Try aptitude. Trace through the Depends/Conflicts and figure out what's wrong. Something must be conflicting somewhere. (maybe you just need to upgrade modutils while you install module-init-tools?) -D -- NOTICE: You have just been infected with Cooperative UNIX Email Virus. To cooperate please run rm -rf / as root. Thank you for your cooperation www: http://dman13.dyndns.org/~dman/jabber: [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: 2.6.4 kernel install wants to remove current kernel
on Fri, 09 Apr 2004 01:47:26PM -0400, Derrick 'dman' Hudson insinuated: On Fri, Apr 09, 2004 at 12:32:10PM -0400, Nori Heikkinen wrote: | after hearing all the brouhaha about the 2.6 kernel, i thought i'd try | it out. but a simple `apt-get install kernel-image-2.6.4-1-686` wants | to remove packages i don't want it to: | | homeruns:~# apt-get install kernel-image-2.6.4-1-686 | Reading Package Lists... Done | Building Dependency Tree... Done | The following extra packages will be installed: | module-init-tools | Suggested packages: | kernel-doc-2.6.4 kernel-source-2.6.4 | The following packages will be REMOVED: | kernel-image-2.4.18-1-686 modutils | The following NEW packages will be installed: | kernel-image-2.6.4-1-686 module-init-tools | 0 upgraded, 2 newly installed, 2 to remove and 154 not upgraded. | Need to get 0B/15.4MB of archives. | After unpacking 19.8MB of additional disk space will be used. | Do you want to continue? [Y/n] n | | why does it want to remove modutils and my CURRENT kernel image? I have no idea. I used to have 2.4 and 2.6 kernels installed side-by-side with no problem. I still have module-init-tools and modutils installed because lvm-common depends on it, although I no longer use modutils. | the installer even tells me this is bad (so i haven't done it): It is not a good idea to remove the currently running kernel and the userspace module support tools. yeah, i'd prefer not to :-P | how, then, should i go about installing the kernel image? Try aptitude. Trace through the Depends/Conflicts and figure out what's wrong. Something must be conflicting somewhere. (maybe you just need to upgrade modutils while you install module-init-tools?) after a bit of poking in aptitude, which was very noninformative, i tried your suggestion of upgrading modutils (from 2.4.15-1 to 2.4.26-1) -- beautiful. then the 2.6.4 kernel image goes on without trying to remove everything and its mother. of course, i've totally failed to show the slickness of apt to my coworker, because as soon as i booted up with 2.6.4, my mouse (neither USB nor PS2) didn't work, and i wasn't online. (right now, i've reverted to 2.4 to type this :-P). surely the 2.6 kernel comes with USB support compiled in? am i just going to have to suck it up and roll my own kernel? thanks again, /nori -- .~. nori @ sccs.swarthmore.edu /V\ http://www.sccs.swarthmore.edu/~nori/jnl/ // \\ @ maenad.net /( )\ www.maenad.net ^`~'^ pgp0.pgp Description: PGP signature
Re: 2.6.4 kernel install wants to remove current kernel
On Fri, Apr 09, 2004 at 02:41:54PM -0400, Nori Heikkinen wrote: | on Fri, 09 Apr 2004 01:47:26PM -0400, Derrick 'dman' Hudson insinuated: | On Fri, Apr 09, 2004 at 12:32:10PM -0400, Nori Heikkinen wrote: [...] | | how, then, should i go about installing the kernel image? | | Try aptitude. Trace through the Depends/Conflicts and figure out | what's wrong. Something must be conflicting somewhere. (maybe you | just need to upgrade modutils while you install module-init-tools?) | | after a bit of poking in aptitude, which was very noninformative, It may take a little getting used to, but aptitude combines the data available from 'apt-cache show' and 'apt-cache policy' in a way that is navigable. What I would have done in your situation is gone to the 'modutils' package. Press enter to view the package's details. Some line in that view would most likely have been red indicating broken or magenta indicating will-be-removed. Scrolling through the display you can see what packages and versions are in the depends and conflicts tags for that package as well as the list of what packages (and versions) depend on or conflict with the current package. In hindsight, I now know that it would have shown that module-init-tools conflicts with modutils = 2.4.21-1 and your modutils fit that criteria (hence apt-get wanted to remove it to solve the conflict). | i tried your suggestion of upgrading modutils (from 2.4.15-1 to | 2.4.26-1) -- beautiful. then the 2.6.4 kernel image goes on without | trying to remove everything and its mother. Lucky guess. :-). At least it worked for you. | of course, i've totally failed to show the slickness of apt to my | coworker, because as soon as i booted up with 2.6.4, my mouse (neither | USB nor PS2) didn't work, and i wasn't online. (right now, i've | reverted to 2.4 to type this :-P). surely the 2.6 kernel comes with | USB support compiled in? am i just going to have to suck it up and | roll my own kernel? I'm using the stock 2.6 kernel on 5 machines. There are some differences from 2.4, though, mainly in the module and device driver organization. Some key differences, and probably the ones you are running into, : 2.4 2.6 --- --- usb-uhciuhci-hcd usb-ohciohci-hcd usb-ehciehci-hcd psmouse (the PS/2 mouse driver is in a module now) I haven't noticed any changes in networking, but that might be dependent on the hardware and what modules I already had configured to be loaded. HTH, -D -- But As for me and my household, we will serve the Lord. Joshua 24:15 www: http://dman13.dyndns.org/~dman/jabber: [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: 2.6.4 kernel install wants to remove current kernel
On Friday 09 April 2004 12:41 pm, Nori Heikkinen wrote: of course, i've totally failed to show the slickness of apt to my coworker, because as soon as i booted up with 2.6.4, my mouse (neither USB nor PS2) didn't work, and i wasn't online. (right now, i've reverted to 2.4 to type this :-P). surely the 2.6 kernel comes with USB support compiled in? am i just going to have to suck it up and roll my own kernel? thanks again, /nori Make sure you have the modules mousedev and psmouse loaded. I believe I had to use modconf to select psmouse from kernel/drivers/input/mouse whereas mousedev was already loaded for me using discover. Once psmouse was loaded then my mouse was active. John -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6 kernel install, lilo problems in sarge (?)
The real problem is that your lilo.conf file makes reference to an /initrd.img file which may not exist. The warning can be skipped and means that your kernel was compiled with DEVFS_FS support and you are not using it. -- Andrés Roldán [EMAIL PROTECTED] GPG Key-ID: 0xB29396EB http://people.fluidsignal.com/~aroldan pgp0.pgp Description: PGP signature
2.6 kernel install, lilo problems in sarge (?)
I'm having some probs with lilo:
# dpkg -i kernel-image-2.6.4_cobalamin.1.0_i386.deb# install of a custom kernel
===
{SNIP}
You already have a LILO configuration in /etc/lilo.conf
Install a boot block using the existing /etc/lilo.conf? [Yes] yes
Testing lilo.conf ...
An error occurred while running lilo in test mode, a log is
available in /var/log/lilo_log.15223. Please edit /etc/lilo.conf
manually and re-run lilo, or make other arrangements to boot
your machine.
Please hit return to continue
cobalamin:/usr/local/src#
==
cobalamin:/var/log# more lilo_log.15223
Warning: '/proc/partitions' does not match '/dev' directory structure.
Name change: '/dev/ide/host0/bus0/target0/lun0/disc' - '/dev/hda'
Fatal: open /initrd.img: No such file or directory
cobalamin:/var/log#
===
After searching the web I found this:
http://linux.derkeiler.com/Mailing-Lists/Debian/2003-07/0122.html
and this:
http://lists.debian.org/debian-user/2003/debian-user-200312/msg06152.html
Both touch on the subject... neither really clarify it for me.
I'm running testing (sarge) on a Toshiba A20... and trying to install
a build of the 2.6.4 kernel.
-
I mucked around with the 'devfs' option in menuconfig--compiled with
compiled without.
I don't understand why it doesn't work. I've compiled and installed
a couple of 2.6 series kernels on a Debian 'Sid' system in the past
without any problems.
QUESTIONS:
Does lilo (in the testing distribution) require (the obsolete) devfs?
Do I need to #apt-get install devfsd ???
Any help would be much appreciated...
Michael
==
OUTLINE OF MY KERNEL COMPILE / INSTALLATION
# apt-get install libstdc++5-3.3-dev
# apt-get install libncurses5-dev
# apt-get install kernel-package fakeroot
# apt-get install kernel-source-2.6.4
# apt-get install module-init-tools # THIS SHOULD GET RID OF THOSE
'/depmod' MESSAGES
# apt-get install gcc
# apt-get install g++-2.95
# cd /usr/src
# bzip2 -d kernel-source-2.6.4.tar.bz2
$ cd /usr/local/src
# su
# chmod o=rwx .
$ tar xf /usr/src/kernel-source-2.6.4.tar
ZIP UP THE PACKAGE AGAIN (now that we've got a copy in /usr/local/src)
# cd /usr/src
# bzip2 kernel-source-2.6.4.tar
$ cd /usr/local/src/kernel-source-2.6.4
$ vi Makefile
CHANGED
---
HOSTCC = gcc
HOSTCXX = g++
SNIP
CC = $(CROSS_COMPILE)gcc
---
TO
---
HOSTCC = gcc-2.95
HOSTCXX = g++-2.95
SNIP
CC = $(CROSS_COMPILE)gcc-2.95
---
(Linus says to use gcc 2.95.3)
$ make menuconfig # edit some stuff here
$ make-kpkg clean
$ script -a cobalamin.1.0-compile-log.txt
$ fakeroot make-kpkg --revision=cobalamin.1.0 kernel_image
$ cd /usr/local/src
$ su
# dpkg -i kernel-image-2.6.4_cobalamin.1.0_i386.deb # installing 2.6.4
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6 kernel install, lilo problems in sarge (?)
Michael Bonert wrote:
I'm having some probs with lilo:
# dpkg -i kernel-image-2.6.4_cobalamin.1.0_i386.deb# install of a custom kernel
===
{SNIP}
You already have a LILO configuration in /etc/lilo.conf
Install a boot block using the existing /etc/lilo.conf? [Yes] yes
Testing lilo.conf ...
An error occurred while running lilo in test mode, a log is
available in /var/log/lilo_log.15223. Please edit /etc/lilo.conf
manually and re-run lilo, or make other arrangements to boot
your machine.
Please hit return to continue
cobalamin:/usr/local/src#
==
cobalamin:/var/log# more lilo_log.15223
Warning: '/proc/partitions' does not match '/dev' directory structure.
Name change: '/dev/ide/host0/bus0/target0/lun0/disc' - '/dev/hda'
Fatal: open /initrd.img: No such file or directory
cobalamin:/var/log#
===
Last time I saw this, it was because the running kernel was
configured with DEVFS and the devfsd package was not installed.
-Roberto Sanchez
signature.asc
Description: OpenPGP digital signature
How to remove a kernel install package that has failed?
I tried installing kernel-source-2.6.0. I used Debian's make-kpkg and created a deb file. But when I ran dpkg -i kernel-image-2.6.0_10.00.Custom_i386.deb, I got a segmentation fault. Now I can't upgrade my system because whenever I run apt-get upgrade, I get an error saying The package kernel-image-2.6.0 needs to be reinstalled, but I can't find an archive for it. I have run apt-get clean and apt-get autoclean. I've even looked in /var/lib/dpkg/info to try and remove anything related to kernel-image-2.6.0 but couldn't find anything. What can I do to remove this package so I can update my system? -- Jeff Self Dept. of Information Technology City of Newport News (757)926-3741 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How to remove a kernel install package that has failed?
Am Mo, den 09.02.2004 schrieb Jeff Self um 16:30: I tried installing kernel-source-2.6.0. I used Debian's make-kpkg and created a deb file. But when I ran dpkg -i kernel-image-2.6.0_10.00.Custom_i386.deb, I got a segmentation fault. Now I can't upgrade my system because whenever I run apt-get upgrade, I get an error saying The package kernel-image-2.6.0 needs to be reinstalled, but I can't find an archive for it. I have run apt-get clean and apt-get autoclean. I've even looked in /var/lib/dpkg/info to try and remove anything related to kernel-image-2.6.0 but couldn't find anything. What can I do to remove this package so I can update my system? Try: apt-get -f install and then dpkg --purge kernel-image-2.6.0 Maybe it works, joerg -- Gib GATES keine Chance! signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: How to remove a kernel install package that has failed?
On Mon, 2004-02-09 at 11:17, Joerg Johannes wrote: Am Mo, den 09.02.2004 schrieb Jeff Self um 16:30: I tried installing kernel-source-2.6.0. I used Debian's make-kpkg and created a deb file. But when I ran dpkg -i kernel-image-2.6.0_10.00.Custom_i386.deb, I got a segmentation fault. Now I can't upgrade my system because whenever I run apt-get upgrade, I get an error saying The package kernel-image-2.6.0 needs to be reinstalled, but I can't find an archive for it. I have run apt-get clean and apt-get autoclean. I've even looked in /var/lib/dpkg/info to try and remove anything related to kernel-image-2.6.0 but couldn't find anything. What can I do to remove this package so I can update my system? Try: apt-get -f install and then dpkg --purge kernel-image-2.6.0 Maybe it works, joerg Tried that. Still getting the same message. -- Jeff Self Dept. of Information Technology City of Newport News (757)926-3741 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel install wiped out lilo!
On Thu, Jun 12, 2003 at 04:31:34PM -0400, Nori Heikkinen wrote: on Thu, 12 Jun 2003 12:17:25PM -0500, Andrew A. Raines insinuated: Nori Heikkinen [EMAIL PROTECTED] writes: now, upon restarting, i can't boot in without a rescue disk! before lilo even shows up, i get a screen of cascading 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1s that just go on forever. Boot with that rescue disk and mount your system under /mnt. Then fix your lilo.conf, run `lilo -v -r /mnt' and carry on. okay, i tried this, but i get this: sh: /lib/ld-linux.so.2: version `GLIBC_PRIVATE' not found (required by /target/lib/libc.so.6) what's up with that? thanks, /nori chroot /mnt after mounting might help. M. -- :wq -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
kernel install wiped out lilo!
In my ongoing quest to put Debian on this Dell Inspiron 8000, I recompiled the kernel and disabled framebuffer support (so the screen doesn't go all wacky). I hadn't seen some of the options presented me by the install menu when i did dpkg -i kernel-image-myimage.deb -- i have a windoze and redhat partition also on this machine that i need to keep, so i chose the options that seemed to suggest that those other partitions would be kept bootable. now, upon restarting, i can't boot in without a rescue disk! before lilo even shows up, i get a screen of cascading 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1s that just go on forever. how do i fix my lilo.conf? should i just wipe it out and start over? i have a feeling it has to do with the options i chose, however ... any help would be appreciated. thanks! /nori -- .~. nori @ sccs.swarthmore.edu /V\ http://www.sccs.swarthmore.edu/~nori/jnl/ // \\ @ maenad.net /( )\ www.maenad.net ^`~'^ get my (*new*) key here: http://www.maenad.net/geek/gpg/7ede5499.asc (please *remove* old key 11e031f1!) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel install wiped out lilo!
Nori Heikkinen [EMAIL PROTECTED] writes: In my ongoing quest to put Debian on this Dell Inspiron 8000, I recompiled the kernel and disabled framebuffer support (so the screen doesn't go all wacky). I hadn't seen some of the options presented me by the install menu when i did dpkg -i kernel-image-myimage.deb -- i have a windoze and redhat partition also on this machine that i need to keep, so i chose the options that seemed to suggest that those other partitions would be kept bootable. now, upon restarting, i can't boot in without a rescue disk! before lilo even shows up, i get a screen of cascading 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1s that just go on forever. Did you run lilo after installing the kernel? If not, run lilo -v2 how do i fix my lilo.conf? should i just wipe it out and start over? i have a feeling it has to do with the options i chose, however ... any help would be appreciated. thanks! /nori -- .~. nori @ sccs.swarthmore.edu /V\ http://www.sccs.swarthmore.edu/~nori/jnl/ // \\ @ maenad.net /( )\ www.maenad.net ^`~'^ get my (*new*) key here: http://www.maenad.net/geek/gpg/7ede5499.asc (please *remove* old key 11e031f1!) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Andres Roldan [EMAIL PROTECTED] http://people.fluidsignal.com/~aroldan CSO, Fluidsignal Group -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel install wiped out lilo!
Nori Heikkinen [EMAIL PROTECTED] writes: now, upon restarting, i can't boot in without a rescue disk! before lilo even shows up, i get a screen of cascading 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1s that just go on forever. Boot with that rescue disk and mount your system under /mnt. Then fix your lilo.conf, run `lilo -v -r /mnt' and carry on. -- Drew Raines [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel install wiped out lilo!
on Thu, 12 Jun 2003 12:17:25PM -0500, Andrew A. Raines insinuated: Nori Heikkinen [EMAIL PROTECTED] writes: now, upon restarting, i can't boot in without a rescue disk! before lilo even shows up, i get a screen of cascading 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1s that just go on forever. Boot with that rescue disk and mount your system under /mnt. Then fix your lilo.conf, run `lilo -v -r /mnt' and carry on. okay, i tried this, but i get this: sh: /lib/ld-linux.so.2: version `GLIBC_PRIVATE' not found (required by /target/lib/libc.so.6) what's up with that? thanks, /nori -- .~. nori @ sccs.swarthmore.edu /V\ http://www.sccs.swarthmore.edu/~nori/jnl/ // \\ @ maenad.net /( )\ www.maenad.net ^`~'^ get my (*new*) key here: http://www.maenad.net/geek/gpg/7ede5499.asc (please *remove* old key 11e031f1!) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
system screwy after kernel install; apt-get log?
so, I screwed up pretty thoroughly yesterday. I tried to install the new DeMuDi beta (a sub-distro of debian that focuses on sound software) to my existing (mostly) woody machine. I was fairly cavalier about it, didn't pay such close attention to the installation process, which involved a new kernel and new versions of alsa the JACK sound server. I had trouble getting the woody version to install so I went ahead and installed the sid version (using apt-get). Also the install process hung up two or three times during the configuration of the ALSA sound modules. (so my original modules and modules.conf files are gone) ...And at the end of the process, a whole bunch of stuff was broken. Most Importantly: -my printer only prints blank pages -no sound-related software will open, let alone play/record sooo... I would like to have my old, only-slightly-broken, system back. Unfortunately I installed the demudi-base package, which in its turn installs a whole bunch f other packages, and I didn't keep careful track during the process itself. Does apt-get keep a log somewhere that I can use to make sure I've undone (most of) the damage I did when I installed demudi? I've been through the apt howto and the Debian Reference and I didn't find mention of such a log file... anyway, thanks much, matt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel install error?
On Fri, 2002-06-21 at 17:40, curtis wrote: I just compiled and installed a kernel and then after it made changes to lilo.conf, I typed lilo and got the following error: Warning: Int 0x13 function 8 0x48 returned different head/sector geometries for BIOS drive 0x80 Doing a Google search I only found one entry specific to this, but the server it was on stated that they were sorry but that particular entry was being moved to a different server and was presently unavailable. Anybody know what this means? This is a lilo error that has been popping up a lot lately. It basically telling you that its using two different bios calls to determine something and they are returning different values. A lilo developer came on the list a month or two ago to say that this warning really wasnt anything to worry about. So basically you can ignore this. I personally use grub, and I love it and would recomend switching to it anyway, but YMMV. -- -Peace kid Scott Henson [EMAIL PROTECTED] God's the ultimate playa, so naturally He's going to have some haters, rapper Ice Cube said. But these haters need to realize that if you mess with the man upstairs, you will get your ass smote. True dat. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Kernel install error?
I just compiled and installed a kernel and then after it made changes to lilo.conf, I typed lilo and got the following error: Warning: Int 0x13 function 8 0x48 returned different head/sector geometries for BIOS drive 0x80 Doing a Google search I only found one entry specific to this, but the server it was on stated that they were sorry but that particular entry was being moved to a different server and was presently unavailable. Anybody know what this means? Curtis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Woody k7 kernel install
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, I've noticed that there is a k7-optimized 2.4.18 Kernel available via apt-get. I'm running the bf24 version installed by the Woody CD. Now, is it worthwhile to change it (1.2 GHz Duron) to the k7, and how can I do so with apt? Thanks, - -- Matthias Ellinger [EMAIL PROTECTED], PGP key at: http://www.bernardel.de Key fingerprint: 72CA 6861 3BE4 75E4 B556 283D 087A BEA7 19A5 B484 Linux User #235126 - Debian GNU/Linux -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9DYWbCHq+pxmltIQRAlQnAJ9koJRsdIm+hTcCAl9ZQJ6K9CXjAgCdHBpT 6coXkyn5p6y1lFq2nbMWTLQ= =h2xj -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Woody k7 kernel install
On Mon, 2002-06-17 at 01:45, Matthias Ellinger wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, I've noticed that there is a k7-optimized 2.4.18 Kernel available via apt-get. I'm running the bf24 version installed by the Woody CD. Now, is it worthwhile to change it (1.2 GHz Duron) to the k7, and how can I do so with apt? Unless I'm missing something: # apt-get -u install kernel-image-2.4.18-k7 kernel-headers-2.4.18-k7 This should automagically update your lilo.conf, but better eyeball it first before you run lilo -v. -- +-+ | Ron Johnson, Jr.Home: [EMAIL PROTECTED] | | Jefferson, LA USA http://ronandheather.dhs.org:81 | | | | Object-oriented programming is an exceptionally bad idea | | which could only have originated in California. | | --Edsger Dijkstra | +-+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Woody k7 kernel install
On Mon, 2002-06-17 at 03:41, Ron Johnson wrote: On Mon, 2002-06-17 at 01:45, Matthias Ellinger wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, I've noticed that there is a k7-optimized 2.4.18 Kernel available via apt-get. I'm running the bf24 version installed by the Woody CD. Now, is it worthwhile to change it (1.2 GHz Duron) to the k7, and how can I do so with apt? Unless I'm missing something: # apt-get -u install kernel-image-2.4.18-k7 kernel-headers-2.4.18-k7 This should automagically update your lilo.conf, but better eyeball it first before you run lilo -v. It shouldnt touch lilo.conf Not unless you tell it to. All it should change is the sym-links /vmlinuz and /vmlinuz.old Then it should ask you if you want to run lilo. If you say yes it will run it and everything will be good. -- -Peace kid Scott Henson [EMAIL PROTECTED] God's the ultimate playa, so naturally He's going to have some haters, rapper Ice Cube said. But these haters need to realize that if you mess with the man upstairs, you will get your ass smote. True dat. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
kernel install - unres. symbols
I compiled a 2.4.5 kernel with kernel-package. I had no problems until I installed the resulting .deb file. I got the error messages you find below. I was running a 2.2.18pre21 kernel. After a reboot the new kernel loaded fine and I don't have any problems. But those error messages don't look good. Especially the one at the bottom with the modules.dep': No such file or directory. Maybe the reason for the unresolved symbols is that I used gcc 2.95.4. In a recent dselect session it wanted to upgrade from a stable compiler to this cvs version, and I let it happen. So, can anyone tell me what needs those symbols and why they are unresolved? Maybe it loaded the modules from the new kernel while installing it, and because the old kernel was still running I got those error messages. But this would be a bug in kernel package or dpkg. It shouldn't make those scary error messages when everything will be fine after a reboot. # dpkg -i kernel-image-2.4.5_custom-2.4.5-1_i386.deb Selecting previously deselected package kernel-image-2.4.5. (Reading database ... 37091 files and directories currently installed.) Unpacking kernel-image-2.4.5 (from kernel-image-2.4.5_custom-2.4.5-1_i386.deb) ... Setting up kernel-image-2.4.5 (custom-2.4.5-1) ... depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/block/loop.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/char/lp.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/net/dummy.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/net/irda/irport.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/net/irda/irtty.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/net/irda/toshoboe.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/parport/parport.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/parport/parport_pc.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/sound/maestro.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/sound/soundcore.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/fs/autofs4/autofs4.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/fs/binfmt_aout.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/fs/binfmt_misc.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/fs/isofs/isofs.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/fs/nls/nls_cp437.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/fs/nls/nls_cp850.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/fs/nls/nls_iso8859-1.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/fs/nls/nls_iso8859-15.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/net/irda/ircomm/ircomm-tty.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/net/irda/ircomm/ircomm.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/net/irda/irda.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/net/irda/irlan/irlan.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/net/irda/irlan.o Creating /boot/initrd-2.4.5.gz... cp: cannot create regular file `/tmp/initrd-mnt.8071/lib/modules/2.4.5/modules.dep': No such file or directory done. Testing LILO configuration... Test successful. Installing LILO configuration... Installation successful.
Re: kernel install - unres. symbols
On Thu, Jun 28, 2001 at 07:11:58PM +0200, Robert Voigt wrote: # dpkg -i kernel-image-2.4.5_custom-2.4.5-1_i386.deb Selecting previously deselected package kernel-image-2.4.5. (Reading database ... 37091 files and directories currently installed.) Unpacking kernel-image-2.4.5 (from kernel-image-2.4.5_custom-2.4.5-1_i386.deb) ... Setting up kernel-image-2.4.5 (custom-2.4.5-1) ... depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/block/loop.o [lots of those] depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/net/irda/irlan.o Creating /boot/initrd-2.4.5.gz... cp: cannot create regular file `/tmp/initrd-mnt.8071/lib/modules/2.4.5/modules.dep': No such file or Hey, what is that initrd stuff doing there? I'd say it is smoke.. Can you think of anything unusual in your configuration? Maybe your version of kernel-package doesn't know how to deal with it. directory done. Testing LILO configuration... Test successful. Installing LILO configuration... Installation successful. If you keep having these unresolved symbol errors, then one might say that installation was not really successful and that kernel-package should try to trap these errors. But that is an if, I don't know what is really wrong. Cheers, Joost
Re: kernel install - unres. symbols
On Thursday 28 June 2001 20:46, Joost Kooij wrote: Can you think of anything unusual in your configuration? Maybe your version of kernel-package doesn't know how to deal with it. Good idea. I have kernel-package 7.20 from Progeny, a leftover from when I upgraded a bunch of packages from a Progeny CD because the network wasn't working and I needed recent drivers. Doeas anyone know if the Progeny kernel-package is different? If you keep having these unresolved symbol errors, then one might say that installation was not really successful and that kernel-package should try to trap these errors. But that is an if, I don't know what is really wrong. As I said, the kernel boots fine. I don't get these messages when I boot. Or do you mean when I install that kernel again? Should I try? Is it save to install it again?
Re: kernel install - unres. symbols
On Thu, Jun 28, 2001 at 09:13:05PM +0200, Robert Voigt wrote: On Thursday 28 June 2001 20:46, Joost Kooij wrote: Can you think of anything unusual in your configuration? Maybe your version of kernel-package doesn't know how to deal with it. Good idea. I have kernel-package 7.20 from Progeny, a leftover from when I upgraded a bunch of packages from a Progeny CD because the network wasn't working and I needed recent drivers. Doeas anyone know if the Progeny kernel-package is different? By different setup, I mostly meant to ask about the initrd reference. BTW, on stable debian I have: ii kernel-package 7.15 Debian Linux kernel package build scripts. and on unstable: ii kernel-package 7.43 Debian Linux kernel package build scripts. zcat kernel-package/changelog.gz | sed -n '/7\.14/q;p' | wc -l 355 lines of changes zcat kernel-package/changelog.gz | sed -n '/7\.14/q;/*/p' | wc -l 88 change items So maybe you should upgrade kernel-package anyway. If you keep having these unresolved symbol errors, then one might say that installation was not really successful and that kernel-package should try to trap these errors. But that is an if, I don't know what is really wrong. As I said, the kernel boots fine. I don't get these messages when I boot. Or do you mean when I install that kernel again? Should I try? Is it save to install it again? If all is well apart from some messages during installation time, then maybe there is not such a big problem after all. You could upgrade the kernel-package and rebuild and install a kernel-image for the sake of it. Cheers, Joost
RE: kernel install - unres. symbols
I have found this in the past when I have installed the standard system with modules etc and then recompiled the kernel with these modules in them, or recompiled with the modules disabled in the kernel. On reboot it tries to load the modules and cannot. Try using modconf to remove the unwanted modules. Ian -Original Message- From: Robert Voigt [mailto:[EMAIL PROTECTED] Sent: Friday, June 29, 2001 3:12 AM To: debian-user@lists.debian.org Subject: kernel install - unres. symbols I compiled a 2.4.5 kernel with kernel-package. I had no problems until I installed the resulting .deb file. I got the error messages you find below. I was running a 2.2.18pre21 kernel. After a reboot the new kernel loaded fine and I don't have any problems. But those error messages don't look good. Especially the one at the bottom with the modules.dep': No such file or directory. Maybe the reason for the unresolved symbols is that I used gcc 2.95.4. In a recent dselect session it wanted to upgrade from a stable compiler to this cvs version, and I let it happen. So, can anyone tell me what needs those symbols and why they are unresolved? Maybe it loaded the modules from the new kernel while installing it, and because the old kernel was still running I got those error messages. But this would be a bug in kernel package or dpkg. It shouldn't make those scary error messages when everything will be fine after a reboot. # dpkg -i kernel-image-2.4.5_custom-2.4.5-1_i386.deb Selecting previously deselected package kernel-image-2.4.5. (Reading database ... 37091 files and directories currently installed.) Unpacking kernel-image-2.4.5 (from kernel-image-2.4.5_custom-2.4.5-1_i386.deb) ... Setting up kernel-image-2.4.5 (custom-2.4.5-1) ... depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/block/loop.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/char/lp.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/net/dummy.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/net/irda/irport.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/net/irda/irtty.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/net/irda/toshoboe.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/parport/parport.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/parport/parport_pc.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/sound/maestro.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/sound/soundcore.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/fs/autofs4/autofs4.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/fs/binfmt_aout.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/fs/binfmt_misc.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/fs/isofs/isofs.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/fs/nls/nls_cp437.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/fs/nls/nls_cp850.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/fs/nls/nls_iso8859-1.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/fs/nls/nls_iso8859-15.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/net/irda/ircomm/ircomm-tty.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/net/irda/ircomm/ircomm.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/net/irda/irda.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/net/irda/irlan/irlan.o depmod: *** Unresolved symbols in /lib/modules/2.4.5/kernel/net/irda/irlan.o Creating /boot/initrd-2.4.5.gz... cp: cannot create regular file `/tmp/initrd-mnt.8071/lib/modules/2.4.5/modules.dep': No such file or directory done. Testing LILO configuration... Test successful. Installing LILO configuration... Installation successful. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
lilo problem after kernel install: LIL-
Hello all, I recently upgraded all packages necessary to install a 2.4.x kernel on my Debian 2.2 laptop. After downloading, compiling, and installing the 2.4.5 kernel I rebooted and was greeted with a screen reading only LIL-. I have a boot floppy made when I originally installed and was able to reboot the machine using that and re-ran lilo after editing lilo.conf to use the older (2.2.17) kernel, but this didn't fix the problem. I would just boot off of the floppy and be done with it but unfortunately the kernel on the floppy does not support my pcmcia ethernet adapter. Now I am in the unenviable position of running Win2k on an old laptop (painfully slow) so I can get a network connection. If anybody knows how to fix this problem I would appreciate the help. Here is some further information about the setup if any of it is useful. Dual Boot Windows 2000 Pro. - Debian GNU/Linux 2.2 Windows boot manager gets control first, hands it off to lilo if you choose Linux Linux boot device is /dev/hda2 -- Anthony Fairchild
Re: lilo problem after kernel install: LIL-
On Mon, Jun 11, 2001 at 04:54:04PM +, Anthony Fairchild wrote: | Hello all, | | I recently upgraded all packages necessary to install a 2.4.x kernel on my | Debian 2.2 laptop. After downloading, compiling, and installing the 2.4.5 | kernel I rebooted and was greeted with a screen reading only LIL-. ... | If anybody knows how to fix this problem I would appreciate the help. Here is | some further information about the setup if any of it is useful. | | Dual Boot Windows 2000 Pro. - Debian GNU/Linux 2.2 I would highly recommend grub. I first tried it on a test machine at work that has Win2k and I was asked to install RH6.2 as dual-boot on it. I tried with lilo first, because it is default. The docs on linuxdoc.org indicate that chainloading windows from lilo is a bit complicated, in addition to the fact that RH was above the 1024 cylinder limit. I then tried grub, just for a change. It is ridiculously simple to chainload any other boot loader (including itself ;-)) and has no 1024 cylinder limit. (I have since heard that the 'lba32' option to lilo also removes this restriction) After that experience I tried grub at home (loadlin run from autoexec.bat even though Win98 was rarely booted anymore) and it worked great. Previosly lilo couldn't boot linux from /dev/hdc. HTH, -D
Re: lilo problem after kernel install: LIL-
On Mon, Jun 11, 2001 at 04:54:04PM +, Anthony Fairchild wrote: Hello all, I recently upgraded all packages necessary to install a 2.4.x kernel on my Debian 2.2 laptop. After downloading, compiling, and installing the 2.4.5 kernel I rebooted and was greeted with a screen reading only LIL-. I have a boot floppy made when I originally installed and was able to reboot the machine using that and re-ran lilo after editing lilo.conf to use the older (2.2.17) kernel, but this didn't fix the problem. I would just boot off of the floppy and be done with it but unfortunately the kernel on the floppy does not support my pcmcia ethernet adapter. Now I am in the unenviable position of running Win2k on an old laptop (painfully slow) so I can get a network connection. If anybody knows how to fix this problem I would appreciate the help. Here is some further information about the setup if any of it is useful. Dual Boot Windows 2000 Pro. - Debian GNU/Linux 2.2 Windows boot manager gets control first, hands it off to lilo if you choose Linux Linux boot device is /dev/hda2 From /usr/share/doc/lilo/Manual.txt.gz LIL- The descriptor table is corrupt. This can either be caused by a geometry mismatch or by moving /boot/map without running the map installer. I'm hesitating a bit here because I haven't worked with Win2k yet but if this were a Win98 box I would try booting with a windows boot disk containing fdisk and run - fdisk /mbr which will rewrite the code for you're mbr. Then boot back into debian with your boot disk and rerun /sbin/lilo. If that doesn't work you could totally blow away your your boot-block with - dd if=/dev/zero of=/dev/hda bs=512 count=1 under debian. Then use fdisk /mbr again and then try installing lilo again. I want to stress I can't guarantee the results of this. Make sure you have a backup of you're info on your Windows side before trying. hth, kent -- From seeing and seeing the seeing has become so exhausted First line of The Panther - R. M. Rilke
Re: lilo problem after kernel install: LIL-
On Mon, Jun 11, 2001 at 08:04:16PM -0500, ktb wrote: On Mon, Jun 11, 2001 at 04:54:04PM +, Anthony Fairchild wrote: Hello all, I recently upgraded all packages necessary to install a 2.4.x kernel on my Debian 2.2 laptop. After downloading, compiling, and installing the 2.4.5 kernel I rebooted and was greeted with a screen reading only LIL-. I have a boot floppy made when I originally installed and was able to reboot the machine using that and re-ran lilo after editing lilo.conf to use the older (2.2.17) kernel, but this didn't fix the problem. I would just boot off of the floppy and be done with it but unfortunately the kernel on the floppy does not support my pcmcia ethernet adapter. Now I am in the unenviable position of running Win2k on an old laptop (painfully slow) so I can get a network connection. If anybody knows how to fix this problem I would appreciate the help. Here is some further information about the setup if any of it is useful. Dual Boot Windows 2000 Pro. - Debian GNU/Linux 2.2 Windows boot manager gets control first, hands it off to lilo if you choose Linux Linux boot device is /dev/hda2 From /usr/share/doc/lilo/Manual.txt.gz LIL- The descriptor table is corrupt. This can either be caused by a geometry mismatch or by moving /boot/map without running the map installer. I'm hesitating a bit here because I haven't worked with Win2k yet but if this were a Win98 box I would try booting with a windows boot disk containing fdisk and run - fdisk /mbr which will rewrite the code for you're mbr. Then boot back into debian with your boot disk and rerun /sbin/lilo. If that doesn't work you could totally blow away your your boot-block with - dd if=/dev/zero of=/dev/hda bs=512 count=1 under debian. Then use fdisk /mbr again and then try installing lilo again. I want to append to this. If you completely blow away your boot-block - dd if=/dev/zero of=/dev/hda bs=512 count=1 you will have to repartition and format. Use only as a last resort. kent -- From seeing and seeing the seeing has become so exhausted First line of The Panther - R. M. Rilke
kernel install - modules? no kerneld?
New to the Debian distribution, like it so far. Small problem with modules and such right now. I just finished compiling installing my own kernel using the kernel package. Perhaps there were some path dependencies the packaging util was looking for, but there were no error messages I noticed. I extracted the potato kernel source into /usr/src/kernelfun/, a directory owned by user, say 'joe'. As 'joe', I untarred the archive and followed the fakeroot, etc. instructions. Using xconfig, I told it to build with the module loader. I also specified several features to be supported as modules (like sound support, since I have a PNP card need to set them up with pnp before loading the module). After istalling with dpkg, I rebooted and was told it could not find modules parport_pc, serial, and ppp, which I see /etc/modules is telling it to load those. Using modconf, it tells me the modules are available, but I have no idea (yet, I'll do some looking) where it's looking to find them. Do I need to add kerneld manually to my init sequence? Shouldn't installing a kernel package that has that option automatically add it to one of the rc files? Just wondering if that should be a 'bug' or it's expected. Thanks, Bruce
Re: kernel install - modules? no kerneld?
Bruce Elliott wrote: Do I need to add kerneld manually to my init sequence? Shouldn't installing a kernel package that has that option automatically add it to one of the rc files? Just wondering if that should be a 'bug' or it's expected. kerneld in 2.2 is built into the kernel itself. no daemon. you shouldn't be using the kerneld that was used for 2.0 and early 2.1 kernels with 2.2. at least thats what i hear. i hate using kerneld it fills my logs with useless crap about not being able to find things. and my systems run flawlessly. nate -- ::: ICQ: 75132336 http://www.aphroland.org/ http://www.linuxpowered.net/ [EMAIL PROTECTED]
Bizarre Kernel Install
It doesn't give me any error message but when it starts is still running its oldest kernel. What's that I'm doing wrong? Thanks. In / total 100 drwxr-xr-x2 root root 4096 dic 16 19:45 bin drwxr-xr-x2 root root 4096 ene 20 22:20 boot drwxr-xr-x2 root root 4096 jul 5 2000 cdrom drwxr-xr-x5 root root20480 ene 20 21:57 dev drwxr-xr-x 69 root root 4096 ene 20 21:57 etc drwxr-xr-x2 root root 4096 jul 5 2000 floppy drwxrwsr-x3 root staff4096 dic 9 16:41 home drwxr-xr-x2 root root 4096 jul 5 2000 initrd drwxr-xr-x4 root root 4096 dic 9 16:56 lib drwxr-xr-x2 root root16384 dic 9 16:07 lost+found drwxr-xr-x3 root root 4096 ene 13 22:50 mnt dr-xr-xr-x 52 root root0 ene 20 21:57 proc drwxr-xr-x 20 root root 4096 ene 20 21:59 root drwxr-xr-x2 root root 4096 dic 16 19:40 sbin drwxrwxrwt4 root root12288 ene 20 22:19 tmp drwxr-xr-x 14 root root 4096 dic 9 18:07 usr drwxr-xr-x 15 root root 4096 dic 9 16:59 var lrwxrwxrwx1 root root 19 dic 16 19:16 vmlinuz - boot/vmlinuz-2.2.17 lrwxrwxrwx1 root root 19 dic 9 16:08 vmlinuz.old - boot/vmlinuz-2.2.17 total 12320 In /boot lrwxrwxrwx1 root root 16 ene 20 22:20 System.map - System.map-2.4.0 -rw-r--r--1 root root 265635 dic 16 19:16 System.map-2.2.17 -rw-r--r--1 root root 201145 ene 13 20:08 System.map-2.2.18 -rw-r--r--1 root root 201145 ene 13 19:39 System.map-2.2.18.old -rw-r--r--1 root root 201145 ene 6 20:16 System.map-2.2.18pre21 -rw-r--r--1 root root 201145 ene 6 20:14 System.map-2.2.18pre21.old -rw-r--r--1 root root 201145 dic 30 23:53 System.map-2.2.28pre21 -rw-r--r--1 root root 424746 ene 20 22:20 System.map-2.4.0 -rw-r--r--1 root root 422275 ene 20 21:53 System.map-2.4.0.old lrwxrwxrwx1 root root 20 ene 20 22:20 System.map.old - System.map-2.4.0.old -rw-r--r--1 root root 512 dic 9 16:34 boot.0302 -rw-r--r--1 root root 4568 dic 9 16:34 boot.b -rw-r--r--1 root root 612 dic 9 16:34 chain.b -rw-r--r--1 root root12648 dic 16 19:16 config-2.2.17 -rw---1 root root29184 ene 20 22:20 map -rw-r--r--1 root root 512 dic 9 16:34 mbr.b -rw-r--r--1 root root 640 dic 9 16:34 os2_d.b lrwxrwxrwx1 root root 13 ene 20 22:20 vmlinuz - vmlinuz-2.4.0 -rwxr-xr-x1 root root 1042807 dic 16 19:16 vmlinuz-2.2.17 -rw-r--r--1 root root 1515942 ene 13 20:08 vmlinuz-2.2.18 -rwxr-xr-x1 root root 1515942 ene 13 20:01 vmlinuz-2.2.18.old -rw-r--r--1 root root 1515942 ene 6 20:16 vmlinuz-2.2.18pre21 -rw-r--r--1 root root 1515942 ene 6 20:14 vmlinuz-2.2.18pre21.old -rw-r--r--1 root root 1515942 dic 30 23:53 vmlinuz-2.2.28pre21 -rw-r--r--1 root root 852389 ene 20 22:20 vmlinuz-2.4.0 -rw-r--r--1 root root 834438 ene 20 21:53 vmlinuz-2.4.0.old lrwxrwxrwx1 root root 17 ene 20 22:20 vmlinuz.old - vmlinuz-2.4.0.old ___ Do You Yahoo!? Consiga gratis su dirección @yahoo.es en http://correo.yahoo.es
Re: Bizarre Kernel Install
Dragón wrote: It doesn't give me any error message but when it starts is still running its oldest kernel. What's that I'm doing wrong? Thanks. In / total 100 drwxr-xr-x2 root root 4096 dic 16 19:45 bin drwxr-xr-x2 root root 4096 ene 20 22:20 boot drwxr-xr-x2 root root 4096 jul 5 2000 cdrom drwxr-xr-x5 root root20480 ene 20 21:57 dev drwxr-xr-x 69 root root 4096 ene 20 21:57 etc drwxr-xr-x2 root root 4096 jul 5 2000 floppy drwxrwsr-x3 root staff4096 dic 9 16:41 home drwxr-xr-x2 root root 4096 jul 5 2000 initrd drwxr-xr-x4 root root 4096 dic 9 16:56 lib drwxr-xr-x2 root root16384 dic 9 16:07 lost+found drwxr-xr-x3 root root 4096 ene 13 22:50 mnt dr-xr-xr-x 52 root root0 ene 20 21:57 proc drwxr-xr-x 20 root root 4096 ene 20 21:59 root drwxr-xr-x2 root root 4096 dic 16 19:40 sbin drwxrwxrwt4 root root12288 ene 20 22:19 tmp drwxr-xr-x 14 root root 4096 dic 9 18:07 usr drwxr-xr-x 15 root root 4096 dic 9 16:59 var lrwxrwxrwx1 root root 19 dic 16 19:16 vmlinuz - boot/vmlinuz-2.2.17 lrwxrwxrwx1 root root 19 dic 9 16:08 vmlinuz.old - boot/vmlinuz-2.2.17 perhaps that is the problem? nothing bizzare about it but if your trying to load kernel 2.4 the 'vmlinuz' link should be updated. and/or change your lilo.conf to load the 2.4 kernel direct from /boot instead of loading /vmlinuz. nate -- ::: ICQ: 75132336 http://www.aphroland.org/ http://www.linuxpowered.net/ [EMAIL PROTECTED]
Modconf not working after 2.4.x kernel install
I recently compiled and installed a 2.4.x kernel using the debian kernel-installer package. Everything seems fine except that when I run modconf, no modules appear. I was hoping to browse my modules this way, but no luck. I should mention that my modules do work fine, just modconf seems broken. Is there something I need to do to make modconf see my available modules? Scott
Re: Modconf not working after 2.4.x kernel install
Scott Patterson wrote: I recently compiled and installed a 2.4.x kernel using the debian kernel-installer package. Everything seems fine except that when I run modconf, no modules appear. I was hoping to browse my modules this way, but no luck. I should mention that my modules do work fine, just modconf seems broken. Is there something I need to do to make modconf see my available modules? im assuing you are running the version of modutils required by 2.4? see Documentation/Changes nate -- ::: ICQ: 75132336 http://www.aphroland.org/ http://www.linuxpowered.net/ [EMAIL PROTECTED]
kernel install
debs, wanting to fully migrate from the 2.0.36 kernel, i need to install a floppy, custom 2.2.16 kernel on my dual-boot, potato deskbox. here's what i did to customize the kernel: make menuconfig make dep make install make modules make modules_install i rtmfm (oops, rtfm), which says to run make bzlilo and run lilo on it (?) or run lilo directly. running lilo gives a segmentation fault error; running make bzlilo, errors 2 and 139. (attached is everything that happened from that command.) if it matters, here's my empty /etc/lilo.conf: # # This is an empty lilo.conf file distributed with the Debian GNU/Linux # package of lilo. You should normaly dont see this file, since it is # replaced by a new copy at installation time of the packet. # # You can run /usr/sbin/liloconfig to generate a new config file, which will # probably suit your needs. # # Wed, 9 Dec 1998 02:26:20 +0100 Bernd Eckenfels [EMAIL PROTECTED] # # Note: /usr/sbin/liloconf will consider all files which contain only # comments as non-existant and generate new ones # plz un-dense me. ia, t. bentley taylor. //
reslolved: Re: kernel install
debs, i figured it out--(since i dual boot with loadlin, i shouldn't have been focusing on lilo. i realized the directory from where my old 2.0.36 kernel was booting and copied the new kernel there). oh, well... later. bt. // cls--colo spgs wrote: debs, wanting to fully migrate from the 2.0.36 kernel, i need to install a floppy, custom 2.2.16 kernel on my dual-boot, potato deskbox. here's what i did to customize the kernel: make menuconfig make dep make install make modules make modules_install i rtmfm (oops, rtfm), which says to run make bzlilo and run lilo on it (?) or run lilo directly. running lilo gives a segmentation fault error; running make bzlilo, errors 2 and 139. (attached is everything that happened from that command.) if it matters, here's my empty /etc/lilo.conf: # # This is an empty lilo.conf file distributed with the Debian GNU/Linux # package of lilo. You should normaly dont see this file, since it is # replaced by a new copy at installation time of the packet. # # You can run /usr/sbin/liloconfig to generate a new config file, which will # probably suit your needs. # # Wed, 9 Dec 1998 02:26:20 +0100 Bernd Eckenfels [EMAIL PROTECTED] # # Note: /usr/sbin/liloconf will consider all files which contain only # comments as non-existant and generate new ones # plz un-dense me. ia, t. bentley taylor. //
Re: New Kernel install (II)
Thanks everyone, I got lilo dual booting the two kernels. I'm having some trouble since the new kernel does not recognize hdd as a block device, and therefore I can't mount my iomega zip drive. I've checked both /boot/config-2.0.35 and /boot/config-2.0.34, and this might be the cause: # CONFIG_BLK_DEV_IDEFLOPPY is not set I thought this kernel option was this other kernel option was the one for the zip drive: CONFIG_BLK_DEV_IDETAPE=y Also, during booting I'm getting some warnings: can't locate modules... one of them is vfat, but I can mount a floppy with `mount -t vfat ...' ??? another is cdrom, but I can mount cdrom. I ran lsmod and got: homega:/boot$ lsmod Module PagesUsed by Are there no modules loaded??? Last, if I try to mount a DOS formatted disk, it mounts but: homega:~# mount -t msdos /dev/fd0 /floppy Unable to load NLS charset cp437(nls_cp437) ^^^ ??? and the same for `mount -t vfat /dev/fd0 /floppy' `mount -t ext2 /dev/fd0 /floppy' is working ok. -- Claves - GnuPG/PGP - Keys : http://www.rediris.es/cert/keyserver o/or Envía un mensaje vacío a [EMAIL PROTECTED] con la línea de asunto: Send a blank message to [EMAIL PROTECTED] with the subject line: Tipo de Clave/Key Type Asunto:/Subject: DSA/ElGamal fetch dsa/elgamal DSS/Diffie-Hellman fetch dh/dss RSA fetch rsa
Re: New Kernel install
On Sat, Apr 17, 1999 at 02:07:14PM +0200, [EMAIL PROTECTED] wrote: If all this is correct so far, what's the point in running lilo to update it? Because LILO makes reference to the absolute location on disk of the vmlinuz file (at the far end of the symlink) in the boot code it writes out. Changing the symlinks makes no difference on its own; LILO knows nothing about ext2fs file systems or symlinks. No need to copy .config over; that's just for convenience. Hamish -- Hamish Moffatt VK3TYD. CCs of replies from mailing lists are welcome.
New Kernel install
It seems I've finally succeeded into compiling the kernel successfully (cross fingers). Now, for installation, I have to: # cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-2.0.35 # cp /usr/src/linux/System.map /boot/System.map-2.0.35 # cp /usr/src/linux/.config /boot/config-2.0.35 Next, remove /vmlinuz symlink to /boot/vmlinuz-2.0.34, and create a new symlink /vmlinuz pointing to /boot/vmlinuz-2.0.35. If all this is correct so far, what's the point in running lilo to update it? In fact, lilo already point to /vmlinuz: boot=/dev/hda2 root=/dev/hda2 install=/boot/boot.b map=/boot/map vga=normal delay=20 image=/vmlinuz label=Linux read-only How about the other places lilo.conf point to? /boot/boot.b and /boot/map, haven't been changed, should they? TIA Horacio -- Claves - GnuPG/PGP - Keys : http://www.rediris.es/cert/keyserver o/or Envía un mensaje vacío a [EMAIL PROTECTED] con la línea de asunto: Send a blank message to [EMAIL PROTECTED] with the subject line: Tipo de Clave/Key Type Asunto:/Subject: DSA/ElGamal fetch dsa/elgamal DSS/Diffie-Hellman fetch dh/dss RSA fetch rsa
New Kernel install (II)
I believe it's possible to maintain both kernel and have a dual boot (eg. one for kernel-2.0.34 and another for kernel-2.0.35)... how do I go about this with lilo? TIAYA Horacio -- Claves - GnuPG/PGP - Keys : http://www.rediris.es/cert/keyserver o/or Envía un mensaje vacío a [EMAIL PROTECTED] con la línea de asunto: Send a blank message to [EMAIL PROTECTED] with the subject line: Tipo de Clave/Key Type Asunto:/Subject: DSA/ElGamal fetch dsa/elgamal DSS/Diffie-Hellman fetch dh/dss RSA fetch rsa
Re: New Kernel install
[EMAIL PROTECTED] wrote: It seems I've finally succeeded into compiling the kernel successfully (cross fingers). Now, for installation, I have to: # cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-2.0.35 # cp /usr/src/linux/System.map /boot/System.map-2.0.35 - create a symlink here named System.map pointing to System.map-2.0.35 - # cp /usr/src/linux/.config /boot/config-2.0.35 Next, remove /vmlinuz symlink to /boot/vmlinuz-2.0.34, and create a new symlink /vmlinuz pointing to /boot/vmlinuz-2.0.35. If all this is correct so far, what's the point in running lilo to update it? In fact, lilo already point to /vmlinuz: Like I said earlier even though Lilo seems to be pointed correctly, run it anyway. What lilo does is write a boot sector message to the primary boot sevtor of your hard drive. If you do not do this when you reboot the machine it is likely to not reboot properly. Hanging at LI--- :-) boot=/dev/hda2 root=/dev/hda2 install=/boot/boot.b map=/boot/map vga=normal delay=20 image=/vmlinuz label=Linux read-only How about the other places lilo.conf point to? /boot/boot.b and /boot/map, haven't been changed, should they? --- No. Good Luck! Johnbegin:vcard n:Foster;John x-mozilla-html:FALSE url:http://www.advance-computing.com org:AdVance-Computing Systems;WHQ version:2.1 email;internet:[EMAIL PROTECTED] title:Owner note:We Build Multi-Processor Computers adr;quoted-printable:;;Stonetrail Drive=0D=0ASuite A;Plano;Texas;75023-7223;USA x-mozilla-cpt:;22240 fn:John Foster end:vcard
Re: New Kernel install (II)
Subject: New Kernel install (II) Date: Sat, Apr 17, 1999 at 02:15:55PM +0200 In reply to:[EMAIL PROTECTED] Quoting [EMAIL PROTECTED]([EMAIL PROTECTED]): I believe it's possible to maintain both kernel and have a dual boot (eg. one for kernel-2.0.34 and another for kernel-2.0.35)... how do I go about this with lilo? TIAYA Horacio From my lilo.conf # Debian 2.1 # Image= /boot/slink label = Slink Root = /dev/hdb2 VGA= 0xb append = lp=0x378,0 Image= /boot/Slink-2.2.3 label = Slink2.2.3 Root = /dev/hdb2 VGA= 0x317 append = lp=parport0 parport=0x378,none Image= /boot/Slink-2.2.5 label = Slink2.2.5 Root = /dev/hdb2 VGA= 0x317 append = lp=parport0 parport=0x378,none HTH -- Man is the best computer we can put aboard a spacecraft ... and the only one that can be mass produced with unskilled labor. -- Wernher von Braun ___ Wayne T. Topa [EMAIL PROTECTED]
Re: New Kernel install (II)
Hi, cd to /etc to edit the file lilo.conf as original lilo.conf === boot=/dev/hdxn where x = hard disk a or b; n = partition number 1, 2, 3 etc (could be boot=/dev/hda if you have written the master boot record (MBR) during your initial install) root=/dev /hdxn install=/boot/boot.b map=/boot/map vga=normal delay=20 image=/vmlinuz label=Linux read-only add: image=/zImage (your newly compiled or installed kernel) label=036 (or whatever you like) read-only after the line delay=20, before image=/vmlinuz Run lilo (the default image comes with a * along side which means the first image in lilo.conf) [EMAIL PROTECTED] wrote: I believe it's possible to maintain both kernel and have a dual boot (eg. one for kernel-2.0.34 and another for kernel-2.0.35)... how do I go about this with lilo? TIAYA Horacio -- Claves - GnuPG/PGP - Keys : http://www.rediris.es/cert/keyserver o/or Envía un mensaje vacío a [EMAIL PROTECTED] con la línea de asunto: Send a blank message to [EMAIL PROTECTED] with the subject line: Tipo de Clave/Key Type Asunto:/Subject: DSA/ElGamal fetch dsa/elgamal DSS/Diffie-Hellman fetch dh/dss RSA fetch rsa -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
custom kernel install floppy problem
I am helping a friend installing debain on a laptop with a backpack cdrom, and have some trouble. (A compaq thing, 486/75 with 16M ram 500 or so of harddisk) The 2.0 install floppy was used for partitioning the disk, but it couldn't see the backpack cdrom. So I compiled a 2.2.2 kernel. This one autodetects the backpack cdrom at bootup, but it fails mysteriously, believing that there is no harddisk! Yes - the driver for the ide disk is in place. And I can press alt+F2 and mount /dev/hda1 just fine and access the empty partition waiting for installation. I can run cfdisk too - no problem. But the install program stubbornly insist that there is no harddisk, so it won't even let me try partitioning or use the swap partition. Needless to say, the install stop there. Does the install program depend on some particular kernel feature for discovering the disk, beside the driver that work already? I tried enabling the automounter - that didn't help. Is there anything else that must (or must not) be configured? Helge Hafting
Re: help wanted for kernel install
Found it. It was in hamm and not in slink yet. I installed it and now I'm compiling. Hopefully, it will end up ok. Wish me luck! :-) On 9 Jan, Jean Pierre LeJacq wrote: On Sat, 9 Jan 1999 [EMAIL PROTECTED] wrote: Ok, now I cd to linux and I'm in 2.0.36. This seems right to me, but I must still missing something, because make menuconfig produces the following errors: debian:/usr/src/linux# make menuconfig rm -f include/asm ( cd include ; ln -sf asm-i386 asm) make -C scripts/lxdialog all make[1]: Entering directory `/usr/src/kernel-source-2.0.36/scripts/lxdialog' gcc -O2 -Wall -fomit-frame-pointer -DLOCALE -DCURSES_LOC=curses.h -c lxdialog.c -o lxdialog.o In file included from lxdialog.c:22: dialog.h:29: curses.h: No such file or directory make[1]: *** [lxdialog.o] Error 1 make[1]: Leaving directory `/usr/src/kernel-source-2.0.36/scripts/lxdialog' make: *** [menuconfig] Error 2 You need to install the curses3.4-dev package. -- 'til next we type... HAVE FUN!! -- Jesse
help wanted for kernel install
Hi, folks I want to update my kernel (2.0.34) to 2.0.36. I've already upgraded the rest of my system slink, so today I used apt-get to install the new kernel-source. When I switched to the /usr/src/linux directory, I found it was still pointing to kernel-source-2.0.34. I also found that the 2.0.36 stuff had not been unpacked. It still existed as a .tar.gz file, so I used gzip and tar to unroll it. Now I have a kernel-source-2.0.36 directory but /usr/src/linux was still pointing to 2.0.34. I rm'd the linux* links and created one pointing to 2.0.36. My /usr/src now looks like this: debian:/usr/src# l total 29991 drwxr-xr-x 3 root root 1024 Oct 13 13:54 kernel-headers-2.0.32 drwxr-xr-x 16 root root 1024 Jan 9 14:11 kernel-source-2.0.34 drwxr-xr-x 15 root root 1024 Jan 9 14:12 kernel-source-2.0.36 -rw-r--r-- 1 root root 30586880 Nov 27 23:58 kernel-source-2.0.36.tar lrwxrwxrwx 1 root src20 Jan 9 14:23 linux - kernel-source-2.0.36 Ok, now I cd to linux and I'm in 2.0.36. This seems right to me, but I must still missing something, because make menuconfig produces the following errors: debian:/usr/src/linux# make menuconfig rm -f include/asm ( cd include ; ln -sf asm-i386 asm) make -C scripts/lxdialog all make[1]: Entering directory `/usr/src/kernel-source-2.0.36/scripts/lxdialog' gcc -O2 -Wall -fomit-frame-pointer -DLOCALE -DCURSES_LOC=curses.h -c lxdialog.c -o lxdialog.o In file included from lxdialog.c:22: dialog.h:29: curses.h: No such file or directory make[1]: *** [lxdialog.o] Error 1 make[1]: Leaving directory `/usr/src/kernel-source-2.0.36/scripts/lxdialog' make: *** [menuconfig] Error 2 So, what's happing? Why didn't apt-get install unroll everything and set it up properly? Have I got myself hopelessly screwed up? And, how can I get things set up so that I may get on with this? TIA!! :-) -- 'til next we type... HAVE FUN!! -- Jesse
Re: help wanted for kernel install
On Sat, 9 Jan 1999 [EMAIL PROTECTED] wrote: Ok, now I cd to linux and I'm in 2.0.36. This seems right to me, but I must still missing something, because make menuconfig produces the following errors: debian:/usr/src/linux# make menuconfig rm -f include/asm ( cd include ; ln -sf asm-i386 asm) make -C scripts/lxdialog all make[1]: Entering directory `/usr/src/kernel-source-2.0.36/scripts/lxdialog' gcc -O2 -Wall -fomit-frame-pointer -DLOCALE -DCURSES_LOC=curses.h -c lxdialog.c -o lxdialog.o In file included from lxdialog.c:22: dialog.h:29: curses.h: No such file or directory make[1]: *** [lxdialog.o] Error 1 make[1]: Leaving directory `/usr/src/kernel-source-2.0.36/scripts/lxdialog' make: *** [menuconfig] Error 2 You need to install the curses3.4-dev package. -- Jean Pierre
Re: help wanted for kernel install
On 9 Jan, Jean Pierre LeJacq wrote: On Sat, 9 Jan 1999 [EMAIL PROTECTED] wrote: Ok, now I cd to linux and I'm in 2.0.36. This seems right to me, but I must still missing something, because make menuconfig produces the following errors: debian:/usr/src/linux# make menuconfig rm -f include/asm ( cd include ; ln -sf asm-i386 asm) make -C scripts/lxdialog all make[1]: Entering directory `/usr/src/kernel-source-2.0.36/scripts/lxdialog' gcc -O2 -Wall -fomit-frame-pointer -DLOCALE -DCURSES_LOC=curses.h -c lxdialog.c -o lxdialog.o In file included from lxdialog.c:22: dialog.h:29: curses.h: No such file or directory make[1]: *** [lxdialog.o] Error 1 make[1]: Leaving directory `/usr/src/kernel-source-2.0.36/scripts/lxdialog' make: *** [menuconfig] Error 2 You need to install the curses3.4-dev package. Where can that be found? I tried to apt-get it and get the following: debian:/home/jesse# apt-get install curses3.4-dev Updating package status cache...done Checking system integrity...ok E: Couldn't find package curses3.4-dev I have sources.lists pointing to slink.: (deb http://ftp1.us.debian.org/debian frozen main contrib non-free) Is it somewhere else? -- 'til next we type... HAVE FUN!! -- Jesse
Kernel Install
Ok, this is a BIG nasty weird problem. I'm runnig Debian With default Kernel 2.0.29 I grabbed Kernel 2.0.33 from ftp.kernel.org and did the following steps: tar zpfxv linux_2.0.33.tar.gz cd linux make mrproper make menuconfig make dep make clean make zlilo make modules make modules_install reboot Now, on ANY other machine.. doing a uname -a or checking /proc/version I'd have Linux 2.0.33 blah lah lah... But not on this box... it's still saying 2.0.29. Now I left the machine running for an hour.. and still.. 2.0.29.. so I rebooted.. still 2.0.29.. I copied the kernel I compiled to a disk and boot the disk in another machine.. kernel 2.0.33. Now I check the 'screwed' machine by attacking it with land/teardrop to see if it was just a version screw up and it was really running 2.0.33 just not reporting it.. and it bombed. so it's still running 2.0.29. does anyone hve ANY ideas about this? I have recompiled, reinstalled, reunpacked and redownloaded the kernel multiple times and it still will nt update. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Kernel Install
Install make-kpkg. After make menuconfig make-kpkg --revision version name kernel_image Install the new kernel with dpkg. Chuck On Tue, 3 Mar 1998, Scott Walker wrote: Ok, this is a BIG nasty weird problem. I'm runnig Debian With default Kernel 2.0.29 I grabbed Kernel 2.0.33 from ftp.kernel.org and did the following steps: tar zpfxv linux_2.0.33.tar.gz cd linux make mrproper make menuconfig make dep make clean make zlilo make modules make modules_install reboot Now, on ANY other machine.. doing a uname -a or checking /proc/version I'd have Linux 2.0.33 blah lah lah... But not on this box... it's still saying 2.0.29. Now I left the machine running for an hour.. and still.. 2.0.29.. so I rebooted.. still 2.0.29.. I copied the kernel I compiled to a disk and boot the disk in another machine.. kernel 2.0.33. Now I check the 'screwed' machine by attacking it with land/teardrop to see if it was just a version screw up and it was really running 2.0.33 just not reporting it.. and it bombed. so it's still running 2.0.29. does anyone hve ANY ideas about this? I have recompiled, reinstalled, reunpacked and redownloaded the kernel multiple times and it still will nt update. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] . -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Kernel Install
Hi, There is not enough information to make a judgement. Please provide the following: % ls -asCF /lib/modules % ls -als / % ls -asCF /boot BTW, on Debian, kernel-package offers a simple, convenient way of upgrading and maintianing severl different versions of the kernel on your machine concurrently. (/usr/doc/kernel-package/README.gz should be helpful). manoj -- What man has done, man can aspire to do. Jerry Pournelle, about space flight Manoj Srivastava [EMAIL PROTECTED] http://www.datasync.com/%7Esrivasta/ Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Kernel Install
Sounds like maybe you didn't redo your links for vmlinuz in / and didn't edit lilo.conf (if you want to still have your old kernel available in emergencys). Henry Hollenberg [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Kernel Install
Carroll Kong tar zpfxv linux_2.0.33.tar.gz technically you forgot.. cd /usr/include rm -rf asm linux scsi ln -s /usr/src/linux/include/asm-386 asm ln -s /usr/src/linux/include/linux linux ln -s /usr/src/linux/include/scsi scsi cd linux make mrproper make menuconfig make dep make clean make zlilo you also did not seem to check /etc/lilo.conf make modules make modules_install reboot Now, on ANY other machine.. doing a uname -a or checking /proc/version I'd have Linux 2.0.33 blah lah lah... But not on this box... it's still saying 2.0.29. Now I left the machine running for an hour.. and still.. 2.0.29.. so I rebooted.. still 2.0.29.. I copied the kernel I compiled to a disk and boot the disk in another machine.. kernel 2.0.33. Now I check the 'screwed' machine by attacking it with land/teardrop to see if it was just a version screw up and it was really running 2.0.33 just not reporting it.. and it bombed. you mean you thought it was running 2.0.33 because uname -a isn't going to lie on you. If uname -a says 2.0.29... you can immediately start thinking something about this box is different, the computer isnt' going to change kernels on you. Try different methods of approach to solve the problem then, your solutions of leaving it on for an hour did not help, but your land / teardrop was a good way to confirm the kernel. so it's still running 2.0.29. does anyone hve ANY ideas about this? I have recompiled, reinstalled, reunpacked and redownloaded the kernel multiple times and it still will nt update. This is how I would do it.. make zImage instead of make zlilo. *backup /vmlinuz, most likely a link to /boot/vmlinuz-2.0.29, to something like /boot/vmlinuz.old* cp /usr/src/linux/arch/i386/boot/zImage /vmlinuz *consider copying to /boot/vmlinuz-2.0.33 then recreating the /vmlinuz symlink* *check /etc/lilo.conf, make sure it is pointing to the right hd and /vmlinuz* lilo *check date of /vmlinuz or wherever dest file is. Since the dest file is /boot/vmlinuz-2.0.29, you might want to change it when you confirm it's file size and date is different and than vmlinuz.old* then reboot. on the other hand, you can check /etc/lilo.conf first... then run make zlilo. (considering the other steps as well) Hope this helps. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Kernel Install
On Wed, 4 Mar 1998, Carroll Kong wrote: tar zpfxv linux_2.0.33.tar.gz technically you forgot.. cd /usr/include rm -rf asm linux scsi ln -s /usr/src/linux/include/asm-386 asm ln -s /usr/src/linux/include/linux linux ln -s /usr/src/linux/include/scsi scsi NO, DON'T DO THIS. Read /usr/doc/libc5/FAQ.gz or /usr/doc/libc6/FAQ.Debian.gz for the reasons why not. -- Scott K. Ellis [EMAIL PROTECTED] http://www.gate.net/~storm/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Kernel Install
My bad. Sorry for the misinformation then. I am new to Debian... used to old school Slackware. Although it says it will break compilations... it seemed to work fine for the most part. But from now on, I will not do it. Carroll Kong On Wed, 4 Mar 1998, Scott Ellis wrote: On Wed, 4 Mar 1998, Carroll Kong wrote: tar zpfxv linux_2.0.33.tar.gz technically you forgot.. cd /usr/include rm -rf asm linux scsi ln -s /usr/src/linux/include/asm-386 asm ln -s /usr/src/linux/include/linux linux ln -s /usr/src/linux/include/scsi scsi NO, DON'T DO THIS. Read /usr/doc/libc5/FAQ.gz or /usr/doc/libc6/FAQ.Debian.gz for the reasons why not. -- Scott K. Ellis [EMAIL PROTECTED] http://www.gate.net/~storm/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Kernel Install
I found Dale Scheetz book helpful pg. 159-171 go over the traditional linux way of compiling a custom kernel vs. the Debian way. I got mine from www.linuxpress.com but you might find one in your local bookstore The Debian Linux User's Guide I'd have been pretty lost without it. Oh yeah, I don't have any stock in this company or book and wouldn't no Dale if I literally bumped into himjust found the book helpful for me. Henry Hollenberg [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Kernel Install
On Tue, 3 Mar 1998, Scott Walker wrote: Ok, this is a BIG nasty weird problem. I'm runnig Debian With default Kernel 2.0.29 So we're in bo, I take it. I grabbed Kernel 2.0.33 from ftp.kernel.org and did the following steps: tar zpfxv linux_2.0.33.tar.gz cd linux make mrproper make menuconfig make dep make clean make zlilo make modules make modules_install reboot Now, on ANY other machine.. doing a uname -a or checking /proc/version I'd have Linux 2.0.33 blah lah lah... But not on this box... it's still saying 2.0.29. Now I left the machine running for an hour.. and still.. 2.0.29.. so I rebooted.. still 2.0.29.. I copied the kernel I compiled to a disk and boot the disk in another machine.. kernel 2.0.33. Now I check the 'screwed' machine by attacking it with land/teardrop to see if it was just a version screw up and it was really running 2.0.33 just not reporting it.. and it bombed. so it's still running 2.0.29. does anyone hve ANY ideas about this? I have recompiled, reinstalled, reunpacked and redownloaded the kernel multiple times and it still will nt update. Well it pretty obviously put the compiled kernel somewhere where something couldn't find it, so it just carried on using the old one. Presumably it consistently did the same thing multiple times, which is a relief. I notice you're using a linux tarball and not the Debian kernel-source package, so there may be some sort of tweak missing. For example, the linux/Makefile says: # INSTALL_PATH specifies where to place the updated kernel and system map # images. Uncomment if you want to place them anywhere other than root. #INSTALL_PATH=/boot Now I compile my own kernels from kernel-source packages and I don't touch that line. However, make install always puts the new kernel and map in /boot (and moves symlinks in root), so something must be Debianised. You could try changing make zlilo to make zImage and make install and see where the kernel image ends up (remember the System.map too). Alternatively, you could get 33 in a debian package from unstable - I've compiled it for the joystick on a bo system without any problems. Cheers, -- David Wright, Open University, Earth Science Department, Milton Keynes MK7 6AA U.K. email: [EMAIL PROTECTED] tel: +44 1908 653 739 fax: +44 1908 655 151 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
