- openSUSE AMD64

Re: [opensuse-amd64] How to get a wifi connection running between two Pc Linux ?
by patheve 20 Feb '07

20 Feb '07

Hello Well, some news about my problem. At first, a new upgrade of the rt61 module was necessary. Then, I had use to a DHCP server on PC1 ans a DHCP client on PC2. DHCP server is put on interface ra0 of PC1 with a short range of addresses : 10.0.0.2-10.0.0.3. On PC2 this is easier to manage routes ! The token address is 10.0.0.3. Ping or ssh from PC2 work fine. Now, the new challenge is to share my internet connection on PC1 !!! Pascal --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-amd64+help(a)opensuse.org

2 1

[opensuse-amd64] problem with webcam labtec and kernel 2.6.18.2-34 x86_64
by Piotr Modzelewski 19 Feb '07

19 Feb '07

Hi Recently I`ve changed computer on Athlon +3800 X2 and have problem with webcam. Before I used opensuse 10.2 32bit and this webcam worked perfectly Bus 001 Device 003: ID 046d:0929 Logitech, Inc. but on opensuse 10.2 64bit something goes wrong. In log messages I got kernel: /opt/compile/gspcav1-20070110/Sunplus/spca561.h: [spca561_init:497] Find spca561 USB Product ID 929 Feb 16 20:22:29 dziennik kernel: /opt/compile/gspcav1-20070110/gspca_core.c: [spca5xx_set_light_freq:1858] Sensor currently not support light frequency banding filters. Feb 16 20:22:29 dziennik kernel: /opt/compile/gspcav1-20070110/gspca_core.c: [gspca_set_isoc_ep:881] ISO EndPoint found 0x81 AlternateSet 13 Feb 16 20:22:29 dziennik kernel: ohci_hcd 0000:00:02.0: leak ed ffff8100013bf5a0 (#81) state 2 Feb 16 20:22:30 dziennik kernel: /opt/compile/gspcav1-20070110/gspca_core.c: init isoc: usb_submit_urb(0) ret -28 Feb 16 20:22:30 dziennik kernel: /opt/compile/gspcav1-20070110/gspca_core.c: [gspca_set_isoc_ep:881] ISO EndPoint found 0x81 AlternateSet 12 Feb 16 20:22:30 dziennik kernel: ohci_hcd 0000:00:02.0: leak ed ffff8100013bf5f0 (#81) state 2 Feb 16 20:22:30 dziennik kernel: /opt/compile/gspcav1-20070110/gspca_core.c: init isoc: usb_submit_urb(0) ret -28 Feb 16 20:22:30 dziennik kernel: /opt/compile/gspcav1-20070110/gspca_core.c: [gspca_set_isoc_ep:881] ISO EndPoint found 0x81 AlternateSet 11 Feb 16 20:22:30 dziennik kernel: ohci_hcd 0000:00:02.0: leak ed ffff8100013bf640 (#81) state 2 Feb 16 20:22:30 dziennik kernel: /opt/compile/gspcav1-20070110/gspca_core.c: init isoc: usb_submit_urb(0) ret -28 Feb 16 20:22:30 dziennik kernel: /opt/compile/gspcav1-20070110/gspca_core.c: [gspca_set_isoc_ep:881] ISO EndPoint found 0x81 AlternateSet 10 Feb 16 20:22:30 dziennik kernel: ohci_hcd 0000:00:02.0: leak ed ffff8100013bf690 (#81) state 2 Feb 16 20:22:30 dziennik kernel: /opt/compile/gspcav1-20070110/gspca_core.c: init isoc: usb_submit_urb(0) ret -28 Feb 16 20:22:30 dziennik kernel: /opt/compile/gspcav1-20070110/gspca_core.c: [gspca_set_isoc_ep:881] ISO EndPoint found 0x81 AlternateSet 9 Feb 16 20:22:30 dziennik kernel: ohci_hcd 0000:00:02.0: leak ed ffff8100013bf6e0 (#81) state 2 Feb 16 20:22:30 dziennik kernel: /opt/compile/gspcav1-20070110/gspca_core.c: init isoc: usb_submit_urb(0) ret -28 Feb 16 20:22:30 dziennik kernel: /opt/compile/gspcav1-20070110/gspca_core.c: [gspca_set_isoc_ep:881] ISO EndPoint found 0x81 AlternateSet 8 Feb 16 20:22:30 dziennik kernel: ohci_hcd 0000:00:02.0: leak ed ffff8100013bf730 (#81) state 2 Feb 16 20:22:30 dziennik kernel: /opt/compile/gspcav1-20070110/gspca_core.c: init isoc: usb_submit_urb(0) ret -28 Feb 16 20:22:30 dziennik kernel: /opt/compile/gspcav1-20070110/gspca_core.c: [gspca_set_isoc_ep:881] ISO EndPoint found 0x81 AlternateSet 7 Feb 16 20:22:30 dziennik kernel: ohci_hcd 0000:00:02.0: leak ed ffff8100013bf780 (#81) state 2 Feb 16 20:22:30 dziennik kernel: /opt/compile/gspcav1-20070110/gspca_core.c: init isoc: usb_submit_urb(0) ret -28 Feb 16 20:22:30 dziennik kernel: /opt/compile/gspcav1-20070110/gspca_core.c: [gspca_set_isoc_ep:881] ISO EndPoint found 0x81 AlternateSet 6 Feb 16 20:22:30 dziennik kernel: ohci_hcd 0000:00:02.0: leak ed ffff8100013bf7d0 (#81) state 2 Feb 16 20:22:30 dziennik kernel: /opt/compile/gspcav1-20070110/gspca_core.c: init isoc: usb_submit_urb(0) ret -28 Feb 16 20:22:30 dziennik kernel: /opt/compile/gspcav1-20070110/gspca_core.c: [gspca_set_isoc_ep:881] ISO EndPoint found 0x81 AlternateSet 5 Feb 16 20:22:30 dziennik kernel: ohci_hcd 0000:00:02.0: leak ed ffff8100013bf820 (#81) state 2 Feb 16 20:22:30 dziennik kernel: /opt/compile/gspcav1-20070110/gspca_core.c: init isoc: usb_submit_urb(0) ret -28 Feb 16 20:22:30 dziennik kernel: /opt/compile/gspcav1-20070110/gspca_core.c: [gspca_set_isoc_ep:881] ISO EndPoint found 0x81 AlternateSet 4 Feb 16 20:22:30 dziennik kernel: ohci_hcd 0000:00:02.0: leak ed ffff8100013bf870 (#81) state 2 Feb 16 20:22:30 dziennik kernel: /opt/compile/gspcav1-20070110/gspca_core.c: init isoc: usb_submit_urb(0) ret -28 Feb 16 20:22:30 dziennik kernel: /opt/compile/gspcav1-20070110/gspca_core.c: [gspca_set_isoc_ep:881] ISO EndPoint found 0x81 AlternateSet 3 Feb 16 20:22:30 dziennik kernel: ohci_hcd 0000:00:02.0: leak ed ffff8100013bf8c0 (#81) state 2 Feb 16 20:22:30 dziennik kernel: /opt/compile/gspcav1-20070110/gspca_core.c: init isoc: usb_submit_urb(0) ret -28 Feb 16 20:22:30 dziennik kernel: /opt/compile/gspcav1-20070110/gspca_core.c: [gspca_set_isoc_ep:881] ISO EndPoint found 0x81 AlternateSet 2 Feb 16 20:22:30 dziennik kernel: ohci_hcd 0000:00:02.0: leak ed ffff8100013bf910 (#81) state 2 Feb 16 20:22:30 dziennik kernel: /opt/compile/gspcav1-20070110/gspca_core.c: init isoc: usb_submit_urb(0) ret -28 Feb 16 20:22:30 dziennik kernel: /opt/compile/gspcav1-20070110/gspca_core.c: [gspca_set_isoc_ep:881] ISO EndPoint founernateSet 1 Feb 16 20:22:30 dziennik kernel: ohci_hcd 0000:00:02.0: leak ed ffff8100013bf960 (#81) state 2 Feb 16 20:22:30 dziennik kernel: /opt/compile/gspcav1-20070110/gspca_core.c: init isoc: usb_submit_urb(0) ret -28 Feb 16 20:22:30 dziennik kernel: /opt/compile/gspcav1-20070110/gspca_core.c: [spca5xx_open:1923] DEALLOC error on init_Isoc It seems to me that some options in kernel config are different between version 32 and 64bit, but I have no idea which ones Any helps --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-amd64+help(a)opensuse.org

1 0

[opensuse-amd64] /proc/kcore
by Christine Kreuzer 06 Feb '07

06 Feb '07

Hello, recently I got a second AMD Opteron Dual Core and new RAM for my computer. It seems that everything (SLES10) works fine but as I checked the available disk space I saw that the root partition is complete. The reason for this is the file /proc/kcore. Can someone tell me why /proc/kcore can have a size of 5 GB when the RAM has only a size of 4GB? I thought /proc/kcore is a sort of image of the kernel and has the same size as RAM + some kB. Could someone help me please. Best regards, Christine -- Universität des Saarlandes AG Prof. Dr. Christoph Becher Fachrichtung 7.3 (Technische Physik) Geb. E2.6, Zimmer 2.04 D-66123 Saarbrücken Phone:+49(0)681 302 3418 Fax: +49(0)681 302 4676 E-mail: c.kreuzer(a)mx.uni-saarland.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-amd64+help(a)opensuse.org

3 2

Re: [opensuse-amd64] How to get a wifi connection running between two Pc Linux ?
by patheve 31 Jan '07

31 Jan '07

Hello thanks a lot for these informations. They remember me this is like for a cluster with two ethernet networks. I will try as soon as possible. I will tell you if it is better :-) Kind regards Pascal ================================================================================== El dc 31 de 01 del 2007 a les 20:56 +0100, en/na patheve va escriure: > Hello all > > I would like to link my two laptops with a wifi network : > PC n°1 : SuSE 9.2 Pro 64 bits, a wifi PC card built with chipset rt2500 > (module rt2500 up to date) > PC n°2 : SuSE 9.3 Pro 32 bits, a wifi PC card built with chipset rt61 (module > rt61 up to date) > > On each PC, there are eth0 (ethernet) and ra0 (wifi) interfaces. The IP > addresses are : > PC n°1 : eth0 with 192.168.1.101 (mask 255.255.255.0), ra0 with 192.168.1.201 > (mask 255.255.255.0), > no gateway, mode Ad-Hoc and no WEP key for wifi. > PC n°2 : eth0 with 192.168.1.102 (mask 255.255.255.0), ra0 with 192.168.1.202 > (mask 255.255.255.0), > no gateway, mode Ad-Hoc and no WEP key for wifi. Hello, You should use different network addresses for your wifi link. You have two different interfaces connected to the same network 192.168.1.x, your operating system doesn't know where to send packets to. Try: PC1 - eth0 - 192.168.1.2/24 --> modem ( 192.168.1.1 ) -> Internet - ra0 - 10.0.0.1/24 routes on PC1: network 192.168.1.0/24 dev eth0 network 192.168.2.0/24 via 10.0.0.2 network 0/0 via 192.168.1.1 PC2 - ra0 - 10.0.0.2/24 - eth0 - 192.168.2.1/24 routes on PC2 network 192.168.2.0/24 dev eth0 network 0/0 via 10.0.0.1 First of all, configure both ra0 interfaces and get ping working from both computers to 10.0.0.x interfaces. Later configure connection to the internet from PC1, and finally: Configure PC1 to masquerade 192.168.2.x traffic. hope this helps, > On PC n°1, there is an ADSL modem, plugged on eth0 and whose IP address is > 192.168.1.1. About firewall, ra0 is put in internal area without protection > on each PC. > > Normally by doing a ping -I ra0 192.168.1.202 from PC n°1, I should get an > answer ... like by an ethernet cable link. But NO !!! I get this : > ping -I ra0 192.168.1.202 > PING 192.168.1.202 (192.168.1.202) from 192.168.1.101 ra0: 56(84) bytes of > data. > From 192.168.1.201: icmp_seq=2 Destination Host Unreachable > From 192.168.1.201 icmp_seq=2 Destination Host Unreachable > From 192.168.1.201 icmp_seq=3 Destination Host Unreachable > From 192.168.1.201 icmp_seq=4 Destination Host Unreachable > From 192.168.1.201 icmp_seq=6 Destination Host Unreachable > > That's curious. No better effect with a gateway 192.168.1.201 put on PC n°1. > Am I forgetting something in network configuration ? If I put a name in ESSID > for PC n°1 for example, from the other PC I can see the name. So it seems > that wifi on each PC is OK but something is missing or is not properly > working. Any idea ?? A problem of firewall ? I put ra0 of each PC in internal > area, so it should not be a problem at this level. But .... > > Thanks > > Pascal > --------------------------------------------------------------------- > To unsubscribe, e-mail: opensuse-amd64+unsubscribe@xxxxxxxxxxxx > For additional commands, e-mail: opensuse-amd64+help@xxxxxxxxxxxx > -- --- Jordi Bruguera i Cortada <jordi@xxxxxx> Consultor en Programari Lliure LPIC1-ID: 000001116 Linux User #21587 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-amd64+help(a)opensuse.org

1 0

[opensuse-amd64] How to get a wifi connection running between two Pc Linux ?
by patheve 31 Jan '07

31 Jan '07

Hello all I would like to link my two laptops with a wifi network : PC n°1 : SuSE 9.2 Pro 64 bits, a wifi PC card built with chipset rt2500 (module rt2500 up to date) PC n°2 : SuSE 9.3 Pro 32 bits, a wifi PC card built with chipset rt61 (module rt61 up to date) On each PC, there are eth0 (ethernet) and ra0 (wifi) interfaces. The IP addresses are : PC n°1 : eth0 with 192.168.1.101 (mask 255.255.255.0), ra0 with 192.168.1.201 (mask 255.255.255.0), no gateway, mode Ad-Hoc and no WEP key for wifi. PC n°2 : eth0 with 192.168.1.102 (mask 255.255.255.0), ra0 with 192.168.1.202 (mask 255.255.255.0), no gateway, mode Ad-Hoc and no WEP key for wifi. On PC n°1, there is an ADSL modem, plugged on eth0 and whose IP address is 192.168.1.1. About firewall, ra0 is put in internal area without protection on each PC. Normally by doing a ping -I ra0 192.168.1.202 from PC n°1, I should get an answer ... like by an ethernet cable link. But NO !!! I get this : ping -I ra0 192.168.1.202 PING 192.168.1.202 (192.168.1.202) from 192.168.1.101 ra0: 56(84) bytes of data. From 192.168.1.201: icmp_seq=2 Destination Host Unreachable From 192.168.1.201 icmp_seq=2 Destination Host Unreachable From 192.168.1.201 icmp_seq=3 Destination Host Unreachable From 192.168.1.201 icmp_seq=4 Destination Host Unreachable From 192.168.1.201 icmp_seq=6 Destination Host Unreachable That's curious. No better effect with a gateway 192.168.1.201 put on PC n°1. Am I forgetting something in network configuration ? If I put a name in ESSID for PC n°1 for example, from the other PC I can see the name. So it seems that wifi on each PC is OK but something is missing or is not properly working. Any idea ?? A problem of firewall ? I put ra0 of each PC in internal area, so it should not be a problem at this level. But .... Thanks Pascal --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-amd64+help(a)opensuse.org

2 1

[opensuse-amd64] YOU problem
by Philippe Andersson 31 Jan '07

31 Jan '07

Hi list, Maybe not the best place for this question, but I'm sure some of you must have the answer: Fresh install of OpenSuSE 10.2 (minimal install -- no X). Network properly configured. Start "yast" in ncurses mode, select "Online Update". It loads the list of installed packages and then reports that no patches are available. Based on a quick look on the site (ftp.suse.com), it looks like some patches are available (which is expected, a few months after the release). Is there some change in Yast that I missed (since the 9.3 version) ? YOU used to ask you which server it should connect to to retrieve the patches, but it doesn't seem to do that any longer. Any help or pointer to the relevant doc is appreciated. Thanks in advance. Cheers. Bye. Ph. A. -- *Philippe Andersson* Unix System Administrator IBA Particle Therapy | Tel: +32-10-475.983 Fax: +32-10-487.707 eMail: pan(a)iba-group.com <http://www.iba-worldwide.com> The contents of this e-mail message and any attachments are intended solely for the recipient (s) named above. This communication is intended to be and to remain confidential and may be protected by intellectual property rights. Any use of the information contained herein (including but not limited to, total or partial reproduction, communication or distribution of any form) by persons other than the designated recipient(s) is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free. Ion Beam Applications does not accept liability for any such errors. Thank you for your cooperation. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-amd64+help(a)opensuse.org

2 1

[opensuse-amd64] Trouble installing openSuSE 10.2 due to pci_init
by brian_linux 23 Jan '07

23 Jan '07

Hello: I am having difficulty upgrading my openSuSE 10.1 installation to openSuSE 10.2. In fact, my difficult arises from the fact that I cannot reliably boot into the installation program. Background: (1) I have a Tyan K8HM 3892S motherboard and two dual-core Opterons. (2) I installed the latest BIOS (1.05). I tried a number of BIOS settings but they are currently set to "optimal defaults". (3) openSuSE 10.1 runs without any known problems. Originally I had the double realtime clock issue but a previous BIOS update fixed that. (4) I'm using the openSuSE 10.2 install DVD. I checked the MD5 and it matched. I have also burned a number of DVDs, even using different programs and the behavior is consistent. Issue: (1) The DVD starts to boot. In fact I can get to the "main screen" where I can select to "Boot from the Hard Drive", "Install", ... (2) When I select install to start the upgrade, usually the system hangs. (3) I installed using text mode and the initcall_debug kernel option and I can see progress up until the following: Calling initcall 0xffffffff80317987: pci_init +0x0/0x2b() What I find weird is that sometimes the system will get into the install program, but the vast majority of the time it will not. So it's intermittent. I haven't been able to identify any pattern that I can use to predict whether it'll work on any given boot sequence. Does anyone have any suggestions? This isn't a crisis since I have 10.1 working well, it's just that I really wanted to upgrade to 10.2. Of course I'm willing to provide additional information to the best of my ability. I'm somewhat competent, but must admit that I'm a little out of my comfort zone. Any help or suggestions would be greatly appreciated. Thank you. Brian Schang --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-amd64+help(a)opensuse.org

2 1

[opensuse-amd64]
by r.ramos＠freenet.de 13 Jan '07

13 Jan '07

Hi all, I have upgraded to 10.2. I have the following problem with an avm fritzcard dsl sl usb device. With 10.1 I didn't have any problems. <4>NMI Watchdog detected LOCKUP on CPU 0 <4>CPU 0 <4>Modules linked in: fcdslslusb capi capifs kernelcapi usbhid nvidia ohci1394 snd_intel8x0 snd_ac97_codec snd_ac97_bus ieee1394 ide_cd cdrom snd_pcm snd_timer forcedeth snd soundcore snd_page_alloc ohci_hcd ehci_hcd i2c_nforce2 i2c_core usbcore parport_pc lp parport reiserfs edd fan sg sata_nv libata amd74xx thermal processor sd_mod scsi_mod ide_disk ide_core <4>Pid: 1842, comm: capiinit Tainted: P U 2.6.18.2-34-default #1 <4>RIP: 0010:[.text.lock.spinlock+34/138] [.text.lock.spinlock+34/138] .text.lock.spinlock+0x22/0x8a <4>RSP: 0018:ffff81007b8c9c70 EFLAGS: 00000086 <4>RAX: 0000000000000282 RBX: 0000000000000800 RCX: ffffffff8887b840 <4>RDX: ffff81007b8c9cb0 RSI: ffff81007b8c9cb8 RDI: ffff81007a55724c <4>RBP: ffff81007a557244 R08: ffff81007bad5004 R09: 0000000000000000 <4>R10: 0000000000000003 R11: ffff81007ff14980 R12: ffff81007a55724c <4>R13: ffff81007b8c9cb8 R14: ffff81007b8c9cb0 R15: 0000000000000000 <4>FS: 00002b24a519d6f0(0000) GS:ffffffff805b7000(0000) knlGS:0000000000000000 <4>CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b <4>CR2: 00002b24a4cbb000 CR3: 000000007b6df000 CR4: 00000000000006e0 <4>Process capiinit (pid: 1842, threadinfo ffff81007b8c8000, task ffff81007d7f5080) <4>Stack: ffffffff8889f0b2 0000000000000800 ffffffff8887b840 ffff81007bad5004 <4> ffff81007bad5024 0000000000000800 ffffffff8889b3cb 0000000000000003 <4> 0000000000000003 0000000000000000 0000000000000246 0000000000000800 <4>Call Trace: <4> [_end+136900786/2130640896] :fcdslslusb:claim_urb+0x1d/0x8f <4> [_end+136755264/2130640896] :fcdslslusb:Block_RxHandler+0x0/0x4d0 <4> [_end+136885195/2130640896] :fcdslslusb:os_usb_submit_rx+0x32/0xe9 <4> [_end+136893893/2130640896] :fcdslslusb:OSHWRxBuffer+0x44/0x4f <4> [_end+136527809/2130640896] :fcdslslusb:BLK_Start+0x91/0xe0 <4> [_end+136531091/2130640896] :fcdslslusb:E1_Activate+0x13/0x20 <4> [_end+136454454/2130640896] :fcdslslusb:CM_Activate+0x6/0x50 <4> [_end+136889408/2130640896] :fcdslslusb:start+0x1b4/0x21f <4> [_end+136889849/2130640896] :fcdslslusb:load_ware+0x14e/0x1ab <4> [_end+136295344/2130640896] :kernelcapi:capi20_manufacturer+0x2d5/0x57c <4> [do_gettimeofday+80/148] do_gettimeofday+0x50/0x94 <4> [getnstimeofday+16/40] getnstimeofday+0x10/0x28 <4> [rb_insert_color+97/218] rb_insert_color+0x61/0xda <4> [enqueue_hrtimer+85/112] enqueue_hrtimer+0x55/0x70 <4> [_end+136407267/2130640896] :capi:capi_ioctl+0x2c1/0x441 <4> [do_ioctl+85/107] do_ioctl+0x55/0x6b <4> [vfs_ioctl+584/609] vfs_ioctl+0x248/0x261 <4> [sys_ioctl+89/120] sys_ioctl+0x59/0x78 <4> [system_call+126/131] system_call+0x7e/0x83 <4> <4> <4>Code: 83 3f 00 7e f9 e9 d4 fe ff ff f3 90 83 3f 00 7e f9 e9 d3 fe <4>console shuts up ... And here is the beginnning of the log: Inspecting /boot/System.map-2.6.18.2-34-default Loaded 23895 symbols from /boot/System.map-2.6.18.2-34-default. Symbols match kernel version 2.6.18. No module symbols loaded - kernel modules not enabled. klogd 1.4.1, log source = ksyslog started. <4>Bootdata ok (command line is root=/dev/sda6 vga=0x317 resume=/dev/sda5 splash=silent) <5>Linux version 2.6.18.2-34-default (geeko@buildhost) (gcc version 4.1.2 20061115 (prerelease) (SUSE Linux)) #1 SMP Mon Nov 27 11:46:27 UTC 2006 I have attached the complete log. Thank you Ramon Ramos "Jetzt Handykosten senken mit klarmobil - 14 Ct./Min.! Hier klicken" http://www.klarmobil.de/index.html?pid=73025 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-amd64+help(a)opensuse.org

1 0

[opensuse-amd64] opensuse 10.2 a100u2w and k8temp modules AWOL on x86_64?
by Bernd Felsche 01 Jan '07

01 Jan '07

I've recently installed opensuse 10.2 (release) on some new hardware and have found that the a100u2w and k8temp modules are missing. CPU AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ in Gigabyte GA-M55plus-S3G mainboard with 1GB RAM Everything else works fine. Nice and stable. The former drives the Initio A100U2W SCSI host adapter (modprobe during boot tries but can't load absent module) and the latter is suggested by sensors-detect to ascertain the processor temperature. Driver `k8temp' (should be inserted): Detects correctly: * ISA bus, undetermined address (Busdriver `i2c-isa') Chip `AMD K8 thermal sensors' (confidence: 9) I've tried to figure out why they are absent but can't work it out. Kernel configuration provides the option to build the a100u2w module, and it's compiling now, but I'm stuck on the k8temp as there's no obvious option to build that. -- /"\ Bernd Felsche - Innovative Reckoning, Perth, Western Australia \ / ASCII ribbon campaign | "If we let things terrify us, X against HTML mail | life will not be worth living." / \ and postings | Lucius Annaeus Seneca, c. 4BC - 65AD. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-amd64+help(a)opensuse.org

1 0

[opensuse-amd64] SuSE 10.2 where is XF86Conf
by Harald Finster 30 Dec '06

30 Dec '06

Hello, after long frustrating days attempting to install Debian on my new system, I gave up and returned back to SuSE 10.2. Installation from DVD worked like a charm. (Except a small problem with an existing RAID, which could be solved by cleaning the discs with sand-paper :-) (seriously: dd if=/dev/null of=/dev/sdxxx) Now my current problem: I would like to use a Matrox G550 in dual head mode. At the moment, I am able to configure a single monitor with yast2/sax2 - no problem. According to an older posting, I would like to add an additional Display section in XF86Config. Now, the problem is: where is XF86Config? (I had a look at /etc/X11 and also tried a 'find') At the moment, the behaviour is quite strange: A Samsung Syncmaster 204B is attached to Port A A CRT ADI monitor is attached to Port B The 'console' (F1) is shown on both screens. After startup of runlevel 5, the X11 display appears on the ADI monitor (flickering), whereas the Samsung remains dark. If I swap the connectors, the situation remains the same. Any ideas/suggestions? Thanks in advance. Greetings Harald -- Dr.-Ing. Harald Finster / Aachen Germany http://www.finster-stahlart.de industrial history and architecture http://www.astrid-aix.de gallery: watercolours and oil paintings --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-amd64+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-amd64+help(a)opensuse.org

3 3