SliTaz 4.0-RC1 - Feedback
(69 posts) (33 voices)- Started 13 years ago by pankso
- Latest reply from dracotilla
- This topic is not a support question
-
Ikem
offlineAdministratorFeature request: Enhance the boot menu help -------------------------------------------------------------------------------- I was on the console and struggled at the login. I didn't knew the username/password for user/root. I tried the username "slitaz" with password "slitaz". I needed google to find out the correct username/password. I suggest to show the username/password in the boot menu help.Posted 13 years ago # -
Ikem
offlineAdministratorFeature request: Enable NoHz on demand -------------------------------------------------------------------------------- To switch the CPU to NoHz mode takes 10 seconds. It's a lot faster if I disable them. I know this feature is useful for laptops. No ticks, causes less cpu cycles, causes longer battery time. So I suggest to disable them as default and enable them on demand.Posted 13 years ago # -
Ikem
offlineAdministratorFeature request: Change username from "tux" to "slitaz" -------------------------------------------------------------------------------- I think it's common sense to use the distro name as username. For example: On Linux Mint it is "mint". On Debian it is "debian". So I suggest to change the username to "slitaz".Posted 13 years ago # -
Trixar_za
offlineKey Master@Ikem: And you could put all that in one post?
So let me answer you in order:1. I don't really feel there is a need to localize the boot menu as such, but you're right, it would make it easier to set things at boot. My own solution which I'm pushing is to use English as default since it's the second most understood Language in the world (going on http://www2.ignatius.edu/faculty/turner/languages.htm numbers of combined primary and secondary speaker). Then once booted, it should pop up a box that allows the user to set time and localization to what they want - similar to how Puppy does it. But your way could work too ;)
2 & 4: The majority of SliTaz users are used to tux now. More people would complain about the change if you used your suggestion. I think tux with no password and root with the password root is pretty easy once you know it. If we suddenly changed it and invalidated all the documentation and google info on it, I think we would have a major influx of complaints. Nope, I think this stays as it is.
3. There seems to be two schools on thought with on CPU scaling. Some want it enabled by default and others want it disabled by default. Maybe setting it on demand would be a nice middle ground.
Posted 13 years ago # -
Ikem
offlineAdministrator> And you couldn't put that all in one post? Three small posts are easier to read as one big post. For each post a link is created. That makes it easier to point to them. > 1. I don’t really feel there is a need to localize the boot menu > My own solution which I’m pushing is to use English as default You could say that about the whole system. > Then once booted, it should pop up a box > that allows the user to set time and localization It's about the overall experience. It's just consequent to localize the whole system. From the start, to the shutdown. That makes it more "professional". > 2 & 4: The majority of SliTaz users are used to tux now. > More people would complain about the change I think it would make it easier for new users. And so more attractive for them. -> growing userbase About old users, we need to communicate it clearly. So that they will be "up-to-date". And explain the change, and the possible benefits. > If we suddenly changed it, we invalidated all the documentation The documentation still needs an update. Then we could update this part too. > 3. There seems to be two schools on thought with on CPU scaling. > Maybe setting it on demand would be a nice middle ground. :) My idea is to do that after the boot, with something like: echo "nohz" > /proc/cpuPosted 13 years ago # -
Trixar_za
offlineKey MasterAnd why didn't you use formatting? Are you posting from a mobile phone (I do this sometimes)? Makes it a little hard to read.
In order again:
1: It would only be a nice and neat 'feature' that you would like to see. I'm not even sure we have a German localization for some stuff - nobody really has come forward to do it.2 & 4: And then people would STILL ask why did it change, complain they were never told and stop using SliTaz. Trust me on this. I've was recently forced to changed my domain where I host my SliTaz packages. Even with google pointing to the right site and me countless times telling people where it is and even including it in my nickname here on the forums (just click on it), people STILL ask where it and why it's down. Sometimes even right below the post where I explain where it is. What does that tell you? People won't listen. Even if we put this change in the documentation that's clearly visible on the desktop (and it is in the documentation), people still won't read it even if we made it pop up at boot. You, yourself, are a clear example of this. You see what I'm getting at? Your suggestion would just confuse users MORE and cause MORE complaints. So we'll stick with tux and root as it is ;)
3. I'll forward that suggestion to the developers.
Posted 13 years ago # -
Joe
offlineMemberFeedback from old-guy user messing with v4_cooking on usb. Version 3.0 (not cooking) worked nice, but with limited video on my laptop from hell (Dell Inspiron 1721) and non-working broadcom wireless (did/does not matter yet: old Netgear usb works fine). Everything below is for v4.
1./ v4_RC1 is very nice from cd -- great video at full resolution. VERY quick!
2./ tazusb does not properly install on memory stick. Stick doesn't reboot because rootfs?.gz set is not copied. Rebooted CD and copied them over and system boots, but with no persistence.
"#tazusb writefs /dev/sdb1" makes new file on the usb, but everything is like booting from cd every time except for configs etc in /home/tux.3./ v4 slitaz-cooking-devel.iso with single rootfs.gz almost works: Installed OK on stick and booted, X started with full resolution, but autologin failed and login screen went into X login-screen loop: neither tux nor root/root would work. Rebooted cd, found no tux directory on usb. Copied tux directory over as root, chown -R tux:tux and I'm up and running.
Thank you people for all your good work.
Posted 13 years ago # -
vtailor
offlineMemberI downloaded the latest cooking slitaz to give it a try on my menagerie of test computers.
Observations: The Unetbootin program doesn't work with the slitaz .iso file; the resulting usb flash thumb drive doesn't boot up. If you dd copy the .iso file onto a flash thumb drive, the result does indeed boot up with my supposedly 10 watt Intel 2700MUD computer board, dual atom with gma600 (poulsbo). Video works in vesa mode, really great colors, no sign of a psb_gfx kernel module or egmd driver in your repository. Out of curiosity, I put the flash thumb drive onto an Asus eee box amd 450 atom device, and it flat refused to boot up, no matter what settings I used. Assuming unetbootin works on the Asus, but then boots badly, I see no way to try the new cooking out on an Asus amd 450 setup.
Hint: If the vesa mode you get doesn't match the monitor, switch the monitor from 16:9 mode to 4:3 mode, which should give you round circles with the vesa driver.
The Intel 2700MUD is remarkably fast in psb_gfx plus xf86 fbdev driver mode, given the need to adjust the monitor. Since you use a series 2.6 kernel, you might have some success compiling the emgd (proprietary) video driver available from Intel download, since it provides source code for the similar kernel Fedora 14 video system, as well as compiled rpm packages for Meego.
P. S. The latest open-source AMD nee radeon chips driver code seems to work complete with acceleration, and is only a minor change from the previous iteration of xf86 ati.
Posted 13 years ago # -
vtailor
offlineMemberI found an old unused DVD and copied the iso from my flash thumb drive onto the DVD and booted up the Asus eee box pc with the AMD-450 and the ALC887 sound chip. I know from the Linux 3.2 kernel that alsamixer ought to be enough to find the analog section of the sound chip and set it up to work (an .asoundrc file in /root also helps), and I did exactly that using the latest slitaz, which got me complete silence during flash playback of various streaming video and sound systems. So, the answer is that, unless you have the alsa portion of Linux 3.2, you don't have all the realteck sound chips out there, since there is a slight mistake in the 2 series kernels that prevents all the sound chips from working. You can prove this to yourself by going into Windows 7, which immediately sets up (analog) sound that works, then rebooting into slitaz, which half the Time will grap the device and work without setting it up properly.
P. S. As I pointed out elsewhere, the fglrx driver fails on Ubuntu and slackware and slitaz and other systems as well. The newer open-source xf86 ati driver is very easy to compile and install, and it works extremely well, even providing a streaming video acceleration interface under Linux and handling all the newer AMD cpus, including the E-450 atom.
Posted 13 years ago # -
vtailor
offlineMemberOne more word about the new Intel low-power atom chips with their proprietary graphics: Even in vesa mode, you can see some kind of texturing going on. For example, lines of text outside of X-windows appear rounded when you start up in vga=792 mode. In other words, the vrwhatever graphics subchip does 3dfx even in vesa and fbdev modes. And, with the psb_gfx kernel module running the fbdev video driver, you get a very good combination of speed and 3dfx. You never know, though, someone may actually tweak the last bit out of psb_gfx, or even port the emgd driver so that it comes standard on Linuxes.
Posted 13 years ago # -
Ikem
offlineAdministrator> Trixar_za wrote:
> And why didn't you use formatting?
I used formatting:
http://scn.slitaz.org/groups/devel/forum/topic/slitaz-4-0-rc1-feedback/?topic_page=3#post-6800
Posted 13 years ago # -
Ikem
offlineAdministrator> Trixar_za wrote:
> 2 & 4: Even if we put this change in the documentation
> that's clearly visible on the desktop
> people still won't read it
> You, yourself, are a clear example of this.
I must say, I oversaw the documentation.
I thought it was a regular file. Release Notes or something.
Nevertheless. If I can't login to read the documentation, how do I get the infos to login?
So it must be mentioned before the login.
So in the boot menu help?
Edit: I think an even better place would be "/etc/issue".
Posted 13 years ago # -
Ikem
offlineAdministrator> Trixar_za wrote:
> 3. I'll forward that suggestion to the developers.
I like to mention, the command is meant to be a draft, not an example.
Posted 13 years ago #
Reply »
You must log in to post.
