You are not logged in.
The platform in question of course my Asus eeepc 1015PEM and the issue isn't likely to be coursed by me making a mistake, though I may have misinterpreted what the stock network daemon is all about.
During boot I get this message:
:: Starting network
[ 5.616800] ieee8011 phy0: brcms_ops_bss_info_changed: qos enabled: false (implement)
[ 5.620882] ieee8011 phy0: brcms_ops_config: change power-save mode: false (implement)All I know is that it has something to do with my wireless, as it goes away when I disable it in BIOS, and that I haven't had this issue with previous arch installation, only with the latest release and possibly with the one just before that, which I didn't mess around with.
As far as I know the stock network daemon can't handle wireless devices, so it does confuse me a bit.
Apart from that, the wireless seem to work as it used to, but I can't confirm it as I haven't had a chance to test it.
Also this is a more or less clean install and I've done very little to begin setting up the wireless.
Well, all that doesn't matter anyway, I'd simply like to know what those two lines mean and how to get rid of them.
Best regards.
Last edited by zacariaz (2012-08-22 16:51:35)
I am a philosopher, of sorts, not a troll or an imbecile.
My apologies that this is not always obvious, despite my best efforts.
Offline
Well, which wireless driver are you using? brcmsmac? b43? etc. Try checking out the Archwiki page for Broadcomm
Team Ignition Kernel Developer
linux-ideapad developer/maintainer
Flame Kernel developer for Galaxy Nexus and Galaxy S3
Want a cheap, reliable VPS with AWESOME customer service?
Offline
IF what the wiki states is true, then brcmsmac is the correct driver for BCRM4313 and should also be autoloaded. I'm not exactly sure how to investigate if this is true, but I can find no obvious flaws other than those two annoying lives during boot.
I suppose the'll disappear when I change the network daemon to networkmanager or similar, I don't know, but it doesn't change the fact that I haven't got a clue what those two lines mean.
I am a philosopher, of sorts, not a troll or an imbecile.
My apologies that this is not always obvious, despite my best efforts.
Offline
They won't disappear by changing the network daemon, as they're printed when the brcmsmac driver loads. Which is done by udev. That the messages appear right after the network daemon loads is pure coincidence. I don't think the messages indicate a problem, it's just the brcmsmac driver being a bit too chatty. Try adding loglevel=3 to the kernel line in the grub config (or the append line if you use syslinux or lilo).
Last edited by Gusar (2012-08-22 17:08:05)
Offline
Two points to be made:
1. once it complained about bluetooth just after installing E17, but the message was never repeated upon further reboots.
2. loglevel=3 ensures that I do not see the two (maybe 3) line, which is nice, though I'd prefer another solution.
Anyway, thanks for the help.
I am a philosopher, of sorts, not a troll or an imbecile.
My apologies that this is not always obvious, despite my best efforts.
Offline
loglevel=3 ensures that I do not see the two (maybe 3) line, which is nice, though I'd prefer another solution.
Hack the driver, change the level at which those messages are printed. That's the only other solution.
Offline
Probably way off here but if I do a "modinfo" on (e.g.) snd-hda-intel, a load of "parms" get displayed - I could use those in /etc/modprobe.d/* files. However "modinfo brcmsmac" has no parm settings, so I reckon those messages must be coming from some other wireless module?
Last edited by vacant (2012-08-22 19:11:04)
Offline
I don't know too much about these matter, but as far as I'm aware the Asus eeepc 1015PEM only included two wireless devices, wifi and bt.
I am a philosopher, of sorts, not a troll or an imbecile.
My apologies that this is not always obvious, despite my best efforts.
Offline