January 2008 - openSUSE Mobile (Deutsch)

Re: [opensuse-mobile-de] 10.2 auf einem T23
by Franz Bakan 02 Dec '08

02 Dec '08

On Fri, 6 Jul 2007 08:06:33 +0200, Roger Petry wrote: > > - Der Rechner rödelt nach dem booten minutenlang mit 100% CPU-Last > > und man weiss nicht was er tut, ausser dass er laufend auf die Festplatte > > zugreift. > > - Updates dauern ewig lange, das ganze Prüfen der Abhängikeiten etc. > > frisst unendlich viel Zeit. > zmd und beagle entfernen Und wie genau entfernt man die beiden? Muss man da irgendwelche ini-scripts editieren? Wenn ja, welche? Oder geht das mittels GUI/Yast? Gruß Franz --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-mobile-de+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-mobile-de+help(a)opensuse.org

2 6

neues Kernelpatch
by Christoph Pache 01 Feb '08

01 Feb '08

Habe den neuen Kernel 2.6.22.16-0.1 installiert. seitdem funktioniert die CPU-Geschwindigkeitsanpassung nicht mehr und die CPU brummt bei 1,8 Ghz. Mein System ist eine Opensuse 10.3 auf einem Benq Joybook R55 g22 mit Core duo Prozessor T2400, nvidia Geforce Go 7400, 2 GB Ram, und 80 GB Festplatte. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-mobile-de+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-mobile-de+help(a)opensuse.org

3 3

10.2: touchpad geht nach s2ram nicht mehr / Amilo v2010
by Ekkard Gerlach 27 Jan '08

27 Jan '08

