Re: Mount/fstab problem
I found it!My issue was solved by placing the chroot directories on the root partition. Sometime back, I moved them from /var into /usr/local (which is on another partition) due to some space issues --- I must have not noticed the effect this had on proc right away. If I understand things correctly, debian tries to mount proc in my chroot before the partition with the chroot has been mounted. That's why it helps to have the chroot on the root partition, as it gets mounted first.Sorry to have bothered people about this,landhajLand Haj <[EMAIL PROTECTED]> wrote: Yes, $chroot/etc/fstab has next to nothing in it, but if you check the regular /etc/fstab that I attached to my first mail, you will see that proc is listed just as you suggest. But it still doesn't get mounted as $chroot/proc unless I manually do a 'mount -a' after boot. This is really weird./landhajLennart Sorensen <[EMAIL PROTECTED]> wrote: On Mon, Mar 20, 2006 at 05:33:22AM -0800, Land Haj wrote:> Sorry, I forgot to specify that it is the proc file system in the 32 bit chroot that doesn't get mounted.> > /landhaj> > Land Haj <[EMAIL PROTECTED]> wrote: A few days ago I tried out gnome on my debian sid amd64 installation. For some reason, everytime I started gnome, nautilus would pop up with a little window where it demonstrated the files on a backup partition. This partition is clearly set to noauto in fstab, but I couldn't stop gnome from mounting it.> > I decided kde worked better for me, and uninstalled gnome. The backup partition doesn't get mounted when I enter the desktop anymore, but the funny thing is that now the /proc file system is not being mounted at boot (like it did before), and hence ooffice gives me warning and sound doesn't work in wine. I have followed the instructions in the AMD 64 howto to the letter, and had not altered fstab when the problems occured. Both these issues go away when if I su to root and do mount -a, which shows fstab is fine, doesn't it?> > Anyone know what's going on? Is my problem some kind of rest from the gnome installation, or is nautilus behaviour and the present issues just a coincident?What is in your /etc/fstab (not in the chroot, the one in the chroot hasvery little purpose unless you want to have some mounts available formanual use while in the chroot).Something like this should work fine:proc /proc proc defaults 0 0proc /chroot32/proc proc defaults 0 0Len Sorensen-- To UNSUBSCRIBE, email to [EMAIL PROTECTED]with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] Yahoo! Mail Bring photos to life! New PhotoMail makes sharing a breeze. Yahoo! Mail Bring photos to life! New PhotoMail makes sharing a breeze.
Re: Mount/fstab problem
Yes, $chroot/etc/fstab has next to nothing in it, but if you check the regular /etc/fstab that I attached to my first mail, you will see that proc is listed just as you suggest. But it still doesn't get mounted as $chroot/proc unless I manually do a 'mount -a' after boot. This is really weird./landhajLennart Sorensen <[EMAIL PROTECTED]> wrote: On Mon, Mar 20, 2006 at 05:33:22AM -0800, Land Haj wrote:> Sorry, I forgot to specify that it is the proc file system in the 32 bit chroot that doesn't get mounted.> > /landhaj> > Land Haj <[EMAIL PROTECTED]> wrote: A few days ago I tried out gnome on my debian sid amd64 installation. For some reason, everytime I started gnome, nautilus would pop up with a little window where it demonstrated the files on a backup partition. This partition is clearly set to noauto in fstab, but I couldn't stop gnome from mounting it.> > I decided kde worked better for me, and uninstalled gnome. The backup partition doesn't get mounted when I enter the desktop anymore, but the funny thing is that now the /proc file system is not being mounted at boot (like it did before), and hence ooffice gives me warning and sound doesn't work in wine. I have followed the instructions in the AMD 64 howto to the letter, and had not altered fstab when the problems occured. Both these issues go away when if I su to root and do mount -a, which shows fstab is fine, doesn't it?> > Anyone know what's going on? Is my problem some kind of rest from the gnome installation, or is nautilus behaviour and the present issues just a coincident?What is in your /etc/fstab (not in the chroot, the one in the chroot hasvery little purpose unless you want to have some mounts available formanual use while in the chroot).Something like this should work fine:proc /proc proc defaults 0 0proc /chroot32/proc proc defaults 0 0Len Sorensen-- To UNSUBSCRIBE, email to [EMAIL PROTECTED]with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] Yahoo! Mail Bring photos to life! New PhotoMail makes sharing a breeze.
Re: Mount/fstab problem
Sorry, I forgot to specify that it is the proc file system in the 32 bit chroot that doesn't get mounted./landhajLand Haj <[EMAIL PROTECTED]> wrote: A few days ago I tried out gnome on my debian sid amd64 installation. For some reason, everytime I started gnome, nautilus would pop up with a little window where it demonstrated the files on a backup partition. This partition is clearly set to noauto in fstab, but I couldn't stop gnome from mounting it.I decided kde worked better for me, and uninstalled gnome. The backup partition doesn't get mounted when I enter the desktop anymore, but the funny thing is that now the /proc file system is not being mounted at boot (like it did before), and hence ooffice gives me warning and sound doesn't work in wine. I have followed the instructions in the AMD 64 howto to the letter, and had not altered fstab when the problems occured. Both these issues go away when if I su to root and do mount -a, which shows fstab is fine, doesn't it?Anyone know what's going on? Is my problem some kind of rest from the gnome installation, or is nautilus behaviour and the present issues just a coincident?Please help,Land HajYahoo! Mail Use Photomail to share photos without annoying attachments. Yahoo! Mail Use Photomail to share photos without annoying attachments.
Mount/fstab problem
A few days ago I tried out gnome on my debian sid amd64 installation. For some reason, everytime I started gnome, nautilus would pop up with a little window where it demonstrated the files on a backup partition. This partition is clearly set to noauto in fstab, but I couldn't stop gnome from mounting it.I decided kde worked better for me, and uninstalled gnome. The backup partition doesn't get mounted when I enter the desktop anymore, but the funny thing is that now the /proc file system is not being mounted at boot (like it did before), and hence ooffice gives me warning and sound doesn't work in wine. I have followed the instructions in the AMD 64 howto to the letter, and had not altered fstab when the problems occured. Both these issues go away when if I su to root and do mount -a, which shows fstab is fine, doesn't it?Anyone know what's going on? Is my problem some kind of rest from the gnome installation, or is nautilus behaviour and the present issues just a coincident?Please help,Land Haj Yahoo! Mail Use Photomail to share photos without annoying attachments. fstab Description: 1159799512-fstab
Re: Nvidia driver bypasses xorg.conf settings
Thank you, your mail made me check the changelog for nvidia-glx more carefully. I did this sloppily the first time as I never changed driver or kernel version and it worked before.Adding 'Option "UseEdidFreqs" "no" ' to the device section in xorg.conf fixed my problem.This information is in the NVIDIA_Changelog in /usr/share/doc/nvidia-glx/ . It says that UseEdidFreqs is now set to "on" by default. I'm sorry to have bothered people with stuff that was actually documented :/.Thanks for your help!Lennart Sorensen <[EMAIL PROTECTED]> wrote: On Thu, Feb 16, 2006 at 11:08:16AM -0800, Land Haj wrote:> The monitor instructions says to use 60 Hz instead of 75Hz at the highest resolution (1280x1024), and it is noticeably more comfortable for the eyes. And yes, it is a LCD screen, and yes, I guess it's not the most expensive screen around. But it's new and I am very happy with it at 60Hz.Well for LCD it does make sense yes. They don't flicker in the firstplace at any speed.> I had the nvidia drivers working just fine with the older kernel, with 60 Hz specified in xorg.conf. Changing the xorg.conf entry from '60' to '60-60' doesn't help when I try it. Switching back to the older kernel doesn't help either. I don't think there's a problem with anything but the nvidia driver, since:The nvidia driver has a tendancy to take the DDC data as above all. TheREADME file for the nvidia driver in /usr/share/doc/nvidia-glx/ shouldsay how you can force it to ignore DDC data.> a) Everything worked fine before (i e I used nvidia drivers and had 60Hz)> b) Swithing from nvidia drivers to the nv driver gives me 60 Hz.> > I don't think I misconfigured xorg.conf, since I had it working with the older kernel + nvidia and didn't change anything in it.Probably upgraded nvidia driver changed things.Len Sorensen-- To UNSUBSCRIBE, email to [EMAIL PROTECTED]with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] Brings words and photos together (easily) with PhotoMail - it's free and works with Yahoo! Mail.
Re: Nvidia driver bypasses xorg.conf settings
Lennart Sorensen <[EMAIL PROTECTED]> wrote:Just how exactly can 60hz ever be nicer on the eyes? Well unless it isan LCD in which case it doesn't matter. The lower the refresh the moreflickering you get. That is why the highest possible refresh is alwayspicked. You can enter your maximum for your monitor as 60-60 if youwant or something like that to limit it if you actually think that is animprovement. Some crappy monitors do have problems handling higherfrequencies but the problem is not that the refresh rate is higher, theproblem is crappy electronics in the monitor not able to handle thebetter signal.Len SorensenThe monitor instructions says to use 60 Hz instead of 75Hz at the highest resolution (1280x1024), and it is noticeably more comfortable for the eyes. And yes, it is a LCD screen, and yes, I guess it's not the most expensive screen around. But it's new and I am very happy with it at 60Hz.I had the nvidia drivers working just fine with the older kernel, with 60 Hz specified in xorg.conf. Changing the xorg.conf entry from '60' to '60-60' doesn't help when I try it. Switching back to the older kernel doesn't help either. I don't think there's a problem with anything but the nvidia driver, since:a) Everything worked fine before (i e I used nvidia drivers and had 60Hz)b) Swithing from nvidia drivers to the nv driver gives me 60 Hz.I don't think I misconfigured xorg.conf, since I had it working with the older kernel + nvidia and didn't change anything in it./landhaj Yahoo! Autos. Looking for a sweet ride? Get pricing, reviews, & more on new and used cars.
Nvidia driver bypasses xorg.conf settings
For some reason, using the nvidia driver makes xorg use the wrong vertical refresh rate. My monitor can do 75 Hz at full resolution, but 60 Hz is recommended and much more comfortable for the eyes. All was fine until I* built a custom kernel by copying the config for a stock kernel and adding preemtibel option, then make-kpkg* reboot* m-a prepare* m-a auto-install nvidia* startxWith any kernel (not just the one I built) and the nvidia drivers, my vertrefresh is at 75Hz, despite the fact that xorg.conf says it shall be 60Hz. Switching to the nv driver fixes it.I'm using kernel 2.6.15 as downloaded from a debian mirror and rdonalds nvidia kernel source 1.0-8178-1.There gotta be some file somewhere overriding my xorg.conf, but it's near impossible searching for this problem on the net, since I get a zillion hits using nvidia, vertrefreh, xorg.conf etc.Please help!/landhaj Yahoo! Mail Use Photomail to share photos without annoying attachments.
