Linux-Setup Digest #923, Volume #20 Tue, 27 Mar 01 07:13:08 EST
Contents:
Re: Lilo won't boot on Maxtor 54098H8 (40GB) ("Dirk Kissing")
Re: Check IP address (Glitch)
Re: /etc/modules.conf (Glitch)
Re: Sound Card Problems (Glitch)
Re: uname -r gives incorrect kernel version (M. Buchenrieder)
Re: Lilo won't boot on Maxtor 54098H8 (40GB) ("Eric")
Re: mouse problems ("Ron Nicholls")
Re: Win2k, partitioning, and LILO on Sony Z600TEK ("Shane Ginnane")
help in sendmail ("Findo")
installing linux with solaris (Massimiliano Caovilla)
Re: Lilo won't boot on Maxtor 54098H8 (40GB) ("Trail Attic")
----------------------------------------------------------------------------
From: "Dirk Kissing" <[EMAIL PROTECTED]>
Crossposted-To: nl.comp.os.linux.installatie
Subject: Re: Lilo won't boot on Maxtor 54098H8 (40GB)
Date: Tue, 27 Mar 2001 12:43:04 +0200
Eric,
> how do you plan to boot from hdb?
> is it selected as boot first in the BIOS?
Yep.
> normally a bootchain is floppy; hda; other-bootable-devices
> > vga = normal
> > read-only
> > menu-scheme = Wg:kw:Wg:Wg
>
> what is this?
SuSe menu.
> > image = /boot/vmlinuz
>
> This is the image you want?
> check it again.
Yep.
> > label = linux
> > root = /dev/hdb1
>
> And this is your root? not just /boot?
Yep.
> > initrd = /boot/initrd
>
> Do you need this?
Don't know, put there automatically bij SuSE.
> The main issue is your bootchain.
> make sure it is correct. If there's a hda, and the MBR of hda contains
> old lilo code, you'd get the problems you describe.
> Either choose in the BIOS to boot from hdb, or change the line
> from "boot=/dev/hda" to "boot=/dev/hdb"
>
> And don't forget, run `/sbin/lilo -v -v` afterwards.
I ran only 'lilo', without the params...that could be it?
tnx,
Dirk
------------------------------
Date: Tue, 27 Mar 2001 02:10:25 -0500
From: Glitch <[EMAIL PROTECTED]>
Subject: Re: Check IP address
Patrick F. Clarin wrote:
> Is there a command line to type to see what your IP address and all that
> information is like in windows where you type ipconfig?
ifconfig
the above command display 'config' info for your InterFaces
It can also change settings on the fly thus alleviating the impulse to
reboot that you received while using Windows.
------------------------------
Date: Tue, 27 Mar 2001 03:04:21 -0500
From: Glitch <[EMAIL PROTECTED]>
Subject: Re: /etc/modules.conf
Stephen E. Canell wrote:
> Installed / built 2.4.2 kernel.... modules.conf
> still points to 2.4.0, plus depmod complaining
> about unresolved symbols!
>
> Any ideas how to get it all in sync????
did u do a 'make modules' and a 'make modules_install' after the kernel
was compiled and before you rebooted?
------------------------------
Date: Tue, 27 Mar 2001 03:19:11 -0500
From: Glitch <[EMAIL PROTECTED]>
Subject: Re: Sound Card Problems
Marcio Calixto Cabral wrote:
> Hello there,
>
> I have followed every tutorial, FAQ and other resources but can't make
> my sound card work under linux. I have even bought another one, but
> nothing.
> I always keep getting the message: drive or resource busy.
> How do I check what IRQ number is being used? How do I change it?
>
> Can anybody help me?
>
The output of /proc/interrupts won't matter until you find out the irq
of the sound card so u don't need to show the interrupts output yet.
I use an ISA sound card (ESS1868) so it isn't listed under /proc/pci.
HOwever all my other devices (which are PCI) are listed with their IRQ.
Why your sound card isn't listed with an IRQ is beyond me.
do you have 2 sound cards? if not what is the Cirrus Logic device and
what is the Ensoniq device? Both appear to be sound cards.
by the way, there was NO reason why you had to post the WHOLE output of
/proc/pci. I left it in here so you can see how much unneeded space it
takes up.
Also, since your sound card is a PCI card why are u using
isapnptools???? First, isapnptools is or *ISA* cards. Second, its for
PNP cards. Since no devices were reported I wonder why you even included
the output from that command when it doesn't matter.
bottom line: find out the exact sound card you have (between the
seemingly 2 listed in /proc/pci). After you know which card you have
check ALSA to make sure they support the card. (you have an ALSA driver
loaded below but it is for the Cirrus Logic device, which may be the
wrong one). Also, you should check to see if there is a kernel driver
for your card which would be easier to setup. I fooled around with ALSA
for a while then found out my card is supported within the kernel. I
just have to load the sb module and make some other appropriate drivers
modules as well and I get sound.
> Thank's
>
> Marcio
>
>
> Here is a list of my output:
>
> cat /proc/pci:
>
> PCI devices found:
> Bus 0, device 0, function 0:
> Host bridge: VIA Technologies Unknown device (rev 196).
> Vendor id=1106. Device id=605.
> Medium devsel. Master Capable. No bursts.
> Prefetchable 32 bit memory at 0xfc000000 [0xfc000008].
> Bus 0, device 1, function 0:
> PCI bridge: VIA Technologies VT 82C598 Apollo MVP3 AGP (rev 0).
> Medium devsel. Master Capable. No bursts. Min Gnt=8.
> Bus 0, device 4, function 0:
> ISA bridge: VIA Technologies Unknown device (rev 34).
> Vendor id=1106. Device id=686.
> Medium devsel. Master Capable. No bursts.
> Bus 0, device 4, function 1:
> IDE interface: VIA Technologies VT 82C586 Apollo IDE (rev 16).
> Medium devsel. Fast back-to-back capable. Master Capable.
> Latency=32.
> I/O at 0xd800 [0xd801].
> Bus 0, device 4, function 2:
> USB Controller: VIA Technologies VT 82C586 Apollo USB (rev 16).
> Medium devsel. IRQ 10. Master Capable. Latency=32.
> I/O at 0xd400 [0xd401].
> Bus 0, device 4, function 3:
> USB Controller: VIA Technologies VT 82C586 Apollo USB (rev 16).
> Medium devsel. IRQ 10. Master Capable. Latency=32.
> I/O at 0xd000 [0xd001].
> Bus 0, device 4, function 4:
> Host bridge: VIA Technologies Unknown device (rev 48).
> Vendor id=1106. Device id=3057.
> Medium devsel. Fast back-to-back capable.
> Bus 0, device 9, function 0:
> Multimedia audio controller: Cirrus Logic Unknown device (rev 1).
> Vendor id=1013. Device id=6003.
> Medium devsel. Master Capable. Latency=32. Min Gnt=4.Max
> Lat=24.
> Non-prefetchable 32 bit memory at 0xf8000000 [0xf8000000].
> Non-prefetchable 32 bit memory at 0xf7800000 [0xf7800000].
> Bus 0, device 10, function 0:
> Multimedia audio controller: Ensoniq Unknown device (rev 2).
> Vendor id=1274. Device id=5880.
> Slow devsel. Master Capable. Latency=32. Min Gnt=12.Max
> Lat=128.
> I/O at 0xb800 [0xb801].
> Bus 1, device 0, function 0:
> VGA compatible controller: Matrox Unknown device (rev 130).
> Vendor id=102b. Device id=525.
> Medium devsel. Fast back-to-back capable. IRQ 11. Master
> Capable. Late
> ncy=64. Min Gnt=16.Max Lat=32.
> Prefetchable 32 bit memory at 0xfa000000 [0xfa000008].
> Non-prefetchable 32 bit memory at 0xf9000000 [0xf9000000].
> Non-prefetchable 32 bit memory at 0xf8800000 [0xf8800000].
>
>
> lsipci:
>
>
> 00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 0605 (rev
> c4)
> 00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598 [Apollo MVP3 AGP]
> 00:04.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super] (rev
> 22)
> 00:04.1 IDE interface: VIA Technologies, Inc. VT82C586 IDE [Apollo] (rev
> 10)
> 00:04.2 USB Controller: VIA Technologies, Inc. VT82C586B USB (rev 10)
> 00:04.3 USB Controller: VIA Technologies, Inc. VT82C586B USB (rev 10)
> 00:04.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI]
> (rev 30)
> 00:09.0 Multimedia audio controller: Cirrus Logic CS 4614/22/24
> [CrystalClear SoundFusion Audio Accelerator] (rev 01)
> 00:0a.0 Multimedia audio controller: Ensoniq 5880 AudioPCI (rev 02)
> 01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP
> (rev 82)
>
> cat /proc/interrupt
>
> CPU0
> 0: 33169 XT-PIC timer
> 1: 1586 XT-PIC keyboard
> 2: 0 XT-PIC cascade
> 12: 7238 XT-PIC PS/2 Mouse
> 13: 1 XT-PIC fpu
> 14: 89181 XT-PIC ide0
> 15: 563 XT-PIC ide1
> NMI: 0
> ERR: 0
>
>
> pnpdump:# $Id: pnpdump_main.c,v 1.23 2000/04/19 22:49:44 fox Exp $
> # Release isapnptools-1.22
> #
> # This is free software, see the sources for details.
> # This software has NO WARRANTY, use at your OWN RISK
> #
> # For details of the output file format, see isapnp.conf(5)
> #
> # For latest information and FAQ on isapnp and pnpdump see:
> # http://www.roestock.demon.co.uk/isapnptools/
> #
> # Compiler flags: -DREALTIME -DNEEDSETSCHEDULER -DABORT_ONRESERR
> #
> # Trying port address 0273
> # Trying port address 027b
> # Trying port address 0283
> # Trying port address 028b
> # Trying port address 0293
> # Trying port address 029b
> # Trying port address 02a3
> # Trying port address 02ab
> # Trying port address 02b3
> # Trying port address 02bb
> # Trying port address 02c3
> # Trying port address 02cb
> # Trying port address 02d3
> # Trying port address 02db
> # Trying port address 02e3
> # Trying port address 02eb
> # Trying port address 02f3
> # Trying port address 0303
> # Trying port address 030b
> # Trying port address 0313
> # Trying port address 031b
> # Trying port address 0323
> # Trying port address 032b
> # Trying port address 0333
> # Trying port address 033b
> # Trying port address 0343
> # Trying port address 034b
> # Trying port address 0353
> # Trying port address 035b
> # Trying port address 0363
> # Trying port address 036b
> # Trying port address 0373
> # Trying port address 037b
> # Trying port address 0383
> # Trying port address 038b
> # Trying port address 0393
> # Trying port address 039b
> # Trying port address 03a3
> # Trying port address 03ab
> # Trying port address 03b3
> # Trying port address 03bb
> # Trying port address 03e3
> # Trying port address 03eb
> # Trying port address 03f3
> # No boards found
>
> module.conf:
>
> # --- BEGIN: Generated by ALSACONF, do not edit. ---
> # --- ALSACONF verion 0.4.2 ---
> alias char-major-116 snd
> alias snd-card-0 snd-card-cs461x
> alias char-major-14 soundcore
> alias sound-slot-0 snd-card-0
> alias sound-service-0-0 snd-mixer-oss
> alias sound-service-0-1 snd-seq-oss
> alias sound-service-0-3 snd-pcm-oss
> alias sound-service-0-12 snd-pcm-oss
> options snd snd_major=116 snd_cards_limit=1 snd_device_mode=0666
> snd_device_gid=0 snd_device_uid=0
> options snd-card-cs461x snd_index=0 snd_id=SoundMaker
> snd_dac_frame_size=4 snd_adc_frame_size=4
> # --- END: Generated by ALSACONF, do not edit. ---
------------------------------
From: [EMAIL PROTECTED] (M. Buchenrieder)
Subject: Re: uname -r gives incorrect kernel version
Date: Tue, 27 Mar 2001 06:59:54 GMT
"Mike Ruskai" <[EMAIL PROTECTED]> writes:
[...]
>Thank you for an actual explanation. I never would have guessed that LILO
>ignores the file system. Not exactly a good design.
[...]
A bootloader doesn't know zilch about high-level stuff like
filesystems etc. It's basically just a piece of assembler code that's
supposed to know where the kernel is located on the boot
medium - in abolute figures.
Michael
--
Michael Buchenrieder * [EMAIL PROTECTED] * http://www.muc.de/~mibu
Lumber Cartel Unit #456 (TINLC) & Official Netscum
Note: If you want me to send you email, don't munge your address.
------------------------------
From: "Eric" <[EMAIL PROTECTED]>
Crossposted-To: nl.comp.os.linux.installatie
Subject: Re: Lilo won't boot on Maxtor 54098H8 (40GB)
Date: Tue, 27 Mar 2001 13:36:08 +0200
> > how do you plan to boot from hdb?
> > is it selected as boot first in the BIOS?
>
> Yep.
okay, that's good
> > normally a bootchain is floppy; hda; other-bootable-devices
>
> > > vga = normal
> > > read-only
> > > menu-scheme = Wg:kw:Wg:Wg
> >
> > what is this?
>
> SuSe menu.
let's hope it's nothing weird.
> > > image = /boot/vmlinuz
> >
> > This is the image you want?
> > check it again.
>
> Yep.
>
> > label = linux
> > > root = /dev/hdb1
> >
> > And this is your root? not just /boot?
>
> Yep.
>
> > > initrd = /boot/initrd
> >
> > Do you need this?
>
> Don't know, put there automatically bij SuSE.
>
> > The main issue is your bootchain.
> > make sure it is correct. If there's a hda, and the MBR of hda contains
> > old lilo code, you'd get the problems you describe.
> > Either choose in the BIOS to boot from hdb, or change the line
> > from "boot=/dev/hda" to "boot=/dev/hdb"
> >
> > And don't forget, run `/sbin/lilo -v -v` afterwards.
>
> I ran only 'lilo', without the params...that could be it?
it's a verbose flag, it'll give more info on what happens and why
it might fail. Run it again, with the verbose flags.
Eric
------------------------------
From: "Ron Nicholls" <[EMAIL PROTECTED]>
Subject: Re: mouse problems
Date: Mon, 26 Mar 2001 19:34:50 +1000
Just a thought, some rumour I heard.
Boot up in console mode and run ( as root) "ntsysv" to
disable "gpm" .
This is the console mouse and I heard once it can conflict with
the GUI mouse.
If it fixes the problem you have a conflict and maybe you can live without a
console mouse.
--
-
-
Regards
RonN
Sfw <[EMAIL PROTECTED]> wrote in message
news:99msn4$ijj$[EMAIL PROTECTED]...
> I have installed and re-installed RH7.0 many times, but can't get it to
> work. After typing "startx" I get to the GUI and then can't move around at
> all because the mouse cursor is frozen stiff. I have tried selecting
> different options for mouse during the installation process, but the
result
> is the same.
>
> I am using USB mouse, two buttons with a scroll wheel.
>
> Please tell me what else I can do.
>
> Thanks.
> Sam
>
>
------------------------------
From: "Shane Ginnane" <[EMAIL PROTECTED]>
Subject: Re: Win2k, partitioning, and LILO on Sony Z600TEK
Date: Tue, 27 Mar 2001 21:48:46 +1000
I've got to wonder about all this.
Caveat - I've been doing Linux (*nix) for less than 2 weeks !! ;-)
I have a Toshiba 4600; 20-ish Gig, 4 Gig NTFS (Win2000), 2 Gig VFAT shared,
rest Linux.
Using the 2000 loader, I CANNOT get Linux to boot. And yes I've done the DD
of the boot sector. Screen just goes blank after selecting Linux from the
boot.ini menu. Boot from floppy is fine.
This is RH 7 (plus patches). Other posts have mentioned the "boot code
within 1024" issue. Supposed to have gone away, but I have to wonder ...
Shane ...
"Eric" <[EMAIL PROTECTED]> wrote in message
news:99njsm$cb5$[EMAIL PROTECTED]...
> > OK, the problem is everyone keeps telling me you have to install Linux
> > before the 1024 cylinder in order to get it to work.
>
> You do not.(not with RH7.0 and probably not with the SuSE either)
> Make a bootfloppy just in case something fails.
> You can always boot from floppy (as it never exceeds 1024 cylinders)
> If the installer set up something wrong, boot from floppy and restore it.
>
> If you are really scared, then don't install it. I'm not forcing you to.
>
> > Does that count once you've partitoned the drives? My second partition
> > starts *well above* the 1024 cylinder limit...
>
> Yes it counts, but nowadays it simply doesn't matter anymore.
> It's for older distro's that contained an old LILO.
> The lilo that ships with RH7 is new enough. it will boot without problems.
>
> > Daryl.
> > PS> I jsut know the install on the Sony its tricky and while I'm not too
> > worried about a Win98 install, Win2k has got me sweating bullets as
people
> > seem to deliver mixed reports.
>
> I don't know the sony, (Hey I work for philips, ofcourse I don't know the
> sony :-) )
> But it DOESN'T MATTER.
>
> Install the damn thing, or leave it alone.
>
> Eric
>
>
>
------------------------------
From: "Findo" <[EMAIL PROTECTED]>
Crossposted-To:
aus.computers.linux,comp.os.linux,comp.os.linux.admin,comp.os.linux.questions,alt.comp.linux,linux.redhat
Subject: help in sendmail
Date: Tue, 27 Mar 2001 19:50:37 +0800
Hi, my name is FIndo
I have set the DNS server and I don't know what I have done wrong in
RedHat7. My DNS is ok but I can't recieve mail from the server but can
send the mail out. Please help.
The file of the DNS
@ IN SOA linux.abc.com. root.abc.com. (
20000082101;
199609206;
28800;
7200;
604800;
)
IN NS linux.abc.com.
ABC IN A 213.185.160.218
linux IN A 213.185.160.221
IN MX 10 linux.abc.com.
shop IN A 213.185.160.221
My server host name is linux and I can use shop.abc.com to go to my web
server. But I can't send mail to [EMAIL PROTECTED] Why?
The /etc/mail/local-host-names file
# local-host-names - include all aliases for your machine here.
abc.com
Can anyone tell me what can I do ?
After a few hours I recieve the return mail :
To: <[EMAIL PROTECTED]>
Sent: Friday, March 16, 2001 8:26 PM
Subject: Returned mail: Host unknown (Name server: abc.com: no data
known)
------------------------------
From: Massimiliano Caovilla <[EMAIL PROTECTED]>
Subject: installing linux with solaris
Date: Tue, 27 Mar 2001 11:53:39 GMT
Hello,
I hope I'm not OT, anyway
I have a machine with 8Gb hard drive and solaris in a primary partition
of 4Gb size on /dev/hda. On the same hard disk I want to install linux
on the next 4Gb: so I made a 4Gb extended partition and logical
partitions inside it for /home and so on , with fdisk. My problem is
that redhat's installer (redhat 6.2) founds the solaris partition with
id 82 and takes it for a 4Gb swap partition!
How do I tell it to ignore it, and to not include it in /etc/fstab?
Notice that I have a true swap partition on /dev/hda6, that is also
automatically (but this time correctly) used.
Thanks for any suggestion
Massimiliano
------------------------------
From: "Trail Attic" <[EMAIL PROTECTED]>
Crossposted-To: nl.comp.os.linux.installatie,nl.comp.os.linux.overig
Subject: Re: Lilo won't boot on Maxtor 54098H8 (40GB)
Date: Tue, 27 Mar 2001 12:06:08 GMT
"Eric" <[EMAIL PROTECTED]> wrote in message
news:99pfp5$5p3$[EMAIL PROTECTED]...
> > > All i see when booting is LI
> > >
> > > Linux is installed on /dev/hdb. (within 1024 boundery)
> > > It uses the whole disk and Lilo is written to the MBR.
> > > I tried using the Cylinders, Heads, Sectors params of Lilo, but
nothing
> > > works :-((
> > >
> > > BIOS says CSH: 4982,63,255. Linux also sees this, but not
working.......
> > Looks like your Partition is too big.
> > LiLo does have problems when it tries to boot from such partitions.
> > Unfortunately the only thing that helps is to repartition this disk.
> > Make a small /boot (<= 100mb is enough) Remeber: /boot _must_ be ext2
> > formatted!
>
> 100 MB is enough?
> it's way overkill
> 1 cylinder (approx 16 MB) is enough)
Ben ik het wel mee eens ja.. 100 mb is zonde...
> > you may partiton the rest of the disk as you want. Maybe just one big
> > partiton with mountpoint /
>
> There are some discussions on this topic going on right now.
> Beware what you advise on this topic, or get flamed.
Gaat niet zitten zeiken over kleine dingetjes joh.. met je flamed.. rot
lekker op als je zo graag wilt flamen... En als jij het allemaal zo goed
weet.... ten eerste is dit een NEDERLANDSE nieuwsgroep, en ten tweede is het
ZIJN advies wat hij geeft... Niet de absolute standaard...
Laat mensen alsjeblieft gewoon antwoorden en advies geven... ook al zeggen
ze het naar jouw mening niet perfect.. anderen zijn er wel mee geholpen...
dat moet je niet ontmoedigen.. mafkaas..
Ik treed hierover verder niet met je in discussie..
> For good partitioning advise, read the partitioning howto.
>
> > Install LiLo into the mbr and tell it to boot from you /boot Partition.
> > This should be the first partition on the disk (/dev/hdb1).
> > This is the only thing important! /boot must be inside the 1024 Cyls the
> > rest doesn't matter!
>
> Nor does this matter anymore on most systems
> Upgrade lilo to a version of 21.4.3 or above, and on most
> systems the 1024 cyl. boundary is gone.
>
> Eric
>
Trail.
------------------------------
** 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
******************************
