Re: Firefox problem...another newbie question
It seems that there is some problem with your glib. You might need to upgrade it. Note that portupgrade isn't working for glib/gtk 2.8.x upgrade. You need to use gnome_upgrade212.sh instead, check /usr/ports/UPDATING for details. cheers, --ken On 10/11/05, makisupa <[EMAIL PROTECTED]> wrote: > > Been messing with FreeBSD for a week and a half or so now. Getting my > laptop all setup to play DVDs and something wierd happened to Firefox > (probably unrelated I know). As an aside, xine works well but i'm > not a fan of the gui, gxine core dumps a few seconds after going > fullscreen or toggling a couple of times. They use the same engine > right? Wierd...both installed from recently upgraded ports tree on a > gnome 2.12 6.0-beta5 system. The firefox problem... > > I can replicate this as at will and epiphany works fine. If i click > a .tbz file or something that calls another app and i get a core dump. > Any ideas what's going on here? > > $ firefox > > (Gecko:1985): GLib-CRITICAL **: g_hash_table_lookup: assertion > `hash_table != NU LL' failed > > (Gecko:1985): libgnomevfs-WARNING **: Internal error: the configuration > system w as not initialized. Did you call _gnome_vfs_configuration_init? > > (Gecko:1985): GLib-CRITICAL **: g_hash_table_lookup: assertion > `hash_table != NU LL' failed > > (Gecko:1985): libgnomevfs-WARNING **: Internal error: the configuration > system w as not initialized. Did you call _gnome_vfs_configuration_init? > > (Gecko:1985): GLib-CRITICAL **: g_hash_table_lookup: assertion > `hash_table != NU LL' failed > > (Gecko:1985): libgnomevfs-WARNING **: Internal error: the configuration > system w as not initialized. Did you call _gnome_vfs_configuration_init? > > (Gecko:1985): GLib-CRITICAL **: g_hash_table_lookup: assertion > `hash_table != NU LL' failed > > (Gecko:1985): libgnomevfs-WARNING **: Internal error: the configuration > system w as not initialized. Did you call _gnome_vfs_configuration_init? > > (Gecko:1985): GLib-CRITICAL **: g_hash_table_lookup: assertion > `hash_table != NU LL' failed > > (Gecko:1985): libgnomevfs-WARNING **: Internal error: the configuration > system w as not initialized. Did you call _gnome_vfs_configuration_init? > > (Gecko:1985): GLib-CRITICAL **: g_hash_table_lookup: assertion > `hash_table != NU LL' failed > > (Gecko:1985): libgnomevfs-WARNING **: Internal error: the configuration > system w as not initialized. Did you call _gnome_vfs_configuration_init? > > (Gecko:1985): GLib-CRITICAL **: g_hash_table_lookup: assertion > `hash_table != NU LL' failed > > (Gecko:1985): libgnomevfs-WARNING **: Internal error: the configuration > system w as not initialized. Did you call _gnome_vfs_configuration_init? > > (Gecko:1985): GLib-CRITICAL **: g_hash_table_lookup: assertion > `hash_table != NU LL' failed > > (Gecko:1985): libgnomevfs-WARNING **: Internal error: the configuration > system w as not initialized. Did you call _gnome_vfs_configuration_init? > > (Gecko:1985): GLib-CRITICAL **: g_hash_table_lookup: assertion > `hash_table != NU LL' failed > > (Gecko:1985): libgnomevfs-WARNING **: Internal error: the configuration > system w as not initialized. Did you call _gnome_vfs_configuration_init? > > (Gecko:1985): GLib-CRITICAL **: g_hash_table_lookup: assertion > `hash_table != NU LL' failed > > (Gecko:1985): libgnomevfs-WARNING **: Internal error: the configuration > system w as not initialized. Did you call _gnome_vfs_configuration_init? > > (Gecko:1985): GLib-CRITICAL **: g_hash_table_lookup: assertion > `hash_table != NU LL' failed > > (Gecko:1985): libgnomevfs-WARNING **: Internal error: the configuration > system w as not initialized. Did you call _gnome_vfs_configuration_init? > > (Gecko:1985): GLib-CRITICAL **: g_hash_table_lookup: assertion > `hash_table != NU LL' failed > > (Gecko:1985): libgnomevfs-WARNING **: Internal error: the configuration > system w as not initialized. Did you call _gnome_vfs_configuration_init? > > (Gecko:1985): GLib-CRITICAL **: g_hash_table_lookup: assertion > `hash_table != NU LL' failed > > (Gecko:1985): libgnomevfs-WARNING **: Internal error: the configuration > system w as not initialized. Did you call _gnome_vfs_configuration_init? > > (Gecko:1985): GLib-CRITICAL **: g_hash_table_lookup: assertion > `hash_table != NU LL' failed > > (Gecko:1985): libgnomevfs-WARNING **: Internal error: the configuration > system w as not initialized. Did you call _gnome_vfs_configuration_init? > > (Gecko:1985): GLib-CRITICAL **: g_hash_table_lookup: assertion > `hash_table != NU LL' failed > > (Gecko:1985): libgnomevfs-WARNING **: Internal error: the configuration > system w as not initialized. Did you call _gnome_vfs_configuration_init? > > (Gecko:1985): GLib-CRITICAL **: g_hash_table_lookup: assertion > `hash_table != NU LL' failed > > (Gecko:1985): libgnomevfs-WARNING **: Internal error: the configuration > system w as not initialized. Did you call _gnome_vfs_configuration_init? > > (Gecko:1985): GLib-CRITICAL **: g_hash_table
Re: GNOME Upgrade on a non-GNOME Machine
Yes. I did it a few days as /usr/ports/UPDATING suggests. It worked but it took too much time (1.5 days). This is because a lot packages depend on glib and gtk, so they have to be upgraded as well. I am just wondering if there is any way to accerlerate the process. cheers, --ken On 11/11/05, Robert H. Perry <[EMAIL PROTECTED]> wrote: > > I have a box which needs to upgrade gconf, glib, gnomevfs, and gtk based > on the latest CVSup. Just want to confirm that I should still run the > gnome_upgrade.sh even though GNOME itself is not installed. > > Thnx, > Bob Perry > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > [EMAIL PROTECTED]" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Re[2]: install freebsd with usb keyboard
Thanks you for all your suggestions! I'll burn a 5.4 cd then. cheers, --ken On 6/14/05, Daniel Gerzo <[EMAIL PROTECTED]> wrote: > > Hello Kan, > > Tuesday, June 14, 2005, 11:05:20 PM, you wrote the following: > > > Thanks, Paul. What you meant is that I should choose option 7 when the > > beastie menu pops up, right? I am not sure which FreeBSD release could > do > > that. In my 5.2.1 and 5.3R1, the option 7 is "reboot". Is that in 5.4? > > Well, I'm not sure if that exists in < 5.4 but there is an option > called "Boot FreeBSD with USB keyboard" or similar in 5.4. I was > installing 5.4 on Dell gx280, which doesn't have any PS/2 ports so it > is possible to use only USB keyboard (that really sucks btw.), some > time ago. > > > thanks a lot, > > --ken > > > On 6/14/05, Paul Schmehl <[EMAIL PROTECTED]> wrote: > >> > >> --On Monday, June 13, 2005 22:16:38 -0700 Kan Cai <[EMAIL PROTECTED]> > >> wrote: > >> > >> > Hi, Paul: > >> > > >> > Thanks for the reply, but it didn't work. I tried 3 keyboards and 2 > >> > FreeBSD releases (5.2.1, and 5.3R1). The combination of logitech > >> keyboard > >> > with 5.2.1 does highlight the keymap option in sysinstall menu, but > that > >> > is how far it goes. The keyboard stops working so that I cannot press > >> > "space", "tab" or "enter". > >> > > >> I'm not sure I explained myself clearly. Let's try again. > >> > >> ***During the boot process* before you ever get to sysinstall, when > >> the > >> daemon shows up on the screen and you're given a menu with several > >> options, > >> if you look closely, option seven (7) must be chosen to use a usb > keyboard > >> **during the install**. > >> > >> If you're waiting until the sysinstall appears, that's way too late. > You > >> need to chose option 7 before the kernel even loads, almost immediately > >> after the system boots. > >> > >> If you *are* doing that and the keyboards aren't working anyway, then I > >> have no idea what the problem might be. > >> > > -- > Best Regards, > > DanGer, ICQ: 261701668 | e-mail protecting at: http://www.2pu.net/ > http://danger.rulez.sk | proxy list at: http://www.proxy-web.com/ > | FreeBSD - The Power to Serve! > > [ "They've got us surrounded. The poor bastards." ] > > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: install freebsd with usb keyboard
Thanks, Paul. What you meant is that I should choose option 7 when the beastie menu pops up, right? I am not sure which FreeBSD release could do that. In my 5.2.1 and 5.3R1, the option 7 is "reboot". Is that in 5.4? thanks a lot, --ken On 6/14/05, Paul Schmehl <[EMAIL PROTECTED]> wrote: > > --On Monday, June 13, 2005 22:16:38 -0700 Kan Cai <[EMAIL PROTECTED]> > wrote: > > > Hi, Paul: > > > > Thanks for the reply, but it didn't work. I tried 3 keyboards and 2 > > FreeBSD releases (5.2.1, and 5.3R1). The combination of logitech > keyboard > > with 5.2.1 does highlight the keymap option in sysinstall menu, but that > > is how far it goes. The keyboard stops working so that I cannot press > > "space", "tab" or "enter". > > > I'm not sure I explained myself clearly. Let's try again. > > ***During the boot process* before you ever get to sysinstall, when > the > daemon shows up on the screen and you're given a menu with several > options, > if you look closely, option seven (7) must be chosen to use a usb keyboard > **during the install**. > > If you're waiting until the sysinstall appears, that's way too late. You > need to chose option 7 before the kernel even loads, almost immediately > after the system boots. > > If you *are* doing that and the keyboards aren't working anyway, then I > have no idea what the problem might be. > > Paul Schmehl ([EMAIL PROTECTED]) > Adjunct Information Security Officer > University of Texas at Dallas > AVIEN Founding Member > http://www.utdallas.edu/ir/security/ > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: install freebsd with usb keyboard
Hi, Paul: Thanks for the reply, but it didn't work. I tried 3 keyboards and 2 FreeBSD releases (5.2.1, and 5.3R1). The combination of logitech keyboard with 5.2.1does highlight the keymap option in sysinstall menu, but that is how far it goes. The keyboard stops working so that I cannot press "space", "tab" or "enter". I would appreciate any further suggestions. Otherwise, I have to go for Vizion's solder-wire suggestions. cheers, --ken On 6/13/05, Paul Schmehl < [EMAIL PROTECTED]> wrote: > > --On June 13, 2005 6:42:03 PM -0700 Kan Cai < [EMAIL PROTECTED]> wrote: > > > > I have been trying to install FreeBSD with a usb keyboard (I have > > tried 3 keyboards so far), but no success. It seems that it can > > recognize the device correctly (because it prints out the device names > > precisely when bringing up the usbs), but it freezes right after the > > sysinstall menu comes out. The ps2 plug is broken, so I dont have any > > other choice. > > > > I have searched the google and mail list. One suggestion was to > > change the BIOS setting WRT the legacy usb option. The other is to set > > hint.atkbd.0.flags="0x1" while booting. But the problem is that the > > keyboard doesn't work so that I cannot type anything or enter the > > BIOS. > > > > Is there anything I can do except hammering my box? > > > As a matter of fact there is. You could pay attention when the system is > booting and press the seven (7) key when prompted so your keyboard will be > > recognized for install purposes. > > Paul Schmehl ([EMAIL PROTECTED]) > Adjunct Information Security Officer > University of Texas at Dallas > AVIEN Founding Member > http://www.utdallas.edu/ > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > [EMAIL PROTECTED]" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: install freebsd with usb keyboard
Hi, Thanks for the reply. But, as I said, the keyboard PS2 plugin of my mobo is *physically* broken. So even with a usb->ps2 adapter, it won't work. Any other suggestions? cheers, --ken On 6/13/05, Vizion <[EMAIL PROTECTED]> wrote: > > On Monday 13 June 2005 18:42, the author Kan Cai contributed to the > dialogue > on- > install freebsd with usb keyboard: > > >Hi, there: > > > >I have been trying to install FreeBSD with a usb keyboard (I have > >tried 3 keyboards so far), but no success. It seems that it can > >recognize the device correctly (because it prints out the device names > >precisely when bringing up the usbs), but it freezes right after the > >sysinstall menu comes out. The ps2 plug is broken, so I dont have any > >other choice. > > > >I have searched the google and mail list. One suggestion was to > >change the BIOS setting WRT the legacy usb option. The other is to set > >hint.atkbd.0.flags="0x1" while booting. But the problem is that the > >keyboard doesn't work so that I cannot type anything or enter the > >BIOS. > > > >Is there anything I can do except hammering my box? > > How about a usb to ps2 adapter for a couple of dollars from your favorite > computer store? > David > > > -- > 40 yrs navigating and computing in blue waters. > English Owner & Captain of British Registered 60' bluewater Ketch S/V > Taurus. > Currently in San Diego, CA. Sailing May/June bound for Europe via Panama > Canal. > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
install freebsd with usb keyboard
Hi, there: I have been trying to install FreeBSD with a usb keyboard (I have tried 3 keyboards so far), but no success. It seems that it can recognize the device correctly (because it prints out the device names precisely when bringing up the usbs), but it freezes right after the sysinstall menu comes out. The ps2 plug is broken, so I dont have any other choice. I have searched the google and mail list. One suggestion was to change the BIOS setting WRT the legacy usb option. The other is to set hint.atkbd.0.flags="0x1" while booting. But the problem is that the keyboard doesn't work so that I cannot type anything or enter the BIOS. Is there anything I can do except hammering my box? thanks in advance, --ken ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
any open wireless firmware project for FreeBSD?
Greetings all: I am just wondering if there is ANY open wireless firmware project under FreeBSD, like OpenWrt project for Linksys WRT54G under Linux. Thanks in advance. cheers, --ken ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Dual Boot -- FreeBSD 5.4 and Fedora Core 3
Greetings all: I tried to install Fedora Core 3 to my FreeBSD box and make it dual boot, but with no luck. The FreeBSD 5.4-Pre is installed in the first drive, and work like a champ. I intended to install Fedora Core 3 on my second disk, but anaconda crashed at the last moment. The first few lines of the dumped trace look as follows. Also, should I enable GRUB when installing Fedora, or should I enable it on hdb1? I am afraid that it ends up failing to boot my FreeBSD partition. Any suggestion and help on this will be most appreciated. thanks and cheers, --ken --- Traceback (most recent call last): File "/usr/src/build/475969-i386/install//usr/lib/anaconda/gui.py", line 1074, in handleRenderCal lback self.currentWindow.renderCallback() File "/usr/src/build/475969-i386/install//usr/lib/anaconda/iw/progress_gui.py", line 242, in rend erCallback self.intf.icw.nextClicked() File "/usr/src/build/475969-i386/install//usr/lib/anaconda/gui.py", line 789, in nextClicked self.dispatch.gotoNext() File "/usr/src/build/475969-i386/install//usr/lib/anaconda/dispatch.py", line 171, in gotoNext self.moveStep() File "/usr/src/build/475969-i386/install//usr/lib/anaconda/dispatch.py", line 239, in moveStep rc = apply(func, self.bindArgs(args)) File "/usr/src/build/475969-i386/install//usr/lib/anaconda/packages.py", line 1155, in doPostInst all stdout = devnull) File "/usr/lib/anaconda/iutil.py", line 53, in execWithRedirect raise RuntimeError, command + " can not be run" RuntimeError: /usr/sbin/kudzu can not be run - ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD 4.11-RELEASE & SACK
Greetings, I've installed the standard FreeBSD 4.11-RELEASE and have realized that the sysctl option for enabling SACK in TCP is not available (net.inet.tcp.do_sack). Additionally, the tcp_sack.c file is not in the /usr/src/sys/netinet so I'm guessing this indicates that I need a patch. Hoping to be able to use SACK in FreeBSD 4.11-RELEASE, I wanted to ask : 1) Is my guess correct (Do I need a patch)? Or is my kernel configuration file missing an option? 2) Assuming I need a patch, what patch is generally recommended for using SACK under TCP in FreeBSD 4.11-RELEASE? Any help would be most appreciated. Thanks, ken ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gaim and MSN
Yeah, it works, but there is another problem. When I try to log on, I got "error reading from server". Anything wrong with it? I am sure that the password is right. ;) Thanks a lot for the suggestions. cheers, --ken On Wed, 22 Oct 2003, Joe Marcus Clarke wrote: > On Tue, 2003-10-21 at 22:31, Kan Cai wrote: > > Hi, All: > > > > I am installing gaim 0.71. Everything goes fine, but it seems that there > > is some problem with MSN lib. > > > > Whe I start it, I got plug-in error on finding MSN lib. I didn't install > > it actually, did I? > > > > I have installed Mozilla 1.4, but it seems that it is not able to make > > the SSL option on. Shall I specify the location, and how? Is there anybody > > can help me on this? > > If you're installing gaim from ports, SSL will be enabled > automatically. Just make sure you have the port 0.71_5, and you'll be > set. > > Joe > > > > > Thanks a lot in advance. > > > > Cheers, > > ken > > > > ___ > > [EMAIL PROTECTED] mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- > PGP Key : http://www.marcuscom.com/pgp.asc > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
gaim and MSN
Hi, All: I am installing gaim 0.71. Everything goes fine, but it seems that there is some problem with MSN lib. Whe I start it, I got plug-in error on finding MSN lib. I didn't install it actually, did I? I have installed Mozilla 1.4, but it seems that it is not able to make the SSL option on. Shall I specify the location, and how? Is there anybody can help me on this? Thanks a lot in advance. Cheers, ken ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Toshiba 490XCDT
hi, all: I have a TOSHIBA 490XCDT and try to install freebsd 5.0 on it. Everything goes smoothly but the vga card. The X server cannot use the full screen and totally useless when I start KDE or Gnome. I use dmesg and see the following: vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: can't assign resources (port) unknown: can't assign resources (irq) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) Is there anybody can help me with this? Thanks a lot, Cheers, ken ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: the CPU interrupt handler
On Fri, 4 Apr 2003, Terry Lambert wrote: > Kan Cai wrote: > > I am trying to locate the CPU interrupt handler, but with no luck. I > > guess it is somewhere in the "1386" folder, but not sure which file is > > doing the job. Could someone there shed some lights on this? > > > > Since I am trying to capture the NIC interrupts, so it should not be > > exceptions. Thanks a lot. > > You need to look at an existing NIC driver to see how it > grabs interrupts. The functions you are probably interested > in are bus_setup_intr() and bus_teardown_intr(). > > If you are trying to do this in an evil, i386 way, because you > want to intercept the interrupt path for some legitimate > instrumentation purpose, or because you have some wrong idea > that this will make your networking product run faster, then > you could do worse than to look at the functions "inthand_*" > in /usr/src/sys/i386/isa/intr_machdep.c. Thanks a lot for this info, but I guess I didn't express myself clearly. The real goal of mine is to insert a timer into where the processor gets interrupted, switches the context, and finally calls the corresponding handlers. After reading the intr_machdept.c, I am kinda doubt that it is the right file I should focus, it mainly does the setup and remove entries in GDT and IDT, doesn't it? I found that in "apic_vector.s", there is a function called "INTR", is that true that I should put my timer in this function? Any related info is highly appreciated. Cheers, ken > > -- Terry > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
the CPU interrupt handler
Hi, all: I am trying to locate the CPU interrupt handler, but with no luck. I guess it is somewhere in the "1386" folder, but not sure which file is doing the job. Could someone there shed some lights on this? Since I am trying to capture the NIC interrupts, so it should not be exceptions. Thanks a lot. Have a nice day! Cheer, ken ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
X11 remote connection problem
Hey, all I know this question seems dumb, but it really screws me a lot. Following the handbook, I tried to make my remote X connection work, but with no luck. Here is the error message. #setenv DISPLAY my_machine:0.0 #>gvim Xlib: connection to "my_machine:0.0" refused by server Xlib: Invalid MIT-MAGIC-COOKIE-1 key E233: cannot open displayXlib: connection to "my_machine:0.0" refused by server Xlib: Invalid MIT-MAGIC-COOKIE-1 key I guess it is because I am using KDM instead XDM, so that the handbook instruction doesn't work. I am wondering if someone could instruct me a good reference page. I am using FreeBSD 4.7, KDE 3.0. Thanks for any information about this. Cheers, Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
ibss-master
Hi, All: Just wonder what's the real function of ibss-master? It is only to decide the SSID for all the peers, or ...? Defaultly, is it true that every Linux wireless station creates ibss defaultly? Thanks a lot for any help. Cheers, Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: ad-hoc wireless mode and ticks (fwd)
On Wed, 5 Mar 2003, Eko Suwarsono wrote: > > Hi Warner, > > What kind of version that orinoco's firmware can support > ibss-master mode ? > Last time I change the wi0 (Orinoco) mode to "ibss-master" was "ifconfig: > SIOCSIFMEDIA: Device not configured" I am using Lucent Firmware: Station 8.72.01, and it can support ibss-master mediaopt, but it seems not supporting ibss-create yet. --Ken > but when using Senao Prism Based Card, it's work fine for "hostap" and > "ibss-master". > > Regards, > > Eko Suwarsono > - > [EMAIL PROTECTED] > > - Original Message - > From: "M. Warner Losh" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; > <[EMAIL PROTECTED]> > Sent: Tuesday, March 04, 2003 9:20 PM > Subject: Re: ad-hoc wireless mode and ticks (fwd) > > > > In message: <[EMAIL PROTECTED]> > > "Eko Suwarsono" <[EMAIL PROTECTED]> writes: > > : May be help, > > : > > : http://www.live.com/wireless/unix-base-station.html > > : > > : and a little explanation you can read at, > > : > > : http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/wireless.html > > : > > : Lucent (Orinoco / avaya) base wireless Card will not work for "hostap" > or > > : "ibss-master" mode. To have your own FreeBSD host based Access point, > you > > : must using Prism II or 2.5 Card. > > > > That's not true. Lucent cards *WILL* work as ibss-masters if their > > firmware is new enough. > > > > Warner > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: ad-hoc wireless mode and ticks (fwd)
Hope Greg won't mind we still discuss here. On Mon, 3 Mar 2003, Jason Hunt wrote: > On Mon, Mar 03, 2003 at 08:10:18PM -0800, Kan Cai wrote: > > > > But when I set the option "mediaopt ibss", I cannot set it back to the AP > > mode, or how should I (the ibss-master? it does not work for me)?. I do > > not want this wireless station to be the hostAP itself. > > > > What commands are you running? What errors do you receive? Here is the steps. Step 1 -- " # ifconfig wi0 ssid myessid mediaopt ibss # wicontrol NIC serial number: [ 03UT04368383 ] Station name: [ FreeBSD WaveLAN/IEEE node ] SSID for IBSS creation: [ myessid ] Current netname (SSID): [ myessid ] Desired netname (SSID): [ myessid ] Current BSSID: [ 44:44:44:44:44:44 ] Channel list: [ 2047 ] IBSS channel: [ 10 ] Current channel:[ 10 ] Comms quality/signal/noise: [ 0 27 27 ] Promiscuous mode: [ Off ] Process 802.11b Frame: [ Off ] Intersil-Prism2 based card: [ 0 ] Port type (1=BSS, 3=ad-hoc):[ 4 ] MAC address:[ 00:02:2d:8d:a9:a0 ] TX rate (selection):[ 3 ] TX rate (actual speed): [ 11 ] RTS/CTS handshake threshold:[ 2347 ] Create IBSS:[ Off ] Access point density: [ 1 ] Power Mgmt (1=on, 0=off): [ 0 ] Max sleep time: [ 100 ] WEP encryption: [ Off ] TX encryption key: [ 1 ] Encryption keys:[ ][ ][ ][ ] " The above info shown by wicontrol is same to that uses "-p 4" " # ifconfig fxp0: flags=8843 mtu 1500 inet6 fe80::202:b3ff:fe4d:d16%fxp0 prefixlen 64 scopeid 0x1 inet 142.103.10.99 netmask 0xff00 broadcast 142.103.10.255 ether 00:02:b3:4d:0d:16 media: Ethernet autoselect (100baseTX ) status: active lp0: flags=8810 mtu 1500 lo0: flags=8049 mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff00 ppp0: flags=8010 mtu 1500 sl0: flags=c010 mtu 552 faith0: flags=8002 mtu 1500 wi0: flags=8843 mtu 1500 inet6 fe80::202:2dff:fe8d:a9a0%wi0 prefixlen 64 scopeid 0x7 inet 142.103.240.47 netmask 0xf800 broadcast 142.103.247.255 ether 00:02:2d:8d:a9:a0 media: IEEE 802.11 Wireless Ethernet autoselect (DS/11Mbps ) status: associated " The ifconfig shows a little difference in media, previously it was " media: IEEE 802.11 Wireless Ethernet autoselect (DS/11Mbps ) " no first "ibss" after the autoselect. Step 2: -- and now if I have no idea how to set back to infrastructured mode by ifconfig, or I don't know the right way to do. I attempted to use ibss-master or hostap, although I don't think they are correct. " # ifconfig wi0 mediaopt ibss-master ifconfig: SIOCSIFMEDIA: Device not configured " Step 3: --- Then I tried using wicontrol command " # wicontrol -p 1 # wicontrol NIC serial number: [ 03UT04368383 ] Station name: [ FreeBSD WaveLAN/IEEE node ] SSID for IBSS creation: [ myessid ] Current netname (SSID): [ myessid ] Desired netname (SSID): [ myessid ] Current BSSID: [ 44:44:44:44:44:44 ] Channel list: [ 2047 ] IBSS channel: [ 10 ] Current channel:[ 10 ] Comms quality/signal/noise: [ 0 27 27 ] Promiscuous mode: [ Off ] Process 802.11b Frame: [ Off ] Intersil-Prism2 based card: [ 0 ] Port type (1=BSS, 3=ad-hoc):[ 1 ] MAC address:[ 00:02:2d:8d:a9:a0 ] TX rate (selection):[ 3 ] TX rate (actual speed): [ 11 ] RTS/CTS handshake threshold:[ 2347 ] Create IBSS:[ Off ] Access point density: [ 1 ] Power Mgmt (1=on, 0=off): [ 0 ] Max sleep time: [ 100 ] WEP encryption: [ Off ] TX encryption key: [ 1 ] Encryption keys:[ ][ ][ ][ ] # ifconfig fxp0: flags=8843 mtu 1500 inet6 fe80::202:b3ff:fe4d:d16%fxp0 prefixlen 64 scopeid 0x1 inet 142.103.10.99 netmask 0xff00 broadcast 142.103.10.255 ether 00:02:b3:4d:0d:16 media: Ethernet autoselect (100baseTX ) status: active lp0: flags=8810 m
Re: ad-hoc wireless mode and ticks (fwd)
Thanks for reply.
> > But if I set it to "-p 4", it can do the job. However, I cannot find
> > this option in wicontrol man page or anywhere. Could somebody
> > explain me what's going on here?
>
> I don't know a -p 4. I set ad-hoc (i.e. IBSS) mode with -p 1 (in
> other words, exactly the same way as managed/BSS mode). You'll need
> at least one IBSS, of course. Set that with -c 1. Ignore the claim
> in the man page that it doesn't work. I run my wireless network like
> this, and it interoperates fine with Linux and even Microsoft. See
> http://www.lemis.com/grog/diary-feb2002.html#9 for more details.
>
That is really interesting, does that mean that the FreeBSD wireless
station has to fake a base station in order to make it work? and cannot
join the current available IBSS(es) by specifying the essid? Is that
implemented by the "unleashed" -p 4 option?
Here is the parameters I got using -p 4
NIC serial number: [ 03UT04368383 ]
Station name: [ FreeBSD WaveLAN/IEEE node ]
SSID for IBSS creation: [ myessid ]
Current netname (SSID): [ myessid ]
Desired netname (SSID): [ myessid ]
Current BSSID: [ 44:44:44:44:44:44 ]
Channel list: [ 2047 ]
IBSS channel: [ 10 ]
Current channel:[ 10 ]
Comms quality/signal/noise: [ 0 27 27 ]
Promiscuous mode: [ Off ]
Process 802.11b Frame: [ Off ]
Intersil-Prism2 based card: [ 0 ]
Port type (1=BSS, 3=ad-hoc):[ 4 ]
MAC address:[ 00:02:2d:8d:a9:a0 ]
TX rate (selection):[ 3 ]
TX rate (actual speed): [ 11 ]
RTS/CTS handshake threshold:[ 2347 ]
Create IBSS:[ Off ]
Access point density: [ 1 ]
Power Mgmt (1=on, 0=off): [ 0 ]
Max sleep time: [ 100 ]
WEP encryption: [ Off ]
TX encryption key: [ 1 ]
Encryption keys:[ ][ ][ ][ ]
See the "Create IBSS" if off now.
> Yes, this is very confusing. I've been asking the maintainer to
> change the terminology, but he points out that the other BSDs do it
> this way as well.
>
> > Moreover, could somebody give me a hint what is the corresponding
> > function in FreeBSD like "rdtscl" function in Linux, which returns me the
> > cpu ticks elapsed?
>
> This looks like a completely separate question, probably one which is
> off-topic for -mobile. Can you give context, or better, send another
> message to -questions.
>
Sorry for the off-topic question. But just for those interested, here is
the probable answer:
asm volatile(".byte 0x0f, 0x31" : "=A" (tstart));
asm volatile(".byte 0x0f, 0x31" : "=A" (tend));
Again, thanks a lot, and hope more clarifications.
--Ken
> Greg
> --
> See complete headers for address and phone numbers
> Please note: we block mail from major spammers, notably yahoo.com.
> See http://www.lemis.com/yahoospam.html for further details.
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
ad-hoc wireless mode and ticks
Hi, All: Feel a little confused with the ad-hoc mode set by "wicontrol -p 3", is it Lucent ad-hoc mode instead of the standard IEEE ad-hoc mode (IBSS). After I use "-p 3" option, it cannot talk to Linux/Windows ad-hoc wireless station. But if I set it to "-p 4", it can do the job. However, I cannot find this option in wicontrol man page or anywhere. Could somebody explain me what's going on here? Moreover, could somebody give me a hint what is the corresponding function in FreeBSD like "rdtscl" function in Linux, which returns me the cpu ticks elapsed? Thanks a lot, Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
power monitoring API
Hi, greetings all: Is there any way (API or Macros) provided by FreeBSD that can monitor power consumption? I would like to check how much energy consumed by some operation (for example, sending a package). Any suggestions on this are appreciated. Cheers, Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
