Re: Huawei E3272 tester needed
On 17.09.2014 09:02, Milan Obuch wrote: On Tue, 16 Sep 2014 22:43:34 +0200 Maciej Milewski m...@dat.pl wrote: On 16.09.2014 22:18, Milan Obuch wrote: Your device has different idProduct than this added in patch. It might be caused by different configuration of the device/different provider who sells devices. I know that some devices might show up as HiLink mode(cdce) or serial mode(u3g). And this might be changed by flashing different firmware or sometimes by using usb_modeswitch(under linux not sure if it works under freebsd). Example is here: https://forum.pfsense.org/index.php?topic=48780.20;wap2 Thanks, that's working, verbatim: usb_modeswitch -v 12d1 -p 1f01 -V 012d1 -P 014db -M 55534243123456780a11062100 -W After that, if_cdce and uether kernel modules are automatically loaded and dhclient ue0 successfully acquires IP address. And it is working in 9.2-STABLE, 10.0-STABLE systems I tested with no modification to sources, so this is a good solution for me. Regards, Milan Glad to hear that helped, can you follow Hans suggestion for trying already defined quirks? It's posiible that there is one working. -- Pozdrawiam, Maciej Milewski ___ 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: Huawei E3272 tester needed
On 16.09.2014 16:52, Milan Obuch wrote: On Tue, 16 Sep 2014 09:40:45 +0200 Nick Hibma n...@van-laarhoven.org wrote: Hi, Is there someone who is able to test support for the Huawei E3272 card with CURRENT after 269584? I have not been able to confirm that it works. Thanks in advance. Nick Hi, I did fresh svn update, rebuilt world+kernel, but it does not work for me... From log: ugen1.3: HUAWEI Technology at usbus1 umass1: HUAWEI Technology HUAWEI Mobile, class 0/0, rev 2.00/1.02, addr 3 on usbus1 cd2 at umass-sim1 bus 1 scbus7 target 0 lun 0 cd2: HUAWEI Mass Storage 2.31 Removable CD-ROM SCSI-2 device cd2: 40.000MB/s transfers cd2: cd present [65536 x 2048 byte records] cd2: quirks=0x1010_BYTE_ONLY (cd2:umass-sim1:1:0:0): READ(10). CDB: 28 00 00 00 ff ff 00 00 01 00 (cd2:umass-sim1:1:0:0): CAM status: SCSI Status Error (cd2:umass-sim1:1:0:0): SCSI status: Check Condition (cd2:umass-sim1:1:0:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error) (cd2:umass-sim1:1:0:0): Info: 0x (cd2:umass-sim1:1:0:0): Error 5, Unretryable error (cd2:umass-sim1:1:0:0): cddone: got error 0x5 back ugen1.3: HUAWEI Technology at usbus1 (disconnected) umass1: at uhub1, port 6, addr 3 (disconnected) cd2 at umass-sim1 bus 1 scbus7 target 0 lun 0 cd2: HUAWEI Mass Storage 2.31 detached (cd2:umass-sim1:1:0:0): Periph destroyed I tried attach/detach device beore and after loading u3g (just in case...) and if_cdce kernel modules, but I saw no changes. From 'usbconfig dump_device_desc': ugen1.3: HUAWEI Mobile HUAWEI Technology at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x12d1 idProduct = 0x1f01 bcdDevice = 0x0102 iManufacturer = 0x0002 HUAWEI Technology iProduct = 0x0001 HUAWEI Mobile iSerialNumber = 0x0004 bNumConfigurations = 0x0001 If anything else is important, let me know. Regards, Milan Try ejecting first this cd2 drive by cdcontrol eject or camcontrol eject. I had such scenario with other usb device and that helped. -- Pozdrawiam, Maciej Milewski ___ 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: Huawei E3272 tester needed
On 16.09.2014 22:18, Milan Obuch wrote: On Tue, 16 Sep 2014 21:55:50 +0200 Maciej Milewski m...@dat.pl wrote: On 16.09.2014 16:52, Milan Obuch wrote: On Tue, 16 Sep 2014 09:40:45 +0200 Nick Hibma n...@van-laarhoven.org wrote: Hi, Is there someone who is able to test support for the Huawei E3272 card with CURRENT after 269584? I have not been able to confirm that it works. Thanks in advance. Nick Hi, I did fresh svn update, rebuilt world+kernel, but it does not work for me... [ snip ] I tried attach/detach device beore and after loading u3g (just in case...) and if_cdce kernel modules, but I saw no changes. From 'usbconfig dump_device_desc': ugen1.3: HUAWEI Mobile HUAWEI Technology at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x12d1 idProduct = 0x1f01 bcdDevice = 0x0102 iManufacturer = 0x0002 HUAWEI Technology iProduct = 0x0001 HUAWEI Mobile iSerialNumber = 0x0004 bNumConfigurations = 0x0001 If anything else is important, let me know. Regards, Milan Try ejecting first this cd2 drive by cdcontrol eject or camcontrol eject. I had such scenario with other usb device and that helped. Nothing. # camcontrol eject cd2 Unit stopped successfully, Media ejected That's all. No new device created, neither in /dev directory nor in ifconfig listing. Nothing in console log. From 'usbconfig dump_all_config_desc': ugen1.3: HUAWEI Mobile HUAWEI Technology at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA) Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0020 bNumInterfaces = 0x0001 bConfigurationValue = 0x0001 iConfiguration = 0x0003 Huawei Configuration bmAttributes = 0x0080 bMaxPower = 0x00fa Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x bAlternateSetting = 0x bNumEndpoints = 0x0002 bInterfaceClass = 0x0008 bInterfaceSubClass = 0x0006 bInterfaceProtocol = 0x0050 iInterface = 0x no string Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0001 OUT bmAttributes = 0x0002 BULK wMaxPacketSize = 0x0200 bInterval = 0x bRefresh = 0x bSynchAddress = 0x Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0081 IN bmAttributes = 0x0002 BULK wMaxPacketSize = 0x0200 bInterval = 0x bRefresh = 0x bSynchAddress = 0x Regards, Milan Your device has different idProduct than this added in patch. It might be caused by different configuration of the device/different provider who sells devices. I know that some devices might show up as HiLink mode(cdce) or serial mode(u3g). And this might be changed by flashing different firmware or sometimes by using usb_modeswitch(under linux not sure if it works under freebsd). Example is here: https://forum.pfsense.org/index.php?topic=48780.20;wap2 -- Pozdrawiam, Maciej Milewski ___ 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: USB 2.0 webcam in virtualbox on CURRENT not working!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 16.07.2014 13:28, O. Hartmann wrote: I desperately need to have a SKYPE based chat with an offshore department. Since Skype is not a native port, I try to use a virtual box running Windows 7. And here the nightmare begins. Skype works in the VBox, but audio only. I have two WebCAMs here, a brand new Logitech C270 and a older Medion MD86511. The latter one can be seen in the device list of Windows 7 within the VBox, but can not be activated. More frustrating, the Logitech C270, doesn't work, it is not even seen by the VBox. I tested the cam on another Windows 7 system of a colleague and it works. FreeBSD does also see this USB Cam, but why is the device hidden for the VBox? What do you mean by saying see? usbconfig on freebsd lists it as ugen device? Is it attached to vbox machine by some filter? Have you tried VBoxManage usbfilter add? I'm currently using some kind of software security jingle device this way: VBoxManage usbfilter add 1 --target VMachineName --name USBKey --vendorid 0x --productid 0x But I haven't used any webcam this way. In the configuration, I have the ability to enable/disable USB 2.0 subsystem. Enabled, VBox rejects to start on all FBSD around (9.3-PRE, 11-CURRENT). What is that? Is VBox not capable of using USB 2.0 devices in conjunction with FreeBSD? How to solve this? Is there a Skype 6 client for FreeBSD? Thanks in advance, please CC me, Oliver - -- Pozdrawiam, Maciej Milewski -BEGIN PGP SIGNATURE- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlPGZK0ACgkQPQ1pa2ELkNklvwCfeg0LpjvLZxsJW3J4K3POMfPt z5gAnjnkFuUgJwF0xQRmoCOZE67tYcyq =6krQ -END PGP SIGNATURE- ___ 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: 10.0-BETA1 i386 on VirtualBox
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05.11.2013 08:02, Konstantin Belousov wrote: On Mon, Nov 04, 2013 at 08:53:41PM +0400, Gleb Smirnoff wrote: On Mon, Nov 04, 2013 at 06:38:25PM +0200, Konstantin Belousov wrote: K Also please show me the CPU features banner from the boot in the VB, K like this: I have already collected them all. See attaches. Legend: dmesg.bbpwd_mkdb crashes during install dmesg.milu.pngpwd_mkdb crashes during install dmesg.thinkinstallation succeeds, but world build crashes instantly dmesg.ruall works dmesg.morannonall works First, all reported instances have ata attachment for the ada0, except of milu (possibly). So this means that kernel does transient remapping, and very different code path is executed comparing with what I thought initially. The path is simpler than the pure unmapped i/o. I wasn't able to finish installation in both cases: nor IDE nor SATA emulated VBox disk. Second, I use QEMU with the ata0 attachment for the disks regularly, and I do not have an issue. I also did not see a report from the real h/w. Third point is that all reports are i386. Is there anybody with amd64, vbox, ata and the same corruption hiddent by disabling unmapped i/o ? I'll try amd64 when BETA3 iso arrives to my HDD. In what way the non-working images were installed ? Is it possible to produce the problematic installs by doing it one way, and non-problematic by another ? In my case it was just idiot-proof: enter,enter,enter (except installing ports/src/games), enter password, enter password again...Error...Start over installation. Every case of installation was like that. I tried turning off SU+J, SU. Didn't helped. - -- Pozdrawiam, Maciej Milewski -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJ4wKMACgkQPQ1pa2ELkNnA2wCfY4sgXlI09CDDCS6ZrenAzra5 hQcAoIXQmlhunbgF539JwVYMUiw1Kb08 =b5Pq -END PGP SIGNATURE- ___ 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: 10.0-BETA1 i386 on VirtualBox
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05.11.2013 09:15, Boris Bobrov wrote: Disabling VT-x in VB helps too. I can confirm that. - --hwvirtex off and things are working again. - -- Pozdrawiam, Maciej Milewski -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJ4wakACgkQPQ1pa2ELkNk0mwCeOh4R3Q/yymyqkAxfui8bRIIR UucAniyLb0mnsdkNu39W+stjdtvxrvfT =cXrv -END PGP SIGNATURE- ___ 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: 10.0-BETA1 i386 on VirtualBox
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05.11.2013 08:02, Konstantin Belousov wrote: Third point is that all reports are i386. Is there anybody with amd64, vbox, ata and the same corruption hiddent by disabling unmapped i/o ? In what way the non-working images were installed ? Is it possible to produce the problematic installs by doing it one way, and non-problematic by another ? FreeBSD-10.0-BETA3-amd64-disc1.iso have no such problems - it works and installs fine(after enabling ioapic, which was disabled by default in my case). The only thing which I've changed was --ioapic on and medium for VBox. Rest was the same in both cases. I suspect no big differences between BETA2 and BETA3. - -- Pozdrawiam, Maciej Milewski -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJ4yq4ACgkQPQ1pa2ELkNmJRwCffkycWLFe2LMcNE/NBrTCMCcm IfkAn0riY03NO9e+h6bKeHFRLkRfJ/e8 =3PEf -END PGP SIGNATURE- ___ 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: 10.0-BETA1 i386 on VirtualBox
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03.11.2013 15:41, Konstantin Belousov wrote: On Sun, Nov 03, 2013 at 05:46:01PM +0400, Gleb Smirnoff wrote: Maciej, Boris, On Sun, Nov 03, 2013 at 04:29:11PM +0400, Boris Bobrov wrote: B I traced this down to r248521: B svn log -r248521 B --- B - r248521 | kib | 2013-03-19 16:08:15 +0100 (Tue, 19 Mar 2013) | 5 B lines B B UFS support of the unmapped i/o for the user data buffers. B B Sponsored by: The FreeBSD Foundation B Tested by: pho, scottl, jhb, bf B B --- B - B B The last working revision is 248520. B B Yes, I confirm that. Thanks for you help! Can you please now try unpatched vanilla 10.0-BETA2 iso file and when it boots set in loader (before kernel): OK set vfs.unmapped_buf_allowed=0 OK boot Show what disk driver is used, also show the output of hw.ncpu, both from the guest. Konstantin, do you need any other/more info from guest host? Other than hw.ncpu=1 Disk is ada0 at ahcich0 bus 0 scbus2 target 0 lun 0 and second test instance is ada0 at ata0 bus 0 scbus0 target 0 lun 0 Is Gleb's loader hint the final right solution for this problem? - -- Pozdrawiam, Maciej Milewski -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJ3hUEACgkQPQ1pa2ELkNl26wCdG0wsFWMxu+iN4Xig/I4lQ5pv i+gAn1OAVEvf0vXAZu4PRmr9+oEkW+jA =9+kM -END PGP SIGNATURE- ___ 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: 10.0-BETA1 i386 on VirtualBox
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02.11.2013 08:06, Boris Bobrov wrote: В сообщении от Thursday 31 of October 2013 17:54:32 Gleb написал: On Thu, Oct 31, 2013 at 05:48:43PM +0400, Gleb Smirnoff wrote: T B 1. The bug disappeares if I disable VT-x/AMD-V in my virtual machine T B settings (Settings - System - Acceleration) and appeares if I enable it T B (thanks to Gleb for inspiration yesterday). It disappeares everywhere, on T B all revisions. T B T B 2. r244315 seems to be not buggy even with VT-x enabled. So we have to T B look somewhere between r244315 and r248935. T T Good news! Thanks Boris. T T Can you track this down to a particular revision? I have suspision that it is very close to the bhyve checkin: --- - r245652 | neel | 2013-01-19 08:18:52 +0400 (сб, 19 янв 2013) | 9 lines Merge projects/bhyve to head. 'bhyve' was developed by grehan@ and myself at NetApp (thanks!). Special thanks to Peter Snyder, Joe Caradonna and Michael Dexter for their support and encouragement. Obtained from: NetApp --- - since this is the code that started to utilize VT-x. Can you please check this revision and -1 revision to it? r245652 is not buggy. I traced this down to r248521: svn log -r248521 - r248521 | kib | 2013-03-19 16:08:15 +0100 (Tue, 19 Mar 2013) | 5 lines UFS support of the unmapped i/o for the user data buffers. Sponsored by: The FreeBSD Foundation Tested by: pho, scottl, jhb, bf - The last working revision is 248520. - -- Pozdrawiam, Maciej Milewski -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJ2HUwACgkQPQ1pa2ELkNngDwCgg7lwWXyK5gIsL1i1HssddtlA QocAniNQENn9nGAj7uOYxYRB90Ch5quR =+YaO -END PGP SIGNATURE- ___ 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: 10.0-BETA1 i386 on VirtualBox
On guest hw.ncpu=1 and disk is connected to emulated Intel ahci sata controller visible as ada0. Konstantin Belousov kostik...@gmail.com napisał: On Sun, Nov 03, 2013 at 05:46:01PM +0400, Gleb Smirnoff wrote: Maciej, Boris, On Sun, Nov 03, 2013 at 04:29:11PM +0400, Boris Bobrov wrote: B I traced this down to r248521: B svn log -r248521 B --- B - r248521 | kib | 2013-03-19 16:08:15 +0100 (Tue, 19 Mar 2013) | 5 B lines B B UFS support of the unmapped i/o for the user data buffers. B B Sponsored by: The FreeBSD Foundation B Tested by: pho, scottl, jhb, bf B B --- B - B B The last working revision is 248520. B B Yes, I confirm that. Thanks for you help! Can you please now try unpatched vanilla 10.0-BETA2 iso file and when it boots set in loader (before kernel): OK set vfs.unmapped_buf_allowed=0 OK boot Show what disk driver is used, also show the output of hw.ncpu, both from the guest. -- Wysłane z Androida za pomocą K-9 Mail. Prosze wybaczyć lakoniczność. ___ 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: 10.0-BETA1 i386 on VirtualBox
On 03.11.2013 14:46, Gleb Smirnoff wrote: Maciej, Boris, On Sun, Nov 03, 2013 at 04:29:11PM +0400, Boris Bobrov wrote: B I traced this down to r248521: B svn log -r248521 B --- B - r248521 | kib | 2013-03-19 16:08:15 +0100 (Tue, 19 Mar 2013) | 5 B lines B B UFS support of the unmapped i/o for the user data buffers. B B Sponsored by: The FreeBSD Foundation B Tested by: pho, scottl, jhb, bf B B --- B - B B The last working revision is 248520. B B Yes, I confirm that. Thanks for you help! Can you please now try unpatched vanilla 10.0-BETA2 iso file and when it boots set in loader (before kernel): OK set vfs.unmapped_buf_allowed=0 OK boot Gleb, that seems to work fine. I can end installation without problems. Thank you for this solution. -- Pozdrawiam, Maciej Milewski ___ 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: 10.0-BETA1 i386 on VirtualBox
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02.11.2013 08:06, Boris Bobrov wrote: В сообщении от Thursday 31 of October 2013 17:54:32 Gleb написал: On Thu, Oct 31, 2013 at 05:48:43PM +0400, Gleb Smirnoff wrote: T B 1. The bug disappeares if I disable VT-x/AMD-V in my virtual machine T B settings (Settings - System - Acceleration) and appeares if I enable it T B (thanks to Gleb for inspiration yesterday). It disappeares everywhere, on T B all revisions. T B T B 2. r244315 seems to be not buggy even with VT-x enabled. So we have to T B look somewhere between r244315 and r248935. T T Good news! Thanks Boris. T T Can you track this down to a particular revision? I have suspision that it is very close to the bhyve checkin: --- - r245652 | neel | 2013-01-19 08:18:52 +0400 (сб, 19 янв 2013) | 9 lines Merge projects/bhyve to head. 'bhyve' was developed by grehan@ and myself at NetApp (thanks!). Special thanks to Peter Snyder, Joe Caradonna and Michael Dexter for their support and encouragement. Obtained from: NetApp --- - since this is the code that started to utilize VT-x. Can you please check this revision and -1 revision to it? r245652 is not buggy. It's somewhere between r248500(passwd works) and r248556(passwd don't work). I haven't yet traced this down. - -- Pozdrawiam, Maciej Milewski -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJ05jAACgkQPQ1pa2ELkNlKRgCfUDUUYSE2WAUF3icb9xkaL4HW /mEAn1ohyDuvU+lsEw0DI7iCtktyMYj6 =LC84 -END PGP SIGNATURE- ___ 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: 10.0-BETA1 i386 on VirtualBox
On 31.10.2013 01:08, Boris Bobrov wrote: I'll rephrase that: Can anybody suggest a way to reproduce the bug on a livecd reliably, if you ever met the bug before? Boris what error do you have on the livecd? tail /var/log/messages ? I see some oddity in view /var/log/messages: ^A at the end But the same file copied through disk - network shows no ^A at the end. as /var and /tmp ar on md0 I suspect some kind of memory corruption. -- Pozdrawiam, Maciej Milewski messages Description: Binary data ___ 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: 10.0-BETA1 i386 on VirtualBox
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 31.10.2013 01:08, Boris Bobrov wrote: В сообщении от Thursday 31 of October 2013 02:01:41 Boris написал: В сообщении от Tuesday 29 of October 2013 15:09:57 Gleb написал: Hello, [adding Boris to Cc, who reported same issue in private email] On Thu, Oct 24, 2013 at 05:16:15PM +0200, Maciej Milewski wrote: M I've encountered problems with installing FreeBSD-10.0-BETA1 i386 under M VirtualBox. M The problem is with setting/changing root password during install M process. After entering password twice there is: M M passwd: pam_chauthtok(): error in service module M M Then there shows pwd_mkdb.core in current directory. M The same VirtualBox machine has no problems with installing M FreeBSD-9.2-RELEASE M M Has anyone any clues? I failed to reproduce this with FreeBSD-10.0-BETA2 i386 image :( It installed and booted successfully. Here is my host environment: glebius@think:~:|pkg info -x virtual virtualbox-ose-4.2.18_1 virtualbox-ose-kmod-4.2.18 glebius@think:~:|uname -a FreeBSD think.nginx.com 11.0-CURRENT FreeBSD 11.0-CURRENT #13 r257045: Thu Oct 24 15:16:04 MSK 2013 gleb...@think.nginx.com:/usr/obj/usr/src/head/sys/THINKPAD_X1 amd64 When trying to reproduce I used VirtualBox GUI and choosed defaults in every dialog window. Boris and Maciej, if you use non-default configuration, can you please provide more details? Hi. Can any of you suggest a way to reproduce the bug on a livecd reliably? I'll rephrase that: Can anybody suggest a way to reproduce the bug on a livecd reliably, if you ever met the bug before? Boris what error do you have on the livecd? tail /var/log/messages ? I see some oddity in view /var/log/messages: ^@ at the end The same file copied through disk - network shows no ^@ at the end. As /var and /tmp ar on md0/md1 I suspect some kind of memory corruption. - -- Pozdrawiam, Maciej Milewski -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJyRswACgkQPQ1pa2ELkNll/wCfeqN8k4ZW+E57tDohFGelCGTs E8IAoIB+pRVVQpugIlYEoGj7dnj5HkgX =JRp8 -END PGP SIGNATURE- ___ 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: 10.0-BETA1 i386 on VirtualBox
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 31.10.2013 13:31, Boris Bobrov wrote: When I do less /var/log/messages, less fails with segmentation fault. It happens on BETA1 and BETA2, but not on older 10.0 releases. I got the same with less. - -- Pozdrawiam, Maciej Milewski -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJyVrIACgkQPQ1pa2ELkNkDNACeJKj/7tJUjQ3yCusIZEFQlNJ9 NvoAn0S/zFhRNxuOf+yLcRUlDI9N6u/3 =d0l5 -END PGP SIGNATURE- ___ 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: 10.0-BETA1 i386 on VirtualBox
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 31.10.2013 14:26, Glen Barber wrote: On Thu, Oct 31, 2013 at 09:16:34AM -0400, Glen Barber wrote: http://ftp.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/10.0-BETA1/amd64/20131007/ Wrong arch, sorry. http://ftp.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/10.0-BETA1/i386/20131007/ Glen No worries, found corect one myself :) - -- Pozdrawiam, Maciej Milewski -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJyXAAACgkQPQ1pa2ELkNnwOwCfYTUev/zs7E3sIslsCuCqZ7o+ ie4AmgK8AikXVbfIIeT2kSsZDmXarVGv =rIpl -END PGP SIGNATURE- ___ 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: 10.0-BETA1 i386 on VirtualBox
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 31.10.2013 14:26, Glen Barber wrote: On Thu, Oct 31, 2013 at 09:16:34AM -0400, Glen Barber wrote: http://ftp.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/10.0-BETA1/amd64/20131007/ Wrong arch, sorry. http://ftp.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/10.0-BETA1/i386/20131007/ Glen Glen, Simple less /var/log/messages works fine but passwd: in pam_sm_chauthtok(): pw_mkdb() failed passwd: pam_chauthtok(): error in service module - -- Pozdrawiam, Maciej Milewski -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJyYWAACgkQPQ1pa2ELkNkq0gCggFX1KeU9TyF5s46hjDSdSQDV 5WAAoIn56n9r83RV0kVd4QOQDJNSZQ/Q =7vZS -END PGP SIGNATURE- ___ 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: 10.0-BETA1 i386 on VirtualBox
On 29.10.2013 12:09, Gleb Smirnoff wrote:
Hello,
[adding Boris to Cc, who reported same issue in private email]
On Thu, Oct 24, 2013 at 05:16:15PM +0200, Maciej Milewski wrote:
M I've encountered problems with installing FreeBSD-10.0-BETA1 i386 under
M VirtualBox.
M The problem is with setting/changing root password during install
M process. After entering password twice there is:
M
M passwd: pam_chauthtok(): error in service module
M
M Then there shows pwd_mkdb.core in current directory.
M The same VirtualBox machine has no problems with installing
M FreeBSD-9.2-RELEASE
M
M Has anyone any clues?
I failed to reproduce this with FreeBSD-10.0-BETA2 i386 image :(
It installed and booted successfully.
Here is my host environment:
glebius@think:~:|pkg info -x virtual
virtualbox-ose-4.2.18_1
virtualbox-ose-kmod-4.2.18
glebius@think:~:|uname -a
FreeBSD think.nginx.com 11.0-CURRENT FreeBSD 11.0-CURRENT #13 r257045: Thu Oct
24 15:16:04 MSK 2013
gleb...@think.nginx.com:/usr/obj/usr/src/head/sys/THINKPAD_X1 amd64
When trying to reproduce I used VirtualBox GUI and choosed defaults
in every dialog window.
Boris and Maciej, if you use non-default configuration, can you please
provide more details?
No - in my case it's the same with 10-BETA2 :(
$ pkg_version -vs virtualbox
virtualbox-ose-4.2.18_1 = up-to-date with port
virtualbox-ose-kmod-4.2.18 = up-to-date with port
$ uname -a
FreeBSD intranet.tup.com.pl 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #0
r255613: Mon Sep 16 20:25:59 CEST 2013
m...@intranet.tup.com.pl:/usr/obj/usr/src/sys/intranet amd64
I'm using script:
$ cat create_BSD.sh
#!/bin/sh
NAME=FreeBSD10BETA2
DVDMEDIUM=/data/iso/FreeBSD-10.0-BETA2-i386-disc1.iso
VBoxManage createvm -name ${NAME} -register
VBoxManage modifyvm ${NAME} --memory 1024 --acpi on --boot1 dvd
--nictype1 82540EM --nic1 bridged --bridgeadapter1 rl0
VBoxManage createhd --filename ${NAME} --size 3
VBoxManage storagectl ${NAME} --name SATA Controller --add sata
--controller IntelAhci --sataportcount 4
VBoxManage storageattach ${NAME} --storagectl SATA Controller --port
0 --device 0 --type hdd --medium ${NAME}.vdi
VBoxManage storagectl ${NAME} --name IDE Controller --add ide
--controller PIIX4
VBoxManage storageattach ${NAME} --storagectl IDE Controller --port
0 --device 0 --type dvddrive --medium ${DVDMEDIUM}
VBoxManage modifyvm ${NAME} --vrdeproperty VNCPassword=password
and starting via:
VBoxHeadless -s FreeBSD10BETA2
and connecting through vnc(from krdc) on port 3389
Gleb are you on some irc channel?
--
Pozdrawiam,
Maciej Milewski
___
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: 10.0-BETA1 i386 on VirtualBox
On 29.10.2013 12:09, Gleb Smirnoff wrote: Hello, [adding Boris to Cc, who reported same issue in private email] On Thu, Oct 24, 2013 at 05:16:15PM +0200, Maciej Milewski wrote: M I've encountered problems with installing FreeBSD-10.0-BETA1 i386 under M VirtualBox. M The problem is with setting/changing root password during install M process. After entering password twice there is: M M passwd: pam_chauthtok(): error in service module M M Then there shows pwd_mkdb.core in current directory. M The same VirtualBox machine has no problems with installing M FreeBSD-9.2-RELEASE M M Has anyone any clues? I failed to reproduce this with FreeBSD-10.0-BETA2 i386 image :( It installed and booted successfully. Here is my host environment: glebius@think:~:|pkg info -x virtual virtualbox-ose-4.2.18_1 virtualbox-ose-kmod-4.2.18 glebius@think:~:|uname -a FreeBSD think.nginx.com 11.0-CURRENT FreeBSD 11.0-CURRENT #13 r257045: Thu Oct 24 15:16:04 MSK 2013 gleb...@think.nginx.com:/usr/obj/usr/src/head/sys/THINKPAD_X1 amd64 When trying to reproduce I used VirtualBox GUI and choosed defaults in every dialog window. Boris and Maciej, if you use non-default configuration, can you please provide more details? I've tried default install without any games,ports and src. With guided disk organization, with simple password qaz123 or longer one, results are tha same: error in service module. -- Pozdrawiam, Maciej Milewski ___ 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: 10.0-BETA1 i386 on VirtualBox
On 27.10.2013 09:03, Gleb Smirnoff wrote: Maciej, On Thu, Oct 24, 2013 at 05:16:15PM +0200, Maciej Milewski wrote: M I've encountered problems with installing FreeBSD-10.0-BETA1 i386 under M VirtualBox. M The problem is with setting/changing root password during install M process. After entering password twice there is: M M passwd: pam_chauthtok(): error in service module M M Then there shows pwd_mkdb.core in current directory. M The same VirtualBox machine has no problems with installing M FreeBSD-9.2-RELEASE M M Has anyone any clues? Can you please tell version of VirtualBox and host OS? One of them is: FreeBSD 9.2-PRERELEASE #0 r255613: Mon Sep 16 20:25:59 CEST 2013 $ VBoxManage -v 4.2.18_OSEr88780 # pkg_version -vs virtualbox virtualbox-ose-4.2.18_1 = up-to-date with port virtualbox-ose-kmod-4.2.18 = up-to-date with port And the same is with % VBoxManage -v 4.2.18_OSEr88780 Under ArchLinux. -- Pozdrawiam, Maciej Milewski ___ 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: [rfc] removing the NDISulator
On 24.10.2013 05:46, Thomas Mueller wrote: I have motherboard (MSI Z77 MPOWER) with Realtek 8111E Ethernet that fails to connect in FreeBSD or OpenBSD, OK with NetBSD-current and Linux, and Atheros AR9271 onboard wifi: device athn is included in NetBSD (current only) and OpenBSD. Tom For your problems with Realtek 8111E chipset please have alook at http://lists.freebsd.org/pipermail/freebsd-net/2013-October/036935.html Maybe this patch isn't for you but you need to do something similar to add support. Regards, Maciej ___ 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
10.0-BETA1 i386 on VirtualBox
I've encountered problems with installing FreeBSD-10.0-BETA1 i386 under VirtualBox. The problem is with setting/changing root password during install process. After entering password twice there is: passwd: pam_chauthtok(): error in service module Then there shows pwd_mkdb.core in current directory. The same VirtualBox machine has no problems with installing FreeBSD-9.2-RELEASE Has anyone any clues? Regards, Maciej Milewski ___ 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: 10.0-BETA1 i386 on VirtualBox
On 24.10.2013 17:34, Ryan Stone wrote: On Thu, Oct 24, 2013 at 11:16 AM, Maciej Milewski m...@dat.pl wrote: I've encountered problems with installing FreeBSD-10.0-BETA1 i386 under VirtualBox. The problem is with setting/changing root password during install process. After entering password twice there is: passwd: pam_chauthtok(): error in service module Then there shows pwd_mkdb.core in current directory. The same VirtualBox machine has no problems with installing FreeBSD-9.2-RELEASE Has anyone any clues? Regards, Maciej Milewski I have seen that error when the password database in /etc is not writeable (in my case, / was mounted read-only). I don't think that's the case as during install I went to another console to check how is mounted future / and it's: /dev/ada0p2 on /mnt (ufs, local, journaled soft-updates) and /mnt/etc/pwd.db, group, passwd are 644 and spwd.db,master.passwd are 600 The same as in running 9.2-RELEASE Anyway, thanks for the hint. Regards, Maciej Milewski ___ 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: 10.0-BETA1 i386 on VirtualBox
On 24.10.2013 17:47, Maciej Milewski wrote: On 24.10.2013 17:34, Ryan Stone wrote: On Thu, Oct 24, 2013 at 11:16 AM, Maciej Milewski m...@dat.pl wrote: I've encountered problems with installing FreeBSD-10.0-BETA1 i386 under VirtualBox. The problem is with setting/changing root password during install process. After entering password twice there is: passwd: pam_chauthtok(): error in service module Then there shows pwd_mkdb.core in current directory. The same VirtualBox machine has no problems with installing FreeBSD-9.2-RELEASE Has anyone any clues? Regards, Maciej Milewski I have seen that error when the password database in /etc is not writeable (in my case, / was mounted read-only). I don't think that's the case as during install I went to another console to check how is mounted future / and it's: /dev/ada0p2 on /mnt (ufs, local, journaled soft-updates) and /mnt/etc/pwd.db, group, passwd are 644 and spwd.db,master.passwd are 600 The same as in running 9.2-RELEASE Anyway, thanks for the hint. Regards, Maciej Milewski I've managed to make another simple test: chroot from 9.2-RELEASE kernel and I can change the password without a problem, chroot from 10.0-BETA1 kernel and error appears. No matter if I use 10.0-BETA1 kernel on 9.2-RELEASE userland or boot from CD image. For tests I turned off journal, left only soft-updates. Regards, Maciej Milewski ___ 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
IPSEC with IPv6 crashes
I'm trying to use IPSEC with IPv6 in transport mode. My configuration is simple: IPSEC + racoon from ipsec-utils. One side is RS(MIPS) with HEAD-r252464 and 2nd side ALIX(i386) with 9.1-STABLE. This error is visible only on MIPS side. ipsec.conf: spdadd [ipv6_addr1] [ipv6_addr2] any -P in ipsec esp/transport//require; spdadd [ipv6_addr2] [ipv6_addr1] any -P out ipsec esp/transport//require; And the error is reproducible with just getting transmission over the IPSEC: Trap cause = 2 (TLB miss (load or instr. fetch) - kernel mode) [ thread pid 0 tid 100027 ] Stopped at ipsec6_common_input_cb+0x364: lw v0,116(v1) db bt Tracing pid 0 tid 100027 td 0x80dc2990 db_trace_thread+30 (?,?,?,?) ra c039f2400018 sp 0 sz 0 80083c3c+114 (0,?,,?) ra c039f2580020 sp 1 sz 1 80082f84+388 (?,?,?,?) ra c039f27800a8 sp 0 sz 0 db_command_loop+70 (?,?,?,?) ra c039f3200018 sp 0 sz 0 80085a80+f4 (?,?,?,?) ra c039f33801a8 sp 0 sz 0 kdb_trap+110 (?,?,?,?) ra c039f4e00030 sp 0 sz 0 trap+f18 (?,?,?,?) ra c039f51000b8 sp 0 sz 0 MipsKernGenException+134 (82bee380,81c84900,0,0) ra c039f5c800c8 sp 10001 sz 1 ipsec6_common_input_cb+364 (81c84900,?,28,?) ra c039f6900038 sp 1 sz 1 803c6684+568 (?,?,?,?) ra c039f6c80078 sp 0 sz 0 crypto_done+11c (?,?,?,?) ra c039f7400030 sp 0 sz 0 803fd608+fb4 (?,?,?,?) ra c039f77001a0 sp 0 sz 0 803fb3a8+164 (?,?,?,?) ra c039f9100028 sp 0 sz 0 crypto_dispatch+94 (?,?,?,?) ra c039f9380020 sp 0 sz 0 803c708c+62c (?,?,?,?) ra c039f9580058 sp 0 sz 0 803b2390+52c (?,?,?,?) ra c039f9b00060 sp 0 sz 0 ipsec6_common_input+19c (?,?,?,?) ra c039fa100040 sp 0 sz 0 ip6_input+16d8 (81c84900,?,?,?) ra c039fa500120 sp 1 sz 0 netisr_dispatch_src+134 (?,?,?,?) ra c039fb700040 sp 0 sz 0 netisr_dispatch+14 (?,?,?,?) ra c039fbb00018 sp 0 sz 0 ether_demux+218 (?,81c84900,?,?) ra c039fbc80028 sp 1 sz 0 802d72ec+4a8 (81c84900,?,?,?) ra c039fbf00030 sp 1 sz 0 netisr_dispatch_src+134 (?,?,?,?) ra c039fc200040 sp 0 sz 0 netisr_dispatch+14 (?,?,?,?) ra c039fc600018 sp 0 sz 0 802d6e9c+3c (?,?,?,?) ra c039fc780018 sp 0 sz 0 ieee80211_deliver_data+100 (?,?,?,?) ra c039fc900028 sp 0 sz 0 803387fc+bc4 (?,?,?,ffa0) ra c039fcb80060 sp 0 sz 0 ath_rx_pkt+6c0 (?,?,0,?) ra c039fd180050 sp 0 sz 1 800aa98c+388 (?,1,?,?) ra c039fd680060 sp 1 sz 0 800aaef0+c4 (?,?,?,?) ra c039fdc80020 sp 0 sz 0 8024e34c+e8 (?,?,?,?) ra c039fde80038 sp 0 sz 0 taskqueue_thread_loop+8c (?,?,?,?) ra c039fe200038 sp 0 sz 0 fork_exit+b0 (?,?,?,?) ra c039fe580028 sp 0 sz 0 fork_trampoline+10 (?,?,?,?) ra c039fe80 sp 0 sz 0 pid 0 I'm open to any hints. Regards, Maciej Milewski ___ 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: Panic/Freeze with IPSEC on r254532
On 10.09.2013 14:33, Vincent Hoffman wrote: root@bsdpkgbuild:~ # racoonctl show-sa ipsec send: Bad file descriptor l I did try stating racoon under truss and using racoon -F -d -d -d but didnt see it even try to open /var/db/racoon/racoon.sock while on the other end (8.4-RELEASE) I see 2013-09-10 13:24:19: DEBUG: open /var/db/racoon/racoon.sock as racoon management. in the output from racoon -F -d -d -d Have you enabled admin port during installation of ipsec-tools? -- Pozdrawiam, Maciej Milewski ___ 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: IPSEC crashes after r253088
On 23.07.2013 14:00, Andrey V. Elsukov wrote: Also, I already prepared patch to test. I've tested it on mips platform and it makes it working fine as before that change. I can succesfully boot system. Thank you for patching it. -- Pozdrawiam, Maciej Milewski ___ 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: IPSEC crashes after r253088
On 20.07.2013 22:43, Taku YAMAMOTO wrote:
After r253088, systems with IPSEC and KSTACK_PAGES 4 crashes on
booting into multi-user mode.
The crash is due to sysctl -a in /etc/rc.d/initrandom ended up with
kernel stack overflow.
The problem is what we have in sys/net/vnet.h:
#define SYSCTL_VNET_PCPUSTAT(parent, nbr, name, type, array, desc) \
static int \
array##_sysctl(SYSCTL_HANDLER_ARGS) \
{ \
type s; \
CTASSERT((sizeof(type) / sizeof(uint64_t)) == \
(sizeof(VNET(array)) / sizeof(counter_u64_t))); \
COUNTER_ARRAY_COPY(VNET(array), s, sizeof(type) / sizeof(uint64_t));\
if (req-newptr)\
COUNTER_ARRAY_ZERO(VNET(array), \
sizeof(type) / sizeof(uint64_t)); \
return (SYSCTL_OUT(req, s, sizeof(type))); \
} \
SYSCTL_VNET_PROC(parent, nbr, name, CTLTYPE_OPAQUE | CTLFLAG_RW, NULL, \
0, array ## _sysctl, I, desc)
where type is struct ipsecstat which is 12560 bytes of size (larger than
3 pages) of size when processing net.inet.ipsec.ipsecstats.
I can confirm. I've been hit by that problem on MIPS platform.
--
Pozdrawiam,
Maciej Milewski
___
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: Problem compiling libs after pass to current
Dnia niedziela, 27 listopada 2011 19:59:44 ZaRiuS KRiNG pisze:
Hi! is my first post here and have a little problem try to google some and
don't find any of value.
A week ago compile the src of current, and after that in any new port i
install, if compile before any lib, don't work, i need to install pkg from
repository of that lib and continue compiling the program, and work fine.
Just have this problem with the libs
Any solution?
Have you updated you ports tree? Maybe you are affected by the issue mentioned
in ports/UPDATING:
20110928:
AFFECTS: users of 10-current
AUTHOR: ead...@freebsd.org
There are known issues installing ports on FreeBSD 10+ due to
bogus assumptions by various build scripts. This will not be fixed
until 9-RELEASE is released.
There are two workarounds:
1) Set UNAME_r=9.9-CURRENT in your environment
2) Set REVISION=9.9 in ${SRCDIR}/sys/conf/newvers.sh
--
Maciek
___
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: Problem compiling libs after pass to current
Dnia poniedziałek, 28 listopada 2011 18:55:04 ZaRiuS KRiNG pisze: Ok, the second know how make, but the first no. How can set new uname -r in the environment? Sorry but in some things need a lot of experience, and for that try use current About what programs got the fail? Chromium and Abiword, with one, 2-3 with second just one. But make that, pkg_add -r and continue with compiling but want learn how solve the problem no, just evade it Thanks for all First: don't top post! Second: you haven't answered the question if you have lately updated your ports. As for setting uname please RTFM of uname, it's there. Problem is known to be because of bad comparison done by automake/autoconf scripts. Maciek ___ 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
sys/conf/newvers.sh broken for work with git
Hi,
I encountered newvers.sh issue while working locally with git tree.
The last patch broke correct versioning. The issue is the break after
checking the svnversion cmd.
I use git for local work and have svnversion cmd too. So the first check
is true and break makes exit from further processing for loop. This way
there is no check if git is in path.
Quick hack would be changing the order of this if to first check if
there is .git dir and git cmd and then go further to check svnversion.
This solution might be not perfect but atleast is working for me.
Greetings,
Maciek
Quick patch is attached.
--- sys/conf/newvers.sh 2011-11-19 00:56:50.795815738 +0100
+++ sys/conf/newvers-patched.sh 2011-11-19 00:58:21.187818982 +0100
@@ -88,14 +88,14 @@
i=`${MAKE:-make} -V KERN_IDENT`
for dir in /bin /usr/bin /usr/local/bin; do
- if [ -x ${dir}/svnversion ] ; then
- svnversion=${dir}/svnversion
- break
- fi
if [ -d ${SYSDIR}/../.git -a -x ${dir}/git ] ; then
git_cmd=${dir}/git --git-dir=${SYSDIR}/../.git
break
fi
+ if [ -x ${dir}/svnversion ] ; then
+ svnversion=${dir}/svnversion
+ break
+ fi
done
if [ -n $svnversion ] ; then
___
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: More if_ath churn coming your way!
Dnia czwartek, 20 stycznia 2011 o 10:44:27 Max Khon napisał(a): Adrian, On Thu, Jan 20, 2011 at 11:51 AM, Adrian Chadd adrian.ch...@gmail.comwrote: I'm in the process of merging in the non-intrusive changes to the if_ath code into -HEAD. I'd appreciate some testing just to ensure I haven't broken anything terribly obvious. Any chances for proper support for Atheros 802.11n cards? Should not we just port ath9k (Linux) or athn (OpenBSD) drivers? AFAIK OpenBSD support is limited on these cards. From man athn(4)[1] CAVEATS The athn driver does not support any of the 802.11n capabilities offered by the adapters. Additional work is required in ieee80211(9) before those features can be supported. [1] http://www.openbsd.org/cgi- bin/man.cgi?query=athnapropos=0sektion=0manpath=OpenBSD+Currentarch=i386format=html Regards, Maciej Milewski ___ 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
