SMbus not enabled
Hello, my notebook have a SiS 964 Chipset and "quirked" by "quirk_sis_503", ... but there is no SMbus device. If I add a call to the "quirk_sis_96x_smbus" function directly from the "quirk_sis_503" function, the smbus is present, but I think a call to a quirk from a quirk is not optimal. Is there a better solution? EnricoB __ Mit WEB.DE FreePhone mit hoechster Qualitaet ab 0 Ct./Min. weltweit telefonieren! http://freephone.web.de/?mc=021201 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
SMbus not enabled
Hello, my notebook have a SiS 964 Chipset and quirked by quirk_sis_503, ... but there is no SMbus device. If I add a call to the quirk_sis_96x_smbus function directly from the quirk_sis_503 function, the smbus is present, but I think a call to a quirk from a quirk is not optimal. Is there a better solution? EnricoB __ Mit WEB.DE FreePhone mit hoechster Qualitaet ab 0 Ct./Min. weltweit telefonieren! http://freephone.web.de/?mc=021201 - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.6.11-rc4
Hello, It is possible to include the SIS5595 chip driver to the final release? EnricoB - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.6.11-rc4
Hello, It is possible to include the SIS5595 chip driver to the final release? EnricoB - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BIOS Bug
Aleksey Gorelov schrieb: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Enrico Bartky Sent: Monday, February 07, 2005 7:12 AM To: linux-kernel@vger.kernel.org Subject: BIOS Bug Hello, on my notebook, when I plugged in my USB keyboard the kernel doesnt boot correctly, ... ... BIOS hangoff failed ( 112, 1010001 ) continuing after BIOS bug irq 192, pci mem 0xfebff000 new usb device registered, assigned bus number 1 ... then the notebook hangs. If I boot without the plugged keyboard and plug in when the kernel is ready, there are no problems. I have a SiS USB chipset. Can you help me? What kernel version are you using ? Try 2.6.10 with the following command line parameter: usb-handoff Aleks. Thanx, it works! Can you say me, it is really a BIOS Bug, a buggy ACPI or a driver problem? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BIOS Bug
Aleksey Gorelov schrieb: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Enrico Bartky Sent: Monday, February 07, 2005 7:12 AM To: linux-kernel@vger.kernel.org Subject: BIOS Bug Hello, on my notebook, when I plugged in my USB keyboard the kernel doesnt boot correctly, ... ... BIOS hangoff failed ( 112, 1010001 ) continuing after BIOS bug irq 192, pci mem 0xfebff000 new usb device registered, assigned bus number 1 ... then the notebook hangs. If I boot without the plugged keyboard and plug in when the kernel is ready, there are no problems. I have a SiS USB chipset. Can you help me? What kernel version are you using ? Try 2.6.10 with the following command line parameter: usb-handoff Aleks. Thanx, it works! Can you say me, it is really a BIOS Bug, a buggy ACPI or a driver problem? - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
BIOS Bug
Hello, on my notebook, when I plugged in my USB keyboard the kernel doesnt boot correctly, ... ... BIOS hangoff failed ( 112, 1010001 ) continuing after BIOS bug irq 192, pci mem 0xfebff000 new usb device registered, assigned bus number 1 ... then the notebook hangs. If I boot without the plugged keyboard and plug in when the kernel is ready, there are no problems. I have a SiS USB chipset. Can you help me? Thanx, EnricoB __ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
BIOS Bug
Hello, on my notebook, when I plugged in my USB keyboard the kernel doesnt boot correctly, ... ... BIOS hangoff failed ( 112, 1010001 ) continuing after BIOS bug irq 192, pci mem 0xfebff000 new usb device registered, assigned bus number 1 ... then the notebook hangs. If I boot without the plugged keyboard and plug in when the kernel is ready, there are no problems. I have a SiS USB chipset. Can you help me? Thanx, EnricoB __ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193 - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
PATCH for 2.6: Enabling disabled M7101 device (quirks.c)
Hello, I have ported the prog/hotplug/m7101.c module from lm_sensors for kernel 2.6. Here is the patch. EnricoB __ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193 i2c.diff Description: Binary data
PATCH for 2.6: Enabling disabled M7101 device (quirks.c)
Hello, I have ported the prog/hotplug/m7101.c module from lm_sensors for kernel 2.6. Here is the patch. EnricoB __ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193 i2c.diff Description: Binary data
Re: lspci != scanpci !?
Here are the outputs. Without H1 there is no 7101 device; with H1 there is a 7101 device. Enrico - Original Message - From: "Martin Mares" <[EMAIL PROTECTED]> To: "Enrico Bartky" <[EMAIL PROTECTED]> Cc: Sent: Saturday, January 15, 2005 1:35 PM Subject: Re: lspci != scanpci !? > Hello! > > > Now the scanpci command shows the M7101 BUT lspci and /proc/pci, > > /proc/bus/pci, /sys/bus/pci NOT. What can I do? Is there anything like a > > "update_pci" command? > > What does `lspci -vv -M' and `lspci -vv -M -H1' print? > > (Please Cc to me, I usually read LKML in large batches.) > > Have a nice fortnight > -- > Martin `MJ' Mares <[EMAIL PROTECTED]> http://atrey.karlin.mff.cuni.cz/~mj/ > Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth > Air conditioned environment -- Do not open Windows. WARNING: Bus mapping can be reliable only with direct hardware access enabled. 00:00.0 Host bridge: ALi Corporation M1541 (rev 04) Subsystem: ALi Corporation ALI M1541 Aladdin V/V+ AGP System Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- SERR- 00:01.0 PCI bridge: ALi Corporation M1541 PCI to AGP Controller (rev 04) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- SERR- Reset- FastB2B- ## 00.01:0 is a bridge from 00 to 01-01 00:02.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03) (prog-if 10 [OHCI]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Summary of buses: 00: Primary host bus 01.0 Bridge to 01-01 01: Entered via 00:01.0 00:00.0 Host bridge: ALi Corporation M1541 (rev 04) Subsystem: ALi Corporation ALI M1541 Aladdin V/V+ AGP System Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- SERR- 00:01.0 PCI bridge: ALi Corporation M1541 PCI to AGP Controller (rev 04) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- SERR- Reset- FastB2B- ## 00.01:0 is a bridge from 00 to 01-01 00:02.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03) (prog-if 10 [OHCI]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Summary of buses: 00: Primary host bus 01.0 Bridge to 01-01 01: Entered via 00:01.0
Re: lspci != scanpci !?
Here are the outputs. Without H1 there is no 7101 device; with H1 there is a 7101 device. Enrico - Original Message - From: Martin Mares [EMAIL PROTECTED] To: Enrico Bartky [EMAIL PROTECTED] Cc: linux-kernel@vger.kernel.org Sent: Saturday, January 15, 2005 1:35 PM Subject: Re: lspci != scanpci !? Hello! Now the scanpci command shows the M7101 BUT lspci and /proc/pci, /proc/bus/pci, /sys/bus/pci NOT. What can I do? Is there anything like a update_pci command? What does `lspci -vv -M' and `lspci -vv -M -H1' print? (Please Cc to me, I usually read LKML in large batches.) Have a nice fortnight -- Martin `MJ' Mares [EMAIL PROTECTED] http://atrey.karlin.mff.cuni.cz/~mj/ Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth Air conditioned environment -- Do not open Windows. WARNING: Bus mapping can be reliable only with direct hardware access enabled. 00:00.0 Host bridge: ALi Corporation M1541 (rev 04) Subsystem: ALi Corporation ALI M1541 Aladdin V/V+ AGP System Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=slow TAbort- TAbort- MAbort+ SERR- PERR- Latency: 64 Region 0: Memory at e000 (32-bit, non-prefetchable) Capabilities: [b0] AGP version 1.0 Status: RQ=28 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2 Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=none 00:01.0 PCI bridge: ALi Corporation M1541 PCI to AGP Controller (rev 04) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=slow TAbort- TAbort- MAbort- SERR- PERR- Latency: 64 Bus: primary=00, secondary=01, subordinate=01, sec-latency=64 I/O behind bridge: c000-cfff Memory behind bridge: cde0-cfef Prefetchable memory behind bridge: bdc0-cdcf BridgeCtl: Parity+ SERR- NoISA- VGA+ MAbort- Reset- FastB2B- ## 00.01:0 is a bridge from 00 to 01-01 00:02.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03) (prog-if 10 [OHCI]) 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 (2ns max), cache line size 08 Interrupt: pin A routed to IRQ 0 Region 0: Memory at d000 (32-bit, non-prefetchable) 00:07.0 ISA bridge: ALi Corporation M1533 PCI to ISA Bridge [Aladdin IV] (rev c3) Subsystem: ALi Corporation ALI M1533 Aladdin IV ISA Bridge 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: 0 00:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) Subsystem: D-Link System Inc DRN-32TX 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 (8000ns min, 16000ns max) Interrupt: pin A routed to IRQ 11 Region 0: I/O ports at dc00 Region 1: Memory at dfffef00 (32-bit, non-prefetchable) Capabilities: [50] 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- 00:09.0 Unknown mass storage controller: Promise Technology, Inc. 20269 (rev 02) (prog-if 85) Subsystem: Promise Technology, Inc. Ultra133TX2 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=slow TAbort- TAbort- MAbort- SERR- PERR- Latency: 64 (1000ns min, 4500ns max), cache line size 08 Interrupt: pin A routed to IRQ 10 Region 0: I/O ports at dff0 Region 1: I/O ports at dfe4 Region 2: I/O ports at dfa8 Region 3: I/O ports at dfe0 Region 4: I/O ports at df90 Region 5: Memory at dfff8000 (32-bit, non-prefetchable) Expansion ROM at dffe Capabilities: [60] Power Management version 1 Flags: PMEClk- DSI+ D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX 400] (rev a1) (prog-if 00 [VGA]) Subsystem: ASUSTeK Computer Inc.: Unknown device 4019 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR
