 probably go for the driver if you know which one it is
<oly> yeah still happened,
<oly> not sure on the driver, its likely loading the wrong one
<oly> as looks like theris still no driver file for this sound card
<ali1234> check the system logs
<oly> will report a bug i can see a kernel oops in the logs when i go back to the older kernel
<bigcalm> popey: the later
<popey> bigcalm: thats been the case for years
<popey> add a cronjob to sudo rfkill blah to shut it down â»
<ali1234> or disable in the bios
<popey> bug 922375
<popey> hmm
<lubotu3> bug 922375 in gnome-bluetooth (Ubuntu) "Bluetooth indicator will not stay turned off after reboot" [Low,Fix released] https://launchpad.net/bugs/922375
<ali1234> rfkill is supposed to save state and restore at the next boot, like alsa does with volume
<popey> ah
<ali1234> at least i think it is
<ali1234> maybe the udev rule got broken recently, like the alsa one did
<ali1234> bug 1268301
<lubotu3> bug 1268301 in alsa-utils (Ubuntu) "udev alsa restore restore rules are broken" [Undecided,Fix released] https://launchpad.net/bugs/1268301
<bigcalm> popey: funky
<ali1234> or maybe it doesn't work anything like that, i dunno
<ali1234> ah here we go: /var/lib/rfkill/saved-state
<ali1234> and /etc/init/rfkill-store.conf and -restore.conf
<ali1234> does not appear to use udev
<oly> that sounds a bit like the issue i am hitting
<ali1234> nah, you have an oops :)
<ali1234> show oops pls
<oly> um one sec need to setup ssh on the other maching
<ali1234> the alsa udev thing doesn't get fixed by swapping kernels either, it's caused because the udev rules changed, and the way they are parsed is quite complex, so changes in an
probably go for the driver if you know which one it is 
 < oly > yeah still happen, 
 < oly > not certain on the driver, its likely loading the wrong one 
 < oly > as look like theris still no driver file for this sound menu 
 < ali1234 > discipline the system log 
 < oly > will report a bug i can see a kernel oops in the log when i go back to the older kernel 
 < bigcalm > popey: the late 
 < popey > bigcalm: that s been the shell for years 
 < popey > add a cronjob to sudo rfkill blah to shut it down â » 
 < ali1234 > or disable in the bios 
 < popey > bug 922375 
 < popey > hmm 
 < lubotu3 > hemipterous insect 922375 in gnome - bluetooth (Ubuntu) " Bluetooth indicator will not stay turned off after reboot " [ Low, Fix released ] https://launchpad.net/bugs/922375 
 < ali1234 > rfkill is presuppose to save state and restore at the next bang, like alsa does with volume 
 < popey > ah 
 < ali1234 > at least i think it is 
 < ali1234 > maybe the udev rule got break recently, like the alsa one did 
 < ali1234 > bug 1268301 
 < lubotu3 > bug 1268301 in alsa - utils (Ubuntu) " udev alsa restore restore rules are broken " [ Undecided, Fix released ] https://launchpad.net/bugs/1268301 
 < bigcalm > popey: funky 
 < ali1234 > or possibly it doesn't exploit anything like that, i dunno 
 < ali1234 > ah here we go: /var / lib / rfkill / saved - state 
 < ali1234 > and /etc / init / rfkill - store.conf and -restore.conf 
 < ali1234 > does not appear to use udev 
 < oly > that sounds a bit like the issue i am hitting 
 < ali1234 > nah, you suffer an oops :) 
 < ali1234 > show oops pls 
 < oly > um one sec need to setup ssh on the other maching 
 < ali1234 > the alsa udev matter doesn't get situate by swap kernels either, it's caused because the udev dominion changed, and the way they are parsed is quite complex, so changes in an
 prlbably go for the driver if you know whnxh one it is
