Re: bringing up PCMCIA wireless interface
Dan Christensen wrote:
I've got a PCMCIA wireless card in my laptop, and I'd like to figure
out the Debian way of arranging that it be brought up when the card is
inserted (including on boot). I only use the card on my home network,
which uses WEP.
[...]
Now, I've upgraded to udev 0.079-1, which conflicts with hotplug,
and ifup doesn't seem to get called anymore. I also tried moving
from pcmcia-cs to pcmciautils (version 012-1), and that didn't help.
I'm running a self-compiled 2.6.13.3 kernel.
I also tried ifplugd, but it doesn't run ifup until WEP has been
configured, but I have set things up so that ifup does my WEP
configuration!
Hi Dan,
First of all, just to make sure you did not miss this, it might be
necessary that you include the module for your PCMCIA wireless in
/etc/modules if you have not done so already, as pointed out in
/usr/share/doc/udev/README.Debian.gz. Then you should see a node created
in /dev whenever the card is plugged in, and removed again when you pull
out the card.
If this works you can use udev to run ifup/down when appropriate. (I
have not used this with PCMCIA cards myself, the following is only my
best guess.)
Create a new file in /etc/udev called "local.rules". This file can
contain all your own customizations to udev. Add a line to match your
PCMCIA card, it should probably look something like this:
KERNEL=="eth*", SYSFS{address}=="xx:xx:xx:xx:xx:xx", NAME="wlan0",
PROGRAM="/path/to/your/script"
This has to be on one line, the xx's should be the MAC address of your
PCMCIA card, use only lowercase letters in the hex numbers. This line
matches a device with the kernel name "eth1" or "eth2", etc. and the
specific MAC address. (If the normal device name of the card is not eth*
you have to change the first key accordingly, as described in
/usr/share/doc/udev/writing_udev_rules/index.html) This device is then
assigned the name "wlan0" (or whatever you put there) and you should use
only this identifier at all other places, e.g. in /etc/network/interfaces.
To activate this rule, symlink it in the /etc/udev/rules.d directory.
This symlink should be called "010_local.rules" to make sure it has
priority over the other rules which are already there. (The files are
parsed in lexcial order and the first matching rule "wins".)
/path/to/your/script should point to a short script, for example in
/usr/local/bin/ which gets called whenever the card is plugged in or
pulled out. In the script you can use the $ACTION environmental variable
("add" or "remove") to decide if you do "ifup wlan0" or "ifdown wlan0".
The manpage of udev has more details.
I hope this helps.
Regards,
Florian
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: bringing up PCMCIA wireless interface
Florian Kulzer wrote: [...] /usr/share/doc/udev/README.Debian.gz. Then you should see a node created in /dev whenever the card is plugged in, and removed again when you pull out the card. I just realized that I might be wrong on that, network adapters normally don't show up in /dev. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: bringing up PCMCIA wireless interface
Hello Dan, I've got a PCMCIA wireless card in my laptop, and I'd like to figure out the Debian way of arranging that it be brought up when the card is inserted (including on boot). I only use the card on my home network, which uses WEP. In the old days, I used pcmcia-cs, and /etc/pcmcia/network.opts contained a call to "ifup $1" in start_fn(). In Linux 2.6 usage of pcmcia-cs is deprecated. In my case (D-Link DWL G650+ PCMCIA card) it used to hang laptop occasionally. AFAIK, Linux 2.6 handles PCMCIA devices without additional tools. Then, I switched to using hotplug and put mapping hotplug script grep map wlan0 In my case hotplug service probes for USB, PCI and ISA (ISA PNP) devices. In my laptop I have only USB devices and they are handled properly. Now, I've upgraded to udev 0.079-1, which conflicts with hotplug, and ifup doesn't seem to get called anymore. I also tried moving from pcmcia-cs to pcmciautils (version 012-1), and that didn't help. I'm running a self-compiled 2.6.13.3 kernel. No idea, I never used udev or other dynamic devices filesystem. My working configuration consists of the following elements: - Linux 2.6.14 (patched with suspend2 2.2-rc9) - ndiswrapper 1.5 (there were glitches with rel. 1.6 and 1.7, probably due to pcmcia-cs usage) - ifup/ifdown custom configuration - in the past I used wpa_supplicant, but I gave up in favor of customised ifup/ifdown configuration Best, Chris -- Chris Wilk[EMAIL PROTECTED] Consultant GridwiseTech office/fax: +48 12 294 71 20 * GridwiseTech Globus Grid Training, 18-20 January, Cracow, Poland: --> http://www.gridwisetech.com/globus-toolkit/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: bringing up PCMCIA wireless interface
Krzysztof Wilk <[EMAIL PROTECTED]> writes: > Dan Christensen writes: > >> I've got a PCMCIA wireless card in my laptop, and I'd like to figure >> out the Debian way of arranging that it be brought up when the card is >> inserted (including on boot). I only use the card on my home network, >> which uses WEP. >> In the old days, I used pcmcia-cs, and /etc/pcmcia/network.opts >> contained a call to "ifup $1" in start_fn(). > > In Linux 2.6 usage of pcmcia-cs is deprecated. In my case (D-Link DWL > G650+ PCMCIA card) it used to hang laptop occasionally. > AFAIK, Linux 2.6 handles PCMCIA devices without additional tools. My understanding was that pcmciautils replaces pcmcia-cs. Do you mean that "ifup $DEVICE" is called automatically without *any* additional tools? Not even hotplug? >> Then, I switched to using hotplug and put >> mapping hotplug >> script grep >> map wlan0 > > In my case hotplug service probes for USB, PCI and ISA (ISA PNP) > devices. In my laptop I have only USB devices and they are handled properly. With hotplug installed, ifup is called for me. But my understanding is that hotplug is deprecated with udev replacing it. But without hotplug, ifup is not called. So my question is, using current Debian testing or unstable and udev (which implies no hotplug) how should PCMCIA devices be ifup'd? Dan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Gnome screen shifted up on Dell Inspiron
I've just installed Debian's "Sarge" distribution on a Dell Inspiron 3800 and the display is shifted up by about a quarter of an inch (6mm) so that I only see about half of Gnome's control bar (I don't know it's proper name) at the top of the screen. The keyboard does not have any controls for horizontal/vertical shifts. The computer's user manual does not mention such shifting either. Any ideas on how to fix it? Thanks in advance for any suggestions. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Thinkpad middle mouse button scroll and paste
I was running the xorg-server from experimental that was version 6.9.99.900 that had the patch for middle button scroll and paste functionality for the Thinkpad. However, my recent apt-get upgrade for Sid installed version 6.9.0. Which doesn't seem to have the scroll/paste patch (or at least it no longer works since the upgrade). Did the experimental package not trickle down into unstable with the patch intact? Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: question on IBM-T30
Hi Rich, Rich Macur <[EMAIL PROTECTED]> writes: > > I checked out your web page on your IBM-T30. > We bought a T30 and are having a problem finding a driver for the Matshita > DVD-ROM SR-8177, which is apparently the same DVD-ROM you have. > Do you have any suggestions on where we could get a driver? normally a DVD-ROM doesn't need a special driver, it is a standard IDE device. If you have problems you need to be more specific and post what you did, what did or didn't happen, error messages etc., otherwise people won't be able to help you. Cheers Jürgen -- Jürgen Stuber <[EMAIL PROTECTED]> http://www.jstuber.net/ gnupg key fingerprint = 2767 CA3C 5680 58BA 9A91 23D9 BED6 9A7A AF9E 68B4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Gnome screen shifted up on Dell Inspiron
Mauricio wrote: I've just installed Debian's "Sarge" distribution on a Dell Inspiron 3800 and the display is shifted up by about a quarter of an inch (6mm) so that I only see about half of Gnome's control bar (I don't know it's proper name) at the top of the screen. The keyboard does not have any controls for horizontal/vertical shifts. The computer's user manual does not mention such shifting either. Any ideas on how to fix it? Thanks in advance for any suggestions. Hi Mauricio, You can run xvidtune to shift the screen. It will open a window with "left", "right", "up", "down" buttons. Once you are able to position the screen nicely with it, it can tell you the corresponding ModLine statement. If you copy this into /etc/X11/XF86Config-4 the setting will be permanent for every new start of X (and Gnome). That all being said, these things should be configured automatically nowadays. Therefore I suspect that there is a problem with your X configuration. Someone will probably be able to give you more specific advice on that if you post the following info: 1) the output of the "lspci" command. (i.e. which video card you have) 2) the output of "egrep '\((WW|EE)\)' /var/log/XFree86.0.log" (this will show all error messages and warnings of your X server) 3) the contents of your /etc/X11/XF86Config-4 file Regards, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
UPDATE - Good cell phone to use as modem with Debian? cable? bluetooth?
Hi all:
I'm starting a new thread on this since the old one ended up
concentrating on the relative merits of different providers.
Faced with the many decisions regarding phones, cables, bluetooth,
etc... The last thing I needed was the additional set of decisions
that switching providers would add, so I stayed with Verizon. I might
regret it, but I guess they realized that there was nothing preventing
me from jumping ship when I made all the calls seeking information and
they were pretty nice and helpful. Whether the info given was
correct I'll find out soon enough I suspect.
In any case, I ended up getting a Motorola E815 phone. The list of
features is quite impressive and with the Verizon discounts it only
cost me $50. I'm happy with the reception I get as the importance
is quality as a phone first and data second. I had read that the LG
phones tend to drop calls in marginal reception areas.
Given that I knew bluetooth was going to be a long-term proposition
due to Verizon's crippling of OBEX, I decided to get a usb cable
anyway. I got one just like this, from the same vendor.
http://cgi.ebay.com/Motorola-E815-ROKR-V265-V276-A840-USB-Cable-CD_W0QQitemZ5849729915QQcategoryZ35209QQrdZ1QQcmdZViewItem
I specifically bought this because it said "Built in Charge function"
and I knew how important this is to reinitialize the phone if I end up
messing it up. So I get it and surprise! there's no place to plug the
charger into the cable. A note to the seller about this tells me that
the charging occurs from the usb port itself. This sounds strange to
me. I know that (some?) USB interfaces can provide power, but enough to
charge a phone? Have I been ripped off?
So I try it. Upon plugging the phone in two separate computers (a
Thinkpad 600E with USB 1/sarge and a Dell 8600 with USB2/woody) the
phone beeps like this: two ascending tones, 4 ascending tones and two
desceding tones. Is the latter sign of trouble?
On the Thinkpad/sarge/USB1, lsusb doesn't even report the phone. On the
Dell/woody/USB2, the following error messages are output to stderr:
cannot get string descriptor 1, error = Invalid or incomplete multibyte or wide
character(84)
cannot get string descriptor 2, error = Invalid or incomplete multibyte or wide
character(84)
And the relevant output of lsusb is:
Bus 001 Device 003: ID 22b8:2a62 Motorola PCS
Language IDs: none (cannot get min. string descriptor; got len=-1,
error=84:Invalid or incomplete multibyte or wide character)
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass2 Communications
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize064
idVendor 0x22b8 Motorola PCS
idProduct 0x2a62
bcdDevice0.01
iManufacturer 1
iProduct2
iSerial 0
bNumConfigurations 1
cannot get config descriptor 0, Invalid or incomplete multibyte or wide
character (84)
Language IDs: none (cannot get min. string descriptor; got len=-1,
error=84:Invalid or incomplete multibyte or wide character)
Furthermore the hubs report: ("lsusb | grep Power" on the
Dell/woody/USB2)
MaxPower0mA
MaxPower0mA
MaxPower0mA
This seems to me to indicate that the USB hubs are not capable of
providing power and thus my cable is useless for the purpose of
charging while connected. Am I mistaken here?
There are also no apparent serial devices created by plugging in the
phone. This is on woody. I have yet to try sarge/kernel 2.6.8 on the
Dell/USB2.
Finally, there are two apps out there that deal with cell phones:
moto4lin (specifically for motorola phones) and bitpim. At the very
least, I should see the phone as a storage device, the web site says.
BUT! a usb memory key I have, when plugged in reports (partial output):
MaxPower 90mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk (Zip)
So right away, interfaceClass is different. Can someone that knows the
details of the USB protocols tell me if in fact the phone is not
following the standards? shouldn't I see something about the internal
memory reflected as "Mass Storage"?
If the phone were able to charge from the USB port, shouldn't it report
the MaxPower that it could use? What is the maximum power that a USB
hub can provide? I suspect that it would be much less than an empty
battery would need.
So far I haven't tried either application. I would like to know why
nothing at all shows up in the output of lsusb on the thinkpad. I
thought usb 1 and usb 2 were supposed to be somewhat compatible?
So far all this is not very encouraging.
OT: latest NVidia driver not working
Hello, I'm running a Toshiba TE2100 with the GeForce4 420Go GRU, under unstable with a 2.6.14 standard kernel. On the latest upgrade to 2.6.14-2-686 (2.6.14-2-7) I noticed a new Nvidia kernel. I used module assistant to compile it but on loading it would just hang. No response from the keyboard - complete freeze, requiring a power off. Previously I'd used Nvidia *.run drivers, so I downloaded the latest one of those, NVIDIA-Linux-x86-1.0-8178-pkg1.run. It compiled just fine, as had the 1.0.8178 edition from Debian, but with the same result. Many tries and hours later I decided to download the previous NVIDIA-Linux-x86-1.0-7676-pkg1.run. That compiled and works! There would appear to be a problem with this GRU and the latest kernel from NVidia. I use FlightGear for instrument flying, but it is useless with the open source nv driver, far too slow. My machine does require the "IgnoreEDID" option. Regards, Tim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Grub hangs at stage 1.5 with cd drive in thinkpad
Hi Folks,
Some time ago I started having problems with my cd drive in my R40
Thinkpad. Sometimes it would be detected at boot, other times not.
I also started to get hangs at boot time (the thinkpad bios POST screen
and grub loading stage 1.5, hanging for about 30 secs) I thought the drive
was dying so I removed it and the hanging problem disappeared. Anyway,
after a while I found a cheap upgrade and put it in the machine, and
now I am back to having grub hang at stage 1.5. The drive seems to work ok,
(can even boot from it) but there are a few errors in the logs regarding the
drive. Heres a few.
Jan 4 12:30:43 linux kernel: ide1: BM-DMA at 0x1868-0x186f, BIOS
settings: hdc:pio, hdd:pio
Jan 4 12:30:43 linux kernel: hdc: probing with STATUS(0x51) instead of
ALTSTATUS(0x7f)
Jan 4 12:30:43 linux kernel: hdc: _NEC DVD+/-RW ND-6500A, ATAPI
CD/DVD-ROM drive
Jan 4 12:30:43 linux kernel: hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW
drive, 2048kB Cache, DMA
Jan 4 13:05:02 linux kernel: hdc: lost interrupt
Jan 4 13:05:02 linux kernel: hdc: status error: status=0x58
{ DriveReady SeekComplete DataRequest }
Jan 4 13:05:02 linux kernel: hdc: drive not ready for command
Jan 4 13:05:07 linux kernel: hdc: status timeout: status=0xd8 { Busy }
Jan 4 13:05:07 linux kernel: hdc: DMA disabled
Jan 4 13:05:07 linux kernel: hdc: drive not ready for command
Jan 4 13:05:08 linux kernel: hdc: ATAPI reset complete
Jan 4 13:05:25 linux kernel: hdc: lost interrupt
Jan 4 13:05:25 linux kernel: hdc: status error: status=0x58
{ DriveReady SeekComplete DataRequest }
Jan 4 13:05:25 linux kernel: hdc: drive not ready for command
Jan 4 13:05:30 linux kernel: hdc: status timeout: status=0xd8 { Busy }
Jan 4 13:05:30 linux kernel: hdc: drive not ready for command
Jan 4 13:05:30 linux kernel: hdc: ATAPI reset complete
Jan 4 13:05:48 linux kernel: hdc: lost interrupt
Jan 4 13:05:48 linux kernel: hdc: status error: status=0x58
{ DriveReady SeekComplete DataRequest }
Jan 4 13:05:48 linux kernel: hdc: drive not ready for command
Jan 4 13:05:53 linux kernel: hdc: status timeout: status=0xd8 { Busy }
Jan 4 13:05:53 linux kernel: hdc: drive not ready for command
Jan 4 13:05:53 linux kernel: hdc: ATAPI reset complete
Jan 4 13:05:53 linux kernel: hdc: tray open
Jan 4 13:05:53 linux kernel: end_request: I/O error, dev hdc, sector 64
Jan 4 13:05:53 linux kernel: isofs_fill_super: bread failed, dev=hdc,
iso_blknum=16, block=16
Jan 4 13:12:52 linux kernel: ide1: BM-DMA at 0x1868-0x186f, BIOS
settings: hdc:pio, hdd:pio
Jan 4 13:12:52 linux kernel: hdc: probing with STATUS(0x51) instead of
ALTSTATUS(0x7f)
Jan 4 13:12:52 linux kernel: hdc: _NEC DVD+/-RW ND-6500A, ATAPI
CD/DVD-ROM drive
Jan 4 13:12:52 linux kernel: hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW
drive, 2048kB Cache, DMA
Jan 4 13:12:52 linux kernel: hdc: lost interrupt
Jan 4 13:12:52 linux kernel: hdc: status error: status=0x58
{ DriveReady SeekComplete DataRequest }
Jan 4 13:12:52 linux kernel: hdc: drive not ready for command
Jan 4 13:12:52 linux kernel: hdc: status timeout: status=0xd8 { Busy }
Jan 4 13:12:52 linux kernel: hdc: DMA disabled
Jan 4 13:12:52 linux kernel: hdc: drive not ready for command
Jan 4 13:12:52 linux kernel: hdc: ATAPI reset complete
Jan 4 13:49:36 linux kernel: hdc: drive_cmd: status=0x51 { DriveReady
SeekComplete Error }
Jan 4 13:49:36 linux kernel: hdc: drive_cmd: error=0x04
{ AbortedCommand }
Jan 5 06:18:26 linux kernel: ide1: BM-DMA at 0x1868-0x186f, BIOS
settings: hdc:pio, hdd:pio
Jan 5 06:18:26 linux kernel: hdc: probing with STATUS(0x51) instead of
ALTSTATUS(0x7f)
Jan 5 06:18:26 linux kernel: hdc: _NEC DVD+/-RW ND-6500A, ATAPI
CD/DVD-ROM drive
Jan 5 06:18:26 linux kernel: hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW
drive, 2048kB Cache, DMA
Upgraded to the latest bios and controller, still no joy.
I imagine this is probably a hardware problem, as it happens before booting the
kernel
just hoping to try and debug before thinking about buying a new motherboard for
it.
Any ideas to try and debug this welcome..
Regards
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
