I am thinking of buying the ATi card. Two things I would like to know from other ATi users:
1. Does compiz-fusion work without issues?
2. Given I have an i7 920, given there is no vdpau for ATi; the i7 should be able to handle the strain of say a 1080p video with little fuss?
Yesterday I made my first Linux(Ubuntu 11.04 x64) Installation I think I have some Issues with my GPU driver.
My System Specs:
Core i5-750@stock
4GB DDR3 1333MHz
Corsair F60 SSD
[code]....
Symptoms:
-GUI feels laggy
-glxgears result way too low (2100fps)
-HD video verry laggy (1080p mkv with vlc)
I can set things up on Catalyst Control Center like VSync or scaling options, but if I go to System->System Administration->Additional Drivers (I have german version installed so it could be called slightly different) there is a listing for the FGLRX proprietary Driver and its marked as not active. (Last time I tried to activate it, it broke my bootloader somehow) So I wanted to ask what I should do (before I risk my bootloader a second time by activating the driver in that particular menu)
I have recently moved from an Nvidia 9400 GT to a ATI HD 5670 but im having a little trouble getting ubuntu to run properly with the new graphics card. I have uninstalled all of the old installed graphics drivers for my nvidia card and have tried to install all of the ati ones.
View 9 Replies View RelatedI'm trying to install the nvidia drivers but it is not working.
lspci | grep VGA
02:00.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX - nForce GPU] (rev a3)
My xorg.conf looks like this:
# xorg.conf (X.Org X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
[code]...
And after that my X is not working. And when i try sudo modprobe nvidia I get this:
FATAL: Error inserting nvidia (/lib/modules/2.6.26-2-686/nvidia/nvidia.ko): No such device
I have been learning Debian by using a virtual machine. After fine-tuning my installation procedure, I decided to copy that installation to my physical system. The hard drive already has another Linux based system installed. I plan to dual boot.After copying files I updated fstab and menu.lst.The partition scheme between the virtual and physical environments are similar, but the partitions are not mapped exactly the same.Thus the Debian system on the physical hard drive fails to boot simply because the initrd is created for the root partition location on the virtual machine. The initrd created in the virtual machine is looking for the root file system on /dev/hda1 whereas on my physical drive the new location is /dev/sda7.How can I rebuild the initrd on the physical system? I started to use the installation DVD in rescue mode, but I did not get too far.
View 6 Replies View RelatedUsing online Debian guide, installed latest nvidia-current, glx etc which seems to be 195.xx Machine boots to GUI but monitor setting menu doesnt respond nor is there an nvidia specific one. xorg.conf shows 'nvidia' driver but I suspect I am still on 'nouveau' since the synapatic package manager doesn't show an nvidia xserver-xorg-video choice.
Second question, any trailheads for using wheezy based drivers (i.e. nvidia's latest 270.xx) with squeeze?
I have been learning Debian by using a virtual machine. After fine-tuning my installation procedure, I decided to copy that installation to my physical system. The hard drive already has another Linux based system installed. I plan to dual boot.After copying files I updated fstab and menu.lst.
The partition scheme between the virtual and physical environments are similar, but the partitions are not mapped exactly the same.Thus the Debian system on the physical hard drive fails to boot. I think the initrd created in the virtual machine is looking for the root file system on /dev/hda1 whereas on my physical drive the new location is /dev/sda7.How can I rebuild the initrd on the physical system? Or how can I build an initrd in the virtual system that will function on the physical system.I started to use the installation DVD in rescue mode, but I did not get too far.
I have installed fedora 11, now i want to install touch driver for my dell 15 laptop. when i m moving cursur its moving but when i m clcking on touch pad to open anything its not opening, to open i have 2 select any file then i have to click touchpad keys.
View 2 Replies View RelatedI like the buttons on the left. I'm running 10.04 & I know how to move them. The problem is that changing themes will move them back right. OK, if the new theme has them on the right that's OK. But going back to the other theme doesn't change them back. They don't seem to be controlled by the theme, or I'm just not doing it right.
View 2 Replies View RelatedI've installed years back Debian on my laptop. Last year i did upgrade, i putted an ssd in my old laptop which works great with debian.
Now I bought a new laptop, to replace my old one. Because my new laptop doesn't have an SSD installed, i want to replace the harddrive by the SSD from my old laptop.
Now so said, so done. I replaced the hard drive easy by the ssd. Now if i boot the new laptop with the ssd installed i'm getting message from EUFI/BIOS that there is no OS installed on the ssd???
Debian is installed on it! If a place back the ssd in my old laptop, it's booting like it should, so it's working. Why is EUFI/BIOS think there is no OS installed? Debian is installed on the ssd so it should work i think?
I was looking around in Xfce4 Taskmanager to see what's taking up some memory/processor power, and I noticed when I move the cursor around in cirlces, the CPU spikes from about 5%-10% clear up to about 40%. I also have Audacious2, Chromium, and a file manager open as well.
Why is this? My system is an Eee PC with a 1.6GHz Atom processor and 2GB of DDR2 RAM.
I recently installed Debian (*former Windows user*) with xfce and I only aligned one partition. I have a 80gb SSD where I have the OS and apps. I just now installed a hard drive which I'm going to use for documents, pictures, music etc., but I haven't mounted it yet. I'd like to move /home to it's own partition on the second drive, and I'd like the desktop to be on the HDD also, but I don't really have any idea how to do this and haven't found any information about this (that's why I haven't mounted the HDD yet either). I'd like to keep the SSD purely as a drive for OS and apps so if there's anything else I should consider or if there's a better approach for this?
View 14 Replies View RelatedI'm running Debian Wheezy on a Dell XPS M1530 laptop, 64-bit.
I'm having a boot problem after moving my /usr directory out of the root partition and into its own partition.
I followed the "easy way" here: [url]
Basically, I moved the contents of /usr to a new partition -- renamed /usr in root to /oldusr -- and edited fstab and tried to reboot... but the boot process wasn't able to find the new /usr.
After using /dev/sda7 in fstab (to no success) I ran blkid to find the UUID and used that (again, to no success).
My fstab is below:
For what it's worth, grub is also looking different -- none of the debian backgrounds that were there previously remain. While it lists the same kernels to boot into the boot (as described above) fails.
I'm wondering I've read in some places that if people would like to move from a stable branch of Debian to the testing you can usually just replace the lines in sources.list with the testing release and update and then dist-upgrade. Is this true...and if so is it safe?
View 1 Replies View RelatedMy Debian Lenny box has two hard drives: a smaller one, upon which I installed the system and a 500GB drive which, during installation, I assigned for mounting as the "/home" directory. A few days ago, the smaller (system) hard drive crashed. Although fsck was able to make the drive mountable again, many system files (esp. things like inittab) were lost.
Since the machine, itself, had actually been pretty old when I first installed Debian (Etch, originally), I am going to be replacing it with a new system and I have a few questions about getting this all done.
First of all, the old computer was a Pentium 4 and the new one is a Dual-core, 64-bit Pentium (E6600) with 4GB RAM and a 500GB SATA drive. I'd like to install 64-bit Debian Squeeze onto that drive and, since I've never used the 64-bit Debian before, would like to know if there are any pitfalls or caveats - especially any dire reasons I should stick with 32 bits, instead.
Next, I would like to keep the other 500GB (IDE) drive mounted on "/home" so that my things would be where they already were on the old system - especially files relating to Iceweasel and Icedove. Of course, there are no binaries on that drive, since I had all of that on the drive that crashed, but are there any other things I must take into consideration? Also, what would be the best way to make that drive "/home" during the new installation without wiping it out, but having it ready for when I create the users so I can point them to their appropriate directories?
Finally, since the old computer had been an Etch system that had been upgraded to Lenny and since I would be installing Squeeze (and, likely, the 64-bit Squeeze, at that) onto the new system, would there be any problems with the above scenario, considering the potential of older configuration files, etc. on the old "/home" drive?
My subject line says, "Updating while moving to new machine," but these really may not be "update" questions, per se. Then again, the presence of that old hard drive does introduce some update-like elements into the equation, and that is why I am asking these questions.
On my laptop, squeeze has /, /boot, /usr, /home and I think /tmp /var on separate partitions. I want more space for apps and to not have to be so frugal with /home. Earlier this week I shrank sda1, freeing up 40 GB. I wanted to start moving the squeeze partitions, but GParted logically enough denied it since they were mounted, duh. I'm glad for that, because I was getting overeager and hadn't made even a full system backup.
This is one of those situations where choice, while good, makes it hard to get started. I wouldn't mind using dump, but doesn't it inefficiently copy the whole partition regardless of empty space? I figure tar could do as well, but is it a problem that it doesn't preserve all the meta info? As a starting point, I'd like to have an "quick" and safe way to make sure that if something happens while moving partitions, I can do a restore. I can progress to more optimal solutions later on, like semi- or fully automated incremental backup.
So what is a sure-fire way to do this while preserving all info? Should I stick with something like clonezilla, can I manage it from within Debian (CLI, ready-made script, GUI), is there a still better way?
I have an older system that has been running testing for about 4 years. Originally I was running testing for several packages that were not yet available in stable. However, now that this system has a more crucial role in the network I have considered moving it to stable in hopes that it I can gain some insurance on it's uptime. It is important to note that I have never had a problem with the testing distribution and would be quite content to continue running it; I do want to know my options though.
I have not yet updated the system since the stable release of squeeze, I am considering to change my sources from testing to stable and just let apt take care of the rest. Anyone have any experience with such a thing? After searching Google I have found some solutions to force a downgrade, but that is really not what needs to be done here. I suppose I should have switched my sources to squeeze some time ago and this probably would have worked itself out.
A similar question is what happens a couple of years from now when another release happens. Have you had good luck updating from old stable to stable? I've run testing on several machines now for several years and have went through freezes and dist-upgrades several times with no major problems at all. Will I see the same stability if I move to the stable distribution?
I've been thinking about moving from Gnome to Xfce for atleast something more lightweight and etc. But I do not know of any good ways to completely remove Gnome without issues and etc. removing all of Gnome? And does Debian Squeeze have Xfce 4.8?
View 14 Replies View RelatedI installed debian 8 on a 16 GB usb drive using this guide. I used a debian 8.2 64-bit image with mate. If I were to get a larger usb drive, would I be able to transfer everything from the 16GB drive to it? How?
View 1 Replies View RelatedI ping my router. If I keep my mouse moving (or i'm typing) I get a 5ms ping.If I stop typing/moving my mouse, it times out.
- I disabled NetworkManager for the inteface eth0 but it doesn't solve the problem.
- I'm having the same problem using a Ubuntu 15.01 bootable image
- I'm having the same problem usign an Ethernet PCI Adapter
- I'm having the same problem usign a Wifi PCI Adapter
lsb_release -da
Code: Select allDistributor ID:Â Â Debian
Description:Â Â Debian GNU/Linux testing (stretch)
Release:Â Â testing
Codename:Â Â stretch
[code]....
I want to move my old system to a new drive. Currently I have Debian installed with following configuration:
I have an encrypted system where everything is encrypted except /boot. Currently I've /boot and / installed on a 16 GB mSata SSD and /home on a regulard HDD. I've got a 500GB SSD for Christmas and want to move the whole system to the new SSD.
I just wanted to ask if I've got the process required to to this down:
1. backup root-directory (/) without and /boot /home using tar keeping file-permissions and owners to ext. hard drive
2. backup /boot and /home separately using the same method
2. replace HDD with SSD remove mSATA SDD.
3. boot via live-usb
4. create appropriate volume groups, partitions, setup encryption etc.
5. extract backups to appropriate partitions
6. chroot to old /.
7. edit fstab
8. reinstall grub
9. create new init ram img.
I'm pretty sure I've got steps 1.-6. down but I'm very shaky on what to do next.
My mouse cursor is disappearing when it's not moving, or when I scroll a window with the middle wheel... Then when I move the mouse, the cursor is appearing!
This has started after few things...:
- old video card has died (ati hd4850)
- integrated motherboard video card used (ati hd4250) after solving the black screen (xorg, ati drivers... you know :s )
- since many weeks, computer has not been used before I've plugged a hd7970, solved 1 more time the black screen (.....)
And after many updates + this new video card = cursor is kidding :p
I've tried to change my cursor settings in the GUI config, nothing better.
MATE + XFCE
Problem solved by renaming all cursor files...
Im totally newbie is *nix OS (including debian) but more than pro in Win, so treat me with understanding,
TECH SPEC:
Debian 6
Gnome 2.30.2
PROBLEM DESCRIPTION: Mouse still working well during random period of time (it may be less then one minute and more then few hour's from boot up) then instantly stop moving (cursor are freeze) but it still active. Obviously it is not associated with any program, coz it happens even on log-on screen.
One thing make this case unusual - im using Logitech Wireless Desktop MK710 keyboard + mice set. It mean there is only one receiver for both devices. You guessed it, keyboard continues to operate normally after mouse fail! Absolutely normally! Even more, if i connect new wired usb mouse at this time, it will be work well, but not for log... after random period of time it goes freeze too =/ KEYBOARD STILL WORKING
ive played around with cpusets and now have some processes that cant be moved to the main group /dev/cgroup/tasks. echo pidinquestion >/dev/cgroup/tasks results in:
bash: echo: write error: Invalid argument. how can i move these tasks? or remove the process group alltogether, rm -r is not working. permission denied?
I got a rather big problem since an attempt to upgrade.My debian version is 8.0.I upgraded when apt proposed the change. I did that in two steps, with apt-get upgrade and then apt-get dist-upgrade, with the installation of a new kernel. I moved from 3.2.0-4-686-pae to 3.16.0-4-686-pae.Since the upgrade, I can't boot my system any longer.During the boot sequence, this message appears with a countdown (it's copied by hand) :
Code: Select all(1 of 4) a start job is running for dev-disk-byX2du
At the end of the countdown, the boot sequence starts again, and ends up on an invite to log in as root in rescue mode. I can't connect (maybe due to some azerty/qwerty issue, I got a French keyboard. I tried to type in "qwerty mode", with no success (the password is not prompted)).I can connect with the 3.2 kernel however, selecting it form the grub interface. I can't log in in rescue mode either, but with this kernel the boot sequence goes on and I can log as a regular user or as root, at the end of the boot sequence. There is no X, but the system seems to work.What could I do to make the system boot properly with the new kernel, or to go back to the 3.2 version ?
I am running Vmware server 2.02 on a Windows-7 host. Also I have installed Debian Lenny as a guest on top of the vmware server.
I have installed Vmwaretools, the screen resolution is fine but the mouse pointer movement isn't smoothly. Side effect: When I move the pointer from the Windows-7 host into the debian desktop windows, the pointer stops at the border for a while and then jumps at ones to the middle of the window.
I have the same problem with squeeze-32-kde-4, lenny-kde-64, lenny-gnome-64. I do not have this problem with Suse linux 32-kde4. When I move the pointer over the windows border, the chape of the pointer changes ( windows > linux ) and the movement is fluently without any interuption.
My root filesystems flooded so I'm trying to move it to another (bigger) partition but I'm not sure of the best method. I just tried to use "dd if=/dev/sda1 of=/dev/sda6" to copy it but all that did was give me a brand new partition with no freespace available presumably because the filesystem is smaller than the partition. Is it possible to make the filesystem bigger?
View 8 Replies View RelatedMy UC-LOGIC Maner 850 tablet can't fully functional under fresh debian testing "Jessie".
Code: Select allLinux debrain2 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt9-2 (2015-04-13) x86_64 GNU/Linux
lsusb reports:
Code: Select allBus 002 Device 004: ID 5543:0062 UC-Logic Technology Corp.
dmesg reports:
Code: Select all[66297.932082] usb 2-6: new full-speed USB device number 4 using ohci-pci
[66298.145070] usb 2-6: New USB device found, idVendor=5543, idProduct=0062
[66298.145083] usb 2-6: New USB device strings: Mfr=5, Product=6, SerialNumber=0
[66298.145088] usb 2-6: Product: Maner850
[66298.145093] usb 2-6: Manufacturer: UC-LOGIC
[CODE].....
It looks it should functional well, but... Pen make responses to click (push down the tip), but no luck at move the pen(the pointer won't move, mouse working smoothly)
I have been googled for hours, people occasionly have 'pen moves but no response at click' or even not detected by kernel ...
Because I am using one of the new WD disks I am trying to aling my root partition with the real sectors, as described here: [url]
So I copied all files to a temp location, deleted my partition (/dev/sda3), recreated it a few cylinders later (same name) and copied the files to the newly created partition. I updated UUIDs in grub's configuration as suggested in this thread:[url]
But now it fails to boot with the following error:
Code:
I checked the filesystem on this partition and its fine. I tried to recreate the initramfs from Knoppix:
Code:
But it didn't change anything.
How can I either fix it or install a different kernel on this drive so I could boot into it and re-install my default kernels?
I am running Debian Squeeze with 2.6.32-5 amd64 kernel with GCC 4.3.5 (the same one used to build the kernel) installed. I have a nVidia GTX 470. I'm trying to install the latest nVidia drivers (260. ...). I've never installed noveau or any other open source nVidia driver. Here's what I've been doing:-Change the "Driver "nvidia"" line in /etc/X11/xorg.conf to "Driver "vesa""-Restart system in single user mode as root, no services running-cd to the directory with nvidia-Linux-x86_64-... .run (what I'll call nvidia.run)-enter "sh nvidia.run --uninstall"-enter "CC="/usr/bin/gcc-4.3" && sh nvidia.run"It starts up and it compiles the kernel 100%. Then it says this:
ERROR: Unable to load the kernel module 'nvidia.ko'. This happens most
frequently when this kernel module was built against the wrong or
improperly configured kernel sources, with a version of gcc that differs
[code]....