(98 replies, posted in Hardware )

And about the beeps - is it like a beep from a pc speaker or you hear it through you headphones? Can you test with a sample sound file not trough the browser so we can understand if it is Flash or system (mixer)?


(98 replies, posted in Hardware )

I built a new version with the driver and with Image magic. Well if it doesn't play the sound then you still haven't configured the mixer, you can try storing the sound with "alsactl store" if it is an alsa driver. Did you hear the test sound when you configured it in YaSt? What is the name of the driver of the sound card in YaSt Sound?


(98 replies, posted in Hardware )

I updated the installation guide:
I guess it depends on the system and sound card for me it worked without PulseAudio. I will check how the sound levels can be stored, I don't remember having this issue. Can you confirm that the sound works by playing an audio file or YouTube video with the mixer open?


(98 replies, posted in Hardware )

Well if the test works, then you have to adjust the (Master) volume in the mixer. If it doesn't show up you will have to delete the configured sound card and configure again until you see the master volume and just increase it. I will try to find time to make a video of that I know it is confusing, but this is the way it works in SuSe.


(98 replies, posted in Hardware )

Well the sound. Look at the Main Board specifications and you will also find what kind of sound card you have on the board. Repeat the steps the trick there is to remove the configuration of all sound cards configure them, remove pulse audio on all of them and right after that configure the mixer. What I really notice in OpenSuse is if your sound breaks then you have to reconfigure it again until you see it in the mixer -after doing this settings it is OK. But if you leave it and try to configure your settings in the mixer later you are lost. You don't need a driver you have it already, it comes with the kernel modules. About the bugs thanks for reporting them. I'm currently working on the kernel since this seems to be a main issue. Also i found some bugs in suse studio and reported them and I hope they fix them. One other approach how to find what is the sound card - when you configure the sound from yast and click on test if you hear a sound this is your sound card - good luck.


(98 replies, posted in Hardware )

I maybe will have time tomorrow evening to compile the new kernel. I still am not sure if this will fix the issues with the ram errors. The resume option "tells the kernel where to find the suspend-to-disk image to resume from (for swsusp and suspend2, respectively) ".

Yeah you can leave everything else if sound works. Ok well I can include the driver you just posted.

I'm glad it started working, I'm still wondering if the issues with the kernel are from the kernel or from the bootloader or udev. I will let you know when I have some results.


(98 replies, posted in Hardware )

I think I understand the reason why the kernel breaks. It has to do maybe wiht udev - and probably with the RAM image initrd - sounds logical since the kernel doesn't even boot in this case I might be able to fix it sooner, but I will have to experiment.


(98 replies, posted in Hardware )

The RAM Errors - OMG I think I will have to recompile the kernel again big_smile X-)
"Did you all Disable CONFIG_SYSFS_DEPRECATED _and_ CONFIG_SYSFS_DEPRECATED into the kernel config?"
http://forums-web2.gentoo.org/viewtopic … art-0.html


(98 replies, posted in Hardware )

Yes exactly, you first select the bootloader for me it worked with grub and click install bootloader or something like that. At first I also thought that when I clicked convert it displaied the menu, but now I understand that actually it was the install button. I will try to update the install instructions. But the main idea is to see the menu on the previous tab so you can adjust whatever you want. Well about the partition I'm not sure if it should be sda1 or 2 in your case it is individual. But if it was sda1 leave it that way and it should be fine. You basicly "clone" the entry you already have and create one for GrSecurity by replacing the kernel and the initrd image. I have to admit I'm surprised at how they changet Boot in YaSt - it seems nice, but I think they have lot of work to do - to many stuff doesn't work/experimental or is not intuative. And this error with the RAM they seem to be from the bootloader.


(98 replies, posted in Hardware )

Soooooooo I finally figured it out! With the boot loader. Install this package - kexec-tools then the menus will be displayed and use only grub not grub2, grub2-efi, lili, elilo just grub. I will now edit the appliance and test again.


(98 replies, posted in Hardware )

Ok Step 3. Well the card is usually at index 0 - mine is (HD48x0 - intel something). in step 3 you select the card and you click on the Edit button you then configure it with Normal. About the kernel, yes I know it is because of the boot-loader they are many I have to remove them, I added more because of the EFI - that we discussed, I now reallize this was not a good idea. You have in the installation instruction a screenshot which shows how to configure the boot entry for GrSecurity from YaSt>Boot. But this might not work very good in the moment, I will try to now resolve the issue with the bootloaders. You can use the bootloader of ubuntu to set it up - I think it should work well.


