I just want to know if this list can help me. Not the way it _helped_ me
before.
I can dedicate a few hours each day for kernel-ing (new word? :-) and since
I started weeks ago with Linux I think I'm a little bit closer to the
answer.
Recompiling kernel just seems the wrong way. After some 20 or 25 tries... so
far I can compile with USB support but compiling the controllers as modules.
insmod of any uhci or ohci hangs my laptop and got the message:
Using /lib/modules/2.4.20-8/kernel/drivers/usb/usb-uhci.o
Hint: insmod errors can be caused by incorrect module parameters, including
invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
I get nothing interesting from dmesg.
Well, after lspci -vvx (complete output at request) I get that the PCI
device for USB is 00:07.2 at 0x1800 to 181f, IRQ 5
Check second line of the USB part: (Wrong ID???)
00:07.2 USB Controller: VIA Technologies, Inc. USB (rev 10) (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- <TAbort-
<MAbort- >SERR- <PERR-
Latency: 64, cache line size 08
Interrupt: pin D routed to IRQ 5
Region 4: I/O ports at 1800 [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: 06 11 38 30 17 00 10 02 10 00 03 0c 08 40 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 18 00 00 00 00 00 00 00 00 00 00 25 09 34 12
30: 00 00 00 00 80 00 00 00 00 00 00 00 05 04 00 00
I put reserve=0x1800,20 at the lilo prompt and the system booted farther
than without any parameter till rc.d (using RH9) asked for usb support. It
hung at installing USB support, with cursor blinking. I'm soooo newbie that
I don't know what is the name of this part of booting (second stage?). After
a new reboot I put reserve=0x1800,20 AND nousb as parameters. That booting
went fine to the login screen (full graphical login screen!!!). But had no
mouse and keyboard, and the cursor blinked till I rebooted.
Then, booting well only with nousb as parameter I put
pcitweak -r 00:07:02 -b 0x1800 ... and so on, till 0x180d and got some hex
values 0xXX <> 0x00, but from 0x180f to 0x181f ... got only 0x00, like in
lspci -vvx.
then I hung the machine with ~ as only output putting following line (cursor
blinking):
setpci -s 00:07.2 BASE_ADDRESS_4=1900 (just for probing 1900)
How do I disable USB from the booting scripts, so I can check pcitweak as
before, reserving at LILO 0x1800 and beyond as before, so I can check if
some device was stealing resources? If this behaviour is positive...
Does this all mean that some other device, presumably bus mouse or kbd, are
taking resources from where they are not suppose to do???
How do I know better than in /proc/ioports what-where is eating my few
ports???
In Linux, can I redirect pci situations with setpci for IOports (and IRQ)
for USB-controllers _successfully_?
Can anything be done from compiling usb.c or hub.c again??? I finally
learned how to build Makefiles for specific kernel modules.
Am I totally wrong???
What should I do next???
What I want??? Just to use my poor, old and reliable USB harddrive under
Linux.
I promise you to build a fine web page for installing Linux on any Presario
Laptop, if we find a reliable workaround for my machine.
Thank you
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
