SliTaz Forum
You are not logged in.
Hi,
I tested latest 4.0-RC2-base on a laptop Lenovo T61p.
Something is wrong with usb. Every minute, it automatically disconnects and reconnects the usb mouse.
Steps to reproduce:
- start laptop with 4.0-RC2 live cd,
- select base live,
- select language and keyboard,
- login as tux or root (both behaves the same),
- wait one or two minutes and you'll get this:
root@slitaz:# usb 2-1.1: USB disconnect, address8
USB 2-1.1: new low speed USB device using ehci_hcd and address 9
input: Logitech USB Optical Mouse as /devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1.1/2-1.1:1.a/input/input12 generic-usb 0003:0460:C05A.0009: input: USB HID V1.11 Mouse [Logitech USB Optical Mouse] on usb-0000:00:1d.7-1.1/input 0
And every minutes it fills my screen with that message... This does not happen with Slitaz 3.
Cheers.
Offline
My Wireless is not engaged at boot. It is necessary to manually 'start' wifi. Checked /etc/ network.config and it appears to be triggered 'yes' to start at bootup.
Installed RC2 to eeePC701 and have just completed latest upgrade.
Offline
@plumtreed
Two settings are required in /etc/network.conf to bring up wireless network adapter by /etc/init.d/network.sh on boot:
# Set default interface.
INTERFACE="wlan0"
# Wifi connection.
# Enable/disable wireless connection at boot time.
WIFI="yes"
Default interface is ra0 on some ralink wireless chipset adapters.
If this does not fix the problem:
Before you restart network:
ifconfig
Is your wireless adapter listed?
What kind of install, frugal with persistance or full.
Offline
I guess some more feedback is necessary. At least for me RC2 means trouble, as I am not able to get a working Xscreen straight away.
For the developers who can interprete these data here the Xorg.0.log:
http://pastebin.com/V8ypxcyN
As a workaround I installed the non-free nvidia-driver and now it works - plus: it looks really nice! ;-)
Look here:
http://forum.slitaz.org/topic/nvidia-non-free-drivers/page/3
But in this form Slitaz 4.0 is not kind of ,,ready".
And, developers, not urgent, but to remember:
,,My personal status quo: at least I know and experienced that this nvidia-thing is solvable under Slitaz. No I have three issues left:
- to install fluxbox - done, no problem. But to use the style MerleKay (does not work yet)
- to use Kompozer in Slitaz (3.0 works, cooking not and 4.0 not)
- to wait for a texlive-tazpkg package or something that can give the desired LaTeX-,,motor" under Slitaz"
Offline
@mojo
I can connect manually and I have changed both 'wifi=yes' and to 'wlan0' in /etc/network.conf...............this is a full install of 4.0RC2 (and udated)
....anything else need to be changed?
I thought this might be a prob with 4.0RC2
Offline
@mojo
I just noticed you indicated '/etc/init.d/network.conf' ????.........s/b /etc/network.conf?
Offline
@plumtreed You need glasses. Mojo said /etc/network.conf and /etc/init.d/network.sh
Offline
This morning I tried again to boot the rc2-Live-CD, all options, using both the nomodeset mode and trying it without this command line addition. Everything failed:
[ 213.689] (WW) xf86OpenConsole: setpgid failed: Operation not permitted
[ 213.691] (EE) NV: The PCI device 0x10de016a (GeForce 7100 GS) at 05@00:00:0 has a kernel module claiming it.
[ 213.691] (EE) NV: This driver cannot operate until it has been unloaded.
[ 213.691] (EE) No devices detected.
[ 213.691]
Fatal server error:
[ 213.691] no screens found
The 4.0-devel -variant works straight in case the nomodeset option is used.
It has
xorg-server 1.9.5 x-window
xorg-xf86-input-evdev 2.6.0 x-window
xorg-xf86-video-ati 6.14.1 x-window
xorg-xf86-video-geode 2.11.11 x-window
xorg-xf86-video-intel 2.15.0 x-window
xorg-xf86-video-nv 2.1.18 x-window
xorg-xf86-video-vesa 2.3.0 x-window
So my result is: on this particular machine the present RC2 is not useable. Unless, yes, one installs the proprietary nvidia driver.
Offline
@trixar
Nice of u to set me straight in such a thoughtful way.........and I hadn't even had a beer.........but my ability to read doesn't change things, still does configure wireless at boot up.
Offline
@MB, what do you mean by "he 4.0-devel -variant"? could you give the link?
Offline
Hi,
of course I can:
http://is.gd/TazDevISO
In addition please read this text (which repeats the link):
http://forum.slitaz.org/topic/40-rc1-crashing-on-boot-up-with-kernel-panic-help#post-6722
Plus: this one from @gibor works nice as well http://www.freefilehosting.net/slitaz-40-rc2-xvesa_1
- hopefully it brings help into this Xscreen jungle! ;-)
Plus: I checked my memory - in January I obtained a cooking-vesa-version where one has only xorg-server-light and xorg-xf86-video-vesa and this version booted into an Xscreen with ease, got the right screen resolution automatically.
(Personally I am no fan of proprietary nvidia cards - but I => must be sure that anybody to whome I give a Slitaz is able to boot to an Xscreen without any trouble.
Offline
@plumtreed Actually your ability read really does come into play here. If you bothered to check, /etc/init.d/network.sh is the bash script used at boot to configure network and wifi connections. While it may read it's configuration options from /etc/network.conf it's not the same thing. So to make is simple for you to grasp: it's the place you want to check to fix your problem.
Offline
Problem to run SliTaz RC2 from LiveCD
On an old Pentium IV 1.5GHz 512 M RAM / nVidia GeForce2 MX200 VGA controller
- base and justx = OK
- gtkonly = OK till the keyboard configuration box then the monitor displays OUT OF RANGE and less than 1 sec. later desktop is displayed in 800x600 resolution
- core = OK till keyboard configuration and then the monitor displays OUT OF RANGE ; I have to reset to restart the computer
The stable 3.0 xorg run perfectly well on it in 1024x768.
On a FUJITSU SIEMENS ESPRIMO MOBILE (2x Intel core2 duo CPU P8600 2,4GHz / display controller Intel Mobile 4 series chipset)
- base, justx and core = OK
- gtkonly -> black screen with two low lighted cursors in the top of the screen; this is exactly the problem I had with the 3.0 xorg stable (xvesa was OK) on this machine
Not really a problem because I use the core option but I don't understand why this one is running well...
Bug (?) : during boot, if I clik on the [Cancel] button in the Language configuration box, PC blocks with a black screen. I
need to reboot [Ctrl]+[Alt]+[Esc] to restart the computer.
Congratulations to SliTaz Team for this new release that brought solutions to problems I meat on the FUJITSU machine. I hope I can install it on my P IV 1.5.
Ceel
Offline
how you start slitaz in xvesa mode?
Offline
@sino93
The official slitaz-4.0 releases have xorg-server only, no xvesa.
Offline
Slitaz-4 RC2 update
Gaining confidence from the USB version of Core Live I have now replaced Slitaz3 with 4RC2 full install of Core Live on my HD. An initial prblem wrongly attributed to the OS was traced to a dodgy HD.Everything is working as it should .Midori is working with flash perfectly as is the HP f2280 all in one printer. I am however having difficulty installing Canon 670U scanner although discovered by lsusb..Neither xsane nor simple scan(converted from a deb package) discover the scanner.BTW it is working perfectly under fedora16.
Thinking aloud here. I am wondering if on initial install after selection of language all references to other language packs could be dropped?
Symbolic embracing of the Spider!
Offline
................feedback was requested and I provide some feedback. When booting an OS it would not be unusual to expect it to find and activate a wireless connection on boot-up. This expectation would not include the need for intervention on each occasion. I suggest that this may be a 'bug' worth consideration.
I am using 4.0RC2, installed and recently updated, on a eeePC701SDX. The wireless connection can be made manually by reference to SliazPanel.
Offline
Finding any connection on boot is good hardware analysis.
Activating could be extremely bad security. I prefer being asked.
Offline
I've got a few observations, comments and questions regarding Slitaz 4.0. For my tests I have used all four slitaz-core-4in1 rolling versions that have come out since Saturday, each with the "Live" and the "GTKonly" options. The following findings are the same for all four versions ...
Boot Options
What is the difference between "SliTaz Live" and "SliTaz core Live"? I can see that the respective command lines look differently but both options seem to lead to the same result.
GTKonly - Boot-Up
The procedure prompts for the keymap but not for the locale. Shouldn't both prompts be in there? Also, since Slitaz 3.0 times the German keymap appears as "Deutchland". I like such typos because they're funny. But of course it should be "Deutschland" with an "s".
GTKonly - Logout
The panel-menu (LXpanel) and the desktop-menu (Openbox) use different logout boxes. LXpanel uses "desktopbox logout" and Openbox uses "tazbox logout". I think, they should both be the same. As I prefer the "desktopbox logout" box, I've changed the Openbox menu in /tux/.config/openbox/menu.xml accordingly. (In Slitaz Live both are configured to use "tazbox logout". Maybe they should also be changed, as "desktopbox logout" is simpler and requires fewer mouse clicks?)
GTKonly and Live - Panel
I only use the bottom panel, so I've removed the top panel. In the panel preferences advanced settings the options "Make window manager treat the panel as dock" and "Reserve space, and not covered by maximized windows" should be selected by default, as they were in Slitaz 3.0.
GTKonly - Panel applet - Volume control
The applet doesn't appear in the panel because audio is not configured in GTKonly. Maybe the GTKonly version should have audio configured by default? (not sure about this).
GTKonly and Live - Panel applet - Minimize all windows
The applet also applies its tricks on the panel itself. When I click the icon, the panel disappears but the task manager tells me that it's still running. I have no idea how to bring the panel back in this situation. Is this a bug in LXpanel or in the applet?
GTKonly - Video configuration
From answers further up in this thread I have learned how to set up my Nvidia card for X, using the proprietary driver. Great! But just to make sure I'm not overlooking anything, here's what I'm doing after logging in as root ...
tazhw setup nvidia --non-free
... Read license? no
... Accept license? yes
... Configure X ? no (prevents the creation of 55-DeviceTweaks.conf)
rmmod intel_agp
nvidia-xconfig
nano /etc/X11/xorg.conf
check/edit ... driver "nvidia"
nano /etc/X11/xorg.conf.d/60-Device.conf
check/edit ... driver "nvidia"
ls /etc/X11/xorg.conf.d/55-DeviceTweaks.conf
if it exists ... rm -f /etc/X11/xorg.conf.d/55-DeviceTweaks.conf
nano /etc/rcS.conf
check/edit ... LOAD_MODULES="nvidia" (remove intel_agp)
startx
ctrl + backspace
/etc/init.d/slim start
... maybe, if there's something still terribly wrong in all of this, one of the wizards here can let me know? (P.S.: there's an Intel AGP on my motherboard that cannot be disabled in the BIOS. I disable it here but the module keeps creeping back in whenever I use tazhw detect-pci).
GTKonly and Live - Tazlito
And lastly, the only serious problem I have encountered: I cannot make a customized LiveCD with Tazlito. The first part of the procedure, the gzipping, works well. But when Tazlito tries to fetch the kernel from the CD I get this error message ...
> Unable to mount the cdrom to copy the kernel and needed files. When SliTaz is
> running in RAM the kernel and bootloader files are kept on the cdrom. Please
> insert a LiveCD or unmount the current cdrom to let Tazlito handle the media.
... and I have no idea what to do about this. I suspect there's something wrong with the way the CD drive is detected and mounted. The left pane of PCmanFM shows the same CD drive twice, both unmounted. Maybe it's something in fstab? Maybe its something in tazlito.conf? I am grateful for any suggestions.
Offline
P.S.: In Slitaz 3.0, PCmanFM 0.5.2 had some irritating (but not very serious) bugs that are still present in Slitaz 4.0. Since more than 2 years, the developer of PCmanFM has been busy working on a new gvfs-based version of the file manager, which left the still popular 0.5.2 version more or less unmaintained. But there's an alternative called PCmanFM-Mod ...
http://pcmanfm-mod.sourceforge.net/
http://igurublog.wordpress.com/downloads/mod-pcmanfm/
... which is based on the code of the original PCmanFM 0.5.2 but contains a long list of bugfixes and a handful of interesting new features. Apparently the modified FM can be used as a drop-in replacement for the original. Distros like Parted Magic and Austrumi have already adopted PCmanFM-Mod as their default file manager. Arch, Debian, Slackware and others have it in their repositories.
I know that the official release of Slitaz 4.0 is coming closer. Pankso might decide any day now to make the announcement. But if it is not too late for this, maybe PCmanFM-Mod could still make it into the release, either as default FM or as an option in the repository?
Happy Pi Day everybody!
Offline
Addendum to my post abpve:
With hpf2280 printer/scanner turned on simple scan finds the scanner and am able to scan with it. At least the converted package is working!.
Offline
@Darjeeling It's already been considered. PCManFM-Mod is also now known as SpaceFM (as pointed out in the related blog page) - pankso already said he would included it.
Offline
@ Trixar: That's great. I only suggested PCManFM-Mod because it is basically the same as the original but more mature and more bug-free. The integration of PCManFM-Mod in Slitaz would presumably cause no problems at all. SpaceFM is based in parts on PCManFM but otherwise an entirely new development that is still in its early stages. As the Ignorant Guru says in his blog "available for early testing". If SpaceFM becomes the default FM in Slitaz 4.0 and there are issues with it, will there be regular updates in the Slitaz repository? New and untested software like this can turn out to be a heavy burden for the maintainers. On the other hand ... SpaceFM looks very promising and I'd love to try it out.
Offline
@ Darjeeling : well if you're on 4, try it :
#tazpkg get-install spacefm
Offline
**sigh**
Spacefm segfaults when opening a terminal(F4).
Who knows what other bugs lurk within spacefm.
Not what Slitaz 4 needs at this late date.
Offline
[ Generated in 0.018 seconds, 7 queries executed - Memory usage: 1.6 MiB (Peak: 1.77 MiB) ]