Linux-Hardware Digest #620, Volume #14 Fri, 13 Apr 01 16:13:10 EDT
Contents:
Re: Supermicro 6010 + (3to4 DIMMS) + RH 7 + 2.4 = HELP!! ("Peter T. Breuer")
Pinout: Serial RJ45 for Barcode Scanners (Karsten Jeppesen)
howto properly access serial devices in Perl or C (Ingo Ciechowski)
Re: Any thoughts on a good Sparc Linux? (Eric P. McCoy)
Re: Audio with Linux (2.4.2/2.2.16) kernel and Asus AV7133 (Peter Christy)
Re: Switchboxes for keyboard, mice, video? (Joeri Sebrechts)
Re: howto properly access serial devices in Perl or C (Michael Meissner)
Re: Switchboxes for keyboard, mice, video? (Eric P. McCoy)
Newbie to Linux with Modem Problems ("Chris Routh")
Re: howto properly access serial devices in Perl or C (Ingo Ciechowski)
Re: Any thoughts on a good Sparc Linux? (freedman)
AHA-2940AU problems on SuSE linux 6.4 (nicholas@don'tspam.innoverity.com)
hdc: lost interrupt ("Colin and Julie Boyan")
Re: Supermicro 6010 + (3to4 DIMMS) + RH 7 + 2.4 = HELP!! (Anonymous)
Re: AHA-2940AU problems on SuSE linux 6.4 (Ingo Ciechowski)
----------------------------------------------------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc
Subject: Re: Supermicro 6010 + (3to4 DIMMS) + RH 7 + 2.4 = HELP!!
Date: Fri, 13 Apr 2001 18:53:12 +0200
In comp.os.linux.misc Peter T. Breuer <[EMAIL PROTECTED]> wrote:
> In comp.os.linux.hardware Anonymous <[EMAIL PROTECTED]> wrote:
>> Thanks for responding Peter. I have some notes on your responses below.
>> "Peter T. Breuer" wrote:
> Define the amount of memory you want to be seen in the boot parameters
> of the kernel, but leave APM off. It is not compatible with SMP.
BTW, you don't need to recompile for this. It's "apm=off" and
"apci=off" as I recall, from pm.txt in 2.4.0's Documentation
dir, and the source.
The BootPrompt HOWTO is being left behind ...
>> These are on-board chipsets.
> Disable it. Onboard stuff is always flakey.
You can also do that with boot params, I think, though I don't know
how .. the code isn't transparant.
Peter
------------------------------
From: [EMAIL PROTECTED] (Karsten Jeppesen)
Crossposted-To:
comp.hardware,comp.sys.ibm.pc.hardware.comm,comp.sys.ibm.pc.hardware.misc,comp.sys.mac.hardware.misc
Subject: Pinout: Serial RJ45 for Barcode Scanners
Date: Fri, 13 Apr 2001 17:27:58 GMT
I have not been able to find this pinout anywhere.
Barcode wands and barcode scanners often comes with RJ45 interface. It is
a RJ45 connector, but it is serial. TTL not fully RS232 though.
It usually includes 5V on one of the pins.
Anybody knows the pinout on that one?
TIA
Karsten
------------------------------
From: Ingo Ciechowski <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.development.apps,comp.os.linux.development.system,de.alt.comm.isdn4linux
Subject: howto properly access serial devices in Perl or C
Date: Fri, 13 Apr 2001 19:28:14 +0200
I'd like to access some serial device on my linux box bidirectionally, but
for some reason don't get connected to the device. Seems as if special
precautions are required...
For now the program should simply output a couple of commands to /dev/modem
(shall later become /dev/ttyI0) and print out all replies on that line.
open (OUT, ">/dev/modem");
open (IN, "</dev/modem");
print OUT "AT+FCLASS=8\n";
### for some reason it already stucks here :-((
print OUT "AT&L*\n";
print OUT "AT&E37*\n";
while(<IN>) {
print $_;
if(/RING/) {
print OUT "ATA\n";
print OUT "AT+VRX\n";
$start = 1;
}
print FILE $_ if($start == 1);
}
Hopefully someone can point me into the right direction?
--
Ingo
[EMAIL PROTECTED]
------------------------------
Subject: Re: Any thoughts on a good Sparc Linux?
From: [EMAIL PROTECTED] (Eric P. McCoy)
Date: 13 Apr 2001 13:34:07 -0400
"User Rdkeys Robert D. Keys" <[EMAIL PROTECTED]> writes:
> Debian requires a floppy install, initially, apparently, since
> I did not find any bootable cd images about, although there seemed to be
> some overseas. Is there a url to an official Debian iso image somewhere?
>From what I understand, Suns are sort of picky about CD sector sizes.
Debian requires you to make your own images, but they provide scripts
which make it easy. You pretty much start the scripts running, wait
for an hour or so, and you've got an ISO. That being said, I'm only
certain that Debian has IA32 ISOs, I have no idea if they have Sparc
ones.
You should also check the various Linux-on-Sparc FAQs for a list of
supported CPUs. Most of the sun4's are, but I think there are a few
exceptions.
--
Eric McCoy <[EMAIL PROTECTED]>
"Knowing that a lot of people across the world with Geocities sites
absolutely despise me is about the only thing that can add a positive
spin to this situation." - Something Awful, 1/11/2001
------------------------------
From: Peter Christy <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup,alt.comp.periphs.mainboard.asus
Subject: Re: Audio with Linux (2.4.2/2.2.16) kernel and Asus AV7133
Date: Fri, 13 Apr 2001 18:47:19 +0100
Reply-To: [EMAIL PROTECTED]
I'm not familiar with that particular motherboard, but from the number I'm
guessing it uses the VIA chipset. Many people have had problems getting the
kernel drivers to work with this chipset. I suggest you use the Alsa
drivers (available from the Alsa project website - can't remember the URL,
but search for alsa on google!)
I'm using the latest beta drivers (0.9.0beta3 ) which have proved perfectly
stable, and work with the VIA / AC97 audio setup better than the "stable"
0.5.x drivers.
There is a good "idiots guide" to setting this all up on the linuxnewbie
website (www.linuxnewbie.org).
--
Pete
[EMAIL PROTECTED]
------------------------------
From: Joeri Sebrechts <[EMAIL PROTECTED]>
Subject: Re: Switchboxes for keyboard, mice, video?
Date: Fri, 13 Apr 2001 18:05:46 GMT
"Keith R. Williams" wrote:
> No son, I'm not. A desktop larger than the display simply
> isn't useful.
Not useful for you. In other cases though ...
For example, it's what has breathed new life into my old 486 laptop. The
laptop has a great tft screen (wide viewing angle, good contrast), but
it's only 640*480. So I ran linux on it and enlarged the desktop size to
800*600.
It was necessary anyway, because redhat's graphical configuration tools
(which I needed way back when I installed linux on there), were bigger
than 640*480, which was a major design flaw.
Time I upgrade the system though. I've learned the ways of debian are
far superior to the poorly designed redhat :-)
------------------------------
Crossposted-To:
comp.os.linux.development.apps,comp.os.linux.development.system,de.alt.comm.isdn4linux
Subject: Re: howto properly access serial devices in Perl or C
From: Michael Meissner <[EMAIL PROTECTED]>
Date: 13 Apr 2001 14:33:17 -0400
Ingo Ciechowski <[EMAIL PROTECTED]> writes:
> I'd like to access some serial device on my linux box bidirectionally, but
> for some reason don't get connected to the device. Seems as if special
> precautions are required...
>
>
> For now the program should simply output a couple of commands to /dev/modem
> (shall later become /dev/ttyI0) and print out all replies on that line.
>
>
>
> open (OUT, ">/dev/modem");
> open (IN, "</dev/modem");
>
> print OUT "AT+FCLASS=8\n";
>
> ### for some reason it already stucks here :-((
>
> print OUT "AT&L*\n";
> print OUT "AT&E37*\n";
>
> while(<IN>) {
> print $_;
> if(/RING/) {
> print OUT "ATA\n";
> print OUT "AT+VRX\n";
> $start = 1;
> }
> print FILE $_ if($start == 1);
> }
>
>
>
> Hopefully someone can point me into the right direction?
The quick answer is open (FILE, "+</dev/modem"). Quoting from the fine
perlfunc man page which details the open function:
open FILEHANDLE,MODE,LIST
open FILEHANDLE,EXPR
open FILEHANDLE
Opens the file whose filename is given by EXPR, and associates it with
FILEHANDLE. If FILEHANDLE is an expression, its value is used as the
name of the real filehandle wanted. (This is considered a symbolic
reference, so `use strict 'refs'' should not be in effect.)
If EXPR is omitted, the scalar variable of the same name as the
FILEHANDLE contains the filename. (Note that lexical variables--those
declared with `my'--will not work for this purpose; so if you're using
`my', specify EXPR in your call to open.) See the perlopentut manpage
for a kinder, gentler explanation of opening files.
If MODE is `'<'' or nothing, the file is opened for input. If MODE is
`'>'', the file is truncated and opened for output, being created if
necessary. If MODE is `'>>'', the file is opened for appending, again
being created if necessary. You can put a `'+'' in front of the `'>''
or `'<'' to indicate that you want both read and write access to the
file; thus `'+<'' is almost always preferred for read/write
updates--the `'+>'' mode would clobber the file first. You can't
usually use either read-write mode for updating textfiles, since they
have variable length records. See the -i switch in the perlrun manpage
for a better approach. The file is created with permissions of `0666'
modified by the process' `umask' value.
These various prefixes correspond to the fopen(3) modes of `'r'',
`'r+'', `'w'', `'w+'', `'a'', and `'a+''.
In the 2-arguments (and 1-argument) form of the call the mode and
filename should be concatenated (in this order), possibly separated by
spaces. It is possible to omit the mode if the mode is `'<''.
If the filename begins with `'|'', the filename is interpreted as a
command to which output is to be piped, and if the filename ends with a
`'|'', the filename is interpreted as a command which pipes output to
us. See the Using open() for IPC entry in the perlipc manpage for more
examples of this. (You are not allowed to `open' to a command that
pipes both in and out, but see the IPC::Open2 manpage, the IPC::Open3
manpage, and the Bidirectional Communication with Another Process entry
in the perlipc manpage for alternatives.)
If MODE is `'|-'', the filename is interpreted as a command to which
output is to be piped, and if MODE is `'-|'', the filename is
interpreted as a command which pipes output to us. In the 2-arguments
(and 1-argument) form one should replace dash (`'-'') with the command.
See the Using open() for IPC entry in the perlipc manpage for more
examples of this. (You are not allowed to `open' to a command that
pipes both in and out, but see the IPC::Open2 manpage, the IPC::Open3
manpage, and the Bidirectional Communication entry in the perlipc
manpage for alternatives.)
In the 2-arguments (and 1-argument) form opening `'-'' opens STDIN and
opening `'>-'' opens STDOUT.
Open returns nonzero upon success, the undefined value otherwise. If
the `open' involved a pipe, the return value happens to be the pid of
the subprocess.
If you're unfortunate enough to be running Perl on a system that
distinguishes between text files and binary files (modern operating
systems don't care), then you should check out the binmode entry
elsewhere in this document for tips for dealing with this. The key
distinction between systems that need `binmode' and those that don't is
their text file formats. Systems like Unix, MacOS, and Plan9, which
delimit lines with a single character, and which encode that character
in C as `"\n"', do not need `binmode'. The rest need it.
When opening a file, it's usually a bad idea to continue normal
execution if the request failed, so `open' is frequently used in
connection with `die'. Even if `die' won't do what you want (say, in a
CGI script, where you want to make a nicely formatted error message
(but there are modules that can help with that problem)) you should
always check the return value from opening a file. The infrequent
exception is when working with an unopened filehandle is actually what
you want to do.
By the way, if you are doing this, you probably want to check out the perl CPAN
function of Expect (from http://www.cpan.org/ and many other sites). To give
you an example of Expect, here is a function that I wrote that I wrote to
control running a benchmark suite on a embedded processor connected via a
serial line.
sub runprog {
my ($pathname) = @_;
my ($exp);
my ($timeout);
if (! open (TTY, "+<$opt_t")) {
print "Could not open $opt_t: $!\n";
return 0;
}
print ":::::::::: ", &short_timestamp (), " Running ", $pathname, "\n";
$exp = Expect->exp_init (\*TTY);
$exp->exp_stty ("raw -echo");
$exp->match_max ($opt_c);
if (defined $opt_l) {
if ($opt_l eq "-") {
$exp->log_user (1);
} else {
$exp->log_file ($opt_l);
}
}
print $exp "\n";
$exp->expect (5, '-re' => 'PMON[>]\s*$') || die "Could not find
monitor\n";
print $exp "g\n";
$exp->expect (5, '-re' => 'TH [+][>]\s*$') || die "$pathname: did
not start\n";
if (defined ($opt_i)) {
open (INPUT, "<$opt_i") || die "$pathname:
$opt_i: $!\n";
while (<INPUT>) {
print $exp $_;
$exp->expect (5, '-re' => 'TH [+][>]\s*$');
}
close (INPUT);
}
print $exp "g\n";
$exp->expect ($opt_s, '-re' => 'TH [+][>]\s*$') || die "$pathname: No
end prompt\n";
print $exp "exit\n";
if ($exp->exp_before () =~ m!Iterations/Sec\s+=\s+([0-9.]+)!) {
print ":::::::::: ", &short_timestamp (), " ", &tbl_commas (sprintf
("%.2f", $1)), " Iterations/second\n";
}
$exp->expect (5, '-re' => 'PMON[>]\s*$') || die "Program did
not finish\n";
close ($exp);
return 1;
}
--
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
------------------------------
Subject: Re: Switchboxes for keyboard, mice, video?
From: [EMAIL PROTECTED] (Eric P. McCoy)
Date: 13 Apr 2001 14:39:06 -0400
Joeri Sebrechts <[EMAIL PROTECTED]> writes:
> Time I upgrade the system though. I've learned the ways of debian are
> far superior to the poorly designed redhat :-)
Preach it, brother!
--
Eric McCoy <[EMAIL PROTECTED]>
"Knowing that a lot of people across the world with Geocities sites
absolutely despise me is about the only thing that can add a positive
spin to this situation." - Something Awful, 1/11/2001
------------------------------
From: "Chris Routh" <[EMAIL PROTECTED]>
Subject: Newbie to Linux with Modem Problems
Date: Fri, 13 Apr 2001 18:41:32 GMT
Hi, I have a Us Robotics model 0460 and it was tested to be compatible with
linux, however I can't get mine to work.. I get a Sorry, Modem doesn't
respond. I'm a newbie to linux and I want to start using it.. but I need to
get the modem working so I can on the net.. I'm running Linux-Mandrake
(Redhat re-compilation) 6.1 and I normally use the KDE inteface.. using KPPP
dialer.. I have many other window systems as well. I am very hardware
capable and can do just about anything in windows, but I'm fairly
"Linux-Stupid". Any help with my modem problems and anything you might have
that I can read to get me more familliar with linux terms and basic
functions would be much appreciated.
P.S.: here is a summary of what I have done so far..
PC: Intel 300mhz Celeron, 64MB Ram, 10GB HD running Windows 98 SE and Linux
Mandrake 6.1
I installed linux on a second partition and am using Boot Magic PQ because I
don't know anything about LILO
I went into the KDE interface as root
I ran KPPP dialer and set up my connection, my modem is set to PnP now but
was set to Com2 IRQ3 orginally
I tested the modem using the button in the dialer and everything checked
out.
I tried dialing and got "Sorry, Modem doesn't respond"
I went back to testing and got "Sorry, Modem doesn't respond" there..
I've tried everything I can figure out how to do.. and can't get it to
work.. also. my manual for my linux distribution doesn't cover modems..
Routhy
Chris Routh
http://www.routhy.net
------------------------------
From: Ingo Ciechowski <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.development.apps,comp.os.linux.development.system,de.alt.comm.isdn4linux
Subject: Re: howto properly access serial devices in Perl or C
Date: Fri, 13 Apr 2001 21:37:29 +0200
On Fri, 13 Apr 2001 20:33:17 +0200, Michael Meissner wrote
(in message <[EMAIL PROTECTED]>):
> open (FILE, "+</dev/modem")
great. this works for /dev/modem - but for whatever reason I didn't get it to
work with /dev/ttyI0 (which is provided by isdn4linix).
any idea?
--
Ingo
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (freedman)
Subject: Re: Any thoughts on a good Sparc Linux?
Date: 13 Apr 2001 18:57:57 GMT
Reply-To: [EMAIL PROTECTED]
I'd recommend OpenBSD 2.8 for the server for sure. Probably also for
the desktop also. The 4c machines are pretty slow --- I'm not sure
you're going to be happy with your desktop if you plan to run X-windows
on it. OpenBSD seems to me to be the fastest Linux port for the 4c
machines --- certainly faster than RH6.2.
======================================================
On 13 Apr 2001 16:02:34 GMT,
Robert D. Keys <[EMAIL PROTECTED]> wrote:
>I am thinking of setting up a couple Linux machines, one a server, and
>one a desktop, using sun4c sparcs. I see in the archives that there
>are sparc distros by SUSE, Debian, Redhat, and Slackware. The last
>Linux I used was the old 0.96 stuff from a long time ago. My background
>is fairly strong in the BSD side of the family on sparc hardware. But,
>I wanted to give Linux a fair shake on this architecture. Can anyone
>suggest a few pros and cons of any of the above distros on sparc hardware?
>
>Slackware and SUSE look pretty good. Redhat I have heard mixed things
>about. Debian requires a floppy install, initially, apparently, since
>I did not find any bootable cd images about, although there seemed to be
>some overseas. Is there a url to an official Debian iso image somewhere?
>
>The desktop will be gui driven, and the server tty driven.
>
>Any thoughts or suggestions as to what works relatively well on sun4c
>hadware are appreciated.
>
>Thanks
>
>Bob
>
--
Dick Freedman
------------------------------
From: nicholas@don'tspam.innoverity.com
Subject: AHA-2940AU problems on SuSE linux 6.4
Date: 13 Apr 2001 19:46:32 GMT
Hello all, I was hopeing that someone could give me some insite into some
weirdness that I'm having.
First off, I"m using the ac7xxx and zftape and all the normal happy
configuration for this device,
but I've been havin some problems the symtoms are as follows:
1. On reboot, if I do not detach my VXA Tape drive, I get the following
message from MT:
/dev/st0 (or /dev/nst0 whichever I am using) is not found
BUT, I can clearly see /dev/st0 with an ls. I am doing this as root.
2. If I have detached my tape drive, and rebooted, and mt can see and
manipulate the device:
e.g. mt -f /dev/st0 rewind
tar cannot talk to it, and hangs. even on a small empty file. I've been using
the following command to test it:
tar cv test > /dev/st0
Any thoughts would be HUGELY appreciated.
TIA
Nick
----- Posted via NewsOne.Net: Free (anonymous) Usenet News via the Web -----
http://newsone.net/ -- Free reading and anonymous posting to 60,000+ groups
NewsOne.Net prohibits users from posting spam. If this or other posts
made through NewsOne.Net violate posting guidelines, email [EMAIL PROTECTED]
------------------------------
From: "Colin and Julie Boyan" <[EMAIL PROTECTED]>
Subject: hdc: lost interrupt
Date: Fri, 13 Apr 2001 20:04:07 GMT
I have been searching all over the place for the solution to this problem. I
have seen the same question asked many times but haven't yet seen an answer
....
I have installed RH7.0 on a PIII-933 with intel 815 chipset.
I have 2x IDE drives on the first controller port and a panasonic CD-ROM by
itself (with the appropriate jumper set) on the second port. I am running
kernel version 2.2.16-22 and looking at the boot messages I see that the
CD-ROM is recognised and configured correctly. I have checked
/proc/interrupts and there does not appear to be any conflict there. I also
tried turning off DMA access to this device but it was already off and
cannot be changed it would seem.
The CD-ROM can be mounted and I can read data off it using dd but it these
operations both take a long time (3-5 minutes to mount) and there is a
stream of hdc: lost interrupt messages in the log.
Can anyone help ??
------------------------------
Date: Fri, 13 Apr 2001 15:04:51 -0500
Crossposted-To: comp.os.linux.misc
Subject: Re: Supermicro 6010 + (3to4 DIMMS) + RH 7 + 2.4 = HELP!!
From: Anonymous <[EMAIL PROTECTED]>
It was the bus speed. Reseting it to 100mhz cleared up all the
problems. As soon as I reset it to 133 it suffered a complete meltdown.
I also implemented your other ideas and rebuilt the kernel to match
it(No USB, no apm among others)((I was already at it when your email
showed)). It booted and configured its self correctly for the first
time ever.
Again thanks for your speedy replies.
Scott ES
BTW, kgcc for everything or just the kernel?
"Peter T. Breuer" wrote:
>
> In comp.os.linux.misc Peter T. Breuer <[EMAIL PROTECTED]> wrote:
> > In comp.os.linux.hardware Anonymous <[EMAIL PROTECTED]> wrote:
> >> Thanks for responding Peter. I have some notes on your responses below.
> >> "Peter T. Breuer" wrote:
> > Define the amount of memory you want to be seen in the boot parameters
> > of the kernel, but leave APM off. It is not compatible with SMP.
>
> BTW, you don't need to recompile for this. It's "apm=off" and
> "apci=off" as I recall, from pm.txt in 2.4.0's Documentation
> dir, and the source.
>
> The BootPrompt HOWTO is being left behind ...
>
> >> These are on-board chipsets.
>
> > Disable it. Onboard stuff is always flakey.
>
> You can also do that with boot params, I think, though I don't know
> how .. the code isn't transparant.
>
> Peter
--
************************************
Scott England-Sullivan
Dir. MIS
InterHost USA, Inc.
901 A South Neil Street
Champaign, IL 61820
W. 217-403-1120
E. [EMAIL PROTECTED]
************************************
--------== Posted Anonymously via Newsfeeds.Com ==-------
Featuring the worlds only Anonymous Usenet Server
-----------== http://www.newsfeeds.com ==----------
------------------------------
From: Ingo Ciechowski <[EMAIL PROTECTED]>
Subject: Re: AHA-2940AU problems on SuSE linux 6.4
Date: Fri, 13 Apr 2001 22:08:18 +0200
On Fri, 13 Apr 2001 21:46:32 +0200, nicholas@don'tspam.innoverity.com wrote
(in message <9b7l2o$ago$[EMAIL PROTECTED]>):
> tar cannot talk to it, and hangs. even on a small empty file. I've been using
> the following command to test it:
> tar cv test > /dev/st0
I made similar experiences with an Adaptec AHA2940 card.
In my case I had a significant increase of input/output errors from the
command "mt status -f /dev/st0"
Few days ago I finally abandoned the Adaptec card. Now I'm using a rather
inexpensive DC-2976UW and never again had to deal with those mysterious
errors...
I'm not sure whether this is an Apdaptec problem, but I made a lot of bad
experiences with them through the last few years. This includes multiple
cards for Macintosh and that 2940.
The effect was always that one or more SCSI devices hung or could not be
found occasionally.
--
Ingo
[EMAIL PROTECTED]
------------------------------
** 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
******************************