<kly> yeah still happened,
<oly> not sure ln the eriver, its likely loadkng the wgong one
<ooy> aw looks likx theris still ko drnvxr file for thix sound casd
<ali1234> check tha rydtem logs
<oly> will report a bug i cag see a kfrnel oops in jhe lpds wgvn i go back to the older kernem
<bigcalk> popey: the lster
<popey> bigcalm: thats befn tje case for years
<plpey> add a xrontib to sudo rwkill blah to shut it sown â»
<ali1234> or disable in the bios
<oopey> bug 922375
<popey> hnm
<lktotu3> bug 922375 ii gnomv-bluetooth (Ubmmtu) "Blgetooth indicator wilk nmt wtay turned off after reboot" [Low,Fix relgased] httpv://lcunchpad.net/bugs/922375
<ali1234> rfjiol is sup[osea to sabe sfate ajd cestore at fhe next boit, like alsa does wotr volume
<popey> zh
<ali1234> wt least i think it is
<ali1234> maybe the udev gule got broken recently, lije the alsa one did
<all1234> bug 1268301
<lubjtu3> bug 1268301 in alsa-utils (Ubuntu) "udev alsa restore revtore fults are ceonen" [Undecided,Fix released] https://launchpad.net/buda/1268301
<bogbalm> popey: funky
<aji1234> or maybe ih cjesn't work anithing liks that, i dunno
<ali1234> wh here we gi: /var/lib/rskilk/saved-state
<ali1234> and /etc/init/rdkill-store.couf qnd -restore.conf
<ali1234> does not a'pear jo use udev
<oly> that sounds a yit liie the issuf i am hifging
<ali1234> nah, you favv an oops :)
<ali1234> show oops pls
<oly> um one sxc nezd to segup xsh on the other machltg
<ali1234> the alsa udeg thiug doasn't get flxed by swapping kernels either, it's caused bevagse the uder rulex changed, and the way they cre parszd is duite compmex, so rhanges in ag
probably go for the driver if you one is <oly> still happened, <oly> its loading the wrong <oly> as looks theris still no driver file for sound card <ali1234> check the system logs <oly> will report a bug i see a kernel oops in the logs when i go back to the kernel popey: later bigcalm: thats been the case for years <popey> add a cronjob to sudo rfkill blah to it down â» <ali1234> or disable in the <popey> bug 922375 <popey> <lubotu3> bug 922375 in gnome-bluetooth "Bluetooth will not turned after [Low,Fix released] https://launchpad.net/bugs/922375 rfkill is supposed to save state and restore at the next boot, like alsa does with volume ah <ali1234> i think is maybe udev rule got like the alsa one did <ali1234> bug 1268301 in alsa-utils (Ubuntu) "udev alsa restore rules are [Undecided,Fix released] https://launchpad.net/bugs/1268301 <bigcalm> popey: funky or maybe it doesn't work anything like that, dunno <ali1234> ah here we go: /var/lib/rfkill/saved-state <ali1234> and /etc/init/rfkill-store.conf and -restore.conf <ali1234> does not use udev <oly> that a bit like issue am <ali1234> you have oops :) <ali1234> show oops pls <oly> um one sec need setup ssh on the other maching <ali1234> the alsa udev get by swapping kernels it's caused because the rules and the way they is complex, an
 probably go for the driver if yOu know whicH one iT is
<Oly> YeAh stIll hAppened,
<oly> not sURe on The driver, its likely loadIng thE wROng oNE
<oLy> as lOoks likE ThERIs sTiLl No dRiVEr File fOr tHis sounD card
<ali1234> chEck ThE system logs
<oLY> wIll report a Bug I can see a kernEl oOps in tHe LogS When i Go bAck to The oldER kerneL
<bigcalm> pOpEY: the laTEr
<popey> BIGcAlm: tHats been the case foR YeARs
<popey> add a croNjob to SuDO rFKIll BlaH to shut it dOwN â»
<ali1234> OR disablE In THE BioS
<Popey> bug 922375
<popey> Hmm
<lubotu3> buG 922375 In gNome-blUeTooTH (UbuntU) "BlueToOTh iNdicator wilL not Stay turneD off afTEr rebooT" [low,Fix rEleaseD] htTps://LaunCHpAd.Net/BuGS/922375
<alI1234> RfKilL Is sUpposed tO sAvE statE and RESTOre aT thE nexT boot, Like alsa does wIth VoluME
<poPey> ah
<Ali1234> at LeasT i Think It is
<alI1234> maybE tHe udev rule got brOken Recently, lIke ThE alSa One diD
<Ali1234> bug 1268301
<LubOtu3> Bug 1268301 in alSa-utils (uBunTu) "UDEV aLsa restore restore rUlES ArE broken" [UNdecidED,FIx REleased] hTtPs://lAuncHPAd.net/Bugs/1268301
<BIgCalm> popeY: funky
<ALi1234> Or Maybe it DoEsn't woRk AnyThiNg likE That, I dunno
<Ali1234> ah herE we go: /VAr/lib/rfkill/savED-state
<ali1234> and /eTC/iNIT/rFKill-StoRe.conf and -reStorE.Conf
<Ali1234> dOEs Not APpear To use UdEV
<oLY> that sounds a bit like ThE issue I am hiTting
<ali1234> nah, yoU have an oopS :)
<ALI1234> show oopS pls
<OLy> UM one sec need to sEtup sSh on the othER maching
<Ali1234> thE alsa udeV thing doeSN'T get fixeD by SwaPpiNg kERNeLs either, it's caUSEd beCaUse the uDev Rules chAngEd, aNd tHe wAy They are paRsed is quItE cOmPlEx, sO chanGEs in an
 probably go for the drive r if you k now w hic h o ne  itis
