Re: GPT on amd64 and boot managers
On 05/27/10 13:33, Andriy Gapon wrote: on 27/05/2010 13:55 Alban Hertroys said the following: I can boot FreeBSD just fine off GPT, but I have to select in the BIOS whether I want to boot FreeBSD or Windows (by means of changing the boot sequence). A working boot manager would be so much more convenient for that. Right. OTOH I have standard GPT installation (pmbr + gptzfsboot) and during boot I am presented with a choice which _hard disk_ to boot from. I didn't do anything special for that. Not exactly a boot manager, but OK for me. I'd be quite happy to have something like that, do you have any idea what's doing that for you? I suspect it is your BIOS, as I don't get that choice and AFAIK I also have a standard GPT installation - I literally followed the examples in man gpart up to the point where freebsd-ufs partitions are added. This is my partition layout: dalroi:bommel gpart show ada0 = 34 625142381 ada0 GPT (298G) 34128 1 freebsd-boot (64K) 1622097152 2 freebsd-ufs (1.0G) 2097314 16777216 3 freebsd-swap (8.0G) 188745301024000 4 freebsd-ufs (500M) 198985302097152 5 freebsd-ufs (1.0G) 21995682 41943040 6 freebsd-ufs (20G) 63938722 561203693 7 freebsd-ufs (268G) !DSPAM:930,4bffa1c910415538290380! ___ 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
hid_get_item: Number of items truncated to 255
Hello, I see this message a couple of times in my dmesg every time I boot and I'm wondering from which device these messages originate and whether they might be harmful in some way? They don't seem to cause any trouble, but it's probably better if they weren't there. Below are the relevant section of my dmesg and the output of usbconfig: ugen5.4: Logitech at usbus5 ums0: Logitech Trackball, class 0/0, rev 1.10/2.20, addr 4 on usbus5 ums0: 3 buttons and [XYZ] coordinates ID=0 Root mount waiting for: usbus5 Root mount waiting for: usbus5 ugen5.5: vendor 0x05ac at usbus5 hid_get_item: Number of items truncated to 255 hid_get_item: Number of items truncated to 255 hid_get_item: Number of items truncated to 255 hid_get_item: Number of items truncated to 255 hid_get_item: Number of items truncated to 255 hid_get_item: Number of items truncated to 255 uhid1: vendor 0x05ac product 0x9223, class 0/0, rev 1.10/1.14, addr 5 on usbus5 hid_get_item: Number of items truncated to 255 hid_get_item: Number of items truncated to 255 hid_get_item: Number of items truncated to 255 ugen5.6: Microsoft at usbus5 ukbd0: Microsoft Natural Ergonomic Keyboard 4000, class 0/0, rev 2.00/1.73, addr 6 on usbus5 kbd2 at ukbd0 uhid2: Microsoft Natural Ergonomic Keyboard 4000, class 0/0, rev 2.00/1.73, addr 6 on usbus5 ugen0.1: OHCI root HUB ATI at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen1.1: OHCI root HUB ATI at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen2.1: OHCI root HUB ATI at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen3.1: OHCI root HUB ATI at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen4.1: OHCI root HUB ATI at usbus4, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen5.1: EHCI root HUB ATI at usbus5, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen1.2: Saitek R220 Saitek at usbus1, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen5.2: product 0x6560 vendor 0x04b4 at usbus5, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen5.3: product 0x9131 vendor 0x05ac at usbus5, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen5.4: Trackball Logitech at usbus5, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen5.5: product 0x9223 vendor 0x05ac at usbus5, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen5.6: Natural Ergonomic Keyboard 4000 Microsoft at usbus5, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON I found that vendor 0x05ac is Apple Computer Inc and therefore I suspect the device that's causing these errors could be the brightness control in my Apple Cinema display. The first of below devices is probably the USB-hub in the display and the second the brightness control, but it could be the other way around. ugen5.3: product 0x9131 vendor 0x05ac at usbus5, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen5.5: product 0x9223 vendor 0x05ac at usbus5, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON The other unrecognised device, in case someone wants to add it somewhere: ugen5.2: product 0x6560 vendor 0x04b4 at usbus5, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE This is a Belkin n52te game-controller (http://www.belkin.com/IWCatProductPage.process?Product_Id=390404) !DSPAM:930,4bffa90810411104319959! ___ 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: GPT on amd64 and boot managers
on 28/05/2010 13:58 Alban Hertroys said the following: On 05/27/10 13:33, Andriy Gapon wrote: on 27/05/2010 13:55 Alban Hertroys said the following: I can boot FreeBSD just fine off GPT, but I have to select in the BIOS whether I want to boot FreeBSD or Windows (by means of changing the boot sequence). A working boot manager would be so much more convenient for that. Right. OTOH I have standard GPT installation (pmbr + gptzfsboot) and during boot I am presented with a choice which _hard disk_ to boot from. I didn't do anything special for that. Not exactly a boot manager, but OK for me. I'd be quite happy to have something like that, do you have any idea what's doing that for you? I suspect it is your BIOS, as I don't get that choice and AFAIK I also have a standard GPT installation - I literally followed the examples in man gpart up to the point where freebsd-ufs partitions are added. Looks like I was confused - this was on a system where ZFS was installed in a slice and boot0 was used as MBR. Sorry for misleading you. I wonder if it's possible to cram both disk selection support and GPT support in 512 bytes by throwing out something... Or perhaps add boot manager functions to gptboot, that sounds easier. -- Andriy Gapon ___ 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
clangBSD build error on r208621
Hi rdivacky. I svn updated latest clangBSD: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - $ svn info Path: . URL: file:///home/nork/.svk/local/freebsd/base/projects/clangbsd Repository Root: file:///home/nork/.svk/local Repository UUID: c867b0bc-624e-df11-a429-00248c1b55b2 Revision: 208621 Node Kind: directory Schedule: normal Last Changed Author: rdivacky Last Changed Rev: 208621 Last Changed Date: 2010-05-29 00:45:17 +0900 (Sat, 29 May 2010) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - But I got following error: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -- stage 4.2: building libraries -- cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=amd64 MACHINE=amd64 CPUTYPE= GROFF_BIN_PATH=/usr/obj/usr/src/tmp/legacy/usr/bin GROFF_FONT_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/groff_font GROFF_TMAC_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/tmac _SHLIBDIRPREFIX=/usr/obj/usr/src/tmp VERSION=FreeBSD 9.0-CURRENT amd64 900010 INSTALL=sh /usr/src/tools/install.sh PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin CC=clang -isysroot /usr/obj/usr/src/tmp -B/usr/obj/usr/src/tmp/usr/lib/ -L/usr/obj/usr/src/tmp/usr/lib/ CXX=clang++ -isysroot /usr/obj/usr/src/tmp -B/usr/obj/usr/src/tmp/usr/lib/ -L/usr/obj/usr/src/tmp/usr/lib/ NO_CTF=1 make -f Makefile.inc1 DESTDIR=/usr/obj/usr/src/tmp -DNO_FSCHG -DWITHOUT_HTML -DWITHOUT_INFO -DNO_LINT -DWITHOUT_MAN -DWITHOUT_ PROFILE libraries cd /usr/src; make -f Makefile.inc1 _prereq_libs; make -f Makefile.inc1 _startup_libs; make -f Makefile.inc1 _prebuild_libs; make -f Makefile.inc1 _generic_libs; === gnu/lib/libssp/libssp_nonshared (obj,depend,all,install) rm -f .depend CC='clang -isysroot /usr/obj/usr/src/tmp -B/usr/obj/usr/src/tmp/usr/lib/ -L/usr/obj/usr/src/tmp/usr/lib/' mkdep -f .depend -a-DHAVE_CONFIG_H -I/usr/src/gnu/lib/libssp/libssp_nonshared/.. -I/usr/src/gnu/lib/libssp/libssp_nonshared/../../../../contrib/gcclibs/libssp -I/usr/src/gnu/lib/libssp/libssp_nonshared/../../../../contrib/gcclibs/include -DPIC /usr/src/gnu/lib/libssp/libssp_nonshared/../../../../contrib/gcclibs/libssp/ssp-local.c error: unknown argument: '-ferror-limit' mkdep: compile failed *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Do you have any idea? Of cause I set following environment: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - $ cat /etc/src.conf NO_WERROR= WERROR= - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -- Norikatsu Shigemura n...@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
wpi not working on today's current (r208626)
I am trying to update -current in order to try kib's patch for the nvidia driver, and the wpi driver won't establish a connection. I'm using r207134 right now without any problems, but that's a long time back to try and do a binary search. I don't see any changes to wpi or wpa_supplicant between then and now, anyone have an idea of where to look? My WAP is using WPA2 with AES if that's any help. Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.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
wpa_supplicant (Was: Re: wpi not working on today's current (r208626))
On 05/28/10 13:18, Doug Barton wrote: I am trying to update -current in order to try kib's patch for the nvidia driver, and the wpi driver won't establish a connection. I'm using r207134 right now without any problems, but that's a long time back to try and do a binary search. I don't see any changes to wpi or wpa_supplicant between then and now, anyone have an idea of where to look? My WAP is using WPA2 with AES if that's any help. Correction, the problem seems to be more generally with wpa_supplicant. I tried with the new kernel and my ath PCMCIA card (AR5416 mac 13.10 RF2133 phy 8.1) and it doesn't work with the latest kernel either. However, the same card is working fine with the older kernel (I'm using it now). Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.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: wpa_supplicant (Was: Re: wpi not working on today's current (r208626))
On 05/28/10 13:18, Doug Barton wrote: I am trying to update -current in order to try kib's patch for the nvidia driver, and the wpi driver won't establish a connection. I'm using r207134 right now without any problems, but that's a long time back to try and do a binary search. I don't see any changes to wpi or wpa_supplicant between then and now, anyone have an idea of where to look? My WAP is using WPA2 with AES if that's any help. Correction, the problem seems to be more generally with wpa_supplicant. I tried with the new kernel and my ath PCMCIA card (AR5416 mac 13.10 RF2133 phy 8.1) and it doesn't work with the latest kernel either. However, the same card is working fine with the older kernel (I'm using it now). I can't see any problems when using WPA2 with AES on r208606 i386 with uath(4). I'm updating this machine to r208630 tonight, and if I encounter problems with the later revision, I'll let you know. Are you saying that you experienced problems when trying to use a r207134 base with a r208626 kernel? If that's the case, I would recommend updating the base to the same revision as the kernel, and then retesting. b. ___ 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: wpa_supplicant (Was: Re: wpi not working on today's current (r208626))
On 5/28/2010 4:50 PM, b. f. wrote: I can't see any problems when using WPA2 with AES on r208606 i386 with uath(4). I'm updating this machine to r208630 tonight, and if I encounter problems with the later revision, I'll let you know. Ok, thanks. Are you saying that you experienced problems when trying to use a r207134 base with a r208626 kernel? If that's the case, I would recommend updating the base to the same revision as the kernel, and then retesting. Yes, that's what I'm doing I actually tried running the newly built wpa_supplicant but that didn't work. I'm kind of hesitant to do the full upgrade since I'm having kernel problems with the nvidia driver, but if I'm sure wpa_supplicant will work then I suppose I can bite the bullet. Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.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: wpa_supplicant (Was: Re: wpi not working on today's current (r208626))
On 5/28/10, Doug Barton do...@freebsd.org wrote: On 5/28/2010 4:50 PM, b. f. wrote: I can't see any problems when using WPA2 with AES on r208606 i386 with uath(4). I'm updating this machine to r208630 tonight, and if I encounter problems with the later revision, I'll let you know. Ok, thanks. Are you saying that you experienced problems when trying to use a r207134 base with a r208626 kernel? If that's the case, I would recommend updating the base to the same revision as the kernel, and then retesting. Yes, that's what I'm doing I actually tried running the newly built wpa_supplicant but that didn't work. I'm kind of hesitant to do the full upgrade since I'm having kernel problems with the nvidia driver, but if I'm sure wpa_supplicant will work then I suppose I can bite the bullet. It appears that something is wrong. My wireless stick no longer associates with the network with r208630. I'll do some tinkering. b. ___ 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
