SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
for the framebuffer prob, try compiling for ur video card as a module and compiling the VGA and VESA directly into the kernel. This worked for my system.
I compiled it from scratch and have been using it for the last few days and it seems to work really well on my system. I don't know about K3b as a normal user, but burning data and audio CD's using sudo or kdesu works fine for me with good results.
Installed it just yesterday, after some problems with modules (all my faults), it works fine. Just two flaws:
1. Something asks fos ide_scsi module = FATA: ide_scsi module not found - I just thought I compiled everything around ide and sata into kernel. But I will chceck that later, maybe it is just my fault again :-)
2. less works the interesting way, or better, does not work. When I type "less something" or "anything | less" it just shows the first page and quits. No error, no log, just quits. I does only with this kernel, using 2.6.8* and default vmlinuz it works fine. Deos anyone encountered any problem like that? More and most seem to work ok.
after the patch to 2.6.9 from 2.6.8.1, uname identified it as still a 2.6.8.1 and couldn't ssh out(got a "ssh_askpass: exec(/usr/libexec/ssh-askpass): No such file or directory" error) or use cat.
I compiled from full source, and took care of the identification problem but the other two were still there. installed 2.6.6 and all is fine. I used the same .config from the 2.6.8.1 except minus a few net drivers. I tried looking through the config but didn't see anything that looked relevant to ssh.
any ideas?
thanks.
go to
Device Drivers/Character devices/
and turn off
[ ] Legacy (BSD) PTY support (CONFIG_LEGACY_PTYS=n)
Well, there is a problem viewing man-pages, seems to be in slackware.
But this could be corrected just by opening the file: /etc/udev/rules.d/udev.rules
locating a line that looks like KERNEL="tty[p-za-e][0-9a-f]*", NAME="tty/s%n", SYMLINK="%k"
and if found change "tty/s%n" to "pty/s%n".
Easy done!
I'm not even sure if this is directly related to the kernel but the problem appeared when I went from 2.6.8.1 to 2.6.9 (recompiling the source, not patching since the patch doesn't work on 2.6.8.1) on Slackware. Also when I tried to go back to the old 2.6.8.1-kernel the problem was gone. But it works now anyway.
not sure what's up with it, and not sure what include/linux/version.h is
meant. /usr/include/linux/version.h looks fine, and /usr/src/linux/include/linux/version.h
doesn't exists.
If anyone has an answer, that would be highly appreciated
-JSS
I think you tryed to use an invalid character such as single quotes (') in the "Local Version" option.
Some time around 2.6.7 there was a talk about making the even branch essentially "unstable" by sticking all new "unstable" things in the tree and letting the distros sort this mess out. There was lotsa whining about this but Linus and the rest of the gang stood the ground.
Well, I guess we'll have to wait till Pat finds time/desire to bake a Slackware-specific, hopefully stable source tree.
Alright, I noticed that many commented about their 2.6.9 compilation getting crapped out.
I'd assume that you ran the diff patch on your 2.6.8.1 sources. I've read somewhere (I really can't recall the source), that the patch was meant to be applied on the 2.6.8 sources.
So this might be the source of your problem. I'd recommend that those who are having problems compiling to download the full source of 2.6.9.
You were right it was enabled, but editing the /etc/udev/rules.d/udev.rules file took care of it. I tend to use the CLI alot and if disabling the legacy bsd pty support is going to cause problems opening terminals in X , as cedrik pointed out, I think I might leave as it is.
hmm..... it appears that usb doesn't work... and I did enable it... I'm working to figure out what I did wrong as I really don't think it was just broken for my chipset... though it is a distinct possibility.
if it is I'm definitely reverting to the stock 2.4.27 kernel.
well... that was a fun romp in kernel development... but I think I'm reverting to the ol' 2.4 series.. I'll try the next release but currently I've found that two much stuff doesn't work.. and much of it isn't in my realm of ability to fix..
I think I'll wait until the 2.6 kernel matures a bit more.
I do not think this file has anything to do with it. What I mean is, the option "Local Version -- append to kernel release" which can be found as first option in the "General Setup" (at least using make menuconfig). This feature allows you to append a string to the version number of the kernel. But if this string contains single quotes it will cause this error.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.