ubuntu 10.10 or above not support sis chipset(not the video card)

[prcxjb]

ubuntu 10.04 with a kernel 2.6 or lower works well on my SIS motherboard, but using ubuntu 10.10 or higher I cannot boot into Ubuntu. I'm now using ubuntu 12.04 on an ASUS F81SE notebook with SIS motherboard,and I can't boot it normally.

Mainline kernel version bisect revealed:
v2.6.34-rc1/:well
v2.6.34.1-maverick/:fail

WORKAROUND: Add:
acpi=off

to the grub line.

WORKAROUND: Disable wlan in bios.

WORKAROUND: Download kernel 2.6.34 or lower (used by ubuntu 10.04) from http://kernel.ubuntu.com/~kernel-ppa/mainline/ and boot the system by this kernel.

So i guess ubuntu must have removed sis motherboard acpi support from kernel 2.6 or higher(perhaps linux kernel team should be responsible for it).Please give me an a explanation about it .
Something has to be pointed out that this bug has nothing to do with the video card or video driver!
This bug exists in ALL computers based on SIS motherboard running ubuntu 10.10 or above.

---
AcpiTables:

AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu13
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: SIS966 [HDA SIS966], device 0: ALC269 Analog [ALC269 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: prcxjb 1725 F.... pulseaudio
 /dev/snd/controlC0: prcxjb 1725 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'SIS966'/'HDA SIS966 at 0xfddf4000 irq 18'
   Mixer name : 'Realtek ALC269'
   Components : 'HDA:10ec0269,10431883,00100004'
   Controls : 18
   Simple ctrls : 10
Card1.Amixer.info:
 Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfdeec000 irq 40'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100100'
   Controls : 6
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=141250af-8ad0-41b9-b9d1-4d8829cb83ea
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3)
MachineType: ASUSTeK Computer Inc. F81Se
NonfreeKernelModules: fglrx
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-32-generic-pae root=UUID=0515cb25-936f-47a4-8f4d-b08dec76319f ro quiet splash vt.handoff=7 acpi=off
ProcVersionSignature: Ubuntu 3.2.0-32.51-generic-pae 3.2.30
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-32-generic-pae N/A
 linux-backports-modules-3.2.0-32-generic-pae N/A
 linux-firmware 1.79.1
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: precise running-unity
Uname: Linux 3.2.0-32-generic-pae i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 11/12/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 217
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: F81Se
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr217:bd11/12/2009:svnASUSTeKComputerInc.:pnF81Se:pvr1.0:rvnPEGATRONCORPORATION:rnF81Se:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:
dmi.product.name: F81Se
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1066524

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[prcxjb (prcxjb)]

apport information

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.6 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. Please only remove that one tag and leave the other tags. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6.2-quantal/

[Christopher M. Peñalver (penalvch)]

prcxjb, could you please utilize your WORKAROUND, boot into a Ubuntu kernel that came with Precise, and execute the following in a terminal:
apport-collect 1066524

[prcxjb (prcxjb)]

apport information

[prcxjb (prcxjb)]

apport information

[prcxjb (prcxjb)]

apport information

[prcxjb (prcxjb)]

apport information

[prcxjb (prcxjb)]

apport information

[prcxjb (prcxjb)]

apport information

[prcxjb (prcxjb)]

apport information

[prcxjb (prcxjb)]

apport information

[prcxjb (prcxjb)]

apport information

[prcxjb (prcxjb)]

apport information

[prcxjb (prcxjb)]

apport information

[prcxjb (prcxjb)]

apport information

[prcxjb (prcxjb)]

apport information

[prcxjb (prcxjb)]

apport information

[prcxjb (prcxjb)]

apport information

[prcxjb (prcxjb)]

apport information

[prcxjb (prcxjb)]

apport information

[prcxjb (prcxjb)]

apport information

[prcxjb (prcxjb)]

apport information

[prcxjb (prcxjb)]

apport information

[Christopher M. Peñalver (penalvch)]

prcxjb, thank you for performing the apport-collect.

Regarding your three WORKAROUNDs, do you have to use all 3 simultaneously in Precise, or just any one of them?

