From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1VEQyG-0003wJ-3Q for mharc-grub-devel@gnu.org; Tue, 27 Aug 2013 17:38:40 -0400 Received: from eggs.gnu.org ([2001:4830:134:3::10]:40880) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VEQy7-0003lY-J5 for grub-devel@gnu.org; Tue, 27 Aug 2013 17:38:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VEQy2-0006B9-2j for grub-devel@gnu.org; Tue, 27 Aug 2013 17:38:31 -0400 Received: from mail-ea0-x231.google.com ([2a00:1450:4013:c01::231]:43843) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VEQy1-0006Az-PH for grub-devel@gnu.org; Tue, 27 Aug 2013 17:38:26 -0400 Received: by mail-ea0-f177.google.com with SMTP id f15so2486059eak.8 for ; Tue, 27 Aug 2013 14:38:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=Ya4DS1AJENSo5sU/rSaA+1ZSaLRThd3mNe2ZSncUpnI=; b=KJaxLN6JwUXfOaS4kDy5e+JnmY2DW06bTlG5f+lkS649JM3UF5QMyqD+nLqhMzaBiY OGtcN0eeFSeothJlowiu7x32wUWzGGycv2c31Qw7aTgX+ON89TJSoSgmBgP9VEOMXNBA ruZqBtGsEE/QYBS8HEP19BW7r9p/Qum+rSYpV81E60HBHLNERiYn8+QAKevBv0gkr1aK ggnxjNrKqRv1BdvRkAEphTuY5IBcuHRYWfkfL9JPPPIyT700rVhwSnUX9i8uKG2HgCW7 29JXMStVx3IkgkPAxu6hWt5Gu0v9ozK0J6AEFQ40Z6zM9JjsQYulfSbym7IcqDN//+vf P13Q== X-Received: by 10.15.63.14 with SMTP id l14mr32626454eex.13.1377639504201; Tue, 27 Aug 2013 14:38:24 -0700 (PDT) Received: from [192.168.1.113] (31-249.1-85.cust.bluewin.ch. [85.1.249.31]) by mx.google.com with ESMTPSA id b45sm32127113eef.4.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 27 Aug 2013 14:38:23 -0700 (PDT) Message-ID: <521D1C4E.3060503@gmail.com> Date: Tue, 27 Aug 2013 23:38:22 +0200 From: =?UTF-8?B?VmxhZGltaXIgJ8+GLWNvZGVyL3BoY29kZXInIFNlcmJpbmVua28=?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130630 Icedove/17.0.7 MIME-Version: 1.0 To: The development of GNU GRUB Subject: Re: Missing USB devices. References: <20130807201137.08332daf@opensuse.site> <520534A0.4030009@volny.cz> <52056C1F.5070003@volny.cz> <521D0A45.5000407@volny.cz> In-Reply-To: <521D0A45.5000407@volny.cz> X-Enigmail-Version: 1.5.1 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="----enig2RXURXEUHDPDPHHNRFHIE" X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4013:c01::231 X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: The development of GNU GRUB List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Aug 2013 21:38:37 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) ------enig2RXURXEUHDPDPHHNRFHIE Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 27.08.2013 22:21, Ale=C5=A1 Nesrsta wrote: > On 08/27/13 13:37, Melki Christian (consultant) wrote: >> Hi Ales. >> >> Sorry that I have not replied yet. I've been busy doing other stuff. >> Actually, life seems a little bit brighter with the patch. Not as many= >> lost devices anyway. >> Im running it now and it does not seem to cause any problems anyway, >> so I think it should be comitted? >=20 > I am waiting mainly for Vladimir's "Go on!" :-) I don't see any messages in mymailbox from you tagged as pending patches. Can you tell me the date and subject? > I am not sure if I can commit this patch without his agreement or at > least his comment/code review - even if the patch solves real bug. > But maybe I missed related Vladimir's post in ML. >=20 > BTW, You are probably the first one, who reports any experience with > this patch - thanks. >=20 >=20 >> >> Regarding the latest stuff with nativedisk etc (which I don't like...)= =2E >> It should not matter how I load modues or when I load them. They are >> hook-based and only thing >> that happens is that the refcounter goes up if I load them more than >> one time. >> If GRUB determines that it needs some module early, that's fine with >> me. I don't really care that it loads modules that it think it needs. >=20 > OK, I agree -> But possibly there could be some bug related to > "duplicate/redundant" module loading etc. - that's the main reason why = I > recommended to test another situation. I don't expect such bug - but wh= o > knows... >=20 >=20 >> I have also removed bios-fw-disk disabling from all usb-drivers. >> I think it's just stupid to assume that because you load usb you are >> doing mass storage and thus need nativedisk. >> Im doing perfectly fine without nativedisk and with usb-support enable= d. >> I prefer going all native or just keeping the ata and ahci out of the >> way until you really need them. >> Native disk switching is really slow and so is the disk access in some= >> cases. >> Disabling bios support for disk access and going native is probably >> going to break a couple of cases of exotic hardware too. >=20 > 1. > I didn't such (nativedisk related) changes in USB drivers, it is some > "global" action of other developers... > I was surprised myself little bit with this GRUB behavior change at the= > time when I wanted to debug EHCI module some time ago -> for the first > time I thought it is some GRUB bug... :-) >=20 > To understand: I am really not typical GRUB developer/contributor - I > participate in GRUB development only from time to time and more or less= > I am interested only in things very closed to USB. Additionally, I am > monitoring only ML, not discussion(s) on IRC. -> So, I missed > discussions/patches related to nativedisk philosophy (and many other > things...). -> I have no exact overview how it is done nor why it is > done in this way etc. -> So currently I cannot say anything positive or= > negative about nativedisk and related changes in USB modules -> I > suppose it is probably something more or less experimental, not > final/release state... >=20 > 2. > I think maybe it is not so easy as You may imagine. > I have no detailed information/knowledge but there could happen > something like that: > When You load USB module, You "disconnect" from BIOS any device which i= s > connected to related USB controller - possibly also some mass storage > device(s) or keyboard(s) which were used by GRUB as BIOS disk(s) or BIO= S > keyboard(s) up to this time. > When (later) GRUB calls BIOS routines related to such "disconnected" > device(s), it can crash/freeze (BIOSes are sometimes (often?) buggy...)= =2E > AFAIK, GRUB has no way how to (automatically) prevent such BIOS call of= > "disconnected" device(s) - GRUB probably has no chance to get > information how the BIOS disk/keyboard is connected to PC (to which > controller) etc. > From my point of view, something like that could be one of the reasons > why loading of USB modules requires nativedisk - maybe developers > decided it will be better to avoid such situation even if the nativedis= k > solution can bring another problems... >=20 > 3. > I agree that the nativedisk is unfortunately really slow, and, of > course, possibly it cannot be used on more or less non standard HW. > Additionally, it looks like the native AHCI driver is maybe not working= > well on my PC - GRUB found only two disks from my three connected disks= > in nativedisk mode (as I remember, it found only SATA disks, not PATA > disk - or something like that) - but maybe it is solved now, I didn't > test it again yet. >=20 > BR, > Ales >=20 >> >> Regards, >> C >>> -----Original Message----- >>> From: grub-devel-bounces+christian.melki=3Dsaabgroup.com@gnu.org >>> [mailto:grub-devel-bounces+christian.melki=3Dsaabgroup.com@gnu.org] O= n >>> Behalf Of Ale=C5=A1 Nesrsta >>> Sent: den 10 augusti 2013 00:25 >>> To: The development of GNU GRUB >>> Subject: Re: Missing USB devices. >>> >>> Hi, >>> I forgot one important thing - try to use "nativedisk" command >>> instead of >>> separate loading ehci&uhci modules. >>> BR, >>> Ales >>> >>> Dne 9.8.2013 20:27, Ale=C5=A1 Nesrsta napsal(a): >>>> Hi, >>>> >>>> please send output of >>>> lspci -vvv >>>> lsusb -vvv >>>> Run it as root or via sudo. >>>> >>>> Some general advices: >>>> >>>> 1. >>>> Do not include "insmod usb_keyboard" - this module should be loaded >>>> automatically from usb module. >>>> >>>> 2. >>>> If Your keyboard is connected to USB controller via hub (it can be >>>> internal, integrated in PC), try my patch which I sent in thread >>>> "[PATCH] Re: [grub-devel] loongson-2f mini-pc (fuloong) elf image >>>> generation." (sent at 18.7.2013 18:10 CET). >>>> AFAIK, this patch is not included in trunk yet (I didn't commit it y= et >>>> - and probably nobody else) - it may help (if it is Your case). >>>> >>>> BR, >>>> Ales >>>> >>>> Dne 8.8.2013 09:22, Melki Christian (consultant) napsal(a): >>>>>>> Hi. >>>>>>> >>>>>>> I'm running trunk version 5079 on a rather normal PC. EHCI + UHCI= >>>>>> controller. >>>>>> >>>>>> Did it work in earlier versions? >>>>> >>>>> I made a rather big jump... >>>>> from a backported usb stack on 1.99 to trunk. :( Anyway, I solved >>>>> both my problems. >>>>> I solved them both with letting devices settle before using them. >>>>> Don't know why, and I don't like the solution either (letting devic= es >>>>> settle that is...) The keyboard seems just to take a while to get >>>>> identified properly. >>>>> So I do a sleep interruptible to drive the getkey -> usb_poll and l= et >>>>> the devices get detected. >>>>> >>>>> If I just do: >>>>> >>>>> insmod ehci >>>>> insmod uhci >>>>> insmod usb_keyboard >>>>> >>>>> >>>>> >>>>> things just break... and I get stalls forever from grub when it is >>>>> trying to talk to the keyboard. >>>>> >>>>> If I insert a sleep -i 5 before using it and look at the debug fro= m >>>>> the keyboards I can see that the keyboards get initialized (takes a= >>>>> while) and then it is perfectly fine to use it. >>>>> >>>>> This is ugly, I don't like it and there is atleast one bug or an >>>>> archtectural problem somewhere. >>>>> Btw, normal sleep should do the same as interruptible? >>>>> Just do the same and throw away the getkey result. >>>>> I don't get why they are assymetrical? There is no halt or >>>>> powersaving anyway. >>>>> Normal sleep just stops processing anything since grub is driven fr= om >>>>> the term layer. >>>>> That's just annoying. >>>>> >>>>>> >>>>>>> I load all USB drivers including OHCI. Now with this latest versi= on >>>>>>> GRUB >>>>>> doesn't seem to want to talk to my keyboard anymore. >>>>>>> If I replug the device and reload usb_keyboard then it might work= , >>>>>>> but not >>>>>> right off the bat. >>>>>>> I also have a CCID smartcard reader and it is the same story ther= e. >>>>>>> A normal keyboard plugged while running seems to work just fine >>> though. >>>>>>> All devices are listed with the "usb" command. It looks like it c= an >>>>>>> do control transfers but not real transfers. (lost configuration,= >>>>>>> reset >>>>>>> device?) I >>>>>> noticed that Ales had a similar problem with the fuloong device wi= th >>>>>> OHCI. I don't run OHCI so... >>>>>>> >>>>>>> I am a little bit lost >>>>> >>>>> _______________________________________________ >>>>> Grub-devel mailing list >>>>> Grub-devel@gnu.org >>>>> https://lists.gnu.org/mailman/listinfo/grub-devel >>>>> >>>> >>>> _______________________________________________ >>>> Grub-devel mailing list >>>> Grub-devel@gnu.org >>>> https://lists.gnu.org/mailman/listinfo/grub-devel >>>> >>> >>> _______________________________________________ >>> Grub-devel mailing list >>> Grub-devel@gnu.org >>> https://lists.gnu.org/mailman/listinfo/grub-devel >> >> _______________________________________________ >> Grub-devel mailing list >> Grub-devel@gnu.org >> https://lists.gnu.org/mailman/listinfo/grub-devel >> >=20 > _______________________________________________ > Grub-devel mailing list > Grub-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/grub-devel >=20 ------enig2RXURXEUHDPDPHHNRFHIE Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iF4EAREKAAYFAlIdHE4ACgkQNak7dOguQgkYQAEAkbAqzJJo+/RvIdXi/dGgyl1Q OjJLMYp+qB2Ls9SAiGoA/3IwK02zAyQaiCc7buOVO3PmEpuEXwh3HatcN+p3yoV1 =A7XJ -----END PGP SIGNATURE----- ------enig2RXURXEUHDPDPHHNRFHIE--