Re: on amd64 r246552: iwn0: : fatal firmware error
On Mon, Feb 11, 2013 at 12:18 PM, Anton Shterenlikht wrote: > Yes, I can reproduce this on amd64 -current. > I had to flip the switch twice to cause this: > (..) > However, in my earlier report I got to this > error with no flipping the switch at all. Uhm, on some networks I also very often get information in the dmesg that "wlan0: link state changed to DOWN" and then "wlan0: link state changed to DOWN", maybe this produce issues similar to radio flip switch..? -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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: on amd64 r246552: iwn0: : fatal firmware error
Yesterday I had something similar - it was cause by a radio switch flip: iwn0: RF switch: radio disabled ubt0: ubt_bulk_read_callback:867: bulk-in transfer failed: USB_ERR_STALLED ubt0: ubt_intr_read_callback:767: interrupt transfer failed: USB_ERR_STALLED ugen1.4: at usbus1 (disconnected) ubt0: at uhub3, port 7, addr 4 (disconnected) iwn0: iwn_intr: fatal firmware error firmware error log: error type = "SYSASSERT" (0x0005) program counter = 0x0001EFD8 source line = 0x012E error data = 0x branch link = 0x0001EEE40001EEE4 interrupt link = 0x1532 time= 767402829 driver status: tx ring 0: qid=0 cur=194 queued=0 tx ring 1: qid=1 cur=0 queued=0 tx ring 2: qid=2 cur=0 queued=0 tx ring 3: qid=3 cur=18 queued=0 tx ring 4: qid=4 cur=58 queued=0 tx ring 5: qid=5 cur=0 queued=0 tx ring 6: qid=6 cur=0 queued=0 tx ring 7: qid=7 cur=0 queued=0 tx ring 8: qid=8 cur=0 queued=0 tx ring 9: qid=9 cur=0 queued=0 tx ring 10: qid=10 cur=0 queued=0 tx ring 11: qid=11 cur=0 queued=0 tx ring 12: qid=12 cur=0 queued=0 tx ring 13: qid=13 cur=0 queued=0 tx ring 14: qid=14 cur=0 queued=0 tx ring 15: qid=15 cur=0 queued=0 tx ring 16: qid=16 cur=0 queued=0 tx ring 17: qid=17 cur=0 queued=0 tx ring 18: qid=18 cur=0 queued=0 tx ring 19: qid=19 cur=0 queued=0 rx ring: cur=1 FreeBSD mercury 9.1-RELEASE FreeBSD 9.1-RELEASE #0: Fri Feb 8 23:26:37 CET 2013 root@mercury:/usr/obj/usr/src/sys/CeDeROM-MERCURY amd64 % pciconf -lv iwn0@pci0:2:0:0:class=0x028000 card=0x13218086 chip=0x422c8086 rev=0x35 hdr=0x00 vendor = 'Intel Corporation' device = 'Centrino Advanced-N 6200' class = network Best regards, Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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: 7+ days of dogfood
On Sun, Feb 10, 2013 at 1:07 AM, Steve Kargl wrote: > In a long thread started by Peter Wemm on developers@, he described > the move/upgrade of the FreeBSD.org cluster to using FreeBSD-10. A > part of his description included the need to test top-of-tree under > actual real-world conditions. In his words, FreeBSD should "eat its > own dogfood." The new installation on FreeBSD.org, of course, would > test FreeBSD-10 under (heavy) server load. Just one word from an ordinary user - this is perfect idea to test things in the real world scenario in a dedicated environment because this will show problems and force solutions very quickly. Some more serious tasks may be also a good playground to test stability of the stable branch and make sure they will not propagate issues to the production stable platforms around the world. I really love FreeBSD for the clean, simple and elegant yet still very powerful solutions. Some features are still behind, some features are pioneer, still smart and experienced personnel decisions behind the scenes produces impressive results. I am sure this is also a good decision. This is why I stick and promote the FreeBSD, although some people don't like it, and I even consider to switch to CURRENT in everyday tasks too if this will help your work with necessary feedback :-) Best regards :-) Tomek Cedro -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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: Intel 82574 issue reported on Slashdot
On Sat, Feb 9, 2013 at 4:25 PM, CeDeROM wrote: > On Sat, Feb 9, 2013 at 3:44 PM, Christoph Moench-Tegeder > wrote: >> ## O. Hartmann (ohart...@zedat.fu-berlin.de): >>> We don't even have the tool tcpreplay in the ports mentioned in that BLOG. >> It's in net-mgmt/tcpreplay. > > And I managed to build mentioned Ostinato packet crafting utility with > no problem on my FreeBSD 9.1-RELEASE AMD64. If they provide package > and release (which I already asked from the authors) I will make a > port for this tool as well :-) There it goes http://www.freebsd.org/cgi/query-pr.cgi?pr=175993 have fun! :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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: Intel 82574 issue reported on Slashdot
On Sat, Feb 9, 2013 at 3:44 PM, Christoph Moench-Tegeder wrote: > ## O. Hartmann (ohart...@zedat.fu-berlin.de): >> We don't even have the tool tcpreplay in the ports mentioned in that BLOG. > It's in net-mgmt/tcpreplay. And I managed to build mentioned Ostinato packet crafting utility with no problem on my FreeBSD 9.1-RELEASE AMD64. If they provide package and release (which I already asked from the authors) I will make a port for this tool as well :-) Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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"
wifi and wpa_supplicant
Hello :-) I am wondering how exactly the wifi interface and wpa_supplicant is organized - is there any script at wlan0 interface up that starts wpa_supplicant for that interface? Do I have to start wpa_supplicant by hand any time I bring interface down and up (it looks yes for me)? I have ifconfig_wlan0="WPA DHCP" set in rc.conf so I guess after/when interface is up both wpa_supplicant and dhclient should be started..? What should I make to wpa_supplicant starts automatically when I bring wlan0 up? I am using iwn intel wifi driver. Any hints appreciated :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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: bluetooth a2dp audio
On Thu, Jan 17, 2013 at 12:20 PM, Hans Petter Selasky wrote: > You might want to look at my Virtual OSS from I4B SVN, which creates an entire > /dev/vdsp device from userspace using cuse4bsd! Thank you Hans!! :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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"
bluetooth a2dp audio
Hello :-) Is anyone working on A2DP Audio Profil/Device for Bluetooth devices? The bluetooth layer is working. Audio can use different dsp devices and has very nice control interface. I guess to make it work it would be necessary to create dsp device that could sink data, transform it into a2dp codec and send to bluetooth device.. Where should I start to look for information on this subject? Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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: Hardware VM support for Jails
Good to know thank you! :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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"
Hardware VM support for Jails
Hello :-) I was wondering if there is a hardware accelerated Jail using Virtualization CPU extensions in BSD or everything is done in Kernel by software? SUSE is advertising their "light virtualization" (no hardware emulation) I was wondering if BSD has this capabilities too ;-) What would be benefit for this over Jail? Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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: 9.1-RC3 LiveCD missing features
Hello Garrett :-) UnionFS works very well on Linux based embedded systems and its very powerful :-) I dont know the mdmfs sorry :-) +1 for your ideas :-) Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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: 9.1-RC3 LiveCD missing features
Running fsck -t ufs -fy solved the issue!! http://i47.tinypic.com/35m1qxk.jpg How reliable is new UFS2-SU+J? Are there any journal verification routines (I heard about some chcecks in the background). Will automatic fsck on boot force full filesystem checks in any case (like filesystem related kernel panic will set full filesystem check flag)? This was the filesystem issue not the hard drive (its new 2TB WD disk preformatted before use). Having badblocks and other test solutions on the LiveCD would at least detect some hardware issues I gues, I give +1 for service/support tools in LiveCD :-) Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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: 9.1-RC3 LiveCD missing features
Hello Ian :-) This is the problem - / is read only and /etc/resolv.conf already links to nonexistent file. This way I cannot modify its content nor link other file (i.e. /var/resolv.conf) to /etc/resolv.conf. Creating /var/resolv.conf does not help either. I think /etc/resolv.conf should point to /var/resolv.conf from start so the resolver is functional :-) Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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: 9.1-RC3 LiveCD missing features
dd if=root_part of=root_part took loong time but it did not help :-( -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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: 9.1-RC3 LiveCD missing features
Thanks Warren :-) I noticed that Western Digital disks MUST be preformatted this way at first otherwise stragne things happen later on (I had 3 disks like this for desktop and laptop). Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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: 9.1-RC3 LiveCD missing features
Hello Chuck :-) DD cannot perform non-destructive test.. unless I do dd if=/dev/ada0s2a of=/dev/ada0s2a :-) Do you think drives are now smart enough to remap badblocks this way? What is the probability that there are no badblocks or badblocks are not detected this way? Which pattern is better for format 0x00 or 0xFF or one after another or dont care? I think badblocks is quite useful in this case even in destructive mode.. Btw. I have moved discussion to freebsd-stable , sorry for a mess :-) Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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"
9.1-RC3 LiveCD missing features
Hello :-) I have tried to chceck for badblocks on my / but I did not find badblocks program on LiveCD and there is no option to install it. This is very useful utility, please add it as part of LiveCD :-) Also there is a problem with DHCP based workstations using LiveCD - although interface gets configured it is impossible to update /etc/resolv.conf (by dhclient and by hand) and so this workstation pretty useless for IPv4 (is it more usable on IPv6?). Please update :-) Thank you :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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"
9.1-RC3 AMD64 reproducible kernel panic
Hello :-) After days of problem with my system storage (?) I think I have located the issue, or at least I am able to reproduce it, please take a look at attached picture (photo of a crash). At first I thought that was the Ext2 filesystem issue, but then I have replaced the filesystem to UFS2-SU+J (which increased transfer efficiency and dramatically reduced filesystem check time compared to Ext2) but the issue persisted. This problem occurs also when only / is mounted (no additional storage locations only the OS). This can mean there is a corruption on / that is marked clean. Right now I am not sure if this is storage related anymore... there is however some note on ffs double alloc. Crash occurs after I start Xorg (Kde3 WM, all packages installed from binary packages with portinstall). Please let me know if you need additional information/tests :-) Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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: UFS2 and Journaling in 9.1-RC3
On Fri, Dec 7, 2012 at 4:09 PM, Miroslav Lachman <000.f...@quip.cz> wrote: > In short - if you choose Gjournal with data and journal on the same disk, > you will have about half write speed. Okay, minus for GJournal in that case, but it is very interesting solution, as most of the stuff in FreeBSD :-) > If you choose SU+J, you will not be able to use UFS snapshot feature at this > time (there is some bug and snapshots on SU+J is disabled) Not really need snapshots :-) > Other than that - SU+J is easier to Enable / Disable on existing partition > but is not well testet - it is younger technology than Gjournal. Okay I can test it :-) I just hope it wont eat my precious data :-) I will take UFS2-SU+J then :-) Thanks Miroslav! :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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: UFS2 and Journaling in 9.1-RC3
On Fri, Dec 7, 2012 at 2:41 PM, Ivan Voras wrote: > It looks like you are confusing GEOM journalling (-J) and UFS-SU > journalling (-j). They are very different, and today you probably want > to use the latter. If you are installing 9.x from scratch, it will be > enabled by default. If not, you can use newfs -j or tunefs -j to enable it. "When any other means fail, read the manual" heh :-) I am still a bit confused, even after reading [1], because there is no explanation of difference between GJournal and SU / SU+J (which was introduced in FreeBSD 9.0). I understand GJournal works below filesystem level and I dont need to use fsck. SU/SU+J is part of the UDF/UDF2 filesystem. I should not use SU and GJournal at the same time. What are the advantages of SU/US+J? What is the advantage of SU+J over SU? Should I use Gjournal or SU/SU+J? Any hints welcome! :-) If I have already created UFS2 with -J, I understand I can switch it off, can I then simply turn of UFS+J (-j) with no data loss on existing filesystem? Which solution is better for drives >1TB when I dont want to wait an hour for fsck? [1] http://www.freebsd.org/doc/en_US.ISO8859-1/articles/gjournal-desktop/index.html Thanks! :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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: UFS2 and Journaling in 9.1-RC3
On Fri, Dec 7, 2012 at 2:41 PM, Ivan Voras wrote: > It looks like you are confusing GEOM journalling (-J) and UFS-SU > journalling (-j). They are very different, and today you probably want > to use the latter. If you are installing 9.x from scratch, it will be > enabled by default. If not, you can use newfs -j or tunefs -j to enable it. Hello Ivan! Thanks for the hint! :-) :-) When I have created a new filesystem type 2 (UFS2) with -J switch, then on mount I get this error that filesystem has journaling enabled but no provider is specified, so it looks like no journal is enabled? Does newfs -J create journal as well? According to man newfs: -J Enable journaling on the new file system via gjournal. See gjournal(8) for details. This is why I have started reading man gjournal and saw an example where journal is first created before newfs... Will "gjournal label -f" erase all data on partition with existing newfs/ufs2? Thanks!! :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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"
UFS2 and Journaling in 9.1-RC3
Hello :-) I am new to journaled UFS2, so there goes some questions and remarks: 1. GJournal MUST be run before NewFS, especially on one provider, this should be clearly stated in NewFS manual, before hotshots like me first create the fs and then want the journal, please update. 2. Is it possible to automaticaly create journal by NewFS when -J flag is set? 3. Is it possible to add journal to existing partition (partition and journal are on the same provider) without loosing data on that partition? Gjournal warns that running label -f will destroy the data... 4. When I want to use data and journal on one partiton partition.journal appears after I create a label with gjournal. Why do I mount partition.journal not the partition?? Isn't the journal something that makes data partition to work aka backend? Isn't the journal a metadata that keeps the record of files, if so why do I mount this metadata, this looks odd. 5. In my 9.1-RC3 I see no .journal device for /partition - does it mean that journal is not created by default?? Does bsdinstall remember to first greate gjournal? Any hints welcome :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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: 9.1-RC3 default Linux ALSA configuration
On Sun, Dec 2, 2012 at 10:26 PM, Boris Samorodov wrote: > 03.12.2012 01:08, CeDeROM пишет: > It's the configuration file that is installed by audio/alsa-lib: > LOCALBASE/etc/asound.conf. Perfect solution! Replacing /compat/linux/etc/asound.conf with /usr/local/etc/asound.conf (or using the symlink as you suggeted) also solved my issue on the other machine :-) The configuration for 7.1 sound is more complex and valid for native alsa-lib on FreeBSD, this good configuration also propagates on Linux emulation :-) THANKS A LOT BORIS!!! :-) Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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: 9.1-RC3 default Linux ALSA configuration
On Sun, Dec 2, 2012 at 5:44 PM, Boris Samorodov wrote:
> I've just committed a fix to linux-f10-alsa-lib port. The port now
> creates a soft link to the native FreeBSD configuration file at
> LINUXBASE. That may help here.
Hey Boris :-) What is the native configuration file location? I only
have /compat/linux/etc/alsa/pcm/pcm-oss.conf file.
What is more, according to
http://www.freebsd.org/cgi/man.cgi?query=pcm&sektion=4
hw.snd.default_unit
Default sound card for systems with multiple sound cards. When
using devfs(5), the default device for /dev/dsp. Equivalent to a
symlink from /dev/dsp to /dev/dsp${hw.snd.default_unit}.
But this does not solve the alsa issue for linux even if my default
device is 0, so the /dev/dsp should point to /dev/dsp0 (?) or
/dev/dsp.0.0 (?).
On another machine with SB Audigy I have no sound at all, but the
calls are ongoing (no audio device problem). Any suggestions? :-)
Thanks :-)
Tomek
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
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: 9.1-RC3 default Linux ALSA configuration
Or maybe there is another way to set /dev/dsp to be /dev/dsp0 (or
others) at system level? That would be even better that setting every
config file by hand, just to point to the default dsp device :-)
On Fri, Nov 30, 2012 at 2:45 PM, CeDeROM wrote:
> I have installed and started Skype (2.1 and 2.2 devel) with success
> using Linux binaries provided in port tree. However there is an issue
> with default ALSA configuration and sound/calls does not work properly
> off out the box. I suggest to set /dev/dsp0 and /dev/mixer0 as default
> devices in the alsa configuration, so the sound works on the default
> audio device. Right now it does not work at all.
>
> # pcm-oss plugin configuration
>
> pcm.oss {
> type oss
> device /dev/dsp0
> hint {
> description "Open Sound System"
> }
> }
>
> ctl.oss {
> type oss
> device /dev/mixer0
> hint {
> description "Open Sound System"
> }
> }
>
>
> Best regards :-)
> Tomek
>
> --
> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
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"
9.1-RC3 default Linux ALSA configuration
Hello :-)
I have installed and started Skype (2.1 and 2.2 devel) with success
using Linux binaries provided in port tree. However there is an issue
with default ALSA configuration and sound/calls does not work properly
off out the box. I suggest to set /dev/dsp0 and /dev/mixer0 as default
devices in the alsa configuration, so the sound works on the default
audio device. Right now it does not work at all.
# pcm-oss plugin configuration
pcm.oss {
type oss
device /dev/dsp0
hint {
description "Open Sound System"
}
}
ctl.oss {
type oss
device /dev/mixer0
hint {
description "Open Sound System"
}
}
Best regards :-)
Tomek
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
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: Re-sizable UFS project
Btw. are there any projects to make UFS natively available (something like fs-driver for ExtFS) on platforms such as Windows, Linux, MacOS? It would be nice to have native UFS instead Ext2 as universal filesystem among these operating systems... :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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"
9.1-RC3 magicnum/mount/cam issue
Hello :-) I have installed 9.1-RC3 on my desktop. After installation I wanted to mount Ext2 drive but provided bad device name, I got error that magic number was invalid, but then I had to wait some time until CAM returned error status to get back to the shell. Is that correct? The drive is functional. Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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"
wifi + wpa_supplicant in 9.1-RC3
Hello :-) I have some problems with WiFi connectivity on my Dell Latitude E4310 laptop with Intel card. Very often connection is broken, although windows clients of the same network is working fine. I need to turn radio off and on, sometimes this does not help, I need to kill wpa_supplicant and start one by hand, so probably this is something related with wpa_supplicant. Anyone observed similar issues? Btw if WiFi N supported? Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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: sluggish X.org/Xfce behavior
On Tue, Nov 20, 2012 at 2:44 PM, Bernhard Fröhlich wrote: > Very interesting symptoms. I had the same until xf86-input-mouse was fixed > with the last update. The symptoms were reproducible when attaching an > USB mouse which caused all kind of weird X11 (re)drawing issues. Exactly, known issue with xorg-mouse and xorg configuration + hald + allowEmptyInput, see list archive for good explanation :-) Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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: 9.1-RC3 feels okay :-)
Yes, Hal is also required for other applications to detect hardware (i.e. KDE). This is pretty nice feature for desktop environment, maybe unwanted to embedded or dedicated system :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info On Nov 8, 2012 5:59 PM, "Richard Kuhns" wrote: > On 11/08/12 10:45, Warren Block wrote: > > On Thu, 8 Nov 2012, CeDeROM wrote: > > > >> I have tested additional options in xorg runtime :-) > >> > >> With the patched xorg mouse driver 1.7.1 (or driver version >=1.7.2) > >> situation is following: > >> > >> 1. With hald and dbus no xorg.conf file is needed. However it might bo > >> option to pass some additional featutes parameters with xorg.conf. > >> 2. With no hald and dbus mouse and keyboard does not work in xorg unless > >> Option "AllowEmptyInput" "False" is added to Section "ServerLayout" by > >> hand in xorg.conf. Without this option input does not work even if > >> xorg.conf defines it! AllowEmptyInput=False forces to detect input > deviced > >> by Xorg at startup. > > > > No. AllowEmptyInput is wrong. It was causing so many problems that it > > has been removed from later xorg-server releases. > > > > Option "AutoAddDevices" "Off" is the one that means "dont' use Hal to > > detect input devices". > > > >> Thank you for this hint! This could be added to the handbook :-) > >> AllowEmptyInput=False should be a default for Xorg IMO we can report it > to > >> the Xorg project! :-) > > > > Really, the simplest solution is to build xorg-server with the HAL > > option disabled. I agree that this should be the default. > > ___ > > 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" > > > > Just a comment: according to http://wiki.freebsd.org/VirtualBox, Hal is > still > required for VirtualBox in order to have host DVD/CD access. > > -- > Richard Kuhns My Desk: 765-269-8541 > Wintek Corporation Internet Support: 765-269-8503 > 427 N 6th Street STE C Consulting: 765-269-8504 > Lafayette, IN 47901-2211 Accounting: 765-269-8502 > ___ 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"
Failed to switch consoles in 9.0-RC3
Hello :-) When switching from Xorg (installed from package by portinstall) to console I got this bad behavior and constantly beeping speaker. On the console, when it switched, I got this message 3 times: Failed to switch console (Invalid agrument) There are no more messages or debug information to better describe the problem sorry... Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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: 9.1-RC3 feels okay :-)
I was using xorg from package so it is default configuration, which is built with Hal support because it can make use of it I guess... The more important thing is that Xorg starts without autodetecting input devices by default. Maybe this is caused by Hal support being compiled in. This might implict using Hal for devices detection and disabling detection by Xorg. Xorg detection can be enforced by disabling empty input in that case. Disabling empty input shloud be a default for Xorg IMO... Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info On Nov 8, 2012 10:01 AM, "Boris Samorodov" wrote: > 08.11.2012 12:46, CeDeROM пишет: > > > With no hald and dbus mouse and keyboard does not work in xorg > > Do you mean "that if xorg-server is compiled with hal but you do not > launch it at startup" mouse and keyboard does not work? If yes, I'd > say that this is a bit... expected. ;-) > > -- > WBR, Boris Samorodov (bsam) > FreeBSD Committer, http://www.FreeBSD.org The Power To Serve > ___ 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: 9.1-RC3 feels okay :-)
Hello :-) I have tested additional options in xorg runtime :-) With the patched xorg mouse driver 1.7.1 (or driver version >=1.7.2) situation is following: 1. With hald and dbus no xorg.conf file is needed. However it might bo option to pass some additional featutes parameters with xorg.conf. 2. With no hald and dbus mouse and keyboard does not work in xorg unless Option "AllowEmptyInput" "False" is added to Section "ServerLayout" by hand in xorg.conf. Without this option input does not work even if xorg.conf defines it! AllowEmptyInput=False forces to detect input deviced by Xorg at startup. Thank you for this hint! This could be added to the handbook :-) AllowEmptyInput=False should be a default for Xorg IMO we can report it to the Xorg project! :-) Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info On Nov 6, 2012 10:58 PM, "Julian H. Stacey" wrote: > Hi, > Reference: > > From: CeDeROM > > Date: Tue, 6 Nov 2012 22:14:03 +0100 > > Message-id:h8ga9vwme+trdng_kyjc...@mail.gmail.com> > > CeDeROM wrote: > > I have also noted that mouse cursor is very often not moving in Xorg > > but it works in the console! I need to move cursor while statrx or > > restart Xorg for mouse to start moving. Is it a bug or feature? :-) > > > > In the xorg.conf: > > Section "InputDevice" > > Identifier "Mouse0" > > Driver "mouse" > > Option "Protocol" "auto" > > Option "Device" "/dev/sysmouse" > > Option "ZAxisMapping" "4 5 6 7" > > EndSection > > Inside > Section "ServerLayout" > Just after > InputDevice"Mouse0" "CorePointer" > Append > Option "AllowEmptyInput" "False" > > Cheers, > Julian > -- > Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich > http://berklix.com > Reply below not above, like a play script. Indent old text with "> ". > Send plain text. Not: HTML, multipart/alternative, base64, > quoted-printable. > ___ > 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: 9.1-RC3 feels okay :-)
On Wed, Nov 7, 2012 at 9:39 AM, Boris Samorodov wrote: >> You may be interested in: >> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/171433 >> >> If the patch from the PR helps you, please submit a follow-up >> to the PR. > > Well, actually I've just committed an upstream patch to > x11-drivers/xf86-input-mouse. Please give it a try. I put this by hand into mouse.c: pInfo->options = dev->commonOptions; Yes it solves the issue! Thanks!! :-) According to the PR the 1.7.2 xorg-mouse driver has this fix, so I would strongly recommend to put 1.7.2 driver into a release, or use patch provided by Boris, otherwise users will have problems with mouse on default install. Best regards! :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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: 9.1-RC3 feels okay :-)
Isn't this a Xorg bug then? When I have no configuration file Hal should provide the configuration, so sooner or later the mouse should start moving... but is does not.. Do I get http://www.wonkity.com/~wblock/docs/html/aei.html correct that when I am using xorg.conf there is no need for Hal and when I am using Hal there is no need for xorg.conf? Thanks :-) Tomek On Nov 6, 2012 10:58 PM, "Julian H. Stacey" wrote: > Hi, > Reference: > > From: CeDeROM > > Date: Tue, 6 Nov 2012 22:14:03 +0100 > > Message-id:h8ga9vwme+trdng_kyjc...@mail.gmail.com> > > CeDeROM wrote: > > I have also noted that mouse cursor is very often not moving in Xorg > > but it works in the console! I need to move cursor while statrx or > > restart Xorg for mouse to start moving. Is it a bug or feature? :-) > > > > In the xorg.conf: > > Section "InputDevice" > > Identifier "Mouse0" > > Driver "mouse" > > Option "Protocol" "auto" > > Option "Device" "/dev/sysmouse" > > Option "ZAxisMapping" "4 5 6 7" > > EndSection > > Inside > Section "ServerLayout" > Just after > InputDevice"Mouse0" "CorePointer" > Append > Option "AllowEmptyInput" "False" > > Cheers, > Julian > -- > Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich > http://berklix.com > Reply below not above, like a play script. Indent old text with "> ". > Send plain text. Not: HTML, multipart/alternative, base64, > quoted-printable. > ___ > 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: 9.1-RC3 feels okay :-)
I have also noted that mouse cursor is very often not moving in Xorg but it works in the console! I need to move cursor while statrx or restart Xorg for mouse to start moving. Is it a bug or feature? :-) In the xorg.conf: Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/sysmouse" Option "ZAxisMapping" "4 5 6 7" EndSection -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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: 9.1-RC3 feels okay :-)
Okay, Ill try to build the kernel with debug symbols and provide backtrace if possible. The generic one provided with the distribution is stripped? Where can I find configuration for release kernel? :-) Thanks for all hints! :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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: 9.1-RC3 feels okay :-)
On Tue, Nov 6, 2012 at 5:10 PM, Adrian Chadd wrote: > Please file a bug about the intel wifi crash! Hello Adrian! :-) Should I attach kernel core dump / backtrace or simply write that "kernel crash on unstable wifi connection or when switching radio on and off multiple times or switching wpa_supplicant multiple times" is enough? :-) Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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"
9.1-RC3 feels okay :-)
Hello world! :-)
After big shock with new organization of 9.0 and some mobilization to
take part in RC I have tested 9.1-RC{1,2,3} and found no bigger issues
so far from user perspective :-)
Also the installation method is now more familiar than before as I got
used to it - its nice that message is shown in the partitioning
section to remove and create a partition to do a fresh install, which
is not obvious for at first contact.
I was using RC1 and RC2 on virtual machine, then installed RC3 in
place of my stable system on Dell Latitude E4310 laptop - with normal
usage and hard overload I can see no issues - ext2fs and zfs
partifions are working fine also when serving content for virtual
machines inside virtualbox-ose 4.1.22 :-)
The initial packages installation is hard because there is no 9.1
ports directory on the ftp servers to use, so I had to build
portupgrade and then install packages with portinstall -PP. Before I
was using pkg_add -r and portmaster (which is a bit worse than
portupgrade I think because it cannot find any binary packaged
itself). But the first impression is that there are no packages
available to install!
Also the relase notes documents still use 9.0 numbering...
Except some issues with current ports like xfce4 window manager does
not work properly (this might impact release binaries) and fusefs-kmod
does not build with ruby1.9 which are reported already, I might have
some wishlist for future:
It would be nice to have ext4 natively implemented in the kernel,
because ext2 still seems to be most multiplatform filesystem to share
partitions across different operating systems. Or another solution is
to port new UFS driver for Linux and Windows so we can use BSD
partitions and filesystems on them with no problem :-)
WiFi Intel driver crashed my system on 9.0, I hope its fixed :-)
It would be really good to have hardware graphics acceleration for
Intel X3400 chipsets, and the way it does not destroys the native
console because it is very useful for tracing problems...
If you have any particular requests to test some stuff on this
hardware let me know :-)
Thank you for your hard work! Best regards :-)
Tomek Cedro
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
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"
