Linux-Hardware Digest #252, Volume #14 Fri, 26 Jan 01 02:13:06 EST
Contents:
Re: Corel Linux Sucks :( ("Dave Stanton")
Re: problems accessing "X" ("TCP")
Re: Help with X on Dell Inspiron 5000 ("mpierce")
Re: Problems with archiving to tape ([EMAIL PROTECTED])
Re: HELP: Kernel panic on first reboot after install of RH6.0 ("mpierce")
Re: What is the kernel module for realtek 8139??? (Trygve Selmer)
Re: ISA Modems. Suggestions? ([EMAIL PROTECTED])
Re: IDE CD-R and SCSI harddrive (hac)
Re: HELP: Kernel panic on first reboot after install of RH6.0 (Juergen Pfann)
Re: What is the kernel module for realtek 8139??? (Juergen Pfann)
Re: ide cd-rw and scsi harddrives (hac)
----------------------------------------------------------------------------
From: "Dave Stanton" <[EMAIL PROTECTED]>
Subject: Re: Corel Linux Sucks :(
Date: Fri, 26 Jan 2001 05:23:46 -0000
"Tina Carter" <[EMAIL PROTECTED]> wrote in message
news:797c6.2100$[EMAIL PROTECTED]...
> I am thinking of Redhat one. Any thoughts?
>
bother everyone here.
> >
> > I gave up on Corel long ago. Try Mandrake for ease of install.
I concur with that, Mandrake 7.2 is the best install I have ever seen and I
thought suse was good.
Dave
------------------------------
From: "TCP" <[EMAIL PROTECTED]>
Subject: Re: problems accessing "X"
Date: Fri, 26 Jan 2001 05:22:27 GMT
Could you tell me how I would switch to using the SVGA server from using the
XFree86?
I tried the command below and it did not work.
Help?
DjM <[EMAIL PROTECTED]> wrote in message
news:SMKa6.3479$[EMAIL PROTECTED]...
> Did you run Xconfigurator?
>
> You must have installed the SVGA server (e.g. /usr/X11R6/bin/XF86_SVGA) as
> your video card deserves this setting. FYI: I am using another video card
> with a different chip set and mine also uses this setting.
>
> The symollic link /etc/X11/X must point to this SVGA server. Make sure
this
> link is in place.
>
> If you are unsure of what servers you installed, use this command:
> ls /usr/X11R6/bin/XF*
>
> All the best,
> DjM
>
>
>
>
> "TCP" <[EMAIL PROTECTED]> wrote in message
> news:h0N96.13514$[EMAIL PROTECTED]...
> > Ok, So I am a newbie. I am sorry to say that I am just now getting into
> the
> > whole Linux thing. I have just installed Linux Mandrake 7.2 on a:
> > IBM Aptiva
> > pentium 166
> > 48 MB ram
> > ATI Mach 64 Rage Video card
> > 3.02 Gb hard drive
> >
> > I currently have Windows ME installed on C:
> > and installed Mandrake on my 2nd partition D:
> >
> > Did a customize install - install was succesful. I configured X on my
own
> > to include
> > my video card - monitors horizontal and Vert. Synch range 30-69 and
50-120
> > respectively.
> >
> > I log in as root - type startx
> > and black screen, everytime. I have gone into XF86Config several times
> and
> > re-set up my setting through there and still black screen.
> > Is there any help out there? I desperately need it.
> > Thanks
> >
> >
> >
>
>
------------------------------
From: "mpierce" <[EMAIL PROTECTED]>
Subject: Re: Help with X on Dell Inspiron 5000
Crossposted-To: comp.os.linux.x,comp.os.linux.setup
Date: Fri, 26 Jan 2001 05:50:01 GMT
I run an I7K and originally had 3.36 configured. Probably have the file
somewhere and will look it you need it. Easier solution upgrade to 4.01
using the Mandrake rpms. You'll have much better performance and if
you're using VMware, it now reads it very nicely - full screen resolution
w/o any problems. Email me if you want me to look for my old config
files.
Marvin
--
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] wrote:
> I have a Dell Inspiron 5000 (not 5000e) running Linux Mandrake 7.1 with
> a
> 1400x1050 pixel 15" screen. The video card is an
>
> ATI 3D Rage P/M Mobility AGP 2X
>
> with 8MB memory. I'm running XFree86-3.3.6 Mach64 server patched with
> Steve Hsieh's patches according to the various Linux on Laptop HOWTOs
> for the I-5000. I'm using vga=2 in the lilo.conf file as required.
>
> For the life of me, I can't get 1280x1024 to run on this thing---which I
> need for presentations. I always get a distored wrapped-around image.
> 1400x1050,
> 1024x768, and 800x600 work fine.
>
> Have tried `xvidtune', read ESR's video HOWTO, &c., used `kvideogen'
> from KDE, all with no good results.
>
> I've also tried 1280x960 thinking that I must stay with a 3x4 aspect
> ratio, this being an LCD display.
>
> �Would someone point me straight (or give me a known
> working modeline for 1280x1024 or 1280x960) please?
>
>
> D. S. Messing
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.misc
Subject: Re: Problems with archiving to tape
Date: Fri, 26 Jan 2001 00:51:20 -0800
[EMAIL PROTECTED] wrote:
>
> I am using a SCSI tape drive that uses standard data cartidges (DC6525).
>
> I created an archive on the tape using tar with the -W option to verify the
> archive. It streams along, gets to the end of the tape, then streams back
> the other way. When it gets to the last file, it "shoe shines" for a few
> minutes. It then begins to verify the files and streams along. When it gets
> to the last file it says "tar: /dev/nst0: Cannot read: Input/Output error"
> and repeats this several times. Then it says "tar: too many errors, quitting"
> and "tar: Error is not recoverable: exiting now".
>
> The cartridge is new. I retensioned it a couple of times before I used it
> and also made some small test archives on the tape and had no problems.
> After having problems with the large archive, I erased the tape, retensioned
> it a couple of more times, and wrote the archive to the tape over again
> and I still had the same problem as before.
>
> Does the "shoe shining" indicate a problem writing to the tape or is this
> normal behaviour? Is it possible that after retensioning a tape several times
> that it still could be too loose? Any ideas on possible defects in the tape
> or the drive?
>
> TIA
The last file of the archive was truncated. The archive was made from the
contents
of a directory. I added one file to the directory, which became the new last
file.
I recreated the archive. This time it got past the orignal last file, but
reported
I/O errors when it got to the new last file which was truncated. The previous
last
file extracted okay, but the current last file did not.
This second attempt should have caused the tape to run past the spot where it
had
stopped last time. This appears to indicate that it wasn't a bad spot on the
tape.
I made a third attempt to make the archive, but this time I changed the blocking
factor. On previous attempts, I had used the default which, according the the
info
pages is 20. On this last attempt I used a blocking factor of 128 and tar
reported
no errors when creating the archive, but it still "shoe shines" for a few
minutes
when it gets to the last file before verifying.
------------------------------
From: "mpierce" <[EMAIL PROTECTED]>
Subject: Re: HELP: Kernel panic on first reboot after install of RH6.0
Date: Fri, 26 Jan 2001 05:59:36 GMT
I'll bet that the problem is being caused by the fact that you have an
ide hd and the kernel you are loading has probably configured this as a
module. This means kernel panic if your root fs is / on hda. I'd
recompile my kernel and for ATA/IDE/MFM/RLL SUPPORT say "Y" and then for
IDE/ATA and ATPI Block Devices say "Y".
I think this is probably your problem as I too once spent several days
doing what you've done and this was my solution.
As a temp patch, you can probably boot off the bootdisk if you made one
as it config different.
Hope this helps.
Marvin
--
In article <[EMAIL PROTECTED]>, "Ray"
<[EMAIL PROTECTED]> wrote:
> On Thu, 25 Jan 2001 05:36:59 GMT, MisterD <[EMAIL PROTECTED]> wrote:
>>Greetings,
>>
>>Just recently built a new machine to take the place of my currently
>>tired old firewall. It's a 486 DX4/100-SE w/ 32 MB RAM (4 x 8MB 72-pin
>>(non-EDO)),
>>4 PCI, 3 ISA, 1 VLB, chipset is UMC (kernel reports UM8886BF). Drives
>>are
>>1
>>x Maxtor 540S (540MB) and 1 x Seagate ST14200 (1GB) hooked to an Adaptec
>>2940 SCSI controller (PCI), has an 8-bit mono video card (ATI) and 3
>>Intel EtherExpress Pro/10 ISA NIC's (PnP), only 1 setup for install
>>purposes. Everything seems to work fine during the install of RH6.0, via
>>FTP from an internal server. Once the install has finished, on the first
>>reboot after, it stops at the last line below everytime ...
>>
>>... snipped ...
>>UM8886BF: port 0x01f0 already claimed by ide0 UM8886BF: port 0x0170
>>already claimed by ide1 UM8886BF: neither IDE port enabled (BIOS) Floppy
>>drive(s): fd0 is 1.44M FDC 0 is an 8272A md driver 0.90.0
>>MAX_MD_DEVS=256, MAX_REAL=12 raid5: measuring checksuming speed
>>8regs : 78.105 MB/sec
>>32regs : 61.341 MB/sec
>>using fastest function: 8regs (78.105 MB/sec) scsi : 0 hosts. scsi :
>>detected total. md.c: sizeof(mdp_super_t) = 4096 Partition check:
>>autodetecting RAID arrays autorun ...
>>... autorun DONE.
>>request_module[block-major-8]: Root fs not mounted VFS: Cannot open root
>>device 08:01 Kernel panic: VFS: Unable to mount root fs on 08:01
>>
>>I've tried different boot parameters (root=/dev/sda1 and linear), didn't
>>work. I've tried another SCSI controller, a 2940W dual channel, same
>>problem. After 13 install attempts over 3 nights, this is starting to
>>get old real quick! The kernel says it's installing bug fixes for the
>>UMC chipset above what I have typed in from dmesg, could that be causing
>>it? Block-major-8 doesn't sound like IDE, and since both channels are
>>disabled in the BIOS, it shouldn't be interfering should it? Is/are the
>>drive(s) failing? Ahhhh!!! As you might be able to tell, I'm at my wits
>>end! Any and all help greatly appreciated!
>
> Maybe I'm blind but I don't even see the scsi adaptor driver loading....
> Also, when you boot the machine (before Linux loads) you should see the
> scsi cards initializing and detecting whatever is attached to it. Does
> it do that and does the list of detected devices look right?
>
>
------------------------------
From: Trygve Selmer <[EMAIL PROTECTED]>
Subject: Re: What is the kernel module for realtek 8139???
Date: Thu, 25 Jan 2001 23:17:30 +0100
"Morten F. Klausen" wrote:
>
> Hi!
>
> What is the kernel module for realtek 8139???
>
> Best regards
>
> Morten F. Klausen
Have you tried rtl8139.o ?
Trygve.
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: ISA Modems. Suggestions?
Date: Fri, 26 Jan 2001 01:24:09 -0800
[EMAIL PROTECTED] wrote:
>
> I found an old isa 33.6 modem to test out in the router. I put it in
> and it had jumpers for the com port and irq. I set those and ran the
> freesco auto modem config. It didn't find it. I tried to set it up
> manually but I don't know what the initizilitation string is. It is a
> rockwell modem. I am not sure what rockwell chipset it has though. It
> should work? shouldn't it?
>
> In article <94nqh6$5b5$[EMAIL PROTECTED]>,
> [EMAIL PROTECTED] wrote:
> > I need an isa modem for my freesco router. 56 k modem. I found a
> Modem
> > Blaster 56 k on mwave.com. Will a modem blaster work w/ minor setup
> > problems or tweaking? What isa modem do you suggest? I would get an
> > external but it is on a 386 and the freesco site said that internal is
> > better with the old compters because they had slow comm ports.
> >
> > Sent via Deja.com
> > http://www.deja.com/
> >
>
> Sent via Deja.com
> http://www.deja.com/
You could try sending it some commands. If you send "ATZ" followed by a carriage
return, it should reply "OK". The required initialisation string depends on the
software that will be used with the modem and is usually stored in a conf file.
------------------------------
From: hac <[EMAIL PROTECTED]>
Subject: Re: IDE CD-R and SCSI harddrive
Date: Fri, 26 Jan 2001 06:48:04 GMT
mpierce wrote:
>
> Hac,
> Can you explain how you've got the IDE-CDR working, configuration, etc.
> I have a zip on USB which is detected but get an error regarding wrong
> major & minor numbers on the CDRW which should be scd0.
I compiled a 2.2.18 kernel with ide-scsi support. Others load the
ide-scsi module; I just prefer to include permanently drivers for
hardware that's permanently installed. Either way should work. No
patches, just vanilla kernel source, configured to my tastes and
hardware.
Looks like you're looking for an old, deprecated name (scd0). Use
sr0.
Here's a section of my dmesg:
PIIX4: IDE controller on PCI bus 00 dev 39
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:pio
hda: Maxtor 54098U8, ATA DISK drive
hdc: PLEXTOR CD-R PX-W8432T, ATAPI CDROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: Maxtor 54098U8, 39082MB w/2048kB Cache, CHS=4982/255/63, UDMA
Floppy drive(s): fd0 is 1.44M, fd1 is 1.2M
FDC 0 is a post-1991 82077
i91u: PCI Base=0xD000, IRQ=5, BIOS=0xFF000, SCSI ID=7
i91u: Reset SCSI Bus ...
i91u: PCI Base=0xD400, IRQ=5, BIOS=0xFF000, SCSI ID=7
i91u: Reset SCSI Bus ...
scsi0 : Initio INI-9X00U/UW SCSI device driver; Revision: 1.03g
scsi1 : Initio INI-9X00U/UW SCSI device driver; Revision: 1.03g
scsi2 : SCSI host adapter emulation for IDE ATAPI devices
scsi : 3 hosts.
Vendor: PLEXTOR Model: CD-ROM PX-32TS Rev: 1.02
Type: CD-ROM ANSI SCSI revision: 02
Detected scsi CD-ROM sr0 at scsi1, channel 0, id 2, lun 0
Vendor: PLEXTOR Model: CD-R PX-W8432T Rev: 1.09
Type: CD-ROM ANSI SCSI revision: 02
Detected scsi CD-ROM sr1 at scsi2, channel 0, id 0, lun 0
scsi : detected 2 SCSI generics 2 SCSI cdroms total.
Uniform CD-ROM driver Revision: 3.11
sr1: scsi3-mmc drive: 32x/32x writer cd/rw xa/form2 cdda tray
Note that the burner shows up as hdc and sr1. As a CD-ROM, it's
/dev/sr1; as a burner, it gets used as /dev/sg1, the generic SCSI
device. Cdrecord can use it as /dev/sg1 or /dev/sgb, depending on how
your system is set up, or by it's own 2,0,0 device naming convention:
bash$ cdrecord -scanbus
Cdrecord 1.8 (i686-pc-linux-gnu) Copyright (C) 1995-2000 J�rg
Schilling
Using libscg version 'schily-0.1'
scsibus0:
0,0,0 0) *
0,1,0 1) *
0,2,0 2) *
0,3,0 3) *
0,4,0 4) 'ARCHIVE ' 'VIPER 150 21247' '-011' Removable Tape
0,5,0 5) 'UMAX ' 'Astra 1200S ' 'V2.8' Scanner
0,6,0 6) 'EXABYTE ' '8200SX ' '261A' Removable Tape
0,7,0 7) *
scsibus1:
1,0,0 100) *
1,1,0 101) *
1,2,0 102) 'PLEXTOR ' 'CD-ROM PX-32TS ' '1.02' Removable CD-ROM
1,3,0 103) *
1,4,0 104) *
1,5,0 105) *
1,6,0 106) *
1,7,0 107) *
scsibus2:
2,0,0 200) 'PLEXTOR ' 'CD-R PX-W8432T' '1.09' Removable CD-ROM
2,1,0 201) *
2,2,0 202) *
2,3,0 203) *
2,4,0 204) *
2,5,0 205) *
2,6,0 206) *
2,7,0 207) *
I don't normally have the external SCSI devices turned on, which is
why they didn't show up in the dmesg output. The scanner can cause
the SCSI generics to be numbered differently, something that devfs (in
2.4) should fix.
Hope that helps. Now I need to figure out why the burner doesn't seem
to work with the 2.4.0 kernel I recently built. Good thing that I
kept the 2.2.18!
--
Howard Christeller Irvine, CA [EMAIL PROTECTED]
------------------------------
From: Juergen Pfann <[EMAIL PROTECTED]>
Subject: Re: HELP: Kernel panic on first reboot after install of RH6.0
Date: Fri, 26 Jan 2001 07:50:41 +0100
mpierce wrote:
>
> I'll bet that the problem is being caused by the fact that you have an
> ide hd and the kernel you are loading has probably configured this as a
> module. This means kernel panic if your root fs is / on hda. I'd
> recompile my kernel and for ATA/IDE/MFM/RLL SUPPORT say "Y" and then for
> IDE/ATA and ATPI Block Devices say "Y".
>
Sorry, you're wrong, Marvin - it's the other way 'round :
The root file system is on the 1st partition of the 1st
SCSI hard disk, /dev/sda1, which has the major and minor
numbers (8 and 1) in the orig. posting.
If you've got another box, you should compile a kernel
with SCSI support for your HA and at least SCSI disk
support compiled *statically* into the kernel.
Alternatively, if you insist on using modules for
your root fs driver, you _must_ configure an initial
ram disk (initrd) that holds the resp. drivers =>
man mkinitrd.
But IMHO, besides installation, there's no advantage
with an initrd - being somewhat "conservative",
I'd *always* recommend to compile the root fs driver(s)
fixed into the kernel.
BTW I've had the same problem, too, last week, but managed
to boot a SuSE system on the same box, and compile a
custom RH 7 kernel after mounting that fs...
In my eyes, not all features of the Linux kernel are
useful altogether; before the "initrd" eara, the distros
usually offered different bootable kernels e.g. for
SCSI or IDE systems (that is, root fs). That was in
the "good old days", however... (SCNR).
Juergen
------------------------------
From: Juergen Pfann <[EMAIL PROTECTED]>
Subject: Re: What is the kernel module for realtek 8139???
Date: Fri, 26 Jan 2001 07:50:48 +0100
Trygve Selmer wrote:
>
> "Morten F. Klausen" wrote:
> >
> > Hi!
> >
> > What is the kernel module for realtek 8139???
> >
> > Best regards
> >
> > Morten F. Klausen
>
> Have you tried rtl8139.o ?
>
> Trygve.
As for 2.4(.test) kernels, you can choose the
"rtl8139too" driver, alternatively.
With SuSE 7.0, I don't notice any difference
to my other distros with the "old" driver, neither
in terms of stability nor performance, though.
Juergen
------------------------------
From: hac <[EMAIL PROTECTED]>
Subject: Re: ide cd-rw and scsi harddrives
Date: Fri, 26 Jan 2001 07:03:03 GMT
Dances With Crows wrote:
>
> On Fri, 26 Jan 2001 01:42:46 +0900, Saender A. Clark staggered into the
> Black Sun and said:
> >I have a machine with two scsi harddrives on scsibus 0 - redhat 6.2 ,
> >kernel 2.2.16- sees them as sda and sdb
> >When I loaded the ide-scsi module and rebooted, the cd-rw was now seen
> >as sda and I got a kernel panic because it didn't know where to look for
> >boot instructions.
> >
> >I tried changing fstab and lilo.conf (and ran lilo) to reflect this
> >change, but no joy. All it has done is make it impossible for me to get
> >into the machine at all.
> >
> >Any ideas how to get linux to boot from the now moved devices?
>
> This is really f***ed up; a CD-RW should not appear as "sda" no matter
> what. When you get back into the system, make sure that ide-scsi
> support is built as a module, not directly into the kernel, and this
> should not present a problem to the booting process as long as you're
> not using a RAMdisk. (RAMdisks are completely unnecessary if you
> compile SCSI support, SCSI disk support, and support for your particular
> brand of SCSI adapter directly into the kernel. Their only purpose is
> for installation and rescue systems; IMHO RedHat's reliance on the
> RAMdisk causes more problems and confusion than it solves.)
>
My ide-scsi support is compiled directly into the kernel, and works.
I agree about initrd; I don't use it.
> Also go into the BIOS and disable (U)DMA for this device; CD-ROM-type
> devices don't need it, most of them can't use it, and trying to use it
> with a CD-ROM can cause funky errors like that to happen.
>
My ATAPI burner has DMA enabled, as is recommended for this drive, and
it works. This is drive specific. Some don't like it, mine does, and
it allows me to burn CD-R's while hammering on the hard drive pretty
hard.
> Anyway: boot from a bootdisk (you DO have a bootdisk, right?
> http://www.toms.net/rb/ if you don't, and keep 2 or 3 copies around) or
> boot from a bootable CD ("linux root=/dev/sda3" or wherever your real
> root partition is) then see if you can make those changes discussed in
> the first paragraph. HTH, bonne chance....
>
You need RAMdisk support if you want to create a customized version of
Tom's RB. ;-)
I'm not trying to be disagreeable, I just think it's odd that my
experience seems to point in different directions than yours. Having
a CD-RW show up as /dev/sda is truly broken, though. I think that
there was one early drive that reported itself as a WORM-drive, which
could cause this type of problem. Other than that, I lean towards
BIOS problems. The CD-RW should show up in the BIOS as an ATAPI
device, and NOT as a hard drive.
--
Howard Christeller Irvine, CA [EMAIL PROTECTED]
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list by posting to comp.os.linux.hardware.
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Hardware Digest
******************************
