Linux-Setup Digest #334, Volume #21 Wed, 30 May 01 12:13:09 EDT
Contents:
Re: What to install for a laptop? (Keith McGavin)
Problem Booting Redhat 7.1 ("Mars")
Re: Via VT82C686 Sound Card (Rod Smith)
Re: Help, I'm trying to find COM2 (KCmaniac)
Re: ADSL and linux ?? (Rod Smith)
Re: Help, I'm trying to find COM2 ("Peter T. Breuer")
Re: Red Hat 7.1 MultiBoot Problem (Lee Merrill)
Strange problem, related to sound and pcmcia (Edward Ned Harvey)
my us robotic--a nobrainer? (Marko P. Milosavljevic)
Strange problem... (Errol Dunlap)
Re: Please help me get my WIN98 back! ("Block Iron & Supply Co - CIS")
Linux PCMCIA problem (Unknown)
Re: tar "append" to tape problen (John Thompson)
Re: configuring the modem (Victor S. Miller)
X configuration ("D.P.Conroy")
Installing RH 7 neighbour table overflow (Jim)
----------------------------------------------------------------------------
From: Keith McGavin <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.hardware,comp.os.linux.help,linux.redhat.install
Subject: Re: What to install for a laptop?
Date: Thu, 31 May 2001 01:16:10 +1200
Hi Liam,
RH6.2 was a stable release and worked well.With RH7.1
you will get the lastest network tools if that matters.
KDE is slow to load but the kde programmes are ideal for
a laptop. Just a matter of whether it crashes, but if memory
is without fault and seated it should run alright.
Usual RH install with KDE is 550M
Definately the best window manager for 16M ram is Windowmaker.
Fast to load up,reliable and you can still run the KDE programmes
with Windowmaker.
Don't forget the libproplist and libwraster libraries that are
also required with the Windowmaker rpms.
http://www.windowmaker.org has info on how to install.
Should you have problems installing RH or Mandrake on the laptop
you should try Slackware 7.1 It installs easily and puts KDE
Windowmaker and networking down on only 290 Meg diskspace.
See the "4mb-laptop" howto for info on Slackware.
regards
Keith
LRW wrote:
>
> Need some advice from experienced people.
> I have an icky 486DX-66 with 16MB RAM and 2GB HD 640x480 laptop.
> I have RedHat 5.0, RH 6.2, and RH 7.1 and Mandrake 6.0.
> What would be a better package for this thing? Latest and greatest, like
> with Windows, is not always a good idea. So I'm leaning toward RH 6.2. But
> if I can't get Xwindows to run anyway, the is there any problem with using
> RH 7.1?
> Speaking of Xwindows, think any desktop will work? I know Gnome and KDE are
> right out (darn it), but what about one of the lesser memory intensive
> desktops?
>
> Thanks for any advice!!
> =)
> Liam
> [EMAIL PROTECTED]
------------------------------
From: "Mars" <[EMAIL PROTECTED]>
Subject: Problem Booting Redhat 7.1
Date: Wed, 30 May 2001 09:05:42 -0400
I just installed Redhat 7.1 on an old P5 166 machine and now have a strange
problem. When I last logged off using "Log Off" from the Gnome menu my
machine went dead. I tried re-booting several times and get the initial
splash screen, but the screen then blanks out and the pc hangs. I had a
similar problem when installing the OS and got around it using the "expert"
install and specifying "linux hdb=cdrom". When I could boot properly and
log on everything seemed to be configured correctly and work fine. Any
ideas/suggestions? Thanks in advance...
Mars
------------------------------
From: [EMAIL PROTECTED] (Rod Smith)
Crossposted-To: comp.os.linux.networking,linux.redhat.install
Subject: Re: Via VT82C686 Sound Card
Date: Wed, 30 May 2001 13:34:25 -0000
Reply-To: [EMAIL PROTECTED]
[Posted and mailed]
In article <9f0bld$ddn$[EMAIL PROTECTED]>,
"<toor>" <[EMAIL PROTECTED]> writes:
> I have a Via VT82C686 Sound Card, and Its not working in Linux. Redhat 7.0
> detects it, but after it detects it, it completly freezes the system. I
> don't know what to do. Do I need to change anything in the BIOS like the
> IRQ's or DMA channel?
I had problems on a notebook in which the 82c686 sound support
conflicted with the USB support. I worked around it (and other problems
with 82c686 sound on other computers) by using the ALSA drivers for
sound (http://www.alsa-project.org). These are more trouble to install
and configure than the standard kernel drivers, but in my experience
they work better. (In fairness, I haven't tried the standard kernel
drivers with the 2.4.x kernels.)
--
Rod Smith, [EMAIL PROTECTED]
http://www.rodsbooks.com
Author of books on Linux & multi-OS configuration
------------------------------
From: KCmaniac <[EMAIL PROTECTED]>
Subject: Re: Help, I'm trying to find COM2
Date: Wed, 30 May 2001 09:42:36 -0400
Thanks for your input, Peter.
> >Use minicom to confirm that /dev/ttyS14 is where the action is.
> >Then use that port.
>
> I wanted to do that but neither minicom nor kermit apparently is part of Debian's
> basic system. I couldn't find them so I couldn't run them. I already said that
> I set up the only two script files that I know of where you stipulate the device
> for using ttyS14. That did not work. According to the reading I have done,
> there are two files /etc/chatscripts/provider and /etc/ppp/peers/provider that
> require information concerning the dial-up process. These two files are so
> unintuitive, its ridiculous. But what do I want for nothing. The install
> process was supposed to configure these files and for all I know it correctly
> did. If COM2 isn't being recongized in the first place, though, I don't think
> nothing will work.
>
> Be precise. What does "ls -l /dev/ttyS14" show you?
>
I don't know, I have not tried that. I really don't see what more it could tell
me. There is a file called /etc/serial.conf, I believe it is. Are you familiar
with this file? Your comment about reading the serial HOWTO probably applies here.
> >No documentation is required for a task as trivial as that! It's a pci
> >device, so requires no configuration other than what the driver
> >supplies. Make the ttyS14 if it's not there already. Lucent needs a
> >special major and minor (as per the lucent docs):
>
Your telling me. That is why I said all this was so unexpected. Why are you
ignoring the part where I have been saying that when I boot my copy of RH it brings
the modem up with no problems and that is the ancient 5.2 version!!!
>Yours should look like that. It's the lucent documentation that comes
>with the lucent windmodem driver that tells you what to do. Please
>read it ... but it strikes me that you could do with a good read of the
>Serial-HOWTO.
What more do I have to read about this specific modem just because I am using
Debian?? Are you saying that lucent's documentation will differentiate between
linux distributions because obviously I know enough to have gotten RH to use this
exact same modem in the exact same slot. It seems I should be able to get Debian
to use it. What difference should it be making at this point in the system, which
is detecting and assigning IRQ's and ports, between these two distributions?? Why
does my RH system detect COM2 and Debian does not?
barney:/usr/oboe/ptb% ls -l /dev/ttyS14
> crw-rw-rw- 1 root 62, 78 Feb 12 2000 /dev/ttyS14
>
If that is what yours looks like then what is it that you are using on that device,
just out of curiousity?
Any body out there know that Debian requires some kind of a nudge to recognize COM2
or maybe more specifically the Lucent WinModem? Is any body out there using a
WinModem on COM2 with Debian?
RLH
------------------------------
From: [EMAIL PROTECTED] (Rod Smith)
Subject: Re: ADSL and linux ??
Date: Wed, 30 May 2001 13:48:38 -0000
Reply-To: [EMAIL PROTECTED]
[Posted and mailed]
In article <[EMAIL PROTECTED]>,
Kjell Andersson <[EMAIL PROTECTED]> writes:
> Hi every one !
> I'm about to get ADSL service at home does anybody know where i can get
> some info on how set my RedHat 7.1 box up to make it work ?
Others have pointed you to Roaring Penguin. This may or may not be
relevant. In terms of Linux compatibility and setup, you need to be
concerned with two factors:
1) Modem interface method. Get an external Ethernet-interfaced modems.
Although I know of one exception for each, internal and
USB-interfaced modems are largely unsupported in Linux.
2) IP address assignment method. Many low-end DSL providers in the
United States now use PPPoE, which is what Roaring Penguin is for.
This usage is *NOT* universal, though, and I've no idea what's
prevalent outside the U.S. Some distributions now ship with PPPoE
support, but I don't know offhand if Red Hat 7.1 is one of these.
Aside from PPPoE, the most common methods are static IP addresses
and DHCP, both of which work just as if you were connecting to a
LAN. This will also be the case if you use an external broadband
router/firewall device.
--
Rod Smith, [EMAIL PROTECTED]
http://www.rodsbooks.com
Author of books on Linux & multi-OS configuration
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: Re: Help, I'm trying to find COM2
Date: Wed, 30 May 2001 16:40:46 +0200
KCmaniac <[EMAIL PROTECTED]> wrote:
> Thanks for your input, Peter.
>> >Use minicom to confirm that /dev/ttyS14 is where the action is.
>> >Then use that port.
>>
>> I wanted to do that but neither minicom nor kermit apparently is part of Debian's
>> basic system. I couldn't find them so I couldn't run them. I already said that
Of course they ARE! Install them (and where did anyone say kermit ...).
I don't know where you get the concept of a "basic system" from! What
your debian system contains is exactly what you choose to put in it, no
more and no less! On my old debian stable distro, minicom is at 1.82.1:
it011:/usr/oboe/ptb% dpkg -l minicom
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==============-==============-============================================
ii minicom 1.82.1-1 Clone of the MS-DOS "Telix" communications
do an "apt-get install minicom" !!
>> Be precise. What does "ls -l /dev/ttyS14" show you?
> I don't know, I have not tried that. I really don't see what more it could tell
Well, try it, and that way you will be able to know and answer! It
would tell you if it exists, for one thing.
> me. There is a file called /etc/serial.conf, I believe it is. Are you familiar
> with this file? Your comment about reading the serial HOWTO probably applies here.
I have never heard of this file. What is it used for? I would suppose
it contains configuration parameters for use by setserial when called
from one of the init.d scripts in your debian setup. Throw it away,
unless you plan on using it for something!
> Your telling me. That is why I said all this was so unexpected. Why are you
> ignoring the part where I have been saying that when I boot my copy of RH it brings
> the modem up with no problems and that is the ancient 5.2 version!!!
I fail to see the relevance. No configuration is required. Just talk
to the modem on port ttyS14. Go ahead! Try it!
>>with the lucent windmodem driver that tells you what to do. Please
>>read it ... but it strikes me that you could do with a good read of the
>>Serial-HOWTO.
> What more do I have to read about this specific modem just because I am using
It is not a modem. It is an analogue device that can be made to funcion
like a modem with sufficient software resources. When the kernel driver
(ltmodem.o) is loaded, it presents a serial interface that can be
accessed by a node with major 62 and minor 78. That's all.
> Debian?? Are you saying that lucent's documentation will differentiate between
> linux distributions because obviously I know enough to have gotten RH to use this
No it will not tell you anything about distros. It will tell you how to
connect to your lucent winmodem, which is what you want to do.
> exact same modem in the exact same slot. It seems I should be able to get Debian
> to use it. What difference should it be making at this point in the system, which
You should indeed, so how about talking to the modem on the port that
it assigns itself, with the device major and device minor that's
appropriate?
> is detecting and assigning IRQ's and ports, between these two distributions?? Why
> does my RH system detect COM2 and Debian does not?
No, neither of them detects anything (possibly - debian certainly doesn't).
In both cases you have to follow the instructions in the lucent documentation.
The winmodem requires a special device node, which you have to make and talk
to. I imagine that in the case of redhat, they simply linked /dev/modem to
this node when you told them you had a winmodem in the setup. You can do
the same for debian, but please don't. The correct way to access serial
devices is via the special device node, not via a link to that node.
> barney:/usr/oboe/ptb% ls -l /dev/ttyS14
>> crw-rw-rw- 1 root 62, 78 Feb 12 2000 /dev/ttyS14
> If that is what yours looks like then what is it that you are using on that device,
> just out of curiousity?
Eh? What do you mean? It's just an access point for the modem. You talk
to it as you would talk to any modem, with minicom, pppd, kppp, wvdial,
seyon, mgetty, etc. etc. etc.
> Any body out there know that Debian requires some kind of a nudge to recognize COM2
> or maybe more specifically the Lucent WinModem? Is any body out there using a
It requires none. And "recognize" is not a word that has any semantics,
by the way! Why don't you just go ahead and talk to /dev/ttyS14, after
making the node? Provided the driver is loaded, that is.
> WinModem on COM2 with Debian?
COM2 does not exist in linux. Lucent winmodems do as I have just spent
condiderable time (and patience, apparently to no avail) telling you
they do.
What kernel are you running? I wasn't even aware that debian came with
an ltmodem package. I certainly don't find one when I look ... mind
telling me the name of the package that contains the driver?
Peter
------------------------------
From: [EMAIL PROTECTED] (Lee Merrill)
Subject: Re: Red Hat 7.1 MultiBoot Problem
Date: 30 May 2001 08:06:11 -0700
A few thoughts:
Are you using the lba32 option with LILO? e.g put a line "lba32" in
your /etc/lilo.conf file.
I had to create a /boot partition with my /boot directory contents
placed there, for Redhat 7.1 to be bootable. This partition had to be
below the cylinder limit that you mentioned.
Are you using the LILO that came with the 7.1 distribution? i.e. the
latest version of LILO.
Lee
------------------------------
From: Edward Ned Harvey <[EMAIL PROTECTED]>
Subject: Strange problem, related to sound and pcmcia
Crossposted-To:
comp.os.linux.hardware,comp.os.linux.help,comp.os.linux.portable,comp.os.linux.questions
Reply-To: [EMAIL PROTECTED]
Date: Wed, 30 May 2001 15:15:50 GMT
I've got a Dell Inspiron 8000 running Mandrake 8.0.
You can get details of my procedure and problem at nedharvey.com but here's
what it's about:
By default, the pcmcia doesn't work on this laptop. If you insert a pcmcia
card, the whole system instantly crashes.
So I download the newest package and install it.
Now, when I reboot, insert the pcmcia card, the system doesn't crash, but
the card doesn't work properly.
Then, I install the package for a second time, and reboot, and the card
works perfectly. ... BUT, the sound gets a little messed up. (Details
below).
Ordinarily, with a problem like this, you'd think that there's a problem
with irq's or something. So to test this theory, I disabled the pcmcia
package entirely. (remove /etc/rc.d/rc5.d/S09pcmcia)
Of course, pcmcia doesn't start, but the sound is unaffected. still messed
up.
This suggests that the problem is not with the pcmcia itself, but with the
installer -- that during the part when it calls depmod or the like, it
changes something for the sound modules. Unfortunately, that's a subject
that I don't fully understand.
Now, the details of what's wrong with the sound:
It can only play one sound at a time. So on startup, the startup sound
plays, and tricks me into thinking that sound works. But then I do
something else, like play a video game, and suddenly it's obvious that it's
messed up.
Finally...
I do keep regular backups of my system, so if anybody has a suggestion for
some files to compare, I have both the before-version and the after-version.
------------------------------
From: [EMAIL PROTECTED] (Marko P. Milosavljevic)
Subject: my us robotic--a nobrainer?
Date: 30 May 2001 08:19:16 -0700
I'm trying to install and use my internal US robotics sportster 33.6
under linux with 2.2.x kernel. I've been using programs like minicom
or yast (suse setup tool) to configure it, but havent even detected
the damn thing. Doesn anyone know if my modem is a winModem, or any
setup tips?
thankx in advance
------------------------------
From: Errol Dunlap <[EMAIL PROTECTED]>
Subject: Strange problem...
Date: Wed, 30 May 2001 10:40:53 -0500
Here is the problem:
Installed Apache - runs fine standalone
Installed Cold Fusion - runs fine standalone
but when trying to run together...no avail.
Opening the .cfm file in ie or netscape starts the cold fusion program
editor instead of actually processing the file.
==========\Errol Dunlap\=============\=================================
------------------------------
From: "Block Iron & Supply Co - CIS" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc,comp.os.linux.redhat,comp.os.linus.hardware
Subject: Re: Please help me get my WIN98 back!
Date: Wed, 30 May 2001 10:40:52 -0500
If you have your Win98 CDROM boot from that when you get to the three
choices choose #2 boot with cdrom support. Then type fdisk /mbr. Also make
sure your BIOS is set to boot from the CDROM drive first.
"Arnulf Norkus" <0003236521380222513204#[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Somphong K schrieb:
>
> > During this Memorial weekend, I installed Redhat 7.1 (Kernel 2.4.2-2)
> > on my PC at home. Win98 is on IDE drive/A and Rh7.1 completely on IDE
> > drive/B. I did not realize at the time that part of linux, such as /boot
> > partition, had to be on drive/A to use LILO.
> >
> > During graphic installation,I was prompted where to put LILO i.e. in MBR
> > or linux drive's boot partition. Unfortunately I decided to avoid
fooling
> > with MBR and opted for the later.
> >
> > The lilo installation ended up with failure. Everything else went fine.
> > I created boot diskette. I then realized I was no longer able to boot
> > Win98. Everybody in my household jumped on me!! My wife wanted to search
> > webs about her stock investment, my kid wanted to play starcraft with
his
> > folks, ....
> >
> > I hoped to restore MBR by executing 'fdisk /MBR' under MSDOS but I was
> > surprised to learn that all my Windows rescue and MSDOS diskettes failed
> > to even boot. PC tried to boot from the floppies but hang after reading/
> > loading a few blocks.
> >
> > When I mounted on to /dev/hda1, I could see that all Win98 directories
> > and files were still intact. I just do not know why drive/A broke when I
> > tried my best < which was obviously not good enough :-( > not to disturb
> > its MBR.
> >
> > I would appreciate any advice that can pull me out of this mess.
> >
> > 1) What corruptions on drive/A and how to restore it??
> >
> > 2) I configured lilo to boot either linux and win98 but the later never
> > came up - it hang just like when I booted off diskettes. Could you
> > offer me a copy of /etc/lilo.conf to compare. My copy is at home.
> >
> > 3) I configured printer OK but not my sound card (Turtle Beach Montogo
II
> > and Altec Lansing 495). sndconfig autoprobe concluded it was Altec
> > ADA305 and mentioned it is not supported by Linux yet. I tried
without
> > probe but there were only 2 Turtle Beach choices and my Montego II
was
> > not ont the list. I tried both and they all ended up in errors.
> >
> > Does it mean I'm out of luck as far as sound card is concerned?
> >
> > 4) Does Linux support HP 6200C scanner?? If affirmative, how?
> >
> > 5) I have MSN connection which I usually use their 'MSN Internet Access'
> > tool to connect. Could and how I connect to MSN from Linux??
> >
> > Please asnwer to my e-mail address. Thanks for kind assistance.
> >
> > Rgds somphong
>
> I had the same problems with various linuxes. Best what helped me was the
> following.
> First: be sure that your computer is set to boot from floppy at bios.
> Next: boot from a bootable (rescue) disk and at the DOS-prompt set "sys
c:",
> after that maybe "fdisk /mbr" to make sure that mbr on boot-disk is
correct.
> Tip: set LILO to a disk and start linux from there.
> Hope to have helped you
> Ulf
>
>
------------------------------
Date: Wed, 30 May 2001 08:43:24 -0700 (PDT)
From: Unknown <Unknown>
Subject: Linux PCMCIA problem
I have a laptop running Redhat 7.0. Until yesterday, all was
well but I needed to recompile the kernel in order to install
FREES/WAN (it was an exercise). The compile and install
wen't well (I guess) but now I can't get on the network.
I don't know where I went wrong but when I do a make xconfig
I see no reference to PCMCIA but it looks as if the pcmcia
module didn't get loaded. When I do a make config in the
pcmcia-cs-3.1.19 directory I get all kinds of errors.
Can someone point me to a solution? Is it an xconfig problem
or a FreeS/WAN problem?
Thanks for any help,
PK
----
Posted via http://www.etin.com - the FREE public USENET portal on the Web
Complete SEARCHING, BROWSING, and POSTING of text and BINARY messages!
------------------------------
From: John Thompson <[EMAIL PROTECTED]>
Subject: Re: tar "append" to tape problen
Date: Wed, 30 May 2001 10:19:05 -0500
Kirill Sapelkin wrote:
> Am not able to append to an archive on tape. Using the command:
> tar cvf /dev/st0 file1
>
> writes the file1 to the tape. It can be seen using the command:
> tar tvf /dev/st0
>
> Using the command:
> tar rvf /dev/st0 file2
> seems to do something, file2 pops up on screen but
> tar tvf /dev/st0
> shows that only file1 is on the tape.
>
> file2 does not seem to be written on /dev/st0
You should use the non-rewinding device nst0 if you want to add
to the tape.
--
-John ([EMAIL PROTECTED])
------------------------------
Subject: Re: configuring the modem
From: [EMAIL PROTECTED] (Victor S. Miller)
Date: Wed, 30 May 2001 15:49:51 GMT
More information:
I'm running RH 7.0 with kernel 2.2.19-7.0.1.
setserial -a /dev/ttyS1 yields
/dev/ttyS1, Line 1, UART: 16550A, Port: 0x02f8, IRQ: 3
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal skip_test
and ls -l /dev/ttyS1
crw-rw---- 1 root uucp 4, 65 Aug 24 2000 /dev/ttyS1
The modem on COM2 (ttyS1) is a USR Sportster 33.6 fax/modem.
wvdialconf can't find it! It works flawlessly in win 98.
Victor
------------------------------
From: "D.P.Conroy" <[EMAIL PROTECTED]>
Subject: X configuration
Date: Wed, 30 May 2001 16:56:12 +0100
I have just installed RedHat 7.1. The install seems to have worked fine
apart from the X configuration. I was wondering if anyone knows how to
configure X for a laptop TFT screen or how to go about it.
Cheers
Darren
------------------------------
From: Jim <[EMAIL PROTECTED]>
Subject: Installing RH 7 neighbour table overflow
Date: Wed, 30 May 2001 16:00:12 GMT
Installing RH 7 neighbour table overflow
I have IBM Pcserver 320, with 133 Mhz Dual CPU, Adaptech series SCSI
card, 4.3 GB Hdd, 128 MB IBM EDO Ram.
I am installing Redhat 7.0 but while POST INSTALLATION my pc stops
responding
( Pressing Ctrl+Alt+F4) it shows message of
"<4> neighbour table overflow "
It is not hanging, mouse, keyboard works but no disk activity, and
status bar of POST installation do not go ahead.
Has anyone seen this before ?
TIA
------------------------------
** 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.setup.
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-Setup Digest
******************************