(98 replies, posted in Hardware )

Well seems that earlier when I tested and when it didn't boot - it really didn't.
I recreated the appliance:

Try now and again with nomodeset option during boot.

I also added this:

# recreate initrd without KMS, if the use of KMS is enabled in initrd
if grep -q NO_KMS_IN_INITRD=\"no\" /etc/sysconfig/kernel; then
   sed -i 's/NO_KMS_IN_INITRD.*/NO_KMS_IN_INITRD="yes"/g' /etc/sysconfig/kernel

From here both recomended for nvidia and ati.


(98 replies, posted in Hardware )

OK, seems that the option works (nomodeset), but something else doesn't now I should figure out what exactly doesn't work - strange.


(98 replies, posted in Hardware )

Try now.


(98 replies, posted in Hardware )

Ok, well now that you posted the error I know what the problem is it is the kernel firmware it's not the driver that I included so yes it will fail. I will now include the kernel firmware and rebuild once it is done I will let you know to try again.


(98 replies, posted in Hardware )

Look also at this http://www.gnu.org/software/automake/ma … STDIR.html


(98 replies, posted in Hardware )

Yes I built it, but i didn't share it. Now I shared it you can check. I'm in doubt if it works, if you wish clone and change as you want. Well these questions on building from source etc. They are all answered, just have to reach out and read. If everything was figured out it wouldn't be fun. But you can read this and it will answer many of your questions:


(98 replies, posted in Hardware )

The hard driver - well it is dected by th Kernel so most probably, if there are other kernels you with Qubes you will have to try them. If not I guess you will have to write at their forum or whatever they have.

About dnscrypt-proxy - well you can always compile from source.


(98 replies, posted in Hardware )

Well, for windows use this: https://github.com/downloads/openSUSE/k … Writer.exe
If it doesn't recognize the USB pull it out and plug it again - it has to appear as device in explorer. About the driver I added it, but what troubles me is that you say it didn't even start booting the OS usually this driver is for the Xorg session. I read this and added the driver:
It takes time to build the image a bit longer than usual, but I will let you know when it is done.


(98 replies, posted in Hardware )

Well congratulations on the new hardware and lots of luck with it and no issues smile


(98 replies, posted in Hardware )

I did some changes. I got the size of the USB image smaller. I didn't got time to test it out good, but I think it should work. One thing now the appliance is updated with 12.2 OpenSuse packages and it might look different during boot - for instance I was able to directly edit the grub menu before boot (don't remember the key combinations but try Alt+F1, F1 or Shift). How is the graphic card in the new Mother Board integrated or separate? I would make a research in google lets say OpenSuse 12.2 + your mother board model and try to see what kind of issues the other had if any. I'm not sure but maybe if you buy only a cheap graphic card your issues might be resolved.


(98 replies, posted in Hardware )

And here is the suggestion form suse studio:
"you can just dd the isos to the usb stick and it will work. And that'll also allow for
adding boot parameters..."


(98 replies, posted in Hardware )

I mentioned about the Live Installer in mail, when you send me the picture of the option which is enabled anyway. Nothing can be done here.

Yeah about the DVD player, sorry about that I forgot. But I think the problems start from using Unetbootin. You actually can try booting the ISOs from your hard drive - through grub.
Look here:
submenu "My ISOs" {
menuentry "Natty_test.iso
loopback loop (hd1,6)/iso/$isofile
linux (loop)/casper/vmlinuz boot=casper iso-scan/filename=/iso/$isofile noprompt noeject
initrd (loop)/casper/initrd.lz
menuentry 'ISO SystemRescue sdb5-vm' {
loopback loop (hd1,5)/$isofile
linux (loop)/isolinux/rescue64 setkmap=us isoloop=/$isofile
initrd (loop)/isolinux/initram.igz




(98 replies, posted in Hardware )

->Adding the Live Installer to the 'USB & disk image' as I suggested
As I said before it is not possible.

I tested and you can pass the option also to the preload format during boot again by writing nomodeset. But I am not sure IF you can pass the parameter when you use Unetbootin, just burn it.

Also "If you have more than one disk available, you can choose it from the list:"
http://1.bp.blogspot.com/_5_1pXrfRcyg/T … choice.png

So what's the issue?


(98 replies, posted in Hardware )

Actually I got a reply from suse studio. And after I tested I was able to pass a boot parameter. I tried on the Live CD/DVD, just write nomodeset in the BootOptions field and hit enter on the Secure OS.