Linmodems Mailing list Archives

	Web archives.linmodems.org

Return-Path: <david@zakar.com>
Mailing-List: contact discuss-help@linmodems.org; run by ezmlm
Delivered-To: mailing list discuss@linmodems.org
Received: (qmail 12513 invoked from network); 3 Oct 2002 15:50:49 -0000
Received: from desk.crynwr.com (65.172.240.34)
  by www.linmodems.org with SMTP; 3 Oct 2002 15:50:49 -0000
Received: (qmail 9283 invoked by uid 501); 3 Oct 2002 15:50:48 -0000
Received: (qmail 5585 invoked from network); 3 Oct 2002 14:16:43 -0000
Received: from host13.the-web-host.com (209.239.38.170)
  by www.linmodems.org with SMTP; 3 Oct 2002 14:16:43 -0000
Received: from dialup-63.215.152.117.dial1.washington1.level3.net (localhost [127.0.0.1])
	by host13.the-web-host.com (8.10.2/8.10.2) with ESMTP id g93EGgr01123
	for <discuss@linmodems.org>; Thu, 3 Oct 2002 10:16:42 -0400
To: discuss@linmodems.org
From: David Zakar <david@zakar.com>
Subject: lt_modem and RedHat 8.0 problem
Reply-To: david@zakar.com
Date: Thu, 3 Oct 2002 10:11:58 -0700
X-Sender: david@zakar.com
X-Originating-Host: dialup-63.215.152.117.dial1.washington1.level3.net [63.215.152.117]; Thu, 3 Oct 2002 14:16:42 GMT
X-Mailer: WebMail Check v2.3.21 (2000-7-19)
X-Browser: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98), JavaScript: On
Message-ID: <jUsT.aNoTheR.mEsSaGe.iD.10336546021118@www.zakar.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

I installed RedHat 8.0 onto my main machine yesterday. No complaints 
with the install, it looks absolutely gorgeous, feels much faster,
and comes with gcc 3.2 (which my university has recently moved to 
for computer science projects, so I needed it). But, it's in the 
last thing there's the issue. All the binary-made drivers on my system 
(in particular, the Vortex2 and ltmodem drivers) promptly broke. 
This is decidedly uncool, especially since I do quite a bit of my 
work online.

I did a normal build_module install, no problems spotted. The drivers 
compile just fine, but upon modprobing lt_modem, modprobe responds 
that it was compiled with gcc 2.X, and since the kernel was done 
with gcc 3.X, this ain't going to work, and it promptly exits. Seeing 
as lt_modem is the proprietary/binary-only part of the driver (presumably),
am I right in seeing this as Lucent/Agere's issue to fix?

As a side note, someone _did_ manage to make Vortex2 cards work in 
Linux again by disassembling the drivers and reassembling them. Quite 
a trick, I must say, and perhaps one we could use with now unsupported 
binary winmodem drivers as well?

-DMZ