Linux-Hardware Digest #601, Volume #14 Tue, 10 Apr 01 14:13:10 EDT
Contents:
Re: Spontaneous combustion ("Peter T. Breuer")
Via + Maxtor + kernel 2.4.3 = crash? ("Edwin Lau")
ATA100 on A7V133 with 2 NICs --> problems! ("Chris Dodge")
ATA100 on A7V133 with 2 NICs --> problems! ("Chris Dodge")
Re: Linux modems ([EMAIL PROTECTED])
Re: Linux modems (Michael Meissner)
Re: A Linux emulator for Linux, does this exist? ([EMAIL PROTECTED])
Re: A Linux emulator for Linux, does this exist? (Grant Edwards)
Re: PHP and passwd change (David Griffith)
----------------------------------------------------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: Re: Spontaneous combustion
Crossposted-To: comp.os.linux.misc
Date: Tue, 10 Apr 2001 15:09:31 GMT
In comp.os.linux.hardware Christopher Wong <[EMAIL PROTECTED]> wrote:
> In article <WUEA6.4324$[EMAIL PROTECTED]>, Tauno Voipio wrote:
>>
>>"Christopher Wong" <[EMAIL PROTECTED]> wrote in message
>>news:[EMAIL PROTECTED]...
>>> I wonder if anyone can give me a hint as to how to diagnose and/or fix
>>> my problem. My Red Hat 7 system reboots spontaneously from time to time,
>>> and fsck runs because the filesystem was not cleanly unmounted. There
>>> are usually fsck errors. It is as if someone pressed the reset switch on
>>> the PC. It always happens on some sort of user input: a mouse click,
>>> usually, or a page up keystroke.
> (...)
>>
>>Quite often unexpected hardware resets come from the power supply. Is it
>>*surely* sturdy enough?
> Well, this is not a heavily loaded system. Besides, wouldn't power
> issues be too far removed from user gestures? The system never blows
You can't tell. My machine started rebooting spontaneously while I was
in the states recently! The techs couldn't stop it, so they put the
disk in another machine as a stopgap.
When I started looking for the cause, I got it down to one of four
things: cpu, power supply, memory, motherboard. Then I had the good
luck to develop a test that would take the machine down: cat
/proc/kcore | ssh other machine dd of=/dev/null. You can see that this
doesn't touch disk at all, but it needs a network card to go. But I
knew it wasn't the network card anyway as the machine died every five minutes
both with and without the NIC.
With that test I eliminated the memory and the cpu as the cause (the test
still "succeeded" with them changed. I then changed the power supply.
Same thing. So I changed the motherboard. Test stopped working.
Amazing .. the mobo developed a fault after three years while nobody
was touching it. Gamma rays.
It can be anything. Powe is indeed very likely.
Peter
------------------------------
From: "Edwin Lau" <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.questions,comp.os.linux.development.system,comp.os.linux.misc
Subject: Via + Maxtor + kernel 2.4.3 = crash?
Date: Tue, 10 Apr 2001 15:03:49 GMT
Hi everyone,
I don't know if my case has anything to do with the via chipset problem.
I use an Asus P3V4X motherboard + maxtor 9000 series hd and kernel 2.4.3.
Once in a while (a couple of days, and seems getting more often now), linux
said the harddisk is busy and not ready for command and some i/o errors. and
it just keeps on saying that until a reboot. the strange thing is that the
bios did not recognize the hd if I reboot using the reset botton. only power
off and back on again solved the problem. the problem often happen with I
was using dselect to upgrade the system. it results in huge file system
corruption.
I am also wondering what the status of resiefs, it is in production
state like ext2?
thanx in advance
Edwin Lau
------------------------------
From: "Chris Dodge" <[EMAIL PROTECTED]>
Subject: ATA100 on A7V133 with 2 NICs --> problems!
Date: Tue, 10 Apr 2001 16:19:07 +0100
Hi,
I've recently got a system running using the Asus A7V133 motherboard and
UDMA100 drive (IBM DTLA-307030) attached to the first master channel of the
Promise ATA/100 controller using the 2.2.19 kernel with the latest IDE
patch. Thanks to many of you - see end of post.
The above setup had one network card, the SMC EZCard (SMC1211TX/WL) using
the rtl8139.o driver.
All worked fine until I added a second NIC, exactly the same type as above,
but for some reason adding the second NIC prevents the system from booting.
What seems to happen is that during startup, something (bios, lilo,
kernal????) thinks the HD is no longer on the first master channel of the
ATA100 controller (ide2 --> hde) but has been moved to the second channel
(ide3 --> hdg). As it can't find anything now on hde, it terminates the boot
procedure (see boot logs below).
I've tried moving the NIC cards around in all the different PCI slots, but
this has no effect! Can anyone point me in the right direction???? Why would
the disk be "moved" from ide2 to ide3 simply by adding an extra NIC, and how
could this be prevented??
Thanks a lot for any help.
Chris Dodge
SUCCESSFUL BOOT:
================
PDC20265: IDE controller on PCI bus 00 dev 88
PDC20265: chipset revision 2
PDC20265: not 100%% native mode: will probe irqs later
PDC20265: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode.
PDC20265: FORCING PRIMARY MODE BIT 0x00 -> 0x01 MASTER
PDC20265: FORCING SECONDARY MODE BIT 0x00 -> 0x01 MASTER
ide2: BM-DMA at 0x7800-0x7807, BIOS settings: hde:pio, hdf:DMA
ide3: BM-DMA at 0x7808-0x780f, BIOS settings: hdg:DMA, hdh:DMA
hdc: CREATIVECD-RW RW121032E, ATAPI CDROM drive
hde: IBM-DTLA-307030, ATA DISK drive
ide1 at 0x170-0x177,0x376 on irq 15
ide2 at 0x9000-0x9007,0x8802 on irq 11
hde: IBM-DTLA-307030, 29314MB w/1916kB Cache, CHS=59560/16/63, UDMA(100)
...
etc... goes on to boot fine.
FAILED BOOT
===========
PDC20265: IDE controller on PCI bus 00 dev 88
PDC20265: chipset revision 2
PDC20265: not 100%% native mode: will probe irqs later
PDC20265: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode.
PDC20265: FORCING PRIMARY MODE BIT 0x00 -> 0x01 MASTER
PDC20265: FORCING SECONDARY MODE BIT 0x00 -> 0x01 MASTER
ide3: BM-DMA at 0x7400-0x7407, BIOS settings: hdg:pio, hdh:DMA
ide4: BM-DMA at 0x7408-0x740f, BIOS settings: hdi:DMA, hdj:DMA
hdc: CREATIVECD-RW RW121032E, ATAPI CDROM drive
hdg: IBM-DTLA-307030, ATA DISK drive
ide1 at 0x170-0x177,0x376 on irq 15
ide3 at 0x8800-0x8807,0x8402 on irq 11
hdg: IBM-DTLA-307030, 29314MB w/1916kB Cache, CHS=59560/16/63, UDMA(100)
...
Kernel panic: VFS: Unable to mount root fs on 21:01
Thanks so far to:
Tom Berger - http://www.mandrakeuser.org/docs/hardware/hbits5.html
Aaron Cline - http://www.geocities.com/ender7007/
Michael ?? - http://www.themonsens.org/michaelfamily/a7v_and_mandrake_7.2
------------------------------
From: "Chris Dodge" <[EMAIL PROTECTED]>
Subject: ATA100 on A7V133 with 2 NICs --> problems!
Date: Tue, 10 Apr 2001 16:20:08 +0100
Hi,
I've recently got a system running using the Asus A7V133 motherboard and
UDMA100 drive (IBM DTLA-307030) attached to the first master channel of the
Promise ATA/100 controller using the 2.2.19 kernel with the latest IDE
patch. Thanks to many of you - see end of post.
The above setup had one network card, the SMC EZCard (SMC1211TX/WL) using
the rtl8139.o driver.
All worked fine until I added a second NIC, exactly the same type as above,
but for some reason adding the second NIC prevents the system from booting.
What seems to happen is that during startup, something (bios, lilo,
kernal????) thinks the HD is no longer on the first master channel of the
ATA100 controller (ide2 --> hde) but has been moved to the second channel
(ide3 --> hdg). As it can't find anything now on hde, it terminates the boot
procedure (see boot logs below).
I've tried moving the NIC cards around in all the different PCI slots, but
this has no effect! Can anyone point me in the right direction???? Why would
the disk be "moved" from ide2 to ide3 simply by adding an extra NIC, and how
could this be prevented??
Thanks a lot for any help.
Chris Dodge
SUCCESSFUL BOOT:
================
PDC20265: IDE controller on PCI bus 00 dev 88
PDC20265: chipset revision 2
PDC20265: not 100%% native mode: will probe irqs later
PDC20265: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode.
PDC20265: FORCING PRIMARY MODE BIT 0x00 -> 0x01 MASTER
PDC20265: FORCING SECONDARY MODE BIT 0x00 -> 0x01 MASTER
ide2: BM-DMA at 0x7800-0x7807, BIOS settings: hde:pio, hdf:DMA
ide3: BM-DMA at 0x7808-0x780f, BIOS settings: hdg:DMA, hdh:DMA
hdc: CREATIVECD-RW RW121032E, ATAPI CDROM drive
hde: IBM-DTLA-307030, ATA DISK drive
ide1 at 0x170-0x177,0x376 on irq 15
ide2 at 0x9000-0x9007,0x8802 on irq 11
hde: IBM-DTLA-307030, 29314MB w/1916kB Cache, CHS=59560/16/63, UDMA(100)
...
etc... goes on to boot fine.
FAILED BOOT
===========
PDC20265: IDE controller on PCI bus 00 dev 88
PDC20265: chipset revision 2
PDC20265: not 100%% native mode: will probe irqs later
PDC20265: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode.
PDC20265: FORCING PRIMARY MODE BIT 0x00 -> 0x01 MASTER
PDC20265: FORCING SECONDARY MODE BIT 0x00 -> 0x01 MASTER
ide3: BM-DMA at 0x7400-0x7407, BIOS settings: hdg:pio, hdh:DMA
ide4: BM-DMA at 0x7408-0x740f, BIOS settings: hdi:DMA, hdj:DMA
hdc: CREATIVECD-RW RW121032E, ATAPI CDROM drive
hdg: IBM-DTLA-307030, ATA DISK drive
ide1 at 0x170-0x177,0x376 on irq 15
ide3 at 0x8800-0x8807,0x8402 on irq 11
hdg: IBM-DTLA-307030, 29314MB w/1916kB Cache, CHS=59560/16/63, UDMA(100)
...
Kernel panic: VFS: Unable to mount root fs on 21:01
Thanks so far to:
Tom Berger - http://www.mandrakeuser.org/docs/hardware/hbits5.html
Aaron Cline - http://www.geocities.com/ender7007/
Michael ?? - http://www.themonsens.org/michaelfamily/a7v_and_mandrake_7.2
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Linux modems
Date: Tue, 10 Apr 2001 10:49:08 -0500
US Robotics are great modems, but get an external modem, if your budget allows.
They are more expensive, but can use with other computers you may have.
If you go with an internal modem, get an ISA or at least make sure it is not a
Win modem.
Get a hardaware based modem. These have the controller and/or DSP chip on the
modem
and don't rely on your CPU to process the data and convert from analog to
digital and vice-versa.
Thanks
Mike
William Rivera wrote:
> I am a linux newbie and I would like to know if anyone can recommend a modem
> that works with linux. I have a a system with Win95 and Mandrake 6.1.
> Everything works fine in my system but the modem. A million thanks.
> Bill
------------------------------
Subject: Re: Linux modems
From: Michael Meissner <[EMAIL PROTECTED]>
Date: 10 Apr 2001 12:14:43 -0400
[EMAIL PROTECTED] (Kenneth R�rvik) writes:
> [EMAIL PROTECTED] (William Rivera) wrote in <[EMAIL PROTECTED]>:
>
> >I am a linux newbie and I would like to know if anyone can recommend a
> >modem that works with linux. I have a a system with Win95 and Mandrake
> >6.1. Everything works fine in my system but the modem. A million thanks.
> >Bill
>
> Get an external modem, and stay clear of anything internal :)
Ummm, unless you are running a relatively new release of Linux, you might want
to narrow it down to an external model that uses a serial port to connect with,
and not the newer USB based modems. The 2.4.x kernel supports USB devices, as
well as late 2.2.x kernels (2.2.18, 2.2.19), but earlier kernels did not.
If you do go for a USB modem, here is the readme file that includes supported
models:
Linux ACM driver v0.16
(c) 1999 Vojtech Pavlik <[EMAIL PROTECTED]>
Sponsored by SuSE
============================================================================
0. Disclaimer
~~~~~~~~~~~~~
This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the Free
Software Foundation; either version 2 of the License, or (at your option)
any later version.
This program is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY
or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
more details.
You should have received a copy of the GNU General Public License along
with this program; if not, write to the Free Software Foundation, Inc., 59
Temple Place, Suite 330, Boston, MA 02111-1307 USA
Should you need to contact me, the author, you can do so either by e-mail
- mail your message to <[EMAIL PROTECTED]>, or by paper mail: Vojtech Pavlik,
Ucitelska 1576, Prague 8, 182 00 Czech Republic
For your convenience, the GNU General Public License version 2 is included
in the package: See the file COPYING.
1. Usage
~~~~~~~~
The drivers/usb/acm.c drivers works with USB modems and USB ISDN terminal
adapters that conform to the Universal Serial Bus Communication Device Class
Abstract Control Model (USB CDC ACM) specification.
Many modems do, here is a list of those I know of:
3Com OfficeConnect 56k
3Com Voice FaxModem Pro
3Com Sportster
MultiTech MultiModem 56k
Zoom 2986L FaxModem
Compaq 56k FaxModem
ELSA Microlink 56k
I know of one ISDN TA that does work with the acm driver:
3Com USR ISDN Pro TA
Unfortunately many modems and most ISDN TAs use proprietary interfaces and
thus won't work with this drivers. Check for ACM compliance before buying.
The driver (with devfs) creates these devices in /dev/usb/acm:
crw-r--r-- 1 root root 166, 0 Apr 1 10:49 0
crw-r--r-- 1 root root 166, 1 Apr 1 10:49 1
crw-r--r-- 1 root root 166, 2 Apr 1 10:49 2
And so on, up to 31, with the limit being possible to change in acm.c to up
to 256, so you can use up to 256 USB modems with one computer (you'll need
three USB cards for that, though).
If you don't use devfs, then you can create device nodes with the same
minor/major numbers anywhere you want, but either the above location or
/dev/usb/ttyACM0 is preferred.
To use the modems you need these modules loaded:
usbcore.o
usb-[uo]hci.o or uhci.o
acm.o
After that, the modem[s] should be accessible. You should be able to use
minicom, ppp and mgetty with them.
2. Verifying that it works
~~~~~~~~~~~~~~~~~~~~~~~~~~
The first step would be to check /proc/bus/usb/devices, it should look
like this:
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 0.00
S: Product=USB UHCI Root Hub
S: SerialNumber=6800
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.00 Cls=02(comm.) Sub=00 Prot=00 MxPS= 8 #Cfgs= 2
P: Vendor=04c1 ProdID=008f Rev= 2.07
S: Manufacturer=3Com Inc.
S: Product=3Com U.S. Robotics Pro ISDN TA
S: SerialNumber=UFT53A49BVT7
C: #Ifs= 1 Cfg#= 1 Atr=60 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=acm
E: Ad=85(I) Atr=02(Bulk) MxPS= 64 Ivl= 0ms
E: Ad=04(O) Atr=02(Bulk) MxPS= 64 Ivl= 0ms
E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=128ms
C:* #Ifs= 2 Cfg#= 2 Atr=60 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=02(comm.) Sub=02 Prot=01 Driver=acm
E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=128ms
I: If#= 1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=acm
E: Ad=85(I) Atr=02(Bulk) MxPS= 64 Ivl= 0ms
E: Ad=04(O) Atr=02(Bulk) MxPS= 64 Ivl= 0ms
The presence of these three lines (and the Cls= 'comm' and 'data' classes)
is important, it means it's an ACM device. The Driver=acm means the acm
driver is used for the device. If you see only Cls=ff(vend.) then you're out
of luck, you have a device with vendor specific-interface.
D: Ver= 1.00 Cls=02(comm.) Sub=00 Prot=00 MxPS= 8 #Cfgs= 2
I: If#= 0 Alt= 0 #EPs= 1 Cls=02(comm.) Sub=02 Prot=01 Driver=acm
I: If#= 1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=acm
In the system log you should see:
usb.c: USB new device connect, assigned device number 2
usb.c: kmalloc IF c7691fa0, numif 1
usb.c: kmalloc IF c7b5f3e0, numif 2
usb.c: skipped 4 class/vendor specific interface descriptors
usb.c: new device strings: Mfr=1, Product=2, SerialNumber=3
usb.c: USB device number 2 default language ID 0x409
Manufacturer: 3Com Inc.
Product: 3Com U.S. Robotics Pro ISDN TA
SerialNumber: UFT53A49BVT7
acm.c: probing config 1
acm.c: probing config 2
ttyACM0: USB ACM device
acm.c: acm_control_msg: rq: 0x22 val: 0x0 len: 0x0 result: 0
acm.c: acm_control_msg: rq: 0x20 val: 0x0 len: 0x7 result: 7
usb.c: acm driver claimed interface c7b5f3e0
usb.c: acm driver claimed interface c7b5f3f8
usb.c: acm driver claimed interface c7691fa0
If all this seems to be OK, fire up minicom and set it to talk to the ttyACM
device and try typing 'at'. If it responds with 'OK', then everything is
working.
--
Michael Meissner, Red Hat, Inc. (GCC group)
PMB 198, 174 Littleton Road #3, Westford, Massachusetts 01886, USA
Work: [EMAIL PROTECTED] phone: +1 978-486-9304
Non-work: [EMAIL PROTECTED] fax: +1 978-692-4482
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: A Linux emulator for Linux, does this exist?
Crossposted-To: comp.os.linux.development.system,comp.os.linux.misc
Date: Tue, 10 Apr 2001 17:03:09 GMT
In comp.os.linux.development.system Grant Edwards <[EMAIL PROTECTED]> wrote:
: Yes. You can run multiple instances of Linux on an IBM 390.
Why do I have the feeling that the S/390 isn't exactly in the
price range that the OP was talking about? :)
--
Jeff Gentry [EMAIL PROTECTED] [EMAIL PROTECTED]
SEX DRUGS UNIX
------------------------------
From: [EMAIL PROTECTED] (Grant Edwards)
Crossposted-To: comp.os.linux.development.system,comp.os.linux.misc
Subject: Re: A Linux emulator for Linux, does this exist?
Date: Tue, 10 Apr 2001 17:39:51 GMT
In article <h1HA6.394$[EMAIL PROTECTED]>, [EMAIL PROTECTED] wrote:
>In comp.os.linux.development.system Grant Edwards <[EMAIL PROTECTED]> wrote:
>: Yes. You can run multiple instances of Linux on an IBM 390.
>
>Why do I have the feeling that the S/390 isn't exactly in the
>price range that the OP was talking about? :)
Replacing two PCs with a 390 may not be feasible. It would be
interesting to see an analysis of where the break-even point
is. 50 PC's? 1000 PD's?
--
Grant Edwards grante Yow! I'm ANN LANDERS!! I
at can SHOPLIFT!!
visi.com
------------------------------
From: David Griffith <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.security
Subject: Re: PHP and passwd change
Date: Tue, 10 Apr 2001 18:56:39 +0100
"Colin G." wrote:
> I've developed a basic web-based POP3 client using PHP and Apache. One of
> the features I'd like to implement is to allow a user who is logged into the
> system to change their password. This would, of course, be PHP-based and
> secure. Anyone have any ideas how I might accomplish this?
>
> --
> Colin G.
> coling (at) intrive (dot) com
PHP has a posix_setuid function and then use the backtick or exec()
Problem is AFAIK you need to SUID root the php binary, so it will have to be
CGI, and then you have
a setuid cgi prog running through apache. I think this is too risky but its how
it could be done
Why not get clients to ssh?
David Griffith
------------------------------
** 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
******************************