As well, the next step is to perform a mainline kernel bisect from v2.6.34-lucid to v2.6.35.14-maverick, in order to identify the last known working mainline kernel, and the first bad one. As per http://kernel.ubuntu.com/~kernel-ppa/mainline/ the kernels we have are:

v2.6.34-lucid/
v2.6.34-rc1/
v2.6.34.1-maverick/
v2.6.34.2-maverick/
v2.6.34.3-maverick/
v2.6.34.4-maverick/
v2.6.34.5-maverick/
v2.6.34.6-maverick/
v2.6.34.7-maverick/
v2.6.34.8-maverick/
v2.6.34.9-maverick/
v2.6.34.10-maverick/
v2.6.34.11-maverick/
v2.6.34.12-maverick/
v2.6.34.13-maverick/
v2.6.35-maverick/
v2.6.35-rc1-lucid/
v2.6.35-rc2-maverick/
v2.6.35-rc3-maverick/
v2.6.35-rc4-maverick/
v2.6.35-rc5-maverick/
v2.6.35-rc6-maverick/
v2.6.35.1-maverick/
v2.6.35.2-maverick/
v2.6.35.3-maverick/
v2.6.35.4-maverick/
v2.6.35.5-maverick/
v2.6.35.6-maverick/
v2.6.35.7-maverick/
v2.6.35.8-maverick/
v2.6.35.9-maverick/
v2.6.35.10-maverick/
v2.6.35.11-maverick/
v2.6.35.12-maverick/
v2.6.35.13-maverick/
v2.6.35.13-original-maverick/
v2.6.35.14-maverick/

Hence, could you please test http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.35-rc2-maverick/ ?

Thank you for your understanding.

Helpful Bug Reporting Tips:
https://help.ubuntu.com/community/ReportingBugs

[prcxjb (prcxjb)]

If i use a ubuntu kernel lower than 2.6.34,there is no need for me to disable wlan in bios or add "acpi=off" to the grub line.Each of the 3 WORKAROUNDs works well independently.
I have tesetd almost all the kernels you listed.It's really a big job.

v2.6.34-lucid/:well
v2.6.34-rc1/:well
v2.6.34.1-maverick/:fail
v2.6.34.2-maverick/:not test
v2.6.34.3-maverick/:not test
v2.6.34.4-maverick/:not test
v2.6.34.5-maverick/:not test
v2.6.34.6-maverick/:not test
v2.6.34.7-maverick/:not test
v2.6.34.8-maverick/:not test
v2.6.34.9-maverick/:not test
v2.6.34.10-maverick/:not test
v2.6.34.11-maverick/:not test
v2.6.34.12-maverick/:not test
v2.6.34.13-maverick/:fail
v2.6.35-maverick/:fail
v2.6.35-rc1-lucid/:well
v2.6.35-rc2-maverick/:fail
v2.6.35-rc3-maverick/:not test
v2.6.35-rc4-maverick/:not test
v2.6.35-rc5-maverick/:not test
v2.6.35-rc6-maverick/:not test
v2.6.35.1-maverick/:fail
We can see that kernels made for lucid work well."v2.6.35-rc1-lucid" is the last kernel made for lucid ,so it's the newest kernel working well on my computer.

[Christopher M. Peñalver (penalvch)]

prcxjb, thank you for performing the upstream kernel bisection. In order to further limit the work necessary to bisect this problem, for now, let us not focus on the results for:
v2.6.35-rc1-lucid/:well

Instead, let us focus on:
v2.6.34-rc1/:well
v2.6.34.1-maverick/:fail

The next step is to perform a commit bisect from upstream v2.6.34-rc1 to v2.6.34.1-maverick, in order to identify the offending commit(s). Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Thank you for your understanding.

Helpful Bug Reporting Tips:
https://help.ubuntu.com/community/ReportingBugs

[prcxjb (prcxjb)]

I notice that there are some kernels made for maverick lower than kernel v2.6.34-rc1:
v2.6.33.6-maverick/
v2.6.33.7-maverick/
v2.6.33.20-maverick/
Do I need to test them as well?

