Hi,
I tried to install Antix 16 on a very old computer (MSI-6215, P3, 512MB, with an onboard Intel graphic controller 82815), but the ISO (Antix_16_386_full) has a video bug.
I can only see a screen during the Grub display and before Xserver start.
Is there a missing video driver on the ISO ?
Could you fix this bug ?
Regards.
NB : Antix 15 use to run fine on this computer.
-
Posts: 9
- Joined: 29 Jul 2015
-
Posts: 99
- Joined: 07 Feb 2013
#2
Can you drop to a command line? Ctrl + Alt + F2? Can you show us your etc/X11/xorg.conf file?
What does inxi -Fxx output for you?
What does inxi -Fxx output for you?
-
Posts: 2,238
- Joined: 16 Dec 2007
#3
it might not be the video. btw the driver is present.
how long have you waited before giving up on the desktop coming up.
and have you tried the safe or failsafe boot mode?
there is a possibility that a new feature in 16 is creating an issue for you. for intel parts, the boot system on the live media creates a special xorg.conf file that sets the video acceration method for the intel part. this was intended for parts older than sandy bridge era to be set to"uxa" method rather than the current"sna" method.
your chipset might be old enough that it doesn't support uxa, which might be causing a hiccup . If this is the case, you should boot with the"safe" mode,then remove the / etc/X11/xorg.conf file that was created. Then run the installer. On your reboot your intel driver should kick in.
how long have you waited before giving up on the desktop coming up.
and have you tried the safe or failsafe boot mode?
there is a possibility that a new feature in 16 is creating an issue for you. for intel parts, the boot system on the live media creates a special xorg.conf file that sets the video acceration method for the intel part. this was intended for parts older than sandy bridge era to be set to"uxa" method rather than the current"sna" method.
your chipset might be old enough that it doesn't support uxa, which might be causing a hiccup . If this is the case, you should boot with the"safe" mode,then remove the / etc/X11/xorg.conf file that was created. Then run the installer. On your reboot your intel driver should kick in.
-
Posts: 9
- Joined: 29 Jul 2015
#4
Here is the transcript of the xorg.conf file (booting with CD) :
******************
Section"Monitor"
Identifier"Monitor0"
Option"DPMS""true"
EndSection
Section"Device"
Identifier"Device0"
Driver"vesa"
EndSection
Section"Screen"
Identifer"Screen0"
Monitor"Monitor0"
Device"Device0"
DefaultDepth 16
SubSection"Display"
Modes"1280x1024""1333x768""1024x768""800x600"
EndSubSection
EndSection
bus-ID : 00:02.0 chip-ID: 8086:1132
Display Server : X.org 1.16.4 driver: vesa
tty size: 80x25 Advanced Data: N/A for root out of X
With one of my monitors, I can drop to command line (not with another).spaceman wrote:Can you drop to a command line? Ctrl + Alt + F2? Can you show us your etc/X11/xorg.conf file?
Here is the transcript of the xorg.conf file (booting with CD) :
******************
Section"Monitor"
Identifier"Monitor0"
Option"DPMS""true"
EndSection
Section"Device"
Identifier"Device0"
Driver"vesa"
EndSection
Section"Screen"
Identifer"Screen0"
Monitor"Monitor0"
Device"Device0"
DefaultDepth 16
SubSection"Display"
Modes"1280x1024""1333x768""1024x768""800x600"
EndSubSection
EndSection
Graphics : Card: Intel 82815 Graphics Controller (GCC)spaceman wrote:What does inxi -Fxx output for you?
bus-ID : 00:02.0 chip-ID: 8086:1132
Display Server : X.org 1.16.4 driver: vesa
tty size: 80x25 Advanced Data: N/A for root out of X
-
Posts: 9
- Joined: 29 Jul 2015
#5
************************************
undefined video mode number : 314
press enter to see video mode available, space to continue or wait 30sec
current boot codes :
vga=788 quiet spalsh=v disable=lx nomodeset xorg=safe
scaning for harware specific video modules
Configuring etc/X/xorg.conf file with safe
************************************
Can I do these instructions with command line ?
Regards
OK, thanks for the information.dolphin_oracle wrote:it might not be the video. btw the driver is present.
a long time (> 5 minutes with a scrambling screen)dolphin_oracle wrote:how long have you waited before giving up on the desktop coming up.
Yes. When booting, I get these messages :dolphin_oracle wrote:and have you tried the safe or failsafe boot mode?
************************************
undefined video mode number : 314
press enter to see video mode available, space to continue or wait 30sec
current boot codes :
vga=788 quiet spalsh=v disable=lx nomodeset xorg=safe
scaning for harware specific video modules
Configuring etc/X/xorg.conf file with safe
************************************
That's possible ...dolphin_oracle wrote:there is a possibility that a new feature in 16 is creating an issue for you. for intel parts, the boot system on the live media creates a special xorg.conf file that sets the video acceration method for the intel part. this was intended for parts older than sandy bridge era to be set to"uxa" method rather than the current"sna" method.
your chipset might be old enough that it doesn't support uxa, which might be causing a hiccup .
Even with safe mode, I can get video only if I drop to a command line (Ctrl + Alt + F2).dolphin_oracle wrote:If this is the case, you should boot with the"safe" mode,then remove the / etc/X11/xorg.conf file that was created. Then run the installer. On your reboot your intel driver should kick in.
Can I do these instructions with command line ?
Regards
-
Posts: 2,238
- Joined: 16 Dec 2007
#6
Ok, let's try this.
1. on the grub boot screen, choose the standard option, but add a"3" to the boot parameter line
2. this should bring you to a command prompt and not start the X server. change directory to /etc/X11/ and remove xorg.conf (it hasn't been used yet).
3. issue this command to start the display manager
and see if anything is improved.
1. on the grub boot screen, choose the standard option, but add a"3" to the boot parameter line
2. this should bring you to a command prompt and not start the X server. change directory to /etc/X11/ and remove xorg.conf (it hasn't been used yet).
3. issue this command to start the display manager
Code: Select all
sudo service slim start
-
Posts: 9
- Joined: 29 Jul 2015
#7
Hi dolphin,
I followed your instructions and was able to install the system using GUI. Thank you very much.
Now, the system boots but ends on a linux login prompt without GUI. The prompt indicates"Welcome to antiX. Power by Debian. (Name of Computer) login :" and the cursor is blinking.
The problem is that the keyboard is not responding (whether USB or PS/2).
FYI, at the very begining of boot, the system indicates :
After, I also saw this :
Can you help, or is this PC too old for Antix 16 ?
Regards
I followed your instructions and was able to install the system using GUI. Thank you very much.
Now, the system boots but ends on a linux login prompt without GUI. The prompt indicates"Welcome to antiX. Power by Debian. (Name of Computer) login :" and the cursor is blinking.
The problem is that the keyboard is not responding (whether USB or PS/2).
FYI, at the very begining of boot, the system indicates :
Code: Select all
Loading Linux 4.4.10-antix.1-486-smp ...
vga=788 is deprecated. Use set gfxpayload=800x600x16, 800x600 before linux command instead.
Loading initial ramdisk ...
Code: Select all
Setting preliminary keymap ... [] usb 1-1.4: 3:1: cannot get freq at ep 0x84
Regards
-
Posts: 9
- Joined: 29 Jul 2015
#8
Hi,
I finally decided to open the PC and clear the CMOS (= reset the BIOS to default values).
Now, I can use the mouse and keyboard.
However, when I start the PC, I get a command line screen in antix (no X GUI).
I have to select advanced options in GRUB windows and this second option to get a GUI :
antix GNU/Linux, with Linux 4.4.10-antix.1-486-smp (sysvinit)
Can you explain why I have to do this each time (select sysvinit) to get a GUI ?
Is it normal I don't have a"xorg.conf" file in / etc / X11 directory ?
Thank you very much for your help.
I finally decided to open the PC and clear the CMOS (= reset the BIOS to default values).
Now, I can use the mouse and keyboard.
However, when I start the PC, I get a command line screen in antix (no X GUI).
I have to select advanced options in GRUB windows and this second option to get a GUI :
antix GNU/Linux, with Linux 4.4.10-antix.1-486-smp (sysvinit)
Can you explain why I have to do this each time (select sysvinit) to get a GUI ?
Is it normal I don't have a"xorg.conf" file in / etc / X11 directory ?
Thank you very much for your help.
-
Posts: 2,238
- Joined: 16 Dec 2007
#9
It's normal to not have a xorg.conf. I'll look into the differences in the boot options. You might post your /boot/grub.cfg .
-
Posts: 47
- Joined: 20 Apr 2016
#10
Hello, tahitibub...
I am reluctant to butt-in, BUT, I hate to see others struggle - and I too have an old system (with an old graphics card, but not Intel).
Since I am new at working down in the guts of Linux, I offer this help as"try" only. If it fails then change the modified settings back immediately (and wait for other help).
Before continuing I am a little unclear if you have an Antix system installed onto HD, or if you are working from some"Live" system - or even something else.
IF you are NOT working from HD install then none of the following applies.
IF you ARE working from an Antix installed onto HD then perhaps the following might help...
(A.) ATTEMPT WITH (ie USING) VESA DRIVER, PLUS MODIFIED KERNEL LINE ARGS
I learned that I had to set or unset certain kernel args (ie on the kernel line in old grub-0.97) at boot time.
My setup seemed to have a lot of trouble with VESA, so I tried to stay clear of it.
1.
If you keep the line > Driver"VESA" < in xorg.conf (as you had in an earlier post) then only do steps 2. and 3. below (and reboot).
[However, if it doesn't work and you next try part (B.) - by commenting out VESA (as described later) - then you might do steps 2. and 3. anyway (just to see what happens). Perhaps not?]
2.
On the kernel line (in grub) I remove:- vga=788
[Advice somewhere in another forum said using it interfered with loading the VESA driver later in the boot.]
3.
On kernel line I included :- nosmp
[Yes; I prevented usage even though the kernel was ---.smp because I discovered my CPU was not smp.]
.
(B.) ATTEMPT WITHOUT VESA, BUT WITH CORRECT VIDEO-CARD DRIVER
If you find the right video card driver then include it in xorg.conf (as described below) and comment out the VESA line with # at the start of line, then do the following...
4.
At CLI (command line) inside the booted system, edit / etc/X11/xorg.conf file and setup loading of the right driver.
(For you I don't know. Antix-16 does have"intel" in the /usr/lib/xorg/modules/drivers directory - or is it"nouveau" or some other thing for you. Others might help on that.) So in xorg.conf comment out the VESA line and add your driver (ie use the name of YOUR video-card driver, and included inside the double-quotes):-
5.
You also might need to ensure your xorg.conf file has a modules section, which loads the right module (ie the module containing your driver, and include it inside the double-quotes):-
However it might also need the video-for-linux module, eg...
[Someone else might have to advise you on checking if the v4l module is installed/available on the system, or how to"apt-get" it first. I don't know how to do that exactly.]
.
.
As I said before, if that doesn't work - sorry. It all worked for me.
Regards,
aka boombaby
I am reluctant to butt-in, BUT, I hate to see others struggle - and I too have an old system (with an old graphics card, but not Intel).
Since I am new at working down in the guts of Linux, I offer this help as"try" only. If it fails then change the modified settings back immediately (and wait for other help).
Before continuing I am a little unclear if you have an Antix system installed onto HD, or if you are working from some"Live" system - or even something else.
IF you are NOT working from HD install then none of the following applies.
IF you ARE working from an Antix installed onto HD then perhaps the following might help...
(A.) ATTEMPT WITH (ie USING) VESA DRIVER, PLUS MODIFIED KERNEL LINE ARGS
I learned that I had to set or unset certain kernel args (ie on the kernel line in old grub-0.97) at boot time.
My setup seemed to have a lot of trouble with VESA, so I tried to stay clear of it.
1.
If you keep the line > Driver"VESA" < in xorg.conf (as you had in an earlier post) then only do steps 2. and 3. below (and reboot).
[However, if it doesn't work and you next try part (B.) - by commenting out VESA (as described later) - then you might do steps 2. and 3. anyway (just to see what happens). Perhaps not?]
2.
On the kernel line (in grub) I remove:- vga=788
[Advice somewhere in another forum said using it interfered with loading the VESA driver later in the boot.]
3.
On kernel line I included :- nosmp
[Yes; I prevented usage even though the kernel was ---.smp because I discovered my CPU was not smp.]
.
(B.) ATTEMPT WITHOUT VESA, BUT WITH CORRECT VIDEO-CARD DRIVER
If you find the right video card driver then include it in xorg.conf (as described below) and comment out the VESA line with # at the start of line, then do the following...
4.
At CLI (command line) inside the booted system, edit / etc/X11/xorg.conf file and setup loading of the right driver.
(For you I don't know. Antix-16 does have"intel" in the /usr/lib/xorg/modules/drivers directory - or is it"nouveau" or some other thing for you. Others might help on that.) So in xorg.conf comment out the VESA line and add your driver (ie use the name of YOUR video-card driver, and included inside the double-quotes):-
Code: Select all
Load"right driver here"
You also might need to ensure your xorg.conf file has a modules section, which loads the right module (ie the module containing your driver, and include it inside the double-quotes):-
Code: Select all
Section"Module"
Load"right module here"
EndSection
Code: Select all
Section"Module"
Load"v4l"
Load"right module here"
EndSection
.
.
As I said before, if that doesn't work - sorry. It all worked for me.
Regards,
aka boombaby
-
Posts: 9
- Joined: 29 Jul 2015
#11
I don't manage to publish my grub.cfg here, I always get a"Forbidden - You don't have permission to access /posting.php on this server.".
Hi,dolphin_oracle wrote:It's normal to not have a xorg.conf. I'll look into the differences in the boot options. You might post your /boot/grub.cfg .
I don't manage to publish my grub.cfg here, I always get a"Forbidden - You don't have permission to access /posting.php on this server.".
-
Posts: 521
- Joined: 20 Apr 2015
#12
Put a space between the / and etc.
- Posts: 9 tahitibub
- Joined: 29 Jul 2015
#13
@ boombaby
Hi,
I have no xorg.conf file, so I don't know how to specify the driver to use.
However, I applied your advices 2 and 3 (remove"vga=788" and add"nosmp"), but without hyphen ("-").
Regards
Hi,
I have no xorg.conf file, so I don't know how to specify the driver to use.
However, I applied your advices 2 and 3 (remove"vga=788" and add"nosmp"), but without hyphen ("-").
Regards
-
Posts: 9
- Joined: 29 Jul 2015
#14
Here is the initial grub.cfg (before removing"vga=788" and adding"nosmp" to lines 142, 160 and 177) :Shay wrote:Put a space between the / and etc.
Code: Select all
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from / etc/grub.d and settings from / etc/default/grub
#
### BEGIN / etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
if ["${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if ["${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z"${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 d4e4d70f-2ef4-4ef4-974c-bdf132c27c8f
else
search --no-floppy --fs-uuid --set=root d4e4d70f-2ef4-4ef4-974c-bdf132c27c8f
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 d4e4d70f-2ef4-4ef4-974c-bdf132c27c8f
else
search --no-floppy --fs-uuid --set=root d4e4d70f-2ef4-4ef4-974c-bdf132c27c8f
fi
insmod jpeg
background_image -m stretch /usr/share/wallpaper/back.jpg
if ["${recordfail}" = 1 ] ; then
set timeout=-1
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
fi
### END / etc/grub.d/00_header ###
### BEGIN / etc/grub.d/05_debian_theme ###
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 d4e4d70f-2ef4-4ef4-974c-bdf132c27c8f
else
search --no-floppy --fs-uuid --set=root d4e4d70f-2ef4-4ef4-974c-bdf132c27c8f
fi
insmod jpeg
if background_image /usr/share/wallpaper/back.jpg; then
true
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END / etc/grub.d/05_debian_theme ###
### BEGIN / etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'antiX GNU/Linux' --class antix --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-d4e4d70f-2ef4-4ef4-974c-bdf132c27c8f' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 d4e4d70f-2ef4-4ef4-974c-bdf132c27c8f
else
search --no-floppy --fs-uuid --set=root d4e4d70f-2ef4-4ef4-974c-bdf132c27c8f
fi
echo 'Loading Linux 4.4.10-antix.1-486-smp ...'
linux /boot/vmlinuz-4.4.10-antix.1-486-smp root=UUID=d4e4d70f-2ef4-4ef4-974c-bdf132c27c8f ro vga=788 quiet 3
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-4.4.10-antix.1-486-smp
}
submenu 'Advanced options for antiX GNU/Linux' $menuentry_id_option 'gnulinux-advanced-d4e4d70f-2ef4-4ef4-974c-bdf132c27c8f' {
menuentry 'antiX GNU/Linux, with Linux 4.4.10-antix.1-486-smp' --class antix --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.10-antix.1-486-smp-advanced-d4e4d70f-2ef4-4ef4-974c-bdf132c27c8f' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 d4e4d70f-2ef4-4ef4-974c-bdf132c27c8f
else
search --no-floppy --fs-uuid --set=root d4e4d70f-2ef4-4ef4-974c-bdf132c27c8f
fi
echo 'Loading Linux 4.4.10-antix.1-486-smp ...'
linux /boot/vmlinuz-4.4.10-antix.1-486-smp root=UUID=d4e4d70f-2ef4-4ef4-974c-bdf132c27c8f ro vga=788 quiet 3
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-4.4.10-antix.1-486-smp
}
menuentry 'antiX GNU/Linux, with Linux 4.4.10-antix.1-486-smp (sysvinit)' --class antix --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.10-antix.1-486-smp-init-sysvinit-d4e4d70f-2ef4-4ef4-974c-bdf132c27c8f' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 d4e4d70f-2ef4-4ef4-974c-bdf132c27c8f
else
search --no-floppy --fs-uuid --set=root d4e4d70f-2ef4-4ef4-974c-bdf132c27c8f
fi
echo 'Loading Linux 4.4.10-antix.1-486-smp ...'
linux /boot/vmlinuz-4.4.10-antix.1-486-smp root=UUID=d4e4d70f-2ef4-4ef4-974c-bdf132c27c8f ro vga=788 quiet 3 init=/lib/sysvinit/init
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-4.4.10-antix.1-486-smp
}
}
### END / etc/grub.d/10_linux ###
### BEGIN / etc/grub.d/20_linux_xen ###
### END / etc/grub.d/20_linux_xen ###
### BEGIN / etc/grub.d/20_memtest86+ ###
menuentry"Memory test (memtest86+)" {
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 d4e4d70f-2ef4-4ef4-974c-bdf132c27c8f
else
search --no-floppy --fs-uuid --set=root d4e4d70f-2ef4-4ef4-974c-bdf132c27c8f
fi
linux16 /boot/memtest86+.bin
}
menuentry"Memory test (memtest86+, serial console 115200)" {
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 d4e4d70f-2ef4-4ef4-974c-bdf132c27c8f
else
search --no-floppy --fs-uuid --set=root d4e4d70f-2ef4-4ef4-974c-bdf132c27c8f
fi
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
menuentry"Memory test (memtest86+, experimental multiboot)" {
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 d4e4d70f-2ef4-4ef4-974c-bdf132c27c8f
else
search --no-floppy --fs-uuid --set=root d4e4d70f-2ef4-4ef4-974c-bdf132c27c8f
fi
multiboot /boot/memtest86+_multiboot.bin
}
menuentry"Memory test (memtest86+, serial console 115200, experimental multiboot)" {
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 d4e4d70f-2ef4-4ef4-974c-bdf132c27c8f
else
search --no-floppy --fs-uuid --set=root d4e4d70f-2ef4-4ef4-974c-bdf132c27c8f
fi
multiboot /boot/memtest86+_multiboot.bin console=ttyS0,115200n8
}
### END / etc/grub.d/20_memtest86+ ###
### BEGIN / etc/grub.d/30_os-prober ###
### END / etc/grub.d/30_os-prober ###
### BEGIN / etc/grub.d/30_uefi-firmware ###
### END / etc/grub.d/30_uefi-firmware ###
### BEGIN / etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END / etc/grub.d/40_custom ###
### BEGIN / etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z"${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END / etc/grub.d/41_custom ###
-
Posts: 47
- Joined: 20 Apr 2016
#15
Hello, tahitibub...
Others might need to help you out here. I think you might have gone a bit too deep into the system when it needs a lighter touch.
As I suggested before, you can try either (A.) or (B.)
(A.) was for using VESA video driver (as you showed in your original xorg.conf file) BUT to do that you (MIGHT) need to modify the kernel line in the Grub file (as I showed)
(B.) was for using your physical device (ie video card) video driver.
So I am suggesting you can use one solution or the other BUT you might need to do the"nosmp" part anyway (depending on CPU type).
.
Here's a small wrap-up to try and help...
(I) MODIFYING GRUB
Also I boot with the old Grub-0.97
> You are using the modern Grub-2
> At the top of the .cfg file that you showed it says"don't edit". However I know there is another file you can edit, but I'm not sure which. (Others can help on that.)
So for me (in Grub-0.97) I only edited one line - the"kernel" line. So steps (2.) and (3.) that I mentioned happen on one line.
ie
2.) Remove any"vga=..." ie for you remove the vga=788 OFF the one kernel line
3.) Add nosmp on the same kernel line
Those modifications you do in Grub are prepping your boot for using the VESA DRIVER when it (Linux) starts up the xorg.conf file.
.
(II) MODIFYING xorg.conf FILE - FOR EITHER VESA DRIVER OR THE RIGHT DEVICE DRIVER
In another post I had to supply my org.conf for inspection. Here is my post...
That's mine. It sits under"/ etc/X11" directory - ie"/ etc/X11/xorg.conf"
(It is specific to my PC, but you can copy the structure - and replace YOUR PC details.)
See the two bolded parts where I show my video Module and video Driver? See my driver is entered as...
You need to replace your module and driver there (IF you are not using VESA).
So that's where you use (ie type in) the VESA module and VESA driver OR your device module and device driver.
>> So in the Section"Module" type in...
> OR
(which contains some driver info for your card)
...depending on which direction you've taken.
.
>> And in Section"Device" type in...
> OR
...depending on which direction you've taken.
.
N.B.
All that I have said has two caveats:-
(i) That your GRUB-2 modern setup is fixable in the same way as my older GRUB-0.97 setup. (Others will know for sure, and help.)
(ii) That I know what I am doing. (That's never a surety - in which case others will jump on me from high places.)
.
P.S.
tahitibub, do I detect that English is your second language (and that you might be translating parts of the information)? Sometimes that can cause difficulty in getting all the tweaks right too, so stick with it.
Regards,
aka boombaby
Others might need to help you out here. I think you might have gone a bit too deep into the system when it needs a lighter touch.
As I suggested before, you can try either (A.) or (B.)
(A.) was for using VESA video driver (as you showed in your original xorg.conf file) BUT to do that you (MIGHT) need to modify the kernel line in the Grub file (as I showed)
(B.) was for using your physical device (ie video card) video driver.
So I am suggesting you can use one solution or the other BUT you might need to do the"nosmp" part anyway (depending on CPU type).
.
Here's a small wrap-up to try and help...
(I) MODIFYING GRUB
Also I boot with the old Grub-0.97
> You are using the modern Grub-2
> At the top of the .cfg file that you showed it says"don't edit". However I know there is another file you can edit, but I'm not sure which. (Others can help on that.)
So for me (in Grub-0.97) I only edited one line - the"kernel" line. So steps (2.) and (3.) that I mentioned happen on one line.
ie
2.) Remove any"vga=..." ie for you remove the vga=788 OFF the one kernel line
3.) Add nosmp on the same kernel line
Those modifications you do in Grub are prepping your boot for using the VESA DRIVER when it (Linux) starts up the xorg.conf file.
.
(II) MODIFYING xorg.conf FILE - FOR EITHER VESA DRIVER OR THE RIGHT DEVICE DRIVER
In another post I had to supply my org.conf for inspection. Here is my post...
Code: Select all
./i-just-installed-antix-16-here-s-what-happened-t6463.html
.
Scroll down to the post by me (aka boombaby) dated:"Posted: Tue Jul 05, 2016 5:43 pm"
.
And look at section:">>3. CURRENT xorg.conf FILE WHEN RUNNING INSTALLED ANTIX (ie NORMAL USE)"
(It is specific to my PC, but you can copy the structure - and replace YOUR PC details.)
See the two bolded parts where I show my video Module and video Driver? See my driver is entered as...
Code: Select all
Driver"sisimedia"
So that's where you use (ie type in) the VESA module and VESA driver OR your device module and device driver.
>> So in the Section"Module" type in...
Code: Select all
Load"VESA"
Code: Select all
Load"the right module"
(which contains some driver info for your card)
...depending on which direction you've taken.
.
>> And in Section"Device" type in...
Code: Select all
Driver"VESA"
> OR
Code: Select all
Driver"your driver"
.
N.B.
All that I have said has two caveats:-
(i) That your GRUB-2 modern setup is fixable in the same way as my older GRUB-0.97 setup. (Others will know for sure, and help.)
(ii) That I know what I am doing. (That's never a surety - in which case others will jump on me from high places.)
.
P.S.
tahitibub, do I detect that English is your second language (and that you might be translating parts of the information)? Sometimes that can cause difficulty in getting all the tweaks right too, so stick with it.
Regards,
aka boombaby