Public bug reported:
Binary package hint: eiciel
The version 0.9-1 of eiciel is known to cause Nautilus to restart when opening
a property-view on a file or folder on the Gnome Desktop.
On Debian this was also the case.
Version 0.9.2-1 of eiciel (Debian testing repository) seems to resolve that
Public bug reported:
This relates to the eiciel bug I filed earlier.
I know eiciel is not (yet) a supported ubuntu package, but,
If ubuntu is going support the beagle-engine later-on then ea/acl-support is
paramount:
- the file-system should be mounted with acl,user_xattr on installation
- packag
ed in *two*
/etc/config-files.
The third culprit is that apparmor does not correctly reloads changes by a
simple restart.
Access on my ~/pdfout123 is: 755 (did not try other settings but logic
suggests 700 should work too.
I hope this works as good for you as it did for me,
Cheers,
Inte
For me this worked :
sudo echo "fbcon" >> /etc/modules
sudo echo "vesafb" >> /etc/modules
sudo update-initramfs -v -u -k $(uname -r)
The screen will remain blank for some time until the drivers are loaded.
To have them loaded earlier-on initrd has to be modified.
Some info of my machine:
grub me
@ardchoille
I actually used mc as root to add the module-names and then posted the
append-commands without checking if they worked.
And you are right, they don't work; shame on me.
Your comment reminds me again to always double-check before posting.
Thanks !
--
tty[1-6] are active but display n
@Goodness
Maybe this script fixes it for you.
** Attachment added: "Fix gutsy initrd.img to load vesafb unconditionally"
http://launchpadlibrarian.net/10292550/fix-gutsy-initramfs
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You received this bu
@Goodness
The pushd and popd commands could not be found on your system.
I did not realize they are not installed by default, sorry for that.
Here is a fixed script.
Hope this one works for you.
@angel1127
The vesafb should work with any vesa 2.0 compliant videocard.
It is only used for the conso
@Shriramana Sharma
In my former post I meant: vga=792 uses 24-bpp.
So try vga=791 and please see if this new script fixes the cpio error you had.
** Attachment added: "Script to fix gutsy initrd.img to load vesafb
unconditionally #4"
http://launchpadlibrarian.net/10301766/fix-gutsy-initramfs
ou.
Server: kubrick.freenode.net
Channel: #ubuntu
Nick: interbird
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
u
@Shriramana Sharma
You are right, I was wondering why pushd and popd were not found.
I changed the symlink from dash to bash on my system months ago due to more
strange behaviour from dash.
(I upgraded feisty to gutsy which left my symlink to bash untouched)
I too quickly tried to determine which
@angel1127
Vesa is a videocard independant standard to access higher resolutions than
standard vga (640x480x16).
Almost any recent videocard supports this.
You can read what vesa is here:
http://en.wikipedia.org/wiki/VESA_BIOS_Extensions
$kernel-source/Documentation/fb/vesafb.txt is correct in t
@Goodness
Can you send your initrd image to the email-address in the script?
I'll try it on my system to see what's wrong with it.
Please also include the out put of the lspci -v and lmod commands.
*Before you modprobe vesafb; thus when your Ctrl-Alt-Fn terminals are blank*
You can use: lspci -v >
@strabes
At boot-time the splash-screen takes it's resolution from /etc/usplash.conf,
*which is in the initramfs image* !
At boot the root-filesystem is changed from the initramfs to the real-root.
Your system is on the real-root.
On shutdown, the splash-screen takes it's resolution, again, from
errata:
#1
s/Which is different/Which could be different/
#2
What's a link to a link without a link...
http://en.wikipedia.org/wiki/VESA_BIOS_Extensions#Linux_video_mode_numbers
(thx, caravel)
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You receiv
@strabes
To extract the usplash.conf file from the initramfs, follow these steps:
1. open a terminal
2. run this command: mkdir tmp; cd tmp; gzip -cd /boot/initrd.img-$(uname -r) |
cpio -im; cp -a etc/usplash.conf ..; cd ..; rm -rf tmp
(best is to paste this line in your terminal, if you retype i
@strabes
At boot-time the splash-screen takes it's resolution from /etc/usplash.conf,
*which is in the initramfs image* !
At boot the root-filesystem is changed from the initramfs to the real-root.
Your system is on the real-root.
On shutdown, the splash-screen takes it's resolution, again, from
errata:
#1
s/Which is different/Which could be different/
#2
What's a link to a link without a link...
http://en.wikipedia.org/wiki/VESA_BIOS_Extensions#Linux_video_mode_numbers
(thx, caravel)
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You receiv
@strabes
To extract the usplash.conf file from the initramfs, follow these steps:
1. open a terminal
2. run this command: mkdir tmp; cd tmp; gzip -cd /boot/initrd.img-$(uname -r) |
cpio -im; cp -a etc/usplash.conf ..; cd ..; rm -rf tmp
(best is to paste this line in your terminal, if you retype i
For me this worked :
sudo echo "fbcon" >> /etc/modules
sudo echo "vesafb" >> /etc/modules
sudo update-initramfs -v -u -k $(uname -r)
The screen will remain blank for some time until the drivers are loaded.
To have them loaded earlier-on initrd has to be modified.
Some info of my machine:
grub me
@Goodness
Maybe this script fixes it for you.
** Attachment added: "Fix gutsy initrd.img to load vesafb unconditionally"
http://launchpadlibrarian.net/10292550/fix-gutsy-initramfs
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You received this bu
@Goodness
The pushd and popd commands could not be found on your system.
I did not realize they are not installed by default, sorry for that.
Here is a fixed script.
Hope this one works for you.
@angel1127
The vesafb should work with any vesa 2.0 compliant videocard.
It is only used for the conso
@Shriramana Sharma
In my former post I meant: vga=792 uses 24-bpp.
So try vga=791 and please see if this new script fixes the cpio error you had.
** Attachment added: "Script to fix gutsy initrd.img to load vesafb
unconditionally #4"
http://launchpadlibrarian.net/10301766/fix-gutsy-initramfs
ou.
Server: kubrick.freenode.net
Channel: #ubuntu
Nick: interbird
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
u
@Shriramana Sharma
You are right, I was wondering why pushd and popd were not found.
I changed the symlink from dash to bash on my system months ago due to more
strange behaviour from dash.
(I upgraded feisty to gutsy which left my symlink to bash untouched)
I too quickly tried to determine which
@angel1127
Vesa is a videocard independant standard to access higher resolutions than
standard vga (640x480x16).
Almost any recent videocard supports this.
You can read what vesa is here:
http://en.wikipedia.org/wiki/VESA_BIOS_Extensions
$kernel-source/Documentation/fb/vesafb.txt is correct in t
@Goodness
Can you send your initrd image to the email-address in the script?
I'll try it on my system to see what's wrong with it.
Please also include the out put of the lspci -v and lmod commands.
*Before you modprobe vesafb; thus when your Ctrl-Alt-Fn terminals are blank*
You can use: lspci -v >
@ardchoille
I actually used mc as root to add the module-names and then posted the
append-commands without checking if they worked.
And you are right, they don't work; shame on me.
Your comment reminds me again to always double-check before posting.
Thanks !
--
tty[1-6] are active but display n
Public bug reported:
Binary package hint: eiciel
The version 0.9-1 of eiciel is known to cause Nautilus to restart when opening
a property-view on a file or folder on the Gnome Desktop.
On Debian this was also the case.
Version 0.9.2-1 of eiciel (Debian testing repository) seems to resolve that
Public bug reported:
This relates to the eiciel bug I filed earlier.
I know eiciel is not (yet) a supported ubuntu package, but,
If ubuntu is going support the beagle-engine later-on then ea/acl-support is
paramount:
- the file-system should be mounted with acl,user_xattr on installation
- packag
Public bug reported:
Binary package hint: eiciel
The version 0.9-1 of eiciel is known to cause Nautilus to restart when opening
a property-view on a file or folder on the Gnome Desktop.
On Debian this was also the case.
Version 0.9.2-1 of eiciel (Debian testing repository) seems to resolve that
Public bug reported:
This relates to the eiciel bug I filed earlier.
I know eiciel is not (yet) a supported ubuntu package, but,
If ubuntu is going support the beagle-engine later-on then ea/acl-support is
paramount:
- the file-system should be mounted with acl,user_xattr on installation
- packag
ed in *two*
/etc/config-files.
The third culprit is that apparmor does not correctly reloads changes by a
simple restart.
Access on my ~/pdfout123 is: 755 (did not try other settings but logic
suggests 700 should work too.
I hope this works as good for you as it did for me,
Cheers,
Inte
For me this worked :
sudo echo "fbcon" >> /etc/modules
sudo echo "vesafb" >> /etc/modules
sudo update-initramfs -v -u -k $(uname -r)
The screen will remain blank for some time until the drivers are loaded.
To have them loaded earlier-on initrd has to be modified.
Some info of my machine:
grub me
@ardchoille
I actually used mc as root to add the module-names and then posted the
append-commands without checking if they worked.
And you are right, they don't work; shame on me.
Your comment reminds me again to always double-check before posting.
Thanks !
--
tty[1-6] are active but display n
@Goodness
Maybe this script fixes it for you.
** Attachment added: "Fix gutsy initrd.img to load vesafb unconditionally"
http://launchpadlibrarian.net/10292550/fix-gutsy-initramfs
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You received this bu
@Goodness
The pushd and popd commands could not be found on your system.
I did not realize they are not installed by default, sorry for that.
Here is a fixed script.
Hope this one works for you.
@angel1127
The vesafb should work with any vesa 2.0 compliant videocard.
It is only used for the conso
@Shriramana Sharma
In my former post I meant: vga=792 uses 24-bpp.
So try vga=791 and please see if this new script fixes the cpio error you had.
** Attachment added: "Script to fix gutsy initrd.img to load vesafb
unconditionally #4"
http://launchpadlibrarian.net/10301766/fix-gutsy-initramfs
ou.
Server: kubrick.freenode.net
Channel: #ubuntu
Nick: interbird
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
u
@Shriramana Sharma
You are right, I was wondering why pushd and popd were not found.
I changed the symlink from dash to bash on my system months ago due to more
strange behaviour from dash.
(I upgraded feisty to gutsy which left my symlink to bash untouched)
I too quickly tried to determine which
@angel1127
Vesa is a videocard independant standard to access higher resolutions than
standard vga (640x480x16).
Almost any recent videocard supports this.
You can read what vesa is here:
http://en.wikipedia.org/wiki/VESA_BIOS_Extensions
$kernel-source/Documentation/fb/vesafb.txt is correct in t
@Goodness
Can you send your initrd image to the email-address in the script?
I'll try it on my system to see what's wrong with it.
Please also include the out put of the lspci -v and lmod commands.
*Before you modprobe vesafb; thus when your Ctrl-Alt-Fn terminals are blank*
You can use: lspci -v >
@strabes
At boot-time the splash-screen takes it's resolution from /etc/usplash.conf,
*which is in the initramfs image* !
At boot the root-filesystem is changed from the initramfs to the real-root.
Your system is on the real-root.
On shutdown, the splash-screen takes it's resolution, again, from
errata:
#1
s/Which is different/Which could be different/
#2
What's a link to a link without a link...
http://en.wikipedia.org/wiki/VESA_BIOS_Extensions#Linux_video_mode_numbers
(thx, caravel)
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You receiv
@strabes
To extract the usplash.conf file from the initramfs, follow these steps:
1. open a terminal
2. run this command: mkdir tmp; cd tmp; gzip -cd /boot/initrd.img-$(uname -r) |
cpio -im; cp -a etc/usplash.conf ..; cd ..; rm -rf tmp
(best is to paste this line in your terminal, if you retype i
ed in *two*
/etc/config-files.
The third culprit is that apparmor does not correctly reloads changes by a
simple restart.
Access on my ~/pdfout123 is: 755 (did not try other settings but logic
suggests 700 should work too.
I hope this works as good for you as it did for me,
Cheers,
Inte
Public bug reported:
Binary package hint: eiciel
The version 0.9-1 of eiciel is known to cause Nautilus to restart when opening
a property-view on a file or folder on the Gnome Desktop.
On Debian this was also the case.
Version 0.9.2-1 of eiciel (Debian testing repository) seems to resolve that
Public bug reported:
This relates to the eiciel bug I filed earlier.
I know eiciel is not (yet) a supported ubuntu package, but,
If ubuntu is going support the beagle-engine later-on then ea/acl-support is
paramount:
- the file-system should be mounted with acl,user_xattr on installation
- packag
For me this worked :
sudo echo "fbcon" >> /etc/modules
sudo echo "vesafb" >> /etc/modules
sudo update-initramfs -v -u -k $(uname -r)
The screen will remain blank for some time until the drivers are loaded.
To have them loaded earlier-on initrd has to be modified.
Some info of my machine:
grub me
@ardchoille
I actually used mc as root to add the module-names and then posted the
append-commands without checking if they worked.
And you are right, they don't work; shame on me.
Your comment reminds me again to always double-check before posting.
Thanks !
--
tty[1-6] are active but display n
@Goodness
Maybe this script fixes it for you.
** Attachment added: "Fix gutsy initrd.img to load vesafb unconditionally"
http://launchpadlibrarian.net/10292550/fix-gutsy-initramfs
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You received this bu
@Goodness
The pushd and popd commands could not be found on your system.
I did not realize they are not installed by default, sorry for that.
Here is a fixed script.
Hope this one works for you.
@angel1127
The vesafb should work with any vesa 2.0 compliant videocard.
It is only used for the conso
@Shriramana Sharma
In my former post I meant: vga=792 uses 24-bpp.
So try vga=791 and please see if this new script fixes the cpio error you had.
** Attachment added: "Script to fix gutsy initrd.img to load vesafb
unconditionally #4"
http://launchpadlibrarian.net/10301766/fix-gutsy-initramfs
ou.
Server: kubrick.freenode.net
Channel: #ubuntu
Nick: interbird
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
u
@Shriramana Sharma
You are right, I was wondering why pushd and popd were not found.
I changed the symlink from dash to bash on my system months ago due to more
strange behaviour from dash.
(I upgraded feisty to gutsy which left my symlink to bash untouched)
I too quickly tried to determine which
@angel1127
Vesa is a videocard independant standard to access higher resolutions than
standard vga (640x480x16).
Almost any recent videocard supports this.
You can read what vesa is here:
http://en.wikipedia.org/wiki/VESA_BIOS_Extensions
$kernel-source/Documentation/fb/vesafb.txt is correct in t
@Goodness
Can you send your initrd image to the email-address in the script?
I'll try it on my system to see what's wrong with it.
Please also include the out put of the lspci -v and lmod commands.
*Before you modprobe vesafb; thus when your Ctrl-Alt-Fn terminals are blank*
You can use: lspci -v >
@strabes
At boot-time the splash-screen takes it's resolution from /etc/usplash.conf,
*which is in the initramfs image* !
At boot the root-filesystem is changed from the initramfs to the real-root.
Your system is on the real-root.
On shutdown, the splash-screen takes it's resolution, again, from
errata:
#1
s/Which is different/Which could be different/
#2
What's a link to a link without a link...
http://en.wikipedia.org/wiki/VESA_BIOS_Extensions#Linux_video_mode_numbers
(thx, caravel)
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You receiv
@strabes
To extract the usplash.conf file from the initramfs, follow these steps:
1. open a terminal
2. run this command: mkdir tmp; cd tmp; gzip -cd /boot/initrd.img-$(uname -r) |
cpio -im; cp -a etc/usplash.conf ..; cd ..; rm -rf tmp
(best is to paste this line in your terminal, if you retype i
@Goodness
Maybe this script fixes it for you.
** Attachment added: "Fix gutsy initrd.img to load vesafb unconditionally"
http://launchpadlibrarian.net/10292550/fix-gutsy-initramfs
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You received this bu
@Goodness
The pushd and popd commands could not be found on your system.
I did not realize they are not installed by default, sorry for that.
Here is a fixed script.
Hope this one works for you.
@angel1127
The vesafb should work with any vesa 2.0 compliant videocard.
It is only used for the conso
@Shriramana Sharma
In my former post I meant: vga=792 uses 24-bpp.
So try vga=791 and please see if this new script fixes the cpio error you had.
** Attachment added: "Script to fix gutsy initrd.img to load vesafb
unconditionally #4"
http://launchpadlibrarian.net/10301766/fix-gutsy-initramfs
ou.
Server: kubrick.freenode.net
Channel: #ubuntu
Nick: interbird
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
u
@Shriramana Sharma
You are right, I was wondering why pushd and popd were not found.
I changed the symlink from dash to bash on my system months ago due to more
strange behaviour from dash.
(I upgraded feisty to gutsy which left my symlink to bash untouched)
I too quickly tried to determine which
@angel1127
Vesa is a videocard independant standard to access higher resolutions than
standard vga (640x480x16).
Almost any recent videocard supports this.
You can read what vesa is here:
http://en.wikipedia.org/wiki/VESA_BIOS_Extensions
$kernel-source/Documentation/fb/vesafb.txt is correct in t
@Goodness
Can you send your initrd image to the email-address in the script?
I'll try it on my system to see what's wrong with it.
Please also include the out put of the lspci -v and lmod commands.
*Before you modprobe vesafb; thus when your Ctrl-Alt-Fn terminals are blank*
You can use: lspci -v >
@strabes
At boot-time the splash-screen takes it's resolution from /etc/usplash.conf,
*which is in the initramfs image* !
At boot the root-filesystem is changed from the initramfs to the real-root.
Your system is on the real-root.
On shutdown, the splash-screen takes it's resolution, again, from
errata:
#1
s/Which is different/Which could be different/
#2
What's a link to a link without a link...
http://en.wikipedia.org/wiki/VESA_BIOS_Extensions#Linux_video_mode_numbers
(thx, caravel)
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You receiv
@strabes
To extract the usplash.conf file from the initramfs, follow these steps:
1. open a terminal
2. run this command: mkdir tmp; cd tmp; gzip -cd /boot/initrd.img-$(uname -r) |
cpio -im; cp -a etc/usplash.conf ..; cd ..; rm -rf tmp
(best is to paste this line in your terminal, if you retype i
Public bug reported:
Binary package hint: eiciel
The version 0.9-1 of eiciel is known to cause Nautilus to restart when opening
a property-view on a file or folder on the Gnome Desktop.
On Debian this was also the case.
Version 0.9.2-1 of eiciel (Debian testing repository) seems to resolve that
Public bug reported:
This relates to the eiciel bug I filed earlier.
I know eiciel is not (yet) a supported ubuntu package, but,
If ubuntu is going support the beagle-engine later-on then ea/acl-support is
paramount:
- the file-system should be mounted with acl,user_xattr on installation
- packag
For me this worked :
sudo echo "fbcon" >> /etc/modules
sudo echo "vesafb" >> /etc/modules
sudo update-initramfs -v -u -k $(uname -r)
The screen will remain blank for some time until the drivers are loaded.
To have them loaded earlier-on initrd has to be modified.
Some info of my machine:
grub me
@ardchoille
I actually used mc as root to add the module-names and then posted the
append-commands without checking if they worked.
And you are right, they don't work; shame on me.
Your comment reminds me again to always double-check before posting.
Thanks !
--
tty[1-6] are active but display n
ed in *two*
/etc/config-files.
The third culprit is that apparmor does not correctly reloads changes by a
simple restart.
Access on my ~/pdfout123 is: 755 (did not try other settings but logic
suggests 700 should work too.
I hope this works as good for you as it did for me,
Cheers,
Inte
ed in *two*
/etc/config-files.
The third culprit is that apparmor does not correctly reloads changes by a
simple restart.
Access on my ~/pdfout123 is: 755 (did not try other settings but logic
suggests 700 should work too.
I hope this works as good for you as it did for me,
Cheers,
Inte
Public bug reported:
Binary package hint: eiciel
The version 0.9-1 of eiciel is known to cause Nautilus to restart when opening
a property-view on a file or folder on the Gnome Desktop.
On Debian this was also the case.
Version 0.9.2-1 of eiciel (Debian testing repository) seems to resolve that
Public bug reported:
This relates to the eiciel bug I filed earlier.
I know eiciel is not (yet) a supported ubuntu package, but,
If ubuntu is going support the beagle-engine later-on then ea/acl-support is
paramount:
- the file-system should be mounted with acl,user_xattr on installation
- packag
For me this worked :
sudo echo "fbcon" >> /etc/modules
sudo echo "vesafb" >> /etc/modules
sudo update-initramfs -v -u -k $(uname -r)
The screen will remain blank for some time until the drivers are loaded.
To have them loaded earlier-on initrd has to be modified.
Some info of my machine:
grub me
@ardchoille
I actually used mc as root to add the module-names and then posted the
append-commands without checking if they worked.
And you are right, they don't work; shame on me.
Your comment reminds me again to always double-check before posting.
Thanks !
--
tty[1-6] are active but display n
@Goodness
Maybe this script fixes it for you.
** Attachment added: "Fix gutsy initrd.img to load vesafb unconditionally"
http://launchpadlibrarian.net/10292550/fix-gutsy-initramfs
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You received this bu
@Goodness
The pushd and popd commands could not be found on your system.
I did not realize they are not installed by default, sorry for that.
Here is a fixed script.
Hope this one works for you.
@angel1127
The vesafb should work with any vesa 2.0 compliant videocard.
It is only used for the conso
@Shriramana Sharma
In my former post I meant: vga=792 uses 24-bpp.
So try vga=791 and please see if this new script fixes the cpio error you had.
** Attachment added: "Script to fix gutsy initrd.img to load vesafb
unconditionally #4"
http://launchpadlibrarian.net/10301766/fix-gutsy-initramfs
ou.
Server: kubrick.freenode.net
Channel: #ubuntu
Nick: interbird
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
u
@Shriramana Sharma
You are right, I was wondering why pushd and popd were not found.
I changed the symlink from dash to bash on my system months ago due to more
strange behaviour from dash.
(I upgraded feisty to gutsy which left my symlink to bash untouched)
I too quickly tried to determine which
@angel1127
Vesa is a videocard independant standard to access higher resolutions than
standard vga (640x480x16).
Almost any recent videocard supports this.
You can read what vesa is here:
http://en.wikipedia.org/wiki/VESA_BIOS_Extensions
$kernel-source/Documentation/fb/vesafb.txt is correct in t
@Goodness
Can you send your initrd image to the email-address in the script?
I'll try it on my system to see what's wrong with it.
Please also include the out put of the lspci -v and lmod commands.
*Before you modprobe vesafb; thus when your Ctrl-Alt-Fn terminals are blank*
You can use: lspci -v >
@strabes
At boot-time the splash-screen takes it's resolution from /etc/usplash.conf,
*which is in the initramfs image* !
At boot the root-filesystem is changed from the initramfs to the real-root.
Your system is on the real-root.
On shutdown, the splash-screen takes it's resolution, again, from
errata:
#1
s/Which is different/Which could be different/
#2
What's a link to a link without a link...
http://en.wikipedia.org/wiki/VESA_BIOS_Extensions#Linux_video_mode_numbers
(thx, caravel)
--
tty[1-6] are active but display nothing in Gutsy
https://bugs.launchpad.net/bugs/129910
You receiv
@strabes
To extract the usplash.conf file from the initramfs, follow these steps:
1. open a terminal
2. run this command: mkdir tmp; cd tmp; gzip -cd /boot/initrd.img-$(uname -r) |
cpio -im; cp -a etc/usplash.conf ..; cd ..; rm -rf tmp
(best is to paste this line in your terminal, if you retype i
ed in *two*
/etc/config-files.
The third culprit is that apparmor does not correctly reloads changes by a
simple restart.
Access on my ~/pdfout123 is: 755 (did not try other settings but logic
suggests 700 should work too.
I hope this works as good for you as it did for me,
Cheers,
Inte
90 matches
Mail list logo
