title Tiny Core Linux
kernel (hd0,1)/tinycore/bzImage quiet embed ht=on hpet=disabled quiet tz=PST+8PDT,M3.2.0/2,M11.1.0/2 home=hda2 opt=hda2 norestore nodhcp
initrd (hd0,1)/tinycore/tinycore.gz
iwconfig eth1 essid "mynetworkname" key FDFDFDFD
udhcpc -i eth1
I shutdown the mini9 and upon next boot I have wireless and proper screen resoultion!.....Same for /opt. I will share the current /opt directory for my persistent storage..........What do u use /opt for?
echo num > /sys/class/backlight/acpi_video0/brightness
(where "num" is a value from 0 to 15.)The extension graphics-2.6.29.1 has the intel agp modules.
@Juanitoyes, from the graphics-2.6.29.1-tinycore extension
Thanks for the info. I just modprobed "i915" and "drm" and they appeared (and stayed in subsequent boots). Don't know if they came from an extension or not.
However, still no way to adjust the backlight brightness with TC.
Going to look into the acpi bootcodes when I get the chance. Just need to make "/sys/class/backlight/acpi_video0/brightness" appear.
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not set
..which might influence the use of libsmbios, etc
$ sudo smbios-lcd-brightness --password=xxx -a --value=7
Reading current AC mode setting
current: 3
min: 0
max: 7
Write new AC mode setting
Reading current AC mode setting
current: 7
min: 0
max: 7
Note that the backlight adjustment cannot be set to "auto" for this to work.By the way, when I first attempted acpid, errors appeared stating that a directory and subdirectory didn't exist, and acpid wouldn't run. I had to mkdir the directory and sub-directory to get acpid to run.
In the latest version of the acpid extension, the start-up script should take care of this - could you confirm which version you were using?
root@box:~# acpid -d
acpid: starting up
acpid: opendir(/usr/local/etc/acpi/events): No such file or directory#!/bin/sh
start() {
if [ ! -d /usr/local/etc/acpi/events ]; then
mkdir -p /usr/local/etc/acpi/events
fi
if [ ! -e /var/run/acpid.pid ]; then
/usr/local/sbin/acpid
fi
}
stop() {
killall acpid 2>/dev/null
}
status() {
if [ -e /var/run/acpid.pid ]; then
echo -e "\nacpid is running.\n"
else
echo -e "\nacpid is not running.\n"
fi
}
case $1 in
start) start
;;
stop) stop
;;
status) status
;;
restart) stop; start
;;
*) echo -e "\n$0 [start|stop|restart|status]\n"
;;
esac
updated acpid posted
# cat /proc/acpi/video/GFX0/LCD/brightness
levels: 25 30 35 ... 90 95 100
current: 40
# echo 25 > /proc/acpi/video/GFX0/LCD/brightness
(it changes)$ ossmix jack.int-speaker.mute ON
(Use the GUI 'ossxmix' not the CLI 'ossmix' to get a sense of the# grub --device-map /tmp/devmap
$ sudo su
# fsck.extM /dev/sdX1
# mount /mnt/sdX1
# cd /mnt/sdX1/boot/grub
# cp -p /usr/lib/grub/i386-pc/* .
# cd
# sync ; sync
# umount /mnt/sdX1
Anything seen in capital letters is a replaceable (single-# echo "(hd0) /dev/sdX" > /tmp/devmap
# exit
$ sudo su
# grub --device-map /tmp/devmap
> root (hd0,Y)
> setup (hd0)
> quit
> exit
$ cat /etc/X11/xorg.conf | egrep Opt | egrep "Im|mi|Bu"
Option "Protocol" "ImPS/2"
Option "Device" "/dev/input/mice"
Option "Buttons" "5"
The options helped wake up the third mouse button, instead of# /sbin/loadkmap < /opt/private/dvorak-mine.kmap
I brought my kmap over from an earlier tc system (see below). You$ cat /home/tc/.xsession | grep vo
/usr/bin/xmodmap /home/tc/dvorak.xmodmap
which is also homebrew. The combination provides Dvorak$ xrandr --output VGA --mode 1024x768
$ xrandr --output LVDS --mode 1024x600
$ xrandr --output LVDS --pos 0x300 (offsets display 300px vert.)
$ xrandr --output LVDS --pos 0x0 (mirror)
Can't get beyond --pos 0x425 or so without artifacts (should$ xset s 900 (900 second timeout)
This seems to reset itself on a whim, so I loop it in a script:#!/bin/sh
for i in 1 1 1 1 1 \
1 1 1 1 1 1 1 1 \
1 1 1
do
xset s 900
sleep 912
done
(change the loop to get it to run a very long time).# wpa_supplicant \
-BWdddd \
-D wext \
-i eth1 \
-c /etc/wpa_supplicant.conf
That's called after a modprobe of 'wl' (if needed; not required# wpa_cli \
-a /path/to/any/shell/script-of-mine.sh \
>/dev/null 2>&1 &
# wpa_cli status
# cat script-of-mine.sh
#!/bin/sh
# does absolutely nothing of use; dummy script for wpa_cli
echo
exit 0
# cat /etc/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
ap_scan=2
network={
ssid="corytine"
scan_ssid=0
proto=WPA RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP
#psk="some-funky-wpa-seekrit-passphrase-enlightenment-40327"
psk=700521cc0bea96fef88872e7757e7c3afb46a1b7ace09a7422b13e9439c9ab1f
}
Seems to default to CCMP when forced in the wireless# wpa_cli
Selected interface 'eth1'
Interactive mode
> status
bssid=00:24:b2:0a:bc:23
ssid=corytine
id=0
pairwise_cipher=CCMP
group_cipher=CCMP
key_mgmt=WPA2-PSK
wpa_state=COMPLETED
ip_address=192.168.1.38
> quit
The above says it is in CCMP rather than the inferior TKIP$ wpa_passphrase corytine
# reading passphrase from stdin
some-funky-wpa-seekrit-passphrase-enlightenment-40327
network={
ssid="corytine"
#psk="some-funky-wpa-seekrit-passphrase-enlightenment-40327"
psk=700521cc0bea96fef88872e7757e7c3afb46a1b7ace09a7422b13e9439c9ab1f
}
# udhcpc -b -i eth1 # wifi
cpanel defaults to eth0.# iwconfig eth1 essid "chauncey"
# udhcpc -b -i eth1 # wifi
# /usr/bin/aircraft-manager-util AC_CHARGING off (or on).
Turning AC_CHARGING off
$ md5sum *
a6a9dbd8e1dfe2ad799640d8cbdf5ba6 dvorak-kmap.txt
60c284c353ebd602e782fcac08056025 dvorak.kmap
97d2404eb48f188364a40354b0de21c9 xorg.conf
I have been playing around with the brightness keys during
boot-up, and the brightness can sometimes be adjusted with
the keys, when viewing the grub menu. It doesn't always work.
However, the brightness keys have no effect when TC is running.
Install Grub 2.0, which is consistently responsive to the
Dell Mini 9 brightness hotkeys (Fn 9, Fn 0) here (ymmv).
This should be a clue how to do it without specific acpi
support; Linux hasn't booted yet.
At the SSD password prompt, the brightness hotkeys
are also responsive. The 8GB SSD from Dell accepts
a password; the 4GB SSD does not seem to (therefore no
prompt, so this may fail with a 4GB SSD installed).
As Grub hasn't booted yet, looks like the SSD password
prompt video environment is not harmed by subsequently
booting Grub 2.0; whereas booting Grub 0.97 does seem to
trash the state of the machine, to the extent that the
brightness keys are sometimes unresponsive.
$ xrandr --output LVDS --off # turns off LVDS
$ xrandr --output LVDS --mode 1024x600 # turns on LVDS
... xrandr canHave you tried running extended period with '$ xrandr --output LVDS --off'? Because I tried using this but the VGA screen freezes after some minutes. I have to have LVDS on.
shut off the LVDS. You can toggle this as often as you wish.
Therefore this is the most dynamic method I can demonstrate,
with TC 2.7 running:Code: [Select]$ xrandr --output LVDS --off # turns off LVDS
$ xrandr --output LVDS --mode 1024x600 # turns on LVDS
Have you tried running extended period with
$ xrandr --output LVDS --off ?
Because I tried using this but the VGA screen freezes after
some minutes. I have to have LVDS on.
In the meantime, if anyone has a clue as to why the /sys/class/backlight directory doesn't appear, please chime in.
sudo modprobe generic_bl
orsudo modprobe backlight
default 0
timeout 0
color cyan/blue white/blue
title Tiny Core Linux 3.0
kernel (hd0,1)/boot/boot/bzImage quiet embed ht=on hpet=disabled blacklist=ssb blacklist=b43 tce=hda2 home=hda2 opt=hda2 nodhcp norestore restore=hda2
initrd (hd0,1)/boot/boot/tinycore.gz
$ sudo iwconfig eth1 essid "essid"
$ sudo iwconfig eth1 key restricted 12:34:56:78:9A:BC:DE:F0:12:34:56:78:9A
$ sudo udhcpc -b -i eth1
..or similar (this example is for wep)?
"eth1 Failed to read scan data : Invalid argument". The same message appears after "iwlist scanning".The same message would appear after "iwlist s" as well :P
sudo ifconfig eth1 up
and/orsudo iwconfig eth1 mode managed
first, depending on particular driver.
Just curious, why does one now have to blacklist the Broadcom modules and manually start the wireless interface? -- I don't recall having to make these moves on earlier versions of TC.
You're not blacklisting the broadcom module, you're blacklisting the reverse engineered in-kernel module (b43) - wl is the broadcom module.
As mentioned elsewhere, you'd possibly get more functionality out of using b43 and firmware rather than wl.
Thank you for the suggestion. I might try it, but installing the firmware seems a little involved, and there are a few variables which are unknown to me.
It looks like I need to compile version 013 of b43-fwcutter. I don't think that I can use b43-fwcutter.tcz in the repository, because it is version 012. So, apparently I must have a compiler (which I guess means installing gcc.tcz) and headers for libc. Which extension contains the libc headers?
These seem to be the instructions for installing the firmware for my wireless card with kernel 2.6.33.3: http://linuxwireless.org/en/users/Drivers/b43#fw-b43-lp (http://linuxwireless.org/en/users/Drivers/b43#fw-b43-lp) However, in TC, to which directory do I install the firmware? TC hasn't a "/lib/firmware" directory nor a "/usr/local/lib/firmware." I did find "/sys/firmware."
You might temporarily want to load the firmware-*-tinycore.tcz extension to get the path structure, or alternatively just look at firmware-*-tinycore.tcz.files
To compile, you just need to use the appbrowser to download/install compiletc - this will get all of the required extensions for you.
You can create /lib/firmware, copy the firmware files to there and make your own extension out of it. /usr/local/lib/firmware would probably also work, but I didn't try this myself.
* is meant as wildcard for the variable kernel version number ;)QuoteYou might temporarily want to load the firmware-*-tinycore.tcz extension to get the path structure, or alternatively just look at firmware-*-tinycore.tcz.files
Thanks. I can't seem to find any "firmware-*-tinycore.tcz" extensions
* is meant as wildcard for the variable kernel version number
Okay. So, if I can make an extension for the new firmware files, I would need to install it as onboot to keep it automatically persistent?