« first day (1947 days earlier)      last day (3025 days later) » 
03:00 - 20:0020:00 - 00:00

8:02 PM
@Dinir What are you using right now?
 
Debian 8, on a lenovo ideapad 500S.
This is only OS I've installed.
 
@Dinir Ah, well, one possible approach is to install Ubuntu. If it works, you can compare the two.
Hardware configuration is always a pain. Don't worry about it.
 
:O......
As a beginner on using this OS, that sounds hugely scary.
 
@Dinir Which part?
 
I've already set few settings on this OS: other language input method and lots of small changes on panel or other settings...
that 'input method' thing is still a nightmare
I hope it is not the only way to progress...
 
8:13 PM
@Dinir @FaheemMitha I haven't read the full scrollback... but that looks awfully like PA is muted...
 
nothing special so far...
 
have you looked a pavucontrol?
 
and PA... PulseAudio?
yes
 
yes, PA = PulseAudio
there are two mutes you need to look at in pavucontrol—one on the output device, one on the app under the playback tab
 
dropbox.com/s/c2r6pq63xizx933/vc.png?dl=0 I don't know this will help, but it's the current state of pavucontrol screen captured.
 
8:15 PM
if either of those is set, under the default PA config, alsa will be muted
 
Okay, I checked Playback tab and everything is unmuted.
 
what about under the playback tab?
 
ok, that all looks good. And you're not hearing anything?
 
