I just installed Squeeze on a 4 disk system, each disk set up identically with 4 partitions, with the last partition of each disk used for a raid 5 array. I used the squeeze installer, and chose the 'manual' partition option for this setup.
After installation, fdisk reports the ending cylinder number of each of the 4 disks as one more than the total number of cylinders for the disk. I've never seen this before. In the past when I've used fdisk to manually partition disks, the final cylinder number was always equal to the total number of cylinders.
The disk has 60801 cylinders, and the 'End" cylinder number for /dev/sdd4 is reported as 60802. I would have expected it to be 60801. Is this a bug or problem? It's working OK, but I don't know if it will cause instability in the future.
is there a common reason why modules get mismatched with the running kernel version?why do I always get that uneasy feeling like I'm headed in the wrong direction?
how to install Dropbox for Debian Squeeze from source.Please read everything before you begin. I prepared it as I installed Dropbox for my own system. Please Note: I use sudo, you may have to use root or 'su' from the command line. If you don't know the difference between sudo and su, then you shouldn't try this until you know. At the time I did this, the lastest dropbox version was 0.6.7.
The VirtualBox website have a 64 bit deb for installation available for AMD64 Lenny but not for Squeeze. Is it okay to install the Lenny package on Squeeze or would this cause a problem?
I installed Debian Squeeze (choosing no when prompted to add support for non-free or contrib sources) and noticed that the fan of my Nvidia 9600 GT video card is constantly running at full speed. I thought this meant that the default driver is not properly working. I would like to configure my system so that the video card fan is not being pushed so hard.
I downloaded the latest Nvidia (propietary) driver, stopped gdm3, and ran the driver installer. The installer failed because it said the Nouveau kernel driver was currently in use and incompatible with the Nvidia driver. I chose not to allow the installer to update my modprobe configuration directory. nvidia-installer log file '/var/log/nvidia-installer.log'
[Code]...
It looks at though the xorg.conf.new file has the nv driver in use, but the Nvidia installer says the Nouveau driver is being used. I ran a line in terminal (i forget the exact line) to test the xorg.conf.new file in the /root/ directory. The result was No Screens Found.
Next, I tried to remove the xserver-xorg-video-nouveau package using aptitude, but it displayed a message indicating that xserver-xorg-video-all depends on it. I decided not to remove the xserver-xorg-nouveau package. Any suggestions on how to proceed in order to configure X with a free driver (nv, vesa, or nouveau) so that the video card is handled properly?
Device Boot Start End Sectors Size Id Type /dev/sdb1 16065 584830259 584814195 278.9G f W95 Ext'd (LBA) /dev/sdb5 16128 584830259 584814132 278.9G 7 HPFS/NTFS/exFAT
I have 2 hard drives both are 278.9GB in a mirror raid 1. Why does 2 partitions show up? Are they referring to each physical hard drive? I want to believe that this is the same partition and not two different physical hard drives since both are in the same 'start' and 'end' range. Is that correct?
I am running Debian 3.2.0-0.bpo.2-amd64 on hyper-v, my / volume ran out of space and is sitting at 100%, I have extended the disk size on hyper-v, however when I go to Fdisk I see duplicates of each disk.
I have total of 2 vhds on the vm, so I see 4 disks under fdisk. Here is the output of fdisk
I have never seen this one before (see below) - note how /dev/sda1 is mounted from the first disk listed by fdisk, but /dev/sda2 comes from the second disk; what is going on here? This is what I did: I installed the latest debian "Testing", which went well - it found the disks in the order show by fdisk -l here. When it booted up after installation, it failed because it couldn't find /, which I repaired by editing the grub menu (I told it to start from the other disk), and it came up. But now I had to mount /u01 by hand from /dev/sda1; strange. I suppose I could just go and change the physical disks around, but I'd like to understand this. Any ideas?
so I just installed Squeeze Alpha1 amd64, dual boot with MS Vista using Grub. Everything seemed fine, but I'm apparently missing about 40GB of space. It should be set up as so:
101GB NTFS /dev/sda1 - Vista 12GB NTFS /dev/sda2 - HP Recovery 45GB ext3 /dev/sda3 - / Debian squeeze
Our Canon MX340 printer is WiFi connected using an IP address. This works well except that whenever the printer is turned off (for any reason) it chooses another IP next time it is turned on. As near as I can tell, it has two IP numbers: 192.168.1.64 and 192.168.1.65 Is it possible to enter both in the CUPS configuration so that CUPS will find the printer whichever number it is using?
I have a set of vm's with stable, testing, and sid to keep track of how things are going. When I did an apt-get dist-upgrade with squeeze last week, things seemed to OK (350 package updates) until the end. It didn't seem to like and / or was confused by a kernel dependency.
I am not too concerned yet. Because these are in vm's, I do a snapshot before any significant change. I can futz around with impunity because I have that backup.
I re-booted, and tried the apt-get dist-upgrade again with same results. I think I also tried apt-get -f install.
So I reverted to the snapshot, and will simply try again in the future. I recall that with lenny as testing, the font-desktop was really screwed up for about a period of 6 weeks.
However, just in case someone else runs into this:
1) a re-boot worked, but the failure of apt-get made me nervous enough to revert.
2) waiting for corrections has seemed to work in the past (with a single exception with a 4-disk SCSI software RAID10 update that failed to re-boot lenny successfully after what seemed to be a minor update -- that was on a real system, not a vm. I haven't gotten back to look at that.)
I recently just installed Squeeze on an ia64 system and was having some troubles with running VNC.I get the following error, more specifically for some reason I get a malloc - memory corruption error:
Xtightvnc(9165): unaligned access to 0x60000000001ea06c, ip=0x4000000000268280 Xtightvnc(9165): unaligned access to 0x60000000001ea074, ip=0x4000000000268280 Xtightvnc(9165): unaligned access to 0x60000000001ea07c, ip=0x4000000000268280 Xtightvnc(9165): unaligned access to 0x60000000001ea084, ip=0x4000000000268280
[code]...
After display all the code above, it just stops. The port 5901 is still closed - if it runs properly, would it open automatically?Is there something that is incompatible? Or am I missing some system configuration component?
I installed Firestarter firewall on debian Squeeze.Now i note there is a gui available in System->Administration which apparently does not need to be running all the time - its not set up to start on boot.When I boot I notice the boot message has a line saying "Starting Firestarter firewall .... failed"When I am logged in and type "/etc/init.d/firestarter status" as the Firestarter FAQs say, I get"Firestarter is running... ... (warning)"I can run the gui manually and still same message.
When I activate Tor in Iceweasel, it forbids me access to the internet completely. Even attempting Google results in "Iceweasel is configured to use proxy server that is refusing connection".
I have seen this in Lenny, too - it was caused by activating Tor without having installed privoxy. I installed privoxy and everything was okay. In Squeeze, Tor is using polipo. Polipo is installed and running. I have not played with settings of polipo or Tor, the configuration is the same as it was after installation.
What can be wrong? I am a rather an user than a networking guru. I am connected to internet by means of DHCP, no local lans, no special routings, no additional proxies. I have already tired to reinstall polipo.
Just installed squeeze on a new laptop(had been runny Lenny on my older one with no issues, but no sound or wireless on the new one).I decided to install the ATI drive for my Radeon Mobility 4500(or some close revision) because the fan is constantly running and based on some other postings, it seems that it could be the graphics card causing it.Downloaded the driver from ATI's site and it seemed to install fine but when starting X.
When I try to downgrade from sid squeeze I don't get GDM running just a login promt after a reboot.Have also reinstalled nvidia driver but still only login promt.I did aptitude update and aptitude full-upgrade after changing sources.list from sid to squeeze.
Got a problem mounting my Windows partition in Squeeze. It keeps refusing to mount it for me in Dolphin. I am a member of the disk and fuse groups, /dev/fuse is owned by root:fuse, and /sbin/mount.ntfs points to /sbin/mount.ntfs-3g, which in turn points to the ntfs-3g executable. I kind of need this ASAP. I am supposed to be finishing with this machine in 35min, and I am dead in the water without the ability to copy some files from the Squeeze ext4 partition over.
I installed Debian Squeeze from a net install to a raid 1 array. I have been having a lot of troubles related to being able to write to one or more of the mounted drives - even touch gives me errors.
The most interesting line from dmesg is:
Here is the full output from dmesg:
I found a thread that indicated that this bug was fixed in the next kernel version: 2.6.32-6. I am willing to upgrade the kernel to get rid of my problems. Is a squeeze kernel at 2.6.32-6 or higher available? If so, where? I have not compiled my own kernel, and am not very interested in getting into that.
I use my laptop at the college, and I've to suspend him frequently. So, I've decided to install the package pm-utils, to hibernate my PC, instead of power off it. When I try to do "# pm-hibernate", a tty appear, and this error is displayed :
[3506.405310] pm_op(): usb_dev_suspend+0x0/0xa [usbcore] returns -2 [3506.405310] PM: Device usb1 failed to freeze: error -2 This is the result in pm-suspend.log : Initial commandline parameters:
I have upgraded my server to Debian 6.0 Squeeze but it looks like some of my sites are not compatible with PHP 5.3.x so I would like to revert to previous 5.2.6 version.So my question is what to do?a) Remove PHP 5.3.x from system via apt-get and install my old 5.2.6 from old archives at /var/cache/apt/archivesorb) just try to update from archives PHP to 5.2.6?
-rw-r--r--. 1 root root 2413316 May 11 2008 libapache2-mod-php5_5.2.0-8+etch11_i386.deb -rw-r--r--. 1 root root 2413290 Oct 6 2008 libapache2-
As a long time user of some other distributions I decided to switch to Debian and installed 6.0 from amd64 kde cd image.Upon logging to KDE I discovered thatant locate knetworkmanager anywhere,it doesnt autostart and I could not find it anywhere else.I am connecting through a wireless network to the Internet so I cant connect through the Ethernet to download it through apt-get for example,if it is not installed by default.lly confused,knetworkmanager is standard tool in KDE but I cant find it in Debian 6.0
A couple days ago I installed Debian Lenny (netinst) to my friend's laptop, a IBM Thinkpad T23. Got a black screen after gdm loaded and the laptop seemed frozen. Decided to upgrade to squeeze. I edited the apt sources file and changed all the instances of lenny to squeeze, and then upgraded.Had the same display problem, but found a web site that suggested disabling acpi. So I did that, got the sound working, (needed cs46xx firmware), and all seems to be running fine.I get some weird udev messages at boot time, but I have a feeling that's due to how I upgraded. I can't copy and paste since the messages aren't in my system log. If anybody wants more information about it, I can supply it. pgrep shows two instances of udev running so it appears the messages are only warnings.When upgrading to squeeze, I used tds.net debian mirror links. Earlier today I switched to Debian's official US repo URLs and had to upgrade about 250 packages after reloading package data.
Now, when I click on System -> Administration -> Time and Date.After a couple seconds I get a dialog box that says "The configuration data could not be loaded" in bold black letters. Underneath that in smaller letters, "You are not allowed to access the system configuration" I receive that same error when accessing "services" and "users and groups."But I can access the synaptic package manager and update manager from the administration submenu.
I've been testing Squeeze to determine whether KDE4 is finally suitable for my primary machine. Everything seems to be working fine except for detection of IDE devices. My CD/DVD drive no longer automounts and the reason seems to be that no device is being created. My Lenny system detects the drive as /dev/hda, but no such device exists in Squeeze. During boot, Squeeze appears to detect the drive as /dev/sr0 (according to dmesg), but in fact that device does not exist either.I'm actually running the Lenny kernel, as I am unable to compile my Ralink wireless driver (rt2860sta) using the Squeeze kernel. Also, for inquiring minds, I use removable HDD drive bays on my systems to simplify testing.
I have been trying to build a Debian-live-version for some time using live-helper. It works fine if I choose lenny as distribution. With sid I always get into trouble.Sometimes live-helper does't find any aufs-modules but it stops looking for them if I keep the options as simple as above.What is the problem of live-helper's to build on sid or squeeze (which I have met similar troubles with)?
Alright, first Squeeze wouldn't create an initial RAM disk even with "--initrd" specified. Now I don't need one and it's creating one for me even though I don't want one! How do I stop this? I'm beginning to feel like I am using Windows in the sense that it's doing things on its own. Don't make me a RAM disk unless I say so!
I just noticed that I had a sid line on my sources.list, at the end of all squeeze lines, and I've been updating more or less regularly. Does the ordering imply some sort of "preference", so that the first lines are preferred over the subsequent ones, or is it all about the latest version?After removing that line, and taking a look at my installed packages with synaptic, all the "latest versions" of the packages seem to be the ones that are already installed, and I click on properties, and there are no older versions available, only "##.##-### (testing)". Emphasis on "testing", rather than "sid" or "unstable". Of course I didn't check all of them, but about a dozen, and none deviated from that pattern. However, I went to double check on the web pages about the packages, and it seems that many of the squeeze's packages are at the same version of sid. I couldn't yet find one that is not.perhaps the sole fact that the sid line was on sources.list is enough to know that something happened -- as I don't recall having ever set up those configuration files about preferred sources/pins or however it's called), and suggestions on how to proceed? My hunch would be to just downgrade things gradually as they eventually fail (as I did with geeqie, which is why I suspect that there is some mess), but leave everything alone. Not try to fix what is not quite broken. And if it fails too often, go full-blown sid.
I don't print much, but tonight needed to print and found that none of the printers were listed in Okular or Openoffice, then when I tried to open Cups Administration http://localhost:631/ I got the error message Connection to Server Refused
1) old a1300 laptop: P3 800, 256 MiB RAM, HDD, PC-CARD NIC. from lspci: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10) with debian (i386), previously lenny, now squeeze. running as server.
[Code]...
Smaller files seem to transfer faster, but I have no idea why. I've checked with ethtool that both NICs are running at 1000Mb/s, and both are connected to the same Gigabit switch. The HDD in the laptop had previously provided (nfs) transfer speeds of 12-13 MiB/s. The options in fstab on the client are what I've changed them to since, while trying to fix the problem. Can't remember exactly what they were, but rsize, wsize and nfsvers are some I put there trying to fix it.
I had considered buying a new, faster HDD for the laptop, but that is certainly out of the question until this is resolved. Edit: Is this the right place to ask about this? I did wonder if the 'General Questions' category was a better fit.
