Pages : 1
#1 Le 23/10/2006, à 19:07
- lionel1086
probléme avec ndiswrapper
Bonjour ,
Voulant installer ma clé wifi usb netgear wg111t j'ai suivi ce petit howto :
http://forum.ubuntu-fr.org/viewtopic.php?id=52293
mais j'ai un probléme au niveau de modprobe :
lionel@lionel-desktop:~$ sudo modprobe ndiswrapper
FATAL: Module ndiswrapper not found.
j'ai eu beau desinstaller reinstaller je ne sais plus quoi faire
Merci de votre aide
#2 Le 23/10/2006, à 22:45
- Karpatt
Re : probléme avec ndiswrapper
ya un prob entre ndiswrapper et edgy... perso jai du installé les derniers ndiswrapper pour que mon wifi fonctionne..
Hors ligne
#3 Le 24/10/2006, à 12:54
- paulmillot
Re : probléme avec ndiswrapper
Perso, je suis toujours sous Dapper, j'ai un peu galléré (allez... deux, trois heures au plus) puis je suis tombé sur cette page, magique :
http://www.ubuntuforums.org/showthread.php?t=197102
Il y a des explications pour à peu près tout types de cartes.
- Pour savoir quel type de carte on a la commande : lspci
(des fois Ubuntu la reconnait sous un autre nom... perso j'ai essayé avec les drivers fournis par ndiswrapper sous son nom officiel : F5D7001 - ca n'a pas marché - alors qu'en la considérant comme une :
paul@paul-desktop : lspci
...
0000:00:09.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)
...
et en me servant du script fourni par le lien plus haut, ça a très bien marché...
Pour les cartes nécessitant "ndiswrapper" ne pas oublier de regarder si elle est bien supportée :
http://ndiswrapper.sourceforge.net/medi … x.php/List
Sinon il existe d'autre façons de faire fonctionner les cartes wifi, apparement grace à une sorte de driver universel (ou presque) qui devrait être amélioré dans Edgy...
Good luck quand même, j'ai l'impression qu'il en faut...
----------------------------------------------------------------------
Par ailleurs, n'étant plus dépendant un cable ethernet, je peux désormais fermer ma fenêtre (l'hiver approche) mais j'ai tout de même un problème au démarage d'ubuntu... Je dois à chaque fois aller dans Système Administration Réseau et configurer ma carte wlan0 comme "par défaut" et dans ses propriétés décocher "Texte ASCII" pour "Exadécimal", fermer, ouvrir, puis reselectionner "Texte ASCII", et valider... c'est un peu lourd... D'autre part, samba (je suis sur un réseau avec deux autres PC sous Windaube) est très instable (des fois ça marche... des fois ça marche pas...) les pc sous la daube n'ont quand à eux aucun problème à me trouver sur le réseau et à consulter mes fichiers partagés.
Merci d'avance de votre aide
Paul
-------------------------------------
paul@paul-desktop:~$ iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wlan0 IEEE 802.11g ESSID:"BelgaCom"
Mode:Managed Frequency:2.437 GHz Access Point: 00:15:E9:06:C5:4E
Bit Rate:11 Mb/s Tx-Power:25 dBm
RTS thr:2347 B Fragment thr:2346 B
Power Management:off
Link Quality:100/100 Signal level:-83 dBm Noise level:-256 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
sit0 no wireless extensions.
---------------------------------------
paul@paul-desktop:~$ ndiswrapper -l
Installed ndis drivers:
bcmwl5 driver present, hardware present
---------------------------------------
/etc/samba/smb.conf
#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
#
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentary and a ; for parts of the config file that you
# may wish to enable
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.
#
#======================= Global Settings =======================
[global]
## Browsing/Identification ###
# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = DARLON
printcap name = lpstat
load printers = yes
printing = cups
# server string is the equivalent of the NT Description field
server string = %h server (Samba, Ubuntu)
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
wins support = yes
# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z
# This will prevent nmbd to search for NetBIOS names through DNS.
dns proxy = no
# What naming service and in what order should we use to resolve host names
# to IP addresses
; name resolve order = lmhosts host wins bcast
#### Networking ####
# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
; interfaces = 127.0.0.0/8 eth0
# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
; bind interfaces only = true
#### Debugging/Accounting ####
# This tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m
# Put a capping on the size of the log files (in Kb).
max log size = 1000
# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
; syslog only = no
# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
syslog = 0
# Do something sensible when Samba crashes: mail the admin a backtrace
panic action = /usr/share/samba/panic-action %d
####### Authentication #######
# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba-HOWTO-Collection/ServerType.html
# in the samba-doc package for details.
; security = user
# You may wish to use password encryption. See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
encrypt passwords = true
# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.
passdb backend = tdbsam
obey pam restrictions = yes
; guest account = nobody
invalid users = root
# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
; unix password sync = no
# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n *password\supdated\ssuccessfully* .
# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
; pam password change = no
########## Domains ###########
# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
#
; domain logons = yes
#
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of the user's profile directory
# from the client point of view)
# The following required a [profiles] share to be setup on the
# samba server (see below)
; logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
; logon path = \\%N\%U\profile
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
; logon drive = H:
; logon home = \\%N\%U
# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
; logon script = logon.cmd
# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe. The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u
########## Printing ##########
# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
load printers = yes
# lpr(ng) printing. You may wish to override the location of the
# printcap file
; printing = bsd
; printcap name = /etc/printcap
# CUPS printing. See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
printing = cups
printcap name = cups
# When using [print$], root is implicitly a 'printer admin', but you can
# also give this right to other users to add drivers and set printer
# properties
; printer admin = @lpadmin
############ Misc ############
# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include = /home/samba/etc/smb.conf.%m
# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/speed.html
# for details
# You may want to add the following on a Linux system:
# SO_RCVBUF=8192 SO_SNDBUF=8192
socket options = TCP_NODELAY
# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.
; message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &
# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to 'no'; otherwise, the default behavior is recommended.
; domain master = auto
# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
; idmap uid = 10000-20000
; idmap gid = 10000-20000
; template shell = /bin/bash
#======================= Share Definitions =======================
# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
[homes]
comment = Home Directories
browseable = yes
# By default, \\server\username shares can be connected to by anyone
# with access to the samba server. Un-comment the following parameter
# to make sure that only "username" can connect to \\server\username
; valid users = %S
# By default, the home directories are exported read-only. Change next
# parameter to 'yes' if you want to be able to write to them.
; writable = no
# File creation mask is set to 0600 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0664.
; create mask = 0600
# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
; directory mask = 0700
# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
; comment = Network Logon Service
; path = /home/samba/netlogon
; guest ok = yes
; writable = no
; share modes = no
# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
; comment = Users profiles
; path = /home/samba/profiles
; guest ok = no
; browseable = no
; create mask = 0600
; directory mask = 0700
wins support = yes
[printers]
comment = All Printers
browseable = no
path = /tmp
printable = yes
public = no
writable = no
create mode = 0700
# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
browseable = yes
read only = yes
guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# Replace 'ntadmin' with the name of the group your admin users are
# members of.
; write list = root, @ntadmin
# A sample share for sharing your CD-ROM with others.
[cdrom]
comment = Samba server's CD-ROM
writable = no
locking = no
path = /cdrom
public = yes
# The next two parameters show how to auto-mount a CD-ROM when the
# cdrom share is accesed. For this to work /etc/fstab must contain
# an entry like this:
#
/dev/scd0 /cdrom iso9660 defaults,noauto,ro,user 0 0
#
# The CD-ROM gets unmounted automatically after the connection to the
#
# If you don't want to use auto-mounting/unmounting make sure the CD
# is mounted on /cdrom
#
; preexec = /bin/mount /cdrom
; postexec = /bin/umount /cdrom
available = no
browseable = no
[A_GRAVER]
path = /media/DDPAUL/A_GRAVER
available = yes
browseable = yes
public = yes
writable = no
[MUSIQUE]
path = /media/DDPAUL/MUSIQUE
available = yes
browseable = yes
public = yes
writable = no
[Temp]
path = /media/fat/Temp
available = yes
browseable = yes
public = yes
writable = no
[FILMS]
path = /media/fat/films
available = yes
browseable = yes
public = yes
writable = no
[MONTAGE]
path = /media/fat/Montage
available = yes
browseable = yes
public = yes
writable = yes
[PROGRAMMES]
path = /media/fat/PROGRAMMES NEW 4_2
available = yes
browseable = yes
public = yes
writable = no
------------------------------------
Merci encore et désolé pour la place que ça prend sur ce post mais je crois que toutes ces infos sont nécessaires si je veux qu'on m'aide...
Paul
OSx86 iATKOS / Ubuntu 6.10 / Windows XP PRO - Intel Q6600 / GA-P35-DS3 / Nvidia GeForce 7300GT 256Mo / 3 Go pc6400 800Mhz
Hors ligne
#4 Le 24/10/2006, à 12:56
- paulmillot
Re : probléme avec ndiswrapper
Pardon pour la liste des cartes supportées par ndiswrapper, le lien est :
http://ndiswrapper.sourceforge.net/mediawiki/index.php/List
OSx86 iATKOS / Ubuntu 6.10 / Windows XP PRO - Intel Q6600 / GA-P35-DS3 / Nvidia GeForce 7300GT 256Mo / 3 Go pc6400 800Mhz
Hors ligne
#5 Le 24/10/2006, à 18:13
- lionel1086
Re : probléme avec ndiswrapper
Merci beaucoup pour cette aide
Purée trop venere ce matin j'etais proche de la faire fonctionner en me connectant au reseau sans fil et puis blam quitant ubuntu j'ai eu un kernel panic et le serveur x ne marche plus
Je vais faire une crise je sens ^^
Sinon est ce que vous connaitriez des cartes wifi marchant parfaitement sous linux ?
Pages : 1