NotebookForums.com › Forums › General Notebook Discussions › Linux & Other OS's › The 5680/8890 Gentoo Thread
New Posts  All Forums:Forum Nav:

The 5680/8890 Gentoo Thread - Page 4

post #61 of 170
Thread Starter 
Wow! Cool! So the 12.3 driver is actually available on the mirrors?
post #62 of 170
No, because the 0.12.3 ebuild isn't technically in the portage tree (yet). So when you emerge 0.12.3, it'll try to get the file from the mirrors, won't find it, and then resort to the real source (http://w1.894.telia.com/~u89404340/touchpad/) and get it from there.
post #63 of 170
Thread Starter 
Smart mo'fo'! Thanks for the info, Xiphux.
post #64 of 170

Howto for "Logitech QuickCam for Notebooks Pro"

Howto get a "Logitech QuickCam for Notebooks Pro" working on a Sager 5680 laptop using a Gentoo/Linux 2.6 kernel

First you need to activate a few options in your kernel .config and recompile the kernel:
HTML Code:
CONFIG_VIDEO_DEV=y
CONFIG_SND_USB_AUDIO=y
CONFIG_USB_AUDIO=y
CONFIG_USB_PWC=m
If you want image compression (who wouldn't, saves bandwidth) you must download the pwcx module here:
http://www.smcc.demon.nl/webcam/pwcx-8.2.2.tar.gz
The 8.4 version from same site won't work, but the new 9.0 beta-release might. However, I haven't tested it yet, mileage may very, etc.

Untar the module somewhere and remember to copy it to the newest /lib/modules directory like this (I extracted mine in my /root folder):
HTML Code:
cp -v /root/usb-pwcx-8.2.2/x86/gcc-3.2/pwcx-2.5.67.ko /lib/modules/$NEWKERNELVERSION/kernel/drivers/usb/media/pwcx.ko
where $NEWKERNELVERSION is the version of the new kernel you'll be running.

Insert the following two lines in your /etc/modules.autoload.d/kernel-2.6 in this order to enable automatic use of the modules upon system boot:
HTML Code:
pwc
pwcx
Create a file named pwc in your /etc/modules.d/ directory with the following contents:
HTML Code:
options pwc size=vga leds=500,500 fps=15 compression=0
post-install pwc insmod /lib/modules/`uname -r`/kernel/drivers/usb/media/pwcx.ko >/dev/null 2>&1  || :
If you haven't installed the pwcx module, leave out the "options" line, as the size vga is only possible to run at 15 fps using compression.

Last time I checked, the pwcx module caused a kernel panic when rmmod'ed upon reboot/shutdown, so comment out the following line in /etc/hotplug/usb.rc like this:
HTML Code:
#rmmod pwc pwcx         >/dev/null 2>&1
Ok, now that the video part of the webcam setup is done, it's time to add the final part, the USB audio setup.

Modify your /etc/modules.d/alsa to fit in the USB soundcard from the webcam. Mine looks like this:
HTML Code:
# Alsa 0.9.X kernel modules' configuration file.
# $Header: /home/cvsroot/gentoo-x86/media-sound/alsa-utils/files/alsa-modules.conf-rc,v 1.1 2003/08/05 21:07:55 johnm Exp $

# ALSA portion
alias char-major-116 snd
# OSS/Free portion
alias char-major-14 soundcore

##
## IMPORTANT:
## You need to customise this section for your specific sound card(s)
## and then run `update-modules' command.
## Read alsa-driver's INSTALL file in /usr/share/doc for more info.
##
##  ALSA portion
## alias snd-card-0 snd-interwave
## alias snd-card-1 snd-ens1371
alias snd-card-0 snd-intel8x0
#alias snd-card-1 snd-usb-audio
alias snd-card-1 snd-pcm-oss
##  OSS/Free portion
alias sound-slot-0 snd-card-0
alias sound-slot-1 snd-card-1
##

# OSS/Free portion - card #1
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
##  OSS/Free portion - card #2
alias sound-service-1-0 snd-mixer-oss
alias sound-service-1-3 snd-pcm-oss
alias sound-service-1-12 snd-pcm-oss

alias /dev/mixer snd-mixer-oss
alias /dev/dsp snd-pcm-oss
alias /dev/midi snd-seq-oss

# Set this to the correct number of cards.
options snd cards_limit=2
After all the above has been done, run the following as root to update the module info:
HTML Code:
update-modules
Now all there's left is to reboot the machine in order to run the new kernel.

There! Everything should run smoothly! Now would be a good time to emerge gnomemeeting to see if everything does indeed work as expected.
post #65 of 170
Thread Starter 
Thanks a lot, Darkless. Really good info. It would be interesting to hear if it works properly for people.

Mikhail
post #66 of 170
Quote:
Originally Posted by xiphux
Just copy the ebuild and merge.

cp /usr/portage/x11-misc/synaptics/synaptics-0.12.1.ebuild /usr/portage/x11-misc/synaptics/synaptics-0.12.3.ebuild
emerge synaptics
Hi guys, I just joined the forums as I've got a 5680 on order and am something of a gentoo fanatic.

I just thought I'd add by way of introduction that if you're worried about the strict correctness of your portage tree, you'd want to:
HTML Code:
cp /usr/portage/x11-misc/synaptics-0.12.1.ebuild /usr/local/portage/x11-misc/synaptics/synaptics-0.12.3.ebuild
and if you haven't already, uncomment
HTML Code:
PORTDIR_OVERLAY="/usr/local/portage"
in /etc/make.conf

This keeps what is technically an "unofficial" ebuild in your own sandbox and out of the main portage tree. This technique is also useful for installing ebuild from places like breakmygentoo.net.

No big deal, just thought I'd mention it
post #67 of 170
Thread Starter 
Good stuff, Thinknot. Speaking of portage, has anyone noticed it misbehave recently? For a little while (a certain version of it) had some devfs 'no entry found' messages at the end of successful emerges, while recently its been trying to downgrade packages via 'emerge -U world) even with the upgradeonly switch; I even tried setting ACCEPT_KEYWORDS to "~x86" at the beginning of the merge command. The most recent victim of the downgrade syndrome has been gaim (of course, I never downgraded the thing - I always pretend an emerge before doing the same thing; I discovered the issue and had to manually emerge all legit emerge -U world packages). Ideas?

Mikhail
post #68 of 170

5670 note may be relevant to newer models.

I just did a emerge -U world and had problems with qt
got this at the failure
!!! ERROR: x11-libs/qt-3.2.3-r1 failed.
!!! Function src_compile, Line 109, Exitcode 2
!!! (no error message)
I "fixed" it by unemerging the existing qt, then doing a opengl-update xfree and reemerged seemes to have worked. Now I just have to let it finish and fix my config files and we shall see.
post #69 of 170
Thread Starter 
Woah, thats a weird one. Is that the Qt that went along with KDE 3.1.5? Mine compiled flawlessly with opengl set to ATI, etc. Did you by any chance try to find the cause & solution on the Gentoo forums? Unless its something simple, I usually head over there right away in hope of finding a reference to a bug report, etc.

Mikhail
post #70 of 170
I don't use KDE proper, but I do have a few apps that depend on it. Yeah it's happened to a few guys on there. From what I read there wasn't any defined reason for it nor a bug report as it can't be narrowed down to any specifics. The "fix" was mentioned in the spanish forum.
post #71 of 170
Thread Starter 
... Small tip for those who want to access Windows shares on their home network under Linux:

All I had to do is emerge samba, and recompile my kernel with SMB support (for 2.6.1, using menuconfig, File Systems -> Network File Systems -> SMB file system support). While Samba itself gave me all the core utilities, the SMB support in the kernel allowed me to mount Windows shares or just browse them by typing smb://[WHATEVER WINDOWS MACHINE NAME]/[SHARE FOLDER]... into a file browser. In addition, for convenience, I emerge Smb4K (a very nice Windows network browser for KDE) along with ksambaplugin (a very nice Samba configuration utility that integrates itself into the KDE Control Center).

Mikhail
post #72 of 170
Quote:
Originally Posted by mmarkin
... Small tip for those who want to access Windows shares on their home network under Linux:

All I had to do is emerge samba, and recompile my kernel with SMB support (for 2.6.1, using menuconfig, File Systems -> Network File Systems -> SMB file system support). While Samba itself gave me all the core utilities, the SMB support in the kernel allowed me to mount Windows shares or just browse them by typing smb://[WHATEVER WINDOWS MACHINE NAME]/[SHARE FOLDER]... into a file browser. In addition, for convenience, I emerge Smb4K (a very nice Windows network browser for KDE) along with ksambaplugin (a very nice Samba configuration utility that integrates itself into the KDE Control Center).

Mikhail
For those of us not using KDE LinNeighborHood seems to work well for a network neighborhood replacement. I've been using it since my redhat 5.x days.
post #73 of 170
Quote:
Originally Posted by thinknot
Hi guys, I just joined the forums as I've got a 5680 on order and am something of a gentoo fanatic.

I just thought I'd add by way of introduction that if you're worried about the strict correctness of your portage tree, you'd want to:
HTML Code:
cp /usr/portage/x11-misc/synaptics-0.12.1.ebuild /usr/local/portage/x11-misc/synaptics/synaptics-0.12.3.ebuild
and if you haven't already, uncomment
HTML Code:
PORTDIR_OVERLAY="/usr/local/portage"
in /etc/make.conf

This keeps what is technically an "unofficial" ebuild in your own sandbox and out of the main portage tree. This technique is also useful for installing ebuild from places like breakmygentoo.net.

No big deal, just thought I'd mention it
Well, I personally leave it in the standard portage tree because I _want_ it to be deleted on the next sync. So it'll be gone, and when it finally makes it back into the portage tree through normal means, I can re-emerge it in case the new ebuild has version specific fixes that weren't in the old copied ebuild. Because forcing the version is not really the standard way to upgrade, I don't really want to keep the forced ebuilds around.

Plus, my portage overlay is so cluttered with stuff that I want to keep the ebuilds I put in there to a minimum. And if an emergency really does arise, there's always a backup copy of the ebuild in /var/db/pkg.
post #74 of 170
Thread Starter 
Good point, Xiphux... Thanks for the tip, BSmith.
post #75 of 170
I haven't read over all the other threads, but I've fixed my general problems with Gentoo on the 5670.

For the sound, it turns out that ALSA defaults the mixer to zero levels.

The graphics was a bit more complex. It turns out that you have to (on the M9, at least) completely disable DRI in order for the ati-drivers to work. One kernel change later, it was working.

Next: to get ACPI working.
post #76 of 170
That's weird, ati-drivers work for me with dri in the kernel. In fact, I have both an fglrx (ati-drivers) and radeon (DRI) module for my particular sources, and switch at will with just a modprobe or two, an opengl-update and a symlink for XF86Config.
post #77 of 170
Xiphux, do you have a 5680? Because I think that the Radeon 9600 Pro Mobility *does* work with the drivers with DRI enabled.
post #78 of 170
No, I have an 8887, Radeon R250 Lf [Radeon Mobility 9000 M9].
post #79 of 170
Well, then I'm stumped. I got gentoo-dev-sources today for 2.6.1, and this time I configured my system without DRI (as recommended by some guys on the gentoo forums) and now I can get direct rendering. Before, my XFree86.log showed that there was an error activating DRI.

Anyways, we've all got rendering, so happy days.
post #80 of 170
Thread Starter 
As suggested somewhere, I set up my kernel without DRM (I think it was DRM in the kernel, not DRI) in the first place. Maybe due to this, the ati-driver installation was totally smooth on my machine. For those jumping in and only reading the end of this thread, I have a 5680.

Mikhail
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Linux & Other OS's
NotebookForums.com › Forums › General Notebook Discussions › Linux & Other OS's › The 5680/8890 Gentoo Thread