Re: Replacing bcmxx wifi cards with intel 2200 & 2915 in Lenny and Squeeze
Hi Mark, On Wed, Dec 14, 2011 at 04:24:55PM -0800, Mark wrote: > is it necessary to remove/purge the b43-fwcutter/b43 firmware in order to > install ipw2x00, or is it ok to leave it installed should I need to return > to those wifi cards at some point in the future? Firmware installed by the firmware-b43-installer and firmware-ipw2x00 packages are placed in separate directories (/lib/firmware/b43 and /lib/firmware respectively) and the relevant drivers request differently named files. As they do not conflict, both packages can be installed on the same system. Geoff -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111215005234.gb4...@chmmr.gsimmons.org
Re: how to examine the wireless
On Mon, Dec 12, 2011 at 02:37:44PM +, steef wrote: > you could use the broadcom-sta (source-package) in combination with this > webpage: http://wiki.debian.org/wl The proprietary driver has no support for the BCM4331 at this time. Geoff -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111214072851.gm3...@chmmr.gsimmons.org
Re: Network Connection issue
Hi John, On Thu, Nov 03, 2011 at 02:55:51PM -0500, John Foster wrote: > I recently installed a new D-Link DGE-530T 10/100/1000 Gigabit Desktop PCI > Adapter card to connect to the internet. It was originally not recognized > as there was not a driver available in debian. Support for the DGE-530T revision C1 (Realtek RTL8169 based, PCI ID 1186:4302) was added to the in-tree r8169 driver at Linux 3.0.2. This was incorporated in Debian's linux-2.6 as of version 2.6.32-36 (part of the 6.0.3 point release). Firmware from userspace is not required for use of this device. > I had also installed another 'recognized' 3-com card, just to get the > system to work. [...] > Debian did find the new card & set it up as eth1 while the 3-com card > which worked was at eth0. [...] > I decided to try to get my system to use the new card today so I went into > the box & removed the 3-com card, leaving only the D-Link card connected. > Well, I was back where I started. Now my system will not connect to the > network, & the router that supplies the connection will not see the card. Your network configuration likely requires adjustment. Through udev, Debian systems use persistent names for network interfaces; your DGE-530T device will still be assigned eth1 even when the 3Com card is physically removed. The output of "ifconfig -a" (as requested by Victor Nitu) would have been useful to confirm the current interface assignment. You can either: * Modify /etc/udev/rules.d/70-persistent-net.rules to assign eth0 to your DGE-530T device (e.g. NAME="eth0"). The relevant line to adjust should be present under a comment such as '# PCI device 0x1186:0x4302 (r8169)'. After modification, save the file and reload the r8169 module using the command "modprobe -r r8169 ; modprobe r8169" (alternatively, execute "udevadm trigger"). Run "ifconfig -a" to confirm interface assignment. * Amend your system's network configuration (/etc/network/interfaces) to use eth1 instead of eth0, then bring the interface up using "ifup eth1". The interfaces(5) manual page describes this file's format (execute "man interfaces" to view this), see also other information available at [1]. Note that other application configuration files (e.g. iptables based firewall) may require to be similarly updated. On Fri, Nov 04, 2011 at 08:49:56AM -0500, John Foster wrote: > It seems the correct driver is being loaded & I changed the etc/network > interfaces to this now. It is the factory setup for a single card. [...] > --- > # This file describes the network interfaces available on your system > # and how to activate them. For more information, see interfaces(5). > # The loopback network interface > auto lo > iface lo inet loopback > > # The primary network interface > allow-hotplug eth0 > iface lo inet loopback > -- This is incorrect, as two iface stanzas are stated for loopback. It should contain a line for the eth* network interface (e.g. "iface eth0 inet dhcp"). Geoff [1] http://wiki.debian.org/NetworkConfiguration -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2005051931.ga9...@chmmr.gsimmons.org
Re: Support of Ethernet card Broadcom
Hi Bruno, On Sat, Sep 17, 2011 at 07:06:21PM +0200, Bruno Costacurta wrote: > I bought an Acer (model 4750) and tried to install on it Squeeze > image i386 CD-ROM. > During the network hardware detection the Ethernet card Broadcom > (model Netlink BCM57785) is not recognized (note : I identified this > model using an Ubuntu 11.04 live DVD). Support of the Broadcom BCM57785 (PCI ID 14e4:16b5) was introduced in the tg3 driver at Linux 2.6.34. > I suppose it is simply not included in the Squeeze image i386 CD-Rom I > used. Yes, Debian 6.0.2.1 installation media will not support your device; support is anticipated for the upcoming 6.0.3 point release. > My questions is does Debian propose a package supporting Ethernet > card Broadcom BCM57785 ? For device support during and after Debian installation, you would need to use an unofficial installer (containing a backported Linux kernel) at this time, see [1] for further details. For an established system (with an alternate form of connectivity), you can use either a backported linux-image package from Debian Backports [2], or a linux-image package proposed for the 6.0.3 point release [3]. Geoff [1] http://kmuto.jp/debian/d-i/ [2] http://backports-master.debian.org/Instructions/ [3] http://www.debian.org/releases/proposed-updates -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110918081915.ga28...@chmmr.gsimmons.org
Re: CrystalClear SoundFusion Audio Accelerator
On Tue, Sep 13, 2011 at 09:28:09AM -0400, co...@esid.gecgr.co.cu wrote: > i'm trying to get my sound card pci: > > 06:01.0 Multimedia audio controller: Cirrus Logic CS 4614/22/24/30 > [CrystalClear SoundFusion Audio Accelerator] (rev 01) > > but is not possible the kernel dos not support > > i use Debian squeeze. You need to supply firmware for support of your device (PCI ID 1013:6003), see http://wiki.debian.org/snd-cs46xx for more information. Geoff -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110915080822.gd2...@chmmr.gsimmons.org
Re: Kernel 2.6.38-bpo.2-686 and Virtualbox
Hi Perry, On Wed, May 25, 2011 at 01:07:21PM -0400, Perry Thompson wrote: > Examining /etc/kernel/header_postinst.d. > run-parts: executing /etc/kernel/header_postinst.d/dkms 2.6.38-bpo.2-686 [...] > ndiswrapper (1.56)...failed. [...] > Any ideas how to fix Virtualbox and/or the other two packages that are > no longer working? You require a later NDISwrapper version for use with Linux 2.6.38 (see Debian bugs #604880, #622709) which is available in the testing branch. Geoff -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110526032654.ga6...@chmmr.gsimmons.org
Re: Dlink DWA-525
On Tue, May 17, 2011 at 10:25:17PM +0300, Алекс Скоропад wrote: > I have this wireless network card, and it work just fine with drivers > from dlink website until the last kernel update. In new kernel were > included support for some dlink wireless cards, but there are no > rt3562sta support. Experimental support for the Ralink RT3060 chip contained within your device was enabled in rt2800pci at linux-2.6 2.6.38-5 (Debian bug #623808). This conflicts with the out-of-tree rt3562sta driver made available by the vendor. > Now I removed > /lib/modules/2.6.38-2-amd64/kernel/drivers/net/wireless/rt2x00 > directory and my card work fine again with driver from dlink website. > Can You fix driver that You include in new kernel? Consider blacklisting[1] rt2800pci instead if you prefer use of the out-of-tree vendor driver, as the removed directory will reinstated/repopulated during future linux-image-* package updates. Geoff [1] http://wiki.debian.org/KernelModuleBlacklisting -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110518012858.gg2...@chmmr.gsimmons.org
Re: Squeeze. Broken native laptop screen res 1366x768@NVIDIA after last update
Hi Mark, On Mon, Mar 21, 2011 at 06:08:01AM +0300, Mark Goldshtein wrote: > This case is solved with # mv /etc/X11/XF86Config /etc/X11/xorg.conf > > I am just interesting, what was introduced by the last update, if it > broke my X configuration? >From the xorg-server package changelog: xorg-server (2:1.7.7-12) unstable; urgency=low [...] * Add 22-stop-searching-for-xf86config-files, cherry-picking the upstream commit below (which we can't do directly since it depends on a patch kept in the quilt series: 08-config-xorg-conf-d.diff), so that XF86Config-4 is no longer considered (Closes: #610453). Thanks, Bernhard R. Link! - Stop searching for XF86Config files This change is briefly mentioned in the 6.0.1 news release. Geoff -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110321084230.ga2...@chmmr.gsimmons.org
Re: modem symlink in /dev
Hi Martin, On Sun, Mar 13, 2011 at 11:16:43PM +0100, Martin wrote: > I installed martian-modem and martian-modem-source that work fine > but after each reboot I have to issue command: > # ln -s /dev/ttySM0 /dev/modem The device symlink created by the martian-modem daemon (/dev/ttySM0 by default) can be set within /etc/default/martian-modem. Adding "DEVICE=/dev/modem" to this file should provide your expected behaviour, after the martian-modem daemon is restarted. Alternatively, adjust your PPP dialer application to use /dev/ttySM0. Geoff -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110314052203.ga6...@chmmr.gsimmons.org
Re: installing rtl8187B on debian lenny with kernel 2.6.26 - need help on installing backport kernel to recognise chipset
Hi Rico, On Mon, Jan 31, 2011 at 02:04:55PM +1100, Rico D wrote: > i'm trying to follow this article: http://wiki.debian.org/rtl818x > > But i'm very new to linux and i'm having trouble in installing the > back port kernel. [...] > and I tried running this command - > > aptitude -t lenny-backports install linux-image-2.6-$(uname -r | sed > 's,.*-,,') wireless-tools You are required to add the Debian Backports repository to your /etc/apt/sources.list file prior to this command. See [1] for instructions, which was linked from this procedure. > but the above command failed. from they way i understand it, it's > trying to install backported version of wireless tools.. If you received an error, it would have been helpful to include that here. There is no backported wireless-tools package available in lenny-backports. Amend your /etc/apt/sources.list file, run "aptitude update", install the backported linux-image-* package (using your earlier command) and restart your system into the 2.6.32 kernel. Geoff [1] http://wiki.debian.org/Backports -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110131104728.gl3...@p67.lan.gsimmons.org
Re: Re: WPA2-WLAN on Laptop with PCMCIA card and wpa_supplicant
Hi Clemens, On Sun, Jan 09, 2011 at 06:03:00PM +0100, eltre...@web.de wrote: > Trying to get online wirelessly I encountered problems connecting by > means of wpa_supplicant. [...] > For the WLAN connection I have a PCMCIA WLAN card from 3com. I will guess you are using either a 3CRSHPW_96 or 3CRWE62092B 802.11b device here. > The access point I am trying to connect to only allows WPA2-encrypted > connections. Despite the loading of WPA-capable firmware, the atmel_cs driver does not support Wi-Fi Protected Access, as indicated by the "Driver does not support WPA" message from wpa_supplicant. > I also tried to use the atmel driver explicitely [...] > wpa_supplicant -D atmel -c /etc/wpa_supplicant/wpa_supplicant.conf -i eth1 > -dd. The atmel wpa_supplicant driver backend was only usable with the obsolete atmelwlandriver, not atmel_cs. Building of this backend was disabled in Debian's wpasupplicant package at version 0.6.10-1. Consider using a different device (your laptop has a CardBus slot) with a WPA-capable driver available; any 802.11g device supported by an in-tree driver would provide your necessary support. Note that use of NDISwrapper as a workaround is not possible, as 16-bit PCMCIA devices are not supported. Geoff -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110109190012.gh6...@tammy.lan.gsimmons.org
Re: how to make pdnsd listen on all interfaces?
Hi Martin, On Thu, Dec 16, 2010 at 07:56:47PM +0100, Martin Kraus wrote: > I'm trying to get pdnsd to listen on all interfaces. server_ip=any > should work but it always listens only on 127.0.0.1 even with several > other interfaces present. is this a bug or am I missing something? The pdnsd package defaults to use of an automatic configuration file (containing reasonable defaults) from /usr/share/pdnsd, overriding /etc/pdnsd.conf. Both pdnsd-recurse.conf and pdnsd-resolvconf.conf define a server_ip value of 127.0.0.1. You probably want to adjust /etc/default/pdnsd to enable manual mode, as described in /usr/share/doc/pdnsd/README.Debian. Geoff -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101216232903.ga15...@tammy.lan.gsimmons.org
Re: wireless adapters
Hi Bill, On Mon, Sep 20, 2010 at 11:12:48PM -0500, William Kindler wrote: > I have a USB device which is a D-Link DWA-130, and a PCI adapter which > is a Netgear WN311T. [...] > Does anyone know if either or both of these devices are supported with > Debian? The D-Link DWA-130 has had a number of hardware revisions: - Revision A1 (USB ID 07d1:3b11) contains a Marvell 88W8360 chipset, which has no native driver available. You would need to use NDISwrapper[1] for device support. - Revision B (USB ID 07d1:3c13) is supported by the rt2800usb driver, which is included in the mainline Linux kernel since 2.6.31. For Lenny, you can acquire backported 2.6.32 linux-image packages from Debian Backports[2]. The firmware-ralink package from lenny-backports will also need to be installed. - Revision C1 (USB ID 2001:3301) is supported by the rtl8192u[3] driver. - Revision C2 (USB ID 07d1:3302) and revision E (USB ID 07d1:3300) are supported by the rtl8192su[3] driver. - Revision D (USB ID 07d1:3a0f) contains an Atheros AR9001U chipset, which is not currently claimed by the ar9170usb[4] driver in Debian Linux kernel images. After using modprobe to insert ar9170usb, you can try executing "echo 07d1 3a0f > /sys/bus/usb/drivers/ar9170usb/new_id" to inform the driver of this device. The Netgear WN311T (PCI ID 11ab:2a02) contains a Marvell 88W8361 chipset, which has no native driver available; NDISwrapper[1] would be required for device support. > If so could you tell me where the drivers can be obtained, and where > to install them, if they are not native to the Debian distribution? For your DWA-130 device, determine its USB ID (you can use lsusb from the usbutils package), then refer to the respective page on the Debian wiki. Geoff [1] http://wiki.debian.org/NdisWrapper [2] http://wiki.debian.org/Backports [3] http://wiki.debian.org/rtl819x [4] http://wiki.debian.org/ar9170usb -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100921055706.gb20...@tammy.lan.gsimmons.org
Re: Can't locate ndiswrapper module!
Hi Bruce,
On Thu, Sep 16, 2010 at 08:57:43PM +1200, Bruce Ward wrote:
> I get this message:
> FATAL: Module ndiswrapper not found.
On Lenny, you would usually want to build this dependent kernel module
using module-assistant, which automates installation of prerequisite
packages, the process of compiling module source and binary module
installation. See [1].
> I cannot find "pre-compiled modules" anywhere on the Debian site. Do
> they exist, or are they just a myth?
Pre-compiled NDISwrapper modules were last available for Debian 3.1
("Sarge") via the ndiswrapper-modules-i386 source package, removed to
resolve Debian bug #418929.
Efforts were made for inclusion of module packages built from
linux-modules-extra-2.6 (BTS #385553, #400752), which itself was
eventually removed (#552369) in favour of DKMS or other out-of-tree
build method.
The inaccuracy of pre-compiled module availability within
ndiswrapper-source's package description (added in version 1.53-1) was
corrected at ndiswrapper version 1.55-1.
Geoff
[1] http://wiki.debian.org/NdisWrapper#Lenny
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100916160559.gf23...@tammy.lan.gsimmons.org
Re: detect ethernet card?
Hi Atu, On Fri, Sep 10, 2010 at 02:42:12AM +0200, Atu wrote: > 00.19.0 Ethernet controller: Intel Corporation 82567LM-3 Gigabit Network > Connection (rev 02) Support for the 82567LM-3 (PCI ID 8086:10de) was added to the e1000e driver in linux-2.6 2.6.26-25, which is part of the recent[1] Debian Lenny point release (5.0.6). In your situation, you could either: * Acquire an update CD/DVD[2] and upgrade your system to 5.0.6. * Temporarily use an alternate network device (e.g. supported wireless LAN adapter) in order to communicate with a Debian archive mirror, then upgrade your system to 5.0.6. * Manually acquire the relevant linux-image-2.6.26-2-* package for your system from packages.debian.org[3], transfer and install via dpkg. An interface for this network device should become available once your system is restarted with the updated kernel. Geoff [1] http://www.debian.org/News/2010/20100904 [2] http://www.debian.org/CD/faq/#update-cd [3] http://packages.debian.org/linux-image-2.6.26-2 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100910081021.ga26...@tammy.lan.gsimmons.org
