For anyone interested in testing new xorg stuff, here it is: [URL]. The good news is that this package set should work fine in either 13.1 or -current. The build box is 13.1, so I know they're compatible there; however, I'm running them on both 13.1 and -current systems, so I'm pretty sure they'll work on either. Be sure to read the NOTES file before you go digging around in PACKAGES.
View 14 RepliesI am using Fedora 13 and I have one program (wine) that I need to start grabbing for the updates-testing repo instead of the default repositories in order to get newer versions. I think I can figure out how to add that repository, but I need to know if there are any others I need to disable or any other changes I need to make to my system so that I don't confuse my set up with conflicting updates.
Also, is there anything special I need to do to be sure that only that one program is grabbed from the testing repo when I run regular updates?
New applesmc kernel module with dynamic configuration. The amount of machines supported by this module has increased rapidly over the past years, and the detailed driver support of the many flavors is quickly becoming a problem. The attached dkms package contains a new, dynamically configured driver which fixes a number of outstanding issues:
* Support for all new models since MacbookPro 6.
* Support for variable number of processors in the MacPros.
* Handles the odd temperature sensor types found on new models.
* Fixes minor read problems on many intermediate models.
And, of course, all models back to the MacBook1,1 should work at least as well as before. Please test and report the outcome in this thread, stating your machine model and a simple "OK" or a description of the problem. As soon as things seem to work as expected, the patches will go upstream.
It was released a couple days ago, and the Scribus team always sends new releases to Fedora, but on my Fedora 14 x86_64 computer I can't find it in updates-testing:
Code:
# yum install scribus --enablerepo=updates-testing
Loaded plugins: refresh-packagekit
updates-testing/metalink | 15 kB 00:00
updates-testing | 4.7 kB 00:00
updates-testing/primary_db | 880 kB 00:00
Setting up Install Process
Package scribus-1.3.9-1.fc14.x86_64 already installed and latest version
Nothing to do
I can always download the RPM and install it directly, but I prefer to use yum. Did the updates-testing people misplace it? Or did the Scribus team forget to send it to Fedora?
I'm running Debian testing, and am very happy with it. But, I have a question. Let's say that package A has a dependency (package B). A new version of package A is released into testing, but package B, it's dependency hasn't been updated yet. What happens in a situation like that when I try to update my computer?
View 3 Replies View RelatedI just updated my Debian testing as usual (apt-get update && apt-get dist-upgrade), and it totally screwed up Nvidia drivers. I had to revert to integrated graphic card to start Xorg.
After that, I noticed that libgl1-nvidia-glx is missing, and when I tried to install it back, it produces the following:
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libgl1-nvidia-glx : Depends: libgl1-nvidia-alternatives but it is not going to be installed
E: Broken packages
Any ideas what's going on with it?
I'm new to Debian and GNU/Linux, and I don't know when it is time to update or upgrade Debian, and how to do it in order to avoid breakages
View 4 Replies View RelatedI am using Fedora 14 and I need to install the libudev-devel package, but the following error occurs:
Error: Package: libudev-devel-161-8.fc14.i686 (updates)
Requires: udev = 161-8.fc14
This is because the actual version I have installed is:
udev-161-9.fc14.i686 (@updates-testing)
How can I downgrade to the udev-161-8.fc14.i686 package?
More details:
[root@localhost xxx]# yum install libudev-devel
Loaded plugins: langpacks, presto, refresh-packagekit
Adding en_GB to language list
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package libudev-devel.i686 0:161-8.fc14 set to be installed
--> Processing Dependency: udev = 161-8.fc14 for package: libudev-devel-161-8.fc14.i686
--> Processing Dependency: libudev = 161-8.fc14 for package: libudev-devel-161-8.fc14.i686
--> Finished Dependency Resolution
Error: Package: libudev-devel-161-8.fc14.i686 (updates)
Requires: udev = 161-8.fc14
Installed: udev-161-9.fc14.i686 (@updates-testing)
udev = 161-9.fc14
Available: udev-161-4.fc14.i686 (fedora)
udev = 161-4.fc14
Available: udev-161-8.fc14.i686 (updates)
udev = 161-8.fc14
Error: Package: libudev-devel-161-8.fc14.i686 (updates)
Requires: libudev = 161-8.fc14
Installed: libudev-161-9.fc14.i686 (@updates-testing)
libudev = 161-9.fc14
Available: libudev-161-4.fc14.i686 (fedora)
libudev = 161-4.fc14
Available: libudev-161-8.fc14.i686 (updates)
libudev = 161-8.fc14
Trying to use --skip-broken doesn't work.
Two days ago I downloaded and installed new updates after upgrading from 10.04 to 10.10. After the update I was informed I needed to restart. Once my laptop booted up again it stayed to a black screen and then filled up with error messages like something about trace call or call trace?
I had no way to get into my system but I did have some minor success starting in an old kernel. However after a while it would freeze like the graphics driver was going wrong.
Two attempt later of reinstalling 10.10 from disc after deleting the drive content and after updating it would go back to the same.
So I have now disabled updates as I haven't a clue on which one(s) is causing these problems.
I am on a HP Pavillion dv7 with nVidia graphics card and running 64amd Ubuntu.
i tried running (yum update, also yum install vlc) and i get these error
Code:
Error: Package: abrt-1.0.7-1.fc12.i686 (updates-testing)
Requires: librpm.so.0
Removing: rpm-libs-4.7.1-6.fc12.i686 (@anaconda-InstallationRepo-200911081854.i386)
[code]....
From aptitude log
[UPGRADE] acpi 1.5-1 -> 1.5-2
[UPGRADE] acpid 1:2.0.4-1 -> 1:2.0.5-1
[UPGRADE] cron 3.0pl1-110 -> 3.0pl1-111
[UPGRADE] initscripts 2.87dsf-10 -> 2.88dsf-5
[UPGRADE] libavcodec52 5:0.5.1+svn20100427-0.0 -> 5:0.5.1+svn20100512-0.1
[UPGRADE] libavformat52 5:0.5.1+svn20100427-0.0 -> 5:0.5.1+svn20100512-0.1
[UPGRADE] libavutil50 5:0.5.1+svn20100427-0.0 -> 5:0.5.1+svn20100512-0.1
[UPGRADE] libcue1 1.3.0-1 -> 1.4.0-1
[UPGRADE] libpostproc51 5:0.5.1+svn20100427-0.0 -> 5:0.5.1+svn20100512-0.1
[UPGRADE] libswscale0 5:0.5.1+svn20100427-0.0 -> 5:0.5.1+svn20100512-0.1
[UPGRADE] sysv-rc 2.87dsf-10 -> 2.88dsf-5
[UPGRADE] sysvinit 2.87dsf-10 -> 2.88dsf-5
[UPGRADE] sysvinit-utils 2.87dsf-10 -> 2.88dsf-5
[UPGRADE] xserver-xorg-video-vesa 1:2.3.0-2 -> 1:2.3.0-3
I start my box from startx but after getting these updates, x tries to start, I see a mouse and a screen for a second and then it drops out again. I'm running the latest nvidia drivers from nvidia and have tried reinstalling them and they install fine, but no go.
Only thing I can find in xorg.log is:
(II) Power Button: Close
(II) UnloadModule: "evdev"
(II) Power Button: Close
(II) UnloadModule: "evdev"
(II) Logitech Logitech BT Mini-Receiver: Close
(II) UnloadModule: "evdev"
(II) Logitech Logitech BT Mini-Receiver: Close
(II) UnloadModule: "evdev"
(II) MLK wireless combo set: Close
(II) UnloadModule: "evdev"
(II) MLK wireless combo set: Close
(II) UnloadModule: "evdev"
(II) IR-receiver inside an USB DVB receiver: Close
(II) UnloadModule: "evdev"
(II) IR-receiver inside an USB DVB receiver: Close
(II) UnloadModule: "evdev"
(II) Macintosh mouse button emulation: Close
(II) UnloadModule: "evdev"
My xorg.conf file is void of anything related to input devices and has been working a treat. So it would seem one of these updates has screwed evdev. I've tried reverting back to earlier versions, but I get the same issues. I was running squeeze with kernel 2.6.32-4-amd64 when all this happened. It was running like a trooper. I've now tried 2.6.32-5-amd64 but still no go.
1. What is the difference between files (xorg.conf and xorg.conf-vesa)
2. No matter how hard I try I can't change keyboard layout in xorg.conf-vesa (I change it in file ) but there is no actually anything changing, it starts to get annoying - for example - below goes my xorg.conf-vesa, if I uncomment and set line from
[Code]...
i can normally adjust the back light settings of my lap top by pressing fn and the up and down aarows. I am using the default xorg server without using xorgconfig in slackware, and it works perfect so far dispite this slight problem. When i do, do that key combo, (in kde) it does display the the meter of brightness, but i can't move the settings. I believe this may be an x issue, but not sure.
View 6 Replies View RelatedJust a quick question: can I safely install the 2.6.38.4 kernel in /testing and not screw up any other part of my Slackware64 13.37 installation? Should I install the kernel headers or leave the default ones since that's what glibc was compiled against? Obviously I'd need to update lilo.conf as well as run lilo itself.The reason I ask is because I'm having suspend/resume problems on my laptop (worked fine with 13.1) and I wanted to see if a kernel driver was the issue.
View 1 Replies View RelatedLast week google introduced the capability of using gmail to call other people in Canada or the US on landlines or mobile devices. This capability is free for 2010.
I gave this a try in Slackware 13.1 and it works. To do this I was browsing with Fire Fox 3.6.8 and logged into my gmail account. On the left hand side of your e-mail account window you will see a phone icon.
1. When you click on that icon you will be prompted to install the gmail phone application.
2. A download window will open asking you to download a .deb source. I downloaded it and then I used src2pkg to create a Slackware package, then installed it.
3. Re-launch Fire Fox.
4. Click on the phone application and call up people. The voice quality is quite good, I experienced little lag.
How does one install packages from testing using slackpkg or is that possible?
View 4 Replies View RelatedI had a fresh install of Slackware 13.1 up and running. I was looking to use an app which could only run on a gnome distro. So I installed gnomeslackbuild. Ran into dependency hell so I gave up the ghost and decided to reinstall.Re-install resulted in a message "Call to lnusertemp failed(temporary directories full).Had this before a different machine and sorted with another install at the time.Tried this but it keeps coming up with the same message. (4 installs later).Quote:
xset: bad font path element (#23) possible causes are:
Directory does not exist or has wrong permissions
Directory missing fonts.dir
[code]....
I am having a problem with my slackware version 12 server. I tried installing a new joomla theme from the rockettheme and its giving me the following error while loading the site.
Fatal error: Call to undefined function imagecreatefromjpeg()in /home/www/verticaltest/modules/mod_rokstories/thumbnail.inc.php on line 167
Thought it was a problem with gd library modules, but in info.php, its showing that gd is installed in the server. Pasting the result form info.php below..
If gd is installed, what should be the problem?
I'm trying to add my own personal database of quotes for the fortune app to call when i open a terminal. I was able to successfully create the data base from a text file along the lines of this thread [URL] And it works when i type :$ fortune mydatabase The problem is, when i open a terminal i dont believe fortune knows to look for the new database, and im yet to see one of my quotes appear. If anyone can point me in the right direction as to where the command is issued to run fortune when i open the terminal
View 5 Replies View RelatedIn practice I have a script that call a java program that call a linux system command. The script if I run it, from a shell functions well,so it is not a java problem. The problem come out when i put this script in a crontab schedulation. The result in this case is that java do not execute the system command. I think it depends on crontab
View 4 Replies View RelatedSorry if this was well covered here when most up-to-date Slackers moved to 13.0, but I have just jumped from 12.1 to 13.1. Generally very happy that I do not have to think about xorg.conf as I always found the structure of this conf file a tad confusing. However if I do need to (for example) change my video driver (I might for example want to try the nvidia driver from NVIDIA) or configure my touchpad - how do I do this ?
I understand that xorg.conf can still be created. If I do so, do I have to put all the stuff in that used to be there or can I just add the stuff I need to make the changes I am looking for?
I just did a clean install of 13.1 on one of my laptops and the scroll doesn't work on the synaptics touchpad. I've seen some comments about adding a file to the /etc/X11/xorg.conf.d/ directory. I don't have this directory. Is it ok to add this, or did I screw something up during the install. I did another 13.1 install about a week ago and it is also missing this directory. Is this just something in current and not in 13.1?
View 1 Replies View RelatedI have freshly installed Slackware 13 64-bit.
After messing around last time trying to compile fglrx for my ATi card, I now understand it uses a built in radeon driver.
My question is this: how do I get X to recoqnise my custom xorg.conf file? I dropped it in /etc/X11 but to no avail.
HAL does it great job - but I need my xorg.conf as I have dual monitors which HAL doesn't configure correctly (displays mirrored, not stretched).
I am new to Slackware/Linux and completed the install (Slackware 13 64-bit x86_64).Everything is running correctly.During the install I was asked if I wanted to install X-Windows and I declined.Now I want to install it.I downloaded xorg-server-1.6.3-x86_64-1.txz and installed it using slackpkg.It seemed to me to install very quickly. I see it in the list of installed packages now.What are the steps install a fresh X-Windows on Slackware if I did not pick it during install?
View 5 Replies View RelatedI bought a very beaultiful pink tv-monitor 26", model LG26LED6500 for my daughter and I also intend to enjoy it setting up in my slackware 13.37. Then I use a VGA cable and 6600GT nvidia card, but now I'm having a doubt because there aren't vertical and horizontal frequencies specs in this manual. Only:
I did a xorg.conf using a vesa driver and kde screen output was a 1024x768 - 61hz.
If I try to use a nvidia driver and xorg.conf piece above X break down. If I use any manual frequency parameters X break down too.
1)What's the difference between CRT config and tv-monitor xorg?
2)Have I use strings modeline monitor and modes screen in this situation?
I am using Slackware 13.1 and recently Xorg servercaused segmentation fault under KDE 4.4.3 twice. Here are listings from Xorg.log files
Code:
Backtrace:
0: X (xorg_backtrace+0x3b) [0x80a1e6b]
[code]....
I'm using slackware-current and I followed the instructions on how to upgrade the xorg-server from 1.7.7 to 1.8.1.
But when I tried to start X, there's the error:
Cannot find module "intel" (module requirement mismatch)
Cannot find module "vesa" (module requirement mismatch)
Cannot find module "fbdev" (module does not exist)
It looked like I have to recompile the whole X package,but I don't know how to recompile the package as well on which package to recompile.
I have the same problem as described in [URL]. Apparently the solution is to add
PHP Code:
Option "AccelMethod" "EXA" to xorg.conf.
However my system apart from this works fine without xorg.conf. Is there a way to change the AccelMethod without an xorg.conf?
I am using a AOC 19" LCD on a system with an on board Nvidia GeForce 4 MX and I cannot get X to start with 1280x1024, the max for the monitor.
Here is the sections for xorg.conf
It always defaults to 160x1200, which the monitor proclaims "Out of Range" and I have to in through Display Setings to set to 1280x1024. What do I need to put in xorg.conf to default to 1280x1024.
What a difference, using fglrx, this is like a new computer with this latest update. It runs a bit colder, flashplayer video actually goes all the way to the edge in fullscreen mode and no hardlocks yet (the kind with a blinking capslock light). Maybe fglrx isn't the only bad app in the village after all.
View 7 Replies View Related