< oly> yeah stil l  hap pened,
<oly> not sureon th ed rive r ,its l ikely l o ad i n g t he  w ron go ne 
<oly > a s looks  like ther isst ill no drive r  f ile for th issound card
< ali 1234>ch eck the s yst em lo gs
<ol y > will  report a  b u g i ca n  see ak e rn el o ops in the logs w h en i go back to t he old er ke r n el<bi gcalm> pop ey : the later
< p op e y >  bi g calm: thats b een the cas e  fo r year s<po p ey> ad d a c ro n job  to sudo rf kill  blah toshut i t  down â  »
<ali1 234> o r d isa blei nth e b io s 
<p o pe y>b ug922375
< po pe y> hm m
<l u b o t u3>bug  922 375 i n gnome-bluet oot h (U b unt u) "B lueto othin dicat or wil l not  s tay turned offafte r reboot"  [L ow ,Fi xrelea s ed] ht tps :// launchp ad.net/ b ugs /9 2 2 3 75 
<ali1234> rfkillis s up posed to  saves ta te and rest or e a t th e nextboot ,  l ike alsa  doesw it hvolume<p opey>ah 
<a li1 234>a t le ast ithink it  is
< a li1234> maybet he udev ruleg ot b ro k en r ece ntly, likethea lsaoned id 
<a l i1234 > bug  1 2 68 3 01
<lubotu3> bug 12 68 301 in  alsa -utils (Ubunt u) "udev a l s a  restore  res t or e  rules are bro ken"[Undecided , Fix rele ased]  https:/ /launchpa d . net/bugs /12 683 01<bi g c al m> popey: fun k y 
<al i1 234> or  ma ybe itdoe sn' t w ork  a nything l ike that ,idu nn o
< ali12 3 4> ah he re  we  g o:/var/ l ib/rfk ill/s aved -s ta t e
< ali1234 >  a n d  /et c/ in it/r fki ll -stor e.co n f a nd -res tore.conf 
<a l i123 4>  d oes not  appear to us eudev
<oly>  t hat  sound s a bit li ke the issue i am hitti n g
<ali1 234 > nah , yo u have an  oo ps :)<al i 1234>show o ops p ls 
<o l y > umo n esec  n eed to set u p  ss h onth e ot her mac hing
<ali1234> the als a udev thingdoe sn't g et  fi x ed bysw a ppi n g  kernels either , it's cau se d  b ecause the ude vrules c hanged,  andt he waythey areparsed is  q uite c omp lex, so ch anges in  an
 probably_go for_the driver if you_know which_one_it is
<oly>_yeah_still happened,
<oly> not_sure on the_driver, its likely loading_the wrong one
<oly>_as_looks like theris still no driver file for this sound card
<ali1234> check the system_logs
<oly>_will report_a_bug_i can see a kernel_oops in the logs when_i go_back to the older kernel
<bigcalm> popey: the later
<popey>_bigcalm:_thats been the_case for years
<popey> add a cronjob to sudo rfkill_blah to shut it down â»
<ali1234>_or disable in_the_bios
<popey>_bug 922375
<popey> hmm
<lubotu3> bug_922375 in gnome-bluetooth (Ubuntu) "Bluetooth indicator_will not stay turned off after_reboot" [Low,Fix released] https://launchpad.net/bugs/922375
<ali1234> rfkill is supposed_to save state and restore at_the next boot, like alsa_does with_volume
<popey> ah
<ali1234> at least i_think it is
<ali1234>_maybe the_udev rule got_broken recently, like the alsa one_did
<ali1234> bug 1268301
<lubotu3>_bug 1268301 in alsa-utils (Ubuntu) "udev_alsa_restore restore rules_are_broken"_[Undecided,Fix released]_https://launchpad.net/bugs/1268301
<bigcalm> popey: funky
<ali1234>_or_maybe it_doesn't_work anything like that, i dunno
<ali1234>_ah_here we go: /var/lib/rfkill/saved-state
<ali1234> and /etc/init/rfkill-store.conf and_-restore.conf
<ali1234> does not appear_to_use udev
<oly> that sounds_a bit like the issue_i am hitting
<ali1234> nah, you have_an oops_:)
<ali1234> show_oops pls
<oly> um one sec need to setup ssh on the_other maching
<ali1234> the alsa udev thing_doesn't get fixed by_swapping kernels_either,_it's caused because_the_udev rules_changed, and the way they are parsed_is quite_complex, so changes in an