Debian on HP T5325 Thin Client

Wow! good works CV & Gravelrash, I went to bed and now wake up with a display working :)

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

LeggoMyEggo Wrote:
-------------------------------------------------------
> Quick question for bodhi, will the
> kirkwood-t5325.dtb file work to boot with earlier,
> non-Jessie, rootfs'? I ask because I am trying to
> modify an existing 4.1 wheezy flash drive that has
> everything I need already loaded and I would like
> to use the T5325 for those functions.

It should work with older kernel, since DTS has not changed format. But if the kernel is too old, it might not have the required modules or code. Try it, 4.1 is recent.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

> Now I can kwboot fine, and the first thing I'm
> going to do is nuke the current u-boot as it has
> already annoyed me A LOT.

If you look at the HP u-boot patches source code, you are going to be mad, not just annoyed :))

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

just flashed the uboot and envs and stuff on my thinclient n. 1.

During pre-flashing checks I saw this line

[    1.745538] m25p80 spi0.0: found sst25vf080b, expected m25p80

But then the chip was initialized correctly anyway

[    1.751336] m25p80 spi0.0: sst25vf080b (1024 Kbytes)
[    1.756396] 5 cmdlinepart partitions found on MTD device spi0.0
[    1.762342] Creating 5 MTD partitions on "spi0.0":
[    1.767182] 0x000000000000-0x000000080000 : "uboot"
[    1.773411] 0x000000080000-0x0000000c0000 : "sdd_firmware"
[    1.780160] 0x0000000c0000-0x0000000d0000 : "uboot_env"
[    1.786692] 0x0000000d0000-0x0000000e0000 : "permanent_uboot_env"
[    1.794112] 0x0000000e0000-0x0000000f0000 : "hp_env"

So I went ahead with the flashing.

Now my first box has been liberated and boots fine to Debian. Thanks bodhi. :)


