Using Automount to mount Windows Shares

2004-02-28 Thread Graeme Smith
Out of curiosity does anyone have this combination working?

I managed to get it automounting NFS no problem, but would like to 
know if it's worth spending another few hours trying to get 
mount_smbfs to cooperate with it or if it's just a lost cause. 

Thanks,

Graeme
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Using Automount to mount Windows Shares

2004-02-28 Thread Graeme Smith
On Saturday 28 Feb 2004 10:40 am, albi wrote:
 i've got autofs + samba working on Linux (from Linux to Linux
 actually), haven't tried on FreeBSD (yet)

 documentation on the internet was not very much at all, but still
 managed to make it work :)

 i can make a small howto (later) for you if you like

I managed to get autofs successfully working on a Linux server to a 
windows machine.  Now that server is running FreeBSD and I attempted 
to get automount to do the same as I had with autofs.  I figured I 
should be able to use 'command' with mount_smbfs but neither 
Automount or mount_smbfs seems happy with that arrangement.  I can 
manually mount the Windows shares no problem.

Thanks for your offer of help though.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: System hangs when I go from X to console (nvidia)

2004-02-20 Thread Graeme Smith
 I have a similar issue with an MX440SE. From what I've read the
 likely candidate is ACPI (try disabling it with option 2 from the
 FreeBSD boot menu). Works for me. I'm using the nv driver from the
 XFree port, you might need to research further for using the
 nvidia-supplied drivers.


 Wayne

Thanks for the reply Wayne.

Option 2 on my boot menu is enable instead of disable so it looks 
like it's already disabled.  I did however try enabling it, but 
unfortunately it had no effect on the problem.

Graeme
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: System hangs when I go from X to console (nvidia)

2004-02-20 Thread Graeme Smith
On Thursday 19 Feb 2004 21:18, Karel J. Bosschaart wrote:
 I had a similar problem with an nvidia GeForce4 (Ti4200). Switching
 to console would make it hang while the letters on the console
 appeared very faint. Searching on the linux forum of the nvidia
 site I found people having the same problem as well as a
 workaround: put 'Option IgnoreDisplayDevices TV' in the
 'Screen' section of XF86Config, disabling the TV-out. 

I had read that too, except that it should go in the device section.  
However, I tried in screen section but it didn't improve matters. 
XFree86.0.log shows that the option is being used though.

a working console is much more important for me.)

I agree that a working console is far more useful than TV out.

 Hmm, if you have another machine and a network you could try to do
 a remote login and see if that works. If you succeed to login (ie.
 the machine is still alive but displays nothing on the screen), you
 might be able to bring it back killing X.

A very good point (can't believe I didn't think of it).  I opened an 
SSH session on my SGI and ran 'top'. As soon as it switched to 
console 'top', and the SSH session, froze.

 Not sure if this helps but I wish you good luck.

 Karel.

Thanks for the help Karel, it's much appreciated.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


System hangs when I go from X to console (nvidia)

2004-02-19 Thread Graeme Smith
I wonder if anybody has had this problem or can tell me what to try   
next.

I installed a Geforce 2 400 MX into my machine yesterday and actually 
succeeded in getting it to work with X after 12 hours.  All apart 
from from one annoying detail anyway.  When I leave X, either by 
ctrl+alt+bs or ctrl+alt+f[1-8] or rebooting etc. the machine becomes 
totally non responsive as soon as it tries to go into console.  I 
have to switch off and switch on (no reset button) to get it back to 
life.  I think my hard drives are going to start a petition soon to 
make me stop.

I've tried the VESA, nv and nvidia drivers for X and all seem to 
exhibit this in one form or another.  I've tried loading with and 
without the VESA driver at boot with no apparent difference. At the 
moment I'm using the nvidia drivers. 

If I had to put money on what I think is happening I would say the 
card tells the monitor go into x by y mode at z refresh but the 
monitor can't handle that mode.  However it doesn't tell the card it 
can't deal with it, but the card is waiting for the OK from the 
monitor before it tells the machine to carry on.  That's what it 
looks like from where I'm sitting anyway.

The machine is a Compaq Proliant 800 (with embedded video which I've 
turned off on motherboard)
The card is a Elsa Gladiac 511 PCI (with twin output + TV, I'm only 
interested in getting it to work with one output)
FreeBSD is 5.2 and all ports are up to date as of this morning.

Any pointers or suggestions welcomed.

Many thanks,

Graeme
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: 5.2.1 - KDELibs and total freeze-up

2004-02-12 Thread Graeme Smith
The same thing happened to me on a PII Siemens laptop last night.  At the
time I figured it was just a heat issue, but perhaps there is more to it.  I
hard booted it and just let make carry on.  I can't tell if there is a
problem running KDE 3.20 yet as it's not finished compiling...  It was
definitely kdelibs where it froze though.

KDE-3.1.4  KDE-3.20 on 5.2

Good Luck!

Graeme

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf Of Chris
 Sent: 12 February 2004 4:24 am
 To: FreeBSD Questions
 Subject: 5.2.1 - KDELibs and total freeze-up

 Well folks, 
 
   Like the subject states - is anyone having this issue 
 when portupgrading 
 KDE-3.1.4 to KDE-3.20 (kdelibs) under 5.2.1?
 
   Some stats, I'm using an AthelonXP 2100 and the mb type 
 fleas my thought 
 process at the moment.  In any event, portupgrade hums along 
 then nada - 
 total freeze. 
 
   I'm forced to hard boot the box.
 - -- 
 Best regards,
 Chris
 

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]