Hi all:
I am giving 11.3 a test for the sake of a review, and I’d like to ask a couple of questions here to make sure that I have some facts straight. For the most part, problems have been few, but for users who aren’t familiar with Linux to begin with, some problems I ran into would be potential show-stoppers.
- After the OS was installed, my network simply didn’t work. I couldn’t get online at all, which was a bit strange since I haven’t had an issue like that with any other distro I’ve tested out in recent memory. The problem is that DHCP wasn’t used, so after a quick configuration change, I was online.
Is this kind of thing typical of new installations, or did I run into a bizarre instance where the Ethernet just happened to not function for some reason?
- When clicking on “My Computer”, many different hard drives and partitions are listed. However, when clicking on any of them, I’ll receive an inode/blockdevice error, when I would have expected it to launch the drive in a file manager. The reason that this really strikes me is that the drives I tried to open were using Linux file systems (ext4, to be exact, just like openSUSE’s default).
Is this the expected effect? Is there a reason that the drives can’t be auto-mounted when clicked on, which is typical of a few other distributions?
- My PC has two audio cards, the on-board HDA Intel and also an ASUS Xonar Essence STX. Both cards were probed and installed fine, but the latter won’t actually emit sound, even though it appears to function fine (volume sliders are visible and functional). The problem, I thought, was due to YaST applying the snd-oxygen module rather than the snd-virtuoso module, which the Xonar cards require, but a quick lsmod shows that things still should work:
snd_virtuoso 36361 1
snd_oxygen_lib 37400 1 snd_virtuoso
Here’s the lspci output:
07:04.0 Multimedia audio controller: C-Media Electronics Inc CMI8788 [Oxygen HD Audio]
Subsystem: ASUSTeK Computer Inc. Virtuoso 100 (Xonar Essence STX)
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32 (500ns min, 6000ns max)
Interrupt: pin A routed to IRQ 16
Region 0: I/O ports at ee00 [size=256]
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: AV200
Normally, the kernel driver in use would be snd-virtuoso, not the AV200 that it mentions above. AV200 isn’t even a module, but for what it’s worth, most of the Xonar’s, including the STX, use AV100, not AV200. I thought that running ‘alsaconf’ could remedy the situation, but that just killed the entire sound system, requiring a reboot to get it back.
Any help for any of these issues would be greatly appreciated! :)[/size]
The issue I’m having isn’t as simple as having two audio devices, because it shouldn’t be a problem at all. I have a bit of a unique issue here.
I’ll test it again as soon as possible and submit the bug report.