potato to woody upgrade problem
I searched but didn't find anything in google... I upgraded a box to 3.0 and that part went fine. But then I upgraded to the standard 2.4.18 kernel image deb (from a 2.2 kernel. I installed the matching initrd package too. At first I tried the k6 kernel, and I tried the 2.4bf kernel and got the same problem. Which is, it reboots fine, but when loads the kernel modules it locks up dead, I have to hit the reset button. I remember that if you wanted to run a 2.4 kernel under potato you needed to install a different version of modutils, but I'm running 3.0, and I have the latest modutils installed. The release notes didn't say there were any problems going from 2.2 to 2.4. What did I forget to do? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: potato to woody upgrade problem
On Tue, Oct 22, 2002 at 08:26:09AM -0400, [EMAIL PROTECTED] wrote: > > > The release notes didn't say there were any problems going > > from 2.2 to 2.4. What did I forget to do? > > If you modified /etc/lilo.conf to add the new kernel, did you remember to > type "lilo" before rebooting? Not doing this will lock it up for sure. > > The bootdisk-HOWTO tells you what various LILO error codes (ie, "L" or > "LI") mean and how to fix them: > > http://www.tldp.org/HOWTO/Bootdisk-HOWTO/a1483.html > > I get well past the lilo prompt. I can see my initrd being mounted in the bootup messages. Then it mounts the real root filesystem, it gets past the point where it checks module dependency, it locks up right after it loads the module for my network card. The same setup with my old 2.2.15 kernel boots just fine, loads the eepro module and is fully functional on my network. If I comment out eepro from /etc/modules, my box boots up under the 2.4 kernels and I can log in. An odd thing I just noticed is there are no modules loaded at all. However, I can insmod eepro if I give it the IRQ and IO port on the commandline, but it locks up dead when I do an "ifup eth0". I have to hit reset to reboot, if I hit capslock or numlock, the lights on the keyboard do not change. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: potato to woody upgrade problem
On Tue, Oct 22, 2002 at 03:07:00PM -0700, nate wrote: > D.U. said: > > On Tue, Oct 22, 2002 at 08:26:09AM -0400, [EMAIL PROTECTED] wrote: > > > If I comment out eepro from /etc/modules, my box boots up under the 2.4 > > kernels and I can log in. An odd thing I just noticed is there are no > > modules loaded at all. However, I can insmod eepro if I > > give it the IRQ and IO port on the commandline, but it locks up dead when > > I do an "ifup eth0". I have to hit reset to reboot, if I hit > > capslock or numlock, the lights on the keyboard do not change. > > > looks like you found the problem then :) > > I'm not sure if the stock 2.4.x kernel has it but there is another > module for the eepro called the e100 module which is from intel. I think > it is included in the 2.4.x tree, try it out 'modprobe e100'. another > thing may be to try to compile another version of the driver, the official > site for the eepro driver is here: > http://www.scyld.com/network/eepro100.html > > theres also mailing list and stuff there too, I reccomend posting > there, I used to be on the list, donald becker is quite helpful to > posters. Also you can try to grab the diagnostics program and run it > on your card as well. > > all my systems run 2.2.19.. > > nate > The page you point to is only for PCI cards, mine is a ISA intel pro10. Thanks for the tip, but I don't think the problem is specific to the NIC module. I'll wait a bit before I bother them. At boot up some basic modules like unix.o, etc should be loaded but they are not. There is a full set of modules for each kerenel in /lib/modules/ so I'm not sure what is going on. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
unix2dos equivalent?
What is the debian eqivalent of dos2unix and unix2dos? I've apt-cache searched but came up empty. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
