Re: 2.6.11 USB broken on VIA computer (not just ACPI)
On Wed, Mar 16, 2005 at 12:50:38PM -0500, Robert W. Fuller wrote: > Greg KH wrote: > >On Wed, Mar 16, 2005 at 01:58:50AM -0500, Robert W. Fuller wrote: > >>>Are you running the latest BIOS? > >>The manufacturer, Tyan, didn't produce more than a handful of BIOS'es > >>within a matter of months after they started producing the board. They > >>haven't released an update since 2000. > >I used to have this motherboard, and Randy Dunlap and I spent a lot of > >time to try to get this to work properly. Just give up and go by a > >motherboard that actually has a sane bios, or, buy a USB pci card (less > >than $20). > > Tempting, but how do I know the new board will work? Shoot, it took me > about a year to get everything in this system to work excepting the USB. > Do you have any recommendations for a good Linux SMP motherboard, > preferably for AMD processors? Get a PCI USB card, that's the easiest solution (and cheapest.) Good luck, greg k-h - 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: 2.6.11 USB broken on VIA computer (not just ACPI)
Greg KH wrote: On Wed, Mar 16, 2005 at 01:58:50AM -0500, Robert W. Fuller wrote: Are you running the latest BIOS? The manufacturer, Tyan, didn't produce more than a handful of BIOS'es within a matter of months after they started producing the board. They haven't released an update since 2000. I used to have this motherboard, and Randy Dunlap and I spent a lot of time to try to get this to work properly. Just give up and go by a motherboard that actually has a sane bios, or, buy a USB pci card (less than $20). Tempting, but how do I know the new board will work? Shoot, it took me about a year to get everything in this system to work excepting the USB. Do you have any recommendations for a good Linux SMP motherboard, preferably for AMD processors? Sorry, Thanks for the insight. Now I won't waste too much more time on this. Regards, Rob - 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: 2.6.11 USB broken on VIA computer (not just ACPI)
On Wed, Mar 16, 2005 at 01:58:50AM -0500, Robert W. Fuller wrote: > >Are you running the latest BIOS? > > The manufacturer, Tyan, didn't produce more than a handful of BIOS'es > within a matter of months after they started producing the board. They > haven't released an update since 2000. I used to have this motherboard, and Randy Dunlap and I spent a lot of time to try to get this to work properly. Just give up and go by a motherboard that actually has a sane bios, or, buy a USB pci card (less than $20). Sorry, greg k-h - 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: 2.6.11 USB broken on VIA computer (not just ACPI)
On Tue, Mar 15, 2005 at 10:19:29PM -0500, Robert W. Fuller wrote: > This isn't limited to the ACPI case. My BIOS is old enough that ACPI is > not supported because the kernel can't find RSDP. I found that the USB > works if I boot with "noapic." This is probably sub-optimal on an SMP > machine. If don't boot with "noapic" I get the following errors: This is a _very_ old bug/issue. The "noapic" boot paramater is the proper fix for such broken hardware. thanks, greg k-h - 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: Documentation/i386/IO-APIC.txt (Re: 2.6.11 USB broken on VIA computer (not just ACPI))
Le mercredi 16 mars 2005 Ã 11:00 +0100, Xavier Bestel a Ãcrit : > Le mardi 15 mars 2005 Ã 21:54 -0800, Andrew Morton a Ãcrit : > > You may be able to set the thing up by hand with the help of > > Documentation/i386/IO-APIC.txt. > > There's something I don't get in this document's ascii-art: > > 8<-- >,-.,-.,-.,-.,-. > PIRQ4 | |-.,-| |-.,-| |-.,-| || | >|S| \ / |S| \ / |S| \ / |S||S| > PIRQ3 |l|-. `/---|l|-. `/---|l|-. `/---|l||l| >|o| \/|o| \/|o| \/|o||o| > PIRQ2 |t|-./`|t|-./`|t|-./`|t||t| >|1| /\ |2| /\ |3| /\ |4||5| > PIRQ1 | |- `| |- `| |- `| || | >`-'`-'`-'`-'`-' > > every PCI card emits a PCI IRQ, which can be INTA,INTB,INTC,INTD: > >,-. > INTD--| | >|S| > INTC--|l| >|o| > INTB--|t| >|x| > INTA--| | >`-' > > These INTA-D PCI IRQs are always 'local to the card', their real meaning > depends on which slot they are in. If you look at the daisy chaining diagram, > a card in slot4, issuing INTA IRQ, it will end up as a signal on PIRQ2 of > the PCI chipset. [...] > 8<-- > > If I follow the wire from Slot4's INTA, I'm ending on PIRQ4 whereas the > doc says IRQ2. Do I need glasses, or a new fixed-font ? Sorry for replying to myself, in fact it seems like somebody reversed the order of PIRQ[1-4] and INT[A-D] in the ascii-art, but didn't touch the rest of the text at all. There are several more references to a "reversed order". Xav - 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/
Documentation/i386/IO-APIC.txt (Re: 2.6.11 USB broken on VIA computer (not just ACPI))
Le mardi 15 mars 2005 Ã 21:54 -0800, Andrew Morton a Ãcrit : > You may be able to set the thing up by hand with the help of > Documentation/i386/IO-APIC.txt. There's something I don't get in this document's ascii-art: 8<-- ,-.,-.,-.,-.,-. PIRQ4 | |-.,-| |-.,-| |-.,-| || | |S| \ / |S| \ / |S| \ / |S||S| PIRQ3 |l|-. `/---|l|-. `/---|l|-. `/---|l||l| |o| \/|o| \/|o| \/|o||o| PIRQ2 |t|-./`|t|-./`|t|-./`|t||t| |1| /\ |2| /\ |3| /\ |4||5| PIRQ1 | |- `| |- `| |- `| || | `-'`-'`-'`-'`-' every PCI card emits a PCI IRQ, which can be INTA,INTB,INTC,INTD: ,-. INTD--| | |S| INTC--|l| |o| INTB--|t| |x| INTA--| | `-' These INTA-D PCI IRQs are always 'local to the card', their real meaning depends on which slot they are in. If you look at the daisy chaining diagram, a card in slot4, issuing INTA IRQ, it will end up as a signal on PIRQ2 of the PCI chipset. [...] 8<-- If I follow the wire from Slot4's INTA, I'm ending on PIRQ4 whereas the doc says IRQ2. Do I need glasses, or a new fixed-font ? Xav - 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: 2.6.11 USB broken on VIA computer (not just ACPI)
Andrew Morton wrote: "Robert W. Fuller" <[EMAIL PROTECTED]> wrote: Nobody's going to fix that machine while you persist in top-posting ;) OK OK. No more top posting. It's Mozilla's fault you know It steers you in the wrong direction by leaving a few lines at the top. Yes I'm ashamed to admit I remember when the default behavior of mail clients was to put the cursor at the bottom. How old is it, anyway? Hmm. I think I built it in 2000. Wow, time flies when you're having fun! Of course, I don't know how well video capture is going to work without the apic programming. So I guess I'm reduced to rebooting when I want to switch between USB peripherals and video capture? > hm, you didn't mention video capture before. It should work OK? I've only ever used it with the APIC enabled. We'll see what happens without? Are you running the latest BIOS? The manufacturer, Tyan, didn't produce more than a handful of BIOS'es within a matter of months after they started producing the board. They haven't released an update since 2000. You may be able to set the thing up by hand with the help of Documentation/i386/IO-APIC.txt. I'll check it out. Thanks! - 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: 2.6.11 USB broken on VIA computer (not just ACPI)
"Robert W. Fuller" <[EMAIL PROTECTED]> wrote: > > I suppose you have to have your priorities. It may be old to you, but > it's current to me! That used to be the hallmark of Linux, the fact > that it would run on lesser hardware. Nobody's going to fix that machine while you persist in top-posting ;) How old is it, anyway? > Of course, I don't know how well video capture is going to work without > the apic programming. So I guess I'm reduced to rebooting when I want > to switch between USB peripherals and video capture? hm, you didn't mention video capture before. It should work OK? Are you running the latest BIOS? You may be able to set the thing up by hand with the help of Documentation/i386/IO-APIC.txt. - 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: 2.6.11 USB broken on VIA computer (not just ACPI)
I suppose you have to have your priorities. It may be old to you, but it's current to me! That used to be the hallmark of Linux, the fact that it would run on lesser hardware. Of course, I don't know how well video capture is going to work without the apic programming. So I guess I'm reduced to rebooting when I want to switch between USB peripherals and video capture? Maybe I should have lied and said it worked :-) Andrew Morton wrote: "Robert W. Fuller" <[EMAIL PROTECTED]> wrote: I never actually saw it work until I added the noapic option to the 2.6.11.2 boot. Now I can usually my USB mouse! Of course the downside to specifying noapic is only one CPU is servicing interrupts on my SMP system. Oh, OK. I was just wondering whether this was an actual regression. I guess as it's an old machine and you have a workaround, we have other things to be working on. It would be nice to fix though. It certainly doesn't work under 2.4.28, but I haven't tried specifying noapic to that kernel. Would that be useful information? Probably not. - 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: 2.6.11 USB broken on VIA computer (not just ACPI)
I never actually saw it work until I added the noapic option to the 2.6.11.2 boot. Now I can usually my USB mouse! Of course the downside to specifying noapic is only one CPU is servicing interrupts on my SMP system. It certainly doesn't work under 2.4.28, but I haven't tried specifying noapic to that kernel. Would that be useful information? Andrew Morton wrote: "Robert W. Fuller" <[EMAIL PROTECTED]> wrote: This isn't limited to the ACPI case. My BIOS is old enough that ACPI is not supported because the kernel can't find RSDP. I found that the USB works if I boot with "noapic." This is probably sub-optimal on an SMP machine. If don't boot with "noapic" I get the following errors: Did it work OK under previous kernels? If so, which versions? - 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: 2.6.11 USB broken on VIA computer (not just ACPI)
"Robert W. Fuller" <[EMAIL PROTECTED]> wrote: > > I never actually saw it work until I added the noapic option to the > 2.6.11.2 boot. Now I can usually my USB mouse! Of course the downside > to specifying noapic is only one CPU is servicing interrupts on my SMP > system. Oh, OK. I was just wondering whether this was an actual regression. I guess as it's an old machine and you have a workaround, we have other things to be working on. It would be nice to fix though. > It certainly doesn't work under 2.4.28, but I haven't tried specifying > noapic to that kernel. Would that be useful information? Probably not. - 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: 2.6.11 USB broken on VIA computer (not just ACPI)
"Robert W. Fuller" <[EMAIL PROTECTED]> wrote: > > This isn't limited to the ACPI case. My BIOS is old enough that ACPI is > not supported because the kernel can't find RSDP. I found that the USB > works if I boot with "noapic." This is probably sub-optimal on an SMP > machine. If don't boot with "noapic" I get the following errors: Did it work OK under previous kernels? If so, which versions? - 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/
2.6.11 USB broken on VIA computer (not just ACPI)
This isn't limited to the ACPI case. My BIOS is old enough that ACPI is not supported because the kernel can't find RSDP. I found that the USB works if I boot with "noapic." This is probably sub-optimal on an SMP machine. If don't boot with "noapic" I get the following errors: Mar 15 21:30:17 falcon USB Universal Host Controller Interface driver v2.2 Mar 15 21:30:17 falcon uhci_hcd :00:07.2: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller Mar 15 21:30:17 falcon uhci_hcd :00:07.2: irq 19, io base 0xa400 Mar 15 21:30:17 falcon uhci_hcd :00:07.2: new USB bus registered, assigned bus number 1 Mar 15 21:30:17 falcon hub 1-0:1.0: USB hub found Mar 15 21:30:17 falcon hub 1-0:1.0: 2 ports detected Mar 15 21:30:17 falcon usb 1-2: new low speed USB device using uhci_hcd and address 2 Mar 15 21:30:18 falcon uhci_hcd :00:07.2: Unlink after no-IRQ? Controller is probably using the wrong IRQ. Mar 15 21:30:18 falcon usb 1-2: khubd timed out on ep0in Mar 15 21:30:24 falcon usb 1-2: khubd timed out on ep0out Mar 15 21:30:29 falcon usb 1-2: khubd timed out on ep0out Mar 15 21:30:29 falcon usb 1-2: device not accepting address 2, error -110 Here's my lspci: :00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev c4) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Latency: 0 Region 0: Memory at d000 (32-bit, prefetchable) Capabilities: [a0] 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=x2 Capabilities: [c0] 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:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Latency: 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 9000-9fff Memory behind bridge: e000-e1ff Prefetchable memory behind bridge: d800-dfff Expansion ROM at 9000 [disabled] [size=4K] BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B- Capabilities: [80] 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:07.0 ISA bridge: VIA Technologies, Inc. VT82C596 ISA [Mobile South] (rev 23) Subsystem: VIA Technologies, Inc. VT82C596/A/B PCI to ISA Bridge Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Latency: 0 :00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 10) (prog-if 8a [Master SecP PriP]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Latency: 32 Region 4: I/O ports at a000 [size=16] Capabilities: [c0] 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:07.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 11) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Latency: 32, cache line size 08 Interrupt: pin D routed to IRQ 11 Region 4: I/O ports at a400 [size=32] Capabilities: [80] 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:07.3 Host bridge: VIA Technologies, Inc. VT82C596 Power Management (rev 30) Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- :00:0f.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- SERR- Latency: 32 (1000ns min, 4500ns max), cache line size 08 Interrupt: pin A routed to IRQ 11 Region 0: I/O ports at a800 Region 1: I/O ports at ac00 [size=4] Region 2: I/O ports at b000 [size=8] Region 3: I/O ports at b400 [size=4] Region 4: I/O ports at b80
