Archive for the ‘linux’ Category

Sound support on Zepto Znote 6324w

30 January, 2008

I recently bought a laptop, of the make mentioned in the heading, and installed opensuse 10.3 on it (I can’t quite remember if I had opensuse 10.2 installed first, but that’s beside the point).

I pretty much succeeded in getting things to work, the wireless LAN required the intel drivers, which were not included in the install at that time, but downloading and compiling the drivers went smoothly, so in no time I had wireless networking working with knetworkmanager supporting it, and connecting to open WLAN’s WEP protected WLAN’s, and my home WLAN which runs WPA.

Bluetooth also worked, and I tried connecting to my Mobile phone (That’s Cell phone for americans), and downloaded a couple of pictures I had taken with it. The mobile phone is a Nokia 6310i by the way.

But no sound.

And even though I found lots of discussion,especially on ubuntu fora, about sound with hdaudio from intel, I was not able to get it working even though I upgraded to the latest version of ALSA.

Very recently though I found a forum, where a guy with the signature “oldcpu” guided someone else through a step by step test and config of the sound configuration, and following his suggestions I soon had sound working.

So here is my setup (I gave up getting yast to configure sound for me, and manually edited the file instead):

This is the content of my /etc/modprobe.d/sound:

options snd-hda-intel model=toshiba
alias snd-card-0 snd-hda-intel
alias sound-slot-0 snd-hda-intel
I haven’t experimented with it at all since it started working, but I think the “toshiba” option was the trick for me.

Other than that, I have ALSA 1.0.15 driver and tools, manually installed and compiled. But since then yast has upgraded the driver to ALSA 1.0.15 as well, and it still works. But yast breaks sound for me, and so does alsaconfig.

A very good test for me while testing the options in the file above was this (also suggested by “oldcpu”):

speaker-test -c2 ddefault -twav

Suddenly the speakers were saying: “front left”, “front right”, and so forth endlessly until i killed it with ctrl-c

So If anyone else is having trouble with this, I hope the above gave you some inspiration about how to get sound support working on your laptop.


Mythtv and ACPI wakeup on Opensuse 10.2

07 October, 2007

Today I got acpi wakeup working on my opensuse 10.2 based mythtv box ;-))

As I wrote in a lengthy earlier post, I am pretty much happy about my mythtv setup now. It has been running quite well for some time now.

But one thing has been bothering me: I had not managed to configure the box to turn itself off, and back  on, so I let it run 24/ 7, which ofcourse is fine from a purely stability point of view, after all this is linux which unlike windows is fine to run for years without reboot.

But from a power consumption point of view, this has been annoying me and today I set out to fix it.


mythtv on opensuse 10.2, a small success

14 July, 2007

This evening I moved the mythtv box into the living room, to experiment.

Some time ago I wrote that the PSU had unexpectedly died. A few days ago, I finally received a replacement PSU free of charge (apart from the 50 dkr it cost me to send in the defect one of course).

I had already found out that wlan now works with my Allnet 0271 nic (using wep only, since I can’t get it to connect without using knetworkmanager, and knetworkmanager refuses to let me select wpa. I finally found out that the prism54 driver which I use for the nic has incomplete wpa support, so I settled for wep for now).

I wanted to see if I could get the Hauppauge win tv nova-t dvb-t tuner to work, since everywhere it is stated that it should just work out of the box with opensuse 10.2. Well not quite, but after a long time trying to select some cx2388-something drivers with yast, and sometimes manually writing these drivers into /etc/modprobe.d/tv, and back and forth trying out different combinations, I finally tried to let kaffeine see if it could find any channels. And to my surprise it did !!!

It turns out, that kaffeine identified the tuner and on it’s own decided to use the cx22702 driver to control it.

So kaffeine successfully found the DVB-T multiplex in Denmark even when yast channel tune, and mythtv channel tuner could not. I am very grateful right now that I had kaffeine installed.

After this, I went back into yast, and selected the cx22702 driver instead of the default bcom-something (I turned off the other machine because it is getting late, and only on second thought decided to write about my partial success before I went to sleep. An update will follow sometime later, probably next week).

And then also mythtv could successfully tune and find the multiplex. (I had to tell mythtv to search using the german channel range, there is no danish list selectable in mythtv).