Yes. :(
only hear beep sounds
like when I pressed Home button on an empty notepad program.
 
8:18 PM
Ok... could you paste the output of pactl list sinks
 
oh it's long...
Sink #0
	State: RUNNING
	Name: alsa_output.pci-0000_00_1f.3.analog-stereo
	Description: Built-in Audio Analog Stereo
	Driver: module-alsa-card.c
	Sample Specification: s16le 2ch 44100Hz
	Channel Map: front-left,front-right
	Owner Module: 6
	Mute: no
	Volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% / 0.00 dB
	        balance 0.00
	Base Volume: 65536 / 100% / 0.00 dB
	Monitor Source: alsa_output.pci-0000_00_1f.3.analog-stereo.monitor
	Latency: 113847 usec, configured 371519 usec
 
@Dinir you've tried all three output ports (under the "output devices" tab in pavucontrol)? Well, at lest 'analog' and 'spakers'?
 
Default was 'Speakers' and Faheem suggested changing it to 'Analog'
Headphones (unplugged)
I could try plugging earbuds...
No sounds.
 
Hi @derobert
 
It says now 'Headphones (plugged in)', so it knows I plugged them in.
 
8:23 PM
@derobert I ran out of things to suggest.
But I think we must be missing something obvious.
 
you could also try pasuspender -- speaker-test -c 2 -D hw:0 ... and also with hw:1, hw:2, etc. ... see if any of them produce sound. That bypasses PulseAudio.
control-C to stop speaker-test
 
hw:1 and 2 returns error
hw:0 does no sound
 
ok... if you leave the hw:0 one running, can you play with the mute settings in alsamixer to get sound?
 
@derobert What kind of sound should he be getting? I get static alternating between the left and right speaker.
 
@FaheemMitha yep, that's the desired sound
 
8:27 PM
I think I have to hear a pink noise, which is one of my favorite...
 
@derobert Ok.
 
@Dinir ok! then that's working
 
oh wait I mean it's...
I think I supposed to hear that. :(
 
@Dinir Are you hearing alternating noises from each speaker in turn? Or not?
 
Apparently, not...
 
8:28 PM
while running the speaker-test, I opened Audio Mixer (it seems a GUI version of alsamixer) and tried changing mute-unmute.
no sounds yet.
 
I'd avoid the GUI one, it might actually be talking to PulseAudio instead of ALSA...
 
I could post the screen of the Audio Mixer if I should be little more specific.
 
try alsamixer -D hw:0
 
oh thanks I could open second terminal...
 
@derobert incidentally, pactl list sinks gives errors for me.
How would one start debugging that?
 
8:29 PM
I don't know if anything S/PDIF has to do with this problem...
 
@FaheemMitha Depends on the error. You could also try pacmd list-sinks
 
alsamixer -D hw:0 gives the friendly ascii screen.
 
@Dinir Doubtful, S/PDIF is digital output, typically over coax or TOSLINK (fiber).
 
pactl list sinks
Connection failure: Access denied
pacmd list-sinks
Daemon not responding.
 
tried changing 00 <-> MM and yet nothing I can hear.
 
8:30 PM
There isn't any actual problem - sound works.
 
changing this on Master, Headphone, Speaker
 
@Dinir do you have a "front" ?
 
I don't.
Master, Headphone, Speaker, PCM, Mic Boost, S/PDIF, Auto-Mute, Internal Mic Boost
Mice ones are set 0<>0, auto-mute is disabled.
 
And you've got the volume up on Master, PCM, and Speaker, correct?
 
all the way to 100<>100.
 
8:32 PM
What is PCM again?
 
Ok... have you tried plugging the speakers in to all different ports? Even the ones labeled input?
(Most sound hardware is fully configurable as to what each port does... and Linux may have configured it weirdly...)
 
This is rather a portable computer, so I believe they're already connected as a built-in form.
 
Ok. Tells you how much of the scrollback I've read... So this is built-in speakers on a laptop or similar?
 
yes. it's a notebook one.
 
Is this a new Linux install, where sound has never worked? Or was it working then broke at some point?
 
8:36 PM
This is a new install.
Nothing was tested before.
I bought it without any OS installed.
hmm
that speaker-test left something.
Write error: -5,Input/output error
xrun_recovery failed: -5,Input/output error
Transfer failed: Input/output error

Would this be related to the issue?
 
@Dinir yeah, that's a weird error to get from it. Was that it's entire output?
 
I'll paste full log from the line I wrote the command....
dinir@Dinir-Notebook:/$ pasuspender -- speaker-test -c 2 -D hw:0

speaker-test 1.0.28

Playback device is hw:0
Stream parameters are 48000Hz, S16_LE, 2 channels
Using 16 octaves of pink noise
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 64 to 16384
Period size range from 32 to 8192
Using max buffer size 16384
Periods = 4
was set period_size = 4096
was set buffer_size = 16384
 0 - Front Left
Write error: -5,Input/output error
xrun_recovery failed: -5,Input/output error
Transfer failed: Input/output error
I will add this to my current question
 
ok, yeah, that's something clearly broken...
what does aplay -l show?
 
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ID 236 Analog [ID 236 Analog]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
 
Another place you could look for errors is the output of dmesg—that displays the kernel's logs. Beware it will give a lot of output.
For some reason, it seems ALSA (the low-level Linux sound subsystem) is unable to produce any audio output...
 
8:42 PM
I've seen it goes more than 1000 lines...
 
@Dinir what is your lsmod output?
 
While trying to get solve this issue I also was trying to solve a wi-fi problem, and it asks me to reboot. askubuntu.com/questions/708061/…
lsmod...
Module                  Size  Used by
hid_generic            12393  0
usbhid                 44460  0
i915                  837175  0
cfg80211              405538  0
bnep                   17431  2
nfsd                  263032  2
auth_rpcgss            51211  1 nfsd
oid_registry           12419  1 auth_rpcgss
nfs_acl                12511  1 nfsd
nfs                   188136  0
lockd                  83389  2 nfs,nfsd
fscache                45542  1 nfs
sunrpc                237402  6 nfs,nfsd,auth_rpcgss,lockd,nfs_acl
 
Also, what is the output of groups?
 
groups includes audio.
I checked with id dinir to see if I have permission to use audio.
will be unresponsible for a while, let me reboot this machine to try wi-fi...
 
Um, why do you have realtek loaded?
This is an intel onboard card, right?
@derobert Any reason he should have realtek loaded?
@Dinir What is your laptop model?
 
8:46 PM
@Dinir are you running 14.04 LTS? If so, I'd suggest trying sound under a more recent release, just from the Live CD (e.g., from 15.10). The most likely think is, I think, that there is a bug in the kernel sound driver, or it just isn't new enough to support your hardware...
 
rebooted.
 
@FaheemMitha probably probed it as the sound hardware on the system
 
@Dinir I'd blacklist the realtek thing. It may or not be the problem. Regardless, having it loaded isn't helping you.
 
having an SSD for first time is this good...
 
See for example:
1
Q: Sound not working

JasonI am new to ubuntu, but really enjoy it. I do have one issue with setting it up on my computer. It is a GoBook XR-1 and everything works perfectly except there is no sound. I've searched and tried everything that I can think of, even uninstalling ubuntu and trying Windows to see if the speaker...

 
8:47 PM
the model is... Lenovo ideapad 500S.
500S-14ISK
 
@derobert Hmm. But it sounds like he only has the one sound thingy.
 
wiki.debian.org / HowToInstall maybe? has no information about this model.
 
@derobert Any downside wrt blacklisting the realtek?
 
Arrgh
 
@Dinir What does lspci say? Do you have multiple sound cards on this machine?
 
8:48 PM
The link contains some kind of compiling things so I can't rollback the change, and it doesn't work.
:(( NO
00:00.0 Host bridge: Intel Corporation Device 1904 (rev 08)
00:02.0 VGA compatible controller: Intel Corporation Device 1916 (rev 07)
00:14.0 USB controller: Intel Corporation Device 9d2f (rev 21)
00:14.2 Signal processing controller: Intel Corporation Device 9d31 (rev 21)
00:15.0 Signal processing controller: Intel Corporation Device 9d60 (rev 21)
00:16.0 Communication controller: Intel Corporation Device 9d3a (rev 21)
00:17.0 SATA controller: Intel Corporation Device 9d03 (rev 21)
00:1c.0 PCI bridge: Intel Corporation Device 9d10 (rev f1)
 
@FaheemMitha not really... if it doesn't work, you undo it
@FaheemMitha HD Audio implements its own bus, besides the PCI bus...
 
@derobert Ok. So he could just add:
@Dinir Not seeing any realtek audio devices in there.
 
I could want to reinstall the whole Debian now...
I have to consider realtek because of wireless issue,
 
So just add blacklist snd_hda_codec_realtek:
 
seems it's more related to Qualcomm device.
 
8:50 PM
in " /etc/modprobe.d/blacklist.conf"
 
...was I trying to use realtek model to produce sound?
I will.
 
@Dinir It's loading a realtek sound module.
Which it has no reason to do, as far as I can tell.
 
anthony@Watt:~$ lspci | grep -i audio
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
... and yet, this board uses a Realtek ALC887
 
If the wireless issue doesn't go well... I'll format and reinstall right now.
 
anthony@Watt:~$ lsmod | grep -i ^snd_hda_codec
snd_hda_codec_hdmi     53248  1
snd_hda_codec_realtek    73728  1
snd_hda_codec_generic    65536  1 snd_hda_codec_realtek
snd_hda_codec          94208  5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel,snd_hda_controller
 
8:52 PM
and then I can investigate to this problem again.
 
@derobert It's showing up as unused in his output. Is Realtek mentioned in lspci?
@Dinir reinstalling for no particular reason isn't useful, imo.
 
The answer requires me to run a script
it seems do lots of things that I can't make it back if it failed...
And I am frustrated on having not working things left here and there on the computer...
as I am not an expert on using this OS.
 
@Dinir What answer?
 
@FaheemMitha I'd guess there is something in dmesg about the realtek codec failing to initialize
 
While trying to get the sound issue, I also try to get to wi-fi. askubuntu.com/questions/708061/…
 
8:55 PM
@derobert Hmm. @Dinir, have the logs have anything about realtek?
 
do you mean dmesg one?
what should I use as keyword for grep...
 
yeah, dmesg | grep -i realtek
 
@derobert And to return to my issue, what do you suggest (if anything) about debugging pactl?
@derobert grep -i ealtek
 
@FaheemMitha do you have PA running???
 
no output. @derobert
 
8:56 PM
@derobert I think so.
How should I check?
@Dinir I'd try blacklisting as I suggested. You can always undo it.
Or you could just try unloading the realtek driver manually and see what happens.
 
Yep. I can undo blacklist command... as long as I don't forget I made blacklist on /etc/......modprobe.d/ .
 
@FaheemMitha err, ps should work for that. See if the daemon is even running.
 
@derobert Would rmmod snd_hda_codec_realtek be reasonable?
 
shrug should be harmless enough. Unload it and reload it, and see if anything shows in dmesg
 
ps aux | grep pulseaudio
faheem 4933 0.2 0.0 386876 10272 ? S<l Jan31 33:49 /usr/bin/pulseaudio --start --log-target=syslog
faheem 4941 0.0 0.0 122876 276 ? S Jan31 0:00 /usr/lib/pulseaudio/pulse/gconf-helper
@Dinir Ok. Try that.
 
8:58 PM
Sep 01 20:57:15 Watt kernel: snd_hda_codec_realtek hdaudioC0D2: autoconfig for ALC887-VD: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line
Sep 01 20:57:15 Watt kernel: snd_hda_codec_realtek hdaudioC0D2:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Sep 01 20:57:15 Watt kernel: snd_hda_codec_realtek hdaudioC0D2:    hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
Sep 01 20:57:15 Watt kernel: snd_hda_codec_realtek hdaudioC0D2:    mono: mono_out=0x0
Sep 01 20:57:15 Watt kernel: snd_hda_codec_realtek hdaudioC0D2:    dig-out=0x11/0x0
... that's the realtek lines I get when booting
 
Why is an Intel device using Realtek?
Also, Realtek is the Spawn of Satan. I just wanted to mention that.
 
@FaheemMitha The Intel chipset provides the HD Audio bus. (And also the HDMI audio codec). The mobo manufacturer picked to use a Realtek codec for analog and S/PDIF input & output, at least on my board.
 
@derobert That's a bit over my head, but Ok.
@Dinir Try unloading the realtek thing. See if it makes any difference to the sound. Alos see if the logs say anything.
It's possible it is unused but is blocking the sound in some way.
 
@FaheemMitha HD Audio implements a bus, sort of like a PCI bus. You (or, really, to mobo maker) can connect different devices (chips, called "codecs") to that bus to actually handle sound I/O.
Realtek makes a lot of those codecs.
 
@derobert Oh. But it looks like it is not being used in his case. There is a 0 alongside it.
Is that normal?
 
9:05 PM
@FaheemMitha No. At least not when sound is open. Not sure when nothing has the sound device open.
 
I screwed on wireless setting.
After set the sound problem. I'll reinstall the OS and try make the setting again.
Now... I should... unload realtek thing.
let me scrollback on chat
I blacklisted the sdn_hda_codec_realtek
what next is...
see dmesg again
dmesg | grep -i realtek still gives no text.
headphone was muted
 
after the blacklist, you need to run update-initramfs -u and also reboot
then after booting confirm via lsmod | grep realtek that it wasn't loaded.
 
seems I have bunch of error message...
and it seems not related to sound issue.
 
@Dinir Anthony thinks the realtek thing is not the problem...
 
Yes, could be not related.
and here goes reboot
okay, lsmod reveal no realtek related thing.
no output.
and still no sound.
 
9:14 PM
you could try "modprobe snd_hda_codec_realtek" and see if (a) that adds anything to dmesg; (b) sounds works
or the weird steps @FaheemMitha found in askubuntu.com/a/377810 ... which I think can best be described as working around some bug.
 
to both (a) and (b): nothing changed.
 
Huh.
Which logs are you looking at?
Did you look at /var/log/kern.log?
 
tried cat /var/log/kern.log | grep realtek and got one line saying about Modules linked in.
no I get a result now?
 
@Dinir Just scan the whole thing. It's probably not long.
@Dinir What?
 
it's 5300 lines.
 
9:19 PM
@Dinir Oh. Well, look at recent entries.
 
this is a single line.
for... cat /var/log/kern.log | grep realtek.
 
Ok, we're seeing no evidence that the realtek thing is the problem.
Before you do anything else, check alsamixer.
I mean, without the realtek stuff.
 
nothing special......?
nothing special except headphone got muted again.
 
wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS ... might help. But I'd just try booting a newer Ubuntu and seeing if it works.
 
9:26 PM
@derobert Well, he's using Debian atm. I did suggest trying Ubuntu earlier.
If it works, he could use it to debug the Debian install.
 
@FaheemMitha Oh! I thought he was on 14.04 LTS.
 
Not the most heroic way to debug, but we've tried the obvious.
 
It was my previous one I used...
 
@derobert He said earlier he's on Debian.
 
Jessie?
 
9:27 PM
@Dinir What version of Debian?
 
Jessie.
jessie 8
 
Ah.
Well, it's worth trying a recent version of Ubuntu. Like I said, if it works, you can compare the config.
 
Could you try installing linux-image-4.3.0-0.bpo.1-amd64 from jessie-backports?
 
I was trying to find anything to help searching on wiki.debian.org, and it was not helpful enough for a beginner.
 
@derobert You think this might be a kernel bug?
 
9:28 PM
I want to ask that if that 'linux-image' is big.
 
@FaheemMitha Yep. And 4.3 should give the realtek debug messages.
 
@derobert Ok. Sounds like a plan.
@Dinir Do you know how to do that?
 
I... thought I already added that backport one to my repository list......
 
@Dinir Not sure the exact download size, maybe 50MB?
 
Size: 35521412
 
9:29 PM
It isn't big though the name feels like it's heavy ISO like one.
 
Installed size.
@Dinir Is your concern hard disk space?
 
@Dinir if backports is already in the sources.list, then that should be available in your package manager
 
@Faheem more like concerning about installation time going long.
 
@Dinir It shouldn't take long to install, if your connection is reasonably fast.
@Dinir don't forget to remove that blacklist entry - the realtek thing.
 
okay... I should want to add 'backport' on the section in here? dropbox.com/s/iw7vigkmxsdoloi/backporr.png?dl=0
remove blacklist...
 
9:31 PM
@derobert And he needs to run initramfs after doing that, right?
 
@FaheemMitha that'll happen automatically on kernel image install
@Dinir if backports isn't already in the list, you'll need to add a new one for it---it's not just a section
(I can't tell what's there if you scroll down)
 
@Dinir deb http://httpredir.debian.org/debian/ jessie-backports main contrib non-free
 
"jessie-backports" is the distribution in FaheemMitha's line.
 
/etc/apt/sources.list.d/sources.list is where I should go...
 
@Dinir Just post the output of /etc/apt/sources.list.
 
9:34 PM
#

# deb cdrom:[Debian GNU/Linux 8 _Jessie_ - Official Snapshot amd64 LIVE/INSTALL Binary 20160124-15:59]/ jessie main

deb cdrom:[Debian GNU/Linux 8 _Jessie_ - Official Snapshot amd64 LIVE/INSTALL Binary 20160124-15:59]/ jessie main

deb ftp.kr.debian.org/debian jessie main contrib non-free
deb-src ftp.kr.debian.org/debian jessie main

deb security.debian.org jessie/updates main
deb-src security.debian.org jessie/updates main

# jessie-updates, previously known as 'volatile'
not added obviously.
 
@Dinir Ok, just add what I put in there. And consider using httpredir. I'm using it. Mostly it works well.
 
deb ftp.kr.debian.org/debian jessie-backports main contrib non-free
deb-src ftp.kr.debian.org/debian jessie-backports main contrib non-free
 
@Dinir It's latish. I'm going afk now. Let me know how it goes.
 
that should be it
 
@derobert Take care.
 
9:36 PM
Thanks for inviting me here, @Faheem.
 
(I'm not entirely sure the Korean mirror has jessie-backports, if it doesn't then use that httpredir line FaheemMitha posted... or just use the httpredir line anyway.)
 
httpredir is generally good, imo.
 
changed to httpredir
changed jessie to jessie-backports
can't find linux-image-4.3.0..... on synaptic.
 
@Dinir sorry, forgot to mention update the package list
 
sorry I often forget I have to do update. :(
finally installing the image.
httpredir couldn't be fetched so I got it back to ftp.kr.
installed...
 
9:42 PM
also, whatever your wifi card is... there might be a backports firmware package for it. I'd install that as well
 
I have to know how to find correct package for a device I have...
I should run initramfs, right?
update-initramfs -u...
 
@Dinir when you install a kernel, it does that for you
 
oh...
okay, now reboot...?
 
yep
if it doesn't boot, you can pick the old kernel in grub (to get the machine back up)
 
okay now I got stucked.
[ OK ] Started Update UTMP about System Runlevel Changes.
was the last line.
I am trying 4.3.0 on recovery mode.
I am now on root terminal.
startx doesn't work.
will get back to old kernel...
 
9:49 PM
ok... what about speaker-test?
 
...could it be different though I am getting back to old kernel?
or... I can try speaker-test on the recovery mod.
 
yeah, try it from the recovery
if it fixes that problem, just need to figure out why X failed.
 
pasuspender -- speaker-test -c 2 -D hw:0
Connection failure: connection refused
pa_context_connect() failed: Invalid argument
 
Leave out the pasuspender -- part
PulseAudio isn't running in recovery mode
 
astonished.
I hear static.
rather scary, I now hate pink noise.
 
9:53 PM
control-C it and put a -t wav at the end of the line
 
so the end of the line looks like -c 2 -D hw:0 -t wav?
 
yeah
 
some human voice.
 
yep, saying something like "front left", "front right", correct?
 
right.
 
9:54 PM
And it sounds OK? Not garbled or anything?
Then that means upgrading to 4.3 makes sound work...
 
I am worried that my trial on correct wifi setting screwed the x...
garbled?
sounds... clear?
 
@Dinir yeah, clear. Not full of static or noise.
 
it say left when 0 -front left appears.
and voice was clear.
okay I could write answer to my own question that installing linux-image-4.3.0... could solve the problem.
still the boot process is not properly finished.
 
Ok. You'd want to check /var/log/Xorg.0.log to see if that gives a reason that X fails to start
 
125 lines...
I coud grep (WW) and (EE)?
 
9:57 PM
yeah
 
...hmm
 
also, I'd guess that 4.3 + installing firmware-iwlwifi from jessie-backports will fix your wifi. At least if its an Intel wifi chipset.
 
anyway I can get both of them at single try?
QualComm Atheros, I think.
grep ([W|E]{2}) doesn't give back proper answer...
 
@Dinir firmware-atheros then
 
thanks. I can try later as X works.
..
Is it like simply I put sudo apt-get install firmware-atheros?
I don't get how to install firmwares.
 
9:59 PM
@Dinir grep -E 'WW|EE' should get close enough
 
put that apt-get command after including backports on repositories?
 
@Dinir sudo apt-get install -t jessie-backports firmware-atheros
you have to tell it you want to pull from jessie-backports (with -t), it won't by default.
 
even when I added the repositories...
but I still have to do that command after adding the repository, right?
 
@Dinir yeah, the backports repositories are configured like that. You only grab things you need from them
yes
 
anyway, grep gives...
it found no screens.
[369.085].
 
10:01 PM
@Dinir Let @derobert do it. It was his suggestion.
@derobert So, sound is now working?
 
(WW) intel(0): Unknown chipset
(EE) Screen(s) found, but none have a usable configuration.
(EE)
(EE) no screens found(EE)
 
@FaheemMitha nah, he can write it up... I've got to run soon
 
@Faheem Yes. I traded them for whole X.
 
@Dinir apt-get install -t jessie-backports xserver-xorg-video-intel will probably fix that
 
`E: The value 'jessie-backports' is invalid for APT::Default-Release as such a release is not availabe in the sources
I should change again, from ftp.kr to httpredir.
could not resolve any of them...
oh wait I am not online
so...
I pull the lan cable and will plug it in to notebook
:(
I will try all of them and tell the result.
af this channel.
 
10:05 PM
ok. You should be able to have both ftp.kr and httredir in your sources.list. You can just add another line.
and remember to run update (apt-get update or apt update on the command line)
Unfortunately, I have to run...
 
So, sound is now working with the new kernel, but now X is not? Bummer.
 
What a twist, @Faheem...
Thanks for helping @derobert.
 
@Dinir Was X working with the old kernel?
 
yes.
It feels like I owe you a lot.
 
Strange. Also lsmod | grep realtek
 
10:11 PM
snd_hda_codec_realtek, snd_hda_codec_generic, snd_hda_codec, snd_hda_core, snd are found.
I added both ftp.kr and httpredir, and any of them doesn't work on apt-get update.
Always get Could not resolve 'ftp.kr.debian.org' or 'httpredir.debian.org'.
I will try running on old kernel.
no
old kernel also seems not work...
I can... now...
now I know little about how to get over the problem,
though it could not be a complete guide...
and I can't boot again properly...
I rather just reinstall the whole thing.
 
 
1 hour later…
11:34 PM
installing linux-image-4.3.0 always makes problem.
This time I can successfully remove it to get back to old kernel.
 
03:00 - 20:0020:00 - 00:00

« first day (1947 days earlier)      last day (3025 days later) »