Hallo, bin mit 10.2 zufrieden, nach dem neusten Kernelupdate funktioniert s2disk out of the box. s2ram muckt noch rum, mit framebuffer gehts nicht, vga=0 ist notwendig. Dann gehts nach: echo 2 > /proc/sys/kernel/acpi_video_flags # s2 s2ram -f -p -m s3 geht nicht. s1 auch schon probiert. Die anderen Beispiel für s2ram -..... aus http://en.opensuse.org/S2ram habe ich durchprobiert, es geht nur bei s2ram -f -p -m. Leider will das touchpad nach einem r2ram nicht mehr. Ein strg-alt-F1 -> strg-alt-F7 hilft auch nicht. Hat jemand einen Tipp? Gruss Ekkard Anhang: ======= dmesg: [...] mice: PS/2 mouse device common for all mice [...] amilo:~ # s2ram -i This machine can be identified by: sys_vendor = "FUJITSU SIEMENS" sys_product = "AMILO V Series" sys_version = "" bios_version = "1.0D-0031-0812" See http://en.opensuse.org/S2ram for details. xorg.conf: [...] Section "Device" Identifier "VIA Technologies, Inc. S3 Unichrome Pro VGA Adapter" Driver "via" BusID "PCI:1:0:0" EndSection [...] Section "ServerLayout" Identifier "Default Layout" Screen "Default Screen" InputDevice "Generic Keyboard" InputDevice "Configured Mouse" InputDevice "stylus" "SendCoreEvents" InputDevice "cursor" "SendCoreEvents" InputDevice "eraser" "SendCoreEvents" EndSection [...] amilo:~ # lspci 00:00.0 Host bridge: VIA Technologies, Inc. CN400/PM880 Host Bridge 00:00.1 Host bridge: VIA Technologies, Inc. CN400/PM880 Host Bridge 00:00.2 Host bridge: VIA Technologies, Inc. CN400/PM880 Host Bridge 00:00.3 Host bridge: VIA Technologies, Inc. CN400/PM880 Host Bridge 00:00.4 Host bridge: VIA Technologies, Inc. CN400/PM880 Host Bridge 00:00.7 Host bridge: VIA Technologies, Inc. CN400/PM880 Host Bridge 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge 00:06.0 Network controller: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01) 00:0c.0 CardBus bridge: ENE Technology Inc CB1410 Cardbus Controller (rev 01) 00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) 00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80) 00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge 00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) 00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50) 00:11.6 Communication controller: VIA Technologies, Inc. AC'97 Modem Controller (rev 80) 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74) 01:00.0 VGA compatible controller: VIA Technologies, Inc. S3 Unichrome Pro VGA Adapter (rev 02) lspci -vv [...] 01:00.0 VGA compatible controller: VIA Technologies, Inc. S3 Unichrome Pro VGA Adapter (rev 02) (prog-if 00 [VGA]) Subsystem: Fujitsu Siemens Computer GmbH Unknown device 1078 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: 64 (500ns min) Interrupt: pin A routed to IRQ 7 Region 0: Memory at f0000000 (32-bit, prefetchable) [size=64M] Region 1: Memory at d1000000 (32-bit, non-prefetchable) [size=16M] Capabilities: [60] Power Management version 2 Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [70] AGP version 2.0 Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4 Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none> amilo:~ # cat /proc/cmdline root=/dev/hda2 maxcpus=0 resume=/dev/hda6 vga=0 amilo:~ # s2ram -f -p -m Switching from vt7 to vt1 Calling get_mode Calling do_post Calling set_vbe_mode Calling INT 0x1A (F000:FE6E) EAX is 0xB108 switching back to vt7 /var/log/messages eines s2ram: Jan 18 01:12:52 amilo kernel: Freezing cpus ... Jan 18 01:12:52 amilo kernel: Stopping tasks: =========================================================================| Jan 18 01:12:52 amilo kernel: ACPI: PCI interrupt for device 0000:00:11.5 disabled Jan 18 01:12:52 amilo kernel: ACPI: PCI interrupt for device 0000:00:10.3 disabled Jan 18 01:12:52 amilo kernel: ACPI: PCI interrupt for device 0000:00:10.1 disabled Jan 18 01:12:52 amilo kernel: ACPI: PCI interrupt for device 0000:00:10.0 disabled Jan 18 01:12:52 amilo kernel: ACPI: PCI interrupt for device 0000:00:0c.0 disabled Jan 18 01:12:52 amilo kernel: wlan0: got suspend request (event 2) Jan 18 01:12:52 amilo kernel: Intel machine check architecture supported. Jan 18 01:12:52 amilo kernel: Intel machine check reporting enabled on CPU#0. Jan 18 01:12:52 amilo kernel: Back to C! Jan 18 01:12:52 amilo kernel: PM: Writing back config space on device 0000:00:01.0 at offset 7 (was 222000f0, writing e22000f0) Jan 18 01:12:52 amilo kernel: PCI: Setting latency timer of device 0000:00:01.0 to 64 Jan 18 01:12:52 amilo kernel: wlan0: got resume request Jan 18 01:12:52 amilo kernel: PM: Writing back config space on device 0000:00:06.0 at offset f (was 100, writing 1ff) Jan 18 01:12:52 amilo kernel: PM: Writing back config space on device 0000:00:06.0 at offset 4 (was ffffe000, writing d0002000) Jan 18 01:12:52 amilo kernel: PM: Writing back config space on device 0000:00:06.0 at offset 3 (was 0, writing 4008) Jan 18 01:12:52 amilo kernel: PM: Writing back config space on device 0000:00:06.0 at offset 1 (was 4100000, writing 4100016) Jan 18 01:12:52 amilo kernel: PM: Writing back config space on device 0000:00:0c.0 at offset 1 (was 2100000, writing 2100007) Jan 18 01:12:52 amilo kernel: ACPI: PCI Interrupt 0000:00:0c.0[A] -> Link [LNKB] -> GSI 10 (level, low) -> IRQ 10 Jan 18 01:12:52 amilo kernel: ACPI: PCI Interrupt 0000:00:10.0[A] -> Link [LNKA] -> GSI 7 (level, low) -> IRQ 7 Jan 18 01:12:52 amilo kernel: usb usb2: root hub lost power or was reset Jan 18 01:12:52 amilo kernel: ACPI: PCI Interrupt 0000:00:10.1[B] -> Link [LNKB] -> GSI 10 (level, low) -> IRQ 10 Jan 18 01:12:52 amilo kernel: usb usb3: root hub lost power or was reset Jan 18 01:12:52 amilo kernel: ACPI: PCI Interrupt 0000:00:10.3[D] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11 Jan 18 01:12:52 amilo kernel: usb usb1: root hub lost power or was reset Jan 18 01:12:52 amilo kernel: ehci_hcd 0000:00:10.3: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 Jan 18 01:12:52 amilo kernel: PM: Writing back config space on device 0000:00:11.1 at offset 3 (was 0, writing 4000) Jan 18 01:12:52 amilo kernel: PM: Writing back config space on device 0000:00:11.5 at offset f (was 300, writing 305) Jan 18 01:12:52 amilo kernel: PM: Writing back config space on device 0000:00:11.5 at offset 4 (was 1, writing 1401) Jan 18 01:12:52 amilo kernel: PCI: Enabling device 0000:00:11.5 (0000 -> 0001) Jan 18 01:12:52 amilo kernel: ACPI: PCI Interrupt 0000:00:11.5[C] -> Link [LNKC] -> GSI 5 (level, low) -> IRQ 5 Jan 18 01:12:52 amilo kernel: PM: Writing back config space on device 0000:00:11.6 at offset f (was 300, writing 3ff) Jan 18 01:12:52 amilo kernel: PM: Writing back config space on device 0000:00:11.6 at offset 4 (was 1, writing 1801) Jan 18 01:12:52 amilo kernel: PM: Writing back config space on device 0000:00:12.0 at offset f (was 8030100, writing 8030107) Jan 18 01:12:52 amilo kernel: PM: Writing back config space on device 0000:00:12.0 at offset 5 (was 0, writing d0000400) Jan 18 01:12:52 amilo kernel: PM: Writing back config space on device 0000:00:12.0 at offset 4 (was 1, writing 1c01) Jan 18 01:12:52 amilo kernel: PM: Writing back config space on device 0000:00:12.0 at offset 3 (was 0, writing 4008) Jan 18 01:12:52 amilo kernel: PM: Writing back config space on device 0000:00:12.0 at offset 1 (was 2100080, writing 2100017) Jan 18 01:12:52 amilo kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 Jan 18 01:12:52 amilo kernel: PM: Writing back config space on device 0000:01:00.0 at offset b (was 31181106, writing 10781734) Jan 18 01:12:52 amilo kernel: PM: Writing back config space on device 0000:01:00.0 at offset 1 (was 2300003, writing 2300007) Jan 18 01:12:52 amilo kernel: pnp: Failed to activate device 00:07. Jan 18 01:12:52 amilo kernel: pnp: Failed to activate device 00:08. Jan 18 01:12:52 amilo kernel: Restarting tasks... done Jan 18 01:12:52 amilo kernel: Thawing cpus ... --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-mobile-de+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-mobile-de+help(a)opensuse.org

