Re: WiFi 802.11/ac PCIe supported adaptor
Am Sun, 28 Sep 2014 00:22:09 +0200 Lars Engels lars.eng...@0x20.net schrieb: On Sat, Sep 27, 2014 at 02:38:30PM +0200, O. Hartmann wrote: I'm looking for a replacemnt for my 802.11g WiFi PCIe adaptor card and want to replace it with an 802.11ac adaptor. Since I made very bad experiences with CURRENT and support of modest modern hardware (Haswell CPU/Intel 7260 DualBand WiFi NIC), I'd like to ask here first. I found this PCIe adaptor card attractive: GigaByte Gigabyte GC-WB867D-I I can not find ad hoc the WLAN chip used on that specific card, but maybe someone has experiences with that litte board. FreeBSD doensn't support 802.11ac, yet. I'm bitter aware of that. This OS doesn't support the chipsets, even if they provide also 11a/g/n. We have at our department now a bunch of Lenovo hardware, with Intels 7260 chipset. The laptops are now runninmg Ubuntu 14.0X something which obviously supports the WiFi chip. I'm the last man standing with FreeBSD on my private Lenovo :-( signature.asc Description: PGP signature
Re: WiFi 802.11/ac PCIe supported adaptor
On 09/27/14 23:06, O. Hartmann wrote: Am Sun, 28 Sep 2014 00:22:09 +0200 Lars Engels lars.eng...@0x20.net schrieb: On Sat, Sep 27, 2014 at 02:38:30PM +0200, O. Hartmann wrote: I'm looking for a replacemnt for my 802.11g WiFi PCIe adaptor card and want to replace it with an 802.11ac adaptor. Since I made very bad experiences with CURRENT and support of modest modern hardware (Haswell CPU/Intel 7260 DualBand WiFi NIC), I'd like to ask here first. I found this PCIe adaptor card attractive: GigaByte Gigabyte GC-WB867D-I I can not find ad hoc the WLAN chip used on that specific card, but maybe someone has experiences with that litte board. FreeBSD doensn't support 802.11ac, yet. I'm bitter aware of that. This OS doesn't support the chipsets, even if they provide also 11a/g/n. We have at our department now a bunch of Lenovo hardware, with Intels 7260 chipset. The laptops are now runninmg Ubuntu 14.0X something which obviously supports the WiFi chip. I'm the last man standing with FreeBSD on my private Lenovo :-( This is a serious problem. I'm about ready to install Linux on my laptop as well just to get a usable system. Some kind of funding directed to a willing developer would be hugely valuable for the usability of the operating system on recent hardware. This is probably more important even than Haswell graphics since without a driver, Haswell is merely slow, whereas networking is completely broken. -Nathan ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: SOEKRIS kernel config
On Sat, Sep 27, 2014 at 9:47 PM, Tom Everett t...@khubla.com wrote: I see there is no SOEKRIS config on the tree, here https://svnweb.freebsd.org/base/head/sys/i386/conf/ I have attached one for addition to the tree. Since you only appended a few configuration options to the end of the GENERIC configuration, it would be better to use the include directive in the SOEKRIS config file. This allows changes to be made to the GENERIC configuration, and the SOEKRIS kernel would automatically get those changes. Here's a shorter version of that configuration file: # # SOEKRIS -- Generic Kernel configuration file for FreeBSD/i386 on SOEKRIS # # $FREEBSD include GENERIC ident SOEKRIS # To Make a SOEKRIS Kernel, the next options are needed options CPU_SOEKRIS options CPU_ELAN #options CPU_ELAN_PPS #options CPU_ELAN_XTAL=32768000 options CPU_GEODE # Include TMPFS options TMPFS -- DISCLAIMER: No electrons were maimed while sending this message. Only slightly bruised. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: WiFi 802.11/ac PCIe supported adaptor
On Sat, Sep 27, 2014 at 11:20 PM, Nathan Whitehorn nwhiteh...@freebsd.org wrote: On 09/27/14 23:06, O. Hartmann wrote: Am Sun, 28 Sep 2014 00:22:09 +0200 Lars Engels lars.eng...@0x20.net schrieb: On Sat, Sep 27, 2014 at 02:38:30PM +0200, O. Hartmann wrote: I'm looking for a replacemnt for my 802.11g WiFi PCIe adaptor card and want to replace it with an 802.11ac adaptor. Since I made very bad experiences with CURRENT and support of modest modern hardware (Haswell CPU/Intel 7260 DualBand WiFi NIC), I'd like to ask here first. I found this PCIe adaptor card attractive: GigaByte Gigabyte GC-WB867D-I I can not find ad hoc the WLAN chip used on that specific card, but maybe someone has experiences with that litte board. FreeBSD doensn't support 802.11ac, yet. I'm bitter aware of that. This OS doesn't support the chipsets, even if they provide also 11a/g/n. We have at our department now a bunch of Lenovo hardware, with Intels 7260 chipset. The laptops are now runninmg Ubuntu 14.0X something which obviously supports the WiFi chip. I'm the last man standing with FreeBSD on my private Lenovo :-( This is a serious problem. I'm about ready to install Linux on my laptop as well just to get a usable system. Some kind of funding directed to a willing developer would be hugely valuable for the usability of the operating system on recent hardware. This is probably more important even than Haswell graphics since without a driver, Haswell is merely slow, whereas networking is completely broken. -Nathan While I don't yet have need of it and probably won't any time soon, Haswell support is becoming critical. It is getting more and more difficult to get boards with pre-Haswell processors, especially for laptops. It is still pretty easy to get supported WiFi cards for both desktops and laptops. I feel Haswell is getting to be a critical issue. VESA is available for Haswell systems, but it is very slow and too often the BIOS support of VESA is poor. Vendors want text mode for boot and such, but really have little interest in graphics as Intel has good native Windows drivers for them.Still waiting for Lenovo to fix VESA for my old Sandy Bridge laptop. I used VESA, which was badly broken, for almost a year waiting for KMS support, though I did get a recent BIOS update and have not tried VESA on it. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: AHCI after 271145 does not work for me
Hi Warner, it's not AHCI, it's something else I am trying to track down. Sorry for thinking it was AHCI, the kernel loops at the latest probe, which happens to be AHCI, but if I remove that from the kernel it loops on something else (usb, clock, whatever). Cheers, On Thu, 25 Sep 2014 17:55:09 -0700, Warner Losh wrote I’m afraid I have no clue. I’ll need hardware to debug this, since I don’t have any, or someone that can provide some feedback or even probe messages with it going off the rails (before/after). Warner On Sep 25, 2014, at 9:12 AM, Adrian Chadd adr...@freebsd.org wrote: Hi! 271146 was Warner's AHCI probe/attach changes. Maybe he'll have some ideas. :) Warner? -a On 25 September 2014 08:48, José Pérez Arauzo f...@aoek.com wrote: Hi, on my Acer Aspire V5, AHCI does not complete device_attach after 271145. Am I the only one experiencing this? Can I help fixing it? Thank you. BR, -- José Pérez Arauzo ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org -- José Pérez Arauzo ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
What do you use for kernel debugging?
Hello, I am trying to track down a (deadlock?) issue in CURRENT via DDB. The kernel does not complete hw probes on my Acer V5. I get stuck on apic_isr looping which leads nowhere. So I thought maybe things improve if I debug from another machine. What do you use for kernel debugging? According to the handbook kgdb over serial is a good option, do you agree? I'm on a netbook with no ethernet and no option for firewire: can I have a USB / nullmodem setup to work? I have no old-style uarts hardware anymore, as the handbook suggests... Any idea is welcome before I buy extra hw. I have a USB to serial showing up as /dev/cuaU0, do I need to grab another one and a nullmodem cable or there are better alternatives? Thank you. BR, -- José Pérez Arauzo ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: WiFi 802.11/ac PCIe supported adaptor
Am Sat, 27 Sep 2014 23:44:19 -0700 Kevin Oberman rkober...@gmail.com schrieb: On Sat, Sep 27, 2014 at 11:20 PM, Nathan Whitehorn nwhiteh...@freebsd.org wrote: On 09/27/14 23:06, O. Hartmann wrote: Am Sun, 28 Sep 2014 00:22:09 +0200 Lars Engels lars.eng...@0x20.net schrieb: On Sat, Sep 27, 2014 at 02:38:30PM +0200, O. Hartmann wrote: I'm looking for a replacemnt for my 802.11g WiFi PCIe adaptor card and want to replace it with an 802.11ac adaptor. Since I made very bad experiences with CURRENT and support of modest modern hardware (Haswell CPU/Intel 7260 DualBand WiFi NIC), I'd like to ask here first. I found this PCIe adaptor card attractive: GigaByte Gigabyte GC-WB867D-I I can not find ad hoc the WLAN chip used on that specific card, but maybe someone has experiences with that litte board. FreeBSD doensn't support 802.11ac, yet. I'm bitter aware of that. This OS doesn't support the chipsets, even if they provide also 11a/g/n. We have at our department now a bunch of Lenovo hardware, with Intels 7260 chipset. The laptops are now runninmg Ubuntu 14.0X something which obviously supports the WiFi chip. I'm the last man standing with FreeBSD on my private Lenovo :-( This is a serious problem. I'm about ready to install Linux on my laptop as well just to get a usable system. Some kind of funding directed to a willing developer would be hugely valuable for the usability of the operating system on recent hardware. This is probably more important even than Haswell graphics since without a driver, Haswell is merely slow, whereas networking is completely broken. -Nathan While I don't yet have need of it and probably won't any time soon, Haswell support is becoming critical. It is getting more and more difficult to get boards with pre-Haswell processors, especially for laptops. It is still pretty easy to get supported WiFi cards for both desktops and laptops. I feel Haswell is getting to be a critical issue. VESA is available for Haswell systems, but it is very slow and too often the BIOS support of VESA is poor. Vendors want text mode for boot and such, but really have little interest in graphics as Intel has good native Windows drivers for them.Still waiting for Lenovo to fix VESA for my old Sandy Bridge laptop. I used VESA, which was badly broken, for almost a year waiting for KMS support, though I did get a recent BIOS update and have not tried VESA on it. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org Some notes from my side. I have personally a i3-3220 IvyBridge based server with iGPU HD2500, which doesn't work properly on CURRENT and gets messed up with EFI and vt(). The screen is dark after loading i915kms and the reason having a highres console is at hand. This is two year old hardware! This server is now getting a new XEON CPU (same board, but with a professional CPU i5-122X v2 with a P4000 iGPU). At another site I work for there are plans obtaining also such toy-XEONs for power consumption reasons and the iGPU play an important role here. And those systems are due to government funding for the next couple of years definitely NOT outdated hardware from the past, they will be Haswell. So what now? As far as I can say: maintaining a FreeBSD based server system on hardware that needs more than one single compromise is cost-ineffective. I hate to judge things in terms of cost-effectiveness, but the time, I spent now getting a crap iGPU on my laptop to work or that on that IvyBridge is unaffordable! The same is now with the laptops. Intels iGPU is getting stronger and stronger and combined with their CPUs, there is rarely need for a dedicated GPU. We use OpenCL a lot, so GPUs are welcome, even in notebooks. But not for FreeBSD, since OpenCL seems to be Linux-domain only. Anyway, the new bunch of laptops we order is not the crap from yesterday. Since my last Dell had to last for at least four years, I will order top of the line hardware now - and I'm willing to wait for some weeks, two months with interim solutions until FreeBSD would support the hardware we obtain, but compared to the past I see chance. Not all of us want Linux, some use PC-BSD, some FreeBSD. The picture changes now. Networking wasn't an issue for me for years, but now, sitting on a pile of neat new hardware of which FreeBSD can not make any serious use, let me rethink. Luckily, The Lenovo laptops have a mini PCIe WiFi NIC - if I'm willing to follow FreeBSDs agony I'm able to swap the NIC with a piece of hardware that is supported. But it is additional cost. I would happily do so - if there wouldn't be Linux support! I tried Ubuntu 14 something, and the
Re: x11/nvidia-driver (340.24/340.32/343.13): nvidia BLOB doesn't recognize any display socket on Lenovo E540/UEFI and FBSD CURRENT
Am Sat, 20 Sep 2014 21:21:46 +0200 Koop Mast k...@rainbow-runner.nl schrieb: On Sat, 2014-09-20 at 20:13 +0200, O. Hartmann wrote: Am Sat, 20 Sep 2014 19:15:30 +0200 O. Hartmann ohart...@zedat.fu-berlin.de schrieb: Am Sat, 20 Sep 2014 08:27:27 -0600 (MDT) Warren Block wbl...@wonkity.com schrieb: On Sat, 20 Sep 2014, O. Hartmann wrote: Am Sat, 20 Sep 2014 07:36:21 -0600 (MDT) Warren Block wbl...@wonkity.com schrieb: On Fri, 19 Sep 2014, O. Hartmann wrote: nVidia's BLOB from port x11/nvidia-driver seems to have problems in FreeBSD 11.0-CURRENT #2 r271869: Fri Sep 19 13:28:03 CEST 2014 amd64, on Lenovo ThinkPad Edge E540 laptop with CPU i5-4200M (Haswell) with integrated HD4600 Intel iGPU and dedicated nVidia GT 740M (Optimus) working correctly. Optimus is supposed to be full Intel graphics plus an Nvidia GPU. The extra GPU uses the same display memory and can be enabled to speed up the Intel graphics or disabled for power saving. I don't know if versions where the Nvidia section is a full discrete video adapter that can be used alone are still called Optimus. Some Optimus owners have reported being able to use the Intel drivers after disabling the Nvidia GPU in the BIOS or UEFI. If an option to disable the Nvidia GPU is not present, some people have reported success with an xorg.conf that uses only the intel driver and ignores the Nvidia hardware. Thanks Warren. But this sounds even more frustrating now. I look around the web even at Lenovo's support forum. Many people report the GT 740M nVidia adaptor as a discrete adaptor with Optimus technology and everything sounds to me like it can be selected exclusively. What you describes is that I definitely need to use the HD4600 iGPU on FreeBSD in the first place since the nVidia hardware is a kind of appendix to the HD4600. Optimus started out that way, but they might use the same name now for models where the additional GPU is a full discrete adapter. I tried to retrieve informations about the settings and implementations in the lenovo E540, but I guess the only answer can be given by developer documentation. I can not figure out how the GPU is attached to the system. The technical specifications do not mention the requirement of a iGPU and shared memory - as Optimus would require. But extrapolating from that shit-covering public relations talking at nVidia's site I guess the GT 740M is definitely a shared memory solution and requires the presence of the iGPU. That would explain why the nvidia BLOB is detecting the GPU, but can not find any physical display socket, not even the built-in LCD. They're maybe wired all throught the Haswell's HD4600 iGPU? Anyway, I also tried to configure X11 as HD4600 only and X11 doesn't work properly: it doesn't even start up and loading the intel driver complains about a missing device - preceeded by a lot of /dev/dri errors. This indicates to me, in a naiv manner, that this HD4600 isn't recodnized by the kernel, either. I do not see any kind of vga0: entry in the kernel log when enabling Integrated Graphics only in the laptop's UEFI/Firmware. When enabling nVidia Optimus, a recognized vga0: device shows up. Whoops, HD4600 is Haswell. The intel driver on FreeBSD does not support Haswell video yet. I suspected that :-( Thanks anyway, Oliver Oh, by the way, where is x11-drivers/xf86-video-noveau? I can only find x11-drivers/xf86-video-nv, which covers old hardware and it is not applicable to the GT 740M (complains, rightfully, that the found device isn't supported by the nv driver). I face a mess here ... :-( It was removed, because we missing kernel support for the nouveau driver. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org Without nouveau driver, FreeBSD people do not have the slightes chance to play with OpenCL/libclc on nVidia's hardware. I'm eager to watch the day when even the Radeon driver gets ripped off due to lack of kernel support :-) signature.asc Description: PGP signature
Re: WiFi 802.11/ac PCIe supported adaptor
These should be good job for The FreeBSD FOUNDATION, like former Diablo JDK/JRE case. At least, as far as I remember, adrian@ noted a patent issue (RSU) in porting Intel 7260AC.[1] If I remember correctly, there was anothe thread in another ML, but currently I missed it. Maybe -arch ML? In these cases, The FreeBSD FOUNDATION would be good legal body for licence contracts / agreements with patent holder(s). [1] https://lists.freebsd.org/pipermail/freebsd-wireless/2014-June/004748.html On Sat, 27 Sep 2014 23:20:53 -0700 Nathan Whitehorn nwhiteh...@freebsd.org wrote: On 09/27/14 23:06, O. Hartmann wrote: Am Sun, 28 Sep 2014 00:22:09 +0200 Lars Engels lars.eng...@0x20.net schrieb: On Sat, Sep 27, 2014 at 02:38:30PM +0200, O. Hartmann wrote: I'm looking for a replacemnt for my 802.11g WiFi PCIe adaptor card and want to replace it with an 802.11ac adaptor. Since I made very bad experiences with CURRENT and support of modest modern hardware (Haswell CPU/Intel 7260 DualBand WiFi NIC), I'd like to ask here first. I found this PCIe adaptor card attractive: GigaByte Gigabyte GC-WB867D-I I can not find ad hoc the WLAN chip used on that specific card, but maybe someone has experiences with that litte board. FreeBSD doensn't support 802.11ac, yet. I'm bitter aware of that. This OS doesn't support the chipsets, even if they provide also 11a/g/n. We have at our department now a bunch of Lenovo hardware, with Intels 7260 chipset. The laptops are now runninmg Ubuntu 14.0X something which obviously supports the WiFi chip. I'm the last man standing with FreeBSD on my private Lenovo :-( This is a serious problem. I'm about ready to install Linux on my laptop as well just to get a usable system. Some kind of funding directed to a willing developer would be hugely valuable for the usability of the operating system on recent hardware. This is probably more important even than Haswell graphics since without a driver, Haswell is merely slow, whereas networking is completely broken. -Nathan ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org -- Tomoaki AOKIjunch...@dec.sakura.ne.jp ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: WiFi 802.11/ac PCIe supported adaptor
Am Sat, 27 Sep 2014 23:44:19 -0700 Kevin Oberman rkober...@gmail.com schrieb: On Sat, Sep 27, 2014 at 11:20 PM, Nathan Whitehorn nwhiteh...@freebsd.org wrote: On 09/27/14 23:06, O. Hartmann wrote: Am Sun, 28 Sep 2014 00:22:09 +0200 Lars Engels lars.eng...@0x20.net schrieb: On Sat, Sep 27, 2014 at 02:38:30PM +0200, O. Hartmann wrote: I'm looking for a replacemnt for my 802.11g WiFi PCIe adaptor card and want to replace it with an 802.11ac adaptor. Since I made very bad experiences with CURRENT and support of modest modern hardware (Haswell CPU/Intel 7260 DualBand WiFi NIC), I'd like to ask here first. I found this PCIe adaptor card attractive: GigaByte Gigabyte GC-WB867D-I I can not find ad hoc the WLAN chip used on that specific card, but maybe someone has experiences with that litte board. FreeBSD doensn't support 802.11ac, yet. I'm bitter aware of that. This OS doesn't support the chipsets, even if they provide also 11a/g/n. We have at our department now a bunch of Lenovo hardware, with Intels 7260 chipset. The laptops are now runninmg Ubuntu 14.0X something which obviously supports the WiFi chip. I'm the last man standing with FreeBSD on my private Lenovo :-( This is a serious problem. I'm about ready to install Linux on my laptop as well just to get a usable system. Some kind of funding directed to a willing developer would be hugely valuable for the usability of the operating system on recent hardware. This is probably more important even than Haswell graphics since without a driver, Haswell is merely slow, whereas networking is completely broken. -Nathan While I don't yet have need of it and probably won't any time soon, Haswell support is becoming critical. It is getting more and more difficult to get boards with pre-Haswell processors, especially for laptops. It is still pretty easy to get supported WiFi cards for both desktops and laptops. I feel Haswell is getting to be a critical issue. I use the xf86-video-scfb driver, VESA driver doesn' coop with the resolution of my display (called Full HD, 1980x1080 pixel). VESA complains about not know resolution when starting. The SCFB is unusable. The i5-4200M CPU has enough stamina to do well, but when it comes to video/desktop/graphics under load, the graphics is rendered unusable. The laptop is not productive and an expensive heap of plastic, silica and metal with FreeBSD that way. VESA is available for Haswell systems, but it is very slow and too often the BIOS support of VESA is poor. Vendors want text mode for boot and such, but really have little interest in graphics as Intel has good native Windows drivers for them.Still waiting for Lenovo to fix VESA for my old Sandy Bridge laptop. I used VESA, which was badly broken, for almost a year waiting for KMS support, though I did get a recent BIOS update and have not tried VESA on it. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org signature.asc Description: PGP signature
Re: x11/nvidia-driver (340.24/340.32/343.13): nvidia BLOB doesn't recognize any display socket on Lenovo E540/UEFI and FBSD CURRENT
On 28.09.2014 11:41, O. Hartmann wrote: Without nouveau driver, FreeBSD people do not have the slightes chance to play with OpenCL/libclc on nVidia's hardware. Some time in the past it was possible to run CUDA/OpenCL Linux binaries with the Nvidia driver in Linux emulation mode on FreeBSD: https://web.archive.org/web/20121015180221/http://blogs.freebsdish.org/jhb/2010/07/20/using-cuda-with-the-native-freebsdamd64-nvidia-driver Not sure if that still works though. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: WiFi 802.11/ac PCIe supported adaptor
Grr... Not RSU, but RCU. And found these threads in -arch ML. https://lists.freebsd.org/pipermail/freebsd-arch/2014-June/015413.html https://lists.freebsd.org/pipermail/freebsd-arch/2014-June/015419.html On Sun, 28 Sep 2014 18:45:23 +0900 Tomoaki AOKI junch...@dec.sakura.ne.jp wrote: These should be good job for The FreeBSD FOUNDATION, like former Diablo JDK/JRE case. At least, as far as I remember, adrian@ noted a patent issue (RSU) in porting Intel 7260AC.[1] If I remember correctly, there was anothe thread in another ML, but currently I missed it. Maybe -arch ML? In these cases, The FreeBSD FOUNDATION would be good legal body for licence contracts / agreements with patent holder(s). [1] https://lists.freebsd.org/pipermail/freebsd-wireless/2014-June/004748.html On Sat, 27 Sep 2014 23:20:53 -0700 Nathan Whitehorn nwhiteh...@freebsd.org wrote: On 09/27/14 23:06, O. Hartmann wrote: Am Sun, 28 Sep 2014 00:22:09 +0200 Lars Engels lars.eng...@0x20.net schrieb: On Sat, Sep 27, 2014 at 02:38:30PM +0200, O. Hartmann wrote: I'm looking for a replacemnt for my 802.11g WiFi PCIe adaptor card and want to replace it with an 802.11ac adaptor. Since I made very bad experiences with CURRENT and support of modest modern hardware (Haswell CPU/Intel 7260 DualBand WiFi NIC), I'd like to ask here first. I found this PCIe adaptor card attractive: GigaByte Gigabyte GC-WB867D-I I can not find ad hoc the WLAN chip used on that specific card, but maybe someone has experiences with that litte board. FreeBSD doensn't support 802.11ac, yet. I'm bitter aware of that. This OS doesn't support the chipsets, even if they provide also 11a/g/n. We have at our department now a bunch of Lenovo hardware, with Intels 7260 chipset. The laptops are now runninmg Ubuntu 14.0X something which obviously supports the WiFi chip. I'm the last man standing with FreeBSD on my private Lenovo :-( This is a serious problem. I'm about ready to install Linux on my laptop as well just to get a usable system. Some kind of funding directed to a willing developer would be hugely valuable for the usability of the operating system on recent hardware. This is probably more important even than Haswell graphics since without a driver, Haswell is merely slow, whereas networking is completely broken. -Nathan ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org -- Tomoaki AOKIjunch...@dec.sakura.ne.jp ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org -- Tomoaki AOKIjunch...@dec.sakura.ne.jp ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: x11/nvidia-driver (340.24/340.32/343.13): nvidia BLOB doesn't recognize any display socket on Lenovo E540/UEFI and FBSD CURRENT
Am Sun, 28 Sep 2014 12:05:36 +0200 Jan Kokemüller jan.kokemuel...@gmail.com schrieb: On 28.09.2014 11:41, O. Hartmann wrote: Without nouveau driver, FreeBSD people do not have the slightes chance to play with OpenCL/libclc on nVidia's hardware. Some time in the past it was possible to run CUDA/OpenCL Linux binaries with the Nvidia driver in Linux emulation mode on FreeBSD: https://web.archive.org/web/20121015180221/http://blogs.freebsdish.org/jhb/2010/07/20/using-cuda-with-the-native-freebsdamd64-nvidia-driver Not sure if that still works though. Well, I went through this stuff that time and from the date, you can see its four years in the past! There was also thast promising thing from Pathscale, HMPC ast promising thing from Pathscale, HMPC or similar, now OpenACC. But at the end it was a dream-bubble. And as far as I know: even the Linuxulator is ways behind the recent development and still 32Bit (ancient, so to speak). I do not want myself having lots of outdated hard- and software running and developing on outdated platforms. And it is even worse: some new technology utilizing LLVM, libCLC, most recent MESA libs and the most recent opensource graphics driver provide rudimentary OpenCL support for the GPU - but as I stated in the thread concerning the missing WiFi Intel 7260 support - FreeBSD hasn't even the xf86-video-nouveau driver anymore which is supposed to work best in that scenario. I had very longish discussions in 2010 about this subject - from a naiv non-developer point of view. I was always told, FreeBSD is an OS for servers and we all know, that servers do not rely on graphics hardware that much as it is important for graphics workstations and not at least desktop machines. But what we faced five years ago in science regarding the rapid development of OpenCL and GPGPU showed me very ckearly that GPU hardware is becoming dramatically important. With AMD providing powerful iGPUs and now Intel doing the same, number crunching isn't the domain of physicists and numerical geeks anymore, GEGL starts to incorporate OpenCL and GIMP is about to utilize the GPU as well. BLENDER is utilizing CUDA in Linux and I guess OpenCL is also on the way. And if this isn't convincing: I read about cloud computing with massively parallelized TESLA backends, a typical domain of dump and unexciting hardware and their operating systems. And guess what? The key is obviously the support of the graphical functionality, not necessarily the X11 desktop it self. The project that time in 2010, where we were supposed and inclined to use FreeBSD as the development platform for a highly parallelized application for planetary science imaging was then based on OpenSUSE and Ubuntu Linux and OpenCL. From a simple naive point of view, I can not express deeply enough how excited I was when I saw, how fast the combination of CPUs and GPUs using OpenCL coding could be. What was done in an expensive and professional manner on expensive hardware was developed and tested on cheaper gaming riggs and even on those platforms the boost was tremendous. But not with FreeBSD! All Linux. I think FreeBSD will find its niche in the embedded networking hardware market as long as it still has the faster network stack. But since the Linux folks started to attack this domain in a disgusting PR-ish way, I doubt that even this will last long. Or FreeBSD will show its power with colourless databases. One of the reasons why FreeBSD is still on top of the list of the OSes is the fact of its deep ZFS incorporation - as Matthew Dillon once said: it saved FreeBSD's ass. Well, Dillon developed then HAMMER and showed once again, that the effords in the BSD field are spread all over the area and thinning out as times passes. For FreeBSD, the day when Linux will have its ZFS in-kernel will be devastating - I guess. signature.asc Description: PGP signature
Re: WiFi 802.11/ac PCIe supported adaptor
On Sun, 28 Sep 2014, O. Hartmann wrote: Am Sat, 27 Sep 2014 23:44:19 -0700 Kevin Oberman rkober...@gmail.com schrieb: On Sat, Sep 27, 2014 at 11:20 PM, Nathan Whitehorn nwhiteh...@freebsd.org wrote: On 09/27/14 23:06, O. Hartmann wrote: Am Sun, 28 Sep 2014 00:22:09 +0200 Lars Engels lars.eng...@0x20.net schrieb: FreeBSD doensn't support 802.11ac, yet. I'm bitter aware of that. This OS doesn't support the chipsets, even if they provide also 11a/g/n. As Lars says, we don't yet support anything 11ac, either hardware/driver wise, or in the 802.11 stack. I am aware of people working on support for the 7260, though I suspect a working driver will be some time away. It will also only support a/b/g and maybe n to begin with - we are quite a way from having 11ac support in the stack. We have at our department now a bunch of Lenovo hardware, with Intels 7260 chipset. The laptops are now runninmg Ubuntu 14.0X something which obviously supports the WiFi chip. I'm the last man standing with FreeBSD on my private Lenovo :-( This is a serious problem. I'm about ready to install Linux on my laptop as well just to get a usable system. Some kind of funding directed to a willing developer would be hugely valuable for the usability of the operating system on recent hardware. This is probably more important even than Haswell graphics since without a driver, Haswell is merely slow, whereas networking is completely broken. Unfortunately, funding is just half the problem - we also need to find a developer capable of doing the work. The Intel 3160 and 7260 will likely require a whole new driver - almost no code can be shared between it and the iwn(4) driver. Please understand though that getting a driver for the Intel 11ac devices is seen as a big priority. Some notes from my side. I have personally a i3-3220 IvyBridge based server with iGPU HD2500, which doesn't work properly on CURRENT and gets messed up with EFI and vt(). The screen is dark after loading i915kms and the reason having a highres console is at hand. This is two year old hardware! This server is now getting a new XEON CPU (same board, but with a professional Can you point me to a thread or PR about this? Networking wasn't an issue for me for years, but now, sitting on a pile of neat new hardware of which FreeBSD can not make any serious use, let me rethink. Luckily, The Lenovo laptops have a mini PCIe WiFi NIC - if I'm willing to follow FreeBSDs agony I'm able to swap the NIC with a piece of hardware that is supported. But it is additional Unfortunately, many Lenovo laptops lock the BIOS down in such a way that they won't boot without the NIC they were shipped with :( I was always told (or even thaught!) that FreeBSD hasn't the fundings or the manpower to solve problems like KMS, driver and so on. I guess several Linux distributions face a similar problem, but somehow the manufactureres emmit drivers or support. I was aware of that guy that was payed by Intel to develop OpenSource NIC drivers, wasn't his name Vogel? What happened to him? If FreeBSD is pushed more and more in the background, then Jack Vogel still supports wired Intel NIC drivers for us, and other Intel staff support other hardware such as their new storage controllers. it is also due to a bad politics. nVidia, for instance, offers a BLOB for their GPUs. Yeah! But no OpenCL support. AMD offers nothing but promises and their efforts regarding opensource drivers is a pity. nVidia just informed Nouveau (so the headline at Phoronix, if I'm not wrong), that they now make some new restrictions about their harware. Well, FreeBSD hasn't this problem, we do not haven even xf86-video-nouveau in the ports due to the lack of functionality in the kernel. The fact is: under these circumstances, FreeBSD is UNUSABLE on some sort of recent hardware and even opensource drivers are not an option anymore. I'm not hugely knowledgeable on the state of drivers, but: - We have new drivers for the Radeon stuff, in head and 10.1. - nVidia provide FreeBSD drivers for FreeBSD. I understand that part of the reason we don't have OpenCL support is because they don't know there is a demand for it. - I have no idea what functionality we lack for Nouveau, is that documented anywhere? Thanks, Gavin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: SOEKRIS kernel config
That's a great idea. I'll give it a try and get back to the list. On Sun, Sep 28, 2014 at 12:33 AM, Scot Hetzel swhet...@gmail.com wrote: On Sat, Sep 27, 2014 at 9:47 PM, Tom Everett t...@khubla.com wrote: I see there is no SOEKRIS config on the tree, here https://svnweb.freebsd.org/base/head/sys/i386/conf/ I have attached one for addition to the tree. Since you only appended a few configuration options to the end of the GENERIC configuration, it would be better to use the include directive in the SOEKRIS config file. This allows changes to be made to the GENERIC configuration, and the SOEKRIS kernel would automatically get those changes. Here's a shorter version of that configuration file: # # SOEKRIS -- Generic Kernel configuration file for FreeBSD/i386 on SOEKRIS # # $FREEBSD include GENERIC ident SOEKRIS # To Make a SOEKRIS Kernel, the next options are needed options CPU_SOEKRIS options CPU_ELAN #options CPU_ELAN_PPS #options CPU_ELAN_XTAL=32768000 options CPU_GEODE # Include TMPFS options TMPFS -- DISCLAIMER: No electrons were maimed while sending this message. Only slightly bruised. -- A better world shall emerge based on faith and understanding - Douglas MacArthur ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[no subject]
I'm starting to look at FreeBSD 11-current to see what's coming soon. I have an older notebook that I use for test environments for purposes such as this. Unfortunately, the notebook won't boot up from the install CD, there's a loop it cannot seem to get out of. Details are: - The install CD was made from this image: FreeBSD-11.0-CURRENT-i386-20140918-r271779-disc1 - The dmesg for the notebook is at the end of this message. The dmesg was captured with FreeBSD 10.0. In the dmesg, you can see the following lines: (aprobe0:ata1:0:1:0): ATAPI_IDENTIFY. ACB: a1 00 00 00 00 40 00 00 00 00 00 00 (aprobe0:ata1:0:1:0): CAM status: Command timeout (aprobe0:ata1:0:1:0): Error 5, Retry was blocked run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config (aprobe0:ata1:0:1:0): ATAPI_IDENTIFY. ACB: a1 00 00 00 00 40 00 00 00 00 00 00 (aprobe0:ata1:0:1:0): CAM status: Command timeout (aprobe0:ata1:0:1:0): Error 5, Retry was blocked which, while slowing down the boot process drastically, still allowed the boot process to run to successful completion. - When I try to boot using the FreeBSD 11-current install CD, that loop seems to go on ad infinitum, or at least for the 5 minutes until I gave up. I cannot post a dmesg from that boot-up because I never got to a prompt. However, I did take a couple of pictures of the offending screens. They are here: http://archive.mgm51.com/cache/fbsd-11-current-01.jpg http://archive.mgm51.com/cache/fbsd-11-current-02.jpg The first image shows the start of the looping, and the second shows the continuation. While this notebook is used only for testing, it is important to me in that aspect. How can I get around this looping issue? Please let me know if there's any additional info you need. Thanks. And now, the dmesg... Copyright (c) 1992-2014 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.0-RELEASE-p8 #1 r271323: Wed Sep 10 20:25:45 EDT 2014 r...@a31pf.245l.home:/usr/obj/usr/src/sys/GENERIC i386 FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 CPU: Intel(R) Pentium(R) 4 Mobile CPU 1.70GHz (1698.60-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf24 Family = 0xf Model = 0x2 Stepping = 4 Features=0x3febf9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE, MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM real memory = 1073741824 (1024 MB) avail memory = 1029230592 (981 MB) kbd1 at kbdmux0 random: Software, Yarrow initialized acpi0: IBM TP-1G on motherboard acpi_ec0: Embedded Controller: GPE 0x1c, ECDT port 0x62,0x66 on acpi0 acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 3ff0 (3) failed cpu0: ACPI CPU on acpi0 attimer0: AT timer port 0x40-0x43 irq 0 on acpi0 Timecounter i8254 frequency 1193182 Hz quality 0 Event timer i8254 frequency 1193182 Hz quality 100 atrtc0: AT realtime clock port 0x70-0x71 irq 8 on acpi0 Event timer RTC frequency 32768 Hz quality 0 Timecounter ACPI-safe frequency 3579545 Hz quality 850 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 acpi_lid0: Control Method Lid Switch on acpi0 acpi_button0: Sleep Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Intel 82845 host to AGP bridge on hostb0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 vgapci0: VGA-compatible display port 0x3000-0x30ff mem 0xe800-0xefff,0xd010-0xd010 irq 11 at device 0.0 on pci1 vgapci0: Boot video device uhci0: Intel 82801CA/CAM (ICH3) USB controller USB-A port 0x1800-0x181f irq 11 at device 29.0 on pci0 usbus0 on uhci0 uhci1: Intel 82801CA/CAM (ICH3) USB controller USB-B port 0x1820-0x183f irq 11 at device 29.1 on pci0 usbus1 on uhci1 uhci2: Intel 82801CA/CAM (ICH3) USB controller USB-C port 0x1840-0x185f irq 11 at device 29.2 on pci0 usbus2 on uhci2 pcib2: ACPI PCI-PCI bridge at device 30.0 on pci0 pci2: ACPI PCI bus on pcib2 cbb0: RF5C476 PCI-CardBus Bridge mem 0x5000-0x5fff irq 11 at device 0.0 on pci2 cardbus0: CardBus bus on cbb0 pccard0: 16-bit PCCard bus on cbb0 cbb1: RF5C476 PCI-CardBus Bridge mem 0x5010-0x50100fff irq 11 at device 0.1 on pci2 cardbus1: CardBus bus on cbb1 pccard1: 16-bit PCCard bus on cbb1 pci2: serial bus, FireWire at device 0.2 (no driver attached) fxp0: Intel 82801CAM (ICH3) Pro/100 VE Ethernet port 0x8000-0x803f mem 0xd020-0xd0200fff irq 11 at device 8.0 on pci2 miibus0: MII bus on fxp0 inphy0: i82562ET 10/100 media interface PHY 1 on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow fxp0: Ethernet address: 00:0e:9b:2c:d3:f6 isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH3 UDMA100 controller port
Looping during boot-up process in FreeBSD-11 current
I'm starting to look at FreeBSD 11-current to see what's coming soon. I have an older notebook that I use for test environments for purposes such as this. Unfortunately, the notebook won't boot up from the install CD, there's a loop it cannot seem to get out of. Details are: - The install CD was made from this image: FreeBSD-11.0-CURRENT-i386-20140918-r271779-disc1 - The dmesg for the notebook is at the end of this message. The dmesg was captured with FreeBSD 10.0. In the dmesg, you can see the following lines: (aprobe0:ata1:0:1:0): ATAPI_IDENTIFY. ACB: a1 00 00 00 00 40 00 00 00 00 00 00 (aprobe0:ata1:0:1:0): CAM status: Command timeout (aprobe0:ata1:0:1:0): Error 5, Retry was blocked run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config (aprobe0:ata1:0:1:0): ATAPI_IDENTIFY. ACB: a1 00 00 00 00 40 00 00 00 00 00 00 (aprobe0:ata1:0:1:0): CAM status: Command timeout (aprobe0:ata1:0:1:0): Error 5, Retry was blocked which, while slowing down the boot process drastically, still allowed the boot process to run to successful completion. - When I try to boot using the FreeBSD 11-current install CD, that loop seems to go on ad infinitum, or at least for the 5 minutes until I gave up. I cannot post a dmesg from that boot-up because I never got to a prompt. However, I did take a couple of pictures of the offending screens. They are here: http://archive.mgm51.com/cache/fbsd-11-current-01.jpg http://archive.mgm51.com/cache/fbsd-11-current-02.jpg The first image shows the start of the looping, and the second shows the continuation. While this notebook is used only for testing, it is important to me in that aspect. How can I get around this looping issue? Please let me know if there's any additional info you need. Thanks. And now, the dmesg... Copyright (c) 1992-2014 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.0-RELEASE-p8 #1 r271323: Wed Sep 10 20:25:45 EDT 2014 r...@a31pf.245l.home:/usr/obj/usr/src/sys/GENERIC i386 FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 CPU: Intel(R) Pentium(R) 4 Mobile CPU 1.70GHz (1698.60-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf24 Family = 0xf Model = 0x2 Stepping = 4 Features=0x3febf9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE, MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM real memory = 1073741824 (1024 MB) avail memory = 1029230592 (981 MB) kbd1 at kbdmux0 random: Software, Yarrow initialized acpi0: IBM TP-1G on motherboard acpi_ec0: Embedded Controller: GPE 0x1c, ECDT port 0x62,0x66 on acpi0 acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 3ff0 (3) failed cpu0: ACPI CPU on acpi0 attimer0: AT timer port 0x40-0x43 irq 0 on acpi0 Timecounter i8254 frequency 1193182 Hz quality 0 Event timer i8254 frequency 1193182 Hz quality 100 atrtc0: AT realtime clock port 0x70-0x71 irq 8 on acpi0 Event timer RTC frequency 32768 Hz quality 0 Timecounter ACPI-safe frequency 3579545 Hz quality 850 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 acpi_lid0: Control Method Lid Switch on acpi0 acpi_button0: Sleep Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Intel 82845 host to AGP bridge on hostb0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 vgapci0: VGA-compatible display port 0x3000-0x30ff mem 0xe800-0xefff,0xd010-0xd010 irq 11 at device 0.0 on pci1 vgapci0: Boot video device uhci0: Intel 82801CA/CAM (ICH3) USB controller USB-A port 0x1800-0x181f irq 11 at device 29.0 on pci0 usbus0 on uhci0 uhci1: Intel 82801CA/CAM (ICH3) USB controller USB-B port 0x1820-0x183f irq 11 at device 29.1 on pci0 usbus1 on uhci1 uhci2: Intel 82801CA/CAM (ICH3) USB controller USB-C port 0x1840-0x185f irq 11 at device 29.2 on pci0 usbus2 on uhci2 pcib2: ACPI PCI-PCI bridge at device 30.0 on pci0 pci2: ACPI PCI bus on pcib2 cbb0: RF5C476 PCI-CardBus Bridge mem 0x5000-0x5fff irq 11 at device 0.0 on pci2 cardbus0: CardBus bus on cbb0 pccard0: 16-bit PCCard bus on cbb0 cbb1: RF5C476 PCI-CardBus Bridge mem 0x5010-0x50100fff irq 11 at device 0.1 on pci2 cardbus1: CardBus bus on cbb1 pccard1: 16-bit PCCard bus on cbb1 pci2: serial bus, FireWire at device 0.2 (no driver attached) fxp0: Intel 82801CAM (ICH3) Pro/100 VE Ethernet port 0x8000-0x803f mem 0xd020-0xd0200fff irq 11 at device 8.0 on pci2 miibus0: MII bus on fxp0 inphy0: i82562ET 10/100 media interface PHY 1 on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow fxp0: Ethernet address: 00:0e:9b:2c:d3:f6 isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH3 UDMA100 controller port
Re: Looping during boot-up process in FreeBSD-11 current
The only recent ATAPI change I recall is 270327, does it still occur if you revert that? Regards Steve - Original Message - From: Mike. the.li...@mgm51.com I'm starting to look at FreeBSD 11-current to see what's coming soon. I have an older notebook that I use for test environments for purposes such as this. Unfortunately, the notebook won't boot up from the install CD, there's a loop it cannot seem to get out of. Details are: - The install CD was made from this image: FreeBSD-11.0-CURRENT-i386-20140918-r271779-disc1 - The dmesg for the notebook is at the end of this message. The dmesg was captured with FreeBSD 10.0. In the dmesg, you can see the following lines: (aprobe0:ata1:0:1:0): ATAPI_IDENTIFY. ACB: a1 00 00 00 00 40 00 00 00 00 00 00 (aprobe0:ata1:0:1:0): CAM status: Command timeout (aprobe0:ata1:0:1:0): Error 5, Retry was blocked run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config (aprobe0:ata1:0:1:0): ATAPI_IDENTIFY. ACB: a1 00 00 00 00 40 00 00 00 00 00 00 (aprobe0:ata1:0:1:0): CAM status: Command timeout (aprobe0:ata1:0:1:0): Error 5, Retry was blocked which, while slowing down the boot process drastically, still allowed the boot process to run to successful completion. - When I try to boot using the FreeBSD 11-current install CD, that loop seems to go on ad infinitum, or at least for the 5 minutes until I gave up. I cannot post a dmesg from that boot-up because I never got to a prompt. However, I did take a couple of pictures of the offending screens. They are here: http://archive.mgm51.com/cache/fbsd-11-current-01.jpg http://archive.mgm51.com/cache/fbsd-11-current-02.jpg The first image shows the start of the looping, and the second shows the continuation. While this notebook is used only for testing, it is important to me in that aspect. How can I get around this looping issue? Please let me know if there's any additional info you need. Thanks. And now, the dmesg... Copyright (c) 1992-2014 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.0-RELEASE-p8 #1 r271323: Wed Sep 10 20:25:45 EDT 2014 r...@a31pf.245l.home:/usr/obj/usr/src/sys/GENERIC i386 FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 CPU: Intel(R) Pentium(R) 4 Mobile CPU 1.70GHz (1698.60-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf24 Family = 0xf Model = 0x2 Stepping = 4 Features=0x3febf9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE, MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM real memory = 1073741824 (1024 MB) avail memory = 1029230592 (981 MB) kbd1 at kbdmux0 random: Software, Yarrow initialized acpi0: IBM TP-1G on motherboard acpi_ec0: Embedded Controller: GPE 0x1c, ECDT port 0x62,0x66 on acpi0 acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 3ff0 (3) failed cpu0: ACPI CPU on acpi0 attimer0: AT timer port 0x40-0x43 irq 0 on acpi0 Timecounter i8254 frequency 1193182 Hz quality 0 Event timer i8254 frequency 1193182 Hz quality 100 atrtc0: AT realtime clock port 0x70-0x71 irq 8 on acpi0 Event timer RTC frequency 32768 Hz quality 0 Timecounter ACPI-safe frequency 3579545 Hz quality 850 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 acpi_lid0: Control Method Lid Switch on acpi0 acpi_button0: Sleep Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Intel 82845 host to AGP bridge on hostb0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 vgapci0: VGA-compatible display port 0x3000-0x30ff mem 0xe800-0xefff,0xd010-0xd010 irq 11 at device 0.0 on pci1 vgapci0: Boot video device uhci0: Intel 82801CA/CAM (ICH3) USB controller USB-A port 0x1800-0x181f irq 11 at device 29.0 on pci0 usbus0 on uhci0 uhci1: Intel 82801CA/CAM (ICH3) USB controller USB-B port 0x1820-0x183f irq 11 at device 29.1 on pci0 usbus1 on uhci1 uhci2: Intel 82801CA/CAM (ICH3) USB controller USB-C port 0x1840-0x185f irq 11 at device 29.2 on pci0 usbus2 on uhci2 pcib2: ACPI PCI-PCI bridge at device 30.0 on pci0 pci2: ACPI PCI bus on pcib2 cbb0: RF5C476 PCI-CardBus Bridge mem 0x5000-0x5fff irq 11 at device 0.0 on pci2 cardbus0: CardBus bus on cbb0 pccard0: 16-bit PCCard bus on cbb0 cbb1: RF5C476 PCI-CardBus Bridge mem 0x5010-0x50100fff irq 11 at device 0.1 on pci2 cardbus1: CardBus bus on cbb1 pccard1: 16-bit PCCard bus on cbb1 pci2: serial bus, FireWire at device 0.2 (no driver attached) fxp0: Intel 82801CAM (ICH3) Pro/100 VE Ethernet port 0x8000-0x803f mem 0xd020-0xd0200fff irq 11 at device 8.0 on pci2 miibus0: MII bus on fxp0 inphy0: i82562ET 10/100 media interface PHY 1 on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow fxp0: Ethernet address:
Re: Looping during boot-up process in FreeBSD-11 current
On 9/28/2014 at 5:01 PM Steven Hartland wrote: |The only recent ATAPI change I recall is 270327, does it still occur |if you revert that? | = OK, I'll download the 11-current source. Then revert 270327 https://svnweb.freebsd.org/base/head/sys/cam/ata/ata_xpt.c?r1=270327; r2=270326pathrev=270327 Recompile the system And try to boot. I'll post the results in a couple of days (full system compiles take a while on this notebook). (unless someone has a 11-current ISO snapshot from before 270327?) ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Looping during boot-up process in FreeBSD-11 current
You'll only need a new kernel and if you cut down to modules / drivers you need then that shouldn't take too long. Regards Steve - Original Message - From: Mike. the.li...@mgm51.com To: freebsd-current@freebsd.org Sent: Sunday, September 28, 2014 5:43 PM Subject: Re: Looping during boot-up process in FreeBSD-11 current On 9/28/2014 at 5:01 PM Steven Hartland wrote: |The only recent ATAPI change I recall is 270327, does it still occur |if you revert that? | = OK, I'll download the 11-current source. Then revert 270327 https://svnweb.freebsd.org/base/head/sys/cam/ata/ata_xpt.c?r1=270327; r2=270326pathrev=270327 Recompile the system And try to boot. I'll post the results in a couple of days (full system compiles take a while on this notebook). (unless someone has a 11-current ISO snapshot from before 270327?) ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Looping during boot-up process in FreeBSD-11 current
On 9/28/2014 at 6:25 PM Steven Hartland wrote: |You'll only need a new kernel and if you cut down to modules / drivers |you need then that shouldn't take too long. | = Buildworld is running now. So it will be running overnight, and should be finished by the time I can get to it again tomorrow. Thanks. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: What do you use for kernel debugging?
On Sun, 28 Sep 2014, José Pérez Arauzo wrote: Hello, I am trying to track down a (deadlock?) issue in CURRENT via DDB. The kernel does not complete hw probes on my Acer V5. I get stuck on apic_isr looping which leads nowhere. So I thought maybe things improve if I debug from another machine. What do you use for kernel debugging? According to the handbook kgdb over serial is a good option, do you agree? I'm on a netbook with no ethernet and no option for firewire: can I have a USB / nullmodem setup to work? You cannot. I have no old-style uarts hardware anymore, as the handbook suggests... Any idea is welcome before I buy extra hw. I have a USB to serial showing up as /dev/cuaU0, do I need to grab another one and a nullmodem cable or there are better alternatives? Thank you. I'm not sure that there are alternatives at all, unfortunately. You may be reduced to debugging-via-printf. -Ben Kaduk ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: SOEKRIS kernel config
Bugzilla ID is *194003 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194003* On Sun, Sep 28, 2014 at 8:59 AM, Tom Everett t...@khubla.com wrote: That's a great idea. I'll give it a try and get back to the list. On Sun, Sep 28, 2014 at 12:33 AM, Scot Hetzel swhet...@gmail.com wrote: On Sat, Sep 27, 2014 at 9:47 PM, Tom Everett t...@khubla.com wrote: I see there is no SOEKRIS config on the tree, here https://svnweb.freebsd.org/base/head/sys/i386/conf/ I have attached one for addition to the tree. Since you only appended a few configuration options to the end of the GENERIC configuration, it would be better to use the include directive in the SOEKRIS config file. This allows changes to be made to the GENERIC configuration, and the SOEKRIS kernel would automatically get those changes. Here's a shorter version of that configuration file: # # SOEKRIS -- Generic Kernel configuration file for FreeBSD/i386 on SOEKRIS # # $FREEBSD include GENERIC ident SOEKRIS # To Make a SOEKRIS Kernel, the next options are needed options CPU_SOEKRIS options CPU_ELAN #options CPU_ELAN_PPS #options CPU_ELAN_XTAL=32768000 options CPU_GEODE # Include TMPFS options TMPFS -- DISCLAIMER: No electrons were maimed while sending this message. Only slightly bruised. -- A better world shall emerge based on faith and understanding - Douglas MacArthur -- A better world shall emerge based on faith and understanding - Douglas MacArthur ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: What do you use for kernel debugging?
- Original Message - From: Benjamin Kaduk ka...@mit.edu To: José Pérez Arauzo f...@aoek.com Cc: FreeBSD Current freebsd-current@freebsd.org Sent: Sunday, September 28, 2014 8:54 PM Subject: Re: What do you use for kernel debugging? On Sun, 28 Sep 2014, José Pérez Arauzo wrote: Hello, I am trying to track down a (deadlock?) issue in CURRENT via DDB. The kernel does not complete hw probes on my Acer V5. I get stuck on apic_isr looping which leads nowhere. So I thought maybe things improve if I debug from another machine. What do you use for kernel debugging? According to the handbook kgdb over serial is a good option, do you agree? I'm on a netbook with no ethernet and no option for firewire: can I have a USB / nullmodem setup to work? You cannot. I have no old-style uarts hardware anymore, as the handbook suggests... Any idea is welcome before I buy extra hw. I have a USB to serial showing up as /dev/cuaU0, do I need to grab another one and a nullmodem cable or there are better alternatives? Thank you. I'm not sure that there are alternatives at all, unfortunately. You may be reduced to debugging-via-printf. dtrace can also be quite invaluable. Regards Steve ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: What do you use for kernel debugging?
On Sep 28, 2014, at 0:34, José Pérez Arauzo f...@aoek.com wrote: Hello, I am trying to track down a (deadlock?) issue in CURRENT via DDB. The kernel does not complete hw probes on my Acer V5. I get stuck on apic_isr looping which leads nowhere. So I thought maybe things improve if I debug from another machine. What do you use for kernel debugging? According to the handbook kgdb over serial is a good option, do you agree? I'm on a netbook with no ethernet and no option for firewire: can I have a USB / nullmodem setup to work? I have no old-style uarts hardware anymore, as the handbook suggests... Any idea is welcome before I buy extra hw. I have a USB to serial showing up as /dev/cuaU0, do I need to grab another one and a nullmodem cable or there are better alternatives? Thank you. There was some discussion recently about this on an internal list. Unfortunately no, there isn’t a usable way, but there were some interesting viable methods that came up (which haven’t been implemented): ethernet/sound/xHCI. Your best bet, as others have noted, is to use boot -d, use WITNESS to spot locking issues, dtrace to isolate which section of code there are problems, and finally use one of the DEBUG options noted in /sys/conf/NOTES and /sys/your-architecture/conf/NOTES . Hope that helps! -Garrett signature.asc Description: Message signed with OpenPGP using GPGMail
Re: WiFi 802.11/ac PCIe supported adaptor
On Sun, 28 Sep 2014, Gavin Atkinson wrote: On Sun, 28 Sep 2014, O. Hartmann wrote: Networking wasn't an issue for me for years, but now, sitting on a pile of neat new hardware of which FreeBSD can not make any serious use, let me rethink. Luckily, The Lenovo laptops have a mini PCIe WiFi NIC - if I'm willing to follow FreeBSDs agony I'm able to swap the NIC with a piece of hardware that is supported. But it is additional Unfortunately, many Lenovo laptops lock the BIOS down in such a way that they won't boot without the NIC they were shipped with :( Well, or a short list of approved Lenovo-branded cards. In the past, Lenovo (or IBM) has supplied Atheros cards. The trick will be finding that list and identifying the chipsets on each. There are also unofficial BIOS modifications to remove the limits. it is also due to a bad politics. nVidia, for instance, offers a BLOB for their GPUs. Yeah! But no OpenCL support. AMD offers nothing but promises and their efforts regarding opensource drivers is a pity. AMD has actually supported the open Radeon driver, both with programming information and (I think) employing developers to work on it. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: WiFi 802.11/ac PCIe supported adaptor
Hi, It's not a high priority in FreeBSD. It's just highly desired. There's a difference. Someone paid someone to do a 7260 driver for OpenBSD. It'll work, like iwn worked, but it's missing a lot of the 11n and 11ac bits that are going to be crucial to do 11ac stack bring-up on FreeBSD. So, if this is really high priority in FreeBSD, someone would've paid someone to port the Linux driver to FreeBSD. But right now all there really is right now is desire, not priority. -a On 28 September 2014 07:57, Gavin Atkinson ga...@freebsd.org wrote: On Sun, 28 Sep 2014, O. Hartmann wrote: Am Sat, 27 Sep 2014 23:44:19 -0700 Kevin Oberman rkober...@gmail.com schrieb: On Sat, Sep 27, 2014 at 11:20 PM, Nathan Whitehorn nwhiteh...@freebsd.org wrote: On 09/27/14 23:06, O. Hartmann wrote: Am Sun, 28 Sep 2014 00:22:09 +0200 Lars Engels lars.eng...@0x20.net schrieb: FreeBSD doensn't support 802.11ac, yet. I'm bitter aware of that. This OS doesn't support the chipsets, even if they provide also 11a/g/n. As Lars says, we don't yet support anything 11ac, either hardware/driver wise, or in the 802.11 stack. I am aware of people working on support for the 7260, though I suspect a working driver will be some time away. It will also only support a/b/g and maybe n to begin with - we are quite a way from having 11ac support in the stack. We have at our department now a bunch of Lenovo hardware, with Intels 7260 chipset. The laptops are now runninmg Ubuntu 14.0X something which obviously supports the WiFi chip. I'm the last man standing with FreeBSD on my private Lenovo :-( This is a serious problem. I'm about ready to install Linux on my laptop as well just to get a usable system. Some kind of funding directed to a willing developer would be hugely valuable for the usability of the operating system on recent hardware. This is probably more important even than Haswell graphics since without a driver, Haswell is merely slow, whereas networking is completely broken. Unfortunately, funding is just half the problem - we also need to find a developer capable of doing the work. The Intel 3160 and 7260 will likely require a whole new driver - almost no code can be shared between it and the iwn(4) driver. Please understand though that getting a driver for the Intel 11ac devices is seen as a big priority. Some notes from my side. I have personally a i3-3220 IvyBridge based server with iGPU HD2500, which doesn't work properly on CURRENT and gets messed up with EFI and vt(). The screen is dark after loading i915kms and the reason having a highres console is at hand. This is two year old hardware! This server is now getting a new XEON CPU (same board, but with a professional Can you point me to a thread or PR about this? Networking wasn't an issue for me for years, but now, sitting on a pile of neat new hardware of which FreeBSD can not make any serious use, let me rethink. Luckily, The Lenovo laptops have a mini PCIe WiFi NIC - if I'm willing to follow FreeBSDs agony I'm able to swap the NIC with a piece of hardware that is supported. But it is additional Unfortunately, many Lenovo laptops lock the BIOS down in such a way that they won't boot without the NIC they were shipped with :( I was always told (or even thaught!) that FreeBSD hasn't the fundings or the manpower to solve problems like KMS, driver and so on. I guess several Linux distributions face a similar problem, but somehow the manufactureres emmit drivers or support. I was aware of that guy that was payed by Intel to develop OpenSource NIC drivers, wasn't his name Vogel? What happened to him? If FreeBSD is pushed more and more in the background, then Jack Vogel still supports wired Intel NIC drivers for us, and other Intel staff support other hardware such as their new storage controllers. it is also due to a bad politics. nVidia, for instance, offers a BLOB for their GPUs. Yeah! But no OpenCL support. AMD offers nothing but promises and their efforts regarding opensource drivers is a pity. nVidia just informed Nouveau (so the headline at Phoronix, if I'm not wrong), that they now make some new restrictions about their harware. Well, FreeBSD hasn't this problem, we do not haven even xf86-video-nouveau in the ports due to the lack of functionality in the kernel. The fact is: under these circumstances, FreeBSD is UNUSABLE on some sort of recent hardware and even opensource drivers are not an option anymore. I'm not hugely knowledgeable on the state of drivers, but: - We have new drivers for the Radeon stuff, in head and 10.1. - nVidia provide FreeBSD drivers for FreeBSD. I understand that part of the reason we don't have OpenCL support is because they don't know there is a demand for it. - I have no idea what functionality we lack for Nouveau, is that documented anywhere? Thanks,
Mesa-9: configure: error: C compiler cannot create executables
Greetings, A recent install of RELENG_9, followed by a build|install world|kernel. Returns the following error when attempting an make install of x11/xorg-minimal === Configuring for dri-9.1.7_5,2 configure: loading site script /usr/ports/Templates/config.site checking build system type... amd64-portbld-freebsd9.3 checking host system type... amd64-portbld-freebsd9.3 checking target system type... amd64-portbld-freebsd9.3 checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking whether build environment is sane... yes checking for a thread-safe mkdir -p... (cached) /bin/mkdir -p checking for gawk... (cached) /usr/bin/awk checking whether gmake sets $(MAKE)... yes checking whether gmake supports nested variables... yes checking for style of include used by gmake... GNU checking for gcc... clang checking whether the C compiler works... no configure: error: in `/usr/ports/graphics/dri/work/Mesa-9.1.7': configure: error: C compiler cannot create executables See `config.log' for more details === Script configure failed unexpectedly. Please report the problem to x...@freebsd.org [maintainer] and attach the /usr/ports/graphics/dri/work/Mesa-9.1.7/config.log including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. a /usr/local/sbin/pkg-static info -g -Ea). *** [do-configure] Error code 1 Any thoughts on how to overcome this issue? Relevant info: # svn info /usr/src Path: /usr/src Working Copy Root Path: /usr/src URL: svn://svn.freebsd.org/base/stable/9 Relative URL: ^/stable/9 Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 272203 Node Kind: directory Schedule: normal Last Changed Author: thomas Last Changed Rev: 272184 Last Changed Date: 2014-09-26 12:13:13 -0700 (Fri, 26 Sep 2014) svn info /usr/ports Path: /usr/ports Working Copy Root Path: /usr/ports URL: svn://svn.freebsd.org/ports/head Relative URL: ^/head Repository Root: svn://svn.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 369380 Node Kind: directory Schedule: normal Last Changed Author: mva Last Changed Rev: 369380 Last Changed Date: 2014-09-27 01:34:11 -0700 (Sat, 27 Sep 2014) FreeBSD demon 9.3-STABLE FreeBSD 9.3-STABLE #0 r272203: Sat Sep 27 15:49:55 PDT 2014 root@demon:/usr/obj/usr/src/sys/DEMON amd64 Thank you for all your time, and consideration. --Chris ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Mesa-9: configure: error: C compiler cannot create executables
On 09/28/2014 17:37, Chris H wrote: Greetings, A recent install of RELENG_9, followed by a build|install world|kernel. Returns the following error when attempting an make install of x11/xorg-minimal === Configuring for dri-9.1.7_5,2 configure: loading site script /usr/ports/Templates/config.site checking build system type... amd64-portbld-freebsd9.3 checking host system type... amd64-portbld-freebsd9.3 checking target system type... amd64-portbld-freebsd9.3 checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking whether build environment is sane... yes checking for a thread-safe mkdir -p... (cached) /bin/mkdir -p checking for gawk... (cached) /usr/bin/awk checking whether gmake sets $(MAKE)... yes checking whether gmake supports nested variables... yes checking for style of include used by gmake... GNU checking for gcc... clang checking whether the C compiler works... no configure: error: in `/usr/ports/graphics/dri/work/Mesa-9.1.7': configure: error: C compiler cannot create executables See `config.log' for more details === Script configure failed unexpectedly. Please report the problem to x...@freebsd.org [maintainer] and attach the /usr/ports/graphics/dri/work/Mesa-9.1.7/config.log including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. a /usr/local/sbin/pkg-static info -g -Ea). *** [do-configure] Error code 1 Any thoughts on how to overcome this issue? Relevant info: # svn info /usr/src Path: /usr/src Working Copy Root Path: /usr/src URL: svn://svn.freebsd.org/base/stable/9 Relative URL: ^/stable/9 Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 272203 Node Kind: directory Schedule: normal Last Changed Author: thomas Last Changed Rev: 272184 Last Changed Date: 2014-09-26 12:13:13 -0700 (Fri, 26 Sep 2014) svn info /usr/ports Path: /usr/ports Working Copy Root Path: /usr/ports URL: svn://svn.freebsd.org/ports/head Relative URL: ^/head Repository Root: svn://svn.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 369380 Node Kind: directory Schedule: normal Last Changed Author: mva Last Changed Rev: 369380 Last Changed Date: 2014-09-27 01:34:11 -0700 (Sat, 27 Sep 2014) FreeBSD demon 9.3-STABLE FreeBSD 9.3-STABLE #0 r272203: Sat Sep 27 15:49:55 PDT 2014 root@demon:/usr/obj/usr/src/sys/DEMON amd64 Thank you for all your time, and consideration. --Chris ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org What does config.log say? also 'clang -v' -- Allan Jude ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Mesa-9: configure: error: C compiler cannot create executables
On 09/28/2014 17:37, Chris H wrote: Greetings, A recent install of RELENG_9, followed by a build|install world|kernel. Returns the following error when attempting an make install of x11/xorg-minimal === Configuring for dri-9.1.7_5,2 configure: loading site script /usr/ports/Templates/config.site checking build system type... amd64-portbld-freebsd9.3 checking host system type... amd64-portbld-freebsd9.3 checking target system type... amd64-portbld-freebsd9.3 checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking whether build environment is sane... yes checking for a thread-safe mkdir -p... (cached) /bin/mkdir -p checking for gawk... (cached) /usr/bin/awk checking whether gmake sets $(MAKE)... yes checking whether gmake supports nested variables... yes checking for style of include used by gmake... GNU checking for gcc... clang checking whether the C compiler works... no configure: error: in `/usr/ports/graphics/dri/work/Mesa-9.1.7': configure: error: C compiler cannot create executables See `config.log' for more details === Script configure failed unexpectedly. Please report the problem to x...@freebsd.org [maintainer] and attach the /usr/ports/graphics/dri/work/Mesa-9.1.7/config.log including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. a /usr/local/sbin/pkg-static info -g -Ea). *** [do-configure] Error code 1 Any thoughts on how to overcome this issue? Relevant info: # svn info /usr/src Path: /usr/src Working Copy Root Path: /usr/src URL: svn://svn.freebsd.org/base/stable/9 Relative URL: ^/stable/9 Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 272203 Node Kind: directory Schedule: normal Last Changed Author: thomas Last Changed Rev: 272184 Last Changed Date: 2014-09-26 12:13:13 -0700 (Fri, 26 Sep 2014) svn info /usr/ports Path: /usr/ports Working Copy Root Path: /usr/ports URL: svn://svn.freebsd.org/ports/head Relative URL: ^/head Repository Root: svn://svn.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 369380 Node Kind: directory Schedule: normal Last Changed Author: mva Last Changed Rev: 369380 Last Changed Date: 2014-09-27 01:34:11 -0700 (Sat, 27 Sep 2014) FreeBSD demon 9.3-STABLE FreeBSD 9.3-STABLE #0 r272203: Sat Sep 27 15:49:55 PDT 2014 root@demon:/usr/obj/usr/src/sys/DEMON amd64 Thank you for all your time, and consideration. --Chris ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org What does config.log say? Please see attached (config.log.txt) -- it's big. :) also 'clang -v' nadda -- don't think it's installed -- WITHOUT_CLANG=true (/etc/make.conf) Thank you for your thoughtful reply, Allan. --Chris -- Allan Jude ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by Mesa configure 9.1.7, which was generated by GNU Autoconf 2.69. Invocation command line was $ ./configure --disable-gles2 --disable-egl --enable-gallium-llvm --disable-gallium-egl --with-gallium-drivers=r300,r600,radeonsi,svga,swrast --with-dri-drivers=i915 i965 r200 radeon swrast --x-libraries=/usr/local/lib --x-includes=/usr/local/include --prefix=/usr/local --mandir=/usr/local/man --infodir=/usr/local/info/ --build=amd64-portbld-freebsd9.3 ## - ## ## Platform. ## ## - ## hostname = demon uname -m = amd64 uname -r = 9.3-STABLE uname -s = FreeBSD uname -v = FreeBSD 9.3-STABLE #0 r272203: Sat Sep 27 15:49:55 PDT 2014 root@demon:/usr/obj/usr/src/sys/DEMON /usr/bin/uname -p = amd64 /bin/uname -X = unknown /bin/arch = unknown /usr/bin/arch -k = unknown /usr/convex/getsysinfo = unknown /usr/bin/hostinfo = unknown /bin/machine = unknown /usr/bin/oslevel = unknown /bin/universe = unknown PATH: /sbin PATH: /bin PATH: /usr/sbin PATH: /usr/bin PATH: /usr/games PATH: /usr/local/sbin PATH: /usr/local/bin PATH: /root/bin ## --- ## ## Core tests. ## ## --- ## configure:2778: loading site script /usr/ports/Templates/config.site | # $FreeBSD: head/Templates/config.site 349240 2014-03-26 11:16:42Z bapt $ | # Do not add: | # - toolchain related | # - arch-dependent values | # - anything =no unless guaranteed to never be | # implemented in FreeBSD | # - also avoid working values | # This file must reflect the oldest supported
Re: Mesa-9: configure: error: C compiler cannot create executables
On 09/28/2014 18:11, Chris H wrote: On 09/28/2014 17:37, Chris H wrote: Greetings, A recent install of RELENG_9, followed by a build|install world|kernel. Returns the following error when attempting an make install of x11/xorg-minimal === Configuring for dri-9.1.7_5,2 configure: loading site script /usr/ports/Templates/config.site checking build system type... amd64-portbld-freebsd9.3 checking host system type... amd64-portbld-freebsd9.3 checking target system type... amd64-portbld-freebsd9.3 checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking whether build environment is sane... yes checking for a thread-safe mkdir -p... (cached) /bin/mkdir -p checking for gawk... (cached) /usr/bin/awk checking whether gmake sets $(MAKE)... yes checking whether gmake supports nested variables... yes checking for style of include used by gmake... GNU checking for gcc... clang checking whether the C compiler works... no configure: error: in `/usr/ports/graphics/dri/work/Mesa-9.1.7': configure: error: C compiler cannot create executables See `config.log' for more details === Script configure failed unexpectedly. Please report the problem to x...@freebsd.org [maintainer] and attach the /usr/ports/graphics/dri/work/Mesa-9.1.7/config.log including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. a /usr/local/sbin/pkg-static info -g -Ea). *** [do-configure] Error code 1 Any thoughts on how to overcome this issue? Relevant info: # svn info /usr/src Path: /usr/src Working Copy Root Path: /usr/src URL: svn://svn.freebsd.org/base/stable/9 Relative URL: ^/stable/9 Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 272203 Node Kind: directory Schedule: normal Last Changed Author: thomas Last Changed Rev: 272184 Last Changed Date: 2014-09-26 12:13:13 -0700 (Fri, 26 Sep 2014) svn info /usr/ports Path: /usr/ports Working Copy Root Path: /usr/ports URL: svn://svn.freebsd.org/ports/head Relative URL: ^/head Repository Root: svn://svn.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 369380 Node Kind: directory Schedule: normal Last Changed Author: mva Last Changed Rev: 369380 Last Changed Date: 2014-09-27 01:34:11 -0700 (Sat, 27 Sep 2014) FreeBSD demon 9.3-STABLE FreeBSD 9.3-STABLE #0 r272203: Sat Sep 27 15:49:55 PDT 2014 root@demon:/usr/obj/usr/src/sys/DEMON amd64 Thank you for all your time, and consideration. --Chris ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org What does config.log say? Please see attached (config.log.txt) -- it's big. :) also 'clang -v' nadda -- don't think it's installed -- WITHOUT_CLANG=true (/etc/make.conf) Thank you for your thoughtful reply, Allan. --Chris -- Allan Jude ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org echo $CC It seems it is trying to use clang, and you have disabled clang check your /etc/make.conf you might need to add CC=gcc to /etc/make.conf to make it work Warning: I have no idea what I am talking about, it is 2am at a BSD conference hacking lounge -- Allan Jude ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Looping during boot-up process in FreeBSD-11 current
Hi Mike, it looks like we are hitting the same problem. If we find a third person with the same issue we can fund a club. :) Interesting to note: 1) we both run FBSD on small netbooks which usually get equipped with crappy ^D^D^D^D^D^D^D cheap hardware. 2) yours seems to be an Intel-only box, mine is an AMD-only, so the problem is not there (I mean, it's not the graphic chip). 3) we both have an Atheros wifi, whose driver has been updated recently, maybe this is the issue? As of now I suspect the problem is not related to AHCI because if you remove it from the kernel you still end up in an enless loop in some other driver. Actually the latest device_attach loops forever. You might still get some output from previous device probes complaining, notably USB, especially if you plug something in, or AHCI --as we both report--. I would like to debug the running kernel from another machine, altought the suggestions I got so far (see thread about kernel debugging in this same mailing list) are not encouraging. I will keep you posted, in the meantime you can try and boot your pc from 271146, it works for me. BR, On Sun, 28 Sep 2014 11:53:05 -0400, Mike. wrote I'm starting to look at FreeBSD 11-current to see what's coming soon. I have an older notebook that I use for test environments for purposes such as this. Unfortunately, the notebook won't boot up from the install CD, there's a loop it cannot seem to get out of. Details are: - The install CD was made from this image: FreeBSD-11.0-CURRENT-i386-20140918-r271779-disc1 - The dmesg for the notebook is at the end of this message. The dmesg was captured with FreeBSD 10.0. In the dmesg, you can see the following lines: (aprobe0:ata1:0:1:0): ATAPI_IDENTIFY. ACB: a1 00 00 00 00 40 00 00 00 00 00 00 (aprobe0:ata1:0:1:0): CAM status: Command timeout (aprobe0:ata1:0:1:0): Error 5, Retry was blocked run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config (aprobe0:ata1:0:1:0): ATAPI_IDENTIFY. ACB: a1 00 00 00 00 40 00 00 00 00 00 00 (aprobe0:ata1:0:1:0): CAM status: Command timeout (aprobe0:ata1:0:1:0): Error 5, Retry was blocked which, while slowing down the boot process drastically, still allowed the boot process to run to successful completion. - When I try to boot using the FreeBSD 11-current install CD, that loop seems to go on ad infinitum, or at least for the 5 minutes until I gave up. I cannot post a dmesg from that boot-up because I never got to a prompt. However, I did take a couple of pictures of the offending screens. They are here: http://archive.mgm51.com/cache/fbsd-11-current-01.jpg http://archive.mgm51.com/cache/fbsd-11-current-02.jpg The first image shows the start of the looping, and the second shows the continuation. While this notebook is used only for testing, it is important to me in that aspect. How can I get around this looping issue? Please let me know if there's any additional info you need. Thanks. And now, the dmesg... Copyright (c) 1992-2014 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.0-RELEASE-p8 #1 r271323: Wed Sep 10 20:25:45 EDT 2014 r...@a31pf.245l.home:/usr/obj/usr/src/sys/GENERIC i386 FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 CPU: Intel(R) Pentium(R) 4 Mobile CPU 1.70GHz (1698.60-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf24 Family = 0xf Model = 0x2 Stepping = 4 Features=0x3febf9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR, PGE, MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT, TM real memory = 1073741824 (1024 MB) avail memory = 1029230592 (981 MB) kbd1 at kbdmux0 random: Software, Yarrow initialized acpi0: IBM TP-1G on motherboard acpi_ec0: Embedded Controller: GPE 0x1c, ECDT port 0x62,0x66 on acpi0 acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 3ff0 (3) failed cpu0: ACPI CPU on acpi0 attimer0: AT timer port 0x40-0x43 irq 0 on acpi0 Timecounter i8254 frequency 1193182 Hz quality 0 Event timer i8254 frequency 1193182 Hz quality 100 atrtc0: AT realtime clock port 0x70-0x71 irq 8 on acpi0 Event timer RTC frequency 32768 Hz quality 0 Timecounter ACPI-safe frequency 3579545 Hz quality 850 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 acpi_lid0: Control Method Lid Switch on acpi0 acpi_button0: Sleep Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Intel 82845 host to AGP bridge on hostb0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 vgapci0: VGA-compatible display port 0x3000-0x30ff mem 0xe800-0xefff,0xd010-0xd010 irq 11 at device 0.0 on pci1 vgapci0: Boot video device uhci0:
Re: Mesa-9: configure: error: C compiler cannot create executables
On 09/28/2014 18:11, Chris H wrote: On 09/28/2014 17:37, Chris H wrote: Greetings, A recent install of RELENG_9, followed by a build|install world|kernel. Returns the following error when attempting an make install of x11/xorg-minimal === Configuring for dri-9.1.7_5,2 configure: loading site script /usr/ports/Templates/config.site checking build system type... amd64-portbld-freebsd9.3 checking host system type... amd64-portbld-freebsd9.3 checking target system type... amd64-portbld-freebsd9.3 checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking whether build environment is sane... yes checking for a thread-safe mkdir -p... (cached) /bin/mkdir -p checking for gawk... (cached) /usr/bin/awk checking whether gmake sets $(MAKE)... yes checking whether gmake supports nested variables... yes checking for style of include used by gmake... GNU checking for gcc... clang checking whether the C compiler works... no configure: error: in `/usr/ports/graphics/dri/work/Mesa-9.1.7': configure: error: C compiler cannot create executables See `config.log' for more details === Script configure failed unexpectedly. Please report the problem to x...@freebsd.org [maintainer] and attach the /usr/ports/graphics/dri/work/Mesa-9.1.7/config.log including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. a /usr/local/sbin/pkg-static info -g -Ea). *** [do-configure] Error code 1 Any thoughts on how to overcome this issue? Relevant info: # svn info /usr/src Path: /usr/src Working Copy Root Path: /usr/src URL: svn://svn.freebsd.org/base/stable/9 Relative URL: ^/stable/9 Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 272203 Node Kind: directory Schedule: normal Last Changed Author: thomas Last Changed Rev: 272184 Last Changed Date: 2014-09-26 12:13:13 -0700 (Fri, 26 Sep 2014) svn info /usr/ports Path: /usr/ports Working Copy Root Path: /usr/ports URL: svn://svn.freebsd.org/ports/head Relative URL: ^/head Repository Root: svn://svn.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 369380 Node Kind: directory Schedule: normal Last Changed Author: mva Last Changed Rev: 369380 Last Changed Date: 2014-09-27 01:34:11 -0700 (Sat, 27 Sep 2014) FreeBSD demon 9.3-STABLE FreeBSD 9.3-STABLE #0 r272203: Sat Sep 27 15:49:55 PDT 2014 root@demon:/usr/obj/usr/src/sys/DEMON amd64 Thank you for all your time, and consideration. --Chris ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org What does config.log say? Please see attached (config.log.txt) -- it's big. :) also 'clang -v' nadda -- don't think it's installed -- WITHOUT_CLANG=true (/etc/make.conf) Thank you for your thoughtful reply, Allan. --Chris -- Allan Jude ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org echo $CC # echo $CC CC: Undefined variable It seems it is trying to use clang, and you have disabled clang check your /etc/make.conf I'm carrying over defines from a 9.2-STABLE box: WITHOUT_CLANG=true FAVORITE_COMPILER=gcc These worked famously on the 9.2. So I thought them safe here (9.3). you might need to add CC=gcc to /etc/make.conf to make it work Warning: I have no idea what I am talking about, it is 2am at a BSD conference hacking lounge LOL I wish you the best! :) Thank you for taking the time to reply, Allan. Especially under the circumstances! --Chris -- Allan Jude ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: What do you use for kernel debugging?
Hi Garrett, On Sun, 28 Sep 2014 13:38:24 -0700, Garrett Cooper wrote On Sep 28, 2014, at 0:34, José Pérez Arauzo f...@aoek.com wrote: Hello, I am trying to track down a (deadlock?) issue in CURRENT via DDB. The kernel does not complete hw probes on my Acer V5. I get stuck on apic_isr looping which leads nowhere. So I thought maybe things improve if I debug from another machine. What do you use for kernel debugging? According to the handbook kgdb over serial is a good option, do you agree? I'm on a netbook with no ethernet and no option for firewire: can I have a USB / nullmodem setup to work? I have no old-style uarts hardware anymore, as the handbook suggests... Any idea is welcome before I buy extra hw. I have a USB to serial showing up as /dev/cuaU0, do I need to grab another one and a nullmodem cable or there are better alternatives? Thank you. There was some discussion recently about this on an internal list. Unfortunately no, there isn’t a usable way, but there were some interesting viable methods that came up (which haven’t been implemented): ethernet/sound/xHCI. Your best bet, as others have noted, is to use boot -d, use WITNESS to spot locking issues, dtrace to isolate which section of code there are problems, and finally use one of the DEBUG options noted in /sys/conf/NOTES and /sys/your-architecture/conf/NOTES . Hope that helps! Well, it's not so encouraging but I'll work on it. Do you mean that we can get rid of chapter 10.5 of the handbook (On-Line Kernel Debugging Using Remote GDB)? Just to have it clear, when people develop or fix drivers in FreeBSD their only option is to use the above mentioned tools, as they have no access to a live, on-line kernel debugger?? It's disappointing, to say the least! I hope Dcons + 1394 works where it's applicable. BR, -- José Pérez Arauzo ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: What do you use for kernel debugging?
On Mon, 29 Sep 2014 02:31:25 +0200 José Pérez Arauzo f...@aoek.com wrote: I hope Dcons + 1394 works where it's applicable. BR, -- José Pérez Arauzo As a constant user of DCons+firewire, I can say it certainly works, and quite well at that. At least on PowerPC where firewire is everywhere. I only wish it were possible to use dcons+firewire even earlier in the boot (before the firewire device is probed), maybe initialize something in the loader. - Justin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: What do you use for kernel debugging?
Hi Benjamin, On Sun, 28 Sep 2014 15:54:36 -0400 (EDT), Benjamin Kaduk wrote On Sun, 28 Sep 2014, José Pérez Arauzo wrote: Hello, I am trying to track down a (deadlock?) issue in CURRENT via DDB. The kernel does not complete hw probes on my Acer V5. I get stuck on apic_isr looping which leads nowhere. So I thought maybe things improve if I debug from another machine. What do you use for kernel debugging? According to the handbook kgdb over serial is a good option, do you agree? I'm on a netbook with no ethernet and no option for firewire: can I have a USB / nullmodem setup to work? You cannot. Oh, what a shame. Why not? Is it because you need hardware probe to be over to use it? Today I bought a shining USB to USB thingy made by Hama, and guess what? It's not supported on FBDS, altought uplcom(4) reports support for Hama USB to RS232 brother. I have no old-style uarts hardware anymore, as the handbook suggests... Any idea is welcome before I buy extra hw. I have a USB to serial showing up as /dev/cuaU0, do I need to grab another one and a nullmodem cable or there are better alternatives? Thank you. I'm not sure that there are alternatives at all, unfortunately. You may be reduced to debugging-via-printf. Wow, bad news! :-| BR, -- José Pérez Arauzo ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Mesa-9: configure: error: C compiler cannot create executables
On 09/28/2014 18:11, Chris H wrote: On 09/28/2014 17:37, Chris H wrote: Greetings, A recent install of RELENG_9, followed by a build|install world|kernel. Returns the following error when attempting an make install of x11/xorg-minimal === Configuring for dri-9.1.7_5,2 configure: loading site script /usr/ports/Templates/config.site checking build system type... amd64-portbld-freebsd9.3 checking host system type... amd64-portbld-freebsd9.3 checking target system type... amd64-portbld-freebsd9.3 checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking whether build environment is sane... yes checking for a thread-safe mkdir -p... (cached) /bin/mkdir -p checking for gawk... (cached) /usr/bin/awk checking whether gmake sets $(MAKE)... yes checking whether gmake supports nested variables... yes checking for style of include used by gmake... GNU checking for gcc... clang checking whether the C compiler works... no configure: error: in `/usr/ports/graphics/dri/work/Mesa-9.1.7': configure: error: C compiler cannot create executables See `config.log' for more details === Script configure failed unexpectedly. Please report the problem to x...@freebsd.org [maintainer] and attach the /usr/ports/graphics/dri/work/Mesa-9.1.7/config.log including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. a /usr/local/sbin/pkg-static info -g -Ea). *** [do-configure] Error code 1 Any thoughts on how to overcome this issue? Relevant info: # svn info /usr/src Path: /usr/src Working Copy Root Path: /usr/src URL: svn://svn.freebsd.org/base/stable/9 Relative URL: ^/stable/9 Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 272203 Node Kind: directory Schedule: normal Last Changed Author: thomas Last Changed Rev: 272184 Last Changed Date: 2014-09-26 12:13:13 -0700 (Fri, 26 Sep 2014) svn info /usr/ports Path: /usr/ports Working Copy Root Path: /usr/ports URL: svn://svn.freebsd.org/ports/head Relative URL: ^/head Repository Root: svn://svn.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 369380 Node Kind: directory Schedule: normal Last Changed Author: mva Last Changed Rev: 369380 Last Changed Date: 2014-09-27 01:34:11 -0700 (Sat, 27 Sep 2014) FreeBSD demon 9.3-STABLE FreeBSD 9.3-STABLE #0 r272203: Sat Sep 27 15:49:55 PDT 2014 root@demon:/usr/obj/usr/src/sys/DEMON amd64 Thank you for all your time, and consideration. --Chris ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org What does config.log say? Please see attached (config.log.txt) -- it's big. :) also 'clang -v' nadda -- don't think it's installed -- WITHOUT_CLANG=true (/etc/make.conf) Thank you for your thoughtful reply, Allan. --Chris -- Allan Jude ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org echo $CC # echo $CC CC: Undefined variable It seems it is trying to use clang, and you have disabled clang check your /etc/make.conf I'm carrying over defines from a 9.2-STABLE box: WITHOUT_CLANG=true FAVORITE_COMPILER=gcc These worked famously on the 9.2. So I thought them safe here (9.3). you might need to add CC=gcc to /etc/make.conf to make it work Warning: I have no idea what I am talking about, it is 2am at a BSD conference hacking lounge LOL I wish you the best! :) Thank you for taking the time to reply, Allan. Especially under the circumstances! --Chris A trip to lang/gcc; make install clean. Also failed to help. I guess there isn't a compiler capable of creating executables available with RELENG_9? Is this some fascist move to eliminate (g)cc from FreeBSD. So that only clang/llvm work? ugh. :-| --Chris -- Allan Jude ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list
Re: What do you use for kernel debugging?
On Sep 28, 2014, at 17:35, Justin Hibbits chmeeed...@gmail.com wrote: On Mon, 29 Sep 2014 02:31:25 +0200 José Pérez Arauzo f...@aoek.com wrote: I hope Dcons + 1394 works where it's applicable. BR, -- José Pérez Arauzo As a constant user of DCons+firewire, I can say it certainly works, and quite well at that. At least on PowerPC where firewire is everywhere. I only wish it were possible to use dcons+firewire even earlier in the boot (before the firewire device is probed), maybe initialize something in the loader. It would be nice if both the FireWire and USB subsystems started up sooner. There are other issues (with USB for instance), where ukbd not being initialized before the mount root prompt can leave the system undebuggable. In the short term: can the SYSINIT priority be changed in the drivers to support this? It would be nice if there was a pluggable infrastructure for bootloader enabling of devices as debugger consoles that would make this possible. Thanks! -Garrett ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: What do you use for kernel debugging?
On Sep 28, 2014, at 17:51, José Pérez Arauzo f...@aoek.com wrote: Hi Benjamin, On Sun, 28 Sep 2014 15:54:36 -0400 (EDT), Benjamin Kaduk wrote On Sun, 28 Sep 2014, José Pérez Arauzo wrote: Hello, I am trying to track down a (deadlock?) issue in CURRENT via DDB. The kernel does not complete hw probes on my Acer V5. I get stuck on apic_isr looping which leads nowhere. So I thought maybe things improve if I debug from another machine. What do you use for kernel debugging? According to the handbook kgdb over serial is a good option, do you agree? I'm on a netbook with no ethernet and no option for firewire: can I have a USB / nullmodem setup to work? You cannot. Oh, what a shame. Why not? Is it because you need hardware probe to be over to use it? Today I bought a shining USB to USB thingy made by Hama, and guess what? It's not supported on FBDS, altought uplcom(4) reports support for Hama USB to RS232 brother. The bootloader doesn't support USB debugging and I'm pretty sure the devices don't support local/remote debugging :(.. I'll do some poking around. I'll talk to some SMEs and see if I can write up a TODO list for a wiki page. Cheers! ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: What do you use for kernel debugging?
On Sep 28, 2014, at 17:31, José Pérez Arauzo f...@aoek.com wrote: Hi Garrett, On Sun, 28 Sep 2014 13:38:24 -0700, Garrett Cooper wrote On Sep 28, 2014, at 0:34, José Pérez Arauzo f...@aoek.com wrote: Hello, I am trying to track down a (deadlock?) issue in CURRENT via DDB. The kernel does not complete hw probes on my Acer V5. I get stuck on apic_isr looping which leads nowhere. So I thought maybe things improve if I debug from another machine. What do you use for kernel debugging? According to the handbook kgdb over serial is a good option, do you agree? I'm on a netbook with no ethernet and no option for firewire: can I have a USB / nullmodem setup to work? I have no old-style uarts hardware anymore, as the handbook suggests... Any idea is welcome before I buy extra hw. I have a USB to serial showing up as /dev/cuaU0, do I need to grab another one and a nullmodem cable or there are better alternatives? Thank you. There was some discussion recently about this on an internal list. Unfortunately no, there isn’t a usable way, but there were some interesting viable methods that came up (which haven’t been implemented): ethernet/sound/xHCI. Your best bet, as others have noted, is to use boot -d, use WITNESS to spot locking issues, dtrace to isolate which section of code there are problems, and finally use one of the DEBUG options noted in /sys/conf/NOTES and /sys/your-architecture/conf/NOTES . Hope that helps! Well, it's not so encouraging but I'll work on it. Do you mean that we can get rid of chapter 10.5 of the handbook (On-Line Kernel Debugging Using Remote GDB)? No. It still works quite well with serial consoles (both physical and virtual uarts, i.e. IPMI). Just to have it clear, when people develop or fix drivers in FreeBSD their only option is to use the above mentioned tools, as they have no access to a live, on-line kernel debugger?? It's disappointing, to say the least! There are other things that people use, but they're a bit expensive. I'll have to look up I hope Dcons + 1394 works where it's applicable. Yes, it should work as a debug console if the system has been booted up. When I was debugging getting ACPI to work on my netbook, here were some other things I did to get the system up and going: - Built a stripped down kernel that just contains the essential bits (CPU, filesystem, storage). - built one kernel with debug bits and one with release bits (titled them differently of course). - built networking and other components as klds and loaded them at boot. This gave me a quick turnaround time when figuring out what was broken suspend/resume wise. It might help you isolate which drivers or subsystems are causing boot issues as well (at least netbook system boot is relatively quick compared to the other systems I boot off of with gobs of ram and storage drives...). HTH! -Garrett ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Mesa-9: configure: error: C compiler cannot create executables
On 09/28/2014 18:11, Chris H wrote: On 09/28/2014 17:37, Chris H wrote: Greetings, A recent install of RELENG_9, followed by a build|install world|kernel. Returns the following error when attempting an make install of x11/xorg-minimal === Configuring for dri-9.1.7_5,2 configure: loading site script /usr/ports/Templates/config.site checking build system type... amd64-portbld-freebsd9.3 checking host system type... amd64-portbld-freebsd9.3 checking target system type... amd64-portbld-freebsd9.3 checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking whether build environment is sane... yes checking for a thread-safe mkdir -p... (cached) /bin/mkdir -p checking for gawk... (cached) /usr/bin/awk checking whether gmake sets $(MAKE)... yes checking whether gmake supports nested variables... yes checking for style of include used by gmake... GNU checking for gcc... clang checking whether the C compiler works... no configure: error: in `/usr/ports/graphics/dri/work/Mesa-9.1.7': configure: error: C compiler cannot create executables See `config.log' for more details === Script configure failed unexpectedly. Please report the problem to x...@freebsd.org [maintainer] and attach the /usr/ports/graphics/dri/work/Mesa-9.1.7/config.log including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. a /usr/local/sbin/pkg-static info -g -Ea). *** [do-configure] Error code 1 Any thoughts on how to overcome this issue? Relevant info: # svn info /usr/src Path: /usr/src Working Copy Root Path: /usr/src URL: svn://svn.freebsd.org/base/stable/9 Relative URL: ^/stable/9 Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 272203 Node Kind: directory Schedule: normal Last Changed Author: thomas Last Changed Rev: 272184 Last Changed Date: 2014-09-26 12:13:13 -0700 (Fri, 26 Sep 2014) svn info /usr/ports Path: /usr/ports Working Copy Root Path: /usr/ports URL: svn://svn.freebsd.org/ports/head Relative URL: ^/head Repository Root: svn://svn.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 369380 Node Kind: directory Schedule: normal Last Changed Author: mva Last Changed Rev: 369380 Last Changed Date: 2014-09-27 01:34:11 -0700 (Sat, 27 Sep 2014) FreeBSD demon 9.3-STABLE FreeBSD 9.3-STABLE #0 r272203: Sat Sep 27 15:49:55 PDT 2014 root@demon:/usr/obj/usr/src/sys/DEMON amd64 Thank you for all your time, and consideration. --Chris ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org What does config.log say? Please see attached (config.log.txt) -- it's big. :) also 'clang -v' nadda -- don't think it's installed -- WITHOUT_CLANG=true (/etc/make.conf) Thank you for your thoughtful reply, Allan. --Chris -- Allan Jude ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org echo $CC It seems it is trying to use clang, and you have disabled clang check your /etc/make.conf I'm carrying over defines from a 9.2-STABLE box: WITHOUT_CLANG=true FAVORITE_COMPILER=gcc These worked famously on the 9.2. So I thought them safe here (9.3). you might need to add CC=gcc to /etc/make.conf to make it work # echo $CC CC: Undefined variable Warning: I have no idea what I am talking about, it is 2am at a BSD conference hacking lounge LOL I wish you the best! :) Thank you for taking the time to reply, Allan. Especially under the circumstances! --Chris -- Allan Jude ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Mesa-9: configure: error: C compiler cannot create executables
On 09/28/2014 18:11, Chris H wrote:
On 09/28/2014 17:37, Chris H wrote:
Greetings,
A recent install of RELENG_9, followed by a build|install world|kernel.
Returns the following error when attempting an make install of
x11/xorg-minimal
=== Configuring for dri-9.1.7_5,2
configure: loading site script /usr/ports/Templates/config.site
checking build system type... amd64-portbld-freebsd9.3
checking host system type... amd64-portbld-freebsd9.3
checking target system type... amd64-portbld-freebsd9.3
checking for a BSD-compatible install... /usr/bin/install -c -o root -g
wheel
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... (cached) /bin/mkdir -p
checking for gawk... (cached) /usr/bin/awk
checking whether gmake sets $(MAKE)... yes
checking whether gmake supports nested variables... yes
checking for style of include used by gmake... GNU
checking for gcc... clang
checking whether the C compiler works... no
configure: error: in `/usr/ports/graphics/dri/work/Mesa-9.1.7':
configure: error: C compiler cannot create executables
See `config.log' for more details
=== Script configure failed unexpectedly.
Please report the problem to x...@freebsd.org [maintainer] and attach the
/usr/ports/graphics/dri/work/Mesa-9.1.7/config.log including the
output of
the failure of your make command. Also, it might be a good idea to
provide
an overview of all packages installed on your system (e.g. a
/usr/local/sbin/pkg-static info -g -Ea).
*** [do-configure] Error code 1
Any thoughts on how to overcome this issue?
Relevant info:
# svn info /usr/src
Path: /usr/src
Working Copy Root Path: /usr/src
URL: svn://svn.freebsd.org/base/stable/9
Relative URL: ^/stable/9
Repository Root: svn://svn.freebsd.org/base
Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Revision: 272203
Node Kind: directory
Schedule: normal
Last Changed Author: thomas
Last Changed Rev: 272184
Last Changed Date: 2014-09-26 12:13:13 -0700 (Fri, 26 Sep 2014)
svn info /usr/ports
Path: /usr/ports
Working Copy Root Path: /usr/ports
URL: svn://svn.freebsd.org/ports/head
Relative URL: ^/head
Repository Root: svn://svn.freebsd.org/ports
Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
Revision: 369380
Node Kind: directory
Schedule: normal
Last Changed Author: mva
Last Changed Rev: 369380
Last Changed Date: 2014-09-27 01:34:11 -0700 (Sat, 27 Sep 2014)
FreeBSD demon 9.3-STABLE FreeBSD 9.3-STABLE #0 r272203: Sat Sep 27
15:49:55 PDT 2014
root@demon:/usr/obj/usr/src/sys/DEMON amd64
Thank you for all your time, and consideration.
--Chris
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
freebsd-current-unsubscr...@freebsd.org
What does config.log say?
Please see attached (config.log.txt) -- it's big. :)
also 'clang -v'
nadda -- don't think it's installed -- WITHOUT_CLANG=true (/etc/make.conf)
Thank you for your thoughtful reply, Allan.
--Chris
--
Allan Jude
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
echo $CC
# echo $CC
CC: Undefined variable
It seems it is trying to use clang, and you have disabled clang
check your /etc/make.conf
I'm carrying over defines from a 9.2-STABLE box:
WITHOUT_CLANG=true
FAVORITE_COMPILER=gcc
These worked famously on the 9.2. So I thought them safe here (9.3).
you might need to add CC=gcc to /etc/make.conf to make it work
Warning: I have no idea what I am talking about, it is 2am at a BSD
conference hacking lounge
LOL I wish you the best! :)
Thank you for taking the time to reply, Allan. Especially under the
circumstances!
--Chris
A trip to lang/gcc; make install clean. Also failed to help.
I guess there isn't a compiler capable of creating executables
available with RELENG_9? Is this some fascist move to eliminate
(g)cc from FreeBSD. So that only clang/llvm work?
ugh. :-|
Well. A quick look at graphics/dri/Makefile, reveals it is
a diabolical plot to insist gcc goes away. :(
I simply commented the conditional, and added GCC to suit my needs. :)
# gcc from base can't handle some code in mesa 9.1+
# We only care for 9.x and 8.x, not for old pre-clang default current.
# This is for 0b binary which gcc 4.3+ understands and is in the i965
driver.
.if defined(WITH_NEW_XORG)
. if (${OSVERSION} = 901500 ${OSVERSION} 100) \
${ARCH} == amd64
USE_GCC=yes
#CC=clang
#CXX=clang++
#CPP=clang-cpp
. elif ${OSVERSION} 901500
USE_GCC=yes
