Command:
sudo mount -t cifs //<server>/<share> -o username=user@domain,password=**** /mnt/<mountpoint>
error message:
Unable to find suitable address.
The syslog has:
CIFS VFS: Error connecting to socket. Aborting operation.
CIFS VFS: cifs_mount failed w/return code = -111
When I check out the documentation for mount via man mount
I see the following information about the error codes:
RETURN CODES
mount has the following return codes (the bits can be ORed):
0 success
1 incorrect invocation or permissions
2 system error (out of memory, cannot fork, no more loop devices)
4 internal mount bug
8 user interrupt
16 problems writing or locking /etc/mtab
32 mount failure
64 some mount succeeded
So does -111 mean the same thing as 1? If so, how can you diagnose if it’s permissions or the command isn’t correct?
asked May 5, 2015 at 13:50
1
111 = 64+32+8+4+2+1
So it meant to tell you that you hit every error except 16.
On my Ubuntu 14.04, I had to add -o sec=ntlmv2 or it will always give me 111 error, but I don’t need that option on my Ubuntu 15.04. Isn’t it confusing?
answered Jul 22, 2015 at 8:20
Tankman六四Tankman六四
1,5582 gold badges12 silver badges17 bronze badges
3
It means «Connection refused». To see a complete list of errors, check errno.h in the kernel source code. Partially listed here for your quick reference: (Note the minus sign will be added by the caller):
#define▸EL2HLT▸ ▸ 51▸ /* Level 2 halted */
#define▸EBADE▸ ▸ 52▸ /* Invalid exchange */
#define▸EBADR▸ ▸ 53▸ /* Invalid request descriptor */
#define▸EXFULL▸ ▸ 54▸ /* Exchange full */
#define▸ENOANO▸ ▸ 55▸ /* No anode */
#define▸EBADRQC▸▸ 56▸ /* Invalid request code */
#define▸EBADSLT▸▸ 57▸ /* Invalid slot */
#define▸EDEADLOCK▸ EDEADLK
#define▸EBFONT▸ ▸ 59▸ /* Bad font file format */
#define▸ENOSTR▸ ▸ 60▸ /* Device not a stream */
#define▸ENODATA▸▸ 61▸ /* No data available */
#define▸ETIME▸ ▸ 62▸ /* Timer expired */
#define▸ENOSR▸ ▸ 63▸ /* Out of streams resources */
#define▸ENONET▸ ▸ 64▸ /* Machine is not on the network */
#define▸ENOPKG▸ ▸ 65▸ /* Package not installed */
#define▸EREMOTE▸▸ 66▸ /* Object is remote */
#define▸ENOLINK▸▸ 67▸ /* Link has been severed */
#define▸EADV▸ ▸ 68▸ /* Advertise error */
#define▸ESRMNT▸ ▸ 69▸ /* Srmount error */
#define▸ECOMM▸ ▸ 70▸ /* Communication error on send */
#define▸EPROTO▸ ▸ 71▸ /* Protocol error */
#define▸EMULTIHOP▸ 72▸ /* Multihop attempted */
#define▸EDOTDOT▸▸ 73▸ /* RFS specific error */
#define▸EBADMSG▸▸ 74▸ /* Not a data message */
#define▸EOVERFLOW▸ 75▸ /* Value too large for defined data type */
#define▸ENOTUNIQ▸ 76▸ /* Name not unique on network */
#define▸EBADFD▸ ▸ 77▸ /* File descriptor in bad state */
#define▸EREMCHG▸▸ 78▸ /* Remote address changed */
#define▸ELIBACC▸▸ 79▸ /* Can not access a needed shared library */
#define▸ELIBBAD▸▸ 80▸ /* Accessing a corrupted shared library */
#define▸ELIBSCN▸▸ 81▸ /* .lib section in a.out corrupted */
#define▸ELIBMAX▸▸ 82▸ /* Attempting to link in too many shared libraries */
#define▸ELIBEXEC▸ 83▸ /* Cannot exec a shared library directly */
#define▸EILSEQ▸ ▸ 84▸ /* Illegal byte sequence */
#define▸ERESTART▸ 85▸ /* Interrupted system call should be restarted */
#define▸ESTRPIPE▸ 86▸ /* Streams pipe error */
#define▸EUSERS▸ ▸ 87▸ /* Too many users */
#define▸ENOTSOCK▸ 88▸ /* Socket operation on non-socket */
#define▸EDESTADDRREQ▸ 89▸ /* Destination address required */
#define▸EMSGSIZE▸ 90▸ /* Message too long */
#define▸EPROTOTYPE▸ 91▸ /* Protocol wrong type for socket */
#define▸ENOPROTOOPT▸92▸ /* Protocol not available */
#define▸EPROTONOSUPPORT▸93▸ /* Protocol not supported */
#define▸ESOCKTNOSUPPORT▸94▸ /* Socket type not supported */
#define▸EOPNOTSUPP▸ 95▸ /* Operation not supported on transport endpoint */
#define▸EPFNOSUPPORT▸ 96▸ /* Protocol family not supported */
#define▸EAFNOSUPPORT▸ 97▸ /* Address family not supported by protocol */
#define▸EADDRINUSE▸ 98▸ /* Address already in use */
#define▸EADDRNOTAVAIL▸ 99▸ /* Cannot assign requested address */
#define▸ENETDOWN▸ 100▸/* Network is down */
#define▸ENETUNREACH▸101▸/* Network is unreachable */
#define▸ENETRESET▸ 102▸/* Network dropped connection because of reset */
#define▸ECONNABORTED▸ 103▸/* Software caused connection abort */
#define▸ECONNRESET▸ 104▸/* Connection reset by peer */
#define▸ENOBUFS▸▸ 105▸/* No buffer space available */
#define▸EISCONN▸▸ 106▸/* Transport endpoint is already connected */
#define▸ENOTCONN▸ 107▸/* Transport endpoint is not connected */
#define▸ESHUTDOWN▸ 108▸/* Cannot send after transport endpoint shutdown */
#define▸ETOOMANYREFS▸ 109▸/* Too many references: cannot splice */
#define▸ETIMEDOUT▸ 110▸/* Connection timed out */
#define▸ECONNREFUSED▸ 111▸/* Connection refused */
#define▸EHOSTDOWN▸ 112▸/* Host is down */
#define▸EHOSTUNREACH▸ 113▸/* No route to host */
#define▸EALREADY▸ 114▸/* Operation already in progress */
#define▸EINPROGRESS▸115▸/* Operation now in progress */
#define▸ESTALE▸ ▸ 116▸/* Stale file handle */
#define▸EUCLEAN▸▸ 117▸/* Structure needs cleaning */
#define▸ENOTNAM▸▸ 118▸/* Not a XENIX named type file */
#define▸ENAVAIL▸▸ 119▸/* No XENIX semaphores available */
#define▸EISNAM▸ ▸ 120▸/* Is a named type file */
#define▸EREMOTEIO▸ 121▸/* Remote I/O error */
#define▸EDQUOT▸ ▸ 122▸/* Quota exceeded */
#define▸ENOMEDIUM▸ 123▸/* No medium found */
#define▸EMEDIUMTYPE▸124▸/* Wrong medium type */
#define▸ECANCELED▸ 125▸/* Operation Canceled */
#define▸ENOKEY▸ ▸ 126▸/* Required key not available */
#define▸EKEYEXPIRED▸127▸/* Key has expired */
#define▸EKEYREVOKED▸128▸/* Key has been revoked */
#define▸EKEYREJECTED▸ 129▸/* Key was rejected by service */
/* for robust mutexes */
#define▸EOWNERDEAD▸ 130▸/* Owner died */
#define▸ENOTRECOVERABLE▸131▸/* State not recoverable */
#define ERFKILL▸▸ 132▸/* Operation not possible due to RF-kill */
#define EHWPOISON▸ 133▸/* Memory page has hardware error */
answered Oct 4, 2021 at 18:43
Penghe GengPenghe Geng
12.6k4 gold badges30 silver badges40 bronze badges
I recently started getting this error on Fedora 27.
Changing option vers=1.0 to vers=2.0 ( -o defaults,vers=2.0,rsize=…) solved the issue.
answered Apr 11, 2018 at 7:11
scharettescharette
6051 gold badge9 silver badges23 bronze badges
Command:
sudo mount -t cifs //<server>/<share> -o username=user@domain,password=**** /mnt/<mountpoint>
error message:
Unable to find suitable address.
The syslog has:
CIFS VFS: Error connecting to socket. Aborting operation.
CIFS VFS: cifs_mount failed w/return code = -111
When I check out the documentation for mount via man mount
I see the following information about the error codes:
RETURN CODES
mount has the following return codes (the bits can be ORed):
0 success
1 incorrect invocation or permissions
2 system error (out of memory, cannot fork, no more loop devices)
4 internal mount bug
8 user interrupt
16 problems writing or locking /etc/mtab
32 mount failure
64 some mount succeeded
So does -111 mean the same thing as 1? If so, how can you diagnose if it’s permissions or the command isn’t correct?
asked May 5, 2015 at 13:50
1
111 = 64+32+8+4+2+1
So it meant to tell you that you hit every error except 16.
On my Ubuntu 14.04, I had to add -o sec=ntlmv2 or it will always give me 111 error, but I don’t need that option on my Ubuntu 15.04. Isn’t it confusing?
answered Jul 22, 2015 at 8:20
Tankman六四Tankman六四
1,5582 gold badges12 silver badges17 bronze badges
3
It means «Connection refused». To see a complete list of errors, check errno.h in the kernel source code. Partially listed here for your quick reference: (Note the minus sign will be added by the caller):
#define▸EL2HLT▸ ▸ 51▸ /* Level 2 halted */
#define▸EBADE▸ ▸ 52▸ /* Invalid exchange */
#define▸EBADR▸ ▸ 53▸ /* Invalid request descriptor */
#define▸EXFULL▸ ▸ 54▸ /* Exchange full */
#define▸ENOANO▸ ▸ 55▸ /* No anode */
#define▸EBADRQC▸▸ 56▸ /* Invalid request code */
#define▸EBADSLT▸▸ 57▸ /* Invalid slot */
#define▸EDEADLOCK▸ EDEADLK
#define▸EBFONT▸ ▸ 59▸ /* Bad font file format */
#define▸ENOSTR▸ ▸ 60▸ /* Device not a stream */
#define▸ENODATA▸▸ 61▸ /* No data available */
#define▸ETIME▸ ▸ 62▸ /* Timer expired */
#define▸ENOSR▸ ▸ 63▸ /* Out of streams resources */
#define▸ENONET▸ ▸ 64▸ /* Machine is not on the network */
#define▸ENOPKG▸ ▸ 65▸ /* Package not installed */
#define▸EREMOTE▸▸ 66▸ /* Object is remote */
#define▸ENOLINK▸▸ 67▸ /* Link has been severed */
#define▸EADV▸ ▸ 68▸ /* Advertise error */
#define▸ESRMNT▸ ▸ 69▸ /* Srmount error */
#define▸ECOMM▸ ▸ 70▸ /* Communication error on send */
#define▸EPROTO▸ ▸ 71▸ /* Protocol error */
#define▸EMULTIHOP▸ 72▸ /* Multihop attempted */
#define▸EDOTDOT▸▸ 73▸ /* RFS specific error */
#define▸EBADMSG▸▸ 74▸ /* Not a data message */
#define▸EOVERFLOW▸ 75▸ /* Value too large for defined data type */
#define▸ENOTUNIQ▸ 76▸ /* Name not unique on network */
#define▸EBADFD▸ ▸ 77▸ /* File descriptor in bad state */
#define▸EREMCHG▸▸ 78▸ /* Remote address changed */
#define▸ELIBACC▸▸ 79▸ /* Can not access a needed shared library */
#define▸ELIBBAD▸▸ 80▸ /* Accessing a corrupted shared library */
#define▸ELIBSCN▸▸ 81▸ /* .lib section in a.out corrupted */
#define▸ELIBMAX▸▸ 82▸ /* Attempting to link in too many shared libraries */
#define▸ELIBEXEC▸ 83▸ /* Cannot exec a shared library directly */
#define▸EILSEQ▸ ▸ 84▸ /* Illegal byte sequence */
#define▸ERESTART▸ 85▸ /* Interrupted system call should be restarted */
#define▸ESTRPIPE▸ 86▸ /* Streams pipe error */
#define▸EUSERS▸ ▸ 87▸ /* Too many users */
#define▸ENOTSOCK▸ 88▸ /* Socket operation on non-socket */
#define▸EDESTADDRREQ▸ 89▸ /* Destination address required */
#define▸EMSGSIZE▸ 90▸ /* Message too long */
#define▸EPROTOTYPE▸ 91▸ /* Protocol wrong type for socket */
#define▸ENOPROTOOPT▸92▸ /* Protocol not available */
#define▸EPROTONOSUPPORT▸93▸ /* Protocol not supported */
#define▸ESOCKTNOSUPPORT▸94▸ /* Socket type not supported */
#define▸EOPNOTSUPP▸ 95▸ /* Operation not supported on transport endpoint */
#define▸EPFNOSUPPORT▸ 96▸ /* Protocol family not supported */
#define▸EAFNOSUPPORT▸ 97▸ /* Address family not supported by protocol */
#define▸EADDRINUSE▸ 98▸ /* Address already in use */
#define▸EADDRNOTAVAIL▸ 99▸ /* Cannot assign requested address */
#define▸ENETDOWN▸ 100▸/* Network is down */
#define▸ENETUNREACH▸101▸/* Network is unreachable */
#define▸ENETRESET▸ 102▸/* Network dropped connection because of reset */
#define▸ECONNABORTED▸ 103▸/* Software caused connection abort */
#define▸ECONNRESET▸ 104▸/* Connection reset by peer */
#define▸ENOBUFS▸▸ 105▸/* No buffer space available */
#define▸EISCONN▸▸ 106▸/* Transport endpoint is already connected */
#define▸ENOTCONN▸ 107▸/* Transport endpoint is not connected */
#define▸ESHUTDOWN▸ 108▸/* Cannot send after transport endpoint shutdown */
#define▸ETOOMANYREFS▸ 109▸/* Too many references: cannot splice */
#define▸ETIMEDOUT▸ 110▸/* Connection timed out */
#define▸ECONNREFUSED▸ 111▸/* Connection refused */
#define▸EHOSTDOWN▸ 112▸/* Host is down */
#define▸EHOSTUNREACH▸ 113▸/* No route to host */
#define▸EALREADY▸ 114▸/* Operation already in progress */
#define▸EINPROGRESS▸115▸/* Operation now in progress */
#define▸ESTALE▸ ▸ 116▸/* Stale file handle */
#define▸EUCLEAN▸▸ 117▸/* Structure needs cleaning */
#define▸ENOTNAM▸▸ 118▸/* Not a XENIX named type file */
#define▸ENAVAIL▸▸ 119▸/* No XENIX semaphores available */
#define▸EISNAM▸ ▸ 120▸/* Is a named type file */
#define▸EREMOTEIO▸ 121▸/* Remote I/O error */
#define▸EDQUOT▸ ▸ 122▸/* Quota exceeded */
#define▸ENOMEDIUM▸ 123▸/* No medium found */
#define▸EMEDIUMTYPE▸124▸/* Wrong medium type */
#define▸ECANCELED▸ 125▸/* Operation Canceled */
#define▸ENOKEY▸ ▸ 126▸/* Required key not available */
#define▸EKEYEXPIRED▸127▸/* Key has expired */
#define▸EKEYREVOKED▸128▸/* Key has been revoked */
#define▸EKEYREJECTED▸ 129▸/* Key was rejected by service */
/* for robust mutexes */
#define▸EOWNERDEAD▸ 130▸/* Owner died */
#define▸ENOTRECOVERABLE▸131▸/* State not recoverable */
#define ERFKILL▸▸ 132▸/* Operation not possible due to RF-kill */
#define EHWPOISON▸ 133▸/* Memory page has hardware error */
answered Oct 4, 2021 at 18:43
Penghe GengPenghe Geng
12.6k4 gold badges30 silver badges40 bronze badges
I recently started getting this error on Fedora 27.
Changing option vers=1.0 to vers=2.0 ( -o defaults,vers=2.0,rsize=…) solved the issue.
answered Apr 11, 2018 at 7:11
scharettescharette
6051 gold badge9 silver badges23 bronze badges
- Forum
- The Ubuntu Forum Community
- Ubuntu Official Flavours Support
- General Help
- [ubuntu] Issue Mounting CIFS Share
-
Issue Mounting CIFS Share
Hi all,
I’m trying to mount a share on a Windows 7 desktop from my Ubuntu build. the share I’m trying to connect to is the administrative share «C$». the command I’m entering is
mount -t cifs //IP_Address/C$ -o username=domain_namewindows_username,password=win dows_password /mnt/ntserver
and I am getting the following error
mount error(111): Connection refused
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)I did attempt this to another share (Temp) with everyone read access however I got the same error as above. The account I’m trying to authenticate is a local administrator of the Windows 7 build.
I’m not a Linux expert so be gentle
Thanks.
-
Re: Issue Mounting CIFS Share
A couple of things:
The dollar sign ($) is an special character on bash, it maybe necessary to «escape it». Try this:
Code:
$ mount -t cifs //IP_Address/C$ ...
In order to mount samba shares on bash, you need an additional package besides samba. Check if it is install:
Code:
$ dpkg -l | grep smbfs
If it isn’t install, get it like this:
Code:
$ sudo apt-get install smbfs
Good Luck!
Last edited by papibe; December 2nd, 2010 at 05:50 AM.
Reason: spelling
-
Re: Issue Mounting CIFS Share
Hi,
I know this is a bit of an old post, but better late than never hey?
I managed to resolve similar issues connecting to the windows 7 admin shares (c$ d$ etc) from xubuntu 11.04.
The problem was with the windows machine, there is setting in the windows registry that prevents local network users connecting to the admin shares. You just have to put a new reg key in to fix it.
Key goes in:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurr entVersionPoliciesSystemKey DWORD (32-bit): LocalAccountTokenFilterPolicy
Key Value : 1Further information from Microsoft available here
Hope that helps
Last edited by RustySheriffsBadge; May 7th, 2011 at 04:00 PM.
Tags for this Thread
Bookmarks
Bookmarks
Posting Permissions
Description of problem:
if i try and mount a cifs file I get
mount.cifs kernel mount options unc=//127.0.0.1wally,pass=xxxxxx,ver=1,rw,username=wally,port=1139
mount error(111): Connection refused
the server is fc10 the client is fc11
Version-Release number of selected component (if applicable):
server:
samba.x86_64 3.2.11-0.30.fc10 installed
samba-client.x86_64 3.2.11-0.30.fc10 installed
samba-common.x86_64 3.2.11-0.30.fc10 installed
samba-winbind.x86_64 3.2.11-0.30.fc10
client:
samba-winbind3.3.2-0.33.fc11.x86_64 samba-common3.3.2-0.33.fc11.x86_64 samba-client-3.3.2-0.33.fc11.x86_64
How reproducible:
ssh -L 1139:127.0.0.1:139 user
sudo /bin/mount -v -t cifs //127.0.0.1/wally /home/wally/z -o username=wally,port=1139
results:
mount.cifs kernel mount options unc=//127.0.0.1wally,pass=xxxxx,ver=1,rw,user=wally,port=1139
mount.cifs kernel mount options unc=//127.0.0.1wally,pass=xxxxx,ver=1,rw,user=wally,port=1139
mount.cifs kernel mount options unc=//127.0.0.1wally,pass=xxxxx,ver=1,rw,user=wally,port=1139
mount error(111): Connection refused
Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)
if i do:
[wally@localhost ~]$ smbclient -L 127.0.0.1 -p 1139 --workgroup=MYGROUP
Enter wally's password:
Domain=[GENEPI1] OS=[Unix] Server=[Samba 3.2.11-0.30.fc10]
Sharename Type Comment
--------- ---- -------
IPC$ IPC IPC Service (Samba Server)
software Disk lab software
share_genetics Disk lab stuff
share_lab Disk lab stuff
rm233 Printer color printer
rm209 Printer hp1300n
wally Disk Home Directories
Connection to 127.0.0.1 failed (Error NT_STATUS_CONNECTION_REFUSED)
NetBIOS over TCP disabled -- no workgroup available
and get a log like:
[2009/06/17 12:32:31, 0] lib/util_sock.c:matchname(1749)
matchname: host name/address mismatch: ::ffff:127.0.0.1 != localhost.localdomain
[2009/06/17 12:32:31, 0] lib/util_sock.c:get_peer_name(1870)
Matchname failed on localhost.localdomain ::ffff:127.0.0.1
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
thanks for any help, I've spent much time trying to trouble shoot, I also
tried running fc10's versions of samba-{common,client,winbind}, still no
work. I also tried disabling ipv6 at the module level, nada. I did verify
my tunnel using netcat and xeyes, both worked as expected. -- gary
when i try the mount I get prompted 3x for a passwd and each time it is rejected, because I'm tunneling thru ssh it useless to to a net trace.
NT_STATUS_CONNECTION_REFUSED usually just means there is no listening daemon on the ip/port you are trying to connect to. given smbclient succeedes it seem like mount.cifs is trying to connect to the wrong host or connecting to the wrong port. You can check what's going on by taking a network trace of the local interface on the client or on the server Use wireshark/tcpdump and listen on interface "lo"
ok, will do, I can't get to it asap, but early next week will response. This is a 'show stopper' for my environment -- should be for anyone tunneling ports. Without samba on the linux desktop I'll get lotsa complaints. I did tunnel ports 14000 (local) 14001 (remote) using nc (netcat) and worked fine. my guess is its mount.cifs. thanks much for your help, will reply shortly! g.
Created attachment 349010 [details]
wireshark trace of lo
added simple text output from wireshark. Seems the mount.cifs never tries to go to 1139. let me need more detail. i noted that mount.cifs segfaults if you try running it directly.
command executed:
ssh -L 1139:127.0.0.1:139 waldo
sudo /bin/mount -v -t cifs -o port=1139,username=waldo,password=xxxxxxx //127.0.0.1/waldo /home/waldo/z
smbclient -p 1139 //127.0.0.1/user works, i get into the cifs shell or whatever. mount.cifs still borken! -- g
Created attachment 349091 [details]
patch -- fix port= mount option for cifs
This patch should fix it. Can you test it out and let me know whether it does?
thanks, will do. since its a fs/cifs patch I need to learn the fc/redhat methods of src updates/compiles of kernel -- i could do this with gentoo in a wink, but i know there's more to it with RH/fc. bare with me as i muddle along, but __hey__ thanks for find this for us!! -- g. -- should have feed back by Friday at the latest.
no go, same problem after patching and installing rpm kernel. did you get it to work? thanks much. maybe there is an easier way? ... [wally@localhost ~]$ sudo /bin/mount -v -t cifs //127.0.0.1/wally /home/wally/z -o username=wally,port=1139 parsing options: rw,username=wally,port=1139 Password: mount.cifs kernel mount options unc=//127.0.0.1wally,pass=abc123,ver=1,rw,username=wally,port=1139 mount.cifs kernel mount options unc=//127.0.0.1wally,pass=abc123,ver=1,rw,username=wally,port=1139 mount.cifs kernel mount options unc=//127.0.0.1wally,pass=abc123,ver=1,rw,username=wally,port=1139 mount error(111): Connection refused Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)
on attempts get these on console. the wireshark show no attempt to go to 1139 port. smbclient works. CIFS VFS: Error connecting to socket. Aborting operation CIFS VFS: cifs_mount failed w/return code = -111 CIFS VFS: Error connecting to socket. Aborting operation CIFS VFS: cifs_mount failed w/return code = -111 CIFS VFS: Error connecting to socket. Aborting operation CIFS VFS: cifs_mount failed w/return code = -111 CIFS VFS: Error connecting to socket. Aborting operation
forget post #8/#9, i made an error and am retrying now. (be back)
ok, retested with the little change Jeff and it works! ha! blew off on disk the first time i tried building the kernel rpms and forgot to re-apply the change and tested it without them. re-did with patches and the mount flys, * * One question, when/how will I know the patch has made it into the kernel? * * cheers, thanks thanks thanks, Gary
Steve French (the upstream CIFS maintainer) committed this into his tree last night. I expect that this patch will make 2.6.31.
Ok, closing this bug as it is fixed upstream. As soon as we have the new kernel including these patches in Fedora it will work automatically.
Ok, I'll wait and test with 2.6.31 ( cheers ).
Please don't close F-11 bugs as soon as upstream patches are submitted. It will be many months until those patches would automatically get into f-11, if ever.
ok, sorry about that.
Fixed in kernel-2.6.29.5-204
kernel-2.6.29.6-213.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update kernel'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-7617
kernel-2.6.29.6-213.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report. |