1 1

[10.3] Suspend mit Dell Latitude 830 und Dell Quadro NVS 140M
by Martin Schröder 07 Jan '08

07 Jan '08

Moin, hat jemand mit der Hardware brauchbaren Suspend hinbekommen? Bei mir schläft er mit dem Nvidia-BLOB nicht richtig ein und mit dem nv-Treiber wacht er nich wieder auf... :-( Auf https://wiki.ubuntu.com/LaptopTestingTeam/DellLatitudeD830 gibt's eine Lösung für Ubuntu, aber wie "übersetze" ich deren /etc/default/acpi-support für SUSE? Gruß Martin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-mobile-de+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-mobile-de+help(a)opensuse.org

1 0

suspend nach update von 10.2 auf 10.3 kaputt
by Hungerpirat 02 Jan '08

02 Jan '08

Hallo Liste, ich habe ein Samsung X30 notebook. mit der 10.2 konnte ich nach der SDB suspend2ram einrichten. seit dem update auf die 10.3 schläft das notebook ein, beim aufwachen habe ich allerdings einen hellen farbigen bildschirm, der die farbe langsam ändert. danach hilft nur noch der harte reset. vermutlich liegts am grafikkartentreiber, doch wo fang ich an zu suchen ? mehr info: - grafikkarte ist eine nvidia geforce 5200 mit folgendem treiber: - rpm -qa |grep nvidia nvidia-gfxG01-kmp-default-100.14.19_2.6.22.5_30-1.1 x11-video-nvidiaG01-100.14.19-4 - lsmod | grep agp agpgart 35764 1 nvidia - xorg.conf Section "Device" BoardName "GeForce FX Go5200 32M/64M" BusID "1:0:0" Driver "nvidia" Identifier "Device[0]" VendorName "NVIDIA" Option "NvAGP" "1" EndSection vielen dank für die hilfe! --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-mobile-de+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-mobile-de+help(a)opensuse.org

3 2