Italian translation and installation issues

D

diaolin

Renowned Member
Jul 7, 2008
332
8
83
Trentino Italy
First: italian


  • This is not a bug, only a request to clarify
  • The button text "Shutdown" has been translated into "Spegni"and this is OK
  • The button text "Stop" has been translated into "Stop", :( i think it's more comfortable a translation like "Togli corrente" or whatever similar. This only do differentiate the two actions.
  • Many thanks to Angelo Volpato for the translation
Second: installation on new hardware, very new hardware

  1. on a new (laptop) Turion amd64 the screen freezes after boot during installation
  2. changing the boot parameters in this manner :
    linux26 vesa video=vesafb nosplash it works OK
If anyone needs this info.... It's the vesa video=vesafb the real problem.

Anyway, resolved. It installs ok

Tx, Diaolin
 
diaolin said:
changing the boot parameters in this manner :


  1. linux26 vesa video=vesafb nosplash it works OK
Click to expand...

interesting - what does boot parameter 'vesa'? I found no info about that.

by default we use:

linux26 vga=791 video=vesa:ywrap,mtrr splash=silent

does it work with:

linux26 vga=791 video=vesa:ywrap,mtrr nosplash

just curious. Maybe it should be 'video=vesafb:ywrap,mtrr' anyways?

- Dietmar
 
vesa as mode (kernel parameter)

A common mistake is that folks use a wrong parameter format when using the driver compiled into the kernel. Please note: If compiled into the kernel, the parameter format is video=sisfb:mode:none or video=sisfb:mode:1024x768x16
(or whatever mode you want to use, alternatively using any other format
described above or the vesa keyword instead of mode). If compiled as a module,
the parameter format reads mode=none or mode=1024x768x16 (or whatever mode you
want to use). Using a "=" for a ":" (and vice versa) is a huge difference!
Additionally: If you give more than one argument to the in-kernel sisfb, the
arguments are separated with ",". For example:

video=sisfb:mode:1024x768x16,rate:75,mem:12288
 
First, we use the vesa fb by default (vga=791)

diaolin said:
It let's the kernel use vesa driver.
Click to expand...

There is no 'vesa' boot parameter in the docs (Documentation/kernel-parameters.txt). Where did you find that?

Also, 'nosplash' seems to have no effect at all.

So what is the effect of your changed boot parameters?

- Dietmar
 
diaolin said:
The installer works without hanging.
Withouth the parameter it does "black screen" and stop.
Diaolin
Click to expand...

Sure, but I read through the kernel sources and your changes has no effect IMO.

And if I use what you recommend, it does not switch to FB mode at all.

linux26 vesa video=vesafb nosplash

(above does not start a vesa FB and so the installer fails)

so I am confused.

- Dietmar
 
I didn't know how to installat?
​
 
Last edited by a moderator:
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back