During boot I see these info about GPU and sound chip (it's different from the one posted by CV):

[   20.592829] xgifb: module is from the staging directory, the quality is unknown, you have been warned.
[   20.670371] xgifb 0000:01:00.0: Relocate IO address: 10000 [00010030]
[   20.686414] orion_wdt: Initial timeout 21 sec
[   20.726949] marvell-cesa: probe of f1030000.crypto failed with error -524
[   20.753354] xgifb 0000:01:00.0: enabling device (0140 -> 0143)
[   20.759255] xgifb 0000:01:00.0: chipid = 32
[   20.838550] xgifb: SR14=51 DramSzie 2000000 ChannelNum 1
[   20.865055] asoc-simple-card sound: alc5621-hifi <-> spdif mapping ok
[   20.896330] xgifb 0000:01:00.0: Framebuffer at 0xe0000000, mapped to 0xe1000000, size 32768k
[   20.952751] xgifb 0000:01:00.0: MMIO at 0xe4000000, mapped to 0xe0e00000, size 256k
[   21.079844] xgifb 0000:01:00.0: No or unknown bridge type detected
[   21.107889] xgifb: Default mode is 800x600x16 (60Hz)

EDIT: got console and xorg working, posted in the XGI graphics thread http://forum.doozan.com/read.php?9,26555,26623#msg-26623



Edited 2 time(s). Last edit at 03/12/2016 09:53AM by bobafetthotmail.

Btw, I've seen a cpu frequency env in stock uboot. Does that mean we can bump the frequency to 1.6 Ghz like the nsa325?

the eth controller (behind the eth port) is a marvell one, this guy here Marvell-88E3016 http://www.marvell.com/transceivers/assets/Marvell-88E3016-Fast-Ethernet.pdf

will see if I can swap it with a gigabit one. hoping I can find a pin-compatible one.

It seems they are pin-upgradable to gigabit http://www.marvell.com/transceivers/assets/Marvell-Alaska-88E3015-16-18-PHY.pdf
" In addition, the 88E3016 and 88E3018 are the only single-port FE PHYs available in the industry which are pin-upgradeable to Gigabit Ethernet"

what does "pin-upgradable" mean? I hope it means they are pin-compatible with a gigabit eth controller from marvell, which would be nice.

It seems they do. http://www.marvell.com/transceivers/assets/88E1118R_Technical_Product_Brief.pdf

pins are the same. Need to check others http://www.marvell.com/transceivers/alaska-gbe/

and see if they are fully compatible with the specs of the one we have already.



Edited 3 time(s). Last edit at 03/12/2016 10:17AM by bobafetthotmail.

Nice work there bobbafethotmail!

im trying to flash one of mine from the stock OS, my settings and labels seem to differ from what is expected on the uboot page.

Expected

[    0.000000] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=spi0.0:512K(uboot),256K(sdd_firmware),64K(uboot_env),64K(permanent_uboot_env),64K(hp_env) earlyprintk=serial
[    1.577638] m25p80 spi0.0: m25p80 (1024 Kbytes)
[    1.582271] 5 cmdlinepart partitions found on MTD device spi0.0
[    1.588221] Creating 5 MTD partitions on "spi0.0":

Actual

# dmesg | grep spi 
[    1.070000] Creating 5 MTD partitions on "spi_flash":
# dmesg | grep SPI 
[    0.250000] SPI_CS ....base f4000000, size  16MB 
[    1.070000] SPI Serial flash detected @ 0xf4000000, 1024KB (16sec x 64KB)

Expected

[    1.593062] 0x000000000000-0x000000080000 : "uboot"
[    1.599248] 0x000000080000-0x0000000c0000 : "sdd_firmware"
[    1.606064] 0x0000000c0000-0x0000000d0000 : "uboot_env"
[    1.612592] 0x0000000d0000-0x0000000e0000 : "permanent_uboot_env"
[    1.619970] 0x0000000e0000-0x0000000f0000 : "hp_env"

Actual

[    1.070000] 0x000c0000-0x000d0000 : "u-boot env"
[    1.070000] 0x000d0000-0x000e0000 : "permanent u-boot env"
[    1.070000] 0x000e0000-0x000f0000 : "HP env"
[    1.070000] 0x00000000-0x00080000 : "u-boot"
[    1.070000] 0x00080000-0x000c0000 : "SSD firmware"

Expected

dev:    size   erasesize  name
mtd0: 00080000 00010000 "uboot"
mtd1: 00040000 00010000 "sdd_firmware"
mtd2: 00010000 00010000 "uboot_env"
mtd3: 00010000 00010000 "permanent_uboot_env"
mtd4: 00010000 00010000 "hp_env"

Actual

dev:    size   erasesize  name
mtd0: 00010000 00010000 "u-boot env"
mtd1: 00010000 00010000 "permanent u-boot env"
mtd2: 00010000 00010000 "HP env"
mtd3: 00080000 00010000 "u-boot"
mtd4: 00040000 00010000 "SSD firmware"

flashcp -v uboot.2015.10-tld-2.t5325.mtd0.kwb /dev/mtd0

Expected

Erasing blocks: 8/8 (100%)
Writing data: 512k/0k (100%)
Verifying data: 512k/0k (100%)

Actual

t# flashcp -v uboot.2015.10-tld-2.t5325.mtd0.kwb /dev/mtd0
uboot.2015.10-tld-2.t5325.mtd0.kwb won't fit into /

so thats as far as i can take it from stock. i get the usual fw_setenv error if i try to do this from the prepped environment of a bootable usb when in bodhi's debian - i.e. cant read the information etc.

any thoughts? do we have differing equipment for differing geographic regions?

the upside is that the usb created with an embedded dtb, works fine and dandy with the correct boot_args. so while i could happily just live with this and run on the standard uboot, would be nice to migrate to the new one.



Edited 1 time(s). Last edit at 03/12/2016 10:46AM by Gravelrash.

I flashed mine from debian. I kwbooted the newer uboot first (:P), but you can set the stock uboot to boot into debian too.

> i get the usual fw_setenv error if i try to do this from the prepped environment of a bootable usb when in bodhi's debian - i.e. cant read the information etc.

from inside debian you must open /etc/fw_env.config

and write
/dev/mtd2 0x00000 0x10000 0x10000

instead of the /dev/mtdX xxxxx xxxxx xxxxxx
that you find in there.

this tells fw_printenv where to find stuff.

Inside debian you should have all you need to do this.

install "mtd-utils" so you can get the flashcp utility in Debian

I would try doing this from Debian first, if it still fails, try what I say now. (at your own risk)

from the table posted

dev:    size   erasesize  name
mtd0: 00010000 00010000 "u-boot env"
mtd1: 00010000 00010000 "permanent u-boot env"
mtd2: 00010000 00010000 "HP env"
mtd3: 00080000 00010000 "u-boot"
mtd4: 00040000 00010000 "SSD firmware"

it seems you should

flashcp -v uboot.2015.10-tld-2.t5325.mtd0.kwb /dev/mtd3

as that is the mtd where uboot stays.

and the uboot envs should be flashed in what is called mtd0 in your table.

If you see the size and erasesize, also the adresses above, the actual places of all the mtd partitions are the same, but in HP stock OS they are indexed at weird places (and with less zeroes on top in the addresse, that does not matter).

HP firmware is funky, who knew? :)



