SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
patching file scripts/Kbuild.install
patch unexpectedly ends in middle of line
Hunk #1 succeeded at 95 with fuzz 1.
but klibc seemed to build OK anyway! There were a lot of warnings about zero length files at the end, but all seemed to be .install files inside the klibc headers directories, so I assume these are nothing to worry about!
The next job will be to build all the other bits and pieces I need to get uvesafb running. Hopefully, they will be simpler than this!
Yes, thanks! I know about v86d, but that needs to be built with klibc (as I understand it), so I needed to get that built first!
From my experience, klibc isn't quite ready for general purpose release yet. It seems that it works fine if you have a bog-standard system, but if you have built your own kernel, it needs some tweaks to get it to work! And some of the steps necessary aren't obvious to "hobbyist" users, like myself!
Hopefully this thread will help others avoid my mistakes, and again, a big thank you to turtleli for correcting my errors! If (s)he isn't a klibc dev, (s)he should be!
Yes you are correct, you have to build klibc first then v86d, I actually maintain the klibc package over at www.slackbuilds.org but I hadn't tried building it with a custom 3.4 kernel so I knew wouldn't be able to help. I'm glad you got it sorted out though .
Have all the vga lines been commented out in lilo.conf?
Nothing obvious in /var/log/messages or dmesg. uvesafb doesn't auto-load, unless forced to by an initrd, which shouldn't be necessary. The initramfs image is in /usr/share/v86d and has been inserted into the kernel config.
Sorry for the delayed reply - I'm away from home at the moment, and my connection is erratic!
I built uvesafb as a module. I was trying to avoid building it in, as the NVidia drivers complain bitterly if you build the vesa driver in, and I assume they would also complain about uvesafb. But maybe not?
And I need the NVidia drivers as I do a lot of HD video work, so I need the GPU acceleration for video. The open source drivers don't provide this, sadly.
I'm beginning to wonder if uvesafb is worth the aggro though. The NVidia drivers still worked - even though they complained - when I used the plain vesafb, but there seemed to be a slight performance hit in processing some video files.