Kev: How did you build that kernel? I tried building one for Ubuntu, but
end up with the error message:
II: Checking for missing symbols in new ABI...
MISS : sata_pmp_error_handler
MISS : sata_pmp_qc_defer_cmd_switch
MISS : sata_pmp_port_ops
found 3 missing symbols
EE: Symbols
I just installed the new kernel (2.6.27-9-generic x86_64), but this fix
doesn't seem to have made it in there yet. nodfs seems to be an unknown
mount option for cifs.
Any indication as to which update will have this fix?
Thanks,
--
Access to samba 3.0.24-3.0.25 shares using CIFS is broken on
I just installed the new kernel (2.6.27-9-generic x86_64), but this fix
doesn't seem to have made it in there yet. nodfs seems to be an unknown
mount option for cifs.
Any indication as to which update will have this fix?
Thanks,
--
Access to samba 3.0.24-3.0.25 shares using CIFS is broken on
I've attached a tar file with two Wireshark dumps, as I couldn't work out how to
attach two files to a comment here directly.
If more information is required, please let me know.
Server: DNS-323, samba 3.0.24
Client: Ubuntu 8.10, kernel 2.6.27-7-generic
with standard settings:
# uname -r
2.6.27-7-generic
# mount -t cifs -o rw,user=xxx,password=xxx,nodfs //dns-323/Shared /mnt/dummy
# tail -1 /var/log/messages
Nov 20 08:34:24 mgjv kernel: [ 1670.862969] CIFS: Unknown mount option nodfs
Looks like that needs an ever newer kernel.
I am having this problem with a DNS-323
I've attached a tar file with two Wireshark dumps, as I couldn't work out how to
attach two files to a comment here directly.
If more information is required, please let me know.
Server: DNS-323, samba 3.0.24
Client: Ubuntu 8.10, kernel 2.6.27-7-generic
with standard settings:
I have a similar problem, but the other way around from the original
report.
I upgraded from Hardy to Intrepid a few days ago on a few machines. The
upgrade went without glitches on two i386 installations (one VirtualBox
and one on my old laptop). On this AMD64 installation, however, there
have
I've just been trying to determine where, during the boot cycle,
/lib/udev/hdparm is being called for the permanently attached disks.
While I can see the devices in /var/log/udev, I don't think that the
/lib/udev/hdparm script is run correctly, or maybe it's called too early
in the boot process.
I'm pretty sure that all /dev/[sh]d[a-z] devices would not have a digit
at the end unless they're partitions.
I don't mind using -h instead of -L.
I need to do some more testing. While the above worked fine when running
/lib/udev/hdparm from command line. i am not entirely convinced yet that
it
I've run into this same problem, but I actually use /dev/disk/by-uuid/*
links, which all link to a partition on the given device, rather than
the device itself. I suggest the following as a fix for this as well as
the earlier suggested fix:
93c93,100
DISC=$KEY
---
if
10 matches
Mail list logo
