<hanetzer>
some specific firmware is needed, if you check out archlinux-arm's veyron-firmware or veyron-firmware you can see what files you need
<JohnDoe2>
well the problem is I have no idea how to install drivers on *nix
<JohnDoe2>
but thank you I'll look into that
<hanetzer>
the firmware needs to be dropped in /lib/firmware/{???}
<JohnDoe2>
oh yeah I did that using chromium's own /lib/firmware
<hanetzer>
most drivers are available in the linux kernel packages by default
<hanetzer>
you may need to install a specific kmod package
<JohnDoe2>
yeah that's why I'm hoping that RockMyy will build a newer kernel
gnufan_home has quit [Quit: Leaving.]
vicencb has quit [Quit: Leaving.]
vstehle has quit [Ping timeout: 246 seconds]
vstehle has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
JohnDoe_71Rus has joined #linux-rockchip
default__ has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
cyteen has quit [Read error: Connection reset by peer]
cyteen has joined #linux-rockchip
JohnDoe_71Rus has quit [Ping timeout: 246 seconds]
ayaka has quit [Ping timeout: 250 seconds]
Substring has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
stikonas has joined #linux-rockchip
Substring has quit [Quit: Leaving]
_whitelogger has joined #linux-rockchip
lykt has quit [Ping timeout: 245 seconds]
field^Mop has joined #linux-rockchip
gnufan_home has joined #linux-rockchip
lykt has joined #linux-rockchip
default__ is now known as ldevulder
<EmilKarlson>
IIRC the driver was brcmfullmac
<EmilKarlson>
should be in linux-4.9, if enabled
<EmilKarlson>
CONFIG_BRCMFMAC
<EmilKarlson>
I guess you should see in kernel log, if it's not finding the fw.
urjaman has quit [Read error: Connection reset by peer]
vicencb has joined #linux-rockchip
fireglow has quit [Remote host closed the connection]
fireglow has joined #linux-rockchip
kaspter has quit [Quit: kaspter]
rich0 has quit [Quit: rich0]
rich0 has joined #linux-rockchip
urjaman has joined #linux-rockchip
Substring has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
JohnDoe_71Rus has joined #linux-rockchip
Substring has quit [Quit: Leaving]
<sphalerite>
I have a SuzyQable and connecting it to my gru-bob chromebook does make several serial devices show up in /dev, but the chromebook's kernel doesn't seem to talk to ttyS1 as I expect it to. None of the ttyS* on the chromebook seem to be connected to that either.
<sphalerite>
Is there a kernel parameter or something that I need to set to get a serial console?
warpme_ has joined #linux-rockchip
warpme_ has quit [Client Quit]
gnufan_home has quit [Ping timeout: 258 seconds]
<hanetzer>
sphalerite: yeah, prolly either a kparam or using whatever distro you have's agetty starting thing
<hanetzer>
eg, inittab, /etc/init.d/agetty.ttyN, or that systemd service I forget
<sphalerite>
hanetzer: none of the /dev/tty* things on the chromebook seem to connect to it
field^Mop has quit [Ping timeout: 245 seconds]
gnufan_home has joined #linux-rockchip
<mmind00>
sphalerite: shipping kernels and bootloaders do no do serial (for performance reasons I guess)
<sphalerite>
mmind00: hmm ok, which config parameter would it be?
<sphalerite>
(it's not a chromeos kernel, but who knows, maybe the relevant option is disabled)
<mmind00>
sphalerite: don't really know for the kernel side ... I just know for coreboot it requires actually flashing a dev-image
<mmind00>
sphalerite: hmm, if it isn't a chromeos kernel, then it should just work with serial though
<mmind00>
sphalerite: your kernel commandline should of course contain something like a console=ttyS2,115200 or so
<mmind00>
hmm, or that could also be covered by the stdout-path in the dt ... I somehow don't look at that too often
<sphalerite>
mmind00: well, echo hello > /dev/ttyS2 also doesn't show anything (that's what I meant by "None of the ttyS* on the chromebook seem to be connected to that either.")
stikonas has joined #linux-rockchip
return0e has quit [Remote host closed the connection]
MoeIcenowy has quit [Quit: ZNC 1.6.5+deb1+deb9u1 - http://znc.in]
MoeIcenowy has joined #linux-rockchip
return0e has quit [Remote host closed the connection]
adjtm has quit [Remote host closed the connection]
adjtm has joined #linux-rockchip
<JohnDoe2>
come on man it can't be that damn hard. This pisses all over linux being friendly. How do you install a wifi driver? Nothing works, I've compiled kernels, flashed every image I could find, no wifi detected on this POC c201
field^Mop has quit [Ping timeout: 246 seconds]
return0e has joined #linux-rockchip
<vagrantc>
i've only ever used the c201 with a usb wifi adapter ... or maybe i did install the firmware for it. been so long since it worked at all.
<JohnDoe2>
well this is not so much about the c201 as much as it is finding info on how to install a driver in linux
<JohnDoe2>
that would be a basic thing for any os. I've built hackintoshes in 1/3 of the time I spent on this guy getting it to boot something :)
<JohnDoe2>
I don't get it
<hanetzer>
JohnDoe2: honestly I don't know what your problem is with the c201. It 'just worked' for me
<JohnDoe2>
I'm happy to hear that but my experience has been 2+ days of trying to understand *HOW* to install a wifi driver
<vagrantc>
well, there's the driver and the firmware, for one thing
<JohnDoe2>
yes, so I've been reading but when it comes down to HOW to get them installed, it's a dead end
<JohnDoe2>
chromium already has its firmware so in my mind I could simply copy that from there
<JohnDoe2>
which I did. I copied everything in fact, not just the wifi firmware
<JohnDoe2>
but I have no idea how to get it to scan for stuff. lspci is blank, lsusb doesn't list a network adapter
<JohnDoe2>
I also tried devsus but that's abandoned, it fails to download whatever it needs. dead end.
return0e has quit [Remote host closed the connection]
<JohnDoe2>
alright well thanks for your help guys
JohnDoe2 has left #linux-rockchip [#linux-rockchip]
vicencb has quit [Quit: Leaving.]
stikonas has quit [Remote host closed the connection]