Edited 2 time(s). Last edit at 03/12/2016 11:45AM by bobafetthotmail.

post in error



Edited 1 time(s). Last edit at 03/12/2016 11:59AM by Gravelrash.

bobafetthotmail Wrote:
-------------------------------------------------------
> I flashed mine from debian. I kwbooted the newer
> uboot first (:P)

:headbang

> from inside debian you must open
> /etc/fw_env.config
>
> and write
> /dev/mtd2 0x00000 0x10000 0x10000
>
> instead of the /dev/mtdX xxxxx xxxxx xxxxxx
> that you find in there.
>
> this tells fw_printenv where to find stuff.

Still doesnt work... hmmm

> install "mtd-utils" so you can get the flashcp
> utility in Debian

Done

> I would try doing this from Debian first, if it
> still fails, try what I say now. (at your own
> risk)
>
> from the table posted
>
>

> dev:    size   erasesize  name
> mtd0: 00010000 00010000 "u-boot env"
> mtd1: 00010000 00010000 "permanent u-boot env"
> mtd2: 00010000 00010000 "HP env"
> mtd3: 00080000 00010000 "u-boot"
> mtd4: 00040000 00010000 "SSD firmware"
>

>
> it seems you should
>
> flashcp -v uboot.2015.10-tld-2.t5325.mtd0.kwb
> /dev/mtd3
>
> as that is the mtd where uboot stays.
>
> and the uboot envs should be flashed in what is
> called mtd0 in your table.
>
> If you see the size and erasesize, also the
> adresses above, the actual places of all the mtd
> partitions are the same, but in HP stock OS they
> are indexed at weird places (and with less zeroes
> on top in the addresse, that does not matter).
>
> HP firmware is funky, who knew? :)


Ill give it a go - if i mash it i mash it - already mashed one with a powerblip!

Gravelrash,

It is easier that you boot with stock u-boot, and Debian rootfs. And use the new mtdparts setting in bootargs. They are actually the same. But it is harder to flash with 1 MTD so I forced it to be like stock (5 MTDs).

Let me see... stock MTDs were like bobafett post above?

> dev:    size   erasesize  name
> mtd0: 00010000 00010000 "u-boot env"
> mtd1: 00010000 00010000 "permanent u-boot env"
> mtd2: 00010000 00010000 "HP env"
> mtd3: 00080000 00010000 "u-boot"
> mtd4: 00040000 00010000 "SSD firmware"

And, you should not flash u-boot when MTDs are different :)

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 3 time(s). Last edit at 03/12/2016 03:07PM by bodhi.

It seems I need to revise the instruction to make it easier. My mistake :)

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Gravelrash,

If you are still trying to figure out. You can start booting again and stop at serial console. With the Debian rootfs plugged in. Let me know when you are at that point and I'll get you to Debian with the correct MTDs.

UPDATE:

I saw you are booting this box with USB Debian rootfs. So the only thing you need to do is to define mtdparts correctly in bootargs.

setenv bootargs_usb 'console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=spi0.0:512K(uboot),256K(sdd_firmware),64K(uboot_env),64K(permanent_uboot_env),64K(hp_env)'

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 2 time(s). Last edit at 03/12/2016 04:07PM by bodhi.

@bodhi
I will try that in a little while.

HOWTO for display located here : http://forum.doozan.com/read.php?9,26687,26687#msg-26687

The WOL in stock u-boot is pretty ugly :)

What we need is information about what are the values to write to the 88E1116 Ethernet PHY registers , similar to the settings in the kernel for the 88E1318S. According to the info out there, the 88E1116 does have WOL (I am puzzle, because if it is true, why nobody has done this).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:
-------------------------------------------------------
> The WOL in stock u-boot is pretty ugly :)
>
> What we need is information about what are the
> values to write to the 88E1116 Ethernet PHY
> registers , similar to the settings in the kernel
> for the 88E1318S. According to the info out there,
> the 88E1116 does have WOL (I am puzzle, because if
> it is true, why nobody has done this).

