General TC > Tiny Core Netbooks
TinyCore on a Dell Mini 1011
nitram:
Believe Xvesa is an older graphic standard than Xorg. Lighter to load, tends to be more suited for older hardware. Your netbook should run Xorg just fine, however, if you choose. There are lots of old Xvesa hits on this forum:
https://www.google.ca/search?q=xvesa+site:forum.tinycorelinux.net&sa=X&ved=0CC4QrQIoBDABahUKEwiq7MSggd_IAhXPlogKHbX1Bug&biw=1024&bih=444
You can try a similar site search as linked above but with your specific Dell Mini, it is likely someone has already got a similar system running with TC.
The graphic server needs to be exited before restarting. Modify the .xsession file and reboot, provided you have persistent home backup. Otherwise can also try running 'exittc', select 'exit to prompt', maybe 'killall Xvesa' (confirm via top) then 'startx'.
Blacklist is done through the bootloader, i use Grub2, what's your bootloader?
Why, because someone much smarter than me already figured this out :)
Sorry can't help with keyboard layout/language.
Rich:
Hi emninger
You can't restart X from a terminal. Pressing Ctrl-Alt-Backspace will kill the current instance of X and leave you at the
console. Then enter startx.
Juanito:
--- Quote from: emninger on October 25, 2015, 03:05:07 PM ---No. Definitely it did not. I followed exactly the instrcutions, but wireless is still not working. Is there any toolor "how to" for tinycore how to manage network interfaces and setup?
--- End quote ---
The statement above is not really supported by the statement below ;)
--- Quote ---Where (and why??) do you blacklist ssb and b43?
--- End quote ---
If you don't blacklist the kernel modules mentioned in the info file, re-boot and then try wl-modules-KERNEL, things will not work.
Note that once you've done things as per the info file, you can use the wifi extension to manage wireless connections.
Note also that the broadcom firmware is contained in the driver supplied by the wl-modules-KERNEL extension (so you don't need additional firmware) and your wireless connection will most likely be named "eth1".
Juanito:
--- Quote from: emninger on October 25, 2015, 08:31:27 PM --- i do not really understand how to get to edit the bootloader. I tried tab and e (what i know from lilo and grub) but that does not work. F2 brings me to the bios of the netbook?
--- End quote ---
When you boot, the name of the bootloader - grub, lilo, syslinux, etc - should be displayed at the top of the screen.
The name and location of the bootloader configuration file will depend on which bootloader you have, for example:
/mnt/sdb1/boot/grub/grub.cfg
..and can be edited using, for example:
sudo vi /mnt/sdb1/boot/grub/grub.cfg
emninger:
--- Quote from: Juanito on October 25, 2015, 11:54:35 PM ---
When you boot, the name of the bootloader - grub, lilo, syslinux, etc - should be displayed at the top of the screen.
The name and location of the bootloader configuration file will depend on which bootloader you have, for example:
/mnt/sdb1/boot/grub/grub.cfg
..and can be edited using, for example:
sudo vi /mnt/sdb1/boot/grub/grub.cfg
--- End quote ---
May be it's too fast for my eyes (i presume it's syslinux, since i installed TC for the moment on an usb-stick) ...
So there is no /etc/grub.conf (or lilo.conf of whatelse) which then has to "bless" the the real bootloader.cfg by, eg., update-grub; and you got to edit directly (?)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version