Topic: Secure OS 32 debuging

Hi,

So I have few questions about your problems:
1. What is your configuration, mainboard+videocard?
2. You said you were able to start with GrSecurity - how exactly, did you put any boot flags or anything?
3. I will now build a version without ATI&Nvidia video drivers and you will test. I will post the link here.
4. How big is your flash drive?

Thank you,
Yuriy

Re: Secure OS 32 debuging

1. mainboard: intel D915GUX
graphic : intel gma900
also tested on samsung n150 plus
2.
I was able to start one time with GrSecurity on
samsung n150 plus (but only one time) next boot with grsec was fail.
I added flags on firefox after system start but that is no matter.
3.
I have integrated graphic on both computers.
4.
About 16GB.

Re: Secure OS 32 debuging

Try now, i tested and at least here it runs:
https://susestudio.com/a/EmL6GN/secured-os-32-bit

Also if it doesn't work try this from the Boot Menu> Advanced options> Grsecurity (failsafe) <- I think it was the second option in the menu for GrSecurity

Re: Secure OS 32 debuging

netseclteam wrote:

Try now, i tested and at least here it runs:
https://susestudio.com/a/EmL6GN/secured-os-32-bit

Also if it doesn't work try this from the Boot Menu> Advanced options> Grsecurity (failsafe) <- I think it was the second option in the menu for GrSecurity

Same situation.

Re: Secure OS 32 debuging

netseclteam wrote:

Try now, i tested and at least here it runs:
https://susestudio.com/a/EmL6GN/secured-os-32-bit

Also if it doesn't work try this from the Boot Menu> Advanced options> Grsecurity (failsafe) <- I think it was the second option in the menu for GrSecurity

Same situation.
"No signal" from monitor while booting and keyboard no responding(also can't turn on/off caps lock,num lock, scroll lock).
After reset(with button) usually pen-drive is not detected(changing usb socket helps) .
In recovery mode system stops after  setting up network  and "-" is blinking, keyboard etc. still works.

Re: Secure OS 32 debuging

OK, I guess I will have to dig a bit. Do this - boot with the normal kernel and then open a terminal and issue lsmod and paste the output here.

EDIT: I made some research now and it seems both of your hardware have intel cards and intel chipsets when you give me the output of lsmod I will know exactly waht modules you will need and I will recompile the kernel.

Re: Secure OS 32 debuging

Module                  Size  Used by
ipt_REJECT             12485  1 
xt_length              12480  8 
xt_tcpudp              12756  307 
xt_recent              13898  31 
xt_limit               12541  3 
xt_conntrack           12664  44 
xt_LOG                 17247  11 
iptable_mangle         12615  0 
iptable_nat            13138  0 
nf_nat                 25025  1 iptable_nat
nf_conntrack_ipv4      14501  47 iptable_nat,nf_nat
nf_conntrack           80683  4 xt_conntrack,iptable_nat,nf_nat,nf_conntrack_ipv4
nf_defrag_ipv4         12649  1 nf_conntrack_ipv4
iptable_filter         12706  1 
ip_tables              17987  3 iptable_mangle,iptable_nat,iptable_filter
x_tables               26087  11 ipt_REJECT,xt_length,xt_tcpudp,xt_recent,xt_limit,xt_conntrack,xt_LOG,iptable_mangle,iptable_nat,iptable_filter,ip_tables
af_packet              30681  2 
snd_hda_codec_realtek    71454  1 
snd_hda_intel          32351  0 
snd_hda_codec         122027  2 snd_hda_codec_realtek,snd_hda_intel
snd_hwdep              13272  1 snd_hda_codec
snd_pcm                96931  2 snd_hda_intel,snd_hda_codec
snd_timer              24318  1 snd_pcm
sr_mod                 21872  0 
cdrom                  41398  1 sr_mod
snd                    70407  6 snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
ata_generic            12779  0 
8139too                32537  0 
ata_piix               26359  0 
ppdev                  17398  0 
tpm_infineon           13200  0 
tpm                    25960  1 tpm_infineon
sky2                   53003  0 
8139cp                 31196  0 
ahci                   25496  0 
libahci                29901  1 ahci
microcode              22850  0 
iTCO_wdt               17652  0 
iTCO_vendor_support    13502  1 iTCO_wdt
sg                     35635  0 
soundcore              14599  1 snd
snd_page_alloc         14036  2 snd_hda_intel,snd_pcm
libata                196296  4 ata_generic,ata_piix,ahci,libahci
parport_pc             36449  0 
parport                40726  2 ppdev,parport_pc
tpm_bios               13421  1 tpm
serio_raw              13155  0 
pcspkr                 12630  0 
i2c_i801               17499  0 
autofs4                33231  2 
usbhid                 51444  0 
hid                    81672  1 usbhid
usb_storage            48133  2 
uhci_hcd               35655  0 
ehci_hcd               59455  0 
usbcore               193958  5 usbhid,usb_storage,uhci_hcd,ehci_hcd
usb_common             12525  1 usbcore
i915                  447547  2 
drm_kms_helper         45453  1 i915
drm                   232040  2 i915,drm_kms_helper
i2c_algo_bit           13197  1 i915
i2c_core               33925  5 i2c_i801,i915,drm_kms_helper,drm,i2c_algo_bit
video                  18841  1 i915
button                 13626  1 i915
processor              43534  0 
thermal_sys            19935  2 video,processor
hwmon                  12911  1 thermal_sys
scsi_dh_hp_sw          12745  0 
scsi_dh_rdac           17171  0 
scsi_dh_alua           16940  0 
scsi_dh_emc            17061  0 
scsi_dh                14178  4 scsi_dh_hp_sw,scsi_dh_rdac,scsi_dh_alua,scsi_dh_emc

Last edited by pant3k (2013-01-08 19:17:47)

Re: Secure OS 32 debuging

Ok, thanks. I will now try to recompile a kernel that firs more your configuration and lets hope this time it will work for you and other that have similar configurations.

Re: Secure OS 32 debuging

Ok, try now. I have built in the video driver inside the kernel. If it doesn't work again we'll at least know it is not from the graphic card. Try again the recovery mode of the kernel and if you get again no signal, please notice what is the last you see it might be helpful to understand the issue if it is not from the graphic driver.

https://susestudio.com/a/EmL6GN/secured-os-32-bit

Re: Secure OS 32 debuging

netseclteam wrote:

Ok, try now. I have built in the video driver inside the kernel. If it doesn't work again we'll at least know it is not from the graphic card. Try again the recovery mode of the kernel and if you get again no signal, please notice what is the last you see it might be helpful to understand the issue if it is not from the graphic driver.

https://susestudio.com/a/EmL6GN/secured-os-32-bit

now works

PS. why there is no kern.log file?
This is helpfull in debuging

Last edited by pant3k (2013-01-21 21:07:54)

Re: Secure OS 32 debuging

Great, good that it works. About the log it is either the logging service or grsecurity blocking it, might be an option in the kernel - but I don't belive that. I will look into it, thanks for noticing and happy using. If you find anything else let me know.