- openSUSE Bugs

[Bug 214202] New: Suspend led blinking after resume after suspend2disk
by bugzilla_noreply＠novell.com 19 Dec '06

19 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=214202 Summary: Suspend led blinking after resume after suspend2disk Product: SUSE Linux 10.1 Version: Final Platform: i686 OS/Version: SuSE Linux 10.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: lashkevi(a)landau.ac.ru QAContact: qa(a)suse.de When I suspend my IBM Thinkpad 600X to disk the suspend led does not blinking, but when I resume after suspend, the led starts to blink and remains blinking till the switching off the computer. There was no such problem in SUSE 9.3, but it appeared in 10.1. I temporarily cured this by addin a line "echo 7 off >/proc/acpi/ibm/led 2>/dev/null" into the file "/usr/lib/powersave/scripts/restore_after_suspend_to_disk", but it is not a real solution. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 15

[Bug 220197] New: monitor settings not properly detected; cannot continue installation
by bugzilla_noreply＠novell.com 19 Dec '06

19 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=220197 Summary: monitor settings not properly detected; cannot continue installation Product: openSUSE 10.2 Version: Beta 2 Platform: x86-64 OS/Version: Other Status: NEW Severity: Blocker Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: francisg(a)gmail.com QAContact: jsrain(a)novell.com I tested a beta1 install on this machine, and things were ok, so this must be new in beta2. The whole actual package installation goes fine, and I'm able to make my user and set the pass. SuSEconfig is run, and then it appears that it's getting to the hardware (i.e. Monitor, Graphics card) detection and the screen goes blank. <Esc> does nothing, and/or leaving it for a long time (couple of minutes) does nothing, too. Some info: root@suse /h/francis> lspci 00:00.0 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge 00:00.1 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge 00:00.2 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge 00:00.3 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge 00:00.4 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge 00:00.7 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 South] 00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80) 00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) 00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) 00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) 00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) 00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) 00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South] 00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60) 00:13.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6200] (rev a1) root@suse /h/francis> hwinfo --monitor 33: None 00.0: 10000 Monitor [Created at monitor.93] Unique ID: rdCR.GcJJsNDmHr6 Hardware Class: monitor Model: "LM19T" Vendor: GRE Device: eisa 0x0000 "LM19T" Serial ID: "0" Resolution: 720x400@70Hz Resolution: 640x480@60Hz Resolution: 640x480@72Hz Resolution: 640x480@75Hz Resolution: 800x600@56Hz Resolution: 800x600@60Hz Resolution: 800x600@72Hz Resolution: 800x600@75Hz Resolution: 1024x768@60Hz Resolution: 1024x768@70Hz Resolution: 1024x768@75Hz Resolution: 1280x1024@75Hz Resolution: 1280x1024@60Hz Size: 359x287 mm Driver Info #0: Max. Resolution: 1280x1024 Vert. Sync Range: 50-76 Hz Hor. Sync Range: 30-80 kHz Bandwidth: 108 MHz Config Status: cfg=new, avail=yes, need=no, active=unknown -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 44

[Bug 223516] New: sax2 does not return to previous state after chosing an improper value
by bugzilla_noreply＠novell.com 19 Dec '06

19 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=223516 Summary: sax2 does not return to previous state after chosing an improper value Product: openSUSE 10.2 Version: Beta 2 Platform: i686 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: f.de.kruijf(a)hetnet.nl QAContact: jsrain(a)novell.com During the installation in the final stage of installation one gets the opportunity to change the configuration of the display and monitor. I did this on my Toshiba laptop with an Intel 855 GM and an LCD monitor of 1024x768@60Hz. I changed the last to 1024x768@75Hz and ended up with a unusable system. I got a clobbered screen and tried <ctrl><alt><backsp> to return to a workable situation, but this did not work. Also a timeout of 30 seconds did not work. Although I still had a clobbered screen I could see being back at the console and init 6 finsihed the situation and I could boot again. However Yast was run again and I had trouble to finish that. In init 5 I did not get a normal screen. I finally managed to restore /etc/X11/xorg.conf and am back in business. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 10

[Bug 227372] New: X11 doesn't work on Supermicro 370DE6/P3TDE6 motherboard when onboard SCSI controller is enabled
by bugzilla_noreply＠novell.com 19 Dec '06

19 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=227372 Summary: X11 doesn't work on Supermicro 370DE6/P3TDE6 motherboard when onboard SCSI controller is enabled Product: SUSE Linux 10.1 Version: Final Platform: i686 OS/Version: SuSE Linux 10.1 Status: NEW Severity: Critical Priority: P5 - None Component: X.Org AssignedTo: sndirsch(a)novell.com ReportedBy: jd_ruan(a)hotmail.com QAContact: sndirsch(a)novell.com X11 just never work when onboard SCSI controller is enabled. Because of this, installation of Opensuse has to be done via text mode. Soft-disabling SCSI in BIOS won't help. I have to hard-disable onboard SCSI controller by setting jumper J60 to 2-3 position. I'v tried both nvidia Geforce2 and Quodro FX/500. Both are AGP card. Repro step: 1. set motherboard jumper J60 to 1-2 position. This will make onboard SCSI enumerable. 2. boot 3. start X window 4. Monitor will stay at no signal or 720x400 resolution 5. At this stage, the system can still respond to <CTRL>-<ALT>-<DEL> 6. reboot machine 7. check /var/log/Xorg.0.log. It was hung at "PCI scan". The last line is (II) PCI: 00:04:2: chip 1106,3104 card 0925,1234 rev 51 class 0c,03,20 hdr 80 8. check the output of lspci Onboard SCSI device should have followed device "00:04:2" if everything had gong smoothly. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 2

