[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Sheflug] Dell X200 and Redhat 8.0
OK I've abandoned getting the CD-RW to work for the moment. Next
possible steps are upgrade to 2.4.20 or try SuSE 8.1. I've decided to
have another stab at getting the internal modem to work.
I've signed up to virgin.net to see if that made a difference and whilst
I got a different response when trying to connect via minicom, the
ultimate error was the same NO CARRIER.
Here are some screen dumps from minicom. The first is /var/log/messages
after insmod -f pctel and insmod -f ptserial. The second is an attempt
to connect to virgin.net and the second, freeserve no ties.
Feb 1 12:16:28 localhost kernel: AC97 modem device found: devnum =
8000FE00, de
vid = 8086/2486
Feb 1 12:16:28 localhost kernel: iobase_0=0x8800,
iobase_1=0x8c00,irq=10
Feb 1 12:16:28 localhost kernel: PCTel driver version 0.9.5
[5.05c-4.27.215 (09
-14-2001)] (MR) (2002-01-31) with MANY_PORTS SHARE_IRQ SERIAL_PCI
AUDIO_ROUTING[
INTEL] enabled.
Feb 1 12:16:28 localhost kernel: PCTel driver built on [Linux 2.4.18-14
i686 i6
86 "2.4.18-14 <132114>"] with gcc-gcc (GCC) 3.2 20020903 (Red Hat Linux
8.0 3.2-
7).
Feb 1 12:16:28 localhost kernel: ttyS15 at 0x8800 (irq = 10) is a PCTel
Feb 1 12:16:28 localhost kernel: PCI: Found IRQ 10 for device 00:1f.6
Feb 1 12:16:28 localhost kernel: PCI: Sharing IRQ 10 with 00:1f.3
Feb 1 12:16:28 localhost kernel: PCI: Sharing IRQ 10 with 00:1f.5
Minicom output
Welcome to minicom 2.00.0
OPTIONS: History Buffer, F-key Macros, Search History Buffer, I18n
Compiled on Jun 23 2002, 16:41:20.
Press CTRL-A Z for help on special keys
AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0
OK
ATDT08454550280
CONNECT 46666
Virgin EDI-CVX1-A login: nicola.richmond
password:
Exiting shell, and starting PPP session.
~.}#@!}!}!} }8}!}$}%\}"}&} }*} } }%}&FGwB}'}"}(}"j.~~.}# [at] !}!}"}
}8}!}$}%\}"}&} ~
NO CARRIER
Welcome to minicom 2.00.0
OPTIONS: History Buffer, F-key Macros, Search History Buffer, I18n
Compiled on Jun 23 2002, 16:41:20.
Press CTRL-A Z for help on special keys
AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0
OK
ATDT08450796699
CONNECT 46666
User Access Verification
login: rrmedia.fsnet.co.uk
Password:
Entering PPP mode.
Async interface address is unnumbered (FastEthernet0)
Your IP address is 62.137.6.164. MTU is 1500 bytes
~?}#.!}!k} )}"}&} }*} } }%}&k
U?}'}"}(}"}1}$}%?}3}1}!FREE-MULTILINK}+.~~?}#.!}!~NO CARRIER
]Alex Hudson wrote:
>
> Hi Nicola,
>
> Not sure how much use this will be to you, but anyway:
>
> On Sun, 2003-02-02 at 14:50, Nicola Richmond wrote:
> > I have just acquired a Dell Latitude X200
>
> (can I just say: ooo swanky!)
>
> > to test the modem. I have successfully managed to connect to Freeserve
> > (I get a message like CONNECT 46999) but then shortly afterwards get a
> > NO CARRIER message. I understand that this is a known bug in the driver
> > but that it's believed to be ISP dependent.
>
> That sounds a little odd, but vaguely believable, given it's a software
> modem.
>
> > Does anyone know if
> > freeserve could be the culprit and if so could someone recommend another
> > ISP (I'm currently paying £14/mth for unlimited use).
>
> If you're on an all-you-can-eat, then Freeserve will not be the culprit.
> Connectivity is provisioned via BT, who sell ISPs 'ports' (virtual
> modems) in their exchanges - so, the leg of the trip you're having
> problems with suggests it's a problem interfacing with the exchange. In
> which case, you can swap ISPs all you like and it won't make any
> difference (if you're sticking to all-you-can-eat). However, it might be
> worth trying some of the 0845 free signup ISPs, and see if it does make
> any difference: these types of connections are usually more reliable.
> It's not a solution, but it does at least allow you to figure out where
> the problem lies, and might aid future decisions.
>
> Alternatively, you could try turning the speed on the modem down to a
> 33.6 or something - the driver could be having problems getting enough
> CPU in time to process things, so throttling back a little might make
> the problem go away. I would go all the way back to 14.4 I think; just
> to be as sure as possible.
>
> > ohci1394 and sbp2 amongst others. It seems to recognise that there is a
> > CD drive but I can't mount it.
>
> You seem to be correct:
>
> > Jan 30 12:05:28 localhost /etc/hotplug/ieee1394.agent: Setup sbp2 for
> > IEEE1394 product 0x00065b/0x00609e/0x010483
> > Jan 30 12:05:28 localhost kernel: ieee1394: sbp2: Logged into SBP-2
> > device
> > Jan 30 12:05:28 localhost kernel: ieee1394: sbp2: Node[01:1023]: Max
> > speed [S400] - Max payload [2048]
> > Jan 30 12:05:28 localhost kernel: scsi0 : IEEE-1394 SBP-2 protocol
> > driver (host: ohci1394)
> > <snip>
> > Jan 30 12:07:14 localhost kernel: Attached scsi CD-ROM sr0 at scsi0,
> > channel 0, id 0, lun 0
> > Jan 30 12:07:44 localhost kernel: ieee1394: sbp2: aborting sbp2 command
>
> :eek:
>
> > Jan 30 12:07:44 localhost kernel: Mode Sense 00 2a 00 80 00
> > Jan 30 12:07:54 localhost kernel: ieee1394: sbp2: aborting sbp2 command
> > Jan 30 12:07:54 localhost kernel: Test Unit Ready 00 00 00 00 00
> > Jan 30 12:07:54 localhost kernel: ieee1394: sbp2: reset requested
> > Jan 30 12:07:54 localhost kernel: ieee1394: sbp2: Generating IEEE-1394
> > bus reset
> > Jan 30 12:07:54 localhost kernel: ieee1394: sbp2: reset requested
> > Jan 30 12:07:54 localhost kernel: ieee1394: sbp2: Generating IEEE-1394
> > bus reset
> > Jan 30 12:07:59 localhost kernel: scsi: device set offline - not ready
> > or command retry failed after bus reset: host 0 channel 0 id 0 lun 0
>
> There's the reason right there; the system is having trouble talking to
> the drive. I have seen similar message on the lkml, but they appear to
> be related to work on the VM (i.e., related to the rmap patches and
> their effect on the disk elevator/write scheduler). But, I don't think
> that has any bearing on your problem. You would try switching to a
> different kernel if you have any variations available, but I'm not
> convinced that would make much difference.
>
> Is the hardware definitely known working? If you can at all, that would
> be the thing to determine first, if you haven't already - it's not the
> most likely solution, but it is something easy to check before doing
> anything else.
>
> There are some parameters to the sbp2 module which you might try;
> sbp2_serialize_io=1 and sbp2_max_speed=0 being potentially the most
> interesting settings. The former looks most juicy, I would give that a
> go on it's own.
>
> Hope this helps some.
>
> Cheers,
>
> Alex.
>
> ------------------------------------------------------------------------
> Name: signature.asc
> signature.asc Type: application/pgp-signature
> Description: This is a digitally signed message part
--
Dr. Nicola J. Richmond,
Department of Information Studies,
University of Sheffield,
Regent Court, 211 Portobello Street, S1 4DP.
___________________________________________________________________
Sheffield Linux User's Group -
http://www.sheflug.co.uk/mailfaq.html
GNU the choice of a complete generation.