Just my two cents worth

Others will have other ideas, but I believe we would be better off not reimplementing this feature.

From this discussion thread that feature has been nothing but a cause of nuisance. Maybe that's why no-one else has implemented it? It causes more issues than it solves?

Gravelrash,

> Just my two cents worth
>
> Others will have other ideas, but I believe we
> would be better off not reimplementing this
> feature.
>
> From this discussion thread that feature has been
> nothing but a cause of nuisance. Maybe that's why
> no-one else has implemented it? It causes more
> issues than it solves?

The issue was because the way HP implemented it, not because the WOL implementtion in general. I won't use their approach, for sure, if I try.

However, I agreed, we don't really need this. Unless we can do it the rigth way like the current Marvell PHY driver for the 8138s, I will not bother wasting effort :)

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

[SOLVED]: kwbooted new uboot, then linux, then flash worked!

@Bodhi:
I just tried to flash new uboot to my second box - did'nt work, see below errors:
the NAND of my second box seems to readonly..!!!


Note: my stock /proc/mtd looked different, like that of Gravelrash, uboot was in mtd3, I think.

But I thought this wouldn't matter as
"setenv bootargs_usb 'console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=spi0.0:512K(uboot),256K(sdd_firmware),64K(uboot_env),64K(permanent_uboot_env),64K(hp_env)'"
would set the new MTD layout.

Now the good thing is nothing broke - I can still reboot my box, also cold boot - stock uboot coming up again.

See below what I did:

root@debian:~
# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00080000 00010000 "uboot"
mtd1: 00040000 00010000 "sdd_firmware"
mtd2: 00010000 00010000 "uboot_env"
mtd3: 00010000 00010000 "permanent_uboot_env"
mtd4: 00010000 00010000 "hp_env"

root@debian:~
# dmesg | grep spi
[    0.000000] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=spi0.0:512K(uboot),256K(sdd_firmware),64K(uboot_env),64K(permanent_uboot_env),64K(hp_env)
[    1.745410] m25p80 spi0.0: m25p80 (1024 Kbytes)
[    1.749982] 5 cmdlinepart partitions found on MTD device spi0.0
[    1.755984] Creating 5 MTD partitions on "spi0.0":

root@debian:~
# dmesg | grep 0x0 | grep ""
[    0.000000] Booting Linux on physical CPU 0x0
[    0.925617] pci 0000:00:01.0: [11ab:6281] type 01 class 0x060400
[    0.925665] pci 0000:00:01.0: calling pci_fixup_ide_bases+0x0/0x40
[    0.926193] pci 0000:01:00.0: [18ca:0027] type 00 class 0x030000
[    0.926328] pci 0000:01:00.0: calling pci_fixup_ide_bases+0x0/0x40
[    1.760801] 0x000000000000-0x000000080000 : "uboot"
[    1.766985] 0x000000080000-0x0000000c0000 : "sdd_firmware"
[    1.773756] 0x0000000c0000-0x0000000d0000 : "uboot_env"
[    1.780221] 0x0000000d0000-0x0000000e0000 : "permanent_uboot_env"
[    1.787646] 0x0000000e0000-0x0000000f0000 : "hp_env"

root@debian:~
# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00080000 00010000 "uboot"
mtd1: 00040000 00010000 "sdd_firmware"
mtd2: 00010000 00010000 "uboot_env"
mtd3: 00010000 00010000 "permanent_uboot_env"
mtd4: 00010000 00010000 "hp_env"

root@debian:~
# flashcp -v uboot.2015.10-tld-2.t5325.mtd0.kwb /dev/mtd0
Erasing blocks: 8/8 (100%)
Writing data: 512k/0k (100%)
Verifying data: 10k/0k (512%)File does not seem to match flash data. First mismatch at 0x00000000-0x00002800

root@debian:~
# flashcp -v uboot.2014.07-tld-3.environment.64K.img /dev/mtd2
Erasing blocks: 1/1 (100%)
Writing data: 64k/0k (100%)
Verifying data: 10k/0k (64%)File does not seem to match flash data. First mismatch at 0x00000000-0x00002800
root@debian:~

EDIT:
[SOLVED]: kwbooted new uboot, then linux, then flash worked!



Edited 1 time(s). Last edit at 03/15/2016 10:52AM by CV.

