So I'm posting using Slitaz-4-0-rc1 running inside VirtualBox in Windows Vista, first boot I had the kernel memory error, I used the boot command codes:
core-basic kmap=us lang=en_US
It looks like it's running at 800x600 though ...
So I'm posting using Slitaz-4-0-rc1 running inside VirtualBox in Windows Vista, first boot I had the kernel memory error, I used the boot command codes:
core-basic kmap=us lang=en_US
It looks like it's running at 800x600 though ...
just tried 4.0, some comments.
by chance i could easily go back to the previous interface, not a big fan of the changes which i understand have been on the way for a while.
Saw the web interface, nice for package installation, not so nice for wifi (compared to the interface that was available with 3.0). would prefer a button to run the previous interface rather than editing a file !
Wifi VERY unstable, constantly disconnecting, which makes it viruatlly unusable here.
I do have some unstability with 3.0 but not at this scale...
I found what is below, without being sure this is useful (When the network seems to be disconnect i have to disconnect then reconnect)
root@slitaz:~# dmesg
02 (try 1)
wlan0: direct probe to e6:a6:53:55:50:02 (try 2)
wlan0: direct probe to e6:a6:53:55:50:02 (try 3)
wlan0: direct probe to e6:a6:53:55:50:02 timed out
eth0: Media Link Off
eth0: Media Link Off
wlan0: authenticate with e6:a6:53:55:50:02 (try 1)
wlan0: authenticated
wlan0: associate with e6:a6:53:55:50:02 (try 1)
wlan0: RX AssocResp from e6:a6:53:55:50:02 (capab=0x401 status=0 aid=1)
wlan0: associated
phy0 -> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 0.
Please file bug report to http://rt2x00.serialmonkey.com.
ieee80211 phy0: wlan0: No probe response from AP e6:a6:53:55:50:02 after 500ms, disconnecting.
cfg80211: Calling CRDA to update world regulatory domain
wlan0: direct probe to e6:a6:53:55:50:00 (try 1)
wlan0: direct probe to e6:a6:53:55:50:00 (try 2)
wlan0: direct probe to e6:a6:53:55:50:00 (try 3)
wlan0: direct probe to e6:a6:53:55:50:00 timed out
wlan0: direct probe to e6:a6:53:55:50:00 (try 1)
wlan0: direct probe to e6:a6:53:55:50:00 (try 2)
wlan0: direct probe to e6:a6:53:55:50:00 (try 3)
Parallel port: I am still looking on how to get a parrallel port scanner be recognised by Slitaz: still no /dev/parport -> how should that work?
Thanks
Really really huge thanks to everyone who helped on this RC1. We need you to make SliTaz always better :-)
- Christophe
just installed RC 1 but I can't get online the wifi box has no place to install firmware. Any thoughts?
Installed RC2, all goes well and able to burn CD isos and liveUSB but while wireless on my eeePC701 RTL8187sle worked ok on RC1, I couldn't get it going on RC2.
It finds it and I can put in my key but it only sends, doesn't receive. Any hints happily accepted.
PS........... 4RC2 looks sophisticated and very professional
I think my issue with wireless is that I need to install ipw2200 firmware and a orinico_cs module. Slitaz 3.0 allows me to do that, but RC1 doesn't appear to have that option.
I think my issue with ethernet connection is that Slitaz sees my comp as 192.168.0.2 while in fact it should be 192.168.1.2 since the gateway is 192.168.1.1
Editing the file is to no avail since with the Live-CD there's no point logging out or rebooting to enable changes.
@eeried
Come on: then just make a small frugal hdd-install on some ext3-partition. Edit the rcS-file, as far as I understand it, and set the details right. I vaguely remember I had a similar issure one year before, but this machine I do not have here.
The procedure: boot with the CD, copy the content of the CD to the hard-drive directory, name it ,,slitaz". Then set up the right details while you are booted. Then use ,,tazusb writefs". After that you delete the rootfs.gz-file in ,,slitaz" and replace it with /rootfs.gz.
Add the right GRUB config expression into the menu.lst of /boot/grub:
root (hd0,1) - or what you have
kernel /slitaz/boot/bzImage root=/dev/ram0 rw nomodeset
initrd /slitaz/boot/rootfs.gz
boot
If there is a problem when you use it look into /var/log/messages.
Hello!
eeried, you don't need to log out or reboot to enable changes. Just edit /etc/network.conf (with nano or leafpad) and then "/etc/init.d/network.sh restart". That should work.
Hope it helps!
You must log in to post.