[Bug 215619] New: Software Removal Tool
by bugzilla_noreply＠novell.com 19 Dec '06

19 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=215619 Summary: Software Removal Tool Product: SUSE Linux 10.1 Version: Final Platform: i386 OS/Version: SuSE Linux 10.1 Status: NEW Severity: Critical Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: alpha096(a)tpg.com.au QAContact: qa(a)suse.de The software removal tool found off menu system> configuration is capable of reming most of the entire installed system without root authority. This is a security issue. The principle that if an intruder can take over a system can only perform the same functions as the user is now flawed. Now a user can remove the whole system without escalation of authority and dependant files. If you select package you can remove the total installation. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 13

[Bug 190481] save_video_pci_state support for s2ram
by bugzilla_noreply＠novell.com 19 Dec '06

19 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=190481 ------- Comment #16 from seife(a)novell.com 2006-12-19 13:44 MST ------- Created an attachment (id=110415) --> (https://bugzilla.novell.com/attachment.cgi?id=110415&action=view) the s2ram binary if you don't want to install the package, just use this binary for testing :-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 0

[Bug 190481] save_video_pci_state support for s2ram
by bugzilla_noreply＠novell.com 19 Dec '06

19 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=190481 ------- Comment #15 from seife(a)novell.com 2006-12-19 13:41 MST ------- Created an attachment (id=110414) --> (https://bugzilla.novell.com/attachment.cgi?id=110414&action=view) rpm package of current suspend CVS + the pci_save patch Usage is simple: root@strolchi:/tmp# s2ram -h Usage: s2ram [-nhi] [-fspmra] Options: -h, --help: this text. -n, --test: test if the machine is in the database. returns 0 if known and supported -i, --identify: prints a string that identifies the machine. -f, --force: force suspending, even on unknown machines. the following options are only available with --force: -s, --vbe_save: save VBE state before suspending and restore after resume. -p, --vbe_post: VBE POST the graphics card after resume -m, --vbe_mode: get VBE mode before suspend and set it after resume -r, --radeontool: turn off the backlight on radeons before suspending. -a, --acpi_sleep: set the acpi_sleep parameter before suspend 1=s3_bios, 2=s3_mode, 3=both -v, --pci_save: save the PCI config space for the VGA card. -------- so you just add "-v" to the flags you already found out working, in your case the complete command line will probably be "s2ram -f -v -a3" or "s2ram -f -v -p -m" Let me know if this helps :-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 0

[Bug 227653] New: Octal/Technotrend DVB-C card not possible to be configured
by bugzilla_noreply＠novell.com 19 Dec '06

19 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=227653 Summary: Octal/Technotrend DVB-C card not possible to be configured Product: openSUSE 10.2 Version: RC 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: kylmakorpi(a)kolumbus.fi QAContact: jsrain(a)novell.com During installation the installer crashed when it reached DVB-card configuration phase and gave a memory error (sorry, don't remember the exact error message). I passed the installation during second try, RC1 installed itself but when trying to configure the TV-card, Yast just disappears - crashes without any message - when trying to edit the card. Package dvb which contains the firmware is installed but lsmod shows that dvb-ttpci is not present, nor available. I suppose installer is not working properly. The card is functioning fully and normally out-of-the-box-installation with version 10.1, with both 32- and 64-bit versions. If needed, y2logs-, hwinfo- & lsmod-dumps are available, at least some days. Rgs, Ilpo -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 10

[Bug 190481] save_video_pci_state support for s2ram
by bugzilla_noreply＠novell.com 19 Dec '06

19 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=190481 ------- Comment #14 from seife(a)novell.com 2006-12-19 13:31 MST ------- Created an attachment (id=110411) --> (https://bugzilla.novell.com/attachment.cgi?id=110411&action=view) the patch, it applies against current CVS, not sure about the 10.2 version -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 0

[Bug 190481] save_video_pci_state support for s2ram
by bugzilla_noreply＠novell.com 19 Dec '06

19 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=190481 ------- Comment #13 from seife(a)novell.com 2006-12-19 13:29 MST ------- Ok, i still have no hardware, but due to popular demand, and given the answer i got asking "when will this be fixed in kernel?" (the answer was "expect about two years"), i have cooked up a patch :-) I am not able to test it (it does no harm for my machines, but it also does nothing good - they just work as before), so i'd be very interested in your results. I'll attach the patch and the package to this bug -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 0