Linux-Hardware Digest #447, Volume #13 Sat, 19 Aug 00 12:13:07 EDT
Contents:
Re: KDE (Ashley Drees)
Re: Whoopee ("Neil Golstein")
Ethernet EEPROM on Supermicro PIIIDME - CORRECT VALUES! (Chris Rankin)
Correct value for "idebus=xxxx"? (Chris Rankin)
Re: How can i install redhat5.2 with scsi ultra160 hard disk(aic7892)?
([EMAIL PROTECTED])
Re: How can i install redhat5.2 with scsi ultra160 hard disk(aic7892)?
([EMAIL PROTECTED])
free photos ("martin")
Problem Compiling driver for NIC. ([EMAIL PROTECTED])
USB Visor hotsync failure w/ ALi mbs & TP600E with 2.4.0-test5 ("Bruce H. McIntosh")
Re: RH 6.2 installation hangs (Gey-Hong Gweon)
Re: Partition Size Advice (hac)
Re: Not all memory detected under linux (Mark irvine)
----------------------------------------------------------------------------
From: Ashley Drees <[EMAIL PROTECTED]>
Subject: Re: KDE
Date: Sat, 19 Aug 2000 09:46:14 +0100
In article <[EMAIL PROTECTED]>, "Ralph" <[EMAIL PROTECTED]>
wrote:
> How do I make the screen size fit the actual screen size on my monitor.
> Mine's too big and I can't get down to the bottom to click the buttons. I
> have tried everything.
Try alt clicking on the window you want to move... ie... press alt and
click and hold.. you should be able to pick up the window.. move it up
and then press whatever button you want.. (I am not at the machine now..
if it is not alt then try Ctl.. or what ever you have to hand as a
modifyer)
if X cannot run your screen at a better res... then it might be worth
getting a newer or better graphics card... loads of second hand ones
about as the WIN/PC bods maddly upgrade to the latest 3D/All singing and
dancing kit.
------------------------------
From: "Neil Golstein" <[EMAIL PROTECTED]>
Subject: Re: Whoopee
Date: 19 Aug 2000 05:52:01 -0500
Reply-To: "Neil Golstein" <[EMAIL PROTECTED]>
I still have it working fine for the most part, I compiled the initio driver
into the kernel and load the promise driver as a module. Once though it
still conflicted and panicked the kernel, however I shut down, power off for
a few secs, then boot up and no probs. When the driver loads successfully
never any more problems. However, could not get USB working in this kernel
2.2.12-20. That's the trouble with these RedHat kernels, none of the
standard kernel patches work right. Wish they would put out a driver for
stock kernel.
Have not heard anything from Promise in email, may call them next week.
"Benjamin Grimm" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> It took it out of my system and all problems are solved .... I changed to
> ArcoRaid DupliDisk and hoping that this
> little thing will show some more funktion than the Promise (maybe I use it
with
> a Win machine).
>
> bg
>
> Neil Golstein wrote:
>
> > OK, it took about half a dozen test boots with the floppy. To cut to
the
> > chase, the driver works with the Initio card out of the system, it also
> > works with the card in another slot. The only other slot I had was a
> > "non-bus mastering" slot but that's OK (I think?) since I no longer have
a
> > boot drive on the adapter, having moved to the Promise. It also worked
with
> > an Adaptec narrow card in any slot. So it works with another SCSI
adapter,
> > it's just fussy about slots and such.
> >
> > So I booted into my Redhat 2.2.12 kernel. Loaded both drivers in both
> > orders (it matters what order you load them cause it changes the drive
> > letters). Worked perfectly. From the way the array sounds, it is
working
> > pretty fast too.
> >
> > Of course now I have to live with the 2.2.12 kernel, but that might not
be
> > so bad. Already have my sound driver and nvidia opengl driver working
> > (though I don't think I have the agp driver in this kernel). Have to try
> > quake again, now that I can access my game files. Now just have to
install
> > the USB backport to get my scanner back and the ppp multilink patch to
get
> > my two line modem working again, sigh, that's gonna be a bitch. I'll
write
> > Promise again thanking them profusely and ask if they're working on a
driver
> > for the 2.4.0 kernels...
> >
> > On the plus side, I can now run internet apps under wine, when I was
running
> > the new kernels the tcp/ip connectivity was broken.
> >
> > "Benjamin Grimm" <[EMAIL PROTECTED]> wrote in message
> > news:[EMAIL PROTECTED]...
>
------------------------------
From: Chris Rankin <au.zipworld.com@{no.spam}rankinc>
Subject: Ethernet EEPROM on Supermicro PIIIDME - CORRECT VALUES!
Date: Sat, 19 Aug 2000 22:41:13 +1000
Hi,
I have been discussing the EtherExpress Ethernet chip with the
Supermicro support people, since the original EEPROM values installed in
my board were obviously wrong. They sent me the following file and an
update utility:
xxxx xxxx xxxx 031B 0000 0201 4701 0000
3899 1125 40A2 000D 8086 0064 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
002C 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 CHKS
The first three words are where the MAC address goes; you should never
change these. Interestingly enough, these "xxxx" values are also the
reason why my EEPROM was wrong in the first place. It turns out that the
update utility only reads numbers and totally ignored the "xxxx"s when
handed this text-block as input. This resulted in the contents of the
EEPROM being written shifted 3 words to the left. Replacing them with
"0000" allowed the utility to write the EEPROM correctly.
Chris
------------------------------
From: Chris Rankin <au.zipworld.com@{no.spam}rankinc>
Subject: Correct value for "idebus=xxxx"?
Date: Sat, 19 Aug 2000 22:56:09 +1000
Hi,
I have been trying to optimise Linux 2.4 on my motherboard, and I
stumbled across the idebus boot-parameter. Now I understand that this is
the PCI bus speed and nothing to do with ATA66 on IDE drives, but on the
otherhand I ran successfully with idebus=66 for several weeks before I
discovered this ... ;-). The board supports 4 33MHz 32 bit PCI slots and
2 66MHz 64 bit slots, but I couldn't recognise anything that would tell
me the optimal "idebus" value. The best candidate is this output from
lspci:
00:1f.1 IDE interface: Intel Corporation 82801AA IDE (rev 02) (prog-if
80 [Master])
Subsystem: Intel Corporation 82801AA IDE
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- F
astB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >S
ERR- <PERR-
Latency: 0
Region 4: I/O ports at ffa0 [size=16]
00: 86 80 11 24 05 00 80 02 02 80 01 01 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: a1 ff 00 00 00 00 00 00 00 00 00 00 86 80 11 24
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Is this enough to justify setting idebus to 66MHz? I am currently using
the default value of 33MHz:
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
Cheers,
Chris
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: How can i install redhat5.2 with scsi ultra160 hard disk(aic7892)?
Date: Sat, 19 Aug 2000 12:47:08 GMT
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] wrote:
> [EMAIL PROTECTED] writes:
>
> > When i install redhat5.2,kernel couldn't find my hard disk?
> > redhat 5.2 didn't support scsi ultra160 aic7892,only support
> > aic788x.How can i install redhat5.2?
>
> Modern Linux kernels should support all AIC-78xx chipsets. Use a more
> current RedHat.
>
> --
> Eric McCoy ([EMAIL PROTECTED])
>
> "misfortune, n. The kind of fortune that never misses."
> - Ambrose Bierce, The Devil's Dictionary
>
Is it the only way to use linux with aic-7892?
Can i complie my kernel(2.0.34) to support aic-7892?
And How?
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: How can i install redhat5.2 with scsi ultra160 hard disk(aic7892)?
Date: Sat, 19 Aug 2000 12:47:17 GMT
In article <[EMAIL PROTECTED]>,
Bartek Kostrzewa <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> >
> > When i install redhat5.2,kernel couldn't find my hard disk?
> > redhat 5.2 didn't support scsi ultra160 aic7892,only support
> > aic788x.How can i install redhat5.2?
> >
> > Sent via Deja.com http://www.deja.com/
> > Before you buy.
>
> Just use the aic78xx driver, it works for me.
>
> --
> Bartek kostrzewa - [EMAIL PROTECTED]
> <<< http://technoage.web.lu >>>
>
my linux kernel was 2.0.34,it couldn't find my hard disk when i install
linux? How to complie my kernel to support aic7892?
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: "martin" <[EMAIL PROTECTED]>
Subject: free photos
Date: Sat, 19 Aug 2000 13:42:53 GMT
free pics
http://utenti.tripod.it/freeteens69/foto.html
www.geocities.com/freeteens69/index.html
------------------------------
From: [EMAIL PROTECTED]
Subject: Problem Compiling driver for NIC.
Date: Sat, 19 Aug 2000 13:55:44 GMT
Hey I have been trying to compile the tulip.c driver for my Linksys
network card. I comile it then test it with insmod tulip.o and I get:
tulip.o: unresolved symbol pci_drv_unregister
tulip.o: unresolved symbol pci_drv_register
If I install it then do depmod -a I get: unresolved symbol in
/lib/modules/2.2.14-5.0/net/tulip.o. I really need to get this working.
Can anybody help?
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: "Bruce H. McIntosh" <[EMAIL PROTECTED]>
Crossposted-To: linux.dev.kernel
Subject: USB Visor hotsync failure w/ ALi mbs & TP600E with 2.4.0-test5
Date: Sat, 19 Aug 2000 10:18:21 -0400
Problem
=======
All attempts at getting my Visor to sync with the USB cradle under linux
have failed miserably. All the appropriate modules are loaded, the Visor
starts communicating just fine, then things just seem to go off into limbo,
requiring cancelling the hotsync on the Visor.
/dev/visor and /dev/pilot are both symlinks to /dev/ttyUSB1, as per the
linux-usb howto."pilot-xfer -L" works fine, giving a list of everything
on the Visor. "pilot-xfer -s" or "pilot-xfer -b" start up, then hang
after copying one or two files from the Visor.
I have two machines, one a K6-2-400 on an ASUS P5A-B, the other a K6-2-450
on an ASUS P5A. I also have a ThinkPad 600E which exhibits the same problem.
On all three of these machines I have tried 2.2.14 with the latest backpatch,
2.4.0-test4 and 2.4.0-test5. In all cases I have every option for /dev
entries and verbose messages turned on. In no case can I find any helpful
messages. I see the Visor connect, then I see the Visor disconnect.
One last, very frustrating note: on the P5A-B and the ThinkPad, USB syncing
works just fine under Windows98SE using the Palm Desktop software.
System 1
========
K6-2-400, P5A-B, 128MB PC100, TNT2, Symbios875 UW, 2x9GB IBM UW, 1 4GB Mic.UW,
Mandrake 7.0, kernel 2.4.0-test5, pilot-link RPM 0.9.3-6MDK
Sysetm 2
========
K6-2-450, P5A, 256MB PC100, TNT2, Symbios875 UW, 9GB IBM UW, 9GB Seagate uW,
Mandrake 7.0, kernel 2.4.0-test5, pilot-link RPM 0.9.3-6MDK
System 3
========
IBM TP 600E, PII-366, 128MB PC133, Nm256, 10GB EIDE,
Mandrake 7.0, kernel 2.4.0-test5, pilot-link RPM -.9.3-6MDK
Output from dmesg
=================
hub.c: port 1 connection change
hub.c: portstatus 101, change 1, 12 Mb/s
hub.c: portstatus 103, change 10, 12 Mb/s
usb.c: USB new device connect, assigned device number 2
usb.c: kmalloc IF c7c30940, numif 1
usb.c: new device strings: Mfr=1, Product=2, SerialNumber=0
usb.c: USB device number 2 default language ID 0x409
Manufacturer: Handspring Inc
Product: Handspring Visor
usbserial.c: Handspring Visor converter detected
visor.c: Handspring Visor: Number of ports: 2
visor.c: Handspring Visor: port 1, is for Generic use and is bound to ttyUSB0
visor.c: Handspring Visor: port 2, is for HotSync use and is bound to ttyUSB1
usbserial.c: Handspring Visor converter now attached to ttyUSB0 (or usb/tts/0
for devfs)
usbserial.c: Handspring Visor converter now attached to ttyUSB1 (or usb/tts/1
for devfs)
usb.c: serial driver claimed interface c7c30940
usb.c: kusbd: /sbin/hotplug add 2
usb.c: kusbd policy returned 0x0
hub.c: port 1 connection change
hub.c: portstatus 100, change 3, 12 Mb/s
usb.c: USB disconnect on device 2
usb.c: kusbd: /sbin/hotplug remove 2
usb.c: kusbd policy returned 0x0
usbserial.c: Handspring Visor converter now disconnected from ttyUSB0
usbserial.c: Handspring Visor converter now disconnected from ttyUSB1
hub.c: port 1 enable change, status 100
Output from relevant portion of lspci -vv
=========================================
00:02.0 USB Controller: Acer Laboratories Inc. [ALi] M5237 USB (rev 03) (prog-if
10 [OHCI])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 80 max, 64 set
Interrupt: pin A routed to IRQ 15
Region 0: Memory at de800000 (32-bit, non-prefetchable) [size=4K]
Output from /var/log/messages
=============================
Aug 19 09:18:15 linux-ws kernel: usb.c: USB new device connect, assigned device
number 2
Aug 19 09:18:15 linux-ws kernel: Manufacturer: Handspring Inc
Aug 19 09:18:15 linux-ws kernel: Product: Handspring Visor
Aug 19 09:18:15 linux-ws kernel: usbserial.c: Handspring Visor converter
detected
Aug 19 09:18:15 linux-ws kernel: visor.c: Handspring Visor: Number of ports: 2
Aug 19 09:18:15 linux-ws kernel: visor.c: Handspring Visor: port 1, is for
Generic use and is bound to ttyUSB0
Aug 19 09:18:15 linux-ws kernel: visor.c: Handspring Visor: port 2, is for
HotSync use and is bound to ttyUSB1
Aug 19 09:18:15 linux-ws kernel: usbserial.c: Handspring Visor converter now
attached to ttyUSB0 (or usb/tts/0 for devfs)
Aug 19 09:18:15 linux-ws kernel: usbserial.c: Handspring Visor converter now
attached to ttyUSB1 (or usb/tts/1 for devfs)
Aug 19 09:19:10 linux-ws kernel: usb.c: USB disconnect on device 2
Aug 19 09:19:10 linux-ws kernel: usbserial.c: Handspring Visor converter now
disconnected from ttyUSB0
Aug 19 09:19:10 linux-ws kernel: usbserial.c: Handspring Visor converter now
disconnected from ttyUSB1
--
========================================================================
Bruce H. McIntosh [EMAIL PROTECTED] http://www.afn.org/~scotsman
========================================================================
Network geek with a strong affinity for Telecasters
------------------------------
Crossposted-To: comp.os.linux.setup,linux.redhat
Subject: Re: RH 6.2 installation hangs
From: Gey-Hong Gweon <[EMAIL PROTECTED]>
Date: 19 Aug 2000 10:52:55 -0400
Thank you and Wayne Pilgrim for the messages. Yes, you did shed some
light on the problem! I looked up the web page that you refers to, and
then some more that are referred to by that web page.
So far, I tried to
(1) do what Wayne Pilgrim has suggested: i.e. specifying PCI=BIOS option
at the bootup
(2) specify ide2=addr1,addr2 ide3=addr3,addr4 boot options that are
explained in the web page that you refer to in your message
(3) pull out the Ultra 100 IDE Controller PCI card from the computer,
and connect hard drives to the motherboard, and then boot up with the
linux installation CD, as suggested by the UDMA FAQ web page
None of these let me go farther than the dead-end after the same message:
PCI: PCI BIOS Revision 2.10 entry at 0xfdb91
PCI: Using configuration type 1
PCI: Probing PCI hardware
Does this mean that something else is not compatible with the linux
kernel in the distribution CD? For example, the motherboard?
I found out that my motherboard is
400474 Intel RAMBUS Motherboard with integrated LAN and audio
I wonder if the "RAMBUS" part is the culprit, since I remember reading
on the RedHat web page that Motherboard with a DRAM controller is not
supported.
Andrey Vlasov <[EMAIL PROTECTED]> writes:
> hi there,
>
> I beleive that your problem related to famous UDMA66 problem - RedHat 6.2
> doesn't know how to work with it. UDMA66 became FAQ check next page
>
> http://www.linuxnewbie.org/nhf/intel/hardware/udma66.html
>
> Hope it will shed a little light
>
> Andrey
>
> Gey-Hong Gweon wrote:
>
> > Hi, I have a brand-new Gateway E-5400 system and my first try to install
> > the RedHat 6.2 failed because the installation program hangs after the
> > message:
> >
> > PCI: PCI BIOS Revision 2.10 entry at 0xfdb91
> > PCI: Using configuration type 1
> > PCI: Probing PCI hardware
> >
> > I wonder if anybody can shed some light on this problem. System
> > configuration is roughly:
> > Ultra 100 Bios Version 2.00
> > Dual Intel 800MHz Pentium III
> > 128 Mb PC600 ECC RDRAM
> > Win2000 Promise Ultra 100 IDE Controller
> > Two 20Gb 7200 RPM Quantrum ATA66 Hard drives
> > etc ...
> >
> > Gey-Hong.
>
--
Gey-Hong Gweon
------------------------------
From: hac <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup,linux.redhat.install
Subject: Re: Partition Size Advice
Date: Sat, 19 Aug 2000 15:45:36 GMT
John Beardmore wrote:
>
> So is this analogous to cluster size / directory entry issues in FAT
> file systems ?
>
Unlike FAT, it has nothing to do with partition size limits.
It's more of a performance issue. A larger block size, particularly
one related to the processor's 'natural' block size, can give you
faster reads and writes. But a larger block also wastes more space.
My /boot filesystem is small and only used during booting (and when I
run lilo). Speed is not important, size is, so that filesystem has
1024 byte blocks. My /usr partition has many large executables and
libraries on it, and is in constant use. Speed is more important, so
it uses 4096 byte blocks. Figure that half of the block size times
the number of files is wasted space. How important is that space, and
how important is speed.
You can also set the bytes/inode ratio. This indirectly sets the
limit to the number of inodes that the filesystem can hold. I usually
run out of space rather than inodes, so I bump this up. This is a
trade-off between the space used for files and the space used for
filesystem overhead. Not worth fretting over, but something you can
tweak to more closely match your actual use. You do NOT want to run
out of inodes, so don't overdo it.
The percentage of space reserved for root can be adjusted from the
default 5%. After an ordinary user fills the disk, root still has
some space to work with to clean up. The side-effect, and an
important one, is that fragmentation goes up markedly as the disk
approaches full. The reserved space helps keep the fragmentation
down.
When I upgrade disks, I take a look at the statistics for my existing
filesystems, and create the new ones based on what I find. The block
size does make a noticeable difference in speed. The bytes/inode
ratio is more of a "Why not?" tweak.
--
Howard Christeller Irvine, CA [EMAIL PROTECTED]
------------------------------
From: Mark irvine <[EMAIL PROTECTED]>
Subject: Re: Not all memory detected under linux
Date: Sat, 19 Aug 2000 16:46:09 -0400
Hi,
I'm having a similar problem as described by Kai below. I've just
upgraded from 64MB to 128 MB (2x64MB pci100). My system (kernel 2.2.16,
RH6.0, AMDk62-500) still only detects 64MB:
=====8<===================================================
mark@localhost mark]$ cat /proc/meminfo
total: used: free: shared: buffers: cached:
Mem: 65916928 63983616 1933312 44060672 1359872 18808832
Swap: 271392768 25141248 246251520
MemTotal: 64372 kB
MemFree: 1888 kB
MemShared: 43028 kB
Buffers: 1328 kB
Cached: 18368 kB
SwapTotal: 265032 kB
SwapFree: 240480 kB
=====8<===================================================
I tried passing the parameter'mem=128M' at the lilo prompt, but I also
get the same kernel panic error.
The bootup sequence shows only 64MB are detected, even though the BIOS
detect the extra memory.
----8<----------------------------------------------------
[mark@localhost mark]$ dmesg
Linux version 2.2.16 ([EMAIL PROTECTED]) (gcc version
egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #8 Sun Jul 30 01:31:31
EDT 2000
Detected 501143 kHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 999.42 BogoMIPS
Memory: 64396k/66496k available (788k kernel code, 416k reserved, 856k
data, 40k init)
...
=====8<===================================================
If I boot into windows it detects the memory without problems, so I think
the memory is fine.
Any help would be appreciated, I'd hate to think I wasted my money,
memory is so expensive these days...
Regards
Mark irvine
[EMAIL PROTECTED] wrote:
> I seem to be having the same RAM problem where Linux only detects a
> very small amount (14M). I tried the Linux mem=128M and I get
> "Kernal panic: Attempted to kill the idle task!
> In Swapper task - not syncing"
>
>
------------------------------
** 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.hardware) 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-Hardware Digest
******************************