Thought I would post a pic of my T5325 running headless with Debian 3.17 loaded per this thread. I'm using it as a combo PBX (running IncrediblePBX for Pogoplug from here: IPBX on PP) and as a Squeezelite client (notice the Plantronics DECT base which I use for wireless music listening). I was also able to compile the 8812au driver for the shown Trendnet AC1200 wireless adapter using this source 8812au.ko for Kirkwood. Picked up the T5325 for less than the price of a movie ticket. Pretty cool :) and thanks to the contributors that made this possible.

CV Wrote:
-------------------------------------------------------
> [SOLVED]: kwbooted new uboot, then linux, then
> flash worked!
>
> @Bodhi:
> I just tried to flash new uboot to my second box -
> did'nt work, see below errors:
> the NAND of my second box seems to readonly..!!!
>
>
> Note: my stock /proc/mtd looked different, like
> that of Gravelrash, uboot was in mtd3, I think.
>
> But I thought this wouldn't matter as
> "setenv bootargs_usb 'console=ttyS0,115200
> root=LABEL=rootfs rootdelay=10
> mtdparts=spi0.0:512K(uboot),256K(sdd_firmware),64K
> (uboot_env),64K(permanent_uboot_env),64K(hp_env)'"
>
> would set the new MTD layout.
>
> Now the good thing is nothing broke - I can still
> reboot my box, also cold boot - stock uboot coming
> up again.
>
> See below what I did:
>
>

> root@debian:~
> # cat /proc/mtd
> dev:    size   erasesize  name
> mtd0: 00080000 00010000 "uboot"
> mtd1: 00040000 00010000 "sdd_firmware"
> mtd2: 00010000 00010000 "uboot_env"
> mtd3: 00010000 00010000 "permanent_uboot_env"
> mtd4: 00010000 00010000 "hp_env"
> 
> root@debian:~
> # dmesg | grep spi
> [    0.000000] Kernel command line:
> console=ttyS0,115200 root=LABEL=rootfs
> rootdelay=10
> mtdparts=spi0.0:512K(uboot),256K(sdd_firmware),64K
> (uboot_env),64K(permanent_uboot_env),64K(hp_env)
> [    1.745410] m25p80 spi0.0: m25p80 (1024
> Kbytes)
> [    1.749982] 5 cmdlinepart partitions found on
> MTD device spi0.0
> [    1.755984] Creating 5 MTD partitions on
> "spi0.0":
> 
> root@debian:~
> # dmesg | grep 0x0 | grep ""
> [    0.000000] Booting Linux on physical CPU 0x0
> [    0.925617] pci 0000:00:01.0: [11ab:6281] type
> 01 class 0x060400
> [    0.925665] pci 0000:00:01.0: calling
> pci_fixup_ide_bases+0x0/0x40
> [    0.926193] pci 0000:01:00.0: [18ca:0027] type
> 00 class 0x030000
> [    0.926328] pci 0000:01:00.0: calling
> pci_fixup_ide_bases+0x0/0x40
> [    1.760801] 0x000000000000-0x000000080000 :
> "uboot"
> [    1.766985] 0x000000080000-0x0000000c0000 :
> "sdd_firmware"
> [    1.773756] 0x0000000c0000-0x0000000d0000 :
> "uboot_env"
> [    1.780221] 0x0000000d0000-0x0000000e0000 :
> "permanent_uboot_env"
> [    1.787646] 0x0000000e0000-0x0000000f0000 :
> "hp_env"
> 
> root@debian:~
> # cat /proc/mtd
> dev:    size   erasesize  name
> mtd0: 00080000 00010000 "uboot"
> mtd1: 00040000 00010000 "sdd_firmware"
> mtd2: 00010000 00010000 "uboot_env"
> mtd3: 00010000 00010000 "permanent_uboot_env"
> mtd4: 00010000 00010000 "hp_env"
> 
> root@debian:~
> # flashcp -v uboot.2015.10-tld-2.t5325.mtd0.kwb
> /dev/mtd0
> Erasing blocks: 8/8 (100%)
> Writing data: 512k/0k (100%)
> Verifying data: 10k/0k (512%)File does not seem to
> match flash data. First mismatch at
> 0x00000000-0x00002800
> 
> root@debian:~
> # flashcp -v
> uboot.2014.07-tld-3.environment.64K.img /dev/mtd2
> Erasing blocks: 1/1 (100%)
> Writing data: 64k/0k (100%)
> Verifying data: 10k/0k (64%)File does not seem to
> match flash data. First mismatch at
> 0x00000000-0x00002800
> root@debian:~
>

