Back to Home / #debian / 2014 / 08 / Prev Day | Next Day
#debian IRC Logs for 2014-08-23

---Logopened Sat Aug 23 00:00:00 2014
00:07-!-NomadJim [] has quit [Read error: Connection reset by peer]
00:08-!-Q-Master [] has quit [Remote host closed the connection]
00:13-!-FlowRiser [~FlowRiser@] has quit [Remote host closed the connection]
00:17-!-mode/#debian [+l 609] by debhelper
00:19-!-renatoag [~runa@] has quit [Quit: leaving]
00:22-!-cheus [] has quit [Ping timeout: 480 seconds]
00:26-!-hlozada [~hlozada@] has quit [Ping timeout: 480 seconds]
00:30-!-aidalgol [] has quit [Quit: ERC Version 5.3 (IRC client for Emacs)]
00:32-!-FlowRiser [~FlowRiser@] has joined #debian
00:43-!-sylar [] has quit [Ping timeout: 480 seconds]
00:50-!-InvadeD [] has joined #debian
00:50-!-[Steven_M] [] has joined #debian
00:57-!-imavlr [~n@] has quit [Quit: Kuit!]
00:57-!-frangor [] has joined #debian
01:00-!-FlowRiser [~FlowRiser@] has quit [Ping timeout: 480 seconds]
01:00-!-wompa [] has joined #debian
01:02-!-jalalsfs [] has joined #debian
01:11-!-freex [] has quit [Ping timeout: 480 seconds]
01:18-!-Optical [~dlz@] has quit [Ping timeout: 480 seconds]
01:28-!-mentor [] has quit [Ping timeout: 480 seconds]
01:30-!-xakz [] has joined #debian
01:39-!-teslasmhd [] has quit [Quit: ownz j00!]
01:48-!-jalalsfs [] has quit [Ping timeout: 480 seconds]
01:49-!-kriger [] has quit [Ping timeout: 480 seconds]
01:50-!-jalalsfs [] has joined #debian
02:25-!-Cylus [] has quit [Ping timeout: 480 seconds]
02:27-!-mode/#debian [+l 603] by debhelper
02:29-!-ao2 [~ao2@2001:1418:117::1] has joined #debian
02:31-!-mgv [marius@] has quit [Ping timeout: 480 seconds]
02:35-!-Cylus [] has joined #debian
02:37-!-Cylus is "" on # #debian #debian-offtopic #oftc #xhtml #html @#w3c #php
02:47-!-T0rch [] has joined #debian
02:48-!-csotelo [~csotelo@] has quit [Remote host closed the connection]
02:51-!-mgv [marius@] has joined #debian
03:03-!-smulverine [] has joined #debian
03:04-!-melmothX [~melmoth@] has joined #debian
03:22-!-dardevelin [] has quit [Quit: Leaving]
03:31-!-[Steven_M] [] has quit [Quit: Konversation terminated!]
03:39-!-melmothX [~melmoth@] has quit [Ping timeout: 480 seconds]
03:43-!-gjerich [] has quit [Ping timeout: 480 seconds]
03:45-!-Netsplit <-> quits: xiqy, namix, diocles, k3t, defane, hubutm20, f3rn4nd0, protomouse, huayra, Hunger, (+58 more, use /NETSPLIT to show all of them)
03:46-!-Netsplit over, joins: przemoc
03:47-!-Netsplit over, joins: swo
03:47-!-tidal [] has quit [Ping timeout: 480 seconds]
03:47-!-Netsplit <-> quits: jthomas, jrib, tehgooch, CompWizrd, dark-jedi, towski, ixti, mattcen, eliasp, ghartz, (+3 more, use /NETSPLIT to show all of them)
03:47-!-frangor [] has quit [Quit: WeeChat 0.4.3]
03:49-!-Netsplit over, joins: wompa, protomouse, DonVitoCorleone
03:49-!-Netsplit over, joins: Celelibi
03:49-!-Gogeta70 [] has joined #debian
03:49-!-ixti [~ixti@] has joined #debian
03:49-!-ghartz [] has joined #debian
03:49-!-CompWizrd [] has joined #debian
03:49-!-eliasp [] has joined #debian
03:49-!-jthomas [] has joined #debian
03:49-!-joeyo [] has joined #debian
03:49-!-quasisane [] has joined #debian
03:49-!-mattcen [] has joined #debian
03:49-!-tehgooch [] has joined #debian
03:49-!-eliasp [] has quit [Max SendQ exceeded]
03:49-!-tehgooch [] has quit [Max SendQ exceeded]
03:49-!-quasisane [] has quit [Max SendQ exceeded]
03:49-!-jthomas [] has quit [Read error: Connection reset by peer]
03:49-!-CompWizrd [] has quit [Ping timeout: 484 seconds]
03:49-!-Netsplit over, joins: petris
03:49-!-ixti [~ixti@] has quit [Ping timeout: 484 seconds]
03:49-!-Netsplit over, joins: mgv
03:50-!-ixti [~ixti@] has joined #debian
03:50-!-Netsplit over, joins: tdi, rudi_s
03:50-!-Netsplit over, joins: namix
03:50-!-Netsplit over, joins: davromaniak
03:50-!-Netsplit over, joins: manio
03:50-!-quasisane [] has joined #debian
03:51-!-Netsplit over, joins: zem
03:51-!-Netsplit over, joins: dooglus
03:51-!-glebihan_ [] has quit [Read error: Connection reset by peer]
03:52-!-Netsplit over, joins: xiqy
03:53-!-xakz [] has quit [Quit: Lost terminal]
03:56-!-xakz [] has joined #debian
03:56-!-T0rch [] has joined #debian
03:57-!-mode/#debian [+l 545] by debhelper
03:57-!-stdhell [] has joined #debian
03:57-!-ServerMode/#debian [+l 603] by
03:57-!-k3t [~k3t@2002:4dbf:e913:0:ba27:ebff:fe64:ce16] has joined #debian
03:57-!-spion [] has joined #debian
03:57-!-niko_20010 [] has joined #debian
03:57-!-eric [eric@2a01:7e00:e000:69::c0ca:c01a] has joined #debian
03:57-!-mteufel [] has joined #debian
03:57-!-iron [iron@2001:41d0:52:300::5b0] has joined #debian
03:57-!-gautier [] has joined #debian
03:57-!-edog [] has joined #debian
03:57-!-diocles [] has joined #debian
03:57-!-MrPlop [] has joined #debian
03:57-!-madduck [] has joined #debian
03:57-!-EmleyMoor [] has joined #debian
03:57-!-CapnRat [~ShawnWhit@2a01:7e00::f03c:91ff:fe70:27e1] has joined #debian
03:57-!-nkukard [] has joined #debian
03:57-!-jalalsfs [] has joined #debian
03:58-!-holmgren [] has joined #debian
04:00-!-frangor [] has joined #debian
04:07-!-mode/#debian [+l 560] by debhelper
04:08-!-xakz [] has quit [Quit: Lost terminal]
04:08-!-Guest1715 [~gsb@] has quit [Remote host closed the connection]
04:09-!-xakz [] has joined #debian
04:10-!-igmp [] has quit [Ping timeout: 480 seconds]
04:14-!-oufo [] has joined #debian
04:15-!-kenoby [] has quit [Ping timeout: 480 seconds]
04:16-!-dselect [] has joined #debian
04:18-!-dandersson [] has joined #debian
04:28-!-frangor [] has quit [Quit: WeeChat 0.4.3]
04:30-!-melmothX [~melmoth@] has joined #debian
04:33-!-rueh [] has joined #debian
04:44-!-phdeswer__ [] has quit [Ping timeout: 480 seconds]
04:44-!-warhead [] has joined #debian
04:45-!-debchange [] has joined #debian
04:51-!-xakz [] has quit [Ping timeout: 480 seconds]
04:54-!-warhead [] has quit [Ping timeout: 480 seconds]
04:55-!-carnil [] has joined #debian
04:57-!-xakz [] has joined #debian
04:58-!-InvadeD [] has quit [Quit: Leaving]
05:02-!-bluewater [] has joined #debian
05:08-!-jalalsfs [] has quit [Ping timeout: 480 seconds]
05:11<Champie>Gogeta70: run 'badblocks' on your suspicious disk ? I do it on every new drive I get.
05:13-!-frangor [] has joined #debian
05:17-!-dselect [] has quit [Ping timeout: 480 seconds]
05:23-!-s_i_m [] has joined #debian
05:23-!-citruslogic [] has joined #debian
05:23-!-melmothX [~melmoth@] has quit [Ping timeout: 480 seconds]
05:24-!-sven__ [] has joined #debian
05:25<sven__>Hello all
05:25<sven__>I would need some help please. Just did a dist-upgrade from wheezy and now my / is read only. When the boot messages show up, they stop and I get droped in the console window 1. when I do a mount -o remount, rw / it automaticly goes to the console where X is running and starts up gdm as usual. what can i do to make the fs by default RW again. I tried to change ro to rw in fstab but it still does read only ;(
05:27<s_i_m>sven__, did you run fsck on your root partition?
05:28-!-gnugr [] has quit [Quit: WeeChat 0.4.3]
05:29<s_i_m>sven__, btw asking on #debian-next may help you better
05:32-!-gnugr [] has joined #debian
05:34-!-ph0b0s [] has joined #debian
05:34<sven__>how do i do run fsck on my root partition i tried and it said it is in use
05:34-!-ph0b0s [] has quit [Quit: Leaving.]
05:34<sven__>thanks for the hint, the "-next" is the channel for the "testing" currently jessie?
05:35<Champie>testing/unstable iirc
05:35<s_i_m>sven__, the best is to boot from another media (debian CD or usb stick, etc) and then run it from there
05:35<sven__>and what would possible the result? you think the root part has an error?
05:35-!-ph0b0s [] has joined #debian
05:35<sven__>does the os automatically go to ro when that happens?
05:36<s_i_m>Debian CD has the rescue mode, you can boot in that. Yes, normally, if there are errors on the fs it will be mounted in RO
05:37<Champie>by default, there's "errors=remount-ro" for the / mount, in /etc/fstab
05:37<sven__>well indeed it was xD
05:37<Champie>is to protect against file system damage
05:37<sven__>but i dont understand when i erased it and switched the ro to rw why it wont work
05:37<sven__>well but if i force it to do it?
05:37<sven__>it still does what it thinks is right hmm?
05:38<sven__>or possibly protecting me from an unworking os then
05:38-!-sjefen6 [] has quit [Remote host closed the connection]
05:39<sven__>how is the complete fsck command then for the root?
05:39<Champie>hmz, shutdown doesn't offer the "-F" option anymore ?
05:39<sven__>fsck /dev/sda
05:39<Champie>ah, doesn't offer it when running systemd :[
05:40<sven__>just one question
05:40-!-valdyn [] has quit [Ping timeout: 480 seconds]
05:41<sven__>when i do the fsck what will this lead to simply correcting and then i restart as usual?
05:42<Champie>that's what it should do
05:43<sven__>alright, will try it now, hope to see you soon xD thanks a lot for your help and time.
05:43-!-sven__ [] has quit [Quit: Konversation terminated!]
05:43-!-MichaelPaoli [~michael@] has joined #debian
05:57-!-valdyn [] has joined #debian
06:00-!-ph0b0s [] has quit [Ping timeout: 480 seconds]
06:05-!-MichaelPaoli [~michael@] has quit [Quit: Leaving.]
06:06-!-melmothX [~melmoth@] has joined #debian
06:11-!-dselect [] has joined #debian
06:14-!-valdyn [] has quit [Quit: leaving]
06:14-!-valdyn [] has joined #debian
06:16-!-claw__ [~claw@] has quit [Ping timeout: 480 seconds]
06:16-!-kraiskil [] has joined #debian
06:21-!-Out`Of`Control [] has joined #debian
06:24-!-melmothX [~melmoth@] has quit [Ping timeout: 480 seconds]
06:28-!-dario` [] has quit [Quit: ircbox moving to new hardware \o/]
06:37-!-Freejack [] has quit [Ping timeout: 480 seconds]
06:38-!-spippi [] has joined #debian
06:38-!-lsbit [] has joined #debian
06:38-!-Freejack [] has joined #debian
06:39<lsbit>hi to everybody
06:39<lsbit>I'm new here :)
06:40<lsbit>how long are you linux user sippi? I need some help with wifi and I dont know is this a good place to ask?
06:41<lsbit>spippi* sorry for typo
06:42<lsbit>maybe you or someone else could help me?
06:42<spippi>if you have a debian distribution it's the correct place
06:42-!-f10 [] has joined #debian
06:43<lsbit>ofc I have :)
06:43<spippi>when have you a problem ask directly in chat
06:43<spippi>the better and beatiful comunity is here for help you
06:44<devil>spippi: if you are a debian user, this is the right place to ask
06:44<lsbit>ok thank you very much I will explain my problem as best as I can
06:44<devil>ok, it is lsbit asking :)
06:45<spippi>lsbit where are you from
06:45<lsbit>from serbia
06:46<lsbit>and devil and you?
06:46<lsbit>I've got a new Laptop (Lenovo Thinkpad E540) and installed debian with xfce, cause gnome were buggy. Then I've tried to make wifi to work
06:47<devil>that is a bit offtopic here. If you want to sozialize, please join #debian-offtopic
06:47-!-omnidan [] has quit [Ping timeout: 480 seconds]
06:47<devil>lsbit: for wifi you will probably need firmware fronm the non-free repos
06:47<lsbit>yes I know
06:47<devil>lsbit: is it a builtin wifi or usb?
06:48<lsbit>I found out
06:48-!-omnidan [] has joined #debian
06:48<devil>do you know which firmware you need?
06:48<lsbit>that I need iwlwifi
06:48<devil>ok, so intel
06:48<lsbit>but lspci doesnt directly show me wifi manifacture
06:48<devil>the name of the package is irmware-iwlwifi
06:49<lsbit>but I found out with vendor id provided
06:49<devil>the name of the package is firmware-iwlwifi
06:49<devil>and it lives in non-free
06:49<devil>did you add that to your sources.list?
06:49-!-Out`Of`Control [] has quit [Remote host closed the connection]
06:49<lsbit>and I've installed it
06:50<lsbit>but I dont know how to configure it
06:50<devil>you need to either reload the module or reboot to make it work
06:50<devil>no config needed
06:50<lsbit>last command which I was able to follow
06:50<lsbit>was modprobe iwlwifi
06:50<devil>does iwlist scan show anything?
06:51<lsbit>well I'm not sure what is it I can copy the output here
06:51<devil>lsbit: you should do modprobe -r iwlwifi && modprobe iwlwifi
06:51<devil>so to unload and reload the module
06:52<lsbit>I've also done removeal first
06:52<devil>output goes to
06:52-!-warhead [] has joined #debian
06:52-!-znalo [ambrose@] has quit [Ping timeout: 480 seconds]
06:52<lsbit>iwlist scan
06:52<devil>if it is more than a line or 2
06:52-!-CyberBob [~CyberBob@] has quit [Ping timeout: 480 seconds]
06:53<devil>iwlist scan wlan0 should narrow it in
06:53-!-protomouse [] has quit [Quit: this is not a drill]
06:53<lsbit>eth0 Interface doesn't support scanning. lo Interface doesn't support scanning.
06:53<devil>we are looking for wlan0
06:53<lsbit>wlan0 is not recognized at all
06:53<lsbit>this two are only available
06:54-!-dutchfish [] has joined #debian
06:54<devil>lsbit: can you pastebin the output of: dpkg -l | grep iwl
06:54-!-fisted [] has quit [Ping timeout: 480 seconds]
06:54-!-XaF [] has quit [Read error: Operation timed out]
06:55<devil>pastebin= paste to and give us the URL you get after hitting 'send'
06:55<lsbit>I've also updated kernel to 3.14 cause I red somewhere that iwlwifi doesn't work corectly with my model on wheezy 3.2 kernel
06:56-!-amphi_ [] has quit [Ping timeout: 480 seconds]
06:57<lsbit>sorry for my slowliness
06:57-!-jmux [] has joined #debian
06:59<lsbit>04:00.0 Network controller [0280]: Intel Corporation Device [8086:08b2] (rev 73)
06:59<lsbit>this lspci output
07:00-!-jalalsfs [] has joined #debian
07:00<lsbit>and that is the wifi device which correspond to [8086:08b2]
07:03<lsbit>does anybody have any idea?
07:03<devil>lsbit: did you also install kernel headers?
07:04<lsbit>I've downloaded kernel source, compile it, and instaled it
07:04<SynrGy>which version?
07:04<devil>well, you should use the kernel in backports plus the headers
07:04<SynrGy>and you've rebooted, i assume ...
07:05-!-dpkg [] has quit [Quit: buh bye!]
07:05<SynrGy>yes, you don't need to compile your own
07:05<judd>Available kernel versions are: experimental: 3.16-trunk-686-pae (3.16-1~exp1); sid: 3.14-2-686-pae (3.14.15-2); jessie: 3.14-2-686-pae (3.14.15-2); wheezy-backports: 3.14-0.bpo.2-686-pae (3.14.13-2~bpo70+1); wheezy: 3.2.0-4-686-pae (3.2.60-1+deb7u3); squeeze-backports: 3.2.0-0.bpo.4-686-pae (3.2.57-3+deb7u2~bpo60+1); squeeze: 2.6.32-5-686 (2.6.32-48squeeze6)
07:05-!-dpkg [] has joined #debian
07:05<devil>and I am happy if SynrGy takes over because my attention needs to go back to work :)
07:05<SynrGy>heh. well, i was just passing through ...
07:06<lsbit>I read that thread
07:06<SynrGy>going to church shortly
07:06<devil>well, installing kernel and headers should fix the issue
07:06<devil>iwlwifi mostly works ootb
07:06<SynrGy>"The firmware-iwlwifi that supports the Intel 7260 only works with kernel version 3.10 and above."
07:07<lsbit>ok thnks i'll try :)
07:07<SynrGy>so it sounds like all you really need is to install the backports kernel *and* the backports firmware.
07:07<SynrGy>why the kernel headers?
07:07<SynrGy>i'm not sure what that has to do with this issue
07:07<devil>not sure if they are needed
07:07<SynrGy>it's not an out-of-tree module is it?
07:07<devil>it is, yeah
07:08<devil>as I always have headers installed with my kernels, I am not sure
07:08<SynrGy>which module?
07:08<SynrGy>i'm not seeing it ...
07:08<SynrGy>iwlwifi is in tree
07:08*devil is walking the dog and then back to work
07:09<SynrGy>all lsbit needs is backports kernel + backports firmware-iwlwifi
07:09<SynrGy>lsbit: do you have already backports in your sources.list? or need instructions for that?
07:09<lsbit>should I add something to src list for backports
07:09<SynrGy>!tell lsbit about wheezy-backports
07:09<lsbit>I think I dont have it
07:09-!-otherflow [] has joined #debian
07:10<lsbit>I think I will be able to manage that
07:10<SynrGy>and after that, apt-get install -t wheezy-backports linux-image-amd64 firmware-iwlwifi
07:10<SynrGy>make sure the backports line includes contrib non-free
07:10<lsbit>but why compiled kernel didn't solved the problem
07:10<SynrGy>no idea.
07:11<SynrGy>best not to get too lost in that direction. there are many ways to shoot yourself in the foot there.
07:11<SynrGy>the backports way is the one we support here.
07:12<lsbit>Ok thank you very much I will try it and tell you the results :)
07:12<SynrGy>good luck.
07:12<SynrGy>i may not be able to help when you return, but may be around several hours hence
07:12<SynrGy>but if not me, someone else here ought to be able to help
07:16-!-Out`Of`Control [] has joined #debian
07:17-!-bsc [~balasanka@] has joined #debian
07:22-!-MY123 [] has joined #debian
07:27-!-mode/#debian [+l 566] by debhelper
07:28-!-bsc [~balasanka@] has quit [Ping timeout: 480 seconds]
07:31-!-amraw [~amraw@] has joined #debian
07:36-!-protomouse [] has joined #debian
07:37<devil>lsbit: working now?
07:38-!-Walex [] has joined #debian
07:50-!-amraw [~amraw@] has quit [Quit: Leaving]
07:50<SynrGy>lsbit: i'm curious too. leaving the house in 15
07:51-!-amraw [~amraw@] has joined #debian
07:52-!-s_i_m [] has quit [Ping timeout: 480 seconds]
07:52-!-jalalsfs [] has quit [Ping timeout: 480 seconds]
07:54-!-q66 [] has joined #debian
07:59-!-Brigo [] has joined #debian
08:01-!-melmothX [~melmoth@] has joined #debian
08:01-!-himanshu [~himanshu@] has joined #debian
08:01<himanshu>Hello All.
08:02-!-Big-Blue [] has joined #debian
08:02-!-jalalsfs [] has joined #debian
08:03-!-duglas [] has joined #debian
08:04<himanshu>Please tell me how do I create a system recovery disk for my Debian wheezy?
08:04<himanshu>Im new to linux platform and googling on this brings me to Live Install images of debian
08:05<himanshu>I dont know how to create a recovery disk from that
08:07-!-mode/#debian [+l 573] by debhelper
08:07-!-melmothX [~melmoth@] has quit [Remote host closed the connection]
08:07-!-melmothX [~melmoth@] has joined #debian
08:09<himanshu>point me in the right direction
08:10<devil>himanshu: clonezilla might be what you want
08:11<himanshu>thanks,ill try that
08:17-!-himanshu [~himanshu@] has quit [Remote host closed the connection]
08:23-!-warhead [] has quit [Ping timeout: 480 seconds]
08:23-!-amraw [~amraw@] has quit [Ping timeout: 480 seconds]
08:24-!-hicks [~who@] has joined #debian
08:30-!-debchange [] has quit [Remote host closed the connection]
08:30-!-debchange [] has joined #debian
08:32-!-monod [~monod@] has joined #debian
08:32-!-amraw [~amraw@] has joined #debian
08:39-!-Big-Blue [] has quit [Quit: Big-Blue]
08:41-!-melmothX [~melmoth@] has quit [Ping timeout: 480 seconds]
08:47-!-FlowRiser [] has joined #debian
08:52-!-amraw [~amraw@] has quit [Ping timeout: 480 seconds]
08:58-!-lsbit [] has quit [Remote host closed the connection]
09:02-!-melmothX [~melmoth@] has joined #debian
09:03-!-dvs [] has joined #debian
09:05-!-kilelme [~kilelme@] has joined #debian
09:05-!-FlowRiser [] has quit [Ping timeout: 480 seconds]
09:07-!-lsbit [] has joined #debian
09:07<lsbit>Hi peope
09:08<lsbit>your sugestions didn't help me unfortunatly
09:08<devil>lsbit: did you install iwlwifi from sid?
09:09<devil>then that shoulsd work
09:09<devil>did you reboot?
09:09<lsbit>but system told me that I've already had the newest one
09:09<MY123>mixing wheezy and sid is bad
09:09<lsbit>and I uninstaled that
09:09<lsbit>and installed new again
09:10<dpkg>When you get random packages from random repositories, mix multiple releases of Debian, or mix Debian and derived distributions, you have a mess. There's no way anyone can support this "distribution of Frankenstein" and #debian certainly doesn't want to even try. See if you can convince ##linux to help.
09:10<devil>iwlist scan does not list wlan0?
09:10<lsbit>just sec
09:11<lsbit>itsn't visible at all
09:11<lsbit>just eth0 and lo
09:11<lsbit>what is 'lo' anyway?
09:11<devil>modprobe -r iwlwifi && modprobe iwlwifi && iwlist scan wlan0
09:11<devil>lo ist the localhost
09:12-!-debchange [] has quit [Remote host closed the connection]
09:12<lsbit>iwlist: unknown command `wlan0' (check 'iwlist --help').
09:12-!-debchange [] has joined #debian
09:12<lsbit>that is the output
09:12<devil>and iwlist scan still has no wlan0?
09:13<devil>hm, someone else will have to dig deeper into that, I need to get back to work
09:13<lsbit>but I know it should work cause I've tried with ubuntu and yesterday and it was normal
09:13<gsimmons>lsbit: Just to confirm, which Linux kernel version is currently in use? (uname -r)
09:14<gsimmons>lsbit: The exact output of that command, please.
09:14<lsbit>@devil kk np :)
09:14<lsbit>I wrote it
09:15<gsimmons>lsbit: That isn't a version which would be reported by a linux-image package from wheezy-backports. Did you install the packages SynrGy indicated earlier?
09:16<lsbit>Do you think that problem might be that lspci command doesn't recognize device as Wireless device
09:16-!-melmothX [~melmoth@] has quit [Quit: #]
09:16<lsbit>I think that package name was
09:16<blast007>lsbit: are you still running a custom compiled kernel?
09:16-!-kilelme [~kilelme@] has quit [Ping timeout: 480 seconds]
09:17<lsbit>I've added backports to src list
09:18<lsbit>and installed on this way (just a moment to find a link)
09:19<lsbit>so I've run
09:19<lsbit>apt-get -t wheezy-backports install linux-image-amd64
09:19-!-dark-jedi [~dark-jedi@] has joined #debian
09:19<lsbit>apt-get -t wheezy-backports install firmware-iwlwifi
09:20<gsimmons>lsbit: OK. Just to confirm, what does "apt-cache policy linux-image-amd64 | grep Installed" return?
09:20<lsbit>Installed: 3.14+59~bpo70+1
09:22<gsimmons>Right, the packages are installed. Yet, you're still booting into your custom kernel. You would want to restart your system and boot with the wheezy-backports version (linux-image-3.14-0.bpo.2-amd64).
09:24<lsbit>I'll try
09:25-!-lsbit [] has quit [Remote host closed the connection]
09:25-!-AzaToth [] has joined #debian
09:25-!-FlowRiser [] has joined #debian
09:28-!-lsbit [] has joined #debian
09:29<lsbit>I've reboted
09:29<lsbit>doesn't show wlan0
09:29<gsimmons>lsbit: What does "uname -r" report now?
09:31<gsimmons>lsbit: OK. Please provide the output of "dmesg | grep iwlwifi" and "lspci -nnk" at a paste site.
09:33<lsbit>first one
09:34<lsbit>and second
09:35<gsimmons>lsbit: Your system doesn't seem to have the 7260 device firmware present. What does "apt-cache policy firmware-iwlwifi | grep Installed" return?
09:35-!-mdik is now known as Guest94
09:35-!-mdik [] has joined #debian
09:36<lsbit>Installed: 0.36+wheezy.1
09:36<lsbit>I concluded by this site
09:36<lsbit>that i've 7260 device
09:37-!-Guest94 [] has quit [Ping timeout: 480 seconds]
09:37<gsimmons>Yes, we know.
09:37<gsimmons>You need to install firmware-iwlwifi from wheezy-backports (which provides version 0.41~bpo70+1). Please ensure "contrib non-free" is present for your backports sources, then run "apt-get -t wheezy-backports install firmware-iwlwifi" to install.
09:37-!-duglas [] has quit [Quit: Leaving]
09:40-!-Rykun [] has quit [Ping timeout: 480 seconds]
09:40-!-FlowRiser [] has quit [Remote host closed the connection]
09:41-!-JanC [] has joined #debian
09:41<lsbit>it is instaling now
09:41<lsbit>my mistake
09:42<lsbit>I didn't included non-free backports
09:42<lsbit>should I reboot
09:42<gsimmons>No problem. Once that's installed, run "modprobe -r iwlwifi && modprobe iwlwifi" to reload the driver, for it to access that firmware.
09:42<gsimmons>An interface (e.g. wlan0) should then be present on your system.
09:43<lsbit>its showed up :)
09:43<lsbit>with iwconfig
09:43<lsbit>should I do some other configuration
09:44<lsbit>or I can try wifi right now?
09:44<gsimmons>You can go ahead and configure your wireless interface. You probably would want to remove your custom kernel now, given that you won't be using it.
09:46<lsbit>it wasnt custom I just compiled the source cause I didnt know for bacports :)
09:46-!-Eremiell [] has quit [Ping timeout: 480 seconds]
09:46<lsbit>what is the best way to remove it
09:47<lsbit>is it ok to remove wheezy original kernel also?
09:50<gsimmons>You can remove the Linux 3.2 kernel package (linux-image-3.2.0-4-amd64) if you won't have any need for it. As for your custom kernel: did you generate and install a package for it?
09:55-!-lsbit [] has quit [Ping timeout: 480 seconds]
09:57-!-dvs [] has quit [Ping timeout: 480 seconds]
10:02-!-thunderrd [~thunderrd@] has quit [Ping timeout: 480 seconds]
10:03-!-lsbit [] has joined #debian
10:05-!-thunderrd [~thunderrd@] has joined #debian
10:07<lsbit>I've done it now I'm writing over wifi :)
10:10-!-lsbit [] has quit [Remote host closed the connection]
10:18-!-ToApolytoXaos [~ToApolyto@] has joined #debian
10:23-!-klando [] has quit [Ping timeout: 480 seconds]
10:32-!-centrx [] has joined #debian
10:33-!-MY123 [] has quit [Ping timeout: 480 seconds]
10:34-!-FlowRiser [] has joined #debian
10:35-!-eljefe_ [] has quit [Ping timeout: 480 seconds]
10:50-!-holmgren [] has quit [Ping timeout: 480 seconds]
10:53-!-EmleyMoor [] has quit [Read error: No route to host]
10:57-!-mode/#debian [+l 567] by debhelper
10:58-!-lsbit [] has joined #debian
10:59-!-monod [~monod@] has quit [Quit: Quit]
11:10-!-Big-Blue [] has joined #debian
11:10-!-spippi [] has quit [Read error: Connection reset by peer]
11:10-!-spippi [] has joined #debian
11:11-!-Scratso [] has joined #debian
11:11<Scratso>Hi, could anyone help me?
11:12<petn-randall>Hi Scratso, don't ask to ask, just ask your actual question. :)
11:13-!-Iridos [] has quit [Remote host closed the connection]
11:14<Scratso>oh, okay. Well, I got Debian a few says ago and it wont boot up. omething about "Duplicate or bad block in use" when loading /dev/sda6 and then fsck exits with code 4 or something
11:15<Scratso>It says the block message at about 70% on the little loading thing that shows below a message saying that /dev/sda6 contains a bad file system or something
11:15-!-lsbit [] has quit [Remote host closed the connection]
11:17<centrx>Scratso, You successfully installed and it was working fine before?
11:25<Scratso>it worked for like 2 hours, then I shut my computer off and wont start up
11:25<centrx>Scratso, Sounds like a hardware problem with your disk. You can diagnose/fix it with fsck/badblocks
11:25<Scratso>it originally hung at /dev, but a google search suggested for me to add nomodeset to a line and it removed that issue, not sure if this is connected though
11:25-!-mentor [] has joined #debian
11:26<centrx>e2fsck -c <device>
11:27<Scratso>...what do I put instead of <device>?
11:27<centrx>You may need to boot up with a rescue disk to scan the root drive
11:27<centrx>Scratso, /dev/sda6
11:27<centrx>Scratso, Based on your error message, that's it
11:29<Scratso>k, it's checking for bad blocks
11:31<centrx>Scratso, Physical parts of your disk may be broken, but when they are marked as broken the rest of the disk can be used.
11:32<centrx>Scratso, Another possibility is your disk is failing irreversibly. In which case, this scan will mark any bad blocks, but more may come and problems continue.
11:33<Scratso>and I can't access the BIOS :/
11:33<Scratso>(never could)
11:35-!-Cylus [] has quit [Ping timeout: 480 seconds]
11:37-!-gsb [~gsb@] has joined #debian
11:38-!-spippi [] has quit [Ping timeout: 480 seconds]
11:40-!-jalalsfs [] has quit [Read error: Connection reset by peer]
11:40-!-jalalsfs [] has joined #debian
11:42-!-variable_ [] has joined #debian
11:45-!-skitt [] has joined #debian
11:48-!-spippi [] has joined #debian
11:50<oldlaptop>Scratso: if there are any bad blocks, you need to replace the hard disk. It's quite probable that means it's failing entirely, and you probably want to replace it before that happens
11:50<oldlaptop>although if you're keeping backups like you're supposed to it won't be a huge problem ;)
11:52-!-Blacker47 [] has joined #debian
11:53<Scratso>how can you backup disks?
11:54-!-WangDang [] has joined #debian
11:54<WangDang>when did debian start requiring the registration of nicks in order to be able to join the chat?
11:55<WangDang>I've always just joined in the past. Had to register today
11:56-!-jalalsfs [] has quit [Ping timeout: 480 seconds]
11:58<gsb>oldlaptop: is it advisable to reformat hard disk by telling mkfs to avoid bad blocks?
11:59<gsb>oldlaptop: e.g. using -c option or -l <filename> option
11:59-!-jalalsfs [] has joined #debian
11:59<oldlaptop>and then what happens more blocks go bad? :|
12:00<oldlaptop>if at all possible you don't want to use that disk, certainly don't rely on it
12:00<oldlaptop>(it's dangerous to rely on *any* disk, though...)
12:00<Scratso>relying on disks is bad?
12:00<oldlaptop>there is a universal conspiracy
12:00<oldlaptop>all storage devices are out to get you
12:01<centrx>Scratso, Anything important should always be backed up, on another disk, offsite
12:01<oldlaptop>they want to destroy your data, because they hate you
12:01<oldlaptop>don't let them get away with it!
12:01<oldlaptop>more seriously, no storage device is 100% reliable, failures happen.
12:01<Scratso>centrx, what about Dropbox?
12:01<oldlaptop>Dropbox counts
12:02<oldlaptop>stuff you put on "cloud" services can't be considered private though
12:02<Scratso>is it suitably realiable?
12:02<oldlaptop>if Dropbox know what they're doing, it is
12:02<gsb>oldlaptop: yeah you are right. bad blocks tend to increase
12:03<oldlaptop>(of course Dropbox could go out of business tomorrow and take all your data with them - but they probably won't lose anything otherwise)
12:03<Scratso>hmm... this block check appears to be doing 1% a minute...
12:03<oldlaptop>they have all kinds of tricks to maintain essentially 100% availability of your data
12:03<Scratso>ah. I managed to get 50gb storage with Dropbox lol
12:04<oldlaptop>they will have RAID arrays so that when a hard disk fails they can simply swap it for a new one without anyone else knowing or caring
12:04<oldlaptop>if for some reason a whole array gets killed they will have their own offsite backups
12:04<oldlaptop>they do this stuff for a living, they're good at it :)
12:04<oldlaptop>But you can't entrust data to them and expect it to be secret
12:05<centrx>It's an infinite regression of backups.
12:05<centrx>Your backup/cloud provider has its own backup service which has its own backup service, ad infinitum
12:05<oldlaptop>if that's a problem you need to encrypt the data yourself before you send it to them
12:05<oldlaptop>(and then make sure you don't lose the key... :))
12:06<Scratso>this block check has done about 33% and it says "0/0/0 errors"
12:07<Scratso>why so many 0s
12:08-!-skitt [] has quit [Ping timeout: 480 seconds]
12:08-!-mkoskar [] has joined #debian
12:09-!-smulverine [] has quit [Quit: WeeChat 0.4.2]
12:09-!-spippi [] has quit [Read error: Connection reset by peer]
12:18-!-integfred [] has joined #debian
12:18<integfred>Hi, does anyone know where I can find the debian deblob script for the linux kernel?
12:19<integfred>I looked at linux-libre but it stops the user from loading non-free if they wish.
12:20<centrx>integfred, You can install the firmware-linux-nonfree package in Debian to get that non-free firmware back
12:20<integfred>centrx, I'm looking to build a new kernel, which I want deblobbed
12:20<centrx>integfred, You can download the source package and look at it to see what it does
12:20-!-oitofelix [] has joined #debian
12:20<centrx>integfred, You can build a new kernel from out of the Debian source package, result is a Debian package
12:21<integfred>centrx, I've downloaded the sources for kernel-package but cannot seem to find the deblob script
12:22-!-otherflow [] has quit [Quit: Quitte]
12:22-!-MY123 [] has joined #debian
12:22<integfred>Was the kernel deblobbed manually?
12:24<centrx>integfred, deblob is apparently something not used by Debian at all
12:25<integfred>so there isn't a script to remove blobs from a vanilla kernel? I thought squeeze had all it's blobs removed and put in firmware-linux-nonfree?
12:31<integfred>centrx, what I'm really asking is how blobs are removed from a debian kernel, and how firmware-linux-nonfree package is generated?
12:31-!-gsb [~gsb@] has quit [Quit: leaving]
12:37-!-bsc [~balasanka@] has joined #debian
12:39-!-frangor [] has quit [Quit: WeeChat 0.4.3]
12:40<centrx>integfred, Debian uses its own package management system
12:40<integfred>is centrx a bot?
12:40<centrx>integfred, That is used to manipulate the upstream source package and output the de-blobbed compiled Debian package
12:41<integfred>oh okay, sorry
12:41<integfred>so how would I do that?
12:41-!-Walex [] has quit []
12:41<centrx>Use apt-get source to get the Debian source package, if you have deb-src lines in your sources.list
12:42<centrx>Otherwise, you can download it from
12:43<integfred>hrr, okay so the package I'd need to deblob an upstream linux kernel is ..?
13:00-!-integfred [] has quit [Quit: Leaving]
13:01-!-bluewater [] has quit [Quit: Konversation terminated!]
13:08-!-himanshu [~himanshu@] has joined #debian
13:10-!-FlowRiser [] has quit [Ping timeout: 480 seconds]
13:11-!-f10 [] has quit [Ping timeout: 480 seconds]
13:24-!-FlowRiser [] has joined #debian
13:26<Scratso>btw, if this block check turns out with no errors, is that a good thing?
13:27<petn-randall>Scratso: yes, that's a good thing.
13:27<Scratso>but then what would the issue be?
13:28<petn-randall>Scratso: for filesystem errors? Faulty RAM, faulty S-ATA drives, faulty S-ATA controller, faulty mainboard, etc.
13:28<Scratso>, basically, no one would have any clue?
13:32<oldlaptop>pretty much
13:38<petn-randall>Scratso: Did you do an offline fsck of the filesystem, and the problem showed up again?
13:39<Scratso>I just did a e2fsk -c /dev/sda6 when fsck gave me control
13:42-!-FlowRiser [] has quit [Remote host closed the connection]
13:45<Scratso>is that unmounted or...?
13:50<Scratso>okay, it finished the scan finally, and said "done
13:51<Scratso>Updating bad block inodes
13:51<Scratso>Pass 1: <some stuff I can't remember>"
13:55<petn-randall>Scratso: If you flip the power switch, your filesystem will automatically be marked as "dirty". In seldom cases it might not fix itself until you do an offline fsck. If the problem shows up again even though nothing happened (power outage, kernel crash, etc), that's cause for concern.
13:58-!-variable_ [] has quit [Ping timeout: 480 seconds]
14:00<Scratso>ooh, hang on
14:01<Scratso>after the fsck thing it just asked a load of questions about fixing. I just went with all the defaults (y) and then it rebooted and now it boots up, but then sits on a screen with a flashinng underscore as if it's a command terminal... what do I do now?
14:06<oldlaptop>is X failing to start or something?
14:06<oldlaptop>what happens if you try switching to a text VT?
14:08<Scratso>what do you mean?
14:09<oldlaptop>try ctrl-alt-F1
14:10-!-f10 [] has joined #debian
14:12<Scratso>done, logged into that
14:12<Scratso>it asked for my login and password, then came up with a screen. Now what~?
14:12-!-variable_ [] has joined #debian
14:13<Scratso>how can I get into the GUI version?
14:14<oldlaptop>you have a command prompt! Maybe we can find out why X isn't starting now
14:14<oldlaptop>try and stop whichever DM you're using; e.g. "service gdm stop" as root for GDM
14:14<Scratso>I think before it stopped working I did CTRL-ALT-F12 for some reason
14:15<oldlaptop>well that's your problem
14:15<oldlaptop>X will be running on VT 7
14:16<Scratso>then when I couldn't get out of it was stupid and hit the power button attempting to get out. okay.
14:16<oldlaptop>and most probably nothing will be on VT 12
14:16<Scratso>Thank you sooo much. :D
14:18<Scratso>urgh, hang on
14:18<Scratso>ctrl+alt+F7 turns up the same as F12
14:18<Scratso>F7 and above return the same screen... :/
14:19<oldlaptop>so X isn't starting then?
14:19<oldlaptop>did you stop GDM already?
14:20<Scratso>ill do that now. Just logged into root
14:21<oldlaptop>*it's not even running
14:21<oldlaptop>if there's nothing on VT7
14:22<Scratso>gdm: unrecognised service
14:23<Scratso>ooh, service --status-all came up with a list, and showed gdm3
14:23<oldlaptop>yes, maybe you don't use it - whatever DM is installed isn't running anyhow though
14:23<Scratso>should I stop that?
14:23<oldlaptop>gdm3, ah.
14:24<oldlaptop>It's running?
14:24<Scratso>yes, stopped it
14:24<oldlaptop>now (as a normal user) try 'startx'
14:27-!-thunderrd [~thunderrd@] has quit [Ping timeout: 480 seconds]
14:27<Scratso>fatal serveer error: no screens found
14:28<Scratso>*fatal server error: no screens found
14:28<Scratso>xinit: unable to connect to X server: Connection refused
14:31<dpkg>i guess no screens found is not a useful message - it means X11 has a problem somewhere with something. Read your /var/log/Xorg.0.log more closely, and look for the real error, which probably begins with (EE). See also <troubleshooting x>.
14:32-!-kilelme [~kilelme@] has joined #debian
14:36-!-thunderrd [~thunderrd@] has joined #debian
14:46-!-ch3pa [] has quit [Quit: Quitte]
14:47<Scratso>how can I read that?
14:49<oldlaptop>/msg dpkg <topic>
14:50-!-f10 [] has quit [Ping timeout: 480 seconds]
14:50<blast007>Scratso: are you asking how to read the Xorg.0.log file or how to get the additional 'troubleshooting x' information?
14:50-!-valessio [] has joined #debian
14:52-!-frangor [] has joined #debian
14:57-!-sbadia [] has joined #debian
15:03<Scratso>log file
15:04<Scratso>sorry for the wait for the answer
15:12<oldlaptop>see the command less
15:13<oldlaptop>or should I say less(1) :)
15:14-!-himanshu [~himanshu@] has quit [Remote host closed the connection]
15:15<Scratso>I dont understand?
15:16-!-f10 [] has joined #debian
15:16<blast007>Scratso: try 'less /var/log/Xorg.0.log'
15:16<Scratso>oh, i see
15:17<blast007>you can also see a manual for most commands with the man command, for instance, 'man less'
15:17<Scratso>(EE) VESA(0): V_BIOS address 0xd00 out of range is what is says is the actual error
15:18<blast007>are there other lines with EE?
15:19<Scratso>there are lines with (**), (II) and (==) but no more (EE)s
15:20<blast007>and this was all working before the issue with bad file system?
15:21-!-lsbit [] has joined #debian
15:22<Scratso>would nomodeset cause it?
15:23-!-mteufel [] has quit [Ping timeout: 480 seconds]
15:23<blast007>ah, try removing that
15:29<Scratso>now it hangs at Waiting for /dev to be fully populated then blackscreens
15:29<lsbit>Does anybody know how can I get rid of brightness control bug? I have two buttons to adjust screen brightness, but they doesn't behave properly.
15:30<Scratso>CTRL+Alt+Delete won't even turn it off now
15:30-!-kilelme [~kilelme@] has quit [Quit: kilelme]
15:30<lsbit>I've changed parameters in /etc/default/grub (GRUB_CMDLINE_LINUX and GRUB_CMDLINE_LINUX_DEFAULT)
15:31-!-skitt [] has joined #debian
15:31<lsbit>cause I found on askubuntu that it will solve the problem
15:31<lsbit>but it didn't completly
15:32<blast007>Scratso: Ctrl+Alt+Delete may just be disabled in the graphical interface. Try Ctrl+Alt+F1
15:32<Scratso>blast, nothing works
15:32<Scratso>I tried that already, it just blackscreens
15:32<lsbit>cause there was just few brightness levels (5 I guess)
15:33<lsbit>I would be happy if someone can point me in right direction and if there is no any page with explanation to explain what exactly I'm changing
15:34<blast007>Scratso: it it had been working, you might just need to reinstall Debian, though I'd recommend running something like the "Seatools for DOS" CD and doing the long self check of the drive to see if it says it's failing
15:34<Scratso>I can't access BIOS
15:34<Scratso>Never could
15:34<blast007>is that relevant somehow?
15:34<Scratso>It goes Samsung screen, I try all the Function screens, but it just goes and loads the os
15:35<Scratso>...not sure how I could reinstall debiaj
15:35<blast007>can't pick boot order you mean?
15:35<Scratso>blast, yes
15:35<Scratso>because i have to do that in BIOS, which I can't access without Windows 8 which I installed Debian over
15:35<Scratso>well, "alongside", but still cant access
15:35<blast007>is this a desktop or a laptop?
15:36<blast007>and you've tried repeatedly hitting the function key for the boot menu or the BIOS setup key as soon as you turn it on?
15:37<blast007>contact the manufacturer then
15:37-!-mteufel [] has joined #debian
15:37<Scratso>F2 according to samsung, but it doesn't load bios. There isn't any bar saying "BIOS: F2" either
15:38<Scratso>I'm 99% the manufacturer will murder me for not sticking with windows 8, but okay.
15:38-!-valessio [] has quit [Quit: Page closed]
15:38<blast007>try all the function keys, just repeatedly pressing one as soon as you power it on, until it works or goes to the grub screen (and if it hits grub, reboot and try the next)
15:39<Scratso>I've tried that already
15:39-!-Blacker47 [] has quit [Quit: Unfortunately, the internet is not available in Germany because it may contain music for which GEMA has not granted the respective music rights.]
15:40<Scratso>hmm... what do samsung call laptops? Netbooks or notebooks?
15:40<blast007>tried the delete key too?
15:42<oldlaptop>try holding some key down the whole time
15:42<oldlaptop>some machines will get a 'stuck key' error and let you get into setup
15:43<Scratso>is this not fixable through Debian?
15:43-!-bsc [~balasanka@] has quit [Ping timeout: 480 seconds]
15:44<Scratso>btw, what does nomodeset do?
15:45<oldlaptop>tells the kernel not to do certain graphical configuration (mode setting) itself, leaving that up to X
15:45<Scratso>so... why would that make X not work?
15:45-!-ruben_varnish [] has quit [Ping timeout: 480 seconds]
15:46<Champie>I srsly wonder how this worked before and wtf happened that made it not work anymore.
15:48<Scratso>it stopped working when I tried installing steam, got a sudo-user error thing, asked about it, went into CRL+Alt+F12, then turned off the laptop through the power button because I was tired.
15:51<Scratso>when I first tried starting it and experiencing issues, it was /dev populating. Google searched, got told to add nomodeset to the end of the "quiet" line. Then i got the sda6 issue, which is solved. Now there's this X issue
15:53-!-raidensnake [] has joined #debian
15:53<raidensnake>does anyone have an idea how I can restrict user shell access to their home directories?
15:55-!-supaman [] has joined #debian
15:56<Champie>Scratso: considered backing up your data, formatting & re-installing ?
15:56-!-Freejack [] has quit [Read error: Connection reset by peer]
15:56<Scratso>I can't rei-install
15:57-!-FlowRiser [~FlowRiser@] has joined #debian
15:57<Champie>sure can
15:58<Scratso>I can't boot from a disc!
15:58-!-swo [] has quit [Quit: Kein bock mehr.]
15:59<Champie>you can load the installer from grub
15:59<Scratso>... how?
15:59<Scratso>I see no option for that
15:59<Champie> is first hit when googling for "boot debian installer from grub"
16:00<Champie>might need a tweak left or right, but if you've got a working Grub it shouldn't be rocket science
16:01-!-Freejack [] has joined #debian
16:02-!-swo [] has joined #debian
16:02-!-f10 [] has quit [Ping timeout: 480 seconds]
16:04<Scratso> refers to modifying files... Now do I do that in a command prompt?
16:04<Champie>vi ?
16:04<Champie>nano ?
16:05<Champie>you don't need to modify any files by the way
16:05<Scratso>"The procedure for GRUB1 is quite similar. Locate your menu.lst in the /boot/grub/ directory (or sometimes /boot/boot/grub/) and add an entry for the installer, for example (assuming /boot is on the first partition of the first disk in the system):"
16:06-!-Steltek [] has joined #debian
16:06<Scratso>I dont understand
16:06<Champie>just make sure you download the needed files and put them in an easy to remember place
16:07<Champie>then boot up, hit F10 (iirc) for grub boot stuff
16:07<Champie>and type in the grub2 stuff from that page
16:07<Champie>(remove what grub already provides)
16:08<Steltek>Anyone good with VLAN configs in /etc/network/interfaces. Mine won't work for some reason (RTNETLINK answers: File exists when trying to bring up eth0.1) Here's what I have:
16:08<Steltek>(Tried it without the iface eth0 block and with/without auth eth0, no dice)
16:09<Champie>I suppose you installed the 'vlan' package ?
16:10<valdyn>Steltek: that error message sais that the route already exists
16:10<Steltek>I know, but which route and most importantly, why? (This fails while the server is booting.)
16:11<valdyn>Steltek: probably route add -net netmask gw, but how should I know ?
16:11<Scratso>ugh, I'm stuck.
16:13-!-skitt [] has quit [Ping timeout: 480 seconds]
16:14<Champie>Scratso: iirc, you can even install Debian from inside Windows.
16:14<valdyn>Steltek: however, the interface is brought up even if the up command fails, so your error could be something else
16:14<Scratso>what's iirc?
16:14<Champie>"if I recall correctly"
16:16<Scratso>right, well, you can install from inside windows - I tried that on a different machine. But... I dont know how to install from within the debian terminal/grub
16:16<Steltek>Yeah, that's what I'm thinking, but I cannot find what.
16:17<Steltek>Just ran an update-initramfs (maybe something old is stuck in there) and am rebooting...
16:24<Champie>Scratso: you got a 64bit laptop I presume ?
16:24<Scratso>also, when trying to start X, it also comes up with "(EE) Screens found, but none are usable"
16:25<Scratso>along with the VESA error
16:27-!-sig_wall [~adjkru@] has quit [Quit: _]
16:27-!-monod [~monod@] has joined #debian
16:28-!-sig_wall [] has joined #debian
16:30<Champie>well, I can't fix your X for you but I can try to point you to loading the installer from grub
16:34<Champie>which path you take (reinstall or attempting to fix) is your choice
16:37<Champie>it's also 22:40 here so I won't be active here long anymore :)
16:38<Scratso>21:35 here
16:38<Scratso>... though I did wake up around 3:00
16:38<Scratso>in the afternoon xD
16:38<Champie>you in .uk ?
16:44-!-rryoumaa [] has quit [Remote host closed the connection]
16:47<Champie>well, I'm going to leave you in the capable hands of the rest of Google and the rest of the channel :)
16:51-!-ixti [~ixti@] has quit [Ping timeout: 480 seconds]
17:03-!-T0rch [] has quit [Quit: Leaving]
17:04<lsbit>does anybody know something about my problem?
17:04<lsbit>I can copy it again if you didn't notice it
17:06-!-kraiskil [] has quit [Ping timeout: 480 seconds]
17:06-!-InvadeD [] has joined #debian
17:08-!-ixti [~ixti@] has joined #debian
17:13-!-lsbit [] has quit [Quit: Leaving]
17:20-!-variable_ [] has quit [Ping timeout: 480 seconds]
17:23-!-ypcs [] has quit []
17:23-!-jmux [] has quit [Quit: Konversation terminated!]
17:24-!-dvs [] has joined #debian
17:32<raidensnake>does anyone know how to set up a jailed access?
17:36-!-raidensnake [] has quit [Quit: - A hand crafted IRC client]
17:41-!-kamaraju [] has joined #debian
17:42-!-frangor [] has quit [Quit: WeeChat 0.4.3]
17:43-!-xakz [] has quit [Ping timeout: 480 seconds]
17:44-!-ypcs [] has joined #debian
17:45-!-aidalgol [] has joined #debian
17:47<kamaraju>Can some one please tell me which script is run when example(min) is executed in /usr/bin/R ?
17:49-!-Wyzard [] has quit [Ping timeout: 480 seconds]
17:53-!-ixti [~ixti@] has quit [Ping timeout: 480 seconds]
17:55-!-FlowRiser [~FlowRiser@] has quit [Remote host closed the connection]
18:03-!-jalalsfs [] has quit [Ping timeout: 480 seconds]
18:04-!-evanvarvell [] has quit [Read error: Operation timed out]
18:07-!-mode/#debian [+l 560] by debhelper
18:13-!-dererk [] has joined #debian
18:16-!-ixti [~ixti@] has joined #debian
18:20-!-otherflow [] has joined #debian
18:23-!-dsr [~dsr@] has joined #debian
18:26-!-dsr [~dsr@] has quit []
18:29-!-FlowRiser [~FlowRiser@] has joined #debian
18:31-!-dvs [] has quit [Remote host closed the connection]
18:31-!-usrnix [] has joined #debian
18:32-!-dsr [~dsr@] has joined #debian
18:34-!-skitt [~steve@] has joined #debian
18:36-!-ToApolytoXaos [~ToApolyto@] has quit [Quit: Leaving]
18:38-!-ao2 [~ao2@2001:1418:117::1] has quit [Quit: Ex-Chat]
18:47-!-skitt [~steve@] has quit [Quit: Leaving]
18:47-!-skitt [~steve@] has joined #debian
18:50-!-usrnix [] has left #debian []
18:55-!-monod [~monod@] has quit [Quit: Quit]
18:57-!-monod [~monod@] has joined #debian
19:09-!-wompa [] has quit [Ping timeout: 480 seconds]
19:10-!-FlowRiser [~FlowRiser@] has quit [Ping timeout: 480 seconds]
19:11-!-pbn [pbn@2002:d447:1366::22] has quit [Remote host closed the connection]
19:29<Scratso>I have a question. Before, i was having issues starting the GUI (X thing), i got it to work but GNOME 3 wont start
19:33-!-Out`Of`Control [] has quit [Remote host closed the connection]
19:42-!-dutchfish [] has quit [Quit: Splash, leaving the bowl]
19:45-!-Scratso [] has left #debian [Leaving]
19:53-!-rueh [] has quit [Ping timeout: 480 seconds]
19:55-!-ixti [~ixti@] has quit [Quit: WeeChat 0.4.3]
19:58-!-skitt [~steve@] has quit [Ping timeout: 480 seconds]
20:01-!-monod [~monod@] has quit [Quit: Quit]
20:03-!-dererk [] has quit [Ping timeout: 480 seconds]
20:07-!-mode/#debian [+l 552] by debhelper
20:07-!-medicalwei [] has quit [Ping timeout: 480 seconds]
20:39-!-James is now known as Wnzrf_G
20:52-!-M3TA4dotNET [~druski@] has joined #debian
20:53<M3TA4dotNET>Hi there. I was if anyone could help me out with a glx issue i am having when trying to run ryzom_client? just pm if you how to fix it or could help me please?
20:54<M3TA4dotNET>the issue that i am trying to explaing is at
21:10-!-amraw [~amraw@] has joined #debian
21:12-!-skitt [~steve@] has joined #debian
21:20-!-deltron [] has joined #debian
21:21-!-supaman [] has quit [Ping timeout: 480 seconds]
21:22-!-vasil [~quassel@] has joined #debian
21:24-!-aidalgol [] has quit [Quit: ERC Version 5.3 (IRC client for Emacs)]
21:25-!-vasil [~quassel@] has quit [Remote host closed the connection]
21:29-!-vasil [~quassel@] has joined #debian
21:30-!-kamaraju [] has quit [Ping timeout: 480 seconds]
21:30-!-vasil [~quassel@] has quit [Remote host closed the connection]
21:31-!-vasil [~quassel@] has joined #debian
21:32-!-FlowRiser [~FlowRiser@] has joined #debian
21:35-!-neo-laptop [] has joined #debian
21:36-!-Big-Blue [] has quit [Ping timeout: 480 seconds]
21:37-!-neo-laptop [] has quit [Quit: Leaving]
21:45-!-adga [~alejandro@] has joined #debian
21:46-!-ixti [~ixti@] has joined #debian
21:47<txt-file>M3TA4dotNET, this web page is not really readable
21:48<adga>i am registered on debian irc..... :)
21:50-!-FlowRiser [~FlowRiser@] has quit [Ping timeout: 480 seconds]
21:52<adga>when will the new version of debian???
21:54-!-electrobald is now known as but3k4
21:55-!-dererk [] has joined #debian
21:56-!-dererk [] has quit [Remote host closed the connection]
22:03-!-skitt [~steve@] has quit [Ping timeout: 480 seconds]
22:11-!-Cylus [] has joined #debian
22:11-!-Cylus is "" on #php #oftc #debian-offtopic #debian #
22:21<centrx>adga, Probably mid-nextyear
22:21-!-AzaToth [] has quit [Remote host closed the connection]
22:26<adga>centrx, thanks, i am use debian GNU/Linux for 12 years....
22:26<centrx>me too
22:26<centrx>I am using testing
22:31<adga>centrx, you speak spanish?
22:33<adga>centrx, mmmm ok i am speak spanish :), i from Venezuela....
22:33<centrx>I am from the moon (el luna)
22:35-!-jalalsfs [] has joined #debian
22:35<adga>centrx, jajajajaja la luna muy buena esa, i english: hahahaha very good.....
22:35<adga>centrx, jajajajaja la luna muy buena esa, in english: hahahaha very good.....
22:37<adga>centrx, good night and good night for all
22:38<centrx>Fare thee well
22:39-!-phorce1_home [] has joined #debian
22:41<oldlaptop>adga: #debian-es will have spanish speakers
22:46<adga><oldlaptop>: yes pardon for use spanish in the channel...
22:46<adga>good bye...
22:46-!-dererk [] has joined #debian
22:48-!-centrx [] has quit [Quit: Mead error: Connection reset by beer]
22:54-!-dererk [] has quit [Remote host closed the connection]
22:57-!-oitofelix [] has quit [Ping timeout: 480 seconds]
23:07-!-q66 [] has quit [Quit: Leaving]
23:07-!-amraw [~amraw@] has quit [Ping timeout: 480 seconds]
23:12-!-amraw [~amraw@] has joined #debian
23:13-!-skitt [] has joined #debian
23:17-!-vook [~vook@] has joined #debian
23:17-!-ckk [] has joined #debian
23:17-!-adga [~alejandro@] has quit [Ping timeout: 480 seconds]
23:21-!-smulverine [] has joined #debian
23:23-!-skitt is now known as Guest184
23:24-!-Guest184 [] has quit [Quit: Leaving]
23:28-!-amraw [~amraw@] has quit [Remote host closed the connection]
23:34-!-ixti [~ixti@] has quit [Quit: WeeChat 0.4.3]
23:34-!-M3TA4dotNET [~druski@] has quit [Quit: Leaving]
23:35-!-vook [~vook@] has left #debian []
23:52-!-vasil [~quassel@] has quit [Ping timeout: 480 seconds]
23:55-!-pfsense_rookie [] has joined #debian
23:56-!-otherflow [] has quit [Quit: Quitte]
---Logclosed Sun Aug 24 00:00:06 2014