Linux-Hardware Digest #337, Volume #14 Tue, 13 Feb 01 06:13:04 EST
Contents:
Re: USR 3CP5610A - Modem won't work (Nader)
Re: Tx attempt prior to association problems with DWL-500 ("Jason T. Linhart")
Re: hedrick's ide patch for 2.2.14 (Joe Pfeiffer)
Re: What's a good AGP 1x video card? (Marada C. Shradrakaii)
Supressing Audio Feedback (Anes Lihovac)
Re: DVD decoder: software vs. hardware (Calvin N.)
Can't delete file (Eric Ho)
Re: Can't delete file (Paul Colquhoun)
kernel 2.4.1 for Iomega ZIP 100 USB drive (Massimo Pinto)
----------------------------------------------------------------------------
From: Nader <[EMAIL PROTECTED]>
Subject: Re: USR 3CP5610A - Modem won't work
Date: Mon, 12 Feb 2001 21:47:03 -0800
I had what sounds like a very similar problem. I corrected it by moving to a
newer kernel that could be patched for UDMA66 support and upgraded the serial
drivers to support PCI IRQ sharing. Until I did that, the UDMA controller
dominated the IRQ and 'serial' did not show up in /proc/interrupts.
Specifically, I went from 2.2.14 to 2.2.16 since 2.2.16 can be easily patched
using the UDMA66 HOW-TO. I then went to serial.sourceforge.net to get
serial.5.05 and added that to the kernel. My modem was always working as COM5
in Windows. It ended up on /dev/tty4 in Linux after adding the new serial
driver.
Warren S Baker III wrote:
> Edward J. Stammer wrote:
>
> > Unfortunately, this modem is reported to not work with any version of
> > Linux that does not have Kernel 2.3 or higher. Unfortunately, there is no
> > current release of Linux that uses Kernel 2.3 or higher. Just wait, and
> > it will be out. I am having the exact same problem. If I find anything,
> > I will let you know what I found.
> >
> > Ed
> >
> >
> > Andy Judge wrote:
> >
> >>
> >> I have the USER 3CP5610A modem on Mnadrake 7.2 and can't make it work.
> >
> > It
> >
> >> shows up in hard drake, but when I try to configure it, hard drake stares
> >> that it can't configure a win. This isn't a win and I have tried the
> >> following based on my /proc/pci:
> >>
> >> <snip>
> >>
> >> Bus 0, device 9, function 0:
> >> Serial controller: Unknown vendor Unknown device (rev 1).
> >> Vendor id=12b9 Device id=1008
> >> Medium devsel. IRQ 9 I/O at 0xdc00 [0xdc01]
> >> </snip>
> >>
> >> setserial /dev/ttyS2 irq 9 port 0xdc00 autoconfig
> >>
> >> setserial /dev/ttyS2 irq 9 port 0xdc00 ^fourport ^auto_irq skip_test
> >> autoconfig spd_vhi
> >>
> >> proc/interrupts yields:
> >> CPU0
> >> 0: 32694 XT-PIC timer
> >> 1: 75 XT-PIC keyboard
> >> 2: 0 XT-PIC cascade
> >> 4: 3 XT-PIC serial
> >> 5: 3365 XT-PIC EMU10K1
> >> 8: 2 XT-PIC rtc
> >> 9: 0 XT-PIC usb-uhci, usb-uhci
> >> 11: 263 XT-PIC eth0
> >> 12: 2313 XT-PIC PS/2 Mouse
> >> 13: 1 XT-PIC fpu
> >> 14: 16095 XT-PIC ide0
> >> 15: 10 XT-PIC ide1
> >> NMI: 0
> >>
> >> Procinfo yeilds:
> >> irq 0: 47053 timer irq 8: 2 rtc
> >> irq 1: 75 keyboard irq 9: 0 usb-uhci,
> >> usb-uhci
> >> irq 2: 0 cascade [4] irq 11: 331 eth0
> >> irq 3: 3 irq 12: 2313 PS/2
> >> Mouse
> >> irq 4: 3 serial irq 13: 1 fpu
> >> irq 5: 3365 EMU10K1 irq 14: 16617 ide0
> >> irq 6: 2 irq 15: 10 ide1
> >>
> >>
> >> Neither setserial commands work. Also, the IRQ appears to be unused by
> >
> > any
> >
> >> other device. proc/interrupts seems to say there is a problem w/
> >> conflicting USB, but I disabled the USB support in the bios and it didn't
> >> help? But doesn't IRQ 9 get re-wired to the 8-bit slot connector in
> >
> > place
> >
> >> of IRQ 2 so 8-bit cards can treat IRQ9 as IRQ 2? Can anyone point me in
> >
> > the
> >
> >> right direction? Thxs.
> >>
> >>
> >> Andy
> >>
> >>
> >>
> >
> >
> >
> > --
> > Posted via CNET Help.com
> > http://www.help.com/
>
> I'm not expert enough to point you in the right direction but I can
> offer encouragement. This modem is NOT a WinModem. I am, as I type this,
> connected to my ISP using a USR/3Com 5610 FaxModem.
>
> 00:03.0 Serial controller:\
> US Robotics/3Com 56K FaxModem Model 5610 (rev 01) (prog-if 02 [16550])
> Subsystem: US Robotics/3Com: Unknown device 00a2
> Flags: medium devsel, IRQ 3
> I/O ports at 2478
>
> I too, initially, had problems configuring this modem. Essentially, I
> used lspci -v to determine the IRQ and port address. That done I had to
> use setserial to make it actually work. As I recall this was relatively
> straight-forward once I remembered to use hex values :-). The command
> line was, in my case, something like...
>
> setserial /dev/ttyS1 uart 16550A port 0x2478 irq 3
>
> At that point the device worked. Naturally, it was necessary to set the
> init process up to execute this during boot up. On my distribution
> (SuSE) that meant enabling the serial script (/sbin/init.d/serial) to
> configure the modem manually. Of course, I did not have any conflicts to
> deal with. Subsequently I did try to add a SCSI card to my system and
> was never able to make it work simulataneously with the modem. It seemed
> to disable the modem (it appeared busy) anytime I enabled the SCSI card.
> I was never able to resolve the conflict and ultimately removed the SCSI
> card. But, bottom line is that this modem card did work but had to be
> manually configured. So, unless your modem is different than mine, there
> is hope.
>
> Warren
------------------------------
Subject: Re: Tx attempt prior to association problems with DWL-500
From: "Jason T. Linhart" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Date: Tue, 13 Feb 2001 05:47:24 GMT
In article <[EMAIL PROTECTED]>, Jason T.
Linhart <[EMAIL PROTECTED]> wrote:
> When I attempt to access the wireless network from Linux I get:
> kernel: p80211knetdev_hard_start_xmit: Tx attempt prior to association,
> frame dropped.
> over and over and no data ever goes across. The light on the card
> blinks fairly rapidly, which is what it does under Windows when I
> misspell the SSID.
After fighting with this for another 12 hours I finally figured it out.
I love a good puzzle, but one paragraph about PCIC_OPTS would have
saved me hours and a link to the mailing list archive in an obvious
place would also have been a life saver.
1) I updated the BIOS to the latest version. It was at Sept 2000, I
updated to Jan 2001. This allowed the cardbus adapter board to get
allocated a PCI interrupt. The Ricoh RL5C475 was now allocated
interrupt 9, but the prism2_cs was still getting interrupt 5. This
turned out to be critical, although I didn't know it at the time. The
symptom changed from card silent to an entire machine hang, complete
lockup of all processes, cntrl-alt-del didn't work, etc. I'm unclear on
what really happened here, the card worked with Windows without the
BIOS update, but the BIOS update turned out to be required to work
under Linux.
2) I set PCIC_OPTS="irq_mode=0". I was getting desperate at this point,
I had seen a suggestion to set irq_mode to 1 on the mailing list, that
didn't work. Then I did a search for documentation of what PCIC_OPTS
were available and what they meant. I couldn't find ANY documentation
on this. So I just started changing it till I found one that worked,
set irq_mode to 0. Good thing it was 0, I wasn't going to have tried 37
or anything like that.
Setting it to zero appears to force PCI mode. Both the Ricoh and the
prism2 were now allocated interrupt 9. This was the big break through,
the light on the card went to solid on, the access point listed the
card as a client. Not quite there yet though, Linux couldn't send any
packets (packets were sent somewhere I guess, they just vanished).
3) Examining ifconfig for wlan0 showed crazy IP address settings. I was
running the /etc/pcmcia/network script that came with pcmcia-cs-3.1.24.
This turned out to be a bad thing, it depends on iwconfig, which
doesn't work with wlan-ng. Lucky for me I had had
kernel-pcmcia-cs-2.2.14-5.0 installed from the original RedHat install.
The /etc/pcmcia/network script that came with it was still present as
/etc/pcmcia/network.O and contained code to use the usual ifup/ifdown
scripts instead of iwconfig and custom code in the new script. The old
one worked perfectly and the link came up!
Lessons learned:
My motherboard, apparently can only safely allocate interrupts 9, 10,
or 11 to PCI cards under Linux. Linux is convinced that it can allocate
other interrupts, and indeed allocating interrupt 5 crashes the
machine, so it does something, but wasn't useful.
There really really needs to be documentation for PCIC_OPTS.
wlan-ng is not fully compatible with pcmcia-cs-3.1.24 (bad
/etc/pcmcia/network script) or kernel-pcmcia-cs-2.2.14-5.0 (my machine
is incompatible old version of cardmgr). I needed to install a mixture
of the two versions.
There really should be a link to one of the mailing list archives at
<http://www.linux-wlan.com/linux-wlan/lists.html>. I used the archive
at <http://www.lifix.fi/extarchive/lwlan/>, but latter I used Google
and it found others.
The symbolic link at /lib/modules/x.y.z/pcmcia/prism2_cs.o causes
problems. I had to either hard link it or modify the card database to
load prism2sta_cs.o directly.
I lucked out in getting the D-Link DWL-500 instead of the Addtron
AWA-100. Everything I could find about them at first indicated that
they were the same. The Addtron was cheaper so I was going to buy it.
Luck for me it was out of stock and I got the D-Link instead, because
other people on the mailing list (which I hadn't seen at first) seem to
say that it doesn't work (uses a PCI-ISA adapter chip instead of a full
Cardbus-PCI bridge chip).
Everything is working now, the universe smiles on my network. Now I'm
off to decipher policy based routing. I want to get load sharing (or at
the very least failover) working between my DSL line and my cable
modem. The DSL line is down at least 15 minutes a day, but the cable
modem is really slow on weekday afternoons. I want everything to
automatically avoid which ever one is not working and distribute
traffic between both of them when they are both working.
Happy happy, joy joy.
Jason
------------------------------
From: Joe Pfeiffer <[EMAIL PROTECTED]>
Subject: Re: hedrick's ide patch for 2.2.14
Date: 12 Feb 2001 22:50:05 -0700
Ekkard Gerlach <[EMAIL PROTECTED]> writes:
> aha1505 ! ). Is there a big difference between IV+ an V ?
That's my impression (though I hasten to add that I say this without
certain knowledge). After it was too late, I did some web searches on
the chipset and found some reviews; I never found a review saying a
motherboard in the veview had any troubles at all, but there seem to
be a lot of comments about early problems with the chipset which are
always All Better on the board being described. One of the more blunt
remarks is at http://www2.anandtech.com/showdoc.html?i=1373:
>Unfortunately, as the K6-3D was eventually released as the K6-2, and
>as VIA?s solution debuted as well, it became clear that the ALi
>solution wasn?t the best overall solution for Super7 platforms.
>Especially when regarding AGP compatibility with some of the newer
>AGP adapters such as NVIDIA's TNT2, the Aladdin V chipset had quite a
>few problems. As support for the platform died down, more and more
>manufacturers turned to VIA for their Super7 chipset and ALi slowly
>faded away from our sights.
Ekkard Gerlach <[EMAIL PROTECTED]> writes:
> Joe Pfeiffer wrote:
> >
> > Ekkard Gerlach <[EMAIL PROTECTED]> writes:
> > >
> > > somebody knows where I can get the ide-patch
> > > (for AliV-Chipset support) for Kernel 2.2.14 ? In
> > > .../kernel/hedrick/ there an no patches
> > > below kernel 2.2.16.
> >
> > My experience was that you should buy a new motherboard -- I made the
> > mistake of getting two AladdinV motherboards (Gigabyte GA-5AX) to run
> > with AMD K6 processors. One wound up in a Windows environment, one in
> > Linux. Neither I on the Linux side, nor my wife on the Windows side,
> > was ever able to get either one of them to run reliably.
>
> I can hope , hope and hope! Okay last try with 2.4.0 .
Good luck!
--
Joseph J. Pfeiffer, Jr., Ph.D. Phone -- (505) 646-1605
Department of Computer Science FAX -- (505) 646-1002
New Mexico State University http://www.cs.nmsu.edu/~pfeiffer
SWNMRSEF: http://www.nmsu.edu/~scifair
------------------------------
From: [EMAIL PROTECTED] (Marada C. Shradrakaii)
Date: 13 Feb 2001 07:20:12 GMT
Subject: Re: What's a good AGP 1x video card?
Have you looked into a Voodoo 3 card? I've used one on a board which IIRC
supports no higher than 2X AGP, but I can't say about 1X. Mine has 16M of
memory and cost about 60USD (OEM packaging). I run a 1800x1440 virtual desktop
at 16bpp.
They're probably in firesale mode with 3Dfx out of business.
--
Marada Coeurfuege Shra'drakaii
Colony name not needed in address.
This post is No. 54 056 in a limited edition of 700 000 000. Certificate of
Authenticity attached.
------------------------------
Date: Tue, 13 Feb 2001 09:41:52 +0100
From: Anes Lihovac <[EMAIL PROTECTED]>
Subject: Supressing Audio Feedback
Hello !
I would like to supress the audio feedback whenn doing microphone
speech input under linux. I know that under Win32 that this can be
done very easily, and I would like to have this option too, under
Linux.
If anyone have an idea, how this could be done, please drop a line.
Thanks in advice and best regards
Anes Lihovac
------------------------------
From: Calvin N. <[EMAIL PROTECTED]>
Subject: Re: DVD decoder: software vs. hardware
Date: Tue, 13 Feb 2001 09:30:18 -0000
Well...
> >> I honestly can't see any advantages of software decoding over a modern
> >> hardware decoder. Unless you just can't stand to have your CPU sit in
> >> an idle loop.
>
> It's a lot easier to get support for a fast general purpose
> CPU than it is for a hardware DVD decoder.
I don't know of too many people who require support concerning their CPU.
Also, even if you are a total DVD newbie (e.g., me), installation and use
of a well-packaged product such as the Sigma Designs Hollywood Plus is
fairly straightforward.
> The price of a good hardware DVD decoder will buy a good chunk
> of extra CPU power that can then be used for other things.
My Hollywood Plus cost $96 Canadian. Not exactly breaking the bank.
Also, if you are serious about watching DVDs on your comp, the quality of
good hardware decoding is a necessity, in my opinion.
Calvin.
--
Posted via CNET Help.com
http://www.help.com/
------------------------------
From: Eric Ho <[EMAIL PROTECTED]>
Subject: Can't delete file
Date: 13 Feb 2001 09:43:36 GMT
Hi,
I am trying to delete a file, but got this error :
bash-2.03# rm plusnode.gif
rm: cannot remove `plusnode.gif': Value too large for defined data type
bash-2.03#
Can someone tell me how to delete it ?
Best Regards,
Eric Ho
------------------------------
From: [EMAIL PROTECTED] (Paul Colquhoun)
Subject: Re: Can't delete file
Reply-To: <[EMAIL PROTECTED]>
Date: Tue, 13 Feb 2001 10:52:54 GMT
On 13 Feb 2001 09:43:36 GMT, Eric Ho <[EMAIL PROTECTED]> wrote:
|Hi,
|
|I am trying to delete a file, but got this error :
|bash-2.03# rm plusnode.gif
|rm: cannot remove `plusnode.gif': Value too large for defined data type
|bash-2.03#
|
|Can someone tell me how to delete it ?
Care to post the output for:
ls -l plusnode.gif
file plusnode.gif
uname -a
This will give people a little nore info to work with in spotting
the potential cause of the problem.
--
Reverend Paul Colquhoun, [EMAIL PROTECTED]
Universal Life Church http://andor.dropbear.id.au/~paulcol
-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-=*=-
xenaphobia: The fear of being beaten to a pulp by
a leather-clad, New Zealand woman.
------------------------------
From: Massimo Pinto <[EMAIL PROTECTED]>
Subject: kernel 2.4.1 for Iomega ZIP 100 USB drive
Date: Tue, 13 Feb 2001 10:52:26 +0000
I have tried to compile the kernel version 2.4.1 with SCSI and USB support
(as modules) to be able to use a Iomega ZIP 100MB USB drive which I have
just bought a few days ago.
The computer is a Toshiba Tecra 520CDT notebook, so I have also inluded
the associated Toshiba Module. After having loaded usb-ohci and
usb-storage, plus the scsi module I have not been able to mount my zip
drive using /dev/sda4. My kernel would reply to me saying that /dev/sda4
has got wrong minor-major number, these are:
ls -l /dev/sda4*
brw-rw---- 1 root disk 8, 4 ago 24 10:00 sda4
I guess these numbers are 8 and 4, but what do these minor/major numbers
mean?
For completeness, I include the output of `dmesg', hopefully someone can
spot the stain and give some hints!
Thanks in advance
Massimo
Linux version 2.4.1 ([EMAIL PROTECTED]) (gcc version 2.96
20000731 (Red Hat Linux 7.0)) #2 mer feb 7 22:36:08 GMT 2001 BIOS-provided
physical RAM map:
BIOS-e820: 000000000009fc00 @ 0000000000000000 (usable)
BIOS-e820: 0000000000000400 @ 000000000009fc00 (reserved)
BIOS-e820: 0000000000010000 @ 00000000000f0000 (reserved)
BIOS-e820: 0000000001f20000 @ 0000000000100000 (usable)
BIOS-e820: 0000000000010000 @ 00000000fffe0000 (reserved)
BIOS-e820: 0000000000010000 @ 00000000ffff0000 (reserved) On node 0
totalpages: 8224 zone(0): 4096 pages. zone(1): 4128 pages. zone(2): 0
pages. Kernel command line: auto BOOT_IMAGE=linux-2.4.1 ro root=301
BOOT_FILE=/boot/vmlinuz-2.4.1 Initializing CPU#0 Detected 165.860 MHz
processor. Console: colour VGA+ 80x25 Calibrating delay loop... 329.31
BogoMIPS Memory: 29836k/32896k available (1218k kernel code, 2672k
reserved, 479k data, 204k init, 0k highmem) Dentry-cache hash table
entries: 8192 (order: 4, 65536 bytes) Buffer-cache hash table entries:
1024 (order: 0, 4096 bytes) Page-cache hash table entries: 16384 (order:
4, 65536 bytes) Inode-cache hash table entries: 4096 (order: 3, 32768
bytes) CPU: Before vendor init, caps: 008001bf 00000000 00000000, vendor =
0 Intel Pentium with F0 0F bug - workaround enabled. CPU: After vendor
init, caps: 008001bf 00000000 00000000 00000000 CPU: After generic, caps:
008001bf 00000000 00000000 00000000 CPU: Common caps: 008001bf 00000000
00000000 00000000 CPU: Intel Pentium MMX stepping 04 Checking 'hlt'
instruction... OK. POSIX conformance testing by UNIFIX PCI: PCI BIOS
revision 2.10 entry at 0xfdce3, last bus=21 PCI: Using configuration type
1 PCI: Probing PCI hardware isapnp: Scanning for Pnp cards... isapnp: No
Plug & Play device found Linux NET4.0 for Linux 2.4 Based upon Swansea
University Computer Society NET3.039 Starting kswapd v1.8 pty: 256 Unix98
ptys configured Toshiba System Managment Mode driver v1.7 22/6/2000 block:
queued sectors max/low 19696kB/6565kB, 64 slots per queue Uniform
Multi-Platform E-IDE driver Revision: 6.31 ide: Assuming 33MHz system bus
speed for PIO modes; override with idebus=xx hda: TOSHIBA MK2103MAV, ATA
DISK drive hdc: TOSHIBA CD-ROM XM-1502BN, ATAPI CD/DVD-ROM drive ide0 at
0x1f0-0x1f7,0x3f6 on irq 14 ide1 at 0x170-0x177,0x376 on irq 15 hda:
4233600 sectors (2168 MB) w/128KiB Cache, CHS=525/128/63 hdc: ATAPI 10X
CD-ROM drive, 128kB Cache Uniform CD-ROM driver Revision: 3.12 Partition
check:
hda: hda1 hda2 < hda5 hda6 hda7 > Floppy drive(s): fd0 is 1.44M FDC 0 is
an 8272A Serial driver version 5.02 (2000-08-09) with MANY_PORTS SHARE_IRQ
SERIAL_PCI ISAPNP enabled ttyS00 at 0x03f8 (irq = 4) is a 16550A ttyS01 at
0x02f8 (irq = 3) is a 16550A Linux agpgart interface v0.99 (c) Jeff
Hartmann agpgart: Maximum main memory to use for agp memory: 4M agpgart:
no supported devices found. [drm] Initialized tdfx 1.0.0 20000928 on minor
63 [drm:radeon_init] *ERROR* Cannot initialize agpgart module. SCSI
subsystem driver Revision: 1.00 request_module[scsi_hostadapter]: Root fs
not mounted es1371: version v0.27 time 21:40:32 Feb 7 2001 Linux PCMCIA
Card Services 3.1.22
options: [pci] [cardbus] [pm]
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 2048 bind 2048)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
ds: no socket drivers loaded!
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 204k freed
Adding Swap: 52376k swap-space (priority -1)
Soundblaster audio driver Copyright (C) by Hannu Savolainen 1993-1996
sb: No ISAPnP cards found, trying standard ones...
SB 3.01 detected OK (220)
SB DSP version is just 3.01 which means that your card is
several years old (8 bit only device) or alternatively the sound driver
is incorrectly configured.
VFS: Disk change detected on device fd(2,0)
--
Massimo Pinto
Ph.D. student
Gray Laboratory Cancer Research Trust
http://www.graylab.ac.uk/usr/pinto
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list by posting to comp.os.linux.hardware.
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Hardware Digest
******************************
