LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
LinkBack Search this Thread
Old 11-17-2012, 08:04 PM   #16
turtleli
Member
 
Registered: Aug 2012
Location: UK
Distribution: Slackware 14.0, 14.1
Posts: 108

Rep: Reputation: Disabled

I think the "make install" command doesn't work with KLIBCKERNELSRC set to /kernel_source/usr .

I've attached a quick fix patch (remove the .txt) which lets it build (I've tested it on the 3.4 series). You'll need to add to your current SlackBuild script
Code:
patch -p1 < $CWD/klibc_directory.patch
directly after the line
Code:
cd $PRGNAM-$VERSION
Attached Files
File Type: txt klibc_directory.patch.txt (919 Bytes, 32 views)
 
Old 11-18-2012, 07:48 AM   #17
pchristy
Member
 
Registered: Oct 2012
Location: UK
Distribution: Slackware
Posts: 59

Original Poster
Rep: Reputation: Disabled
WooHoo! It finally built!

Turtleli - you are a genius!

The patch threw up an error when it went in:

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!

Many, many thanks for your help!

--
Pete
 
Old 11-18-2012, 08:49 AM   #18
turtleli
Member
 
Registered: Aug 2012
Location: UK
Distribution: Slackware 14.0, 14.1
Posts: 108

Rep: Reputation: Disabled
Whoops, I cut off the newline at the end of the patch by mistake. Was SSHing to my Slackware box and copy and pasted instead of doing a file transfer.
 
Old 11-18-2012, 11:43 AM   #19
pchristy
Member
 
Registered: Oct 2012
Location: UK
Distribution: Slackware
Posts: 59

Original Poster
Rep: Reputation: Disabled
Luckily, it doesn't matter! I've tried it again with a newline added, and it still works just the same - but no error message!



--
Pete
 
Old 11-18-2012, 01:45 PM   #20
Daedra
Senior Member
 
Registered: Dec 2005
Location: Springfield, MO
Distribution: Slackware64-14.1
Posts: 1,216

Rep: Reputation: 176Reputation: 176
If your going to use uvesafb your going to also need v86d, here is a SlackBuild I made for it if you are interested, I ran uvesafb for a while about a year or so ago.


http://dl.dropbox.com/u/85079539/v86d.tar.gz
 
Old 11-18-2012, 06:40 PM   #21
pchristy
Member
 
Registered: Oct 2012
Location: UK
Distribution: Slackware
Posts: 59

Original Poster
Rep: Reputation: Disabled
Daedra,

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!

--
Pete
 
Old 11-18-2012, 07:01 PM   #22
Daedra
Senior Member
 
Registered: Dec 2005
Location: Springfield, MO
Distribution: Slackware64-14.1
Posts: 1,216

Rep: Reputation: 176Reputation: 176
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 .
 
Old 11-19-2012, 04:01 AM   #23
pchristy
Member
 
Registered: Oct 2012
Location: UK
Distribution: Slackware
Posts: 59

Original Poster
Rep: Reputation: Disabled
Yes, the failure to build was partly my fault (misunderstanding where the kernel headers got installed), but also partly due to obscure requirements from the library, which aren't clearly documented!

I'm hoping to get the rest of the requirements built today, and get uvesafb up and running.

Again, thanks to all here for your assistance!

--
Pete
 
Old 11-19-2012, 08:54 AM   #24
pchristy
Member
 
Registered: Oct 2012
Location: UK
Distribution: Slackware
Posts: 59

Original Poster
Rep: Reputation: Disabled
Hm! Still in trouble! Having built everything, dmesg reports:

dmesg |grep uvesafb
Command line: auto BOOT_IMAGE=Linux ro root=802 video=uvesafb:1024x768-32,mtrr:3,ywrap
Kernel command line: auto BOOT_IMAGE=Linux ro root=802 video=uvesafb:1024x768-32,mtrr:3,ywrap

and I only get a vga console. The uvesafb module does not load, though it does exist.

Creating an initrd to force the uvesafb module to load generates this:

dmesg |grep uvesafb
Command line: auto BOOT_IMAGE=Linux ro root=802 video=uvesafb:1024x768-32,mtrr:3,ywrap
Kernel command line: auto BOOT_IMAGE=Linux ro root=802 video=uvesafb:1024x768-32,mtrr:3,ywrap
uvesafb: NVIDIA Corporation, GT216 Board - 0682vb12, Chip Rev , OEM: NVIDIA, VBE v3.0
uvesafb: VBIOS/hardware supports DDC2 transfers
uvesafb: monitor limits: vf = 75 Hz, hf = 83 kHz, clk = 170 MHz
uvesafb: scrolling: redraw
uvesafb: framebuffer at 0xdf000000, mapped to 0xffffc90008100000, using 10240k, total 14336k

Better, but still only a vga console! Any references to the protected mode interface are missing.

The only oddity I've noticed are the zero length .install files created when klibc is built. Is this normal?

--
Pete
 
Old 11-20-2012, 07:01 AM   #25
turtleli
Member
 
Registered: Aug 2012
Location: UK
Distribution: Slackware 14.0, 14.1
Posts: 108

Rep: Reputation: Disabled
The zero length .install files should be normal.

Have all the vga lines been commented out in lilo.conf?
 
Old 11-20-2012, 09:16 AM   #26
pchristy
Member
 
Registered: Oct 2012
Location: UK
Distribution: Slackware
Posts: 59

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by turtleli View Post
The zero length .install files should be normal.
OK, that's good - I need to look elsewhere....

Quote:
Originally Posted by turtleli View Post
Have all the vga lines been commented out in lilo.conf?
Yes.

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.

Stumped!!!



--
Pete
 
Old 11-21-2012, 05:06 PM   #27
turtleli
Member
 
Registered: Aug 2012
Location: UK
Distribution: Slackware 14.0, 14.1
Posts: 108

Rep: Reputation: Disabled
Did you build uvesafb into the kernel or as a module?

I don't use uvesafb anymore, but I remember it worked when I built it into the kernel.
 
Old 11-24-2012, 08:10 AM   #28
pchristy
Member
 
Registered: Oct 2012
Location: UK
Distribution: Slackware
Posts: 59

Original Poster
Rep: Reputation: Disabled
Hi Turtleli,

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.

Cheers,

--
Pete
 
Old 12-19-2012, 01:53 PM   #29
paltus
LQ Newbie
 
Registered: Dec 2012
Posts: 1

Rep: Reputation: Disabled
Many thanks to Turtleli!

Using his patch and instructions
klibc-2.0.2
and SlackBuild for 2.0.1. from slackbuilds.org (modified version number in the script)

sucessfully built klibc for kernel-3.5.3
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Is it a bug of klibc? If so, how can I update it? yangzhichina Slackware 5 11-07-2010 12:18 AM
Trying to install ethernet adapter driver, not finding kernel-devel or kernel-headers oneFishtwoFish Red Hat 5 08-31-2010 06:24 PM
/usr/lib klibc question Daedra Slackware 5 01-06-2010 03:25 AM
Zypper wants to dl the wrong kernel headers... YaST doesnt have current headers zorb Suse/Novell 2 11-28-2009 11:12 AM
Automatic removal of kernel headers package when kernel packages are removed bgoodr Debian 3 12-30-2008 08:14 PM


All times are GMT -5. The time now is 03:24 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration