Tiny Core Linux
Tiny Core Extensions => TCE Talk => Topic started by: bitweisor on July 18, 2015, 12:15:12 PM
-
O.k. So I have downloaded and installed Nvidia driver 304.125. I did use Rich's scripts create-raw and create package, and both seemed to have worked. I am however having problems with the driver and I'm not sure if it's an Xorg problem, xorg.config, or a problem with the build.
dmesg gives me this:
ACPI Warning: SystemIO range 0x00000c00-0x00000c1f conflicts with OpRegion 0x00000c00-0x00000c1f (\_SB_.PCI0.SBRG.SMRG) (20140424/utaddress-258)
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Linux agpgart interface v0.103
agpgart-sis 0000:00:00.0: SiS chipset [1039/0740]
agpgart-sis 0000:00:00.0: AGP aperture is 64M @ 0xd0000000
[drm] Initialized drm 1.1.0 20060810
nvidia: module license 'NVIDIA' taints kernel.
Disabling lock debugging due to kernel taint
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11
vgaarb: device changed decodes: PCI:0000:00:09.0,olddecodes=io+mem,decodes=none:owns=none
[drm] Initialized nvidia-drm 0.0.0 20140818 for 0000:00:09.0 on minor 0
NVRM: loading NVIDIA UNIX x86 Kernel Module 304.125 Mon Dec 1 19:55:52 PST 2014
and sudo modprobe nvidia reports no errors.
when I run nvidia-settings I get this message:
You do not appear to be using the NVIDIA X driver. Please edit your X configuration file (just run `nvidia-xconfig` as root), and restart the X server.
I have run nvidia-xconfig as root, and have not improved my situation.
Here is my xorg.config:
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 304.125 (buildmeister@swio-display-x86-rhel47-08) Mon Dec 1 21:14:12 PST 2014
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection
Section "Files"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
EndSubSection
EndSection
and my onboot.lst:
nano.tcz
firefox-official.tcz
xfe.tcz
Xorg-7.7.tcz
graphics-3.16.6-tinycore.tcz
nvidia-304.125-3.16.6-tinycore.tcz
Am I forgetting something?
-
For me, it was needed to delete /usr/local/lib/*tls*.* .
Also, you might need to run this command while not running X.
sudo nvidia-xconfig --mode=1280x1024 --force-generate --virtual=1280x1024
Substitute 1280x1024 with whatever screen resolution works with your display.
-
Thanks for the quick response Misalf.
I ran the nvidia-xconfig and updated my xorg.conf:
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 304.125 (buildmeister@swio-display-x86-rhel47-08) Mon Dec 1 21:14:12 PST 2014
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection
Section "Files"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Virtual 800 600
Depth 24
Modes "800x600"
EndSubSection
EndSection
But I'm not able to locate /usr/local/lib/*tls*.* . It's not there.
Still no joy.
-
Try to confirm which driver is utilized:
lspci -v
Confirm nvidia is loaded and installed:
tce-status -i | grep nvidia
-
Sorry, should be /usr/lib/libnvidia-tls.so.304.125 which I have just renamed in my extension.
There is also /usr/lib/tls/libnvidia-tls.so.304.125 but you don't need to touch this one.
I wonder if you need Xorg-7.7-3d.tcz .
-
Misalf,
Sorry, should be /usr/lib/libnvidia-tls.so.304.125 which I have just renamed in my extension.
There is also /usr/lib/tls/libnvidia-tls.so.304.125 but you don't need to touch this one.
I wonder if you need Xorg-7.7-3d.tcz .
I do have the extension at /usr/lib/tls/libnvidia-tls.so.304.125, and also
in /var/tmp/tcloop/nvidia-304.125-3.16.6-tinycore/usr/lib/tls, but not in /usr/lib/.
Initially I was using Xorg-7.7-3d.tcz, but I was concerned It could be the culprit so I went with Xorg-7.7.tcz
nitram,
Try to confirm which driver is utilized:
lspci -v
Confirm nvidia is loaded and installed:
tce-status -i | grep nvidia
It looks like the nvidia package is loaded.
tc@box:~$ tce-status -i|grep nvidia
nvidia-304.125-3.16.6-tinycore
tc@box:~$ lspci -v
00:09.0 VGA compatible controller: NVIDIA Corporation NV44A [GeForce 6200] (rev a1) (prog-if 00 [VGA controller])
Subsystem: eVga.com. Corp. Device b399
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 11
Memory at cf000000 (32-bit, non-prefetchable) [size=16M]
Memory at b0000000 (32-bit, prefetchable) [size=256M]
Memory at ce000000 (32-bit, non-prefetchable) [size=16M]
Expansion ROM at cdfe0000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: nvidia
,and Kernel driver in use is nvidia, yet I still have a problem with nvidia-settings.
Glxgears does not load.
-
Try adding this to your xorg.conf:
Section "DRI"
Mode 0666
EndSection
-
glxgears is not part of Tiny Core base install, you need to install it seperately. Did not see it in your onboot.lst:
tce-load -wi glxgears
Have you tried the vesa driver, maybe it gives good enough performance, example:
xf86-video-vesa.tcz
-
glxgears is in xdemos.tcz.
-
nitram,
glxgears is not part of Tiny Core base install, you need to install it seperately. Did not see it in your onboot.lst:
tce-load -wi glxgears
Have you tried the vesa driver, maybe it gives good enough performance, example:
xf86-video-vesa.tcz
I'd like to use the proprietary driver if it's at all faster at 3d rendering. I'm trying to set up a CNC contoler, and without this card's native capabilities, real time visualization is lagging. This card running under XP is adequate for visualization, it's just that Xp is just not that great as a controller. Tiny Core is so much better. Particularly on an older machine like I have here. The bottom line is that I know the card can do what I want, I just need to get it working with Tiny Core. It'd be the perfect "appliance machine" type setup. (By the way, LinuxCNC won't work as I'm using an arduino/gshield setup).
I did have glxgears installed ondemand (I don't know if that's a problem.), so I just moved it to onboot. Now I get this:
tc@box:~$ tce-load -i /mnt/sda1/tce/optional/glxgears.tcz
glxgears is already installed!
tc@box:~$ glxgears
Xlib: extension "GLX" missing on display ":0.0".
Error: couldn't get an RGB, Double-buffered visual
-
Don't know if i can help, but here's some info. The TC 6 32-bit repository has two glxgears extensions:
1. glxgears.tcz:
v10.4.4
info xorg x 3d test
binaries glxgears and glxinfo
2. xdemos.tcz:
v9.1
info x xorg OpenGL demos
binaries glxinfo and glxgears
Maybe try them both. Maybe run 'glxinfo' to see if it's useful.
-
What does xorg.log say regarding NVIDIA
Sent from my iPhone using Tapatalk
-
Xorg.log might show the reason
Sent from my iPhone using Tapatalk
-
I hadn't realised that glxgears was in xdemos when the x86 Xorg-7.7 was updated recently and hence placed glxgears in an extension of the same name.
If you have the latest version of the Xorg-7.7 extension, you need to use glxgears and not xdemos.
-
Xorg.log might show the reason
I did a search for Xorg.log, log and Xorg and can't find the log files.
Is this correct for Xorg?
tc@box:~$ tce-status -i | grep Xorg
Xorg-7.7
Xorg-7.7-3d
Xorg-7.7-bin
Xorg-7.7-lib
Xorg-fonts
tc@box:~$
And my current onboot.lst:
nano.tcz
firefox-official.tcz
xfe.tcz
graphics-3.16.6-tinycore.tcz
nvidia-304.125-3.16.6-tinycore.tcz
pci-utils.tcz
Xorg-7.7-3d.tcz
I hadn't realised that glxgears was in xdemos when the x86 Xorg-7.7 was updated recently and hence placed glxgears in an extension of the same name.
If you have the latest version of the Xorg-7.7 extension, you need to use glxgears and not xdemos.
I do have glxgears and not xdemos.
Maybe run 'glxinfo' to see if it's useful.
tc@box:~$ glxinfo
name of display: :0.0
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Error: couldn't find RGB GLX visual or fbconfig
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Something to do with X?
-
The screen resolution in xorg.conf is set for 800x600 but my actual resolution right now is 1024x768.
tc@box:~$ xrandr
SZ: Pixels Physical Refresh
0 320 x 200 ( 347mm x 260mm ) 0
1 640 x 480 ( 347mm x 260mm ) 0
2 800 x 600 ( 347mm x 260mm ) 0
*3 1024 x 768 ( 347mm x 260mm ) *0
4 1280 x 1024 ( 347mm x 260mm ) 0
5 320 x 400 ( 347mm x 260mm ) 0
6 320 x 240 ( 347mm x 260mm ) 0
7 640 x 400 ( 347mm x 260mm ) 0
8 2048 x 1536 ( 347mm x 260mm ) 0
Here is my current xorg.conf:
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 304.125 (buildmeister@swio-display-x86-rhel47-08) Mon Dec 1 21:14:12 PST 2014
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection
Section "Files"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
EndSection
Section "Module"
Load "glx"
EndSection
Section "DRI"
Mode 0666
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Virtual 800 600
Depth 24
Modes "800x600"
EndSubSection
EndSection
-
Hi bitweisor
I ran the nvidia-xconfig and updated my xorg.conf:
If I remember correctly, that creates the new xorg.conf file in your home directory. Did you remember to copy it to your
/etc/X11/ directory? You also need to add a line that says:
etc/X11
to your /opt/.filetool.lst file so it gets backed up.
I did a search for Xorg.log, log and Xorg and can't find the log files.
Try:
/var/log/Xorg.0.log
-
If I remember correctly, that creates the new xorg.conf file in your home directory. Did you remember to copy it to your /etc/X11/ directory?
Hi Rich,
When I run nvidia-xconfig it creates the file in my X11 directory, so all I had to do was include /etc/X11 in my /opt/filetool.lst.
Here it is:
opt
home
etc/X11/
No Xorg.0.log:
tc@box:/var/log$ ls -a
./ ../ autologin wtmp
-
What gives
cat /etc/sysconfig/Xserver
and
cat ~/.xsession
?
-
What gives
cat /etc/sysconfig/Xserver
and
cat ~/.xsession
?
Hi Misalf,
I guess this explains it, but what to do?
tc@box:~$ cat /etc/sysconfig/Xserver
Xvesa
tc@box:~$ cat ~/.xsession
Xvesa -br -screen 1024x768x32 -shadow -2button -mouse /dev/input/mice,5 -nolisten tcp -I >/dev/null 2>&1 &
export XPID=$!
waitforX || ! echo failed in waitforX || exit
"$DESKTOP" 2>/tmp/wm_errors &
export WM_PID=$!
[ -x $HOME/.setbackground ] && $HOME/.setbackground
[ -x $HOME/.mouse_config ] && $HOME/.mouse_config &
[ $(which "$ICONS".sh) ] && ${ICONS}.sh &
[ -d "$HOME/.X.d" ] && find "$HOME/.X.d" -type f -print | while read F; do . "$F"; done
tc@box:~$ tce-status -i|grep nvidia
nvidia-304.125-3.16.6-tinycore
tc@box:~$ lspci -v
00:09.0 VGA compatible controller: NVIDIA Corporation NV44A [GeForce 6200] (rev a1) (prog-if 00 [VGA controller])
Subsystem: eVga.com. Corp. Device b399
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 11
Memory at cf000000 (32-bit, non-prefetchable) [size=16M]
Memory at b0000000 (32-bit, prefetchable) [size=256M]
Memory at ce000000 (32-bit, non-prefetchable) [size=16M]
Expansion ROM at cdfe0000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: nvidia
-
Remove Xvesa from onboot.lst and replace it with Xorg-7.7.tcz.
-
I guess this explains it, but what to do?
When you load Xvesa, Xfbdev or Xorg-7.7, the extension start-up script copies the text "Xvesa", "Xfbdev" or "Xorg" to /etc/sysconfig/Xserver. If you loaded Xorg-7.7 and then Xvesa and you would like to use Xorg, then you need to edit /etc/sysconfig/Xserver to read "Xorg" and then "startx"
-
Remove Xvesa from onboot.lst and replace it with Xorg-7.7.tcz.
Hi gerald_clark,
Xvesa wasn't in my onboot.lst. Here it is:
nano.tcz
firefox-official.tcz
xfe.tcz
graphics-3.16.6-tinycore.tcz
nvidia-304.125-3.16.6-tinycore.tcz
pci-utils.tcz
Xorg-7.7-3d.tcz
-
Something to do with X?
Do you have the nvidia file /usr/local/lib/X11/modules/extensions/libglx.so.304.51 (or similar) loaded?
-
Do you have the nvidia file /usr/local/lib/X11/modules/extensions/libglx.so.304.51 (or similar) loaded?
I have /usr/local/lib/xorg/modules/extensions/libglx.so.304.125. Shouldn't X load this when it parses xorg.conf load "glx"?
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 304.125 (buildmeister@swio-display-x86-rhel47-08) Mon Dec 1 21:14:12 PST 2014
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection
Section "Files"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
EndSection
Section "Module"
Load "glx"
EndSection
Section "DRI"
Mode 0666
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Virtual 800 600
Depth 24
Modes "800x600"
EndSubSection
EndSection
-
I have /usr/local/lib/xorg/modules/extensions/libglx.so.304.125. Shouldn't X load this when it parses xorg.conf load "glx"?
If the nvidia xorg.conf is correct, the nvidia kernel module is loaded and the nvidia version of various libX* are all present, then yes.
Does /var/log/Xorg.0.log show any relevant errors?
-
Does /var/log/Xorg.0.log show any relevant errors?
No Xorg log.
tc@box:/var/log$ ls -a
./ ../ autologin wtmp
-
If you issued the command "startx" or "Xorg -nolisten tcp", even if things fail immediately there is usually at least a couple of lines in Xorg.0.log.
What do you get when you try "Xorg -nolisten tcp"?
-
What do you get when you try "Xorg -nolisten tcp"?
The screen went blank. Didn't know how to recover, so rebooted.
-
You could try ctrl-alt-F1 and then "sudo killall Xorg.bin"
-
Probably always better (if X hangs and you can't get out) instead of hard reboot/shutdown:
ALT+SysRq + R,E,I,S,U,B
-
You could try ctrl-alt-F1 and then "sudo killall Xorg.bin"
No process killed. Apparently Xorg is not running. Does it not start automatically?
tc@box:~$ cat /mnt/sda1/tce/onboot.lst
nano.tcz
firefox-official.tcz
xfe.tcz
graphics-3.16.6-tinycore.tcz
nvidia-304.125-3.16.6-tinycore.tcz
pci-utils.tcz
Xorg-7.7-3d.tcz
-
Probably always better (if X hangs and you can't get out) instead of hard reboot/shutdown:
ALT+SysRq + R,E,I,S,U,B
O.k. Thank you Misalf.
-
Everything bitweisor posts indicates Xvesa is running, not Xorg.
run 'ls -l /etc/sysconfig/tcedir' and see if you are looking at the wrong tce directory.
-
Everything bitweisor posts indicates Xvesa is running, not Xorg.
run 'ls -l /etc/sysconfig/tcedir' and see if you are looking at the wrong tce directory.
tc@box:~$ ls -l /etc/sysconfig/tcedir
lrwxrwxrwx 1 root root 13 Jul 19 12:20 /etc/sysconfig/tcedir -> /mnt/sda1/tce/
I'm pretty sure it's the only one I have.
-
Are you running tce-load in bootlocal.sh?
-
Are you running tce-load in bootlocal.sh?
No. I wasn't aware I needed to add this to bootlocal.sh.
Should I add this now?
-
No, bootlocal.sh runs as root. tce-load shouldn't/can't.
-
Hi bitweisor
Try changing Xorg-7.7-3d.tcz to Xorg-7.7.tcz in onboot.lst then reboot and see if that helps.
-
Hi bitweisor
Try changing Xorg-7.7-3d.tcz to Xorg-7.7.tcz in onboot.lst then reboot and see if that helps.
No luck.
Do you think deleting the old packages and reinstalling would help?
-
I think if Xvesa.tcz wasn't loaded, and Xorg-7.7.tcz was badly downloaded, it should not be able to launch X at all. It would say "Failed in wait for X".
What about these?
tce-status -i | grep -i vesa
tce-status -i | grep -i xorg
-
Indications are you're running Xvesa, otherwise first line of .xsession shoud read similar to: /usr/local/bin/Xorg -nolisten tcp &
Your onboot.lst is missing Xprogs.tcz (essential). Here's the most basic onboot.lst that i believe results in a working Xorg system. Subsitute for your preferred window manager and video driver.
xf86-video-intel.tcz
Xorg-7.7.tcz
Xprogs.tcz
fluxbox.tcz
aterm.tcz
Your xorg.conf file is obvioulsy not being utiized as your xorg.conf and xrandr screen resolutions don't match. Try a very basic, simple xorg.conf file. Reboot system and check xorg.conf, xrandr and .xsession for resolution and persistent reboots. If your system isn't running in persistent mode then the changes won't take effect at reboot. Here's a good, basic xorg.conf file, change to your preferred driver, etc.
Section "Monitor"
Identifier "Monitor0"
HorizSync 28.0 - 96.0
VertRefresh 50.0 - 75.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Card0"
Driver "intel"
BusID "PCI:0:1:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 16
SubSection "Display"
Depth 16
Modes "1152x864"
EndSubSection
EndSection
Have you tried nouveau driver?
Since you have old hardware, may want to try TC 4 which may have more appropriate older kernel, Xorg and video driver.
-
1. What are you booting from?
2. Show the output of 'showbootcodes'
3. Show the output of 'ls /etc/sysconfig/tcedir'
4. Show the output of 'cat /etc/sysconfig/tcedir/onboot.lst'
-
O.k. everybody. I was able to get Xorg to run. I had to remove "Xvesa", then add "Xorg" to the /etc/sysconfig/Xserver file. Finally I added it to .filetool.lst. The nvidia driver is now working.
Thank you so much, to everyone who helped me with this one. I can't thank you enough.
-
The only reason you would have Xvesa in /etc/sysconfig/Xserver is that you are loading Xvesa.
Instead of trying to fudge the fact with .filetool.lst you need to find where you are loading Xvesa and correct it.
-
The only reason you would have Xvesa in /etc/sysconfig/Xserver is that you are loading Xvesa.
Instead of trying to fudge the fact with .filetool.lst you need to find where you are loading Xvesa and correct it.
Yeah, I know gerald. I call it a kludge the size of Montana, but it's working so far.
If anyone can point me in the right direction I'd appreciate it.
-
Hi bitweisor
I would recommend providing the information gerald_clark requested:
1. What are you booting from?
2. Show the output of 'showbootcodes'
3. Show the output of 'ls /etc/sysconfig/tcedir'
4. Show the output of 'cat /etc/sysconfig/tcedir/onboot.lst'
It might provide a clue as to what's going on.
-
Hi bitweisor
I would recommend providing the information gerald_clark requested:
1. What are you booting from?
2. Show the output of 'showbootcodes'
3. Show the output of 'ls /etc/sysconfig/tcedir'
4. Show the output of 'cat /etc/sysconfig/tcedir/onboot.lst'
It might provide a clue as to what's going on.
Ok. thanks. Here they are:
tc@box:~$ showbootcodes
loglevel=3 cde waitusb=5 initrd=/boot/core.gz BOOT_IMAGE=/boot/vmlinuz
tc@box:~$ ls /etc/sysconfig/tcedir
firstrun onboot.lst optional/ xwbar.lst
mydata.tgz ondemand/ provides.db
tc@box:~$ cat /etc/sysconfig/tcedir/onboot.lst
nano.tcz
firefox-official.tcz
xfe.tcz
graphics-3.16.6-tinycore.tcz
nvidia-304.125-3.16.6-tinycore.tcz
pci-utils.tcz
Xorg-7.7-3d.tcz
tc@box:~$
-
Hi bitweisor
The first thing you need to do is get rid of that CDE bootcode. That used only for read only media like CDs and DVDs.
What do you get for:
ls -l /mnt/sda1
and:
ls -l /mnt/sda1/cde
-
Hi bitweisor
The first thing you need to do is get rid of that CDE bootcode. That used only for read only media like CDs and DVDs.
What do you get for:
ls -l /mnt/sda1
and:
ls -l /mnt/sda1/cde
Hi Rich,
I'm booting from CD.
Here's my sda1:
tc@box:~$ ls -l /mnt/sda1
total 8
drwxr-xr-x 2 tc staff 4096 Jul 20 12:39 downloads/
drwxrwxr-x 4 tc staff 4096 Jul 19 20:41 tce/
There is no cde under sda1.
-
Hi bitweisor
Then Xvesa is probably coming from the CDE directory of the CD.
-
Hi bitweisor
Then Xvesa is probably coming from the CDE directory of the CD.
Is there any way to prevent it from loading or do I need to install TC to a hard drive?
-
Hi bitweisor
If you burn Core to a CD that might work since it's a command line environment.
http://tinycorelinux.net/downloads.html
-
Hi bitweisor
Other possibilities include installing to a hard drive, installing to a USB thumb drive if your machine can boot from USB, or
re-mastering the CD.
-
Hi bitweisor
Other possibilities include installing to a hard drive, installing to a USB thumb drive if your machine can boot from USB, or
re-mastering the CD.
O.k. Thanks Rich.
I think I might try installing to USB and see how that goes.