[Christopher M. Peñalver (penalvch)]

prcxjb, regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066524/comments/28 :
>"I notice that there are some kernels made for maverick lower than kernel v2.6.34-rc1:
v2.6.33.6-maverick/
v2.6.33.7-maverick/
v2.6.33.20-maverick/
Do I need to test them as well?"

No.

[prcxjb (prcxjb)]

I have done it following the instructions

"Build Upstream Test Kernel
The next step is to run the mainline-build-one script. This script will build an upstream kernel that will be able to install and run on a Ubuntu system. Run the mainline-build-one script as follows (assuming you've added kteam-tools/mainline-build to your PATH):
mainline-build-one fe10e6f4b24ef8ca12cb4d2368deb4861ab1861b precise
This will generate a bunch of .debs one directory level above. One of the debs will be something like:
linux-image-3.2.0-0302rc1gfe10e6f-generic_3.2.0-0302rc1gfe10e6f.201112010256_amd64.deb
This is the deb you will want to test and see if the bug exists or not."

But I cannot find the .deb files anywhere .It cost only several minutes to generate the kernel,so i doubt if there was something wrong.This is the output information.

"prcxjb@prcxjb-F81Se:~/linux-stable$ '/home/prcxjb/kteam-tools/mainline-build/mainline-build-one' 6f063aea557f66eea8c35034a25df85cae5ced33 precise
*** BUILDING: commit:6f063aea557f66eea8c35034a25df85cae5ced33 series:precise abinum: ...
full_version<2.6.34-rc2>
version<2.6.34>
long<v2.6.34-rc2-265-g6f063ae>
abinum<020634rc2>
remote: Counting objects: 41323, done.
remote: Compressing objects: 100% (8820/8820), done.
remote: Total 35921 (delta 28211), reused 34324 (delta 26743)
Receiving objects: 100% (35921/35921), 43.01 MiB | 1.33 MiB/s, done.
Resolving deltas: 100% (28211/28211), completed with 2882 local objects.
From git://kernel.ubuntu.com/ubuntu/ubuntu-precise
 * [new branch] day-0 -> precise/day-0
 * [new branch] lts-backport-quantal -> precise/lts-backport-quantal
 * [new branch] master -> precise/master
 * [new branch] master-next -> precise/master-next
 * [new branch] ti-omap4 -> precise/ti-omap4
 * [new tag] Ubuntu-3.2.0-1421.28 -> Ubuntu-3.2.0-1421.28
 * [new tag] Ubuntu-3.2.0-24.37 -> Ubuntu-3.2.0-24.37
 * [new tag] Ubuntu-3.2.0-33.52 -> Ubuntu-3.2.0-33.52
 * [new tag] Ubuntu-Q-sync -> Ubuntu-Q-sync
 * [new tag] Ubuntu-lts-3.5.0-17.28 -> Ubuntu-lts-3.5.0-17.28
From git://kernel.ubuntu.com/ubuntu/ubuntu-precise
 * [new tag] Ubuntu-3.2.0-22.35 -> Ubuntu-3.2.0-22.35
 * [new tag] Ubuntu-3.2.0-23.36 -> Ubuntu-3.2.0-23.36
 * [new tag] Ubuntu-3.2.0-24.38 -> Ubuntu-3.2.0-24.38
 * [new tag] Ubuntu-3.2.0-24.39 -> Ubuntu-3.2.0-24.39
 * [new tag] Ubuntu-3.2.0-25.40 -> Ubuntu-3.2.0-25.40
 * [new tag] Ubuntu-3.2.0-26.41 -> Ubuntu-3.2.0-26.41
 * [new tag] Ubuntu-3.2.0-27.42 -> Ubuntu-3.2.0-27.42
 * [new tag] Ubuntu-3.2.0-27.43 -> Ubuntu-3.2.0-27.43
 * [new tag] Ubuntu-3.2.0-28.44 -> Ubuntu-3.2.0-28.44
 * [new tag] Ubuntu-3.2.0-29.45 -> Ubuntu-3.2.0-29.45
 * [new tag] Ubuntu-3.2.0-29.46 -> Ubuntu-3.2.0-29.46
 * [new tag] Ubuntu-3.2.0-30.47 -> Ubuntu-3.2.0-30.47
 * [new tag] Ubuntu-3.2.0-30.48 -> Ubuntu-3.2.0-30.48
 * [new tag] Ubuntu-3.2.0-31.49 -> Ubuntu-3.2.0-31.49
 * [new tag] Ubuntu-3.2.0-31.50 -> Ubuntu-3.2.0-31.50
 * [new tag] Ubuntu-3.2.0-32.51 -> Ubuntu-3.2.0-32.51
Checking out files: 100% (31414/31414), done.
Previous H...

[Christopher M. Peñalver (penalvch)]

prcxjb, if you need more granular support on bisecting, please contact the Ubuntu Kernel Team via https://wiki.ubuntu.com/KernelTeam#Communications .

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[Christopher M. Peñalver (penalvch)]

prcxjb, as per http://www.asus.com/Notebooks/Versatile_Performance/F81Se/#download an update is available for your BIOS (218). If you update to this, does this have an impact on using any of the WORKAROUNDs?

[prcxjb (prcxjb)]

My computer's bios has been updated before I submitted the bug.The bug still exists.

[Christopher M. Peñalver (penalvch)]

prcxjb, as per your Bug Description:
dmi.bios.version: 217

your BIOS is not updated to the latest version (218).

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[prcxjb (prcxjb)]

I have updated the bios to the latest version 218 and ubuntu 13.04,but the bug still exists.
It seems that i can't run sudo apport-collect 1066524 in the terminal of ubuntu 13.04.It said "ERROR: The launchpadlib Python module is not installed. This functionality is not available."But the python-apport has been installed.

[Christopher M. Peñalver (penalvch)]

prcxjb, thank you for updating to the newest BIOS and Raring. Could you please test the latest upstream kernel available (v3.9-saucy) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.9

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[prcxjb (prcxjb)]

I have tested the upstream kernel v3.9.1,but the bug still exists.

[Christopher M. Peñalver (penalvch)]

prcxjb, thank you for testing the newest mainline kernel. The next step is to commit bisect the mainline kernel from v2.6.34-rc1 (GOOD) to v2.6.34.1-maverick (BAD) in order to identify the offending commit. Following mainline kernel bisect instructions noted in https://wiki.ubuntu.com/Kernel/KernelBisection you will need to run the following terminal command:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git && cd linux && git bisect start && git bisect good v2.6.34-rc1 && git bisect bad v2.6.34

This will post:
Bisecting: 1899 revisions left to test after this (roughly 11 steps)

[fd218cf9557b9bf7061365a8fe7020a56d3f767c] bridge: Fix IGMP3 report parsing

Next you need to run the following to build the mainline kernel up to this commit:
git checkout fd218cf9557b9bf7061365a8fe7020a56d3f767c && cp /boot/config-`uname -r` .config && yes '' | make oldconfig && make-kpkg clean && CONCURRENCY_LEVEL=`getconf _NPROCESSORS_ONLN` fakeroot make-kpkg --initrd --append-to-version=-custom2 kernel_image kernel_headers && cd .. && sudo dpkg -i *.deb

Restart into this built kernel and please advise on the results. Thank you for your understanding.

[prcxjb (prcxjb)]

I have tried the steps above,but after building the kernel it said "make: *** [debian/stamp/build/kernel] error 2.No .deb exists in the folder.
A message was showed many times when building the kernel "warning： variable ‘pao_tmp__’ is set but never used [-Wunused-but-set-variable] (Translated from Chinese because of Chinese language pack in my ubuntu)

[Christopher M. Peñalver (penalvch)]

prcxjb, thank you for performing the requested terminal command. I beg your pardon as I should have run this command before requesting you to do so, as I would have seen this error. Despite this, I've requested the help of the Ubuntu Kernel Team via their mailing list at https://lists.ubuntu.com/archives/kernel-team/2013-May/028290.html . I'll mark the Status Confirmed until the error has been sorted out.

[Po-Hsu Lin (cypressyew)]

Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!