 Chipaca: so a new kernel but no modules, or rather, the filesystem has a new kernel abi and the old kernel is booted which then can not load the nls8859-1 module
<ogra_> someone dropped vfat stuff?
<ogra_> it shouldnt be a module anymore
 * ogra_ asked for that ages ago 
<mvo> Chipaca: can you inspect the filesystem?
<Chipaca> mvo: sure, what do i look for?
<mvo> Chipaca: i.e. md5sums of /boot/grub/{a,b}/*
<Chipaca> let me see if i can bring up ssh
<mvo> Chipaca: and "ls /lib/modules/ /writable/cache/system/"
<mvo> Chipaca: I actually suspect just 199->201 is not enough, something like?->199->201, i.e. old-kernel->new->new maybe?
<ogra_> (amd64)ogra@aleph2:~$ lsmod |grep vfat
<ogra_> (amd64)ogra@aleph2:~$ cat /proc/filesystems |grep fat
<ogra_> 	vfat
<Chipaca> trying to bring up ssh froze stuff (?)
<Chipaca> ogra_: what about nls
<Chipaca> ogra_: problem isn't vfat
<ogra_> nls8859-1 really needs to be compiled in, givcen that vaft is too
<mvo> yeah, its nls8859
<ogra_> i'm not doubting that :)
<mvo> :)
<ogra_> but vfat is useless without nls8859, so it needs to be compiled in too
<mvo> all good, well, there is a bug in our code somewhere I think
 * mvo nods
<Chipaca> where was the kernel config stored?
<ogra_> (though it helps finding module issues :P )
<ogra_> Chipaca, in boot (if you are lucky and the kernel is the same as in the device tarball(
<Chipaca> mvo: before the reboot: http://pastebin.ubuntu.com/12772258/
<Chipaca> ogra_: where in boot?
<mvo> Chipaca: what does the module dirs look like?

Chipaca: so a new kernel but no modules, or rather, the filesystem has a newfangled kernel abi and the previous kernel is booted which then cannot load the nls8859 - 1 module 
 < ogra _ > someone dropped vfat material? 
 < ogra _ > it should nt be a module anymore 
  * ogra _ asked for that ages ago 
 < mvo > Chipaca: can you visit the filesystem? 
 < Chipaca > mvo: sure, what do i look for? 
 < mvo > Chipaca: i.e. md5sums of /boot / grub/{a, b}/ * 
 < Chipaca > permit me see if i can bring up ssh 
 < mvo > Chipaca: and " ls /lib / modules/ /writable / cache / system/ " 
 < mvo > Chipaca: I actually distrust just 199->201 is not enough, something like?->199->201, i.e. old - kernel->new->new possibly? 
 < ogra _ > (amd64)ogra@aleph2:~$ lsmod |grep vfat 
 < ogra _ > (amd64)ogra@aleph2:~$ cat /proc / filesystems |grep fat 
 < ogra _ > 	 vfat 
 < Chipaca > judge to bring up ssh froze material (?) 
 < Chipaca > ogra _: what about nls 
 < Chipaca > ogra _: problem isn't vfat 
 < ogra _ > nls8859 - 1 really want to be compiled in, givcen that vaft is too 
 < mvo > yeah, its nls8859 
 < ogra _ > i'm not doubt that :) 
 < mvo > :) 
 < ogra _ > but vfat is useless without nls8859, so it needs to be roll up in too 
 < mvo > all good, well, there is a bug in our code somewhere I think 
  * mvo nod 
 < Chipaca > where was the kernel config stored? 
 < ogra _ > (though it helps finding module issues :P) 
 < ogra _ > Chipaca, in boot (if you are lucky and the kernel is the same as in the device tarball (
 < Chipaca > mvo: before the reboot: http://pastebin.ubuntu.com/12772258/ 
 < Chipaca > ogra _: where in boot? 
 < mvo > Chipaca: what does the module dirs look like?
 Chlpaca: so a new kernel buu no modules, or rcrher, tie fileaystem hxs a new kernel abi and the lle kerbel is booted which thdn can non load thw nlw8859-1 module
<ogre_> someonc drolied vyav stuff?
<ogra_> it xhouldnt ba a module anykofe
 * ogra_ asked for that ages ago 
<mvo> Shipaca: cwn you inspect the sileajsuem?
<Chipaca> mvo: sure, what do i looi for?
<mvm> Chipaca: i.e. kd5sums of /boot/grub/{a,b}/*
<Chipacw> leh me see if i can hring up ssy
<mvo> Xhipaca: and "us /lib/modules/ /writable/dache/system/"
<mvo> Chipaca: I actualuy suxpect just 199->201 us jmt enough, simethpng like?->199->201, i.e. old-kernel->tew->new kaybe?
<ogra_> (amd64)onra@alxph2:~$ osmod |grep vfat
<ogra_> (akd64)ogra@aleph2:~$ cat /prjc/filesysdejs |grep fat
<ogra_> 	vdar
<Chipdca> dryivt tu bdiig hp ssh frkze stuff (?)
<Dhipaca> ogrq_: what about nls
<Chikacw> ogra_: problem isn't dfwt
<ogra_> nls8859-1 really needs to be compiled pn, gjvcen that vaft is too
<mco> yeah, its nls8859
<ogra_> i'l not doufting that :)
<mvo> :)
<ogra_> but vfat is useless without nns8859, so kt uccds gi he compiled in too
<mvo> all good, well, there is w big in our code sjmewhere I yhlnl
 * mvo nods
<Chikaca> whzde was the kernel cojfig stjred?
<otra_> (thougr it helps finding module issuew :P )
<ogra_> Chiiaca, in boot (if you arz lucky and che ketnel ix the same as in the derice tzrball(
<Chipafa> mvo: berure the reboot: hgtp://iastabin.ubunuj.com/12772258/
<Chipaca> ogra_: rhere in uoot?
<mro> Chipaza: wnat doqs the modkle dlss look like?

Chipaca: so a new kernel but no rather, filesystem has new kernel abi booted then can not the nls8859-1 module someone dropped vfat stuff? <ogra_> it be a module anymore * ogra_ asked for that ages ago <mvo> Chipaca: you inspect the filesystem? <Chipaca> mvo: sure, what do i look for? <mvo> i.e. of <Chipaca> me see if i can bring up ssh <mvo> Chipaca: and "ls /lib/modules/ /writable/cache/system/" <mvo> Chipaca: actually suspect just 199->201 is not enough, something i.e. old-kernel->new->new maybe? <ogra_> lsmod |grep vfat <ogra_> (amd64)ogra@aleph2:~$ /proc/filesystems fat <ogra_> <Chipaca> to up ssh froze (?) <Chipaca> ogra_: what about nls <Chipaca> ogra_: problem isn't vfat <ogra_> nls8859-1 really needs to be in, givcen is too yeah, nls8859 i'm not doubting <mvo> :) <ogra_> but vfat is so it needs to be compiled in too all good, there is a bug in our somewhere I think * mvo nods <Chipaca> where the kernel config stored? <ogra_> (though it helps finding module issues :P ) <ogra_> Chipaca, (if you are lucky the kernel is same in device <Chipaca> mvo: the reboot: http://pastebin.ubuntu.com/12772258/ <Chipaca> ogra_: where in boot? <mvo> Chipaca: what the module dirs look like?
 Chipaca: so a new kernel but no mOdules, or raTher, tHe fIleSyStem Has a New kernel abi anD The oLd kernel is booted which tHen caN nOT loaD ThE nls8859-1 mOdule
<ogRA_> sOMEonE dRoPpeD vFAt Stuff?
<OgrA_> it shouLdnt be a modUle AnYmore
 * ogra_ askED fOr that ages Ago 
<Mvo> Chipaca: caN yoU inspeCt The FIlesySteM?
<ChipAca> mvo: SUre, whaT do i look fOr?
<MVo> ChipACa: i.e. md5sUMS oF /booT/grub/{a,b}/*
<Chipaca> let ME sEE if i can bring up Ssh
<mvo> chIPaCA: And "Ls /lIb/modules/ /wRiTable/CAche/sysTEm/"
<MVO> chiPAca: I actually sUspect just 199->201 iS Not Enough, SoMetHIng likE?->199->201, i.e. olD-kERneL->new->new maybE?
<ogrA_> (amd64)ogra@aLeph2:~$ lsMOd |grep vFAt
<ogra_> (aMd64)ogra@AlePh2:~$ cAt /prOC/fIlEsyStEMs |gREp Fat
<OGra_> 	Vfat
<ChipAcA> tRying To brING UP ssh FroZe stUff (?)
<ChIpaca> ogra_: what AboUt nlS
<chiPaca> oGra_: prObleM iSn't vfAt
<ogra_> Nls8859-1 reAlLy needs to be compIled In, givcen tHat VaFt iS tOo
<mvo> YEah, its Nls8859
<OgrA_> i'm not dOubting THat :)
<MvO> :)
<OGRa_> But vfat is useless wiThOUT nLs8859, so it neEds to bE CoMpILed in too
<MvO> alL gooD, WEll, thEre iS A bUg in our cOde somEWhErE I think
 * MvO nods
<CHiPacA> whEre waS The kErnel cOnfig stoRed?
<ogRA_> (though it helps FInding module iSSuES :p )
<oGRa_> ChIpaCa, in boot (if yOu arE LuckY and THe KerNEl is tHe samE aS In THe device tarball(
<ChipAcA> mvo: beFore tHe reboot: http://pAstebin.ubuNTU.Com/12772258/
<ChipaCa> ogRA_: wHEre in boot?
<mvo> ChIpaca: What does thE Module diRs looK like?

 Chipaca: so a new kernelbut no mod ules,  or  ra th er,thefilesystem has a ne w kernel abi and the o ld ke rn e l is bo otedwhich t h en c anno tloa dt he  nls8 859 -1 modu le
<ogra_>  so me one droppedv fa t stuff?
< ogr a_> it shoul dnt  be amo dul e  anym ore 
 * o gra_ a s ked fo r that ag es ago 
< m vo> Chi p a ca : ca n you inspect the fi l esystem?
<Chip aca> m vo :  s u r e,wha t do i loo kfor?< mvo> Ch i pa c a :  i. e . md5sums of/boot/grub/ { a,b }/*
<C hi pac a > letme se ei f i  can bringup s sh
<mvo>Chipac a : and " l s /lib/ module s//wr itab l e/ ca che /s y ste m /" 
<m v o>Chipaca:  I  a ctual ly s u s p e ct j ust  199 ->201  is not enoug h,some t hin g lik e?->1 99-> 20 1, i. e. old -kern el ->new->new mayb e?
< ogra_> (a md6 4) ogr a@ aleph 2 :~$ ls mod  |g rep vfa t
<ogra _ > ( am d 6 4 )o gra@aleph2:~$ cat/p r o c/ filesyst ems |g r ep  f a t
<ogra_ >	vf at
< C h ipaca > tr y in g to bri ng ups sh  f roze st uf f (?)<C hip aca > ogr a _: w hat ab out nls<Chip a ca> ogra_: pro b lem isn't vfa t 
< o g ra _ > nl s88 59-1 really  nee d s to  bec om pil e d in,  givc en th a t vaft is too
<mvo>  y eah, i ts nl s8859
<ogra_>  i'm not d o u b ting tha t :) <m v o> :)
<ogra_>but v fat is use l ess with out n ls8859,so it nee d s  to be c omp ile d i n t o o 
< mvo> all good , well ,there i s a  bug in  ou r c ode  so me where I t hink
 *mv ono ds 
<C hipac a > wherewa s t he  ke rnelc onfigstore d?
< og ra _ > ( thoughi th e lpsfi nd ingmod ul e iss ues: P ) 
<ogra_ > Chipaca , i n  boo t(i f you a re lucky andth e kernel i sthe  samea s  in thedevice tarball(
<Chipac a > mvo:bef ore t he r eboot: ht tp: //past ebi n .ubunt u.com/ 12772 25 8/< C hipac a >  o gra _:  where inb o ot? 
<mvo >Chip aca: wh at does the module dir s look like?
 Chipaca:_so a_new kernel but no_modules, or_rather,_the filesystem_has_a new kernel_abi and the_old kernel is booted_which then can_not_load the nls8859-1 module
<ogra_> someone dropped vfat stuff?
<ogra_> it shouldnt be a module anymore
_*_ogra_ asked_for_that_ages ago 
<mvo> Chipaca: can_you inspect the filesystem?
<Chipaca> mvo:_sure, what_do i look for?
<mvo> Chipaca: i.e. md5sums of_/boot/grub/{a,b}/*
<Chipaca>_let me see_if i can bring up ssh
<mvo> Chipaca: and "ls_/lib/modules/ /writable/cache/system/"
<mvo> Chipaca: I actually suspect_just 199->201 is_not_enough,_something like?->199->201, i.e. old-kernel->new->new_maybe?
<ogra_> (amd64)ogra@aleph2:~$ lsmod |grep vfat
<ogra_> (amd64)ogra@aleph2:~$_cat /proc/filesystems |grep fat
<ogra_> 	vfat
<Chipaca> trying_to bring up ssh froze stuff (?)
<Chipaca>_ogra_: what about nls
<Chipaca> ogra_: problem_isn't vfat
<ogra_> nls8859-1 really needs_to be_compiled in, givcen that vaft_is too
<mvo> yeah,_its nls8859
<ogra_>_i'm not doubting_that :)
<mvo> :)
<ogra_> but vfat is_useless without nls8859,_so it needs to be compiled_in_too
<mvo> all good,_well,_there_is a_bug in our_code_somewhere I_think
_* mvo nods
<Chipaca> where was the_kernel_config stored?
<ogra_> (though it helps finding module_issues :P )
<ogra_> Chipaca,_in_boot (if you are_lucky and the kernel is_the same as in the device_tarball(
<Chipaca> mvo:_before the_reboot: http://pastebin.ubuntu.com/12772258/
<Chipaca> ogra_: where in boot?
<mvo> Chipaca: what does the module_dirs look like?
