Linux-Setup Digest #77, Volume #19 Tue, 4 Jul 00 21:13:11 EDT
Contents:
Re: Weird problem with Red Hat & Storm setup - text displays black on black
background (bullwinkle)
Re: HP 8100i CDRW not working (UPDATE) (E J)
Re: Postscript Level 1 printing under RH6.2 (U S-D)
Re: How to put RH6.2 on end of 27gb HD, install new lilo? (Mark Hahn)
Re: Settings problems (Re: My Linux Adventure) (Dex)
No 'rescue root' disk in Slackware 7.1? (ljb)
Re: No 'rescue root' disk in Slackware 7.1?
----------------------------------------------------------------------------
From: bullwinkle <[EMAIL PROTECTED]>
Subject: Re: Weird problem with Red Hat & Storm setup - text displays black on black
background
Date: Wed, 05 Jul 2000 00:30:04 GMT
Christopher Adams wrote:
>
>
> Help!
>
> I've decided to try another set of distributions in order to get a
> working Linux system. Whenever I try to install Linux in graphics
> mode, I get black text on a black background. All other icons, etc,
> seem to display properly.....
>
> What's wrong, and is there anything I can do about it? My video is
> on the motherboard, and it is a SIS 5798 (I can double check this
> later), and I have no problems with display in either the Caldera
> distribution or in Windows (aargh!) environments.
>
> I can't afford to keep playing with new distributions - I want
> something that will work! I know Linux is a great o/s - I've seen it
> in action on other computers. All I want is to get it working on my
> system. Can anyone help?
>
> Thanks....
>
> Chris
I had a similiar problem with a SiS 6326 chipset on a Diamond Speedstar
A50 video card running RH6.1. In /ect/X11/XF86Config, in the "Device"
section, I added a couple of options. Different video cards/mainboards
with SiS chipsets would need different options. Go to
http://www.xfree.org/3.3.6/SiS3.html for information on the different
options. I suggest you make a copy of your file, and be prepared to go to
text mode after making changes, as some video controllers don't like some
of the options, and render X unreadable.
--
Posted via CNET Help.com
http://www.help.com/
------------------------------
From: E J <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux,comp.os.linux.questions,,comp.os.linux.hardware,comp.os.linux.help
Subject: Re: HP 8100i CDRW not working (UPDATE)
Date: Tue, 04 Jul 2000 17:48:26 -0700
Almost there!!! Go to www.freshmeat.org and get the latest lilo. It breaks the
1024 cylinder limit.
NYCeyes wrote:
> Hello All:
>
> Thank you collectively for your replies!!!
> At the end of this letter is what my configuration
> looks like right now. Have a look please and see if
> anything pops out at you. If you need more information
> let me know. Sorry for the verbose email and posting,
> but I can only help my cause by giving as much info
> as I can.
>
> TIA,
> Milton
>
> First, a couple of things to note.
>
> (1)
> As far as kernel support goes, I did a "make menuconfig"
> and under the "Block Devices" menu there is a submenu
> that shows this:
> <M> SCSI emulation support
> which I guess means that it is supported as a module.
> Should I look somewhere else to see if it SCSI emulation
> is configured in.
>
> (2)
> I implemented EJ's suggestion of editing /etc/lilo.conf,
> (see his response) but when I run /sbin/lilo I get the
> following error (this is something I caused a while back but
> I forgot how):
> =========================================================
> root@linuxpc# /sbin/lilo -v -v -v -v
> LILO version 21, Copyright 1992-1998 Werner Almesberger
> [... cut out ...]
> Reading boot sector from /dev/hda1
> Device 0x0300: BIOS drive 0x80, 128 heads, 767 cylinders,
> 63 sectors. Partition offset: 0 sectors.
> Merging with /boot/boot.b
> Caching device /dev/hdc1 (0x1601)
> Device 0x1601: BIOS drive 0x81, 15 heads, 8894 cylinders,
> 63 sectors. Partition offset: 63 sectors.
> geo_comp_addr: Cylinder number is too big (4764 > 1023) <---
> ==============================================================
>
> Now for my configuration. Have a look.
>
> #################################################################
> root@linuxpc# cat /etc/lilo.conf
> boot=/dev/hda1
> map=/boot/map
> install=/boot/boot.b
> prompt
> timeout=50
> default=linux
>
> image=/boot/vmlinuz-2.2.12-20
> label=linux
> initrd=/boot/initrd-2.2.12-20.img
> read-only
> root=/dev/hdc1
> append="hdb=ide-scsi"
>
> image=/boot/vmlinuz-2.2.12-20.FCS
> label=FCS_linux
> initrd=/boot/initrd-2.2.12-20.img
> read-only
> root=/dev/hdc1
> append="hdb=ide-scsi"
> ##################################################################
>
> ###################################################################
> root@linuxpc# cat /etc/conf.modules
> #----------------------------------------------
> #Alias for eth0 placed here by mvega. This is
> #for the 3c905b 3COM Card in the lower slot.
> #----------------------------------------------
> alias eth0 3c90x
>
> #----------------------------------------------
> #Alias for eth1 placed here by mvega. This is
> #for the 3CR990 x3 3COM Card in the upper slot.
> #The card is not supported at the moment, but
> #we'll give this one a try until it is. Doesnt
> #work... need to wait for a new driver for the
> #3COM 3CR990x3 card (top slot).
> #----------------------------------------------
> alias eth1 3c90x
>
> alias sound sb
> pre-install sound /sbin/insmod sound dmabuf=1
> options opl3 io=0x388
> alias midi awe_wave
> post-install awe_wave /bin/sfxload /etc/midi/GU11-ROM.SF2
> options sb io=0x220 irq=5 dma=1 dma16=5 mpu_io=0x330
>
> # ----------------------------------------
> # Stuff to get the HP8100i CD-RW to work.
> # ----------------------------------------
> alias scd0 sr_mod # load sr_mod upon access of scd0
> alias scsi_hostadapter ide-scsi # SCSI hostadaptor emulation
> options ide-cd ignore=hdb # if /dev/hdb is your CD-writer
> #########################################################################
>
> ##############################################################
> root@linuxpc# grep insmod /etc/rc.d/rc.local
> insmod ide-scsi
> ##############################################################
>
> #################################################################################
> root@linuxpc# ls -l /dev/cdrom*
> lrwxrwxrwx 1 root root 9 Jul 4 17:20 /dev/cdrom ->
> /dev/scd0
> lrwxrwxrwx 1 root root 3 Apr 8 10:08 /dev/cdrom.ORIG
> -> hdb
> lrwxrwxrwx 1 root root 3 Apr 8 10:08 /dev/cdrom1 ->
> hdd
> #################################################################################
>
> ###############################################################################
> root@linuxpc# ls -l /dev/sg*
> lrwxrwxrwx 1 root root 3 Apr 27 22:01 /dev/sg0 -> sga
> lrwxrwxrwx 1 root root 3 Apr 27 22:01 /dev/sg1 -> sgb
> lrwxrwxrwx 1 root root 3 Apr 27 22:01 /dev/sg2 -> sgc
> lrwxrwxrwx 1 root root 3 Apr 27 22:01 /dev/sg3 -> sgd
> lrwxrwxrwx 1 root root 3 Apr 27 22:01 /dev/sg4 -> sge
> lrwxrwxrwx 1 root root 3 Apr 27 22:01 /dev/sg5 -> sgf
> lrwxrwxrwx 1 root root 3 Apr 27 22:01 /dev/sg6 -> sgg
> lrwxrwxrwx 1 root root 3 Apr 27 22:01 /dev/sg7 -> sgh
> crw------- 1 root sys 21, 0 Apr 27 22:01 /dev/sga
> crw------- 1 root sys 21, 1 Apr 27 22:01 /dev/sgb
> crw------- 1 root sys 21, 2 Apr 27 22:01 /dev/sgc
> crw------- 1 root sys 21, 3 Apr 27 22:01 /dev/sgd
> crw------- 1 root sys 21, 4 Apr 27 22:01 /dev/sge
> crw------- 1 root sys 21, 5 Apr 27 22:01 /dev/sgf
> crw------- 1 root sys 21, 6 Apr 27 22:01 /dev/sgg
> crw------- 1 root sys 21, 7 Apr 27 22:01 /dev/sgh
> ###############################################################################
>
> ###################################################################
> root@linuxpc# cat /proc/modules
> sg 15052 0 (autoclean) (unused)
> ide-scsi 7008 0
> ppp 20012 2 (autoclean)
> slhc 4328 0 (autoclean) [ppp]
> 3c90x 21972 1 (autoclean)
> awe_wave 157804 0
> sb 33620 0
> uart401 5968 0 [sb]
> sound 57240 0 [awe_wave sb uart401]
> soundlow 300 0 [sound]
> soundcore 2372 7 [sb sound]
> ##################################################################
>
> #####################################################################
> root@linuxpc# cat /proc/devices
> Character devices:
> 1 mem
> 2 pty
> 3 ttyp
> 4 ttyS
> 5 cua
> 7 vcs
> 10 misc
> 14 sound
> 29 fb
> 36 netlink
> 128 ptm
> 136 pts
> 162 raw
>
> Block devices:
> 1 ramdisk
> 2 fd
> 3 ide0
> 9 md
> 22 ide1
> ######################################################################
>
> ####################################################################
> root@linuxpc# cdrecord -v -scanbus
> Cdrecord release 1.8a29 Copyright (C) 1995-1999 Jörg Schilling
> TOC Type: 1 = CD-ROM
> cdrecord: No such file or directory. Cannot open SCSI driver.
> ####################################################################
>
> #########################################################
> root@linuxpc# mount -t iso9660 -o ro /dev/cdrom /mnt
> mount: the kernel does not recognize /dev/cdrom as a block device
> (maybe `insmod driver'?)
> #########################################################
>
> #######################################################################
> root@linuxpc# cdrecord -v -scanbus
> Cdrecord release 1.8a29 Copyright (C) 1995-1999 Jörg Schilling
> TOC Type: 1 = CD-ROM
> cdrecord: No such file or directory. Cannot open SCSI driver.
> #######################################################################
>
> ##############################################################################
> root@linuxpc# dmesg
> Linux version 2.2.12-20 ([EMAIL PROTECTED]) (gcc version
> egcs-2
> ..91.66 19990314/Linux (egcs-1.1.2 release)) #1 Mon Sep 27 10:25:54 EDT
> 19
> 99
> Detected 199436655 Hz processor.
> Console: colour VGA+ 80x25
> Calibrating delay loop... 398.13 BogoMIPS
> Memory: 79284k/81920k available (1008k kernel code, 412k reserved, 1152k
> data, 64k init)
> DENTRY hash table entries: 262144 (order: 9, 2097152 bytes)
> Buffer-cache hash table entries: 131072 (order: 7, 524288 bytes)
> Page-cache hash table entries: 32768 (order: 5, 131072 bytes)
> VFS: Diskquotas version dquot_6.4.0 initialized
> CPU: AMD AMD-K6tm w/ multimedia extensions stepping 01
> Checking 386/387 coupling... OK, FPU using exception 16 error reporting.
> Checking 'hlt' instruction... OK.
> AMD K6 stepping B detected - <6>K6 BUG 20022307 20000000 (Report these
> if
> test report is incorrect)
> AMD K6 stepping B detected - system stability may be impaired when more
> t
> han 32 MB are used.
> Please see http://www.mygale.com/~poulot/k6bug.html
> POSIX conformance testing by UNIFIX
> PCI: PCI BIOS revision 2.10 entry at 0xfb420
> PCI: Using configuration type 1
> PCI: Probing PCI hardware
> Linux NET4.0 for Linux 2.2
> Based upon Swansea University Computer Society NET3.039
> NET4: Unix domain sockets 1.0 for Linux NET4.0.
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP, IGMP
> TCP: Hash tables configured (ehash 131072 bhash 65536)
> Initializing RT netlink socket
> Starting kswapd v 1.5
> Detected PS/2 Mouse Port.
> Serial driver version 4.27 with MANY_PORTS MULTIPORT SHARE_IRQ enabled
> ttyS00 at 0x03f8 (irq = 4) is a 16550A
> ttyS01 at 0x02f8 (irq = 3) is a 16550A
> pty: 256 Unix98 ptys configured
> apm: BIOS version 1.2 Flags 0x07 (Driver version 1.9)
> Real Time Clock Driver v1.09
> RAM disk driver initialized: 16 RAM disks of 4096K size
> PIIX3: IDE controller on PCI bus 00 dev 39
> PIIX3: not 100% native mode: will probe irqs later
> ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:pio, hdb:pio
> ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:pio, hdd:pio
> hda: WDC AC33100H, ATA DISK drive
> hdb: Hewlett-Packard CD-Writer Plus 8100, ATAPI CDROM drive
> hdc: ST34342A, ATA DISK drive
> hdd: CDA66801I, ATAPI CDROM drive
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> ide1 at 0x170-0x177,0x376 on irq 15
> hda: WDC AC33100H, 3020MB w/128kB Cache, CHS=767/128/63
> hdc: ST34342A, 4103MB w/0kB Cache, CHS=8894/15/63
> hdb: ATAPI 24X CD-ROM CD-R/RW drive, 1024kB Cache
> Uniform CDROM driver Revision: 2.56
> hdd: ATAPI 6X CD-ROM drive, 240kB Cache
> Floppy drive(s): fd0 is 1.44M
> FDC 0 is a post-1991 82077
> md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12
> raid5: measuring checksumming speed
> raid5: MMX detected, trying high-speed MMX checksum routines
> pII_mmx : 311.277 MB/sec
> p5_mmx : 286.893 MB/sec
> 8regs : 277.368 MB/sec
> 32regs : 195.453 MB/sec
> using fastest function: pII_mmx (311.277 MB/sec)
> scsi : 0 hosts.
> scsi : detected total.
> md.c: sizeof(mdp_super_t) = 4096
> Partition check:
> hda: hda1
> hdc: hdc1
> autodetecting RAID arrays
> autorun ...
> .... autorun DONE.
> VFS: Mounted root (ext2 filesystem) readonly.
> Freeing unused kernel memory: 64k freed
> Adding Swap: 262136k swap-space (priority -1)
> Soundblaster audio driver Copyright (C) by Hannu Savolainen 1993-1996
> SB 4.16 detected OK (220)
> <SoundBlaster EMU8000 (RAM512k)>
> 3Com 3c90x Version 1.0.0i 1999 <[EMAIL PROTECTED]>
> CSLIP: code copyright 1989 Regents of the University of California
> PPP: version 2.3.7 (demand dialling)
> PPP line discipline registered.
> registered device ppp0
> PPP BSD Compression module registered
> PPP Deflate Compression module registered
> scsi0 : SCSI host adapter emulation for IDE ATAPI devices
> scsi : 1 host.
> ########################################################################
------------------------------
From: [EMAIL PROTECTED] (U S-D)
Crossposted-To: uk.comp.os.linux,comp.os.linux.hardware,comp.os.linux.redhat
Subject: Re: Postscript Level 1 printing under RH6.2
Date: 5 Jul 2000 00:48:14 GMT
In article <8jtqsq$19ahr$[EMAIL PROTECTED]>, U S-D wrote:
>
>I've recently upgraded from 6.0 to 6.2 and now my Postscript Level 1
>printer (OL840) refuses to play ball. Curiously, printtool's
>Postscript test page is produced fine. I guess this is because
>it conforms to PS level 1 whereas mpage output does not.
>
>% cat /etc/printcap
>
># /etc/printcap
># This file can be edited with the printtool in the control-panel.
>
>##PRINTTOOL3## LOCAL POSTSCRIPT 300x300 a4 {} PostScript Default {}
>lp:\
> :sd=/var/spool/lpd/lp:\
> :mx#0:\
> :sh:\
> :lp=/dev/lp0:\
> :if=/var/spool/lpd/lp/filter:
>
>-------------------
>
>/var/spool/lpd/lp/filter doesn't need to call gs because the
>printer handles Postscript natively (albeit at level 1).
>Instead just a cat is issued.
>
>Maybe I need to ditch these versions of printtool and
>filters for those distroed with my original RH6.0 ?
>
>Currently installed are printtool-3.44-1 and printfilters-1.63-1
>
>Anyone found a work-around?
I should have added that printtool can set up correctly the OL840's
Laserjet II emulation (PCL3) to which I can print perfectly.
Trapsing through deja - I've discovered it's not a particularly unique
problem... This guy below is having the same problem with his
level 1/2 postscript printer (TI Microlaser Plus)..
=============================================================================
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: Re: Weird printing problem
Date: 02 May 2000 00:00:00 GMT
Message-ID: <8emf34$c9v$[EMAIL PROTECTED]>
Newsgroups: comp.os.linux.hardware
Thaddeus <[EMAIL PROTECTED]> wrote:
:Robie Basak <[EMAIL PROTECTED]> wrote:
:> On Wed, 26 Apr 2000 14:18:51 GMT, Thaddeus said:
:>> I recently upgraded to a new computer. I kept most of the same files
:>> and peripherals of the old computer, including the printer. I've got a
:>> TI Microlaser Plus printer. It worked fine on the old computer when
:>> setup under printtool using the Generic Postscript driver. On the new
:>> computer, I set everything up exactly the same as it was and
:>> printtool's test pages worked perfectly. The problem is that whenever
:>> I try to print postscript from an application it doesn't work. The
:>> file gets sent to the printer just fine and the printer display
:>> indicates that it's processing the file. But then when it would
:>> normally print it just goes back to the online idle state. Same thing
:>> happens with every program. I also tried printing to a file and using
:>> lpr to send the file to the printer, no good. It prints ASCII just
:>> fine, postscript is the only problem. I have the EOF option set.
:>>
:>> Any ideas? TIA
:> Get hold of a postscript file which you know works (there's one
:> called testpage-a4.ps somewhere if you have Redhat).
:> [ /usr/lib/rhs/rhs-printfilters/testpage-a4.ps ]
:>
:> Then do:
:> cat filename > /dev/lp0
:>
:> and see if that does anything.
: Okay, that worked for the PS test page. It didn't work for any other PS
: page though. I also tried changing the printer command in my application,
: but that didn't work either. Now what?
Nothing. If your printer doesn't understand postscript correctly,
nobody can do anything. You just fed it raw postscript directly and
it belched. It's a foozle. Take it back.
It's only excuse is if it never got to see the page, because the
interrupts are all hosed. But it saw the test page fine. Enter the
bios and fiddle with the parallel port types available. Try echoing raw
postscript commands at the printer to see what it does.
Peter
========================================================================
FWIW, I don't agree with Peter. This has nothing to do with the parallel
ports. IMHO, there should be no such thing as a 'generic postscript printer'
when backwardly-incompatible levels 3,2 and 1 exist.
The problem is level 1/2 Postscript devices where mpage (etc) output
is in level 3.
Any work-arounds?
Michael
------------------------------
From: Mark Hahn <[EMAIL PROTECTED]>
Subject: Re: How to put RH6.2 on end of 27gb HD, install new lilo?
Date: 5 Jul 2000 00:40:37 GMT
> I'm not familiar with the new lilo, but as long as you can resize things
> enought (free up about 10-16Mb) to fit a /boot partition between your 3Gb adn
actually, the normal/old lilo will do just fine if you can simply
guarantee that the files it needs at boot are accessible via bios.
they could reside in, say, that first fat32 3G filesystem just fine.
(assuming it lies under the standard 1K cyl limit...)
------------------------------
From: Dex <[EMAIL PROTECTED]>
Subject: Re: Settings problems (Re: My Linux Adventure)
Date: Tue, 04 Jul 2000 21:03:38 -0400
Laura Goodwin wrote:
> Laura Goodwin wrote:
>
> > Ironic: Normally I'd be screaming at Scotty for more bandwidth, but
> > right now I'd be satisfied with a 16 bit, 800x600. Funny how an
> > emergency situation makes you reorganize your priorities....
> >
> > (to be continued)
>
> I figured out how to get more colors, but the display is still
> distorted. And how to enable my modem (I repeat, NOT a Winmodem)?
>
> I'm having problems figuring out how to set my monitor display to what I
> want in Linux, and this is *after* consulting two different Linux
> manuals. I can do it through the terminal emulation via KDE, but how?
> I can give you my monitor specs:
>
> Horizontal = (KHz)30-70
> Vertical= (Hz)50-120
> Vid bandwidth= 110 MHz
> Maximum resolution= VESA 1280x1024 (fh KHz=63.981, fv Hz=60.02)
> Max Colors= unlimited
> Size= 17" (CRT)
> dot pitch= .26
> Viewable area=300x225
>
> Need more details? I got 'em all in my monitor manual. All anyone can
> tell me is "trial and error" but that is NOT GOOD ENOUGH. Trial and
> error will not be necessary. Just tell me where I go to input the
> freaking data! I can set and reset my monitor settings in sixteen
> different ways with a few clicks and little risk in Windows, and if I
> can't do that in LINUX then no wonder the OS isn't catching on! How the
> display looks is pretty basic!
>
> Being able to set up TCP/IP and simply sign on is also pretty basic and
> should be a bit more obvious, IMHO. Any enlightenment available here, my
> dears? With Windows anything and BeOS, all I had to do was poke around
> a bit to find the place to input my dialup settings. Where is it in
> LINUX? I got the info...where do I input it?
>
> --
> Laura Goodwin
>
> "Pain is fleeting, glory is forever.
> Remember: scars are sexy."
If you've already tried these suggestions, sorry to be redundant. Did you
run Xconfigurator? It should set your display settings for you. You can set
up your networking by running linuxconf and going under networking and
setting up ppp.
Good luck,
Dex
------------------------------
From: [EMAIL PROTECTED] (ljb)
Subject: No 'rescue root' disk in Slackware 7.1?
Date: 5 Jul 2000 01:06:44 GMT
I think Slackware 4.0 was the last one with a Rescue Root disk, which you
could use with a boot floppy to recover a system from various problems. Did
this go away with Slackware 7.0, a casualty of the upgrade to glibc? It
seems to be missing at Slackware 7.1 too. This was really useful - is there
any alternative to use to fix problems on a server which cannot reliably
boot from CD?
------------------------------
From: [EMAIL PROTECTED] ()
Subject: Re: No 'rescue root' disk in Slackware 7.1?
Reply-To: [EMAIL PROTECTED]
Date: Wed, 05 Jul 2000 01:08:30 GMT
On 5 Jul 2000 01:06:44 GMT, ljb <[EMAIL PROTECTED]> wrote:
>I think Slackware 4.0 was the last one with a Rescue Root disk, which you
>could use with a boot floppy to recover a system from various problems. Did
>this go away with Slackware 7.0, a casualty of the upgrade to glibc? It
>seems to be missing at Slackware 7.1 too. This was really useful - is there
>any alternative to use to fix problems on a server which cannot reliably
>boot from CD?
If you can't boot from CD then you should fix your crap hardware.
Or get something newer than a 386.
------------------------------
** 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 (and comp.os.linux.setup) via:
Internet: [EMAIL PROTECTED]
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
******************************
