Linux-Setup Digest #420, Volume #21 Mon, 11 Jun 01 22:13:12 EDT
Contents:
Re: Thanks Rob Davies for the hdparm info (Dave Uhring)
Lost libc.so.6 (Xiaoqin Qiu)
Sound Module Problems (Rand Simberg)
cdrom_pc_intr ("IT - Auto Parts Manufacturers Co. S/B")
cdrom_pc_intr ("IT - Auto Parts Manufacturers Co. S/B")
Re: LILO stops at LI with IDE & SCSI setup (Ardith Hoyt)
ipchain settings for "soft" router ("Qisheng Pan")
Re: IPMasqerading Setup Still Not Right ("Qisheng Pan")
Re: HELP: Redhat 7.1 install (logs included)
Re: IPMasqerading Setup Still Not Right (Dean Thompson)
Re: Thanks Rob Davies for the hdparm info (Michael Perry)
Re: Sound Module Problems (H.Bruijn)
Re: linux 7.1 install "sup wit dat"?
Selecting screen resolution with GDM / changing res NICELY in GNOME ("Steve
Bougerolle")
----------------------------------------------------------------------------
From: Dave Uhring <[EMAIL PROTECTED]>
Subject: Re: Thanks Rob Davies for the hdparm info
Date: Mon, 11 Jun 2001 18:29:45 -0500
Robert Davies wrote:
> Michael Perry wrote:
>
>> From the posts, I would now agree that a person should go out and find
>> whether disk/file corruption could happen and take reasonable steps to
>> preclude it.
>
> There's a german site with info on BIOS updates, the problem has afflicted
> Win users, but Via have been less than helpful at what PCI parameters
> should be tweaked.
>
> Linus decreed DMA with Via should simply be turned off! Whether the
> chipset is good or not. I returned 2 1GHz Athlon boards before Christmas,
> with KT133, at the time there was nothing about stability problems, but my
> thrash testing caused lockups and crashes. Had to go with PIII and Intel,
> which was a shame :(
>
> The good news is, folk are working on work rounds, so hopefully Via users
> will be better servered, and perhaps a BIOS update and kernel upgrade in
> future will make this safe, with the white and black lists properly
> configured.
>
> Rob
>
There is some other problem involved than just the KT133 chipset. I'm
using MSI K7T Pro2-A MB with Athlon 850 and and IBM-DTLA-307045 HDD and
have had absolutely no problems with the 2.4.X kernels as long as the VIA
chipset support was compiled into the kernel. Now, the 2.2.XX kernels are
another bag of worms.
------------------------------
From: Xiaoqin Qiu <[EMAIL PROTECTED]>
Subject: Lost libc.so.6
Date: Mon, 11 Jun 2001 16:40:02 -0700
Hi,
We have a PC with RedHat 6.2 installed with 2.2.14-5 kernel. The
/lib/libc.so.6 link got removed by accident, but the original file which
it was pointing to is still in the system. Now I cann't do anything,
even recreate the link failed.
How can I get the link back, so the machine can function again?
Thank you very much for your help!
Xiaoqin
------------------------------
From: [EMAIL PROTECTED] (Rand Simberg)
Subject: Sound Module Problems
Date: Mon, 11 Jun 2001 23:51:52 GMT
I've got a cm8338-based sound card that I'm trying to use in my RH6.2
system (running 2.2.19 of my own build). The instructions for the
driver say to run make config or make menuconfig, and "select sound
card (CONFIG_SOUND='m') support, and CMPCI driver
(CONFIG_SOUND_CMPCI='m') as modules."
I don't see these items anywhere in the sound menu of menuconfig. I
can select sound cards support as a module, and in fact the current
kernel already supports that. But none of the driver modules listed
show anything about CMPCI. Also, there are certain things to
configure, and I don't see where I get the opportunity to do that.
Questions. First of all, what are the instructions talking about--why
don't I see the options that it's describing? Second, do I need to
recompile the kernel just to add a specific sound module, if it
already has sound card support? Finally, is there some way that I can
just compile the driver itself and install it manually? I know the
network drivers usually have a compile command at the end of the
source, but this one doesn't...
--
simberg.interglobal.org * 310 372-7963 (CA) 307 739-1296 (Jackson Hole)
interglobal space lines * 307 733-1715 (Fax) http://www.interglobal.org
"Extraordinary launch vehicles require extraordinary markets..."
Replace first . with @ and throw out the "@trash." to email me.
Here's my email address for autospammers: [EMAIL PROTECTED]
------------------------------
From: "IT - Auto Parts Manufacturers Co. S/B" <[EMAIL PROTECTED]>
Subject: cdrom_pc_intr
Date: Tue, 12 Jun 2001 07:56:44 +0800
Hi,
Recently I install RedHat 6.2 and i have the following error. cdrom_pc_intr:
The drive appears confused (ireason=0x1). After this error the pc cannot
boot and continuesly displaying this error. if i remove the cd-rom from the
pc then this error is disappear. wht could me the problem. pls advice.
Regards,
Arulthas.
--
____________________________________________________________________________
_______________________________
Please visit our site at www.apm-automotive.com
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to which they are addressed.
This communication may contain material protected by intellectual property
rights laws. If you are not the intended recipient, be advised that you have
received this email in error and that any use, dissemination, forwarding,
printing, or copying of this email is strictly prohibited. If it has come to
you in error, please notify the sender immediately. You should not copy this
email, disclose its contents to anyone else, or take any action based on it.
------------------------------
From: "IT - Auto Parts Manufacturers Co. S/B" <[EMAIL PROTECTED]>
Subject: cdrom_pc_intr
Date: Tue, 12 Jun 2001 07:58:32 +0800
Reply-To: "IT - Auto Parts Manufacturers Co. S/B" <[EMAIL PROTECTED]>
Hi,
Recently I install RedHat 6.2 and i have the following error. cdrom_pc_intr:
The drive appears confused (ireason=0x1). After this error the pc cannot
boot and continuesly displaying this error. if i remove the cd-rom from the
pc then this error is disappear. wht could me the problem. pls advice.
Regards,
Arulthas.
--
____________________________________________________________________________
_______________________________
Please visit our site at www.apm-automotive.com
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to which they are addressed.
This communication may contain material protected by intellectual property
rights laws. If you are not the intended recipient, be advised that you have
received this email in error and that any use, dissemination, forwarding,
printing, or copying of this email is strictly prohibited. If it has come to
you in error, please notify the sender immediately. You should not copy this
email, disclose its contents to anyone else, or take any action based on it.
------------------------------
From: Ardith Hoyt <[EMAIL PROTECTED]>
Subject: Re: LILO stops at LI with IDE & SCSI setup
Date: Mon, 11 Jun 2001 13:47:35 -0500
Reply-To: [EMAIL PROTECTED]
Robert Davies wrote:
> Ardith Hoyt wrote:
>
>> Robert Davies wrote:
>>
>>>> lilo.conf:
>>>> boot=/dev/sda1
>>>
>>> ^^^^^^^
>>>
>>> You're installing lilo into the partition, not the MBR. Are you using
>>> another boot manager?
>>>
>>> Try boot=/dev/sda, and get your BIOS to boot off that disk as C:.
>>
>> I guess I was under the impression you could boot off the partition if
>> it's bootable flag is toggled.
>
> Only if you have the original MBR, or recreate it with 'fdisk /mbr'.
I get it now. Thanks again,
Ardith
------------------------------
From: "Qisheng Pan" <[EMAIL PROTECTED]>
Crossposted-To:
alt.os.linux,comp.os.linux,comp.os.linux.admin,comp.os.linux.networking,comp.os.linux.redhat,linux.redhat,linux.redhat.misc,comp.os.linux.questions
Subject: ipchain settings for "soft" router
Date: Mon, 11 Jun 2001 17:05:10 -0700
My server/router is running on Redhat linux 7.1 and has Dual NIC (eth0 and
eth1). eth1 connects to a cable modem that provides Internet service. eth0
connects to internal subnetwork. It has worked fine on Windows95 with Sygate
3.1. However, it has problem on linux with ipchains.
Following offical ip-chain-howto and ip-masquerade-howto, I set ipchains as
follows:
(1) Modify /etc/sysconfig/network and change FORWARD_IPV4=false to
FORWARD_IPV4=true
(2) At the end of /etc/rc.d/rc.local, I add the following code:
/sbin/depmod -a
/sbin/modprobe ip_masq_ftp
echo "1" > /proc/sys/net/ipv4/ip_forward
echo "1" > /proc/sys/net/ipv4/ip_always_defrag
# As dynamic IP users of (DHCP) cable modem, I set:
echo "1" > /proc/sys/net/ipv4/ip_dynaddr
/sbin/ipchains -M -S 7200 10 160
# As dynamic IP users of (DHCP) cable modem, I set:
/sbin/ipchains -A input -j ACCEPT -i eth1 -s 0/0 67 -d 0/0 68 -p udp
/sbin/ipchains -P forward DENY
/sbin/ipchains -A forward -i eth1 -s 192.168.10.0/24 -j MASQ
The linux server/router can connect to Internet. PCs on internal subnet can
also ping outside IPs, but they can not visit them by HTTP or Telnet. They
cannot even resolve the name (though I already set DNS in resolv.conf). If I
use IP address directly on netscape, the error message is:
"netscape's network connection was refused by the server
xxx.xxx.xxx.xxx, The server may not be accepting connection
or may be busy. Try connecting again later".
If anyone know what is the problem? Maybe probem come from firewall. But I
don't know how to fix it. Any suggestion is welcome. Thanks.
------------------------------
From: "Qisheng Pan" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.networking
Subject: Re: IPMasqerading Setup Still Not Right
Date: Mon, 11 Jun 2001 17:14:51 -0700
I have the similar setting and similar problem too. With the setting for
DHCP, The subnet computers can ping outside IPs successfully, but they still
cannot access them by browser or telnet. My friend told me maybe my firewall
setting block the connection, but I still don't know how to make it work.
Hope it can be solved.
"Felix Miata" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> With all the help I've gotten here and elsewhere on this subject, plus
> the many HOWTO's on this and related subjects, I had hoped to get this
> figured out long ago. I suspended attempts for several days in order to
> start from scratch with my RHL 6.2 install on machine st21s, spending
> some time doing a custom install in order to get the right combination
> of packages installed and dependencies met in order to do little more
> than operate as my internet connection. Actually my ulterior motive was
> to scrap Gnome in favor of KDE. Anyway, two birds with one stone. Now,
> back where I left off.
>
> My /etc/rc.d/rc.local ends with:
>
> #rc.firewall script - Start IPMASQ and the firewall
> /etc/rc.d/rc.firewall
>
> #This probably belongs somewhere else
> /usr/bin/smbmount file://td91w/c /share/td91w/c
>
> and /etc/rc.d/rc.firewall currently contains only the following:
> #rc.firewall - firewall startup commands
>
> echo 1 > /proc/sys/net/ipv4/ip_forward
> /sbin/ipchains -P forward DENY
> /sbin/ipchains -A forward -s 192.168.0.0/16 -j MASQ
>
> This is currently providing a shared internet connection for to my other
> three machines (except when one of them is booted to Mandrake 7.1, but
> fixing that's reserved as next project. ifconfig looks good, but no
> ping).
>
> Besides improving on the basic security that is mostly missing from the
> current setup (IP-Masquerade-HOWTO.html is open in Netscape right now),
> I have the following problems:
>
> 1-When I first boot, the last startup message prior to the initial login
> prompt used to be 'linuxconf'. Now that I've created
> /etc/rc.d/rc.firewall to replace the previous ipchains entries in
> /etc/rc.d/rc.local, the last message prior to the initial login prompt
> is a password prompt. I've been able to find nothing to explain what
> about those three little startup lines might cause this.
>
> 2-I want to login to st21s via telnet from OS/2 and start and stop the
> ppp connection at will. I don't want a demand setup, as I have Netscape
> querying for new mail every nine minutes in order to maintain a
> connection that might otherwise be dropped by my ISP for lack of
> activity. Wvdial appears to require that the telnet session be kept
> open, and that it be a root access login. I want to dial as an ordinary
> user. The scripts in /etc/sysconfig/network-scripts, supplied here, on
> Usenet, and in the HOWTO's all manage in one way or another to not work.
> Maybe I'm trying too hard and reading too many HOWTO's. Ideally, I could
> set up OS/2 with some sort of non-root scripted telnet login that does
> no more either establish or terminate a connection and then exit.
>
> 3-(not that important right now) I'd like to know why I follow what seem
> to be simple enough Samba directions and still can't see any shared
> Linux resources on either OS/2 or windoze. To get anything to pass from
> Linux, I had to create RW access on a windoze directory and put the
> desired files there with Linux.
>
> All help much appreciated.
> --
> A fool gives full vent to his anger, but a wise man keeps himself under
> control. Proverbs 29:11 NKJV
>
> Felix Miata *** http://mrmazda.members.atlantic.net/
------------------------------
From: <[EMAIL PROTECTED]>
Crossposted-To: linux.redhat,linux.redhat.install
Subject: Re: HELP: Redhat 7.1 install (logs included)
Date: Tue, 12 Jun 2001 00:30:14 -0000
I had similar problem (a number of people are getting it as well). I
almost given up & wanting to try Mandrake 8.0 instead.
However I discovered the workaround by chance.
What I did was to boot up using cdrom.
At the the boot prompt entered the following to perform a text-based
install.
boot: linux text hdc=cdrom
or hdd=cdrom if your cd-rom is the 2nd ide device on the 2nd ide channel.
After that just go through with text mode install.
It'll fail a couple of times stating "not enough space" & throw you back
to the X server video card detection. Just press OK & it'll copy the files
across.
Hope it helps.
Koi
Maarten wrote:
>
>
> Hi,
>
> I posted this question before, but now it has been updated with new log
> information. I really hope this helps.
>
> I wanted to install Linux Redhat 7.1 on my computer, so I saved up some
> money and bought a 'new' 3.2 gb hdd (WD). I downloaded both the ISO files
> and burned them on a CD. So far so good.
>
> CD 1 is bootable and took me to the installation menu. Keyboard and Mouse
> detected (cordless). I partitioned linux using the disk druid and made a
128
> mb swap file and the rest (I checked use remaining space) linux native
(29xx
> mb). I did a custom installation and checked most of the packages, in
total
> 1.1 gb. My diamond viper v550 card was detected and also my monitor works
> fine. So far so good. I finally came to the part where the files were
copied
> and installed. First he started to format both partitions (native and
swap
> (128 mb))
> and then things went wrong: half way the status bar i got the
error : "Error
> writing install image to disk. You probably run out of disk space". This
is
> not possible, cause i have 3 gb of empty space and only 1 gb of
packages. I
> figured it must be a bad block on my "new" hdd, so i took another hdd
(which
> was tested and ok.) but the same problem at the same time. Then i figured
> something was wrong with the ISO file and downloaded both files from a
> different location and burned them on a CD again. But after installing
> again, same problem, same time. I tried selecting different packages and
> changing my partitions (I added /boot (300mb) and enlarged my swap, but
> still the same error). My configuration:
>
> Intel p3-450 (slot 1)
> 256 mb memory
> prim master : maxtor 8.4 gb (win2k pro is here)
> prim slave : WD 3.2 gb (linux should be here)
> sec. master : philips 40 x cdrom
> sec. slave : philips CDrw
> Diamond viper v550
> Logitech cordless desktop
> Eicon diva ISDN
>
> When I do a "df" when the error appears, i get the following output:
>
> Mount point 1k-blocks Used Available
> / 4030 1007 3023
> /proc 0 0 0
> /dev/pts 0 0 0
> /proc/bus/usb 0 0 0
> /mnt/source 656756 656756 0
> /mnt/runtime 100168 85370 14798
> /mnt/sysimage 2992336 21928 2970408
> /mnt/sysimage/proc 0 0 0
>
> When I look into the error messages i see the following information:
>
> <4> Unable to identify CDrom format
> <6> CDROM open failed
> <4> hdc: command error: status=0x51 {DriveReady Seekcomplete error}
> <4> hdc: command error=0x50
> <4> end_request : I/O error, dev 16:00 (hdc), sector 1078404
>
> I really want to install RH 7.1, so I hope someone can help me fix this
> problem.
>
> Hope to hear from you,
>
> Grtnx, Maarten
>
>
>
>
>
--
Posted via CNET Help.com
http://www.help.com/
------------------------------
From: Dean Thompson <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.networking
Subject: Re: IPMasqerading Setup Still Not Right
Date: Tue, 12 Jun 2001 11:00:36 +1000
Hi!,
> I have the similar setting and similar problem too. With the setting for
> DHCP, The subnet computers can ping outside IPs successfully, but they
> still cannot access them by browser or telnet. My friend told me maybe my
> firewall setting block the connection, but I still don't know how to make
> it work.
Does your firewall allow you to accept packets on port 67 and 68 using the
TCP/UDP protocol?, this is where the dhcp return packets come in on.
See ya
Dean Thompson
--
+____________________________+____________________________________________+
| Dean Thompson | E-mail - [EMAIL PROTECTED] |
| Bach. Computing (Hons) | ICQ - 45191180 |
| PhD Student | Office - <Off-Campus> |
| School Comp.Sci & Soft.Eng | Phone - +61 3 9903 2787 (Gen. Office) |
| MONASH (Caulfield Campus) | Fax - +61 3 9903 1077 |
| Melbourne, Australia | |
+----------------------------+--------------------------------------------+
------------------------------
From: [EMAIL PROTECTED] (Michael Perry)
Subject: Re: Thanks Rob Davies for the hdparm info
Date: Tue, 12 Jun 2001 01:17:10 -0000
Reply-To: [EMAIL PROTECTED]
On Mon, 11 Jun 2001 18:29:45 -0500, Dave Uhring <[EMAIL PROTECTED]> wrote:
> Robert Davies wrote:
>
>> Michael Perry wrote:
>>
>>> From the posts, I would now agree that a person should go out and find
>>> whether disk/file corruption could happen and take reasonable steps to
>>> preclude it.
>>
>> There's a german site with info on BIOS updates, the problem has afflicted
>> Win users, but Via have been less than helpful at what PCI parameters
>> should be tweaked.
>>
>> Linus decreed DMA with Via should simply be turned off! Whether the
>> chipset is good or not. I returned 2 1GHz Athlon boards before Christmas,
>> with KT133, at the time there was nothing about stability problems, but my
>> thrash testing caused lockups and crashes. Had to go with PIII and Intel,
>> which was a shame :(
>>
>> The good news is, folk are working on work rounds, so hopefully Via users
>> will be better servered, and perhaps a BIOS update and kernel upgrade in
>> future will make this safe, with the white and black lists properly
>> configured.
>>
>> Rob
>>
>
> There is some other problem involved than just the KT133 chipset. I'm
> using MSI K7T Pro2-A MB with Athlon 850 and and IBM-DTLA-307045 HDD and
> have had absolutely no problems with the 2.4.X kernels as long as the VIA
> chipset support was compiled into the kernel. Now, the 2.2.XX kernels are
> another bag of worms.
>
I believe that too. Hence, my statement regarding the "greylist" of drives,
chipsets, and boards that work properly. Without hdparm at all and with the
VIA IDE drive compiled for my K7T Pro2-A, I get pretty reasonable results
given the cheapness of the drives. The kernel development lists are pretty
interesting in that people often report no problem at all with pretty much
the same combination of things that others have issues with. I think the
variability gets down to what we were talking about in the other post;
namely combinations of drives, chips, and boards.
I have to admit to some degree of caution though when I read some of the
accounts of using hdparm with the VIA ide driver in place.
Many of the discussions regarding via and corruption seem to have tailed off
a bit now. I kinda wonder if this is due to the SuSE sponsored VIA ide
driver getting better overall. I think things were much more grim late last
year when people started finding issues with no driver developed to take
care of some of the VIA issues. The informatioin in the kernel driver in
the first few lines is pretty interesting as it names specific via based
chipsets which benefit from the driver.
I definitely stopped using hdparm after reading some of the cautionary
notes. I also own a western digital drive which is not blacklisted but I
think its performance is rather suspect. I am very interested in the IBM
drives you use overall. I would not mind switching if I felt that things
were better there.
I posted in the other thread some basic stuff from /proc/ide/via which I
found interesting. The other is running hdparm against the drives now and
seeing what I get.
The main problem I see is that there is no continuum of evidence since so
many people report no problem, others report some problems and use the VIA
ide driver, and others report quite terrible problems with losing file
systems, re-installing, etc. I spent over two days searching on google for
various reports on this. There are lots.
--
Michael Perry
[EMAIL PROTECTED]
====================
------------------------------
From: [EMAIL PROTECTED] (H.Bruijn)
Subject: Re: Sound Module Problems
Date: 12 Jun 2001 01:22:44 GMT
Reply-To: [EMAIL PROTECTED]
On Mon, 11 Jun 2001 23:51:52 GMT, Rand Simberg allegedly wrote:
> I've got a cm8338-based sound card that I'm trying to use in my RH6.2
> system (running 2.2.19 of my own build). The instructions for the
> driver say to run make config or make menuconfig, and "select sound
> card (CONFIG_SOUND='m') support, and CMPCI driver
> (CONFIG_SOUND_CMPCI='m') as modules."
Instructions like these refer to the "raw" kernel configuration file,
which is what you create in a more userfriendly way with "make (menu)config".
It is a hidden file in your linux source tree, most likely called
/usr/src/linux/.config Ignore the warning on top and edit it by hand,
often that will be the quickest way to get something done, but you have to
consider all dependancies as well, fi a module to support a specific network
card is useless without general networking support.
# /usr/src/linux/.config
# OPTION_1 is not set
#
# OPTION_2 is built-in in the kernel
OPTION_2=y
#
# OPTION_3 is compiled as a seperate module, to be loaded on demand
OPTION_3=m
So in your case, search for those options and set them as asked (the
sound settings are near the end of the file):
#
# Sound
#
CONFIG_SOUND=m
CONFIG_SOUND_CMPCI=m
# CONFIG_SOUND_CS4281 is not set
# CONFIG_SOUND_FUSION is not set
# CONFIG_SOUND_EMU10K1 is not set
# ...
# End of Sound config
As menu options in make menuconfig you get something like:
Linux Kernel v2.2.9 Configuration
---------------------- Sound ----------------------
<M> Sound card support
<M> C-Media PCI (CMI8338/8378)
< > Crystal CS4281
< > Crystal SoundFusion (CS4280/461x)
< > Creative SBLive! (EMU10K1)
...
Which in the end has the same result.
> I don't see these items anywhere in the sound menu of menuconfig. I
> can select sound cards support as a module, and in fact the current
> kernel already supports that. But none of the driver modules listed
> show anything about CMPCI. Also, there are certain things to
> configure, and I don't see where I get the opportunity to do that.
>
> Questions. First of all, what are the instructions talking about--why
> don't I see the options that it's describing? Second, do I need to
> recompile the kernel just to add a specific sound module, if it
> already has sound card support? Finally, is there some way that I can
> just compile the driver itself and install it manually? I know the
> network drivers usually have a compile command at the end of the
> source, but this one doesn't...
>
You don't need to recompile the complete kernel after selecting some
new modules. Just run "make dep" which makes sure the dependancies are
correct. Then "make modules" which should notice that all the previously
selected modules are already compiled and up-to-date, and needn't be
compiled again and will only compile the newly selected modules. The
last step "make modules_install" will install all modules in the correct
subdirectories of /lib/modules.
Then run "depmod -a" to update dependancies, and you should now be able
to, without rebooting, to load the module cmpci to support your
soundcard. "modprobe cmpci" (IIRC it doesn't take any parameters for
irq, dma or io) Because of the depmod it will also load the module
soundcore, you don't need to load that one by hand.
If the sound devices were created when you installed the system, you now
have sound. "cat file.wav > /dev/dsp" to test.
If /dev/dsp*, /dev/mixer*, /dev/audio* etc. don't exist, they can be
created with the command "/sbin/MAKEDEV audio". They are essential for
sound support, as they are the only way for the system to
contact/control your soundcard once the module cmpci has been loaded.
--
If a trainstation is the place where trains stop, what is a workstation?
========================================================================
Herman Bruijn website: http://HermanBruijn.com
The Netherlands
------------------------------
From: <[EMAIL PROTECTED]>
Subject: Re: linux 7.1 install "sup wit dat"?
Date: Tue, 12 Jun 2001 01:30:05 -0000
I had similar problem (a number of people are getting it as well). I
almost given up & wanting to try Mandrake 8.0 instead.
However I discovered the workaround by chance.
What I did was to boot up using cdrom (A Mitsubishi Diamond Data 32X, OEM
is Acer!!!!!)
At the the boot prompt entered the following to perform a text-based
install.
boot: linux text hdd=cdrom
or hdc=cdrom if your cdrom is the 1st device on the 2nd ide channel.
After that just go through with text mode install.
It'll fail a couple of times stating "not enough space" & throw you back
to the X server video card detection. Just press OK & it'll copy the files
across and completes the installations.
It has nothing to do with fdisk. You must have /boot, / & swap. I've tried
almost every combinations.
Hope it helps.
Koi
gman1 wrote:
>
> Here is what happens when I try to install or update red hat 7.1:
>
> when i get to the "moving install image to hard drive" in the
> installation
> I get the error: "an error occured, probably because you don't have
> enough disk space"
>
> I have:
> /boot - 64 megs
> {swap}- 256 megs
> / - 2.9 gigs(but it doesn't seem to matter how big I make "root")
>
> When I do finally get the install to start copying the files - I get an
> anaconda crash?
>
> ps. I have no problems with any other version of red hat including
> 7.0....
>
> Thanks to all in advance!!!!
>
--
Posted via CNET Help.com
http://www.help.com/
------------------------------
From: "Steve Bougerolle" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.x,comp.os.linux.misc
Subject: Selecting screen resolution with GDM / changing res NICELY in GNOME
Date: Tue, 12 Jun 2001 09:33:06 +0800
Does anyone know how I can set up GDM to change the screen resolution of
my GNOME session? What I'd like is a menu of sessions that lists
"GNOME" and "GNOME Big screen", so we can pick before we log in.
Now, I DON'T mean all that simple basic stuff about changing video modes
in XFree86 using CTRL ALT + and CTRL ALT -. I know all that. The
problem is, if I change resolutions once GNOME has started the GNOME
panel and windows won't automatically resize, plus this tedious virtual
window is left around. All this is OK for me but I need to set this up
so high school kids can use it, and it should work easily and nicely.
That means no windows or panels left hanging off the screen, and no
virtual window causing things to disappear every time a kid moves the
mouse too far to the left. It also means not using 1024x768 as a default
(because most of them complain it makes the letters too small on our 15"
screens).
In the past we didn't use GDM and solved this problem by having different
versions of startx, which picked different XF86Config files to get the
desired res. I've tried similar things with GDM but get hung up trying
to restart X in the right mode.
Ideas, please? I have also thought of fixing it at 1024x768 by default
and increasing the font sizes, but I'd like to leave that as a last
resort.
------------------------------
** 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
******************************
