Date: Sat, 25 Jan 2014 23:16:46 +0000 From: "Mike C." <miguelmclara@gmail.com> To: =?ISO-8859-1?Q?Jean-S=E9bastien_P=E9dron?= <dumbbell@FreeBSD.org>, freebsd-current@freebsd.org Subject: Re: Newcons radeonkms - Failed to load firmware "radeonkmsfw_TURKS_PFP" Message-ID: <1ab937f2-aca2-41d0-a1a7-a7eb232b9c83@email.android.com> In-Reply-To: <52E435A3.6010900@FreeBSD.org> References: <1367fd4d-9128-4df0-a250-fb3c1f67f0c5@email.android.com> <52E42A3A.7000901@FreeBSD.org> <712a6e8d-e34b-4321-8c23-aa9edfe6147f@email.android.com> <52E435A3.6010900@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Sure, Btw, I wonder if there's a way to ignore loader.conf at boot? Otherwise I can boot from an install image, just courious tough, would be nice if there a way to do it. I will post the output on the other mailing list "Jean-Sébastien Pédron" <dumbbell@FreeBSD.org> wrote: >On 25.01.2014 22:45, Mike C. wrote: >> Worked but I'm still stuck in this case at 'vt_allocate: Replace >existing VT driver.' >> >> a few lines up I see: >> No connectors reported connected with modes. > >Could you please boot without loading the Radeon driver from >loader.conf, and run "kldload radeonkms", then post a full dmesg? > >> should I post to freebsd-x11@FreeBSD.org? > >Yes, this will be more on topic. > >-- >Jean-Sébastien Pédron -- Sent from my Android device with K-9 Mail. Please excuse my brevity. From owner-freebsd-current@FreeBSD.ORG Sat Jan 25 23:57:58 2014 Return-Path: <owner-freebsd-current@FreeBSD.ORG> Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CA496DAC; Sat, 25 Jan 2014 23:57:58 +0000 (UTC) Received: from mail-gw13.york.ac.uk (mail-gw13.york.ac.uk [144.32.129.163]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7FD64136A; Sat, 25 Jan 2014 23:57:58 +0000 (UTC) Received: from ury.york.ac.uk ([144.32.64.162]:40059) by mail-gw13.york.ac.uk with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from <gavin@FreeBSD.org>) id 1W7D1H-0007yk-AY; Sat, 25 Jan 2014 23:52:11 +0000 Date: Sat, 25 Jan 2014 23:52:11 +0000 (GMT) From: Gavin Atkinson <gavin@FreeBSD.org> X-X-Sender: gavin@ury.york.ac.uk To: "Lundberg, Johannes" <johannes@brilliantservice.co.jp> Subject: Re: Install 10.0-RC3 on MacBookPro Late 2013 In-Reply-To: <CAASDrV=k1QmQ5cui+S5QjtmQztwy11eSZhGNWfPS0wSn9kcW0w@mail.gmail.com> Message-ID: <alpine.BSF.2.00.1401252349100.33534@ury.york.ac.uk> References: <CAB8uncZO19Aen+uQRgO3whSOTVM+ftcsGrJuGZZd4Qbd1Zf5mw@mail.gmail.com> <CAB8unca6XZSEa8=c21yDJ=ueuUiW=D4v2PcLEzgt_sfTgsuzqA@mail.gmail.com> <CAB8unca8G32qcz67EaRdqrSBuO0YiBV4zL7fV3EfMozdeSsBQA@mail.gmail.com> <52CA56E5.8030101@bitfrost.no> <CAJ-Vmo=AxbQ9MMtkB_W3YW0s9QwmR8qWzgprOM_66MQqcgmdNQ@mail.gmail.com> <CAB8uncbjhzG-9BYbYH6skhnf-O24hDeX644aEpz162C-FHWTFA@mail.gmail.com> <52CA6E3F.9000301@bitfrost.no> <CAB8uncah+COOptDmOiaKseqfDyeVd3veg2RLREOzfYtaJhfLYA@mail.gmail.com> <52CA7CE0.7070202@bitfrost.no> <CAJ-Vmok16O0hR9G9rhVeO6Ki3yn4DZgjj4s65ddhQS5MZXVeXw@mail.gmail.com> <52CACBB8.1020905@bitfrost.no> <52CB2591.9050401@bitfrost.no> <CAB8uncYnbto=vavyWEWjwPtYqn4Uthb-V6YHXeqd3G01=f8UbQ@mail.gmail.com> <CAASDrVmMuX4OrEAyL6SQ_vcC6nKz0uOmbr1vJp4gcwGj1tCMog@mail.gmail.com> <CAB8uncbAMhaC3GkAqqny6Rpe0C-+Z5=dxdrL=OYfbau4T9P-jg@mail.gmail.com> <CAASDrV=k1QmQ5cui+S5QjtmQztwy11eSZhGNWfPS0wSn9kcW0w@mail.gmail.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-2022-jp X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: Hans Petter Selasky <hps@bitfrost.no>, =?GB2312?B?u8bOxLvU?= <huanghwh@gmail.com>, Adrian Chadd <adrian@freebsd.org>, freebsd-current <freebsd-current@freebsd.org> X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the use of FreeBSD-current <freebsd-current.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/> List-Post: <mailto:freebsd-current@freebsd.org> List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 25 Jan 2014 23:57:59 -0000 On Tue, 7 Jan 2014, Lundberg, Johannes wrote: > I have also experienced random hangs. However, I'm not sure if they are > really hangs or just the USB driver stopped working. Since mouse pad, > keyboard everything is run through USB I couldn't tell really what happened. It seems that the frequency of these hangs depends on the speed of the CPU. With "powerd -a max -b max" the machine can last hours without hanging, with the CPU throttled down the machine can hang within seconds. The MBA at least defaults to a CPU speed midway between minimum and maximum. > Did you have any problems with the identifier of the ssd? When I first > tried FreeBSD on MBA2013 it couldn't identify the ssd because there was > some weird characters in the ssd's identifier. Gavin helped me create a > patch that solved the problem temporary (by hard coding a different ident) > but I'm not sure if a permanent fix has been merged. Yes, mav@ committed the real fix for this in r258683. Thanks, Gavin > -- > Johannes Lundberg > BRILLIANTSERVICE CO., LTD. > > > On Tue, Jan 7, 2014 at 12:05 PM, Huang Wen Hui <huanghwh@gmail.com> wrote: > > > USB problem fixed by revert to r245731, > > set "hint.ahci.0.msi=0" seem to fixed timeout problem of AHCI. > > > > Random hang I think still exist, will check later... > > > > Cheers, > > Huang Wen Hui > > > > > > 2014/1/7 Lundberg, Johannes <johannes@brilliantservice.co.jp> > > > >> Hi Huang > >> > >> Good job!! By "works", which parts do you mean has been fixed? > >> > >> 1. USB problem > >> or > >> 2. AHCI timeout problem > >> or > >> 3. Random hang > >> > >> Best regards! > >> > >> -- > >> Johannes Lundberg > >> BRILLIANTSERVICE CO., LTD. > >> > >> > >> On Tue, Jan 7, 2014 at 11:30 AM, Huang Wen Hui <huanghwh@gmail.com>wrote: > >> > >>> Hans, > >>> > >>> This wild guess do NOT works. > >>> I binary sect xhci.c in SVN, found that *r245732 > >>> *<http://svnweb.freebsd.org/base?view=revision&revision=245732>* > >>> introduce the bug.* > >>> <http://svnweb.freebsd.org/base?view=revision&revision=245732> > >>> > >>> revert to r345731 fixed this USB problem in 9.2R > >>> > >>> I also copy xhci_interrupt(struct xhci_softc *sc) from 9.1R to CURRENT, > >>> CURRENT also works! > >>> > >>> Cheers, > >>> Huang Wen Hui. > >>> > >>> > >>> 2014/1/7 Hans Petter Selasky <hps@bitfrost.no> > >>> > >>> > On 01/06/14 16:28, Hans Petter Selasky wrote: > >>> > > >>> >> On 01/06/14 15:17, Adrian Chadd wrote: > >>> >> > >>> >>> Right, but it used to work. That's the confusing bit. How'd you make > >>> >>> it not work? :) > >>> >>> > >>> >> > >>> >> Binary sect the sys/dev/usb/controller/xhci.c revision history? There > >>> >> has been several bug reports for the Lynx point, and others XHCI > >>> >> chipsets are working just fine. > >>> >> > >>> >> > >>> > A wild guess: > >>> > > >>> > Copy the USB-code from -current. > >>> > > >>> > Add "#if 0" as shown sys/dev/usb/controller/xhci_pci.c > >>> > > >>> > static int > >>> > xhci_pci_port_route(device_t self, uint32_t set, uint32_t clear) > >>> > { > >>> > #if 0 > >>> > uint32_t temp; > >>> > > >>> > temp = pci_read_config(self, PCI_XHCI_INTEL_USB3_PSSEN, 4) | > >>> > pci_read_config(self, PCI_XHCI_INTEL_XUSB2PR, 4); > >>> > > >>> > temp |= set; > >>> > temp &= ~clear; > >>> > > >>> > pci_write_config(self, PCI_XHCI_INTEL_USB3_PSSEN, temp, 4); > >>> > pci_write_config(self, PCI_XHCI_INTEL_XUSB2PR, temp, 4); > >>> > > >>> > device_printf(self, "Port routing mask set to 0x%08x\n", temp); > >>> > #endif > >>> > return (0); > >>> > } > >>> > > >>> > --HPS > >>> > > >>> _______________________________________________ > >>> freebsd-current@freebsd.org mailing list > >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current > >>> To unsubscribe, send any mail to " > >>> freebsd-current-unsubscribe@freebsd.org" > >>> > >> > >> > >> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > >> $BHkL)J];}$K$D$$$F!'$3$NEE;R%a!<%k$O!"L>08?M$KAw?.$7$?$b$N$G$"$j!"HkF?FC8"$NBP>]$H$J$k>pJs$r4^$s$G$$$^$9!#(J > >> $B$b$7!"L>08?M0J30$NJ}$,<u?.$5$l$?>l9g!"$3$N%a!<%k$NGK4~!"$*$h$S$3$N%a!<%k$K4X$9$k0l@Z$N3+<(!"(J > >> $BJ#<L!"G[I[!"$=$NB>$NMxMQ!"$^$?$O5-:\FbMF$K4p$E$/$$$+$J$k9TF0$b$5$l$J$$$h$&$*4j$$?=$7>e$2$^$9!#(J > >> --- > >> CONFIDENTIALITY NOTE: The information in this email is confidential > >> and intended solely for the addressee. > >> Disclosure, copying, distribution or any other action of use of this > >> email by person other than intended recipient, is prohibited. > >> If you are not the intended recipient and have received this email in > >> error, please destroy the original message. > >> > > > > > > -- > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > $BHkL)J];}$K$D$$$F!'$3$NEE;R%a!<%k$O!"L>08?M$KAw?.$7$?$b$N$G$"$j!"HkF?FC8"$NBP>]$H$J$k>pJs$r4^$s$G$$$^$9!#(J > $B$b$7!"L>08?M0J30$NJ}$,<u?.$5$l$?>l9g!"$3$N%a!<%k$NGK4~!"$*$h$S$3$N%a!<%k$K4X$9$k0l@Z$N3+<(!"(J > $BJ#<L!"G[I[!"$=$NB>$NMxMQ!"$^$?$O5-:\FbMF$K4p$E$/$$$+$J$k9TF0$b$5$l$J$$$h$&$*4j$$?=$7>e$2$^$9!#(J > --- > CONFIDENTIALITY NOTE: The information in this email is confidential > and intended solely for the addressee. > Disclosure, copying, distribution or any other action of use of this > email by person other than intended recipient, is prohibited. > If you are not the intended recipient and have received this email in > error, please destroy the original message. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1ab937f2-aca2-41d0-a1a7-a7eb232b9c83>