Re: kernel 2.1.3x?
I have a working 2.1.31 kernel that I compiled. Some of the modules, such as vfat and serial, load ok but scsi_mod has missing symbols that prevent my aic7xxx from loading. --Brian. Hamish Moffatt wrote: Anyone having much luck with 2.1.3x? I'm running 2.1.29 and it's fine, except that the nfs module doesn't insert. But no luck with 2.1.33 or 2.1.35; both have lots of missing symbols on all the hardware drivers, probably relating to PNP support. I just ftpd the whole 2.1.35 source and the new modutils 2.1.34 and will see how it goes, I have been patching up. Anyone else having this? Nobody in the linux.dev.kernel group (or the mailing list) seem to have mentioned it. Hamish -- Hamish Moffatt, StudIEAust[EMAIL PROTECTED] Student, computer science computer systems engineering.3rd year, RMIT. http://yallara.cs.rmit.edu.au/~moffatt (PGP key here) CPOM: [ ] 42% -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: kernel 2.1.3x?
Brian N. Borg [EMAIL PROTECTED] writes: I have a working 2.1.31 kernel that I compiled. Some of the modules, such as vfat and serial, load ok but scsi_mod has missing symbols that prevent my aic7xxx from loading. --Brian. Hamish Moffatt wrote: Anyone having much luck with 2.1.3x? I'm running 2.1.29 and it's fine, except that the nfs module doesn't insert. But no luck with 2.1.33 or 2.1.35; both have lots of missing symbols on all the hardware drivers, probably relating to PNP support. I just ftpd the whole 2.1.35 source and the new modutils 2.1.34 and will see how it goes, I have been patching up. Anyone else having this? Nobody in the linux.dev.kernel group (or the mailing list) seem to have mentioned it. Hamish I just compiled a fresh 2.1.35 kernel for my home machine (IDE-based). When I try to boot this kernel, either from the IDE disk or from a floppy disk, I get the messages about uncompressing the kernel, then now booting the kernel, then nothing. Well, actually not nothing. There is a whole lot of disk activity on the IDE disk at this point, even when booting off the floppy. When I eventually halt this and reboot an old kernel, it has to fsck my disk partitions because they look dirty. So I don't even get as far as finding out that there are missing symbols. We were able to compile and boot a 2.1.35 kernel for my office machine but that has / on a SCSI disk. We do have an old IDE drive in there as well and this morning the driver for that got jammed to the point that we had to reboot. It appears that the 2.1.3x series of kernels are indeed development versions. I think I will stay with the 2.0.3x series for a while. -- Douglas Bates[EMAIL PROTECTED] Statistics Department608/262-2598 University of Wisconsin - Madisonhttp://www.stat.wisc.edu/~bates/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: kernel 2.1.3x?
Douglas Bates writes: It appears that the 2.1.3x series of kernels are indeed development versions. I think I will stay with the 2.0.3x series for a while. 2.1.29 seems pretty stable. From what I gather, for later ones you are better off not using modules and then I think you're safe. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
2.1.35 works [was: kernel 2.1.3x?]
On Tue, 22 Apr 1997 21:16:19 -0500 (CDT), Douglas Bates [EMAIL PROTECTED] said: Douglas I just compiled a fresh 2.1.35 kernel for my home machine (IDE-based). Douglas When I try to boot this kernel, either from the IDE disk or from a Douglas floppy disk, I get the messages about uncompressing the kernel, then Douglas now booting the kernel, then nothing. Well, actually not nothing. Douglas There is a whole lot of disk activity on the IDE disk at this point, Douglas even when booting off the floppy. When I eventually halt this and Douglas reboot an old kernel, it has to fsck my disk partitions because they Douglas look dirty. I ran into the same problem myself, but luckily I also ran into the answer in comp.os.linux.development.system: in the newest kernels, virtual tty support is optional, and is not on by default (don't ask me why). The system boots ok, but it doesn't have a console :-) Use 'make oldconfig' when you're configuring the kernel, or do the normal config routine and remember to turn virtual console support on. 2.1.35 works ok for me over here -- I don't use modules, though, so can't comment on that. BTW, if anyone can tell me what my /etc/init.d/network should look like with the new kernel, I'd be grateful. Things seem to work ok, but /sbin/ifconfig and /sbin/route are giving me warnings at boot time. Well, life on the bleeding edge is always interesting :-) //Petri -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: 2.1.35 works [was: kernel 2.1.3x?]
Petri Wessman [EMAIL PROTECTED] writes: Well, life on the bleeding edge is always interesting :-) I'd be a little careful with 2.1.25. At least on my system, clock() always returned 0. Not good. -- Rob -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
kernel 2.1.3x?
Anyone having much luck with 2.1.3x? I'm running 2.1.29 and it's fine, except that the nfs module doesn't insert. But no luck with 2.1.33 or 2.1.35; both have lots of missing symbols on all the hardware drivers, probably relating to PNP support. I just ftpd the whole 2.1.35 source and the new modutils 2.1.34 and will see how it goes, I have been patching up. Anyone else having this? Nobody in the linux.dev.kernel group (or the mailing list) seem to have mentioned it. Hamish -- Hamish Moffatt, StudIEAust[EMAIL PROTECTED] Student, computer science computer systems engineering.3rd year, RMIT. http://yallara.cs.rmit.edu.au/~moffatt (PGP key here) CPOM: [ ] 42% -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: kernel 2.1.3x?
Anyone having much luck with 2.1.3x? I'm running 2.1.29 and it's fine, except that the nfs module doesn't insert. But no luck with 2.1.33 or 2.1.35; both have lots of missing symbols on all the hardware drivers, probably relating to PNP support. The same is true here. I can run 2.1.29 but not 2.1.30-35. I receive the messages you describe above. I just ftpd the whole 2.1.35 source and the new modutils 2.1.34 and will see how it goes, I have been patching up. Already done this without any luck. If you have a better luck, let me know what you have done. Thanks. Ramos. -- Jose' RAMOS Goncalves [EMAIL PROTECTED] Department of Physics * http://www.rdg.ac.uk/Physics University of Reading, Reading, England, U.K. Debian GNU/Linux 1.3 * http://www.debian.org -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
