Hi,
I just got a Wacom Graphire3 USB tablet, and had some troubles to get it
working under SuSE 9.2 (amd64 edition). The X server simply crashes on
loading the wacom driver. Well, obviously wacom_drv.o is broken, and
recompiling from the source (that's 0.6.6 then) fixed the problem.
Recompiling wasn't easy, I'll send a patch to the linuxwacom maintainer in
the next days (the attached patch is to be applied after configure, so what's
really needed is to change the configure file; that'll take longer ;-). But
to keep other people out of troubles, I've put the compiled binary on the
web.
http://www.jwdt.com/~paysan/wacom.html
or direct to the driver:
http://www.jwdt.com/~paysan/wacom_drv.o.gz
Please, SuSE maintainers: Put that fix into your update, it's simply annoying
that it is still there, when it already was reported here for SuSE 9.1.
--
Bernd Paysan
"If you want it done right, you have to do it yourself"
http://www.jwdt.com/~paysan/
Hi all,
Got a quick question about partitioning. I have a laptop that has XP and Linux
9.0. I need to resize the SuSE partition and make it smaller and the XP
larger (giving it to my wife). What's the easiest way to do this? Partition
Magic or use SuSE?
Thanks,
Tom
--
Tom Nielsen
Neuro Logic Systems
1.805.389.5435 x18
www.neuro-logic.com
There was a thread earlier this month regarding the
Tyan S2885 MB, and 8 GB of memory. I'm seeing a
the same problem on similar hardware with SuSE 9.2
(2.6.8-24).
To recap, problems with peripheral devices with
limited addressing capability when greater than
2 GB of memory is present.
thanks,
-bob
I had my SB Audigy 2 ZS almost completely working (a couple of games were
giving me trouble), but I decided (quite regretfully) to manually run
alsaconf. As a result I get no sound output now. Even running yast2 sound
again, and rebooting. All cable connections were rechecked.
yast finds the card and everything. But everytime I try to test the volume
nothing happens. No audio apps seem to be working.
This is stock SuSE 9.2 64bit, completely patched.
The card's IRQ is 185.
I'd really appreciate some help. TIA.
My /etc/modprobe.d/sound:
options snd-emu10k1 enable=1 extin=0x3fff extout=0x7fff index=0 \
max_buffer_size=128 max_synth_voices=64 seq_ports=4
# qnJ_.9jPiZAnlR97:SB Audigy 2 ZS (SB0350)
alias snd-card-0 snd-emu10k1
The module options are
from /usr/src/linux/Documentation/sound/alsa/ALSA-Configuration.txt, and they
were working before I decided to run alsaconf.
These are some log messages I found that could be related:
From dmesg:
drivers/usb/input/hid-input.c: event field not found
drivers/usb/input/hid-input.c: event field not found
Creative EMU10K1 PCI Audio Driver, version 0.20a, 15:26:57 Dec 22 2004
ALSA sound/core/seq/oss/seq_oss.c:234: can't register device seq
ACPI: PCI interrupt 0000:00:0d.0[A] -> GSI 18 (level, low) -> IRQ 185
From /var/log/messages:
Dec 28 13:27:07 severian kernel: ALSA sound/core/seq/oss/seq_oss.c:234: can't
register device seq
Dec 28 13:27:07 severian modprobe: FATAL: Error inserting snd_seq_oss
(/lib/modules/2.6.8-24.10-default/kernel/sound/core/seq/oss/snd-seq-oss.ko):
Device or resource busy
Dec 28 13:27:08 severian kernel: ACPI: PCI interrupt 0000:00:0d.0[A] -> GSI 18
(level, low) -> IRQ 185
Hello,
Set up a directory /sda/home, a raid device, to house all the Linux accounts
and I want to mount it as /home, which is currently on the system drive.
When I try to make a symbolic link from /home to /sda/home the users can't
access their files since root owns the link.
What is the best way to accomplish this?
Thank you in advance,
James
James,
The source permissions are the issue. Check the permissions and
ownership on the source (as in ln -s <source> <target>). Symbolic links
(targets) are always owned by root, but have permissions of 777.
Regards,
Patrick W. Freeman
Systems Specialist
DATAllegro, Inc ... Data at the speed of business
O: (949) 330-7699
-----Original Message-----
From: James D. Parra [mailto:Jamesp@MusicReports.com]
Sent: Tuesday, December 28, 2004 10:08 AM
To: SuSE AMD64 (E-mail)
Subject: [suse-amd64] mounting question; mounting /home to a
sub-directory on another device
Hello,
Set up a directory /sda/home, a raid device, to house all the Linux
accounts
and I want to mount it as /home, which is currently on the system drive.
When I try to make a symbolic link from /home to /sda/home the users
can't
access their files since root owns the link.
What is the best way to accomplish this?
Thank you in advance,
James
--
Check the List-Unsubscribe header to unsubscribe
For additional commands, email: suse-amd64-help(a)suse.com
Hi everyone,
New to the list, new to suse...
I am trying to install suse 9.2 on:
CPU AMD 64 3500+ (939P)
MB ABIT AV8 VIA K8T800 PRO
DDRAM 512x2 OCZ PC3500 433M
DVD+/-RW 16x+ NEC ND-3500A BK
HD 40GB WD
VGA FX5200-DV128 64BIT 8X
I get variations of
crc error
Kernel panic-not syncing: VFS: Unable to mount fs on unknown-block
That includes DVD1, CD1 and CD2 and all modes of installation (safe bla bla...)
I tried to pass to the kernel "linux mem=1Gb" but then I get:
"Can not find kernel image: initrd=initrd64" (Any explanation?)
I also tried "idle=poll" to no avail. (kernel panic)
The USB Legacy Support is disabled - BIOS
Note that the system is brand new - untested. That means that a problem could be anyware. Bad memory (I tried memtest86 - no errors). I run my memory sticks to 400 not 433? - I haven't overclock or anything. Problematic DVD - Unsupported maybe?
On the other hand debian and gentoo installation media do fine. (that is they load both the kernel and the virtual file system on RAM and run their installers)
Do I miss some trivial thing here?
Any ideas?
Best,
Zacharias.
PS: I am a couple of BIOS versions behind. But please if you suggest me to flash to the latest version include the reason you think that could solve the problem. Last time I flashed I had to buy a new mobo...
---------------------------------
Do you Yahoo!?
Dress up your holiday email, Hollywood style. Learn more.
There seems to be a severe problem with the 64 bit Kernel of Suse 9.2.
I am using Tax 2004, it is a 32 bit application running on Wine. It has
its own implementation of wine, which worked with Suse 9.0 and 9.1, but
now I had to use the wine package that comes with Suse 9.2.
After I had fixed the configuration of the paths, I was able to start
the application. It crashes very often, which is not a problem in
itself. But sometimes the screen freezes, the keyboard doesn't react
anymore and finally even a ping to the freezing machine stops working.
The only explanation I have is that the kernel has crashed.
Interesting enough I can start the same application with Transgaming
cedega and it doesn't crash or freeze the machine. (Not all parts of Tax
are working with cedega, so I can't use it all the time.)
My assumption is that the wine package that comes with Suse 9.2 crashes
the 64 bit kernel while running a 32 bit application in user space.
This is a very severe problem and I would rather see that only the 32
bit application crashes, but not the kernel.
Without further assistance I can only guess what is happening here.
Judging by the poor stability of wine it could be the NX feature or of
course any other problem in the kernel.
Has anyone similar experiences with the new kernel?
Regards
Detlef Grittner
-------------------------
uname -a
Linux linux 2.6.8-24.5-default #1 Wed Nov 17 11:10:06 UTC 2004 x86_64
x86_64 x86_64 GNU/Linux
rpm -qi wine
Name : wine Relocations: (not relocatable)
Version : 20040813 Vendor: SUSE LINUX AG,
Nuernberg, Germany
Release : 7 Build Date: Mo 04 Okt 2004
21:30:04CEST
Install date: Sa 04 Dez 2004 14:11:52 CET Build Host: g242.suse.de
Group : System/Emulators/PC Source RPM:
wine-20040813-7.src.rpm
Size : 51062464 License: LGPL, Other
License(s),see package
Signature : DSA/SHA1, Mo 04 Okt 2004 21:39:37 CEST, Key ID
a84edae89c800aca
Packager : http://www.suse.de/feedback
URL : http://www.winehq.com
Summary : An MS Windows emulator (ALPHA)
....