Correct me if I'm wrong, but isn't 40cm (about 16") the maximum cable
length for EIDE cables? Especially for UDMA connections?
That would explain that your drives work now.
Am Mit, 09 Mai 2001 schrieb Olaf Hering:
> What kernel do you use?
> I recommend the 2.4.2 kernel, the used CMD646 controller is broken and
> works only with 2.2.16 and 2.4.2.
> Gruss Olaf
Until now I tried 2.2.16, 2.2.18 and 2.4.2! I got a hint from Jochen
Hoffmann. He told me they had similar problems with two IBM DTLA-305040
(same family as mine) on AMD K7 computers running SuSE 6.4. Kernel
update from 2.2.18 to 2.2.19 solved his problem and as a work around
he turned off dma support. So I installed 2.2.18 and 2.4.2 but the
error messages still occurred. Then I turned off UDMA of the
DTLA-307030 and for the first time these kernel messages disappeared
(with kernel 2.2.16 or 2.4.2).
It must be a data transfer problem. After shortening the UltraATA cable
from 24" to 12" I turned on again UDMA Mode 2. It works well since five
hours. I only get a nfsserver failure during bootup with kernel 2.4.2:
Starting kernel based NFS serverlockdsvc: Invalid argument .....failed
and a few new kernel messages:
May 9 19:46:46 MacHu8 inetd: swat/tcp (2): bind: Address already in
May 9 19:47:37 MacHu8 /usr/sbin/gpm: Error in protocol
I'm not sure why this cable shortening works. Why should a longer cable
support one UDMA/33 drive and another on the same cable won't work? And
what about my CMD646? In which way is it broken?
> Second: with 7.0 I changed the boot priority to MacOS by
> swapping lines in the os.chooser file so I had to press the space bar
> to launch Linux. This doesn't seem to function anymore with 7.1. In
> fact 7.1 seems to ignore the os.chooser file. I'm currently stuck
> with Linux as the default OS. How do I switch it to default to MacOS?
I experienced the same problem just recently when I updated from 7.0 to 7.1
and wanted to re-use my old os.chooser file. I managed to have the open
firmware become aware of my os.chooser file by removing the Mac OS Rom file
from the suseboot folder (and of course marking the os.chooser file as
tbxi). At least this worked for me on my Powerbook G3 Pismo. It does indeed
seem that the os.chooser file was ignored when the Mac OS Rom file was
Visual Systems GmbH
hello out there,
i have lots of trouble trying to use my second eth interface under suse
linux, both 6.4 and 7.1.
this is concerning my home server (and every other mac i set up with suse
linux 'til now) with the following unspectacular config:
power mac 8200/120,
one 1,2gb scsi hd (apple built in),
one 4,5gb scsi hd (/home),
64 megs of ram (ok ok, it's not my g4 with 1gig ;),
on board 10mbit eth (=eth0, works fine unless its pretty slow),
one smc etherpower 10/100 (9432TX/MP) via the 'epic 100' module.
(if i does work after your hints i guess i'll give it a second to manage nfs
for my sun machine... ;)
this seems to be pretty normal.
everything works fine until you try to activate this smc card to work as the
eth1 interface -- there's no difference trying device eth0 for the card.
restarting the network (to enable eth1=smc) results in a hanging machine
which is not only dead on the console, but also doesn't answer pings nor is
reachable via telnet. you have to reset the machine.
***my question now is: did anyone successful use this card under (suse)
i tried to use this card on a power mac with netbsd -- no problem there...
because it's a pretty good card, i think ;)
tia for your answers and greetz,
timo (aka Pansen)
I'm trying to collect some information on Linux-irDA
and using it in connection with mobile phones.
I checked the irDA project site at sourceforge but
couldn't really find any helpful information on this
subject. As I understood the current kernel already
supports the irDA protocols (not sure which ones,
though), but couldn't find any tools apart from Palm
related stuff. In this case, I'm using a nokia 8210
and I'd love to connect through the irDA port. Does
anyone know of any tools or libs (so I can roll my
Tel.+49 (40)432 923-0
Fax +49 (40)432 923-23
Das Buch zum Autor jetzt bestellen unter:
a couple of days ago I installed an OrangeLink Firewire/USB PCI Card in my
beige G3 (266MT). Since then I haven't been able to boot into an existing
SuSE 7.0 installation.
I tried quite a few precompiled kernels (SuSE 2.2.14, SuSE 2.2.16, SuSE
2.2.18, SuSE 2.4.1, SuSE, 2.4.2, a couple of kernels from Benjamin
Herrenschmidt and others) and none did work except for the official 2.2.19
kernel. Even that one only works after a cold restart. I wouldn't mind using
that kernel but since using it my mouse stopped working under linux
completly and I can't convince it to work.
Any ideas? (I only want my mouse back - I'm not asking for a way how to use
USB or Firewire under Linux)
Is there any way of reading HFS+ partitions from linux?
Dr Doug Edwards, Senior Lecturer in Computer Science
Room IT 210, Department of Computer Science,
University of Manchester, Oxford Road, Manchester, M13 9PL, U.K.
Tel: (+44) 161 275 6191 Mobile: 07968 799 336
email: doug(a)cs.man.ac.uk FAX: (+44) 161 275 6204
The box said 'Requires Windows 95, or better.' So I bought a Macintosh.
as i connected an USB barcode reader on the USB-port, i got the following
unresolved symbol mac_hid_mouse_emulate_buttons
unresolved symbol macv_hid_keyboard_sends_linux_keycodes
insmod /lib/modules/2.4.2/kernel/drivers/input/keybdev.o failed
insmod keybdev failed
i'm using an iBook with SuSE 7.1 and Kernel 2.4.2
What can i do to let it work ?
The barcode reader works with keyboard emulation and works fine on MacOS.
thanks for reply,
Much to my shock and surprise, when I purchased SuSE 7.0, it was only
-after- I made the purchase that I found out that the kernel as shipped
didn't support both PCI busses in my PM 9600. So now, I guess I have
to ask: is it supported? I can't, for the life of me, find an entry
in any of the knowledgebases, so I'm wondering- anyone out there know?