The parts I did not get to work tonight was audio, and perhaps IR (I say perhaps, because I will check if the batteries are alive before I draw any conclusions about that first 🙂

But I am pretty sure that will come along too soon enough.

Also I experimented a little with the nvidia-setting (nvidia xserver control), to set up the tv out so the text would be readable on the tv. I did not find a setting to my liking before I quit.

But theoretically I could start recording shows starting tomorrow, so I am optimistic that the remaining minor problems will be solvable too,

Update (22.07.2007 at 1:20)

Some time has passed, and I had resigned to use kaffeine to record and watch tv, since I could not find out how to get the correct drivers loaded automatically (I did so using modprobe instead), and mythtvbackend would crash every few minutes. If i had started mythtvbackend from a term, as root I saw this line when it crashed (I think it was the same line each time, but can’t be sure):

pcHDTV::GetSignal(fd 41 …….) (Invalid Argument)

I could not remember the parameters in the parenthesis so the “…” should not be taken literally 😉

But tonight I played a little with it, and after having tried unsuccessfully to edit /etc/modprobe.d/tv manually to force Yast2 to accept the cx88_dvb and cx22702 modules to be loaded for the card (my Hauppauge winvt nova-t DVB-t), I found out that:

  1. cx88_dvb depends on cx22702 and when cx88_dvb is loaded, then cx22702 is automatically loaded too.
  2. I _could_ select cx88_dvb within Yast if I chose that _instead_ of the cx8800 module.

Now it seems mythtvbackend does not crash nearly so often as it did before. I guess the drivers I loaded before made mythtv think the card was a HD card?… I don’t know. I downloaded the source for mythtv with the intent to try and compile it, and see if I could make some sort of workaround, or at least provide better feedback to the maintainers if I filed a bug report. Now I will hold the bug report back a little until I am sure there is one.

I “fixed” one more small thing tonight:

Whenever thebox booted, it would halt with a message about the wrong screen mode being passed at boot, and I should choose another, or press space to continue anyway.

This is not the prettiest way to fix this, but simply removing the screen option, which was 0x31a, from grub (I did it from within Yast2->BootLoader) made it go away and just boot.

The downside of this simple and ugly fix, is that I do not have the flash screen active while booting, but at least it will now boot unattended,

I should probably fix this before too long though, as it most certainly will affect the WAF (Wife Acceptancy Factor;-) negatively if I don’t.

Still missing:

Configure mythtv to use the remote for controlling it.

Mythtv on open suse 10.2 a fresh start

05 May, 2007


After having spent the winter mostly doing other stuff, like getting the boat ready for the new season I recently decided to do something about my mythtv box which I had almost but not quite running as I liked in the beginning of december last year.

This is what I mean by “not quite running as I liked” by the way:

  1. I did not get the ALLNET 0271 wireless NIC to work with OpenSuse, I felt I made some progress, but never quite got it to work even though I could connect from a knoppix cd (actually knoppix V 5.01) booted on the same machine.
  2. I did not get the remote control configured so I used a keyboard and mouse to program recordings, and play them.
    1. I did confirm with Yast that key events got received correctly by the driver so I was probably close there.
  3. I was not really happy with the boot screen, or the resolution when booting and running anything other than the mythfrontend.
    1. I had to manually bypass a warning about graphics modes during boot.
  4. I did not untill later after the DVB-T tuner had stopped working for me, get the software installed for modifying the BIOS wakeup time, so I while I actually used it to record tv I always had to manually turn the machine on before the recording should start. As mentioned I later got this to work, so I am confident I will get it to work again, and will of course describe it here when I get to that point.

The box would not boot, probably due to the fact that I had installed on the SATA drive, and having the bios reset and not getting the right boot order. I finally gave up on it and reinstalled open suse 10.2, so now I have relative fresh install to start from. This is already a while ago in which I have not even powered up the box, so I hope I haven’t forgotten something essential.

Because this time I will try to record what I have done here in my blog so I and others may benefit from it. The progress might be slow since I get scouled at by my wife if I spend too much time by the computer, and I also have the boat in the water now. Oh, and then there is this half marathon thing early next month whivh I am training for. link:

This is the hardware in the box:

Motherboard: ASUS A8N-SLI premium

CPU: Athlon 3200+

TV tuner: Hauppauge WinTV Nova-T DVB-T model 909

Wlan: ALLNet 0271

OS: Open suse 10.2

The last time I installed this box I referred a lot to these web sites:

I did not however succeed last time in getting my wlan ALLNET 0271 to connect to my WAP. I did try to install knoppix V (whatever was the latest version around november / december 2006) and that successfully connected to my WAP, so there certainly is hope. I just couldn’t get it to work with Suse 10.1 which I was using at that time, nor with Open suse 10.2 which I tried with the last time. Hopefully this time I will manage to get it right. (or buy another wlan nic which “just works” with Open Suse 10.2, time will tell). (more…)

My mythtv box is idling at the time being

13 December, 2006

My DVB-T tuner was garbling the analog tv signal “down stream” from it, with the effect that my TV could only be used to watch tv on some of the frequency bands (perhaps those not used my the DVB-T signal?)

Anyway, last week I tried inserting a T-splitter to the antenna cable for the DVB-T tuner to see if this would improve the signal relative to what I had been doing so far, which was to connect the antenna cable for the tv to the antenna out connector on the tuner.Since then I have been unable to get mythtv to tune to the DVB-T signal. It’s just as though the tuner is broken, yet the drivers seem to load ok. I decided that knowing the software works was enough for me for the time being, and I was really too busy to do anything to fix it, so it’s idling (meaning I am not using it for the time being).

Also even though I am not 100% sure I didn’t break something in the configuration, because around the time just before this strangeness with the tuner I had been modifying the /etc/modprobe.d/tv file to get the cx88_dvb kernel module loaded at boot time so I wouldn’t have to log in as root and modprobe it manually to get the tuner working. (The other kernel modules _did_ load at boot, only this one did not). Anyway the addition of this module to the file seemed to work as I wanted, but I am not sure I actually tested if the tuner worked after doing this untill I did the thing with the antenna cable.

I know, the antenna and T-splitter (which is a passive component) can not reasonably be responsible for the tuner to stop working, but at the time it was the only thing I could remember doing before it stopped working. And again time prohibits me from tinkering with the box for the time being.

Also I am holding back upgrading the box to opensuse 10.2 because I filed a bug report about wlan support with knetworkmanager for my Allnet 0271 (which just works out of the box when I boot with knoppix v 5.01), and I want to see if they need more info from log files or other before I upgrade…

Beginning to use my new mythtv box

04 December, 2006


This weekend I finally decided to connect my mythtv box to the tv in the living room, just to see how much still needed fixing, and was quite happily surprised to find that apart from a few glitches it just worked.

I have some tweaking to do though:

  • I managed to configure the graphics card and the resolution so even normal text screens (not mythtv ones, but for instance term windows) were almost readable. I could probably improve this still, but I am not sure if this is just because the tv is one with a crt.
  • I initially could only find live views in the media library, untill I found (and the config screens for mythtv are not _that_ readable on the tv either) the option to also view default, and standard recording groups in the view filter in the media library.
  • I need to figure out how to get the box to turn it self on (and off) when recordings start and stop (if it is not being used) I haven’t looked into this yet.
  • I need to set up the IR for my remote so I don’t have to have the wireless keyboard and mouse around to control mythtv
  • Maybe a second dvb-t tuner instead of one dvb-t and one analogue (the analogue is not connected yet).

But overall I am very happy with my mythtv box so far.

Building a mythtv box on suse 10.2 rc1

27 November, 2006

Well I could not figure out how to get wireless working for me in the suse 10.1 install I had on the machine. So in the hope that a reinstall with the wireless nic installed in the machine during installation would somehow configure the network correctly for me I upgraded to suse 10.2 rc1.

But the problem is still the same. Only difference is that the installer suggested to use networking _without_ the networkmanager (which I had seen in the buglist for 10.1 does not work with prism54 which is the driver for my wireless nic unfortunately)

But it did not work (wired ethernet works fine ofcourse)

So I started trying the same tricks I had learned on suse 10.1 ( symlinking /etc/sysconfig/network/ifcfg-eth2-> ifcfg-wlan……… ) and again I saw using iwevent that I seemed to get my nic associated with the wireless router. But still no dhcp assigned ip address for the wireless interface.

I tried disconnecting the wired ethernet and restarting the network, but no luck with that.

I tried adding a route for the wireless interface to the wireless router manually, but no luck.

I tried setting the ip for the wireless interface manually, and disconnecting the wired ethernet (using the same ip address that was assigned (by DHCP) ) but still no luck.

Despairing for a bit, while I think about how to proceed from here.

Building a mythtv box

21 November, 2006


recently I started configuring an Athlon 3200+ equipped box, with a sata and an IDE hard disk, a Hauppauge DVB-t tuner, and a Hauppauge 150, and because I would prefer not to draw ethernet cables to the living room where the box should live an Allnet 0271 wlan nic.

I installed open suse 10.1 on it (this was some time before the novell / Microsoft announcement which I still don’t know quite what to think of other than this: I don’t trust Microsoft further than I can throw it so I will not be surprised to learn that Microsoft does something ugly with this to try and damage linux).

I Installed mythtv, and tv_grab_dk (I live in Denmark) and configured mythtv. But I could not get my wlan to connect to my wlan. A lot of debugging later I have learned a few things:

  1. A live cd with knoppix v.5.01 allowed me to configure the wlan nic and connect to the wlan (and get an ip address via dhcp) in less than 5 minutes using wep encryption. (I have been fighting it with suse 10.1 for weeks now)
  2. Under suse 10.1 if I disable knetworkmanager, and make a symlink from /etc/sysconfig/network/scripts/ifcfg-eth1 to /etc/sysconfig/network/scripts/ifcfg-wlan-bus-pci-0000:05:08.0 I can at least get a connection to the wlan now, but still no ip address via dhcp.
  3. A post on suseforums indicate that knetworkmanager (which is a frontend for networkmanager, natively a gnome program I think) seems to be a bit unreliable.

So now I am downloading suse 10.1 to burn a dvd, and try to reinstall it. My hope with this plan is that if the nic is in the machine at install time (which I can’t remember if it were the first time or not) the install program will correctly configure it this time. Otherwise I might switch to ubuntu, although I still like the feel of suse better than ubuntu (Can’t really say why other than having no root login however good an idea seems strange to me).

Today I am struggling to get mythbackend running and connect to it (from the same machine). Maybe it is because I have been messing around with the network configuration a lot lately.

Anyway, I am _still_ waiting for the last 0.1% of the suse 10.1 DVD to finish download via torrent. It has been at 99.90% for almost 4 hours now and it is just stalled. 😦

Update: I started downloading suse 10.2 rc1 as well, also using ktorrent. It also started to go slower and slower and finally grinding to a halt at 93%. I read about some similar problems, and restarted ktorrent as suggested, and both torrents came back to life and finished with no further problems.