>
> EDIT:
> [SOLVED]: kwbooted new uboot, then linux, then
> flash worked!

Sorry CV, I need to add more instruction to the u-boot thread. Have not got around to do that :)

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

@bodhi - Im still on stock uboot as i already borked one, hopefull i can fix it and be able to kwboot when my new TTL adaptors land

@Leggo - would you be willing to share you alsa conf files and alsastate file. i would like to compare with mine and see if its actually a harware fault i have with the unit as i get no sound, but alsa reckons to be fuctioning and outputting to the correct device.

Gravelrash Wrote:
-------------------------------------------------------

> @Leggo - would you be willing to share you alsa
> conf files and alsastate file. i would like to
> compare with mine and see if its actually a
> harware fault i have with the unit as i get no
> sound, but alsa reckons to be fuctioning and
> outputting to the correct device.


Not using built in sound device as my DECT base has USB and it shows up as an output when I change snd_usb_audio to =0 in alsa-base.conf. I couldn't get built in sound to work unfortunately.



Edited 1 time(s). Last edit at 03/15/2016 02:42PM by LeggoMyEggo.

@Leggo, thanks for the fast response. I will stick a usb sound board in for now as it sounds like your experience mirrors mine

@bodhi there appears to be from my limited research special considerations in the compilation of the Kirkwood SoC architecture for this unit in relation to sound output

Q. is it a whole bunch of work for you to mangle the sound options for this unit.

If it is then i for one dont want to take up your limited and valuable time on this unit when for approx $1 we can add sound another way.



Edited 1 time(s). Last edit at 03/15/2016 02:57PM by Gravelrash.

Gravelrash,

I've included virtually all kernel options for sound. Perhaps something is still missing! It's no problem to add more. Can you find the name and model number for this sound chip?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Found it.

This could be the sound alc5623 codec patch that was missing from the kernel DTS:
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-May/253014.html

UPDATE:

This patch is already in the kernel.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 03/16/2016 01:57AM by bodhi.

This could be the problem:

root@T5325:/localdisk# dmesg | grep alc
[   18.399141] asoc-simple-card sound: alc5621-hifi <-> spdif mapping ok

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

@bodhi you are relentless in your desire to fix problems!

I went to bed with the intention of doing more investigation this morning and you find the problem. is this something i can fix with console commands or is it one that needs to wait for your next kernel release?

BTW - im still playing with the graphics options for this unit, for some reason i cant seem to leave it alone!!.

There are apparently some options i can give to the xgifb in the inittab that modify its behaviour so im going to try that and see if i get any differing results. I do seem to be enjoying better screen response behaviours than CV reports, having said that im running at a lower resolution so that is probably the reason!

Only problem i have found that is really annoying me is that from the FULL LXDE desktop, iceweasel doesnt load, im going to look at this in a bit and i bet that i havent set the user/group permissions correctly.

Gravelrash,

> I went to bed with the intention of doing more
> investigation this morning and you find the
> problem. is this something i can fix with console
> commands or is it one that needs to wait for your
> next kernel release?

This seems like it could be fixed in DTS. Will see if that was the cause. If that's true then the DTB can be updated any time.

The error (when playing with cmus):

Error: opening audio device: No such device

> BTW - im still playing with the graphics options
> for this unit, for some reason i cant seem to
> leave it alone!!.

Hardcore modders are obsessive :))

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 03/16/2016 04:41AM by bodhi.

root@debian:~# cat /proc/asound/cards
 0 [i2salc5621hifi ]: i2s-alc5621-hif - i2s-alc5621-hifi
                      i2s-alc5621-hifi
 1 [Device         ]: USB-Audio - USB PnP Sound Device
                      Generic USB PnP Sound Device at usb-f1050000.ehci-1.1, full speed
root@debian:~# top

http://www.realtek.com.tw/products/productsView.aspx?Langid=1&PFid=39&Level=4&Conn=3&ProdID=159

http://www.datasheet4u.com/datasheet/A/L/C/ALC5621_RealtekMicroelectronics.pdf.html

Gotta love Realtek - great in one direction and a headache in another :)



Edited 1 time(s). Last edit at 03/16/2016 05:07AM by Gravelrash.